Long Intl The Importance of Proj Handover Docs PDF
Long Intl The Importance of Proj Handover Docs PDF
Andrew McIntosh
L ONG INTERNATIONAL
Long International, Inc. • 5265 Skytrail Drive • Littleton, Colorado 80123-1566 USA • Telephone: (303) 972-2443 • Fax: (303) 200-7180 • www.long-intl.com
The Importance of Project Handover Documentation
S. Andrew McIntosh
Table of Contents
1. INTRODUCTION ............................................................................................................................... 1
2. SCOPE ................................................................................................................................................. 2
2.1 KEY DOCUMENTATION ..........................................................................................................................2
2.1.1 Term Definition ................................................................................................................................2
2.1.2 Project Deliverable Requirement (PDR) Planning and Preparation ..................................................3
2.1.2.1 PDR Workshops ......................................................................................................................................... 3
2.1.2.2 PDR Schedule ............................................................................................................................................. 3
2.1.2.3 PDR Status Meetings: ................................................................................................................................. 4
2.1.3 Project Deliverable Requirements .....................................................................................................4
2.1.3.1 Systems Turnover Packages ....................................................................................................................... 4
2.1.3.2 Operations and Maintenance Manuals ....................................................................................................... 7
2.1.3.3 Fabrication, Installation and Verifying Documentation............................................................................. 9
2.1.3.4 Vendor Documentation............................................................................................................................. 10
2.1.3.5 Design Documentation ............................................................................................................................. 12
2.1.3.6 Engineering Databases.............................................................................................................................. 16
2.1.3.7 Emergency Response Documents ............................................................................................................ 17
2.1.3.8 Performance Test Data ............................................................................................................................. 17
2.1.4 Final As-Built Documentation ........................................................................................................ 18
2.1.4.1 Electronic Project Delivery Documentation ............................................................................................ 18
2.1.4.2 Electronic Prepared Documentation ......................................................................................................... 18
2.1.4.3 Project Deliverability Requirement: Final Delivery Format ................................................................... 19
3. CONCLUSION.................................................................................................................................. 20
List of Tables
Table 1 Sample of Document Type Electronic File Formats ................................................................... 19
This discussion of Project Documentation Requirements (PDR) sets forth a controlled and
auditable process to identify all of the manuals, procedures, documents, drawings, databases, and
indexes required for Installation, Hook-up, Commissioning, and Handover of Final Project
Documentation to the Owner for safe and sustainable Operability and Maintainability of a typical
Process Plant.
The PDR defines the minimum required documentation from an EPC Contractor to the Owner.
The PDR lists the documents by type, format, and source, and identifies the partitioning of the
documentation into specific categories.
It is recommended that the Contractor work jointly with the Project Leadership Team to develop
a PDR compilation and completion schedule to track and ensure timely delivery of Final
Project Documentation.
The scope of this PDR document describes the planning, preparation, and compilation requirements,
and the inclusion and development of the Master Document Register. The PDR includes the listing
of project documentation deliverables and milestones, identifies early project delivery
documentation for Installation, Hook-up, and Commissioning, and the required PDR delivery
formats. The PDR describes the partitioning process and listing of technical documentation into the
specific Project Documentation groupings.
One of the criteria by which a project is evaluated as successful is the quality of Handover
documentation. This article examines some of the more important aspects that should be
considered as part of the Project Deliverables.
There is voluminous information generated during the life of a major project and, in order for the
Client to access specific records, the Owner should consider establishing a Document Management
System (DMS) at the initiation of the Project. Moreover, the DMS should be designed such that
Project documentation from all sources (Pre-Final Investment Decision, Engineering, Procurement,
and Construction (EPC) works, Project Handover and Close Out) is prepared in formats that
facilitate easy import into the Owner’s DMS.
The planning and preparation of Project deliverable requirements typically should include
workshops, schedules, and status meetings.
Because documentation requirements are often accorded low priority in the EPC phase of a major
project, it is recommended that in addition to its inclusion in the Engineering, Procurement and
Construction (EPC) Invitation to Bid (ITB) documentation, the Project Leadership and
Contractor(s) hold a pre-bid PDR workshop and planning session to develop a clear understanding
of the PDR and to establish the strategy, mechanism, the timing of the PDR handover phases, the
tools to manage the compilation and, very importantly, review the formats for delivery of final
documentation from Contractor(s) to the Owner. This strategy will ensure that the Project
Handover requirements are adequately considered in the preparation of the EPC Contractor’s Cost
and Implementation Schedule.
Given its importance for future operations and archiving of Project information and data, a PDR
schedule should be developed jointly by the Project Leadership and Contractor at the initiation of
EPC Works. The PDR schedule should define each deliverable and record its expected and actual
delivery dates in a Master Document Register.
To ensure tracking of PDR Handover, Delivery Status Reports – detailing the progress of the
Handover documentation – should be issued monthly, with reports on the overall progress and
status for the Contractor/Subcontractor deliverables by grouping, including:
PDR status meetings should be scheduled periodically between the Owner and Contractor to
discuss the overall status of PDR and project activities affecting handover schedules. It is best
practice to include progress on Handover Documentation in the EPC Contractor’s Monthly Project
Report. This should be a permanent agenda item for the Owner-Contractor Monthly Progress
Review Meeting in order to ensure parallel development of the PDR in alignment with the
Owner’s expectations.
A brief overview of the PDR contents for each of the partitioned groups is discussed below. The
PDR partitions the project documentation into eight (8) groupings of information. Each bucket
contains specific recordkeeping content necessary to compile the final documentation.
Each Systems Turnover Package will contain the System Descriptions for all identified systems to
be installed, hooked-up, and commissioned. The Contractor will describe the system’s design
basis, function, description, and controls, and detail any special considerations. Each system will
be defined on Issued for Construction (IFC) Piping & Instrumentation Diagrams (P&IDs) and
Process Flow Diagrams (PFDs), where appropriate.
There should also be information on the Mechanical Completion and Commissioning activities,
Non-conformances, Deviations, Pressure Safety Valve (PSV) Certification, and Lifting Equipment
Certifications. This section will also include the Instrumentation Data sheets, Control Systems
data, Alarm management information, Process Safety System (PSS) information, Safety
Instrumented Systems (SIS), Safety Integrity Levels (SILs), Rotating Equipment test reports,
Vibration Baseline data, Equipment Vessel Installation reports (including QA/QC closure sheets
for Vessels, Heat Exchangers, Columns, Heaters, etc., signed by the authorized Operations
representative), Piping Isometrics, weld maps, and all installation activities. The documentation
will be mainly in hard copy (i.e., original certificates, PSV data cards and lifting equipment and
Installation reports).
It is readily seen that this level of documentation requires upfront agreement to avoid delays and
disputes that disaffect final EPC Contractor payments. The following are typical contents of a
System Turnover Package:
• System Description
• System Limits
• Associated Systems
• Performance Standards
Safety Assessment
• General Safety
• System Specific Safety
• Environmental Considerations
Completions
• Weld Maps should be available in the project Handover files but are generally
too large to include in a System Turnover Package
• Hydrotest Records by Test Packs
• Line Flushing/Blowout documents certified by Operations
• Bolt Torqueing Records
• Preservation and Maintenance Records
• Alignment Records
• No-load Motor Voltage, Current and Vibration records
• Preservation and Maintenance Records
• Commissioning Materials
• Commissioning Spares
• Special Tools and Test Equipment
Vendor Support
It is highly recommended that the definition of all systems in a process plant and the contents of
each System Turnover Package be agreed as early as possible in the EPC Phase so that the
System Mechanical Completion could be easily tracked and certified, including agreement on
Punch Lists, etc. Moreover, getting these protocols right will greatly enhance efficiency in the
Pre-Commissioning, Commissioning, and Start-up phases.
Operations and Maintenance (O&M) Manuals are central to training the Owner’s operating
personnel in advance of the commencement of Commissioning and Start-up activities. Operation
Manuals describe each system’s mode of operations and the Overall Plant Operating and
Maintenance philosophy. In addition to O&M manuals, Owners sometimes procure generic and/or
custom built Operator Training Simulator(s) to ensure that process Operators are well trained
ahead of Start-up.
General Description
• Plant Duty
• Listing of various Processes (Licensors) and Product Streams
• Design Basis for Plant Throughput
• Material Balance Information
• Description of Flow Parameters
• Utilities and Chemicals Requirements
• Vendor supplied Operations & Maintenance manuals (see typical Vendor
supplied data/information later at 2.1.3.4 in this article)
• Process Description
• Operating Philosophy and Normal Operation
• Discussion of Process Variables
• Discussion of the Effect of Process Variables on Process Control and
Product Quality
• Guidelines for Checking Process Conditions at the operating (control) panel
and in the field, and making adjustments to process control parameters
• Discussion of Unit, System, and Plant Process Control, with emphasis on
control loops
• Development and application of Process Trends to aid Operators
• Sampling and Laboratory Analyses and their application to process control
• Description of Electrical Systems and Equipment
• Description of Instrumentation
• Description of Utility Systems, including required inventories of chemicals or
other special materials
• Equipment sparing philosophy
Major Equipment
• Plot Plans
• Process Flow Diagrams (PFDs)
• Piping & Instrument Diagrams (P&IDs)
• Electrical One-lines
• Electrical Schematics
• Emergency Shut Down (ESD) Logic diagrams
• Cause and Effect diagrams
These PDR sections also focus on capturing deviations occurring from design/fabrication
requirements, specifications, etc., along with the reasons and the follow up actions taken to achieve
“As-Built” status. The Fabrication and Installation data record major occurrences during the
project fabrication and installation phases of the project. The data further provides the Owner with
key As-Built information identifying Areas of Concern, e.g., difficult repairs, special rigging or
tooling equipment requirements, and/or complex installation procedures for very heavy equipment
such as large reactors that can weigh in excess of 300 tons.
Most importantly, the Fabrication and Installation documentation reflects the As-Built status of
the installation.
On large projects, Vendors supply major equipment on a subcontracted procurement basis with the
EPC Contractor, who has the responsibility to install the equipment as part of the construction
process. In some instances, Vendors may also be required to supervise and even install their
equipment. Most certainly, Vendors play a very important part in the mechanical completion,
pre-commissioning, commissioning, and start-up of their packages and by extension the entire
process plant. They also provide hands-on training for Owner personnel, both at their factories
where witnessed tests take place and at the installation site.
It is, therefore, very important that Vendor Documentation be supplied in a form and of a quality
that complements the overall Project Documentation Requirement. As a first step, Owners must
ensure that the relevant procurement clauses in the EPC Contract reflect the Owner’s
understanding of the value of such information. The Owner must also ensure that the EPC
Vendor Documentation would typically be contained in several volumes (binders) that include, but
are not limited to, the following:
Introduction
Description
Procedures
User’s Manuals
Interchangeability List
Design documents for all aspects of the Plant design define the design bases of the plant and they
ensure that the design components fit together. When these documents are of Issued for
Construction (IFC) quality, they are used as references by external regulatory agencies, equipment
vendors and construction contractors. They are also of critical importance in the conduct of
This documentation is prepared during the detail engineering design activities and provides a
listing of all major changes/deviations from the design basis considerations, but also the reasons
and approvals behind the deviations. Also listed are any Areas of Concern that Operations should
be aware of during facility Operations and Maintenance (i.e., areas of high stress, areas of potential
high corrosion, and areas requiring frequent reviews and checks.)
During the execution of the contract, there is a systematic compilation of all design documentation
records generated. On a major Contract, several volumes of Design Data would be compiled
which typically reflect:
• Design Basis
• Functional Codes, Standards and Specifications
• Functional Description of Control and Monitoring System and Software
• Project Design Criteria
• Design Philosophies
• Design/Engineering Studies
• Design Reports
• Environmental Parameters
• Criticality Classification
• Corrosion/Cathodic Protection Design
Instrumentation Drawings/Diagrams/Documents
Structural Drawings/Diagrams/Documents
The contents of the engineering databases will be transferred from the Contractors as one final
delivery with all Subcontractors and Supplier/Vendor information integrated. The final delivery
format will be by native format in a Microsoft database. Engineering database indexes
may include:
Emergency Response Documents could include, but are not limited to, the following:
The type and extent of Plant Performance Testing is typically driven by the project specifications
or the EPC contract. A successful Performance Test – when accepted by the Owner – is also
usually linked to a key progress payment milestone and is the final test prior to handover to and
acceptance by the Owner.
The test team collects the necessary data and runs them through the facility correction model to
obtain preliminary results. Usually within a day, a preliminary test report or letter is generated to
allow the Owner to declare Substantial Completion and commence commercial operation.
The results from the analysis of all Plant data and product quality are usually available within a
couple of weeks, allowing the final Performance Test Report to be compiled and submitted to the
Client. This usually takes the form of a lengthy presentation by the EPC Contractor to the Owner
and the handing over of all test data and corresponding analyses in a hard copy and as well in the
approved electronic form.
The Contractor must certify that all Final Documentation in each of the foregoing areas reflects the
As-Built status of the facility by ensuring all changes – which occurred during the Installation,
Hook-up, and Commissioning – are captured and updated in the final Handover Documentation.
All drawings and technical documents delivered to the Owner will be in electronic format as
shown below:
USB or external portable hard drives are the preferred transfer media for electronic deliverables,
which should be seamlessly transportable into Owner’s Document Management System (DMS)
Compiled documents such as Manufacturer Record Books and Fabrication Record Books are to be
delivered in PDF format in addition to the hard copy.
Only certain document file formats are acceptable as project documentation. These file formats
include the following:
Table 1
Sample of Document Type Electronic File Formats
This table does not contain all possible associated or supported file types.
3. CONCLUSION
Once there is alignment between the Project and the Owner, the particular specifications of the
agreed PDR must be included in the Invitation to Bid (ITB) documentation for Engineering,
Procurement, and Construction (EPC) Works and emphasized during ITB Clarification meetings
that take place before bids are received by Owner. This will ensure that misalignment between the
Owner’s expectations and the Contractor’s understanding of its responsibility is minimized.
The EPC ITB should require the Contractor to include a detailed documentation plan and schedule,
which would be accorded appropriate weighting for Bid Evaluation. It should also be included in
the Contractor’s Work Breakdown Structure (WBS) for the EPC Works.
During the execution of EPC works, the Project Team and the Owner should ensure that the PDR
deliverables are being progressed to ensure achievement of the PDR Schedule Milestones. This
aspect cannot be overemphasized, as the author has seen several Projects fail to incorporate the
guidelines in this article, with the predictable outcome of disputes that require much time and many
resources to resolve. Getting PDR right contributes greatly to the safe and sustainable commercial
operation of Process Plants.