PEP 202

Page 1 of 8
PROJECT EXECUTION PLAN

Rev. Date: 29 Sep 2009

TABLE OF CONTENTS
SECTION

PAGE NO.

1.0

PURPOSE AND SCOPE........................................................................................ 2

2.0

DEFINITIONS......................................................................................................... 2

3.0

REFERENCES....................................................................................................... 3

4.0

PROCEDURE......................................................................................................... 4

5.0

RECORDS.............................................................................................................. 7

6.0

FORMS AND EXHIBITS......................................................................................... 8

CONFIDENTIAL AND PROPRIETARY

Copyright 2009 Washington Group International, Inc. (Ohio) ALL RIGHTS RESERVED

PEP 202
Page 2 of 8
PROJECT EXECUTION PLAN

1.0

Rev. Date: 29 Sep 2009

PURPOSE AND SCOPE

The purpose of this procedure is to establish a consistent and uniform method for the preparation of a
Project Execution Plan. This procedure applies to projects undertaken by the Company with revenue in
excess of $2,000,000 for lump sum and not-to exceed contracts and $5,000,000 for cost reimbursable
and open-ended contracts. Smaller projects are required to produce an abbreviated plan addressing the
key issues associated with the execution of the project. A single Project Execution Plan may cover
several projects for the same Client if the projects are covered by the same contract. An abbreviated
Project Execution Plan is prepared during the proposal/bid phase and the detailed plan is prepared after
contract award. The PXP is a living document. From initial development of the PXP and at each stage
thereafter, the PXP must:

Have all major strategic issues embedded for the executing project team

Be documented and sufficient to support the next phase of the project

2.0

DEFINITIONS

2.1

Project Execution Plan

The Project Execution Plan (PXP) is a document that states the project teams plan for executing the
project in accordance with the project Scope of Work and contractual commitments. It is the working
document governing project execution to be used by project members. Although usually not a contract
document, it must be consistent with such documents. The PXP is comprised of several sections, which
are prepared and maintained throughout the life of the project. The PXP contains, or refers to the Project
Execution Procedures that define how the work will be done and the Project specific procedures that will
be used to plan, supervise and control the work on the project and should define:

What must be accomplished

Who will do the work
Where the work will be done
When contractual obligations are required

The PXP will be the document that defines the detailed execution plans for engineering, procurement,
project controls, project administration, construction, pre-commissioning, quality assurance, safety, and
start-up (as appropriate) to be followed while executing the Scope of Work. It is intended to be a tool for
use by project personnel executing the work on the Project and should be written in such a way as to
provide specific guidance for normal day-to-day work in progress.
2.2

Scope of Work Document

The Scope of Work Document includes a written description of the work, proposed or contracted, to be
performed by the Company for the Client. The document includes a written description of the project,
including a summarization of the physical aspects of the project, a definition of the project battery limits,
a listing of project scope inclusions, exclusions, assumptions, and clarifications. The document also
includes information on the site conditions, division of responsibilities between the Company and Client,
project milestones, list of deliverables, and third party interfaces associated with the work. The Scope of
Work may include drawings, specifications, design criteria, a master schedule, equipment list, instrument
index and other information required to define, as specifically as possible, the work to be accomplished
for a project. The level of detail included in the Scope of Work Document can vary substantially between
specific projects, Clients and Business Units. Once the Company and the Client approve the document,

CONFIDENTIAL AND PROPRIETARY

Copyright 2009 Washington Group International, Inc. (Ohio) ALL RIGHTS RESERVED

PEP 202
Page 3 of 8
PROJECT EXECUTION PLAN

Rev. Date: 29 Sep 2009

it may become part of the contract and form the basis for Project Execution and for changes in the work
to be handled by the Companys Change Control procedure.
2.3

Client Procedure

Any procedure, specification, or standard that is provided directly or indirectly by the Client for a specific
project and the use of which is mandatory under the terms of the contract.
2.4

Issue Authorization and Maintenance for Use

The Project Management Functional Leader is responsible for the maintenance of this procedure and will
review the procedure annually to determine any necessary updates. Should an individual employee
have a suggestion for improvement or modification to this procedure, he or she may mark-up a copy of
the PEP and send to the Project Management Functional Leader for review. The Project Management
Functional Leader will review the recommended changes and respond back to the employee on plans to
address the suggestions. Changes to the procedure will be distributed to other Corporate Department
Managers and Corporate Functional Leads for their concurrence. When the reviews are complete, the
Project Management Functional Leader will consolidate and recommend changes to this PEP to the
Senior Vice President, Project Operations who has the authority to issue revisions to this PEP.
3.0

