1 / 21

Real Time Data As A Corporate Asset

Real Time Data As A Corporate Asset. Presenters: Steve Browder John Rodgers. Transmission Segment. 16,700 miles of pipeline 44 storage fields. NY. 12,500 miles of pipeline 140 compressor stations 585,000 horsepower of compression 220 Bcf working gas storage capacity in 44 fields

renee
Download Presentation

Real Time Data As A Corporate Asset

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Real Time Data As A Corporate Asset Presenters: Steve Browder John Rodgers

  2. Transmission Segment 16,700 miles of pipeline 44 storage fields

  3. NY 12,500 miles of pipeline 140 compressor stations 585,000 horsepower of compression 220 Bcf working gas storage capacity in 44 fields 4.5 Bcf peak day storage deliverability 1.2 Tcf annual throughput 7.3 Bcf peak day deliverability PA NJ MD OH WV VA KY NC TN

  4. SCADA Data SCADA Data Attributes Valve Position Line Pressure Engine Status etc... SCADA Data SCADA Data SCADA Data SCADA Primary Users - Gas Control Users Location - Charleston, WV Number of Sites - 500+ Data Granularity - 2 Minutes NY PA NJ MD OH WV VA KY NC TN

  5. EM Data Attributes Flow Total Specific Gravity BTU etc... EM Data EM Data EM Data EM Primary Users - Gas Measurement Users Location - Charleston, WV Number of Sites - 800+ Data Granularity - 1 Hour NY PA NJ MD OH WV VA KY NC TN

  6. Compressor Automation Data Compressor Automation Data Attributes Oil Pressure Run Hours RPM etc... Compressor Automation Data Compressor Automation Data Compressor Automation Data Compressor Automation Primary Users - Station Employees Users Location - System Wide Number of Sites - 140+ Data Granularity - Sub-Second NY PA NJ MD OH WV VA KY NC TN

  7. PI Real Time Systems SCADA Data EM Data Charleston WV NY SCADA EM PA NJ MD OH WV VA KY SCADA Data NC TN EM Data SCADA Data EM Data

  8. Environmental Turbine Monitoring Modeling Facility Planning Gas Control Field PI Users NY PA NJ MD OH WV VA KY NC

  9. Compressor Automation Data Attributes Oil Pressure Run Hours RPM etc... Compressor Automation Data Compressor Automation Data Compressor Automation Data Real Time Systems SCADA Data EM Data Attributes Gas Flow Total Specific Gravity BTU etc... NY EM Data PA Attributes SCADA Data NJ Valve Position Line Pressure Engine Status etc... MD OH WV SCADA Data VA KY SCADA Data NC TN EM Data SCADA Data EM Data

  10. Infamous IT “Black Box” Solution SCADA Data EM Data Compressor Automation Data NY Compressor Automation Data PA EM Data NJ MD SCADA Data OH WV VA KY NC TN

  11. P resentation Columbia Gas Transmission Users and Business Applications O f P Convert Data to Information I T ags A cross R eal T ime S ystems Data Abstraction Black Box 3 Layers I/O Abstraction Communication Disclaimer: The name “POPTARTS” does not reflect the views of management and therefore will only be used as an internal engineering name.

  12. Communication Layer MBS100 Driver ACME Driver OPEN BSI Driver OPC Driver Input 7 Analog Input 8 Analog Input 5 Analog Input 3 Discrete Input 9 Analog Inputs Input 4 Discrete Input 6 Discrete Inputs • Purpose • Support for Low Cost Field Devices with non-standard data • Support for Low Cost Field Devices with non-standard communications Bristol Babcock Compressor Automation Device Columbia SCADA Device Columbia EM Device ACME Device

  13. I/O Abstraction Layer EM Database Layout Analog Input 1 = EM Device Input 9 Analog Input 2 = EM Device Input 5 Discrete Input 1 = EM Device Input 6 ACME Database Layout SCADA Database Layout Analog Input 1 = SCADA Device Input 7 Analog Input 2 = SCADA Device Input 8 Discrete Input 1 = SCADA Device Input 3 Discrete Input 2 = SCADA Device Input 4 Bristol Babcock Database Layout Analog Input 1 = ... Communication Layer ACME MBS100 OPC OPEN BSI Compressor Automation SCADA Inputs EM ACME Inputs Inputs

  14. Purpose • Remove Field Device Database Layout from Business Applications • Separate Business Requirements and Field Device Requirements • Opportunity to Automate Field Device Configuration I/O Abstraction Layer EM Database Layout ACME Database Layout SCADA Database Layout Bristol Babcock Database Layout Communication Layer ACME MBS100 OPC OPEN BSI Compressor Automation SCADA Inputs EM ACME Inputs Inputs

  15. Data Abstraction Layer Location.FacilityType.EquipmentGroup…Attribute = Bristol Database Analog Input 9 Artemas.CS.Compression.Unit1.Status = SCADA Database Discrete Input 7 Artemas.CS.Compression.Unit1.RPM Artemas.CS.Compression.Unit1.RunHours = Bristol Database Analog Input 3 Artemas.MR.804418.StaticPressure = EM Database Analog Input 4 Artemas.MR.804418.Run1.StaticPressure = EM Database Analog Input 5 Artemas.MR.803773.StaticPressure = SCADA Database Analog Input 12 I/O Abstraction Layer EM Database Layout ACME Database Layout SCADA Database Layout Bristol Babcock Database Layout Communication Layer ACME MBS100 OPC OPEN BSI Compressor Automation SCADA Inputs EM ACME Inputs Inputs

  16. Data Abstraction Layer Artemas.CS.Compression.Unit1.RPM = Bristol Database Analog Input9 Artemas.CS.Compression.Unit1.Status = SCADA Database Discrete Input 7 Artemas.CS.Compression.Unit1.RunHours = Bristol Database Analog Input 3 Artemas.MR.804418.StaticPressure = EM Database Analog Input 4 Artemas.MR.804418.Run1.StaticPressure = EM Database Analog Input 5 Artemas.MR.803773.StaticPressure = SCADA Database Analog Input 12 ACME Database Analog Input 10 ACME Database Discrete Input 3 Location.FacilityType.EquipmentGroup…Attribute I/O Abstraction Layer EM Database Layout ACME Database Layout SCADA Database Layout Bristol Babcock Database Layout Communication Layer ACME MBS100 OPC OPEN BSI Compressor Automation SCADA Inputs EM ACME Inputs Inputs

  17. Data Abstraction Layer Real Time Data PI Self Scheduling Data In Real Time I/O Abstraction Layer EM Database Layout ACME Database Layout SCADA Database Layout Bristol Babcock Database Layout Communication Layer ACME MBS100 OPC OPEN BSI Compressor Automation SCADA Inputs EM ACME Inputs Inputs

  18. PI Applications Process Book, Datalink Active View, API/SDK COM/DCOM, OPC Clients, ODBC, other Data Abstraction Layer Location.FacilityType.EquipmentGroup…Attribute = PI Tag Name I/O Abstraction Layer EM Database Layout ACME Database Layout SCADA Database Layout Bristol Babcock Database Layout Communication Layer ACME MBS100 OPC OPEN BSI Compressor Automation SCADA Inputs EM ACME Inputs

  19. Anticipated Uses • Provide Efficiency data from Compressor Stations • Support for Operations Optimization • Support for Reliability Centered Maintenance • Support for Standards • Increased Remote Monitoring by Field Personnel • Support for External Customer Access POPTARTS Data Abstraction Layer Location.FacilityType.EquipmentGroup…Attribute I/O Abstraction Layer EM Database Layout ACME Database Layout SCADA Database Layout Bristol Babcock Database Layout Communication Layer ACME MBS100 OPC OPEN BSI

  20. Conclusion • The object model provides for an unambiguous namespace that is easily navigable by users familiar with the physical assets and equipment. • PI provides a proven and reliable archive for vast quantities of operational data. • PI desktop tools permit us to utilize our existing investment in Microsoft operating systems and office applications. • Standards such as COM/DCOM, ODBC, and OPC will drastically simplify the task of interfacing both legacy and new applications to real time operational data. • Our experience suggests that the most valuable uses for this data are not yet known and will not appear until after several months of data have been archived. These uses will provide the value of real time data as a corporate asset.

  21. Questions With Answers • Product used to implement POPTARTS? • OA Enterprise by Wellspring Solutions Inc. integrated with the PI historian using the PI SDK/API. • Project Sponsors/Drivers? • IT Infrastructure Project. • Project Timeframe? • This year implement namespace and start using PI tools for access. • Questions Without Answers • How many POPTARTS boxes? • Where will they be located? • What Granularity of Data is needed? • Will the current PI tools support our new namespace?

More Related