SP 1131 Rv.7

Petroleum Development Oman L.L.C.
Plant Lifecycle Information Plan

(Handover and As-Built Documentation)
Document ID SP-1131
Document Type Specification
Security Restricted
Discipline Project Engineering
Owner UEA
Issue Date November 2020
Revision 7.0
This document is the property of Petroleum Development Oman, LLC. Neither the whole nor any part of this document
may be disclosed to others or reproduced, stored in a retrieval system, or transmitted in any form by any means
(electronic, mechanical, reprographic recording or otherwise) without prior written consent of the owner.
Petroleum Development Oman LLC Revision: 7.0
Effective: Nov-2020
I Authorized For Issue – November 2020
Page 2 SP-1131: Plant Lifecycle Information Plan (Handover and As-Built Documentation) Printed: Nov 2, 2020
The controlled version of this CMF Document resides online in Livelink®. Printed copies are UNCONTROLLED.
Effective: Nov-2020
II Revision History
The following are brief revision summary of this document. Details of all revisions prior to these
are held on file by the issuing department.
Revision Date Originator Checker Reviewers Scope /

No. Remarks
Revision 7.0 Oct-20 Lawati, Muna UOP21; PDRN2; Updated to
UOI411 PDRN7; UOP41; incorporate
Al Zaabi, Amal UOI Delivery Leads PDRG2; UOI412; Dependency
UOI414 UOI33; UEI11; Matrix, MRB,
Kingsley Chime UEC12;UEMP1; POM and EORD
UEOI41 UOP6; UEFM1; delivery
UEE31; UEAA; requirements
UEV4; UEP1
Revision 6.0 Apr-18 Kingsley Chime Maulana, Andre CTP34 Brockman, Anna Updated to
UEOI41 Chukwuma, Chinonso UOP21; incorporate
UEOI12 Patrick Liesker outcome of FRD2,
Morowei, Ebikpogba UEP5; Bulushi, address EORD
UEOI23 Yousuf UOI1; delivery, Tier1
Parthasarathy, Yahyaee, Ali UOI2; Dependency
Veeraraghavan UEOI14 Campbell, Ian Matrix and PLIP
Mistry, Daxesh UEOI13 UOP6 doctype
Paramasivan, Suresh rationalization
Kumar UEOI15
Patel, Amitkumar UEOI46;
Bhayani, Kaushikkumar
UEOI43; Lawatia, Ali
UEOI11
Effective: Nov-2020
TABLE OF CONTENT
I Authorized For Issue – November 2020............................................................................ 2
II Revision History ................................................................................................................... 3
1 NTRODUCTION ............................................................................................................................. 6
1.1 Purpose ................................................................................................................................... 6
1.2 Changes to this Specification ......................................................................................... 6
1.3 Step-out Approval ................................................................................................................ 6
1.4 Scope ....................................................................................................................................... 6
1.5 Definitions ............................................................................................................................... 7
1.6 Abbreviations ......................................................................................................................... 7
1.7 Related CMF Business Control Documents ............................................................. 8
2 GENERAL REQUIREMENT ...................................................................................................... 9
3 PROJECT HANDOVER DELIVERABLES REQUIREMENT ......................................10
3.1 Master Information Deliverables ..................................................................................10
3.2 Critical Documents & Data .............................................................................................10
3.3 Manufacturers (Vendor) Record Book (MRB) ........................................................10
3.4 Plant Operating Manual ..................................................................................................12
3.5 Completion Dossiers ........................................................................................................13
3.6 Project Change Control ...................................................................................................14
3.7 Document Classification .................................................................................................14
3.8 Information Storage and Archiving .............................................................................14
3.9 Master Information Retrieval and Control ................................................................14
3.10 Pre-Start-up Audit (PSUA) Documentation .............................................................14
3.11 As-Building and TA Approval ........................................................................................14
3.12 Quality Assurance .............................................................................................................15
3.13 IM Kick-off Form .................................................................................................................15
3.14 Engineering and Operations Reference Document (EORD) ...........................15
3.15 Early Tie-in/Scope Handover ........................................................................................15
3.16 Critical Documentation Modification Dependency ................................................16
4 ROLES AND RESPONSIBILITIES.......................................................................................... 5
4.1 Project Engineer/Manager ............................................................................................... 5
4.2 Project Discipline Engineer .............................................................................................. 5
4.3 IM Delivery Lead .................................................................................................................. 5
4.4 Contractor ............................................................................................................................... 5
5 PLIP TEMPLATE DESCRIPTION ........................................................................................... 3
6 NAMES OF DISCIPLINE SUPPORT ENGINEER ............................................................ 6
7 APPENDICES .................................................................................................................................. 8
7.1 APPENDIX 1: Plant Lifecycle Information Plan (PLIP Template) .................... 8
7.2 Appendix 2: MRB Document Type Handover Format Definition ...................... 8
7.3 Appendix 3: IM Kick-off Form ......................................................................................... 8
7.4 Appendix 4: User Feedback Form ................................................................................ 8
7.5 Appendix 5: MRB Document/Drawing Hanover ...................................................... 8
7.6 Appendix 6: MRB File Handover Template ............................................................... 8
Effective: Nov-2020
7.7 Appendix 7: MRB Quality Check List (QC) ............................................................... 8

