Model-driven integration architecture for IO G2

Transcription

1 Model-driven integration architecture for IO G2 Digital Platform for next generation IO: A prerequisite for the High North? The 5th International Conference on Integrated Operations in the Petroleum Industry Trondheim, Norway, September 2009, Frode Myren IBM

2 1 2 Draft Reference Architecture for OLF Integrated Operations Generation 2 Presentation at DI and ICF meetings OLF, ICT Knut Sebastian Tungland (StatoilHydro) Frode Myren (IBM) Paul Carr (GapGemini) Svein G. Johnsen (SINTEF) Einar Landre (StatoilHydro) Background Model driven integration architecture for IO G2 information Reference Semantic Model alignment to ISO 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

3 Overview Background Integrated Operations Architectural challenges in cross-facility and vertical application integration How is ISO and Reference Semantic Model related Summary 3

4 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 Source: IBM ? 4

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

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

7 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 MIMOSA PRODML WITSML OAGIS OPC SENSORS & ACTUATORS DRILLING EQUIPMENT RESERVOIR & WELLS SUB ICE PROCESS SYSTEMS Architecture based on Reference Architecture for OLF Integrated Operations Generation 2 7

8 Application integration requires agreement about terminology and models Source: Camelot project, FIATECH 2009 Engineering Companies The iring ISO15926 RDL Oil and Gas Owner/Operator with facilities Engineering Company Owner/Operator integration needs shared terminology in Reference Data Libraries (RDL) ISO 15926: the semantics of iring Oil and Gas Enterprise Facility Integration needs a neutral information model between applications (Integration Information Model) Reference Semantic Model (RSM): the basis for IO integration infrastructures 8

9 Overview Background Integrated Operations Architectural challenges in cross-facility and vertical application integration How is ISO and Reference Semantic Model related Summary 9

10 The complexity of the technical infrastructure in the oil & gas industry requires highly integrated IT system support Integrated Operations requires deep insight into the state & condition of production facilities, dynamic real time data Snøhvit Consolidation of the monitoring and controlling production facilities across facilities is required Åsgard A Åsgard B Åsgard C Snorre A Norne Heidrun Kristin Global Support Centers There is a need for enterprise-wide Integrated Operations solutions Statfjord C Statfjord A Statfjord B Gullfaks C Gullfaks B Snorre B Visund Kvitebjørn Gullfaks A Huldra IT solutions in the area of Integrated Operations must access various enterprise-wide information sources Veslefrikk Petrojarl/Glitne Sleipner feltet Sleipner B Troll A Global Operations Support Centers Vertical integration of IT solutions has to be coupled with horizontal integration 10

11 IOHN Architecture - integration architecture for Integrated Operations iring touchpoints Engineering System Well Monitoring Enterprise Production Optimization Equipment Monitoring Open O&M touchpoints 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 11

12 Integration across Facilities Systems Monitoring Security Model Management Engineering Design Systems Integration Framework Well Production Information WS/ SQL Production Optimization WS/ OPC Integration Information Model Condition Monitoring WS/ OPC Enterprise Asset Management WS/ BAPI Process Choreography Event Processing Integration Bus Model mgmt OFFICE Integration Layer OPC Historian OPC Historian WS WS Asset Management (incl field worker) Plant Integration WS/ OPC Asset Monitoring Historian OPC TCPIP Other Subsystems FACILITY Vibration Subsystem Distributed Control System 12 FACILITY A FACILITY B

13 Requirements fullfilled by IOHN architecture One standardized information model is not enough for Integrated Operations use cases Different standardized information models within different domains of the O&G industry, e.g. S95, S88, MIMOSA, ISO 15926, PRODML, WITSML An Integration Information Model is needed, IIM as a model-in-the-middle to avoid point-to-point bilateral translations, As part of an integration layer platform to mediate between different industry standards, to and from the IIM 13

14 An Integration Information Model connects applications with different information needs Classical Horizontal EAI (topfloor-to-topfloor integration) Connects enterprise applications which operate at the same level of information Integration typically requires rewriting of similar information Vertical (E)AI (shopfloor-to-topfloor integration) Connects 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 for for the the semantic information slope slope between applications especially on on the the vertical integration path path 14

