1. Introduction to IDS-ADI 15926 Resources
Ian Glendinning, DNV Information Risk Management
July 2009 (additional links added August 2009)
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

2. Everything you needed to know, but ...
Not Technology – Technology independent content aspects
Not Training – Overview what there is and where to look. (Further training can be project related.)
ISO15926 Standard
IDS-ADI Collaboration
Wiki Pages, File Repositories, Projects & Documents.- The key entry points.
Primer - What is about, why would / should business care >>> getting started.
”How to” guidelines – 90% technology independent step-wise ”maturity” from ”getting started” to full & sophisticated usage. Think ... Driving out ”ambiguity” is driving out cost and risk.
Compliance Guideline & Methodology Guideline & Business Interfaces Definition Guideline.
(Recap of ALL Linked Resources at the end.)
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

3. ISO 15926 - Reference Data Model
Templates (Part 7)
Standardised in ISO
Data Model
Standard &
Proprietary
Properties Classes
Manufacturer Specified Properties Classes
Property Classes
Standard &
Proprietary
Activity Classes
Manufacturer Specified Activity Classes
Standardised in ISO
Common
Terminology
Core
Classes
Standardised by e.g. ISO /IEC/ ANSI/ BS/DIN,
Represented using ISO 15926
Standard &
Proprietary
Classes
Implemented using SPARQL / Facade (Part 9)
Represented using RDF / OWL (Part 8)
Grouping Mechanism (Classes of Class etc.)
Product Catalogues
represented using ISO 15926
Physical Object Classes
This is 99% about Reference Data
Manufactured Item Classes
R D L
© Det Norske Veritas AS. All rights reserved
My thing
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

4. The Complete ISO15926 ”Stack”
ISO Overview and fundamentals (Approved IS)
ISO Data model (Approved IS) Represented in Part 4 RDL
ISO Geometry (Approved TS) (ISO Represented according to Part 2 in Part 4 RDL)
ISO Initial reference data. (Approved TS) (Included in the RDS/WIP RDL and extended from there according to Parts 5 & 6)
ISO Procedures for registration and maintenance of reference data (NWI/CD pending resolution on Management Agency) (Superseded - Ongoing migration to SC4 MA process. Involves PCA Special Interest Groups.)
ISO Scope and methodology for developing additional reference data (NWI/CD submitted to ISO Q3 2007) (Technical rules and meta-data for Part 5 process. In need of update partly due to evolution of Part 5 and Part 7.)
ISO Implementation methods for the integration of distributed systems (TS submitted to ISO Q3 2007) Approved with comments / Agreed split into separate parts Q (Completion Jun 2009) Represented in Part 4 RDL
ISO – OWL/RDF (W3C) implementation schema (Completion Sep 2009)
ISO – Façade (Web Interface) implementation (ISO deadline Feb 2010)
ISO – Test Methods (in planning / discussion)
ISO – Industrial Usage Guidelines (NWI agreed based on existing best-practice methodologies .)
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

5. ISO 15926 “Parts” Analogy Part 2 (in RDL) Natural Language Grammar
Core Data Model
Natural Language Grammar
(Basic rules)
Part 4 (RDL)
Reference Data
Dictionary & Thesaurus (Words & terms, extensible)
Phrase, Sentence, Paragraph, Verse, Rhyme, Lyric (Useful semantic structures, extensible)
Part 7 (in RDL)
Templates
Part 8
RDF/OWL
Paper, File, Website, Stone-tablet
(Representation technology)
Part 9
Façades
“Reading”
(Read, write, query, services technology)
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

6. The IDS-ADI Collaboration
- Realizing Open Information Interoperability … through deployment & exploitation of ISO15926 … as a close ongoing collaboration since 2007 between:
POSC-Caesar’s IDS Project(s), and
FIATECH’s ADI Project(s)
Multiple projects with a Coordinated plan & steering team.
Steering Team – Bechtel, Bentley, DNV, Fluor, Noumenon, NRX
Participants – AVEVA, Bentley, Bechtel, CCC, Chevron, Conoco-Phillips, DNV, Dow, Du Pont, Emerson, Fluor, Hatch, Intergraph, Noumenon, NRX, SNC-Lavalin, TCS ... and more in IDS2 and other newer projects
Projects – many “core” and “matrix” projects since 2008 : including ...
Modelling & Implementation (& ISO) core tasks
15926 Industrial Usage Guidelines (Mapping & Compliance)
CAMELOT - “iRING” implementation and deployment of open-source infrastructure using W3C technologies (>>> Avalon)
PROTEUS (Matrix123) - XML implementation of P&ID & 3D Content
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

