Document Number

Project Quality Plan

2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 1316-OctNov-2024

CONTRACTOR Reference: Page 1 of 29

ARAMIS PROJECT

Revision
Rev. Step Date Issued by Checked by Approved by
Description

Issued for
02 IFR 13-Nov-2024 P. LAMPROPOULOS J. BROUAT P. LAMPROPOULOS
Review
Issued for
01 IFR 15-Oct-2024 P. LAMPROPOULOS J. BROUAT P. LAMPROPOULOS
Review
 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 2 of 29

REVISION CHANGE DETAILS

Rev. Description

01 Issued for Review

HOLD ITEMS

Page Description

Project Quality Plan Page 2 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 3 of 29

Table of Contents
Introduction .......................................................................................................................... 6
1.1 Background ............................................................................................................... 6
1.2 Purpose ..................................................................................................................... 7
1.3 Scope ........................................................................................................................ 8
1.4 Definitions and Abbreviations .................................................................................... 9
Quality Management System ............................................................................................. 11
2.1 Quality .................................................................................................................. 11
2.2 Quality Policy ....................................................................................................... 11
2.3 Quality Objectives ................................................................................................ 11
2.4 Quality Strategy.................................................................................................... 12
2.5 Regulatory Compliance and Safety Standards ........................................................ 13
Project Quality Control ...................................................................................................... 15
3.1 Project Controls Matrix ......................................................................................... 15
3.2 Initialization .......................................................................................................... 15
3.2.1 Embedding Quality Control in the Project’s Organizational Structure .................... 15
3.2.2 Development of PEP and PQP ............................................................................. 16
3.2.3 Preparation of QC Tools ....................................................................................... 16
3.3 Quality Assessment, Reporting and Control ......................................................... 17
3.3.1 Corrective Actions ............................................................................................. 20
Project Quality Assurance ................................................................................................. 21
4.1 Critical Milestone Pre-FAT QA Audit ........................................................................ 21
4.2 Critical Milestone Pre-Shipment QA Audit ................................................................ 21
4.3 Lessons-Learned ................................................................................................. 22
4.4 Control of non-compliances...................................................................................... 23
4.5 Customer Satisfaction .............................................................................................. 23
REVIEW AND APPROVAL OF PROJECT QUALITY PLAN ............................................... 24
5.1 Review and approval................................................................................................ 24
5.2 PQP distribution ....................................................................................................... 24
5.3 PQP revision ............................................................................................................ 24
Annex 1 – CERTIFICATION ISO 9001 - 2015 ..................................................................... 25
Annex 2 – General Policy................................................................................................... 26

Project Quality Plan Page 3 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 4 of 29

Annex 3 – SSE EKIUM ENGAGEMENTS ........................................................................... 28

Annex 4 – Deliverables List ............................................................................................... 29
Introduction .......................................................................................................................... 5
1.1 Background .................................................................................................................... 5
1.2 Purpose .......................................................................................................................... 5
1.3 Scope .............................................................................................................................. 6
Definitions and Abbreviations .............................................................................................. 7
Quality Management System ............................................................................................... 9
2.1 Quality .................................................................................................................... 9
2.2 Quality Policy ......................................................................................................... 9
2.3 Quality Objectives .................................................................................................. 9
2.4 Quality Strategy.................................................................................................... 10
Project Quality Control ...................................................................................................... 11
3.1 Project Controls Matrix ......................................................................................... 11
3.2 Initialization .......................................................................................................... 11
3.2.1 Embedding Quality Control in the Project’s Organizational Structure .................... 11
3.2.2 Development of PEP and PQP ............................................................................. 12
3.2.3 Preparation of QC Tools ....................................................................................... 12
3.3 Quality Assessment, Reporting and Control ......................................................... 13
3.3.1 Corrective Actions ............................................................................................. 16
Project Quality Assurance ................................................................................................. 17
4.1 Critical Milestone Pre-FAT QA Audit ........................................................................ 17
4.2 Critical Milestone Pre-Shipment QA Audit ................................................................ 17
4.3 Lessons-Learned ................................................................................................. 18
4.4 Control of non-compliances...................................................................................... 19
4.5 Customer Satisfaction .............................................................................................. 19
REVIEW AND APPROVAL OF PROJECT QUALITY PLAN ............................................... 20
5.1 Review and approval................................................................................................ 20
5.2 PQP distribution ....................................................................................................... 20
5.3 PQP revision ............................................................................................................ 20
Annex 1 – CERTIFICATION ISO 9001 - 2015 ..................................................................... 21
Annex 2 – General Policy................................................................................................... 22

