The Role of ISO 15926 for Applying Enterprise Service Bus Technologies in Oil & Gas Industry Solutions

Dr. Udo Pletat IBM Deutschland Research & Development GmbH Böblingen, Germany, [email protected]

Semantic Days 2010 Tutorial The role of ISO 15926 for applying enterprise service bus technologies in oil & gas industry solutions

Dr. Udo Pletat IBM Germany, Boeblingen

Enterprise Application Integration flashback

Industry standard information models and EAI – ISO 15926 and Reference Semantic Model ISO 15926 and Reference Semantic Model alignment revisited Relating iRING and IIF from an EAI bus perspective Summary

Observe existence of different application integration infrastructures & technologies –Enterprise application level: Enterprise Service Bus approach to connect ERP, EAM, CRM systems

–Production Control Level: Open Process Control (OPC) to integrate DCS and MES systems

Integrate integration infrastructures vertical application integration

Application 1 SemanticSemantic modelmodel // Application 2 syntacticsyntactic representationrepresentation ASBO 1 ASBO 2

Adapter 1 Adapter 2 GBO GBO Integration flows based on Generic Business Objects

GBO Enterprise Service Bus GBO Adapter 3 Adapter 4

ASBO 3 ASBO 4 Integration logic / Application 3 use case Application 4

• Applications to be integrated are – More established & harder to change – Based on their application specific business objects • Integration bus (Enterprise Service Bus) – Host integration logic based on a ‚common ground‘ – Operate on generic business objects • Adapters – Translate between application specific and generic business objects – Trigger the integration logic (workflows)

Where can industry standard information models be found? Application specific business objects

standards based applications Application 1 Application 2

ASBO 1 ASBO 2

Adapter 1 Adapter 2 Generic business objects GBO GBO Integration flows based on standards based Generic Business Objects GBO Enterprise Service Bus GBO application integration Adapter 3 Adapter 4

ASBO 3 ASBO 4

Application 3 Application 4 Mapping between/to/from for AS exam industry standards BO 1 ple AS = IS BO 2 O 1 for AS = I 592 becomes part of the EAI discipline G exa BO SA S 6 BO = ASmpl 3 = M 95 G ISOBO e IMO BO = 15 4 = C SA G ISA 926 IM BO = S9 G MIM 5 BO = OS CIM A

‚Classical‘ Horizontal EAI (topfloor-to-topfloor integration) Connects enterprise applications which operate at similar levels of semantic information

Couples systems which operate at the same processing speed (order of magnitude)

Overlap between business objects is required ASBO App1 ∩∩∩ GBO ∩∩∩ ASBO App2

TheThe ASBOs ASBOs carry carry enough enough information information to to populate populate the the GBO GBO

‚Overlap area‘ Semantically related Application 1 ASBO Info Model ‚Enrichment area‘ information that can Integration Layer can be transported enrich information from Application 1 from Application 1 to to Application 2 generate information GBO Info Model for Application 2

Application 2 ASBO Info Model

Plant-level Systems Plant-level SystemsL2 Plant-level Systems Plant-level Systems DCS Process Control DCS ProcessControl DCS Process Control DCS ProcessControl – Plant-level process control

L0,1 Physical Equipment Physical Equipment Production equipment Physical Equipment Physical Equipment

Application layers Enterprise Systems Enterprise Systems L4 – Enterprise wide business Engineering ProductionMonitoring CRM/ERP/EAM Engineering ProductionMonitoring CRM/ERP/EAM applications Integration Bus Plant-level Systems Plant-level Systems Plant-level Systems Plant-level SystemsL3 – Plant-level manufacturing MES ProductionControl MES ProductionControl MES ProductionControl MES ProductionControl execution Integration Bus Integration Bus Plant-level Systems Plant-level SystemsL2 Plant-level Systems Plant-level Systems DCS Process Control DCS ProcessControl DCS Process Control DCS ProcessControl – Plant-level process control

L0,1 Physical Equipment Physical Equipment Production equipment Physical Equipment Physical Equipment

Plant-level Systems Plant-level Systems Plant-level Systems Plant-level SystemsL3 – Plant-level manufacturing MES ProductionControl MES ProductionControl MES ProductionControl MES ProductionControl execution Integration Bus Integration Bus Plant-level Systems Plant-level SystemsL2 Plant-level Systems Plant-level Systems DCS Process Control DCS ProcessControl DCS Process Control DCS ProcessControl – Plant-level process control

L0,1 Physical Equipment Physical Equipment Production equipment Physical Equipment Physical Equipment

Advanced Vertical (E)AI (shopfloor-to-topfloor integration) Connects plant control and enterprise applications operating at different levels of semantic information

