Information - the lifeblood of the business how ISO 15926 enables its integration
Why ISO 15926? The Process Industries have many players: Plant Owner/Operators EPC Contractors and subcontractors Suppliers Authorities in rather “promiscuous” operational relationships. These all use their software systems to fit their operations, and these systems are incompatible for the most. ISO 15926 provides an ISO-standard “Lingua Franca” that allows for interoperability of those systems.
The data jungle
Objectives of ISO 15926 To build the Semantic Web for the Process Industries, enabling generic model-driven: Integration - “cradle to grave” Exchange - by mapping to standard format Sharing - by querying on an as-needed basis Hand-over - for consolidation up the hierarchy *) of globally distributed Plant Life-cycle Information *) e.g. app → discipline → project → JV project → owner/operator
Data used & Data produced Example: A pump sizing program requires process data and produces a pump size, which is of interest to Procurement
This has its drawbacks because of lack of real data management App to App Exchange This has its drawbacks because of lack of real data management
Map - Store - and - Query A query can be for the next task in the work flow, but also for a revamp 20 years from now.
Collecting, Mapping, Validating, Storing & Querying
Life-cycle Information Integration
Reference Data Library In order to avoid misunderstandings ISO 15926 has a Reference Data Library, that allows for local extensions:
Why not use the Semantic Web as-is? Because those semantics are too user-driven to be reliable enough for information exchange on a global scale. The Upper Ontology of ISO 15926-2 is used to enforce rigor. ISO 15926 fills the “Ontology vocabulary”, the “Logic” and the “Proof layer” in:
ISO 15926-2 – Data Model [1]
Any proprietary format
ISO 15926 information in Turtle format Information in some database, Excel spreadsheet, or other carrier can be mapped to a standard ISO 15926-8 file in Turtle format: :6AD438B0786841759B57F97E6EE9C5C7 rdf:type dm:Person, dm:WholeLifeIndividual, dm:ActualIndividual ; rdfs:label "John Doe" ; meta:valEffectiveDate "1971-05-27T05:34:00Z"^^xsd:dateTime . :F5EDBB01C666418897A696869DB3EFE rdf:type tpl:IndividualHasPropertyWithValue ; tpl:hasPropertyPossessor :6AD438B0786841759B57F97E6EE9C5C7 ; tpl:hasPropertyType rdl: RDS353339 ; # MASS tpl:hasPropertyValue "87,4"^^xsd:decimal ; tpl:hasScale rdl: RDS1328669 ; # KILOGRAM meta:valEffectiveDate "2019-03-27T14:25:00Z"^^xsd:dateTime .
ISO 15926 information in triple format That turtle file can be automatically converted to triples: <http://www.xyz.org/6AD438B0786841759B57F97E6EE9C5C7> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003#Person> . <http://www.xyz.org/6AD438B0786841759B57F97E6EE9C5C7> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003#WholeLifeIndividual> . <http://www.xyz.org/6AD438B0786841759B57F97E6EE9C5C7> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003#ActualIndividual> . <http://www.xyz.org/6AD438B0786841759B57F97E6EE9C5C7> <http://www.w3.org/2000/01/rdf-schema#label> "John Doe" . <http://www.xyz.org/6AD438B0786841759B57F97E6EE9C5C7> <http://data.15926.org/meta/valEffectiveDate> "1971-05-27T05:34:00+00:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> . <http://www.xyz.org/F5EDBB01C666418897A696869DB3EFE> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://data.15926.org/tpl/IndividualHasPropertyWithValue> . <http://www.xyz.org/F5EDBB01C666418897A696869DB3EFE> <http://data.15926.org/tpl/hasPropertyPossessor> <http://www.xyz.org/6AD438B0786841759B57F97E6EE9C5C7> . <http://www.xyz.org/F5EDBB01C666418897A696869DB3EFE> <http://data.15926.org/tpl/hasPropertyType> <http://data.15926.org/rdl/RDS2229547> . <http://www.xyz.org/F5EDBB01C666418897A696869DB3EFE> <http://data.15926.org/tpl/hasPropertyValue> "87,4"^^<http://www.w3.org/2001/XMLSchema#decimal> . <http://www.xyz.org/F5EDBB01C666418897A696869DB3EFE> <http://data.15926.org/tpl/hasPropertyType> <http://data.15926.org/rdl/RDS1328669> . <http://www.xyz.org/F5EDBB01C666418897A696869DB3EFE> <http://data.15926.org/meta/valEffectiveDate> "2002-09-27T14:25:00+00:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> . All plant life-cycle information, when converted this way and validated, is stored in an integrated manner in a Triple Store: the ISO 15926 Plant Archive It can be queried with the SPARQL query language.
Use of Semantic Web technologies For the implementation of ISO 15926 the following W3C Semantic Web standards are used: OWL - Web Ontology Language RDF - Resource Description Framework SPARQL - SPARQL Protocol and RDF Query Language R2RML - RDB to RDF Mapping Language SHACL - Shapes Constraint Language
The end result