15 Overview Background Integrated Operations Architectural challenges in cross-facility and vertical application integration How is ISO and Reference Semantic Model related Summary 15

16 Alignment of ISO and RSM terminology/semantics: A key driver for information integration in IOHN IOHN assignment: Represent RSM in ISO Scoping statement: Parts of RSM piloted at StatoilHydro Mimosa ISA88 Populated in Pilot (Scope) RSM ISA95 Status: Classes and relations added to PCA RDL RSM model version 2.0 proposed Ready for review and standardization through PCA Participants StatoilHydro Requirements POSC Caesar Association (PCA) Custodian of ISO RDL IBM RSM provider UML modeling expertise Application integration know-how Business scenario insight DNV Vendor independent advisor Semantic technology expertise ISO modeling expertise Project management Epsis Semantic technology expertise Mimosa Domain standards expertise 16

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

18 RSM implementing an Oil and Gas instance model RSM unite model elements from different industry standards RSM model elements include access paths to OPC infrastructures and Representation of measurements and measurement values Production management Tagno. Drilling & Completion Production & Reservoir SH Enterprise 1 N2 Country Operations & Maintenance ERP, EAM,... Functional location Allocation value Calculated value, softtag DCS, IMS,... Tagno. Wellhead tmp, timestmp Allocation Wells Work Equipment Transmitter Plant/ Facility A W1 1 2 A B C D.. SF.. Z SN WS W4 TR W9 Wellhead temp TP P Measuremt Msrmtval P5 Area ProdUnit Notification Plant/ Facility B WorkCenter Separator Control Loops P&IDs Notification Functional location Activity 18 WO Planning, optimization P&ID:Process and Instrumentation Diagrams

19 ISO supports standardized classification of data Concepts: Separator Generator Pump Tank... ISO RDL Reference classes WATER SEPARATOR SEPARATOR TEST SEPARATOR Standardized representation of Separator Used as classifiers in RSM WATER SEPARATOR RSM SEPARATOR TEST SEPARATOR IIF Integration Layer 19

20 IIF implementing the RSM integration information model and an ISO RSM adapter Enterprise Engineering System Well Monitoring Production Optimization Equipment Monitoring Asset Management ISO IBM Integrated Information Framework Reference Semantic Model (Federated IIM) Enterprise Service Bus Process Choreography Engine Analytics and Optimization Engine Event engine OPC OPC Historians Real-Time Operations Historians Real-Time Operations Facility A Facility B 20

21 ISO RSM alignment example: adapter transforming a payload of connection relations ISO data set transported through iring RSM data set residing in IIF a Generator a Socket Export Import a S-P_Connect a Plug a Fan 21

22 ISO RSM model alignment: Configure complex relationship mappings for the ISO15926 RSM adapter ISO ArrangedIndividual haswhole 1 1 haspart FeatureWholePart ArrangedIndividual 2 2 hasside1 ConnectionOfIndividual 3 3 hasside2 ArrangedIndividual haspart 4 4 haswhole FeatureWholePart ArrangedIndividual

23 Overview Background Integrated Operations Architectural challenges in cross-facility and vertical application integration How is ISO and Reference Semantic Model related Summary 23

24 IOHN Activity 2 tasks Integration architecture, platform and infrastructure 0 IOHN IO G2 Architecture, 4 Security / Network Architecture 1 Model Exchange interface 2 Model Query interface 3 Integration platform enablement 5a Drilling use case enablement 5b Production use case enablement Semantic models 5a 5b 5c Integration architecture, Platform and infrastructure c Operations use case enablement Bold focus of this presentation 24

25 Summary ISO get the terminology right RSM implement based on the right terminology Enable model integration using bi-directional translations between ISO and RSM Enable shopfloor-to-topfloor/vertical upstream integration scenarios IIF is an integration layer platform for owner operator facilities IO, which can be hooked into in an iring network for integration of information models 25

26 IOHN team collaboration Frode Myren, IBM IBM Dr. Udo Pletat, IBM IBM Einar Landre StatoilHydro Johan W. Klüwer DNV Pål Rylandsholm DNV Jørn Ølmheim StatoilHydro For more information: template=/ecommerce/productdisplay.cfm&productid=

27 27