Semantically aware integration architecture for oil & gas solutions

Transcription

1 Semantically aware integration architecture for oil & gas solutions Frode Myren, IBM ISO and Semantic Technologies 2009 Sogndal, September 10, IBM Corporation

2 ISO & RSM- based integration architecture for oil & gas industry solutions Udo Pletat [1] and Johan Wilhelm Klüwer [2] Einar Landre [3] and Jørn Ølmheim [3] Frode Myren [4] and Pål Rylandsholm [2] 2 IBM Oil & Gas Centre of Excellence Further context Model driven integration architecture for IO G2 information Reference Semantic Model alignment to ISO [1] IBM Deutschland R&D GmbH [2] Det Norske Veritas, [3] StatoilHydro ASA [4] IBM Norway Semantic Days, May 20, Stavanger, Norway Frode Myren Senior Certified Executive IT Architect IBM myren@no.ibm.com Dr. Udo Pletat Senior Certified IT Specialist IBM pletat@de.ibm.com Johan W. Klüwer Principal Specialist DNV Copyright IBM Corporation 2009 Sta ndards Certification Educatio n & Training Publishing Conferences & Exhibits Draft Reference Architecture for OLF Integrated Operations Generation 2 Svein G. Johnsen (SINTEF) Einar Landre (StatoilHydro) Knut Sebastian Tungland (StatoilHydro) Frode Myren (IBM) Paul Carr (GapGemini) Presentation at DI and ICF meetings OLF, ICT 1

3 IBM Oil & Gas Centre of Excellence The technical evolution continues: the 3 rd Web Era FUNTIONALITY Web 2.0 era Collaborative interaction services integration Decouple services and processes, SOA, structured data content 3 rd Web era Smarter, semantically aware integration Decouple master data, context, rules, semantics from programming as services. IOD. Event driven architecture Cloud. 1 st Internet era Web documents Static content, easily linked. e-business Before public Internet era Corporate and application specific sharing (Disks, Databases, Ethernet, OSI) T I M E ? 3 Copyright IBM Corporation 2009

4 Overview Background Integrated Operations, High North challenges, Integrated Operations in the High North project Architectural challenges Model Transformation Summary 4

5 The context - Integrated Operations Generation 2 (IO G2) Integrated Operations (IO) IO is more information in real time offshore and onshore IO is safer, faster and better decisions IO has a potential of NOK 300 billions on the NCS Integrated Operations (IO) OLF s Generation 1 and 2 Integration across onshore and offshore Limited integration Potential Integration across companies Traditional processes Self-sustainable fields Specialized onshore units Periodic onshore support 2005 Generation 1 Integrated onshore and offshore centers Continuous onshore support Generation 2 Integrated operation centers of operators and vendors Heavily automated processes 24/7 operation Time 17 OLF s Information Management Strategy An efficient pipeline for real-time data transferal and analysis Field data Health, safety, environment Seismic Drilling & Completion Reservoir & production Operation & maintenance Smarter solutions Web portals Web services Common XML schemas Semantic Web Infrastructure for web services Oil & Gas Ontology Operator Vendor Vendor Smarter data *Ontology = A hierarchical data structure containing concepts, relationships, properties and rules for a The Norwegian Oil specific Industry domain Association

6 Integrated Operations in the High North (IOHN) project - demonstrating a reliable digital platform for IO G2 in the High North Business processes Safety and risk Semantic model Integration platform Data capture Drilling & Completion Production & Reservoir Operation & Maintenance Digital platform Focus of this presentation 6

7 Information models embedded in the integration layer are of high importance EQUIPMENT FAULT DETECTION MONITOR EQUIPMENT CONDITION DRILLING PROGRAM PLANNING PRODUCTION OPTIMIZATION EXECUTE MAINTENANCE OPERATIONS PLAN TURNAROUND NEW COMPOSITE APPLICATIONS Enterprise Area Asset Production Unit Work Equipment Measurement Measurement Value ISA 95 PRODML ISA 88 MIMOSA ISO OAGIS WITSML Semantic Model Services Pattern Integration Pattern DCS, PLC & Historians Rotating Equipment Monitoring Facility Monitoring and MES Engineering Systems Maintenance & Asset Management Equipment and Process Documentation EXISTING APPLICATIONS & INFORMATION REPOSITORIES PROCESS CONTROL DOMAIN ENTERPRISE DOMAIN Draft Reference Architecture for OLF Integrated Operations Generation 2 7

