An Introduction to ISO 15926 November 2011 - iRINGToday

information has a standard representation, some exchanges can be automated. The following
examples show how ISO 15926 works in realistic project situations.
Project Design
To mitigate the time delay between receiving project documents from an EPC contractor and
getting the relevant information entered into its document control systems and operations
and its maintenance systems, an owner may wish to specify in advance the precise nature of
the data handover. Unless the EPC contractor has worked for the owner previously, there will
be a delay while the EPC configures its engineering systems to comply with data handover
requests—and the costs of doing so will be borne by the owner either explicitly or embedded
into the fees.
When ISO 15926 is mature, this will all change. As soon as the owner determines that the EPC
contractor can hand over the project data following the ISO 15926 protocols, no one will have
to give data handover any more thought. Project participants will be able to simply get on
with design. In addition to not having to spend time negotiating handover up front, any information
exchanges during the project design (Figure 1.16)—such as between EPC contractors
and vendors, between the EPC contractors themselves, and to the owner—will be easier.
Procurement
EPC 1
EPC 2
V
10
ISO 15926
V
11
Owner
Fig 1.16 Information exchanges during design.
On a large capital project, an equipment supplier bidding on the project will receive a great
deal of information with the initial inquiry—which can consist of many books of specifications
and many partially filled-in data sheets. All bidders will have to read everything carefully and
make enough enquiries to verify that all parties agree on the terminology. The successful bid-
CHAPTER 1
32