Version 8 (modified by gordonrachar, 14 years ago)

--

What Has Been Done to Implement ISO 15926

Status of this document: Working Draft

This document is open for feedback, please post questions and comments in the forum at the bottom of this page. You will need a login to post in the forum.


Contents

  1. Abstract
  2. ISO 15926 Part 4 Implementations
    1. One
    2. Two
  3. Origin of Proteus and Camelot
  4. Proteus
    1. Participants
    2. Scope
  5. Proteus Data Flows
    1. P&ID to P&ID
    2. 3D to 3D
    3. P&ID to 3D
  6. Camelot - the Kitty Hawk of ISO 15926
    1. Purpose of Camelot
    2. Project Participants
    3. ISO 15926 Realtime Interoperability Network Grid
  7. Camelot Demonstration Data Flows
    1. P&ID to P&ID - Property Update Scenario
    2. P&ID to Data Warehouse - Handover Scenario
    3. P&ID to Data Warehouse - Visualization Scenario
    4. P&ID to Datasheet - Supplier Scenario
    5. P&ID to Datasheet - Email Scenario
  8. Next

Abstract

Ogranizations have been using the ISO 15926 dictionary, Part 4 (ISO 15926-4) for over a decade.

In the spring of 2009 two projects were initiated to take the Implementation of ISO 15926 to a new level. Conceived as "Proofs of Concept", they were demonstrated at the May 2009 FIATECH conference in Las Vegas, Nevada.

  • Proteus - Improve the implementation of ISO 15926-4
  • Camelot - Implement the full specification of ISO 15926 including parts 7, 8, and 9

ISO 15926 Part 4 Implementations

...

One

...

Two

...


Origin of Proteus and Camelot

In April 2008, FIATECH convened a meeting of Owner/Operators, EPCs, software vendors and equipment suppliers to see what could be done to jump-start the development of some of the details of ISO 15926. As a result, two subprojects were spawned.

  • Proteus, to improve the implementation of ISO 15926-4 (originally called Matrix 123)
  • Camelot, a proof of concept implementation of ISO 15926-7,8,9 (originally called Matrix 8)

Error: Macro Image(Implement_01.JPG, 700px) failed
Attachment 'wiki:ISO15926Primer_Implementations_WhatBeenDone: Implement_01.JPG' does not exist.

Fig 1 - Proteus and Camelot Information Exchange Subprojects


Proteus

The purpose of Proteus was to prove that P&ID data and 3D data can be transferred between commercial software from competing vendors. These objectives were met, and in addition achieved two significant breakthroughs:

  • Competing vendors have committed to deliver commercial interfaces for ISO 15926 Dictionary XML files for release by the end of 2009.
  • Going forward, these same vendors have agreed to collaborate to test their interfaces.

The significance of this milestone is that it bootstraps the adoption of the full specification of ISO 15926:

  • Organizations can use commercial tools to implement ISO 15926 at the dictionary level to get a quick return on their investment.

  • The ISO 15926 RDS/WIP has been extended to support Proteus. As organizations use Dictionary-enabled software, new opportunities will be identified to extend it further.

Participants

  • Dow
  • AspenTech
  • Noumenon
  • DuPont
  • Intergraph
  • Octega
  • AVEVA
  • Innotec (Comos)
  • Bentley
  • Dassault

Scope

Scope of Data Exchange:

  • Tag No’s
  • Schematic information (i.e., look and feel, topology)
  • All P&ID connectivity, including off-page connectors
  • Flow direction is implicit
  • Metadata of P&ID

Not in Scope:

  • Design data and process data
  • Process data propagation rules
    • flow direction
    • spec-based restrictions
    • metadata of represented objects

General Rules

  • Use RDS/WIP for class names
  • Use XMpLant schema 3.3
  • Each vendor to submit P&IDs of agreed content executed in own system, with XML output files.
  • Each vendor will demonstrate on its own at the FIATECH conference in April, plus at a common desk.

