Академический Документы
Профессиональный Документы
Культура Документы
Document ID CP-206
Security Unrestricted
Revision 1.0
This document is the property of Petroleum Development Oman, LLC. Neither the whole nor any part of
this document may be disclosed to others or reproduced, stored in a retrieval system, or transmitted in any
form by any means (electronic, mechanical, reprographic recording or otherwise) without prior written
consent of the owner.
Revision: 1.0
Petroleum Development Oman LLC Effective Nov-11
i Document Authorisation
Authorised For Issue – November 2011
ii Revision History
The following is a brief summary of the 4 most recent revisions to this document. Details of
all revisions prior to these are held on file by the issuing department.
Revision Date Author Scope / Remarks
No.
Refer to Appendix 2
Table of Contents
1 Introduction ............................................................................................................................. 7
1.1 Purpose ............................................................................................................................ 7
1.2 Objectives ......................................................................................................................... 7
1.3 Applicability ...................................................................................................................... 7
1.4 Document Implementation and Deviation ........................................................................ 7
1.5 Review and Improvement ................................................................................................ 8
2 Scope and Definitions ............................................................................................................. 9
2.1 Scope ............................................................................................................................... 9
2.2 Terms and Definitions for Change ................................................................................... 9
2.3 PDO Management of Change Procedures .................................................................... 11
2.3.1 Projects Phase ......................................................................................................... 11
2.3.2 Operations Phase .................................................................................................... 11
2.3.3 Abandonment Phase ............................................................................................... 12
2.3.4 Organisational Changes .......................................................................................... 12
3 Management of Change Process (MOC) ............................................................................. 13
3.1 Screen ............................................................................................................................ 13
3.2 Review............................................................................................................................ 13
3.3 Approve .......................................................................................................................... 14
3.4 Implement....................................................................................................................... 14
3.5 Close-Out ....................................................................................................................... 14
4 MOC Procedures .................................................................................................................. 15
4.1 Change Recognition ....................................................................................................... 15
4.1.1 Like-for-Like ............................................................................................................. 15
4.1.2 New for Old .............................................................................................................. 15
4.1.3 Upgrades ................................................................................................................. 15
4.1.4 Change to Design .................................................................................................... 15
4.1.5 Changes to Process Conditions .............................................................................. 15
4.1.6 Change to Material Specification ............................................................................. 15
4.1.7 Changes to Size ...................................................................................................... 15
4.1.8 Control Systems ...................................................................................................... 15
4.1.9 Instrumentation ........................................................................................................ 16
4.1.10 Changing Documents .............................................................................................. 16
4.2 Emergency Change ....................................................................................................... 16
5 Accountabilities and Responsibilities .................................................................................... 17
6 Audit and Review of MOC Process ...................................................................................... 19
6.1 HSE MS Audit ................................................................................................................ 19
6.2 Operational Excellence Internal and External Reviews ................................................. 19
1 Introduction
Analysis of world-wide oil incidents over a three year period indicated that 50% of
incidents were attributable to failures in Management of Change (MOC). 50% of those
MOC failures, i.e. 25% of total, were due to weaknesses in organisational change
related to HSE critical activities. The documented direct and underlying cause of many
incidents, accidents and injuries in oil and gas industries is failure to properly recognise
and/or manage change. This has been a frequent finding of incident investigations. The
impact on safety and Asset Integrity from MOC related incidents is clear.
The indirect impact on production and ultimately economic field life is also significant.
Poor MOC played a large role in major world-wide incidents such as Flixborough
Chemical Plant in the UK in 1974 and Chernobyl in USSR in 1986. Apart from impact
on human life, incidents like this halted production, in some cases permanently, and
cost the business dearly. The change in specification for an O-Ring on the Space
Shuttle Challenger had huge repercussions on the USA Space Shuttle programme.
These worldwide well known incidents are infrequent but most companies, if
questioned, could cite local MOC incidents within the last 2 years that have adversely
impacted their business objectives.
It will be the responsibility of each Directorate and / or Asset to appoint an MOC
Focal Point who will be responsible for implementation of the MOC for that
directorate and / or Asset in accordance with this Code of Practice.
1.1 Purpose
The purpose of this Code of Practice (CoP) is to define PDO’s minimum requirements
for effectively managing all permanent or temporary changes to organisation, critical
staff positions, equipment, plant, materials, standards or procedures and changes
associated with laws and regulations of Oman associated with the activities of PDO and
its Contractors.
1.2 Objectives
The objectives of the Management of Change (MOC) Process will be to ensure
changes to organisational, safety and business which affect the overall operations of
PDO are managed, recorded and implemented correctly, and that no changes are
implemented which have not been assessed and approved.
1.3 Applicability
This Code of Practice will be applicable to all Business Elements within PDO and its
approved Contractors.
It can be seen from the Table above that there are many types of change that can and
do occur over the lifecycle of an Operational Asset. All types of change that occur in
PDO are managed by mandatory procedures that require to be complied with.
1. SCREEN 2. REVIEW
Proposed Define Proposed Evaluate Proposed
Change Change Change
3. APPROVE 4. IMPLEMENT
Authorise Change Build the Change,
Or Document,
Communicate and
REJECT Train.
5. CLOSE-OUT Start Up
Close out and archive
records.
Change
3.1 Screen
The ‘Screen’ process will ensure the proposed change:
- justified and necessary;
- meets the criteria for being considered under the MOC process, and;
- has sufficient detail to enable the reviewers to fully understand the purpose,
scope and context of the change.
IMPORTANT: MOC shall not be used as a tool to test out ideas and theories within the
area and asset.
3.2 Review
The ‘Review’ process will ensure the proposed change:
- is evaluated;
- is risk assessed;
- issues involving the proposed change are identified and documented;
- correct approval level is identified.
3.4 Implement
The ‘Implement’ process will ensure the proposed change:
- is documented;
- is registered;
- is planned;
- is communicated;
- has required training identified;
- has been reviewed for readiness before start-up.
3.5 Close-Out
The ‘Close’ process will ensure the proposed change:
- has all documentation completed;
- has suitably trained personnel;
- has been communicated effectively within the organisation.
4 MOC Procedures
4.1 Change Recognition
The need for a change can be identified by anyone in the organisation.
The proposed change must be reviewed according to the correct procedure and a
decision to be made on whether MOC is required or not.
IMPORTANT NOTE: It is mandatory that HSE critical positions know how to
recognise requirement and know how to initiate the MOC process.
4.1.1 Like-for-Like
A change that results in a component, item, length of pipework etc, being replaced by
another that is the same is termed a ‘like-for-like’ change and does not require an MOC
to be raised.
4.1.3 Upgrades
In line with 4.1.1 and 4.1.2 above ‘upgrades’ that meet this criterion will not require an
MOC. However if the implementation of the upgrade requires changes to configurations
either structural or mode of operation will require an MOC to be raised.
4.1.9 Instrumentation
In line with 4.1.1 and 4.1.2 above ‘instrument’ that meet this criteria will not require an
MOC. All other changes will require an MOC to be raised.
Basic
implementation
Asset Manager
Emergency Change in place
Authorisation
The relevant MOC procedure will still be followed, however, it must be a timely and
pragmatic approach that has a fit for purpose risk assessment, which is carried out by
available on-call personnel, but not necessarily documented before the change is
realised.
The process for an emergency MOC needs to be accelerated by engaging the right
people, documenting conversations and decisions before the change is implemented.
The official documentation of the MOC can be completed ASAP. The organisation has
the accountability to handle any emergency by first securing the situation and making
things safe. It should, however, not make changes to the process as a result of the
emergency, whether the change is temporary or permanent, without going through the
MOC process. It is important to get production back on line but it has to be done
under controlled conditions.
HSSE MS Audit
MOC KPIs
Operations Manager, who will be the accountable body for MOC within the Asset. This
Assurance Plan will include:
review of the integrity of the MOC process;
confirmation of change management procedure compliance to the MOC
process steps, where required;
sample checking of compliance with procedural steps, including:
o audit trail from initiation to close out and archive;
o references to documented risk analysis outcomes;
o references to risk mitigation actions and associated verification;
o close out of Secondary Changes required as result of primary change,
e.g. update of CMMS master data, updated competence requirements
as result of a hardware change;
o confirmation that where requested a Post Implementation Review (PIR)
has been carried out and the learning disseminated;
creation and subsequent monitoring of generic MOC KPIs for use by all Assets,
which can be rolled up from facility to Asset level;
Creation and subsequent monitoring of generic MOC process indicators, which
can be rolled up from facility to Asset level.
Specifications
Procedures
Guidelines
Appendix 3 – Abbreviations
AI-PS Asset Integrity – Process Safety
ASAP As Soon As Possible
CoP Code of Practice
Cv or CV Flow coefficient or flow capacity rating of valve
DCAF Discipline Controls and Assurance Framework
FSR Field Status Report
HSE Health Safety and Environment