Integration typically requires enrichment/reduction of different information

Couples systems which operate at different processing speeds (order of magnitude)

Overlap between business objects is required ASBO App1 ∩∩∩ GBO ∩∩∩ ASBO App2 !

ASBOsASBOs from from the the plantfloor plantfloor (L1, (L1, L2) L2) do do not not carry carry eno enoughugh information information toto populate populate the the GBO! GBO!

Application 1 ASBO Info Model Adapter 1 Adapter 2 GBO GBO Enterprise Integration GBO Bus Info Model GBO GBO Adapter 3 Adapter 4 Application 2 ‚Horizo ntal EA ASBO Info Model applic I‘ inte ations rconn sem from ects antic simila spaces r Enric hment imp hardly ortant

Application 1 ASBO Info Model Adapter 1 Adapter 2 GBO GBO Enterprise GBO Integration Bus Info Model GBO GBO Adapter 3 Adapter 4 Application 2 ‚Vertic ASBO Info Model al EAI‘ applic interco ations nnects disp from m arate s ore emant Enrich ic spac ment es imp becom ortant es

Adapter 1 Adapter 2 GBO GBO Enterprise Integration flows based on GBO Store Integration Generic Business Objects for enrichment Bus GBO GBO Adapter 3 Adapter 4

In the classical horizontal bus GBOs exist In the modern vertical bus GBOs exist mainly transiently also persistently

ImportanceImportance of of GBO GBO information information model model grows grows for for verti verticalcal EAI EAI

Enterprise Application Integration flashback

Industry standard information models and EAI – ISO 15926 and Reference Semantic Model

ISO 15926 and Reference Semantic Model alignment revisited Relating iRING and IIF from an EAI bus perspective Summary

Thing

PossibleIndividual AbstractObject & sub-classes & sub-classes

Relationship & sub-classes Class & sub-classes

ISO 15926 Part 2 top level class categories

Part 2 is the master GBO schema – All ISO 15926 data to be transported is – in the end – instance data of the Part 2 meta-model

Part 4 is ‚just‘ instance data according to Part 2 – Would a Part 4 Oil & Gas ontology defining an O & G meta- model also serve as the GBO meta-model? NO! – Do interaction partners have to agree on the same Part 4 O&G ontology? YES!

Part 7 template definitions allow – To define the translations to be performed in the adapters model X IS0 15926 model Y

ISO 15926 Part 2 is fairly generic – pro easy to map into – con hard to map out of

pumpXpumpX : :ISO15926-2_PossibleIndividual ISO15926-2_PossibleIndividual

Relate the transported content to an RDL – pro know the terms that are transported – con both parties have to agree on the same RDL

pumpXpumpX : :ISO15926-2_PossibleIndividual ISO15926-2_PossibleIndividual classification(pumpX,classification(pumpX, iso15926-4_CentrifugalPump) iso15926-4_CentrifugalPump) iso15926-4_CentrifugalPumpiso15926-4_CentrifugalPump : :ISO15926-2_ClassOfInan ISO15926-2_ClassOfInanimatePhysicalObjectimatePhysicalObject

pumpXpumpX : :RSM_FunctionalEntity RSM_FunctionalEntity pumpXpumpX : :S95_Unit S95_Unit pumpX.typepumpX.type = = rsm_centrifugalPump rsm_centrifugalPump pumpX.typepumpX.type = = s95_centrifugalPump s95_centrifugalPump RSM ASBO S95 ASBO iso15926-4_CentrifugalPump : Adapter 1 iso15926-4_CentrifugalPump : Adapter 2 ISO15926-2_ClassOfInanimatePhysicalObjectISO15926-2_ClassOfInanimatePhysicalObject 15926 GBO 15926 GBO rsm_pi_cpTemplate(P,rsm_pi_cpTemplate(P, cP_rsm) cP_rsm) ≡≡ ISO 15926 Part 4 possibleIndividual(P)possibleIndividual(P) & & RDL classification(P,classification(P, iso15926-4_CP) iso15926-4_CP) ≡≡ ISO 15926 Part 7 S95_pi_cpTemplate(P,S95_pi_cpTemplate(P, cP_s95) cP_s95) Templates iRING Integration Bus

rsm_pi_cpTemplate(pumpX,rsm_pi_cpTemplate(pumpX, cP_rsm) cP_rsm) s95_pi_cpTemplate(pumpX,s95_pi_cpTemplate(pumpX, cP_s95) cP_s95)

GBO‘s are ISO 15926 ‚sentences‘, i.e., multiple Part 2 statements compress these sentences into a Part 7 Template

Blend of different industry standards – S88, S95, CIM (IEC 61970), MIMOSA, ISO 15926, UNCEFACT, ...