7.8 Appendix 8: MRB Delivery SOP .................................................................................... 8
Effective: Nov-2020
1 NTRODUCTION
Project records, documents, drawings and business process data (for CIMS, SAP, EDW, etc), are critical
to safe Operation and Maintenance of PDO’s Assets. This document brings the deliverable requirements
for Asset Lifecycle Information Management into one place. It is applicable for all PDO assets and
projects no matter which contracting strategy is pursued.
The Plant Lifecycle Information Plan (PLIP) is the standard PDO document reference library that
describes ‘What’ information shall be developed by a project and their distribution. It contains generic
listing of Information deliverables requirements (drawing, data, records and documents) to be developed
during project, and which to be handed over to support Operations. It provides means of ensuring
deliverables completeness of all Critical Documentation that are essential for Asset Operations lifecycle
as required in CP-115.
1.1 Purpose
Every new or modified Asset will either produce new information deliverables or modify existing ones.
The purpose of this specification is to specify information requirements (records, drawings, business
process data and documents), that may be developed or modified and delivered at the end of a project.
It shall be used to set project deliverable expectation in SELECT (Basis for Design), DEFINE (FEED),
EXECUTE (Detailed Design and Construction) and OPERATE (modifications) phases.
The PCAP (DCAF) deliverables requirement is mapped in the PLIP so that it serves as the primary
source of information deliverables that shall be scaled by the project delivery team to produce a project
specific DDR.
This requirements is aligned with DEP 82.00.10.30-Gen: Engineering Information Specification (EIS),
section 3.3 Classification of Documents.
1.2 Changes to this Specification
The Owner of this document is the CFDH, Engineering and Operations Data Management and the
custodian is the Head of Business Improvement (UOI4). Users of this Document who identify inaccuracy
or ambiguity should utilize the “User Feedback Page” provided in the Appendix 4 to notify the Custodian
or his/her delegate, and request changes be initiated.
1.3 Step-out Approval
Should compliance be considered inappropriate, then step out approval must be obtained from the
Document Custodian in accordance with approved Change Control system prior to any changes or
activities associated with the specification being carried out.
1.4 Scope
The reference Information set contained in appendix 1 is a generic list of Information requirements from
which a project specific DDR shall be developed. The PLIP template readily filters into PDO deliverables
distribution requirement (DDM), final handover deliverables, and Critical Documentation requirement
(required for Operating Integrity).
All Operations activities that change the plant shall also modify corresponding Information in line with the
modification Dependency Matrix of section 3.15 to reflect the change. The "default values" in the template
came originally from 3 sources:
 Reference tables in DEP 82.00.10.30-Gen Engineering Information Specifications,
 Data from previous projects
 Existing discipline documents
These have been validated by the respective discipline CFDHs.
Effective: Nov-2020
1.5 Definitions
Deliverable(s) Product(s) of an activity (ies) or undertaking(s). The product can be a
document, data, drawing, record or just an activity.
DCAF Discipline Control and Assurance Framework: specifies the TA level
required to review and approve discipline control deliverables.
Electronic Electronic file created by scanning or direct rendition through software.
Image
Document Manuals, drawing, reports, datasheet, etc
Information Documents, 3D Model, Engineering Data and Business process data
deliverables (E-SPIR; SAP-PM, CIMS, EDW, etc)
IM Kickoff Form Template populated to request existing data to be issued for a project
work. It contains concurrent modification and dependency declaration
by the PE.
Livelink PDO corporate EDMS.
Compound Multiple files (maybe containing independent files), which are delivered
Document as a single document, e.g. MRBs
Contractor A party to a Contract with PDO.
1.6 Abbreviations
AFC Approved for Construction
AFD Approved for Design
AIC Asset Information Center
AI-PSM Asset Integrity – Process Safety Management
CCMS Certification and Completion Management System
CMMS Computerized Maintenance Management System
DDR Document Deliverables Register
DDM Document Distribution Matrix
EDS Engineering Design System
EDMS Electronic Document Management System
EIS Engineering Information Specification
EOIM Engineering and Operations Information Management
FCP Facility Change Proposal
IFR Issued for Review
IM Information Management
IOM Installation, Operation and Maintenance Manual
ITT Invitation To Tender
MRB Manufacturers Record Book
PCAP Project Control and Assurance Plan
PCC Project Close-out Certificate
PE Project Engineer
PLIP Plant Lifecycle Information Plan
PLN SP-2065 document status that indicates a document is planned for
development in project, will change to IFR document is created.
SoF Statement of Fitness
Effective: Nov-2020
PIN Project Initiation Note

POM Plant Operating Manual
PDMS Plant Design Management System
PSUA Pre-Start-up Audit
RLMU Redline Mark-up Drawings
TA Technical Authority
VDRL Vendor Document Requirements Listing: listing showing specific
Document requirement relating to the equipment being supplied or
manufactured.
WP Work Package; a group of activities that are considered as one unit from
the planning perspective.
1.7 Related CMF Business Control Documents
The related CMF Documents can be retrieved from the CMF Business Control Portal.
1 CP-102: Data and Document Management Code of Practice
2 CP-115: Operation of Surface Product Flow Assets
3 CP-117: Project Engineering Code of Practice
4 CP-223: Opportunity Realization Code of Practice
5 SP-1074: Preparation of Plant Operation Manuals
6 SP-1131: Handover & As-Built Documentation (Plant Lifecycle Information Plan)
7 SP-1134: General Specification for Detailed Engineering of Oil & Gas Facilities
8 SP-2065: Document Management In Engineering Projects and Operations
9 SP-2113: Project Commissioning and Start-Up Specification
10 SP-2122: E&O Information Management Specification
11 SP-2142: Engineering Project Data Specification
12 SP-2144: Engineering Project IM SoW
13 PR-1052: Preparation and Updating of Station Plant Operating Manuals
14 PR-1150: Project Close-out Procedure
15 PR-1159: Commissioning and Startup
16 PR-1169: Initial Start-Up Procedure
17 PR-1247: Project Management of Change Procedure
18 PR-1358: Concept Engineering in Select Phase (DG3) Procedure
19 PR-1666: E & O Document, Drawing and Data Management Procedure
20 PR-1692: PDO Document Retention Procedure
21 PR-2066: Deviation from Standard and Procedure
22 PR-2160: Pre Start-up Audit Procedure
23 DEP 82.00.10.30-GEN (Engineering Information Specification) February 2012
Effective: Nov-2020
2 GENERAL REQUIREMENT
Plant Lifecycle Information Plan (PLIP) appendix 1 is the PDO’s information reference library (document,
drawings and data) of all information that could be generated in projects. It shall be referenced by project
delivery team to select information deliverables scope for the project. The deliverables selected becomes
the project specific DDR.
The PLIP has predefined distribution list for each deliverable, which may be customized for a project
specific scope. The project shall produce a project specific DDM from the predefined list in PLIP.
The project engineer/manager shall notify the IM team, with the discipline resources, who will carry out
the discipline review/approval and the IM team will update DDM.
The project will develop/modify deliverables in line with PR-1666 - Engineering and Operations
Document, Drawing and Data Control Procedure, and on completion of project, handover the IM
deliverables electronically to the project IM focal point.
The project shall follow SP-2122: E&O IM Specifications, for deliverables handover and assurance
requirements. The IM team shall deliver the Business process data to application owners for publishing
as required by SP-2142: Engineering Project Data Specification.
The project IM team shall follow PR-1150: Project Close-out Procedure for a successful IM deliverables
handover and closeout.
Effective: Nov-2020
3 PROJECT HANDOVER DELIVERABLES REQUIREMENT