Project Quality Plan Page 4 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 5 of 29

Annex 3 – SSE EKIUM ENGAGEMENTS ........................................................................... 24

Annex 4 – Deliverables List ............................................................................................... 25

Project Quality Plan Page 5 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 6 of 29

Introduction

1.1 Background
The Aramis project is a cooperation between Shell, TotalEnergies, Gasunie and EBN to utilize
depleted gas fields and potentially aquifers in the Dutch North Sea to establish an open-access
CCS infrastructure for transport and storage, targeting hard-to-abate industrial emissions in the
Netherlands and Europe.

This part of the project provides the transport of CO2 from the onshore terminal to an offshore
platform, which is used as a distribution hub (D-Hub). Other parts of the project are provided by
CO2next and Porthos, while the actual storage in the depleted offshore gas fields under the North
Sea is performed by Shell and TotalEnergies as part of their offshore operations.

In Figure 1.1 below, the envisaged CCS infrastructure is outlined. The left panel illustrates the
trunkline that transports the CO2 from the Maasvlakte to the offshore storage. The middle panels
illustrate the Maasvlakte Hub with the Porthos compressor station and the CO2next Terminal. The
right panel shows the platforms of TotalEnergies and Shell.

Figure 0 – Overview of CCS Infrastructure

1.1 Background
The rapid growth in atmospheric CO₂ emissions has caused the planet’s temperature to rise,
negatively impacting the climate. Countries across the world have realized that there is no time to

Project Quality Plan Page 6 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 7 of 29

waste in trying to slow down and stop global warming. National and international agreements have
been reached and steps are being taken to bring about large-scale reductions in CO₂ emissions.
Carbon capture and storage (CCS) is a key solution.
The technology for capturing CO₂ and storing it deep underground has been around for decades.
The decarbonization of Dutch and European industries can benefit significantly from CCS. In effect,
CCS can remove a huge amount of CO₂ from the atmosphere; it can be realized swiftly and offers
a decarbonization solution for hard-to-abate industries at short notice.
The Aramis CCS project aims to contribute to the reduction of CO₂ emissions for hard-to-abate
industries. It will do this by providing CO₂ transport to unlock storage capacity for the industry.

The CO₂ will be stored in depleted offshore gas fields, deep under the North Sea. It will be based
on an ‘open access’ philosophy so that other industrial customers and storage fields can be added
incrementally to the system.
The project’s location on the Maasvlakte in the Port of Rotterdam makes the CO₂ transport and
storage service accessible to various industrial clusters.

1.2 Purpose
This document describes the quality framework for the Telecom scope during the project execution
phase to ensure that Ekium will achieve the required quality objectives.

The purpose of this Project Quality Plan (PQP) is to:

1. Specify the required quality level the project will deliver.
2. Describe the control mechanism used by the project to assure that the project quality
requirements are attained.
3. Describe how Ekium will assure that project Quality Control measures are effectively in
place in accordance with the MAC procedures, COMPANY/ ENGINEERING
CONTRACTOR requirements and regulatory standards.

The PQP serves as a formal agreement between EKIUM , YOKOGAWA and COMPANY. It defines
the roles and responsibilities of each party, with respect to Quality Control and Quality Assurance.

All project team members are responsible for carrying out their work in supporting the appointed
project quality objectives in compliance with the requirements as defined in this Project Quality
Plan.

The key stakeholders of this Project Quality Plan are:

• EKIUM: Project Manager, Project Engineers, QHSE Advisor.
• MAC: Project Manager, Project Engineers, QHSE Advisor.
• CUSTOMER: Lead CS&I Engineer, ICSS Engineer, Project Engineering Manager, Project
Procurement Manager and Quality Manager.
• COMPANY: Project Manager, Lead Engineer, Technical Authorities and Quality Manager.