8 Information models embedded in the integration layer are of high importance (AUTOMATED) DECISION SUPPORT COMMON SERVICES PLATFORM (AUTONOMOUS) CONTROL SYSTEMS REMOTE DRILLING PRODUCTION OPTIMIZATION (Real-time) Information exchange, validation & integration Semantic Platform SUB ICE OPERATIONS Security Safety Networking Offshore Onshore ISA S95 ISO ISA S88 WITSML PRODML OPC OAGIS MIMOSA SENSORS & ACTUATORS DRILLING EQUIPMENT RESERVOIR & WELLS SUB ICE PROCESS SYSTEMS Architecture based on Reference Architecture for OLF Integrated Operations Generation 2 and NTNU IO Center Architectures 8

9 Application integration requires agreement about the meaning of information to exchange iring ISO RDL (Ontology) ISO Asset Management MIMOSA IIM-to-MIMOSA Event Processing Engine IIM-to-WITSML EngineeringSystem ISO to-RSM ISO IIM-to-ISO Integration Platform Integration Information Model Reference Semantic Model IIM-to-OPC EquipmentMonitoring S95 IIM-to-S95 Workflow Execution Engine ISO13628-to-IIM Engineering Companies Drilling Device Control Oil & Gas Company with facilities Engineering Company Owner/Operator integration requires agreement about the meaning of information to exchange Integration Information Model e.g., ISO with Reference Data Libraries as the basis of iring Oil and Gas Enterprise Facility Integration approaches recommend a neutral information model in the middle between applications Integration Information Model e.g., Reference Semantic Model as the basis for IO integration infrastructures WITSML OPC Realtime&History ProductionControl 9

10 Overview Background Architectural challenges in cross-facility and vertical application integration Model Transformation Summary 10

11 The complexity of the technical infrastructure in the oil & gas industry requires highly integrated IT system support. Excellence in Integrated Operations requires deep insight into the state & condition of production facilities Monitoring and controlling production facilities individually will no longer be sufficient Snøhvit Norne There is need for enterprise-wide Integrated Operations solutions Åsgard A Åsgard B Åsgard C Heidrun Kristin Global Support Centers IT solutions in the area of Integrated Operations must access various enterprise-wide information sources Statfjord C Statfjord A Statfjord B Gullfaks C Gullfaks B Gullfaks A Snorre A Snorre B Visund Kvitebjørn Huldra Vertical integration of IT solutions has to be coupled with horizontal integration Veslefrikk Petrojarl/Glitne Sleipner feltet Sleipner B Troll A Global Operations Support Centers 11

12 IOHN Architecture - integration architecture for Integrated Operations iring touchpoints Enterprise Open O&M touchpoints Engineering System Well Monitoring Production Optimization Equipment Monitoring Asset Management ISO WITSML ProdML MIMOSA Integration Layer Integration Information Model Integration Bus OPC OPC Historians Real-Time Operations Historians Real-Time Operations Facility A Facility B 12

13 Requirements fullfilled by IOHN architecture Applications relevant for Integrated Operations operates on different standardized information models One standardized information model is not enough for integrated operations use cases A comprehensive application integration platform has to mediate between different industry standards An Integration Information Model is needed, plus adapters translating to and from the IIM... 13

14 Applications to be integrated often operate on different information models/industry standards. To facilitate different aspects of monitoring and control applications, different information models have been standardized within different domains of the O&G industry, e.g. S95, S88, MIMOSA, ISO 15926, PRODML, WITSML,... For application integration this requires translations between standardized information models In order to avoid point-to-point bilateral translations, an Integration Information Model should be identified as a model-in-the-middle 14

15 An Integration Information Model connects applications with different information needs Classical Horizontal EAI (topfloor-to-topfloor integration) Connect enterprise applications which operate at the same levels of information Integration typically requires rewriting of similar information Vertical (E)AI (shopfloor-to-topfloor integration) Connect plant control and enterprise applications operating at different levels of information Integration typically requires enrichment/reduction of different information An An IIM IIM enables compensating the the semantic information slope slope between applications especially on on the the vertical integration path path 15

