Changes between Version 14 and Version 15 of ISO15926HowTo_CaseStudy_OEM_1
- Timestamp:
- 12/10/09 05:34:53 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ISO15926HowTo_CaseStudy_OEM_1
v14 v15 1 1 [[TracNav(TracNav/ISO15926HowTo)]] 2 2 3 = Equipm nent Manufacturer Case Study !#1 =3 = Equipment Manufacturer Case Study !#1 = 4 4 5 5 Status of this document: Working Draft … … 18 18 In 2008, The Company launched an internal project to implement ISO 15926. When the project is finished, The Company will be able to communicate directly with the engineering and asset management systems of any customer who uses ISO 15926-enabled tools. 19 19 20 == Bu isness Case ==20 == Business Case == 21 21 22 22 '''Summary''' To make trivial the exchange of information about complex plant instrumentation and services. … … 24 24 At the beginning of a project, a large effort is required to simply agree on terms. The first task of a sales engineer is to read the customer's data sheets and specifications and recommend a model number. But despite many years of experience in the industry, it seems that there is always ambiguity somewhere. This is true regardless of how sophisticated the customer is, or whether the customer is an EPC or an Owner. 25 25 26 One would think that experienced instrumentation engineers would have solved this long ago. For instance, in North America we have the Instrument Society of America which publishes recommended data sheets for almost every kind of instrument that exists. Other countries have similar standards. But most engineers and owners customize the standards for th ier particular situations. The result is that even for simple instruments, the names of attributes are different, or a property or two is missing. So there still has to be a discussion. No one wants to deliver a product and find out that certain terms have been understood differently.26 One would think that experienced instrumentation engineers would have solved this long ago. For instance, in North America we have the Instrument Society of America which publishes recommended data sheets for almost every kind of instrument that exists. Other countries have similar standards. But most engineers and owners customize the standards for their particular situations. The result is that even for simple instruments, the names of attributes are different, or a property or two is missing. So there still has to be a discussion. No one wants to deliver a product and find out that certain terms have been understood differently. 27 27 28 What ISO 15926 brings to the table, then, is a common language for describing the properties of plant equipment. It also brings with it a critical mass of instrument users. Of the organizations world-wide that are sharing the develop ement of ISO 15926, several are large, international EPCs, and several are large, international Owner/Operators. If The Company joined the loose consortium and implemented ISO 15926, there would be a large group of organizations to share information with.28 What ISO 15926 brings to the table, then, is a common language for describing the properties of plant equipment. It also brings with it a critical mass of instrument users. Of the organizations world-wide that are sharing the development of ISO 15926, several are large, international EPCs, and several are large, international Owner/Operators. If The Company joined the loose consortium and implemented ISO 15926, there would be a large group of organizations to share information with. 29 29 30 30 By implementing ISO 15926 the information exchange about instruments would no longer be a major task, but would move to the background. … … 34 34 The Company has already come up with its own list of terms that were associated with each item in its product line. Each term has its own ID number. Using this ID number, information exchanges within the company are much more reliable. But external business partners do not use this terminology and are not likely to adopt it. 35 35 36 One attempt at interoperability was to build software to communicate directly with commer ical 3D design systems. ("Build a Decoder Ring" in the words of the project manager.) But several years and a great deal of money later, they had import/export with exactly one such commercial system. The Company did not want to have build that kind of a "Decoder Ring" for every software vendor. But if they used ISO 15926, they would only have to build one "Decoder Ring."36 One attempt at interoperability was to build software to communicate directly with commercial 3D design systems. ("Build a Decoder Ring" in the words of the project manager.) But several years and a great deal of money later, they had import/export with exactly one such commercial system. The Company did not want to have build that kind of a "Decoder Ring" for every software vendor. But if they used ISO 15926, they would only have to build one "Decoder Ring." 37 37 38 38 === Step Two: Map Internal Terms to ISO 15926 ===
