Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Why ISO15926 is the best


Published on

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.

Published in: Technology, Business
  • Be the first to comment

Why ISO15926 is the best

  1. 1. Why ISO 15926 oil and gas data integration technology iscapable to solve of problems that can’t being solved byprevious generations of technologies and previousgenerations of data integration standards.Moscow29th of April, 2013
  2. 2. ISO 15926 technologySource: FIATECH
  3. 3. Framework for enterpriseinteroperability• ISO 11354-1 Advanced automation technologiesand their applications — Requirements forestablishing manufacturing enterprise processinteroperability — Part 1: Framework forenterprise interoperability• Clause 5.4.1:There are three approaches to achieve enterpriseinteroperability:-- integrated,-- unified,-- and federated.These three approaches were first identified in ISO 14258.3ISO 15926
  4. 4. ISO 113545.4.4 Federated approachIn the federated approach, there is no sufficiently capable common form or meta-model to guide theinteraction between enterprises that need to interoperate . The lack of capability is often related todifferent terminologies or methodologies that need to be resolved by business entity interaction. Whilethere can be a common understanding between the business entities, in the federated approach, nobusiness entity imposes their own models, languages and methods of work.To establish interoperability, parties shall accommodate and adjust their operations. Interoperation canbe supported by providing a priori information about the capabilities of the entities to be involved inthe exchange or by employing agents to discover the needed information. Support for the a priori casecan be provided by establishing entity capability profile s that hold syntactic and semantic informationon both entity inputs and outputs. Interoperability can be established by mapping corresponding inputand output information of the entities and identifying inconsistencies. Any remaining inconsistenciesshall be resolved by manual interventions.This approach is more suitable for peer-to-peer situations, where each enterprise has resources fornegotiation and compromise. The approach is particularly adapted to virtual enterprises, where diversecompanies 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 mainresearch 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 supportfor the federated approach is seen in entity profiles, which identify particular entity characteristics andproperties relevant for interoperation (e.g. ISO 15745 and ISO 16100).4
  5. 5. iRING architecture: federation5ProductdatamodelISO 15926RDLfederationProductdatamodelProduct dataProduct data1 ISO 15926 Rule ISO 15926 2circle radius radius*2 diameter окружностьmappingmapping1. Mappingeditor4. adaptor3. SPARQLendpoint2. Referencedata editor5. adaptorfacades
  6. 6. Version of iRING (ISO 15926) architecture6
  7. 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 standard7
  8. 8. Domain scalability• «Multiple closed vocabularies» do not fit domainscalability -- STEP (ISO 10303)• Computer ready standard: administration ofamendment procedures as in standards whilemaintaining standard-as-a-database• Levels of standardization (organization of referencedata development/approval): ISO – JORD – … –enterprise8
  9. 9. Fact-orientedness and semantics• EPISTLE: «object in a one project is an attribute ofanother project and vice versa»  fact-orientedness• Work on-line:– Amendability and collaborative development: open worldassumption (XML schemas are corresponded to closeworld 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. 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 mentalframework. Therefore it should be “one picture of the world” for all“mental frameworks” to superimpose objects (e.g. superimpose systemcomponent from design stage and supply item from construction stage).• 4D extensionalism• Information systems federation use Relations that transcend boundariesof individual information systems. Most of these “boundary crossingrelations” are of type TemporalWholePart(Whole, Part)• Notion of the “system” right out of the box: pump component changeexample.• Multiple identification schemes (classifiers) – classes of classes• Agreements: how to model a World + who to model a computerrepresentation of the World10
  11. 11. Life cycle of valve in ISO 1592611!!!
  12. 12. 12DesignapplicationsProcurementapplicationsP&IDapplicationsOperationapplicationsISO 15926 – «Englishas a global language»for life cycle dataISO 15926 define:1. Terminology2. Classification3. Software protocol
  13. 13. “Plain language”[is not supported by “plain and pure semanticweb”: this is very specific feature of ISO 15926]• Means: understandability by engineers (notprogrammers)• Ends: template patterns13Engineeringapplication(CAD/PLM)SemanticnetworkISO 15926-2TemplatepatternsISO 15926
  14. 14. Availability of high quality reference data: JORD RDL14“Plain language”:patternsDownload freeware .15926 Editor here: than 58,000objects including morethan 10,000 equipmentclasses, 1,500 UoMs,etc.
  15. 15. Product knowledge pyramid (ISO 15926)ISO 15926typesRDLCatalogue(standard classes)Product linesand projectDebug, change managementProduct configurationbaselinesHistoric data (product operations timerows)RDLProductdata15Huge! Needsfederation ofmultiple sources!But: one formatNeeds federationeven more!Multiple formatsEnterprise-relateddata excluded onlyto clarity of a slide.201 type: ontological commitments(shared reality)
  16. 16. Reference data libraries and services16RDLRDL (GOSTstandards)RDL (industrystandards)Project-specific RDLRDL of equipmentcatalogueProject-specific informationData of equipment catalogueISO/JORDNational associationsIndustry associationsCatalogue providersEPCM company
  17. 17. Tools: variety of implementations of a standardSoftware 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 ISO15926 tool vendors. The more, the merrier!17
  18. 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 datatransfers in Bechtel provided with usage of ISO 15926technology• 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 forGOSTs and other Russia-specific standards are oflimited interest to JORD]18
  19. 19. 19Thank you!Anatoly Levenchuk,ailev@asmp.msk.suBlog: http://levenchuk.comVictor Agroskin, (member of POSCCaesar Association)+7 (495) 748-53-88.15926 Editor blog (in Russian)