MIMOSA. The Oil and Gas Interoperability (OGI) Pilot Enabling Sustainable Interoperability for the Oil and Gas Industry

Size: px
Start display at page:

Download "MIMOSA. The Oil and Gas Interoperability (OGI) Pilot Enabling Sustainable Interoperability for the Oil and Gas Industry"

Transcription

1 MIMOSA The Oil and Gas Interoperability (OGI) Pilot Enabling Sustainable Interoperability for the Oil and Gas Industry MIMOSA Members Meeting Applied Technology Publications Dec 11, 2013 Alan Johnston MIMOSA President ISO TC 184/WG 6 Convener

2 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)

3 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

4 MIMOSA Summary Focus on Physical Asset Life-Cycle Management and Facilities O&M Develops and publishes industry-driven standards in alignment with ISO Officially organized as a 501 c(6) non-profit industry association in 1997 Membership Owner/Operators Oil and Gas, Chemical, Aerospace and Defense Sectors Suppliers/integrators Academia/Researchers Industrial Media Founding Member and IP Manager for OpenO&M Initiative OpenO&M Owner/Operator Leadership Council Founding Member Standards Leadership Council

5 Requirements-driven Development of Standards MIMOSA has a rich history of developing industry standards which are driven by industry requirements Open Systems Architecture for Enterprise Application Integration (OSA-EAI)-1997 Open Systems Architecture for Condition Based Maintenance (OSA-CBM)-1999 OpenO&M Information Service Bus Model (ISBM)-2011 OpenO&M Common Interoperability Register (CIR)-2011 MIMOSA works closely with formal standards bodies to help develop international standards reflecting industry requirements ISO TC 108/SC 5 ISO (CBM) ISO TC 184/SC 5 ISO (O&M) ISO TC 184/WG 6 Developing ISO OGI Technical Specification

6 Immutable, Globally-Unique, Non-Meaningful Integer Object Identifiers MIMOSA CCOM Object Identifier History 1998 Distinct Objects for Functional Tag (Segment), Product Catalog Object (Model), and Serialized Equipment (Asset) CRIS MED ASCII Document Exchange CRIS DTD XML Document Exchange 2002 CRIS XML Schema Point-to- Point Web Services 2003 CRIS XML Schema for Compound Documents Web Services 2007 Immutable, Globally-Unique, Non-Meaningful ISO/IEC Object Identifier CCOM XML Schema with ISBM Web Services Today OpenO&M Information Service Bus & Common Interoperability Register

7 OSA-CBM Dual Use Technology Program - Office of Naval Research MIMOSA Information Network (MIN) The OSA-CBM MIN Demonstration Concept Remote Diagnostics Provider A June 21, 2000 MIN-Viewer OSA-CBM Presentation Alan T. Johnston MIN Project Director Carrier USS NIMITZ Remote Maintenance Coordination Center Remote Diagnostics Provider B MIN-Viewer Segment Navigation 1 User Interface Modeled On The Microsoft Windows Explorer

8 Army Collaborative Telemaintenance Army CECOM U.S. Army CECOM Collaborative Telemaintenance Project Phase I Demonstration Briefing July 31, 2002 Alan Johnston MIMOSA Kenneth Bever MIMOSA Bob Walter Penn State ARL U.S. Army Collaborative Telemaintenance Demonstration Revised 07/03/2002 Phase I Demonstration Demo Architecture Based on reusable MIN-Client & MIN- Server Components Maintenance Technician (MT) Simulated Platform (SP) CMA Showing Measurement Events In Alarm Condition Data Request for data Condition data Failure and diagnostic info Request for work PMA Data Services (PDS) MIN-Clients Reg Dyn Maintenance Subject Matter Expert (SME) Central Maintenance Aid (CMA) User Interface (CGUI) CMA Data Services (CDS) CMAG { MIN-Clients Reg Dyn Trend Work XML User Interface (PGUI) MIN-Servers Portable Maintenance Aid (PMA) MIN-Servers PMA Database Services (CDBS) XML Reg Dyn Trend Work CMA Database Services (CDBS) Persistent DB } PMAG Trend Work Reg Dyn Trend Work Persistent DB MIN-Client & MIN-Server are Trademarks of MIMOSA

9 UNCLASSIFIED Platform Life-cycle Information Management Concept Mapping- Aerospace & Defense Industry Aerospace and Defense Industry Developed Life-cycle Reference Data Exchange Sets OAGIS Process Industry Developed, Ontology-based Geometry, Topology and Reference Information Standards Cross Industry Developed Physical Asset Management Standards (Sensor To Enterprise) STEP PLCS DEXs GEIA 927 ISO &4 GEIA STD 0007 MIMOSA OSA-EAI OSA-CBM ASD S1000D Government Developed Military Platform Element Definitions in ISO STEP AP Formats Aerospace and Defense Industry Developed IETM Standard 6 Yourfilename.ppt UNCLASSIFIED

10 Organization Legend ODH ICDM HMI DSS EAM ODH DSS EAM 1-3eTI 2 - Ivara 3 - Indus 4 - Iconics 5 - ESRG 6 - IFS 7 - Honeywell 8 - AspenTech 9 - Matrikon 10 - PdMA 11 - Synergen 12 - Yokogawa 13 - Rockwell 14 - DEI MRB HMI ODH Function Legend ALM Asset Lifecycle Mgmt & Universal ID HMI HMI CM ODH Condition Monitoring Operational Data Historian EAM DSS MRB HMI Human-Machine Interface DSS ICDM Instrumentation & Control Device Management CM ALM CM DSS EAM MRB Decision Support System Enterprise Asset Management / CMMS Maintenance & Reliability Browser OpenO&M Network CM December 2004

11 bp data model map plant lifecycle engineering procurement construction operation capability materials model Material Specifications Piping Specs. Material Master Catalog Tool Catalog Crude Assays MSDS Spare Parts Lists Stores Inventory Reliability Data equipment model Vendor Catalogs Bill of Material As-installed Equipment Data Operations Procedures Equipment & Alarm Configuration Operating Envelopes Maintenance Procedures Job plans As maintained eqpt. data As operated reliability data personnel model Vendor & Engineering Contracts Service Contracts Contracted Services Contracts Operator Unit knowledge Trade skills register Root Cause Analysis Data Work requests plant model Design Requirements Purchase Requests Construction Schedule Shift roster Daily plans Stock progressions Price sets TAR plans PM program Inspection schedule Maintenance roster Equipt. Calibration Equipt. Capability Forecast actuals model Calculations Project P&ID s Purchase Orders Invoices As-built P&ID s HAZOP minutes Tag Monitoring Locations Process Data Tank inventories Lab results Bill of Lading Transfer Advices Operator Logs TAR reports Fault data w Op Params Component tracking Inspection records Work Order History Work Permits PISTEP PIDX ISA95 OPC MIMOSA ISO14224 October 13, 2011 ISO Chevron 2007

12 The OpenO&M Initiative Enabling Open Standards-based O&M Interoperability Enterprise Business Systems Enterprise Resource Planning (ERP) Operations OpenO&M Maintenance F O U N D A T I O N Physical Asset Control Real-time Systems

13 Points of intersection Data in Motion Life Cycle Facility Mgmt

14 Reasons for Oil and Gas Interoperability (OGI) Pilot and ISO OGI TS (ISO 18101) Problem Statement Current Oil and Gas and other Asset Intensive industry enterprise solutions are too chaotic and too difficult to sustain. The current enterprise solutions model is critically dependent on large amounts of custom Systems Integration and this is a weak link. Chaotic and Fragile Vulnerable to breakage and exploitation Expensive to sustain (20% annual recurring maintenance cost) Proprietary point to point interfaces also limit flexibility and constrain innovation The current solutions model often forces data to be re-entered many times rather than managing it on a full life-cycle basis and data is trapped in proprietary applications. Decreases availability and portability of information Highly inefficient and chaotic business process Increases costs Decreases quality Owner/Operators are asking for a better Solutions Model

15 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.

16 We Need a Significant Paradigm Shift The Un-walled Garden and the OGI Ecosystem A new industry solutions model where systems of systems interoperate in an industry eco-system defined by open, supplier neutral standards Collaboration between industry standards bodies Bring proven standards together Shared, supplier neutral industry information models O/O Data is not trapped Shared, supplier neutral industry utility services, driven by industry use cases All other required conventions maintained and published by industry (not individual suppliers) Suppliers have responsibility for developing and maintaining compatibility of their own solutions components Trusted public/private organization provide third-party certification & identification Owner/Operator Leadership and Governance Incremental, prioritized transformation

