Oil and Gas Interoperability (OGI)

Transcription

1 Oil and Gas Interoperability (OGI) OGI Pilot Program ISO Technical Specification Houston, Texas-March 19, 2014 Alan Johnston, MIMOSA President, ISO TC 184/WG 6 Convener

2 Key Oil and Gas IT Problems Fragile systems integration Expensive capital and sustainment costs Limited flexibility Constrained innovation Trapped data High switching costs

3 Critical Intersection for a Supplier Neutral Ecosystem Enabling Multi-domain Systems Interoperability Enterprise Business Systems Big Data and Analytics Ecosystem Control Console Supplier Neutral Open Specifications LIFE CYCLE ENGINEERING Systems Automation and Control Systems

4 IEEE: The capability IEEE Interoperability Definition of two or more systems or elements to exchange information and to use the information that has been exchanged. for units of equipment to work together to do useful functions. that enables heterogeneous equipment, generally built by various vendors, to work together in a network environment. of two or more systems or components to exchange information in a heterogeneous network and use that information.

5 Current Eco-system Options Walled Garden Large suppliers proprietary eco-systems Suppliers make the rules Suppliers often set high barriers to entry High switching cost O/O lock in O/O data is trapped in proprietary apps Innovation can be constrained Open Source Can be chaotic Suppliers may be unknown Ambiguous support model Fragmentation often takes place Interoperability may become poor Critical infrastructure often precluded Industrial solutions are still heavily dependent on large scale custom integration services efforts. Individual Owner/Operators redundantly bear the development and sustainment cost for each of these efforts.

6 Transforming the Oil and Gas Industry Solutions Model From Systems Integration to System of Systems Interoperability Custom Integration Open Industrial IT Interoperability Ecosystem Custom development Specific data adapters Owner/operator responsible for sustainment Configuration rather than development Based on supplier neutral open standards Plug and Play model Suppliers responsible for sustainment May incorporate open source Does not require open source

7 OGI Principles OGI Solutions Process Industry requirements-driven solution methodology All working documents and results openly published on the MIMOSA website OGI Pilot Public piloting and assessment Focus on COTS products OGI Ecosystem Based on supplier-neutral international and industry standards incorporated by reference Fully dressed use cases, including reusable scenarios and service definitions Semantics, objects, event-driven architecture

8 OGI Pilot Business Use Cases Roadmap - Part 1 Enterprise Capital Project Data Management Standards Fiatech EDRC Use Fiatech Case EDRC 1 Use Case 2 Plan / Program / Contract Engineer / Design Procure Fabricate / Construct Complete / Commission / Startup Operate / Maintain Decommissi on / Dispose Continuous Handover of Structured Digital Assets Establishing an Environment for Lifecycle System of Systems Interoperability Sustained Lifecycle Digital Asset Management OGI Use Case 1: Capital project handovers to O&M OGI Use Case 4: Enterprise Product Data Library Management OGI Use Case 10: Automated provisioning of O&M systems OGI Use Case 11: Enterprise Reference Data Library (RDL) Management Fiatech EDRC Use Case 1: Pump Replacement Specification Handover (O/O to EPC) Fiatech EDRC Use Case 2: Field Instruments & Control System (EPC to Supplier)

9 OGI Pilot Business Use Cases Roadmap - Part 2 Enterprise Capital Project Data Management Standards Plan / Program / Contract Engineer / Design Procure Fabricate / Construct Complete / Commission / Startup Operate / Maintain Sustained Lifecycle Digital Asset Management Continuous Handover of Structured Digital Assets Sustaining the Interoperable O&M Environment OGI Use Case 2: Recurring Engineering Updates to O&M OGI Use Case 3: Field Changes to Plant/Facility Engineering OGI Use Case 4: Enterprise Product Data Library Management OGI Use Case 5: Asset Installation/Removal Updates OGI Use Case 6: Preventive Maintenance Triggering OGI Use Case 7: Condition-Based Maintenance Triggering OGI Use Case 8: Early Warning Notifications OGI Use Case 9: Incident Management/Accountability OGI Use Case 10: Provisioning of O&M systems OGI Use Case 11: Enterprise Reference Data Library (RDL) Management Decommissi on / Dispose

10 OGI Ecosystem Simplified Systems Architecture Enterprise Business Systems Engineering Design Construction Procurement Standardized Interoperability Register Operations Management Operations Risk Management Maintenance Management OpenO&M Information Service Bus Model Construction Management Industrial DMZ Automation and Control HSE and Operation Monitoring Prognostic and Health Management ISBM services ISO SPARQL OPC Interfaces Deterministic interface Enterprise Mirrored Reference Data Library/ Enterprise Specific Reference Data Library Device Automation Control Bus Device Sensor/ Transducer Enterprise Specific Reference Data Library EPC/OEM Reference Data Libraries PCA Reference Data Library

11 Debutanizer

12 Debutanizer Tower P&IDs Worley Parsons

13 OGI Pilot Phase 1+ Presentation IBM ISBM Implementation Provides Connectivity Environment AVEVA P&ID ISO (Proteus) Bentley OpenPlant ISO15926 (OWL) UniSA Transform MIMOSA CCOM-ML IOMOG Register MIMOSA CCOM-ML IBM IIC Intergraph P&ID ISO (Proteus) ISO Reference Data MIMOSA CCOM Reference Data Worley Parsons-Lead EPC for Downstream OGI Pilot Developing and Managing Reference Engineering Data Set Providing standard engineering artifacts used for EPC process Tag Register OSIsoft PI/AF Historian OPCUA

14 Upstream and Downstream The Same Basic Engineering Artifacts Wellhead P&ID Offshore Production Unit P&ID

15 OGI Pilot Coordination Call 3/06/2014 Activity update for OGI Pilot and Industry Standards Leadership Council (SLC)-March Houston, TX SLC (Energistics/MIMOSA/PCA) Shared Asset Model (SAM) Workshop Houston, TX March Fiatech Showcase-March 31-April 3- Huntington Beach, CA Pilot Plan for 2014 Incorporate updates to specifications and related products driven from gap analysis, EDRC and IIMM Add more details to engineering data sets to meet O/O requirements and have an EPC for each technology Re-implement O&M Use Cases 5, 6 and 7 using new Joint IT Architecture O&M Suppliers Sub-team to test Microsoft middleware Initiate Upstream Asset Pilot in conjunction with SLC/SAM O&M Sub-team and ISBM enabled Microsoft Middleware Current: Aveva (WorkMate), Rockwell Automation Coordinate Next Week Possible: Invensys, OSI Soft and Emerson Process Management Need to confirm UniSA Transform against new Bentley output Georg, Keith, Avin

16