Project Quality Plan Page 7 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 8 of 29

1.3 Scope
This Project Quality Plan (PQP) describes all the measures implemented within the framework of
the project (organisation, responsibilities, methods and tools) to satisfy the requirements of the
Ekium and those of the Customer defined under the Contract. This document regroups the Project
Quality Assurance and Project Management Plans.
Each employee is responsible to strictly follow the rules of this PQP within the area under his / her
responsibility.
The Project Manager is responsible for the update and distribution of this document.

Project Quality Plan Page 8 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 9 of 29

1.4 Definitions and Abbreviations

Abbreviations:

CS&I Control Systems & Instrumentation

CTQ Critical To Quality
DoC (FS) Declaration of Conformance for Functional Safety
DGD General and Final Account
EPC Engineering Procurement & Construction
FAC Account Analysis Sheet
FAT Factory Acceptance Test
FSM Functional Safety Management
GES Global Engineering Standards
HW HardWare
I&C Instrumentation and Control
IA Industrial Automation
IEC International Electrotechnical Committee
ISO International Standards Organisation
KOM Kick-Off Meeting
LL Lessons Learned
MAC Main Automation Contractor
MAPP Measure of Performance and Physical advancement
MT Management Team
NC Non-Conformance
OTS Operator Training System
PEP Project Execution Plan
PLC Project Life Cycle
PM Project Manager / Project Management
POSC Preparation, Organization and Follow-up
PQP Project Quality Plan
QA Quality Assurance
QC Quality Control
QG Quality Gate
QHSE Quality Health Safety & Environment
QMS Quality Management System
RACI Responsible, Accountable, Consulted, Informed
SA Safety Assurance
SAT Site Acceptance Test
SVP Safety Validation Plan
SW SoftWare
YMS Yokogawa Management System

Definitions:
TSI : EKIUM
MAC : Yokogawa Europe Solutions BV

Project Quality Plan Page 9 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 10 of 29

COMPANY : ARAMIS Company

ENGINEERING CONTRACTORS: EPC(s) Company
PROJECT : ARAMIS CCS Project
CUSTOMER : Refers to the ENGINEERING CONTRACTORS for ICSS and Telecommunication scope.
: Refers to the COMPANY for the System Integrator System Scope.1

1
The term “Customer” is used in the document instead of ENGINEERING CONTRACTORS and/or COMPANY when
statements are generic and apply to the complete scope delivered by MAC.

Project Quality Plan Page 10 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 11 of 29

Quality Management System

This section describes a high-level overview of Ekium’s Quality Management System (QMS) for
this project.

2.1 Quality
Quality is defined as:
• Fitness for use
• Conformance to requirements
• Consistently meeting COMPANY / ENGINEERING CONTRACTOR’s needs and
expectations
• The totality of features and characteristics of a product or service that bear on its ability to
satisfy stated or implied needs (ISO 9001)

Quality assurance activities focus on the processes used to manage and deliver the required
solution.

2.2 Quality Policy

EKIUM commits to take all necessary measures to provide services in accordance with good
engineering practices and a level of quality in all tasks meeting contractual, reliability and safety
requirements.
EKIUM is committed to continuous improvements, reaffirmed in the Group’s QHSE Policy (Annex
2 – General Policy).

2.3 Quality Objectives

The quality objectives for this project are to deliver a fully tested, conforming and documented
solution on time, cost and to full satisfaction of YOKOGAWA:
1. Tested, audited and conforming: The solution to be delivered will be 100% tested
against technical requirements and all applicable codes and standards, at each stage
of the project, as defined in the Quality Control Plan and based on the criticality rating
assigned, and approved by YOKOGAWA, to each unit included in the scope. No
nonconforming items will be delivered without an approved Deviation Request as
described in our procedure 7C-80-PI-PRO-010-Gestion des écarts et des
ameliorations (control of non-compliance).
2. On time: All agreed lead-times for each project stage
3. On cost: No deviations from budget not supported by Change Orders.
4. Customer satisfaction. Objective is to have the CLIENT satisfied during FEED and
full project execution and after delivery. This satisfaction will be formally assessed
after the FEED and each phase of the project through a simple questionnaire. In case
of dissatisfaction or passive score, recovery action plans will be implemented, and
results validated with YOKOGAWA. This will also be assessed at the closure of
contractual activities in a debriefing meeting.