17 Life-cycle Interoperability Context for O&M LIFE CYCLE ENGINEERING Systems ISO 18435

18 Critical Control Point for a Supplier Neutral Ecosystem Enabling Systems Interoperability Enterprise Business Systems Ecosystem Control Console Supplier Neutral Open Specifications LIFE CYCLE ENGINEERING Systems Automation and Control Systems

19 Why an Oil and Gas Industry Pilot Is Required The OGI Ecosystem model offers cost, quality, flexibility and risk management features distinctively superior to those achievable by individual owner/operators Establishing and validating a To Be Industry Ecosystem and the required Industry Foundation Architecture is not something which can be reasonably addressed by individual owner/operator project teams Industry Use Case-driven, solutions component specifications can be safely taken from the industry pilot and applied to real projects, only once they have been properly proven in an industry pilot Makes standards consumable A properly supported OGI Pilot provides a required transformational development and validation proving grounds at minimum total cost and risk Focused on proper asset classes and prioritized functions Downstream, mid-stream and upstream At industry scale Enables pragmatic, incremental transformation for owner operators

20 2013 MIMOSA Members Meeting-Status Have reached key milestones for OGI Pilot in preparation for Machine Readable, Supplier Neutral Handover from Capital Project to Operations and Maintenance Just published Joint MIMOSA/PCA IT Architecture Version 1.0 Are prepared to pivot back to O&M Suppliers starting in 2014

21 Owner/Operators Objective Shared Industry Foundation Architecture OpenO&M Information Service Bus Model (ISBM) OpenO&M 2 1

22 Reference Information Environment ISO Engineering & Construction PCA RDL/Ontology Context for Collaboration Semantic Context Enterprise Business Systems Transform Engine OpenO&M Information Service Bus Controls Physical Assets Execution Environment P2B Stack ISO MIMOSA O&M Requirements Repository Registry ISO ISO TC 184/WG 6

23 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 Sensor/ Transducer Automation Control Bus Sensor/ Transducer Sensor/ Transducer Enterprise Specific Reference Data Library EPC/OEM Reference Data Libraries PCA Reference Data Library

24 OGI Pilot Phase 1+ Presentation IBM ISBM Implementation Provides Connectivity Environment AVEVA P&ID Proteus Bentley OpenPlant OWL/ecXML UniSA Transform MIMOSA CCOM-ML IOMOG Register MIMOSA CCOM-ML IBM IIC Intergraph P&ID XMpLant 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 Cormac 6 Minutes OPCUA

25

26 Debutanizer P&ID 001- Worley Parsons

27 Live Interoperability Demonstration ISBM AVEVA P&ID Bentley OpenPlant XMpLant OWL/ecXML Assetricity Transform UniSA Transform MIMOSA CCOM-ML MIMOSA CCOM-ML ISO Reference Data Assetricity IOMOG Register MIMOSA CCOM Reference Data IBM IIC Provision OSI Soft PI and View MIMOSA CCOM-ML Tag Register IBM IIC OPCUA OSIsoft PI/AF Historian

28

29 Oil and Gas Interoperability (OGI) Pilot - Summary Owner/Operator leadership Industry Use Case driven - (OpenO&M, PCA and SPE DSA-TS) Use Cases Cooperatively aligned with PCA under Joint MIMOSA/PCA O&M SIG Managed like a true capital project- Worley Parsons-Lead EPC for downstream Pragmatic focus on Commercial Off The Shelf (COTS) products Suppliers assume responsibility for compliance of their own products Current Status-Planning Phase 2 inclusions based on closing gaps identified in Phase 1, adding existing O&M use cases and adding upstream specific elements Publication Working documents and results are on the mimosa website at Proven OGI Pilot output provides basis for ISO Technical Specification Industry press coverage for OGI Pilot iring Today

30 LEVERAGING THE ISO PROCESS FOR ESTABLISHING STANDARDS AND SPECIFICATIONS The ISO Manufacturing asset management Integration Task Force ISO OGI Technical Specification (ISO 18101)