When a project is completed, it is the responsibility of the Project delivery team to ensure delivery of both
completed Physical Asset as well as the Information Asset to Operations in line with PR-1150: Project
Close-Out Procedure.
Final Master Information to be delivered to PDO shall be as specified in the project specific DDR:
 Project IM Coordinator/Lead shall receive final handover package electronically as specified in
project scope specific DDR, verify completeness and handover to AIC.
 Operating Integrity IM (UOI22X) shall prepare and deliver Tier1 Critical Document to the Field
 Tier1 Master Hardcopy delivered to the field shall be received by the OI Coordinator (XXO16X),
along with ePAD-AutoPCC receipt acknowledgement request which shall be approved to confirm
deliverables receipt and RLMU “Replace” at the station
 Information retention shall be in line with CP-102: Corporate Document Management – CoP and
PR-1692: PDO Document Retention Procedure
3.1 Master Information Deliverables
Master information comprises of: As-Built drawings like PEFS, Certified Final Document like POM, 3D
model files and Business Process data for systems (SAP-PM, CCMS, CIMS, EDW, SPI, Intelligent P&ID,
etc). They shall be delivered as applicable to data system custodian in line with SP-2142 and SP-1131.
These information deliverables are developed or modified during projects or operations as a result of new
Asset development or modification of existing Assets (no matter how small the modification may be).
3.2 Critical Documents & Data
Tier 1 and 2 Critical Documentation: As-Built drawing, Certified Final document, and Data (business
process data like SAP-PM, etc), are as defined in CP-115 - Operation of Surface Product Flow Assets -
CoP, as the minimum Master Information deliverables that shall be delivered to Operations at the end of
an Engineering project. The final RLMU, and electronic version of latest status Critical Documents
generated in project, shall be delivered to Field team to support SoF signoff and RFSU milestone.
Only Tier 1 Critical Documentation shall be produced in hardcopy format and maintained at the station to
support Asset operation, refer to PR-1666 for detailed lifecycle management procedure.
3.3 Manufacturers (Vendor) Record Book (MRB)
MRB concept is PDO means of delivering VDRL records (drawings, datasheets, etc) defined in project to
be delivered as part of equipment procurement.
During project handover, MRB shall be delivered to AIC for publishing in SPO E&O IM Portal along with
other project information deliverables. Follow appendix 2 for MRB doctype handover format definition.
The procurer (PDO or Contractor) shall customize the VDRL template in SP-2065 - Document
Management in Engineering Projects - Appendix 3 for relevant documentation required to support
operation and maintenance of the equipment. The MRB shall be delivered in electronic format with only
one clean master hardcopy to be delivered and maintained in the Field.
Effective: Nov-2020
3.3.1 MRB File Handover Template

Follow below structure of appendix 6, for MRB file handover template, which shows the actual
equipment records produced for the equipment and their reference document numbers. During operation,
MRB records shall be retrieved by searching SPO E&O IM Portal using FLOC or Tag or reference record
number. The FLOC-Tag-Document reference table delivered as part of EDW shall retain the link between
equipment and associated MRB documentation.
3.3.2 MRB Document/Multiple Drawing Handover

Each VDRL doctype in MRB shall be delivered separately, doctype by doctype. Where the doctype is a
document (e.g. datasheet, installation manual, etc), or a drawing with multiple sheets (e.g. PEFS, etc),
the structure below, of appendix 5 shall be applied in delivering the MRB electronically.
Effective: Nov-2020
3.3.3 MRB Handover Quality Check:

IM Coordinator shall follow MRB Quality Check template of appendix 7 for final MRB verification that will
ensure MRB is aligned with requirement for handover to AIC.
3.3.4 MRB Quality Check SoP:

IM Coordinator shall follow SOP of appendix 8 to undertake MRB Quality Check for MRB received from
contractors before delivering to AIC.
3.4 Plant Operating Manual

The Plant Operating Manual (POM) contains or refers to document types like PEFS (a distinct document
with identification number). These document types shall not be added or inserted (as picture or object)
directly on the POM but shall be referenced, indexed and hyperlinked from POM to the original location of
the master drawing. This will maintain single master location of information, and allow modification to take
place independently on the referenced information.
For each modification project, an assessment of impact on the existing POM shall be undertaken in line
with section 3.16, and where impact is identified, it shall be made directly to the master POM held by AIC,
rather than creating an addendum file (see section 3.16 for addendum requirements). The Contractor
shall update the POM in accordance with the following Specifications and Procedures:
 SP-1074: Preparation of Plant Operation Manuals Specification
 PR-1052: Preparation and Updating of Station Plant Operating Manuals.
 PR-1666: Engineering and Operations Document, Drawing and Data Control Procedure.
The POM shall be delivered in electronic format, fully indexed with hyperlink of the original location of any
document referenced in the POM, and only one clean master hardcopy delivered and maintained in
the Field.
Effective: Nov-2020
3.4.1 POM Addendum and POM Input File

