Changes between Version 9 and Version 10 of ISO15926Primer_Benefits_Software

Show
Ignore:
Timestamp:
11/16/11 05:23:35 (11 years ago)
Author:
gordonrachar (IP: 75.156.216.35)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ISO15926Primer_Benefits_Software

    v9 v10  
    33= ISO 15926 Benefits for Software Vendors and Service Providers = 
    44 
    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. 
    76 
    8 For software vendors, the benefits of ISO 15926 come from three factors: 
     7This page is out of date and has been depricated. 
    98 
    10  * ISO 15926 is a single standard to support. 
    11  * ISO 15926 data models and templates already exist and are open source. 
    12  * ISO 15926 is extensible. 
     9If you reached this page from a link in another web page please inform the webmaster. 
    1310 
    14 In addition, when ISO 15926 is mature, it will be easier for niche software to find a market because acquiring plant data will be easier. 
     11For a peek at the new book and instructions on how to download a copy please follow this link. 
    1512 
    16 ---- 
    17 == A Single Standard to Support == 
    18  
    19 Currently, plant design software has no industry-wide standard for interoperation.  This means that when information needs to be transferred between applications, some method must be developed from scratch, taking care to preserve the meaning of all the data values. 
    20  
    21 This is true even for applications within one vendor's portfolio.  Applications may have been developed over different time periods, or acquired from other vendors.  With no industry-wide standard for exchanging information, point-to-point data exchanges are often the only alternative, leading to a Confederation of Applications joined by custom maps.  But a network of point-to-point data maps are just as difficult to maintain for a software vendor as for any other organization. 
    22  
    23 But if the software developer instead adopts ISO 15926 as the protocol for transferring information, the individual applications are encapsulated, or decoupled from the System Landscape.  Each application can be updated on its own schedule without impacting any other application. 
    24  
    25 == Benefit:  ISO 15926 Already Exists == 
    26  
    27 Developing a data model for plant applications is not a trivial matter.  If improperly designed, the data model can constrain the utility of the eventual software.   But the data model and templates for ISO 15926 are already developed, and since they are open source can be used without incurring royalties and without legal risk. 
    28  
    29 By using the data model and templates for ISO 15926, software vendors save themselves a great deal of work.  Instead of having to develop a data model, developers can work on other, more value-added, parts of the software. 
    30  
    31 === ISO 15926 is a Robust Data Model === 
    32  
    33 Developing an object information model for modern plant equipment requires a strong knowledge of the equipment domain as well as a high level of data modeling expertise.  The ISO 15926 data model has been developed by professionals from many industries worldwide.  By using the ISO 15926 data model, a software vendor can leverage this work without having to duplicate it at its own expense. 
    34  
    35 Traditional methodology tends to optimize the cost of the initial development, at the expense of greater cost to implement future enhancements, and greater cost of maintenance.  This translates to a shorter application lifetime.  But by using the ISO 15926 data models, the software will be more robust and have a longer lifetime serving a larger clientele. 
    36  
    37  
    38 === ISO 15926 Can be Extended === 
    39  
    40 The ISO 15926 data model is written to be extensible.  Anyone with proper training can add new reference data that can be simply made public, or can be contributed back to the standard.  Changes and additions that are simply made public do not require a lengthy review period, but are available almost immediately.  This means that ISO 15926 can be adapted quickly for a particular integration project, without compromising the standard, or the portability of the data. 
    41  
    42  
    43 == Market for Niche Applications == 
    44  
    45 When ISO 15926 becomes mainstream, it will be easier to implement software that requires a large amount of plant data.  Currently, developers of this kind of software would have to spend considerable effort to import the plant data.  With no industry standard, the software developer will have to deal with every unique plant. 
    46  
    47 All this means that the threshold for this kind of software is quite high. 
    48  
    49 But if an Owner/Operator exposed its plant configuration with an ISO 15926 façade, pulling information into the software would be trivial. 
    50  
    51  
    52 === Next === 
    53  
    54   * [wiki:ISO15926Primer_History Primer: History of ISO 15926] 
    55  
    56 ---- 
     13  * [wiki:ISO15926Primer An Introduction to ISO 15926] 
Home
About PCA
Reference Data Services
Projects