Changes between Version 48 and Version 49 of ISO15926HowTo_Introduction

Timestamp:

07/06/10 06:22:18 (14 years ago)

Author:

gordonrachar (IP: 142.59.241.43)

Comment:

--

ISO15926HowTo_Introduction

@@ -96 +96 @@
 In 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.
 
-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 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.
+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 renamed "Proteus" after the Greek deity whose name has become synonymous with "versatile".  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.
 
 Matrix 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.
 
-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'.  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.
+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'.  The project was successful 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.
 
 Both iRING and Proteus continue to this day.
@@ -106 +106 @@
 === iRING ===
 
-The 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.
+The ISO 15926 Realtime Interoperability Network Grid (iRING) is a collection of software and methodology to implement ISO 15926.  It is open-source, using the BSD3 open source agreement, to enable anyone to use it, extend it, and (preferably) publish the extensions 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.
 
 == Similarities and Differences between iRING and Proteus ==
 
-The similarities and differences between iRING and Proteus are in paylod capacity, preparation require before transer, and the manner in which data is transferred.
+The similarities and differences between iRING and Proteus are in payload capacity, preparation require before transfer, and the manner in which data is transferred.
 
-With 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.
+With Proteus, you transfer a large amount of data from a particular 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.
 
 In 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.
 
-With iRING, you transfer a single value from within one plant design system to the appropriate spot within another plant design system.  (And then do it again for another data value.)  The trick here is that you don't 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 does the same thing, and the iRING software matches up the classes.  Of course both of you have to be careful how you each characterize your own data so that it will not be misunderstood.  This is where you use the other parts of ISO 15926 to get the information modeled properly.
+With iRING, you transfer a single value from within one plant design system to the appropriate spot within another plant design system.  (And then do it again for another data value.)  The trick here is that you don't 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 counter party does the same thing, and the iRING software matches up the classes.  Of course both of you have to be careful how you each characterize your own data so that it will not be misunderstood.  This is where you use the other parts of ISO 15926 to get the information modeled properly.
 
 === Metaphor:  Humanitarian Aid to Haiti After an Earthquake ===
 
-The Proteus approach to sending aid to Haiti is to load up some C-17 heavy transport aircraft with all manner of food and materiel and drop it all off in Port au Prince.  Oh Wait!  Port au Prince doesn't have a large enough airstrip.  No Problem!  We'll build one!  After the crisis is over the Hatians will have really big parking lot, but that's OK.
+The Proteus approach to sending aid to Haiti is to load up some C-17 heavy transport aircraft with all manner of food and materiel and drop it all off in Port au Prince.  Oh Wait!  Port au Prince doesn't have a large enough airstrip.  No Problem!  We'll build one!  After the crisis is over the Haitians will have really big parking lot, but that's OK.
 
-The iRING approach is for for every family in the world to be able to send $5.00 from their own bank account directly to the bank account of an Haitian family.  Oh Wait!  We don't have the banking infrastructure to allow a family at a random place in the world to direct money to the bank account of an Haitian family.  No Problem!  We'll make one!  And afterwards we will be able to use the banking infrastructure for other things.
+The iRING approach is for every family in the world to be able to send $5.00 from their own bank account directly to the bank account of an Haitian family.  Oh Wait!  We don't have the banking infrastructure to allow a family at a random place in the world to direct money to the bank account of an Haitian family.  No Problem!  We'll make one!  And afterwards we will be able to use the banking infrastructure for other things.
 
 === Further Development of Proteus ===
@@ -130 +130 @@
 === Further Development of iRINg ===
 
-Currenty there are two issues facing the iRING approach.  The first is a lack of tools that are easy enough to use that a critical mass of industry playser will indeed use them.  The iRING user group is working diligently to solve this.  The second is the lack of a sufficiently large reference ddata library a dn a common mehodology of user.
+Currently there are two issues facing the iRING approach.  The first is a lack of tools that are easy enough to use that a critical mass of industry players will indeed use them.  The iRING user group is working diligently to solve this.  The second is the lack of a sufficiently large reference data library and a common methodology of user.
 
-Que JORD.
+Queue JORD.
 
 === Joint Operational Reference Data ===
 
-The Joint Operational Reference Data project has just been commissioned by FIATECH and POSC Caesar.  As this is being written, in the late spring of 2010, the foundins being sorted out.
+The Joint Operational Reference Data project has just been commissioned by FIATECH and POSC Caesar.  As this is being written, in the late spring of 2010, the funding is being sorted out.
 
 
 == So Where Do I Start? ==
 
-Let's go back to the orgifinal lsit of scenarios
+Let's go back to the original list of scenarios
 
-1.  If you want to convert a large mass of infromation from one plant design system to another, you are looking for a Proteus solution.  This is an extremely specialized task.  The good news is thqat you don't even need to know how to spell ISO 15926.  An entire supbgroup of contracters and consultatnst are ready to server you.  Search for "XMpLant" and "Proteus".  You seill see a bunch of names poping up over and over.  Call one of them.
+1.  If you want to convert a large mass of information from one plant design system to another, you are looking for a Proteus solution.  This is an extremely specialized task.  The good news is that you don't even need to know how to spell ISO 15926.  An entire subgroup of contractors and consultants are ready to server you.  Search for "XMpLant" and "Proteus".  You will see a bunch of names popping up over and over.  Call one of them.
 
-2, etc.  For the rest you you, some work will be required.  The best first step is to join FIATECH or POSC Caesar.  You will immediatly be part of a gropu of like-kminded organizations and individuals.  At the current stage of developement of ISO 15926, most of the players have a vested intereset in helping others.  once the adoption fo the standard has hit a critcial mass, many will turn back into competiroers.
+2, etc.  For the rest you , some work will be required.  The best first step is to join FIATECH or POSC Caesar.  You will immediately be part of a group of like-minded organizations and individuals.  At the current stage of development of ISO 15926, most of the players have a vested interest in helping others.  once the adoption of the standard has hit a critical mass, many will turn back into competitors.
 
-If you live in a ligigius cultery there is another benefit of joining one of these organizations.  Weh you talk to a competorr you are alowasy at some risk of contravening anti trust legistlation.  but if you discussion (with peopel who work for a competitor) is under the umbrell of an industry standards organization you are protected.
+If you live in a litigious culture there is another benefit of joining one of these organizations.  When you talk to a competitor you are always at some risk of contravening anti trust legislation.  but if you discussion (with people who work for a competitor) is under the umbrella of an industry standards organization you are protected.
 
-The best second step is to activly joing the iRING Users Group with the intent of contributing.  This will give you a very good understanding of thwat is involved, and the attention of people that can help.
+The best second step is to actively join the iRING Users Group with the intent of contributing.  This will give you a very good understanding of what is involved, and the attention of people that can help.
 
-The rest of this works is devoeted to filling in the blanks
+The rest of this works is devoted to filling in the blanks
 
-1.  Learngin Resources
+1.  Learning Resources
 
 2.  Case Studies
@@ -167 +167 @@
 ...
 
-
-=== Joint Operational Reference Data - JORD ===
-
-...
-
-
 ...