Project Quality Plan Page 11 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 12 of 29

2.4 Quality Strategy

Ekium is committed to, and plans to achieve, its quality objectives by adopting the following
strategy:
• Annual review of audit findings and quality objectives via internal management review
meetings.
• Communication of the quality policy to the Ekium’s project team members by the QHSE
Advisor.
• Capturing lessons learned and where applicable embedding lessons learned in procedures
and templates to continuously improve the level of quality.
• Continuous improvement via internal audits, management reviews, and project team
meetings.

Project Quality Plan Page 12 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 13 of 29

2.5 Regulatory Compliance and Safety Standards

EKIUM is committed to delivering the highest quality services while ensuring the utmost safety,
security, and environmental responsibility. Our compliance with internationally recognized
standards underscores our dedication to excellence:
ISO 45001: Prioritizing occupational health and safety for our employees and partners.
ISO 9001: Upholding superior quality management systems to meet and exceed customer
expectations.
You can find here below all the certifications that our company possedes on all the activities that
we participate.

Project Quality Plan Page 13 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 14 of 29

Project Quality Plan Page 14 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 15 of 29

Project Quality Control

This chapter explains the Quality Control measures the project will utilize to achieve the required
quality standards.

3.1 Project Controls Matrix

Ekium has developed the deliverables list (7C-80-A02-EQS-019-Deliverables List) which is an
assessment tool that supports in defining the required project controls and deliverables. The PCM
will, based on the various project characteristics, recommend the applicable project controls and-
deliverables, like for example which Project Life Cycle phase gate reviews shall be applicable,
which reports must be made, etc.
Due to the nature of this PROJECT, there will be a requirement to conduct all project phase gates
for each discipline during the execution phase of this PROJECT.

3.2 Initialization
The following QC-related action is initiated as part of the project start-up:
• Embedding Quality Control in the project’s organizational structure.
• Development and formal approval of PEP and PQP
• Preparation of Quality Control tooling’s

3.2.1 Embedding Quality Control in the Project’s Organizational Structure

Assign project QC role
It is the project team’s responsibility to control the quality of its deliverables and the quality of the
project execution. One of the engineers of the project team is assigned as Quality Control Engineer
whose task is to gather quality metrics and issue the report to the project stakeholders on a regular
basis. The QC engineer also functions as an expediter within the project, to ensure that QC
activities are executed as planned.

Assignment of Project Team for Safety Projects

For projects which involves Safety System scope deliverables, MAC organization shall consider
minimum level of competence of Project Team Members for assigned role to meet the IEC
standard for Safety System Project Execution.

Assign peer reviewers

The Project Manager and/or the Project Engineer arranges specialists (independent of the project
team, technical authorities) who will perform technical Peer-Review which is a technical evaluation
of the solutions provided by the project engineers.

Explain QC to project team

An internal Kick Off Meeting (Kom) is organized by Ekium Project Manager the week before the
official KOM with ARAMIS.
The participants are :
• Branch Manager

Project Quality Plan Page 15 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 16 of 29

• Project Manager
• Department Engineering
The template 7C-80-A02-EQS-009-CR Réunion de lancement contains the checklist of items to
be discussed during the internal kick-off meeting.
Internal KOM was done the 12/08/2024
Important: The technical leader relays the kick-off meeting to his team and all new project
members.

3.2.2 Development of PEP and PQP

During the Early Involvement phase, the Project Manager prepares the Project Execution Plan
(PEP) and the Project Quality Plan (PQP). These documents are issued to YOKOGAWA and
COMPANY for approval.

3.2.3 Preparation of QC Tools

