An Operations and Maintenance Information Open System Alliance

  • Slides: 17
Download presentation
An Operations and Maintenance Information Open System Alliance The Oil and Gas Interoperability (OGI)

An Operations and Maintenance Information Open System Alliance The Oil and Gas Interoperability (OGI) Pilot Dr. Avin Mathew Technical Director MIMOSA

Today’s Problems Fragile custom integration Constrained innovation Expensive capital and sustainment costs Limited flexibility

Today’s Problems Fragile custom integration Constrained innovation Expensive capital and sustainment costs Limited flexibility Trapped data High switching costs 2

Transforming the Oil and Gas Industry Solutions Model Custom Integration Open Interoperability Ecosystem Custom

Transforming the Oil and Gas Industry Solutions Model Custom Integration Open Interoperability Ecosystem Custom development Specific data adapters Owner/operator responsible for sustainment OGI Ecosystem Configuration rather than development Based on well defined standards Suppliers responsible for sustainment 3

OGI Principles OGI Solutions Process OGI Pilot • Industry requirements-driven solution methodology • All

OGI Principles OGI Solutions Process OGI Pilot • Industry requirements-driven solution methodology • All working documents and results openly published on the MIMOSA website • 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 • Semantics, objects, event-driven architecture 4

Context for Collaboration 6

Context for Collaboration 6

High-Level System Architecture

High-Level System Architecture

Prioritised Use Cases Use Case 1 Information Handover from EPC to O/O Use Case

Prioritised Use Cases Use Case 1 Information Handover from EPC to O/O Use Case 2 Recurring Engineering Updates to O&M Use Case 3 Field Changes to Plant/Facility Engineering Use Case 4 Online Product Data Library Use Case 5 Asset Configuration Updates Use Case 6 Preventive Maintenance Triggering Use Case 7 Condition-Based Maintenance Triggering Use Case 8 Early Warning Notifications Use Case 9 Incident Management/Accountability Use Case 10 Information Provisioning of O&M Systems Use Case 11 Enterprise Reference Data Library Management 8

OGI Pilot Business Use Cases Roadmap – Part 1 Enterprise Capital Project Data Management

OGI Pilot Business Use Cases Roadmap – Part 1 Enterprise Capital Project Data Management Standards Plan / Program / Contract Engineer / Design Procure Fabricate / Construct Complete / Commission / Startup Continuous Handover of Structured Digital Assets Establishing an Environment for Lifecycle System of Systems Interoperability Operate / Maintain Decommission / Dispose 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)

OGI Pilot Business Use Cases Roadmap – Part 2 Enterprise Capital Project Data Management

OGI Pilot Business Use Cases Roadmap – Part 2 Enterprise Capital Project Data Management Standards Engineer / Procure / Construct Operate / Maintain Continuous Handover of Structured Digital Assets Decommission / Dispose Sustained Lifecycle Digital Asset Management 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

Systems Landscape Data Flow Diagram

Systems Landscape Data Flow Diagram

Standard Information Models ISO 15926 • Reference data and capital project artefacts MIMOSA CCOM

Standard Information Models ISO 15926 • Reference data and capital project artefacts MIMOSA CCOM • Lifecycle engineering configuration, condition, work and reliability management OPC Classic/UA • Real-time and historical time series data, alarms and events Energistics PRODML/WITSML MESA B 2 MML • Production and well data • Production schedules, forecasts, demand 12

Reference Environment Execution Environment AVEVA P&ID Bentley Open. Plant Power. PID Intergraph Smart. Plant

Reference Environment Execution Environment AVEVA P&ID Bentley Open. Plant Power. PID Intergraph Smart. Plant P&ID Aspen Basic Engineering Sharecat/ Eq. Hub Microsoft ESB (Terawe), IBM ISBM, Assetricity Simple. ISBM ISO 15926 Proteus Maintenance Management System ISO 15926 Part 8 OWL MIMOSA CCOM ISO 15926 Proteus Uni. SA ISO 15926 Eng. XML Transform Engine MIMOSA CCOM Assetricity IOM-OG Register MIMOSA CCOM Rockwell Plant. PAx IBM IIC MIMOSA CCOM ISO 15926 Vendor XML OPC UA ISO 15926 Reference Data IEC 61360 ISO 13709 (API 610) ISA TR 20 ISO 14224 MIMOSA CCOM OSIsoft PI

P&ID Information • • • Functional location, identifier, tag and classification Engineering properties Transmitter

P&ID Information • • • Functional location, identifier, tag and classification Engineering properties Transmitter OPC tag Transmitter range and unit of measure Plant breakdown structure Nozzles/ports and classification Directed connections between nozzles/ports Canvas dimensions X, Y coordinates for functional locations Symbol orientation 15

How To Get Involved • Standards, specs and working documents are freely available at

How To Get Involved • Standards, specs and working documents are freely available at http: //mimosa. org • Standing call every two weeks at 3 pm Thursday (Central Time) 16

Dr. Avin Mathew Technical Director MIMOSA amathew@mimosa. org Alan Johnston President MIMOSA atjohn@mimosa. org

Dr. Avin Mathew Technical Director MIMOSA amathew@mimosa. org Alan Johnston President MIMOSA atjohn@mimosa. org www. posccaesar. org 17