Reference copy of master iPOM is available from the E&O IM Portal for project retrieval.
POM Input File: For On-plot project modification within the facility Plot Plan, copy shall be retrieved in
native/word format and updated directly with tracked input to reflect scope. The updated POM file,
reflecting tracked project modification on the referenced version retrieved from E&O IM Portal is “iPOM
Input file” which shall be delivered at the end of project to support PSUA, Sof and RFSU. For example
FCP, Demolition, PSM, installation of new Units, modification of existing Units, Engineering changes
affecting Operation, Operating Philosophy, schedule, etc.
POM Addendum: For On plot Brownfield project outside the current Plot Plan, for example adding a
Greenfield facility, which belongs to the overall Plant Operation, addendum to existing iPOM shall be
created in line with SP 1074. For example RMS, Test Separators, Remote Manifold, etc; POM numbering
shall be as shown below:
PLANT OPERATING MANUAL FOR MARMUL MAIN
Main iPOM MAR-24-104332-OA-4811-00001-0000
PRODUCTION STATION PLAN
POM Input File MAR-24-104332-OA-4811-00002-0000
PRODUCTION STATION PLAN (Installation of Gas Compressor)
PRODUCTION STATION PLAN (Flare Ignition Improvement)
ADDENDUM TO POM FOR MARMUL MAIN PRODUCTION
POM Addendum MAR-24-104332-OA-4811-00004-0000
STATION PLAN (Installation of Test Separator)
PRODUCTION STATION PLAN (16” Piping Bypass installation)
ADDENDUM TO POM FOR MARMUL MAIN PRODUCTION
POM Addendum MAR-24-104332-OA-4811-00006-0000
STATION PLAN (Installation of Remote Manifold System)
The POM Input File or POM Addendum created in project shall be delivered and accessible to Field
Operations staff as part of RFSU documents, before SoF will be signed.
PDO approach to POM Sustainability is to maintain the POM real-time with Plant modification, such that
changes to Plant is incorporated directly in the Main POM. The concept presented above is best
scenario, the discipline TA discretion will be required to determine approach when below cases are
presented in Plant modification:
 BGS with infill RGMS outside the Plot Plan may not require a new iPOM as it has several inter
references with the BGS hence POM Input File approach will be considered
 Adding a new flare by extending the plot should not call for new iPOM Addendum
 Adding ANR MGI facility should not call for new iPOM but to be part of same iPOM.. Please
consider this examples and justifications.
3.5 Completion Dossiers
On completion of the construction, pre-commissioning / commissioning and handover of the project, all
Construction, Fabrication and Commissioning deliverables (CCMS punch lists, check sheets, test sheets,
quality dossier, handover certificates, etc), associated with works on the facilities shall be assembled,
delivered and archived electronically in AIC, in the appropriate work parks. The work packs shall be
signed off by all parties as detailed on the individual sheets and certificates. For more details refer to:
 SP-2113: Specification for Commissioning and Start-Up (Key Principles)
 PR-2366: Project Certification and Completion Management
Effective: Nov-2020
3.6 Project Change Control

Notification and approval documents relating to: changes / variances in Basis for Design, Front End
Design Deliverables, Project Specification, Budget Proposals / RFAs, Detailed Design (AFC drawings
and documentation) and selected Standards shall be held in the project workspace and form part of the
handover to AIC.
Reference should be made to PR-1247: Project Management of Change Procedure.
3.7 Document Classification
This standard defines document types and assigns numeric classification codes (refer appendix 1) to
each type, to aid their reference and retrieval from IM system.
3.8 Information Storage and Archiving
Electronic version of Master Information delivered at the end of a project shall be stored and maintained
centrally in AIC while hardcopies of Tier 1 Critical Documentation and MRBs shall be delivered to the
respective Field. Project hardcopy information, in which there is no existing electronic version, and which
is required to be kept as record, shall be digitized and published in project IM workspace. The Design
Integrity IM Team shall digitally archive project documentation (after Critical Document handover to AIC)
in line with corporate record retention requirements..
3.9 Master Information Retrieval and Control

Master Information required for Operating, Maintenance and Design Integrity is controlled electronically in
AIC, and becomes uncontrolled when printed unless stamped with “Controlled Hardcopy” and wet
signed, or printed with watermark.
During a project, construction deliverables in hardcopy shall be printed from the project IM system (SPO
or Assai), and signed by the IM focal point of the party that made the print to confirm the source of
printing. Any other printed hardcopy or electronic version residing elsewhere is uncontrolled.
Information required for reference or to support activities (PIN, Integrity and FIP of existing asset) shall be
retrieved from AIC IM Portal system.
3.10 Pre-Start-up Audit (PSUA) Documentation

Documents identified in the project DDR as “REQUIRED_FOR_FINAL_HANDOVER” shall be available in
their final form prior to the PSUA. This requirement recognizes that certain drawings may still be in RLMU
state; As-Built drawings may still be outstanding.
The project IM Lead shall conduct IM Handover Assurance review, to demonstrate status of information
handover deliverables, and provide IM Assurance Certificate to support PSUA.
Refer to PR-2160: Pre Start-up Audit Procedure for general requirement and guidance for PSUA.
3.11 As-Building and TA Approval

TA review/approvals are required during detailed engineering design leading to AFC deliverables. Any
change to the AFC deliverables requires appropriate TA approval before being implemented.
Effective: Nov-2020
At the end of commissioning, the RLMU drawings shall be signed by both the contractor and the PDO
commissioning engineer (or representative at site), to confirm consistency of RLMU with the actual
constructed work, refer to PR-1666.
3.12 Quality Assurance

The contractor shall have an approved checking and approval process in place (as a part of its ISO9000
system), which is implemented and supported by regular assurance /quality checks.
This will ensure that the information deliverables are reviewed and checked internally before they are
delivered to PDO.
3.13 IM Kick-off Form

The project shall utilize IM Kick-off Form in SPO function (SPO projects), or appendix 3 (Assai projects):
 To request for existing information required for project execution
 To confirm the impact of project on concurrent project or FCP
 To request for allocation of Tags
3.14 Engineering and Operations Reference Document (EORD)

The EORD approach of collating and delivering manual of facility documentation have been discontinued
(ie delivery of EORD manual not required). Related EORD documents types are now available in PLIP,
and when produced and delivered from projects they are available in the E&O IM Portal. The following
key EORD facility reference documents were included in the PLIP to ensure that all EORD documents
types were captured in the PLIP.
Document Class Description
PX-3329 Equipment Operating Envelop
PX-4603 Hydraulic Calculation
PX-6967 Process and Simulation Report
PX-6843 Dynamic Simulation Reports
During projects, information deliverables scope shall be selected from the PLIP of appendix 1, confirmed
at project initiation, and included as part project deliverable scope in the DDR.
3.15 Early Tie-in/Scope Handover
When a project needs to deliver and put in Operations, part of the overall scope like early Tie-in scope,
etc, they shall also deliver associated handover information. Where any of the information delivered from
the early scope is required to continue the project work, they shall retrieve it from AIC for reference and
Reserve/checkout for As-Building accordingly.
When early scope delivery is identified, a ePAD-RAMZ subproject ID shall be created to support:
 Delivery of information deliverables associated with the scope to AIC
 ePAD-AutoPCC deliverables approval and closeout of early scope
