Changes between Version 7 and Version 8 of ISO15926Primer_How_Actually

Show
Ignore:
Timestamp:
11/22/11 05:17:58 (12 years ago)
Author:
gordonrachar (IP: 75.156.216.35)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ISO15926Primer_How_Actually

    v7 v8  
    99[[Image(ISO15926Primer_12_How_Actually_a.png, 600px)]] 
    1010 
    11 For instance, the Engineer who specifies the pump is concerned first about its capacity, and whether or not the material is appropriate to the service, and then about it’s physical envelope dimensions and weight. 
     11For instance: 
    1212 
    13 The Constructor is also interested in weight, but only marginally interested in it’s physical dimensions (at least until something doesn’t fit). But it is very interested in delivery schedule. 
     13  * The Engineer who specifies the pump is concerned first about its capacity, and whether or not the material is appropriate to the service, and then about it’s physical envelope dimensions and weight. 
    1414 
    15 The purchasing agent is professionally interested that all of the engineer’s requirements are met in whatever is purchased, but treats the property values, more-or-less as text strings.  For instance the tag number 32-P-101A is treated as a single text string including the dashes, but the engineer wants to deal with all the individual pieces (Plant 32, Equipment type “P”, Sequence number 101, Spare “A”). 
     15  * The Constructor is also interested in weight, but only marginally interested in it’s physical dimensions (at least until something doesn’t fit). But it is very interested in delivery schedule. 
    1616 
    17 The manufacturer is interested in dimensions, but to a far greater level of precision, as well as the precise chemical composition of the material. 
     17  * The purchasing agent is professionally interested that all of the engineer’s requirements are met in whatever is purchased, but treats the property values, more-or-less as text strings.  For instance the tag number 32-P-101A is treated as a single text string including the dashes, but the engineer wants to deal with all the individual pieces (Plant 32, Equipment type “P”, Sequence number 101, Spare “A”). 
    1818 
    19 Standards and regulatory bodies are interested in things that will make the pump blow up and kill people. This includes physical properties, but they want different levels of detail. 
     19  * The manufacturer is interested in dimensions, but to a far greater level of precision, as well as the precise chemical composition of the material. 
    2020 
    21 The Owner-Operator is marginally interested in the physical properties (after all, the pump is there, and it is operating), but is more interested in maintenance schedules and the availability of spare parts. 
     21  * Standards and regulatory bodies are interested in things that will make the pump blow up and kill people. This includes physical properties, but they want different levels of detail. 
    2222 
    23 All of these differences are reflected in different data structures with subtle differences in meaning of even common terms. 
     23  * The Owner-Operator is marginally interested in the physical properties (after all, the pump is there, and it is operating), but is more interested in maintenance schedules and the availability of spare parts. 
    2424 
    25  
    26  
    27  
    28  
    29 As a result, making the software of all the participants communicate is like trying to pound square pegs into round holes, except that in this case there are many different shapes of pegs and many different shapes of holes. It is certainly possible to make the software communicate (an in fact many professionals make a good living doing just that) but it is costly and time-consuming. 
     25All of these differences are reflected in different data structures with subtle differences in meaning of even common terms. As a result, making the software of all the participants communicate is like trying to pound square pegs into round holes, except that in this case there are many different shapes of pegs and many different shapes of holes. It is certainly possible to make the software communicate (an in fact many professionals make a good living doing just that) but it is costly and time-consuming. 
    3026 
    3127In the ''Introduction to ISO 15926'' we give an example of two engineers, each working for a different organization, and who wish to exchange some information but cannot easily do so because their respective systems were designed with different purposes in mind. 
Home
About PCA
Reference Data Services
Projects
Workgroups