Efficient project execution

Operationalization of PD03.421-PD03.64
27.11.2015

Classification: Internal
2013-09-25
PD03: A-standard / C&L execution of all meetings

- Clear and unambigous agenda

- What are the deliveries?
Under-
Understand - What is the challenges?
standing - Correct participation / competance present in the meeting?
task and risk
the task: - Deliveries to the next meeting / date?
Desired
All involved result:
need to Identify and
understand understand • ARIS and TR/GL in Docmap Desired
requirements
what the result shall
• Are there any risk of not meeting the desired result?
end • Are all relevant stakeholders and contributers identified / present? be known by
Manage risk
deliveries • Are the pre-read and necessary meeting-documentation available so that the all meeting
meeting can be executed efficiently to create value?
from the participants
meeting is, • Execute the meeting with good quality and management
Execute task
and what • Ensure that we achieve the desired result
their
contri- Evaluate • Evaluate the meeting. Use some minutes on evaluating improvements to the next
bution is result. Extract meeting.
• Was the purpose with the meeting achieved?
learning
• Correct pre-read and meeting documentation? Correct participation?

Internal
 PD03: Efficient project execution
- execution phase

LCI 2
LCI 1

LCI 3
Equinor Perform kick-off
Clarify project
meeting with
deliveries
executor
R-105730
R-105518

System drawings
IFC RFC
Utførende

R-105545
R-105959

Check of
Design- and installation RFO As-Built
construction preparations
review(s) R-105539 R-100894 R-35166
R-105545 Check of
installation
preparations
Ready for
R-105539
installation
Design freeze R-105539
R-105545

Design freeze
R-105545
Design freeze
R-105545
The following milestones shall be used - if not agreed otherwise:
LCI 0 12 weeks after contract assignment or
covered by frame agreement

LCI 1 Freeze of design - R-105545

LCI 2 Ready for installation

LCI 3 As-built (4 weeks after RFO) – R-35166

3 Classification: Internal
 Kick-off meeting with executor (R-105518 – conduct kick-off meeting)
Purpose
Executor/Vendor shall presesent its understanding of the task / Agreement.

Plan with milestones for the execution shall be presented.

From ARIS:
A meeting shall be conducted to go through the project. Executor shall present the scope of work.
The participant list shall be based on the Involvement Matrix. Meeting minutes shall be written
by a company representative.

Agenda
Executor presents its understanding of the task/Agreement
• Background, purpose
• Presentation pr. discipline of specific work tasks in engineering, together with clarifications of
uncertainties.
• Procurement strategy
• Project risik (preferably from PIMS)
• Live plan for execution of the task/Agreement, GL0587 Responsible for conducting the meeting
• Cost estimate (hours pr phase in live plan)
• Project M5 established for M&M Agreements (Equinor responsibility) Project manager Equinor

The Company presents how it plans use the organization for follow up and involvement in the
project (involvement matrix)

Participants
Desired result Equinor:
- Project manager Equinor’s team
Common understanding of tasks and project execution.
Executor:
Plan with milestones for execution of the Agreement. - Project manager Executor’s team

C
4 lassification: Internal
 Clarify project deliveries (R-105730 – Clarify project deliveries)
Purpose
The meeting shall be held shortly (e.g. 2-6 weeks) after kick-off meeting with executor to ensure
common understanding of the project deliveries for engineering and completion.

The Executor shall use Equinor’s systems to show status (e.g. STID / ProCoSys, SPIR) Projects
with several part-handovers (RFOCs): As-Built shall be clarified - common, or after each part-
handover.

Can be conducted as a Concurrent meeting, ref «R-105531 – Use of concurrent method»

- Required TAGGING, GL0583

Agenda
- SEMI – shall be used for
• Short presentation of design
documentation of standard
• Tags: - Review of tags per discipline, GL0583
- Review of new/modify/deleted tags
equipment
- Review of Tag - SEMI-ID
• Document: - Engineering document
- Supplier document (clarify the need for SPIR) Responsible for conducting the meeting
• Project M5 – task in SAP
1. Project manager Equinor
• Completion strategy / Commissioning
2. Separate follow up between AI/MA/RMM/MOD to clarify
• Review of structure in ProCoSys
document/tag deliveries to the project – post meeting.
• Commissioning procedure (document established)
Responsible: Project manager Equinor
• Clarify sign out of A21/A31/A41 in ProCoSys

Desired result Participants

