Changes between Version 12 and Version 13 of ISO15926Primer_GettingStarted_Organization

11/20/11 03:45:11 (12 years ago)
gordonrachar (IP:



  • ISO15926Primer_GettingStarted_Organization

    v12 v13  
    33= Implementing ISO 15926 in an Organization = 
    5 ---- 
    6 [[PageOutline(2-4,Contents,inline)]] 
     5The '''ISO 15926 Primer''' has been replaced with '''An Introduction to ISO 15926''', a free download from Fiatech. 
    8 == Abstract == 
     7This page is out of date and has been deprecated. 
    10 The actual steps an organization takes to implement ISO 15926 will depend on what exactly it wants to achieve.  However, there are some common steps: 
     9If you reached this page from a link in another web page please inform the webmaster. 
    12   * Join FIATECH or POSC/Caesar[[BR]] 
    13     - A good way to get some help. 
     11For a peek at the new book and instructions on how to download a copy please follow this link. 
    15   * Map Your System Landscape[[BR]] 
    16     - Know where you are. 
    18   * Build a Business Case[[BR]] 
    19     - Know where you are going. 
    21 ---- 
    23 == Join FIATECH or POSC/Caesar - Get Involved in a Project == 
    25 ISO 15926 is a different approach to exchanging information between applications.  In the past, when we've linked two applications, we've always tried to know as much as we can about the applications.  But with ISO 15926, linking applications by exploiting this special knowledge is actually a liability.  For most of us, this is something we have to un-learn. 
    27 Fortunately there are others that can hep you.  A good place to find them will be to join FIATECH or POSC/Caesar.  ISO 15926 is being developed right now.  The developers are accessible.  If you join, there will be people to assist you getting up to speed.  Along with getting help, you may end up helping others, too.  This is a good thing. 
    29 Outside of working on ISO 15926, many of us are competitors.  The natural tendency, then, is to horde information.  But if we cooperate, interoperability of information gets easier, projects become easier, and as projects become easier and cheaper, the owners (who in the end, pay for everything) will be able to do more.  The pie gets bigger. 
    31   * [ POSC Caesar Membership] 
    33   * [ FIATECH Membership] 
    35 === Make a Map of Your System Landscape === 
    37 You will need to know all the individual software applications your organization uses, where they get their input from, and where their output goes.  Show all of the information exchanges.  Your most important applications will probably already be mapped together either with custom programming or commercial middleware.  Other information exchanges might be made with manual keyin every time, exchange files in a neutral format, or perhaps ad hoc software.  Show all of them, even if they seem to be working properly. 
    39 === Gather Application Information === 
    41 Dig into each application and understand the information it deals with. 
    43   * Document the schema - catalogue what's there. 
    44   * Uncover any special requirements.  For instance, uncover any relationships that have to be maintained. 
    45   * Understand what all the data items ''mean''.  Look for implied attributes.  For instance, if an application was written for an organization that always used Imperial units of measurement, the original developer many not have thought to explicitly store Fahrenheit as the units of temperature measurement. 
    47 You may not have to catalogue ''every'' data item in all of your applications but you do need to know everything about the information movements that you want to automate. 
    49 === Some Example Scenarios === 
    51 Here are some examples to help you look for an opportunity to improve an information exchange by using ISO 15926.  Preferably, the entire information exchange should be within your organization, as opposed to automating an exchange with a business partner.  Choose something simple to start with if you have a choice. 
    53 The first three examples involve mapping applications together using ISO 15926 Part 4 (ISO 1596-4): 
    55  * [wiki:ISO15926Primer_GettingStarted_Automate Primer: Automate a Manual Exchange] 
    57  * [wiki:ISO15926Primer_GettingStarted_Encapsulate Primer: Encapsulate an Application] 
    59  * [wiki:ISO15926Primer_GettingStarted_Decouple Primer: Decouple an Application from a Confederation of Applications] 
    61 The fourth example involves working with an external organization: 
    63  * [wiki:ISO15926Primer_GettingStarted_Partner Primer: Expose Information to a Business Partner] 
    65 == Build a Business Case == 
    67 The very first line in this Primer explains why we need ISO 15926: 
    69   ''So we can exchange complex plant and project information easier and cheaper.'' 
    71 So if ISO 15926 actually accomplishes this, it shouldn't be too difficult to build a business case.  Here are some ideas: 
    73  * Look at your system landscape. 
    74    * Which applications are linked? 
    75    * What could you do differently if more of them, or all of them, were able to exchange information easily? 
    77  * What does it cost your organization to maintain the existing links between applications? 
    79  * Is your organization forgoing opportunities to upgrade individual applications because doing so may break links to other applications? 
    81 All of these questions lead to justification to implement ISO 15926.  Basically, you are counting the cost, in both financial and business efficiency terms, of the status quo.  You will likely end up with something in one of the following categories: 
    83  * Increase Reliability - For instance, if your current method of interoperability requires manually rekeying information between applications, you can map your applications to ISO 15926-4 so they will be able to exchange information automatically. 
    85  * Saving Money - For instance, if you have to repeatedly map one application to other applications.  If you use ISO 15926 you only have to map it once (more). 
    87  * Saving Time - For instance, if you repeatedly have to map applications to other, external, applications in a short period of time.  If you map to ISO 15926, the application will be ready to exchange information with any other ISO 15926-compliant application. 
    89  * Reduce Maintenance - For instance, if you currently use custom maps to move information between applications and you have to continually revise the maps because of version changes in the linked application software.  If, instead, you map each application to ISO 15926-4 and the application changes, you will only have to revise the map to ISO 15926-4, none of the other maps will have to change. 
    91  * Interoperability of Internal Applications - For instance, if your organization runs many proprietary applications that have to talk to each other, instead of mapping each of them together one pair at a time, map each to ISO 15926. 
    93  * Experience - For instance, if you anticipate having to implement ISO 15926 in the future, you can do a small project to map two applications together using ISO 15926-4.  You will learn enough to be able to judge the impact of implementing ISO 15926 on a larger scale. 
    95 == Next == 
    97   * [wiki:ISO15926Primer_GettingStarted_Automate Primer: Automate a Manual Exchange] 
    98   * [wiki:ISO15926Primer_GettingStarted_Encapsulate Primer: Encapsulate an Application] 
    99   * [wiki:ISO15926Primer_GettingStarted_Decouple Primer: Decouple an Application from a Confederation of Applications] 
    100   * [wiki:ISO15926Primer_GettingStarted_Partner Primer: Expose Information to a Business Partner] 
    102   * [wiki:ISO15926Primer_GettingStarted_OtherIdeas Primer: Other Ideas for Getting Started] 
    104 ---- 
     13  * [wiki:ISO15926Primer An Introduction to ISO 15926] 
About PCA
Reference Data Services