Project - Execution.Plan - JAG2.REV.00 Compressed PDF
Project - Execution.Plan - JAG2.REV.00 Compressed PDF
Project - Execution.Plan - JAG2.REV.00 Compressed PDF
net/publication/347563526
CITATIONS READS
0 21,087
1 author:
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Jose Agustin Gonzalez on 22 December 2020.
REVIEWED 29/11/2020
AUTHORISED
01 PREPARED
REVIEWED
AUTHORISED
02 PREPARED
REVIEWED
AUTHORISED
03 PREPARED
REVIEWED
AUTHORISED
04 PREPARED
REVIEWED
AUTHORISED
05 PREPARED
REVIEWED
AUTHORISED
06 PREPARED
REVIEWED
AUTHORISED
07 PREPARED
REVIEWED
AUTHORISED
08 PREPARED
REVIEWED
AUTHORISED
09 PREPARED
REVIEWED
AUTHORISED
10 PREPARED
REVIEWED
AUTHORISED
DOCUMENT DISTRIBUTION
No Name Location
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DOCUMENT´S PROPERTIES
TABLE OF CONTENT
1 INTRODUCTION ...................................................................................................................................... 13
9 ENGINEERING ........................................................................................................................................ 40
10 PROCUREMENT .......................................................................................................................... 45
11 CONSTRUCTION ......................................................................................................................... 49
12.3.3 CODES............................................................................................................................ 52
13.5.1 ACCESS.......................................................................................................................... 56
TABLE OF FIGURES
Figure 1 – Develop Project Charter – Section 4.3.2 ISO 21500:2012 ................................................................ 15
Figure 19 – Identification and Classification of Stakeholders – Section 4.3.9 ISO 21500:2012 ......................... 69
LIST OF TABLES
TABLE 1 – PROJECT DETAILS.................................................................................................................................. 15
TABLE 2 - THIS PROJECT CHARTER SHOULD BE READ IN CONJUNCTION WITH THE FOLLOWING DOCUMENTS ................ 15
1 INTRODUCTION
1.1 INTRODUCTION
This Project Execution Plan (P.E.P.) provides a clear and concise summary of the [Project Name]
Project for all parties involved in its delivery both internally and externally.
It provides a baseline position statement about the project as it enters the Detailed Design stage,
against which progress can be monitored and a clear audit trail through to final handover to Client´s
Operations Team.
This document describes The PMO´s intended execution plan for the Implementation Phase through
to and including commissioning of the full chain. The execution plan is the governing document that
establishes the means by which The PMO will execute, monitor and control the [Project Name] Project,
and will serve as the main communication vehicle to ensure that everyone is aware of project objectives
and the mechanisms by which they will be accomplished. It covers all The PMO´s full chain activities
including:
The purpose of this document is to initially identify the parameters and the priorities of the [Project
Name] Project. In addition this document will form the basis for the Monitoring, Evaluation & Co-
Ordination of the various actions and procedures throughout the life of the project.
The P.E.P.:
7. Allows consistent communication across the integrated team for the project’s plans and
processes to execute the required scope;
8. Provides a reference document for project team members.
This P.E.P. does not provide a full description of all the policies, procedures and work instructions that
will be required to execute the work. These will be developed separately and in line with the required
scopes of work defined in the P.E.P.
As this is The PMO´s P.E.P. it does not attempt to describe how The PMO´s EPC Contractors intend
to manage their elements of the work but it does define how The PMO will interface with and between
them, as well as describing how The PMO plan to execute their own work.
The P.E.P. is a living document and will be updated to describe current and future processes and
procedures, such as integrating safety into the design process. Updates will be prepared as the project
moves through the main project phases of engineering, construction and commissioning.
Any change to this P.E.P. or the Division of Work (DoW) schedule will be managed through The
PMO´s Management of Change (MOC) process.
Contact with representatives from television, radio, newspapers, magazines can only be entered into
with the express approval of the Project Manager who will consult with the Client. Publishing of
material in relation to the project must likewise be approved by the Project Manager/Client.
2 PROJECT/PROGRAMME DETAILS
PROJECT/PROGRAMME NAME
PROJECT/PROGRAMME SPONSOR
PROJECT/PROGRAMME MANAGER
3 PROJECT DOCUMENTS
The project charter links the project to the strategic objectives of the organization and should identify
any appropriate terms of reference, obligations, assumptions and constraints. The primary inputs and
outputs are listed in Table 2, page 15.
Table 2 - This Project Charter should be read in conjunction with the following documents
This Project Execution Plan is the combination of the Project Plan and the Project Management
Plan and is developed to reflect the integration of:
It also contains the baselines for carrying out the project, e.g. in terms of:
1. Scope, 4. Costs,
2. Quality, 5. Resources, and
3. Schedule, 6. Risks.
All parts of this Project Execution Plan are consistent and fully integrated. The plan describes how
the management of the individual subsidiary plans are integrated and coordinated. The subsidiary
plans for this project are listed in Table 3, page 17.
1.
2.
3.
This Project Execution Plan shall always be updated and communicated to appropriate stakeholders
throughout the project.
4 PROJECT OVERVIEW
1.
2.
3.
The delivery of the objectives listed above are constrained by the following e.g.:-
…..
.....
…..
The purpose of Control Scope is to maximize positive and minimize negative project impacts created
by scope changes.
This process shall focus on determining the present project scope status, comparing the present scope
status to the approved baseline scope to determine any variance, forecasting scope and implementing
any appropriate change requests to avoid negative scope impacts.
The individual programme and project interfaces are as per those identified below.
1. Government 7. Competitors
2. Economic climate 8. Suppliers, sub-contractors, consultants
3. Finance 9. Owner (customer, client)
4. Community groups 10. Cultural interfaces
5. Media 11. Other external interfaces
6. Regulatory agencies
Timely delivery of the project within budget is based upon the following key assumptions.
Table 5 - Assumptions
1.
2.
3.
Governance, according ISO 21500:2012, is the framework by which an organization is directed and
controlled. Project governance includes, but is not limited to, those areas of organizational governance
that are specifically related to project activities. Project governance may include subjects such as the
following:
The responsibility for maintaining the appropriate governance of a project is usually assigned either to
the Project Sponsor or to a Project Steering Committee. Required approvals and approving
authorities are set out in Table 6.
1.
2.
3.
Table 6, Table 7, and Table 8 list the key personnel, advisors and third parties associated with the
scheme and sets out their roles and responsibilities.
1.
2.
3.
1.
2.
3.
Table 8 sets out the key approval authorities in relation to the project. The list is in no way exhaustive
and all necessary checks should be carried out in relation to third party approvals prior to any project
work commencing.
1.
2.
3.
Table 10, on page 27, summarises the key high level project tasks and deliverables and the member
of the project management team responsible for each task or deliverable.
It should be noted that existing line management and staff in each of the Working Groups will be
expected to take responsibility in each of their functional areas with regard to the performance of these
workgroup activities.
The role of the project team, with some exceptions, will not be to undertake the activities directly itself
but to ensure that the activities are
Tasks
Office (PMO)
Management
Lead Press
Manager
Manager
Planning
Project
Project
Office
1. Prepare, update and manage Project Programme at each
project phase
1.
2.
3.
The principal focus of the programme management process is vested in the roles and responsibilities
defined in Table 12 below:
1.
2.
3.
The project includes a hierarchy of sub-programmes, which can be rolled up into a master programme.
Programme changes shall be adopted or rejected through the Project Change Management process
which is currently under development. Any programme change shall be analysed for wider impacts to
the project in terms of, risk, programme, cost and quality. All changes shall be ratified by the Steering
Committee.
On a monthly basis, or where an event arises which has a significant impact on the project programme,
a baseline review by the Project Management Office will take place and, if appropriate to do so, the
Master Programme will be re-baselined. Proposals to re-baseline the Master Programme shall be
submitted to the Steering Committee for information.
The Master Programme will be reviewed on a regular basis (normally monthly) and actual progress
will be updated and reviewed against planned (baseline) progress. The results of this review will be
reported in the Project Monthly [Bi-monthly] Steering Committee Report.
A series of Progress Reports shall be produced throughout the Project Life-Cycle to provide an up
to date and accurate report of actual progress against planned. Table 16 lists the progress reports that
shall be produced along with their frequency, circulation and owner:
A series of Progress Meetings shall be held throughout the Project Life-Cycle to provide a forum for progress review, resolution of key progress issues
and identification of key actions. Table 17 lists the progress meetings that shall be held along with their frequency, key attendees and chairperson:
1.
2.
3.
The procedures for the development, management and update of the project budget are set out in the
following standards:
4.
5.
6.
The principal focus of the cost management process is vested in the roles and responsibilities defined
in Table 19 below:
1.
2.
3.
4.
5.
6.
7.
8.
1.
2.
3.
4.
The budget may be updated from time to time as the project develops. Budget updates may be
required as a result of:
Budget changes shall be adopted or rejected through the Project Change Management process.
Budget changes which involve transfers between budget line items with no change to the overall total
budget and no reallocation of the risk or contingency line items must be approved by the Project
Manager. The Project Manager however cannot transfer budget from capital contributions approved
by the Sanctioning Authority).
Budget changes which involve reallocation of the risk line item must be approved by the [Insert Title].
Budget changes which involve reallocation of the contingency line item must be approved by [Insert
Title].
Budget changes which result in an increase in the overall budget total as set out in the approved
Detailed / Final Business Case must be approved by the PPM Board.
On a quarterly basis, or where an event arises which has a significant impact on the project budget or
schedule, the Project Cash Flow Forecast will be updated and advised to the Project Manager.
1.
2.
3.
4.
5.
A series of Contract Review Meetings shall be held throughout the Project Life-Cycle to provide a forum for cost, budget and claims review, resolution
of key issues and identification of key actions. Table 22 lists the meetings that shall be held along with their frequency, key attendees and chairperson:
1.
2.
3.
4.
8 RISK MANAGEMENT
It is fundamentally important that a sound and effective Risk Management philosophy and process is
followed. In combination with other aspects such as the management and engineering processes, Risk
Management enhances visibility into the project activities, strengthens decision making and facilitates
the project goals. Risk Management is already an integral part of the management of the project in
the Preparatory Phase and will continue to occupy a central position throughout the Project Life-
Cycle. As the project progresses, the nature of the risks and the context and environment in which
they will have to be managed, will change and therefore this Risk Management Process will be
reviewed and adapted on a regular basis.
The Risk Management Program will be established at all levels and within all domains of the project.
It will be maintained and managed by the Project Managers and System Engineers.
The integration of the Risk Management effort across the project will be the responsibility of the
Project Managers and Project/System Engineers. An overall and integrated Risk
Register/Database will be established and maintained and will be the central source of information on
the status of risks and will be utilised for management of the risks as well as internal and external
communication purposes.
Communication will form the backbone of a successful Risk Management structure and participants
will be encouraged to communicate freely, openly and regularly on these aspects.
Regular reporting and communication to external stakeholders will also be conducted. For this purpose
appropriately condensed and rolled up information from the centralised Risk Register/Database will
be utilised.
Regular risk focus events will be conducted. These events will include:
Brainstorming sessions,
Risk assessment workshops,
Work sessions during Technical Design Reviews,
External review(s) of risk register/database,
Structured or semi-structured interviews with experts,
Using knowledge, expertise and experience of team,
Failure Mode and Effect Analysis (FMEA), and
Fault Tree Analysis (FTA)
Id Description of Risk Impact on Change Date of Mitigation Actions Responsibility Cost Timeline Work
Grade (combined
(including any Project Review (Preventative or for mitigation for Breakdown
identified ‘triggers)
Assessment of
Assessment of
(Identify Contingency) action(s) mitigation
Likelihood and
Structure
Seriousness
Seriousness)
consequences) action(s)
Likelihood
1.
2.
3.
4.
5.
6.
7.
8.
9.
The procedures for the identification, assessment, and mitigation of project risks are set out in the
following standards:
1.
2.
3.
The detailed project Risk Management structure, roles and responsibilities are defined in the Project
Risk Management Plan. The principal focus of the Risk Management process is vested in the roles
and responsibilities defined in Table 25 below:
Project Manager
Project Controls
Manager
Planning Manager
Project/System
Engineers
Risk Owners
Action Owners
The project includes a hierarchy risk classifications, which can be rolled up into a single risk register.
The Risk Register is key document which provides full details in relation to
The development of the Risk Register is an iterative process and requires sustained effort to fully
The Risk Register will be reviewed on a monthly basis and actual progress in implementing mitigation
actions will be reviewed against planned progress. The results of this review and a summary of the
status of the top 3 project risks will be reported in the Project Monthly Report.
9 ENGINEERING
All EPC Contractor scope will comply with the relevant codes and standards in force at Contract award,
and with safety, legal and other regulations (local and national), acts and legislation in force in the
country in which the project is being executed.
In addition, EPC Contractor scope will be required to comply with the particular codes and standards
specified in the Contract. Such codes and standards will be the latest editions with applicable addenda
and code cases in effect on the Contract award date. Application of subsequent addenda and code
cases published after Contract award will be subject to agreement between The PMO and respective
EPC Contractors.
The PMO Delivery Team will implement a formal Engineering Change Management process. The
process will manage Design Development Change to ensure that a safe and operationally robust
design is achieved that allows the project to be executed in accordance with
Changes will be carefully assessed to ensure that they add value; following this the timing of
implementation will be assessed and a decision made on whether to implement.
1.
2.
3.
4.
5.
6.
The procedures for providing the engineering services, and works for all projects are set out in the
following engineering procedures listed in Table 27 below:
1.
2.
3.
4.
5.
6.
The principal focus of the engineering management process is vested in the roles and responsibilities
defined in Table 28 below:
1.
2.
3.
4.
5.
6.
The PMO Engineering Manager is accountable for assuring design quality for the design intent of the
final operating facility and interfaces across the full chain. The PMC will undertake assurance of the
operating facility on behalf of the PMO Engineering Manager. The PMO Engineering Team, reporting
to the PMO Engineering Manager, are responsible for assurance of the interfaces across the full chain.
Assurance activities will be risk based and derived through Criticality Assessment of all packages
and equipment. Criticality Ratings will be used to determine the required level of design verification,
procurement and construction Quality Requirements and will be included in the Project Assurance
Plan.
A Value Engineering process will be implemented with the Property´s Operations Team and
Interconnections with EPC Contractors targeting improved profitability.
The PMO Delivery Team, in conjunction with the PMO Project Sponsor, will define the value factors
to be used to assess any Value Engineering options that impact the project programme or operational
performance.
Value management will be managed on behalf of the PMO Engineering Manager by the PMC, with
changes that impact the project programme, budget or operational performance referred in the first
instance to the PMO Engineering Manager for approval/endorsement and subsequent elevation to
the PMO Project Sponsor if required.
Engineering activity each month will be reported in the Project Monthly Report.
Collects
Defines and Project
Sufficient and
2 Assigns Scope to Data and
Necessary
Engineer Specs
Data
Prepares
Calculation Input
Sheet
Yes
Validates
Comments?
Input Data
No
Yes
Automated Calculations
Soft Ware
Manual
No Selection and Comments?
Calculation?
Validation
Yes No
Validates
Proceed
Calculation Yes
Methodology
Comments?
1
Executes
No
Calculation
Discipline
Yes
Check
Comments? No Comments?
Yes
Engineering Doc
Issue for Design No
Execute
1 Automated 2 Yes Yes
Calculation
Discipline
Comments? No Comments?
Check
Engineering Doc
Issue for Design No
Material Prepares
Requisition Solicitation
Documents
Solicitation Process
Documents to Project
Suppliers Specific
Requirements
Reply to
INPUT Yes Queries?
Queries
No
Prepares/Rev
Technical &
Commercial
Proposal
Technical Technical
Technical Bid
Proposal to Proposal
Analysis
Engineering
Commercial Bid
COMPANY
evaluation Report
Approval
Award
Decision by
Award
Commitee
Prepare &
Final Material
Issue
Requisition
Purchase
Order
Coordinate
Inspections
INPUT No Compliance?
Certifications
Release
10 PROCUREMENT
The purpose of Plan Procurements is to plan and document the procurement strategy and overall
process properly before procurement is initiated. This process is used to
1. To ensure that information is obtained from suppliers so that there is consistent evaluation of
proposals against stated requirements;
2. To review and examine all the submitted information;
3. To select the suppliers.
1.
2.
3.
4.
5.
6.
7.
1.
2.
3.
4.
5.
6.
7.
The procedures for the procurement of services, works and supplies for all projects are set out in the
following Procedures:
1.
2.
3.
4.
5.
6.
7.
The principal focus of the procurement management process is vested in the roles and responsibilities
defined in Table 32 below:
1.
2.
3.
4.
5.
6.
7.
Procurement activity each month will be reported in the Project Monthly Report.
Contract Strategy
The form of contract to be used for each Working group is set out in the Table 33.
11 CONSTRUCTION
The method statements for executing the construction services, and works for all projects are set out
in the following method statements listed in Table 34 below:
1.
2.
3.
The principal focus of the construction management process is vested in the roles and responsibilities
defined in Table 35 below:
1.
2.
3.
4.
5.
6.
7.
8.
Construction activity each month will be reported in the Project Monthly Report.
All Testing and Commissioning should be undertaken after the Construction work has been completed
and cleaned within each phase.
System Testing is performed on a complete integrated system to evaluate the compliance of the
system with the corresponding requirements. System Testing is basically performed by a testing team
that is independent of the development team that helps to test the quality of the system impartial. It has
both functional and non-functional testing.
1.
2.
3.
The principal focus of the testing management process is vested in the roles and responsibilities
defined in Table 37 below:
1.
2.
3.
A master testing programme will be prepared for each system together with detailed programmes
indicating the testing stages and their requisite time duration and the dates when the system will be
available. The programmes will reflect the nature of the construction programme, the appropriate
method statements.
Testing activity each month will be reported in the Project Monthly Report.
12.2 COMMISSIONING
Project Commissioning is the process of assuring that all systems and components of a building or
industrial plant are designed, installed, tested, operated, and maintained according to the operational
requirements of the owner or final client.
1.
2.
3.
The principal focus of the commissioning management process is vested in the roles and
responsibilities defined in Table 39 below:
1.
2.
3.
4.
5.
6.
7.
8.
A master commissioning programme will be prepared for each system together with detailed
programmes indicating the commissioning stages and their requisite time duration and the dates when
the service will be available. The programmes will reflect the nature of the construction programme,
the appropriate method statements.
Testing activity each month will be reported in the Project Monthly Report.
All Commissioning and Testing should be undertaken after the Construction work has been completed
and cleaned within each phase.
12.3.1 RESPONSIBILITY
The Main Contractor shall be responsible for the testing and commissioning of the Mechanical services.
The Engineer will, where appropriate, witness testing to ensure the results are satisfactory to allow
commissioning to commence.
12.3.2 CERTIFICATES
The test and inspection certificates shall be signed by the Engineer the Main Contractor once the test
and inspection is considered satisfactory.
12.3.3 CODES
All wires shall be inspected, tested and commissioned in accordance with all relevant Standard,
specifications, codes of practice and tender documents.
12.3.4 COMMISSIONING
The Main Contractor will ensure that the mechanical and electrical services are brought to a fully
operational status.
The Main Contractor will demonstrate to the Engineer the appropriate commissioning tests and on
satisfactory completion the tests results will be signed-off by the Main Contractor and the Engineer.
Details of outstanding defects will be prepared by the Engineer for action by the Main Contractor.
12.3.7 RECORDS
Complete and comprehensive records of the installation tests and commissioning must be maintained
by the Contractor.
The Main Contractor and the Property´s representatives shall attend a Site meeting to undertake final
acceptance tests of all mechanical and electrical engineering services.
Where the final acceptance test does not meet the acceptable level of performance established in the
performance test, the system will be required to be reset and tested,
The system must be operated for a period of two weeks during which the system’s performance will be
monitored, recorded and compared with the performance criteria specified in the contract
documentation.
The item(s) listed on the defects list will be checked to ensure completion.
12.4.2 APPROVALS
12.4.3 STATUTORY
12.4.4 INSURANCE
The testing and commissioning must be in accordance with current Standards and must be undertaken
in the presence of the Engineer, and must be completed to the satisfaction of the Property´s
representative(s).
The installation must meet the requirements of all applicable statutory legislation.
A master commissioning programme will be prepared for each service together with detailed
programmes indicating the commissioning stages and their requisite time duration and the dates when
the service will be available. The programmes will reflect the nature of the construction programme,
the appropriate method statements.
The production of Operating and Maintenance Manuals should be the clear responsibility of the
Contractors. The requirement to produce such manuals will be a contractual requirement of all trade
contractors. Their submittals will incorporate:
The responsibility for ensuring that the sub-contractors produce this information is vested in the
contractor. In certifying Substantial Completion the Contract Administrator will need to be satisfied that
this documentation is available.
The certificate of practical completion for any phases of the works will be issued by the Engineer who
will examine the entire facility and will only issue the certificate of practical completion when he is
satisfied that:
Details of the requirements for the above will be contained in the contract documents.
1.
2.
3.
1.
2.
3.
4.
5.
6.
7.
8.
The Contractor shall ensure that its obligations under the Health & Safety at Work Act and specific
Regulations are carried out.
Site Address:
…………………
…………………
…………………
…………………
The Property should ensure that its obligations under the Health & Safety at Work Act and relevant
Health & Safety Regulations are carried out.
The Principal Contractor must ensure compliance with Specific Regulations and all relevant Health and
Safety legislation.
The Property will appoint a Health & Safety Coordinator under the Construction Design & Management
Regulations.
A pre-construction Health & Safety Plan will be prepared. Prior to commencement of the main contract
works the Principal Contractor will develop the Health & Safety Plan. The Property´s Coordinator will
confirm that this has been sufficiently developed before works can commence.
13.5.1 ACCESS
Personnel All visitors to the site must report to the site office with the route being clearly
delineated and clear of hazards. Underfoot conditions must be suitable for
pedestrians.
Vehicle Suitable access should be provided by the Contractor for heavy goods vehicles,
heavy plant and machinery, cranage, and skips etc.
Statutory Requirements All statutory requirements must be adhered to and all hardstanding’s must be
regularly cleaned.
13.5.2 STORAGE
The Contractor must provide adequate site storage for materials on site.
1. Name Board: The Contractor will, provide, maintain and take down a name board to display the
title of the contract, the names of the Employer, Employer’s representatives and the Contractor.
2. Use of Car Parks: Car Parking will be managed and controlled by the main contractor.
Access to site will be managed and controlled by the main contractor. The main contractor will ensure
the security of the site at all times. Security of the adjacent …………………………. must not be
compromised by the works.
Work out with normal working hours will require to be sanctioned and monitored by the Project Manager
and will be strictly controlled by The University of Strathclyde.
14 ENVIRONMENTAL STANDARDS
1.
2.
3.
1.
2.
3.
4.
5.
6.
7.
8.
The Project Design Team and Principal Contractor must ensure compliance with the Property´s
standards in relation to the Environment and Sustainability. The Project stakeholders should refer to
the actual legislation on Management Sustainability Policy.
The effect of any environmental hazards will be addressed through the consideration of the treatment
and disposal of waste materials.
Contract documents should include clauses to accommodate the requirements of the project.
Waste control methods should be assessed and agreed with the trade contractors with consideration
being given to:
15 ISSUES MANAGEMENT
In order to ensure the success of the project, all key issues will be identified and reported through the
reporting process. Where appropriate issues arise they will be assigned a priority according to the
extent and severity of their impact.
These issues to be assigned to the appropriate personnel to ensure their resolution and take whatever
actions are necessary.
Issues will be proactively managed until resolved. An Issues Register of the key issues, describing:
16 QUALITY MANAGEMENT
The purpose of Plan quality is to determine the quality requirements and standards that will be
applicable to the project, the deliverables of the project and how the requirements and standards will
be met based on the project objectives. This process includes the following:
1. Determining and agreeing with the project sponsor and other stakeholders as to the objectives
and relevant standards to be achieved;
2. Establishing the tools, procedures, techniques and resources necessary to achieve the relevant
standards;
3. Determining methodologies, techniques and resources to implement the planned systematic
quality activities;
4. Developing the quality plan which includes type of reviews, responsibilities and participants in
a timetable in accordance with the project overall schedule;
5. Consolidating all quality information in the quality plan.
The Project Manager will, in conjunction with the Engineering Team, the Procurement Team, and
the Construction Team, establish a Project Quality Plan to ensure a clear understanding of the
required quality and performance standards both from the Engineering Team, Procurement Team,
and the Construction Team.
The primary goal of the Quality Management Process for this project is to ensure business and
governance needs have been adequately satisfied. Ongoing quality management involves careful
evaluation and monitoring of objectives and deliverables, together the assessment of stakeholder
feedback and the implementation of changes to project methodology or management as appropriate.
Quality Control will therefore be an integral element of the Project Governance Process and will be
considered by the Project Governance Board at its monthly meetings. Specifically
1. The project will be managed in accordance with the governance structure outlined at 5.2, page
24 above. Roles and responsibilities are also detailed.
2. This document provides an outline of the overall project objectives. The key milestones and
deliverables of the project are outlined in more detail in the accompanying Project Schedule
and will be subject to approval of the Governance Board.
3. In addition to the project/activity Quad Report that will form the basis for monthly reports a
consolidated Actions, Issues and Risk Log will be maintained which will provide oversight of all
such matters to the project Governance Board and team.
4. The full time project team will meet on a weekly basis to discuss progress and identify issues
which need to be progressed.
5. In relation to any system development, structured testing will take place including system test,
load & stress testing, User Acceptance Testing (UAT) and parallel run testing as appropriate.
6. A Change Control Process will be utilised to support agreed project objectives and scope.
4.
5.
6.
The principal focus of the quality management process is vested in the roles and responsibilities
defined in Table 8.1 below:
Project Manager
Project
Management Office
Quality Manager
Quality Assurance
Manager
Quality Control
Manager
16.4.1 GENERAL
The quality requirements set out in this Project Execution Plan are applicable to the <name of project>
project in all phases. This section 16.4 describes essential aspects of quality on the project including:
Objective: Collect and communicate valuable lessons learned in different phases of the project from
previous projects both internal and external.
Continuously improve the quality of project management processes based on lessons learned and
ensure any strategy takes account of such lessons.
1.
2.
3.
4.
5.
6.
1.
2.
3.
4.
5.
6.
1.
2.
3.
4.
The Quality Manager will perform internal and external quality audits at different stages of the Project.
The scope of any quality audit may cover the overall quality management system, quality assurance
system and/or quality management system on the project or any individual process in relation to quality
management.
A Project Quality Audit Programme will be prepared by the Quality Manager and audit reports
maintained as quality records.
Quality Records: Quality Audit Programme and internal and external Quality Audit Reports.
Continuous improvement is a principle of the project’s Quality Management criteria. The project quality
systems, plans and procedures will be reviewed regularly to ensure all lessons learned, suggestions
and discoveries from audits are taken into account to continuously improve The PMO Project Quality
Management processes and procedures.
Information requirements will be clarified between the Contractors and the Client’s representatives.
It is essential that the contractors are fully aware of requirements in respect of the scope, nature and
quality of the drawing information and specification details required, certificates and testing and quality
of workmanship in order that they can provide evidence of their suitability given the requirements of
the project.
Tender documentation will include provisions relating to control mechanisms for the testing, inspecting,
reporting and recording of the quality of work.
Contractors must submit in writing the proposed methods by which compliance with the specified
requirements will be achieved.
Samples of components and workmanship should be obtained prior to work commencing on site.
The Quality Plan will incorporate comments and procedures in relation to:
Programme and Procurement Schedule will be produced which will identify the contractor’s intended
work patterns for the contract.
Tender Documentation will include descriptions in relation to scope of work, specification, workmanship,
quality assurance and programme.
All equipment to be used in the project must meet safety legislation requirements and have the
necessary safety certificates. Equipment must be subject to appropriate controls and properly
calibrated. The Contractor will be responsible for ensuring that all sub-contractors comply with this
requirement.
It should be particularly noted that where an item of equipment’s safety certificate expires the
equipment must be removed from the site or made inoperative.
In order to achieve the appropriate workmanship standards reference and adherence should be made
to Industry Standards for procurement, testing and commissioning.
Sub-contractors and suppliers should be subject to stringent management to ensure compliance with
workmanship standards. Work should therefore be supervised and inspected by suitably qualified staff.
Progress will be reviewed at regular progress meetings with remedial action instructed where
appropriate. These measures will also include quality audits.
Inspection and testing will be initiated by experienced members of the Project Team and remedial
action taken when required.
Remedial work to prefabricated components will be allowed only with the prior approval of the Project
Manager.
Records will be maintained of all inspections and tests which must all be witnessed by the main
Contractor and where appropriate by the Services Consultant. Standards and Codes of Practice by
which the inspection and testing procedures will be measured are to be included within the Contract
Documentation.
Sub-contractors and suppliers will be selected on criteria which include their proven ability to protect
and handle materials.
Method Statements should also be requested from sub-contractors and suppliers where required.
17 PROJECT ADMINISTRATION
This section of the Project Execution Plan sets out the procedures for managing project
administration including:
The principal focus of project administration is vested in the roles and responsibilities defined in Table
50 below:
1.
2.
3.
4.
5.
6.
7.
8.
The document numbering system on the project is generated automatically in the correspondence
control package, [Insert]. All documents issued externally are also accompanied by a transmittal
generated through [Insert].
Reports and other documents shall be stored on the (to be decided by project sponsor). Reports are
issued and received via Expedition.
All Contract correspondence should be received and issued via Expedition. All scanned documentation
shall be attached to the electronic correspondence log by the Document Controller. It should be noted
all contractual correspondence should be received and issued in hard copy following the procedures
within the <insert name of this project> Document Control Procedure. Documents, drawings and
sketches being submitted by post must be submitted in hard and CD copy format.
All Project Team members should obtain access onto the Expedition system and go through the
training related to the software; this training is provided by <designated entity> and should be requested
via the Document Controller. As a safeguard all incoming correspondence, once logged into Expedition,
should also be emailed to team members on the distribution list.
Received letters shall be recorded in Expedition by the document controller. All received letters are to
be reviewed and distributed or approved by the Project Manager.
Letters should be generated through Expedition, the letter printed on Project Headed paper, signed by
the Project Manager, scanned and sent to the Document Controller for issue.
FREQUENCY /
No MEETING CHAIR PURPOSE OUTPUT
TIMING
1.
2.
3.
4.
Minutes should be recorded for all meetings. Minutes generated within Expedition record actions as
new, old or closed. All minutes, whether generated in expedition or not, should be printed on Project
headed paper, signed, scanned and given to the Document Controller for issue.
Induction briefings to all new staff working on the project shall be conducted by the relevant line
manager. The content of this induction shall include:
Insert
17.7 SOFTWARE
Table 52 describes software packages which have been authorised and licensed for use on the Project,
including versioning.
1.
2.
3.
4.
18 STAKEHOLDER MANAGEMENT
The key stakeholders and their respective liaison manager are provided in Table 53 below:
1.
2.
3.
4.
The stakeholder management process commences with identification of all stakeholders that can affect,
or be affected by the project, directly or indirectly. During the lifetime of the project; stakeholders may
come and go depending on the activities at any one time.
In identifying the stakeholders on the project, the following questions were considered:
All projects are split into distinct phases. This project is currently moving from the [insert] phase into
the [insert] phase.
Any person looking to liaise with a stakeholder must firstly liaise with the person identified in Table 53
above to ensure that the particular stakeholder is being managed effectively. Issues raised during
stakeholder liaison must be fed back to the responsible person to ensure all issues are captured.
The responsible person co-ordinates all activities in relation to their stakeholder and must record all
stakeholder issues. Issues involving changes are dealt with using the Change Management
Procedure.
A stakeholder register will be kept that can be accessed by all relevant members of the Project Team,
and it is the responsibility of all team members to keep the register updated as consultation progresses
by forwarding any updated information to the appointed editor which requires inclusion in the Register.
The project will maintain a register of all commitments made to Stakeholders. The register shall track
progress in implementing the commitments.
Regular internal meetings will be convened between the persons responsible for stakeholder liaison to
discuss and agree the best course of action for each stakeholder where applicable. Stakeholder issues
will also feed into project development through the series of meetings.
The Project has developed a Stakeholder Communications Plan; the purpose of this plan is to ensure
effective communications with stakeholders in relation to the development and implementation of plans
for the delivery this project.
Insert