Facilities Systems Completion Planning and Execution

API RECOMMENDED PRACTICE 1FSC FIRST EDITION, JULY 2013

Special Notes

API publications necessarily address problems of a general nature. With respect to particular circumstances, local, state, and federal laws and regulations should be reviewed.

Neither API nor any of API's employees, subcontractors, consultants, committees, or other assignees make any warranty or representation, either express or implied, with respect to the accuracy, completeness, or usefulness of the information contained herein, or assume any liability or responsibility for any use, or the results of such use, of any information or process disclosed in this publication. Neither API nor any of API's employees, subcontractors, consultants, or other assignees represent that use of this publication would not infringe upon privately owned rights.

API publications may be used by anyone desiring to do so. Every effort has been made by the Institute to assure the accuracy and reliability of the data contained in them; however, the Institute makes no representation, warranty, or guarantee in connection with this publication and hereby expressly disclaims any liability or responsibility for loss or damage resulting from its use or for the violation of any authorities having jurisdiction with which this publication may conflict.

API publications are published to facilitate the broad availability of proven, sound engineering and operating practices. These publications are not intended to obviate the need for applying sound engineering judgment regarding when and where these publications should be utilized. The formulation and publication of API publications is not intended in any way to inhibit anyone from using any other practices.

Any manufacturer marking equipment or materials in conformance with the marking requirements of an API standard is solely responsible for complying with all the applicable requirements of that standard. API does not represent, warrant, or guarantee that such products do in fact conform to the applicable API standard.

Users of this Recommended Practice should not rely exclusively on the information contained in this document. Sound business, scientific, engineering, and safety judgment should be used in employing the information contained herein.

All rights reserved. No part of this work may be reproduced, translated, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from the publisher. Contact the Publisher, API Publishing Services, 1220 L Street, NW, Washington, DC 20005.

Copyright © 2013 American Petroleum Institute

Foreword

Nothing contained in any API publication is to be construed as granting any right, by implication or otherwise, for the manufacture, sale, or use of any method, apparatus, or product covered by letters patent. Neither should anything contained in the publication be construed as insuring anyone against liability for infringement of letters patent.

Shall: As used in a standard, “shall” denotes a minimum requirement in order to conform to the specification.

Should: As used in a standard, “should” denotes a recommendation or that which is advised but not required in order to conform to the specification.

May: As used in a standard, “may” is used to express permission or a provision that is optional. Can: As used in a standard, “can” is used to express possibility or capability.

This document was produced under API standardization procedures that ensure appropriate notification and participation in the developmental process and is designated as an API standard. Questions concerning the interpretation of the content of this publication or comments and questions concerning the procedures under which this publication was developed should be directed in writing to the Director of Standards, American Petroleum Institute, 1220 L Street, NW, Washington, DC 20005. Requests for permission to reproduce or translate all or any part of the material published herein should also be addressed to the director.

Generally, API standards are reviewed and revised, reaffirmed, or withdrawn at least every five years. A one-time extension of up to two years may be added to this review cycle. Status of the publication can be ascertained from the API Standards Department, telephone (202) 682-8000. A catalog of API publications and materials is published annually by API, 1220 L Street, NW, Washington, DC 20005.

Suggested revisions are invited and should be submitted to the Standards Department, API, 1220 L Street, NW, Washington, DC 20005, standards@api.org.

iii

Contents

Page

1. Scope 1

2. Terms, Definitions, and Abbreviations 1

   1. Terms and Definitions 1

   2. Abbreviations 3

3. Systems Completion Planning 4

   1. General 4

   2. Planning and Organization 4

4. Systems Completion Execution 5

   1. General 5

   2. Factory Acceptance Testing 5

   3. Verification of Mechanical Completion 5

   4. Pre-commissioning 6

   5. Commissioning 7

   6. Start-up 8

   7. Performance Testing 8

   8. Operations Assistance and Project Closeout 8

Annex A (informative) Turnover and Completions Package 9

Bibliography 11

Figure

1 Systems Completion Execution Process 5

Table

1 Systems Completion Planning and Organization Activities 4

v

Introduction

The systems completion process is the sequential activities within a project that verify and prove the construction, installation, integration, testing, and preparation of systems have been completed as designed, and thus, the facility is ready for start-up and operations. The systems completion process is designed to help prepare and manage the transfer of care, custody, and control of facilities under construction through appropriate certification and documentation, such that the details of progress are evident.

The systems completion process identifies two main phases in the project life cycle — planning and execution. The planning phase begins in front-end engineering design (FEED) and comprises evaluation/planning through the beginning of fabrication/construction. The execution phase (field activities) starts with factory acceptance tests (FATs) and ends with stable operations and acceptance of the facility by operations. Systems completion planning and execution activities overlap at detailed engineering and procurement and fabrication/construction.

For many years the petrochemical industry has prepared documents representing the combined knowledge and experience of the industry on various phases of petrochemical industry operations. In continuation of this effort, this recommended practice assembles in one document established processes, practices, and terminology to standardize systems completion planning and execution within the petrochemical industry.

vi

Facilities Systems Completion Planning and Execution

1. Scope

   This document applies to a wide variety of projects within the oil and gas industry excluding subsurface. Although intended for oil and gas industry, the process described in this document can be applied to other industries as well. It is intended that the processes and practices established herein can be adapted and applied from a single piece of tagged equipment to a complex petrochemical facility. The process described within is intended to be applied at a system level.

   
   

2. Terms, Definitions, and Abbreviations

2.1 Terms and Definitions

For the purposes of this document, the following terms and definitions apply.

2.1.1

“A” check sheet

A recorded verification that the equipment is mechanically complete.

2.1.2

“B” check sheet

A recorded verification that the equipment has been energized and function tested per the engineering design specification.

2.1.3

“C” check sheet

A recorded verification that a system commissioning activity has been completed.

2.1.4

commissioning

Group of energized and dynamic tests that constitute verification that each “system or subsystem” is fabricated, installed, cleaned, and tested in accordance with design and the systems are ready for start-up.

2.1.5

certificate

Documents that the system is complete for each step of the process.

2.1.6

mechanical completion

Milestone point in time when tagged items and equipment within a system is installed in accordance with all drawings, specifications, and documented in accordance with the inspection test plan and is ready for pre-commissioning.

2.1.7

handover

Internal transfer of assets based on either an area/module or systems determination between functional groups within the project organization

2.1.8

inspection and test plan

Document describing activities required to assure quality of manufacturing and installation.

2.1.9

inspection and test record

Record documenting manufacturing and installation of equipment.

1