The following shall be verified by the Project engineer (clarify with AI by relevans): Equinor:
• Tag and document list, can be found in Equinor’s systems. - Project manager Equinor’s team
• Agree on what shall be delivered as standard equipment/documentation.
• Review of SPIR that shall be delivered Executor:
ProCoSys structure established - Project manager Executor’s team
Common understanding of what will be delivered to «Ready for installation»

5 Classification: Internal
 System drawings IFC (R-105545)
Purpose
System design, drawings to be prepared for status IFC:
1. Piping and instrument diagram (P&ID)
2. Cause & effect (C&E)
3. Fire protection data sheet (FPDS)
4. System control diagram (SCD)
5. Area and System Duct & and Instrumentation Diagrams (D&ID)

Ref. chapter 2.6 in TR2381 - Safety critical documents

Responsible
Project manager Executor

Desired result
Participants, ref. Involvement matrix
IFC revision for system design documents/drawings available in STID prior design-construction Equinor:
review. - Project manager Equinor’s team

Executor:
- Project manager Executor’s team

6Classification: Internal
 Design / construction review (R-105545)
Purpose
A multidiscipline review of design with focus on customer and regulatory requirements.
The result of the review is a design that i safe, user-friendly and fit-for-purpose / according to
customer needs (within SOW)

Design /layout approximately complete.

Compare the developed design with the requirements in the project.

Relevant operational competance to participate.
Can be conducted as a Concurrent meeting, ref «R-105531 – Use of concurrent method»

Agenda
Expectations to contents:
• Presentation of design
• Presentation of layout
• List of relevant guidewords
• Meeting memo with actions and presentations attached.
• This should be a meeting with focus on the disciplines and not a status meeting (progress, time
consumption, plan, etc. is not applicable)

Responsible
Project manager Executor

Desired result Participants, ref. Involvement matrix

Agreement of design in accordance with: Equinor:
• Regulatory requirements and customer requirements (Equinor). - Project manager Equinor’s team
• Requirements in PED (pressureised equipment directive) and Machinery directive
• Requirements in valid standards Executor:
• Safety and working environment - Project manager Executor’s team
• User friendlyness and accessability

Classification:
7
2014- Internal
 Milestone
Design freeze (R-105545)
Purpose
Freeze of design to be carried out at the latest one week after design / construction review.
Freeze of:
- Document list
- Tag. list
- System design, drawings to be prepared for status IFC (without «HOLD»)
1. Piping and instrument diagram (P&ID)
2. Cause & effect (C&E)
3. Fire protection data sheet (FPDS)
4. System control diagram (SCD)
5. Area and System Duct & and Instrumentation Diagrams (D&ID)

This doesn’t have to be a meeting, but a milestone where Equinor / conctractor agrees upon
design freeze.
There may be several Design Freeze in a project. This depends on the installation activities in the
project.

Necessary documentation for procurement to be prepared.

This we build.
Desired result Now it’s Team Pursuit to the goal line!
Responsible
• Final TAG list
• Equipment to be delivered with standard documentation Project manager Executor
• Equipment that is not delivered with standard documentation with LCI milestones in
accordance with TR2381 and GL0587
• Final document list over documentation that shall be delivered in the project
• Freeze of 3D PDMS design Participants
• Freeze of safety critical documentation
• Documentation for procurement ready Equinor:
• Documentation for maintenance engineering ready for RMM/MA (Equinor) - MOD normally - Project manager Equinor’s team
use M5 notification for this. «Brownfield» use ProCoSys.
• Documentation for other equipment acc. agreed delivery schedule for the equipment Executor:
- Project manager Executor’s team

Classification:
8 Internal
 Milestone
Check of installation preparations (R-105539 - Check of installation preparations)
Purpose
This is the last check in the engineering phase to ensure that everything is at place before   Action list (suggestion)  
installation can start. Review to be held 3-6 weeks before installation start.
QC check list from Project enginer shall be available on teamsite two days before the review.      
If there is any remaining tasks, a action list is prepared with spesific actions with responsible
person for closing the action, and a clear deadline. See checklist . No Action Deadline Responsible
This can be performed using Concurrent method, ref. «R-105531 – Use concurrent method».
 1  Comm. procedure signed 13.04.2015 

 2 PM completed 04.05.2015

 3 Cable delivered 04.05.2015

Agenda
     