16 Overview Background Architectural challenges Model Transformation between ISO and Reference semantic Model Summary 16

17 IOHN provides ISO semantics to the Reference Semantic Model ISO Drilling & Completion Integration of life-cycle data for process plants including oil and gas production facilities Get the terminology right! Production & Reservoir Oil and gas ontology Reference Data Well Enterprise Plant Transmitter Operations & Maintenance Reference Semantic Model An information model unifying industry standards for vertical integration of IO applications Implement based on the right terminology! Control Loop Facility P&ID 1 N2 1 2 TR SH TP A B C D.. SF.. Z SN Measurement Asset WS P W1 W4 W9 P5 M MV 17

18 Towards implementing the IOHN architecture using runtime frameworks with the IBM C&P Integrated Information Framework Enterprise Engineering System Well Monitoring Production Optimization Equipment Monitoring Asset Management ISO IBM IIF BPM engine Reference Semantic Model Integration Bus Event engine OPC OPC Historians Real-Time Operations Historians Real-Time Operations Facility A Facility B 18

19 ISO RSM alignment - the principles of the ISO15926 RSM adapter ISO RSM 1 RSM_FunctionalEntity_2.0 RSM_ConnectionPoint.belongsTo_PhysicalEntity 2 RSM_ConnectionPoint ISO15926_ConnectionPoint.toConnectionNode 3 RSM_ConnectionNode ISO15926_ConnectionPoint.toConnectionNode 4 RSM_ConnectionPoint Typical information in an RSM database: A generator is connected to power a fan. The general case is: Pieces of equipment are connected. We want to present such connection information in the ISO space as well. 19

20 Alignment of semantic content between ISO and RSM is a key driver towards application integration within IOHN IOHN assignment: Represent the Reference Semantic Model (RSM) in ISO15926 Scoping statement: Represent in ISO15926 the scope of the Reference Semantic Model exploited in pilots at two StatoilHydro facilities Scope Mimosa RSM ISA88 Populated in pilot ISA95 Status: Approximately 100 classes and relations added to PCA RDL RSM model v2.0 proposed Aligned with ISO15926 model Opens up for use of rich information structures contained in RDLs Ready for next step Review and standardization through PCA Making RSM publicly available Participants StatoilHydro Requirements IBM Provider of RSM RSM and UML modeling expertise Application integration know-how Business scenario insight DNV Vendor independent advisor Expertise in semantic technology Expertise in ISO15926 Project management Epsis Expertise in semantic technology Mimosa Expertise in relevant domain standards 20

21 Overview Background Integrated Operations High North challenges Integrated Operations in the High North project Architectural challenges in cross-facility and vertical application integration Model Transformation between ISO and Reference semantic Model Summary 21

22 Summary 1/2 Vertical integration faces an information slope regarding semantic richness between facility, e.g. DCS, and enterprise applications, e.g. ERP information enrichment/reduction becomes a very important aspect for the Integration Layer Integration Information Models like ISO and RSM and adapters between them can balance this information slope bi-directional translations between ISO and RSM iring and IIF are integration layer platforms which can benefit from ISO and RSM alignment for exchange of master and transactional data iring ISO RDL Asset Management EngineeringSystem ISO to-RSM EquipmentMonitoring MIMOSA ISO S95 IIM-to-MIMOSA IIM-to-ISO IIM-to-S95 Integration Platform Event Workflow Processing Integration Execution Engine Information Model Reference Engine IIM-to-WITSML Semantic IIM-to-OPCModel ISO13628-to-IIM WITSML OPC Supplier ISO Drilling Device Control Realtime&History ProductionControl Owner/Operator 22

23 Summary 2/2 The alignment work Driven by StatoilHydro Performed (mainly) between DNV and IBM a good example of cooperation between standards custodians, technology providers and business Alignment between ISO and RSM: Opens up for using the best from two worlds Rich information structures from ISO Standardized classification provides a presctriptive buildtime approach Model instance data integrated with real time data through scalable runtime frameworks Driving towards an ISO15926 oil and gas O&M ontology DNV and IBM are ready to bring the results sketched here forward for validation & review through POSC Caesar standards bodies 23