7. Key IDS-ADI ”Getting Started” Entry Points
Note / Beware ... This is (mostly) open wiki-style collaboration ... it’s no-one’s ”job” to keep all the pages up-to-date / consistent !!! (Formal Documents have publishing version control.)
currently resolves to (PCA funds hosting so far. The business model for a sustainable infrastructure is Avalon’s main goal. FIATECH already agreed to pick-up certain costs.)
ISO Structure & Parts (see earlier slides)
Primer - What is about, why would / should business care up to ”getting started” (so far) We could and should develop getting started scenarios for different starting points and domains of interest. We could and should incorporate the intent of this presentation into the Primer too.
Tutorial – Background and explanation of ISO15926 and its modelling (good, but incomplete).
Avalon Project >> Wiki &”SVN” Repository & Tortoise / Windows Shell and iRING technology
PCA RDS (reference data services & resources) (Note also links to Camelot & Avalon for iRING and OWL RDF Endpoints, Avalon / PCA aim is to fix RDLFACADE endpoints sustainably)
After ”Getting Started” .... Specific ”How To” guideline documents .... >>>> Next
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

8. ”Next” - Other Key Guideline Documents
Compliance Guideline – How do I comply with ISO15926 ?
Mapping & Characterization Methodology Guideline - How do I relate my data to Reference Data ? (No page yet ... omission ... was seen as part of the Part 7 project) Repository, Doc and XLS ... Some overview coming up here ...
Business Interfaces Definition Guideline - How do I determine the content of important data scopes ? (BIDG – aka / was ”Handover Guide”) Technically this is part of the ”Compliance Guideline” as we shall see ...
(Note all these are candidates for incorporation in Part 11 – Industrial Usage Guidelines, in collaboration with USPI and ”Gellish” – already implicit in the Methodology.)
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

9. COMPLIANCE
Levels of Ambiguity / Driving out Ambiguity Progressive / Levels / ”Stepping Stones” Do simple & important stuff first Get more ambitious later.
Several (many) different axes / aspects to this. (what’s simple, what’s important, what’s ambiguous ... ?)
Summary is Table 4.2 in the Compliance Guideline.
The Yellow (aka Dictionary) / Green / Blue / Red (aka Full) levels were seen to have some significance / value ... Targets to aim for ... But this is a checklist for how compliant you might be.
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

10. Information Ambiguity
Greatest
Least Ambiguity
Knowledge
Compliance
Ambiguity Scale
Full Template Implementation with iRING 2.0 technology
Data exchanges operate most successfully when ambiguity is eliminated
Ambiguity between exchanging partners can require significant effort (labor) to remove
The higher the ambiguity, the higher the cost to implement effective and efficient data exchanges
Ambiguity = Cost &/or Risk
ISO 15926
Simplified Template Implementation with iRING 1.0 technology
Information
Least
XML Schema Dictionary Level Exchange
Compliance
Comma Delimited File
Greatest Ambiguity
Data
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

11. Example - The OLF view (from IDS Project)
See also : USPI ”Business Readiness Model” AVEVA & INGR Solution models SAP & IBM Engagement models Dow ”Multi-Generational Plans” DNV ”Maturity Model” ... Etc.
Source – Thore Langeland PCA Kuala-Lumpur Oct 2008
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

12. Pragmatic Business meets Pragmatic ISO15926
>>>>
RDL Content Management
RDS Operations
By establishing compliance at Interfaces only ... aka ”15926 Outside” And by establishing Compliance Categories (Checklist) ... aka ”Stepping Stones” Classifying .... Business-Scope & Information-Criticality; Change-Management-Meta-Data; Mapping & Implementation-Sophistication; Standardization Level & more ...
Dictionary Level
GREEN
BLUE
Full
File Exchange
XML Schema
RDL Content & References
File Exchange, API or Query Interface,
”PublicTemplate” Schema
RDL Endpoint URI’s
File Exchange, API or Query Interface
”Part7Full” Schema
Part 9 Facade Web Interface
Part8-Full-OWL/RDF Schema
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

13. Reference Data Federation
Levels of Standardization
Certification Requests
ISO
RDS/WIP Editor
PCA
Immutable ID’s
Global
Sandbox
iRING
Mapping Editor
Community
Sandbox
Read-Write
Private
Sandbox
Federated Access
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

14. COMPLIANCE
Levels of Ambiguity / Driving out Ambiguity
Several (many) different axes / aspects to this.
NB Remember ... Full Summary is in Table 4.2 in the Compliance Guideline.
The Yellow (aka Dictionary) / Green / Blue / Red (aka Full) levels were seen to have some significance / value ... Targets to aim for ... But this is a checklist for how compliant you might be.
The ”semantic” (ambiguity) axis is what the ”methodology” guideline really focusses on .... Next.
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

15. METHODOLOGY
Follows the COMPLIANCE ”maturity” approach .... Still about driving out ambiguity, progressively ie Do simple & important stuff first Get more ambitious later.
Overview Graphic (from the document). on Template and RDL Item Selection Logic and identifying new RDL Item Requirements
One example issue (Tag / Equipment) that demands ”methodical” approach rather than guesswork based on RDL Item naming ...
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