REFERENCES

3.1

PEMP, Project Execution Management Program

3.2

PEP 200, Project Initiation

3.3

PEP 201, Scope of Work Document

3.4

PEP 203, Engineering Execution Plan

3.5

PEP 204, CAE/CAD Execution Plan

3.6

PEP 205, Procurement Pre-Project Planning

3.7

PEP 206, Lessons Learned Program

3.8

PEP 307, Internal Status Reporting

3.9

PEP 308, Client Status Reporting

3.10

PEP 311, Project Audit Assessment Program

3.11

PEP 365, Constructability

3.12

PEP 601, Project Completion Report

CONFIDENTIAL AND PROPRIETARY

Copyright 2009 Washington Group International, Inc. (Ohio) ALL RIGHTS RESERVED

PEP 202
Page 4 of 8
PROJECT EXECUTION PLAN

4.0

PROCEDURE

4.1

Process Work Flow Chart

Rev. Date: 29 Sep 2009

Figure 4.1.1

Request for Proposal

RFP Scope of Work
Document
PEP 201
Review Company Lessons
Learned PEP 206

RFP Project Execution Plan

Preliminary/Abbreviated
Submit Proposal
to Client

Authorization to Proceed/
Notice to Proceed
Received from Client
PEP 200
Company Lessons
Learned PEP 206

Letter of Instructions
Issued (if applicable)
PEP 200

Update Scope of Work

PEP 201
Project Controls

Engineering Execution Plan

PEP 203
Preparation of
Project Execution Plan
CAE/CAD Execution Plan
PEP 204
Procurement Execution Plan
PEP 205

Safety

Approval

Construction Execution
Plan
Distribution

Quality

Commissioning and
Start-up
Execution Plan

Project Team Training

CONFIDENTIAL AND PROPRIETARY

Copyright 2009 Washington Group International, Inc. (Ohio) ALL RIGHTS RESERVED

PEP 202
Page 5 of 8
PROJECT EXECUTION PLAN

4.2

Rev. Date: 29 Sep 2009

4.1.1Process Work Flow

Action by

Action

Business Unit Business

Development

1. Receives Request for Proposal from Client.

Proposal Manager/Project
Manager

2. Prepares Scope of Work Document, See PEP 201.

3. Reviews Company Lesson Learned Database.
4. Prepares Preliminary/Abbreviated Project Execution Plan (PXP)
with input from proposal team members.

Business Unit Business

Development

5. Submits Proposal to the Client.

Business Unit
Management/Company
Management

6. After Receipt of Authorization to Proceed/Notice to Proceed may

issue the Project Manager Letter of Instruction (LOI), See PEP
200.

Project Manager

7. Prepares and issues the PXP preparation (or updating) schedule

and responsibility assignments.

Project Manager/Project Team

Members

8. Initiates review of Company Lessons Learned Database and

development of PXP.

Project Manager

9. Gathers all the information from Project Team Members for

compiling into the PXP.
10. Reviews and approves the PXP to ensure compliance with the
Company Project Execution Procedures.
11. Obtain approval from local Business Unit Management/Company
Management, Quality Assurance Manager (for nuclear projects),
and client if required by contract.
12. Issues the PXP.

4.3

Instructions

4.4PXP Preparation
Immediately after receipt of the Request for Proposal (RFP) and Approval to Bid, the Proposal
Manager/Project Manager initiates the development of the RFP Scope of Work document, reviews the
Company Lessons Learned Database, and prepares a Preliminary/Abbreviated Project Execution Plan
for review by Company Management prior to submittal of the Proposal to the Client.
Upon receipt of the Authorization to Proceed/Notice to Proceed, the Project Manager issues a schedule
for preparation or updating of the Project Execution Plan (PXP) and assigns key project team members

CONFIDENTIAL AND PROPRIETARY

Copyright 2009 Washington Group International, Inc. (Ohio) ALL RIGHTS RESERVED

PEP 202
Page 6 of 8
PROJECT EXECUTION PLAN

Rev. Date: 29 Sep 2009

the responsibility for development of specific sections of the Plan. The PXP must be completed as soon
as possible after project initiation, but no later than six (6) weeks after the contract award.
The PXP shall be reviewed and approved by the Project Manager. The Project Manager shall review the
PXP with, and obtain approval from, the Business Unit Manager, Quality Assurance Manager (for nuclear
projects), and/or local Company Management prior to use. It is the responsibility of the writers of specific
sections to discuss the contents of those sections with their Functional Leads, if necessary, and to get
concurrence with the contents before presenting them to the Project Manager.
The PXP should be developed from the following information sources:
A.
B.
C.
D.
E.
F.
G.
H.
I.
J.

