SlideShare a Scribd company logo
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
ISO 15926 technology
Source: FIATECH
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
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
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
Version of iRING (ISO 15926) architecture
6
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
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
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
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
Life cycle of valve in ISO 15926
11
!
!!
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
“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
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.
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)
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
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
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
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

More Related Content

PDF
ISO 15926 series standard and its business value
PDF
IoT Analytics From Data to Decision Making - Trends & Challenges
PPTX
Veri Ambarı Nedir, Nasıl Oluşturulur?
PPTX
IBM Cloud Storage - Cleversafe
PDF
Database Cloud Services Office Hours : Oracle sharding hyperscale globally d...
PPT
Implementing Semantic Search
PDF
Infographic: Data Governance Best Practices
PPTX
Taxonomies and Metadata
ISO 15926 series standard and its business value
IoT Analytics From Data to Decision Making - Trends & Challenges
Veri Ambarı Nedir, Nasıl Oluşturulur?
IBM Cloud Storage - Cleversafe
Database Cloud Services Office Hours : Oracle sharding hyperscale globally d...
Implementing Semantic Search
Infographic: Data Governance Best Practices
Taxonomies and Metadata

What's hot (20)

PDF
What Is Hadoop | Hadoop Tutorial For Beginners | Edureka
PDF
Preparing Data for Sharing: The FAIR Principles
PDF
Intuit's Data Mesh - Data Mesh Leaning Community meetup 5.13.2021
PDF
Blockchain Interoperability using Cosmos Interblockchain Communication
PPTX
Data mesh
PPTX
Inside open metadata—the deep dive
PDF
Big data landscape v 3.0 - Matt Turck (FirstMark)
PPTX
Teradata introduction - A basic introduction for Taradate system Architecture
PDF
Advanced level planning and budgeting in Hyperion - Inge Prangel
PDF
Oracle Spatial Studio: Fast and Easy Spatial Analytics and Maps
PDF
Effective Communication Network Development through a Model-Based Systems App...
PPT
Why Data Virtualization? An Introduction by Denodo
PDF
Moving to the Maintenance Cloud
PDF
ODSA - OCP Accelerator Module and the Infrastructure
PDF
2014 한국 링크드 데이터 사례집
PDF
Presentation Maintenance Cloud.pdf
PDF
Data Migration to Azure
PDF
Oracle Analytics Cloud
PDF
Time to Talk about Data Mesh
PPTX
FAIR Data-centric Information Architecture.pptx
What Is Hadoop | Hadoop Tutorial For Beginners | Edureka
Preparing Data for Sharing: The FAIR Principles
Intuit's Data Mesh - Data Mesh Leaning Community meetup 5.13.2021
Blockchain Interoperability using Cosmos Interblockchain Communication
Data mesh
Inside open metadata—the deep dive
Big data landscape v 3.0 - Matt Turck (FirstMark)
Teradata introduction - A basic introduction for Taradate system Architecture
Advanced level planning and budgeting in Hyperion - Inge Prangel
Oracle Spatial Studio: Fast and Easy Spatial Analytics and Maps
Effective Communication Network Development through a Model-Based Systems App...
Why Data Virtualization? An Introduction by Denodo
Moving to the Maintenance Cloud
ODSA - OCP Accelerator Module and the Infrastructure
2014 한국 링크드 데이터 사례집
Presentation Maintenance Cloud.pdf
Data Migration to Azure
Oracle Analytics Cloud
Time to Talk about Data Mesh
FAIR Data-centric Information Architecture.pptx
Ad

Viewers also liked (8)

PDF
2009 Hausmann Catalog Sec1 p1-16
PPTX
Digital humanities
PPT
ISO 18876
PDF
PROTEAM by Hausmann 2011-2013 Catalog
PPT
1257103560 X Mp Lantand Iso15926 Oct2009
PDF
Strategic Planning for 2015 Capital Replacement Projects
PPTX
디지털 플랜트를 위한 정보상호운용성 및 활용성 제고
PPTX
일신오토클레이브 회사소개서
2009 Hausmann Catalog Sec1 p1-16
Digital humanities
ISO 18876
PROTEAM by Hausmann 2011-2013 Catalog
1257103560 X Mp Lantand Iso15926 Oct2009
Strategic Planning for 2015 Capital Replacement Projects
디지털 플랜트를 위한 정보상호운용성 및 활용성 제고
일신오토클레이브 회사소개서
Ad

Similar to Why ISO15926 is the best (20)

