PROJECT EXECUTION PLAN Project Name

Project Execution Plan

---------------------------- Project
Client :
Contract No :
Cost Centre No :
Commencement Date :
Project Duration :

1
 PROJECT EXECUTION PLAN Project Name

Document Control
Document Information

Information
Document Id [Document Management System #]
Document Owner [Owner Name]
Issue Date [Date]
Last Saved Date [Date]
File Name [Name]

Document History

Version Issue Date Changes

[1.0] [Date] [Section, Page(s) and Text Revised]

Document Approvals

Role Name Signature Date

Project Engineer
(Name)
Project Manager

(Name)
PMO Head
(Name)
GM
(Name)

2
 PROJECT EXECUTION PLAN Project Name

Contents

1. Overview
1. Executive Summary
2. Management Summary
2. Project Scope
1. Included
2. Excluded
3. Organization
1. Organizational Boundaries and Interfaces
i. Client
ii. Sub-contractors
iii. Suppliers
2. Project Organization
i. Project Management Team
ii. Project Execution Team
3. Project Organization Chart
4. Project Constraints
1. Project Constraints
2. Critical Project Barriers
3. Long Lead Items
5. Schedule and Budget
1. Work Breakdown Structure
2. Schedule and Milestones
3. Resources
4. Budget
6. Risk Management
7. Sub-contract Management
8. Communication and Reporting
9. Sign Off Sheet

3
 PROJECT EXECUTION PLAN Project Name

Overview

1. Executive Summary

This section will summarize the entire document by describing the background for the project and the proposed
Vision, Goals and Timeframes. So summarize each of the sections in this document concisely by outlining the:

requirements and proposed solution

Project deliverables and timeframes
Resources, budget and success criteria.

(All in red would be removed for every project & actual information will be added.)

i. Background

1. Requirements

Requirement that result in the execution of the project should be mentioned here or if you
have any requirements to avoid problem or risk areas, you can mention them here.

(All in red would be removed for every project & actual information will be added.)

2. Proposal

In the background section above, you have described the general basis upon which the
project will be created. You've described the problem or opportunity that exists in the business
and the solution that the project needs to deliver. In this section, it is now time to describe the
project that you are proposing is initiated.

(All in red would be removed for every project & actual information will be added.)

3. Project deliverables

Where possible, try and link in the business problem or opportunity into the Vision so that the
project team knows exactly what is being solved by the vision.

(All in red would be removed for every project & actual information will be added.)

4
 PROJECT EXECUTION PLAN Project Name

Management Summary

DATE OF COMMENCEMENT :

DATE OF COMPLETION :

DURATION (Days) :

CONTRACT VALUE :

PROVISIONAL SUM :

Project Scope

Clarify what the project will (and will not) deliver, in order to avoid future shifts in the level of ambition.
i. Included

ii. Excluded
State what is specifically excluded from the project but what the customer may expect to be included. This
could, for example, be clarifying that training of end-users is excluded.

5
 PROJECT EXECUTION PLAN Project Name

Organization

Describe the internal project organization and all organizational issues affected by the project result or the project is dependent on

i. Organizational Boundaries and Interfaces

a. Client
Client Name :
Team Leader :
Engineers in charge :

b. Sub-contractors
Sl.# Subcontractor Name Scope of Work Target Finish Date Remarks

c. Suppliers
Sl. # Supplier Name Material Supplied Target Finish Date Remarks

ii. Project Organization

a. Project Management Team

Project
management
Team

Procurement
HR Team
Team

Supply Chain
Finance Team
Team

6
 PROJECT EXECUTION PLAN Project Name

b. Project Team

PROJECT
MANAGER

PLANNING
ENGINEER

MECHANICAL ELECTRICAL
CIVIL ENGINEER
ENGINEER ENGINEER

MECHANICAL ELECTRICAL
CIVIL FOREMAN
FOREMAN FOREMAN

Project Constraints

i. Project Constraints

Sl. # Constraint Items Type of Constraint Constraint Date Remarks

ii. Critical Activities/ Long Lead Items

Sl. # Description Duration Remarks

7
 PROJECT EXECUTION PLAN Project Name

Schedule and Budget

i. Work Breakdown Structure

Cum. Plan %
Description TOTAL WT % Remarks
Progress % WT

1 HSE, PHSER & EIA STUDIES

2 ENGINEERING

3 PROCUREMENT

4 CONSTRUCTION

5 TRAINING

6 TESTING & PRE-COMMISSIONING

7 COMMISSIONING

Total

iii. Milestones

Act. ID Activity Start Finish Remarks

iv. Schedule

Detailed Gantt chart showing project schedule

8
 PROJECT EXECUTION PLAN Project Name

v. Resources

In order to approve the Project Execution Plan, PMO head will want to have an
understanding of the amount of resources required to undertake it. Complete the
following table which sets out the generic resources including people, equipment
and materials needed to undertake the project.

Project Resources
Type Quantity Trade Notes
[list here] [list here]
Labor Mech. / Elec. / Civil
Equipment [list here] Mech. / Elec. / Civil [list here]

vi. Budget

A summary of Project budget can be provided.

9
 PROJECT EXECUTION PLAN Project Name

Risk Management
Describe the procedure to be used for managing risks in the project. The procedure should specify who is responsible
for risk management, when risk situation is regularly considered (e.g. at each project status meeting), and which roles
risks are communicated to, etc.
Also refer to the Risk Management Plan (or Risk Sheet) where the risks are listed, assessed, and mitigation and
contingency is defined.
i. Risk Assessment

The Risk Assessment will be continuously monitored and updated throughout the life of the project, with
monthly assessments included in the status report (see Communications Plan) and open to amendment by the
Project Manager.

Because mitigation approaches must be agreed upon by project leadership (based on the assessed impact of the
risk, the projects ability to accept the risk, and the feasibility of mitigating the risk), it is necessary to allocate
time into each PMO meeting, dedicated to identifying new risks and discussing mitigation strategies.

The Project Manager will convey amendments and recommended contingencies to the PMO monthly, or more
frequently, as conditions may warrant.

Project Risks
Risk Details Likelihood
[list here] [list here] [list here]

[list here] [list here] [list here]

[list here] [list here] [list here]

Project Issues
Issue Details Impact
[list here] [list here] [list here]

[list here] [list here] [list here]

[list here] [list here] [list here]

Initial Project Risk Assessment

Risk Risk Level Likelihood Mitigation Strategy

L/M/H of Event
Project Size
Person Hours H: Over 20,000 Certainty Assigned Project Manager, engaged consultant,
comprehensive project management approach and
communications plan
Estimated Project Schedule H: Over 12 months Certainty Created comprehensive project timeline with
frequent baseline reviews
Team Size at Peak H: Over 15 members Certainty Comprehensive communications plan, frequent
meetings, tight project management oversight
Number of Interfaces to H: Over 3 Certainty Develop interface control document immediately
Existing Systems Affected

10
 PROJECT EXECUTION PLAN Project Name

Risk Risk Level Likelihood Mitigation Strategy

L/M/H of Event
Project Definition
Narrow Knowledge Level of M: Knowledgeable of Likely Assigned Project Manager(s) to assess global
Users user area only implications
Available documentation M: More than 75% Likely Balance of information to be gathered by
clouds establishment of complete/current consultant
baseline
Project Scope Creep L: Scope generally Unlikely Scope intially defined in Project execution Plan,
defined, subject to reviewed monthly by three groups (Project
revision Manager and Steering Committee) to prevent
undetected scope creep
Consultant Project L: Well defined Unlikely Included in Project execution Plan, subject to
Deliverables unclear amendment
Vendor Project Deliverables M: Estimated, not clearly Somewhat Included in Project execution Plan, subject to
defined likely amendment

Cost Estimates Unrealistic L: Thoroughly predicted Unlikely Included in Project execution Plan, subject to
by industry experts using amendment as new details regarding project scope
proven practices to 15% are revealed
margin of error
Timeline Estimates M: Timeline assumes no Somewhat Timeline reviewed monthly by three groups
Unrealistic derailment likely (Project Manager and Steering Committee) to
prevent undetected timeline departures
Number of Team Members L: Team well versed in Unlikely Project Manager and consultant to identify
Unknowledgeable of business operations knowledge gaps and provide training, as necessary
Business impacted by technology
Project Leadership
Steering Committee existence L: Identified and Unlikely Frequently seek feedback to ensure continued
enthusiastic support
Absence of Commitment L: Understands value & Unlikely Frequently seek feedback to ensure continued
Level/Attitude of supports project support
Management
Absence of Commitment L: Understands value & Unlikely Frequently seek feedback to ensure continued
Level/Attitude of Users supports project support
Absence of Mid-Management L: Most understand value Unlikely Frequently seek feedback to ensure continued
Commitment & support project support
Project Staffing
Project Team Availability M: Distributed team Somewhat Continuous review of project momentum by all
makes availability likely levels. Consultant to identify any impacts caused
questionable by unavailability. If necessary, increase
committmment by participants to full time status
Physical Location of Team M: Team is dispersed Likely Use of Intranet project website, comprehensive
prevents effective among several sites Communications Plan
management
Project Teams Shared Work M: Some have worked Somewhat Comprehensive Communications Plan
Experience creates poor together before likely
working relationship
Weak User Participation on L: Users are part-time Unlikely User Group Participants coordinated by full time
Project Team team members employee
Project Management
Procurement L: Procurement Unlikely N/A
Methodology Used foreign to Methodology familiar to
team team
Change Management L: Well-defined Unlikely N/A
Procedures undefined
Quality Management L: Well-defined and Unlikely N/A
Procedures unclear accepted

11
 PROJECT EXECUTION PLAN Project Name

Sub-contract Management
List which part of work is out-sourced to which sub-contractor.
Refer to the sub-contractors agreement that should include or refer to the statement of work, the execution process,
milestones, quality assurance, configuration management, communication structure, hand-over procedure, acceptance
criteria, and quality audits.
Sub-contractor Ref. to sub-
Sub-contracted Work Remark
Company Contact contract

Communication and Reporting

State the principles for reporting and distributing information within the project for the different groups of internal and
external stakeholders. Include, for example, how often the reporting will take place, the type of reports or information, the
type of media in which it is presented, and the type of meetings that will take place.

a) Internal communication and reporting: ensure that all information is available to those who need it. Plan
project meetings, how often they take place, and who will participate Define how project information will
made available to the internal stakeholders (e.g. project library) Define how and how often sub-projects and
sub-contractors report to the project manager Define who participates milestone meetings Define how
events will be communicated

b) External communication and reporting: Define what information will be provided to which stakeholders
Define how and how often information will be provided to which stakeholders often (e.g. project report) Plan
regular meetings with external stakeholders (e.g. SteCo meetings)

Type of Method / Tool Frequency/ Information Participants /

Communication Schedule Responsibles
Internal Communication:
Project Meetings Excel sheet Weekly and on Project status, Project Mgr Project
event problems, risks, Team
changed requirements
Sharing of project data Shared Project When available All project Project Mgr(s) Project
Server documentation and Team Members
reports
Milestone Meetings Excel sheet Before Project status Project Mgr Sub-project
milestones (progess) Mgr
Final Project Meeting Excel sheet M6 Wrap-up Project Mgr Project
Experiences Team

External Communication and Reporting:

Project Report Excel sheet Monthly Project status - Project ManagerSub-
progress - forecast - Project Managers
risks
SteCo Meetings Excel sheet Monthly Project Manager, SteCo Meetings
SteCo

12
 PROJECT EXECUTION PLAN Project Name

Sign-off Sheet

I have read the above Project execution Plan and will abide by its terms and conditions and
pledge my full commitment and support for the Project execution Plan.

Project Engineer:
Date

Project Manager:
Date

PMO Head:
Date

13