Change Control Procedure

Code du document : DOP3000PRC-013-0-03

B&R-C

Date : 10 November 2003

Indice de rvision : 0
Page 1 of 5

Mots cls: Change Control, Project Variation, Contract Change Order

Change Control
Procedure
Evolution du document :
Date
10.11.03

Indice
0

Objet de la modification
Cration

Rdige par: N.Benhalla

Vrifie par: M.Robaine
Approuve par: T.Mokrane

NB/ La procdure signe est disponible au niveau de la Direction Qualit.

Le prsent document est la proprit exclusive de B&R-C.

Change Control Procedure

B&R-C

1.

Code du document : DOP3000PRC-013-0-03

Date : 10 November 2003

Indice de rvision : 0
Page 2 of 5

PURPOSE

This procedure defines the activities and responsibilities associated with the identification and
management of Project Variations and Contract Change Orders.
Project Variations Are internal change notices which must be raised for all changes which can
be: client initiated, sub-contractor initiated, third party (CTC) initiated, BRC initiated design
developed, design errors or omissions.
Contract Changes Are Project Variations which are agreed by the Client and are changes to the
contract scope of work

2.

APPLICABILTY

This procedure map applies to all B&R-C projects regardless of contract type. It identifies the
personnel who are responsible for the development and implementation of Project Change
Control. All Project Variations must be identified and recorded irrespective of originator or
liability.

3.

Attached Documents

1- PVN (Project Variation Notice)

2- CCO (Contract Change Order)

PM-FRM-PVN1
PM-FRM-CCO1

Le prsent document est la proprit exclusive de B&R-C.

Change Control Procedure

Indice de rvision : 0
Page 3 of 5

Code du document : DOP3000PRC-013-0-03

B&R-C

Date : 10 November 2003

Legend
Responsible and
Accountable for Activity
ST

HSE HSE Alert

X X
RISK

Meeting (plus attendees)

Business Risk

Process Measure

Local/Project Variation

END End

Activity Steps
1.0

B&R-C INSTIGATED CHANGE

1.1
1.1

Identify a potential variation to project

scope, cost, schedule, specification or
work plan. Collect supporting data and
complete a Project Variation Notice
form (PVN).

1.2
1.3
1.3
1.4
1.5

Appropriate lead discipline manager

accepts the PVN
Prepare assessment of cost and
schedule impact
Review PVN for incorporation into
scope
Prepare detailed cost estimate and
schedule impact

1.6

Is PVN part of original scope of work?

1.7
1.7

Submit to Client as potential Change

Order

1.8

Does Client approve change and issue

a Change Order ?

1.9

Perform work in accordance with

agreed change

Client

Additional Note

Decision

Suppliers

Involved in Activity

Contractors

Start

Construction

Accountable for Activity

Procurement & Materials

Project Management
Project Controls
(Cost/Planning/Est)
Engineering

Responsible
for Activity

ST

PROJECT VARIATION NOTICE

(PVN)
PMFRM-PVN1

Yes
No

CONTRACT CHANGE ORDER

(CCO)
PMFRM-CCO1

Go to 1.9
Yes
No
A

END

1.10 Update project controls system

2.0

CLIENT INSTIGATED CHANGE

2.1

Issue formal Change Order

2.2

Prepare preliminary cost estimate and

schedule impact and submit to Client

2.3

Agree estimate and confirm acceptance

2.4

ST
END

CONTRACT CHANGE ORDER

(CCO)
PMFRM-CCO1

Yes

Accept instruction and communicate

change required

2.5

Perform the work as instructed

2.6
2.6

Prepare detailed cost and schedule

impact if necessary

2.7

Submit detailed impact to Client and

negotiate if necessary

2.8

Update controls system

No
END

END

Le prsent document est la proprit exclusive de B&R-C.

Change Control Procedure

Indice de rvision : 0
Page 4 of 5

Code du document : DOP3000PRC-013-0-03

B&R-C

Date : 10 November 2003

Legend

Involved in Activity
Additional Note

Decision

HSE HSE Alert

X X
RISK

Meeting (plus attendees)

Business Risk

Process Measure

Local/Project Variation

END End

Activity Steps
3.0
3.1
3.1

MAINTAIN WBS/CBS

Client

Start

Suppliers

ST

Contractors

Accountable for Activity

Construction

Procurement & Materials

Responsible and
Accountable for Activity

Project Management
Project Controls
(Cost/Planning/Est)
Engineering

Responsible
for Activity

ST
DEVELOP WORK
BREAKDOWN STRUCTURE
DOP3000-PRC-005-0-03

Determine the need for new WBS/CBS

codes based on new scope or control
requirements

3,2

Determine the impact of changes on

WBS/CBS codes and structures

3.3
3.3

Approve changes if they affect the

WBS/CBS (Client if appropriate)

3.4

Update project management computer

system

3.5

Issue revised WBS to project team

END
ST

4.0

REVISING THE PROJECT BASELINE

4.1
4.1

Identify potential variations to the project

baseline e.g..
- Contractual Change Orders
- Potential Change Orders
- Major schedule modification
- FY end reporting requirements
- Recovery plan
- Added scope

4.2

Quantify the revised baseline project

4.3

Review the revised project baseline. If

external Client instigated then raise
change order (see 2.0)

4.4

Approve the revised project baseline (as

appropriate) - inform Client

2.0

END

Le prsent document est la proprit exclusive de B&R-C.

Change Control Procedure

B&R-C

Code du document : DOP3000PRC-013-0-03

Date : 10 November 2003

Indice de rvision : 0
Page 5 of 5

NOTES
Note 1.1

Any individual on the project team can identify a potential variation using this
process. Part of the process is to encourage improvements to design and
construction of the project in addition to ensuring that B&R-C's contractual
position is safeguarded.

Note 1.3

This is a high level, quick order of magnitude estimate of total project cost and
schedule impact

Note 1.7

Project controls log the PVN and CCO, if applicable, and issue numbers

Note 2.6

A detailed cost estimate may be required either at Client's or KBR Project

Manager's request. The estimates shall be based on the contractual schedule of
rates, where these exist.

Note 3.1

Any member of the Project Team can identify and propose a new coding
requirement.
Responsibilities for this activity apply to the formal acknowledgment of the need
for new WBS codes. Project scope changes as identified in the change control
process are a primary source for new WBS requirements.

Note 3.3

For Back-charges, rework, and variances, the Project Cost Specialist has the
authority to establish new tracking numbers according to project coding
standards. The Project Controls Manager and/or Technical Service Manager
must approve new WBS codes for items which affect progress calculations or the
collection of information for the historical database.

Note 4.1

Ground rules and timing for resetting each element of the project baseline must
be determined at the beginning of the project. Contractual limitations affecting
change orders and schedule revisions must be reviewed

Le prsent document est la proprit exclusive de B&R-C.