Proposal/Inquiry Documents
Project Scope of Work
Preliminary/Abbreviated Project Execution Plan prepared during the RFP Process
Project Kick-off and Planning Meetings
Contract Briefing Document
As required, Letter of Instruction
Risk Management Plan
Proposal Estimate
Project Schedule
Lessons Learned

The PXP is a living document and should be revised and reissued as necessary to reflect changes
regarding scope and execution requirements, or to complete sections not defined in the initial issue.
4.5

PXP Table of Contents

A standard Table of Contents is provided in 202-01 (MM). To provide consistency from project to project,
the numbering and headings in the Table of Contents should remain the same, even if some sections are
not used. Sections not used for a particular project should be so noted.
4.6

Annotated PXP

An annotated PXP is provided in 202-02 (S) and provides a comprehensive contents checklist of topics
that may be included in the PXP at the discretion of the Project Manager.
4.7

Use of Company Procedures

Each project should be executed in accordance with the Company Project Execution Procedures. The
PXP shall include documentation of any deviations or supplements when necessary. Project Execution
Procedure deviations shall be developed in accordance with the requirements of the Project Execution
Management Program (PEMP), Appendix D.
4.8

Use of Client Procedures

When contractual requirements stipulate that Client-supplied standards or procedures be used in place of
Company Project Execution Procedures, the standards or procedures should be placed in the
appropriate section(s) of the PXP and noted as client-supplied as a means of differentiating them from
Company procedures.

CONFIDENTIAL AND PROPRIETARY

Copyright 2009 Washington Group International, Inc. (Ohio) ALL RIGHTS RESERVED

PEP 202
Page 7 of 8
PROJECT EXECUTION PLAN
4.9

Rev. Date: 29 Sep 2009

Project Specific Procedures

When the Project Manager determines that special circumstances require the development of a new
procedure(s) to handle specific requirements for the execution of a Project, the new procedure(s) shall be
developed in accordance with the format and other requirements of the PEMP, Appendix B and included
in the PXP.
4.10

Revisions to the PXP

Revisions and updated to the PXP should be made as changes or developments require modifications in
the way in which the project is executed. All revisions shall be controlled and distributed in the same
manner as the original issue.
4.11

Distribution of PXP

The PXP is a Controlled document and should be issued in accordance with Company procedures.
Copies of the PXP should be issued to the Project Manager, all appropriate staff personnel including all
Project Manager Direct Reports, Supervising Discipline Engineers, and Project File. The issue of this
document should be accompanied by project specific training to familiarize the users with the contents
and requirements of the document.
4.12

Responsibilities

A. Company Management is responsible for the review and approval of the Project Execution Plan.
B. The Project Manager is responsible for the preparation and maintenance of the PXP in
accordance with this procedure.
C. The Project Manager is responsible for training the Project Team on the execution requirements
included in the PXP.
D. The Project Engineering Manager is responsible for the review, determination, and development
of Client and/or Company technical criteria and requirements for project execution in a timely
manner, and providing the required information for incorporation into the PXP.
E. Each Functional Group Representative, assigned to the project by a Functional Manager, is
responsible for providing input to the PXP and for reviewing his/her respective section to ensure
it provides sufficient information for them to execute their work as directed by the Project
Manager.
F. Each Functional Group Representative is responsible for reviewing the other PXP sections to
ensure it provides sufficient information for them to execute their work.
G. Each Project Team Member is individually responsible for executing the work in accordance with
the PXP under the Project Managers/Project Engineering Managers and/or his/her project
supervisors direction.
5.0

RECORDS

A copy of the Project Execution Plan and subsequent revisions are retained in the project files for the
duration of the project. After project completion it is processed in accordance with the procedure for
Record Filing, Retention, Retrieval and Destruction of Documents (see PEP 316).
CONFIDENTIAL AND PROPRIETARY
Copyright 2009 Washington Group International, Inc. (Ohio) ALL RIGHTS RESERVED

PEP 202
Page 8 of 8
PROJECT EXECUTION PLAN
6.0

FORMS AND EXHIBITS

6.1

202-01 (MM), Table of Contents for Project Execution Plans

6.2

202-02 (S), Annotated PXP

Rev. Date: 29 Sep 2009

CONFIDENTIAL AND PROPRIETARY

Copyright 2009 Washington Group International, Inc. (Ohio) ALL RIGHTS RESERVED