Fulfills requirements for a GBO model for vertical application integration

Is the GBO information model for IBM‘s Integrated Information Framework

NamedObject

Chemical and Petroleum Solutions The Conceptual Reference Semantic Model

RSM Team

PCA / POSC Caesar Association – Thore Langeland, Nils Sandsmark, Magne Valen-Sendstad ISA 95 – Keith Unger Organizational ISA 88 – Dennis Brandl OAGi – Dave Connelly Entity WBF – Dave Emerson Energistics – Jerry Hubbard MIMOSA – Alan Johnson, Ken Beaver & sub-classes FunctionalEntity OSIsoft – Jack Aude StatoilHydro - Olav Lerflaten DOW – Russ Dickinson & sub-classes SISCO – Herb Falk, Lorenzo Childress IBM - Russ Lambert,Put Udo Pletat RSM parents diagram here TypeOf... RSM Team Objectives/Milestones Objectives & sub-classes – Advance the modeling work – Ensure compliance with the participating standards Standardisation – Working with ISO15926 through their IO HN project intitative to standardise RSM in ISO1926

Some top level RSM class categories

Hierarchies of organizational units Hierarchies of functional units & much much more

ibmOil : RSM_OrgEntity composition

europe : RSM_OrgEntity

composition ownedBy stavanger : RSM_OrgEntity ullrigg : RSM_FunctionalEntitiy

composition

separator: RSM_WorkCenter

composition liquidFlow : RSM_Measurement takenFor uom = ccm/min pumpX: RSM_WorkEquipment type = centrifugalPump belongsTo mv1 : RSM_MeasurementValue value = 47 23 © 2010 IBM Corporation Dr. Udo Pletat IBM Deutschland Research & Development GmbH Böblingen, Germany, [email protected] Typical vertical EAI use case pattern for IIF: - lift OPC tag reads to RSM GBOs and trigger work flows

Application 1 Application 2

ISO 15026 MIMOSA

Adapter 1 Adapter 2

RSM liquidFlow : RSM_Measurement pumpX:Model RSM_WorkEquipment Store uom = ccm/min type = centrifigalPump meas1 : RSM_MeasurementValue value = 47 EventEngine IIF Integration Bus Adapter 3 Adapter 4 Integrated Information Framework

OPC tag4711.valuetag4711.value = = 123 123 OPC Application 3 Application 4 (OPC Server) (OPC Server)

ESB

JMS Adapter

OPC Client

OPC Server (External Application)

ESB

JMS Adapter

OPC Client

OPC Server (Semantic Transformation to RSM)

OPC Client

OPC Server (External Application)

Enterprise Application Integration flashback Industry standard information models and EAI – ISO 15926 and Reference Semantic Model

ISO 15926 and Reference Semantic Model alignment revisited

Relating iRING and IIF from an EAI bus perspective Summary

Schema level – ISO 15926 - Part 2  RSM classes

Instance level reference data – ISO 15926 – Part 4 (RDL)  RSM classes – ISO 15926 – Part 4 (RDL)  RSM class instances (pre-populated)

Instance level facility representation – Instances of part 2 classes  RSM instances classified by part 4 terms tagged with pre-populated terms

Connectivity Composition Measurement ISO 15926 Part 2 Schema Classification RSM Schema

FunctionalEntities

ISO 15926 Part 4 RDL Equipment types RSM pre-populated content Scales/UOMs

RSM based GBOs ISO 15926 based GBOs Repres entatio of oil p n roduct fa ion Data of cilities Data of ISO 15926 based applications RSM based applications Application Data Schema & Reference Data Reference & Schema Application Data

ISO 15926 RSM

ISO15926-2_PossibleIndividual RSM_OrganizationalEntity

classification : typeOfOrgEntity S ISO15926-2_Thing x ISO15926-2_Class chema

ISO15926-2_ClassOfOrganization RSM_TypeOfOrgEntity Model alignment alignment Model mapping = conceptual

iso15926_WorkUnit (S95) : RSM_WorkUnit (S95) ISO15926_ClassOfInanimatePhysObj RDL iso15926_Enterprise (S95) : rsm_Enterprise (S95) : ISO15926_ClassOfOrganization RSM_TypeOfOrgEntity

ibmOil : ibmOil : ISO15926_PossibleIndividual co RSM_OrganizationalEntity ncrete classification(ibmOil, facil ibmOil.typeOfOrgEntity Data transformation transformation Data mapping = transactional ity iso15926_enterprise) = rsm_Enterprise

30 © 2010 IBM Corporation Dr. Udo Pletat IBM Deutschland Research & Development GmbH Böblingen, Germany, [email protected] Protoype implementation of ISO 15926 – RSM conversion demonstrated at ISA Expo 2009

