Neal Hill Resume - Consolidated Edison of New York, Inc.

Designed and implemented a system to schedule, track, and report on equipment and procedural compliance within the power generating facilities of Con Edison. The business and data analysis was encapsulated using Object Modeling Technique (OMT) [Rumbaugh, et al] and translated into Gane/Sarson to be input into System Architect CASE tool. The system was implemented using Powerbuilder 2.0 to develop the client application and Gupta SQLBase (DOS/Windows), SQL Server (OS/2) and Sybase (DEC VAX VMS) to develop the database counterpart (server).
Ported system to Visual BASIC 2.0 with the database access coded first in SQLServer Toolkit and then in ODBC. This was Consolidated Edison's first Visual BASIC client/server application. Expanded Compliance System to include lubrication scheduling, human resource procedures, and any other schedule-based business procedures. The system also necessitated the construction of a general purpose toolkit (VBGRID), written in Visual BASIC, to initialize and manage Visual BASIC grid controls for database access and user interaction.

Designed and implemented DBObject, an abstraction of database access for Visual BASIC. DBObject provided the Visual BASIC application developer with a seamless, easy-to-use database datatype (called a DBObject) and collection of functions and subroutines to perform database queries and data processing. The benefit of DBObject was that it became a consistent, API-independent method for accessing database management systems. An application using DBObject with an underlying implementation of ODBC could be ported to Q+E Multilink/VB or SQL Server Toolkit without changing the application database access code. Porting the application in the reverse direction was also possible. DBObject was written in Visual BASIC 3.0 using ODBC and Q+E Multilink/VB for database access.

Directed management and a team of analysts in producing the initial object-oriented analysis and design (using OMT) and behavioral analysis (proprietary) for the Indian Point Work Management System. This system replaced the planner's manual tools for work order request processing and work package building with a "file cabinet/folder" desktop metaphor. Similar to an electronic organizer, IPO was the client frontend tool for routing, approving, scheduling, and assigning materials and resources for work order requests. The client application was implemented in Visual BASIC 3.0 using DBObject (see above) to access DB2, SQL Server, and Sybase as the database servers.