31 ISO TC184 Manufacturing Asset Management Integration Task Force March 2009 Total Asset Life-Cycle Summary FIATECH POSC CAESAR Commissioning MIMOSA/OpenO&M Continuous Improvement Feedback Loops Product Design Asset MFG Construction Operations & Maintenance (O&M) End of Life Product/Asset/Plant/Facility/Vehicle Life-Cycles SC1 & SC4 Other Standards IEC TC 65 Standards SC5, SC5-IEC/JWG5, SC4-SC5/JWG8 OpenO&M & Other Standards Other Standards ISO/IEC UID DB 1 DB 2 DB 3 DB 4 DB N DB N+1 DB N+2 DB N+4 Services Oriented Architecture Using Standards-based Federated Data Model

32 ISO TC 184/WG 6 Oil and Gas asset management operations and maintenance Interoperability (OGI) Technical Specification Project Update Alan T. Johnston Convener Nils Sandsmark Co-convener September 23-25, 2012 Orlando, FL ISO TC 184/WG 6

33 The OpenO&M Initiative Enabling Open Standards-based O&M Interoperability Enterprise Business Systems Enterprise Resource Planning (ERP) Operations OpenO&M Maintenance F O U N D A T I O N Physical Asset Control Real-time ISO TC 184/WG Systems 6

34 ISO Application Domain Integration Diagram Application Domain Integration Diagram A4.1 Intra-enterprise activities: Business Planning, Orders & Production, and Maintenance A4.2 Inter-enterprise activities: Supply Chain Planning, Logistics Strategy Level R4 Enterprise / Site A3.1 - Operations Planning & Scheduling A3.2 Capability Assessment & Order Fulfillment A3.3 - Maintenance Planning & Scheduling Level R3 Area A2.1 - Supervisory Control & Human- Machine Interface A2.2 - Asset Prognostics and Health, Quality, Safety, & Environmental Management A2.3 - Maintenance Execution & Tracking Level R2 Work Center A1.1- Control, I/O,Data Acquisition, Data Historian, Asset Utilization, & Displays A1.2 - Asset Condition Monitoring & Sample / Test / Diagnostic & Quality Monitoring A1.3 - Asset Configuration, Calibration & Repair / Replace Level R1 Work Unit A0.1 - Resource Identification and Location Resources ( Material / Personnel ) A0.2 - Asset Identification and Location Assets (Equipment / Facilities / Serialized Components / Sensors / Transducers / Software / Documents) Level R0 Asset ISO TC 184/WG 6

35 Machine condition assessment data processing & information flow blocks. ISO Standard Open CM&D Processing Architecture Requirements Sensor / Transducer / Manual Entry DATA ACQUISITION (DA) DATA MANIPULATION (DM) External Systems, Data Archiving, & Block Configuration STATE DETECTION (SD) HEALTH ASSESSMENT (HA) PROGNOSTICS ASSESSMENT (PA) Technical Displays & Information Presentation ADVISORY GENERATION (AG) August 2009 ISO TC 184/WG 6

36 Some Relevant ISO Related Activities ISO TC 67 Materials, equipment and offshore structures for petroleum, petrochemical and natural gas industries ISO TC 108 Mechanical vibration and shock ISO TC 184 Industrial automation systems and integration SC5 Condition monitoring and diagnostics of machines SC4 Industrial Data SC5 Architecture, communications and integration frameworks ISO Petroleum, petrochemical and natural gas industries -- Collection and exchange of reliability and maintenance data for equipment ISO MIMOSA OSA-CBM WG6 Formats and methods for communicating, presenting and displaying relevant information and data Data for Process Industries Product data representation and exchange STEP/PLCS OASIS Collaborating on the deployment of an international standard for product data exchange (ISO 10303) ISO MIMOSA OSA-EAI WG7 Diagnostic and maintenance applications integration

37 Scope and Deliverables The OGI TS specifies the use of a combination of ISO and industry standards to meet the interoperability requirements of the Oil and Gas industry and appropriate closely related industry groups such as the Petrochemical industry. Major associated deliverables include: Industry developed and owned Pilots driven by industry Use Cases Downstream Pilot Upstream Production Optimization and Drilling Automation Pilots Industry developed and owned Use Cases are prioritized by owner/operators and incorporated by reference Industry developed and owned pilot & Compliance Data Sets are incorporated by reference Downstream Data Set Plant Light Ends Unit with debutanizer and depropanizer towers Upstream Drilling Automation, Rigs and W ells Construction Data Sets with SPE DSATS ISO TC 184/WG 6