(private instance) IIF  iRING (public or private instance)

Enterprise Application Integration flashback Industry standard information models and EAI – ISO 15926 and Reference Semantic Model ISO 15926 and Reference Semantic Model alignment revisited

Relating iRING and IIF from an EAI bus perspective

Summary

iRING IIF

Base information model ISO 15926 Reference Semantic Model GBO info model

Use of information model Reference Data Library Reference Data Library definition consumption Representation of enterprise Representation of enterprise GBO data (-) GBO data (++) Preferred use intra-enterprise intra-enterprise inter-enterprise (private) inter-enterprise (private) inter-enterprise (public)

Implementation technology .NET architecture JEE ESB architecture

33 © 2010 IBM Corporation Dr. Udo Pletat IBM Deutschland Research & Development GmbH Böblingen, Germany, [email protected] Establishing iRING and IIF interoperability GBO & RDL synchronization in integration buses

Enterprise A using iRING as its internal bus Enterprise B using IIF as its internal bus

Application 1 Application 2 Application 1 Application 2

MIMOSA ISO 15026 ISO 15026 MIMOSA

Adapter 1 Adapter 2 Adapter 1 Adapter 2

RSM Model Store ISO 15926 (µµµRDL) Model Store (RDL) RSM Model Store ISO 15926 GBOs GBO Store iRING Integration Bus IIF Integration Bus

Adapter 3 Adapter 4 Adapter 3 Adapter 4 Integrated Information Framework iRING ISO 15926 Adapter

OPC OPC OPC OPC ISO R 15926 SM is GB is the GB the Application 3 O me Application 4 Application 3 O me Application 4 ta- mo ta- mod fo del f el r iRING or IIF

iRING RDL is local at enterprise A Scenario: use the RDL store for maintaining GBOs

34 © 2010 IBM Corporation Dr. Udo Pletat IBM Deutschland Research & Development GmbH Böblingen, Germany, [email protected] Establishing interoperability between IIF and other bus infrastrcuture through a public iRING

Enterprise A with some internal bus Public iRING Enterprise B using IIF as its internal bus

Application 1 MIMOSA Application 2 Application Data Application 1 Application 2

ISA S95 MIMOSA Adapter15926 ISO ISO 15026 MIMOSA

Adapter 1 Adapter 2 Adapter 1 Adapter 2

RSM Model Store (µµµRDL) RSM Model Store GBOs Enterprise Service Bus IIF Integration Bus Adapter 3 Adapter 4 Adapter 3 Adapter 4 Integrated Information Framework OPC OPC ISO 15926 ISO 15926 Adapter OPC OPC

Application 3 Application 4 Application 3 Application 4

Adapter 1 Adapter 2

ISO 15926 Model Store (RDL)

iRING Integration Bus Adapter 3 Adapter 4 iRING ISA Expo 2009 demo use case: retrieve RSM model store content RSM Model Store content ISO 15926 Data Application Data

ESB A ESB B

iRING

IIF

IDEALLYIDEALLY intraintra enterprise enterprise GBO GBO iRING == interinter enterprise enterprise GBO GBO UNLIKELYUNLIKELY

Enterprise Application Integration flashback Industry standard information models and EAI – ISO 15926 and Reference Semantic Model ISO 15926 and Reference Semantic Model alignment revisited Relating iRING and IIF from an EAI bus perspective

Summary

Horizontal Enterprise Application Integration – contributed the basis of modern enterprise service bus architecture pattern • terms like ASBO, GBO, Adapter (mediation), integration flows

– used for coupling primarily applications on S95 layers 4 and 3

Vertical Enterprise Application Integration – should adopt the established terminology and approaches from horizontal EAI

– includes S95 layer 2 (with its connections into layer 1) into the integration scope

– Has to deal with • ‚information slope‘ between S95 layer 2 and S95 layer 3 & 4 information • higher performance requirements due to layer 2 runtime characteristics

There quite a lot of standards addressing different subject areas relevant for the oil & gas industry

Some are (want to be) by nature – Topic specific WITSML – Topic independent ISO 15926

– ASBO models WITSML – GBO models ISO 15926, RSM

Standard-to-Standard conversions highly appreciated – use for intra-enterprise data exchange – use for inter-enterprise data exchange

Enterprise Application Integration is an adequate conceptual framework for this

EJB, J2EE, J2SE, Java, JavaScript, JDBC, JNI, JRE, RSM, Sun, Sun Java, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. .NET is a trademark of Microsoft Inc.

Other company, product, or service names may be trademarks or service marks of others. The information and materials are provided on an "as is" basis and are subject to change.