Changes between Version 136 and Version 137 of ISO15926Primer_OtherResources

Timestamp:

12/29/11 01:27:46 (12 years ago)

Author:

gordonrachar (IP: 75.156.216.35)

Comment:

--

ISO15926Primer_OtherResources

@@ -174 +174 @@
 One of the major motivations of organizations to sponsor the work that has led to ISO 15926, and the motivations of individuals to participate, is the efficient handover of information from engineering procurement and construction (EPC)  contractors and constructors to owner-operators. After a facility has been built and commissioned, document and information handover must often operate on what is left of the project budget after the original engineering and construction staff have moved on to their next project. It is sometimes difficult for the owner to get all of the information it needs, and in a form that is immediately useful.
 
-One barrier to adequate information handover in the capital projects industry is getting all parties to agree at the beginning of a project what needs to be handed over. So that every project does not have to develop its handover requirements from scratch, a number of handover guides have been created, and more are contemplated. We have come to refer to the discussion of information handover guides as the The Business Interfaces Definition Guide (BIDG).
+One barrier to adequate information handover in the capital projects industry is getting all parties to agree at the beginning of a project what needs to be handed over. So that every project does not have to develop its handover requirements from scratch, a number of handover guides have been created, and more are contemplated. We have come to refer to the discussion of information handover guides as the ''The Business Interfaces Definition Guide'' (BIDG).
 The handover guides developed to date all discuss the importance of good data handover and offer ways of ensuring that this will actually happen on a given project. One of them, published by EPISTLE, explicitly lists deliverables by name and is organized by engineering discipline. One barrier to getting more specific is a common definition of terms. When the JORD project is complete, many of the participants in the development of these handover guides anticipate a harmonization with Part 4.
 
@@ -181 +181 @@
 In the late 1990s at EPISTLE, the first Process Industries Data Handover Guide was published to help project participants define the scope of information turnover. The guide is issued in two parts. Part 1 concentrates on methodology, starting with understanding the business need for information, creating a plan to supply the information, and implementation. Part 2 focuses on recommendations for actual data items ranging from contract management documents, scheduling, materials, construction, and process to information on all of the components that make up the facility.
 
-As its basis, the EPISTLE handover guide used the PISTEP Process Plant Engineering Activity Model (see Chapter 2). This activity model was essentially a very detailed flowchart of the main activities and information exchanges encountered over the life of a typical process plant. EPISTLE used the activity model to make sure its guide captured the most important exchanges. If you are ever involved in planning the information handover for a capital project, EPISTLE’s guides are still worth reading - along with the NIST and EPRI guides.
+As its basis, the EPISTLE handover guide used the PISTEP Process Plant Engineering Activity Model (see Chapter 2 of ''An Introduction to ISO 15926''). This activity model was essentially a very detailed flowchart of the main activities and information exchanges encountered over the life of a typical process plant. EPISTLE used the activity model to make sure its guide captured the most important exchanges. If you are ever involved in planning the information handover for a capital project, EPISTLE’s guides are still worth reading - along with the NIST and EPRI guides.
 
 At the bottom of this page you will see two attachments: