Handover and As-built documentation · Web viewFormat of the Information (Document or Data) to be...

Petroleum Development Oman L.L.C.

Plant Lifecycle Information Plan (Handover and As-Built Documentation)

Document ID SP-1131

Document 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.

Petroleum Development Oman LLC Revision: 5.0

Effective: Aug-15

I Authorized For Issue – August 2015

of 21 SP-1131: Plant Lifecycle Information Plan (Handover and As-Built Documentation)

The controlled version of this CMF Document resides online in Livelink®. Printed copies are UNCONTROLLED.


Effective: Aug-15

II Revision HistoryThe 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 / Remarks

Revision 5.0 Aug-15 Kingsley Chime UEOI41

Spence, Jaqueline UEOI51

Maulana, Andre CTP34Chukwuma, Chinonso

UEOI12Morowei, Ebikpogba

UEOI23Shahaibi, Farid UEOI22

Khusaibi, Abdullah UEOI21

Singh, Vinay UEOI431Parthasarathy,

Veeraraghavan UEOI14Vezhaparamban, Rappai

UEOI411Mistry, Daxesh UEOI13Paramasivan, Suresh

Kumar UEOI15Patel, 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 BulushiUEOI/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)




Effective: Aug-15

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




Effective: Aug-15

TABLE OF CONTENTI Authorized For Issue – August 2015........................................................2II Revision History...............................................................................3

1 INTRODUCTION.....................................................................................61.1 Purpose..........................................................................................61.2 Changes to this Specification.............................................................61.3 Step-out Approval.............................................................................61.4 Scope.............................................................................................6

2 PROCESS DESCRIPTION........................................................................72.1 General Description..........................................................................72.2 Information Deliverables Management.................................................72.3 Definitions.......................................................................................82.4 Abbreviations...................................................................................82.5 Related CMF Business Control Documents..........................................9

3 PROJECT HANDOVER DELIVERABLES REQUIREMENT.........................103.1 General Requirements....................................................................103.2 Master Information Deliverables.......................................................103.3 Critical Documents & Data...............................................................103.4 Manufacturers (Vendor) Record Book (MRB).....................................103.5 Plant Operating Manual...................................................................113.6 Commissioning Work Packs.............................................................113.7 Project Change Control...................................................................123.8 Document Classification..................................................................123.9 Storage of Information.....................................................................123.10 Master Information Retrieval and Control...........................................123.11 Pre-Start-up Audit (PSUA) Documentation.........................................123.12 As-Building and TA Approval............................................................133.13 Quality Assurance..........................................................................133.14 IM Kick-off Form.............................................................................13

4 ROLES AND RESPONSIBILITIES...........................................................144.1 Project Engineer/Manager...............................................................144.2 Project Discipline Engineer..............................................................144.3 Design Integrity (Project) IM Lead.....................................................144.4 Contractor.....................................................................................144.5 PLIP Template Description of Fields and Review Guidelines................164.6 Names of Discipline Engineer...........................................................19Appendix 1: Plant Lifecycle Information Plan (Template).............................21Appendix 2 MRB Content Structure..........................................................21Appendix 3 IM Kick-off Form....................................................................21Appendix 4 User Feedback Form.............................................................21




Effective: Aug-15

1 INTRODUCTIONProject 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 PurposeEvery 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 SpecificationThe 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 ApprovalShould 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 ScopeThe 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.




Effective: Aug-15

2 PROCESS DESCRIPTION 2.1 General DescriptionI. 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.




Effective: Aug-15

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, etcInformation 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 DesignAIC Asset Information CenterAI-PSM Asset Integrity – Process Safety ManagementCCMS Certification and Completion Management SystemCMMS Computerized Maintenance Management SystemEDS Engineering Design System EDMS Electronic Document Management SystemEIS Engineering Information SpecificationEOIM Engineering and Operations Information ManagementFCP Facility Change ProposalIFR Issued for ReviewIM Information ManagementIOM Installation, Operation and Maintenance ManualITT Invitation To TenderMRB Manufacturers Record BookPCAP Project Control and Assurance PlanPCC Project Close-out CertificatePE Project EngineerPLIP Plant Lifecycle Information PlanSoF Statement of FitnessPIN Project Initiation NotePOM Plant Operating Manual




Effective: Aug-15

PDMS Plant Design Management SystemPSUA Pre-Start-up AuditRLMU Redline Mark-up DrawingsTA Technical AuthorityVDRL 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 DocumentsThe 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 Assets3 CP-117: Project Engineering Code of Practice4 SP-1074: Preparation of Plant Operation Manuals5 SP-1122: Specification for Project Quality Plan6 SP-1131: Handover & As-Built Documentation (Plant Lifecycle Information Plan)7 SP-1134: General Specification for Detailed Engineering of Oil & Gas Facilities8 SP-2065: Document Management In Engineering Projects and Operations9 SP-2113: Specification for Commissioning and Start-Up10 SP-2142: Engineering Project Data Specification11 SP-2144: Engineering Project IM SoW12 PR-1052: Preparation and Updating of Station Plant Operating Manuals13 PR-1150: Project Close-out Procedure14 PR-1159: Commissioning Procedure15 PR-1169: Initial Start-Up Procedure16 PR-1247: Project Management of Change Procedure17 PR-1666: E & O Document, Drawing and Data Management Procedure18 PR-1692: PDO Document Retention Procedure19 PR-2066: Deviation from Standard and Procedure20 PR-2117: Engineering Project Data Control Procedure21 PR-2160: Pre Start-up Audit Procedure22 DEP 82.00.10.30-GEN (Engineering Information Specification) February 2012



http://sww1.pdo.shell.om/dept_applications/Infrastucture/IMandT/TAXI/cmf/index.htm


Effective: Aug-15

3 PROJECT HANDOVER DELIVERABLES REQUIREMENT3.1 General RequirementsWhen 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.

3.4 Manufacturers (Vendor) Record Book (MRB)

The MRB is compound document containing distinct document types and identification number. As shown in the table below, the electronic version of these document types shall be delivered as individual files to the parent MRB, while general assembly and presentation of electronic and hardcopy shall follow the structure shown in appendix 2.



http://sww3.pdo.shell.om/livelink/livelink.exe?func=ll&objAction=download&objId=6545293




Effective: Aug-15

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 operations and maintenance of the equipment. The MRB shall be supplied in electronic format with only one clean copy produced in hardcopy and delivered to the field.

3.5 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 project, an assessment of the impact on the existing POM shall be undertaken, and updates (when required), shall be made directly to the master POM held by AIC, rather than creating an addendum file, refer to section 2.2. 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 .

3.6 Commissioning Work Packs 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, retained 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) GU-623: Project Completion Management System CMS Guideline





http://mus-As-330/livelink/livelink.exe?func=ll&objAction=download&objId=95388




Effective: Aug-15

3.7 Project Change ControlNotification 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 and PR-1153: Field Trouble Reporting Procedure for more information.

3.8 Document Classification This standard defines document types and assigns numeric codes (refer appendix 1) to each type, to aid their reference and retrieval from IM system.

3.9 Storage of Information

Electronic version of Information delivered at the end of a project shall be stored and maintained in AIC while hardcopies of Tier 1 Critical Documentation and MRBs shall be delivered to the respective field. Project hardcopy information required shall be delivered to AIC (central archive). Similarly, the EDMS workspace shall be handed over to Design Integrity IM Team in UEOI; refer to PR-1666.

3.10 Master Information Retrieval and Control

Master Information required for Operating, Maintenance and Design Integrity is controlled electronically, and becomes uncontrolled when printed unless stamped with “Controlled Hardcopy” and wet signed, or printed with watermark, etc.

During a project, construction deliverables in hardcopy shall be printed from the project IM system 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 FCP of existing asset) shall be retrieved from AIC master IM system.

3.11 Pre-Start-up Audit (PSUA) Documentation

Documents identified in the project PLIP 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 demonstrate that an information handover assurance review has been undertaken on a project before progressing with PSUA activities.

Refer to PR-2160: Pre Start-up Audit Procedure for general requirement and guidance for PSUA.

3.12 As-Building and TA Approval

TA review/approvals are required during detailed design and engineering leading to AFC deliverables. Any change to the AFC package requires appropriate TA approval before being implemented.







Effective: Aug-15

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.13 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.14 IM Kick-off FormThe project shall utilize the IM Kick-off Form (appendix 3):

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




Effective: Aug-15

4 ROLES AND RESPONSIBILITIES

4.1 Project Engineer/Manager The overall Accountability of ensuring that PLIP activity is completed at the beginning of the project (FEED/Detail Design/Execution). He shall:

Identify IM resource to cover the project scope. Confirm impact of a data type (e.g PEFS) modification on other data system like SAP & POM Convene an integrated session to customize PLIP for the project scope when required. Endorse the project specific PLIP for implementation

4.2 Project Discipline Engineer Utilize the generic PLIP (appendix 1) and filter into discipline deliverables scope.

Work with project IM Lead to customize and validate existing data entries as it affect work scope, ensuring that all PCAP deliverables are incorporated.

Endorse the project specific PLIP (as required by DCAF). When required, participate in joint discipline customization of PLIP Review and approve discipline Information generated in project as required in PLIP

4.3 Design Integrity (Project) IM Lead Ensure contractor understands the information requirement in order to generate the project

PLIP. Provides electronic copy of the master information, including identification of any other

project using the same master. As part of project initiation, ensure PE confirms the impact of modification of PEFS for

example, on other data system like SAP, POM, etc Ensure compliance with IM procedures and specifications. Work with PDO partners developing or modifying information to ensure adequate internal

review and approval. Ensure that information specified in a project PLIP is effectively developed and delivered

ensuring that it meets this specification for handover AIC. Conduct contractor information handover assurance review in line with functional assurance

plan. At the end of project, archive the EDMS workspace of project information deliverables.

4.4 Contractor Propose an IM resource for project and agree resource capability with Design Integrity IM

Lead before assigning responsibility for all or part of information management activities. Produce a project PLIP as part of project initiation and kick-off, (see section 2.1). Develop the MDR and associated plan showing key information development milestone

dates (Issued for Review, Approved for Design and Approved for Construction, etc). These milestones shall be measured and reported as agreed with the Design Integrity IM Lead as one of the project KPIs.

Ensure adequate internal review, checking and approval of information before delivering to PDO.




Effective: Aug-15

Handover electronic information to Design Integrity IM Lead as contained in MDR. Receive notification from project IM Lead and produce master hardcopy of Tier 1 Critical

Documentation.




Effective: Aug-15

4.5 PLIP Template Description of Fields and Review Guidelines

COLUMN NAME DESCRIPTION / CLARIFICATION ACTIONS REQUIRED

SOURCE

ORIGINATOR The party who will produce the document --- either a PDO entity or 3rd party or Contractor or Supplier. Discipline Lead to specify

PROJECT FOCAL POINT The name of the PDO team member who is responsible for the document (prepares or reviews or approves). Discipline Lead to specify

DISCIPLINE_CODE Standard "Discipline Code - Discipline name" as defined in DEP82.00.10.30-Gen Engineering Information Specifications.

Discipline Lead to verify what is selected by IM team and to consult with IM team if it should be changed.

INFORMATION DESCRIPTION

INFORMATION REQUIRED (DOCUMENT & DATA)

A typical titles, type or category of documents and data to be delivered at various stages through the project lifecycle.

Discipline Lead to verify the default value (listed by IM team).

DOCUMENT_TYPE_NAMEStandard "Discipline-Document Type Code + Name" and "Descriptions" defined in DEP82.00.10.30-Gen Engineering Information Specifications. Standard classification on document types facilitates document repository in EDMS (standard folder structure in Livelink) and to make cross reference to the Record Management requirements (e.g. retention).

Discipline Lead to verify the default value (specified by IM team).DOCUMENT_TYPE_

CODE

POSSIBLE TITLES_ AND_TYPE_DESCRIPTION Additional description of document types No action

REFERENCESReference to DEP or other samples/examples which define minimum requirements or level of details regarding the technical contents of the Document.

Discipline Lead to specify or verify the default values. Preferably to refer to a DEP or a Project Specification. As the minimum, the Discipline Lead should be able of providing a sample/example from previous projects.

PROJECT SPECIFIC NOTES Notes to describe specific project requirements or clarifications on the information (document or data) listed.

Discipline Lead to add specific special notes




Effective: Aug-15

BASIC DOCUMENT

PROPERTIES

SECURITY_CLASSIFICATIONDocument Security Classification per PDO guidelines (Unrestricted, Restricted, Confidential, Most Confidential) --- various handling procedures are required

Discipline Lead to verify the default value (specified by IM team).

RELATED_OBJECTS

Related objects of the Document to facilitate navigation from the object to the documents. An object can be an Asset type (in Plant Asset Hierarchy --- Site, Plant, Process_Unit, Equipment, Tag, Model_Parts) or other Document such as a Purchase Order.


DURING_PROJECT_FORMATFormat of the Information (Document or Data) to be delivered during the project for eview/approval/information (Paper, MS Word, MS Excel, MS Access, Adobe Acrobat, AutoCAD, etc.)


AFTER_PROJECT_FORMATFormat of the Information (Document or Data) to be delivered during handover to Operation (Paper, MS Word, MS Excel, MS Access, Adobe Acrobat, AutoCAD, etc.)


REQUIRE_FIELD_CONTROLLED_HARDCOPY

With respect to project scope, identify from the Critical Documentation list of CP-115, which Information is required to be physically available in the field for Operations of the facility.

PE verifies from Operations, default values (Yes or No).

AFTER_PROJECT_CATEGORYCategorization/value of the Information (Document or Data) for PDO after handover from project to operation (Essential, Legal, Desirable) --- different requirements on repository and retention


RETENTION_PERIOD Based on PDO document group retention guidelines (asset life, 2 yrs, etc).


DOCUMENT DELIVERY REQUIRED

PER PROJECT PHASE

CRITICAL_ DOCUMENTATIONCritical Information (document and data) deliverables as defined in CP-115: Operation of Surface Product Flow Asset. This is the minimum deliverables that is required for Operating Integrity.

Discipline Lead to verify the default value (specified by IM Team).

DCAF Control (Identification Number)

Document is a deliverable of PCAP (Project Control and Assurance Plan). Those "Yes" deliverables subject to PCAP requirement.

Discipline Lead to verify the default value (specified by IM team) against the latest signed PCAP-discipline list.

(SELECT) REQ_FOR_ CONCEPT SELECTION

Will the Information (documents & data) be delivered as part of the concept selection?

Discipline Lead to verify the default values (Yes or No).

(DEFINE)REQ_FOR_PROJECTSPECIFICATION/FEED

Will the Information (documents & data) be delivered as part of the project specification package (FEED)?


(DEFINE) REQ_FOR_ DETAILED_ DESIGN

Will the Information (documents & data) be delivered as part of the detailed design package?


(EXECUTE) REQ_FOR_ PSUA AND PRE- COMMISSIONING

Will the Information (documents & data) be required to support PSUA, Pre-commissioning and Commissioning/Start-up





Effective: Aug-15

/ COMMISIONING (Flawless start-up initiative)? REQUIRED_FOR_FINAL_HANDOVER

Will the Information (documents & data) be required as part of the handover package to PDO?


REQUIRED_HANDOVER_STATUS (ASB or FINAL)

Will the Information (documents & data) deliver as As-built (ASB) or Certified FINAL (revision of information not requiring As-Building)? If value is no, then information not required.

Discipline Lead to verify the default values (ASB, FINAL or No).

OTHERS

REQUIRE_PDO_REVIEW/APPROVAL

This field was left blank to allow project customization in line with project strategy. It should be populated as part of MDR development, to capture PDO's review requirements on documents produced by others (contractor / suppliers) per the Document Type: IFR=Issue For Review; IFA=Issue For Approval; IFI=Issue For Information; No=No review required.

Discipline Lead to specify or verify the default values.

FINAL RED-LINE CHECKING

Highlights document types in which RLMUs may be generated. At the end of project, PDO focal point shall check As-Built produced against “RLMU”, to confirm that As-Built produced is a true reflection of constructed works.

Resource typically a commissioning Engineer but the Project Engineer to agree resource with Operations if different

FINAL OWNER/STATUS

Who is the final owner/status of the deliverable after handover? Typically, ownership of Critical Documentations is with the Asset Manager, while other deliverables are stored electronically in a secured EDMS location for future reference.

Discipline Lead to specify or verify the default values.

COMMENT General comments from IM team or Discipline Lead

4.6 Names of Discipline EngineerThe names of respective discipline engineer assigned to support the project scope (full time or part time) are as follows:




Effective: Aug-15

DISCIPLINE_CODE DISCIPLINE DESCRIPTION

DISCIPLINE LEAD (Focal Point in PDO Project Team) Remark

Define-FEED

Detailed Design Execute

AA Management and Project Engineering

Project execution plan, basis of design, organization, authorities. 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 /

FoundationSoil properties, shallow hazards, piles, suction piles, anchors, mud 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.HE Environmental Environment-related topics. HH Health Human and animal health. HP Security Prevention of espionage, sabotage, intellectual property leakage, attack

or unauthorized handling.

HS Safety Technical Safety-related topics. 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 & Optimization.

For Process Control and Optimization discipline related deliverables. Distributed control systems, PLCs, process control logic

IN Instrumentation Instruments and instrument systems JA Information

ManagementContent management, Data, Document and Knowledge management, Procedures, Specifications, Standards.

KA Information Technology

IT Infrastructure, hardware, software, applications

LA Pipelines Line pipe, stability, hydraulics, installation, commissioning.




Effective: Aug-15

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

MaintenanceThe branch of engineering that deals with equipment reliability.

OA Operations Readiness for production, marine, subsea, logistics, supply base, shutdown, etc.

PF Fluid Flow Assurance

Includes all issues important to maintaining the flow of oil and gas from reservoir to receiving facilities.

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 Corrosion

Materials, corrosion and coating issues across multiple disciplines.

TA Telecommunication Radio communication, satellite and Cable communication, etc. ZT Production

TechnologyEverything related to Production Technology

ZP Petrophysics. Everything related to PetrophysicsZR Reservoir

EngineeringEverything related to Reservoir Engineering

ZV Vendor All equipment deliverables ZW Well Engineering Everything related to oil and gas wells.




Effective: Aug-15

Appendix 1: Plant Lifecycle Information Plan (Template)

Appendix 2 MRB Content Structure

Appendix 3 IM Kick-off Form

Appendix 4 User Feedback Form



Handover and As-built documentation · Web viewFormat of the Information (Document or Data) to be...

Documents

Transcript of Handover and As-built documentation · Web viewFormat of the Information (Document or Data) to be...