1. General
2. Plan
3. Assistance
4. Shut down Responsible
5. Installation packages / Work orders
6. Material/Tools/Access Project manager Executor
7. Resources
8. LCI status (per. commissioning package, if applicable)
• TAGs with planed status
• Tags with SEMI ID Participants according to involvement matr.
• Supplier documentation in IFC (ProCoSys checklist A41)
• Engineering documentation (ProCoSys checklist A21) Project manager Equinor, responsible for Equinor
• PM progr. / MA/ Inspection program (A31) praticipation.
9. Completion / ProCoSys – review and verify. Commissioning procedure signed. Cotractors (including ISS)
10. Risks
11. Other Any additional participants:
• O&M leader land
• Relevant Discipline responcible land, and Technical
system resp. (AI)
Desired result • Project engineer
• Operations leader
Verify that the project is ready for installation. • Safety leader/HSE-coordinator
• Construction leader
Desired result is detailed list of actions with deadlines and responsible.

Classification:
9 Internal
 Milestone
Ready for installation milestone (TR2381)
Purpose
  Action list (suggestion)  
All actions from «Check of installation preparations” are closed and we are ready for installation.
     
It's a risk-based assessment of whether the project is ready to install.
No Action Deadline Responsible

 1  Comm. procedure signed 13.04.2015 

 2 PM completed 04.05.2015

 3 Cable delivered 04.05.2015

     

Responsible
Project manager Executor

Participants according to involvement matr.

Project manager Equinor, responsible for Equinor
praticipation.
Cotractors (including ISS)

Any additional participants:

• O&M leader land
Desired result • Relevant Discipline responcible land, and Technical
system resp. (AI)
The project is ready to install.
• Project engineer
All actions from "Check of installation preparations" is closed.
• Operations leader
• Safety leader/HSE-coordinator
If it’s a long time from the review until the installation starts, then the project
• Construction leader
should be frozen (close WBS).

Classification:
10 Internal
 Milestone
RFC(Ready for commissioning) / RFO (Ready For Operation)
Purpose
Completion are important activities for planning in the project. Date for mechanical completion
(RFC) and handover to operations (RFO) are specific milestones.
Completion contains the following elements:
• Mechanical completion (executor), and handover to Commissioning – RFCC
• Commissioning activities (Executor: Equinor and/or contractor)
• Handover from the project/commissoning to Equinor operations – RFOC
When RFOC is signed, Equinor operations has taken over the responsibility for the
equipment/system and can proceed with preparations for start-up.

Desired result (Completion)

RFCC: Executor confirmes mechanical completion according to PD431.01 «perform MC», and
agreed punch items are registered in ProCoSys. RFCC is generated according to R-19337. No A-
punch are accepted at RFCC. Red mark-up is performed where there is changes on installed
equipment from the «IFC» revision, and sent to Engineering for update to As-Built.
Commissioning: Commissioning is performed in accordance with PD03.64, based on approved
commissioning provedure. Punch items related to commissoning are registered in ProCoSys.
Commissioning activities that cannot be performed before start-up shal be registered as remaining
punch items before RFOC is generated. Before completion of such punch items, both the punch
items and the corresponding description of these in the commissioning procedure shall be signed Responsible
out. Red mark-up is performed where there is changes on installed equipment from the «IFC»
revision, and sent to Engineering for update to As-Built. Project manager Executor / Equinor

RFOC: Hand over from the project/commissioning to Equinor Operations are performed in
accordance with PD03.64. by preparing and signing RFOC. This is normally prepared pr system.
Requirements for the RFOC content are given in R-100831. No A-punch shall be open when Participants, ref involvement matrix
issuing RFOC. Commissioning activities that cannot be performed before start-up shall be
registered as remaining punch items. Equinor:
- Project manager Equinor’s team
Ready for safe and efficient start-up of system and equipment
Utførende:
- Project manager Executor’s team

Classification:
11 Internal
 Milestone
As-Built
Purpose
All documentation and TAGs shall be in As-built status , and reserved TAGs/documents for the
project shall be «cleaned». As-Built according to TR2381

Projects with several part hand-over: As-Built shall be clarified in the «clarify project As-Built
deliveries meeting» with regards to how this shall be carried out, collectively at the end, or at each
part hand-over.

Contractor to send over confirmation when As-Built is completed.

Checklist

1. PDMS 
2. TAG
3. Documents
4. Punch
5. MA
6. PM program
7. LOOP/ELE Responsible
Ref: OM06.16 – Follow up and confirm LCI update to as-built Project manager Equinor

Desired result Participants

Equinor:
PM/MA finalized in SAP • Project manager Equinor’s team
As-Built registered in SEMI/STID/SAP.
As-Built according to TR2381

Prosject manager Equinor is responsible for finalizing all deliveries before completing the
final report.

Classification:
12 Internal