Effective: Nov-2020
3.16 Critical Documentation Modification Dependency

The Dependency Matrix provides project team with reference guideline for proper scoping of existing
Asset Information and Data As-Built modification to ensure that changes to existing Critical doctype are
evaluated for impact against dependant documents shown on matrix. During project initiation, IM System
(SPO) will present impacted doctypes based on the matrix below, and project would progressively assess
dependant doctype impact as part of detailed design. The actual impacted doctypes shall be finalized,
updated and delivered as part of AFC milestone.
For example, a project modification that changes existing asset documentation like PEFS shall evaluate
other existing documentation for impact (HAZOP Report, Operation HSSE Case, MRB, POM
Safeguarding Memorandum, Variable Table, etc), in line with the Dependency Matrix below (even with no
impact). The IM Delivery team will verify compliance as part of Information Deliverables Handover
Assurance Review.
Where change impacted the following information deliverables: HAZOP Report, POM, and Safeguarding
Memorandum, the master file shall be retrieved from AIC and updated directly, as part of the project
delivery activities. Addendum shall not be generated in line with section 3.4.1 and agreed with OR focal
point in project, addendum numbering will be same with main On-Plot master POM as shown below:
MAR-24-104332-OA-4811-00001-0000 PLAN OPERATING MANUAL FOR MARMUL MAIN
PRODUCTION STATION PLAN
MAR-24-104332-OA-4811-00002-0000 ADDENDUM TO POM FOR MARMUL MAIN PRODUCTION
STATION PLAN (Installation of Gas Compressor)
Follow PR-1666: Engineering and Operations Document, Drawing and Data Control procedure during
Information development, modification or field hardcopy management.
Effective: Nov-2020
3.16.1 Tier 1 Modification Dependency Matrix

Dependency Matrix for Tier1 Critical Documentation Modification or Verification (SP-1131 section 3.16)
SCEs Inspection Programme and MJR (in

General Arrangement Drawings (Piping, etc)
Escape Routes, Fire Fighting and Life Saving

Change Impact
Process Safeguarding Flow Schemes (PSFS)
Process Engineering Flow Schemes (PEFS)

Utilities Engineering Flow Schemes (UEFS)
List of Safety Critical Elements (in CMMS)

Locked Valves and SBS Spades Register
Hazardous Area Classification Drawing

Process Safeguarding Memorandum
Corrosion Management Framework

Fire and Gas Field Detector Layouts
Overall Plot Plans (Unit Plot Plan)
Variable Table (Alarm Catalogue)

Plant Operating Manual (POM)
Material Selection Report MSR

HAZOP Report (Including IPF)
Risk Based Inspection (RBI)

Cause and Effect Diagrams
Emergency Response Plan

Alarm and Trip Settings
Asset Register (CMMS)
Operations HSSE case

CMMS)
No. Change Driver: Change events PLIP Type Code Field Hardcopy DCAF Discipline
Legacy Verification and 2310 (Diagram) & 6604
1 Cause and Effect Diagrams/Matrix Modification projects (Matrix) Yes Control and Automation D X X X X X X X X X X X X X
Legacy Verification and
2 Alarm and Trip Settings Modification projects 4302 Yes Control and Automation X X X X X D X X X
3 Fire and Gas Field Detector Layouts Modification projects 4019 Yes Control and Automation X X X X X X X X X D
Process Engineering Flow Schemes Legacy Verification and
X X X
4 (PEFS) Modification projects 2365 Yes Process Engineering X X X X X X X D X X X X X X X X X X X X
Utilities Engineering Flow Schemes Legacy Verification and
X X X
5 (UEFS) Modification projects 2364 Yes Process Engineering X X X X X X X X D X X X X X X X X X X X
Legacy Verification, Modification
X
6 HAZOP Report projects and 5 YEARS REVIEW 6875 No Process Engineering X X X X X X X X X X X D
Legacy Verification, Modification
X X
7 Plant Operating Manual (POM)* projects and 5 YEARS REVIEW 4811 Yes Production Operations X X X X X X X X D X X X
8 Variable Table (Alarm Catalogue) Modification projects 4304 No Production Operations X X X X X X X X X X D X X
Operations HSSE Case (ALARP Legacy Verification, and 5 YEARS
X X X
9 Demonstration Report)** OPS REVIEW 7506 Yes Technical Safety X X X X X X X X X D
Escape Routes, Fire Fighting and Life 2318 (excape route) &
10 Saving Equipment Layouts Change of a safety equipment 4016 (fire fighting) No Technical Safety X X X D
Corrosion Management Framework update required 4880 No RA - Materials and Corrosion. X X X X X X X D
Risk Based Inspection (RBI) update required 709 No RA - Materials and Corrosion. X X X X X X X X D
Material Selection Report MSR update required 5009 No RA - Materials and Corrosion. X X X X X X D
* No Addendum, update master. Maintain Field Hardcopy **Update maintianed by Ops Update CIMS each time CMMS is updated D = Change Driver X = Deliverables to be evaluated for impact/update
Effective: Nov-2020
3.16.2 Tier 2 Modification Dependency Matrix

Dependency Matrix for Tier2 Critical Documentation Modification or Verification (SP-1131 section 3.16)
Electrical Control System Block Diagram