Prepare PM Checklists
The records produced throughout a case, in order to provide evidence of the realization of the
activities of the operational processes, are monitored in a dedicated register 7C-80-A02-EQS-024
- Suivi des enregistrements qualité sur affaire.
This register includes company-standard checklists used by the project to validate the managing
quality level of the project from Project Initiation to Project Closure.

Prepare QC Reports
The QHSE Engineer prepares QC reports on a regular basis in which adherence to PM Checklist
and GES standards and procedures by the engineers of the project team is assessed. The QC
Report is discussed with the Project Manager.

Prepare Punch List tool

The Punch List tool is prepared to centrally administer the logging, resolution, and reporting of
punch items that the project will encounter during the project life cycle. Internal test, FAT and SAT
punch lists can be derived from the punch list tool.

Defining Control Point

Ekium defines standard phases in the project engineering process, including Basic Design, Detail
Design/Implementation, Internal Test, FAT and SAT. External audits are performed prior to
entering a critical project phases FAT and Shipment. Technical Peer-Reviews are performed in
other project phases and, depending upon the risk level to which the project is exposed, ad-hoc
control points are organized by the Project Manager.

Test Records
Test records are important quality assessment records of the project. The project team will
maintain test records to demonstrate that system verification has been completed, and that the
system is constructed and assembled in accordance with design and functional specifications. The

Project Quality Plan Page 16 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 17 of 29

test records are compiled and organized by the project team according to the system being tested.
They are based on the test procedure and report. The test records will be reviewed to determine
that verification has been appropriately completed. Observations will be reported in the check at
the applicable phase transfer. Test records will be created for Typical Test, Internal Test, FAT and
SAT.

3.3 Quality Assessment, Reporting and Control

Quality Control records (or quality records) are documented evidence of Quality Control activities
in the project. Quality Control records are used to demonstrate:
• Achievement of specific quality
• Effective operation of the quality management system
• Compliance to Functional Safety Requirements as per GM604 “Yokogawa’s corporate
policy for Functional Safety Management” for project involving and engineered safety
system.

The following documents constitute Quality Control records for the project:
• Completed PM check sheets.
• Document review logs.
• Internal test records for all systems in the project.
• Internal test punch list.
• FAT punch list.
• SAT punch list.
• Impact Analysis details for safety related punch points for projects involving safety system
execution.
• Corrective Action Requests for problems encountered (if any).
• Internal Audit Reports.
• Project close out report (end of project).
• In the table below the quality assessment, reporting and control aspects of the Project
Quality Requirements are described.

Project Quality CTQ Attribute Quality Quality Control

Requirement Assessment &
Report
Adherence to agreed CUSTOMER/ MAC - Monitor document - Expedite delivery
MAC and CUSTOMER document delivery status of due and overdue
document deliverables are documents.
- Report in the ‘QC
deliverablesAdherence promptly issued to the
Report’. - Register
to agreed MAC and other party within the
corrective actions in
document deliverables agreed schedule.
the Project Action &
Decision Tracker.

CUSTOMER/ MAC to
review, modify and

Project Quality Plan Page 17 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 18 of 29

Project Quality CTQ Attribute Quality Quality Control

Requirement Assessment &
Report
approve documents of - Follow up and
the other party within perform corrective
the contractually action.
agreed timescale.

CUSTOMER/ MAC to
incorporate requested
modifications to the
documentation within
the contractually
agreed number of
review cycles.

Adherence to the CUSTOMER-supplied - Assess and grade - Inform customer

agreed MAC and Design-Input the quality level of of the result:
CUSTOMER documents must be received design - document
document deliverables complete, consistent, input documents. approved or
and unambiguous.
- required
revisions.

Issued MAC - Schedule and - Incorporate

document perform internal received
deliverables must be review of document comments.
complete, consistent, deliverables prior to
and unambiguous. submission.

Adherence to Ensure hardware and - Perform ‘Peer- - Incorporate

contractually agreed software quantity and Review’. comments from
hardware and software quality are ‘Peer-Review’
- Perform internal
deliverables appropriately
test. - Resolve Punch
validated.
List items prior to
Register defects in
FAT.
the Punch List Tool
- Impact analysis
for safety related
punch items.

