Changes between Version 44 and Version 45 of ISO15926HowTo_Introduction
- Timestamp:
- 07/02/10 05:23:45 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ISO15926HowTo_Introduction
v44 v45 35 35 There could be a number of different reasons for wanting to know how to implement ISO 15926: 36 36 37 1. Perhaps you have some interest in an industrial plant under development, and would like to convert the 3D models that you will eventually rec ieve from the consortium of EPCs, to one particular plant design system with which you will maintain the plant. You would like to do this efficiently as possible without having to "reinvent the wheel", so to speak, and have heard that ISO 15926 can help you do this.37 1. Perhaps you have some interest in an industrial plant under development, and would like to convert the 3D models that you will eventually receive from the consortium of EPCs, to one particular plant design system with which you will maintain the plant. You would like to do this efficiently as possible without having to "reinvent the wheel", so to speak, and have heard that ISO 15926 can help you do this. 38 38 39 39 2. Perhaps you are caught in the middle, between many other players in the plant design industry, and constantly have to remind yourself to ask "what do you mean by this?", even for simple terms. You would like a common way of describing plant objects that removes the ambiguity, and have heard that ISO 15926 does that. … … 84 84 === XMpLant === 85 85 86 In the early 1990s, some Owner/Operators started seeing that some of the mass of information created by EBCs during the design and construc ion of a new facility would be a useful foundation to the information requried to operate and maintain the plant. One option was to take delivery of the EPC's plant design systems. But a fundamental problem is that while there is overlap between an engineer and an operator, thier needs are different; software systems that do a good job of design generally lack key abilities for operations. What was needed was a way to seed the maintenance systems with certain of the information from the EPC without having to rekey it.86 In the early 1990s, some Owner/Operators started seeing that some of the mass of information created by EBCs during the design and construction of a new facility would be a useful foundation to the information required to operate and maintain the plant. One option was to take delivery of the EPC's plant design systems. But a fundamental problem is that while there is overlap between an engineer and an operator, their needs are different; software systems that do a good job of design generally lack key abilities for operations. What was needed was a way to seed the maintenance systems with certain of the information from the EPC without having to rekey it. 87 87 88 88 There are probably as many options here as there are projects, but a key step in all of the options is to develop a data "framework", or "schema", on which to "hang" the data. Developing such a schema is anything but trivial. Many of the early players started to adopt ISO 15926-4 as the data dictionary. One such schema was released into the public domain in the late 1990s under the name XMpLant. Since that time, XMpLant has been used in over 80 projects to convert plant information from one plant design system to another one. … … 90 90 === IDS-ADI Project === 91 91 92 In the early 2000s, both FIATECH and POSC Caeser initiated projects to work on digital interoperatbility. FIATECH launched the Accellerating the Deployment of ISO 15926 (ADI) project and POSC Caesar launched its Intelligent Data Sets (IDS) project. Although the project's names are different, when it came to implementing them, the directors of both organizations quickly saw that there was a very close overlap with both, and decided to merge the projects into one, now called IDS-ADI. 92 In the early 2000s, both FIATECH and POSC Caesar initiated projects to work on digital interoperability. FIATECH launched the Accelerating the Deployment of ISO 15926 (ADI) project and POSC Caesar launched its Intelligent Data Sets (IDS) project. The project's names are different, but the work of implementing their respective goals is almost identical. Fortunately the directors of both organizations quickly saw this and decided to merge the projects into one, calling it the IDS-ADI project. 93 94 In the spring of 2008, a number of sub-projects were commissioned to demonstrate the capabilities of ISO 15926 at the spring 2009 FIATECH conference. (Perhaps, in a fit of Keno Reeves envy, they were are given Matrix Numbers.) The two projects that emerged from this effort were Matrix 123 (an amalgamation of Matrix 1, 2, and 3) and Matrix 8. 95 96 Matrix 123 was designed to demonstrate a realistic exchange of data between 2D and 3D design systems using the ISO 14926-4 dictionary. It was quickly renamed "Proteus". Since this has been used a great many times with real projects, there was never any doubt about its eventual success. The project demonstrated three data flows; P&ID to P&ID, P&ID to 3D, and 3D to 3D. Each data flow involved moving information from a number of commercial plant design systems to one such system, mimicking an Owner/Operator consolidating work from several EPCs into one. 97 98 Matrix 8, renamed Camelot, was a proof of concept that all parts of ISO 15926 could be used for information transfer. The data flowed in the demonstration were nowhere near realistic in terms of payload size, but were realistic in the kinds of information exchanged. 99 100 After successful demonstration at the spring 2008 conference, both projects continues, Proteus under the same name, and Camelot under the name Avalon. 101 102 === iRING === 93 103 94 104 95 105 96 ... 106 between a number of commercial plant design systems. 107 108 In the spring of 2008 a number of sub-projects were commissioned by the directors of IDS-ADI to demonstrate the 109 110 === Matrix 123 and Matrix 8 === 97 111 98 112 99 ...100 101 102 === Matrix 123 and Matrix 8 ===103 113 104 114 ...