Change Impact
Panel Lay-outs (alarm display and F&G
Material Certificates(for Safety Critical

Firewater demand/distribution report
Functional Logic diagrams (DCS and
Corrosion Management Philosophy

Diagrams (Power and Instruments)
Relief, Flare and Vent Study Report
Vendor Manuals(for Safety Critical

Primary Structural Steel Drawings
Cable Routing Drawings(including
Instrument Signal Loop Diagrams
Passive Fire Protection Schedules

Electrical Key-one Line Diagrams
Passive Fire Protection diagram

Diagrams(for Hazardous Areas,
Control System Block Diagrams
Earthing General Arrangement

Instrument cable terminations
Electrical Single Line Diagrams
Cathodic Protection Diagrams

Telecommunications General
Lighting Lay-out(emergency)
HVAC General Arrangement
Blast and fire walls General
Pipeline Routing Diagrams

Arrangement Diagrams
Arrangement Drawings
Operations Philosophy
Process Flow Schemes

detection display)
Basis for Design

underground)
Safeguarding)
Equipment)
Elements)
PLIP Type
No. Change Driver: DCAF Discipline
Code
1 Control System Block Diagrams 0901 IN - Instrumentation. D x x x x x x x x x x x x x
Functional Logic diagrams (DCS and
IN - Instrumentation. x D x x x x x x x x x x x
2 Safeguarding) 4780
Telecommunications General Arrangement
TA - Telecommunication D x x x x
3 Diagrams 4018
4 Instrument cable terminations 8804 IN - Instrumentation. x x D x x x x x x
5 Instrument Signal Loop Diagrams 2347 IN - Instrumentation. x x x D x x x x x
Panel Lay-outs (alarm display and F&G
IN - Instrumentation. x x x x D x X x x x
6 detection display) 4024
Earthing General Arrangement Diagrams
x X D x x x x x x x x
7 (Power and Instruments) 8809 EA - Electrical.
8 Lighting Lay-out(emergency) 4025 EA - Electrical. x x D x x x x x x x

9 Electrical Single Line Diagrams 2384 EA - Electrical. x x x x x x D x x x x x x x x
10 Electrical Control System Block Diagram 0901 EA - Electrical. x x x x D x x x x x
Cable Routing Drawings(including
11 underground) 2373 EA - Electrical. x x x x x D x x x x x
12 Electrical Key-one Line Diagrams 2384 EA - Electrical. x x x x D x x x x
Corrosion Management Philosophy 5519 RA - Materials and x D x x x x x x
RA - Materials and
15 Cathodic Protection Diagrams
x x D x
2309 Corrosion.
HVAC General Arrangement Diagrams(for
x x x x x D x x x x
17 Hazardous Areas, LQs,TRs) 4018 MH-HVAC
18 Firewater demand/distribution report 7180 HX - HSE&S General. x D x x x x x x x
19 Passive Fire Protection Schedules 5804 HX - HSE&S General. D x x x x
20 Passive Fire Protection diagram 2356 HX -- Civil
CX HSE&S General.
& Structural x x x x D x x x
22 Primary Structural Steel Drawings 2386 Other. x x x x D x
24 Operations Philosophy 5522 OA - Operations. x x x x x x x x x x x x x D x x x
25 Pipeline Routing Diagrams 2373 LA - Pipelines. x x x x x D x x
26 Relief, Flare and Vent Study Report 8249 HX - HSE&S
AA General.
Management & x x x x x x D x x x x
27 Basis for Design 7704 Project Eng. x x x x x x x x x x x x x x x D x
Material Certificates (for Safety Critical RA - Materials and
x D x
28 Elements) 5011 Corrosion.
30 Process Flow Schemes 2366 PX - Process Other. x x x x x x x x x x x x x x D
D = Change Driver X = Deliverables to be evaluated for impact/update
Effective: Nov-2020
4 ROLES AND RESPONSIBILITIES

4.1 Project Engineer/Manager
Accountable for ensuring that project information deliverables are selected from PLIP at the beginning
of the project (FEED/Detail Design). S/he shall:
 Ensure that where project modifies existing asset documents like PEFS, impact on existing
documentation is assessed in line with section 3.16 Modification Dependency as part of scope.
 Endorse the project specific DDM for IM implementation
 Ensure that project information deliverables are not kept or managed elsewhere, and that all
DDR deliverables are managed and available in the document management system
 Ensure that Information/data modification dependency assessment are completed in line with
Dependency Matrix, before AFC
4.2 Project Discipline Engineer
 Ensure that the DDR produced by contractor, contains correct discipline deliverables scope
 Evaluate existing Asset information/data modification for impact in line with Dependency Matrix
 Change Driver/Primary Doctype discipline engineer is accountable to ensure dependent
doctype engineers completes Dependency Matrix and demonstrates compliance before AFC
 Update DDM template from PLIP with any additional project distribution and send to IM Team
 Review and approve discipline deliverables in DDR, as required in DDM
4.3 IM Delivery Lead
 Ensure that DDR and DDM are finalized as part of project initiation, and that DDR deliverables
are planned with status PLN, tracked and reported using the document management system
 Provides electronic reference copy of the master information, including identification of any
other project using the same master.
 Initiate Dependency Matric Compliance workflow in IM System and assign accountability to the
Change Driver/Primary doctype ATA engineer who will facilitate the dependency doctype
modification compliance
 Demonstrate Dependency Matrix compliance as part of IM Handover Assurance Review
 Work with PDO partners developing or modifying information to ensure adequate internal
review and approval.
 Ensure that information specified in a project DDR is developed and delivered, ensuring that
information deliverables meets specification for handover AIC.
 Conduct information deliverables handover assurance review in line with project assurance
plan and archive electronic location of project information.
4.4 Contractor
 Agree IM resource with IM Delivery Lead before assigning responsibility for all or part of
information management activities.
 Produce a project specific DDR from the PLIP template of appendix 1, as part of project
initiation and kick-off and agree with PDO discipline focal point
 Update DDR with associated plan showing key information development milestone dates
(Issued for Review and Approved for Design/Construction). These milestones shall be
measured and reported as agreed with the IM Delivery Lead as one of the project KPIs.
Page 5 SP-1131: Plant Lifecycle Information Plan (Handover and As-Built Printed: Nov 2, 2020
Documentation)
Effective: Nov-2020
 Ensure adequate internal checking and approval of information before delivering to PDO.
 Deliver information deliverables to IM Delivery Lead as contained in DDR.
 Ensure that where project modifies existing asset documentation like PEFS, the impact on
other existing documentation is assessed in line with the modification dependency matrix
Page 6 SP-1131: Plant Lifecycle Information Plan (Handover and As-Built Printed: Nov 2, 2020
Documentation)
Effective: Nov-2020
5 PLIP TEMPLATE DESCRIPTION

COLUMN NAME DESCRIPTION / CLARIFICATION ACTIONS REQUIRED
The party who will produce the document --- either a PDO entity
ORIGINATOR Discipline Lead to specify
or 3rd party or Contractor or Supplier.
The name of the PDO team member who is responsible for the
PROJECT FOCAL POINT Discipline Lead to specify
SOURCE document (prepares or reviews or approves).
Discipline Lead to verify what
Standard "Discipline Code - Discipline name" as defined in is selected by IM team and to
DISCIPLINE_CODE
DEP82.00.10.30-Gen Engineering Information Specifications. consult with IM team if it
should be changed.
Discipline Lead to verify the
INFORMATION REQUIRED A typical title, type or category of documents and data to be
default value (listed by IM
(DOCUMENT & DATA) delivered at various stages through the project lifecycle.
team).
INFORMATION
DESCRIPTION Standard "Discipline-Document Type Code + Name" and
DOCUMENT_TYPE_NAME "Descriptions" defined in DEP82.00.10.30-Gen Engineering
Information Specifications. Standard classification on document
default value (specified by IM
types facilitates document repository in EDMS (standard folder
team).
DOCUMENT_TYPE_ structure in Livelink) and to make cross reference to the Record
CODE Management requirements (e.g. retention).
POSSIBLE TITLES_
Additional description of document types No action
AND_TYPE_DESCRIPTION
Discipline Lead to specify or

verify the default values.
Preferably to refer to a DEP or
Reference to DEP or other samples/examples which define
a Project Specification. As the
REFERENCES minimum requirements or level of details regarding the technical
minimum, the Discipline Lead
contents of the Document.
should be able of providing a
sample/example from previous
projects.
Notes to describe specific project requirements or clarifications Discipline Lead to add specific
PROJECT SPECIFIC NOTES
on the information (document or data) listed. special notes
Effective: Nov-2020
Document Security Classification per PDO guidelines Discipline Lead to verify the
SECURITY_CLASSIFICATION (Unrestricted, Restricted, Confidential, Most Confidential) --- default value (specified by IM
various handling procedures are required team).
Related objects of the Document to facilitate navigation from the
object to the documents. An object can be an Asset type (in
RELATED_OBJECTS default value (specified by IM
Plant Asset Hierarchy --- Site, Plant, Process_Unit, Equipment,
team).
Tag, Model_Parts) or other Document such as a Purchase Order.
Format of the Information (Document or Data) to be delivered Discipline Lead to verify the
BASIC DURING_PROJECT_FORMAT during the project for eview/approval/information (Paper, MS default value (specified by IM
DOCUMENT Word, MS Excel, MS Access, Adobe Acrobat, AutoCAD, etc.) team).
PROPERTIES Format of the Information (Document or Data) to be delivered Discipline Lead to verify the
AFTER_PROJECT_FORMAT during handover to Operation (Paper, MS Word, MS Excel, MS default value (specified by IM
Access, Adobe Acrobat, AutoCAD, etc.) team).
With respect to project scope, identify from the Critical
REQUIRE_FIELD_CONTROLLE PE verifies from Operations,
Documentation list of CP-115, which Information is required to be
D_HARDCOPY default values (Yes or No).
physically available in the field for Operations of the facility.
Categorization/value of the Information (Document or Data) for Discipline Lead to verify the
AFTER_PROJECT_CATEGORY PDO after handover from project to operation (Essential, Legal, default value (specified by IM
Desirable) --- different requirements on repository and retention team).
Based on PDO document group retention guidelines (asset life, 2
RETENTION_PERIOD default value (specified by IM
yrs, etc).
team).
Critical Information (document and data) deliverables as defined Discipline Lead to verify the
CRITICAL_ DOCUMENTATION in CP-115: Operation of Surface Product Flow Asset. This is default value (specified by IM
the minimum deliverables that is required for Operating Integrity. Team).
Document is a deliverable of PCAP (Project Control and
DCAF Control (Identification default value (specified by IM
Assurance Plan). Those "Yes" deliverables subject to PCAP
DOCUMENT Number) team) against the latest signed
requirement.
PCAP-discipline list.
DELIVERY
(SELECT) REQ_FOR_ Will the Information (documents & data) be delivered as part of Discipline Lead to verify the
REQUIRED CONCEPT SELECTION the concept selection? default values (Yes or No).
PER PROJECT
(DEFINE) REQ_FOR_ PROJECT Will the Information (documents & data) be delivered as part of Discipline Lead to verify the
PHASE _ SPECIFICATION/FEED the project specification package (FEED)? default values (Yes or No).
(EXECUTE) REQ_FOR_
Will the Information (documents & data) be delivered as part of Discipline Lead to verify the
DETAILED DESIGN AND
the detailed design package? default values (Yes or No).
CONSTRUCTION
(OPERATE) REQ_FOR_ PSUA_ Will the Information (documents & data) be required to support Discipline Lead to verify the
Effective: Nov-2020
COMMISIONING AND RFSU PSUA, Pre-commissioning and Commissioning/Start-up default values (Yes or No).
(Flawless start-up initiative)?
REQUIRED_FOR_FINAL_HAND Will the Information (documents & data) be required as part of the Discipline Lead to verify the
OVER handover package to PDO? default values (Yes or No).
Will the Information (documents & data) deliver as As-built (ASB) Discipline Lead to verify the
REQUIRED_HANDOVER_
or Certified FINAL (revision of information not requiring As- default values (ASB, FINAL or
STATUS (ASB or FINAL)
Building)? If value is no, then information not required. No).
This field was left blank to allow project customization in line with
project strategy. It should be populated as part of MDR
REQUIRE_PDO_REVIEW/APPR development, to capture PDO's review requirements on Discipline Lead to specify or
OVAL documents produced by others (contractor / suppliers) per the verify the default values.
Document Type: IFR=Issue For Review; IFA=Issue For
Approval; IFI=Issue For Information; No=No review required.
Resource typically a
Highlights document types in which RLMUs may be generated. At
commissioning Engineer but
the end of project, PDO focal point shall check As-Built produced
OTHERS FINAL RED-LINE CHECKING the Project Engineer to agree
against “RLMU”, to confirm that As-Built produced is a true
resource with Operations if
reflection of constructed works.
different
Who is the final owner/status of the deliverable after handover?
Typically, ownership of Critical Documentations is with the Asset Discipline Lead to specify or
FINAL OWNER/STATUS
Manager, while other deliverables are stored electronically in a verify the default values.
secured EDMS location for future reference.
COMMENT General comments from IM team or Discipline Lead
Effective: Nov-2020
6 NAMES OF DISCIPLINE SUPPORT ENGINEER

The names of respective discipline engineer assigned to support the project scope (full time or part time) are as follows:
DISCIPLINE LEAD (Focal

Remark
DISCIPLINE Point in PDO Project Team)
DISCIPLINE DESCRIPTION
_CODE Define- Detailed
Execute
FEED Design
Management and Project execution plan, basis of design, organization, authorities.
AA
Project Engineering Integrated plans such as those for Pre-Commissioning.
BA Construction Construction- and fabrication-related information. Also, installation
and transportation specifications.
CB Architectural All buildings: including interior design and structure.
CG Geotechnical / Soil properties, shallow hazards, piles, suction piles, anchors, mud
Foundation mats.
CI Infrastructure Onshore: Roads, drainage, sewering, fences, etc.
CS Structures All major structures (steel and concrete) also vessels, ships, jackets,
topside modules, floating production systems.
EA Electrical Design and application of circuitry and equipment for power
generation and distribution, machine control.
FA Cost and Planning Integrated project cost, schedule, budget estimating and tracking.
FD Field Development Field Development Plan. Synonyms: Master Development Plan, Area
Plan Development Plan, Base Development Plan.
HX HSE&S General To use if Health, Safety, Environment and Security document cannot
be assigned to one of the other HSE&S document types (i.e. not
Environmental, Health, Safety, Security. Also for Hazard
Management).
IC IC Process control & For Process Control and Optimization discipline related deliverables.
Optimization. Distributed control systems, PLCs, process control logic
IN Control and Instruments and instrument systems
Automation
JA Information Content management, Data, Document and Knowledge management,
Management Procedures, Specifications, Standards.
KA Information IT Infrastructure, hardware, software, applications
Effective: Nov-2020
Technology
LA Pipelines Line pipe, stability, hydraulics, installation, commissioning.
MP Piping Pipe, flanges, fittings, valves, pipe supports, stress analysis.
MH HVAC Heating, Ventilation and Air-conditioning.
MR Rotating Equipment Compressors, pumps turbines, etc.
MS Mechanical - Static Vessels, furnaces, boilers, tanks, etc.
MX Mechanical Other Use only when the other Mechanical disciplines cannot be used (i.e.
not HVAC, Mechanical - Static, Piping, Rotating Equipment)
NA Engineering The branch of engineering that deals with equipment reliability.
Maintenance
OA Operations Surface Readiness for production, marine, subsea, logistics, supply base,
Production. shutdown, etc.
PX Process Other Use only when the other Process disciplines cannot be used (i.e. not
Fluid Flow and Assurance, Process Operational Turnaround Support,
Process Technology)
QA Quality Assurance Includes formal review of designs, problem identification, corrective
actions to remedy any deficiencies and evaluation of actions taken.
RA Materials and Materials, corrosion and coating issues across multiple disciplines.
Corrosion
TA Telecommunication Radio communication, satellite and Cable communication, etc.
VA Contracting and Everything related to procurement and contracting documentation
Procurement
ZT Production Everything related to Production Technology
Technology
ZP Petrophysics. Everything related to Petrophysics
ZR Reservoir Everything related to Reservoir Engineering
Engineering
ZV Vendor All equipment deliverables
ZW Well Engineering Everything related to oil and gas wells.
Effective: Nov-2020
7 APPENDICES
7.1 APPENDIX 1: Plant Lifecycle Information Plan (PLIP Template)
7.2 Appendix 2: MRB Document Type Handover Format Definition
7.3 Appendix 3: IM Kick-off Form
7.4 Appendix 4: User Feedback Form
7.5 Appendix 5: MRB Document/Drawing Hanover
7.6 Appendix 6: MRB File Handover Template
7.7 Appendix 7: MRB Quality Check List (QC)
7.8 Appendix 8: MRB Delivery SOP
Page 8 SP-1131: Plant Lifecycle Information Plan (Handover and As-Built Documentation)

SP 1131 Rv.7

Uploaded by

Copyright:

Available Formats

SP 1131 Rv.7

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SP 1131 Rv.7

Uploaded by

Copyright:

Available Formats

Petroleum Development Oman L.L.C.

Plant Lifecycle Information Plan

Document Type Specification

Discipline Project Engineering

Issue Date November 2020

I Authorized For Issue – November 2020

Revision Date Originator Checker Reviewers Scope /

7.7 Appendix 7: MRB Quality Check List (QC) ............................................................... 8

PIN Project Initiation Note

3 PROJECT HANDOVER DELIVERABLES REQUIREMENT

3.3.1 MRB File Handover Template

3.3.2 MRB Document/Multiple Drawing Handover

3.3.3 MRB Handover Quality Check:

3.3.4 MRB Quality Check SoP:

3.4 Plant Operating Manual

3.4.1 POM Addendum and POM Input File

3.6 Project Change Control

3.9 Master Information Retrieval and Control

3.10 Pre-Start-up Audit (PSUA) Documentation

3.11 As-Building and TA Approval

3.12 Quality Assurance

3.13 IM Kick-off Form

3.14 Engineering and Operations Reference Document (EORD)

3.16 Critical Documentation Modification Dependency

3.16.1 Tier 1 Modification Dependency Matrix

SCEs Inspection Programme and MJR (in

Escape Routes, Fire Fighting and Life Saving

Process Safeguarding Flow Schemes (PSFS)

Process Engineering Flow Schemes (PEFS)

List of Safety Critical Elements (in CMMS)

Hazardous Area Classification Drawing

Corrosion Management Framework

Variable Table (Alarm Catalogue)

Material Selection Report MSR

Risk Based Inspection (RBI)

Emergency Response Plan

Operations HSSE case

3.16.2 Tier 2 Modification Dependency Matrix

Electrical Control System Block Diagram

Panel Lay-outs (alarm display and F&G

Material Certificates(for Safety Critical

Corrosion Management Philosophy

Relief, Flare and Vent Study Report

Vendor Manuals(for Safety Critical

Passive Fire Protection Schedules

Passive Fire Protection diagram

Earthing General Arrangement

Electrical Single Line Diagrams

Cathodic Protection Diagrams

HVAC General Arrangement

Blast and fire walls General

Pipeline Routing Diagrams

Process Flow Schemes

Basis for Design

8 Lighting Lay-out(emergency) 4025 EA - Electrical. x x D x x x x x x x

4 ROLES AND RESPONSIBILITIES

5 PLIP TEMPLATE DESCRIPTION

Discipline Lead to specify or