Ensure the hardware - Perform ‘Peer- - Resolve defects

and software typicals Review’. prior to Prototype
(‘prototypes’) are FAT.
- Perform internal
properly engineered
test.
(and thoroughly
tested).

Project Quality Plan Page 18 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 19 of 29

Project Quality CTQ Attribute Quality Quality Control

Requirement Assessment &
Report
Project team ensures - Perform internal - Resolve defects
that the system is test. prior to internal
engineered review.
appropriately prior to
internal review (QC).

Adherence to Execution in line with - Complete Project - Correct fail and

approved Project the approved Project Management attention points in
Execution Plan Execution Plan. Checklists. (PM PM check sheets
Checklist) prior to next
engineering phase.
- Monitor and
manage project - Perform corrective
execution in line with actions identified in
the PEP. ‘Project QA Audits’.

Adherence to Project is executed in - Assign project - Incorporate

applicable industry adherence to IEC team members with comments from
and regulatory 61508 and IEC 61511 required reviews.
standards (only applicable to competence for their
- Perform corrective
Safety projects). role as per GM604.
actions identified in
- Apply DRC for audits.
safety related
deliverables.
- Carry out impact
analysis for safety
related punch items
and take necessary
corrective actions.
- Schedule Project
functional Safety
Assessment (FSA)
at the appropriate
project lifecycle
phases as defined in
GM604 and obtain
DoC(FS) for the
project.
- Organize Audits by
GM604 governance

Project Quality Plan Page 19 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 20 of 29

Project Quality CTQ Attribute Quality Quality Control

Requirement Assessment &
Report
board authorized
auditors.

- Review - Seek clarification

Technical solution Compliance List to fulfill
delivered is in prepared at sales requirements and,
adherence to the stage with respect to where necessary,
required Codes and Codes and request a formal
Standards defined in Standards concession to
the CONTRACT. waive
requirements.
Project team ensures
Adherence to pre- Review contracts of No major HOLD
that all engineering
production delivery and delivery points.
documents are
milestones
approved. System architecture
All hardware and approved.
software selected,
ordered, and planned
to be delivered in
time.

3.3.1 Corrective Actions

Corrective actions shall be registered in the MAC’s Project Action tracker or equivalent and
executed for all Quality Control efforts that reveal a deviation between the Required Quality Level
and the Assessments of the actual Quality. The corrective actions shall contain, for each action,
the following data:
• Reference number.
• Description of the deviation or reference to a description.
• Description of the action to correct the detected deviation.
• Name of the action owner.
• Due date for the action.

Punch items forthcoming from Internal tests and Factory Acceptance Tests will be administrated
and tracked in the Punch List Tool.

Project Quality Plan Page 20 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 21 of 29

Project Quality Assurance

This chapter explains how Ekium will ensure the project’s adherence to the Quality Control
measures.
The QA’s objectives are as follows:

• Ensure that the project is executed in adherence to the officially approved Project Execution
Plan and Project Quality Plan deliverables.
• Ensure and independently validate the project’s readiness to proceed towards key
schedule milestones.
• Ensure that the project execution approach (and deliverables being produced) follow the
applicable Yokogawa work instructions/procedures, industry requirements and regulatory
standards.
• Ensure and facilitate the capturing of the project ‘lessons-learned’ in Ekium’s effort towards
continuous process improvement.

4.1 Critical Milestone Pre-FAT QA Audit

FAT is the time when Ekium will officially present its project’s output to the customer for acceptance
testing. Hence, it is essential to perform an audit of the project to assess its readiness to enter
FAT.

The Pre-FAT QA Audit is executed and led by the QHSE Advisor, together with the Engineering
Manager or Head of Project Management. The following PM checklists (completed by the Project
Team) will be used as a basis for examining the project’s readiness for FAT.

• Pre-FAT checklist for Project Management

• Pre-FAT checklist for Integrated System including Hardware
• Pre-FAT checklist for Telecom Systems

The QHSE Advisor will report the Pre-FAT Audit findings to the Head of Project Management /
Head of IA Delivery, including the advice to:
• Go for FAT.
• Go-On-Condition.
• No-Go for FAT.

