Why ISO15926 is the best
•Download as PPTX, PDF•
1 like•1,363 views
Talk of Anatoly Levenchuk "Why ISO 15926 oil and gas data integration technology is capable to solve of problems that can’t being solved by previous generations of technologies and previous generations of data integration standard" at conference on industrial data integration 29th of April 2013, Moscow.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Why ISO15926 is the best
Similar to Why ISO15926 is the best (20)
More from Anatoly Levenchuk
More from Anatoly Levenchuk (20)
Recently uploaded
Recently uploaded (20)
Why ISO15926 is the best
- 1. Why ISO 15926 oil and gas data integration technology is capable to solve of problems that can’t being solved by previous generations of technologies and previous generations of data integration standards. Moscow 29th of April, 2013
- 2. ISO 15926 technology Source: FIATECH
- 3. Framework for enterprise interoperability • ISO 11354-1 Advanced automation technologies and their applications — Requirements for establishing manufacturing enterprise process interoperability — Part 1: Framework for enterprise interoperability • Clause 5.4.1: There are three approaches to achieve enterprise interoperability: -- integrated, -- unified, -- and federated. These three approaches were first identified in ISO 14258. 3 ISO 15926
- 4. ISO 11354 5.4.4 Federated approach In the federated approach, there is no sufficiently capable common form or meta-model to guide the interaction between enterprises that need to interoperate . The lack of capability is often related to different terminologies or methodologies that need to be resolved by business entity interaction. While there can be a common understanding between the business entities, in the federated approach, no business entity imposes their own models, languages and methods of work. To establish interoperability, parties shall accommodate and adjust their operations. Interoperation can be supported by providing a priori information about the capabilities of the entities to be involved in the exchange or by employing agents to discover the needed information. Support for the a priori case can be provided by establishing entity capability profile s that hold syntactic and semantic information on both entity inputs and outputs. Interoperability can be established by mapping corresponding input and output information of the entities and identifying inconsistencies. Any remaining inconsistencies shall be resolved by manual interventions. This approach is more suitable for peer-to-peer situations, where each enterprise has resources for negotiation and compromise. The approach is particularly adapted to virtual enterprises, where diverse companies combine their resources and knowledge to manufacture a product for a limited duration. NOTE Using the federated approach to develop enterprise interoperability is most challenging. A main research area is development of a mapping factory that can generate on-demand customized “anybody- anywhere-anytime” mapping agents among existing systems. It is worth noting that a specific support for the federated approach is seen in entity profiles, which identify particular entity characteristics and properties relevant for interoperation (e.g. ISO 15745 and ISO 16100). 4
- 5. iRING architecture: federation 5 Product data model ISO 15926 RDL federation Product data model Product dataProduct data 1 ISO 15926 Rule ISO 15926 2 circle radius radius*2 diameter окружность mappingmapping 1. Mapping editor 4. adaptor 3. SPARQL endpoint 2. Reference data editor 5. adaptor facades
- 6. Version of iRING (ISO 15926) architecture 6
- 7. Problems and solutions Domain scalability Fact-orientedness and semantics Ontological approach: Common “picture of the world” Notion of the “system” right out of the box “Plain language”: patterns Availability of high quality reference data Tools: variety of implementations of a standard 7
- 8. Domain scalability • «Multiple closed vocabularies» do not fit domain scalability -- STEP (ISO 10303) • Computer ready standard: administration of amendment procedures as in standards while maintaining standard-as-a-database • Levels of standardization (organization of reference data development/approval): ISO – JORD – … – enterprise 8
- 9. Fact-orientedness and semantics • EPISTLE: «object in a one project is an attribute of another project and vice versa» fact-orientedness • Work on-line: – Amendability and collaborative development: open world assumption (XML schemas are corresponded to close world assumption, there are problems with merge) – Linked Data (URI), – Quad-stores and SPARQL – Data description availability (resolvable URI) • Ready-made data interchange formats: RDF и OWL • Formal verification (reasoners in OWL) 9
- 10. Ontological approach • “Plain semantics” is fit to federation within one stage of life cycle • In multiple stages of life cycle federation • ISO 24744 define life cycle stages boundaries as changing of mental framework. Therefore it should be “one picture of the world” for all “mental frameworks” to superimpose objects (e.g. superimpose system component from design stage and supply item from construction stage). • 4D extensionalism • Information systems federation use Relations that transcend boundaries of individual information systems. Most of these “boundary crossing relations” are of type TemporalWholePart(Whole, Part) • Notion of the “system” right out of the box: pump component change example. • Multiple identification schemes (classifiers) – classes of classes • Agreements: how to model a World + who to model a computer representation of the World 10
- 11. Life cycle of valve in ISO 15926 11 ! !!
- 12. 12 Design applications Procurement applications P&ID applications Operation applications ISO 15926 – «English as a global language» for life cycle data ISO 15926 define: 1. Terminology 2. Classification 3. Software protocol
- 13. “Plain language” [is not supported by “plain and pure semantic web”: this is very specific feature of ISO 15926] • Means: understandability by engineers (not programmers) • Ends: template patterns 13 Engineering application (CAD/PLM) Semantic network ISO 15926-2 Template patterns ISO 15926
- 14. Availability of high quality reference data: JORD RDL 14 “Plain language”: patterns Download freeware .15926 Editor here: http://techinvestlab.ru/dot15926Editor More than 58,000 objects including more than 10,000 equipment classes, 1,500 UoMs, etc.
- 15. Product knowledge pyramid (ISO 15926) ISO 15926 types RDL Catalogue (standard classes) Product lines and project Debug, change management Product configuration baselines Historic data (product operations time rows) R D L P r o d u c t d a t a 15 Huge! Needs federation of multiple sources! But: one format Needs federation even more! Multiple formats Enterprise-related data excluded only to clarity of a slide. 201 type: ontological commitments (shared reality)
- 16. Reference data libraries and services 16 RDL RDL (GOST standards) RDL (industry standards) Project-specific RDL RDL of equipment catalogue Project-specific information Data of equipment catalogue ISO/JORD National associations Industry associations Catalogue providers EPCM company
- 17. Tools: variety of implementations of a standard Software needed: • Reference data editor • Mapping editor • Quad-store with SPARQL endpoint • Two adaptors (to ISO 15926 and from ISO 15926) Implementations of iRING architecture: • iRINGTools (iRING usergroup with Bechtel leadership) • .15926 (TechInvestLab) • RDL of Rosenergoatom • OpenPlant (Bentley Systems) • JORD RDS infrastructure • XMpLant Protheus-2 software • … Quality of implementations is provided by competition of ISO 15926 tool vendors. The more, the merrier! 17
- 18. Case: Bechtel • 53,000 employee, $27bln/year. • 13 years of leading construction market in USA • Up to end 2012 around 30% of intra-company data transfers in Bechtel provided with usage of ISO 15926 technology • Up to end 2014 it will be 100% • Use of JORD RDL only. No other “proprietary” reference data libraries inside the firewall. [impossible to repeat in Russia: reference data for GOSTs and other Russia-specific standards are of limited interest to JORD] 18 http://iringtoday.com/interview-with-frank-matthewson-of-bechtel/
- 19. 19 Thank you! Anatoly Levenchuk, ailev@asmp.msk.su Blog: http://levenchuk.com Victor Agroskin, vic5784@gmail.com TechInvestLab.ru (member of POSCCaesar Association) +7 (495) 748-53-88 .15926 Editor blog (in Russian) http://dot15926.livejournal.com
Editor's Notes
- 5.4.2 Integrated approachIn the integrated approach a common form shall be used to represent the exchanged entities. This common form shall be sufficiently expressive to capture those details that affect interoperability of the items to be exchanged, rather than the process or system as a whole. The common form is not necessarily an International Standard, but needs to be agreed by participating enterprises in order to elaborate these entities and build systems accordingly.EXAMPLE Examples of developing interoperability using an integrated approach are ISO 10303, ISO 19440 and OASIS/UNCEFACT ebXMLThe integrated approach assures consistency and coherence of the interoperating subsystems by focusing on the components that need to interact. These components are then designed and implemented using a common form (or standard) so that interoperability is seen as a designed-in quality. Interoperation between these various components is therefore obtained a priori without any interfacing effort. Subsystems that are integrated in this way have distinct and individual structure, behaviour, or boundaries, but their combined behaviour is perceived to be as one entity and is achieved by collaboration and coordination through the use of the common form.5.4.3 Unified approachIn the unified approach, a common meta-model, which is applicable for the participating entities and used as a common reference to map existing models’ syntax and semantics, shall be identified and detailed. This meta-model provides at least a reference vocabulary, but could be a complete ontology. Such a meta-model is not an executable entity. Instead, it s hall provide a means for semantic equivalence to enable mapping between entities. Using this meta-model, a translation between the constituent entities is then possible. However, that translation might involve the loss of some informati on because the participating entities can have different extensions or instantiations of the same meta-model.NOTE 1 The unified approach is particularly suitable when developing interoperability for collaborative or networkedenterprises. To be interoperable with networked business partners, a new company maps its own model or system to the neutral meta-model without the necessity to make changes on its own model or system. This approach has an advantage over the integrated approach because of the reduced efforts, time and cost in implementation. It is also suitable for a situation where a large company needs to interoperate with SMEs. Normally an SME works with more than one large company; to interoperate with different companies, the unified approach can be a suitable solution in that it facilitates coordination without requiring conformance to potentially conflicting processes or environments.NOTE 2 In the re-engineering situation, syntactic alignment can be achieved through a unified approach that uses a mapping function to create missing elements of the exchange items, but semantic alignment between partners can be very difficult. Therefore, re-engineering is more applicable to developing intra-enterprise interoperability.5.4.4 Federated approachIn the federated approach, there is no sufficiently capable common form or meta-model to guide the interaction between enterprises that need to interoperate . The lack of capability is often related to different terminologies or methodologies that need to be resolved by business entity interaction. While there can be a common understanding between the business entities, in the federated approach, no business entity imposes their own models, languages and methods of work.To establish interoperability, parties shall accommodate and adjust their operations. Interoperation can be supported by providing a priori information about the capabilities of the entities to be involved in the exchange or by employing agents to discover the needed information. Support for the a priori case can be provided by establishing entity capability profile s that hold syntactic and semantic information on both entity inputs and outputs. Interoperability can be established by mapping corresponding input and output information of the entities and identifying inconsistencies. Any remaining inconsistencies shall be resolved by manual interventions.This approach is more suitable for peer-to-peer situations, where each enterprise has resources for negotiation and compromise. The approach is particularly adapted to virtual enterprises, where diverse companies combine their resources and knowledge to manufacture a product for a limited duration.NOTE Using the federated approach to develop enterprise interoperability is most challenging. A main research area is development of a mapping factory that can generate on-demand customized “anybody-anywhere-anytime” mapping agents among existing systems. It is worth noting that a specific support for the federated approach is seen in entity profiles, which identify particular entity characteristics and properties relevant for interoperation (e.g. ISO 15745 and ISO 16100).