why iso15926 is the best
DESCRIPTION
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.TRANSCRIPT
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.
Moscow29th of April, 2013
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.
ISO 15926
4
ISO 113545.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).
5
iRING architecture: federation
Product data
model
ISO 15926RDL
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
7
Problems and solutions
Domain scalabilityFact-orientedness and semanticsOntological approach:
Common “picture of the world”Notion of the “system” right out of the box
“Plain language”: patternsAvailability of high quality reference dataTools: variety of implementations of a standard
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
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)
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
11
Life cycle of valve in ISO 15926
!
!!
12
mapping
mapping
map
ping
mappingDesign applications
Procurement applications
P&ID applications
Operationapplications
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
Engineering application(CAD/PLM)
Semantic network
ISO 15926-2
Template patterns
ISO 15926
14
Availability of high quality reference data: JORD RDL
“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.
Product knowledge pyramid (ISO 15926)
ISO 15926
types
RDL
Catalogue(standard classes)
Product lines
and project
Deb
ug,
change management
Product configuration
baselines
Historic
data (product operations time rows)
Fo
rm
al
mo
de
l
RDL
Product data
15
Unstructured data
(NLP needed)
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
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!
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]
http://iringtoday.com/interview-with-frank-matthewson-of-bechtel/
19
Thank you!Anatoly Levenchuk,[email protected]: http://levenchuk.com
Victor Agroskin,[email protected]
TechInvestLab.ru (member of POSCCaesar Association)+7 (495) 748-53-88
.15926 Editor blog (in Russian)http://dot15926.livejournal.com