The final decision will be taken by the Head of Project Management in consultation with the QHSE
Advisor.

4.2 Critical Milestone Pre-Shipment QA Audit

Pre-Shipment QA Audit is essential to independently validate the readiness of the project to deliver
to site. In this audit the following GPMS & GES checklists will be used as to examine the project’s
readiness to ship the project:
• Pre-Shipment checklist for Project Management
• Pre-Shipment checklist for Integrated System including Hardware

Project Quality Plan Page 21 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 22 of 29

• Pre-Shipment checklist for Telecom Systems

The QHSE Advisor will issue the Pre-Shipment Audit Report to the Head of Project Management
/ Head of IA Delivery, including the advice to:
• Proceed with the Shipment.
• Ship-On-Condition.
• Hold the Shipment.

The final decision will be taken by the Head of Project Management / Head of IA Delivery in
consultation with the QHSE Advisor.
The CUSTOMER will be invited to a Go-NoGo FAT meeting to determine, based on the Pre-FAT
status and outcomes, whether the FAT can proceed or needs to be postponed.
The CUSTOMER will be informed of all witness and Hold points during testing, as well as all
notifications regarding FATs.The final decision will be taken by the Head of Project Management
in consultation with the QHSE Advisor.

4.3 Lessons-Learned
It is essential to learn from mistakes and successes. The Lessons Learned process is a key
process in the continuous improvement journey of Ekium. It is usually done for each project at
the end of each milestone (tender phase, engineering, procurement, construction and contract
close out).
The Lessons Learned process should be performed with the relevant project team member. It
should be performed with a constructive mindset to reach operational excellence.
The applicable template is 7C-80–A02–EQS–005 – Fiche de Retour d’Expérience

Project Quality Plan Page 22 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 23 of 29

4.4 Control of non-compliances

For the control of non-compliances, Ekium applies the instructions of the procedure 7C-80-PI-
PRO-010-Gestion des écarts et des ameliorations.Customer Satisfaction

4.5 Customer Satisfaction

Ekium assesses YOKOGAWA’s satisfaction informally through steering committees when
appropriate, progress meetings, communications exchanged and various contacts.
Ekium assesses YOKOGAWA’s satisfaction formally through a form formalized by the customer:
the Ekium Customer Satisfaction Evaluation Form sent by email via the ESC app and/or
YOKOGAWA’s evaluation forms.
The observations mentioned in this form are handled by the Contract Manager and the QHSE
department. The processing of these data is taken into account to improve customers satisfaction.

Project Quality Plan Page 23 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 24 of 29

REVIEW AND APPROVAL OF PROJECT QUALITY PLAN

5.1 Review and approval
This Project Quality Plan is specific to this Project.

The document is created, reviewed, and approved by:

• Written by : Project Manager
• Checked by: Head of Service
• Approved by: Project Manager

5.2 PQP distribution

The PQP is distributed to all project personnel prior to their involvement.
Everyone joining this project undergoes a training session on PQP requirements.
This training is documented using the QHSE application “causerie”

5.3 PQP revision

The PQP undergoes regular review and updates as needed, adapting to changes in the project or
integrating approved enhancements to the document.
Individuals outlined in chapter 5.1 are responsible for making these updates.
Additionally, the PQP will be revised at the onset of each phase if required.

Project Quality Plan Page 24 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 25 of 29

Annex 1 – CERTIFICATION ISO 9001 - 2015

Project Quality Plan Page 25 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 26 of 29

Annex 2 – General Policy

Project Quality Plan Page 26 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 27 of 29

Project Quality Plan Page 27 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 28 of 29

Annex 3 – SSE EKIUM ENGAGEMENTS

Project Quality Plan Page 28 of 29

 Document Number
Project Quality Plan
2VFCE0-QSE-PP-002

Revision: 021 Step: IFR

Document Type: SCH Family Equip.: NA Discipline: PCM Class: 2 Date: 135-OctNov-2024

CONTRACTOR Reference: Page 29 of 29

Annex 4 – Deliverables List

Project Quality Plan Page 29 of 29