Changes between Version 46 and Version 47 of ISO15926HowTo_Introduction

Show
Ignore:
Timestamp:
07/06/10 05:44:03 (12 years ago)
Author:
gordonrachar (IP: 142.59.241.43)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ISO15926HowTo_Introduction

    v46 v47  
    9090=== IDS-ADI Project === 
    9191 
    92 In the early 2000s, both FIATECH and POSC Caesar initiated projects to work on digital interoperability.  FIATECH launched the Accelerating the Deployment of ISO 15926 (ADI) project and POSC Caesar launched its Intelligent Data Sets (IDS) project.  The project's names are different, but the work of implementing their respective goals is almost identical.  Fortunately the directors of both organizations quickly saw this and decided to merge the projects into one, calling it the IDS-ADI project. 
     92In the early 2000s, both FIATECH and POSC Caesar initiated projects to work on digital interoperability.  FIATECH launched the Accelerating the Deployment of ISO 15926 (ADI) project and POSC Caesar launched its Intelligent Data Sets (IDS) project.  The project's names are different, but the work of implementing their respective goals had a high degree of overlap.  Fortunately the directors of both organizations quickly saw this and decided to merge the projects into one, calling it the IDS-ADI project. 
    9393 
    9494=== Matrix 123 and Matrix 8 === 
     
    9696In the spring of 2008, a number of sub-projects were commissioned to demonstrate the capabilities of ISO 15926 at the spring 2009 FIATECH conference.  (Perhaps, in a fit of Keno Reeves envy, they were are given Matrix Numbers.)  The two projects that emerged from this effort were Matrix 123 (an amalgamation of Matrix 1, 2, and 3) and Matrix 8. 
    9797 
    98 Matrix 123 was designed to demonstrate a realistic exchange of data between 2D and 3D design systems using the ISO 14926-4 dictionary.  It was quickly renamed "Proteus".  Since this has been used a great many times with real projects, there was never any doubt about its eventual success.  The project demonstrated three data flows; P&ID to P&ID, P&ID to 3D, and 3D to 3D.  Each data flow involved moving information from a number of commercial plant design systems to one such system, mimicking an Owner/Operator consolidating work from several EPCs into one. 
     98Matrix 123 was designed to demonstrate a realistic exchange of data between 2D and 3D design systems using the ISO 14926-4 dictionary.  It was renamed "Proteus" after the Greek diety whose name has become synonomus with "versitile".  Since the underlaying technology had been used a great many times with real projects, there was never any doubt about its eventual success.  The project demonstrated three data flows; P&ID to P&ID, P&ID to 3D, and 3D to 3D.  Each data flow involved moving information from a each of a number of commercial plant design systems to one such system, mimicking an Owner/Operator consolidating work from several EPCs, into one. 
    9999 
    100 Matrix 8, renamed Camelot, was a proof of concept that all parts of ISO 15926 could be used for information transfer.  The data flowed in the demonstrations were nowhere near realistic in terms of payload size, but were realistic in the kinds of information that is exchanged during a typical industrial project. 
     100Matrix 8, renamed Camelot, was a proof of concept using all parts of ISO 15926 for information transfer.  The data flow in the demonstrations were nowhere near realistic in terms of payload size, but were realistic in the kinds of information that is exchanged during a typical industrial project. 
    101101 
    102 During the work on the Camelot project, the participants developed a set of tools and a methodology that could be used to implement ISO 15926.  They gave this methodogy its own name, ''ISO 15926 Realtime Interoperability Network Grid'', or iRING.  It was successful enough that a second project, Avalon, was commissioned to ????? 
     102During the work on the Camelot project, the participants developed a set of tools and a methodology that could be used to implement ISO 15926.  They gave this methodogy its own name, ''ISO 15926 Realtime Interoperability Network Grid'.  The project was sucessful enough that a successor project, named Avalon, was commissioned to set up an infrastructure to enable iRING to continue independent of any one person or organization.  Avalon proposed a method to manage code development, and wrote a business plan, called the "Avalon Service Provision", for funding. 
    103103 
    104  
    105  
    106  
    107  
    108 After successful demonstration at the spring 2008 conference, both projects continued, Proteus under the same name, and Camelot under the name Avalon. 
     104Both iRING and Proteus continue to this day. 
    109105 
    110106=== iRING === 
    111107 
     108The ISO 15926 Realtime Interoperability Network Grid (iRING) is a collection of software and methodology to impliment ISO 15926.  It is open-source, using the BSD3 open source agreement, to anable anyone to use it, extend it, and (preferably) publish the extentions back into the public domain.  The iRING User Group is open for membership to anyone interested, holds regular conference calls, and releases periodic software upgrades. 
    112109 
     110=== Similarities and Differences between iRING and Proteus === 
     111 
     112The similarities and differences between iRING and Proteus are in paylod capacity, preparation require before transer, and the manner in which data is transferred. 
     113 
     114With Proteus, you transfer a large amount of data from a particuarl version of a particular plant design system to a particular version of a different plant design system.  Essentially, you are making a magic decoder ring for each version of each plant design system.  But rather than build a single end-to-end magic decoder ring, you make a magic decoder ring from the first plant design system to the intermediate form of ISO 15926-4 (the dictionary), and another magic decoder ring from ISO 15926-4 to the second plant design system. 
     115 
     116In the typical use case, the objective is to move information from one or more plant design systems to another, within which the work continues.  If there is any ambiguity with a particular data value, humans can look at both plant design systems, determine the meaning, and custom-make the appropriate mapping. 
     117 
     118With iRING, you transer a single value from within one plant design system to the appropriate spot within another plant design system.  The trick here is that you don't have to know (or, more properly, when ISO 15926 is mature you will not have to know) the identity of the plant design system on the other end of the exchange.  To accomplish this, you map your data to the intermediate form of ISO 15926-2 (the class library).  Your counterparty 
    113119 
    114120... 
Home
About PCA
Reference Data Services (RDS)
RDS Operations Support
Meetings and Conferences
ISO 15926
Special Interest Groups
Technical Advisory Board
Norwegian Continental Shelf Std
Projects
Search