Changes between Version 47 and Version 48 of ISO15926HowTo_Introduction

Timestamp:

07/06/10 06:15:38 (14 years ago)

Author:

gordonrachar (IP: 142.59.241.43)

Comment:

--

ISO15926HowTo_Introduction

@@ -108 +108 @@
 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.
 
-=== Similarities and Differences between iRING and Proteus ===
+== 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.
@@ -116 +116 @@
 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 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
+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.
 
-...
+=== 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 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.
+
+=== Further Development of Proteus ===
+
+Although the Proteus approach has only been used for a one-time, one-way, large data transfer, there is a demand for two-way transfer on a more regular basis.  The typical scenario is a large facility designed by many EPCs, where each EPC needs to see the work of others, and where the owner wants to take delivery of each EPC's work.  Currently, the only way to accomplish this is to choose one plant design system, and ensure that it is implemented in exactly the same way in each EPC.  The Proteus approach is have enough magic decoder rings, or the facility to build new ones quickly, that each EPC can transfer information to any of the other project partners.
+
+=== 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.
+
+Que 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.
+
+
+== So Where Do I Start? ==
+
+Let's go back to the orgifinal lsit 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.
+
+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.
+
+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.
+
+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 rest of this works is devoeted to filling in the blanks
+
+1.  Learngin Resources
+
+2.  Case Studies
+
+3.  Interoperability Theory
+
+4.  Public tools and how to use them
+
+5.  Database Mapping Techniques
+