Requirements: Completion methodology Classification: Internal

Requirements Classification: Internal

Status: Relevant
Version: 2.03

TR2394 Completion methodology

Project development

Requirements, TR2394, Version 2.03,

Owner: Cecilie Aarskog Bekkeheien

Author: Arne Oddvar Veland

Document replaces version 2.02

Relevant versions:

2.01 (2017-06-29 15:45)

2.03 (2019-05-28 11:54)

Project development, Requirements, TR2394, Version 2.03

Page 1 of 16
Requirements: Completion methodology Classification: Internal

1 Objective, target group, provision, HSE, principles and responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Provision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 HSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.5 Principles of the Completion methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.6 Responsibility and delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.6.2 Company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.6.3 Contractor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Concept planning phase (DG1 – DG2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Definition phase (DG2 – DG3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2 Organisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3 Plan for preparatory activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Execution Phase (DG3 – DG4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1 Organisation – Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.2 Organisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.1 Company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.2 Contractor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 Information flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3.2 Flowchart Green Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3.3 Flowchart Brown Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.3.4 Site Query handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4.1 General requirements related to progress reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4.2 Weekly reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.5 Field Check Packages (FCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.6 Engineering Work Package (EWP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.7 Work Orders (WO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.7.1 Buffer of Work Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.8 As-built mark-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.9 Relevant information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5 Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2 Changes from previous version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.3 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Project development, Requirements, TR2394, Version 2.03

Page 2 of 16
Requirements: Completion methodology Classification: Internal

This document and its content is for authorised company use only.

1 Objective, target group, provision, HSE, principles and responsibility

1.1 Objective

The objective of this document is to describe the principles of the Completion methodology including the
associated roles and responsibilities for the tasks involved.

1.2 Target group

The main target group is the project organization. This document is applicable for Investment projects.
Operational projects should not use this document unless the execution strategy makes this necessary.

1.3 Provision

Provision is made in Equinor Management System (FR05 Project Develoment).

1.4 HSE

SR-46685 - Plant / Platform Operations are the principal enterprise executed by the Plant or Platform
Manager. The work shall be executed in accordance with governing procedures described in Company
management system.

1.5 Principles of the Completion methodology

SR-46687 - The main principal of the methodology is that the work is performed by an integrated
organisation consisting of Company and Contractor personnel. Contractor shall provide qualified personnel
to the Completion team, except Completion Manager, Completion Preparation Manager and
Commissioning Manager.

1.6 Responsibility and delivery

1.6.1 General

SR-46690 - The Completion organisation is a part of the Company Project Team, and is responsible for
administration, planning, preparation and execution of the work. The Completion Manager shall report to
Project Manager. Contractor’s work in the Completion organisation shall clearly be stated in the Contract.

SR-46691 - When the project is using another contractor for any assistance, such as scaffolding etc., in
performing the work then the/these contractor(s) shall be available for a familiarisation with the main
contractor.

Project development, Requirements, TR2394, Version 2.03

Page 3 of 16
Requirements: Completion methodology Classification: Internal

1.6.2 Company

SR-46693 - Company’s tasks and responsibility:

Provision of Completion Work processes.

Provision of Completion tools.
Completion Preparation
Commissioning, ref. TR2393
Cooperation with Operations both on completion site and at Operation home office.
Installation plan with priorities and milestones

1.6.3 Contractor

SR-46695 - Contractor’s tasks and responsibilities:

Provide personnel to the Completion organisation for planning, preparation and execution of the
Completion work
Provide tools and equipment for the execution of the work
Execute installation and mechanical completion, ref. TR2148 and TR2149
Quality of the work performed
Provision of detailed work procedures and tools
Procurement and delivery of all materials
Detailed installation schedule

2 Concept planning phase (DG1 – DG2)

SR-46697 - Prior to DG2, use of the EPCic contract shall be evaluated and concluded. The PEOPS must
reflect such frame conditions.

3 Definition phase (DG2 – DG3)

3.1 General

SR-46700 - The Completion Manager shall be mobilised after passing DG2, to develop the completion
strategy (ref. GL0417) and contractual requirements. Based on the project complexity, size and schedule,
the Completion Manager shall establish a mobilisation plan for the Completion organisation.

Project development, Requirements, TR2394, Version 2.03

Page 4 of 16
Requirements: Completion methodology Classification: Internal

3.2 Organisation

SR-46702 - The Completion Manager shall report to the Company Project Manager.

3.3 Plan for preparatory activities

SR-46704 - A plan for the completion preparatory work (ref. GL0513) shall be developed and resources
assigned accordingly. The Completion Manager shall assist engineering to follow up the FEED contractors
to ensure that the installation methods minimise the scope at Completion Site.

4 Execution Phase (DG3 – DG4)

4.1 Organisation – Principles

SR-46707 - The Company organisation at Contractor premises shall be organised to ensure full support to
Completion Manager at Completion Site. See the organisation chart in figure 4.1 (Company).

SR-46708 - A HSE resource shall be available for the Completion organisation. At Completion Site the HSE
resource shall be available either as a part of the Company Project organisation or as a dedicated resource
in the Operations organisation.

SR-46709 - The Company organisation at Completion Site shall be organised to ensure execution of the
construction, commissioning and hook-up activities. A typical organisation at Completion Site is illustrated in
figure 4.1 (Completion Site).

Commissioning is a part of the Completion organisation. Commissioning Engineers (Completion Site) have
a dotted line to Commissioning Manager (Company, “home office”) to indicate report line for all technical
matters.

Installation Manager, who is the Contractor representative in the organisation, has a dotted line to
Contractors organisation, to ensure necessary communication between Contractors organisation and
Contractors site personnel.

Completion Site Manager will have a coordination responsibility for the marine / pipeline activities at
Completion Site

SR-46713 - ISO services and personnel (Corrosion Protection/Passive Fire Protection, Scaffolding
works/Scaffolding material, Insulation) shall be integrated into Contractor´s project and site organization.

Project development, Requirements, TR2394, Version 2.03

Page 5 of 16
Requirements: Completion methodology Classification: Internal

Figure 4.1 Typical organisation of Completion in the Execution Phase.

4.2 Organisation

4.2.1 Company

Completion Manager: Responsible for administration, preparation and execution of the completion work
according to Company´s governing processes and documents. Report to Company Project Manager

Completion Preparation Responsible: Responsible for manage and execute completion preparation
activities according to GL0513. Report to the Completion Manager

Commissioning Manager: Responsible for establishing Commissioning plan included estimates, for dividing
scope of work into relevant comm. packages. Further organize and manage all Commissioning activities
and to exercise take-over of commissioning packages to site owner. Reports to the Completion Manager.

Completion Site Manager: Responsible for planning and prepare the site activities for execution, site
manning and needed temporary facilities. Further to ensure required HSE standard of all site work to
executed. Reports to the Completion Manager.

Project development, Requirements, TR2394, Version 2.03

Page 6 of 16
Requirements: Completion methodology Classification: Internal

4.2.2 Contractor

Completion planner: Responsible for planning all site activities, MC activities and Commissioning. Ensure
optimisation, include required HSE standards and improvement in the planning. Prepare and issue periodic
reports to the project. Reports to the Completion Manager

Vendor/POB coordinator: Manage call-out for personnel on site (include booking and travel of personnel).
Coordinate meetings for HSE requirements. Reports to Completion Planner or Completion Manager.

Mechanical Completion coordinator/engineer: Prepare and maintain definition of the MC and Preservation
scope for contractors and suppliers. Process MC documentation and update Procosys with correct MC
status and to verify MC and Preservation status until handover RFCC. Reports to Completion Preparation
Responsible.

Commissioning engineers: Coordinate and performing commissioning activities of relevant system and
disciplines. Ensure coordination with engineering, construction and vendor assistance. Reports to the
Commissioning Manager.

Work Preparation Lead: Active role in participating in the Project team. Leading the work preparation,
verifying all needed documentation for the work orders, with needed quality and deliveries on site.
Supporting site organisation with status reporting and coordinate Site Query´s. Reports to the Completion
Manager.

Material Coordinator: Coordinate and expedite all activities in regards to material and logistics. Report
status, follow-up and coordinate all activities according plan.

Construction Manager: Responsible for coordinating all construction activities and personnel on site and
conducting HSE and efficient execution of the work and to ensure needed cooperation with engineering and
completion. Further responsible for progress reporting and deviations on site. Reports to Completion
Manager or Completion Site Manager.

Completion Site
Installation Manager: Coordinate Contractors personnel offshore and supervise the installation work for all
disciplines. Responsible for progress reporting and deviations.

Field Engineers: Ensure knowledge to scope of work and work preparation for site and established quality
requirements. Assist MC and foremen in planning and execution of the work. Responsible for coordination
of Site Queries between site and home office. Reports to the Completion Site Manager

MC engineers: Lead and coordinate MC activities on site and ensure MC and Preservation activities
executed according to plan and spesifications. Update Procosys with needed status reporting. Reports to
the Completion Site Manager.

Foremen: Manage and coordinate construction work and work teams within disciplines. Ensure that the
work is executed in HSE and efficient way and in right quality. Participate if needed in the physical work as
a leading role. Reports to the Construction Site Manager

Project development, Requirements, TR2394, Version 2.03

Page 7 of 16
Requirements: Completion methodology Classification: Internal

4.3 Information flow

4.3.1 General

The Completion Work Preparation Lead is responsible for interfaces between Completion and engineering
regarding Field Check Packages (FCP)’s,Engineering Work Packages (EWP)’s and related documents

4.3.2 Flowchart Green Field

SR-46738 - For a green field development project, the flow of information between engineering and
Completion shall be as shown in Figure 4-2.

Figure 4-2 Information flow in a green field project

Project development, Requirements, TR2394, Version 2.03

Page 8 of 16
Requirements: Completion methodology Classification: Internal

4.3.3 Flowchart Brown Field

SR-46741 - Brown field project require thorough field/operation-check due to the complexity to integrate a
new project into an existing plant / platform. Field Check Packages (FCP) shall be prepared by Contractor
and a Field Check Review performed by Contractor in cooperation with Completion and Operation. Field
Check Packages shall be developed for the total Completion Site scope of work, Based on the FCP’s,
Contractor shall agree on the detail level and need to develop EWP’s for the total Completion Site scope of
work, ref. chapter 4.4 and 4.5.

The Completion Supervisor, Construction Supervisor and field engineers shall be involved in the
engineering phase of the project to familiarise themselves with the design.

Completion shall participate in constructabillity reviews.

For a brown field project, the flow of information between Contractor and Completion shall be as shown in
4-3.

Figure 4-3 Information flow in a brown field project

Project development, Requirements, TR2394, Version 2.03

Page 9 of 16
Requirements: Completion methodology Classification: Internal

4.3.4 Site Query handling

SR-46747 - All Site Queries (SQ) shall be sent and followed up by using ProCoSys.(ARIS R-90163)

SR-46748 - If an accepted query generates physical work at site, the query shall be registered against a
Work Order and time estimate updated. If the query generates new work not covered by any Work Order, a
new Work Order number shall be included in the reply. See applicable guideline GL0321.

4.4 Reporting

4.4.1 General requirements related to progress reporting

SR-46751 - All progress reporting shall be based on Work Orders for the Completion Site work.

SR-46752 - The Work Order module in ProCoSys shall be used for this purpose.

SR-46753 - The progress monitoring system shall be capable of separately reporting status/progress by:

Work Order
System/subsystem
Discipline
Category of Work
Milestones

Weekly progress report form the basis for project KPI`s. Template for making weekly progress report is
placed in ProCoSys Work Order module.Progress monitoring and reporting will be based on physical
progress of Construction and Commissioning Direct Work.

4.4.2 Weekly reporting

SR-46756 - The Foremen/Supervisors shall report weekly progress on Work Orders to the Completion
team.This progress, along with expended man-hour report from Contractor, will be the basis of the weekly
status report showing e.g. last week’s growth, progress, productivity etc.

4.5 Field Check Packages (FCP)

SR-46758 - Company and contractor shall agree on the detail level and need for FCPs. If FCP is chosen,

SR-46759 - Contractor shall develop multi discipline Field Check Packages (FCP) for all aspects of the
Offshore Work including demolition and removal work. Scope Elements and Tasks should be basis for the
structure of FCPs. Contractor shall make the necessary investigations on the Platform to ensure quality and
a good basis for all FCPs. The sequence and the dependencies in the modification work shall be described
in the FCP in order to give input to planning and monitoring progress of the Offshore Work. Contractor shall
develop a FCP schedule that includes all FCP’s.

SR-46760 - Company and contractor must agree on the detail level of the FCPs.

Project development, Requirements, TR2394, Version 2.03

Page 10 of 16
Requirements: Completion methodology Classification: Internal

Contractor shall strive to minimize the total number of FCPs by seeking to combine natural groups of work
within and across the scope elements, and to find more suitable formats for selected FCPs. Contractor shall
seek to hold preview meetings of FCPs to shorten review time.

A FCP shall as minimum include:

The FCP shall present a clear description for installation method. Use animation video if relevant.
Description of the work for all relevant disciplines including evaluation of condition of existing
facilities.
The FCP shall present clear information on the risks associated with work and HSE checklists.
Involved EWPs.
Attachments as drawings, 3D plots and pictures.

SR-46763 - Contractor shall produce a separate FCP covering all SAS related modifications, if relevant.

SR-46764 - Contractor shall during the engineering phase prepare and present Field Check Packages
(FCP) for commenting to Company. The FCPs shall be completed and accepted by Company before a
Global Design Confirmation can be performed.

SR-46765 - Contractor shall give written response to Company’s Review comments for the FCPs.

4.6 Engineering Work Package (EWP)

SR-46767 - Company and contractor shall agree on the detail level and need for EWPs.

SR-46768 - The EWPs shall present clear information on the risks associated with work, and contain the
necessary work description for execution of the work.

A EWP shall as minimum include (if chosen):

Description of the work and detailed work procedures for installation including Subcontractor work
Risks associated with work and/or special safety precautions
Material requirements, Material Take Off (MTO) and logistics.

SR-46771 - The required verification of available space and material handling shall be done in addition to
offshore surveys, by use of PDMS, laser scanning and / or electronic measurement prior to establishing a
EWP or detail engineering.

SR-46772 - Contractor shall develop a EWP plan that includes all EWPs with defined scope and
corresponding activities in fabrication, installation and commissioning. The plan shall as far as possible take
the completion of systems into account. Company will during the engineering give the definition of
commissioning packages based on P&ID to Contractor. Engineering activities in the level 4 plan shall be
related to the commissioning packages.

SR-46773 - Contractor shall include ISO personnel to work integrated in his project team to assist in
preparing relevant EWPs and Work Orders.

Project development, Requirements, TR2394, Version 2.03

Page 11 of 16
Requirements: Completion methodology Classification: Internal

Company aims to simplify and improve the preparation of the FCPs, EWPs and the WOs. The requirement
for single discipline EWPs may be deviated from to enable system orientated EWPs

4.7 Work Orders (WO)

SR-46776 - Contractor shall be responsible for developing Work Orders (WO) for all Offshore Work based
on FCP’s, EWP’s and detail engineering. Company’s estimating norms (ref. GL0329) shall be used as basis
for the WO’s, and the estimating norms shall be integrated in Contractor's system for use in all estimates
regarding Work Orders for Equinor. If Contractor choose to use own system for work preparation, all WO
data shall daily be transferred to Procosys.

SR-46777 - The Work Orders shall contain the necessary installation method and work description for
execution. Information of the risks associated with the work shall be included. Contractor shall allocate all
necessary materials to Work Order (SAP WO).

SR-46778 - Contractor shall develop a WO plan that includes all WO’s with defined scope and
corresponding activities. The WO plan shall be system based and coordinated with Company’s
commissioning plan and strategy.

SR-46779 - Procosys shall form a basis for offshore construction and completion progress report.

SR-46780 - If the work order is generated in the contractor system, the WO data (ref. table below) shall be
communicated to Equinor via the TIE portal, either via the web services or DropPoint. For the latter, a
special Excel template exists for the Workorder type classes.

Attribute Value / Comment

NORMSHEET String. Norm estimation table name. Required
NORMROW String. Row in estimation table. Required
NORMCOLUMN String. Row in estimation table. Required
QUANTITY Number. As of the unit of the norm. Required
DESCRIPTION String. Any description/remark.
CATEGORY String. Category (according to library). STD is default.
TRADE String. Trade (according to library)
MULTIPLIERS String. Named multiplier (according to the estimation manual, semicolon separated if more than
one).

4.7.1 Buffer of Work Orders

SR-46783 - A minimum of 8 weeks offshore direct work shall be ready for execution at mobilisation
offshore, and this buffer shall be maintained onwards, all according to the installation activities in the
schedule.

This buffer shall consist of relevant work items that naturally fit the sequential plan of performing the Work.

Project development, Requirements, TR2394, Version 2.03

Page 12 of 16
Requirements: Completion methodology Classification: Internal

4.8 As-built mark-up

SR-46786 - Confirmed AS-built or mark-up shall be done after completion of construction and
commissioning, ref. GL0327.

4.9 Relevant information

See GL0323 ICC Planning of the Completion Phase, GL0328 ICC Transfer of Rest scope to Operations
and GL0336 ICC Budgeting and Cost Control for relevant information.

5 Additional information

5.1 Definitions

Shall (requirement) Requirement strictly to be followed in order to conform to the document and from which no
deviation is permitted, unless a deviation permit is approved.

Should Indicates that among several possibilities one is recommended as particularly suitable, without
(recommendation) mentioning or excluding others, or that a certain course of action is preferred but not necessarily
required, or that (in the negative form) possibility or course of action is deprecated but not
prohibited.

May Indicates a course of action permissible within the limits of the document.

Can Statements of possibility and capability, whether material, physical or causal.

Company Equinor ASA. Owner and the final recipient of the equipment who may delegate another agent as
the purchaser of the equipment.

Purchaser Owner or owner's agent, who issues the order and specification to vendor.

Manufacturer Original manufacturer of the equipment.

Vendor/Supplier Manufacturer or manufacturer's agent that supplies the equipment and is normally responsible for
service support.

Contractor Owner or owner’s agent in a contractual situation with the owner who carries out all or part of the
design, engineering, procurement, construction, commission or management of the project,
operation or maintenance of a facility.

Brown field project Means a development project installing a modification and/or tie-in to an existing installation in
operation.

Completion Site Means an Onshore / Offshore Plant where the Completion (including installation) scope shall be
executed and started up with permanent supply. Company is the principal enterprise at the

Project development, Requirements, TR2394, Version 2.03

Page 13 of 16
Requirements: Completion methodology Classification: Internal

Completion Site.

Engineering Work The scope of work described in the FCP is divided into several single discipline EWPs. These
Package (EWP) documents contain a description of the installation of a defined part of the scope of work.
Applicable MTO, information concerning prefabrication and other deliveries and other relevant
information from engineering are included. These documents are the basis for the work orders.

Factory Acceptance Function and/or performance tests prior to acceptance at supplier workshop.
Test (FAT)

Field Check Package The scope of work is divided into several multi discipline FCPs. The FCP is used to verify all
(FCP) relevant documentation against the physical situation on site.

Green field project Project for completely new facilities.

Completion Generic term covering Mechanical Completion and Commissioning

Completion Home The office where the Completion organisation is situated at the Contractors premises.
Office

Completion Completion is the methodology where Equinor takes the lead position in an integrated team
methodology consisting of Company and Contractor personnel responsible for installation and completion at
Completion Site.

Life Cycle LCI is the documentation according to Equinor’s requirements, necessary for the operation and
Information (LCI) maintenance of a system.

Material Take Off MTO refers to the Bill of material / Material take off. MTO is a list of materials applicable for the
(MTO) specified work or installation item.

Project Completion Computerised system for follow-up and status keeping of Mechanical Completion,
System (ProCoSys™) Commissioning and Preservation by individual tag or area.

Project Execution The projects main execution and overall procurement strategy document.
and Overall
Procurement
Strategy (PEOPS)

Ready For Means the process in connection with responsibility transfer from the Construction Team to the
Commissioning Commissioning Team.
(RFC)

Ready for Operation Means the process in connection with responsibility transfer of the daily operation and
(RFO) maintenance activities from the Commissioning Team to Operations.

Work Order (WO) A work order contains a description with necessary information to perform the work.

Project development, Requirements, TR2394, Version 2.03

Page 14 of 16
Requirements: Completion methodology Classification: Internal

5.2 Changes from previous version

Ver 2.03: Document updated from Statoil template to Equinor template. Wording "Statoil" changed to
"Equinor". Insignificant changes, performed by system administrator, on behalf of author/owner.

Changes in version 2.02:

Minor change in chapter 1.2: Text added "This document is applicable for Investment projects. Operational
projects should not use this document unless the execution strategy make this necessary".

Changes in version 2.01:

Published in new minor version as part of the GEM-project (Governing Element Management).
TR-document is digitalized, and each requirement element is now identified with a unique ID.

Changes in version 2:

Reference: Description:

All TR A lot of grammar changes

All TR Term 'ICC' is removed and replaced with Completion

1.6 Responsibility and delivery: revised according to new contract template, making contractor responsible
for work performance up to Mechanical Completion

4.1 Typical organization and information flow chart has been changed to highlight that contractor is
responsible for work performance up to Mechanical Completion

4.5 New chapter FCP

4.6 New chapter EWP

4.7 New chapter WO, specifies that contractor shall be responsible for developing work orders and can
choose own work order preparation software tools

4.8 New chapter regarding AS built (reference to ARIS)

Appendix A Deleted ICC Guidelines (all put in new chapter 5.3-References)

5.3 Main references change removed, GL0320 ICC personnel logistics and vendor coordination, GL0322
ICC Work Order preparation and execution and progress monitoring, GL0325 ICC Material Logistics,
GL0334 ICC Handling of Field Check and Engineering Work Packages

Vi ønsker å endre TR2394 kap 1.2. I dag star det følgende tekst: "The main target group is the project
organization". Denne ønsker vi å endre til følgende tekst: "The main target group is the project organization.
This document is applicable for Investment projects. Operational projects should not use this document
unless the execution strategy make this necessary."

Project development, Requirements, TR2394, Version 2.03

Page 15 of 16
Requirements: Completion methodology Classification: Internal

I tillegg kan dere fjerne følgende tekst i Kap. 1.3 : (FR05 Project Develoment). Ny tekst I kap 1.3 skal da
være : "Provision is made in Equinor Management System".

5.3 References

Reference: Title:

TR2393 “Commissioning Requirements”

TR2148 “Mechanical Completion Manual”

TR2149 “Preservation Requirements”

GL0321 “Query Handling in the Completion Phase”

GL0323 "ICC Planning of the Completion Phase"

GL0327 “Handling of As-Built Mark-up”

GL0328 "ICC Transfer of Rest scope to Operations"

GL0329 “Work order estimating manual”

GL0336 "ICC Budgeting and Cost Control"

GL0417 “Completion Strategy”

GL0513 “Completion Preparation Manual”

Project development, Requirements, TR2394, Version 2.03

Page 16 of 16