Onno Paap Fluor Corporation - Combined with “ISO 15926 templates and the Semantic Web” from DnV “W3C Oil&Gas Workshop” 9-10 Dec 2008 – Houston TX USA ISO 15926 • Interoperability standard • Interoperability: the ability of different types of computers, networks, operating systems, and applications to work together effectively, without prior communication, in order to exchange information in a useful and meaningful manner. • Neutral layer used for data integration Transactions ECC GERMANY QUADREM Catalogues ODETTE Classification FRANCE OASIS REQUI Dictionaries SAP SITE Product Descriptions ccHUB AFIM KOMER WOO KO CAT BMEcat TRADE- TROCS RANGER pilot UN/CEFACT PFI MOSAIC
15926) – Total value $3.5 million • POSC Caesar IDS (Intelligent data Sets) – Total value: $2.5 million 20 ISO 15926 projects RDL: reference data library
ISO 15926
Information Information
Exchange
The ISO 15926 provides the ability to build
common data models ISO 15926 part 4 spreadsheets Spreadsheet count Spreadsheet count
query &map Façade Other’s Façades Confederation of Participating Façades (CPF) Reference Data map façade Library query
Plant Owner/ map façade
Operator - HQ query
Plant Owner/ map façade
Operator - Plant query
EPC contractor – map façade
A query internet EPC contractor – map façade B query
Your laptop with
Supplier Catalog – façade map façade browser e.g. PLib query
Supplier – project map façade
data query
RDL of standards map façade
organization query ISO TC67 OIL Industry Standards Reference Data Libraries ISO defined in core classes ISO 15926-4, & reference in OWL format individuals
mapping in ISO 15926-7 format ERDL standard façade core classes catalogs classes in & reference in other other individuals formats formats n spe atio mapping
mapping iz cia l liza cia tion spe specialization
specialization end-user specialization product &
standard classes & classes service individuals classes
specialization façades of government supplier and industry end-user façades standardization bodies façades Wanted: A simple, compliant interface • Standardized modelling practice • Tools that are familiar to domain experts –Protégé, Reference Data Editor are out • Tools that support the user and check correctness –Excel is out • Tools that provide for working at a suitable level of abstraction –Most ontology editors expose the user to too much ”assembly code” Building domain ontologies with templates
• An ontology is used to record statements. That’s
semantics. • To build the RDL, we need to represent facts about a given domain using the language of ISO 15926 • Ideally, a domain expert states the facts, and the machine interprets the facts automatically A template is a pattern for stating facts • A Template for ISO 15926 is a predicate, a statement form, a pattern for facts • A template has a signature defining the form of a statement – What arguments need to be given – What are their types • Each template has an interpretation rule that interprets facts that fit the pattern – Reducing a complex statement into simpler ones – Eventually, to atomic statements in ISO 15926 – Yielding an expression of the fact in the ontology language • Logical methodology is rigorously defined in ISO 15926-7 Template example I
• Constraint: A car has 3 or more wheels
• Express the constraint with a suitable template Parts-at-least ( Car, Wheel, 3 ) ! • Rules generate a set of ISO 15926 statements
“ The statement Parts-at-least ( C, D, i )
means that Any C has at least i D’s as parts ” Template example I • Assume that any car has 3 or more wheels • Expressed with a suitable template Parts Parts-at-least ( Car, Wheel, 3 ) ! • Rules generate a set of ISO 15926 statements
• … as illustrated by this figure
Input in a straightforward XML format <AScCC> <ASc_Part> <designation>Wheel</designation> </ASc_Part> <ASc_Whole> <designation>Car</designation> </ASc_Whole> <RCard_Lower1> <content […]>1</content> […]>3</content> </RCard_Lower1> <RCard_Upper1/> </AScCC>
AA car car has has at at least least three three wheels. wheels. A familiar interface
• Making the statement
Parts-at-least ( Car, Wheel, 3 ) requires no detailed knowledge about modelling • A list of arguments can easily be stored in a table (Excel!) Equipment type Part type Min. number of parts Car Wheel 3 Bicycle Wheel 1 • Correctness of the generated ontology structure can be checked using generic ontology tools Translation by means of templates
Data in Data in Template Ontology Template Format DB Format lifting lowering And back again A simple mapping into template statements
DB DB Template example II
• A fairly complex claim
“The ambient temperature during operation of a 3051CG pressure transmitter should be within -40 and 85 degrees Celsius.” • Five arguments are required for a precise statement “The body height of a human is a property which varies from 50 to 250 cm” Property with Scale and Quantification Sample device class
3051CG Celsius
CO Individual Scale
“The ambient temperature during operation of a 3051CG pressure
transmitter should be within -40 and 85 degrees Celsius.” Property Range
3051CG
CO Individual Property Range Restriction
Classified
Classifier 3051CG
CO Individual
CO Indirect Property Model: Ambient Temperature Range
building • Let the compiler handle the “assembly language” • Creating rich semantic structure becomes practical • Standardization of templates makes standardized modelling patterns possible Information