16. Methodology (Feb 2009 Latest)
Semantic Characterization Stage
Interact with RDL / WIP Propose New RDL Items
Syntactical Definition Stage No
Use Current Map Version for Intended Business Use Recycle from Start (as necessary)
Yes
(Optional) cardinalities, rules, etc.
Starting Resources (Well-formed Domain Schema & Dataset View)
Starting Resources (Pro-forma Dataset View & sample instances
Excel or XML
(Addr. DOM)
Fig 3.2 Summary Mapping Flowchart
START
END
Pro-Forma Mapping Definition of Template Signature(s).
Part-8&9 OWL / Façade Representation & Implementation ?
View or Report Def
Create Def
Each “Cell”
Simple DOM Addressable (Excel or XML)
Mapping Selection Logic
Select Public Template(s)
Full Part-2-explicit- Part-7 Templates
Select RDL Item(s)
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

17. The Life Cycle According to IEC 61346-4
All objects have separate lifecycles
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

18. Life Cycle Objects All objects have separate lifecycles - Environment
18DE911A
Identifier
Tag xxxx
Design Case 1
Design Case 2
Tag 18nn911A
Process Case n
- Environment
HAZOP
Maintainability
etc
External requirements
Functional Location 18DE911A
Performance Requirements
Driving at 18DE911A
Package
Specification
MMMM
Data Sheet for
xxxx
Tag 18DE911A
Procurement
Package
MMMM
FL / Tag SO
Material
Equipment FR
Tag xxxx
Design Case 1
Design Case 2
Tag 18nn911A
Pumping Case n
Electric Motor
suitable for
18DE911A
Consolidated performance envelope
Model X
Variant Y
Conformance
Consolidated
Requirements
Model: SIEMENS 1LA
Variant: SIEMENS 1LA AA64-
ZA11+G50+K45+N90+Y82
Data Sheet for
Model X Vaiant Y
Model X
Variant Y
Serial #
Conformance
Operational Data
for #123456
Equipment: SIEMENS 1LA AA64-
ZA11+G50+K45+N90+Y82, #
All objects have separate lifecycles
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

19. Example of ”Level of Realization” logic
(Text extracted from the Methodology itself)
LOR (T) – where the subject matter records the definition of an individual functional process location or role, or [....] typically identified by a Tag). The level of least physical realization. (Equivalent to IEC “FR”)
LOR (R) – where the subject matter is consolidated business Requirements including the functional purpose LOR(T) above, other functional cases and other capabilities [....] A level of lesser physical realization. (Equivalent to IEC “CS”)
LOR (P) – where the subject matter concerns an available Product specification, typically catalogue items, [....]. A level of greater physical realization. (Equivalent to IEC “PS”)
LOR (E) – a where the subject matter records an individual resource employed / employable installed / installable to fulfill a business need or role [....] Typically an Equipment item and the individual log or record of that item.) The level of greatest physical realization. (Equivalent to IEC “IL”)
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

20. Recap ... Not Technology – Technology independent content aspects
Not Training – Overview what there is and where to look. (Further training can be project related.)
ISO15926 Standard
IDS-ADI Collaboration
Wiki Pages, File Repositories, Projects & Documents.- The key entry points.
Primer - What is about, why would / should business care >>> getting started.
”How to” guidelines – 90% technology independent step-wise ”maturity” from ”getting started” to full & sophisticated usage. Think ... Driving out ”ambiguity” is driving out cost and risk.
Compliance Guideline & Methodology Guideline & Business Interfaces Definition Guideline.
All linked resources Next page >>>
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

21. Recap – all linked resources.
Note / Beware ... This is (mostly) open wiki-style collaboration ... it’s no-one’s ”job” to keep all the pages up-to-date / consistent !!! (Formal Documents have publishing version control.)
IDS-ADI - currently resolves to (PCA funds hosting so far. The business model for a sustainable infrastructure is Avalon’s main goal. FIATECH already agreed to pick-up certain costs.)
ISO Structure & Parts (see earlier slides)
Primer - What is about, why would / should business care up to ”getting started” (so far) We could and should develop getting started scenarios for different starting points and domains of interest. We could and should incorporate the intent of this presentation into the Primer too.
Tutorial – Background and explanation of the ISO15926 modelling approach (Good, but incomplete in terms of Template usage).
Avalon Project & iRING Technology
PCA RDS (reference data services & resources) ...
(Note also links to Camelot & Avalon for iRING and OWL RDF Endpoints, Avalon / PCA aim is to fix RDLFACADE endpoints sustainably)
Mapping & Characterization Methodology Guideline (Industrial Usage - Proposed Part 11 harmonization with Gellish) - How do I relate my industrial data to Reference Data ?
Compliance Guideline – How do I comply with ISO15926 ?
(BIDG – aka / was ”Handover Guide”) Business Interfaces Definition Guideline - How do I determine the content of important data scopes ? Structly this is part of the ”Compliance Guideline”
© Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y

22. © Det Norske Veritas AS. All rights reserved
17 September 2018
R e a l i z i n g O p e n I n f o r m a t i o n I n t e r o p e r a b i l i t y