Project Management Manual (PMM) - 02
Project Management Manual (PMM) - 02
Project Management Manual (PMM) - 02
UPDATING
The BEE Department or the document owner will issue updates to all registered holders of each “hard
copy” of this document. The registered holder will be responsible for updating the document by
replacing pages or sections as instructed. Printed copies will automatically assume as “unmaintained”
status.
ISSUE PAGE
Prepared by
Table of Contents
I. Purpose ............................................................................................................................................................14
i. Glossary ...................................................................................................................................................14
ii. Ownership ................................................................................................................................................14
iii. Application.........................................................................................................................................14
iv. Maintenance of This Document .........................................................................................................14
v.Document Roles and Responsibilities / Authority Matrix ..........................................................................14
II. Structure of the Manual .....................................................................................................................................15
1 Introduction .......................................................................................................................................................18
1.1 Project Management Manual (PMM) .................................................................................................18
1.2 PMM Sections ...................................................................................................................................18
1.3 How to read PMM .............................................................................................................................21
1.4 Supporting Documents ......................................................................................................................23
2 Glossary ............................................................................................................................................................26
2.1 Glossary Table ..................................................................................................................................26
3 Project Lifecycle and Stage Gate Process ........................................................................................................84
3.1 Project Lifecycle ................................................................................................................................84
3.2 Stage Gate Review Process .............................................................................................................92
3.3 Key Performance Indicators (KPIs) ...................................................................................................96
3.4 Attachments ......................................................................................................................................97
4 Five-Year Projects Portfolio Planning .............................................................................................................100
4.1 PMM-004-FYP-010 Initiate Projects Portfolio at Cluster Level ........................................................102
4.2 PMM-004-FYP-020 Develop and Confirm Initial Cluster Projects Portfolios ...................................107
4.3 PMM-004-FYP-030 Screen NWC Initial Projects Portfolio ..............................................................122
4.4 PMM-004-FYP-040 Develop Draft FYPPP and Submit for Review .................................................131
4.5 PMM-004-FYP-050 Update FYPPP and Prepare Annual Capital Works Plan ................................134
4.6 PMM-004-FYP-060 Develop Final FYPPP and Annual Capital Works Plan and Submit to MOF for
Budget Approval ..............................................................................................................................136
4.7 PMM-004-FYP-070 Five-Year Projects Portfolio Variation Control .................................................140
4.8 Key Performance Indicators (KPIs) .................................................................................................148
4.9 Attachments ....................................................................................................................................148
5 Project Team Management .............................................................................................................................152
5.1 Project Management Team Roles ...................................................................................................152
5.2 Responsibility Assignment Matrix (RAM) ........................................................................................155
5.3 Key Performance Indicators (KPIs) .................................................................................................156
5.4 Attachments ....................................................................................................................................156
6 Project Governance Management ..................................................................................................................160
6.1 PMM-006-GOV-010 Enterprise Environmental Factors and Organizational Process Assets ..........160
6.2 PMM-006-GOV-030 Project Initiator and Sponsor ..........................................................................164
Table of Figures
Figure 1-1 Example Flowchart ............................................................................................................................... 22
Figure 3-1 “Design-Bid-Build” Project Lifecycle ..................................................................................................... 85
Figure 3-2 “Design & Build” Project Lifecycle ........................................................................................................ 86
Figure 3-3 The Stage Gate Process Flowchart ...................................................................................................... 94
Figure 3-4 Simplified Stage Gate Process Flowchart ............................................................................................ 95
Figure 3-5 Gate Committee ................................................................................................................................... 96
Figure 4-1 Road Map for Five-Year Projects Portfolio Planning .......................................................................... 101
Figure 4-2 High-Level Process Map for Project Integration Management ........................................................... 102
Figure 4-3 PMM-004-FYP-010 Initiate Projects Portfolio s at Cluster Level Flowchart ........................................ 103
Figure 4-4 PMM-004-FYP-020 Develop and Confirm Initial Cluster Projects Portfolios Flowchart ...................... 108
Figure 4-5 PMM-004-FYP-030 Screen NWC Initial Projects Portfolio Flowchart ................................................. 123
Figure 4-6 PMM-004-FYP-040 Prepare Draft FYPPP and Submit for Review Flowchart .................................... 132
Figure 4-7 PMM-004-FYP-050 Update FYPPP and Prepare Annual Capital Works Plan Flowchart ................... 134
Figure 4-8 PMM-004-FYP-060 Prepare Final FYPPP and Annual Capital Works Plan and Submit to MOF for Budget
Approval Flowchart .............................................................................................................................................. 137
Figure 4-9 PMM-004-FYP-070 Five-Year Projects Portfolio Variation Control Flowchart .................................... 141
Figure 6-1 PMM-006-GOV-010 Enterprise Environmental Factors and Organizational Process Assets Flowchart
............................................................................................................................................................................ 162
Figure 6-2 PMM-006-GOV-030 Project Initiator and Sponsor Flowchart ............................................................. 165
Figure 6-3 PMM-006-GOV-040 End User Flowchart ........................................................................................... 167
Figure 6-4 The Recurring Cycle of Continual Improvement ................................................................................. 171
Figure 6-5 PMM-006-GOV-050 PMM Update and Continual Improvement Flowchart ........................................ 172
Figure 6-6 PMM-006-GOV-060 Control of Project Management Documents Flowchart...................................... 176
Figure 6-7 PMM-006-GOV-070 Control Responsibilities and Authorities Flowchart ............................................ 180
Figure 6-8 PMM-006-GOV-080 Management Representative Flowchart ............................................................ 183
Figure 6-9 PMM-006-GOV-100 Management Review Flowchart ........................................................................ 185
Figure 6-10 PMM-006-GOV-110 Human Resources Centralization Flowchart .................................................... 186
Figure 6-11 PMM-006-GOV-120 Infrastructure Flowchart ................................................................................... 189
Figure 6-12 PMM-006-GOV-130 Work Environment Flowchart ........................................................................... 190
Figure 6-13 PMM-006-GOV-140 PMM user feedback Flowchart ........................................................................ 192
Figure 6-14 PMM-006-GOV-160 Internal Audit Flowchart ................................................................................... 194
Figure 6-15 PMM-006-GOV-170 Monitoring & Measurement of PMM Processes Flowchart .............................. 197
Figure 6-16 PMM-006-GOV-180 Stage Gate Review Flowchart ......................................................................... 200
Figure 6-17 PMM-006-GOV-190 Project Management Data Analysis Flowchart ................................................ 204
Figure 7-1 High-Level Process Map for Project Integration Management ........................................................... 215
Figure 7-2 PMM-007-INT-010 Develop the Project Charter Flowchart ................................................................ 216
Figure 7-3 PMM-007-INT-015 Plan Project Integration Management Flowchart ................................................. 218
Figure 7-4 PMM-007-INT-020 Develop the Project Management Plan Flowchart ............................................... 223
Figure 7-5 PMM-007-INT-023 Site Handover to Contractor and Consultant Work Commencement Flowchart .. 231
Figure 7-6 PMM-007-INT-026 Conduct Project Kick Off Meeting Flowchart ........................................................ 239
Figure 7-7 Directing the Project in Design-Bid-Build Projects .............................................................................. 241
Figure 7-8 Directing the Project in Design & Build Projects ................................................................................. 241
Figure 12-1 High-Level Process Map for Project Quality Management ............................................................... 461
Figure 12-2 PMM-012-QUA-010 Plan Project Quality Management Flowchart ................................................... 463
Figure 12-3 PMM-012-QUA-020 Perform Quality Assurance Flowchart.............................................................. 469
Figure 12-4 PMM-012-QUA-030 Perform Quality Control Flowchart ................................................................... 477
Figure 13-1 High-Level Process Map for Project Human Resources Management ............................................. 493
Figure 13-2 PMM-012-QUA-010 Plan Project Human Resource Management Flowchart .................................. 495
Figure 13-3 PMM-013-HUM-020 Acquire the Project Team Flowchart................................................................ 499
Figure 13-4 PMM-013-HUM-050 Close the Project Team Flowchart .................................................................. 508
Figure 14-1 High-Level Process Map for Project Communication Management ................................................. 514
Figure 14-2 PMM-014-COM-010 Plan Project Communications Flowchart ......................................................... 516
Figure 14-3 PMM-014-COM-020 Distribute Confidential Correspondence from Consultant/Contractor to NWC
Flowchart ............................................................................................................................................................. 522
Figure 14-4 PMM-014-COM-030 Distribute Confidential Correspondence from NWC to Consultant/Contractor
Flowchart ............................................................................................................................................................. 524
Figure 14-5 PMM-014-COM-040 Distribute Non-Confidential Correspondence from Consultant to NWC Flowchart
............................................................................................................................................................................ 528
Figure 14-6 PMM-014-COM-050 Distribute Non-Confidential Correspondence from Contractor to NWC Flowchart
............................................................................................................................................................................ 530
Figure 14-7 PMM-014-COM-060 Distribute Non-Confidential Correspondence from NWC to Consultant Flowchart
............................................................................................................................................................................ 533
Figure 14-8 012-COM-070 Distribute Non-Confidential Correspondence from NWC to Contractor Flowchart .... 536
Figure 14-9 PMM-014-COM-080 Distribute Non-Confidential Correspondence from Supervision Consultant to
Contractor Flowchart ........................................................................................................................................... 539
Figure 14-10 PMM-014-COM-090 Distribute Submittals for Approval Flowchart ................................................. 543
Figure 14-11 PMM-014-COM-100 Distribute Non-Conformance Report (NCR) Flowchart .................................. 547
Figure 14-12 PMM-014-COM-110 Distribute Request for Information (RFI) Flowchart ....................................... 553
Figure 14-13 Objectives Cascade Model ............................................................................................................. 557
Figure 14-14 PMM-014-COM-115 Cascade Objectives Flowchart ...................................................................... 557
Figure 14-15 PMM-014-COM-120 Perform Design Performance Reporting Flowchart ....................................... 559
Figure 14-16 PMM-014-COM-130 Perform Construction Performance Reporting Flowchart .............................. 563
Figure 15-1 High-Level Process Map for Project Risk Management ................................................................... 576
Figure 15-2 PMM-015-RIS-010 Risk Management at Portfolio levels Flowchart ................................................. 577
Figure 15-3 Relation between Risk Process and Risk Workshops ...................................................................... 583
Figure 15-4 PMM-015-RIS-020 Plan Project Risk Management at Project Level Flowchart ............................... 584
Figure 15-5 PMM-015-RIS-030 Identify Risks at Project Level Flowchart ........................................................... 588
Figure 15-6 PMM-015-RIS-040 Qualitative Risk Analysis at Project Level Flowchart ......................................... 596
Figure 15-7 PMM-015-RIS-050 Quantitative Risk Analysis at Project Level Flowchart ....................................... 597
Figure 15-8 PMM-015-RIS-060 Plan Risk Responses at Project Level Flowchart .............................................. 600
Figure 15-9 PMM-015-RIS-070 Implement Risk Responses at Project Level Flowchart ..................................... 603
Figure 15-10 PMM-015-RIS-080 Monitor Risk Responses at Project Level Flowchart ........................................ 605
Figure 16-1 High-Level Process Map for Project Procurement Management ...................................................... 614
Figure 16-2 PMM-PRO-010 Plan Purchases and Acquisitions at Portfolio Level Flowchart ................................ 616
Figure 16-3 PMM-016-PRO-020 Plan Project Procurement Management Flowchart .......................................... 622
Figure 16-4 PMM-016-PRO-025 Acquire Project Land ....................................................................................... 626
Figure 16-5 PMM-016-PRO-030 Prepare Tender Documents ............................................................................. 628
Table of Tables
Table II-1 Project Management Manual Sections .................................................................................................. 15
Table 1-1 Flowchart Shapes Legend ..................................................................................................................... 23
Table 2-1 The Glossary Table ............................................................................................................................... 26
Table 3-1 Project Status Indicators ........................................................................................................................ 92
Table 3-2 Project Life Cycle and Stage Gate Process KPIs .................................................................................. 97
Table 3-3 Project Lifecycle and Stage Gate Process forms, templates and guidelines ......................................... 97
Table 4-1 Five-Year Projects Portfolio Planning KPIs ......................................................................................... 148
Table 4-2 Project Five-Year Projects Portfolio Planning forms, templates and guidelines................................... 148
Table 5-1 Cluster Projects Team Roles that Involved in PMM ............................................................................. 152
Table 5-2 HQ Projects Team Roles that Involved in PMM................................................................................... 153
Table 5-3 Second Party Roles ............................................................................................................................. 155
Table 5-4 Project Team Management forms, templates and guidelines .............................................................. 156
Table 6-1 Project Governance Management KPIs .............................................................................................. 205
Table 6-2 Project Governance Management forms, templates and guidelines .................................................... 209
Table 7-1 Project Integration Management KPIs ................................................................................................. 263
Table 7-2 Project Integration Management forms, templates and guidelines ...................................................... 265
Table 8-1 Project Scope Management KPIs ........................................................................................................ 349
Table 8-2 Project Scope Management forms, templates and guidelines ............................................................. 350
Table 9-1 Project Value Engineering KPIs........................................................................................................... 378
Table 9-2 Project Value Engineering forms, templates and guidelines ................................................................ 378
Table 10-1 Schedule Levels Layout Over Project Life Cycle ............................................................................... 384
Table 10-2 Project Schedule Management KPIs ................................................................................................. 411
Table 10-3 Project Schedule Management forms, templates and guidelines ...................................................... 413
Table 11-1 Cost Estimate Classes ...................................................................................................................... 418
Table 11-2 Project Cost Management KPIs ......................................................................................................... 456
Table 11-3 Project Cost Management forms, templates and guidelines .............................................................. 458
Table 12-1 Project Quality Management KPIs ..................................................................................................... 485
Table 12-2 Project Quality Management forms, templates and guidelines .......................................................... 486
Table 13-1 Project Human Resource Management KPIs .................................................................................... 510
Table 13-2 Project Human Resource Management forms, templates and guidelines ......................................... 510
Table 14-1 Project Communications Management KPIs ..................................................................................... 569
Table 14-2 Project Communications Management forms, templates and guidelines .......................................... 570
Table 15-1 Project Risk Management KPIs ......................................................................................................... 607
Table 15-2 Project Risk Management forms, templates and guidelines .............................................................. 608
Table 16-1 Project Procurement Management KPIs ........................................................................................... 672
Table 16-2 Project Procurement Management forms, templates and guidelines ................................................. 674
Table 17-1 Project Health, Safety & Environmental Management KPIs .............................................................. 706
Table 17-2 Project Health, Safety & Environmental Management forms, templates and guidelines ................... 709
Table 18-1 Project Financial Management KPIs .................................................................................................. 725
Table 19-1 Project Claim Management KPIs ....................................................................................................... 749
Table 19-2 Project Claim Management forms, templates and guidelines ............................................................ 749
PREAMBLE
I. Purpose
The purpose of this manual is to standardize the Project Management processes, procedures, templates
and forms that applied to all NWC Capital Projects that managed by Projects & Technical Services
sector.
i. Glossary
Refer to PMM section 2.
ii. Ownership
This document is owned by the NWC PMO GM.
iii. Application
This Project Management Manual (PMM) is applicable to all NWC Projects.
iv. Maintenance of This Document
This document will be maintained by the document owner and will follow the Change Management
Process; 00_BEED_PP_001 - Change Management Process.
This document will be reviewed regularly.
v. Document Roles and Responsibilities / Authority Matrix
This manual records the roles and responsibilities specifically related to the document including
who is responsible for the review / endorsement / approval of the document.
Prepare /
Maintain
Update / Review Endorse Approve Publish
Register
Amend
Owner YES
Section
Abbreviation Title
No.
1 IND Introduction
2 GLO Glossary
Section 1 - Introduction
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022
Abdulaziz K. Aljawan
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020
Abdullah M. Albani
1 Introduction
The subject of this particular section of the Project Management Manual (PMM) is to introduce the
Project Management Manual.
The Project Management Manual (PMM) identifies the principles and objectives of project management
for NWC projects, as mandated by NWC, which must be adhered to by HQ and the Clusters Projects &
Technical Services team members.
1.1 Project Management Manual (PMM)
The Project Management Manual (PMM) identifies the principles and objectives of project
management for NWC projects, as mandated by the NWC Projects & Technical Services
department, and which must be adhered to by NWC Project Managers and their Project Teams.
The management system also includes flowcharts, attachments and learning support materials.
The manual identifies and describes each of these types of management system document in their
context and serves to pull them together into a unified and integrated set.
Project Teams include Second Party Design Consultants, Supervision Consultants and
Contractors, as well as NWC staff from the Clusters and Various NWC staff performing corporate
functions at the headquarters (HQ) in Riyadh also interact with projects on a routine, periodic or
occasional basis. A special example is the NWC Projects & Technical Services department, which
exercises governance over the projects in each Cluster. Other examples include the Procurement
department, which engages the Second Parties through formal tendering and contract award, and
the Finance department, which controls payments to the Second Parties and ensures that adequate
financial resources are available to support the projects. The manual and its underlying
management system are mandated for use by all internal staff and external Second Parties who
are involved in the delivery of NWC projects.
The manual is following the best practice framework of knowledge areas defined in the PMBOK
Guide, issued by the Project Management Institute (PMI).
1.2 PMM Sections
Each section of the manual has its own process map showing the processes. These processes are
numbered in the high-level process map within each section of the manual where user can find the
relevant detail in the format of a flowchart.
The procedures also show how to use the relevant forms, templates or guidelines, which are also
provided as part of the manual and are uniquely identified with system document numbers.
An outline of each section is provided in the following sub-sections:
1.2.1 PMM-001-IND Introduction
The Introduction section (i.e. this section) provides an overview of the management system.
1.2.2 PMM-002-GLO Glossary
The Glossary section defines all the terms used throughout the management system and cites
their sources, for example: the “Project Management Body of Knowledge” (PMBOK)
maintained by the Project Management Institute (PMI), so that the reader may go and research
these sources for their origins and for further information.
procured to execute the project. However, the NWC Project Manager has overall responsibility
for ensuring that the project is delivered in a timely manner. This section describes the
mandated approach to Project Schedule Management.
1.2.11 PMM-011-COS Project Cost Management
The Project Cost Management section describes how the cost of executing the project must
initially be estimated, then firmly budgeted and later it must be controlled to within the budget.
Unlike Project Schedule Management, much of the discipline of Project Cost Management is
“owned” by the NWC Project Manager, who has overall responsibility for ensuring that the
project is delivered in a cost-effective manner. This section describes the mandated approach
to Project Cost Management.
1.2.12 PMM-012-QUA Project Quality Management
The Project Quality Management section is a very broad discipline, concerned with ensuring
that internal and external requirements, are properly defined and assuring that the
requirements will be met through effective work processes including control measures. The
approach to quality management follows the universally accepted plan-do-check-act model
(the Deming Cycle) and is described throughout the project lifecycle in this section of the
manual.
1.2.13 PMM-013-HUM Project Human Resource Management
The Project Human Resources Management section describes how the project team is brought
together, how competence requirements are managed (especially in support of quality, health,
safety, environment, risk and value) and how the project team is ultimately closed, with capture
of lessons learned. The NWC approach to human resource management is a collaborative
partnering approach. This approach uses open communications and constructive feedback are
given on issues, performance feedback and opportunities for continuous improvement.
1.2.14 PMM-014-COM Project Communications Management
The Project Communications Management section describes effective communication
processes, through effective stakeholder management, communications planning, information
distribution and performance reporting. All are defined in this section of the manual.
1.2.15 PMM-015-RIS Project Risk Management
The Project Risk Management section describes how project risks are identified, analyzed,
planned, monitored and controlled to the point of mitigation or fruition. This applies throughout
the project lifecycle and the approach to be adopted is scaled to the cost and complexity of the
project from an early stage.
1.2.16 PMM-016-PRO Project Procurement Management
The Project Procurement Management section describes how procurement starts early in the
project with a clear strategy to decide the best contracting method for the project. The process
also involves maintaining a healthy climate of pre-qualification and re-qualification to NWC’s
list of authorized project vendors, as NWC seeks to build long-lasting and effective business
relationships for repeated successes in project execution. A key requirement of procurement
is to include the Project Management Plan in the tender documents whenever seeking to
procure Second Party services for project execution. All of these proactive steps, and the steps
of regular contract administration right up to contract closure, are described in this section of
the manual.
In addition, this section describes the processes of Site Handover, Kickoff Meeting, Project
Suspension and Project Withdrawal.
The NWC Supply Management Policy and Procedure Manual is cross-referenced where
appropriate.
1.2.17 PMM-017-HSE Project Health, Safety & Environmental Management
The Project Health, Safety and Environmental Management section describes where potential
to cause harm to persons and to the environment is proactively reduced to acceptable minimum
levels. The approaches to planning, assurance and control are described in this section of the
manual.
1.2.18 PMM-018-FIN Project Financial Management
The Project Financial Management section describes how the funding of projects is planned,
controlled, monitored and reported to provide better control on finance processes.
1.2.19 PMM-019-CLA Project Claim Management
Project Claim Management section describes how to seek to avoid claims from both sides:
Second Party to NWC and NWC to Second Party. However, construction is a complex sector
of industry and the possibility of claims always remains high. Therefore, this section of the
manual describes how claims must be identified, quantified and resolved, in the event that the
prescribed methods of prevention cannot deal with every possible situation.
1.3 How to read PMM
It is strongly recommended to read this section first (Introduction Section); then read Section 2
Project Lifecycle and Section 5 (Project Team Management), before looking at the other sections
in any order.
Section 2 Glossary is to occasionally be visited as per required.
Section 6 Governance shall be of most interest to PMO department.
Generally, each section consists of:
● Firstly, a history of the section.
● Secondly, an introduction to the section.
● Thirdly, the section processes are detailed next. Each process contains process objective,
number of policies, procedures and one flowchart. The flowchart corelates procedures
together and in some cases links them to other processes as necessary. Each process
flowchart illustrates how inputs and outputs are linked when applicable.
● Fourthly, the section presents number of Key Performance Indicators (KPIs). Each KPI
explains the subject, the application frequency and measurement scale.
● Fifthly, at the section end, the section attachments (forms, templates and guidelines) are
listed.
The sections “Introduction”, “Project Lifecycle and Stage Gate Process”, “Project Team
Management” and “Glossary” deviate from this section structure as they have no processes. They
are structured as follows:
● Firstly, a history of the section.
● Secondly, an introduction to the section.
● Thirdly, the section details are represented.
● Fourthly, at the section end, the section attachments (forms, templates and guidelines) are
listed.
To understand how flowcharts are read, let us take the below example for a hypothetical process
PMM-020-XXX-050 which is the fifth process in section 20. The letters XXX are the abbreviation of
the section name (e.g. PRO is for Procurement Section).
In procedure numbering, there is an additional number which distinguishes the procedure within the
process.
Figure 1-1 Example Flowchart
● Horizontal lanes represent the Entities (HQ, Cluster, Design Consultant, Supervision
Consultant or Contractor) which shall perform the procedures in each. This process is
performed by “Design Consultant” and “Cluster”.
● Vertical lanes represent the stages (e.g. Tender for Design, Design, Tender for Construction,
Construction etc.) in which the procedures are performed. This process is performed in 2
stages “Tender for Design Stage” and “Design Stage”.
● If a template is used in a procedure, it shall be located above the procedure.
● The person who is responsible to perform a procedure, his role shall be located below the
procedure.
● Every procedure located on a horizonal boundary (e.g. PMM-020-XXX-050-040) is
performed jointly by the two parties.
● Every procedure located on a vertical boundary (e.g. PMM-020-XXX-050-020) can be
performed during one or both of the stages.
● The shapes which are illustrated in the flowchart are described in the below table.
TO PERFORM ANY PROCESS, DO NOT RELY ON FLOWCHART ONLY APART OF THE
OBJECTIVE, POLICIES, PROCEDURES AND FORMS OF THE PROCESS.
Section 2 - Glossary
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This section is developed as an update to “Glossary” section in first version the Project
Management Manual (PMM) which developed by Faithful + Gould. The following are
Change the changes:
Description
● Added number of definitions.
● Deleted number of definitions.
2 Glossary
The subject of this particular section of the Project Management Manual (PMM) is the Glossary for the
PMM.
2.1 Glossary Table
Table 2-1 The Glossary Table
Term Definition
Acceptance Criteria Those defined, written criteria, including performance requirements and
essential conditions, which must be met before project deliverables can be
accepted.
Acquire Project The process of obtaining the human resources needed to complete the
Team project.
Activity Attributes Multiple attributes associated with each schedule activity that can be
included within the activity list. Activity attributes include activity codes,
predecessor activities, successor activities, logical relationships, leads and
lags, resource requirements, imposed dates, constraints and assumptions.
Activity Code One or more numerical or text values that identify characteristics of the
work or in some way categorize the schedule activity that allows filtering
and ordering of activities within reports.
Activity Definition The process of identifying the specific schedule activities that need to be
performed to produce the various project deliverables.
Activity Description A short phrase or label for each schedule activity used in conjunction with
(AD) an activity identifier to differentiate that project schedule activity from other
schedule activities. The activity description normally describes the scope of
work of the schedule activity.
Activity Duration The time in calendar units between the start and finish of a schedule
activity. See also Actual Duration, Original Duration and Remaining
Duration.
Activity Duration The process of estimating the number of work periods that will be needed
Estimating to complete individual schedule activities.
Term Definition
Activity Identifier A short unique numeric or text identification assigned to each schedule
activity to differentiate that project activity from other activities. Typically,
unique within any one project schedule network diagram.
Activity List A documented tabulation of schedule activities that shows the activity
description, activity identifier, and a sufficiently detailed scope of work
description so project team members understand what work is to be
performed.
Activity Resource The process of estimating the types and quantities of resources required to
Estimating perform each schedule activity.
Actual Cost (AC) Total costs actually incurred and recorded in accomplishing work
performed for a schedule activity or work breakdown structure component.
Actual cost can sometimes be direct labor hours alone, direct costs alone,
or all costs including indirect costs. Also referred to as the Actual Cost of
Work Performed (ACWP). See also Earned Value Management and
Earned Value Technique
Actual Duration The time in calendar units between the actual start date of the schedule
activity and either the data date of the project schedule if the schedule
activity is in progress or the actual finish date if the schedule activity is
complete.
Actual Finish Date The point in time that work actually ended on a schedule activity. (Note: in
(AF) some application areas, the schedule activity is considered “finished” when
work is “substantially complete”).
Actual Start Date The point in time that work actually started on a schedule activity.
(AS)
Advanced Payment A payment to a second party who is awarded a Contract with an approved
budget. This payment is paid to the second party at amount and time
identified in the contract.
Advanced Payment A bank bond provided by contractor to get an advance payment. It equals
Bond to the advance payment.
Term Definition
Alternate Dispute Methods, other than litigation, for resolving disputes including arbitration,
Resolution (ADR) mediation and mini-trials.
Analogous An estimating technique that uses the values of parameters, such as scope,
Estimating cost, budget and duration, or measures of scale, such as size, weight and
complexity, from a previous, similar activity as the basis for estimating the
same parameter or measure for a future activity. It is frequently used to
estimate a parameter when there is a limited amount of detailed information
about the project (e.g. in the early phases).
Analogous estimating is a form of expert judgment. Analogous estimating
is most reliable when the previous activities are similar in fact and not just
in appearance, and the project team members preparing the estimates
have the needed expertise.
Annual Capital It is a slice of the Five-Year Projects Portfolio Plan for the forthcoming year
Works Plan (ACWP) only.
It reflects the Capital Works planned for only the next year and the
associated financial obligations.
This plan is required by the Ministry of Finance (MOF) to formally assess
and ultimately grant annual budget to NWC.
Application Area A category of projects that have common components significant in such
projects but are not need or present in all projects. Application areas are
usually defined in terms of either the product (i.e. by similar technologies or
production methods) or the type of customer (i.e. internal versus external,
government versus commercial) or industry sector (i.e. utilities, automotive,
aerospace, information technologies). Application areas can overlap.
Approved Variation A variation request that has been processed through the Variation Control
process and approved.
Arrow Diagramming A schedule network diagramming technique in which schedule activities are
Method (ADM) represented by arrows. The tail of the arrow represents the start, and the
head represents the finish of the schedule activity. (The length of the arrow
does not represent the expected duration of the scheduled activity.)
Schedule activities are connected at points called nodes (usually drawn as
small circles) to illustrate the sequence in which the schedule activities are
expected to be performed.
See also Precedence Diagramming Method
Term Definition
Assumptions Assumptions are factors that, for planning purposes, are considered to be
true, real or certain without proof or demonstration. Assumptions affect all
aspects of project planning and are part of the progressive elaboration of
the project. Project teams frequently identify, document and validate
assumptions as part of their planning process.
Assumptions generally involve a degree of risk.
Audit Evidence Records, statements of fact or other information which are relevant to the
audit criteria and verifiable.
Audit Findings Results of the evaluation of the collected audit evidence against audit
criteria.
Audit Schedule Set of one or more audits planned for a specific time frame and directed
towards a specific purpose.
Audit Team One or more auditors conducting an audit, supported if needed by technical
experts.
Authority The right to apply project resources, expend funds, make decisions, or give
approvals.
Term Definition
Backward Pass The calculation of late finish dates and late start dates for the uncompleted
portions of all schedule activities. Determined by working backwards
through the schedule network logic from the project’s end date. The end
date may be calculated in a forward pass or set by the customer or sponsor.
See also Schedule Network Analysis
Bar Chart A graphic display of schedule-related information. In the typical bar chart,
schedule activities or work breakdown structure components are listed
down the left side of the chart, dates are shown across the top and activity
durations are shown as date-placed horizontal bars. Also called a Gantt
chart.
Baseline Finish Date The finish date of a schedule activity in the approved schedule baseline.
See also Scheduled Finish Date
Baseline Start Date The start date of a schedule activity in the approved schedule baseline. See
also Scheduled Start Date
Term Definition
Basic Design Data It is a project specific document that generated by the Design Consultant
(BDD) in full and prompt assistance from NWC. BDD describes the current site
conditions which are required to design the project.
BDD shall be completed early at the beginning of the design stage and
submitted to NWC for approval. BDD to be developed and approved before
finalizing:
● Project Design Basis Report (DBR)
● Design Criteria.
BDD must be updated by the Design Consultant as required throughout the
design stage.
BDD includes but not limited to the following:
● Prepared by Design Consultant
○ Brief project description describes project capacity, design
requirements, risks, open issues, etc. (extracted from RFP).
○ HSE plan
○ Meteorological Information
○ Any other information / data stated in the contract.
● Provided by NWC
○ Environmental Studies
○ Meteorological Studies
○ Seismic studies
○ Topographical Survey Plans
○ Tidal records
○ Land Boundary Plans
○ Geotechnical reports (Site Investigation and Interpretive).
○ Existing Utility surveys reports and future utility plans.
○ NWC design guidelines / templates / checklists.
○ NWC standard technical specifications and BoQ.
○ NWC project related policies and regulations such as HSE,
Assets, etc.
○ Any other information / data stated in the contract.
Term Definition
Benchmark A point of reference for measuring against, i.e. Project progress, cost and
quality. Benchmarking evaluates various aspects of a project (or process)
in relation to best practice or agreed parameters.
Blueprint The detailed schedule, plan, strategy or manual for progressing forward.
Brainstorming A general data gathering and creativity technique that can be used to
identify risks, ideas or solutions to issues by using a group of team
members or subject-matter experts. Typically, a brainstorming session is
structured so that each participant’s ideas are recorded for later analysis.
Budget The approved estimate for the project or any work breakdown structure
component or any schedule activity. See also Estimate
Budget at The sum of all the budgets established for the work to be performed on a
Completion (BAC) project or a work breakdown structure component or a schedule activity.
The total planned value for the project.
Budget Cap / An annual limit on the Capital Expenditure (CAPEX) of NWC over a period
CAPEX Cap of Five-Year -set by the Ministry of Finance.
Calendar Unit The smallest unit of time used in scheduling the project. Calendar units are
generally in hours, days or weeks, but can also be in quarter years, months,
shifts or even in minutes.
Term Definition
Capital Development The Capital Development Plan is a five-year Asset Management Plan
Plan focused each financial year (April to March) into a CAPEX plan. The
CAPEX plan is submitted to the Ministry of Water and Electricity and the
Ministry of Finance, in order to obtain ministerial approval and to secure
budgetary funding on an annual basis. During this process, the asset
requirements are described in terms of project requirements, in order to
deliver the intended asset at the right time, cost and quality.
Capital Works Plan An annual submission by Entities to the MOF for budget review / approval.
Cash Flow Forecast Modeling of NWC’s expected future financial commitment to projects /
assets based on current information.
Center for Spending It is a governmental agency that is responsible for ensuring the efficiency
Efficiency (CSE) of expenditure in governmental projects.
In February 2021, it is merged with National Project Management
Organization (Mashroat) to constitute Expenditure Efficiency & Projects
Authority (EXPRO)
Chart of Accounts Any numbering system used to monitor project costs by category (e.g.
labor, supplies, materials and equipment). The project chart of accounts is
usually based upon the corporate chart of accounts of the primary
performing organization.
Contrast with Code of Accounts.
Close Project The process of finalizing all activities across all of the project process
groups to formally close the project or phase.
Term Definition
Closing Processes Those processes performed to formally terminate all activities of a project
or stage and transfer the completed product to others or close a cancelled
project.
Co-Location An organizational placement strategy where the project team members are
physically located close to one another in order to improve communication,
working relationships and productivity.
Communication The document that describes: the communications needs and expectations
Management Plan for the project; how and in what format information will be communicated;
when and where each communication will be made; and who is responsible
for providing each type of communication. A communications management
plan section can be formal or informal, highly detailed or broadly framed,
based on the requirements of the project stakeholders. The communication
management plan is contained as a section in the Project Management
Plan.
Configuration A component of the project management plan that describes how to identify
Management Plan and account for project artifacts under configuration control, and how to
record and report changes to them.
Primarily, it describes how control the version of project’s assets
Configuration A collection of procedures used to track project artifacts and monitor and
Management control changes to these artifacts.
System
Primarily, it is version control for the organization's assets.
Term Definition
Constraint The state, quality or sense of being restricted to a given course of action or
inaction. An applicable restriction or limitation, either internal or external to
the project that will affect the performance of the project or a process. For
example, a schedule constraint is any limitation or restraint placed on the
project schedule that affects when a schedule activity can be scheduled
and is usually in the form of fixed imposed dates. A cost restraint is any
limitation or restraint placed on the project budget such as funds available
over time. A project resource constraint is any limitation or restraint placed
on resource usage, such as what resource skills or disciplines are available
and the amount of a given resource available during a specified time frame.
Constructability The ease, safety, economy, and clarity of construction of a project. It mainly
focuses on reviewing:
● Logic of activity relations.
● Colocation in execution works.
Construction Permit Means the permit to commence construction activities issued by the
relevant municipality.
Contract The process of managing the contract and the relationship between the
Administration buyer and the seller, reviewing and documenting how a seller is performing
or has performed to establish required corrective actions and provide a
basis for future relationships with the seller, managing contract related
variations and, when appropriate, managing the contractual relationship
with the outside buyer of the project.
Contract Closure The process of completing and settling the contract, including resolution of
any open items and closing each contract.
Term Definition
Contract Documents Documents that consist of an agreement between owner (client) and
Contractor, and include conditions of the contract, drawings, specifications,
and other documents listed in the agreement.
Corrective Action Documented direction for executing the project work to bring expected
future performance of the project work in line with the Project Management
Plan.
Action to eliminate the cause of a detected nonconformity or other
undesirable situation.
Cost The monetary value or price of a project activity or component that includes
the monetary worth of the resources required to perform and complete the
activity or component, or to produce the component. A specific cost can be
composed of a combination of cost components including direct labor
hours, other direct costs, indirect labor hours, and purchased price.
(However, in the earned value management methodology, in some
instances, the term cost can represent only labor hours without conversion
to monetary worth.) See also Actual Cost and Estimate
Cost Benefit The quantification of a Value Improvement (VI) Opportunity in terms of the
Analysis (CBA) cost of realizing the potential benefits considered against the value of the
potential benefits.
Cost Budgeting The process of aggregating the estimated costs of individual activities or
work packages to establish a cost baseline.
Cost Control The process of influencing the factors that create variances and controlling
variations to the project budget.
Cost Estimate Evaluation of all costs of the elements of a project or effort as supported by
an agreed-upon-scope
Term Definition
Cost Estimating The process of developing an approximation of the cost of the resources
needed to complete project activities.
Cost Management The document that sets out the format and establishes the activities and
Plan criteria for planning, structuring and controlling the project costs. A cost
management plan can be formal or informal, highly detailed or broadly
framed, based on the requirements of the project stakeholders. The cost
management plan is contained in, or is a subsidiary plan of, the Project
Management Plan.
Cost Performance A measure of cost efficiency on a project. It is the ratio of earned value (EV)
Index (CPI) to actual costs (AC). CPI = EV divided by AC. A value equal to or greater
than one indicates a favorable condition and a value less than one indicates
an unfavorable condition.
Cost Variance (CV) A measure of cost performance on a project. It is the algebraic difference
between earned value (EV) and actual cost (AC). CV = EV minus AC. A
positive value indicates a favorable condition and a negative value
indicates an unfavorable condition.
Create WBS (Work The process of subdividing the major project deliverables and project work
Breakdown into smaller, more manageable components.
Structure)
Critical Activity Any schedule activity on a critical path in a project schedule. Most
commonly determined by using the Critical Path Method. Although some
activities are “critical”, in the dictionary sense, without being on the critical
path, this meaning is seldom used in the project context.
Critical Chain A schedule network analysis technique that modifies the project schedule
Method to account for limited resources. The critical chain method mixes
deterministic and probabilistic approaches to schedule network analysis.
Term Definition
Critical Path Generally, but not always, the sequence of schedule activities that
determines the duration of the project. Generally, it is the longest path
through the project. However, a critical path can end, as an example, on a
schedule milestone that is in the middle of the project schedule and that
has a finish-no-later- than imposed date schedule constraint. See also
Critical Path Method
Critical Path Method A schedule network analysis technique used to determine the amount of
scheduling flexibility (the amount of float) on various logical network paths
in the project schedule network, and to determine the minimum total project
duration. Early start and early finish dates are calculated by means of a
forward pass, using a specified start date. Late start and finish dates are
calculated by means of a backward pass, starting from a specified
completion date, which sometimes is the project early finish date
determined during the forward pass calculation.
CSE Center for Spending Efficiency which responsible for reviewing of annual
Entity Draft Five-Year Projects Portfolio Plans
Current Finish Date The current estimate of the point in time when a schedule activity will be
completed, where the estimate any reported work progress. See also
Scheduled Finish Date and Baseline Finish Date
Current Invoice A payment certificate other than the Final Invoice that issued to a second
party against his works in a project.
Also known as Interim Payment.
Current Start Date The current estimate of the point in time when a schedule activity will begin,
where the estimate any reported work progress. See also Scheduled Start
Date and Baseline Start Date
Customer The person or organization that will use the project’s product or service or
result. See also User
Organization or person that receives a product.
Cutoff Date The date up to or through which the project’s reporting system has provided
actual status and accomplishments. In some reporting systems, the status
information for the data date is included in the past and in some systems
the status information is in the future. Also known as data date.
Date A term representing the day, month and year of a calendar, and in some
instances, the time of day.
Term Definition
Defect Notification Means the period for notifying defects in the Works or a Section (as the
Period case may be), which for the purposes of the Contract shall be 24 months,
calculated from the date on which the Works are completed (Taking Over
of the Works and Sections).
Deliverable Any unique and verifiable product, result, or capability to perform a service
that must be produced to complete a process, phase, or project. Often used
more narrowly in reference to an external deliverable, which is a deliverable
that is subject to approval by the project stakeholders. See also Product,
Service and Result
Dependability Collective term used to describe the availability performance and its
influencing factors: reliability performance, maintainability performance and
maintenance support performance.
Term Definition
Design and Set of processes that transforms requirements into specified characteristics
Development or into the specification of a product, process or system.
Design Management The management, supervision and evaluation of the design process to
achieve the objectives/criteria set by the project. The project could be the
Employer’s vision, specific requirements, a system or process, or a
strategy.
Term Definition
Design Review A management technique used for evaluating a proposed design to ensure
that the design of the project meets the Employer’s Requirements or to
assure that the design will perform successfully, can be built and can be
maintained.
Design-Build A project life cycle in which the Contractor is responsible for all aspects of
the design and construction of the product in the project contract. The
scope of the contract includes management and design services;
preparation and execution of construction documents; and construction,
Testing & Commissioning of the product.
Develop Project The process of improving the competencies and interaction of team
Team members to enhance project performance.
Deviation Permit Permission to depart from the originally specified requirements of a product
prior to realization.
Direct and Manage The process of executing the work defined in the Project Management Plan
Project Execution to achieve the project’s requirements defined in the project scope
statement.
Discipline A field of work requiring specific knowledge and that has a set of rules
governing work conduct (e.g. civil engineering, cost estimating, etc.)
Discrete Effort Work effort that is separate, distinct and related to the completion of specific
work breakdown structure components and deliverables, and that can be
directly planned and measured. Contrast with Apportioned Effort
Dispute Review A board formed at the start of or early in the project to review and adjudicate
Board any disputes that may arise.
Document A structured method for the control of incoming and outgoing documents.
Management Can be an analogue system or more commonly electronic.
System
Term Definition
Drawings Means the drawings of the Works, as included in the Contract, and any
additional and modified drawings issued by (or on behalf of) the Employer
in accordance with the Contract.
Dummy Activity A schedule activity of zero duration used to show a logical relationship in
the arrow diagramming method. Dummy activities are used when logical
relationships cannot be completely or correctly described with schedule
activity arrows. Dummy activities are generally shown graphically as a
dashed line headed by an arrow.
Duration The total number of work periods required to complete a schedule activity
or work breakdown structure component. Usually expressed as workdays
or workweeks. Sometimes incorrectly equated with elapsed time. Contrast
with Effort. See also Original Duration, Remaining Duration and Actual
Duration.
Early Finish Date In critical path method, the earliest possible point in time on which the
(EF) uncompleted portions of a schedule activity (or the project) can finish,
based on the schedule network logic, the data date, and any schedule
constraints. Early finish dates can change as the project progresses and as
changes are made to the Project Management Plan.
Early Start Date (ES) In critical path method, the earliest possible point in time on which the
uncompleted portions of a schedule activity (or the project) can start, based
on the schedule network logic, the data date, and any schedule constraints.
Early start dates can change as the project progresses and as changes are
made to the Project Management Plan.
Earned Value (EV) The value of work performed expressed in terms of the approved budget
assigned to that work for a schedule activity or work breakdown structure
component. Also referred to as the Budgeted Cost of Work Performed.
Earned Value A specific technique for measuring the performance of work and used to
Technique (EVT) establish the performance measurement baseline (PMB).
Term Definition
Effectiveness Extent to which planned activities are realized and planned results
achieved.
Efficiency Relationship between the result achieved and the resources used.
Effort The number of labor units required to complete a schedule activity or work
breakdown structure component. Usually expressed as staff hours, staff
days, or staff weeks. Contrast with duration.
Enterprise Any or all external environmental factors and internal organizational factors
Environmental that surround or influence the project’s success. These factors are from any
Factors or all of the enterprises involved in the project and include organizational
culture and structure, infrastructure, existing resources, commercial
databases, market conditions and project management software.
EOT Extension-of-Time
EPC Engineering-Procurement-Construction
EPCC Engineering-Procurement-Construction-Commissioning
EPCM Engineering-Procurement-Construction-Management
Establishing the Defining the external and internal parameters to be taken into account
Context when managing risk and setting the scope and risk criteria for the risk
management policy.
Term Definition
Estimate at The expected total cost of a schedule activity, a work breakdown structure
Completion (EAC) component, or the project when the defined scope of work will be
completed. EAC is equal to the actual cost (AC) plus the estimate to
complete (ETC) for all the remaining work. EAC = AC plus ETC. The EAC
may be calculated based on performance to date or estimated by the
project team based on other factors, in which case it is often referred to as
latest revised estimate. See also Earned Value Technique and Estimate to
Complete.
Estimate to The expected cost needed to complete all the remaining work for a
Complete (ETC) schedule activity, work breakdown structure component, or the project. See
also Earned Value Technique and Estimate at Completion
Exception Report Document that includes only major variations from the plan (rather than all
variations).
Term Definition
Exit Interviews Interviews of construction (and project) staff as they leave the project as a
means to record lessons learned.
Expected Monetary A statistical technique that calculates the average outcome when the future
Value (EMV) includes scenarios that may or may not happen. A common use of this
Analysis technique is within decision tree analysis. Modeling and simulation are
recommended for cost and schedule risk analysis because it is more
powerful and less subject to misapplication than expected monetary value
analysis.
External Context External environment in which the organization seeks to achieve its
objectives.
Fast Tracking A specific project schedule compression technique that changes network
logic to overlap phases that would normally be done in sequence, such as
the design phase and construction phase, or to perform schedule activities
in parallel. See Schedule Compression
Term Definition
Final Invoice The last payment certificate issued to a second party against his works in
a project.
Also known as Final Payment.
Finish Date A point in time associated with a schedule activity’s completion. Usually
qualified by one of the following actual, planned, estimated, scheduled,
early, late, baseline, target or current.
Finish-to-Finish (FF) The logical relationship where completion of work of the successor activity
cannot finish until the completion of work of the predecessor activity. See
also Logical Relationship
Finish-to-Start (FS) The logical relationship where initiation of work of the successor activity
cannot finish until the completion of work of the predecessor activity. See
also Logical Relationship
Five Case Model An approach to business cases, created by the UK Treasury and since
adopted worldwide.
Five-Year Projects The group NWC Projects that shall be executed in specific five years. It is
Portfolio (FYPP) annually updated.
Five-Year Projects The schedule of NWC Projects that shall be executed in specific five years.
Portfolio Plan It is annually updated.
(FYPPP)
Float Also called slack. See Total Float and Free Float.
Flowchart The diagram depicts the process procedures in sequent relation. Inputs,
outputs and comments are depicted when required. It may depict related
processes or related procedures from other processes.
Force Majeure An event not reasonably anticipated and acts of God, such as weather,
strikes, or other uncontrollable events.
Term Definition
Forward Pass The calculation of the early start and early finish dates for the uncompleted
portions of all network activities. See also Schedule Network Analysis and
Backward Pass.
Free Float The amount of time that a schedule activity can be delayed without delaying
the early start of any immediately following schedule activities. See also
Total Float.
Fringe Benefits Costs of labor beyond wages. Such items may include vacation, holidays,
insurance, and taxes.
Functional Manager Someone with management authority over an organizational unit within a
functional organization. The manager of any group that actually makes a
product or performs a service.
Sometimes called a Line Manager.
Functional A hierarchical organization where each employee has one clear superior,
Organization staff are grouped by areas of specialization and managed by a person with
expertise in that area.
General Contractor A Contractor who does not specialize in one kind of work. Often used to
refer to the major Contractor who employs specialty subcontractors.
Hazard Analysis A review of all the safety hazards that may be encountered in a project.
Used to develop the safety and environmental plans. Also used to
undertake safety and environmental risk analyses.
Term Definition
Health, Safety & This is an integral part of all projects and sets out the HSE policies and
Environment Plan procedures for the specific project in relation to the corporate policy.
Historical Documents and data on prior projects including project files, records,
Information correspondence, closed contracts and closed projects.
Hold Point It is a verification time which work cannot proceed beyond without an
approval or confirmation by a designated/authorized person.
Imposed Date A fixed date imposed on a schedule activity or schedule milestone, usually
in the form of a “start no earlier than” and “finish no later than” dat.
Inductions Similar to tool box meetings but used to convey specific job site practices
or other pertinent issues to the field supervisors and workers.
Infrastructure System of facilities, equipment and services needed for the operation of an
organization.
Initiating Processes Those processes performed to authorize and define the scope of a new
phase or project or that can result in the continuation of halted project work.
A large number of the initiating processes are typically done outside the
project’s scope of control by the organization, program or portfolio
processes and those processes provide input to the project’s initiating
processes group.
Initiator A person or organization that has both the ability and authority to start a
project.
Input Any item, whether internal or external to the project that is required by a
process before that process proceeds. May be an output from a
predecessor process.
Term Definition
Internal Audit Undertaken by suitably qualified staff within the organization using a
systematic methodology for analyzing business processes, procedures and
activities with the goal of highlighting organizational problems and
recommending solutions.
Key Performance These are a measure (benchmark, target) of performance and are used to
Indicators (KPI) evaluate how successful an organization or project is in attaining its
objectives.
Term Definition
Late Finish Date In the critical path method, the latest possible point in time that a schedule
(LF) activity may be completed based upon the schedule network logic, the
project completion date, and any constraints assigned to the schedule
activities without violating a schedule constraint or delaying the project
completion date. The late finish dates are determined during the backward
pass calculation of the project schedule network.
Late Start Date (LS) In the critical path method, the latest possible point in time that a schedule
activity may begin based upon the schedule network logic, the project
completion date, and any constraints assigned to the schedule activities
without violating a schedule constraint or delaying the project completion
date. The late start dates are determined during the backward pass
calculation of the project schedule network.
Lessons Learned The learning gained from the process of performing the project. Lessons
learned may be identified at any point. Also considered a project record, to
be included in the lessons learned knowledge base.
Level of Effort (LOE) Support-type activity (e.g. seller or customer liaison, project cost
accounting, project management, etc.) which does not produce definite end
products. It is generally characterized by a uniform rate of work
performance over a period of time determined by the activities supported.
Log A document used to record and describe or denote selected items identified
during execution of a process or activity.
Usually used with a modifier, such as issue, quality control, action, or
defect.
Term Definition
Manage Project The process of tracking team member performance, providing feedback,
team resolving issues, and coordinating changes to enhance project
performance.
Mashroat Projects The Mashroat Projects White Book (MPWB) is a publishment by the
White Book (MPWB) National Project Management Organization (Mashroat) to standardize
operating structures, systems, processes and procedures across all
Government Entities.
It consists of 16 volumes. Each volume contains a general procedure, and
may contain other procedures, guidelines, checklists, templates, indicators
to measure compliance and appropriate tools to be employed.
The Mashroat Projects White Book covers all phases of a typical project’s
lifecycle and will remain a living document updated periodically to reflect
technical and operational advancements and lessons learned.
Every Entity shall use the Mashroat Projects White Book as the basis for
developing the Entity’s own documents (Procedures, Templates,
Checklists, etc.) which will constitute the Entity’s own self-standing, self-
contained and comprehensive project management system for managing
its own type of projects.
The Mashroat Projects White Book defines the minimum requirements to
be followed in the planning, execution and delivery of projects.
Master Schedule A level 1 summary schedule that introduces all portfolio projects in one
schedule. It identifies, for portfolio projects, the major deliverables and work
breakdown structure components and key schedule milestones.
Matrix Organization Any organizational structure in which the project manager shares
responsibility with the functional managers for assigning priorities and for
directing the work of persons assigned to the project.
Term Definition
Methodology A system of practices, techniques, procedures and rules used by those who
work in discipline.
Milestone A significant point or event in the project. See also Schedule Milestone
Monitor Observe and/or determine the status to identify change from the
performance level required or expected (collect project performance data)
with respect to a plan, produce performance measures and report and
disseminate performance information.
Monitor and Control The process of monitoring and controlling the processes required to initiate,
Project Work plan, execute and close a project to meet the performance objectives
defined in the Project Management Plan and project scope statement.
Monitoring and Those processes performed to measure and monitor project execution so
Controlling Process that corrective action can be taken when necessary to control the execution
of the phase or project.
Monte Carlo A technique that computes, or iterates, the project cost or project schedule
Analysis many times using input values selected at random from probability
distributions of possible costs or durations, to calculate a distribution of
possible total project cost or completion dates.
Term Definition
Non-Conformance A report detailing the failure to meet specifications and often recommending
Report (NCR) a method of correction.
Objectives Hierarchy A hierarchy setting out the objectives in ranked order i.e. the need to be
(Ranked) delivered in respect to the NWC business case and related project.
Opportunity Opportunity. A risk that would have a positive effect on one or more
business or project objectives.
Organization A group of persons organized for some purpose or to perform some type of
work within an enterprise.
Group of people and facilities with an arrangement of responsibilities,
authorities and relationships.
Term Definition
Original Duration The activity duration originally assigned to a schedule activity and not
(OD) updated as progress is reported on the activity.
Typically used for comparison with actual duration and remaining duration
when reporting schedule progress.
P6 Oracle “Primavera P6” software for project scheduling. See “Primavera P6”.
Term Definition
Paired Comparison Used to compare one Project Objective (Ranked) with another so that all
objectives are compared to identify the relative importance of each of them.
Can also be used to compare site / design options using relevant criteria
e.g. ranked objectives.
Pareto Chart A histogram, ordered by frequency of occurrence, that shows how many
results were generated by each identified cause.
Perform Quality The process of applying the planned, systematic quality activities (such as
Assurance (QA) audits or peer reviews) to ensure that the project employs all processes
needed to meet requirements.
Perform Quality The process of monitoring specific project results to determine whether
Control (QC) they comply with relevant quality standards and identifying ways to
eliminate causes of unsatisfactory performance.
Performance A set of activities to ensure that goals are consistently being met in an
Management effective and efficient manner and can be applied to an organization,
department, project, service or employees.
Planning Package A work breakdown structure component below the control account with
known work content but without detailed schedule activities. See also
Control Account
Portfolio A collection of projects or programs and other work that are grouped
together to facilitate effective management of that work to meet strategic
business objectives. The projects or programs of the portfolio may not
necessarily be interdependent or directly related.
Term Definition
Preventive Action Documented direction to perform an activity that can reduce the probability
of occurrence of negative consequences associated with project risks.
Action to eliminate the cause of a potential nonconformity or other
undesirable potential situation.
Probability and A common way to determine whether a risk is considered low, moderate or
Impact matrix high by combining the two dimensions of a risk: its probability of
occurrence, and its impact on objectives if it occurs.
Procurement The document that describes the procurement processes will be managed
Management Plan from developing procurement documentation through to contract closure.
Product An artifact that is produced, is quantifiable, and can be either an end item
in itself or a component item. Additional words for products are Materiel and
Goods. Contrast with Result and Service. See also Deliverable.
Result of a process.
Product Scope The features and functions that characterize a product, service or result.
Term Definition
Progress Curves A plot of a project’s progress shown in percent complete versus amount of
time. Used to display status and trends.
Progress Payments A method defined in the contract documents that specifies the payments to
be made which correspond directly to the seller’s monthly progress of work.
Progressive Continuously improving and detailing a plan as more detailed and specific
Elaboration information and more accurate estimates become available as the project
progresses, and thereby producing more accurate and complete plans that
result from the successive iterations of the planning process.
Project Calendar A calendar of working days or shifts that establishes those dates on which
schedule activities are worked and nonworking days that determine those
dates on which schedule activities are idle. Typically defines holidays,
weekends and shift hours. See also Resource Calendar.
Project Charter A document issued by the project initiator or sponsor that formally
authorizes the existence of a project and provides the project manager with
the authority to apply organizational resources to project activities.
Project Initiation Launching a process that can result in the authorization and scope
definition of a new project.
Project Life Cycle A collection of generally sequential project phases whose name and
number are determined by the control needs of the organization or
organizations involved in the project. A life cycle can be documented with
a methodology.
Project Management The application of knowledge, skills, tools and techniques to project
(PM) activities to meet project requirements.
Term Definition
Project Management A formal approved document that defines how the project is executed,
Plan monitored and controlled. It may be a summary or detailed and may be
composed of one or more subsidiary management plans and other
planning documents.
Project Management One of the 44 processes, unique to project management and described in
Process the PMBOK Guide.
Project Management A person certified as PMP® by the Project Management Institute (PMI®).
Professional
(PMP®)
Term Definition
Project Management The members of the project team who are directly involved in the project
Team management activities.
Project Manager The person assigned by the performing organization to achieve the project
(PM) objectives.
Project Organization A document that graphically depicts the project team members and their
Chart interrelationships for a specific project.
Project Phase A collection of logically related project activities usually culminating in the
completion of a major deliverable. Project phases are mainly completed
sequentially but can overlap in some project situations. Phases can be
subdivided into sub- phases and then components; this hierarchy, if the
project or portions of the project are divided into phases, is contained in the
work breakdown structure. A project phase is a component of a project life
cycle. A project phase is not a project management process group.
Project Schedule The planned dates for performing schedule activities and the planned dates
for meeting schedule milestones.
Project Schedule Any schematic display of the logical relationships among the project
Network Diagram schedule activities. Always drawn from left to right to reflect project work
chronology.
Project Scope The work that must be performed to deliver a project, service or result with
the specified features and functions.
Project Scope The document that describes how the project scope will be defined,
Management Plan developed and verified and how the work breakdown structure will be
created and defined, and that provides guidance on how the project scope
will be managed and controlled by the project management team. It is
contained as a section in the Project Management Plan. The project scope
management plan can be informal and broadly framed or formal and highly
detailed based on the needs of the project.
Term Definition
Project Scope The narrative description of the project scope, including major deliverables,
Statement project objectives, assumptions, constraints and a statement of work, that
provides a documented basis for making future project decisions and for
confirming or developing a common understanding of project scope among
the stakeholders. The definition of the project scope – what needs to be
accomplished?
Project The engineering and architectural plans and written requirements for a
Specifications project. Similar to statement of work.
Project Team All the project team members, including the project management team, the
project manager and for some projects, the project sponsor.
Project Team A documented list of project team members, their project roles and
Directory communication information.
Project Team The persons who report either directly or indirectly to the project manager
Members and who are responsible for performing project work as a regular part of
their assigned duties.
Projectized Any organizational structure in which the project manager has full authority
Organization to assign priorities, apply resources, and direct the work of persons
assigned to the project.
Projects & Technical The department of NWC Headquarters, which is charged with providing
Services department governance over the Capital Programs.
Public Private An alternative procurement option involving the transfer of risk to the private
Partnership (PPP) sector, which may also provide private capital. The costs and benefits of
the approach will be compared to the Private Sector Comparator (PSC).
Qualitative Risk The process of prioritizing risks for subsequent further analysis or action by
Analysis assessing and combining their probability of occurrence and impact.
Quality Assurance Part of quality management focused on providing confidence that quality
requirements will be fulfilled.
Quality Management Coordinated activities to direct and control an organization with regard to
quality.
Term Definition
Quality Management The quality management plan describes how the project management team
Plan will implement the performing organization’s quality policy. The quality
management plan is a section of the Project Management Plan. The quality
management plan may be formal or informal, highly detailed, or broadly
framed, based on the requirements of the project.
Quality Management Management system to direct and control an organization with regard to
System quality.
Quality Planning The process of identifying which quality standards that are relevant to the
project and determining how to satisfy them.
Part of quality management focused on setting quality objectives and
specifying necessary operational processes and related resources to fulfil
the quality objectives.
Quantitative Risk The process of numerically analyzing the effect on overall project objectives
Analysis of identified risks.
RACI RACI matrix is model for Responsibility Assignment Matrix that describes
the participation by roles in performing activities/procedures for a project or
business process.
RACI is an acronym derived from the four key responsibilities most typically
used: responsible, accountable, consulted, and informed which define roles
and responsibilities in cross-functional or departmental projects and
processes.
There are a number of alternatives to the RACI model such as RASCI,
PARIS, PACSI and CAIRO.
Reliability The probability of a product performing its intended function under specific
conditions for a given period of time.
Term Definition
Residual Risk A risk that remains after risk responses have been implemented.
Risk remaining after risk treatment.
Term Definition
Resource Calendar A calendar of working days and nonworking days that determines those
dates on which each specific resource is idle or can be active. Typically
defines resource specific holidays and resource availability periods. See
also Project Calendar
Resource Leveling Any form of schedule network analysis in which scheduling decisions (start
and finish dates) are driven by resource constraints (e.g. limited resource
availability or difficult to manage changes in resource availability levels).
Resource-Limited A project schedule whose schedule activity, scheduled start dates and
Schedule scheduled finish dates reflect expected resource availability. A resource-
limited schedule does not have any early or late start or finish dates. The
resource-limited schedule total float is determined by calculating the
difference between the critical path method late finish date and the
resource-limited scheduled finish date. Sometimes called resource-
constrained schedule. See also Resource Leveling
Retention Period It is a document aspect which identifies the duration for which the
information should be maintained or retained regardless its format (i.e. hard
or soft).
Risk Acceptance A risk response planning technique that indicates that the project team has
decided not to change the Project Management Plan to deal with a risk or
is unable to identify any other suitable response strategy.
Risk Analysis Process to comprehend the nature of risk and to determine the level of risk.
Term Definition
Risk Appetite It is the amount and type of risk that an organization is willing to pursue or
retain. (ISO Guide 73:2009 Risk Management)
Determining risk appetite in a risk management of an organization helps to
determine the amount of risk the organization (both):
● willing to “live” with.
● need to manage.
Risk appetite is concerned with multi risks at organization management
level (including financial and operational impacts) in order to innovate in
pursuing the organizational objectives. It is not concerned with individual
risks at program or project level.
Risk appetite is defined once at organization level by defined criteria based
on factors includes but not limited to:
1. Industry
2. Company culture
3. Competitors
4. Nature of the organizational objectives (e.g. how aggressive they are)
5. Financial strength and capabilities of the organization
Risk appetite is periodically revised (e.g. annually or semi-annually).
Risk Assessment Overall process of risk identification, risk analysis and risk evaluation.
Risk Attitude Organization's approach to assess and eventually pursue, retain, take or
turn away from risk.
Risk Avoidance A risk response planning technique for a threat that creates changes to the
Project Management Plan that are meant to either eliminate the risk or to
protect the project objectives from its impact. Generally, risk avoidance
involves relaxing the Schedule, cost, scope or quality objectives.
Risk Breakdown A hierarchically organized depiction of the identified project risks arranged
Structure (RBS) by risk category and subcategory that identifies the various areas and
causes of potential risks. The risk breakdown structure is often tailored to
specific project types.
Risk Category A group of potential causes of risk. Risk causes may be grouped into
categories such as technical, external, organizational, environmental or
project management. A category may include subcategories such as
technical maturity, weather or aggressive estimating. See also Risk
Breakdown Structure
Risk Criteria Terms of reference against which the significance of a risk is evaluated.
Term Definition
Risk Database A repository that provides collection, maintenance and analysis of data
gathered and used in the risk management process.
Risk Evaluation Process of comparing the results of risk analysis with risk criteria to
determine whether the risk and/or its magnitude is acceptable or tolerable.
Risk Identification The process of determining which risks might affect the project and
documenting their characteristics.
Process of finding, recognizing and describing risks.
Risk Management Coordinated activities to direct and control an organization with regard to
risk.
Risk Management Set of components that provide the foundations and organizational
Framework arrangements for designing, implementing, monitoring, reviewing and
continually improving risk management throughout the organization.
Risk Management The document describing how project risk management will be structured
Plan and performed on the project. It is contained as a section in the Project
Management Plan. The risk management plan can be informal and broadly
framed or formal and highly detailed based on the needs of the project.
Information in the risk management plan varies by application area and
project size. The risk management plan is different from the risk register
that contains the list of project risks, the results of risk analysis and the risk
responses.
Scheme within the risk management framework specifying the approach,
the management components and resources to be applied to the
management of risk.
Risk Management The process of deciding how to approach, plan and execute risk
Planning management activities for a project.
Risk Management Statement of the overall intentions and direction of an organization related
Policy to risk management.
Risk Mitigation A risk response planning technique associated with threats that seek to
reduce the probability of occurrence or impact of a risk to below an
acceptable threshold.
Risk Monitoring and The process of tracking identified risks, monitoring residual risks, identifying
Control new risks, executing risk response plans and evaluating their effectiveness
throughout the project lifecycle.
Term Definition
Risk Owner Person or entity with the accountability and authority to manage a risk.
Risk Register The document containing the results of the qualitative risk analysis,
quantitative risk analysis and risk response planning. The risk register
details all identified risks, including description, category, cause, probability
of occurring, impacts on objectives, proposed responses, owners and
current status. The risk register is a component of the Project Management
Plan.
Risk Response The process of developing options and actions to enhance opportunities
Planning and to reduce threats to project objectives.
Risk Source Element which alone or in combination has the intrinsic potential to give
rise to risk.
Risk Tolerance It is an organization’s or stakeholder’s readiness to bear the risk after risk
treatment in order to achieve its objectives. (ISO Guide 73:2009 Risk
Management)
When one or more issues (which were risks) take place, variations happen.
Risk tolerance reflects the acceptable variations in outcomes related to
specific performance measures linked to objectives that the organization
seeks to achieve when the outcomes are exposed to issues. If risks are
multiple, risk tolerance definition shall require studying all expected
scenarios that the multiple risks may take.
Risk tolerance to be identified during risk workshops.
Risk tolerance is concerned with individual risks at program or project level.
It is not concerned with multi risks at organization management level.
Risk Transference A risk response planning technique that shifts the impact of a threat to a
third party, together with ownership of the response.
Term Definition
Root Cause Analysis An analytical technique used to determine the basic underlying reason that
causes a variance or a defect or a risk. A root cause may underlie more
than one variance or defect or risk.
Schedule Activity A discrete scheduled component of work performed during the course of a
project. A schedule activity normally has an estimated duration, an
estimated cost and estimated resource requirements. Schedule activities
are connected to other schedule activities or schedule milestones with
logical relationships and are decomposed from work packages.
Schedule Shortening the project schedule duration without reducing the project
Compression scope. See also Crashing and Fast Tracking
Schedule The document that establishes criteria and the activities for developing and
Management Plan controlling the project schedule. It is contained as a section in the Project
Management Plan. The schedule management plan may be formal or
informal, highly detailed or broadly framed based on the needs of the
project.
Schedule Milestone A significant event in the project schedule such as an event restraining
future work or marking the completion of a major deliverable. A schedule
milestone has zero duration.
Sometimes called a milestone activity. See also Milestone
Schedule Model A model used in conjunction with manual methods or project management
software to perform schedule network analysis to generate the project
schedule for use in managing the execution of a project. See also Project
Schedule
Term Definition
Schedule Network The technique of identifying early and late start dates, as well as early and
Analysis late finish dates, for the uncompleted portions of project schedule activities.
See also Critical Path Method, Critical Chain Method, What-If Analysis, and
Resource Leveling.
Scheduled Finish The point in time that work was scheduled to finish on a schedule activity.
Date (SF) The scheduled finish date is normally within the range of dates delimited by
the early finish date and the late finish date. It may reflect resource leveling
of scarce resources. Sometimes called Planned Finish Date.
Scheduled Start The point in time that work was scheduled to start on a schedule activity.
Date (SS) The scheduled start date is normally within the range of dates delimited by
the early start date and late start date. It may reflect resource leveling of
scarce resources. Sometimes called Planned Start Date.
Scope The sum of drawing, specification and BoQ that describes the products,
services and results to be provided by a project.
Scope Creep Adding features and functionality (project scope) without addressing the
effects on Schedule, costs and resources or without customer approval.
Scope Definition The process of developing a detailed project scope statement as the basis
for future project decisions.
Scope Variation Any change to the project scope. A scope change almost always requires
an adjustment to the project cost or schedule.
Term Definition
Second Party A project partner external to the NWC organization that have direct contract
with NWC (i.e. Design Consultant, Supervision Consultant and Contractor).
Secondary Risk A risk that arises as a direct result of implementing a risk response.
Select Sellers The process of reviewing offers, choosing from among potential sellers and
negotiating a written contract with a seller.
Sensitivity Analysis Varying several constituents of a calculated study to see what the effect is.
Usually performed in connection with a feasibility study.
A quantitative risk analysis and modeling technique used to help determine
which risks have the most potential impact on the project. It examines the
extent to which the uncertainty of each project element affects the objective
being examined when all other elements are held at their baseline values.
The typical display of results is in the form of a tornado diagram.
Service Useful work performed that does not product a tangible product or result,
such as performing any of the business functions supporting production or
distribution. Contrast with product or result. See also Deliverable
Short List A list that is distilled from a larger group of proposers or bidders through
the use of a set of criteria.
Simulation A simulation uses a project model that translates the uncertainties specified
at a detailed level into their potential impact on objectives that are
expressed at the level of the total project. Project simulations use computer
models and estimates of risk, usually expressed as a probability distribution
of possible costs or durations at a detailed work level and are typically
performed using Monte Carlo Analysis.
Term Definition
Site Means the places where the Permanent Works are to be executed and to
which Plant and Materials are to be delivered as described in the
Specification, and any other places as may be specified in the Contract as
forming part of the Site.
Snag List The work items that are identified during a final inspection which need to
be completed.
Also, known as a Defects List or Punch List.
Sole Source A type of procurement where only one supplier is asked to bid. Often
required to obtain proprietary products.
Special Cause A source of variation that is not inherent in the system, is not predictable,
and is intermittent. It can be assigned to a defect in the system. On a control
chart, points beyond the control limits, or non-random patterns within the
control limits, indicate a special cause. Also referred to as Assignable
Cause. Contrast with Common Cause
Specification Limits The area, on either side of the centerline, or mean, of data plotted on a
control chart that meets the customer’s requirements for a product or
service. This area may be greater than or less than the area defined by the
control limits. See also Control Limits
Sponsor The person or group that provides the financial resources, in cash or in
kind, for the project.
Staffing Plan The document that describes when and how human resource requirements
will be met. It is contained as a section in the Project Management Plan.
The staffing plan can be informal and broadly framed, or formal and highly
detailed, based on the needs of the project. Information in the staffing plan
varies by application area and project size.
Stage Gate Review A systematic methodology to ensure the completion of all technical and
legal requirement for each project stage prior to proceed to the next stage
of the project lifecycle.
Term Definition
Stakeholder Analysis An analysis setting out the current and required position of the stakeholders
to a project.
Stakeholder Map A map identifying the critical and non-critical stakeholders to a project.
Start Date A point in time associated with a schedule activity’s start, usually qualified
by one of the following: actual, planned, estimated, scheduled, early, late,
target, baseline or current.
Start-to-Finish (SF) The logical relationship where completion of the successor schedule
activity is dependent upon the initiation of the predecessor schedule
activity. See also Logical Relationship
Start-to-Start (SS) The logical relationship where initiation of the work of the successor
schedule activity is dependent upon the initiation of the predecessor
schedule activity. See also Logical Relationship
Strategic A document that summarizes the project’s strategic context, mandate and
Assessment scope.
Strategic Outline The first business case of a Project prepared by NWC in support of a
Case (SOC) potential project.
Term Definition
Strengths, This information gathering technique examines the project from the
Weaknesses, perspective of each project’s strengths, weaknesses, opportunities and
Opportunities and threats, to increase the breadth of the risks considered by risk
Threats (SWOT) management.
Analysis
Subproject A smaller portion of the overall project created when a project is subdivided
into more manageable components or pieces. Subprojects are usually
represented in the work breakdown structure. A subproject can be referred
to as a project, managed as a project, and acquired from a seller. May be
referred to as a subnetwork in a project schedule network diagram.
Successor Activity The schedule activity that follows a predecessor activity as determined by
their logical relationship.
Summary Activity A group of related schedule activities aggregated at some summary level
and displayed/reported as a single activity at the summary level. See also
Subproject and Subnetwork
Task A term for work whose meaning and placement within a structured plan for
project work varies by the application area, industry and brand of project
management software.
Technical Expert Person who provides specific knowledge or expertise to the audit team.
Term Definition
Testing & It is a list that specifically and clearly identifies all project deliverables that
Commissioning shall be commissioned such as systems, equipment or interfaces.
Items (T&C Items)
It is a key part in the T&C Plan.
Testing & It is a written protocol which defines procedures and expectations for tests
Commissioning conducted on equipment, systems and interfaces.
Method Statement
The document includes test prerequisites, test conditions, tools and
(T&CMS)
instruments to be used, schematics, acceptance criteria and safety risk
assessment.
Contractor is responsible for preparing the T&C Method Statement and
submitting it to NWC Project Manager for approval at the beginning of T&C
stage. NWC Project Manager and Supervision Consultant shall review and
approve the T&C Method Statement. T&C department and T&C Consultant
(if assigned) shall be consulted if required.
Contractor is responsible for inclusion of the following two T&C method
statements in the method statement that he prepares for the project. This
incorporation obligates that, the Contractor T&C Method Statement
includes T&C integration activities to integrate all project
systems/equipment/interfaces.
● Some equipment manufacturers/suppliers prepare a method
statement for their equipment functional testing and performance
testing. These method statements shall be submitted and approved
by NWC Project Manager and Supervision Consultant during the
equipment approval process.
● Some specialized work requires that its method statements be
prepared by a specialized T&C specialist (SME). Contractor is
responsible for providing this method statement from the SME.
Term Definition
Term Definition
● Reporting procedure for progress, defects and corrections :
○ Timings of T&C report submission.
○ Expected defects correction duration in coordination with the
contractor.
● Approval Authority:
○ Identify the authority that shall approve the T&C report and T&C
certificate that prepared by the T&C Working Group.
● T&C checklist and templates:
○ Attach the checklists and test procedures that shall be used in
T&C process.
○ Attach any template that need to use in T&C process.
Third Party A project partner external to the NWC organization that have no direct
contract with NWC (i.e. third party lab).
Threat A risk that would have a negative effect on one or more business or project
objectives.
Time for Completion Means the time for completing the Works or a Section (as the case may
be) as stated in the Particular Conditions, calculated from the date specified
in the Notice to Proceed.
Time-Scaled Any project schedule network diagram drawn is such a way that the
Schedule Network positioning and length of the schedule activity represents its duration.
Diagram Essentially, it is a bar chart that includes schedule network logic.
Tool Box Meetings A regular meeting of field supervisors and workers to review important work
issues; particularly those pertaining to safety. Tool box meetings are
usually restricted to a specific subject, for example, excavation, concrete
placing, or heavy lifts, etc.
Term Definition
Top Management Person or group of people who directs and controls an organization at the
highest level.
Total Float (TF) The total amount of time that a schedule activity may be delayed from its
early start date without delaying the project finish date or violating a
schedule constraint. Calculated using the critical path method technique
and determining the difference between early finish dates and late finish
dates.
See also Free Float
Traceability Ability to trace the history, application or location of that which is under
consideration.
Trend Analysis Analytical technique that uses mathematical models to forecast future
outcome based on historical results. It is a method of determining the
variance from a baseline of a budget, cost, schedule or scope parameter
by using prior progress reporting periods’ data and projecting how much
that parameter’s variance from baseline might be at some future point in
the project if no changes are made in executing the project.
Triggers Indications that a risk has occurred or is about to occur. Triggers may be
discovered in the risk identification process and watched in the risk
monitoring and control process.
Triggers are sometimes called risk symptoms or warning signs.
Triple Constraint A framework for evaluating competing demands. The triple constraint is
often depicted as a triangle where one of the sides or one of the corners
represents one of the parameters being managed by the project team.
User The person or organization that will use the project’s product or service.
See also Customer
Term Definition
Value Analysis (VA) The application of the Value Methodology to an existing project, product, or
process to achieve value improvement.
Value Appetite Amount and type of value improvement opportunity that an organization is
willing to pursue or retain.
Value Attitude Organization’s approach to assess and eventually pursue, retain, take or
turn away from a value improvement opportunity.
Term Definition
Value Methodology A systematic process used by a multidisciplinary team to improve the value
of a project, product, or process through the analysis of functions. The
(VM)
value methodology is applied during the three stages of a value study:
1. Pre-Workshop
2. Workshop (Using the Six-Phase VM Job Plan)
3. Post-Workshop.
Value Proposal A recommendation, resulting from the application of the VM Job Plan during
a value workshop, to increase the value of a project, product, or process so
as to improve function and/or decrease the resources required. It is a
deliverable of the Development Phase of the VM Job Plans.
Value Study The application of the three stages of the Value Methodology (pre-
workshop, workshop, and postworkshop) in a structured effort led by a
CVS® to improve the value of a project, product, or process.
Value Workshop The application of the six phases of the VM Job Plan (1. Information, 2.
Function Analysis, 3. Creativity, 4. Evaluation, 5. Development, and 6.
Presentation) to a project, product, or process by a multidisciplinary team
led or facilitated by a Certified Value Specialist.
Variance Analysis A method for resolving the total variance in the set of scope, cost and
schedule variables into specific component variances that are associated
with defined factors affecting the scope, cost and schedule variables.
Variation Control The process of requesting, reviewing and approving all variation requests
and controlling changes to deliverables and organizational process assets.
Variation Order (VO) An instruction to implement a change to a one or more documents of the
project contract. It is controlled by a process where carefully reviewed,
evaluated and approved or rejected.
Variation Request A request to expand or reduce the project scope, modify policies,
processes, plans or procedures, modify costs or budgets, or revise
schedules. Requests for variations can be externally or internally initiated,
and legally or contractually mandated or optional. Only formally
documented requested variations are processed and only Approved
Variations are implemented.
Term Definition
Virtual Team A group of persons with shared objective who fulfill their roles with little or
no time spent meeting face to face. Various forms of technology are often
used to facilitate communication among team members. Virtual teams can
be comprised of persons separated by great distances.
Voice of the A planning technique used to provide products, services and results that
Customer truly reflect customer requirements by translating those customer
requirements into the appropriate technical requirements for each phase of
project product development.
Whole Life Costing Includes all cost components incurred throughout the life of a project.
(WLC)
Work Authorization A permission and direction, typically written, to begin work on a specific
schedule activity or work package or control account. It is a method for
sanctioning project work to ensure that the work is done by the identified
organization at the right time and in the proper sequence.
Term Definition
Work Breakdown An entry in the work breakdown structure that can be at any level.
Structure
Component
Work Breakdown A document that describes each component in the work breakdown
Structure Dictionary structure (WBS). For each WBS component, the WBS dictionary includes
a brief definition of the scope or statement of work, defined deliverables, a
list of associated activities and a list of milestones. Other information may
include, responsible organization, start and end dates, resources required,
an estimate of cost, charge number, contract information, quality
requirements and technical references to facilitate performance of the work.
Work Item Term no longer in common usage. See Activity and Schedule Activity
Work Package A deliverable or project work component at the lowest level of each branch
of the work breakdown structure. The work package includes the schedule
activities and schedule milestones required to complete the work package
deliverable or project work component. See also Control Account
Work Performance The performance data collected from controlling processes, analyzed in
Information comparison with project management plan components, project
documents, and other work performance information.
Working Group An informal group comprising members of different entities and regional
representation that performs a cross-sector integration check
Term Definition
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022
Abdulaziz K. Aljawan
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020
Abdullah M. Albani
This section is developed as an update to “Project Life Cycle” section in first version
the Project Management Manual (PMM) which developed by Faithful + Gould. The
following are the changes:
● Updated as per Mashroat Project Life Cycle and Stage Gate procedure.
Change ● Adding Stage Gates description.
Description
● Adding Stage Gate process map.
● Adding simplified stage gate process map.
● Adding gate committee and responsibilities.
● Referring to Mashroat Stage Gate procedures, guidelines, register and forms.
Stage 1
Project Registration
Stage Gate 1
Stage 2
Initial Planning
Stage Gate 2
Stage 3
Tender for Design
Stage Gate 3
Stage 4
Design
Stage Gate 4
Stage 5
Tender for Constructon
Stage Gate 5
Stage 6
Construction
Stage Gate 6
Stage 7
Testing and Commissioning
Stage Gate 7
Stage 8
Handover and Closout
Stage Gate 8
For “Design & Build” project (EPC Projects), the lifecycle, illustrated in figure 3-2, shall be followed.
It consists of six stages.
1. Project Registration Stage.
2. Initial Planning Stage.
3. Tender Stage.
Stage 1
Project Registration
Stage Gate 1
Stage 2
Initial Planning
Stage Gate 2
Stage 3
Tender
Stage Gate 3
Stage 4
Design and Construction
Stage Gate 4
Stage 5
Testing and Commissioning
Stage Gate 5
Stage 6
Handover and Closout
Stage Gate 6
In some projects, the project may be subdivided into parts. And each part is subdivided into stages.
In this case, the stage gate processes should be repeated for each . A suitable life cycle is to be
developed and agreed upon.
For details of the stage gate reviews to be carried out at the end of each stage, please refer to the
manual Section 6 “Governance”.
The period from the beginning of Registration Stage up to the end of:
● Tender for Construction stage in design-bid-build projects.
or
● Tender for Design and Construction stage in Design & Build projects
is known as development period.
Also, the:
● Construction stage in design-bid-build projects.
● Design and Construction stage in Design & Build projects.
is known as the execution period.
The NWC Five-Year Projects Portfolio Plan is focused, each financial year, into a CAPEX plan. The
CAPEX plan is to be submitted to the Ministry of Environment, Water and Agriculture MEWA and
the Ministry of Finance MOF, in order to obtain ministerial approval and to secure budgetary funding
on an annual basis. During this process, the asset requirements are described in terms of project
requirements, in order to deliver the intended asset at the right time, cost and quality.
As per the initial project business case which developed during the preparation of NWC Five-Year
Projects Portfolio Plan, the project owner is required to prove that the potential project represents
the best way of meeting a defined need.
3.1.1 Stage 1: Project Registration
The objective of this stage is to register the MOF approved projects, in Expenditure Efficiency
& Projects Authority (EXPRO). For registration, a New Project Registration Form (PMF-003-
PLC-001 NPMO New Project Registration Form) is to be completed and submitted to NPMO
along with key supporting evidence (PMF-003-PLC-002 Project Registration Checklist). NWC
Five-Year Strategy Plan will act as the key source for information required as supporting
evidence.
Once project is assessed and registered with the NPMO, an official NPMO Project No. will be
obtained.
The following deliverables are required to this stage:
● Scope of Work Outline (PMM-004-FYP-010-040)
● Level 1 Schedule (PMM-004-FYP-020-040)
● Class 5 Cost Estimate (PMM-004-FYP-020-020)
● Risk Potential Assessment (PMM-004-FYP-030-020)
● Business Case (PMM-004-FYP-030-040)
● MOF approval to initiate project (PMM-004-FYP-060-010)
● NPMO Project Registration Form
3.1.2 Stage 2: Initial Planning
In the Initial Planning stage, NWC sets up the Project Team under an appointed Project
Manager, to define the project’s objectives, to outline possible design options and to select the
most suitable option through risk assessment and value analysis, to:
● Establish the execution strategy for the selected design option.
Under Initial Handing This status means the initial handing over process is not
Over completed.
Initially Handed Over This status means the initial handing over process is completed.
Finally Handed Over This status means the final handing over process is completed.
Closed This status means that the entire project has been completed.
Cancelled This status indicates that a decision has been made to terminate
the project.
Suspended This status indicates that a decision has been made to suspend the
project.
Withdrawn This status indicates that the project is withdrawn from the
Contractor.
Troubled This status indicates that one or more of the following is true:
● the variance between planned and actual progress is more than
25%.
● the project time overrun is more than 25%.
● there is no approved schedule after 60 days from site handover
to Contractor.
Delayed This status indicates that 10% < variance between planned and
actual progress ≤ 25%.
On Time This status indicates that the variance between planned and actual
progress ≤ 10%.
Ahead of Schedule This status indicates that the actual progress exceeds the planned
progress.
Projects which do not fulfill one or more of the above criteria (projects below SAR 25M and/or
of less than one year duration), shall go through a Simplified Stage Gate Process at the end of
each stage.
Below flowchart describes the simplified stage gate process.
Figure 3-4 Simplified Stage Gate Process Flowchart
GATE COMMITEE
Represent the Functional Departments and internal stakeholders at the Stage Kick-off Meeting and
the Stage Gate Review Meeting
Table 3-2 Project Life Cycle and Stage Gate Process KPIs
3.4 Attachments
The table below identifies mandated forms, templates and guidelines and for this section (PMM-
002-GEN Project Lifecycle and Stage Gate Process).
Table 3-3 Project Lifecycle and Stage Gate Process forms, templates and guidelines
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022
Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-004-FYP-010 Initiate Projects Portfolio s at Cluster Level” is
elaborated.
● The process “PMM-004-FYP-020 Develop and Confirm Initial Cluster Projects
Portfolios” is elaborated.
● The process “PMM-004-FYP-030 Screen NWC Initial Projects Portfolio” is
elaborated.
Change ● The process “PMM-004-FYP-040 Develop Draft FYPPP and Submit for Review” is
Description elaborated.
● The process “PMM-004-FYP-050 Update FYPPP and Prepare Annual Capital
Works Plan” is elaborated.
● The process “PMM-004-FYP-060 Develop Final FYPPP and Annual Capital Works
Plan and Submit to MOF for Budget Approval” is elaborated.
● The process “PMM-004-FYP-070 Five-Year Projects Portfolio Variation Control” is
added.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020
Abdullah M. Albani
Change
● This is the first versions of this section.
Description
4.1.2 Policies
Policies for this process are as follows:
1. MOF shall provide NWC with a medium-term Capital Works Budget Cap, for the
forthcoming Five-Year. This cap will help guide the early identification of potential
projects, their screening, cross-sectoral integration and prioritization.
2. Every cluster must have its own Projects Portfolio .
4.1.3 Flowchart
Figure 4-3 PMM-004-FYP-010 Initiate Projects Portfolio s at Cluster Level Flowchart
4.1.4 Procedures
4.1.4.1 PMM-004-FYP-010-010 Identify Capital Projects & Technical Services
Objectives
CEO
Informed:
Chief Financial Officer
Transformation & Governance VP
Shared Services VP
Strategy, Corporate Performance & Systems VP
Privatization VP
Customer Care VP
Business Operational Support VP
Cluster Projects GMs
4.1.4.2 PMM-004-FYP-010-020 Identify Infrastructure Gap and Prepare Local Master
Plans
Procedure: ● The Local Master Plan Consultants shall identify the demand for
infrastructure by many factors including changes in population,
demographics, levels of urbanization, urban residential densities and by
changes in the type and range of services to be provided.
● The Local Master Plan Consultants shall assess and confirm
infrastructure gap within each of the six Clusters. The following should
be considered:
○ Establish Baseline: Confirm the present baseline. This is the level of
infrastructure recorded within the year prior to this annual Capital
Works Plan.
○ Generate Infrastructure Forecast: Generate the projected future
infrastructure forecast, for a minimum 10-year horizon, based on the
anticipated rates of development growth / change. This forecast
should be under-pinned and supported by up-to-date statistics and
data, including established population growth projections.
○ Establish Infrastructure Gap: Establish the gap for infrastructure, by
assessing the difference between the baseline and the forecast
generated.
○ Identify Potential Projects: To address the confirmed infrastructure
gap (per Cluster), potential projects shall be identified and listed.
● Request all relevant stakeholders including Cluster Asset Management
& Operation Excellence to communicate their needs.
● Transfer stakeholder needs into projects requirements.
● Rate the Relative Importance of Projects Requirements.
● Achieve consensus on the project requirements and approach by the
project stakeholders including Cluster Asset Management & Operation
Excellence .
● The local master plan Consultant shall develop and submit the local
master plan with the list of projects for NWC review and approval.
Procedure: ● Local Master Plan Consultant shall develop, for every potential project
(initiative), an initial project scope. The initial project scope should
include at least the following information:
○ A brief description of the proposed project and identification of its
anticipated outcome/s.
○ An outline of the project scope of work (PMF-004-FYP-003 Initial
Project Scope Outline Form) to assist in identifying and capturing
the key project information.
○ At least three “viable” site location options should be identified for
each project (i.e. the type of development should be compatible with
the surrounding existing or proposed land uses, accessible from
existing or proposed road networks, have access to the required
utilities and have limited impact on the existing natural environment).
The location options identified are to be appropriately assessed,
during (PMM-004-FYP-020-010 Undertake Pre-Concept Site
Options Testing).
Local Master Plan Consultant
Roles: Responsible:
Capital Projects Strategic Planning GM
Accountable: Cluster Projects GM
Engineering Director
Consulted:
Cluster Projects GM
Cluster Technical Services Director
Cluster Asset Management & Operation Excellence
Director
Cluster GIS Specialist
Cluster Technical Services Director
Informed:
Portfolios Strategic Planning & Spending Efficiency
Director
Strategic Studies Manager
Cluster Strategic Planning Manager
4.2.3 Flowchart
Figure 4-4 PMM-004-FYP-020 Develop and Confirm Initial Cluster Projects Portfolios Flowchart
4.2.4 Procedures
4.2.4.1 PMM-004-FYP-020-010 Undertake Pre-Concept Site Options Testing
Procedure: ● For all projects in the LMP Projects List, each of the potential site location
options previously identified, shall be assessed for suitability against high
level, socio-economic and environmental criteria. These criteria could
include the level of vehicular access to / from the site, site topography
and geography, population demographics and acceptability of proposed
land use within the existing or planned context.
● Confirm the preferred site option and update the scope of work (i.e. if the
preferred site may require additional works to facilitate the development).
This should be added to the initial project scope using (PMF-004-FYP-
003 Initial Project Scope Outline Form).
Local Master Plan Consultant
Roles: Responsible:
Cluster Strategic Planning Manager
Accountable: Cluster Projects GM
Cluster Technical Services Director
Consulted:
Engineering Director
Cluster Asset Management & Operation Excellence
Director
Cluster Value Engineering Specialist
Cluster GIS Specialist
Value Engineering Director
Procedure: ● For all projects in the LMP Projects List, using the preferred site option
analysis and refined scope of work, the Local Master Plan Consultant
shall prepare Initial Cost Estimate (Class 5) for the proposed projects.
● For above action, refer to (PMF-011-COS-005 Cost Estimate Form) and
(PMF-011-COS-001 Cost Estimating Guidelines).
● Refer to the Cost Database for analogous data.
● Ensure that assumptions, issues and risks are formally recorded (e.g.
Risk Workshop No.1 Report should be reviewed) and attached to the
completed form.
● Send the prepared Cost Estimate (Class 5) to National Master Plan
Consultant for review and processing.
Procedure: ● For all projects in the LMP Projects List, Cluster Technical Services
Director, Cluster Cost Estimation Specialist and Strategic Planning
Manager shall review the Initial Cost Estimate (Class 5) provided by local
master plan Consultant.
● For above action, refer to (PMF-011-COS-005 Cost Estimate Form) and
(PMF-011-COS-001 Cost Estimating Guidelines).
● Refer to the Cost Database for analogous data.
● Ensure that assumptions, issues and risks are formally recorded (e.g.
Risk Workshop No.1 Report should be reviewed) and attached to the
completed form.
Cluster Technical Services Director
Roles: Responsible:
Cluster Cost Estimation Specialist
Cluster Strategic Planning Manager
Accountable: Cluster Projects GM
Local Master Plan Consultant
Consulted:
Cost Estimation Manager
Cluster Scheduling Section Head
Cluster Risk Section Head
Cluster Technical Services Director
National Master Plan Consultant
Strategic Studies Manager
Portfolios Strategic Planning & Spending Efficiency
Director
Capital Projects Strategic Planning GM
Local Master Plan Consultant
Informed:
Cluster Projects GM
Capital Projects Strategic Planning GM
Cluster Strategic Planning Manager
National Master Plan Consultant
Procedure: ● For all projects in the LMP Projects List, prepare initial level 1 schedule.
As a minimum, it should identify the following:
○ The total duration of the project.
○ Major project phases and high-level milestones such as completion
of initial planning and specialist technical studies, tender for design,
design, tender for construction, construction, testing &
commissioning and handover and closeout.
○ Identify major work packages / scope breakdown (Work Breakdown
Structure Level 1).
● Estimate the project duration based on the given data and previous
executed projects.
● Breakdown the overall project duration into stages, based on the
selected procurement strategy for the project and the associated
lifecycle.
● Identify the duration of project and its stages clearly in the NWC strategic
Master Plan of Projects using “Primavera P6”.
● Develop initial Project Level 1 Schedule.
Procedure: ● Cluster Scheduling & Control Manager, Cluster Scheduling Section Head
and Cluster Strategic Planning Manager shall review the initial level 1
schedule provided by local master plan Consultant.
● Ensure that assumptions, issues and risks are formally recorded (e.g.
Risk Workshop No.1 Report should be reviewed) and attached to the
completed form.
Cluster Scheduling & Control Manager
Roles: Responsible:
Cluster Scheduling Section Head
Cluster Strategic Planning Manager
Procedure: ● Perform every contractual activity and study that is essential to develop
the Local Master Plan (e.g. developing inception report, Master Plan
Guidelines, Bulk Water Development Plans, Water Leakage Study, etc.).
● Compile and consolidate the produced deliverables to create the Local
Master Plan.
● Raise the Local Master Plan to Capital Projects Strategic Planning GM
for approval.
Procedure: ● Capital Projects Strategic Planning GM shall review the local master plan
in consultation with:
○ National Master Plan Consultant.
○ Strategic Studies Manager.
○ Portfolios Strategic Planning & Spending Efficiency Director.
○ Cluster Projects GM
● Capital Projects Strategic Planning GM shall give final approval on the
local master plan.
● Capital Projects Strategic Planning GM shall send the local master plans
to the National Master Planning Consultant for incorporation in the
National Maser Plan
Procedure: ● Review the Local Master Plans that approved at cluster level.
● Perform every contractual activity or study that is essential to develop the
National Master Plan (e.g. developing inception report, Master Plan
Guidelines, Bulk Water Development Plans, Water Leakage Study, etc.).
● Compile, consolidate and integrate the Local Master Plans to create The
National Master Plan.
● Identify and address:
○ Interfaces between Local Master Plans.
○ incompatibilities between Local Master Plans.
○ overlapping aspects such as objectives or resources.
● Perform integration, from national wise, between Local Master Plans to
eliminate any potential issues in both National and Local Master Plans.
● Raise the National Master Plan to Capital Projects Strategic Planning
GM for approval.
Procedure: ● Capital Projects Strategic Planning GM shall pass the National Master
Plan to Strategic Studies Manager and Portfolios Strategic Planning &
Spending Efficiency Director for review and initial approval.
● Strategic Studies Manager and Portfolios Strategic Planning & Spending
Efficiency Director shall review the National Master Plan and give initial
approval on it.
● Capital Projects Strategic Planning GM shall review the National Master
Plan and give final approval on it.
● Capital Projects Strategic Planning GM shall forward the approved
National Master Plan to all Cluster Senior GMs and Cluster Projects GMs
to adopt and formally make any required adjustments in Local Master
Plans.
Strategic Studies Manager
Roles: Responsible:
Portfolios Strategic Planning & Spending Efficiency
Director
Capital Projects Strategic Planning GM
Accountable: Capital Projects Strategic Planning GM
Procedure: ● Review the proposed projects in approved Local Master Plans against
the NWC’s medium-term Capital Budget.
● Identify the projects to be included in Cluster Initial Projects Portfolio .
● Ensure, for every project in the Cluster Initial Projects Portfolio , there
are:
○ confirmed demands.
○ confirmed site locations.
○ updated Project Scope.
○ class 5 cost estimate.
○ level 1 schedule.
○ initial business case.
● Prioritize projects using (PMF-004-FYP-010 Project Prioritization
Template).
● Develop the Cluster Initial Projects Portfolio .
● Use (PMF-004-FYP-005 Draft Five-Year Projects Portfolio Plan
Checklist) to help develop Cluster Initial Projects Portfolio.
● Send the Cluster Initial Projects Portfolio to Cluster Projects GM for
confirmation.
Cluster Strategic Planning Manager
Roles: Responsible:
Cluster Technical Services Director
Accountable: Cluster Projects GM
Cluster Projects GM
Consulted:
Cluster Scheduling & Control Manager
Cluster Environmental Compliance Manager
Cluster PMO Manager
Local Master Plan Consultant
Cluster Asset Management & Operation Excellence
Director
Cluster Finance GM
Operation Excellence GM
Asset Management GM
Corporate Finance Planning & Reporting GM
National Master Plan Consultant
Cluster Projects GM
Informed:
Cluster Asset Management & Operation Excellence
Director
Operation Excellence GM
Asset Management GM
4.2.4.14 PMM-004-FYP-020-140 Confirm Cluster Initial Projects Portfolio
4.3.3 Flowchart
Figure 4-5 PMM-004-FYP-030 Screen NWC Initial Projects Portfolio Flowchart
4.3.4 Procedures
4.3.4.1 PMM-004-FYP-030-010 Perform Project Strategic Assessment
Procedure: ● For every project in the Cluster Local Master Plan, Undertake Strategic
Assessment to:
○ provide initial justification for the need to invest.
○ form the Strategic Case in the “Business Case”.
● Consider the key elements in this exercise which are:
○ Initiate proposal investment.
○ Identify key stakeholders and analyze stakeholder interests and
influences. These stakeholders shall participate in workshops to
identify investment drivers.
○ Arrange and facilitate workshops to describe the project, its strategic
context and alignment to existing policies or strategies, and to
identify and agree investment drivers (problems and opportunities).
These workshops shall be attended by the identified key
stakeholders.
○ Finalize and compile the workshop outputs and draft the strategic
assessment document.
● Use (PMF-004-FYP-007 Strategic Assessment Template) and (PMF-
004-FYP-008 Strategic Assessment Checklist).
● Send the Project Strategic Assessment to Cluster Projects GM for
approval
Cluster Strategic Planning Manager
Roles: Responsible:
Cluster Technical Services Director
Accountable: Cluster Projects GM
Portfolios Strategic Planning & Spending Efficiency
Consulted:
Director
Cluster Projects GM
Informed:
Portfolios Strategic Planning & Spending Efficiency
Director
Procedure: ● Review and giving 1st approval the completed Business Case/s within 7
days.
● Use (PMF-004-FYP-018 Five Case Model Guidelines), Use (PMF-004-
FYP-001 Business Case) and (PMF-004-FYP-004 Business Case
Checklist) to review the Business Case.
● Send the Business Case to the Capital Projects Strategic Planning GM
for review and final approval.
Technical Services GM
Consulted:
Scheduling & Control GM
PMO GM
Portfolios Strategic Planning & Spending Efficiency
Director
Strategic Studies Manager
Cluster Projects GM
Project Requester
Portfolios Strategic Planning & Spending Efficiency
Informed:
Director
4.3.4.9 PMM-004-FYP-030-060 Confirm Projects Suitable for Private Sector
Participation
Procedure: ● Asses every project that had a Business Case to determine whether they
are suitable or not for potential private sector participation.
● Forward all projects identified as potentially suitable for private sector
participation to the National Centre for Privatization (NCP) for formal
assessment.
● Receive the response from NCP and:
○ Projects that deemed (by the NCP) suitable for private sector
participation, shall follow the NCP’s defined project delivery route.
○ Projects that deemed (by the NCP) NOT suitable for private sector
participation, shall continue in FYPP planning for further action.
Cluster Projects GM
Roles: Responsible:
Cluster Strategic Planning Manager
Cluster Technical Services Director
Accountable: Cluster Projects GM
National Master Plan Consultant
Consulted:
Portfolios Strategic Planning & Spending Efficiency
Director
Strategic Studies Manager
National Centre for Privatization (NCP)
Capital Projects Strategic Planning GM
Informed:
Cluster Senior GM
1. The draft FYPPP with all its documentation must be submitted to the Joint Working
Group (CAPEX Panel) for formal review and written feedback.
4.4.3 Flowchart
Figure 4-6 PMM-004-FYP-040 Prepare Draft FYPPP and Submit for Review Flowchart
4.4.4 Procedures
4.4.4.1 PMM-004-FYP-040-010 Develop Draft Cluster FYPPP
Procedure: ● Based on outcomes from the previous phase, prepare a Draft Cluster
FYPPP.
○ Include in the draft plan all projects which shall seek for MOF funding
approval.
○ Develop an initial financial plan for the FYPPP.
○ Attach documentations prepared in the previous processes to the
projects included within the draft plan.
● Use (PMF-004-FYP-005 Draft Five-Year Projects Portfolio Plan
Checklist) to help prepare Draft Cluster FYPPP.
● Endorse the Draft Cluster FYPPP.
● Raise the Draft Cluster FYPPP to Capital Projects Strategic Planning
GM.
Cluster Strategic Planning Manager
Roles: Responsible:
Cluster Technical Services Director
Cluster Projects GM
Accountable: Cluster Projects GM
National Master Plan Consultant
Consulted:
Portfolios Strategic Planning & Spending Efficiency
Director
Strategic Studies Manager
Cluster Asset Management & Operation Excellence
Director
Procedure: ● Submit DRAFT Entity 5-Year Projects Portfolio Plan to the Joint Working
Group (CAPEX Panel) for review.
● Present the DRAFT Entity 5-Year Projects Portfolio Plan and all its
documentations to the Joint Working Group (CAPEX Panel).
● If the Joint Working Group (CAPEX Panel) inquires about submitted plan,
promptly reply.
Cluster Projects GM
Consulted:
Capital Projects & Technical Services VP
Joint Working Group (CAPEX Panel)
Informed: Joint Working Group (CAPEX Panel)
4.5.4 Procedures
4.5.4.1 PMM-004-FYP-050-010 Receive and Review Formal CAPEX Panel Feedback
Procedure: ● Study the feedback received from Joint Working Group (CAPEX Panel).
● Update Draft Cluster FYPPP by:
○ incorporating the feedback in the Draft Cluster FYPPP.
○ performing any consequent change, revision, re-prioritization on the
Draft Cluster 5-Year Projects Portfolio Plan.
● Develop the Final Cluster FYPPP.
● Endorse the Final Cluster FYPPP.
● Use (PMF-004-FYP-006 Final Five-Year Projects Portfolio Plan
Checklist) to help develop the Final Cluster FYPPP.
1. The Final NWC FYPPP is the result of consolidation of the six Final Cluster FYPPPs.
2. The Final NWC Annual Capital Works Plan is the result of consolidation of the six
Final Cluster Annual Capital Works Plan.
3. Every cluster is responsible to annually update the Cluster FYPP in alignment with
the Local Master Plan. The cluster is to obtain approval on the updated Cluster FYPP
form Capital Projects Strategic Planning GM as per the approved updating
procedures. The guideline (PMF-004-FYP-022 FYPP Update Guidelines) to be used
in updating process.
4.6.3 Flowchart
Figure 4-8 PMM-004-FYP-060 Prepare Final FYPPP and Annual Capital Works Plan and Submit to
MOF for Budget Approval Flowchart
4.6.4 Procedures
4.6.4.1 PMM-004-FYP-060-010 Develop the Final NWC FYPPP and Final NWC
Capital Works Plan
Procedure: ● Submit Final NWC FYPPP and Final NWC Annual Capital Works Plan to
the Joint Working Group (CAPEX Panel) for approval.
● Present the Final NWC FYPPP and Final NWC Annual Capital Works
Plan and all related documentations to the Joint Working Group (CAPEX
Panel).
● If the Joint Working Group (CAPEX Panel) inquires about submitted
plans, promptly reply.
Procedure: ● After receiving the CAPEX Panel approval, give final approval on the
NWC FYPPP and NWC Annual Capital Works Plan.
● Upload the approved NWC FYPPP and NWC Annual Capital Works Plan
to OPPM.
4.6.4.5 PMM-004-FYP-060-050 Distribute the Approval from CAPEX Panel and MOF
Procedure: ● Share with Capital Projects & Technical Services VP and Cluster
Projects GM the:
○ FYPPP and Annual Plan approvals from Joint Working Group
(CAPEX Panel).
○ Budget (approval / approval with conditions) from MOF
● Share with Joint Working Group (CAPEX Panel) the Budget (approval /
approval with comments) form MOF.
● Post MOF budget approval, NWC shall then register its projects with
Mashroat as a first action in the first stage in project life cycle.
4.7.3 Flowchart
Figure 4-9 PMM-004-FYP-070 Five-Year Projects Portfolio Variation Control Flowchart
4.7.4 Procedures
4.7.4.1 PMM-004-FYP-070-010 Develop FYPP Variation Documents
Procedure: ● Monitor any need to make any change to FYPPP such as:
○ execute a new project that not included in the approved FYPPP.
○ make any change to any aspect to a project that included in the
FYPPP.
● If monitored a need to:
○ create a new project:
- Identify and document the need (the problem).
- Conduct and document a Strategic Assessment for the needed
project.
- Develop and document Class 5 Cost Estimation.
- Develop and document Level 1 Schedule for the project.
- Identify the preferred site option over at least three site options
by conducting assessment investigations. Investigation
activities shall be documented.
- Identify, over a workshop, potential project risks and document
the identified risks in a list.
- Perform a Cross Sector Integration research and document the
activities and results.
- Develop a Business Case for a new project or update an
existing Business Case for a project exists in the FYPPP using
(PMF-004-FYP-001 Business Case), (PMF-004-FYP-004
Business Case Checklist) and (PMF-004-FYP-018 Five Case
Model Guidelines for Business Case) to develop the Business
Case.
○ change an aspect in a project in the FYPPP:
- Identify and document the need (the problem).
- Conduct and document a Strategic Assessment for the needed
change.
- Propose and document a revised version to the followings as
needed after performing required studies, consultation and
investigations:
· Class 5 Cost Estimation
· Level 1 Schedule.
· preferred site location.
· Risk Lists.
· Cross Sector Integration research.
· Business Case.
Procedure: ● Capital Projects Strategic Planning GM shall consult the followings about
the Business Case elements within 5 days:
○ Technical Services GM on Project Scope and Class 5 Cost.
○ Scheduling & Control GM on Level 1 Project Schedule.
○ PMO GM on Risk List.
○ Portfolios Strategic Planning & Spending Efficiency Director on the
Financial Case.
○ Strategic Studies Manager to agree on Commercial Case.
● Based on the above feedback, Portfolios Strategic Planning & Spending
Efficiency Director and Strategic Studies Manager shall review and
comment:
○ the remaining sections on the Business Case
○ all documents of the FYPP Variation Request.
● Capital Projects Strategic Planning GM shall forward the feedback
comments to the Cluster Projects GM for implementation
● Update the (PMF-004-FYP-020 FYPP Variation Register) accordingly.
Procedure: ● Capital Projects Strategic Planning GM shall forward the FYPP Variation
Request with its Business Case to Joint Working Group (CAPEX Panel)
for review and approval if applicable.
● Capital Projects Strategic Planning GM shall receive the Joint Working
Group (CAPEX Panel) feedback and comments if any.
● Capital Projects Strategic Planning GM shall forward the comments to
the Cluster Projects GM for implementation.
● Cluster Projects GM shall implement the comments through Cluster
Technical Services Department then shall return the revised Business
Case to Capital Projects Strategic Planning department. If there is any
inquiry to Joint Working Group (CAPEX Panel), Cluster Technical
Services Department shall seek inquiry feedback from Joint Working
Group (CAPEX Panel) through Capital Projects Strategic Planning
department.
● Capital Projects Strategic Planning GM shall forward the revised
Business Case to Joint Working Group (CAPEX Panel) for review and
approval.
● Update the (PMF-004-FYP-020 FYPP Variation Register) accordingly.
Procedure: ● Review the FYPP variation request and its attached documentations.
● As needed, discuss with Cluster Senior GM and request for any
additional information.
● Approve the FYPP Variation Request and forward it to Capital Capital
Projects & Technical Services VP for final approval.
● Update the (PMF-004-FYP-020 FYPP Variation Register) accordingly.
● This procedure shall be completed within 5 days.
Procedure: ● Review the FYPP variation request and its attached documents.
● As needed, Discuss with Capital Projects Strategic Planning GM and
provide any required directions.
● Give final approval on the FYPP Variation Request and send it to Capital
Projects Strategic Planning GM for implementation.
● Update the (PMF-004-FYP-020 FYPP Variation Register) accordingly.
● This procedure shall be completed within 5 days.
Procedure: ● Capital Projects Strategic Planning GM shall send the approved FYPP
Variation to Portfolios Strategic Planning and Spending Efficiency
Director for implementations.
● Portfolios Strategic Planning and Spending Efficiency Director shall:
○ notify all relevant stakeholders of approved variation and the
variation order.
○ implement the approved FYPPP Variation and update all required
documents.
○ publish the varied FYPPP.
● Update the (PMF-004-FYP-020 FYPP Variation Register) accordingly.
● This procedure shall be completed within 5 days.
Portfolios Strategic Planning & Spending Efficiency
Roles: Responsible:
Director
Capital Projects Strategic Planning GM
Accountable: Capital Projects Strategic Planning GM
4.9 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-004-
FYP Five-Year Projects Portfolio Planning).
Table 4-2 Project Five-Year Projects Portfolio Planning forms, templates and guidelines
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This section is developed as an update to “Team” section in first version the Project
Management Manual (PMM) which developed by Faithful + Gould. The following are
the changes:
● Updating 5 job profile and delete 34.
Contract Manager HQ
PMO GM HQ
Technical Services GM HQ
Engineering Director HQ
Execution Director HQ
Agreement Manager HQ
Contractor External
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022
Abdulaziz K. Aljawan
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
● external influences do not adversely affect the success of projects, as far as practicable.
● ensure that the PMM effectively and efficiently interfaces with other NWC department
manuals and policies, and that PMM is maintained as a valuable knowledge base for
the management of capital projects.
6.1.2 Policies
Policies for this process are as follows:
1. Enterprise Environmental factors includes but not limited to:
i. NWC’s business culture and company structure.
ii. KSA governmental and industry standards (e.g. regulatory agency regulations,
product standards, quality standards, and workmanship standards).
iii. Infrastructure (e.g. existing facilities and capital equipment).
iv. Existing human resources (e.g. skills, disciplines, and knowledge, such as
design, development, legal, contracting and purchasing).
v. Personnel administration (e.g. hiring and firing guidelines, employee
performance reviews, and training records).
vi. The NWC authorizing system.
vii. Marketplace conditions.
viii. Stakeholder risk tolerances (e.g. especially the Ministries of Finance and
Electricity & Water); and
ix. Commercial databases (e.g. standardized cost estimating data, industry risk
study information, and risk databases).
x. NWC Compliance Framework which includes all applicable external regulations.
2. Periodic reviews shall be performed by the Strategic Studies Manager of the above
factors mentioned above.
3. Known and suspected external influences, which can impact upon the success of
NWC’s capital projects, must be reviewed by the Strategic Studies Manager as part
of a structured Semi-annual review of the PMM.
4. The review must be documented and discussed as part of a scheduled Management
Review Meeting.
5. Approved PMM changes (i.e. improvements) must be carried out in a formal manner
in response to the above written review report and its subsequent discussion by
attendees at the Management Review Meeting.
6. The process relies upon periodic reviews by the Continuous Improvement Lead of
changes made by other departments to their policy and procedure manuals, in order
to ensure that PMM remains aligned.
7. The policy and procedure manuals of other departments within NWC must be
reviewed by the Continuous Improvement Lead, in order to identify potential impacts
upon the PMM.
8. The review must be documented and discussed as part of a scheduled Management
Review Meeting.
9. There must be a formal lesson learned capture exercise at the closure of every capital
project, with the findings fed back to improve the PMM for future projects.
6.1.3 Flowchart
Figure 6-1 PMM-006-GOV-010 Enterprise Environmental Factors and Organizational Process Assets
Flowchart
6.1.4 Procedures
6.1.4.1 PMM-006-GOV-010-010 Schedule EEFs & OPAs Reviews
Procedure: ● Collect Semi-Annual EEFs & OPAs reports that developed at cluster
levels.
● Consolidate the cluster Semi-Annual EEFs and OPAs reports into NWC
Semi-Annual EEFs and OPAs report.
● Retain the report in NWC ECMS.
3. Unless otherwise stated, the Project Initiator is always the named the “Cluster Asset
Management & Operation Excellence GM”.
4. The “Cluster Asset Management & Operation Excellence” must always document the
initiation of projects through inclusion in the periodic Asset Management/Development
Plan, supported by a Business Case document.
5. The Sponsor is always the named Capital Projects & Technical Services VP, who is
accountable for securing and controlling the financial resources to undertake the
project.
6. The Project Initiator and Sponsor must always engage the specialists in Cost
Estimation, scheduling and Risk Management in Clusters in order to support the
Business Case with a realistic budget estimate, an estimate of the project duration, a
consideration of sequencing and packaging within the program/portfolio, and the early
creation of risk registers through the holding of a formal workshop.
6.2.3 Flowchart
Figure 6-2 PMM-006-GOV-030 Project Initiator and Sponsor Flowchart
6.2.4 Procedures
6.2.4.1 PMM-006-GOV-030-010 Ensure the Project Initiator is Named and Recorded
Procedure: ● Before allowing the project to start its Initial Planning, check that the
Project Initiator is identified in the (PMF-004-FYP-001 Business Case).
● Do not allow the project to start if the Project Initiator is not clear or maybe
incorrect.
Roles:
Responsible: Cluster Projects GM
Procedure: ● Before allowing the project to start its Initial Planning, check that the
Project Sponsor is identified in the (PMF-004-FYP-001 Business Case).
● Do not allow the project to start if the Sponsor is not clear or maybe
incorrect.
6.3.3 Flowchart
Figure 6-3 PMM-006-GOV-040 End User Flowchart
6.3.4 Procedures
6.3.4.1 PMM-006-GOV-040-010 Ensure That Whole-Life Costing Consideration Was
Made
6.3.4.2 PMM-006-GOV-040-020 Ensure That O&M Topics and Expertise Are Fully
Covered in Workshops
Procedure: ● Design reviews and studies are to be recorded via the Design Review
Checklist.
● Completed checklists must indicate that the relevant experts in Cluster
Asset Management & Operation Excellence department were involved
as part of the reviews and studies.
Procedure: ● At design stage, ensure the identifications of the design deliverables that
the O&M experts shall participate in reviewing and approving.
● Ensure and record O&M experts participation in document reviews and
approvals.
● Completed forms must indicate that the relevant experts in Cluster Asset
Management & Operation Excellence department were involved as part
of the review and approval of O&M documents.
guidelines must be identically styled; all learning support materials must be identically
styled).
5. A complete list of PMM documents must be maintained by the Center of Excellence
Director.
6. All PMM documents must be version-controlled, starting from version 1 and
incrementing to version 2, 3, 4, etc. in major increments (i.e. whole version numbers).
7. Version history information must be included in a table in the PMM document itself,
wherever it is practicable to do so (i.e. all PMM documents except simple forms, which
would become cumbersome if version history was embedded).
8. All master electronic files must be securely stored by the Center of Excellence
Director, to prevent loss of files and also to prevent unauthorized changes by users.
9. A working copy of the current version of all PMM documents must be made available
to all Clusters.
10. Formal PMM document Variation Notices issued by the Center of Excellence Director
must clearly state whether or not the change applies to ongoing projects, seeing as
some changes may have contractual implications.
11. All PMM document changes must be recorded in accordance with the procedure
(PMM-006-GOV-060 Control of PMM Documents).
12. Every project document number must be unique using (EPM-ID0-PR-000002 Project
Standard Document Numbering Procedure). If the document mandatorily shall have
a number by NWC systems such as BARQ, TATABOA or ECMS, the Document
Controller is responsible to ensure the uniqueness of this number.
13. Continual improvement, in PMM terms, has two dimensions:
● Increasing the extent to which planned activities are realized (i.e. raising the
degree of compliance with written procedures held within the PMM); and
● Increasing the extent to which planned results are achieved (i.e. progressive
achievement of the tactical and strategic objectives, which are the desired
business benefits of implementing the PMM.
14. The following PMM documents and records are used to drive continual improvement
(illustrated in Figure 6-2, below):
● The NWC Corporate Policy Statements for Quality and HSE sets the
framework for definition of the tactical objectives on projects.
● The tactical objectives themselves define a large subset of targets in support
of the current NWC strategic objectives
● The results of internal and external audits. since audit activity is largely aimed
at sampling the degree of compliance with written procedures in the Project
Management Manual
● Analysis of data. Principally the KPI data, since these are documented in the
PMM KPI Report, where historical trends can be analyzed, future projections
can be made and business decisions can be supported in order to re-align
business performance with the planned targets. Also, root cause analysis of
audit findings and red traffic lights on the PMM KPI Report.
● Corrective actions, since by their very nature, this type of action is designed to
retrospectively remedy those problems in the business, which have already
been identified and experienced
● Preventive actions, since prevention is better than cure (corrective action) –
although the resources expended on preventive action must be reasonably
practicable in consideration of the defects likely to occur if the preventive action
were not put in place (i.e. increased effectiveness is not to be achieved through
uneconomic reduction in efficiency)
● Management review, since this activity is singularly aimed at retrospectively
assessing PMM performance and proactively considering whether or not the
degree of business direction and control provided by the PMM in its current
mode of use is sufficient to achieve the planned strategic objectives.
15. As shown in the diagram, other contributors toward continual improvement arise
through Project Team engagement and team members considering its performance
and potential in relation to their own work and team/personal objectives. Problems
may be highlighted and innovative improvements may be suggested.
16. All employees are empowered, and encouraged, to suggest changes to the PMM
using the formal PMM Improvement Request Form, or by contacting the Continuous
Improvement Lead in person. See the (PMF-006-GOV-032 PMM Improvement
Request Form).
17. The form may be located, completed and submitted online using the SharePoint portal
or may be used in hard-copy format.
18. A log of PMM improvement requests is maintained in the PMM by the Continuous
Improvement Lead. See the (PMF-006-GOV-033 PMM Improvement Request
Register).
19. PMM user feedback (which can include staff complaints) and suggested changes may
also be requested anonymously through use of the Suggestion Box Scheme. A
suggestion box is available at each office, including construction site offices. Each
box is checked and emptied at least once a week by the key holder.
20. As well as physical suggestion boxes at work locations, there is also a virtual box
provided online through the business intranet.
21. All implemented changes to the PMM are notified to PMM users official
announcement.
22. Rejected or suspended requests and suggestions are notified to the contributing
member of staff, with business justification.
23. A log of Suggestion Box Requests is maintained in the PMM by the Management
Representative.
24. PMM improvement requests and staff suggestions can be made at any time and are
an important contribution towards continual improvement. Recognition of innovation
may be made to contributing employees through appropriate reward to the individual,
in accordance with the Human Resource Policy and Procedure Manual.
6.4.3 Flowchart
Figure 6-5 PMM-006-GOV-050 PMM Update and Continual Improvement Flowchart
6.4.4 Procedures
6.4.4.1 PMM-006-GOV-050-010 Maintain a Register of External Requirement
Documents
Procedure: ● The Capital Projects & Technical Services VP shall approve the updated
document.
● The document shall be raised to the Business Excellence Department
for publishing.
Roles:
Responsible: Capital Projects & Technical Services VP
Accountable: PMO GM
8. The default for soft-copy, project-level PMM records (such as original documents and
correspondence scan files) is to retain within ECMS until handover, upon which
selective files may be retained “online” as a project management knowledge base,
and the remaining files may be retained “offline” as an archive disk in a fireproof and
waterproof safe; or may be moved with the help of NWC’s IT Dept. to an alternative
file server.
6.5.3 Flowchart
Figure 6-6 PMM-006-GOV-060 Control of Project Management Documents Flowchart
6.5.4 Procedures
6.5.4.1 PMM-006-GOV-060-010 Ensure All Documents Are Uniquely Identified,
Stored and Secured
Procedure: ● As new versions of PMM and its attachments are developed, annually
review the need for:
○ larger secure storing area for hard copies in collaboration with
Business Excellence GM
○ larger secured server for soft copies in collaboration with Document
Control Manager.
● Use the (PMF-006-GOV-009 Archival Instruction) and (PMF-006-GOV-
010 Archival Instruction Register) to review all archival and retention
instructions.
Procedure: ● A review shall be carried out at the end of each defined retention period.
In review decide if there is a need for further retention or not.
● Carry out the steps described on the (PMF-006-GOV-009 Archival
Instruction).
● Keep the (PMF-006-GOV-010 Archival Instruction Register) up-to-date
with all completed steps.
● Final disposal decisions must be approved by the PMO GM.
● Retain or dispose of the archive according to the written instruction.
Business Excellence GM
Informed:
Document Control Manager
6.6.3 Flowchart
Figure 6-7 PMM-006-GOV-070 Control Responsibilities and Authorities Flowchart
6.6.4 Procedures
6.6.4.1 PMM-006-GOV-070-010 Develop Organizational Structures for Projects
Teams of HQ and Clusters
Procedure: ● Develop Job Profiles for projects team members at HQ and Clusters in
collaboration with:
○ Project & Technical Services department staff
○ NWC Human Capital department
○ Any NWC department as required
● Obtain required approvals from authorized person as per NWC policies.
● Cascade the approved Organizational Structures for HQ and Clusters to
all NWC Project Team.
● If a change request on approved Job Profile(s) raised, it must be
reviewed and approved through PMO GM from the authorized person at
HQ as per NWC policies.
Accountable: PMO GM
Procedure: ● Review and approve/reject the submitted Local Work Instruction for RAM
Change and/or the Delegation of Authority.
● Send the approved/rejected Local Work Instruction for RAM Change
and/or the Delegation of Authority to the Cluster Projects GM for
cascading.
● Send a copy the Cluster PMO Manager to update the (PMF-006-GOV-
012 Register of Local Work Instruction and Delegation of Authority).
Accountable: PMO GM
Cluster Projects GM
Informed:
Cluster PMO Manager
6.7.4 Procedures
6.7.4.1 PMM-006-GOV-080-010 Ensure the Management Representative is
Authorized, Named and Recorded
Procedure: ● The role holder is the PMO GM, unless an alternative is authorized by
the Capital Projects & Technical Services VP.
● The Management Representative shall do but not limited to the following:
○ ensure that the processes needed for the PMM are established and
subsequently implemented and maintained.
○ report to the Capital Projects & Technical Services VP on all matters
regarding the PMM and advice on resources required to ensure its
ongoing effectiveness and efficiency.
○ organize management review meetings and all associated
paperwork.
○ ensure promotion of suitable awareness of the PMM throughout
relevant project stakeholders in the NWC business, Consultants and
Contractors.
○ liaise with external assessors, such as Government Auditors and
NPMO
Consulted: PMO GM
Informed: PMO GM
6.8.3 Flowchart
Figure 6-9 PMM-006-GOV-100 Management Review Flowchart
6.8.4 Procedures
6.8.4.1 PMM-006-GOV-100-010 Compile a Briefing Paper and Agenda and Send an
Invitation for Management Review Meeting
Accountable: PMO GM
Procedure: ● Follow the agenda and cover all points of the briefing paper.
● Record all non-attendance.
● Use (PMF-006-GOV-018 PMM Management Review Meeting Minutes).
● Develop and distribute the meeting minutes using (PMF-014-COM-051
Standard Minutes of Meeting Template), requesting a read receipt.
● Start the actions and complete them by the due-date.
Center of Excellence Director
Roles: Responsible:
Action Owners
Accountable: PMO GM
6.9.4 Procedures
6.9.4.1 PMM-006-GOV-110-010 Maintain a Centralized Register of Project Team
Members History
Accountable: PMO GM
Cluster Projects GM
Consulted:
Cluster PMO Manager
PMO GM
Informed:
Cluster Projects GM
Cluster PMO Manager
6.9.4.2 PMM-006-GOV-110-020 Maintain a Centralized Register of Inductions and
Trainings
Accountable: PMO GM
Cluster Projects GM
Consulted:
Cluster PMO Manager
PMO GM
Informed:
Cluster Projects GM
Cluster PMO Manager
6.9.4.3 PMM-006-GOV-110-030 Review Performance Appraisal Records for
Continual Improvement Opportunities
Cluster Projects GM
Consulted:
Cluster PMO Manager
PMO GM
Informed:
Cluster Projects GM
Cluster PMO Manager
Procurement Dept. to ensure that essential infrastructure items are available as and
when required.
3. Threats to continuity of project delivery through failure of infrastructure must be
evaluated and mitigated by the Cluster projects GM, in close coordination with the
Procurement Dept. and the Cluster Risk Section Head.
4. Observed defects within the infrastructure must be recorded using the Non-
Conformance reporting system during the course of carrying out internal audits.
6.10.3 Flowchart
Figure 6-11 PMM-006-GOV-120 Infrastructure Flowchart
6.10.4 Procedures
6.10.4.1 PMM-006-GOV-120-010 Keep Local Infrastructure Requirements Under
Review
6.11.4 Procedures
6.11.4.1 PMM-006-GOV-130-010 Keep Local Work Environment Under Review
6.12.3 Flowchart
Figure 6-13 PMM-006-GOV-140 PMM user feedback Flowchart
6.12.4 Procedures
6.12.4.1 PMM-006-GOV-140-010 Run Online Semi-Annual PMM Surveys
Consulted: PMO GM
Roles:
Responsible: PMM User Feedback Initiator
5. The approved PMP constitutes the main audit criterion for all internal, project-based
audits.
6. The full, correct and approved completion of project planning is a vital milestone and
shall be subject to internal audit as verification of the project’s readiness to move
beyond the Feasibility study into the execution stages of Design and Construction.
7. Thereafter, the two supporting management plans (Design Management Plan by the
Design Consultant and Construction Management Plan by the Contractor) also
become criteria for subsequent audits.
8. Projects must be added to the PMM Internal Audit Schedule by the Quality Assurance
Director. See (PMF-006-GOV-027 PMM Audit Schedule).
9. Internal audits must be structured, using standard checklist and report formats. See
(PMF-006-GOV-028 PMM Audit Checklist) and (PMF-006-GOV-029 PMM Audit
Report); also, (PMF-014-COM-013 Non Conformance Report NCR) and (PMF-006-
GOV-036 PMM NCRs Register).
10. Internal Audits must be led by authorized Lead Auditors and carried out by authorized
auditors.
11. The Quality Assurance Director must create and maintain a central register of Lead
Auditors and Internal Auditors, providing assurance of competence to act in the role.
See (PMF-006-GOV-030 PMM Auditors Register).
12. Lead Auditors and Internal Auditors must actively participate in at least one internal
audit per quarter in order to remain on the register.
13. The Quality Assurance Director must oversee the evaluation of performance by Lead
Auditors and Internal Auditors.
14. Ability to act as a Lead Auditor or Internal Auditor should be recorded favorably during
the performance appraisal of staff and must be encouraged as a means to support
career progression within NWC.
15. In line with best practice, follow-up audits should be scheduled in order to verify that
corrective and preventive actions have been documented, approved, implemented
and monitored for effectiveness
6.13.3 Flowchart
Figure 6-14 PMM-006-GOV-160 Internal Audit Flowchart
6.13.4 Procedures
6.13.4.1 PMM-006-GOV-160-010 Develop Cluster Internal Audit Schedule
6.14.4 Procedures
6.14.4.1 PMM-006-GOV-170-010 Apply Appropriate Resources to Gather PMM
Process data
Procedure: ● As per timing of every KPI, formally gather the required data from proper
sources at clusters and HQ to apply PMM KPIs.
● Use the (PMF-006-GOV-015 KPI Report) to develop the KPI Report on
monthly basis.
● Justify for every missing data and/or unsatisfactory data from the Cluster.
Procedure: ● Receive KPI Reports from all cluster and consolidate them into one
report.
● Review the provided reasons of missing and/or unsatisfactory data.
● Review the description of corrective actions already in-hand.
● Analyze the reports to identify common trends across clusters and
benchmarking between clusters.
● This procedure to be performed on monthly basis.
Consulted: PMO GM
Capital Projects & Technical Services GMs
Informed:
Cluster Projects GMs
6.14.4.4 PMM-006-GOV-170-040 Escalate Issues and Publish Final KPI Report
Procedure: ● Review projects and cluster issues with the relevant Cluster Projects GM
and agree with them any action plans and escalation requirements.
● Escalate serious issues, trends and benchmarking problems to the
Capital Projects & Technical Services VP and Cluster Senior GM.
● Record all referrals and escalations as part of the consolidated KPI
Report.
● Agree with the PMO GM which report elements should be published,
including or excluding referrals and escalations (which may be sensitive
for a variety of reasons).
● Publish the agreed, final KPI Report to HQ and Clusters.
● This procedure to be performed on monthly basis.
Accountable: PMO GM
the bottom-up view of progress towards asset delivery, whereas the stage gate
reviews give the top-down assurance that all risks and issues were adequately
addressed whilst the reported progress was being achieved.
5. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
6.15.3 Flowchart
Figure 6-16 PMM-006-GOV-180 Stage Gate Review Flowchart
6.15.4 Procedures
6.15.4.1 PMM-006-GOV-180-010 Notify the Cluster Projects GM by Project Stage
Completions before Two Months
Procedure: ● Make two months forecast based upon the latest approved updated
project schedule and the forecast dates for stage completions.
● If the two months forecast expects the stage completion within, send
notification to scheduled attendees (as per “2.2.2 Gate Committee”) and
Cluster Projects GM for a stage gate review.
● One month later remind all parties about this notification.
Procedure: ● Liaise with the NWC Project Manager, and other parties as needed to
compile objective evidence of stage completion.
● Use the (PMF-006-GOV-037 Stage Gate Review Checklist).
6.15.4.4 PMM-006-GOV-180-040 Conduct the Meeting and Compile Minutes for the
Stage Gate Review Meeting
Procedure: ● Conduct the Stage Gate Review meeting following the agenda.
● The NWC Project Manager must record all non-attendance and any poor
or negative participation.
● Use the meeting record section of the (PMF-006-GOV-037 Stage Gate
Review Checklist) and record all required actions.
● Develop and distribute the Meeting Minutes using (PMF-014-COM-051
Standard Minutes of Meeting Template).
● Update the (PMF-006-GOV-038 Stage Gate Review Register).
Procedure: ● Receive the Minutes and start the actions and complete them by the due
dates.
Procedure: ● Check if all actions are completed using the (PMF-006-GOV-037 Stage
Gate Review Checklist).
● Once all actions are completed, formally approve the project stage
completion.
● Update the (PMF-006-GOV-038 Stage Gate Review Register) which is
for cluster level.
● Inform Scheduling & Control GM and PMO GM by the updated (PMF-
006-GOV-038 Stage Gate Review Register).
6.16.3 Flowchart
Figure 6-17 PMM-006-GOV-190 Project Management Data Analysis Flowchart
6.16.4 Procedures
6.16.4.1 PMM-006-GOV-190-010 Review the Project Management Registers and KPI
Reports
Procedure: ● On semi-annual basis, review the Project Management registers and KPI
reports.
● Relevant Project Management registers include:
○ (PMF-006-GOV-012 Local Work Instruction Register).
○ (PMF-013-HUM-002 Project Team Members Register).
○ (PMF-013-HUM-003 Induction and Training Register).
○ (PMF-006-GOV-024 PMM User Feedback Register).
○ (PMF-006-GOV-025 Monitoring and Measuring Equipment
Register)
○ (PMF-006-GOV-030 PMM Auditors Register).
○ (PMF-006-GOV-033 PMM Improvement Register).
○ (PMF-006-GOV-034 PMM Corrective and Preventive Action
Register).
○ (PMF-006-GOV-036 PMM NCRs Register).
○ (PMF-006-GOV-038 Stage Gate Review Register).
● Review the monthly (PMF-006-GOV-015 KPI Report).
● Consider interfaces with other NWC management systems (e.g. with
Supply Chain department management policies and procedures).
● Make a written note of all perceived strengths and weaknesses, for
potential inclusion in the next PMM management review briefing paper.
Percentage of number
of workshops conducted
in a project with
O&M experts attendance of O&M
participation in experts from Asset
2 Quarterly 1 90% < 90%
workshops of a Management &
project Operation Excellence to
total workshops
conducted in the
projects.
Percentage of number
of design reviews and
approvals in a project in
O&M experts
participation by O&M
participation in
experts from Asset
3 design reviews and Quarterly 1 90% < 90%
Management &
approvals in a
Operation Excellence to
project
the total number of the
conducted design
reviews in the project.
Number of PMM
PMM NCRs in a
4 application NCRs in a Monthly 0 3 >3
project in a month
project.
Number of PMM
PMM NCRs in a
5 application NCRs in a Monthly 0 12 > 12
cluster in a month
cluster.
Percentage of year-to-
date number of
performed PMM
PMM inductions in
9 inductions in a project to Quarterly 1 90% < 90%
a project
total required/planned
PMM Inductions in the
project.
Percentage of year-to-
date number of role-
Role-based based trainings in a
10 trainings in a project to total Quarterly 1 90% < 90%
project required/planned role-
based trainings in the
project.
Percentage of year-to-
date number of
Performance
performed appraisals in
11 appraisals in a Quarterly 1 90% < 90%
a project to total
project
required/planned PMM
appraisals in the project.
Year-to-date number of
Work environment
12 work environment NCRs Quarterly 0 4 >4
NCRs in a cluster
in a cluster
Percentage of year-to-
date number of
Year-to-date audits unperformed scheduled
16 conducting in a audits in a cluster to the Monthly 0 90% > 90%
cluster year-to-date total
scheduled audits in the
cluster.
Year-to-date number of
Projects continue
projects continue
23 without stage gate Monthly 0 3% > 3%
without stage gate
reviews
reviews.
Number of calendar
Time taken to
days elapsed since the
perform stage gate
24 stage gate review Monthly 14 28 > 28
review activities in
meeting to the stage
a project.
decision in a project.
6.18 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-006-
GEN Project Governance Management).
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-007-INT-015 Plan Integration Management” is added.
● The process “PMM-006-INT-020 Develop the Project Management Plan” is revised.
● The process “PMM-007-INT-023 Site Handover to Contractor and Consultant Work
Commencement” is transferred from Procurement section and revised.
Change
Description ● The process “PMM-007-INT-026 Conduct Project Kick Off Meeting” is transferred
from Procurement section and revised.
● The process “PMM-007-INT-060 Integrated Change Control” is revised.
● The process “PMM-007-INT-070 Close the Project” is revised.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
7.1.4 Procedures
7.1.4.1 PMM-007-INT-010-010 Develop the Project Charter
2. The approved Project Management Plan, including the Integration Management Plan
section, must be included in the tender document when NWC is procuring Second
Party services and products in support of project execution.
3. Second Parties must create their own Integration Management Plan sections for the
project as part of their contract mobilization work. These Integration Management
Plan Sections must be approved by NWC during mobilization period.
4. The Integration Management Plans in PMPs of NWC, Design and Construction must
be kept up-to-date throughout the project life cycle.
5. Planning for Integration must be specific and unique to the location, activities and
characteristics of the project. It must not be generic or wholesale copy-and-paste from
previous projects, else it will be rejected and the work will not be allowed to proceed.
7.2.3 Flowchart
Figure 7-3 PMM-007-INT-015 Plan Project Integration Management Flowchart
7.2.4 Procedures
7.2.4.1 PMM-007-INT-015-010 Develop the Integration Management Plan Section of
the Project Management Plan
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the design RFP.
● Ensure the requirement “The Design Consultant is required to create his
own Integration Management Plan and must submit it during the
contractual mobilization period” is stated in the NWC Project
Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes integration assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Integration Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes integration assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
7.3.3 Flowchart
Figure 7-4 PMM-007-INT-020 Develop the Project Management Plan Flowchart
7.3.4 Procedures
7.3.4.1 PMM-007-INT-020-010 Develop the Project Initial Planning Documents,
Strategies and Plans
General Services GM
Consulted:
Cluster Technical Services Director
Cluster Value Engineering Specialist
Business Unit Construction Director
Informed:
Portfolios Strategic Planning & Spending Efficiency
Director
General Services GM
7.3.4.2 PMM-007-INT-020-020 Develop the Project Management Plan
Procedure: ● Use the up-to-date PMP provided by the NWC Project Manager as an
input to develop the Design Management Plan.
● Design Consultant to use his own in-house processes and styles to
produce a project-specific Design Management Plan; but covering the
NWC PMP requirements as a minimum (or use the Design Management
Plan template provided by NWC in PMM).
● Submit the Design Management Plan for approval during the contractual
mobilization period.
Design Consultant
Consulted:
Cluster Technical Services Director
Cluster Value Engineering Specialist
Business Unit Construction Director
Cluster Risk Section Head
Cluster Scheduling Section Head
Cluster Cost Estimation Specialist
Cluster Document Control Section Head
Cluster QA Section Head
Business Unit Safety Section Head
Cluster Cost Control Section Head
Cluster Contracts Administration Section Head
Cluster HSSE Manager
Cluster Scheduling & Control Manager
Informed:
Engineering Director
Value Engineering Director
Design Consultant
7.3.4.7 PMM-007-INT-020-070 Update Section(s) of the Design Management Plan
Based on Approved Variations
Procedure: ● Use the up-to-date PMP provided by the NWC Project Manager as an
input to develop the Construction Management Plan.
● Contractor to use his own in-house processes and styles to produce a
project-specific Construction Management Plan; but covering the NWC
PMP requirements as a minimum (or use the Construction Management
Plan template provided by NWC in PMM).
● The construction management plan along with project early submissions
shall be submitted during the mobilization period which include but not
limited to:
○ Quality Management plan
○ HSE management plan
○ Organizational Chart
○ Resumes of Key Positions
○ Staffing Plan
○ Risk Register
○ Stakeholder Register
○ Site Layout
○ Permitting Plan
● The submitted Construction Project Management Plan shall consider
performing:
○ PMM-011-COS-060-010 Develop and Submit Revised BOQ
○ PMM-011-COS-060-020 Approve Revised BoQ Submitted by
Contractor at Cluster
○ PMM-011-COS-060-030 Approve Revised BoQ Submitted by
Contractor at HQ
○ PMM-011-COS-060-040 Approve Revised BoQ Submitted by
Contractor at MEWA (if required)
7.4.3 Flowchart
Figure 7-5 PMM-007-INT-023 Site Handover to Contractor and Consultant Work Commencement
Flowchart
7.4.4 Procedures
7.4.4.1 PMM-007-INT-023-010 Nominate a Presentative for Project Site Handover
Committee / Work commencement Meeting
Cluster Projects GM
Consulted:
Supervision Consultant (for site handover)
Contractor
Informed:
Supervision Consultant
Design Consultant
Cluster Contracts Administration Section Head
PMO GM
Scheduling & Control GM
Cluster Finance GM
Cluster Supply Chain Manager
7.4.4.6 PMM-007-INT-023-040 Prepare and Issue the Project Site Handover Delay
Report / Work Commencement Delay Report and Arrange Issues Removal
Cluster Projects GM
Consulted:
Supervision Consultant (for site handover)
Contractor
Informed:
Supervision Consultant
Design Consultant
7.4.4.7 PMM-007-INT-023-050 Issue Warning Letter to Contractor/Consultant
7.5.4 Procedures
7.5.4.1 PMM-007-INT-026-010 Prepare the Kickoff Meeting Agenda and Invite
Attendees
Procedure: ● Prepare the agenda for the project Kick off meeting using (PMF-007-INT-
033 Kick-off Meeting Agenda).
● Invite the following attendees to the kickoff meeting:
○ NWC Project Manager
○ Cluster Risk Section Head
○ Cluster Scheduling Section Head
○ Cluster Cost Control Section Head
○ Cluster Contracts Administration Section Head
○ Cluster QA Section Head
○ Business Unit Safety Section Head
○ Supervision Consultant Project Manager and management Team
○ Contractor Project Manager and management team
heavily on the Cluster Technical Services Director (to direct and manage the Design Consultant)
and the Supervision Consultant (to direct and manage the Contractor). The NWC Project Manager
must maintain sufficient monitoring and surveillance to ensure that the outcomes are tangibly
accomplishing the work defined in the Project Management Plan.
The approach of the NWC Project Manager is to ensure alignment between his Project
Management Plan and the Second Party management plans (i.e. Design Management Plan by the
Design Consultant and Construction Management Plan by the Contractor). This is illustrated below
in Figures 7-6 (for design-bid-build projects) and 7-7 (for design & build projects):
Figure 7-7 Directing the Project in Design-Bid-Build Projects
Direct
Project
Management
Plan
NWC
Project Manger
Design Construction
Management Management
Plan Plan
Design Construction
Planned Planned
Activities Activities
Direct
Project
Management
Plan
NWC
Project Manger
Design and
Construction
Management
Plan
Contractor Supervising
Consultant
Design and
Construction
Planned
Activities
The supporting approach of the Cluster Technical Services Director is to ensure accomplishment
by the Design Consultant of all work defined in the Design Management Plan. This is illustrated
below in Figure 7-8:
Project
Management
Plan
NWC
Project Manger
Manage
Design Construction
Management Management
Plan Plan
Design Construction
Planned Planned
Activities Activities
Project
Management
Plan
NWC
Project Manger
Manage
Design Construction
Management Management
Plan Plan
Design Construction
Planned Planned
Activities Activities
Project
Management
Plan
NWC
Project Manger
Manage
Design and
Construction
Management
Plan
Contractor Supervising
Consultant
Design and
Construction
Planned
Activities
Refer to the Project Communications Management section of the manual for information on
how work progress is measured and reported, and to the Project Risk Management section of
the manual for information on how risks to project scope, Schedule, cost and quality are
monitored and controlled through action plans owned by named persons. A key role of the
NWC Project Manager is to ensure that resources are being applied to address any shortfalls
likely to impact upon achievement of the project’s objectives.
7.7.4 Procedure:
7.7.4.1 PMM-007-INT-040-010 Identify Initial Lessons Learned / New Knowledge
Design Consultant
Consulted:
Contractor
Supervision Consultant
Cluster Projects team
Cluster PMO Manager
Lesson Learned Originator
Informed:
Continuous Improvement Lead
7.7.4.3 PMM-007-INT-040-030 Prepare Project Lessons Learned Report
Procedure: ● Prior to project closure, the Project Manager shall prepare a detailed
project lessons learned report (PMF-007-INT-021 Lessons Learned
Report).
● NWC Project Manager shall submit the report to the Continuous
Improvement Lead for review through ([email protected]).
Procedure: ● The Continuous Improvement Lead shall review the Project Lessons
Learned Report (PMF-007-INT-021 Lessons Learned Report).
● Identify the need to change any PMM processes or procedures and
process it through (PMM-006-GOV-050 Control of System Documents
and Continual Improvement)
● Insert applicable Lessons Learned to the NWC Master Lessons Learned
register (PMF-007-INT-020 Lessons Learned Register).
● Store applicable Lessons Learned in ECMS with a link to supporting
documentation.
● Send notification to NWC team about the new added Lessons Learned.
Project
Management
Plan
NWC
Project Manger
Design Construction
Management Management
Plan Plan
Design Construction
Planned Planned
Activities Activities
Figure 7-14 Monitoring and Controlling the Construction in Design & Build Projects
Project
Management
Plan
NWC
Project Manger
Design Construction
Management Management
Plan Plan
Design Construction
Planned Planned
Activities Activities
Figure 7-15 Monitoring and Controlling the Design and Construction in Design & Build Projects
Project
Management
Plan
NWC
Project Manger
Design and
Construction
Management
Plan
Contractor Supervising
Consultant
Design and
Construction
Planned
Activities
7.9.3 Flowchart
Figure 7-16 PMM-007-INT-060 Variation Control Flowchart
7.9.4 Procedures
7.9.4.1 PMM-007-INT-060-010 Initiate Project Variation Notice by NWC
Procedure: ● The scope of every variation request should be clearly defined by NWC
in collaboration with the Supervision Consultant.
● NWC shall prepare a Variation Notice including all related data, drawings
and documentation using (PMF-007-INT-013 Variation Notice Template)
and obtain the proper signatures from authorized persons.
● The Variation Notice shall be numbered and the (PMF-007-INT-010
Project Variation Register) shall be updated accordingly.
● Use (PMF-007-INT-017 Variation Notice Checklist) to ensure the
properness of key requirements that should be addressed for Variation
Notices.
● As a minimum, the following items shall be included in the Variation
Notice:
○ Descriptive scope of the variation.
○ Method of payment (lump sum, unit prices, or cost reimbursable).
○ Schedule adjustments (if known).
○ Directions to respond to the notice.
○ Technical Documents (Drawings, Specifications, Procedures,
Plans, etc.).
○ If the variation reduces the project value by more 20%, the second
party shall provide a letter stating that he accepts to reduce the
variation reduction amount without currently or lately requests any
claim from NWC.
● The approved Variation Notice will be sent to the second party.
● Refer to (PMF-007-INT-022 Variation Control Process Flow in
Governance Document).
Procedure: ● The second party shall respond to the Variation Notice initiated by NWC
within max 14 days.
● The second party shall submit for proposed work:
○ a detailed scope proposal.
○ a schedule proposal incorporated in project schedule.
○ a cost change proposal.
● Update the (PMF-007-INT-010 Project Variation Register) accordingly.
● Refer to (PMF-007-INT-022 Variation Control Process Flow in
Governance Document).
Procedure: ● The second party shall submit Variation Request that at least describes
variation aspects (mentioned next) and their effects on project aspects.
The variation aspects include but not limited to:
○ a detailed scope proposal.
○ a project schedule in P6 format that incorporates variation schedule
proposal.
○ a cost change proposal.
○ any supporting drawings and specifications.
○ any supporting documents.
○ If the variation request reduces the project value by more 20%, the
second party shall provide a letter stating that he accepts to reduce
the variation reduction amount without currently or lately requests
any claim from NWC.
● Update the (PMF-007-INT-010 Project Variation Register) accordingly.
● Refer to (PMF-007-INT-022 Variation Control Process Flow in
Governance Document).
Procedure: ● The Scheduling & Control GM shall review and forward the Variation
Request documents to Technical Services GM for review and feedback
if the variation includes new/modified BoQ items.
● The Scheduling & Control GM shall send the Variation Request
documents within 8 days to the Capital Projects & Technical Services VP
for final approval.
● The Capital Projects & Technical Services VP shall give final approval
on the variation request approval form within 2 days and send to:
○ Authorized Person for variations on MEWA Projects that include
only Extension of Time for final approval.
○ Cluster Senior GM for variations on:
- NWC Projects to forward to Cluster Negotiation & Award
department (N&A).
- MEWA Projects that includes New BoQ items or changes on
existing BoQ items to forward to Bid Examination Committee
(BEC).
● At any step of this procedure, if any additional information is required,
the requester shall request it copying the NWC Project Manager to collect
and transmit it.
● In the event that a Variation Request is rejected at any step, the project
manager shall ensure the rejection justification is recorded on the
Variation Request and shall issue a rejection letter is to be issued to
Variation Requester by the NWC Project Manager.
● Inform NWC Project Manager to update the (PMF-007-INT-010 Project
Variation Register) accordingly.
● Refer to (PMF-007-INT-022 Variation Control Process Flow in
Governance Document).
Scheduling & Control GM
Roles: Responsible:
Technical Services GM
Capital Projects & Technical Services VP
Accountable: Capital Projects & Technical Services VP
Cluster Projects GM
Consulted:
Cluster Senior GM
Authorized Person
Informed:
HQ/Cluster Negotiation & Award department (as per
authority)
Cluster Senior GM
NWC Project Manager
Procedure: ● Review the assessment and negotiate with the second party the final
cost and time impacts and agree the variation settlement.
● Send the Variation Request to the authorized person for approval.
● At any step of this procedure, if any additional information is required,
the requester shall request it copying the NWC Project Manager to collect
and transmit it.
● This procedure shall be completed within 14 days.
● Refer to (PMF-007-INT-022 Variation Control Process Flow in
Governance Document).
HQ/Cluster Negotiation & Award department (as per
Roles: Responsible:
authority)
HQ/Cluster Negotiation & Award department (as per
Accountable:
authority)
Cluster Senior GM (Cluster Projects)
Consulted:
HQ Requesting GM (HQ Projects)
NWC Project Manager
Informed: Authorized Person
Procedure: ● The Supply Chain Department shall receive the approval from the
authorized person.
● The Supply Chain Department shall ensure the documents completion
and issue the Variation Order to the second party.
● Update the (PMF-007-INT-010 Project Variation Register) accordingly.
● Refer to (PMF-007-INT-022 Variation Control Process Flow in
Governance Document).
Procedure: ● Notify all relevant parties of approved variation and the variation order
specially supply chain in order to issue the Variation PO.
● To include any changes happens as a result of the approved Variation
Order and its scope, cost and/or schedule baselines, update the affected
documents of the following:
○ Project Schedule
○ Project Schedule Forecast
○ Project Scope
○ Project Status in ENJAZ system
○ Cash Flow
○ Cash Flow Forecast
○ Risk Register
○ Quality Management Plan
○ Lessons Learned
○ Any other affected document
● Refer to (PMF-007-INT-022 Variation Control Process Flow in
Governance Document).
NWC Project Manager
Roles: Responsible:
Design Consultant / Supervision Consultant / Contractor
Supervision Consultant
Accountable: NWC Project Manager
Cluster Scheduling Section Head
Consulted:
Cluster Cost Control Section Head
Scheduling & Control GM
Informed:
Business Unit Construction Director
Portfolios Strategic Planning & Spending Efficiency
Director
Cluster Asset Management & Operation Excellence
Director
Cluster Scheduling & Control Manager
Cluster Supply Chain Manager
7.10.2 Policies
Policies for this process are as follows:
1. The closure of project requires all the contract documentation to be collected, indexed,
filed and archived.
2. Close the Project process ensures appropriate contract/s closure.
3. The Close Project “Administrative closure” includes the activities, interactions, and
related roles and responsibilities of the project team members and other stakeholders
involved in executing the administrative procedure for the project. Administrative
closure includes:
● Assembling project records.
● Gather lessons learned.
● Archive project information for future use.
4. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
7.10.3 Flowchart
Figure 7-17 PMM-007-INT-070 Close the Project Flowchart
7.10.4 Procedures
7.10.4.1 PMM-007-INT-070-010 Ensure Completeness and Properness of Initial and
Final Acceptance and Handover
Procedure: ● After getting the “GO” decision in stage gate review, Cluster Scheduling
& Control Manager shall change the Project status in ENJAZ System to
closed.
● NWC Project Manager shall notify the key stakeholders such as
Scheduling & Control GM, Cluster Projects GM, Cluster Supply Chain
Department and Cluster Finance Department that the project is closed.
Cluster Scheduling & Control Manager
Roles: Responsible:
NWC Project Manager
Accountable: Cluster Projects GM
Year-to-date number of
projects without
Project Charter approved project
1 Monthly 0 NA >0
Development charters at Initial
Planning stage in the
cluster.
Year-to-date number of
projects without
Project
approved Project
2 Management Plan Monthly 0 NA >0
Management Plans at
Development
Initial Planning stage in
the cluster.
Year-to-date number of
projects in the cluster
that handed the sites to
Site handover to contractors through a
3 Monthly 0 NA >0
Contractor committee within 60
days from PO issuance
date with the condition
the contract is signed.
Year-to-date number of
projects in the cluster
that executed variations
4 Variation Control in scope, schedule, cost Monthly 0 NA >0
or contract without
approved variation
order.
Year-to-date number of
Time for cluster variation requests that
projects raised from cluster
department to raise projects department to
5 Monthly 0 2 >2
variation requests P&TS department at HQ
to P&TS in more than 19 days
department at HQ from contractor request
submission date.
Year-to-date number of
variation requests that
Time for P&TS sent from P&TS
department at HQ department at HQ to
to raise variation cluster projects
6 Monthly 0 2 >2
requests to department in more than
negotiation & 10 days from date of
award department receiving the variation
request from cluster
projects department.
Number of calendar
days to close a project
Close Project and inform key
7 Monthly 14 28 > 28
Duration stakeholder from Final
Acceptance Report
Issuance Date.
Year-to-date number of
8 Project Closeout projects without formal Monthly 0 NA >0
project closeout.
7.12 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-007-
INT Project Integration Management).
PMF-007-INT-041 Warning Letter due to Not Attending the Work Commencement Meeting
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-008-SCO-010 Plan Project Scope Management” is elaborated.
● The process “PMM-008-SCO-030 Define Project Scope” is revised.
● The process “PMM-007-SCO-050 Control Scope” is revised.
● The process “PMM-008-SCO-055 Testing & Commissioning” is added.
Change
Description ● The process “PMM-008-SCO-060 Initial Acceptance and Handing Over of Project
Scope” is revised.
● The process “PMM-008-SCO-065 Partial Initial Acceptance and Handover of Project
Scope” is added.
● The process “PMM-008-SCO-070 Final Acceptance of Project Scope” is revised.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This section is developed as an update to “Scope” section in first version the Project
Management Manual (PMM) which developed by Faithful + Gould. The following are
the changes:
● Adding Process for Analyze Business Case and Finalize Project Requirements.
● Adding a procedure for 30% design review.
● Adding 2 processes for initial and final acceptance instead of verify scope
process.
● Adding the following forms:
○ 30% Design Review Checklist
○ 90% Design Review Checklist
○ Engineering Closeout Checklist
○ Spare Parts Record Template
○ Snag List Template
Change
Description ○ Initial Acceptance and Handover Certificate
○ Initial Handover Rejection Report
○ Final Acceptance Certificate
○ Initial Acceptance Committee Forming Request to Cluster
○ Final Acceptance Committee Forming Request
○ Initial Acceptance Committee Forming Request to HQ
○ Contractor Initial Acceptance Request letter
○ Initial Acceptance and Handing Over Process Flow in Governance
Document
○ Final Acceptance of Project Scope Process Flow in Governance Document
● Updating KPI’s.
● Updating responsibilities as per Organization Chart.
● Creating new Flowcharts.
8.1.3 Flowchart
Figure 8-3 PMM-008-SCO-010 Plan Project Scope Management Flowchart
8.1.4 Procedures
8.1.4.1 PMM-008-SCO-010-010 Develop the Scope Management Plan Section of the
Project Management Plan
Cluster Projects GM
Consulted:
Business Unit Construction Director
Technical Services GM
Technical Services GM
Informed:
Cluster Projects GM
Technical Services GM
8.1.4.2 PMM-008-SCO-010-020 Approve the Scope Management Plan Section of
Project Management Plan
Procedure: ● Review and Approve the Scope Management Plan Section of Project
Management Plan.
● Document and track the results of the reviews till they are closed out
satisfactorily.
● Approve the submitted Project Scope Management Plan Section.
● Ensure that only changes approved through (PMM-007-INT-060
Variation Control) process are implemented.
Procedure: ● Develop Project Scope Management Plan Section in the Project Design
Management Plan.
● Ensure that the Project Scope Management Plan Section in the Project
Design Management Plan is in alignment with the Project Scope
Management Plan Section in the NWC Project Management Plan.
● Consult with NWC Project Manager and Cluster Technical Services
Director about the development of the Project Scope Management Plan
Section.
● Include the Project Scope Management Plan Section in the Project
Design Management Plan to be approved as part of the Project Design
Management Plan.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Scope Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Scope assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
8.2.3 Flowchart
Figure 8-4 PMM-008-SCO-030 Define Project Scope Flowchart
8.2.4 Procedures
8.2.4.1 PMM-008-SCO-030-010 Analyze Business Case and Update Project
Requirements
8.2.4.3 PMM-008-SCO-030-023 Develop the 30% Design Package for EPC Projects
Procedure: ● Develop the project 30% Design Package utilizing, at least, the updated:
○ Owner Project Requirements (OPR).
○ Basic Design Data (BDD).
○ Design Basis Report (DBR).
● Perform internal review for the 30% Design Package using:
○ (PMF-008-SCO-040 Design Package Review Release to
Reviewers).
○ (PMF-008-SCO-038 Design Review Guidelines).
○ (PMF-008-SCO-039 Design Packages Elements).
○ Utilize (EPM-KE0-PR-000002 Design Review Procedure) as much
as possible beside the mentioned attachments.
● Update the (PMF-008-SCO-037 Requirements Traceability Matrix RTM).
● Send the 30% Design Package to Cluster Technical Services Director
for review, approval and Value Engineering.
Cluster Engineering Manager
Roles: Responsible:
Cost Estimation Lead
NWC Project Manager
Design Consultant (if a shared/devoted Design Consultant
assigned)
Accountable: Cluster Technical Services Director
Cluster Value Engineering Specialist
Consulted:
Cluster Risk Section Head
Cluster Asset Management & Operation Excellence
Director
Cluster Scheduling Section Head
Engineering Director
Material Approval Section Head
Value Engineering Director
Informed: Cluster Technical Services Director
8.2.4.4 PMM-008-SCO-030-026 Approve the 30% Design Package for EPC Projects
Procedure: ● For the 30% Design Package, review and approve/reject the package by
following the formal acceptance process described in the Project
Management Plan using:
○ (PMF-008-SCO-040 Design Package Review Release to
Reviewers).
○ (PMF-008-SCO-038 Design Review Guidelines).
○ (PMF-008-SCO-039 Design Packages Elements).
○ Utilize (EPM-KE0-PR-000002 Design Review Procedure) as much
as possible beside the mentioned attachments.
● Send a copy of the submitted 30% Design Package to Value Engineering
department for Value Engineering conducting and feedback.
● After VE study conducting, receive the VE study report.
● Develop a design review report and incorporate the received Value
Engineering Report into it.
● Send the approved 30% design package to NWC Project Manager for
inclusion in RFP.
Procedure: ● After receiving acceptance on 30% design package, update the (PMF-
008-SCO-037 Requirements Traceability Matrix RTM).
● Update the Scope Management Plan Section of Project Management
Plan with updated OPR, selected design option and developed
Conceptual Design (30% design).
Procedure: ● Develop 90% design package utilizing the approved 30% design
package (or 60% design package if contractually stated) and, at least,
the updated:
○ Owner Project Requirements (OPR).
○ Basic Design Data (BDD).
○ Design Basis Report (DBR).
● Perform internal review for the 90% design package using:
○ (PMF-008-SCO-040 Design Package Review Release to
Reviewers).
○ (PMF-008-SCO-038 Design Review Guidelines).
○ (PMF-008-SCO-039 Design Packages Elements).
○ Utilize (EPM-KE0-PR-000002 Design Review Procedure) as much
as possible beside the mentioned attachments.
● Incorporate the internal review comments and develop 90% design
package. The submittal shall include soft and hard copies as per stated
in the contract.
● Send the 90% design package for review and approval to:
○ NWC Project Manager and Cluster Technical Services Director (in
design projects)
○ NWC Project Manager and Supervision Consultant (in Design &
Build projects)
● Update the (PMF-008-SCO-037 Requirements Traceability Matrix RTM).
Design Consultant (in design projects)
Roles: Responsible:
Contractor (in Design & Build projects)
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Cluster Value Engineering Specialist
Value Engineering Director
Design Consultant
Design Consultant
Informed:
NWC Project Manager
Cluster Value Engineering Specialist
Procedure: ● If the 90% design review is the next design review to the 30% design
review that received VE report, forward a copy of the submitted design
package to VE Department to ensure the incorporation of Value
Engineering report recommendations.
● Review the submitted package by following the formal acceptance
process described in the Project Management Plan using:
○ (PMF-008-SCO-040 Design Package Review Release to
Reviewers).
○ (PMF-008-SCO-038 Design Review Guidelines).
○ (PMF-008-SCO-039 Design Packages Elements).
○ Utilize (EPM-KE0-PR-000002 Design Review Procedure) as much
as possible beside the mentioned attachments.
● The Cluster Asset Management & Operation Excellence shall participate
in the review process.
● Develop a design review report.
● Cluster Technical Services Director shall approve/reject the submitted
90% Design Package then send it to Technical Services GM for final
approval.
● Technical Services GM shall approve/reject the submitted 90% Design
Package.
● Cluster Technical Services Director shall send the design review report
to Design Consultant.
Cluster Technical Services Director (in design projects)
Roles: Responsible:
Supervision Consultant (in Design & Build projects)
NWC Project Manager
Technical Services GM
Accountable: NWC Project Manager
Cluster Technical Services Director (in Design & Build
Consulted:
projects)
Cluster Value Engineering Specialist
Value Engineering Director
Design Consultant
Cluster Asset Management & Operation Excellence
Director
Design Consultant
Informed:
Cluster Technical Services Director (in Design & Build
projects)
Guidelines: ● The Complete Design package shall include but not limited to:
○ Design Basis report which includes the design basis for all
disciplines included in the design package
○ Basic Engineering Design Data (BEDD)
○ Design Criteria
○ Drawings
○ Specifications
○ Special studies
Procedure: ● Develop 100% design package utilizing the approved 90% design
package and, at least, the updated:
○ Owner Project Requirements (OPR).
○ Basic Design Data (BDD).
○ Design Basis Report (DBR).
● Perform internal review for the 90% design package using:
○ (PMF-008-SCO-040 Design Package Review Release to
Reviewers).
○ (PMF-008-SCO-038 Design Review Guidelines).
○ (PMF-008-SCO-039 Design Packages Elements).
○ Utilize (EPM-KE0-PR-000002 Design Review Procedure) as much
as possible beside the mentioned attachments.
● Incorporate the internal review comments and develop 100% design
package. The submittal shall include soft and hard copies as per stated
in the contract.
● Send the 90% design package for review and approval to:
○ NWC Project Manager and Cluster Technical Services Director (in
design projects).
○ NWC Project Manager and Supervision Consultant (in Design &
Build projects).
● Update the (PMF-008-SCO-037 Requirements Traceability Matrix RTM).
Design Consultant (in design projects)
Roles: Responsible:
Contractor (in Design & Build projects)
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Cluster Value Engineering Specialist
Value Engineering Director
Design Consultant
Design Consultant
Informed:
NWC Project Manager
Cluster Value Engineering Specialist
Procedure: ● After design completion, update the Project Scope Statement in the
Project Management Plan.
● The Cluster Technical Services Director helps and peer-review the
written definition.
8.3.4 Procedures
8.3.4.1 PMM-008-SCO-040-010 Create Work Breakdown Structure
Procedure: ● Use the applicable WBS template from NWC “Primavera P6” Database.
● Customize the used template to suit the project, in terms of the scope
definition, milestones and deliverables.
● Develop the project Work Breakdown Structure and submit it for
Supervision Consultant and NWC approvals.
● Update the scope section in project management plan by the created
WBS.
1. Changes of the scope definition must be requested formally, accepted by all relevant
stakeholders, and then submitted through (PMM-007-INT-060 Variation Control)
process for business authorization to proceed.
2. Ad hoc scope changes (scope creep) are not allowed and must be prevented.
3. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
8.4.3 Flowchart
Figure 8-6 PMM-008-SCO-050 Control Scope Flowchart
8.4.4 Procedures
8.4.4.1 PMM-008-SCO-050-010 Draft a Scope Change
Procedure: ● Make a clear, written description of the scope change considering the
scope statement in the current Project Management Plan and highlight
proposed changes.
● The following stakeholders are authorized to raise a Variation Request:
○ Cluster Asset Management & Operation Excellence Director
○ Business Unit Construction Director
○ Cluster Technical Services Director
○ NWC Project Manager
○ Design Consultant
○ Supervision Consultant
○ Contractor
Procedure: ● Distribute the new proposed scope statement based on the proposed
changes for initial review and comment of the Engineering Team.
● Engineering team shall review and develop comments.
● Retain a record of all design team comments.
8.4.4.3 PMM-008-SCO-050-030 Perform Impact Analysis for the Draft Scope Change
8.5.4 Procedures
8.5.4.1 PMM-008-SCO-055-010 Pre-design T&C Activities
Procedure: ● Participate in reviewing and approving the following (as applicable in the
project) which prepared by the design consultant and sequentially
submitted for approval.
○ Owner Project Requirements (OPR).
○ Basic Design Data (BDD).
○ Design Basis Report (DBR).
○ 10% design package.
○ 30% design package.
○ 60% design package.
○ 90% design package.
○ 100% design package.
● When Design Consultant inquires about any T&C aspect in the above
mentioned submittals, promptly clarify the inquiry.
● Review and approve the following which prepared and submitted along
with 90% design package:
○ Updated Preliminary T&C Method Statement (with checklists)
○ T&C Items list
○ Updated Preliminary T&C Plan
● Identify if there is a need for any addition T&C SME consultation during
T&C Method Statement development.
● Use (PMF-008-SCO-041 Project Testing & Commissioning Guideline) as
a guideline during Design Stage.
Cluster Testing & Commissioning Section Head
Roles: Responsible:
Cluster Technical Services Director
Testing & Commissioning Director
Testing & Commissioning Consultant
NWC Project Manager
Accountable: Cluster Technical Services Director
Cluster Technical Services Director
Consulted:
Business Unit Construction Director
NWC Project Manager
NWC Project Manager
Informed:
Cluster Technical Services Director
Procedure: ● Continuously updates the T&C Plan and T&C Method Statement during
construction stage, for instance, incorporating the implemented
approved variations Accordingly.
● Complete preparatory works for T&C process. Preparatory work shall
include the following:
○ Signing-off of all Electro-mechanical installation.
○ Labelling and tagging for all electro-mechanical installation.
○ Preparing Lock-out and tag-out and any other HSE procedures and
measures.
○ Preparing all required calculations that proves the resiliency and
correctness of the installation that submitted and approved by the
Supervision Consultant and NWC Project Manager.
● Prepare all documentation and studies that are required for completion
of T&C process. These documentations include but not limited:
Procedure: ● Ensure the completion of preparatory works for T&C process by the
Contractor. Preparatory works are identified in procedure (PMM-008-
SCO-055-040 T&C Preparatory Works and Preparation of T&C
Documentations).
● Ensure that, for all mechanical and electrical equipment, the following
documentation which required for T&C process have been submitted and
approved.
○ Factory Acceptance Testing (FAT) Certificates.
○ Type Testing Certificate (TTC).
● Review and approve all documentations and studies that are required for
completion of T&C process are available. These documentations are
identified in procedure (PMM-008-SCO-055-040 T&C Preparatory
Works and Preparation of T&C Documentations).
● Monitor, review and approve the updates that the Contractor have made
to the OPR, RTM and T&C Plan to incorporate T&C requirements that
identified during activities mentioned in procedure (PMM-008-SCO-055-
040 T&C Preparatory Works and Preparation of T&C Documentations).
● At the end of construction stage, ensure the availability and readiness of
all resources that stated in the T&C Plan and T&C Method Statement to
perform the T&C activities such as potable water, drainage system, and
permanent/stable power. Report any resource lack.
Supervision Consultant
Roles: Responsible:
NWC Project Manager
Accountable: NWC Project Manager
Contractor
Consulted:
Testing & Commissioning Consultant
Testing & Commissioning Director
NWC Project Manager
Contractor
Informed:
Testing & Commissioning Consultant
NWC Project Manager
Procedure: ● Ensure that Contractor has passed all construction tests (site acceptance
tests and site integration tests) for mechanical and electrical installations
prior to conducting the T&C Works by verifying documentations that
proves the conducting and pass. Every unit should have a separate
accepted report using (PMF-008-SCO-043 Unit Test Report).
● Construction tests shall include the following:
○ Mechanical installation pressure testing.
○ Mechanical installation gravity or air testing.
○ Plumbing flow testing.
○ Leakage testing for HVAC ducts.
○ Complete mechanical system installation testing.
○ Electrical wiring continuity and insulation resistance testing.
○ Electrical cold testing.
○ All test for control wiring such as point-to-point testing and loop
testing.
Supervision Consultant
Roles: Responsible:
NWC Project Manager
Accountable: NWC Project Manager
Contractor
Consulted:
Testing & Commissioning Consultant
Testing & Commissioning Director
NWC Project Manager
Contractor
Informed:
Testing & Commissioning Consultant
NWC Project Manager
8.5.4.7 PMM-008-SCO-055-070 Finalize T&C Plan and T&C Method Statement and
Submit for Approval
Procedure: ● Develop finalized version of T&C Plan and T&C Method Statement for
project systems/equipment/interfaces.
● Submit these two submittals to NWC, through the supervision consultant,
for review and approval.
● Use (PMF-008-SCO-041 Project Testing & Commissioning Guideline) as
a guideline during T&C Stage.
Supervision Consultant
Consulted:
Testing & Commissioning Consultant
Testing & Commissioning Director
NWC Project Manager
Supervision Consultant
Informed:
Testing & Commissioning Consultant
NWC Project Manager
8.5.4.8 PMM-008-SCO-055-080 Approve T&C Plan and T&C Method Statement
Procedure: ● Supervision Consultant shall review and endorse the T&C Plan and T&C
Method Statement for project systems/equipment/interfaces that
prepared and submitted by Contractor then transmit the two submittals
to NWC Project Manager for further actions.
● NWC Project Manager shall transmit the two submittals to T&C
Consultant for review and endorsement.
● T&C Consultant shall review and endorse the two submittals then
transmit them back to NWC Project Manager for further actions.
● NWC shall review and endorse the two submittals then transmit them to
T&C Director.
● T&C Director shall review and approve the two submittals then transmit
them back to NWC Project Manager to send them to Contractor.
● During every review, ensure the conformity of these tow submittals to the
adopted codes, standards, and best construction practices.
● Use (PMF-008-SCO-041 Project Testing & Commissioning Guideline) as
a guideline during T&C Stage.
Supervision Consultant
Roles: Responsible:
Testing & Commissioning Consultant
NWC Project Manager
Testing & Commissioning Director
Accountable: NWC Project Manager
Contractor
Consulted:
Cluster Technical Services Director
Business Unit Construction Director
Contractor
Informed:
Cluster Projects GM
Procedure: ● Provide and install field devices that used in T&C activities according to
T&C schedule (part of the T&C plan).
● Confirm that re-certification shall be based on the date of completion of
installation (not on the date of the last test).
● Perform, with equipment suppliers if required, site Pre-Commissioning
Tests (trial runs) to test:
○ Equipment Pre-Start Up or Pre-energization Testing.
○ Functional or Operational testing.
○ Site Equipment Performance Testing.
● Perform, after third fix, tests for all cables in all systems which include
but not limited to:
○ High Voltage
○ Medium Voltage
○ Low Voltage
○ Extra Low Voltage (ELV)
8.5.4.13 PMM-008-SCO-055-130 Issue T&C Working Group Report and T&C Report
3. The Initial Acceptance process including acceptance decision and handing over must
be scheduled in the Project Schedule with sufficient resources and suitable durations.
4. No completed part of project scope shall be initially accepted unless it is verified
through quality control process.
5. No completed part of project scope shall be handed over unless it is initially accepted
through initial acceptance process.
6. If the Contractor does not submit initial acceptance request for not initially accepted
works by the project completion date, the cluster projects GM shall form a committee
to perform inventory on the actual executed and remaining works for further action as
per contract.
7. In case of that initial acceptance committee rejects the initial acceptance request, the
Contractor shall resolve the rejection reasons then resubmit another request.
8. Handing over the initially accepted works to O&M Department must immediately
follow the initial acceptance process. No lag time allowed without formal approval.
9. An initial acceptance committee, which will be formed after the Contractor requests
for initial acceptance, shall comprise at least representatives from the following
functions/departments:
● Cluster Projects Department
● Cluster Operation Excellence department
● Cluster Asset Management department
● Supervision Consultant
● Contractor
● External Subject Matter Expert (if needed).
10. Forming Initial Acceptance Committee shall be approved by:
● Capital Projects & Technical Services VP for:
○ All Treatment Plant Projects.
○ Any other project of a value ≥ 100M SAR.
● Cluster Senior GM for any project < 100M SAR that is not a treatment Plant
project.
11. The contractual “liability and operation” period starts from the Initial Acceptance and
handover date.
12. The final invoice is NOT to be paid to the contractor unless all the snag list items are
rectified.
13. In case the snag list items are awarded to another contractor, the final invoice is NOT
to be paid to the main contractor unless all the new contractor rectifies all snag list
items.
14. The handover process to O&M shall include:
● Ensuring the scope to be handed over is initially accepted.
● Handing over of as built and GIS drawings, O&M manuals and warranty
documents.
- pay all costs for rectifying all defects on project executed works.
d. The commitment letter must be attested by the Chamber of Commerce.
e. Based on the assessment of the Initial Acceptance Committee, the
rectifications on project works needed due to:
- poor contractor execution shall be on the Contractor expense.
- delaying the initial acceptance and handover shall NOT be on Contractor
expense.
f. The Project Bank Guarantee shall be released to Contractor at the end of
the Liability Period.
g. If Contractor does not fulfill to his commitments in paragraph “c”, the following
shall be performed:
- Request from Supply Chain department for tendering to perform tests,
operate the project works or rectify the defects in an independent Contract
to another contractor based on NWC approved policies and procedures.
- Contact the Supply Chain to take formal actions as per NWC Vendor
Relations Procedure.
- Contact the Finance Department to assign a due back charge on the
Contractor to be deducted from his invoices in his other contracts with
NWC if any.
- If Contractor does not pay all required costs or the deduction is not
available, contact the Legal Department to take legal actions against the
contactor.
16. Handover shall be formalized in writing to provide clarity as to when responsibility for
the physical asset transferred.
17. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
8.6.3 Flowchart
Figure 8-8 PMM-008-SCO-060 Initial Acceptance and Handover of Project Scope Flowchart
8.6.4 Procedures
8.6.4.1 PMM-008-SCO-060-010 Receive and Review the Initial Acceptance Request
○ O&M Manuals.
○ Spare Parts list (PMF-008-SCO-006 Spare Parts Record).
○ All Processed Claims.
○ Assets information as per the Assets Registration Manual template.
○ List of all project related:
- Records
- Software Applications
- Databases
- Passwords
● If the Contractor does not submit initial acceptance request by the project
completion date:
○ The cluster projects GM shall form a committee to perform inventory
on the actual executed and remaining works for further action as per
contract.
○ It shall be performed as per procedure (PMM-016-PRO-090-050
Develop a Project Works Inventory and Status Report at the Project
End Date) as part of withdraw process.
NWC Project Manager
Roles: Responsible:
Supervision Consultant
Cluster Projects GM
Accountable: Business Unit Construction Director
Consulted: Contractor
Informed: Contractor
Procedure: ● The NWC Project Manager shall request a representative from but not
limited to the following departments to participate in the Initial
Acceptance Committee:
○ Cluster Projects Department
○ Cluster Operation Excellence department
○ Cluster Asset Management department
○ Contractor
○ Supervision Consultant
○ External Subject Matter Expert (if needed).
● The Cluster Projects GM shall raise a request for initial acceptance
committee forming within 2 days from receiving Contractor request,
mentioning the received nominated persons beside the Contractor
representative and attaching Contractor acceptance request. The NWC
Project Manager is to be designated, in the request, as the committee
coordinator. The request shall be in one of the following forms as per the
case:
○ PMF-008-SCO-015 Initial Acceptance Committee Forming Request
to Cluster
○ PMF-008-SCO-017 Initial Acceptance Committee Forming Request
to HQ
NWC Project Manager
Roles: Responsible:
Cluster Projects GM
Accountable: Cluster Projects GM
Business Unit Construction Director
Consulted:
Cluster Technical Services Director
Cluster Contracts Administration Section Head
Cluster Asset Management & Operation Excellence
Director
Supervision Consultant
Contractor
External Subject Matter Expert (if needed)
Cluster Senior GM
Informed:
Capital Projects & Technical Services VP
Procedure: ● The raised forming request to the Cluster Senior GM is to do one of the
following:
○ raise it to the Capital Projects & Technical Services VP within 2 days
using (PMF-008-SCO-017 Initial Acceptance Committee Forming
Request to HQ) to form the committee for:
- All Treatment Plant Projects
- Any other Projects ≥ 100M SAR.
○ use the form (PMF-008-SCO-015 Initial Acceptance Committee
Forming Request to Cluster) to form the committee within 2 days for
any Project < 100M SAR except treatment Plants.
● If the Capital Projects & Technical Services VP receives the requests, he
shall form the committee within 3 days using the raised forms. He may
add additional committee members as necessary.
Cluster Senior GM / Capital Projects & Technical Services
Roles: Responsible:
VP (as per authority)
Cluster Senior GM / Capital Projects & Technical Services
Accountable:
VP (as per authority)
Cluster Projects GM
Consulted:
Cluster Scheduling & Control Manager
Scheduling & Control GM
Technical Services GM
PMO GM
Cluster Senior GM
Informed:
Cluster Projects GM
Business Unit Construction Director
Initial Acceptance Committee
Procedure: ● After official committee formation, the committee shall conduct a meeting
to review the submitted documents to coordinate the committee
inspection activities.
● Conduct site visits to inspect the completed scope requested for initial
acceptance. Inspection shall include tests as required.
● Initial acceptance inspection shall cover ensuring the completion and
validating of the following:
1. Commissioning approval documents if the project includes
commissioning process.
2. Operation and maintenance manuals of the works that requested
for acceptance are submitted.
3. Assets information as per the Assets Registration Manual
template of the works that requested for acceptance are filled and
submitted.
4. The spare parts, if contractually stated, is handed over to
Operation department using (PMF-008-SCO-006 Spare Parts
Record Template).
5. The training, if contractually stated, is provided to the assigned
Operation individual/team prior to the physical handing over and
accredited certificates are issued to the trained individual/team.
6. The Project IT items. This shall include, if any, project related
software applications, databases, passwords, warranty
documents and insurance documents.
7. The project records such as registers and certificates.
● This procedure shall be completed within 45 days.
Procedure: ● After site visits completion, the committee shall conduct a meeting to
agree on the inspection decision as follows:
1. If the committee monitored deficiencies that prevents the
functional use of the project works, the decision shall be reject the
initial handover. Using (PMF-008-SCO-012 Initial Handover
Rejection), an initial handover rejection report shall be prepared
and attached to the decision letter. The rejection report shall
Supervision Consultant
Consulted:
External Subject Matter Expert (if needed)
Cluster Projects GM
Informed:
Business Unit Construction Director
8.6.4.6 PMM-008-SCO-060-050 Issue Initial Acceptance and Handover Certificate /
Rejection Report / Inventory Report
Procedure: ● All committee members shall sign the prepared Initial Acceptance and
Handover Certificate / Delay Report / Inventory Report.
● The committee coordinator shall raise the signed document to the
Cluster Senior GM for giving 1st approval / final approval (as per
authorization).
● Cluster Senior GM shall do one of the following (as per authorization):
○ Gives final approval on it.
○ Gives 1st approval then raise it to Projects & Technical Services GM
for final approval.
● If Capital Projects & Technical Services VP receives it (as per
authorization), he shall give final approval on it.
● After obtaining approvals:
○ In case of Initial Rejection Decision, issue the rejection report to the
Contractor with a cover letter describes the rejection decision.
○ In case of Initial Acceptance Decision:
- Issue the prepared Initial Acceptance and Handover Certificate
to the Contractor and finance department attaching the snag
list.
- The Contractor shall be granted 60 days to complete all snag
list items. if any item requires more than 60 days for rectification,
the following shall be done during the rectification period:
· Contractor shall request for additional rectification period.
· Based on the Contractor request, the NWC Project
Manager shall raise a request to Scheduling & Control GM
for approval.
- The contractual liability and operation period starts from the
Initial Acceptance date.
○ In case of Inventory report:
- issue the inventory report to the Contractor with a cover letter
describes the case using (PMF-008-SCO-035 Work Inventory
Letter to Contractor Due to Inability for IA&HO Inspection).
- Cluster Projects GM shall request from supply chain assigning
a Contractor to oversee the project executed works and perform
required periodic and preventive maintenance to it.
● This procedure to be completed within 60 days from the Contractor
request submission.
Supervision Consultant
Consulted:
External Subject Matter Expert (if needed)
Cluster Projects GM
Informed:
Business Unit Construction Director
8.6.4.8 PMM-008-SCO-060-056 Actions to Recoup Inability to Handover for More than
Six Months
Procedure: ● If the committee could not perform initial acceptance and handover tests
operate the project works due to reasons out of Contractor’s control and:
○ the Initial Acceptance Committee estimated the duration of
preventing reasons demise more than six months from committee
site visit date.
or
○ the estimated preventing reasons in procedure (PMM-008-SCO-
060-053 Prepare Initial Acceptance and Handover Certificate /
Rejection Report / Inventory Report) exceeded six months.
then:
- issue initial acceptance and handover certificate to the
contractor using (PMF-008-SCO-011 Initial Acceptance and
Handover Certificate)
- Negotiate with the contractor to perform the preventive
maintenance, security and storing of project works and
materials at current market price.
· If an agreement reached, formalize the agreement through
Supply Chain department.
· If the committee does not reach an agreement with the
contractor, request from supply chain for tendering the
preventive maintenance, security and storing of project
works and materials to another contractor via a closed
tender.
- Direct the contractor to submit his final invoice with a
commitment letter to perform, once the preventing reasons
demise, all:
· requirements of testing and operating the project works.
· rectifications due to poor contractor execution.
The commitment letter must be attested by the Chamber of
Commerce.
● NWC Project Manager shall escalate the preventing reasons to Cluster
Projects GM to resolve these issues.
● NWC Project Manager shall keep monitoring the issues resolving to
enable Initial Acceptance and handover.
● Once the preventing reasons demised, direct Contractor to perform his
commitments in his commitment letter.
Procedure: ● If the Contractor does not request for inspecting the snag list fulfilment
within 60 days from the snag list issuance, Cluster Projects GM shall
issue a warning letter to Contractor to complete in 15 days using (PMF-
008-SCO-021 Warning Letter due to Not Request for Inspection for IHO
Snag List Rectification).
Procedure: ● If the Contractor, after 15 days from the warning letter issuance, does
not request for re-inspecting the snag list fulfilment, Cluster Projects GM
shall, within 1 day, request from supply chain assigning another
Contractor to complete the rectification on Contractor expense. The
request shall be attached by:
○ Detailed description for the snag list items (suitable for tendering).
○ Initial Acceptance and Handover Certificate.
○ Warning Letter to Contractor.
● After receiving the selected bid price from supply chain, submit to
Finance department the following to create budget allocation number:
○ The price that selected by Supply Chain.
○ The final invoice including a deduction equals to the cost of the
selected price.
○ Initial Acceptance and Handover Certificate.
● After receiving budget allocation number from Finance department,
prepare the Purchase Requisition (PR) attaching (PMF-016-PRO-005
PR Approval Form) to reserve the project budget.
● Raise the Purchase Requisition (PR) to Supply Chain for issuing a PO to
the new contractor.
Procedure: ● If the Contractor requests to re-inspect the Snag list fulfilment within (60
days from the snag list issuance) or (15 days form the warning letter):
○ the project manager shall coordinate to conduct a site visit to
perform the requested inspection.
○ The Initial Acceptance Committee shall complete the inspection
within 7 days from the Contractor snag inspection request.
● Update the snag list by accepting the rectified snag list items then send
a copy to the Contractor.
Consulted: Contractor
Contractor
Informed:
Cluster Projects GM
Business Unit Construction Director
Cluster Asset Management & Operation Excellence
Director
Finance Department
8.6.4.12 PMM-008-SCO-060-063 Issue Warning Letter Due to Incomplete Snag List
Rectification
Procedure: ● After completing the site visits of inspecting snag list fulfilment, if the
inspection found that, not all deficiencies are rectified, the cluster projects
GM shall issue a warning letter to Contractor to complete the rectification
within 15 days using (PMF-008-SCO-031 Warning Letter due to
Incomplete IA&HO Snag List Rectification).
Procedure: ● After 15 days form the warning letter, the project manager shall
coordinate to conduct a site visit to perform inspection.
● Initial Acceptance Committee shall complete the re-inspection within 7
days from the inspection date that stated in the warning letter.
● After completing the site visits of re-inspecting snag list fulfilment:
○ if the inspection found that, all deficiencies are rectified, update the
snag list by accepting the rectified snag list items then send a copy
to the Contractor.
○ if the inspection found that, not all deficiencies are rectified, Cluster
Projects GM shall, within 1 day, request from supply chain assigning
another Contractor to complete the rectification on Contractor
expense at current market price.
Initial Acceptance Committee
Roles: Responsible:
Cluster Projects GM
Accountable: Cluster Projects GM
Procedure: ● After rectifying the outstanding snag list items at Contractor expense and
receiving a request to inspect the outstanding deficiencies list fulfilment,
the NWC Project Manager shall coordinate to conduct a site visit to
perform the requested inspection.
● Conduct a site visit and inspect the snag list fulfilment. Inspection shall
include tests as required. The inspection is to be completed within 7 days
from the other Contractor snag inspection request.
● After site visits completion and ensuring the outstanding deficiencies
fulfilment, the snag list shall be closed and a closing notification shall be
issued to Contractor to proceed with final invoice submission within 3
days.
11. The contractual “liability and operation” period starts from the Initial Acceptance and
handover date.
12. The handover process to O&M shall include:
● Ensuring the scope to be handed over is initially accepted.
● Handing over of as built and GIS drawings, O&M manuals and warranty
documents.
● Physical handing over of the completed project works.
● Handing over of project records such as registers and certificates.
● Handing over project related software applications, databases and passwords.
● Handing over of spare parts and include them in one list.
● Training of operational staff.
● Handing over of keys.
● Addressing defects (if any) and its warranties.
● Undertaking contractual liability and operation period by Contractor.
● Assets information as per Assets Registration Manual template (from Asset
Management department).
13. If the committee could not perform acceptance and handover tests and operate the
project works due to reasons out of Contractor’s control, works shall remain under
contractor custody till the project end. If then reasons are not demised, policy 13 in
the process (PMM-008-SCO-060 Total Initial Acceptance and Handover of Project
Scope).
14. Handover shall be formalized in writing to provide clarity as to when responsibility for
the physical asset transferred.
15. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
8.7.3 Flowchart
Figure 8-9 PMM-008-SCO-065 Initial Acceptance and Handover of Project Scope Flowchart
8.7.4 Procedures
8.7.4.1 PMM-008-SCO-065-010 Receive and Review the Partial Initial Acceptance
Request
Procedure: ● Receive the Partial Initial Acceptance Request from Contractor (PMF-
008-SCO-027 Contractor Partial Initial Acceptance Request).
● Ensure with the Supervision Consultant that, the Contractor has stated
in the request that:
○ The clear identification of the scope that requested for acceptance
(whole scope / part of the scope) described as per BoQ description.
○ The completion of the scope that requested for acceptance.
○ The scope that requested for acceptance is quality controlled.
○ The availability of technicians and labors required for the inspection.
○ The Contractor representative for the Partial Initial Acceptance
Committee.
● Check the completion of the request attachments which must include but
not limited to the following:
○ Project Contract including all approved variation orders.
Consulted: Contractor
Informed: Contractor
Procedure: ● The NWC Project Manager shall request a representative from but not
limited to the following departments to participate in the Partial Initial
Acceptance Committee:
○ Cluster Projects Department
○ Cluster Operation Excellence department
○ Cluster Asset Management department
○ Contractor
○ Supervision Consultant
○ External Subject Matter Expert (if needed).
● The Cluster Projects GM shall raise a request for Partial Initial
Acceptance Committee forming within 2 days from receiving Contractor
request, mentioning the received nominated persons beside the
Contractor representative and attaching Contractor acceptance request.
The NWC Project Manager is to be designated, in the request, as the
committee coordinator. The request shall be in one of the following forms
as per the case:
○ PMF-008-SCO-025 Partial Initial Acceptance Committee Forming
Request to Cluster
○ PMF-008-SCO-026 Partial Initial Acceptance Committee Forming
Request to HQ
NWC Project Manager
Roles: Responsible:
Cluster Projects GM
Accountable: Cluster Projects GM
Business Unit Construction Director
Consulted:
Cluster Technical Services Director
Cluster Contracts Administration Section Head
Cluster Asset Management & Operation Excellence
Director
Supervision Consultant
Contractor
External Subject Matter Expert (if needed)
Cluster Senior GM
Informed:
Capital Projects & Technical Services VP
Procedure: ● The raised forming request to the Cluster Senior GM is to do one of the
following:
○ raise it to the Capital Projects & Technical Services VP within 2 days
using (PMF-008-SCO-026 Partial Initial Acceptance Committee
Forming Request to HQ) to form the committee for:
- All Treatment Plant Projects
- Any other Projects ≥ 100M SAR.
○ use the form (PMF-008-SCO-025 Partial Initial Acceptance
Committee Forming Request to Cluster) to form the committee
within 2 days for any Project < 100M SAR except treatment Plants.
● If the Capital Projects & Technical Services VP receives the requests, he
shall form the committee within 3 days using the raised forms. He may
add additional committee members as necessary.
Cluster Senior GM / Capital Projects & Technical Services
Roles: Responsible:
VP (as per authority)
Cluster Senior GM / Capital Projects & Technical Services
Accountable:
VP (as per authority)
Cluster Projects GM
Consulted:
Cluster Scheduling & Control Manager
Scheduling & Control GM
Technical Services GM
PMO GM
Cluster Senior GM
Informed:
Cluster Projects GM
Business Unit Construction Director
Partial Initial Acceptance Committee
Procedure: ● After official committee formation, the committee shall conduct a meeting
to review the submitted documents to coordinate the committee
inspection activities.
● Conduct site visits to inspect the completed scope requested for partial
initial acceptance. Inspection shall include tests as required.
● Partial initial acceptance inspection shall cover ensuring the completion
and validating of the following:
1. Commissioning approval documents if the project includes
commissioning process.
2. Operation and maintenance manuals of the works that requested
for acceptance are submitted.
3. Assets information as per the Assets Registration Manual
template of the works that requested for acceptance are filled and
submitted.
4. The spare parts, if contractually stated, is handed over to
Operation department using (PMF-008-SCO-006 Spare Parts
Record Template).
5. The training, if contractually stated, is provided to the assigned
Operation individual/team prior to the physical handing over and
accredited certificates are issued to the trained individual/team.
6. The Project IT items. This shall include, if any, project related
software applications, databases, passwords, warranty
documents and insurance documents.
7. The project records such as registers and certificates.
● This procedure shall be completed within 45 days.
Procedure: ● After site visits completion, the committee shall conduct a meeting to
agree on the inspection decision as follows:
1. If the committee monitored deficiencies that prevents the
functional use of the project works, the decision shall be reject the
initial handover. Using (PMF-008-SCO-024 Partial Initial
Handover Rejection), an initial handover rejection report shall be
prepared and attached to the decision letter. The rejection report
Procedure: ● All committee members shall sign the prepared Initial Acceptance and
Handover Certificate / Rejection Report / Inventory Report.
● The committee coordinator shall raise the signed document to the
Cluster Senior GM for giving 1st approval / final approval (as per
authorization).
● Cluster Senior GM shall do one of the following (as per authorization):
○ Gives final approval on it.
○ Gives 1st approval then raise it to Projects & Technical Services GM
for final approval.
● If Capital Projects & Technical Services VP receives it (as per
authorization), he shall give final approval on it.
● After obtaining approvals:
○ In case of Initial Rejection Decision, issue the rejection report to the
Contractor with a cover letter describes the rejection decision.
○ In case of Initial Acceptance Decision:
- Issue the prepared Initial Acceptance and Handover Certificate
to the Contractor and finance department attaching the snag
list.
- The Contractor shall be granted 60 days to complete all snag
list items. if any item requires more than 60 days for rectification,
the following shall be done during the rectification period:
· Contractor shall request for additional rectification period.
· Based on the Contractor request, the NWC Project
Manager shall raise a request to Scheduling & Control GM
for approval.
- The contractual liability and operation period starts from the
Initial Acceptance date.
○ In case of Inventory report:
- issue the inventory report to the Contractor with a cover letter
describes the case using (PMF-008-SCO-035 Work Inventory
Letter to Contractor Due to Inability for IA&HO Inspection).
● This procedure to be completed within 60 days from the Contractor
request submission.
Partial Initial Acceptance Committee
Roles: Responsible:
Cluster Senior GM
Capital Projects & Technical Services VP
Cluster Senior GM / Capital Projects & Technical Services
Accountable:
VP (as per authority)
Consulted: Cluster Contracts Administration Section Head
Contractor
Informed:
Cluster Senior GM
Cluster Projects GM
Business Unit Construction Director
Cluster Asset Management & Operation Excellence
Director
8.7.4.7 PMM-008-SCO-065-058 Issue Warning Letter Due to Not Request for
Inspection for Snag List Rectification
Procedure: ● If the Contractor does not request for inspecting the snag list fulfilment
within 60 days from the snag list issuance, Cluster Projects GM shall
issue a warning letter to Contractor to complete in 15 days using (PMF-
008-SCO-021 Warning Letter due to Not Request for Inspection for IHO
Snag List Rectification).
● If the Contractor, after 15 days from the warning letter issuance, does
not request for re-inspecting the snag list fulfilment, Cluster Projects GM
shall, within 1 day, request from supply chain assigning another
Contractor to complete the rectification on Contractor expense.
Procedure: ● If the Contractor, after 15 days from the warning letter issuance, does
not request for re-inspecting the snag list fulfilment, Cluster Projects GM
shall, within 1 day, request from supply chain assigning another
Contractor to complete the rectification on Contractor expense. The
request shall be attached by:
○ Detailed description for the snag list items (suitable for tendering).
○ Initial Acceptance and Handover Certificate.
○ Warning Letter to Contractor.
● After receiving the selected bid price from supply chain, submit to
Finance department the following to create budget allocation number:
○ The price that selected by Supply Chain.
○ The final invoice including a deduction equals to the cost of the
selected price.
○ Initial Acceptance and Handover Certificate.
● After receiving budget allocation number from Finance department,
prepare the Purchase Requisition (PR) attaching (PMF-016-PRO-005
PR Approval Form) to reserve the project budget.
● Raise the Purchase Requisition (PR) to Supply Chain for issuing a PO to
the new contractor.
Procedure: ● If the Contractor requests to re-inspect the Snag list fulfilment within (60
days from the snag list issuance) or (15 days form the warning letter):
○ the project manager shall coordinate to conduct a site visit to
perform the requested inspection.
○ The Partial Initial Acceptance Committee shall complete the
inspection within 7 days from the Contractor snag inspection
request.
● Update the snag list by accepting the rectified snag list items then send
a copy to the Contractor.
Consulted: Contractor
Contractor
Informed:
Cluster Projects GM
Business Unit Construction Director
Cluster Asset Management & Operation Excellence
Director
Finance Department
8.7.4.10 PMM-008-SCO-065-063 Issue Warning Letter Due to Incomplete Snag List
Rectification
Procedure: ● After completing the site visits of inspecting snag list fulfilment, if the
inspection found that, not all deficiencies are rectified, the cluster projects
GM shall issue a warning letter to Contractor to complete the rectification
within 15 days using (PMF-008-SCO-031 Warning Letter due to
Incomplete IA&HO Snag List Rectification).
Procedure: ● After 15 days form the warning letter, the project manager shall
coordinate to conduct a site visit to perform inspection.
● Partial Initial Acceptance Committee shall complete the re-inspection
within 7 days from the inspection date that stated in the warning letter.
● After completing the site visits of re-inspecting snag list fulfilment:
○ if the inspection found that, all deficiencies are rectified, update the
snag list by accepting the rectified snag list items then send a copy
to the Contractor.
○ if the inspection found that, not all deficiencies are rectified, Cluster
Projects GM shall, within 1 day, request from supply chain assigning
another Contractor to complete the rectification on Contractor
expense
Partial Initial Acceptance Committee
Roles: Responsible:
Cluster Projects GM
Procedure: ● After rectifying the outstanding snag list items at Contractor expense and
receiving a request to inspect the outstanding deficiencies list fulfilment,
the NWC Project Manager shall coordinate to conduct a site visit to
perform the requested inspection.
● Conduct a site visit and inspect the snag list fulfilment. Inspection shall
include tests as required. The inspection is to be completed within 7 days
from the other Contractor snag inspection request.
● After site visits completion and ensuring the outstanding deficiencies
fulfilment, the snag list shall be closed and a closing notification shall be
issued to Contractor to proceed with final invoice submission within 3
days.
8.8.3 Flowchart
Figure 8-10 PMM-008-SCO-070 Final Acceptance of Project Scope Flowchart
8.8.4 Procedures
8.8.4.1 PMM-008-SCO-070-010 Receive and Review the Final Acceptance Request
Procedure: ● Receive the final acceptance request from Contractor after the
contractual liability and operation period finish.
● Ensure the Contractor has stated in the request that:
○ The clear identification of the scope part that requested for
acceptance (Whole Scope / Section of the scope).
○ The requested scope was initially accepted.
○ The availability of technicians and labors required for the inspection.
○ The Contractor representative for the Final Acceptance Committee.
● Check the completion of the request attachments which must include but
not limited to the following:
○ Initial acceptance certificate.
○ Snag list closing notification.
○ Project Contract including approved Variation Orders documents.
○ Contractor(s) Clearance Certificate(s) from relevant stakeholders.
● If the contractor does not submit a Final Handover Request when it is
due, NWC Project Manager shall officially inform the contractor to submit
his nominees for the Final Handover Committee stating a deadline for
the contractor response. Whether the contractor respond or not by the
stated deadline, NWC Project Manager shall proceed to the next
procedure.
Consulted: Contractor
Informed: Contractor
8.8.4.2 PMM-008-SCO-070-010 Issue Warning Letter due to Not Request for Final
Acceptance and Handover
Procedure: ● If the Contractor does not request for Final Acceptance and Handover by
the liability period end date, Cluster Projects GM shall issue a warning
letter to Contractor to submit the request within 15 days using (PMF-008-
SCO-046 Warning Letter due to Not Request for FA&HO).
● If the Contractor, after 15 days from the warning letter issuance, does
not request for Final Acceptance and Handover, proceed in Final
Acceptance and Handover process by performing procedure (PMM-008-
SCO-070-020 Request Forming a Final Acceptance Committee) without
contractor participation.
Procedure: ● The NWC Project Manager request a representative from but not limited
to the following departments to participate in the Final Acceptance
Committee:
○ Projects & Technical Services department.
○ Business Unit Projects Department.
○ Cluster Project Contract Department.
○ Cluster Asset Management & Operation Excellence Department.
○ External Subject Matter Expert (if needed).
● Cluster Projects GM shall raise a request to the Cluster Senior GM for
final acceptance committee forming within 5 days from receiving
Contractor request, including the received nominated persons beside the
Contractor representative and attaching Contractor final acceptance
request. The NWC Project Manager is to be designated, in the request,
as the committee coordinator.
NWC Project Manager
Roles: Responsible:
Cluster Projects GM
Accountable: Cluster Projects GM
Business Unit Construction Director
Consulted:
Cluster Technical Services Director
Cluster Contracts Administration Section Head
Cluster Asset Management & Operation Excellence
Director
Supervision Consultant
Contractor
External Subject Matter Expert (if needed)
Informed: Cluster Senior GM
Procedure: ● The Cluster Senior GM shall approve the committee formation within 7
days using (PMF-008-SCO-016 Final Acceptance Committee Forming
Request).
Procedure: ● After official committee formation, the committee shall conduct a meeting
to review the submitted documents to coordinate the committee
inspection activities.
● Conduct site visits to inspect the scope requested for final acceptance to
perform inspection and ensure that there are no deficiencies. Inspection
shall include tests as required.
● The inspection is to be completed within 14 days.
Procedure: ● After site visits completion, the committee shall conduct a meeting to
agree on the inspection decision.
○ If any deficiency found, the decision shall be postponing the final
acceptance. The committee shall prepare and issue to Contractor a
snag list within 7 days from inspection completion using (PMF-008-
SCO-008 Snag List Template). The list must clearly describe the
deficiencies. Contractor shall be granted 28 days for rectifying the
outstanding deficiencies then send a re-inspection request.
○ If no deficiencies monitored and the functional use of the
project fully achieved, perform (PMM-008-SCO-070-043 Issue
Final Acceptance and Handover Report).
Roles: Responsible: Final Acceptance Committee
Contractor
Informed:
Cluster Senior GM
Cluster Projects GM
Business Unit Construction Director
Cluster Asset Management & Operation Excellence
Director
8.8.4.7 PMM-008-SCO-070-046 Issue Warning Letter due to Not Request for
Inspection for Snag List Rectification
Procedure: ● If the Contractor does not request for inspecting the snag list fulfilment
within 28 days from the snag list issuance, Cluster Projects GM shall
issue a warning letter to Contractor to complete in 15 days using (PMF-
008-SCO-022 Warning Letter due to Not Request for Inspection for FHO
Snag List Rectification).
● If the Contractor, after 15 days from the warning letter issuance, does
not request for re-inspecting the snag list fulfilment, Cluster Projects GM
shall, within 1 day, request from supply chain assigning another
Contractor to complete the rectification on Contractor expense.
Procedure: ● If Contractor requests to re-inspect the Snag list fulfilment within (28 days
from the snag list issuance) or (15 days form the warning letter):
○ the project manager shall coordinate to conduct a site visit to
perform the requested inspection.
○ The final Acceptance Committee shall complete the inspection
within 7 days from the Contractor snag inspection request.
8.8.4.9 PMM-008-SCO-070-053 Issue Warning Letter due to Not Complete Snag List
Rectification
Procedure: ● After site visits completion, the committee shall conduct a meeting to
agree on the inspection decision.
○ If the inspection found that, some or all snag list items are not
rectified:
- The decision shall be:
· Updating the snag list.
· Issuing a warning letter to Contractor to rectify within 15
days using (PMF-008-SCO-032 Warning Letter due to
Incomplete FA&HO Snag List Rectification).
- The snag list updating and warning letter issuance are to be
completed within 2 days.
○ If no deficiencies monitored and the functional use of the project fully
achieved, perform (PMM-008-SCO-070-043 Issue Final Acceptance
and Handover Report).
Roles: Responsible: Cluster Projects GM
Procedure: ● After 15 days form the warning letter, the project manager shall
coordinate to conduct a site visit to perform inspection.
● Final Acceptance Committee shall complete the re-inspection within 7
days from the inspection date that stated in the warning letter.
● After completing the site visits of re-inspecting snag list fulfilment, if the
inspection found that, not all deficiencies are rectified, Cluster Projects
GM shall, within 1 day, request from supply chain assigning another
Contractor to complete the rectification on Contractor expense.
Final Acceptance Committee
Roles: Responsible:
Cluster Projects GM
Accountable: Cluster Projects GM
Cluster Asset Management & Operation Excellence
Consulted:
Director
Cluster Projects GM
Informed:
Business Unit Construction Director
Procedure: ● After rectifying the outstanding snag list items at Contractor expense and
receiving a request to inspect the outstanding snag list fulfilment, the
committee shall coordinate to conduct a site visit to perform the
requested inspection.
● Conduct a site visit and inspect the snag list fulfilment. Inspection shall
include tests as required. The inspection is to be completed within 7 days
from the other Contractor snag inspection request.
● After site visits completion and ensuring the snag list fulfilment and the
functional use of the project existence, the committee shall conduct a
meeting to agree on closing the snag list, accepting the final acceptance
decision and preparing the final acceptance certificate.
Procedure: ● In the meeting conducted by the committee after the site visits completion
to agree on the inspection decision, if no deficiencies monitored and the
functional use of the project fully achieved:
○ Ensure that, the Contractor has archived and handed over all project
documents.
○ The decision will be acceptance and a final acceptance certificate
shall be prepared within 2 days using (PMF-008-SCO-013 Final
Acceptance Certificate).
○ Cluster Senior GM shall approve and issue the final acceptance and
Handover certificate to Contractor within 3 days.
● NWC Project Manager shall notify related stakeholder and proceed with
project closure.
Final Acceptance Committee
Roles: Responsible:
Cluster Senior GM
NWC Project Manager
Accountable: Cluster Senior GM
Contractor
Informed:
Cluster Senior GM
Cluster Projects GM
Business Unit Construction Director
Cluster Asset Management & Operation Excellence
Director
Cluster Supply Chain Manager
8.9 Key Performance Indicators (KPIs)
The table below identifies the KPIs of Project Scope Management. The NWC Project Manager is
responsible to measure and report these KPIs at each KPI stated frequency. The current status of
each KPI is to be reflected in the monthly project progress report.
For further details refer to (PMF-006-GOV-015 KPI Report).
Year-to-date number of
projects that tendered
NOT as per the following
criteria in the cluster:
Design detail level - tender with design 30%
1 Monthly 0 NA >0
for tendering for design & build
projects.
- tender with design
100% for construction
projects.
Year-to-date number of
projects in the cluster
that initially handed over
2 T&C report without a T&C report Monthly 0 NA >0
with “acceptance” or
“acceptance with
comments”.
Year-to-date number of
projects that its initial
Duration for acceptance committee
combining an initial has been combined in
3 acceptance more than 4/7 calendar Monthly 0 3 >3
committee at days (as per authority)
cluster from contractor initial
acceptance request
submission date.
Year-to-date number of
projects that its initial
acceptance committee
Duration for initial
has responded after
acceptance
4 more than 60 calendar Monthly 0 3 >3
committee
days from contractor
response
initial acceptance
request submission
date.
Year-to-date number of
projects that its final
Duration for
acceptance committee
combining a final
has been combined in
5 acceptance Monthly 0 3 >3
more than 12/27
committee at
calendar days (as per
cluster
case) from liability
period end date.
Year-to-date number of
projects that its final
acceptance committee
Duration for final
has performed the
6 acceptance Monthly 0 3 >3
inspection in more than
inspection
14 calendar days from
committee formation
date.
8.10 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-008-
SCO Project Scope Management).
PMF-008-SCO-021 Warning Letter due to Not Request for Inspection for IA&HO Snag List
Rectification
PMF-008-SCO-022 Warning Letter due to Not Request for Inspection for FA&HO Snag List
Rectification
PMF-008-SCO-035 Work Inventory Letter to Contractor Due to Inability for IA&HO Inspection
PMF-008-SCO-047 Design Submittals in EPC Projects after Award and before 90% Design
Package
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The Value Engineering guidelines from 9.1 to 9.6 are revised.
● The second bullet of the criteria of selecting a project for Value Engineering is
revised.
Change
● The process “PMM-009-VEN-010 Plan and Prepare for Value Engineering Study”
Description
is revised.
● The process “PMM-009-VEN-020 Conduct Value Engineering Study” is revised.
● The process “PMM-009-VEN-040 Monitor and Control Value Improvement” is
revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020
Abdullah M. Albani
01 Walid Eldakhs
Change
● First version developed by PARSONS as a standalone document.
Description
Figure 9-1 Value Engineering Effect on Cost vs Time and Saving vs Time
Furthermore, during construction, a Contractor may submit Value Engineering (Variation Proposals)
alternatives to reduce cost, schedule, or present alternative methods of construction, without
reducing performance or quality. In this case, the NWC project manager and the Supervision
Consultant shall evaluate the proposed alternatives and process it as a variation. If accepted, it
shall be processed through (PMM-007-INT-060 Variation Control) process.
9.5 Value Engineering Study Team
Value Engineering studies are typically performed by specialized experienced multi-disciplinary
team and lead by a Certified Value Specialist (CVS®) or by a Value Engineering expert that certified
in Value Engineering facilitation and participated in VE sessions. The size and composition of the
team is project or program dependent. The members should represent a diverse background that
incorporates relevant knowledge, expertise and experience required to cover the issues and
objectives of the project or program. Typically, these include technical design, operation and
maintenance, cost estimation, procurement, material, construction, and quality.
9.6 Value Engineering Study Process
A Value Engineering Study uses a systematic methodology, known as Value Methodology. The
methodology outlines specific steps to effectively analyze the functions of a project or a program in
order to generate value alternatives to achieve or exceed the project or program’s functional or
performance requirements without additional cost.
Internationally recognized Value Methodology follows eight phases Job Plan, prescribed by SAVE
International (Appendix C of The Value Methodology Standard Reference). These phases are:
1. Preparation Phase – A pre-study meeting is held to identify the VM study subject, goals
and objectives, participants, schedule, information, and logistics.
2. Information Phase – The VM study team reviews the study subject’s scope, schedule,
cost, performance, quality, and risk. Various modeling techniques are applied to develop
an understanding of this information.
3. Function Analysis Phase – The VM study team defines the project functions using a two-
word abridgement. The VM study team reviews and analyzes these functions, using
recognized techniques such as random function identification, FAST diagrams, function
resource allocation, and function performance specification to define functions, allocate
performance and resources, and select functions for value improvement.
4. Creativity Phase – The VM study team employs creativity techniques to generate ideas to
perform the subject’s function(s).
5. Evaluation Phase – The VM study team follows a structured evaluation process to select
those ideas that offer the greatest potential for value improvement while delivering the
project’s function(s) considering performance, quality, schedule, cost, and risk.
6. Development Phase – The VM study team develops the selected ideas into VM proposals
with enough documentation to allow decision makers to determine if they should be
implemented.
7. Presentation Phase – The VM facilitator develops a report and/or presentation that
documents and conveys the conclusions and results of the VM study.
8. Implementation Phase – The sponsoring organization reviews the results of the VM study
and decides which VM proposals to implement. An implementation plan is developed and
executed in order to actualize the value improvements.
Steps 2 to 7 are known as six-step value engineering job plan.
9.6.1 Plan and Prepare for Value Engineering Study: Pre-Study Activities
9.6.1.1 Selection Criteria for a Value Engineering Study
Typically, one or more of the following criteria can be used to select a project for a Value
Engineering Study:
● Unclear scope and deliverables
● Technically complex design
● Environmental risks
● Engineering risks
● Construction risks
● Estimated cost high
● Multiple integration points
● Budgetary and schedule constraints
● Geotechnical risks
● Use of new technology or new construction methods
● Political risks (multiple stakeholders with high expectations)
● Demonstrate “Value for Money” decision
NWC has selected the criteria described in “9.2 What is Value Engineering?”
Engineering Study. This is especially important for strategic and critical projects or
programs and to manage HQ Value Engineering study schedule and workload.
9.6.1.6 Determine Performance Criteria
The following criteria can be used to evaluate value alternatives and their relative
importance.
The performance criteria may be adjusted for a specific study:
● Achieves Strategic Objectives (e.g. Vision 2030)
● Performance Reliability
● Ease of Operation and Maintenance
● Financial Viability (both capital and life cycle)
● Constructability
● Flexibility or Future Adaptability
● Environmental Impact
● Sustainability
9.6.2 Conduct Value Engineering Study
9.6.2.1 Value Engineering Study Workshop
9.6.2.1.1 The workshop shall be conducted with the attendance of:
● Project or Program Manager
● Value Engineering division representatives
● Relevant technical disciplinary experts
● Cost analyst
● Technical Services Dept. reps.
● Relevant Cluster reps
● Operation Excellence reps.
● Asset Management Reps.
● Technical Services Dept. reps.
● Design Consultant
● Important Stakeholders
9.6.2.1.2 The Value Engineering Study workshop shall include the following
phased activities:
1. Information Phase:
In this phase, the Engineering and the Value Engineering team
spend time on the following:
● Program/Project overview
● Business objectives or desired outcome
● Review of gathered data and relevant details
The high-level process map for Project Value Engineering is illustrated below in Figure 9-5:
9.7.2 Procedures
9.7.2.1 PMM-009-VEN-010-010 Schedule Value Engineering Study
Procedure: ● The Value Engineering Director shall, in coordination with the Cluster
Value Engineering Specialist, schedule the Value Engineering
study/workshop after receiving Value Engineering Study Request (PMF-
009-VEN-007 Value Engineering Study Request Form) from the NWC
Project Manager.
● The Value Engineering Director shall use the (PMF-009-VEN-008 Value
Engineering Team Roadmap) as a guide in schedule preparation.
● Value Engineering is focused on the early stages of design (30% design
reviews).
● Any Value Engineering required in next stages will be Conditional.
9.8.1 Flowchart
Figure 9-5 PMM-009-VEN-020 Conduct Value Engineering Study Flowchart
9.8.2 Procedures
9.8.2.1 PMM-009-VEN-020-010 Distribute Design Review Package to Value
Engineering Team Members
Procedure: ● For Transmission Line Projects above 30M SAR and Treatment Plant
Projects, the value engineering workshop shall be led by HQ. Other
projects shall be led by Cluster.
● The following forms/guidelines shall be used during the workshop:
○ (PMF-009-VEN-001 Alternative Template Example)
○ (PMF-009-VEN-003 Functions List Example)
○ (PMF-009-VEN-004 Risks Elements Checklist)
○ (PMF-009-VEN-005 Value Engineering Agenda Sample)
● This approach shall follow the internationally recognized six step Job
Plan of Value Methodology as prescribed by SAVE International and
accredited by Value Analysis Canada:
1. Information Phase (~ 4-6 hours)
2. Function Analysis Phase includes Value Target Functions (~ 2-4
hours)
3. Creative Phase (4 hours)
4. Evaluation Phase (4 hours)
5. Development Phase (16 hours)
6. Presentation Phase (2-4 hours)
● Invite the following list to participate in the workshop:
○ HQ:
- Value Engineering Dept. Reps.
- Technical Services Dept. Reps.
○ Cluster:
- Value Engineering Dept. Reps.
- Operation Excellence Reps.
- Asset Management Reps.
- Technical Services Dept. Reps.
- Projects Scheduling & Control Dept. Reps.
- Environmental Compliance Dept. Reps.
- PMO Dept. Reps.
- NWC Project Manager
- Design Consultant
- Contractor (for Design & Build projects)
● Conduct the workshop following the Job Plan.
● During workshop, use:
○ (PMF-009-VEN-018 Value Engineering Study Functions List)
○ (PMF-009-VEN-016 Value Engineering Study Creativity List)
○ (PMF-009-VEN-017 Value Engineering Study Evaluation List)
○ (PMF-009-VEN-012 Value Engineering Development Sheet)
Value Engineering Team Lead
Roles: Responsible:
Value Engineering Team
Accountable: Value Engineering Director
Cluster Projects GM
Consulted:
Cluster Technical Services Director
Procedure: ● The Cluster Value Engineering Specialist shall review and give first
approval on the Value Engineering Study Recommendation Report.
● The Value Engineering Director shall review and give second approval
on the Value Engineering Study Recommendation Report.
● The Technical Services GM shall give final approval on the Value
Engineering Study Recommendations.
Cluster Value Engineering Specialist
Roles: Responsible:
Value Engineering Director
Technical Services GM
Accountable: Technical Services GM
NWC Project Manager
Consulted:
Cluster Technical Services Director
Design Consultant
Cluster Cost Estimation Specialist
NWC Project Manager
Informed:
Cluster Value Engineering Specialist
Cluster Technical Services Director
Design Consultant
9.8.2.5 PMM-009-VEN-020-050 Issue Approved Value Engineering Study
Recommendations with the Design Review Comments
9.9.2 Procedures
9.9.2.1 PMM-009-VEN-030-010 Incorporate the Value Engineering Study Approved
Recommendations into the Design
9.10.2 Procedures
9.10.2.1 PMM-009-VEN-040-010 Review Implementation of the Value Engineering
Study Recommendations through the next Design Review
Procedure: ● Receive the Value Engineering implementation report submitted with the
next design review package.
● Review drawings and specifications to ensure implementation of the
Value Engineering Study recommendations.
● If the implementation is not satisfactory, report that in the design review
package response.
Procedure: ● Monitor and calculate actual value improvement results and cost
savings.
Cluster Value Engineering Specialist
Roles: Responsible:
Supervision Consultant
Accountable: NWC Project Manager
Cluster Cost Estimation Specialist
Consulted:
Value Engineering Director
Cluster Technical Services Director
Contractor
Value Engineering Director
Informed:
Cluster Technical Services Director
Technical Services GM
Procedure: ● Update the Value Engineering database with the implemented Value
Engineering ideas and its actual results/lessons learned.
● Publish the updated Value Engineering database to clusters and
Technical Services GM to be considered for current and future projects.
● Forward applicable lessons learned to the Continuous Improvement
Lead.
Number/year of projects
fulfill the criteria of
Value Engineering selecting a project for
1 before award for Value Engineering and Monthly 0 projects NA >0
construction awarded to contactors
without Value
Engineering.
Year-to-date number of
missing or overdue
Timely Value Value Engineering
2 Engineering workshop reports in the Monthly 1 2 >2
workshop reports cluster against the
agreed schedule of
workshops
9.12 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-009-
VEN Project Value Engineering).
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The table “Schedule Levels Layout Over a Project Life Cycle” is elaborated.
● The process “PMM-010-SCH-010 Plan Project Schedule Management” is
elaborated.
● The process “PMM-010-SCH-015 Schedule Management for Initial Planning” is
added.
Change
Description ● The process “PMM-010-SCH-020 Schedule Management for Procurement” is
revised.
● The process “PMM-010-SCH-030 Schedule Management for Design” is revised.
● The process “PMM-010-SCH-040 Schedule Management for Construction, Testing
& Commissioning and Handover” is revised.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This section is developed as an update to “Schedule” section in first version the Project
Management Manual (PMM) which developed by Faithful + Gould. The following are
the changes:
● Creating Guideline table for schedule levels.
● Adding process for plan schedule management.
● Adding guidelines for the following:
○ Developing level 1 schedule
○ Developing Level 2 schedule
○ Schedule updating
○ Developing and reviewing level 3 schedule
○ Activity weighting
○ Progress curves
● Adding requirements from Contractors and Design Consultants to include level
2 schedule in their tender proposal.
Change
Description ● Updating KPI’s and adding KPI for time overrun.
● Change the section name from time to schedule.
● Adding procedures to include the updated level schedule in tender documents
for design and construction.
● Adding procedures to review and approve level 3 schedule submitted by
Contractor and Design Consultant.
● Adding procedure for reviewing and approving recovery schedule.
● Adding checklist for reviewing level 3 schedule.
● Adding procedure and guidelines for look ahead schedule.
● Adding procedure and guidelines for reviewing revised schedule submitted in
case of EOT claim.
● Merging the two processes of “time management for construction” and “time
management for handover” into one process.
● Updating flowcharts.
● Updating responsibilities as per NWC organization charts.
384 of 751
Schedule
Created at the beginning Created to be used for project control.
of Design Stage.
Created to be used for
project control.
Level 4 Schedule for Construction (if required).
Covers in greater detail, certain area of concern in
Construction, Testing & Commissioning and
Handover & Closeout.
Created by Contractor.
Level 4
Created During Construction and Testing &
Schedule
Commissioning Stages.
Created to address specific situations that demand
a greater level of detailing than that available on
Level 3 schedule such as mobilization, 3 months
look ahead or a case with an external party.
Level 5 Schedule for Construction.
Covers Construction, Testing & Commissioning and
Handover & Closeout.
Created by Contractor.
Created During Construction and Testing &
Level 5 Commissioning Stages.
Schedule Created to quantify the works in tables at maximum
practical details on hourly, daily or weekly basis
12/01/2022
such as procured material, design deliverables, a
specific work deliverable, etc. to be used by site
execution persons. Dates/times are mentioned in
the table headers instead of time scale.
Section 10 - Project Schedule Management
10.1.3 Flowchart
Figure 10-2 PMM-010-SCH-010 Plan Project Schedule Management Flowchart
10.1.4 Procedures
10.1.4.1 PMM-010-SCH-010-015 Develop the Schedule Management Plan Section of
the Project Management Plan
Procedure: ● Review and Approve the Schedule Management Plan Section of Project
Management Plan.
● Document and track the results of the reviews till they are closed out
satisfactorily.
● Approve the submitted Project Schedule Management Plan Section.
● Ensure that only changes approved through (PMM-007-INT-060
Variation Control) process are implemented.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Schedule Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Schedule assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
10.2.3 Flowchart
Figure 10-3 PMM-010-SCH-015 Schedule Management for Initial Planning Flowchart
10.2.4 Procedures
10.2.4.1 PMM-010-SCH-015-010 Update Project Level 1 Schedule
Procedure: ● Use the “Primavera P6” to develop project level 1 schedule based on the
initial level 1 schedule developed by Strategic planning in NWC Five-
Year Projects Portfolio planning.
● Update the NWC Project Management Plan the project level 1 schedule.
● This schedule shall be revised and updated at the end of every stage
(before the stage gate review) by the new information in the completed
stage. It can also be updated when required by any new rising
information.
10.3.2 Policies
Policies for this process are as follows:
1. The detailed procurement schedule for the tendering activities must be developed
during the Tendering Stages, by the NWC Project Manager, Cluster Scheduling &
Control Manager and Cluster Technical Services Director in coordination with and
Supply Chain Team.
2. The procurement schedule shall be maintained in the “Primavera P6” as an integral
part of the project schedule.
3. The procurement schedule must be updated weekly during the tendering stages to
show actual progress of the procurement activities.
4. The NWC Project Manager, liaising with the Cluster Scheduling Section Head, must
weekly review the updated procurement schedule to identify whether the activities are
on-schedule or not.
5. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
10.3.3 Flowchart
Figure 10-4 PMM-010-SCH-020 Schedule Management for Procurement Flowchart
10.3.4 Procedures
10.3.4.1 PMM-010-SCH-020-010 Define the Procurement Activities
Procedure: ● Discuss the procurement activities with the Supply Chain Team.
● Identify the procurement activities clearly.
● Adjust the tendering stage duration appropriately, if needed.
● Send all assumptions and constraints for inclusion in the Project
Management Plan.
Procedure: ● Use the “Primavera P6” to show the intended relationships and
dependencies between procurement activities.
● Use the “Primavera P6” to show the duration of each procurement activity
and develop the procurement schedule.
● Develop procurement schedule in level 1. If the details and requirements
of procurement schedule cannot be reflected in level 1, develop the
procurement schedule in level 2.
● Send all assumptions and constraints for inclusion in the Project
Management Plan.
Procedure: ● During the tender for design stage and the tender for construction stage,
make weekly updates to the procurement schedule in the “Primavera P6”
to reflect progress and delays of the procurement activities.
● Identify impacts and propose mitigations on the procurement schedule,
caused by events occurring in design.
● Adjust the stage duration appropriately, if needed.
● Send all assumptions and constraints for inclusion in the Project
Management Plan.
Procedure: ● Check objective evidence (checklist) for each weekly update of progress
and delays associated with the procurement activities.
● Meet with the Procurement Team in the event of any uncertainty or lack
of clarity.
● For behind schedule procurement activities, agree an appropriate course
of action with the Procurement Team to bring the procurement schedule
back on track (recovery).
● Make updates to the procurement schedule in the “Primavera P6” to
reflect agreed recovery actions.
● Adjust the stage duration appropriately, if needed.
● Send all assumptions and constraints for inclusion in the Project
Management Plan.
10.4.3 Flowchart
Figure 10-5 PMM-010-SCH-030 Schedule Management for Design Flowchart
10.4.4 Procedures
10.4.4.1 PMM-010-SCH-030-010 Update Level 1 Design Schedule and Include it in
Tender for Design Documents and Evaluation
Procedure: ● Discuss the design activities with the Cluster Technical Services Team.
● Use the “Primavera P6” to show the estimated durations.
● Update level 1 design schedule with the discussed activities in
“Primavera P6”.
● NWC Project Manager shall review the updated level 1 design schedule
and include it in tender for design documentation and evaluation.
● Send all assumptions and constraints for inclusion in the Project
Management Plan.
Procedure: ● After design contract award, the Design Consultant shall use “Primavera
P6” to:
○ identify the design activities clearly.
○ show the intended relationships and dependencies between design
activities.
○ load the resources for activities.
○ show the duration of each design activity, based upon the identified
trades and resources.
○ develop the detailed level 3 design schedule.
● Send all assumptions and constraints for inclusion in the Design
Management Plan.
● Submit the detailed design level 3 schedule to the NWC for review and
approval.
Procedure: ● Within 15 days from submission date, the level 3 design schedule shall
be:
○ reviewed and approved by Cluster Scheduling Section Head and
NWC Project Manager using (PMF-010-SCH-013 Design Schedule
Review Checklist).
○ approved by Cluster Projects GM.
○ raised to Scheduling & Control GM for review and approval using.
Cluster Scheduling Section Head
Roles: Responsible:
NWC Project Manager
Cluster Projects GM
Accountable: Cluster Projects GM
Design Consultant
Consulted:
Cluster Technical Services Director
Scheduling Lead
Procedure: ● Within 7 days from cluster submission date, the level 3 design schedule
shall be:
○ reviewed and approved by Scheduling & Control Director using
(PMF-010-SCH-013 Design Schedule Review Checklist).
○ approved by Scheduling & Control GM.
○ sent back to Cluster Scheduling Section Head for uploading in
ENJAZ system.
Scheduling & Control Director
Roles: Responsible:
Scheduling & Control GM
Accountable: Scheduling & Control GM
NWC Project Manager
Consulted:
Cluster Scheduling Section Head
Scheduling Lead
NWC Project Manager
Informed:
Cluster Scheduling Section Head
10.4.4.5 PMM-010-SCH-030-036 Upload Level 3 Design Schedule to ENJAZ System
Procedure: ● With 1 day from receiving, the Cluster Scheduling Section Head shall
upload the approved Design Level 3 Schedule to “Primavera P6”
database.
Procedure: ● During the design stage, make weekly updates to the approved level 3
design schedule in the “Primavera P6” to reflect progress and delays of
the design activities.
● Submit the updated Level 3 Design schedule.
Procedure: ● Check objective evidence (checklist) for each weekly update of progress
and delays associated with the design activities.
● Meet with the Design Consultant in the event of any uncertainty or lack
of clarity.
● For behind schedule design activities, in the weekly progress meeting,
agree an appropriate course of action with the Design Consultant to bring
the design schedule back on track.
● Include schedule status in monthly progress reports.
● Upload the project status to ENJAZ system.
Procedure: ● Check and review the delay analysis and course of actions proposed by
the Design Consultant to bring the design schedule back on track. Use
as applicable the (PMF-010-SCH-010 Sch. Manual App4 Schedules
Review Checklist).
● Ensure the incorporation of the agreed course of actions in the submitted
recovery schedule which must be in “Primavera P6”.
● Make sure the contractual milestones are in line with the contractual
dates.
● If found satisfactory, accept submitted level 3 design recovery schedule
by the Cluster Scheduling Section Head, Cluster Technical Services
Director and NWC project manager respectively. This acceptance does
not make the recovery an approved baseline.
Procedure: ● Check and review the revised schedule proposed by the Design
Consultant for a Variation Request which includes time extension. Use
as applicable (PMF-010-SCH-010 Sch. Manual App4 Schedules Review
Checklist).
● Check differences between current design schedule and proposed
revised schedule based on the variation request to ensure the fulfillment
of the variation objectives.
● In the proposed schedule, ensure the contractual milestones that not
included in the variation request are in line with the contractual dates.
● Check the stage duration appropriately.
● Recommend approval or disapproval on the revised design schedule for
further processing through (PMM-007-INT-060 Variation Control)
process.
Cluster Scheduling Section Head
Roles: Responsible:
NWC Project Manager
Cluster Technical Services Director
Accountable: NWC Project Manager
Design Consultant
Consulted:
Scheduling & Control Director
Business Unit Construction Director
Informed:
Cluster Contracts Administration Section Head
Scheduling & Control Director
1. The level 1 schedule for the construction stage must be updated by the end the tender
for construction stage by the NWC Project Manager liaising with the Cluster Projects
GM and Cluster Scheduling Section Head.
2. The updated level 1 schedule of construction, testing & commissioning and handover
stages must be maintained in the “Primavera P6” as an integral part of the project
schedule.
3. The level 1 schedule of construction, testing & commissioning and handover stages
must only be changed if there is an approved variation (i.e. create a new baseline).
4. The Contractor shall submit a level 2 schedule of for project scope with his bid
proposal.
5. The detailed activity (level 3) schedule construction, testing & commissioning and
handover stages must cover the:
i. Construction stage.
ii. Testing & commissioning stage.
iii. Acceptance and hand over activities (at least submitting the acceptance and
handover request).
6. After contract award the Contractor shall submit level 3 schedule of construction,
testing & commissioning and handover stages for NWC review and approval
maximum after 15 days from site handover. The Supervision Consultant , NWC
Project Manager and Scheduling & Control GM shall review and approve the
submitted level 3 schedule.
7. The approved level 3 schedule of construction, testing & commissioning and handover
stages must be updated weekly during these stages to show actual progress of the
design activities.
8. The approved level 3 schedule of construction, testing & commissioning and handover
stages must be updated weekly during the Construction, testing & commissioning,
handover & close-out stages to show actual progress of the construction activities.
9. The Supervision Consultant and NWC Project Manager shall ensure each weekly
update of the level 3 schedule is valid. NWC project manager must take the according
action such as urge letter.
10. In case of creating a recovery schedule by the Contractor, NWC acceptance on the
recovery schedule does not make it a baseline. All progress indicators and measures
are still taken from the approved baseline NOT the recovery plan.
11. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
10.5.3 Flowchart
Figure 10-6 PMM-010-SCH-040 Schedule Management for Construction, Testing & Commissioning and
Handover Flowchart
10.5.4 Procedures
10.5.4.1 PMM-010-SCH-040-010 Update Level 1 Construction Schedule and Include it
in Tender for Construction Documents and Evaluation
Procedure: ● Discuss the construction activities with the Cluster Project Scheduling &
Control team.
● Use the “Primavera P6” to show the estimated duration.
● Update level 1 construction schedule with the discussed activities in
“Primavera P6”.
● NWC Project Manager shall review the updated level 1 construction
schedule and include it in tender for Construction documentation and
evaluation.
● Send all assumptions and constraints for inclusion in the Project
Management Plan.
Procedure: ● After construction contract award, the Contractor shall use “Primavera
P6” to:
○ identify the construction activities clearly.
○ show the intended relationships and dependencies between
construction activities.
○ load the resources for activities.
○ show the duration of each construction activity, based upon the
identified trades and resources.
○ develop the detailed level 3 construction schedule.
● The detailed level 3 construction schedule must include a procurement
schedule for critical material and equipment. It shall be created using
(PMF-010-SCH-003 Procurement Schedule for Critical Materials and
Equipment).
● Explain to the Design Consultant and NWC Project Manager how the
contract BoQ is distributed across the construction level 3 schedule in
the “Primavera P6”.
● Within maximum 15 days after site handover, submit the detailed project
schedule including critical material and equipment schedule to the
Supervision Consultant for review and approval.
● Send all assumptions and constraints for inclusion in the Construction
Management Plan.
Procedure: ● Within 15 days from submission date, the level 3 construction schedule
shall be:
○ reviewed and approved by Supervision Consultant and NWC Project
Manager using (PMF-010-SCH-010 Sch. Manual App4 Construction
Schedules Review Checklist).
○ approved by Cluster Projects GM.
○ raised to Scheduling & Control GM for review and approval using.
● See (PMF-011-COS-023 Construction Process Flow in Governance
Document).
Supervision Consultant
Roles: Responsible:
NWC Project Manager
Cluster Projects GM
Accountable: Cluster Projects GM
Contractor
Consulted:
Cluster Scheduling Section Head
Scheduling Lead
Procedure: ● Within 7 days from cluster submission date, the level 3 construction
schedule shall be:
○ reviewed and approved by Scheduling & Control Director using
(PMF-010-SCH-010 Sch. Manual App4 Construction Schedules
Review Checklist).
○ approved by Scheduling & Control GM.
○ sent back to Cluster Scheduling Section Head for uploading in
ENJAZ system.
● See (PMF-011-COS-023 Construction Process Flow in Governance
Document).
Scheduling & Control Director
Roles: Responsible:
Scheduling & Control GM
Accountable: Scheduling & Control GM
NWC Project Manager
Consulted:
Cluster Scheduling Section Head
Scheduling Lead
NWC Project Manager
Informed:
Cluster Scheduling Section Head
10.5.4.5 PMM-010-SCH-040-036 Upload Level 3 Construction Schedule to ENJAZ
System
Procedure: ● With 1 day from receiving, the Cluster Scheduling Section Head shall
upload the approved Design Level 3 Schedule to “Primavera P6”
database.
● See (PMF-011-COS-023 Construction Process Flow in Governance
Document).
Procedure: ● Discuss and agree with the Supervision Consultant and NWC Project
Manager which types of progress curves and dashboards will be used to
illustrate progress in periodic progress report submissions.
● Configure the agreed curves and dashboards in the “Primavera P6” to
the satisfaction of the Supervision Consultant and NWC Project
Manager.
Procedure: ● During the design stage make weekly updates to the approved level 3
construction schedule in “Primavera P6” to reflect progress and delays
of the design activities.
● Prepare/update 2 weeks look ahead schedules every week (PMF-010-
SCH-005 Two Weeks Lookahead).
● Submit the updated Level 3 Construction schedule and the 2 weeks look
ahead schedules.
Procedure: ● Check objective evidence (checklist) for each weekly update of progress
and delays associated with the construction activities.
● Meet with the Contractor in the event of any uncertainty or lack of clarity.
● For behind schedule construction activities, in the weekly progress
meeting, agree an appropriate course of action with the Contractor to
bring the construction schedule back on track.
● Include schedule status in monthly progress reports.
● Upload the project status to ENJAZ system.
Supervision Consultant
Roles: Responsible:
NWC Project Manager
Accountable: NWC Project Manager
Cluster Contracts Administration Section Head
Consulted:
Cluster Scheduling Section Head
Contractor
Business Unit Construction Director
Informed:
Cluster Scheduling Section Head
Project Performance Monitoring Director
Scheduling & Control Director
10.5.4.9 PMM-010-SCH-040-070 Approve Recovery Schedule and Delay Analysis
Submitted by Contractor
Procedure: ● Check and review the delay analysis and course of actions proposed by
the Contractor to bring the Construction schedule back on track. Use
(PMF-010-SCH-010 Sch. Manual App4 Schedules Review Checklist).
● Check the incorporation of the agreed course of actions in the submitted
recovery schedule which must be in “Primavera P6”.
● Make sure the contractual milestones are in line with the contractual
dates.
● If found satisfactory, accept the recovery schedule by the Supervision
Consultant then NWC Project Manager. This acceptance does not make
the recovery an approved baseline.
Procedure: ● Check and review the revised schedule proposed by the Contractor for
a Variation Request which includes time extension. Use (PMF-010-SCH-
010 Sch. Manual App4 Schedules Review Checklist).
● Check differences between current construction schedule and proposed
revised schedule based on the variation request to ensure the fulfillment
of the variation objectives.
● In the proposed schedule, ensure the contractual milestones that not
included in the variation request are still in line with the contractual dates.
● Check the stage duration appropriately.
● Recommend approval or disapproval of the revised construction
schedule for further processing through (PMM-007-INT-060 Variation
Control) process.
Supervision Consultant
Roles: Responsible:
NWC Project Manager
Accountable: NWC Project Manager
Cluster Scheduling Section Head
Consulted:
Contractor
Scheduling & Control Director
Business Unit Construction Director
Informed:
Cluster Contracts Administration Section Head
Cluster Scheduling Section Head
Scheduling & Control Director
10.6 Key Performance Indicators (KPIs)
The table below identifies the KPIs of Project Schedule Management. The NWC Project Manager
is responsible to measure and report these KPIs at each KPI stated frequency. The current status
of each KPI is to be reflected in the monthly project progress report.
For further details refer to (PMF-006-GOV-015 KPI Report).
Year-to-date number of
Approved updated
projects that have
level 1 schedule at
1 approved updated level Monthly 0 1 >1
initial planning
1 schedule by the end of
stage
initial planning stage.
Year-to-date number of
Approved updated projects that have
level 1 schedule at approved updated level
2 Monthly 0 1 >1
tender for 1 schedule by the
construction stage beginning of tender for
construction stage.
Year-to-date number of
Approved updated ongoing design projects
level 3 schedule of in the cluster that did
5 design projects per NOT have an approved Monthly 0 2 >2
month in the level 3 schedule within
cluster 15 days from schedule
submission date.
Year-to-date number of
Approved updated ongoing construction
level 3 schedule of projects in the cluster
construction or that did NOT have an
6 Monthly 0 2 >2
EPC projects per approved level 3
month in the schedule within 15 days
cluster from schedule
submission date.
Percentage of year-to-
date number of ongoing
projects with a schedule
Delayed projects in variance (SV) that "10%
9 Monthly 0 4% > 4%
the cluster < SV ≤ 25%" in a cluster
to the year-to-date total
ongoing projects in the
cluster.
Percentage of year-to-
date number of ongoing
projects that fulfill
Troubled projects "Troubled Project
10 Monthly 0 4% > 4%
in the cluster Criteria" in a cluster to
the year-to-date total
ongoing projects in the
cluster.
10.7 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-010-
SCH Project Schedule Management).
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● Table "Cost Estimate Classes” is elaborated.
● Requirements to develop each Cost Estimate Class are added.
● The process “PMM-009-COS-010 Cost Management During NWC Five Years
Projects Portfolio Plan” is removed as it is covered in FYPPP Section.
● The process “PMM-011-COS-020 Plan Project Cost Management” is elaborated.
● The process “PMM-011-COS-030 Cost Management During Initial Planning Stage”
is revised.
● The process “PMM-011-COS-035 Cost Management During the Tender for Design
Stage” is added.
Change ● The process “PMM-011-COS-040 Cost Management During the Design Stage” is
Description revised.
● The process “PMM-011-COS-050 Cost Management During the Tender for
Construction Stage” is revised.
● The process “PMM-009-COS-060 Cost Management during the Construction,
Testing & Commissioning and Handover & Closeout Stages” is revised and split into
three processes:
○ “PMM-011-COS-060 Control Construction BOQ”
○ “PMM-011-COS-070 Payments during Construction, Testing & Commissioning
and Handover & Closeout Stages”
○ “PMM-011-COS-080 Monitor and Control Budget and Cashflow”
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This section is developed as an update to “Cost” section in first version the Project
Management Manual (PMM) which developed by Faithful + Gould. The following are
the changes:
● Changing the cost estimate level to class as per Mashroat Five-Year Projects
Portfolio Planning and Mashroat White Book.
● Updating the following guidelines:
○ Cost Budgeting Guidelines
○ Cost Estimating Guidelines
Change ● Developing guidelines for Cost Control and Reporting.
Description
● Updating the standard BOQ for water and sewer networks.
● Adding Plan cost management process.
● Adding procedure for payment application of Design Consultant.
● Adding procedure for developing class 3 cost estimate at 30% design
completion.
● Updating responsibilities as per NWC organization charts.
● Updating KPI’s.
● Updating processes flowcharts.
Cost estimate is classified into five estimate classes which range from the lowest class of project
definition and accuracy in Class 5 to the highest class in Class 1.
Produced at Phase/Stage
Estimate Accuracy
Description
Class Range
Design Bid Build Design & Build (EPC)
FYPPP*1 Phase A
Indicative /
Class 5 (Initiate Portfolio) -25% to +50%
Conceptual
At Initial Cost Estimate for Initial Business Case
FYPPP*1 Phase C
Feasibility /
Class 4 Order of (Screen Initial Portfolio) -15% to +25%
Magnitude
At Final Business Case Development
11.1.3 Flowchart
Figure 11-2 PMM-011-COS-020 Plan Project Cost Management Flowchart
11.1.4 Procedures
11.1.4.1 PMM-011-COS-020-010 Develop the Cost Management Plan Section of the
Project Management Plan
Procedure: ● Review and Approve the Cost Management Plan Section of Project
Management Plan.
● Document and track the results of the reviews till they are closed out
satisfactorily.
● The NWC Project Manager shall approve using (PMF-014-COM-004
Document Approval Form).
● Ensure that only changes approved through (PMM-007-INT-060
Variation Control) process are implemented.
Procedure: ● Develop Project Cost Management Plan Section in the Project Design
Management Plan.
● Ensure that the Project Cost Management Plan Section in the Project
Design Management Plan is in alignment with the Project Cost
Management Plan Section in the NWC Project Management Plan.
● Consult with NWC Project Manager and Cluster Technical Services
Director about the development of the Project Cost Management Plan
Section.
● Include the Project Cost Management Plan Section in the Project Design
Management Plan to be approved as part of the Project Design
Management Plan.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Cost Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Cost assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
11.2.3 Flowchart
Figure 11-3 PMM-011-COS-030 Cost Management During the Initial Planning Stage Flowchart
11.2.4 Procedures
11.2.4.1 PMM-011-COS-030-010 Update Class 4 Cost Estimate for Design-Bid-Build
Projects
Procedure: ● Refer to the Risk Workshop No. 2 Report for identified risks.
● Record the forecast cost details of the preferred option. Refer to the Cost
Database as required.
● Refer to (PMF-011-COS-001 Cost Estimating Guidelines) and (PMF-
011-COS-002 Cost Budgeting, Trending and Forecast Guidelines).
● Consider Key studies and plans that feed into preparation of the cost
estimate and budget requirements which include but not limited to the
following:
○ Concept Masterplan and Development Framework
○ 30% Design Package
○ Environmental Assessment
○ Land Acquisition Strategy
○ Permitting Plan
○ Risk Assessment Update
● Develop the class 3 cost estimate.
● Assist the NWC Project Manager to ensure that assumptions, issues and
risks are formally recorded and attached to the completed form, as well
as included in the Project Management Plan.
11.3.3 Flowchart
Figure 11-4 Cost Management During the Tender for Design Stage
11.3.4 Procedures
11.3.4.1 PMM-011-COS-035-010 Ensure Cost Requirements and Technical Evaluation
are Included in the Design Tender Documents
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the design RFP.
● Ensure Cost Requirements are included in the design RFP.
● Ensure the requirement “The Design Consultant is required to create his
own Quality Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes cost assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
11.4.3 Flowchart
Figure 11-5 PMM-011-COS-040 Cost Management During the Design Stage Flowchart
11.4.4 Procedures
11.4.4.1 PMM-011-COS-040-010 Approve Design Consultant Invoice
Procedure: ● NWC Project Manager shall receive hardcopy of the Design Consultant
monthly current invoice and its supporting documents.
● If Design Consultant does not submit the current invoice maximum the
7th of the month, NWC Project Manager shall send an urge letter to the
Design Consultant.
● NWC Project Manager shall within 7 days from invoice submission:
○ with Cluster Cost Control Section Head and Cluster Technical
Services Director, he shall check the submitted monthly current
invoice and its supporting documents.
○ discuss with Design Consultant any discrepancies and receive from
him any required corrections.
○ review and approve the monthly current invoice considering:
- Verify the overall invoice format and calculations for accuracy
and compliance with the Contract’s terms and conditions.
- Verify the inclusion of any due deductions or penalties.
- Verify the invoice items, prices, quantities are in conformity with
the BOQ included in the Contract Documents and the quantities
are verified against actual installed units of Work or Services
completed in the period to which the Application refers.
Procedure: ● Develop Class 3 Cost Estimate for the developed 30% Design package.
During development ensure:
○ Performing adequate quantity survey and measurements from
design drawings.
○ Considering the formal Technical Services forms, policies,
specifications, database and requirements that related to Cost
Estimation,
○ Referring to (PMF-011-COS-001 Cost Estimating Guidelines) and
(PMF-011-COS-002 Cost Budgeting, Trending and Forecast
Guidelines).
○ Considering studies and external plans and requirements that
related to preparation of the Class 3 Cost Estimate which include but
not limited to the following:
- Concept Master plan and Development Framework
- Initial Environmental Assessment
- Land Acquisition Strategy
- Permitting Plan
- Risk Assessment Update
○ Assumptions, issues and risks are formally recorded and considered
in Class 3 Cost Estimate.
● Include the Class 3 Cost Estimate in the 30% Design Package that to be
submitted to NWC for review and approval.
Procedure: ● Receive the Class 3 Cost Estimate for the developed 30% Design
Package from NWC Project Manager and Cluster Technical Services
Director
● Review Class 3 Cost Estimate for the developed 30% Design package
ensuring the alignment to:
○ the formal Technical Services forms, policies, specifications,
database and requirements that related to Cost Estimation,
○ (PMF-011-COS-001 Cost Estimating Guidelines) and (PMF-011-
COS-002 Cost Budgeting, Trending and Forecast Guidelines).
○ studies and external plans and requirements that related to
preparation of the Class 3 Cost Estimate which include but not
limited to the following:
- Concept Master plan and Development Framework
- Initial Environmental Assessment
- Land Acquisition Strategy
- Permitting Plan
- Risk Assessment Update
○ formally recording and considering the assumptions, issues and
risks in Class 3 Cost Estimate.
○ comparing to NWC Cost Database as required.
● Approve/Reject Class 3 Cost Estimate providing adequate comments
and feedback.
● Ensure the inclusion of the approval/rejection of Class 3 Cost Estimate
in the 30% Design package feedback that to be sent to Design
Consultant.
Cluster Cost Estimation Specialist
Roles: Responsible:
Cluster Technical Services Director
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Cluster Scheduling Section Head
Cluster Technical Services Director
Cost Estimation Manager
Design Consultant
NWC Project Manager
Informed:
Portfolios Strategic Planning & Spending Efficiency
Director
Procedure: ● Develop Class 2 Cost Estimate for the developed 90% Design package.
During development ensure:
○ Performing adequate quantity survey and measurements from
design drawings.
○ Considering the formal Technical Services forms, policies,
specifications, database and requirements that related to Cost
Estimation,
○ Referring to (PMF-011-COS-001 Cost Estimating Guidelines) and
(PMF-011-COS-002 Cost Budgeting, Trending and Forecast
Guidelines).
○ Considering studies and external plans and requirements that
related to preparation of the Class 3 Cost Estimate which include but
not limited to the following:
- Concept Master plan and Development Framework
- Initial Environmental Assessment
- Land Acquisition Strategy
- Permitting Plan
- Risk Assessment Update
○ Assumptions, issues and risks are formally recorded and considered
in Class 3 Cost Estimate.
● Include the Class 3 Cost Estimate in the 30% Design Package that to be
submitted to NWC for review and approval.
Procedure: ● Receive the Class 2 Cost Estimate for the developed 90% Design
Package from NWC Project Manager and Cluster Technical Services
Director.
● Review Class 2 Cost Estimate for the developed 90% Design package
ensuring the alignment to:
○ the formal Technical Services forms, policies, specifications,
database and requirements that related to Cost Estimation,
○ (PMF-011-COS-001 Cost Estimating Guidelines) and (PMF-011-
COS-002 Cost Budgeting, Trending and Forecast Guidelines).
○ studies and external plans and requirements that related to
preparation of the Class 3 Cost Estimate which include but not
limited to the following:
- Concept Master plan and Development Framework
- Initial Environmental Assessment
- Land Acquisition Strategy
- Permitting Plan
- Risk Assessment Update
○ formally recording and considering the assumptions, issues and
risks in Class 2 Cost Estimate.
○ comparing to NWC Cost Database as required.
● Approve/Reject Class 2 Cost Estimate providing adequate comments
and feedback.
● Ensure the inclusion of the approval/rejection of Class 2 Cost Estimate
in the 90% Design package feedback that to be sent to Design
Consultant.
Cluster Cost Estimation Specialist
Roles: Responsible:
Cluster Technical Services Director
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Cluster Scheduling Section Head
Cluster Technical Services Director
Cost Estimation Manager
Design Consultant
NWC Project Manager
Informed:
Portfolios Strategic Planning & Spending Efficiency
Director
11.5.4 Procedures
11.5.4.1 PMM-011-COS-050-010 Collect Tender Cost Estimate (Class 2 / Class 3) from
Design Package and Include in RFP
11.6.4 Procedures
11.6.4.1 PMM-011-COS-060-010 Develop and Submit Revised BOQ
Procedure: ● The Contractor shall quantify all project works included in Contract BoQ
based on actual site conditions.
● Contractor shall develop and submit a revised BoQ incorporating his
findings within 90 days from the site handover using form (PMF-011-
COS-026 Revised BoQ Form).
● See (PMF-011-COS-023 Construction Process Flow in Governance
Document).
Procedure: ● The revised BoQ shall be sequentially reviewed and signed within 14
days by:
○ Supervision Consultant
○ NWC Project Manager
○ Cluster Projects GM
● NWC Project Manager shall initiate the approval form using (PMF-011-
COS-029 Revised BOQ Approval Form) and raise all documents to
Cluster Projects GM for 1st approval.
● Cluster Projects GM shall raise to Scheduling & Control GM for review in
following cases:
○ MEWA projects
○ NWC projects that fulfill the following conditions:
- Does not include any new BoQ items or changes in existing item
description.
- Does not include changes in contractual project location.
- Does not include contract value increase.
- Does not include contract value decrease more than 20% of
contract value.
- The sum of all positive value changes does not exceed 30% of
contract value.
- The sum of all negative value changes does not exceed 30% of
contract value.
- Does not increase the contractual duration.
● If the project is not one of the above two cases, the submitted revised
BoQ shall be processed as a Variation through (PMM-007-INT-060
Variation Control) process.
● See (PMF-011-COS-023 Construction Process Flow in Governance
Document).
Supervision Consultant
Roles: Responsible:
NWC Project Manager
Cluster Projects GM
Accountable: Cluster Projects GM
Cluster Scheduling & Control Manager
Consulted:
Cluster Technical Services Director
Contractor
Informed: HQ/Cluster Supply Chain GM (as per authority)
Procedure: ● Scheduling & Control GM shall review and endorse, within 14 days, and
raise the revised BoQ to Capital Projects & Technical Services VP.
● The Capital Projects & Technical Services VP shall, within 2 days, review
and give:
○ 1st approval for MEWA projects, then forward the revised BoQ to the
authorized person in MEWA for final approval.
○ final approval for NWC project, then forward the revised BoQ to the
Cluster/HQ Procurement (as per authority) for issuance to
Contractor.
● The approved revised BoQ shall be forwarded to the Cluster/HQ
Procurement (as per authority) to issue the approved revised BoQ to
Contractor along with any other required document.
● See (PMF-011-COS-023 Construction Process Flow in Governance
Document).
Scheduling & Control GM
Roles: Responsible:
Technical Services GM
Capital Projects & Technical Services VP
Accountable: Capital Projects & Technical Services VP
NWC Project Manager
Consulted:
Cluster Projects GM
HQ/Cluster Supply Chain GM (as per authority)
Informed:
Cluster Senior GM
Cluster Projects GM
11.6.4.4 PMM-011-COS-060-040 Approve Revised BoQ Submitted by Contractor at
MEWA
Procedure: ● Update “ENJAZ” system and “Primavera P6” database by the information
of the processed revised BOQ.
● Use only the information provided in the approved documents.
● Ensure that the update has been reflected in the NWC Finance
Department System.
iii. Contract/agreement.
iv. Bank Guarantee.
v. Commercial Registration Certificate.
vi. Certificate of Subscription to Chamber of Commerce & Industry.
vii. Certificate of GOSI.
viii. Saudization Certificate.
ix. Certificate of Zakat & Income.
4. Paid advance payment shall be recovered at instalments of percent equal to (Advance
payment value to Contract Value) from all monthly invoices starting from first invoice
in the contract.
5. If the project went terminated for any reason, NWC Project Manager shall immediately
request to settle the advance payment.
6. Every current invoice application shall be submitted on monthly basis regardless the
amount of performed work on maximum the 7th days of every month. The invoice
shall cover the month works.
7. Every invoice shall be approved only if all works in the submitted the invoice are:
i. formally accepted by Supervision Consultant.
ii. do not have an open Quality NCR.
8. Contractor final invoice to be submitted only after the closure of all initial acceptance
snag list items.
9. Electronic source files associated with cost management in this phase of the project
lifecycle must be locked to prevent tampering and corruption.
10. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
11.7.3 Flowchart
Figure 11-8 PMM-011-COS-070 Payments during Construction, Testing & Commissioning and
Handover & Closeout Stages Flowchart
11.7.4 Procedures
11.7.4.1 PMM-011-COS-070-010 Approve Supervision Consultant Invoice
Procedure: ● NWC Project Manager shall receive hardcopy of the Contractor monthly
current invoice and its supporting documents.
● If Contractor does not submit the current invoice maximum the 7th of the
month, NWC Project Manager shall send an urge letter to the Contractor.
● The Contractor current invoice shall be reviewed as follows:
○ For Contractor current invoice (for NWC projects):
- Ensure the Contractor has attached:
· the HSE certificate using “00_BS01_FM_021.01 HSSE
Commitment Certificate for Invoicing”.
· the as built drawings and GIS information for works
invoiced two months earlier.
- The Supervision Consultant and NWC project manager shall
review and approve the monthly current invoice and its
supporting documents within maximum 7 days.
· Verify the overall invoice format and calculations for
accuracy and compliance with the Contract’s terms and
conditions.
· Verify the inclusion of any due deductions or penalties.
· Verify the invoice items, prices, quantities are in conformity
with the BOQ included in the Contract Documents and the
quantities are verified against actual installed units of Work
or Services completed in the period to which the
Application refers.
· Verify that all required deliverables have been inspected
and accepted to the Authorized Representative or
Department Representative.
· Verify that any insurances, bonds, securities and like are
still valid and in effect for the Works or Services.
· Verify / Assess any back-charges, retentions, delay
penalties or other deductions to the Payment amount that
the NWC is entitled to withhold in accordance with the
Agreement.
· Create a “Completion” / “Work Confirmation” Certificate in
iSupplier system, print a hardcopy and sign the hardcopy.
· Send a copy the of all invoice documents to the Contractor
including a copy of the signed “Completion” / “Work
Confirmation” Certificate.
- Contractor shall upload the signed copy of the monthly current
invoice to NWC system within 1 day.
- The NWC Project Manager shall approve monthly current
invoice within 3 days.
- The Cluster Projects GM shall give final approval monthly
current invoice within 3 days, then forward it to Finance
Department.
Procedure: ● When the advance payment gets approved, update the status on
(ENJAZ System) by the approval.
● When Contractor receives the advance payment, update (ENJAZ
System) accordingly
● Continuously, ensure the advance payment recovery in Contractor
submitted invoices (current and final).
Consulted: Contractor
NWC Project Manager
Informed:
Cluster Cost Control Section Head
11.7.4.7 PMM-011-COS-070-070 Update “ENJAZ” System and “Primavera P6”
Database
Procedure: ● Update “ENJAZ” system and “Primavera P6” database by the information
of the processed:
○ advance payment
○ current invoice.
○ final invoice
● Use only the information provided in the approved documents.
● Check with Cluster Finance Dept. that the update has been reflected in
the NWC Finance System.
stage (contract award) up to end of Handover & Close-out stage (beginning liability
and operation period). This is known as the “Contract Budget”.
5. The construction and handover schedules must be updated weekly during the
Construction and Handover phases to show actual progress of the activities as a
draw-down of the “Contract Budget”.
6. Electronic source files associated with cost management in this phase of the project
lifecycle must be locked to prevent tampering and corruption.
11.8.3 Flowchart
Figure 11-9 PMM-011-COS-080 Monitor and Control Budget and Cashflow Flowchart
11.8.4 Procedures
11.8.4.1 PMM-011-COS-080-010 Develop Project Cost Metrics
Procedure: ● Review the project cost metrics which prepared by the Contractor:
○ Budget (actual to date, planned and forecast).
○ Budget balance value (approved project value - advance payment -
total of processed current invoices).
○ Cashflow (actual to date, planned and forecast).
○ Any other agreed metrics with NWC Project Manager and
Supervision Consultant.
● Identify any improper information and communicate with contractor to
correct them.
● Accept and send the project cost metrics to NWC Project Manager
Procedure: ● Review the project cost metrics which developed by the Contractor.
● Communicate with Supervision Consultant to correct any improper
information.
● Accept the Project Cost Metrics and direct to include them in Monthly
Progress Report and Executive Summary of Monthly Progress Report.
Year-to-date number of
projects that in initial
Class 4 cost
1 planning stage and do Monthly 0 NA >0
estimates
not have Class 4 cost
estimate.
Year-to-date number of
Class 3 cost Design & Build (EPC)
estimates in projects that without
2 Monthly 0 NA >0
Design & Build Class 3 cost estimate by
(EPC) projects the end of the initial
planning stage.
Year-to-date number of
Design-Bid-Build
Class 3 cost
projects that without
3 estimates Design Monthly 0 NA >0
Class 3 cost estimate by
projects
completion of 30%
design package review.
Year-to-date number of
Design-Bid-Build
Class 2 cost
projects that without
4 estimates Design Monthly 0 NA >0
Class 2 cost estimate by
projects
the end of the end of
design stage.
Year-to-date number of
Untimely current ongoing projects that
invoice NOT submitted the
6 Monthly 0 3 >3
applications up to monthly current invoice
date within the first 7 days of
the month.
Year-to-date number of
Not submitted
7 not submitted invoices Monthly 0 2 >2
invoices
of ongoing projects.
Year-to-date number of
monthly current invoices
Time for that sent from cluster
processing the projects department to
8 Monthly 0 3 >3
submitted monthly Finance Department for
current invoice paying in more than 14
days from contractor
submission date.
Year-to-date number of
Approved first ongoing construction
revised BOQ of projects in the cluster
construction or that did NOT have an
10 Monthly 0 2 >2
EPC projects per approved first revised
month in the BOQ within 14 days
cluster from BOQ submission
date.
Year-to-date number of
“Estimate at projects that its
Completion” Cost "Estimate at
11 compared to the Completion" is out the Monthly 0 1 >1
original design range -20% to +10% of
contract value. the original design
contract value.
Year-to-date number of
“Estimate at
projects that its
Completion” Cost
"Estimate at
compared to the
12 Completion" is out the Monthly 0 1 >1
original
range -20% to +10% of
construction
the original construction
contract value.
contract value.
11.10 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-011-
COS Project Cost Management).
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-012-QUA-010 Plan Project Quality Management” is elaborated.
Change ● The process “PMM-012-QUA-020 Perform Quality Assurance” is revised.
Description
● The process “PMM-012-QUA-030 Perform Quality Control” is revised.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This version is developed as an update to the latest version (v4) of the “Project Quality
Management” section in PMM which developed by Faithful + Gould. The following are
the changes:
● Adding procedures for submission and review of method statement and
Inspection and test plan (ITP).
● Modify the naming of inspection schedule to Inspection and test plan (ITP).
Change ● Adding Audit and Surveillance guidelines, forms and templates from Mashroat
Description White Book.
● Adding guidelines and form for material receiving and inspection.
● Updating forms and templates.
● Updating flowcharts.
● Updating responsibilities as per NWC organization charts.
● Updating KPI’s.
12.1.2 Policies
Policies for this process are as follows:
1. NWC Capital Projects & Technical Services fully supports the high standards and
quality policy of the business. There are no exceptional circumstances where the
quality policy may be ignored at the level of a Cluster program or at individual project
level.
2. Prevention of quality issues is better than cure, all the time and every time.
3. Each project must have a separate section for quality management in the Project
Management Plan, created by the NWC Project Manager and used as the guiding
document for internal and external staff throughout the project.
4. The approved Project Management Plan, including the Quality Management Plan
section, must be included in the tender document when NWC is procuring Second
Party services and products in support of project execution.
5. Second Parties must create their own Quality Management Plan sections for the
project as part of their contract mobilization work based on ISO9001 QMS and
ISO10005 Quality Planning Guidelines. These Quality Management Plan Sections
must be approved by NWC during mobilization period.
6. Second Parties Quality Management Plan Sections must be supported by competent
material testing and works inspection regime, which must be subjected to periodic
inspections and audits by NWC.
7. The Quality Management Plans in PMPs of NWC, Design and Construction must be
kept up-to-date throughout the project life cycle.
8. Planning for quality must be specific and unique to the location, activities and
characteristics of the project. It must not be generic or wholesale copy-and-paste from
previous projects, else it will be rejected and the work will not be allowed to proceed.
12.1.3 Flowchart
Figure 12-2 PMM-012-QUA-010 Plan Project Quality Management Flowchart
12.1.4 Procedures
12.1.4.1 PMM-012-QUA-010-010 Develop the Quality Management Plan Section of the
Project Management Plan
Cluster Projects GM
Consulted:
Business Unit Construction Director
Quality Assurance Director
Cluster PMO Manager
Informed:
Cluster Projects GM
Quality Assurance Director
Guidelines: ● The Quality Management Plan Section of the Project Management Plan
shall address but not limited to the following:
○ Project quality requirements including interpretations and
expectations
○ Vision of high quality performance including key performance
indicator (KPIs) metrics that reflect quality performance
○ measurement methods, frequency of measurement, communication
methods, corrective action responsibility
○ Customer satisfaction
○ Quality audits
○ Non-conformities
○ Repeated violations
○ Management reviews
○ Document and records control
○ Preventive action
○ Corrective action
Procedure: ● Review and Approve the Quality Management Plan Section of Project
Management Plan.
● Document and track the results of the reviews till they are closed out
satisfactorily.
● Approve the submitted Project Quality Management Plan Section.
● Ensure that only changes approved through (PMM-007-INT-060
Variation Control) process are implemented.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the design RFP.
● Ensure the requirement “The Design Consultant is required to create his
own Quality Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Quality assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
Procedure: ● Develop Project Quality Management Plan Section in the Project Design
Management Plan.
● Ensure that the Project Quality Management Plan Section in the Project
Design Management Plan is in alignment with the Project Quality
Management Plan Section in the NWC Project Management Plan.
● The Design Quality Management Plan shall strictly be in alignment with
(PMF-012-QUA-121 Quality Requirements for Construction Contractors
& Design Consultants) which the Design Consultant is responsible to
fulfill during the stages from construction to closeout.
● Consult with NWC Project Manager and Cluster Technical Services
Director about the development of the Project Quality Management Plan
Section.
● Include the Project Quality Management Plan Section in the Project
Design Management Plan to be approved as part of the Project Design
Management Plan.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Quality Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Quality assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
progress report, to the satisfaction of the Supervision Consultant and NWC Project
Manager.
3. Second Party Quality Management Plans must be supported by competent method
statements. Work activities by Second Parties must only be carried out if there are
associated HSE assurance documents in place, such as risk assessments, impact
assessments, construction safety guidelines, induction training records, tool box
training records and, most importantly, an approved NWC permit to carry out the
specific construction activities identified in the method statement. Results of quality
related activities and control measures shall be evaluated on a regular basis and
formally reported in the Contractor’s monthly quality report to the satisfaction of
Supervision Consultant and Cluster QA Section Head.
4. Method Statements must be specific and unique to the location, activities and
characteristics of the project. They must not be generic or wholesale copy-and-paste
from previous projects, else they will be rejected.
5. All Quality inspection test plans and associated assurance records are subject to
periodic internal audits by NWC.
6. There must be provision for training of workers in the importance of method
statements and how method statements must be followed at all times for all activities,
without exception.
7. The NWC Project Manager shall ensure that all Project Team members have been
trained to the project Quality procedures according to training procedures included in
the Construction Quality Management Plan.
8. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
12.2.3 Flowchart
Figure 12-3 PMM-012-QUA-020 Perform Quality Assurance Flowchart
12.2.4 Procedures
12.2.4.1 PMM-012-QUA-020-010 Carry Out the Quality-Related Internal Design
Reviews
Procedure: ● Carry out a quality-related internal design review before each package
submission for design review.
● Prior to formal submission to NWC, each quality-related internal design
review report must first be discussed between the Design Consultant, the
Cluster Technical Services Director and Cluster Value Engineering
Specialist as appropriate.
● Formally report on each completed internal design review.
● Each quality-related internal design review report must be submitted as
an integral part of each design review package with the appropriate
design deliverables, such as drawings, calculations, etc.
● Quality -related internal design reviews are themselves considered as
deliverables by NWC.
Procedure: ● Quality-related internal design review reports must be approved with the
associated design package (drawings, calculations, etc.)
● DO NOT approve design package separately from the associated
quality-related internal design review report(s).
● The review of each design deliverable package, including the associated
quality-related internal design review report, is led by the Cluster
Technical Services Director, assisted by the Cluster QA Section Head,
as part of the review and approval activity.
● Include all internal design review report’s comments and suggestions for
improvements in the design review package response.
Cluster Technical Services Director
Roles: Responsible:
Cluster QA Section Head
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Cluster Value Engineering Specialist
Technical Services GM
Quality Assurance Director
Technical Services GM
Informed:
Quality Assurance Director
Procedure: ● The method statement shall include clearly identified steps, which have
been introduced in order to ensure quality and safety of workmanship.
● Use the Method Statement format provided by NWC (PMF-012-QUA-
004 Method Statement (General)).
● This is developed initially from the quality perspective (i.e. describe what
work is to be done, to what standards of workmanship, etc.)
○ How does the Contractor intend to carry out the work?
○ What resources does he intend to deploy?
○ What is the timescale for completion?
○ Confirm that any external Permits, or other legal requirements, have
been obtained.
○ What quality control measures Contractor proposes to undertake
and at what stages of the construction works these will be
implemented, using the Inspection and Testing Plan (ITP)
○ The quality forms provided by NWC. If a form is not covered in NWC
forms set Contractor shall develop the form and obtain NWC
approval.
○ Are any material approvals needed and/or testing that will be carried
out?
○ Risk assessment.
○ Any other relevant information concerning the execution of the
proposed works.
● Submit the method statement for approval.
12.2.4.5 PMM-012-QUA-020-050 Develop and Submit the Inspection and Testing Plan
(ITP)
Procedure: ● The ITP must be approved with the associated attachments and quality
forms.
● The review of each ITP, including the associated attachments, is
performed by the Supervision Consultant.
Procedure: ● Cluster QA Section Head shall collect all required data for the monthly
Quality KPIs Follow Up Matrix.
● Cluster QA Section Head shall create the Quality KPIs Follow Up Matrix
using (PMF-012-QUA-116 Monthly Quality KPIs Follow Up Matrix.)
● Distribute the Matrix to Cluster PMO Managers, NWC Project Managers
and Quality Assurance Director.
Supervision Consultant
Consulted:
Contractor
Quality Assurance Director
NWC Project Manager
Informed:
Supervision Consultant
Contractor
Quality Assurance Director
12.2.4.9 PMM-012-QUA-020-080 Capture Lessons Learned on Project Regarding
Quality Management
12.3.2 Policies
Policies for this process are as follows:
1. Construction activities in the approved permit to work must be followed at all times,
without exception.
2. NWC reserves the right to stop work by any party on the grounds of unsatisfactory
Quality management performance based on the NWC Project Management Plan and
the supporting project Quality register as criteria for satisfactory performance.
Stopping shall be applied only through formal notice.
3. Stopped works be resumed only upon approval by NWC of appropriate corrective and
preventive actions proposed by the party and accepted by NWC.
4. Any delays or additional costs incurred by the party due to their proven unsatisfactory
Quality management performance will not be accepted as grounds for a claim and
may be counter-claimed (i.e. penalized) by NWC of there is consequential loss as a
result.
5. Prevention is better than cure! Quality is not inspected-in after completion. Rather,
effort must be expended in identifying potential quality defects and eradicating their
root causes. This applies to process defects as well as to product defects.
6. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
12.3.3 Flowchart
Figure 12-4 PMM-012-QUA-030 Perform Quality Control Flowchart
12.3.4 Procedures
12.3.4.1 PMM-012-QUA-030-010 Review the Compliance of Design Packages to
Design Quality Requirements
Procedure: ● Quality must be an agenda item in all technical reviews and regular
progress meetings, as well as regular progress reports by the Design
Consultant.
● Address quality issues in the Technical Review Reports.
● For recording of meetings, use (PMF-014-COM-022 Weekly Meeting
Minutes) and clearly identify any quality-related actions.
● The approach must be collaborative between departments and parties,
and must consider the whole life of the asset, not just its construction
phase.
Cluster Technical Services Director
Roles: Responsible:
Design Consultant
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Cluster QA Section Head
NWC Project Manager
Informed:
Cluster QA Section Head
12.3.4.3 PMM-012-QUA-030-030 Carry Out Root Cause Analysis for Design Quality
Observations
Procedure: ● Design Consultant shall define the corrective and preventive actions for
the following:
○ Correction of the quality observations.
○ Correction of Non-Conformities.
○ Prevention of recurrence (e.g. a change to the design process itself).
● Use the Corrective and Preventive Actions section of the Quality
Observation Form (PMF-012-QUA-006 Quality Observation Record
(General)) or NCR Form (PMF-014-COM-013 Non Conformance Report
NCR) to document the defined actions.
● Each root cause must be adequately treated by a defined mitigation
through correction and/or prevention.
Procedure: ● Oversee that the Contractor carries out the construction activities in
accordance with the approved method statements.
● Ensure that the Contractor has carried out briefings and toolbox talks
associated with the work and has clearly used the approved permit to
work.
● Observe that the briefed staff are the actual staff who perform the work.
● Using the related approved method statements and approved ITPs,
perform:
○ material inspection and testing.
○ work inspection.
○ equipment factory inspections and tests in collaboration with NWC
Project Manager, Manufacturers and Contractor.
● Use (PMF-012-QUA-118 Quality Control Procedures (General)) to
manage material and work inspections via MIRs and WIRs.
● Rejected items shall be re-inspected before proceeding to next activity.
Procedure: ● Quality Observation Record forms and NCR forms must be followed-up
by thorough root cause analysis, leading towards development of robust
corrective and preventive actions
● Root causes during construction can lie within several areas but not
limited to:
○ Incomplete permit to work.
○ Inadequate permit to work.
○ Poor or low level supervision.
○ Staff changes.
○ Poor management of tools and materials.
○ Improper design.
● Use the “Root Cause Analysis” section of the Quality Observation and
NCR Forms to document the outcomes of the analysis exercise.
Procedure: ● “Quality” must be an agenda item in all regular site meetings, as well as
regular progress reports by the Contractor.
● Quality Status for Project should be evaluated as per Quality KPIs in
(PMM-012-QUA-030-007 Quality Status of Project).
● For recording of meetings, use to clearly identify any quality-related
actions.
● The approach must be collaborative between departments and parties,
and must consider the whole life of the asset, not just its construction
phase.
Supervision Consultant
Roles: Responsible:
Contractor
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Cluster QA Section Head
NWC Project Manager
Informed:
Cluster QA Section Head
12.3.4.9 PMM-012-QUA-030-090 Define Construction Corrective and Preventive
Actions
Submission of
10 days > 10 days
Submission of Construction Quality
withing after after
Construction Management Plan in the
1 Monthly mobilizati mobilizati mobilizati
Quality project during the
on period on period on period
Management Plan project mobilization
end end
period.
Year-to-date number of
2 Open quality NCRs open quality NCRs in Monthly 0 1 >1
the project.
Percentage of year-to-
date number of rejected
Rejected Work
WIRs in a project to the
6 Inspection Monthly 10% 25% > 25%
year-to-date total of
Requests (WIR)
submitted WIRs in the
project.
Percentage of year-to-
date number of rejected
Rejected Material
MIRs in a project to the
7 Inspection Monthly 10% 25% > 25%
year-to-date total of
Requests (MIR)
submitted MIRs in the
project.
Percentage of year-to-
date number of failed
Failed Tests
tests in a project to the
8 (excluding welding Monthly 10% 25% > 25%
year-to-date total of the
tests).
performed tests in the
project.
Percentage of year-to-
date number of failed
welding tests in a project
Failed Welding
9 to the year-to-date total Monthly 5% 6% > 6%
Tests
of the performed
welding tests in the
project.
12.5 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-012-
QUA Project Quality Management).
PMF-012-QUA-061 Inspection Test Plan for Manholes and Chambers (Manholes and
Chambers)
PMF-012-QUA-062 Leak Test for Manholes and Chambers (Manholes and Chambers)
PMF-012-QUA-080 Quality Guidelines for Construction Sites (Water Mains, Pipelines and HC)
PMF-012-QUA-081 Inspection Test Plan for Water Mains (Water Mains, Pipelines and HC)
PMF-012-QUA-082 Leak Test for Water Mains (Water Mains, Pipelines and HC)
PMF-012-QUA-083 Sectional Acceptance Certificate for Water Mains Pipeline (Water Mains,
Pipelines and HC)
PMF-012-QUA-086 Inspection Checklist for Pipeline Bedding and Around (All Pipelines)
PMF-012-QUA-104 Site Installation Inspection Request for Plant (Plants and Equipment)
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-013-HUM-010 Plan Project Human Resource” is converted from
a cross reference to detailed process.
● The process “PMM-013-HUM-020 Acquire the Project Team” is elaborated.
● The process “PMM-013-HUM-030 Develop the Project Team” is converted from a
Change cross reference to detailed process.
Description
● The process “PMM-013-HUM-035 Interview and Approve Second Party Project
Team Members” is added.
● The process “PMM-013-HUM-040 Manage the Project Team” is revised.
● The process “PMM-013-HUM-050 Close the Project Team” is revised.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
Figure 13-1 High-Level Process Map for Project Human Resources Management
13.1.3 Flowchart
Figure 13-2 PMM-012-QUA-010 Plan Project Human Resource Management Flowchart
13.1.4 Procedures
13.1.4.1 PMM-013-HUM-010-010 Develop the Human Resource Management Plan
Section of the Project Management Plan
Cluster Projects GM
Consulted:
Business Unit Construction Director
Cluster PMO Manager
Cluster Scheduling & Control Manager
Cluster PMO Manager
Informed:
Business Unit Construction Director
Cluster Projects GM
13.1.4.1 PMM-013-HUM -010-020 Approve the Human Resource Management Plan
Section of Project Management Plan
Procedure: ● Review and Approve the Human Resource Management Plan Section of
Project Management Plan.
● Document and track the results of the reviews till they are closed out
satisfactorily.
● Approve the submitted Project Human Resource Management Plan
Section.
● Ensure that only changes approved through (PMM-007-INT-060
Variation Control) process are implemented.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Human Resource Management Plan and must submit it during the
contractual mobilization period” is stated in the NWC Project
Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Human Resource assessment criteria, which
addresses:
○ the project requirements.
○ the past performance of the bidders.
2. The project team organization chart that included in Human Resource Section in the
Project Management Plan must be followed.
3. All positions in the Project Management Plan organization chart must be occupied
with suitable, competent staff in order to provide the NWC Project Manager with fill
project lifecycle support.
4. It is the responsibility of Line Managers to ensure that their subordinate staff is in
complete understanding of the described Project Team role, responsibilities,
competence requirements and cascaded objectives for the projects they are working
on.
5. A register of all project inductions and role-based training events must be retained
and continually be updated using (PMF-013-HUM-003 Induction and Training
Register).
6. If there is an NWC Project Manager change during a project execution, then there
must be a formally recorded handover from the outgoing Project Manager to the
incoming Project Manager. See (PMF-013-HUM-001 Project Manager Role Handover
Checklist).
13.2.3 Flowchart
Figure 13-3 PMM-013-HUM-020 Acquire the Project Team Flowchart
13.2.4 Procedures
13.2.4.1 PMM-013-HUM-020-010 Assign NWC Project Manager
Procedure: ● Business Unit Construction Director shall review project scope and
requirements and propose a suitable NWC Project Manager to manage
the project.
● Considering the current workload of the proposed NWC Project
Manager, Business Unit Construction Director shall ensure that the NWC
Project Manager has suitable experience in the following areas:
○ Region regulations.
○ Working on project of similar estimated value.
○ Working on projects of similar complexity.
○ Experience of any specialist work required.
● Business Unit Construction Director shall discuss with Cluster Projects
GM the nomination and request for approval.
● Cluster Projects GM shall approve assigning the nominated NWC Project
Manager.
Business Unit Construction Director
Roles: Responsible:
Cluster Projects GM
Accountable: Cluster Projects GM
Cluster Scheduling Section Head
Consulted:
Cluster Capital Resource Manager
Human Capital GM
Informed: NWC Project Manager
Procedure: ● For all changing NWC Project Manager, use (PMF-013-HUM-001 Project
Manager Role Handover Checklist) to carry out formal handover to the
new NWC Project Manager.
NWC Project Manager (outgoing)
Roles: Responsible:
NWC Project Manager (incoming)
Accountable: Cluster Projects GM
Cluster Projects GM
Consulted:
Cluster PMO Manager
Informed: Cluster Senior GM
13.2.4.3 PMM-013-HUM-020-020 Discuss and Identify Suitable Staff for the Project
from the Cluster Projects Team
Procedure: ● Review project scope and requirements and discuss with Cluster
Scheduling & Control Manager and Cluster Technical Services Director
in order to identify suitable staff within the required disciplines to assist
on the project.
● Ensure staff identified has suitable experience in the following areas
○ Experience on project of similar estimated value.
○ Experience on projects of similar complexity.
○ Experience of any specialist work required in project.
○ Experience within the specified field (Wastewater, Water, Plants).
○ Experience on particular Contract Type.
○ Knowledge in Working relationships with Supervision Consultant /
Contractor.
● When identifying staff, take into consideration current workload to ensure
they will have sufficient time available to dedicate to the Project
Business Unit Construction Director
Roles: Responsible:
NWC Project Manager
Accountable: Cluster Projects GM
Cluster Scheduling & Control Manager
Consulted:
Cluster Technical Services Director
Cluster Scheduling Section Head
Cluster Capital Resource Manager
Informed: Cluster Projects GM
Procedure: ● Ensure that the correct personnel have been identified and there are no
outstanding issues or concerns may prevent working in the project.
● Ensure all personnel identified have the required level of experience and
skills to allow for the successful implementation and completion of the
project.
● Review performance reviews if available from previous projects in order
to ascertain their suitability for the project.
● Review current workload and upcoming projects to ensure this project is
best suited to their skills.
● Approve the selected team.
Procedure: ● Following approval from Cluster Projects GM, begin capturing the
acquired resources for the project.
● Ensure all identified positions have been resourced and confirmed.
● Provide the appropriate Job Profile to every team member.
13.3.4 Procedures
13.3.4.1 PMM-013-HUM-030-010 Carry Out Induction and Objectives Briefing
Procedure: ● Perform Induction and objective briefing to every NWC Projects Team
member.
● Perform PMM induction to the NWC Projects Team member.
● Ensure that objectives are cascaded to individuals in the team.
● Register the performed inductions in (PMF-013-HUM-003 Induction and
Training Register).
Procedure: ● NWC Project Manager shall monitor the performance of NWC Projects
Team members and identify the training needs for each member.
● Based on identified training needs, NWC Project Manager shall nominate
NWC Projects Team members for training.
● NWC Project Manager raise the nominations to Cluster PMO Manager.
● Cluster PMO Manager shall raise the nominations from all cluster
projects to Center of Excellence Director to arrange the suitable training
programs.
NWC Project Manager
Roles: Responsible:
Cluster PMO Manager
Accountable: NWC Project Manager
NWC Projects Team
Consulted:
Cluster PMO Manager
Center of Excellence Director
Informed: Center of Excellence Director
13.4.4 Procedures
13.4.4.1 PMM-013-HUM-035-010 Form Interview Working Group for Second Party
Project Team
Procedure: ● NWC Project Manager shall review the submitted staffing plan in
consultation with:
○ Cluster Technical Service for Design Consultant team.
○ Cluster Scheduling & Control for Supervision team.
○ Supervision Consultant for Contractor team.
● If NWC Project Manager approved the staffing plan, NWC Project
Manager shall create a working group forming decision and raise it to
Cluster Projects GM for approval. The request shall nominate
representatives from the following departments beside NWC Project
Manager:
○ Cluster Technical Services department.
○ Cluster Scheduling & Control department.
○ Cluster Environmental Compliance dept (in design projects and STP
Construction projects)
○ Cluster PMO department.
○ Directorate Construction department.
● Cluster Projects GM shall add to the interview working group any
additional suitable members as required.
● Cluster Projects GM shall approve the request and forming decision and
transmit them to NWC Project Manager for further actions.
NWC Project Manager
Roles: Responsible:
Cluster Projects GM
Procedure: ● Review and approve the report that raised from Interview Working
Group.
● Direct the second party to:
○ mobilize the accepted team members as per the staffing plan.
○ introduce other team members for interviews to fill the vacant
positions as per the staffing plan.
13.6.4 Procedures
13.6.4.1 PMM-013-HUM-050-010 Monitor Final Completion of Project Activities to
Ensure No Unnecessary Delays
Procedure: ● Monitor final completion of project activities and ensure that there is no
unnecessary delays or slippage.
● Continuously review Project Schedule to ensure milestones and dates
are being adhered to and maintained.
● Regularly review ongoing work with Project Team, Supervision
Consultant and Contractor to discuss any concerns or issues regarding
completion and closing of the project, to ensure timely closeout of all
activities.
Procedure: ● At the closure of the project, carryout performance appraisals for NWC
team members associated with the project.
● The appraisal should focus solely on their performance on the project.
● This should be completed in conjunction with Human Resources
Procedure Manual.
● Identify training needs based on performance appraisal/weak points.
Percentage of year-to-
Commitment to date number of
staffing plan of the occupied work man-
1 Monthly 100% 90% < 90%
second party in a days to the year-to-date
project total project work man-
days in the project
13.8 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-013-
HUM Project Human Resource Management).
Table 13-2 Project Human Resource Management forms, templates and guidelines
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-014-COM-010 Plan Project Communications” is elaborated.
● The process “PMM-014-COM-100 Distribute Non-Conformance Report (NCR)” is
revised.
● The process “PMM-005-GEN-090 Internal Communication” is revised and
Change transferred to Communication section as “PMM-014-COM-115 Cascade
Description Objectives”.
● The process “PMM-014-COM-120 Perform Design Performance Reporting” is
revised.
● The process “PMM-014-COM-130 Perform Construction Performance Reporting” is
revised.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This version is developed as an update to the latest version (v2) of the “Project
Communication Management” section in PMM which developed by Faithful + Gould.
The following are the changes:
● Dividing distribute information process into 10 processes according to
communication type, document, sender and receiver.
Change ● Dividing performance reporting process into 2 processes one for design
Description performance reporting and one for construction performance reporting.
● Adding internal-external stakeholder communication plan template.
● Updating responsibilities as per NWC Organization charts.
● Updating KPI’s.
● Updating flowcharts for processes and procedures.
8. Second Parties must create their own management plans (design and/or
construction) including Communications Management Plan Section for the project.
These management plans must comply with the Communications management
requirements defined in the NWC Project Management Plan and must be approved
by NWC during mobilization period.
9. The Communications Management Plans in PMPs of NWC, Design and Construction
must be kept up-to-date throughout the project life cycle.
14.1.3 Flowchart
Figure 14-2 PMM-014-COM-010 Plan Project Communications Flowchart
14.1.4 Procedures
14.1.4.1 PMM-014-COM-010-010 Develop the Communication Management Plan
Section of the Project Management Plan
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Communication Management Plan and must submit it during the
contractual mobilization period” is stated in the NWC Project
Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Communication assessment criteria, which
addresses:
○ the project requirements.
○ the past performance of the bidders.
● Report Visualization
8. Manual Transmittals Project correspondence shall:
● Use the mandated Project templates.
● Address the appropriate contact or group for the relevant organization.
● Use a unique reference number and issued date.
● Use a clear and concise subject line.
● Be authorized by the principal contact or designated authority.
9. The following document details shall be defined when register new documents to the
Enterprise Content Management System (ECMS):
● Project
● Document number
● Title
● Status
● Organization
● Discipline
● Document Type
● Date of registration
● Author of the document
10. The Electronic transmittal shall display these attributes:
● Transmittal number
● The transmittal issue date
● The recipients the transmittal was addressed to
● Reason for Issue
● Response Required Date
● Document attributes (Document Number, Revision, Title and Status)
● Comments/Instructions
11. When issuing the manual transmittal and documents via email the following
information shall be included:
● The reason for Issue should be noted i.e. Issued for Information, Issued for
Review, etc.
● The documents and the associated manual transmittal being issued will either
have a secure link to the transmittal package via the Enterprise Content
Management System (ECMS) or are electronically attached to the email.
● To reduce the cost of tracking the “acknowledgement” copies of transmittals,
consideration should be given to utilizing the “Read Receipt” function within
Microsoft Outlook.
● Documents issued externally are to be in PDF format.
12. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
14.2.3 Flowchart
Figure 14-3 PMM-014-COM-020 Distribute Confidential Correspondence from Consultant/Contractor to
NWC Flowchart
14.2.4 Procedures
14.2.4.1 PMM-014-COM-020-010 Issue the Confidential Correspondence
Procedure: ● Prepare the documents and attachments which will be sent from
Consultant/Contractor to NWC.
● Indicate that the correspondence should be handled as confidential.
● Ensure the proper details are provided as follows:
○ Reference Number (which include Project ID)
○ Date
○ Subject
○ Recipient
○ Attachment (number of pages)
○ “Confidential” indicator to indicate the document is confidential.
● Send hard copy original correspondence to Contractor/Consultant
Project Manager for his review and signature.
● Scan the documents and upload to an Enterprise Content Management
System (ECMS) confidential folder.
● Copy the correspondence and place the copy (hard) in the
Contractor/Consultant filing system.
● Send the hard copy original correspondence to the NWC Project
Document Controller with extra cover page for the “Received” stamp.
Procedure: ● File the signed received document in the confidential filing system.
● Review automatically updated document status via Enterprise Content
Management System (ECMS).
14.3.4 Procedures
14.3.4.1 PMM-014-COM-030-010 Draft the Confidential Correspondence to the
Contractor/Consultant
Procedure: ● Prepare the documents and attachments which will be sent from NWC
to Consultant/Contractor.
● Indicate to the NWC Project Document Controller that the
correspondence should be handled as confidential.
● Send the draft to the NWC Project Document Controller .
Consulted: Originator
Procedure: ● Review the documents and sign if acceptable or return to the originator
for adjusting.
● Return the hard copy original correspondence original to the NWC
Project Document Controller for transmission to Contractor/Consultant
Procedure: ● Scan the documents and upload to the Enterprise Content Management
System (ECMS) confidential folder. Fill up all the necessary fields in the
Enterprise Content Management System (ECMS).
● Send the hard copy original correspondence to Contractor/Consultant
Document Controller with extra cover page for the “Received” stamp.
14.4.3 Flowchart
Figure 14-5 PMM-014-COM-040 Distribute Non-Confidential Correspondence from Consultant to NWC
Flowchart
14.4.4 Procedures
14.4.4.1 PMM-014-COM-040-010 Issue the Non-Confidential Correspondence to NWC
Procedure: ● Prepare the documents and attachments which will be sent from
Consultant to NWC.
● Ensure the proper details are provided:
○ Reference Number (which include Project ID)
○ Date
○ Subject
○ Recipient
○ Attachment (number of pages)
● Send hard copy original correspondence to Consultant Project Manager
for his review and signature.
● Scan the documents and upload to the Enterprise Content Management
System (ECMS).
● Copy the correspondence and place the copy (hard) in the Consultant
filing system.
● Send the hard copy original correspondence original to the NWC Project
Document Controller with extra cover page for the “Received” stamp.
Procedure: ● File the signed received document in the confidential filing system.
● Review automatically updated document status via Enterprise Content
Management System (ECMS).
14.5.4 Procedures
14.5.4.1 PMM-014-COM-050-010 Issue the Non-Confidential Correspondence
Procedure: ● Prepare the documents and attachments which will be sent from
Contractor to NWC
● Ensure the proper details are provided:
○ Reference Number (which include Project ID)
○ Date
○ Subject
○ Recipient
○ Attachment (number of pages)
● Send hard copy original correspondence to Contractor Project Manager
for his review and signature.
● Scan the documents and upload to the Enterprise Content Management
System (ECMS).
● Copy the correspondence and place the copy (hard) in the Contractor
filing system.
● Send the hard copy original correspondence to Consultant Document
Controller with extra cover page for the “Received” stamp.
Consulted: Originator
Consultant Document Controller
Informed:
Contractor Project Manager
14.5.4.2 PMM-014-COM-050-020 Receive the Non-Confidential Correspondence
Procedure: ● File the signed received document in the Consultant filing system.
● Review automatically updated document status via Enterprise Content
Management System (ECMS)
14.6.4 Procedures
14.6.4.1 PMM-014-COM-060-010 Draft the Non-Confidential Correspondence to the
Consultant
Procedure: ● Prepare the documents and attachments which will be sent from NWC
to Consultant.
● Send the draft to the NWC Project Document Controller.
Consulted: Originator
Procedure: ● Review the documents and sign, if acceptable or return to the originator
for adjusting.
● Return the hard copy original correspondence to the NWC Project
Document Controller for transmission to the Consultant.
Procedure: ● Scan the documents and upload to the Enterprise Content Management
System (ECMS). Fill-up all the necessary fields in the Enterprise Content
Management System (ECMS).
● Send the hard copy original correspondence to Consultant Document
Controller with extra cover page for the “Received” stamp.
14.7.4 Procedures
14.7.4.1 PMM-014-COM-070-010 Draft the Non-Confidential Correspondence to the
Contractor
Procedure: ● Prepare the documents and attachments which will be sent from NWC
to Contractor.
● Send the draft to the NWC Project Document Controller.
Consulted: Originator
Procedure: ● Review the documents and sign, if acceptable or return to the originator
for adjusting.
● Return the hard copy original correspondence to the Document
Controller for transmission.
Procedure: ● Scan the documents and upload to the Enterprise Content Management
System (ECMS) Fill-up all the necessary fields.
● Send the hard copy original correspondence to Contractor Document
Controller with extra cover page for the “Received” stamp.
Consulted: Originator
14.8.4 Procedures
14.8.4.1 PMM-014-COM-080-010 Draft the Non-Confidential Correspondence to the
Contractor
Procedure: ● Prepare the documents and attachments which will be sent from
Consultant to Contractor.
Consulted: Originator
Procedure: ● Review the documents, make coordination with the NWC Project
Manager if required and sign, if acceptable or return to the originator for
adjusting.
● Return the hard copy original correspondence to the Document
Controller for transmission to Contractor.
Procedure: ● Scan the documents and upload to the Enterprise Content Management
System (ECMS) Fill-up all the necessary fields
● Send the hard copy original correspondence to Contractor Document
Controller with extra cover page for the “Received” stamp.
Consulted: Originator
Contractor Document Controller
Informed:
NWC Project Manager
14.8.4.5 PMM-014-COM-080-050 Receive the Non-Confidential Correspondence
14.9.3 Flowchart
Figure 14-10 PMM-014-COM-090 Distribute Submittals for Approval Flowchart
14.9.4 Procedures
14.9.4.1 PMM-014-COM-090-010 Issue the Submittal
Consulted: Originator
Procedure: ● Scan the submittal and upload to the Enterprise Content Management
System (ECMS) Fill-up all the necessary fields.
● Send the hard copy original submittal to Contractor Document Controller
with extra cover page for the “Received” stamp.
● File the signed received submittal in the Consultant filing system.
● Update the submittal register.
● Review automatically updated document status via Enterprise Content
Management System (ECMS).
2. ANY BOQ ITEM THAT RELATED TO OPEN NCR SHALL NOT BE PAID UNLESS
THE OPEN NCR BE CLOSED.
3. All corrective and preventive actions must be formally proposed on the associated
non-conformance report and approved in principle before implementation.
4. Corrective action is designed to remedy the observed non-conformance and also to
treat its root cause in order to prevent recurrence.
5. Preventive actions are designed to eliminate the causes of potential non-
conformances, which are related to the actual non-conformance report and its root
cause.
6. A non-conformance report must not be closed until the approved corrective and
preventive actions have been taken, and the effectiveness of the actions has been
reviewed.
7. All corrective and preventive actions related to PMM application must be recorded in
a central register by the Quality Assurance Director.
14.10.3 Flowchart
Figure 14-11 PMM-014-COM-100 Distribute Non-Conformance Report (NCR) Flowchart
14.10.4 Procedures
14.10.4.1 PMM-014-COM-100-010 Draft the Non Conformance Report (NCR)
Procedure: ● Identify and compile Non Conformance Report (NCR) using (PMF-014-
COM-013 Non Conformance Report NCR).
● NCR can be for QA, QC or HSE.
● NCR originators include but not limited to inspectors, auditors or
reviewers.
Procedure: ● Scan the NCR and upload to the Enterprise Content Management
System (ECMS).
● Send the hard copy original NCR to Contractor / Design Consultant
Document Controller .
● Send extra cover page for the receive stamp copy.
● Send copy to the NWC Project Manager for his information.
Procedure: ● Review and evaluate the NCR and its attached documents.
● Discuss findings and propose actions.
● Give the NCR to the Document Controller for submission to the
Consultant.
● Submit the NCR with proposed corrective and preventive actions to
Supervision Consultant (in construction projects) / Cluster (in design
projects) by Contractor / Supervision Consultant Document Controller .
Contractor Project Manager (in construction projects)
Roles: Responsible:
Design Consultant Project Manager (in design projects)
Contractor Project Manager (in construction projects) /
Accountable:
Design Consultant Project Manager (in design projects)
Contractor Quality Manager (in construction projects)
Consulted:
Contractor HSE Manager (in construction projects)
Design Consultant Quality Manager (in design projects)
Design Consultant HSE Manager (in design projects)
Supervision Consultant Document Controller (in
Informed:
construction projects)
Cluster Document Control Section Head (in design project)
to the relevant project stakeholders, and to ensure that proper records are made of all such
communications.
14.11.2 Policies
Policies for this process are as in paragraph (12.2.2 Policies).
14.11.3 Flowchart
Figure 14-12 PMM-014-COM-110 Distribute Request for Information (RFI) Flowchart
14.11.4 Procedures
14.11.4.1 PMM-014-COM-110-010 Issue the Request for Information (RFI)
Procedure: ● Originator shall prepare the RFI and attachments using (PMF-014-COM-
014 Request for Information).
● Contractor Document Contractor shall check the details:
○ Reference Number (which include Project ID)
○ Revision
○ Date
○ Document Description
○ Attachment (number of pages)
● Contractor Document Contractor shall send hard copy original RFI to
Contractor Project Manager for his review and signature.
● After Contractor Project Manager signature, Contractor Document
Contractor shall scan the RFI and upload to the Enterprise Content
Management System (ECMS) related workflow.
● Contractor Document Contractor shall copy the RFI and place the copy
(hard) in the Contractor filing system.
● Contractor Document Contractor shall send the hard copy original RFI to
Consultant Document Controller with extra cover page for the “Received”
stamp.
Consulted: Originator
Procedure: ● Review the RFI and provide the information requested, if required,
discuss with the NWC Project Manager.
● Sign the RFI.
● Return hard copy original RFI to the Document Controller for issue to the
Contractor.
Procedure: ● Scan the RFI and upload to the Enterprise Content Management System
(ECMS) Fill-up all the necessary fields.
● Send the hard copy original RFI to Contractor Document Controller with
extra cover page for the “Received” stamp.
● File the signed received RFI in the Consultant filing system.
● Review automatically updated document status via Enterprise Content
Management System (ECMS).
14.12.4 Procedures
14.12.4.1 PMM-014-COM-115-010 Cascade Objectives
2. The format of the monthly progress report must be agreed with the Design Consultant
at his kick-off meeting with NWC, held during his mobilization period after contract
award.
3. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
14.13.3 Flowchart
Figure 14-15 PMM-014-COM-120 Perform Design Performance Reporting Flowchart
14.13.4 Procedures
14.13.4.1 PMM-014-COM-120-010 Conduct Weekly Design Progress Meetings
Procedure: ● Conduct weekly meetings with all relevant team members including
Design Consultant to discuss design progress using (PMF-014-COM-
021 Weekly Meeting Agenda).
● Highlight any issues or concerns which may affect design progress.
● Write and distribute MOM using (PMF-014-COM-022 Weekly Meeting
Minutes).
Cluster Technical Services Director
Roles: Responsible:
NWC Project Manager
Accountable: NWC Project Manager
Design Consultant
Consulted:
Cluster scheduling section head
NWC Project Team
Informed:
Design Consultant
Procedure: ● Conduct monthly meetings with all relevant team members to discuss
progress using as applicable the (PMF-014-COM-023 Monthly Progress
Meeting Agenda).
● Highlight any issues or concerns which may affect design progress.
● Write and distribute MOM using as applicable the (PMF-014-COM-024
Monthly Progress Meeting Minutes).
Cluster Technical Services Director
Roles: Responsible:
NWC Project Manager
Accountable: NWC Project Manager
Design Consultant
Consulted:
Cluster scheduling section head
14.14.4 Procedures
14.14.4.1 PMM-014-COM-130-010 Conduct Construction Weekly Progress Meeting
Procedure: ● Conduct weekly meetings with all relevant team members to discuss
Construction progress.
● Use the weekly meeting agenda (PMF-014-COM-021 Weekly Meeting
Agenda).
● Highlight any issues or concerns which may affect construction progress
including quality and HSE.
● Write and distribute MOM using (PMF-014-COM-022 Weekly Meeting
Minutes).
Guidelines: ● The Monthly Report shall include but not limited to the following:
○ Updated “Primavera P6” schedule
○ Invoice summary log
○ Variations Order summary
○ Progress curves
○ Earned value calculation
○ Forecasts
○ Identification of risks and issues
○ Identification of potential claims
○ Status of submitted claims
○ Summary cost / budget information
○ Critical Item Action Summary
○ NCR Status
○ HSE Summary
Procedure: ● Conduct monthly meetings with all relevant team members to discuss
progress using (PMF-014-COM-023 Monthly Progress Meeting
Agenda).
● Highlight any issues or concerns which may affect construction progress.
● Write and distribute MOM using (PMF-014-COM-024 Monthly Progress
Meeting Minutes).
Procedure: ● Ensure all required documentation and relevant information and issues
have been included.
● Develop and distribute management reports to all relevant parties.
Procedure: ● Collect relevant cost data for all cluster projects using (PMF-011-COS-
019 Monthly Cost Report Input Forms).
● Develop Monthly Cluster Cost Report (PMF-011-COS-020 Monthly
Cluster Cost Report Template).
● Submit Monthly Cluster Cost Report to Scheduling & Control GM.
Overdue
Year-to-date number of
responses to
2 overdue responses to Monthly 0 1 >1
Submittals for
Submittals for Approval.
Approval
Year-to-date number of
late submissions of the
Late submission of
monthly project
project progress
5 progress reports by Monthly 0 2 >2
report by
contractor in the project
contractor
against the agreed
submission date.
Year-to-date number of
late submissions of the
Late submission of
monthly executive
executive
summaries of the
summary of project
6 monthly project Monthly 0 2 >2
progress report by
progress reports by
supervision
supervision consultant
consultant
in the project against the
agreed submission date.
Year-to-date number of
late submissions of the
Late submission of
monthly project
project progress
7 progress reports by Monthly 0 6 >6
report by
contractor in the cluster
contractor
against the agreed
submission dates.
Year-to-date number of
late submissions of the
Late submission of monthly executive
executive summaries of the
summary of project monthly project
8 Monthly 0 6 >6
progress report by progress reports by
supervision supervision consultant
consultant in the cluster against the
agreed submission
dates.
14.17 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-014-
COM Project Communications Management).
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The Value Management is eliminated from this section as it is covered in Value
Engineering Section.
● The process “PMM-015-RIS-010 PMM-013-RIS-010 Risk Management at Portfolio
Level” is elaborated.
● The process “PMM-015-RIS-020 Plan Project Risk Management” is elaborated.
● The process “PMM-015-RIS-030 Identify Risks at Project Level” is elaborated.
● The process “PMM-015-RIS-040 Qualitative Risk Analysis at Project Level” is
Change elaborated.
Description ● The process “PMM-015-RIS-050 Quantitative Risk Analysis at Project Level” is
elaborated.
● The process “PMM-015-RIS-060 Plan Risk Responses at Project Level” is
elaborated.
● The process “PMM-015-RIS-070 Implement Risk Responses at Project Level” is
elaborated.
● The process “PMM-015-RIS-080 Monitor Risk Responses at Project Level” is
elaborated.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This section is developed as an update to “Risk” section in first version the Project
Management Manual (PMM) which developed by Faithful + Gould. The following are
the changes:
● Separating a process for risk management at program/portfolio level.
● Separating a process for risk management at project level.
● Adding guidelines for risk tolerance considerations.
● Adding guidelines for including of risk monitoring and review in risk
management planning.
● Re-arranging procedures among processes.
Change
● Referring to forms and templates’ names and numbers inside the procedures.
Description
● Adding guidelines for stakeholders / projects interfaces.
● Separating process for implementing risk response plans.
● Adding guidelines for closing risk registers.
● Adding Stakeholder Register Template.
● Updating and simplifying flowcharts.
● Updating responsibilities as per NWC organization charts.
● Updating KPI’s.
● Updating forms and templates.
15.1.4 Procedures
15.1.4.1 PMM-015-RIS-010-010 Identify Risks at Cluster Portfolio Level
Procedure: ● New asset needs and wants are described in the Business Case
documents.
● Cluster Risk Section Head compiles and distributes relevant information
to the planned attendees of workshop No.1.
● The introduction of the new asset needs shall be considered before the
workshop in the context of the following:
○ Current risk appetite of NWC
○ Current risk tolerance identification criteria in NWC
○ Lessons learned from previous projects
○ Existing Portfolio Risk Registers (PMF-015-RIS-017 Portfolio Risk
Register Template)
○ (PMF-015-RIS-013 Guide to Hierarchical Sources of Risk)
● The planned attendees send their completed notes to the Cluster Risk
Section Head, in a timely manner on or before the due date advised by
the Risk Section Head.
● The completed notes are assessed by the Cluster Risk Section Head.
● Workshop agenda is developed and distributed to invited individuals,
with any information considered necessary in order to ensure that the
invited individuals are well prepared to attend the workshop.
● Set a date for the workshop.
● The workshop is carried out on the arranged date, in accordance with
the agenda.
● See (PMF-015-RIS-014 Examples of Risk Management Tools and
Techniques).
● Required outputs of the workshop are:
○ a formal workshop report.
○ updated (PMF-015-RIS-017 Portfolio Risk Register).
showing the agreed action plans which nominated Risk Owners must
develop in the next step.
● Perform Quantitative Risk Analysis (if required).
● Forward the cluster portfolio risk register to the HQ risk management
lead.
● HQ risk management lead shall review, evaluate and update the
company wide projects portfolio risk register accordingly.
Cluster Risk Section Head
Roles: Responsible:
Risk Management Lead
Accountable: Cluster Scheduling & Control Manager
Procedure: ● Risk owners nominated in the workshop report develop written action
plans in order to describe steps for opportunity adoption/exploitation and
for associated risk mitigation.
● Each action plan must be formally approved by the cluster Risk Section
Head and with consolidation of details into the Portfolio Risk Register.
● At a minimum, the risk treatment plans will contain:
○ The justification and rationale for selecting the treatment activities.
○ The treatment activity implementation resource requirements (i.e.
cost, time, manpower and materials) and targeted timing for
implementation of the treatment activities and evaluation.
○ The named individuals who will be responsible and accountable for
the treatment activities.
○ The expected outcomes in terms of benefits.
Roles: Responsible: Risk Owners (as nominated in the workshop no. 1 report)
ii. include an approved risk workshops schedule as per risk workshop criteria
mentioned below.
4. The project risk register at initial planning stage must consider:
i. Project assumptions.
ii. Design options.
iii. known risks identified during the FYPPP stage (not a part of PLC).
5. Every individual project risk register is managed, throughout the project lifecycle, by
NWC Project Manager with support of the Cluster Risk Section Head. NWC Project
Manager is dully responsible of Project risk register. He must:
i. ensure that the project risk register is continuously kept up-to-date throughout the
project lifecycle.
ii. report it to PMO at HQ on monthly basis.
6. The risk workshops conducting criteria are as follows:
i. For projects of values ≥ SAR100 Million risk workshop conducting is mandatory
at the beginning of every project stage in the project lifecycle.
ii. For projects of values ≤ SAR100 Million risk workshop conducting is mandatory
at the beginning of:
● Initial planning stage
● Design Stage (in design-Bid-build PLC)
● Construction Stage (in design-Bid-build PLC)
● Design and Construction stage (in Design & Build PLC)
For the remaining stages risk workshop conducting is strongly recommended
depending on the project size, complexity, criticality, strategic importance and
relationship with other projects.
7. All risk workshops in the project, whether mandatory or not, must be stated in the Risk
Management Plan Section of the Project Management Plan (PMP) and tender
documents of design and construction. Risk workshops that stated in the PMP must
be implemented as per stated.
8. Second Parties must create their own management plans (design and/or
construction) including Risk Management Plan Section for the project. These
management plans must comply with the Risk management requirements defined in
the NWC Project Management Plan and must be approved by NWC during
mobilization period.
9. The Risk Management Plans in PMPs of NWC, Design and Construction must be kept
up-to-date throughout the project life cycle.
10. NWC project team, Design Consultant, Supervision Consultant and Contractor are
responsible for continuously monitoring for any potential risk during the project
lifecycle regardless of the ongoing stage. Every potential risk must be immediately
reported to NWC Project Manager. The five processes after the process “PMM-015-
RIS-030 Identify Risks at Project Level” shall continually be performed on urgent basis
for the identified risk once it is identified.
11. When conduct a risk workshop, the six processes after this process “PMM-015-RIS-
020 Plan Project Risk Management at Project Level” shall continually be performed
on urgent basis.
i. Process “PMM-015-RIS-030 Identify Risks at Project Level” and “PMM-015-RIS-
040 Qualitative Risk Analysis at Project Level” shall be performed as part of the
risk workshops. Every risk workshop shall include the outputs of these two
processes.
ii. Processes“PMM-015-RIS-050 Quantitative Risk Analysis at Project Level” and
“PMM-015-RIS-060 Plan Risk Responses at Project Level” shall be performed
after the risk workshops utilizing the workshop outputs.
iii. Processes “PMM-015-RIS-070 Implement Risk Responses at Project Level” and
“PMM-015-RIS-080 Monitor Risk Responses at Project Level”.
Figure 15-3 Relation between Risk Process and Risk Workshops
15.2.3 Flowchart
Figure 15-4 PMM-015-RIS-020 Plan Project Risk Management at Project Level Flowchart
15.2.4 Procedures
15.2.4.1 PMM-015-RIS-020-010 Develop the Risk Management Plan Section of the
Project Management Plan
Cluster Projects GM
Consulted:
Business Unit Construction Director
Risk Management Manager
Cluster PMO Manager
Informed:
Cluster Projects GM
Risk Management Manager
15.2.4.2 PMM-015-RIS-020-020 Approve the Risk Management Plan Section of Project
Management Plan
Procedure: ● Review and Approve the Risk Management Plan Section of Project
Management Plan.
● Document and track the results of the reviews till they are closed out
satisfactorily.
● The NWC Project Manager shall approve using (PMF-014-COM-004
Document Approval Form).
● Ensure that only changes approved through (PMM-007-INT-060
Variation Control) process are implemented.
Procedure: ● Develop Project Risk Management Plan Section in the Project Design
Management Plan.
● Ensure that the Project Risk Management Plan Section in the Project
Design Management Plan is in alignment with the Project Risk
Management Plan Section in the NWC Project Management Plan.
● Consult with NWC Project Manager and Cluster Technical Services
Director about the development of the Project Risk Management Plan
Section.
● Include the Project Risk Management Plan Section in the Project Design
Management Plan to be approved as part of the Project Design
Management Plan.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Risk Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Risk assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
reported to NWC Project Manager. The five processes after the process “PMM-015-
RIS-030 Identify Risks at Project Level” shall be performed to the identified risk once
it is identified.
5. Risk workshops must involve the personal contribution and attendance of all relevant
stakeholders, as far as practicable.
6. NWC Project Managers must not act as the facilitator for Risk workshops on their
project. The workshops must be facilitated by specialist (e.g. the Cluster Risk section
Head or may be an external Consultant if the project is particularly complex, novel or
strategic/critical). The Project Manager must attend the workshops for monitoring and
controlling the actions agreed in the workshop and delegated to named action owners.
7. It is important to ensure that a thorough risk identification is undertaken by conducting
additional workshops at the beginning of each project stage and reviewed regularly,
especially when there are approved variations, so that any new or emerging risks can
be identified for subsequent analysis in a timely manner.
15.3.3 Flowchart
Figure 15-5 PMM-015-RIS-030 Identify Risks at Project Level Flowchart
15.3.4 Procedures
15.3.4.1 PMM-015-RIS-030-010 Identify and Analyze Objective, Issues, Constraints &
Assumptions
Procedure: ● Ensure the following items are integrated into the tender documents:
○ Updated NWC Project Management Plan (PMP) that includes an
updated Risk Management Plan Section.
○ Updated Project Risk Register highlighting the risks transferred to
the Design Consultant / Contractor.
● Review bidder technical proposals for inclusion of transferred risks.
15.4.3 Flowchart
Figure 15-6 PMM-015-RIS-040 Qualitative Risk Analysis at Project Level Flowchart
15.4.4 Procedures
15.4.4.1 PMM-015-RIS-040-020 Risk Analysis and Evaluation
15.5.4 Procedures
15.5.4.1 PMM-015-RIS-050-010 Risk Scoring of Cost and Schedule Impacts
● Monitoring and reviewing of project risks and the associated action plans, in
conjunction with the “owners” on a regular basis (at least once a month) and
inclusion of the outcomes in their regular Project Manager progress reports.
● Escalation of concerns regarding risk levels to the Business Unit Construction
Director and to the supporting Technical Services staff in the Cluster.
● Management of the updates to the Project Risk Register for the project.
● Ensuring that the Consultant(s) and Contractor(s) engaged on the project are
made aware of NWC’s requirements for Risk Management, through inclusion
of the Project Management Manual and the Project Management Plan in the
tender document.
3. Risk Owners (can be anyone within the project team including Project Manager or
more senior management, where appropriate) are individuals within the team
accountable for the management of a particular risk and are responsible for:
● Implementing the Risk Management process for risks allocated to them.
● Evaluating risks and assigning action owners (in conjunction with the Project
Manager).
● Monitoring and supplying regular risk status reports to the Project Manager.
● Reporting new risks to the Cluster Risk Management Lead for addition to the
Project Risk Register.
● Agreeing Risk Management responses with action owners.
● Monitoring the status of risks assigned to them and the associated
management plans.
● Escalating risks to a higher level where they feel they have insufficient authority
or ability to effectively manage a particular risk.
4. Risk Owners must have suitable knowledge and adequate authority in order to make
decisions and act appropriately to effectively manage risks assigned to them.
5. For the majority of risks, the NWC Project Manager will act as Risk Owner unless it is
outside his area of expertise or authority.
6. Staff should be trained in the importance of risk action ownership, and of effective
communication and collaboration in order to mitigate threats and to exploit
opportunities.
7. A contingency plan (or Fallback Plan) can be developed for implementation if the
selected strategy turns out not to be fully effective or if an accepted risk occurs.
8. Secondary Risks should also be identified and they are risks that arise as a direct
result of implementing a risk response.
15.6.3 Flowchart
Figure 15-8 PMM-015-RIS-060 Plan Risk Responses at Project Level Flowchart
15.6.4 Procedures
15.6.4.1 PMM-015-RIS-060-010 Prepare Risk Response Plan
Procedure: ● After risk evaluation and analysis, each identified individual risk shall be
assigned:
○ A “Risk Owner” who is responsible for developing Risk Response
Plan.
○ One response plan which shall be implemented and monitored to
address the risk.
○ A “Response Plan Owner” who is responsible for managing the risk
response plan (developing, implementing and monitoring).
○ “Activity Owners” who shall be one activity owner for each activity in
the response plan. He shall be responsible for implementing the
activity.
● Response plan of every risk shall be documented in the Project Risk
Register.
● The objective of developing and implementing a response plan is to
reduce the likelihood and impact of negative risks (threats) and increase
them for positive risks (opportunities). This objective is achieved by:
○ Identifying targeted risk level for every risk that to be achieved after
implementing its response Plan. This shall be followed by that every
targeted risk level shall be assigned a:
- Required Response
- Response Urgency
Procedure: ● The Design Consultant shall include relevant risk response activities in
his schedule for Design.
● The submitted schedule by Design Consultant shall be reviewed and
approved by Cluster Scheduling Section Head ensuring the inclusion of
risk mitigation activities.
● Records of document approval/rejection must be retained in the Project
Filing System by the Cluster Document Control Section Head.
● The Project risk register shall continuously be updated accordingly.
Procedure: ● The Contractor shall include relevant risk response activities in his
schedule for Construction.
● The submitted schedule by Contractor shall be reviewed and approved
by Cluster Scheduling Section Head ensuring the inclusion of risk
response activities.
● The Project risk register shall continuously be updated accordingly.
15.7.3 Flowchart
Figure 15-9 PMM-015-RIS-070 Implement Risk Responses at Project Level Flowchart
15.7.4 Procedures
15.7.4.1 PMM-015-RIS-070-020 Conduct Risk Response According to the Approved
Risk Response Plan
Procedure: ● The Design Consultant / Contractor / NWC Project Team shall perform
the planned risk responses following the approved risk response
schedule.
● Implementing every planned risk response action shall be led by the
action owner.
● The action owner shall report implementation progress to his Project
Manager who ultimately shall report and discuss it to NWC Project
Manager in the weekly progress meeting.
● The responsibility for the:
○ Actual realization of the added benefits.
○ Omission of unnecessary costs.
○ Treatment/mitigation of the specified Risks
will reside with the respective Risk Owner and their identified Action
Owners with ultimate responsibility residing with the Project Manager.
● Consider any further risks.
● The Project risk register shall continuously be updated accordingly.
Design Consultant
Roles: Responsible:
Contractor
NWC Projects Team
Accountable: NWC Project Manager
Cluster Value Engineering Specialist
Consulted:
Cluster Technical Services Director
Cluster Risk Section Head
Supervision Consultant
Risk Management Lead
Informed:
Value Engineering Director
Cluster Contracts Administration Section Head
15.8.3 Flowchart
Figure 15-10 PMM-015-RIS-080 Monitor Risk Responses at Project Level Flowchart
15.8.4 Procedures
15.8.4.1 PMM-015-RIS-080-010 Monitor Project Risks
Procedure: ● Through project life cycle, monitor project risks through the following:
○ Monitoring the implementation of agreed upon risk response plan.
○ Tracking identified risks.
○ Evaluating risk process effectiveness through the project.
○ Identifying and analyzing new risks.
● This procedure enables project decisions to be based on current
information about overall project risk exposure and individual project
risks.
● The updated project risk register shall be submitted monthly to PMO GM
for review.
● The Project risk register shall continuously be updated accordingly.
Cluster Risk Section Head
Roles: Responsible:
Design Consultant (if assigned)
Supervision Consultant (if assigned)
Contractor (if assigned)
Accountable: NWC Project Manager
Procedure: ● Every stage gate review shall include checking risks status through
Project Risk Register.
● The Project risk register shall continuously be updated accordingly.
Procedure: ● Each Design Consultant / Contractor shall submit his own updated
Project Risk Register at the end of Design stage/Handover and Closeout
Stage.
● This activity is carried out in support of (PMM-016-PRO-100 Contract
Closure) process.
● The updated Risk register shall be submitted monthly to PMO GM for
review.
Cluster Risk Section Head
Roles: Responsible:
Design Consultant
Supervision Consultant
Contractor
Accountable: NWC Project Manager
Guidelines: ● The information contained within the Project Risk Register will be
updated to reflect:
○ The fact that the risk was closed
○ Date when the risk was closed
○ Why the risk was closed
○ If any residual or emerging risks were identified, and what those
risks were.
○ Effectiveness of the response plan (succeed, failed, partial success)
Year-to-date number of
missing or overdue Risk
Timely Risk workshop reports in the
1 Monthly 3 6 >6
workshop reports cluster against the
agreed schedule of
workshops
Year-to-date number of
Timely completion late or overdue Risk
of risk response response actions that
2 actions recorded in recorded in the project Monthly 0 3 >3
the project Risk risk register in the
register project against the
recorded action date.
Year-to-date number of
Stage Gate Review
stage gate reviews that
failures due to
3 fails in the cluster due to Quarterly 0 2 >2
unsatisfactory Risk
unsatisfactory Risk
Management
management.
15.10 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-015-
RIS Project Risk Management).
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-016-PRO-010 Plan Purchases and Acquisitions at Portfolio
Level” is revised.
● The process “PMM-016-PRO-020 Plan Project Procurement Management” is
elaborated.
● The process “PMM-016-PRO-025 Acquire Project Land” is added.
● The process “PMM-016-PRO-030 Prepare Tender Documents” is elaborated.
● The process “PMM-016-PRO-040 Select a Bidder” is elaborated.
● The process “PMM-014-PRO-050 Site Handover to Contractor and Consultant Work
Change Commencement” is transferred to Integration section and revised.
Description
● The process “PMM-014-PRO-060 Conduct Project Kick Off Meeting” is transferred
to Integration section and revised.
● The process “PMM-016-PRO-070 Contract Administration” is revised.
● The process “PMM-016-PRO-080 Suspend and Resume Project” is revised.
● The process “PMM-016-PRO-085 Change Project Status from Partial Suspension
to Total Suspension” is added.
● The process “PMM-016-PRO-090 Withdraw Project” is elaborated.
● The process “PMM-016-PRO-100 Contract Closure” is revised.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
The process described in this section is intended to ensure compliance with current versions of the
following NWC internal documents Supply Management Policy and Procedure Manual.
16.1.3 Flowchart
Figure 16-2 PMM-PRO-010 Plan Purchases and Acquisitions at Portfolio Level Flowchart
16.1.4 Procedures
16.1.4.1 PMM-016-PRO-010-010 Summarize the Requirements of Portfolio High
Volume, Long Lead and Special Materials
Procedure: ● Review the Five-Year Projects Portfolio Plan to identify the planned
projects.
● Summarize the Requirements of Portfolio:
○ High Volume Materials
○ Long Lead Materials
○ Special Materials.
● Add the new material requirements of planned projects (i.e. estimated
quantities and costs) to the material requirements of the ongoing projects
which are not awarded to Contractors yet.
● Refer to the following to support the exercise:
○ Approved Suppliers List
○ Material Requirements Database
○ Cost Database
○ Portfolio Risk Register
● Produce a summary report for each cluster showing the requirements of
different materials, highlighting the high-volume items, the long lead
items and the specialty items.
● The “Clusters Projects Support Team” shall sum the total material (high-
volume, long lead and specialty items) requirements list for the whole
Portfolio and forward to the Portfolios Strategic Planning & Spending
Efficiency Director.
● The Portfolios Strategic Planning & Spending Efficiency Director shall
review the material (high-volume, long lead and specialty items)
requirements list and forward to Capital Projects Strategic Planning GM
who shall review and forward it to the Supply Chain GM.
Cluster Quantity Survey Lead
Roles: Responsible:
Cluster Scheduling Section Head
Cluster Technical Services Director
Accountable: Cluster Projects GM
Portfolios Strategic Planning & Spending Efficiency
Consulted:
Director
Cluster Strategic Planning Manager
Informed:
Portfolios Strategic Planning & Spending Efficiency
Director
Supply Chain GM
Capital Projects Strategic Planning GM
Procedure: ● Review the Five-Year Projects Portfolio Plan to identify the planned
projects.
● Refer to the following to support the exercise:
○ Approved Suppliers List.
○ Contractor Evaluation Reports, Consultant Evaluation Reports, and
Portfolio Risk Register.
● Produce a summary report of the cluster contracting requirements,
highlighting the number and nature of different contract types, any
perceived shortages in local capacity and any overseas options required
to supplement local resources. Submit the report to the Portfolios
Strategic Planning & Spending Efficiency Director.
● The Portfolios Strategic Planning & Spending Efficiency Director shall
review and assemble the summary reports of the contracting
requirements received from clusters, and produce a companywide report
and forward the report to the Supply Chain GM and Capital Projects
Strategic Planning GM.
Cluster Strategic Planning Manager
Roles: Responsible:
Cluster Scheduling Section Head
Cluster Contracts Administration Section Head
Accountable: Cluster Projects GM
Cluster Supply Chain Manager
Consulted:
Supply Chain GM
Portfolios Strategic Planning & Spending Efficiency
Director
Cluster Projects GM
Informed:
Portfolios Strategic Planning & Spending Efficiency
Director
Supply Chain GM
Capital Projects Strategic Planning GM
16.1.4.3 PMM-016-PRO-010-030 Review the Reports for Strategic Recommendations
Procedure: ● Since strategic procurement decisions may significantly affect the overall
performance and cash flow of the business, the requirements reports
must be reviewed by the related senior management team of the
business.
● The senior management team meets to discuss the reports’
recommendations regarding which material will be included in
construction’s scopes and which material will be purchased directly by
NWC.
● All strategic decisions made during the meeting affecting project
procurement methods are communicated to the Clusters.
Capital Projects & Technical Services VP
Roles: Responsible:
Shared Services VP
Chief Financial Officer
Procedure: ● The Portfolio Risk Register shall be updated accordingly by the Risk
Management lead defining all required related actions and shall be
communicated to all clusters.
● Ensure that each risk has an action plan and that action plan owners are
made aware of their action requirements and are kept under review for
the implementation period set by the senior management team.
● Some procurement-related action plans may require additional value
management workshops. This must be clearly stated in the register so
not to be overlooked later in the design stages of the project and before
procurement decisions are finalized for the project.
Monitoring & Strategic Reporting Lead
Roles: Responsible:
Risk Management Manager
Accountable: Capital Projects Strategic Planning GM
Capital Projects Strategic Planning GM
Consulted:
Scheduling & Control GM
Strategic Planning Manager
Capital Projects Strategic Planning GM
Informed:
Cluster Projects GM
Cluster Strategic Planning Manager
16.2 PMM-016-PRO-020 Plan Project Procurement Management
16.2.1 Objective
The objective of this process is to plan how NWC shall enter in a contractual relationship with
a second party. It includes describing the activities that Capital Projects Department shall
perform before, during and after the contract duration.
It also targets to standardize the relationship with the relevant stakeholders (mainly Supply
Chain department).
16.2.2 Policies
Policies for this process are as follows:
defined in the NWC Project Management Plan and must be approved by NWC during
mobilization period.
13. The Procurement Management Plans in PMPs of NWC, Design and Construction
must be kept up-to-date throughout the project life cycle.
14. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
16.2.3 Flowchart
Figure 16-3 PMM-016-PRO-020 Plan Project Procurement Management Flowchart
16.2.4 Procedures
16.2.4.1 PMM-016-PRO-020-010 Develop the Procurement Management Plan Section
of the Project Management Plan
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Procurement Management Plan and must submit it during the
contractual mobilization period” is stated in the NWC Project
Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Procurement assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
16.3.4 Procedures
16.3.4.1 PMM-016-PRO-025-010 Request for Land Acquisition
Procedure: ● NWC Project Manager shall receive from General Services Department
the land acquisition documents.
● NWC Project Manager shall add these documents to the “Request for
Proposal” of the design tendering and the construction tendering.
● If land acquisition process had obstacles, NWC project manager shall
escalate the issue.
ix. Special Conditions Deviation Request (if required) (for Design projects and
Construction projects)
x. Land Acquisition (for Construction projects)
xi. Geotechnical Soil Report (for Construction projects)
xii. External Authorities Approvals (as applicable such as EIA) (for Design and
Construction projects)
2. Every capital project must have a separate Purchase Requisition (PR).
3. Before forwarding tender documents to supply chain department, a Project Pre-
Tender Review Form must be filled and signed from related parties. It must be
included in the forwarded tender documents.
4. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
16.4.3 Flowchart
Figure 16-5 PMM-016-PRO-030 Prepare Tender Documents
16.4.4 Procedures
16.4.4.1 PMM-016-PRO-030-010 Prepare Request for Proposal (RFP) for Design or
Construction Tender
● The RFP Package shall include but not limited to (the minimum
requirements):
○ Approved Business Case (for Design projects, Construction projects
and Design & Build projects)
○ Project Scope (for Design projects, Construction projects and
Design & Build projects)
○ Design Drawings (for Construction projects and Design & Build
projects)
○ Specifications (as per Standard Specifications) (for construction
projects and Design & Build projects)
○ Bill of Quantities (as per Standard BOQ) (for Construction projects
and Design & Build projects)
○ Project Level 1 Schedule (for Design projects, Construction projects
and Design & Build projects)
○ Cost Estimate Class 4 (for Design projects)
○ Cost Estimate Class 3 (for Design & Build projects)
○ Cost Estimate Class 2 (for Construction projects)
○ Special Conditions Deviation Request (if required) (for Design
projects, Construction projects and Design & Build projects)
○ Land Acquisition (for Construction projects and Design & Build
projects)
○ Geotechnical Soil Report (for Construction projects and Design &
Build projects)
○ External Authorities Approvals (as applicable such as EIA) (for
Design projects, Construction projects and Design & Build projects)
● Every component of the RFP must, before consolidation at level cluster,
be separately:
○ Prepared
○ Reviewed
○ Approved
● Cluster Projects GM shall endorse the RFP using (PMF-016-PRO-008
RFP Approval Form) then raise it to the Technical Services GM for
approval.
● See (PMF-016-PRO-036 Tender for Construction Process Flow in
Governance Document).
NWC Project Manager
Roles: Responsible:
Cluster Technical Services Director
Cluster Projects GM
Accountable: Cluster Projects GM
16.4.4.2 PMM-016-PRO-030-020 Approve the Request for Proposal (RFP) for Design
or Construction Tender
Procedure: ● Review and approve the Request for Proposal (RFP) for Design or
Construction Tender within 7 days from request submission.
● Return the RFP to NWC Project Manager at cluster.
Procedure: ● Capital Projects & Technical Services VP shall review the request and
consult Projects GMs.
● Capital Projects & Technical Services VP shall endorse and raise the
request to CEO.
Procedure: ● CEO shall review and transmit the request to Board of Directors.
● Board of Directors shall review and accept/reject the request.
CEO
Roles: Responsible:
Board of Directors
Accountable: CEO
Procedure: ● NWC Project Manager shall ensure from Cluster Finance Department
that the financial liquidity is available.
● Cluster Projects GM and NWC Project Manager shall prepare the
Purchase Requisition (PR) attaching (PMF-016-PRO-005 PR Approval
Form) to reserve the project budget.
● Raise the Purchase Requisition (PR) to Cluster Senior GM.
● This procedure to be completed within 4 days from request approval.
NWC Project Manager
Roles: Responsible:
Cluster Projects GM
Accountable: Cluster Projects GM
Cluster Technical Services Director
Consulted:
Cluster Supply Chain Manager
Cluster Scheduling Section Head
Cluster Contracts Administration Section Head
Cluster Finance GM
Cluster Senior GM
Informed:
Capital Projects & Technical Services VP
16.4.4.7 PMM-016-PRO-030-040 Approve Purchase Requisition (PR) for Design or
Construction Tender
Procedure: ● The Cluster Senior GM shall give 1st approval to the request and raise it
to authorized person within 2 days.
● The authorized person as per latest approved authority matrix shall
review and approve the Purchase Requisition (PR) within 2 days.
Cluster Senior GM
Roles: Responsible:
Authorized Person
Accountable: Cluster Senior GM
Procedure: ● The authorized person shall forward the Purchase Requisition (PR) and
its attachments which includes but not limited to:
○ PR approval form
○ Request for Proposal RFP
○ Project Pre-Tender Review Form
to HQ/Cluster Supply Chain GM (as per authority) for tendering.
● See (PMF-016-PRO-036 Tender for Construction Process Flow in
Governance Document).
16.5.4 Procedures
16.5.4.1 PMM-016-PRO-040-003 Participate in Pre-Tender Meeting
Procedure: ● Arrange and participate in site visit and walkthroughs to explain the
scope of project and its conditions.
● Review the Job Explanation meeting Agenda and provide comments.
● Participate in the Job Explanation meeting and provide responses to
bidder’s questions.
● If required, group bidder requests for information and answers, for
presentation at the Bid Conference.
● Receive and review the conference minutes.
● Refer to (PMF-016-PRO-036 Tender for Construction Process Flow in
Governance Document in Governance Document).
NWC Project Manager
Roles: Responsible:
Cluster Technical Services Director
Accountable: HQ/Cluster Supply Chain GM (as per authority)
Cluster Supply Chain Manager
Consulted:
Business Unit Safety Section Head
Cluster QA Section Head
Cluster Scheduling Section Head
Cluster Contracts Administration Section Head
Design Consultant (If the project is designed)
Engineering Director
Supply Chain GM
Informed: Supply Chain GM
Procedure: ● The Cluster Senior GM shall form the technical evaluation committee for
all projects except:
○ Projects > 100M SAR.
○ Treatment Plant Projects.
which shall be formed by Capital Projects & Technical Services VP.
● The committee formation to be completed within 7 days from tender
schedule preparation.
● Refer to (PMF-016-PRO-036 Tender for Construction Process Flow in
Governance Document).
Capital Projects & Technical Services VP / Cluster Senior
Roles: Responsible:
GM
Capital Projects & Technical Services VP / Cluster Senior
Accountable:
GM
Cluster Projects GM
Consulted:
Cluster Supply Chain Manager
Capital Projects & Technical Services GMs
Supply Chain GM
Technical Evaluation Committee
Informed:
Cluster Supply Chain Manager
Supply Chain GM
16.5.4.5 PMM-016-PRO-040-020 Evaluate Technical Proposal
Procedure: ● The Cluster Senior GM shall approve the technical evaluation report for
all projects except:
○ Projects > 100M SAR.
○ Treatment Plant Projects.
which shall be approved by Capital Projects & Technical Services VP.
● The technical evaluation report approval to be completed within 7 days.
● Refer (PMF-016-PRO-036 Tender for Construction Process Flow in
Governance Document).
Capital Projects & Technical Services VP / Cluster Senior
Roles: Responsible:
GM
Capital Projects & Technical Services VP / Cluster Senior
Accountable:
GM
Technical Evaluation Committee
Consulted:
Cluster Supply Chain Manager
Supply Chain GM
Cluster Supply Chain Manager
Informed:
Supply Chain GM
Procedure: ● After Negotiation & Award recommendation, the authorized person shall
approve the recommendations of negation and award within 5 days.
● For MEWA projects upload and get approval through ITIMAD platform.
● For NWC projects the HQ/Cluster Supply Chain GM (as per authority)
shall get approval for the Selected Bidder and Issue the Purchase Order
(PO) within 5 days from approving the Negotiation & Award Committee
recommendation.
● Proceed with contract issuance as per (PMF-016-PRO-036 Tender for
Construction Process Flow in Governance Document).
13. Inspections, audits and surveillances are to be carried out on second party processes
and contractual deliverables.
14. Performance reporting is to be carried out and analyzed, so that the Project
Management is provided with information on how well the second party is performing
against his contractual obligations. The second party performance is measured
against certain criteria covering technical and quality compliance, works progress,
supplier earned value, manpower usage and material delivery. Performance reporting
must include forecasting and the use of performance trends.
15. A resource calendar must be considered in all project schedules (whether by NWC or
second parties). The resource calendar must adequately record the resource
availability and utilization schedule and show the dates the various resources required
for the execution of the Project Works are becoming available and the dates they may
be active or idle.
16. Payments to the second parties to be processed through NWC Financial System
against Approved Payment Certificates raised by the Project Management Team for
the value of executed and accepted works on monthly basis.
17. The second party accounting department should be able to accommodate the contract
requirements in respect to the format and timing of the payment applications and
invoices as well as for documentation like cost breakdowns, back-up information, etc.
18. In dispute cases, claims must be administered in accordance with the contract
conditions. Dispute resolution through negotiation is always the preferred option. If no
agreement reached by negotiation, Alternative Dispute Resolution (ADR) procedure
shall be implemented if it is stated in the contract.
19. The NWC project team and second party team must perform proper document
controlling for all project documents.
20. Project Information that required by NWC project team or second party team must be
properly managed as per PMM processes and the contract conditions. Examples of
these information are daily logs for Progress, daily Labor and Plant Returns, Second
Party Performance Information, Progress Photos, Disputes, Payment Requests,
Information Requests etc. When NWC project team and or its representative requests
for any of this information from the second party, the second party must immediately
provide the requested information.
21. Enterprise Content Management System (ECMS) is to be used to store, retrieve
and/or archive all the documentation created during the life cycle of a Project. Access
with controlled authorities to be granted to the key members of NWC and/or second
party project management teams.
22. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
16.6.3 Flowchart
Figure 16-7 PMM-016-PRO-070 Contract Administration Flowchart
16.6.4 Procedures
16.6.4.1 PMM-016-PRO-070-010 Design Consultant / Contractor Performance Review
and Reporting
Procedure: ● All reviews in this procedure shall be against the contract provisions.
● Produce Resource Calendar of Design Consultant / Contractor
Resources. Review and maintain the Resource Calendar on weekly
basis.
● Review Design Consultant / Contractor Progress on weekly basis at
activity level.
● Review Design Consultant / Contractor Material and Equipment Delivery
Schedule for actual progress of the purchasing, fabrication and delivery
using (PMF-010-SCH-003 Procurement Schedule for Critical Materials
and Equipment).
● Review Material condition and compliance upon delivery through MIR.
● Review material storage conditions.
● Analyze and Report on Design Consultant / Contractor Progress.
● Review the forecast of progress performance and compliance with
completion date.
● Review Project Expenditure as:
○ Works Value paid
○ Advance payment recovery
Procedure: ● Receive and file the project drawings, shop drawings and all their
revisions.
● Receive and file the works execution Baseline schedule and all schedule
revisions.
● Receive and file all the manpower records.
● Receive and file all plant and equipment records.
● Receive and file all the permanent material records.
● Receive and file records of equipment and material incorporated in the
works together with their operation manuals, warranties and staff training
records.
● Receive and file all the works progress records including the related
photographic records.
● Receive and file all the inspection and audit records.
● Receive and file all the Design Consultant/Contractor payments records
including closeout check report.
● Receive and file all Variation and Claim submissions.
● Receive and file all Design Consultant/Contractor information requests
and subsequent responses.
● Receive and file any other project related information and Design
Consultant/Contractor produced record.
● Use the ECMS to upload and store above documents.
Cluster Contracts Administration Section Head
Roles: Responsible:
NWC Project Document Controller
Accountable: NWC Project Manager
Cluster Technical Services Director
Consulted:
Cluster Supply Chain Manager
Business Unit Safety Section Head
Cluster QA Section Head
Cluster Scheduling Section Head
Supervision Consultant
Supply Chain GM
Cluster Finance GM
Supply Chain GM
Informed:
Cluster Asset Management & Operation Excellence
Director
16.7 PMM-016-PRO-080 Suspend and Resume Project
16.7.1 Objective
The objective of this process is to ensure that the project suspension and resumption are as
per valid reasons and timely activated.
16.7.2 Policies
Policies for this process are as follows:
1. The partial suspension shall not be allowed before consuming the floating time of the
related activities.
2. The Design Consultant / Contractor is not allowed to work at projects sites during the
total suspension period.
3. The Design Consultant / Contractor shall be granted extension period to project
duration:
i. (against total suspension) equals to the total suspension period.
ii. (against partial suspension) equals to the affection on project progress based on
a report prepared by Supervision Consultant (in construction projects) or Cluster
Technical Services department (in design projects).
4. The Design Consultant / Contractor shall be granted additional 3 days against every
sequential thirty days of total suspension for resumption mobilization. The total
granted resumption mobilization periods shall not exceed 45 days.
5. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
16.7.3 Flowchart
Figure 16-8 PMM-016-PRO-080 Suspend and Resume Project Flowchart
16.7.4 Procedures
16.7.4.1 PMM-016-PRO-080-010 Review the Suspension Justifications
Procedure: ● The Capital Projects & Technical Services VP shall review and
approve/reject the complete/partial (for more than 50%) project
suspension request.
● Capital Projects & Technical Services VP shall forward the approved
request to the Cluster Senior GM for issuance.
● This procedure to be completed within 7 days. Refer to (PMF-016-PRO-
034 Projects Suspension and Resumption Process Flow in Governance
Document).
Procedure: ● The project Manager shall review the Supervision Consultant report,
initiate resumption request attaching form (PMF-016-PRO-007
Resumption Approval Form) and send it to Cluster Projects GM within 2
days.
● The Cluster Projects GM shall review the resumption request and
recommendation, give 1st approval and forward it to the Cluster Senior
GM within 2 days.
● The Cluster Senior GM shall:
○ review the resumption request and recommendation.
○ approve the request.
○ issue a formal letter to Design Consultant / Contractor to resume the
suspended work (whole or partial project).
within 2 days, using (PMF-016-PRO-022 Resumption Letter).
● The Design Consultant / Contractor shall submit extension of time
request within 15 days of receiving the resumption letter.
● Refer to (PMF-016-PRO-034 Projects Suspension and Resumption
Process Flow in Governance Document).
NWC Project Manager
Roles: Responsible:
Cluster Projects GM
Cluster Senior GM
Accountable: Cluster Senior GM
Supervision Consultant
Consulted:
Cluster Asset Management & Operation Excellence
Director
Business Unit Construction Director
Cluster Scheduling Section Head
Design Consultant / Contractor
Informed:
Supervision Consultant
Cluster Scheduling Section Head
Cluster Supply Chain Manager
Cluster Projects GM
Scheduling & Control GM
Supply Chain GM
16.8.4 Procedures
16.8.4.1 PMM-016-PRO-085-010 Receive a Report of Changing Project Status from
Partial Suspension to Total Suspension
Procedure: ● When the suspended works become 50% of the remaining available
works, NWC Project Manager shall direct the consultant to create a
report regarding the project progress status using (PMF-016-PRO-043
Report on Changing Partial Suspension to Total Suspension).
● Supervision Consultant shall develop within 3 days from the direction a
report that clearly clarifies:
○ that the suspended works reached 50% of the remaining available
works.
○ the existence of suspension reasons for the suspended works.
○ a recommendation for changing the project status from partial
suspension to total suspension when all available works are
completed.
● For Design Projects, NWC Project Manager shall create this report once
the suspended works become 50% of the remaining available works.
NWC Project Manager
Roles: Responsible:
Supervision Consultant
Accountable: Business Unit Construction Director
NWC Project Manager
Consulted:
Contractor (in construction projects)
Design Consultant (in design projects)
Cluster Technical Services Director (in design projects)
Informed: Cluster Projects GM
Procedure: ● The Capital Projects & Technical Services VP shall review and
approve/reject the (PMF-016-PRO-040 Changing Partial Suspension to
Total Suspension Approval Form).
● Capital Projects & Technical Services VP shall forward the approved
approval form to the Cluster Senior GM for suspension change letter
issuance.
● This procedure to be completed within 7 days.
Procedure: ● NWC Project Manager shall continuously follow with the Supervision
Consultant:
○ whether the available works are completed.
○ whether the partial suspension reasons still exist.
● Once the available works are completed and the partial suspension
reasons still exists, NWC Project Manager shall:
○ notify the Cluster Senior GM to issue a formal suspension change
letter to Design Consultant / Contractor.
○ update the project status in ENJAZ system to total suspension.
● Cluster Senior GM shall issue a formal suspension change letter to
Design Consultant / Contractor within 3 days from the notification. The
total suspension shall be for defined duration or till further notice.
● For resumption follow (PMM-016-PRO-080-040 Issue Resumption
Recommendation) and (PMM-016-PRO-080-050 Issue a Formal Letter
to Resume the Work).
Cluster Senior GM
Roles: Responsible:
NWC Project Manager
Accountable: Cluster Senior GM
Supervision Consultant
Consulted:
Business Unit Construction Director
Capital Projects & Technical Services VP
Design Consultant / Contractor
Informed:
Supervision Consultant
Cluster Scheduling Section Head
Cluster Projects GM
Cluster Supply Chain Manager
Cluster Asset Management & Operation Excellence
Director
Scheduling & Control GM
Supply Chain GM
iv. Any costs of transportation, storing rent and securing the custodied materials and
equipment within first six months from withdraw letter issuance date shall be on
contractor expense.
5. In a withdrawn project, the sites and executed works shall be secured during the
retendering period by a security third party. The cost shall be on contractor expense
for the first six months from withdraw letter issuance date.
6. The Contractor is responsible for securing the safety at site for all withdrawn executed
works, materials and equipment within max 15 days from the withdraw letter.
7. After the duration in policies 5 and 6 exceeds six months from withdraw letter issuance
date (which is the retendering period as per Governance Document), the costs shall
be after then on NWC expense.
8. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
16.9.3 Flowchart
Figure 16-10 PMM-016-PRO-090 Withdraw Project Flowchart
16.9.4 Procedures
16.9.4.1 PMM-016-PRO-090-010 Issue Urge Letter to Design Consultant / Contractor
Supervision Consultant
Consulted:
Cluster Contracts Administration Section Head
Cluster Supply Chain Manager
Cluster Asset Management & Operation Excellence
Director
Supply Chain GM
Legal Department
Design Consultant / Contractor
Informed:
Cluster Projects GM
Cluster Supply Chain Manager
Cluster Asset Management & Operation Excellence
Director
Supply Chain GM
16.9.4.3 PMM-016-PRO-090-030 Issue Final warning letter to Design Consultant /
Contractor
Procedure: ● If the Design Consultant / Contractor doesn’t take any corrective actions
after receiving the final warning, the Cluster Technical Services Director
/ Supervision Consultant shall prepare and submit a detailed project
status report 5 days after the end of the final warning period (15 days)
which shall include but not limited to the following:
○ The work progress.
○ The seriousness of Design Consultant / Contractor in taking the
corrective actions.
○ Recommendation of withdrawal or not.
● Cluster Technical Services Director / Supervision Consultant shall initiate
a withdraw approval form using (PMF-016-PRO-018 Withdraw Approval
Form) and populate it with NWC Project Manager. See procedure (PMM-
016-PRO-090-070 Approve the Project Withdrawal at Cluster).
● Refer to (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
Cluster Technical Services Director (in design projects)
Roles: Responsible:
Supervision Consultant (in construction projects)
Accountable: NWC Project Manager
Procedure: ● If Contractor does not submit initial acceptance request at the project
contractual end date, the cluster projects GM shall form a project
situation assessing committee within 2 days before the project end date
to:
○ do project works inventory
○ identify the project status
○ describe the project situation works indicating the executed and
remaining works.
● The project situation assessing committee shall develop a committee
report using (PMF-016-PRO-048 Work Inventory Report for Not
Requesting IA&HO).
● The Cluster projects GM shall review and approve the report.
● NWC Project manager shall upload the approved report to ENJAZ
system.
● The committee forming, the assessment, the report review and report
uploading shall be completed within 14 days from the contractual project
end date.
● Refer to (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
Supervision Consultant
Roles: Responsible:
NWC Project Manager
Project Status Assessing Committee
Cluster Projects GM
Accountable: Cluster Projects GM
Contractor
Consulted:
Cluster Scheduling Section Head
Informed: Cluster Senior GM
Procedure: ● After 20% time overrun, a project status report shall be initiated by
Supervision Consultant and NWC Project Manager recommending
withdrawal / grace period.
● The cluster Projects GM shall review and sign the report and raise it to
Cluster Senior GM.
● The Cluster Senior GM for review and forward the report to Scheduling
& Control GM.
● The above actions shall be completed within 3 days after reaching 20%
time overrun.
● Refer to (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
Supervision Consultant
Roles: Responsible:
NWC Project Manager
Cluster Projects GM
Cluster Senior GM
Accountable: Cluster Senior GM
Contractor
Consulted:
Cluster Scheduling Section Head
Informed: Scheduling & Control GM
Procedure: ● The Scheduling & Control GM shall review and sign the project status
report and raise it to Capital Projects & Technical Services VP within 7
days.
● The Capital Projects & Technical Services VP shall decide within 2 days
whether to grant the Contractor a Grace Period or go through withdraw
process by issuing the 1st warning letter and after 30 days a final warning
letter.
● In case of grace period, this assessment shall be repeated after grace
period.
● Refer to (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
Scheduling & Control GM
Roles: Responsible:
Capital Projects & Technical Services VP
Accountable: Capital Projects & Technical Services VP
Procedure: ● The Cluster Projects GM shall review the withdraw report and approve
the withdraw approval form (PMF-016-PRO-018 Withdraw Approval
Form) then forward them to Cluster Senior GM within 2 days.
● The Cluster Senior GM shall review the withdraw report and approve the
withdraw approval form (PMF-016-PRO-018 Withdraw Approval Form)
then forward them to Capital Projects & Technical Services VP within 3
days.
● See (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
Cluster Projects GM
Roles: Responsible:
Cluster Senior GM
Accountable: Capital Projects & Technical Services VP
Cluster Scheduling & Control Manager
Consulted:
Cluster Strategic Planning Manager
Cluster PMO Manager
Cluster Asset Management & Operation Excellence
Director
Cluster Supply Chain Manager
Legal Department
Procedure: ● The Capital Projects & Technical Services VP shall review the withdraw
report and approve the withdraw approval form (PMF-016-PRO-018
Withdraw Approval Form) then forward to the HQ/Cluster Negotiation &
Award Department (as per authority) within 7 days. The forwarding shall
be:
○ directly for NWC Projects.
○ through Cluster Senior GM (in 2 days) for MEWA Projects.
● See (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
Procedure: ● After the HQ/Cluster Negotiation & Award Department (as per authority)
within 14 days:
○ reviews the withdraw report and any documentation.
○ approves the and withdraw approval form (PMF-016-PRO-018
Withdraw Approval Form).
○ forwards the withdraw report and withdraw approval form (PMF-016-
PRO-018 Withdraw Approval Form) to Authorized Person for
approval.
the authorized person shall approve the withdrawal approval form within
7 days.
● Refer to (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
Procedure: ● The HQ/Cluster Supply Chain GM (as per authority) shall perform, within
2 days, the following:
○ Review the withdrawal documentation.
○ Execute any contract related penalties.
○ Update the Consultant / Contractor evaluation records.
○ Prepare the Withdraw Letter using (PMF-016-PRO-021 Withdraw
Letter) which shall include the following:
- Demobilization instructions.
- Requesting the Design Consultant / Contractor to identify his
representative in The Actual Quantity Survey Committee.
- Compensation details.
○ Issue the withdraw letter to Consultant / Contractor.
● Refer to (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
Procedure: ● NWC Project Manager shall update the project status in ENJAZ system.
● Cluster Projects GM shall request form HSSE a security team to guard
the project site and all its contents once the withdrawal letter is issued.
● Cluster Projects GM shall request form Assets Management (Business
Operational Support) to oversee and keep the withdrawn works,
equipment and materials once the withdrawal letter is issued.
NWC Project Manager
Roles: Responsible:
Cluster Projects GM
Accountable: Cluster Projects GM
HSSE GM
Consulted:
Legal Department
Business Unit Construction Director
Cluster Senior GM
Cluster Senior GM
Informed:
Cluster Asset Management & Operation Excellence
Director
Cluster HSSE Manager
Procedure: ● After withdraw letter issuance, the NWC Project Manager shall request
for forming a Work Inventory Committee within 2 days from withdraw
letter issuance using (PMF-016-PRO-016 Work Inventory Committee
Forming Request).
● The Cluster Projects GM, within 2 days using (PMF-016-PRO-016 Work
Inventory Committee Forming Request), shall form the Work Inventory
Committee, beside the NWC Project Manager, shall including at least
representatives from:
○ Cluster Projects department
○ Cluster Operation Excellence department
○ Cluster Asset Management department
○ Cluster HSSE department
○ Cluster Finance department
○ Supervision Consultant
○ Design Consultant / Contractor
● The Committee shall plan and perform inventory on the following:
○ all executed and remaining works.
○ all material and equipment on site as per mentioned policy No. 4.
● The Committee shall ensure application of the policies 5 and 6 in the
inventory report.
● The committee shall develop a formal report (PMF-016-PRO-028
Withdrawn Work Inventory Report) with signatures of all representatives.
If Design Consultant / Contractor representative doesn’t attend at the
determined date, he shall not have a right to object the committee report.
● The Cluster Projects GM shall approve the report.
● The whole procedure shall be completed within 45 days from the
withdrawal letter issuance date.
● Refer to (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
NWC Project Manager
Roles: Responsible:
Cluster Projects GM
Work Inventory Committee
Accountable: Cluster Projects GM
Supervision Consultant
Consulted:
Design Consultant / Contractor
Procedure: ● Prepare request for proposal package for the remaining work within
maximum 90 days from the withdrawal letter issuance date.
● The Supply Chain GM shall, within maximum 180 days from the
withdrawal letter issuance date, assign another Contractor (and issue
PO) for completion of the remaining work via one of the following
methods in sequence:
○ Negotiate with project bidders consequently to complete the project
at the contract prices.
○ Negotiate with project bidders consequently to complete the project
at current market prices.
○ Award to a Contractor through direct purchase process at current
market prices to complete the project.
○ Tender to Select New Contractor to complete the project.
● If the duration of inventorying the project works, RFP preparation and PO
issuance exceeds respectively the identified limits (45, 90 and 180 days
from withdrawal), an approval of the Capital Projects & Technical
Services VP must be obtained by a request that details the reasons of
delay.
● Refer to (PMF-016-PRO-033 Projects Withdrawal Process Flow in
Governance Document).
Supply Chain GM
Informed:
Cluster Asset Management & Operation Excellence
Director
Legal Department
Technical Services GM
16.10 PMM-016-PRO-100 Contract Closure
16.10.1 Objective
The objective of this process is to verify that all the Project (or a Project’s Stage) deliverables
and any other related work have been completed and accepted, together with all the
administrative activities. These activities include the finalization and agreement of all open
claims, updating the project records to reflect the final results and archiving them ready for
future use. With multi-contract (or multi-Stage) Projects the process should be repeated for
each one of the Contracts (or Stages).
16.10.2 Policies
Policies for this process are as follows:
1. The closure of a contract requires all the contract documentation to be collected,
indexed, filed and archived.
2. The Contract close documentation includes information on the final project Schedule
and Scope, Quality and Cost performance, Contract Change documentation,
Payment Records, Inspection and Audit results and Supplier prepared and submitted
documents. All these documents are catalogued and archived so that they can be
used for “lessons learned” information and as a basis for future Contractor evaluation.
3. Early termination is a special case of contract closure and can result from:
i. Mutual agreement between the two parties
ii. Default of one party
iii. For convenience of the Employer if it is so provided in the Contract
4. The rights and responsibilities of the contracted parties in the event of early
termination should be clearly detailed in the termination clause of the contract.
5. When the Employer, under the contract procurement terms and conditions, has the
right to terminate a contract, or a portion of the contract, at any time for convenience
he shall have to compensate the Supplier, not only for the value of the completed and
accepted works but for under-recovery of site and Head Office overheads, as well as
any justifiable Staff, Labor and Plant underutilization costs.
6. In the case of unresolved claims, the contract (or Stage) is closed after an accrual is
made on the Project account until the claim is resolved to cater for any potential costs.
Alternatively, the Project account can also be closed and an accrual is made in a
special holding account for unresolved and subject to Litigation Claims. NWC Project
Manager is responsible for requesting for these solutions.
7. In case of any conflicts between approval authorities stated in this manual and the
latest approved NWC Delegation of Authority, the latest approved NWC Delegation
of Authority shall be followed.
16.10.3 Flowchart
Figure 16-11 PMM-016-PRO-100 Contract Closure Flowchart
16.10.4 Procedures
16.10.4.1 PMM-016-PRO-100-010 Audit the Contract Closeout
● Request and receive the Contractor confirmation that the final Payment
Certificate fully represents the fair and final value of all the executed
works, including all the variations and claims and that there will be no
further claims against the project.
● Review and approve the final payment application and forward it to the
Finance Department for payment in accordance with the Contract
provisions.
● Communicate to Finance department on any retention moneys and any
other funds retained with the dates they are due to the Contractor.
● Inform the NWC Project Manager that the audit result is acceptable and
the contract can be closed.
● This procedure is to be completed within 7 days form the formal final
acceptance of the contract deliverables.
Procedure: ● After receiving the result of contract closeout audit as acceptance, NWC
Project Manager shall formally, in 2 days, request from Cluster Projects
GM to issue a contract closeout notification to:
○ Cluster Projects GM
○ Cluster Supply Chain Manager
○ Cluster Finance GM
○ Cluster Asset Management & Operation Excellence Director
○ Supply Chain GM
● Cluster Projects GM shall formally, in 2 days, issue the contract closeout
notification.
NWC Project Manager
Roles: Responsible:
Cluster Projects GM
Accountable: Cluster Projects GM
Cluster Projects GM
Consulted:
Cluster Contracts Administration Section Head
Supervision Consultant
Cluster Supply Chain Manager
Cluster Projects GM
Informed:
Cluster Supply Chain Manager
Cluster Finance GM
Cluster Asset Management & Operation Excellence
Director
Supply Chain GM
Year-to-date, has
Cluster Projects
Participation in pre- Department participated
1 Monthly Yes NA No
tender meeting in all pre-tender
meetings for projects
that tendered this year.
Year-to-date, has
Cluster Projects
Organization of Department organized
2 pre-bid meeting all pre-bid meeting (Job Monthly Yes NA No
(Job Explanation) Explanation meetings)
for all projects that
tendered this year.
Percentage of year-to-
date number of RFPs
that passed the
Request for
minimum RFP
3 Proposal (RFP) Monthly 100% NA < 100%
requirements to the
Completeness
year-to-date total
approved RFP in the
cluster
Year-to-date number of
suspension processes
in the cluster that issued
the suspension letter to
the contractor in more
than:
Commitment to - 15 days for
4 suspension suspensions that do not Monthly 0 1 >1
process duration require HQ approval
- 22 days for
suspensions that
requires HQ approval
from suspension
request submission
date.
Year-to-date number of
processes of changing
project status from
Commitment to partial suspension to
duration of total suspension in the
changing project cluster that issued the
5 status from partial changing letter to the Monthly 0 1 >1
suspension to total contractor in more than
suspension 18 days from the date of
process that the suspended
works become 50% of
the remaining available
works.
Year-to-date number of
projects in the cluster
Withdrawal of that did not issue a final
6 projects that have warning letter to the Monthly 0 NA >0
SV > 20% contractor despite the
SV remained more than
20% for 30 days.
Year-to-date number of
withdraw processes in
the cluster that raised
the withdraw letter to the
authorized person for
Commitment to
approval in more than:
7 withdraw process Monthly 0 1 >1
- 48 days for NWC
duration
projects
- 50 days for MEWA
projects
from final warning letter
issuance date.
Year-to-date number of
projects in the cluster
that did NOT issue a
contract closeout
8 Contract Closeout Monthly 0 2 >2
notification after 9 days
from the date of formal
final acceptance of the
contract deliverables.
16.12 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-016-
PRO Project Procurement Management).
PMF-016-PRO-009 Total or Partial Greater than 50% Suspension Request Approval Form
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-017-HSE-010 Plan Project Health, Safety & Environmental” is
revised.
● The process “PMM-017-HSE-015 Environmental Impact Assessment” is added.
Change
● The process “PMM-017-HSE-020 Perform Health, Safety & Environmental
Description
Assurance” is revised.
● The process “PMM-017-HSE-030 Perform Health, Safety & Environmental Control”
is revised.
● Key Performance Indicators (KPIs) are revised.
● Number of attachments are added, revised or removed.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This section is developed as an update to “HSE” section in first version the Project
Management Manual (PMM) which developed by Faithful + Gould. The following are
the changes:
● Adding HSE guidelines included in Mashroat White Book.
● Adding HSE Bidder evaluation objective scoring table from Mashroat White
Book.
● Adding the Construction HSE plan contents.
Change
Description ● Removing the procedure of developing Method statement to quality section.
● Removing the procedure of capturing quality lessons learned from HSE
planning process to HSE Assurance process.
● Adding the forms number inside the procedures.
● Updating KPI’s.
● Updating responsibilities as per NWC organization charts.
● Updating and simplifying flowcharts.
Figure 17-1 High-Level Process Map for Project Health, Safety & Environmental Management
17.1.3 Flowchart
Figure 17-2 PMM-017-HSE-010 Plan Project HSE Management Flowchart
17.1.4 Procedures
17.1.4.1 PMM-017-HSE-010-010 Develop the HSE Management Plan Section of the
Project Management Plan
Procedure: ● Review and Approve the HSE Management Plan Section of Project
Management Plan.
● Document and track the results of the reviews till they are closed out
satisfactorily.
● Approve the submitted Project HSE Management Plan Section.
● Ensure that only changes approved through (PMM-007-INT-060
Variation Control) process are implemented.
Procedure: ● Develop Project HSE Management Plan Section in the Project Design
Management Plan.
● Ensure that the Project HSE Management Plan Section in the Project
Design Management Plan is in alignment with the Project HSE
Management Plan Section in the NWC Project Management Plan.
● The Design HSE Management Plan shall strictly be in alignment with
(00_BS01_FM_022.01 HSSE Requirements of Contract Appendix)
which the Design Consultant is responsible to fulfill during the Design
Stage.
● Consult with NWC Project Manager and Cluster Technical Services
Director about the development of the Project HSE Management Plan
Section.
● Include the Project HSE Management Plan Section in the Project Design
Management Plan to be approved as part of the Project Design
Management Plan.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
HSE Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes HSE assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
17.2.3 Flowchart
Figure 17-3 PMM-017-HSE-015 Environmental Impact Assessment Flowchart
17.2.4 Procedures
17.2.4.1 PMM-017-HSE-015-010 Prepare Environmental Impact Assessment
Guidelines ● The Consultant shall undertake all surveys and assessments for the
Environmental Baseline Survey Assessment (EBSA) study in line with
the industry standards, National Center for Environmental Compliance
(NCEC) standards and guidelines and the international standards
applicable. The data should be in the report include at least the following:
○ Ambient air quality.
○ Climatic and metrological data.
○ Noise.
○ Soil and groundwater quality.
○ Groundwater hydrology.
○ Geology and seismology.
○ Topography and natural surface drainage.
○ Terrestrial ecology.
○ Socio-economic information
● Environmental Impact Assessments (EIA) study and report are required
for the purposes of obtaining approval from National Center for
Environmental Compliance (NCEC) for the land designated for the STPs
and obtaining permits for TSE discharges to the environment, i.e.
discharges to inland watercourse (wadi). The work should be done as
per NCEC requirement.
Procedure: ● After NWC review, the Environmental Consultant shall obtain approval
from National Center for Environmental Compliance (NCEC) prior to
Design and land acquisition.
● The Environment Consultant shall submit the approved EIA to the
Cluster Environmental Compliance Manager who shall pass it to
Environmental Compliance Director.
Environmental Consultant
Roles: Responsible:
Cluster Environmental Compliance Manager
Accountable: Cluster Projects GM
Environmental Compliance Director
Consulted:
NWC Project Manager
Environmental Compliance Director
Informed:
NWC Project Manager
17.3.2 Policies
Policies for this process are as follows:
1. Assurance must be provided, through objective evidence, that the planned HSE-
related activities and control measures have been properly integrated into the other
project activities, and that their execution has been effective and efficient.
2. Results of the HSE-related activities and control measures must be evaluated on a
regular basis and formally reported in the Construction monthly project progress
report, to the satisfaction of the Supervision Consultant and NWC Project Manager.
3. Second Party HSE Management Plans must be supported by competent health and
safety risk assessments and method statements. Work activities by Second Parties
must only be carried out if there are associated HSE assurance documents in place,
such as risk assessments, impact assessments, method statements, construction
safety guidelines, induction training records, tool box training records and, most
importantly, an approved NWC permit to carry out the specific construction activities
identified in the method statement.
4. All HSE Management Plans and associated assurance records are subject to periodic
audits by NWC.
5. There must be provision for training of workers in the importance of method
statements and how method statements must be followed at all times for all activities,
without exception. This principle must be covered in the workers’ induction training
and subsequent toolbox style training must be given to cover each approved method
statement, using the supporting HSE guidelines from the NWC library and highlighting
the specific steps in the method statement, which have been added as mitigation
against identified HSE risks and impacts.
17.3.3 Flowchart
Figure 17-4 PMM-017-HSE-020 Perform Health, Safety & Environmental Assurance Flowchart
17.3.4 Procedures
17.3.4.1 PMM-017-HSE-020-010 Carry Out and Submit the Scheduled HSE-Related
Design Study
Procedure: ● The number and frequency of HSE-related studies shall be shown by the
Design Consultant in his design activity schedule.
● This shall include the following as a minimum, unless a formal, written
concession is granted by NWC in exceptional circumstances:
○ Hazard and Operability (HAZOP) study
○ Failure Mode, Effect and Criticality Analysis (FMECA) study
● Compile and formally report on each completed study.
● Each HSE-related design study must be submitted as an integral
package with the appropriate design deliverables, such as drawings,
calculations, etc.
Procedure: ● HSE-related design study reports must be approved with the associated
design information (drawings, calculations, etc.)
● The review of each design deliverable package, including the associated
HSE- related study reports, is led by the Cluster Technical Services
Director, assisted by the Business Unit Safety Section Head, as part of
the review and approval activity
● Include all HSE-related design study documentation comments and
suggestions for improvements in the design review package response.
Cluster Technical Services Director
Roles: Responsible:
Business Unit Safety Section Head
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Cluster Risk Section Head
Informed: Design Consultant
Procedure: ● The Risk Assessment must be approved with the method statement.
● The review of each risk assessment, including the associated
attachments, is performed by the Supervision Consultant.
Procedure: ● The Supervision Consultant and Business Unit Safety Section Head shall
carry out periodic and occasional inspections and audits at the
construction site. They can perform the inspections and/or audits jointly
and individually.
● Use the audit checklists to perform the audit:
○ (PMF-017-HSE-015 HSE Inspection Checklists)
○ (00_BS01_FM_001.01 Audit of Contractor Safety Performance)
● During the visits, the Supervision Consultant and/or the Business Unit
Safety Section Head shall discuss and give informal guidance and
directions on his observations and answer any question raised during the
visit.
● As per the findings of inspection and/or audit, use the following forms, as
required, to formally inform the Contractor HSE violation:
○ (PMF-017-HSE-012 HSE Observation Record)
○ (PMF-014-COM-013 Non Conformance Report NCR)
● If an HSE violation found under a provision in (00_BS01_GD_002.01
Fines and Penalties of Contractor HSE Violations), recommend penalties
on Contractor as per the provision using the form (00_BS01_FM_026.01
HSSE Contractors Violation Form for Fine Report). The recommendation
shall be attached to the relevant HSE document (PMF-017-HSE-012
HSE Observation Record) and/or (PMF-014-COM-013 Non
Conformance Report NCR) and raise them to NWC Project Manager for
further process.
Supervision Consultant
Roles: Responsible:
Business Unit Safety Section Head
Accountable: NWC Project Manager
Contractor
Consulted:
Cluster HSSE Manager
NWC Project Manager
Informed:
Contractor
Cluster HSSE Manager
Procedure: ● The Supervision Consultant shall schedule a visit to the construction site,
in order to close the permit in a professional manner.
● The Supervision Consultant shall ensure that all inspection and testing
have been carried out as per approved ITP.
● If the closure request is denied, then Supervision Consultant shall inform
the Contractor verbally during the visit and write the reasons on the PTW
form.
● If the closure request is accepted, then Supervision Consultant shall
inform the Contractor verbally during the visit and record the closure on
PTW form.
● In either case, Supervision Consultant shall return the updated PTW form
to the Contractor for filing.
Procedure: ● Reflect on HSE-related issues and document the key lessons learned
● The lessons learned may include the following:
○ HSE-related performance of the Design Consultant.
○ HSE-related performance of the Supervision Consultant.
○ HSE-related performance of the Contractor.
○ HSE-related performance of NWC staff.
○ HSE issues relating to materials, tools and construction techniques.
○ Improvements to HSE-related documents and processes in the
Project Management System, such as guidelines, formats, etc.
● Individual staff appraisals, or debriefing, must take place for Project
Team members. HSE-related performance and learning opportunities
should be considered as part of this process.
HSSE GM
Informed:
Continuous Improvement Lead
17.4.3 Flowchart
Figure 17-5 PMM-017-HSE-030 Perform Health, Safety & Environmental Control Flowchart
17.4.4 Procedures
17.4.4.1 PMM-017-HSE-030-010 Review the HSE Aspects in Submitted Design
Review Packages
Procedure: ● HSE issues shall be addressed in all technical reviews and regular
progress meetings, as well as regular progress reports by the Design
Consultant.
● Address HSE issues in the Technical Review Reports.
● For recording of meetings, use the Minutes of Meeting format, clearly
identifying any HSE-related actions
Design Consultant
Roles: Responsible:
Cluster Technical Services Director
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Business Unit Safety Section Head
Cluster HSSE Manager
Informed: NWC Project Manager
17.4.4.3 PMM-017-HSE-030-030 Carry Out Root Cause Analysis for Design Related
HSE Observations
Procedure: ● Design Consultant shall define the corrective and preventive actions for
the following:
○ Correction of the HSE observations.
○ Prevention of recurrence (e.g. a change to the design process itself).
● Use the Corrective and Preventive Action’s section in (PMF-017-HSE-
012 HSE Observation Record) or (PMF-014-COM-013 Non
Conformance Report NCR) to document the defined actions.
● Each root cause must be adequately treated (i.e. a defined mitigation
through correction and/or prevention).
Procedure: ● The approved permit to work includes clearly identified steps, which have
been introduced in order to mitigate against known HSE risks.
● The Supervision Consultant must oversee that the Contractor carries out
the construction activities in accordance with the permit-to-work and its
attachments.
● This must start with observation that the Contractor has carried out
briefings and toolbox talks associated with the work and has clearly used
the approved permit to work as a central document for this active
communication purpose.
● Observe that the briefed staff are the actual staff who perform the work.
● Observe that the briefed staff have been made aware of the specific HSE
risk mitigation steps within the workflow.
Supervision Consultant
Roles: Responsible:
Contractor
Accountable: NWC Project Manager
Procedure: ● HSE issues shall be addressed in all regular site meetings, as well as
regular progress reports by the Contractor.
● For recording of meetings, use the Minutes of Meeting format, clearly
identifying any HSE-related actions.
● The approach must be collaborative between departments and parties,
and must consider the whole life of the asset, not just its construction
phase.
Contractor
Roles: Responsible:
Supervision Consultant
Accountable: NWC Project Manager
NWC Project Manager
Consulted:
Business Unit Safety Section Head
Informed: NWC Project Manager
Supervision Consultant
Informed:
NWC Project Manager
Business Unit Safety Section Head
Year-to-date number of
Fatality Case (FTL)
5 Death of a worker Monthly 0 NA 1
(Cumulative)
(Cumulative).
Year-to-date number of
Lost time Injury Site injury that causes
6 (LTI) -CASES the worker to miss 1 day Monthly 0 NA 1
(Cumulative) of work or more
(Cumulative).
Year-to-date number of
Occupational
7 illness due to job Monthly 0 2 >2
Illness (OI)
hazards.
Year-to-date number of
Restricted Work
Site injury resulting to
9 Cases (RWC) Monthly 0 NA 1
change job
(Cumulative)
(Cumulative).
Year-to-date number of
Permanent
Site injury resulting to
10 Disabilities Cases Monthly 0 NA 1
Permanent Disabilities
(Cumulative)
(Cumulative).
Year-to-date number of
Medical Treatment Site injury resulting in
11 Monthly 0 2 >2
Cases (MTC) the Hospitalization of a
worker.
Year-to-date number of
Medical Treatment
Site injury resulting in
12 Cases (MTC) Monthly 0 4 >4
the Hospitalization of a
(Cumulative)
worker.
Year-to-date number of
First Aid Site injury where first aid
13 Monthly 0 5 >5
Administered was administered to the
worker.
Year-to-date number of
First Aid
Site injury where first aid
14 Administered Monthly 0 10 > 10
was administered to the
(Cumulative)
worker (Cumulative).
Year-to-date number of
Site incident that could
15 Near Miss Event Monthly 0 5 >5
have caused an injury or
fatality (but did not).
Year-to-date number of
Near Miss Event Site incident that could
16 Monthly 0 10 > 10
(Cumulative) have caused an injury or
fatality (but did not).
Year-to-date number of
Property Damage
Site incident that could
17 Cases (PDC) Monthly 0 NA 1
have caused a property
(Cumulative)
damage (Cumulative).
Year-to-date number of
accidents that cause
Environmental
pollution of the
18 Incidents Cases Monthly 0 2 >2
environment - Waste
(EIC)
management violations -
air pollution, etc.).
Year-to-date number of
accidents that cause
Environmental pollution of the
19 Incidents Cases environment - Waste Monthly 0 4 >4
(EIC) (Cumulative) management violations -
air pollution, etc.)
(Cumulative).
Year-to-date number of
open NCRs issued to
the Contractor by the
Supervision Consultant
No. of Non-
and/or NWC stating that
20 Conformance Monthly 0 2 >2
the Contractor did not
Reports
conform to site HSE
requirements, site HSE
Plan, or good HSE
practices.
Year-to-date number of
open NCRs issued to
the Contractor by the
No. of Non- Supervision Consultant
Conformance and/or NWC stating that
21 Monthly 0 4 >4
Reports the Contractor did not
(Cumulative) conform to site HSE
requirements, site HSE
Plan, or good HSE
practices.
Year-to-date number of
No. of HSE HSE Penalties
22 Monthly 0 2 >2
Penalties assessed against the
Contractor by NWC.
Year-to-date number of
No. of HSE HSE Penalties
23 Penalties assessed against the Monthly 0 5 >5
(Cumulative) Contractor by NWC
(Cumulative).
17.6 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-017-
HSE Project Health, Safety & Environmental Management).
Table 17-2 Project Health, Safety & Environmental Management forms, templates and guidelines
PMF-017-HSE-151 Lifting Plan & Risk Assessment & Method Statement form
PMF-017-HSE-160 HSE Guideline for Construction Sites Material Handling Storage Use and
Disposal
PMF-017-HSE-190 HSE Guideline for Construction Sites Welding and Cutting Works
PMF-017-HSE-230 HSE Guideline for Construction Sites Machinery Tools and Equipment
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-018-FIN-005 Plan Project Financial Management” is added.
● The process “PMM-018-FIN-010 Financial Planning” is replaced by the process
“PMM-018-FIN-015 Develop Project Cash Flow”.
Change
Description ● The process “PMM-018-FIN-020 Perform Financial Control” is elaborated.
● The process “PMM-016-FIN-030 Perform Financial Reporting” is removed as it is
covered in processes “PMM-014-COM-120 Design Performance Reporting” and
“PMM-014-COM-130 Construction Performance Reporting”. However, it was
describing how to automate the financial reporting.
● Key Performance Indicators (KPIs) are revised.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This section is developed as an update to “Financial” section in first version the Project
Management Manual (PMM) which developed by Faithful + Gould. The following are
the changes:
Change
Description ● Updating KPI’s.
● Updating Responsibilities as per NWC organization chart.
● Updating and simplifying flowcharts.
construction) including Financial Management Plan Section for the project. These
management plans must comply with the financial management requirements defined
in the NWC Project Management Plan and must be approved by NWC during
mobilization period.
3. The Financial Management Plans in PMPs of NWC, Design and Construction must
be kept up-to-date throughout the project life cycle.
4. The NWC Financial Management Plan shall cover all project stages from Initial
Planning stage to project closeout.
18.1.3 Flowchart
Figure 18-2 PMM-018-FIN-005 Plan Project Financial Management Flowchart
18.1.4 Procedure
18.1.4.1 PMM-018-FIN-005-010 Develop the Financial Management Plan Section of
the Project Management Plan
Procedure: ● Review and Approve the Financial Management Plan Section of Project
Management Plan.
● Document and track the results of the reviews till they are closed out
satisfactorily.
● Approve the submitted Project Financial Management Plan Section.
● Ensure that only changes approved through (PMM-007-INT-060
Variation Control) process are implemented.
Cluster Technical Services Director
Roles: Responsible:
Cluster Scheduling & Control Manager
Accountable: Cluster Projects GM
Cost Estimation Lead
Consulted:
Cost Control Section Head
NWC Project Manager
Business Unit Construction Director
Cluster Projects GM
Cost Estimation Manager
Scheduling & Control Director
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Financial Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes financial assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
18.2.4 Procedures
18.2.4.1 PMM-018-FIN-015-010 Prepare for Project Cash Flow Development
Procedure: ● Develop a project cash flow ensuring that planned payments equal to the
project approved budget.
● NWC Project Manager shall update the:
○ NWC Project Management Plan by the Developed Project Cash
Flow.
○ Project Cash Flow as per approved variations; then update NWC
Project Management Plan accordingly.
Cost Estimation Lead
Roles: Responsible:
Cost Control Section Head
NWC Project Manager
Accountable: NWC Project Manager
Cluster Projects GM
Consulted:
Business Unit Construction Director
Cost Estimation Manager
Scheduling & Control Director
Cluster Technical Services Director
Informed:
Cluster Scheduling & Control Manager
Cluster Projects GM
Cost Estimation Manager
Scheduling & Control Director
18.3.3 Flowchart
Figure 18-4 PMM-018-FIN-020 Perform Financial Control Flowchart
18.3.4 Procedures
18.3.4.1 PMM-018-FIN-020-010 Monitor Payment of Invoices
Procedure: ● Ensure that the second party payment is processed with formal approval
as follows:
○ For design projects: NWC Project Manager, Cluster Technical
Services Director, Cluster Projects GM.
○ For EPC/construction projects: Supervision Consultant, NWC
Project Manager and Cluster Projects GM.
● After second party invoice is processed form projects department to
Finance department, monitor on ISupplier whether the Second party has
timely received his payment as per finance policies.
● If the second party has not received his payment, escalate the issue.
Procedure: ● Update the project cash flow as per actual information of:
○ Processed invoices.
○ Made payments.
○ Payment adjustments.
○ Approved variations.
○ Any other related information.
Procedure: ● On monthly basis, create a cash flow forecast for the whole project.
● When requested or as planned, provide the Cluster Finance Department
by created Cash Flow forecast.
Year-to-date number of
Commitment to
months in a project that
1 monthly update the Monthly 0 4 >4
did NOT have updated
project cashflow
cashflow.
18.5 Attachments
NA
History Page
Fakhruddin B. Bilal Mohamed A. Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
12/01
02 Abdulaziz M. Alshehri Majed A. Aljabri
2022 Abdulaziz K. Aljawan
● The responsibilities in all process are revised and updated as per latest NWC
Organizational Structure.
● The process “PMM-019-CLA-005 Plan Project Claim Management” is added.
● The process “PMM-019-CLA-010 Identify Potential Claims by Reviewing Contract
Documentation” is revised.
● The process “PMM-019-CLA-020 Avoid Claims” is revised.
Walid Eldakhs Mohamed Adli Khamees S. Alzahrani Talal M. Alahmari Mansour M. Abuthnain
06/02
01 Fakhruddin Bilal Majed A. Aljabri
2020 Abdullah M. Albani
This section is developed as an update to “Claim” section in first version the Project
Management Manual (PMM) which developed by Faithful + Gould. The following are
the changes:
● Adding the following templates:
○ Constructability master list
Change
Description ○ Lessons Learned Register
● Merging Related/repeated procedures in process 4 to process 2.
● Updating responsibilities as per NWC Organization Chart.
● Simplifying and updating flowcharts.
● Updating KPI’s.
Claims are normal part of projects as they are inevitable in projects. So, the aim of claim management
should be to avoid claims as much as possible. The strategy to achieve this objective is to resolve as
early as possible any circumstance of a potential claim in the most beneficial way for the Project.
Many factors may result in claims (see examples below). The early recognition of such factors and open
communication between the parties can create an environment of cooperation, in terms of seeking
alternative solutions, where claims are less likely to occur.
During all project life, the awareness of the project team members about the typical causes of Claims
helps to early identify them to avoid or manage. The key typical claim causes that enforce the Contractor
/ Design Consultant to perform not contracted work or delay or impact contracted work are as follows:
● Circumstances that out of control of one or more of project parties.
● Improper planning which produces poor scope, schedule and/or cost baselines.
● Improper variation management such as poor effect study.
● Ambiguous terms or specifications.
1. Each project must have a separate section for Claim Management in the Project
Management Plan, created by the NWC Project Manager and used as the guiding
document for internal and external staff throughout the project.
2. The approved Project Management Plan, including the Claim Management Plan
section, must be included in the tender document when NWC is procuring Second
Party services and products in support of project execution.
3. Second Parties must create their own Claim Management Plan sections for the project
as part of their contract mobilization work. These Claim Management Plan Sections
must be approved by NWC during mobilization period.
4. The Claim Management Plans in PMPs of NWC, Design and Construction must be
kept up-to-date throughout the project life cycle.
5. Planning for Claim must be specific and unique to the location, activities and
characteristics of the project. It must not be generic or wholesale copy-and-paste from
previous projects, else it will be rejected and the work will not be allowed to proceed.
19.1.3 Flowchart
Figure 19-2 PMM-019-CLA-005 Plan Project Claim Management Flowchart
19.1.4 Procedures
19.1.4.1 PMM-019-CLA-005-010 Develop the Claim Management Plan Section of the
Project Management Plan
Procedure: ● Review and Approve the Claim Management Plan Section of Project
Management Plan.
● Document and track the results of the reviews till they are closed out
satisfactorily.
● Approve the submitted Project Claim Management Plan Section.
● Ensure that only changes approved through (PMM-007-INT-060
Variation Control) process are implemented.
Procedure: ● Develop Project Claim Management Plan Section in the Project Design
Management Plan.
● Ensure that the Project Claim Management Plan Section in the Project
Design Management Plan is in alignment with the Project Claim
Management Plan Section in the NWC Project Management Plan.
● Consult with NWC Project Manager and Cluster Technical Services
Director about the development of the Project Claim Management Plan
Section.
● Include the Project Claim Management Plan Section in the Project
Design Management Plan to be approved as part of the Project Design
Management Plan.
Procedure: ● Ensure the up-to-date NWC Project Management Plan, with all approved
changes, is included in the Construction RFP.
● Ensure the requirement “The Contractor is required to create his own
Claim Management Plan and must submit it during the contractual
mobilization period” is stated in the NWC Project Management Plan.
● Ensure that the technical evaluation criteria for submitted technical
proposals includes Claim assessment criteria, which addresses:
○ the project requirements.
○ the past performance of the bidders.
19.2.4 Procedures
19.2.4.1 PMM-019-CLA-010-010 Identify Potential Claims by Reviewing Contract
Documentation
19.3.2 Policies
Policies for this process are as follows:
1. NWC team, Design Consultant, Supervision Consultant and Contractor are
responsible for directing and managing the project in manner of avoiding claims
through collaborative working between the project parties and fair and accurate
application of effective project planning, communication, control and variation
management.
2. All project parties are recommended to avoid “hardline” positions when dealing with
claims. However, authority levels for the decision making process should be
designated early in project life.
3. Constructability reviews to be performed as they much help identify problems with the
construction methods subsequently minimize the possibility of site problems during
construction which is a common source of claims.
4. Pre-tender meetings between the interested parties where various details, contract
requirements and owner expectations for the project are clarified prior to the
finalization of the contract help avoiding claims during construction. The request of
proposal (RFP) should be written in clear and unambiguous terms, including
statements in respect to the quantities the bidders should use as a basis for their bids.
5. All members of the project team should endeavor to:
● Identify potential claims and take steps to avoid or mitigate.
● Have frank discussions between parties to discourage spurious claims.
● Apply contract provisions for relief where justified.
● Create prompt resolutions for acknowledged changes.
6. Project manager is responsible for raising the awareness about the typical causes of
Claims to help to avoid potential claims. The early identification of potential claims
during project life the better probability to avoid the claim. Review the examples in the
introduction of this section.
19.3.3 Flowchart
Figure 19-4 PMM-019-CLA-020 Avoid Claims Flowchart
19.3.4 Procedures
19.3.4.1 PMM-019-CLA-020-003 Raise the Awareness about the Typical Claim Causes
Procedure: ● During all project life, the project manager shall raise the awareness of
the project team members about the typical causes of Claims to help to
early identify them to avoid or manage. It can be via:
○ periodic objectives cascading.
○ discussions in risk workshops.
○ discussions in lessons learned workshops.
○ progress meetings.
● See the key typical claim causes in the introduction to this section.
NWC Project Manager
Roles: Responsible:
Supervision Consultant
Accountable: NWC Project Manager
2. The claim should contain written description of all the works, or conditions, believed
to be outside the contract, with details as to where they occurred, when they took
place and why they are not covered by the contract.
3. Reference should be made to the sections and/or clauses (articles) of the contract
that support the claim contents. It is essential that reference is made on every activity
affected by the claimed works as well.
4. The claim should address the effect on the project schedule and any additional time
that might be required to complete the contract works.
5. All documentation of costs and time that related to a claim should be well recorded
and readily available. This documentation should be proper and thorough. Such
documentation may include photographs and videos of the works involved, as well
as, relevant contract sections and drawings, statements of professionals and
personnel involved, relevant correspondence, instructions, approved details or shop-
drawings and as build schedules. A cost accounting for the claimed works or
conditions is also required.
6. Submitted claims should include the following:
● Description of the work performed, delayed or impacted.
● Cost and schedule quantification.
● Contractual basis for entitlement (entitlement justification).
● Cost and schedule impact on project works.
● Requested relief in term of cost and time.
7. All quantities in claims should be measured in the BoQ measuring units.
8. A Claim cost Estimate should cover all direct and indirect claimed work aspects such
as manpower, equipment and material involved in the claimed works. This facilitate
of estimating and reviewing the claim cost.
9. Entitlement identification should be performed and completed independently from the
claim quantification.
10. Computer applications of cost and schedule can be used to partially or completely
prepare or analyze a claim.
11. The submitted full claim document becomes the working documented which the
defending party will use as the basis to formulate its defence, or its negotiation
strategy or acquiesce to the claimed costs and time.
19.4.3 Flowchart
Figure 19-5 PMM-019-CLA-030 Assess and Quantify Claim Flowchart
19.4.4 Procedures
19.4.4.1 PMM-019-CLA-030-010 Receive Claim
Procedure: ● Review claim documentation and claim scope including the scope
quantities to next confirm the contractual entitlement:
○ confirm the claimed scope is not included the project scope.
○ confirm the claimed scope is not covered by project insurance if any.
○ confirm the contract terms and conditions that the claim is based on.
○ confirm that any issues, circumstances and delay reasons are out of
the contract provisions and out of Contractor control.
○ request further supporting information and documentation as
necessary.
○ decide on the contractual entitlement.
● If there is:
○ a contractual entitlement, the claim documentation shall be further
processed.
○ no contractual entitlement, notify the claim developer by a claim
rejection letter indicating the rejection justification.
● Update the (PMF-007-INT-010 Project Variation Register) accordingly.
Cluster Contracts Administration Section Head
Roles: Responsible:
Cluster Technical Services Director (on design projects)
Supervision Consultant (on construction projects)
NWC Project Manager
Accountable: NWC Project Manager
Guidelines: ● The schedule and money involved should not be a factor in determining
entitlement.
● Essential elements for NWC team to achieve a thorough, balanced
conclusion:
○ Reading and studying all pertinent parts of the contract documents.
○ Becoming familiar with the language in the contract and any other
related documents, such as schedules, manuals, and supplements
that are made part of the contract.
○ Identifying the proper parties.
○ Determining the facts, using information from all relevant sources. A
full knowledge of the true facts is essential to reach a correct
conclusion.
○ Carefully examining the material presented by the second party as
proof of causation to spot any inaccuracies or ambiguities that may
discredit or negate all or part of the second party's claim. Requiring
that the second party prove a cause and effect relationship.
○ Asses technical validity and entitlement
Procedure: ● Review claim documentation and project progress reports to identify and
confirm the:
○ Claimed quantities of work.
○ Claimed extension of time.
○ Resources quantity.
○ Overhead quantity.
○ Any other aspects that will require a time and cost.
● NWC Project Manager shall forward the claim documents to one of the
following to develop a claim report indicating any claim impact. NWC
Project Manager shall incorporate any provided clarification replies or
additional information from claim developer (Contractor/consultant).
○ in design projects, to NWC Project Manager shall forward to the
followings to develop specialty reports for design, schedule, scope,
cost/budget and risk as applicable to the claim subject:
- Cluster Technical Services Director (for scope aspects)
- Cluster Value Engineering Specialist (for design aspects)
- Cluster Scheduling Section Head (for schedule aspects)
- Cluster Risk Section Head (for risk aspects)
- Cluster Cost Control Section Head (for cost aspects)
- Cluster Document Control Section Head (for administration
aspects)
Project Manager shall compile the specialty reports into one claim
report.
○ in construction projects, NWC Project Manager shall forward to the
Supervision Consultant. The cluster departments in the above step
shall be consulted as required.
● Previous step shall include calculating the associated indirect cost
including overhead cost.
● At any step of this procedure, if any additional information is required,
the requester shall request the NWC Project Manager to collect and
transmit it.
● Update the (PMF-007-INT-010 Project Variation Register) accordingly.
Supervision Consultant (on construction projects)
Roles: Responsible:
Cluster Contracts Administration Section Head (on design
projects)
Cluster Cost Control Section Head (on design projects)
Cluster Scheduling Section Head (on design projects)
Cluster Technical Services Director (on design projects)
Cluster Risk Section Head (on design projects)
NWC Project Manager
Year-to-date number of
projects in the cluster
Identify Potential
that its potential claims
Claims by
are not identified by
1 Reviewing Monthly 0 4 >4
reviewing the project
Contract
contract documents
Documents
project mobilization
period.
The year-to-date
average of to assess
Actual time to
and quantify a claim by
2 assess and Monthly 7 14 > 14
NWC team (and
quantify a claim
supervision consultant if
assigned) in the project.
Year-to-date number of
projects in the cluster
Projects completed that are:
3 with unresolved - closed with open Monthly 0 2 >2
Claims claims.
- can not be closed due
to open claims.
19.6 Attachments
The table below identifies mandated forms, templates and guidelines for this section (PMM-019-
CLA Project Claim Management).
Table 19-2 Project Claim Management forms, templates and guidelines
References
References:
● PMBOK R6 - (PMI)
● White Book - 2019 (Mashroat)
● Entity Five-Year Projects Portfolio Planning - 2019 (Mashroat)
● Stage Gates Process - 2018 (Mashroat)
● Cost Estimate Classification System - 2019 (AACE)
● Value Methodology Standard Reference - 2020 (SAVE International)
● ISO 9001 Quality Management Systems - Requirements (ISO)
● Project Management Manual PMM - 2012 (NWC)
● Capital Projects Policy - 2020 (NWC)
● Governance Document - 2020 (NWC)
● Projects Processes and Procedures Manual - 2014 (NWC)
● Government Tender and Procurement System and Regulations - 2020 (MOF)