PPTX
ISO 15926 Reference Data Engineering Methodology
PPT
dot15926 Software Presentation
PPTX
Sustaining Nuclear Infrastructure Wna China Nov10
PPTX
Part 10, Need to be clarified
PPT
5 Standards-based Content Resources: A Prerequisite for Content Integration a...
PPT
Michael Lang Sr. Presentation
PPT
Situational Method Engineering
PPTX
ISO SC4 TC184 65th Workshop IMAGINE inputs for Future Architecture
PDF
Corporate presentation (short with examples)
PDF
Ultra large scale systems to design interoperability
PPT
An approach to use PERA in Enterprise Modeling for industrial systems
PDF
ISO 15926 - Enabling a consumer view of data, Glen Worrall, Bentley Systems (...
PPTX
Industry day june 2013 standard and research v2
PPTX
Towards Flexible Indices for Distributed Graph Data: The Formal Schema-level...
PDF
B131626
PDF
Enterprise integration an arch fred a. cummins
PPTX
Why Enterprise Service Bus (ESB)
PPTX
Ontology-Based Systems Federation
PPTX
Knowledge Graph Introduction
PDF
Interoperability For Enterprise Software And Applications Herve Panetto
ISO 15926 Reference Data Engineering Methodology
dot15926 Software Presentation
Sustaining Nuclear Infrastructure Wna China Nov10
Part 10, Need to be clarified
5 Standards-based Content Resources: A Prerequisite for Content Integration a...
Michael Lang Sr. Presentation
Situational Method Engineering
ISO SC4 TC184 65th Workshop IMAGINE inputs for Future Architecture
Corporate presentation (short with examples)
Ultra large scale systems to design interoperability
An approach to use PERA in Enterprise Modeling for industrial systems
ISO 15926 - Enabling a consumer view of data, Glen Worrall, Bentley Systems (...
Industry day june 2013 standard and research v2
Towards Flexible Indices for Distributed Graph Data: The Formal Schema-level...
B131626
Enterprise integration an arch fred a. cummins
Why Enterprise Service Bus (ESB)
Ontology-Based Systems Federation
Knowledge Graph Introduction
Interoperability For Enterprise Software And Applications Herve Panetto

More from Anatoly Levenchuk (20)

PPTX
Contemporary Systems Engineering (oct 2022)
PPTX
Open-endedness curriculum at EEM Institute
PPTX
Праксиология и системное мышление
PPTX
А.Левенчук -- развитие личности
PPTX
А.Левенчук -- стейкхолдерское мастерство
PPTX
А.Левенчук -- SysArchi
PPTX
А.Левенчук -- как выжить в эпоху перемен перемен
PPTX
А.Левенчук -- Практики системной инженерии
PPTX
А.Левенчук -- визуальное мышление
PPTX
А.Левенчук -- системное развитие личности
PPTX
А.Левенчук -- Будущее девелопмента
PPTX
А.Левенчук -- Системное мышление в инженерии предприятий
PPTX
А.Левенчук -- Системное мышление и управление конфигурацией
PPTX
А.Левенчук -- аппаратное ускорение аналитики в BigData
PPTX
А.Левенчук -- Будущее проектирования
PPTX
Future of Engineering
PPTX
А.Левенчук -- безлюдные (дез)организации
PPTX
А.Левенчук -- предпринимательство: кейс NVIDIA
PPTX
Системное мышление -- непопсовый обзор курса
PPTX
А.Левенчук -- системный фитнес
Contemporary Systems Engineering (oct 2022)
Open-endedness curriculum at EEM Institute
Праксиология и системное мышление
А.Левенчук -- развитие личности
А.Левенчук -- стейкхолдерское мастерство
А.Левенчук -- SysArchi
А.Левенчук -- как выжить в эпоху перемен перемен
А.Левенчук -- Практики системной инженерии
А.Левенчук -- визуальное мышление
А.Левенчук -- системное развитие личности
А.Левенчук -- Будущее девелопмента
А.Левенчук -- Системное мышление в инженерии предприятий
А.Левенчук -- Системное мышление и управление конфигурацией
А.Левенчук -- аппаратное ускорение аналитики в BigData
А.Левенчук -- Будущее проектирования
Future of Engineering
А.Левенчук -- безлюдные (дез)организации
А.Левенчук -- предпринимательство: кейс NVIDIA
Системное мышление -- непопсовый обзор курса
А.Левенчук -- системный фитнес

Recently uploaded (20)

PPT
“AI and Expert System Decision Support & Business Intelligence Systems”
PDF
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
PDF
Encapsulation_ Review paper, used for researhc scholars
PDF
Encapsulation theory and applications.pdf
PDF
Chapter 3 Spatial Domain Image Processing.pdf
PPTX
Digital-Transformation-Roadmap-for-Companies.pptx
PDF
Network Security Unit 5.pdf for BCA BBA.
PPTX
20250228 LYD VKU AI Blended-Learning.pptx
PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
DOCX
The AUB Centre for AI in Media Proposal.docx
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
PPTX
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
PDF
MIND Revenue Release Quarter 2 2025 Press Release
PDF
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
PDF
cuic standard and advanced reporting.pdf
PDF
Spectral efficient network and resource selection model in 5G networks
PPTX
sap open course for s4hana steps from ECC to s4
PDF
NewMind AI Weekly Chronicles - August'25 Week I
PDF
Approach and Philosophy of On baking technology
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
“AI and Expert System Decision Support & Business Intelligence Systems”
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
Encapsulation_ Review paper, used for researhc scholars
Encapsulation theory and applications.pdf
Chapter 3 Spatial Domain Image Processing.pdf
Digital-Transformation-Roadmap-for-Companies.pptx
Network Security Unit 5.pdf for BCA BBA.
20250228 LYD VKU AI Blended-Learning.pptx
Mobile App Security Testing_ A Comprehensive Guide.pdf
The AUB Centre for AI in Media Proposal.docx
Reach Out and Touch Someone: Haptics and Empathic Computing
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
MIND Revenue Release Quarter 2 2025 Press Release
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
cuic standard and advanced reporting.pdf
Spectral efficient network and resource selection model in 5G networks
sap open course for s4hana steps from ECC to s4
NewMind AI Weekly Chronicles - August'25 Week I
Approach and Philosophy of On baking technology
The Rise and Fall of 3GPP – Time for a Sabbatical?

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
  • 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

  • #4: 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).