Some Issues:

  • There are differing degrees of definitions in different systems, especially between 2D and 3D. (e.g., generic valve symbol in P&ID, but more specific description in 3D.
  • Some rules may be lost due to the information that some systems do not retain:
    • viability of certain valves
    • details of certain specs
    • orientation of check valves

Proteus Data Flows

P&ID to P&ID

Error: Macro Image(Implement_Proteus_01.JPG, 500px) failed
Attachment 'wiki:ISO15926Primer_Implementations_WhatBeenDone: Implement_Proteus_01.JPG' does not exist.

Fig 1 - P&ID to P&ID

. . .

3D to 3D

Error: Macro Image(Implement_Proteus_02.JPG, 500px) failed
Attachment 'wiki:ISO15926Primer_Implementations_WhatBeenDone: Implement_Proteus_02.JPG' does not exist.

Fig 2 - 3D to 3D

. . .

P&ID to 3D

Error: Macro Image(Implement_Proteus_03.JPG, 500px) failed
Attachment 'wiki:ISO15926Primer_Implementations_WhatBeenDone: Implement_Proteus_03.JPG' does not exist.

Fig 3 - P&ID to 3D

. . .


Camelot - the Kitty Hawk of ISO 15926

Previously in the Primer we have used the metaphor of heavier-than-air flight. Using this same metaphor, the Camelot demonstration in April 6, 2009 in Las Vegas was the Kitty Hawk of ISO 15926.

According to Wikipedia, On December 17, 1903, on the sand dunes of Kill Devil Hills, North Carolina, a town near Kitty Hawk, Orville and Wilbur Wright flew the first airplane on several short flights. The Wright Flyer, as it was called then, was crude by the standards that would become normal even few years later, but proved a number of concepts, not the least of which was three-axis control, a system developed by the bothers that solved the real problem of flight.

Man will fly, but not in our lifetimes.
Wilbur Wright to Orville in 1901 after repeated failure during their second season of field trials.

Camelot was a proof of concept to show that realistic business information can be transferred between EPC, Owner/Operator, Instrument Vendor, and Constructor using ISO 15926 tools. The software was made available under an open source license after the project was completed.

Purpose of Camelot

The purpose of Camelot, was to demonstrate that the full ISO 15926 specification could be used to transfer information between several organizations in a realistic setting. Thus, Camelot proved the viability of ISO 15926 by demonstrating several things:

  • An ISO 15926 open source infrastructure on the Internet and to show the following capabilities:
    • The use of ISO 15926 in modeling business information
    • The setup, configuration, and use of publicly available tools to map legacy systems to ISO 15926
    • The demonstration of several data exchange scenarios between several companies using ISO 15926 over the Internet.

It used the full ISO 15926 specification:

  • Part 2 - Data Model
  • Part 4 - Classes
  • Part 7 - Templates
  • Part 8 - RDF
  • Part 9 - Façades

Project Participants

  • Bechtel
  • Bentley
  • Chevron
  • Consolidated Contractors Company (CCC)
  • Det Norske Veritas (DNV)
  • Dow Chemical
  • DuPont
  • Emerson Process Management
  • Fluor
  • Hatch
  • Intergraph
  • NRX Global
  • Tata Consultancy Services (TCS)
  • Zachry

ISO 15926 Realtime Interoperability Network Grid

In every instance, the data item that was transferred started in a commercial or proprietary software application. It was first transformed in its respective iRING adapter and transferred via the iRING web services to the target location where it was transformed again with an iRING adapter into the target application.

Camelot Demonstration Data Flows

P&ID to P&ID - Property Update Scenario

Error: Macro Image(Implement_Camelot_01.JPG, 500px) failed
Attachment 'wiki:ISO15926Primer_Implementations_WhatBeenDone: Implement_Camelot_01.JPG' does not exist.

Fig 4 - P&ID to P&ID

The first data flow transferred P&ID line properties from a PlantSpace P&ID to the same drawing in SmartPlant P&ID.

The second data flow transferred P&ID equipment properties from an OpenPlant PowerPID to the same drawing in SmartPlant P&ID

P&ID to Data Warehouse - Handover Scenario

Error: Macro Image(Implement_Camelot_02.JPG, 500px) failed
Attachment 'wiki:ISO15926Primer_Implementations_WhatBeenDone: Implement_Camelot_02.JPG' does not exist.

Fig 5 - P&ID to Data Warehouse

The third and fourth data flows represented an EPC-to-Owner Operator scenario transferring P&ID data from two different P&ID products to a common data warehouse. One data flow was from PlantSpace P&ID and the other from OpenPlant PowerPID. Both were merged inside SmartPlant Foundation.

This demonstration showed how ISO 15926 can transform information from one form (P&ID) into a completely different representation (data warehouse). Once the P&ID information data was in the data warehouse, Intergraph demonstrated how the relationship data of ISO 15926 could be exploited to open a 3D representation of the transferred data and use that representation to navigate through the information.

P&ID to Data Warehouse - Visualization Scenario

Error: Macro Image(Implement_Camelot_03.JPG, 500px) failed
Attachment 'wiki:ISO15926Primer_Implementations_WhatBeenDone: Implement_Camelot_03.JPG' does not exist.

Fig 6 - P&ID to Data Warehouse

The fifth and sixth data flows represented a project construction scenario where two EPCs communicate to one constructor.

In this demonstration pipe line properties, including pressure and temperature, in two different commercial P&ID applications were transferred to proprietary 3D construction visualization software at the constructor's office. When the data was received by the constructor's 3D software, the new pressure and temperature values triggered rules that set the color of the pipe to show, in this example, high values for both attributes.

In the sixth data flow, job site delivery dates and hydrostatic testing statuses were sent from the constructors SQL Server database back to the data center of one of the EPCs.

P&ID to Datasheet - Supplier Scenario

The seventh and eighth data flows were from different but related P&ID sheets at two EPCs to a supplier. Vortex Flow Meter data sheet information from the P&IDs was updated into the supplier's data sheets running in Excel.

Error: Macro Image(Implement_Camelot_04.JPG, 500px) failed
Attachment 'wiki:ISO15926Primer_Implementations_WhatBeenDone: Implement_Camelot_04.JPG' does not exist.

Fig 7 - P&ID to Datasheet

P&ID to Datasheet - Email Scenario

Error: Macro Image(Implement_Camelot_05.JPG, 500px) failed
Attachment 'wiki:ISO15926Primer_Implementations_WhatBeenDone: Implement_Camelot_05.JPG' does not exist.

Fig 8 - P&ID to Datasheet via Email

Sometimes setting up web services to support data exchange directly between engineering applications might be difficult, or might violate an organization's Internet security policy. The ninth and final data flow demonstrated the use of iRING technology without web service.

In this demonstration value properties were published to an iRING adapter hosted in one office, and from there exported to an RDF file (A World Wide Web Consortium (W3C) standard) and emailed to the other office. Once arrived, the RDF attachment was imported into the iRING adapter, then mapped and transformed and loaded into a SQL Server database.

Next

Avalon


Discussion

You have no rights to see this discussion.

Home
About PCA
Reference Data Services
Projects
Workgroups