Migrating a Gathering Company’s Pipelines from Legacy Datasets into an Enhanced PODS 3.2 Model

1. Migrating a Gathering Company’s Pipelines from Legacy Datasets into an Enhanced PODS 3.2 Model  Presented by Kenneth Greer – CenterPoint Energy Gas Transmission

2. Contents Different type and quality of data sets 1 Conversion tools 2 Obstacles - Short Timeline 3 The Plan 4

3. Existing data sets – Lotus Notes 1 • Pipe and equipment attributes • Derived from old mainframe data • Poor maintenance

4. Existing data sets - MapInfo 1 • Primary software for field operations • Synchronization already established • Individual file per pipeline • Field GPS of good quality • Excellent maintenance • Field tools already created • No training needed

5. New data sets - Maximo 1 • Scheduling and maintenance • Work Orders • Training needed

6. New data sets - PODS 3.2 enhanced 1 • Enterprise database • Pipe and equipment attributes • Spatialized • Vendor application • Training needed

7. New data sets - ArcGIS 1 • Used to load and maintain centerline • Vendor application required • Training needed

8. Conversion tools 2 • Internally developed loader • Vendor applications • Company developed synchronization applications fro Maximo • Re-stationing process using ArcGIS, MS Access and internally developed loader • Reports generated • Cross reference files maintained in Oracle

9. Obstacles 3 • Six months • Mismatch of pipeline measures – spatial vs. data • Load all data – active, abandoned, sold, etc. • Not all pipeline data had spatial counter parts • Load and re-station all pipelines • Training

10. The Plan 4 • Determine pipeline and route status and match to GIS components to determine routes • Load all data to PODS using measures in Lotus Notes • Re-station per GIS lengths • Load to Maximo • Training for PODS and Maximo • Review re-stationing reports • Correct data with the new interfaces

11. Questions 5