Petroleum Development Oman L.L.C.
Plant Lifecycle Information Plan
(Handover and As-Built Documentation)
Document ID / SP-1131Document Type / Specification
Security / Unrestricted
Discipline / Project Engineering
Owner / Julian Masters UEP
Issue Date / August 2015
Revision / 5.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.
Document No.: / Revision XX
Bonga North/Deepwater Projects
Proprietary Information: This document contains proprietary information and may not be partly or wholly reproduced without prior written permission from Shell Nigeria Exploration and Production Company Ltd.
/ Petroleum Development Oman LLC / Revision: 5.0
Effective: Aug-15
I Authorized For Issue – August 2015
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 No. / Date / Originator / Checker / Reviewers / Scope / RemarksRevision 5.0 / Aug-15 / Kingsley Chime UEOI41 / Spence, Jaqueline UEOI51
Maulana, Andre CTP34
Chukwuma, Chinonso UEOI12
Morowei, Ebikpogba UEOI23
Shahaibi, Farid UEOI22
Khusaibi, Abdullah UEOI21
Singh, Vinay UEOI431
Parthasarathy, Veeraraghavan UEOI14
Vezhaparamban, Rappai UEOI411
Mistry, Daxesh UEOI13
Paramasivan, Suresh Kumar UEOI15
Patel, Amitkumar UEOI46; Bhayani, Kaushikkumar UEOI43; Lawatia, Ali UEOI11 / Julian Masters UEP (Project Delivery)
Harthy, Mohammed UEOI2; Bulushi, Yousuf UEOI1; Lawati, Sadiq UEOI4; Kharousi, Fadya UEOI5; Elharras, Mohamed CTPI; Mullappally, Joseph UEQ11; Harding, David UOP4 / Updated to: incorporate rev 4 feedback; manage PCAP overlap; harmonize doc. classes; Critical Documentation and field hardcopy requirements
Revision No. / Date / Originator / Checker / Reviewers / Scope / Remarks
Revision 4.0 / Oct-13 / Kingsley Chime UEOI/12A / Yousuf Bulushi
UEOI/1
Mohamed Elharras CTPS3
Zykov, Aleksandr CTPS34
Raule, Ramoncito CTPS32
Thane Dewalker, Umashankar CTPS33;
Panayotova, Veronika UEOI12X / Julian Masters UEP (Project Delivery) / Revised deliverables requirement to introduce PLIP concept
Sultan Owaisi (Pipelines CFDH)
Mohammed Aghbari (Electrical CFDH)
Gary Briston (QA/QC CFDH)
Salim Hinai (C&A)
Nasser Behlany (MCI CFDH)
Anthony Sipkema (Tech Safety CFDH)
Hilal Aghbari (Civil Lead CFDH)
Harrasy Saaid (Mechanical CFDH)
Tor Bjerkestrand (UOM CFDH)
Ali Harrasi (UOP CFDH)
Version 3.0 / May-06 / UEV11 / Revised and reformatted
Version 2.0 / Aug-99 / Ohi Aikhoje OTE/4 / Revised
Version 1.0 / July -88 / ETH/11 / Initial issue
TABLE OF CONTENT
I Authorized For Issue – August 2015 2
II Revision History 3
1 Introduction 6
1.1 Purpose 6
1.2 Changes to this Specification 6
1.3 Step-out Approval 6
1.4 Scope 6
2 Process Description 7
2.1 General Description 7
2.2 Information Deliverables Management 7
2.3 Definitions 8
2.4 Abbreviations 8
2.5 Related CMF Business Control Documents 9
3 Project Handover deliverables requirement 10
3.1 General Requirements 10
3.2 Master Information Deliverables 10
3.3 Critical Documents & Data 10
3.4 Manufacturers (Vendor) Record Book (MRB) 10
3.5 Plant Operating Manual 11
3.6 Commissioning Work Packs 11
3.7 Project Change Control 12
3.8 Document Classification 12
3.9 Storage of Information 12
3.10 Master Information Retrieval and Control 12
3.11 Pre-Start-up Audit (PSUA) Documentation 12
3.12 As-Building and TA Approval 13
3.13 Quality Assurance 13
3.14 IM Kick-off Form 13
4 Roles and Responsibilities 14
4.1 Project Engineer/Manager 14
4.2 Project Discipline Engineer 14
4.3 Design Integrity (Project) IM Lead 14
4.4 Contractor 14
4.5 PLIP Template Description of Fields and Review Guidelines 16
4.6 Names of Discipline Engineer 19
Appendix 1: Plant Lifecycle Information Plan (Template) 21
Appendix 2 MRB Content Structure 21
Appendix 3 IM Kick-off Form 21
Appendix 4 User Feedback Form 21
1 Introduction
Project records, documents, drawings and business process data are critical to safe Operations and Maintenance of PDO’s Assets. This document brings the deliverable requirements and 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 a Discipline Control and Assurance Framework (DCAF) Control deliverable (control number 253). It describes ‘What’ information shall be developed from the beginning of a project. It contains generic listing of Information deliverables requirements (drawing, data, records and documents) to be developed during project, and what is to be handed over to support Operations, ensuring complete delivery of all Critical Documentation that are essential for Asset lifecycle Operations.
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 will be used to set project deliverable expectation in SELECT (Basis for Design), DEFINE (FEED), EXECUTE (Detailed Design and Execute) 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 PLIP.
1.2 Changes to this Specification
The Owner of this document is the CFDH, Engineering Project Delivery and the custodian is the manager Engineering and Operations Information Management (UEOI). 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 Information set contained in appendix 1 is a generic list of Information requirements from which a project specific PLIP shall be developed. The PLIP template readily filters into: project review requirement, final handover deliverables, and Critical Documentation requirement (required for Operating Integrity).
All Operations activities that change the plant shall also modify corresponding Information 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.
2 Process Description
2.1 General Description
I. Projects shall follow this sequence of activities to produce project specific PLIP:
1. Select information deliverable that will be generated or modified by the project, as part of project initiation and kick-off, utilizing appendix1 of this document.
2. For modification work, confirm dependency of each data type selected on other data sets: e.g. change in PEFS might affect POM, HAZOP, Operation HSSE Case, SAP, Variable Table, etc.
3. For those deliverables that require PDO review or approval, confirm which PDO focal point will provide the review/approval
4. Populate “REQUIRE_PDO_REVIEW/APPROVAL” with focal point information received to produce project specific PLIP, and obtain TA approval in line with DCAF.
5. Utilize project specific PLIP and produce project master deliverables register (MDR) with tentative information deliverable milestone dates (Issued for Review, Approved for Design, Approved for Construction and As-Built).
6. Develop/modify deliverables in line with PR-1666 - Engineering and Operations Document, Drawing and Data Control Procedure, and on completion of project, handover IM deliverables electronically to the project IM Lead.
II. IM deliverables handover assurance review shall be undertaken by Operating Integrity IM team, to confirm readiness to deliver specified information deliverables.
III. Project IM Lead or delegate shall check attributes of information being delivered, and confirm completeness before handover to Asset Information Center (AIC). He will notify the contractor to proceed and deliver hardcopy of Tier 1 Critical Documentation to the field as identified in PLIP.
IV. AIC IM Lead or delegate will receive IM deliverables (documents and drawings), publish and notify all stakeholders, and sign the Project Completion Certificate (PCC).
V. Business process data shall be delivered to application system owners for publishing as required by SP-2142: Engineering Project Data Specification.
VI. Refer to PR-1150: Project Close-out Procedure for the project activities required for the formal transfer of ownership of a constructed and commissioned facility from the project delivery team to the Asset owner.
2.2 Information Deliverables Management
Follow PR-1666: Engineering and Operations Document, Drawing and Data Control procedure during Information development, modification or field hardcopy management.
When a project modifies existing asset documentation like PEFS, etc, the impact on the following information deliverables: HAZOP Report, Operation HSSE Case, Safeguarding Memorandum, MRB, POM, Variable Table, etc, shall be evaluated and confirmed on the IM Kick-off form. The master revision of these deliverables shall be retrieved and updated as part of the project delivery activities, rather than creating addendum.
2.3 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 Image / Electronic file created by scanning or direct rendition through software.
Document / Manuals, drawing, reports, datasheet, etc
Information deliverables / Documents, 3D Model, Engineering Data and Business process data (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 Document / Multiple files (maybe containing independent files), which are delivered as a single document, e.g. MRBs
Contractor / A party to a Contract with PDO.
2.4 Abbreviations
AFC / Approved for ConstructionAFD / 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
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
SoF / Statement of Fitness
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.
2.5 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 Practice2 / CP-115: Operation of Surface Product Flow Assets
3 / CP-117: Project Engineering Code of Practice
4 / SP-1074: Preparation of Plant Operation Manuals
5 / SP-1122: Specification for Project Quality Plan
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: Specification for Commissioning and Start-Up
10 / SP-2142: Engineering Project Data Specification
11 / SP-2144: Engineering Project IM SoW
12 / PR-1052: Preparation and Updating of Station Plant Operating Manuals
13 / PR-1150: Project Close-out Procedure
14 / PR-1159: Commissioning Procedure
15 / PR-1169: Initial Start-Up Procedure
16 / PR-1247: Project Management of Change Procedure
17 / PR-1666: E & O Document, Drawing and Data Management Procedure
18 / PR-1692: PDO Document Retention Procedure
19 / PR-2066: Deviation from Standard and Procedure
20 / PR-2117: Engineering Project Data Control Procedure
21 / PR-2160: Pre Start-up Audit Procedure
22 / DEP 82.00.10.30-GEN (Engineering Information Specification) February 2012
3 Project Handover deliverables requirement
3.1 General Requirements
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.
Master Information shall be delivered to PDO as specified in the project specific PLIP:
· The Contractor shall deliver to PDO, complete final handover package electronically as specified
· Contractor shall receive notification from project IM Lead to produce Tier 1 Critical Documentation hardcopy and deliver the documentation to the field
· The Master Hardcopy delivered to the field shall be received by the OI Coordinator (OXO16x) who will sign the transmittal, stamp/sign the deliverables received and deliver them to the station
· Information retention shall be in line with CP-102: Corporate Document Management – CoP and PR-1692: PDO Document Retention Procedure
3.2 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, etc). They shall be delivered 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 work may be).
3.3 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 Information deliverable that shall be delivered to Operations at the end of an Engineering project.
Only Tier 1 Critical Documentation shall be produced in hardcopy format, and delivered to the station to support Asset operation, refer to PR-1666 for detailed lifecycle management procedure.