Professional Documents
Culture Documents
B&R-C
Indice de rvision : 0
Page 1 of 5
Change Control
Procedure
Evolution du document :
Date
10.11.03
Indice
0
Objet de la modification
Cration
1.
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
PM-FRM-PVN1
PM-FRM-CCO1
B&R-C
X X
RISK
Business Risk
Process Measure
Local/Project Variation
END End
Activity Steps
1.0
1.1
1.1
1.2
1.3
1.3
1.4
1.5
1.6
1.7
1.7
1.8
1.9
Client
Additional Note
Decision
Suppliers
Involved in Activity
Contractors
Start
Construction
Project Management
Project Controls
(Cost/Planning/Est)
Engineering
Responsible
for Activity
ST
Yes
No
Go to 1.9
Yes
No
A
END
2.1
2.2
2.3
2.4
ST
END
Yes
2.5
2.6
2.6
2.7
2.8
No
END
END
B&R-C
Involved in Activity
Additional Note
Decision
X X
RISK
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
Construction
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
3,2
3.3
3.3
3.4
3.5
4.0
4.1
4.1
4.2
4.3
4.4
2.0
END
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
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