Military reference books and manuals (2009-2023, Volume 1)

Note: Although financial information can be included in the MoC this procedure does not cover any financial controls and normal

budgetary processes and controls will apply.

CVP Stages

appraise

select

define

execute

operate

MoC Process

EQ or other

Process

Initiate

Verify

Review

Approve

Authorise

Out

Annual MoC review for each division across the SPU

MoC compliance will be checked across all of the MoC process and system Performance

indicators will be made available for all by the MoC team

review report will be issued to division vice president and any agreed

corrective actions will be entered in Traction ( the action tracking data

base)

4.1

Management of Change Stages

All change goes through six main stages and is coordinated through the process after verify

Initiate - the creation of the MoC this is the responsibility of the initiator who will:

a. Create the eMOC choosing the affected Site and Facility and choose the correct template for the MoC

type process to be followed (the use of a template is a mandatory requirement).

b. Identify the scope of work (identifies the change and describes all work necessary to produce the

change). The scope establishes the tone for the remainder of the planning efforts and therefore

should be sufficiently detailed. (Keep in mind however that being too detailed can be as bothersome

as not providing enough detail).

Note: for DC&I deviations the DWOP reference number shall be included

c. Provide a justification for the work (this section details why the change is required)

d. Provide details of other options considered.

e. Reference any other business process, Engineering Query, Engineering Technical Practice, Drilling

SEQ or DWOP incident report etc, where this is required. (using the TQ/ EQ box in the eMoC

application box)

Identify the Key Change Verifier as per the specific guidance for the MoC type.

Identify other reviewers and approvers, authorizers as defined as a minimum requirement under

each MoC type

h. Suggest a priority as per the definition in this procedure

Attach all relevant documentation as applicable to MoC for information at REV A (more advance

revisions may be issued if available)

Verify - that the change can proceed. This is the responsibility of Key Verifier (as defined in each MoC type) to

ensure that:

a. The change is described clearly and adequately to avoid any possible confusion

b. The justification for the change is clear and adequate

c. That all options have been considered and documented in the MoC (as appropriate)

d. That the budget is approved and a cost center is identified (as appropriate)

e. Any post start up reviews that may be required to assess the success of the change (as appropriate)

have been identified.

All persons who are required to execute various stages of the MoC have been identified

The priority level as per the IFP matrix

The person who is responsible for the detailed design has been identified and ensure that a full

design work pack has been assembled and attached, with all documents marked up REV A, dated

and signed (more advance revisions may be used if available)

The full scope of work is agreed and appropriate documentation has been identified.

AzSPU-GEN-PRC-001-A2

Page 9 of 102

Any hazards and risks associated with, the change as per the OMS requirements and confirm or

change the risk level (this includes deviations from company or industry standards or practices and

any compliance issues.

k. If the change is to be rejected then the key verifier will cancel the MoC giving a reason

3. Review - confirm that the detail is complete, correct and suitable, it is the responsibility of the reviewers to:

a. Review the change for major hazard, safety or operability issues, and check that key design

documents have been provided appropriate for the risk level and MoC type.

4. Approve - the change for implementation on the site, the approver will

a. Ensure the appropriate process has been followed and will approve the work for implementation

b. Approve the budget for any procurement actives, if procurement starts before the MoC is approved

then this is done as a deviation from this procedure and is at the budget holders risk.

5. Authorize - the change for startup/ use on site, the authorizer will

a. Ensure that all pre implementation actions have been completed to their satisfaction and that it is

safe for use/ startup.

6. Close out - close out the change, the closer will

a. Ensure that all post implementation actions have been closed to their satisfaction

Coordination of the MoC will be the responsibility of the coordinator whose responsibility is to work with all those

who are involved in the MoC to ensure that the MoC follows the process correctly, that all the correct information is

available, clearly identified, filed and that pre and post implementation actions are correctly identified and

completed. The coordinator can be changed at the approve stage if the key approver believes that responsibilities

are best executed by another member of the team

The level of assurance will be appropriate to the level of risk associated with the MoC implementation.

Note: For detail see specific guidance given for each change type.

4.2

MoC Compliance Check

A Bi weekly compliance check will be used to confirm that the MoC procedure is being correctly followed, focusing

on:

 Level of risk associated with the change.

 Appropriate verification, review, approval, authorization and close out of the change.

 Overview of all MoC Key Indicators.

Note: This is the responsibility of the MoC team to gather and present this information

Document number

Document Title

Applies to

Notes

MOC-FRM-023

MOC AUDIT TEMPLATE

AZSPU

Used to consistently audit MoC implementation

The MoC system team leader in consultation with the Functional Vice President and the Engineering Authority will

organize an annual audit of MoCs passed the approved stage

Note: MoCs at the earlier stages of the MoC process are going through the normal verify and review processes for quality and

accuracy and should not be audited while still under the early stages of development

The compliance check team as a minimum will consist of

 TL - MoC system team leader.

 Persons who can independently audit the MoC

 Person with Line responsibility for the Operating area

 Site persons affected by the MoC if required

 Others if required, as identified by the TL

The Functional Vice President is accountable for ensuring that an appropriate annual compliance check is done for

their areas of responsibility.

AzSPU-GEN-PRC-001-A2

Page 10 of 102

The Engineering Authority is accountable for ensuring that the annually technical audit is completed for MoC (SRP

5.0.0001)

Note: It is recommended that compliance checks are scheduled using the computerized maintenance management system or

some other operating area scheduling tool.

5 Managing Risk

A key component for managing change is to understand the hazards and the associated risks. As the risk increases

the verification process required increases. Specific guidance on risk can be found in the sections for each of the

MoC types.

This procedure identifies the minimum MoC review and approval requirements for the different levels of risk as

defined under each MoC type. In reality the risk will have many different levels. To ensure that risk is appropriately

managed on BP operating areas requires appropriate review and approval by BP competent persons and

management personnel of the site(s) that are affected by the change.

It is the job of the MoC key verifier to ensure that the hazard and risk has been properly evaluated as per OMS

section 3 with the correct personnel around a table and that appropriate reviewers and

approvers have been

identified considering work scopes, competencies and responsibilities.

Hazards and Risk should be considered for Personnel Safety Process Safety

HAZARD & RISK

TOOLS

OMS REF

AREAS

Personal safety

Task Risk Assessment

Process safety

ISD (Inherently Safer Design)

GRP3.1 001

HAZID (Hazard Identification)

WHAT IF

HAZOP (hazard and operability)

LOPA (layer of protection Analysis) MAR (major accident and risk)

PSSR (Pre Start up Safety Review) QRA (Quantified Risk Assessment)

SIL (Safety Integrity Level)

Health and industrial

COSHH Control of substances hazardous to health

GRP 3.4-001

hygiene

OGP/ IPIECA Guide to health impact assessments

GRP 3.4-001

AIHA Exposure assessment process

GRP 3.4-001

HS&E Methods for determination of Hazardous substances

GRP 3.4-001

Fitness for task and health surveillance

industrial hygiene

Asbestos

Fatigue

Security

SIS security of information standard

GRP 3.5-001

DSS Digital Systems and Security

Environment

Emission to air

GRP 3.6-0001

Dischargers to Water and Land

Handling disposal of waste

Transport

MAR major accident risk process

GRP 3.7-0001

Marine operations

GRP 3.7-0002

Travel policy

GRP 5.6-0001

Aviation

Driving safety

Note: See MoC personnel register.

Document

Document Title

Notes

number

Assessment , prioritization

This will be used along with the guidance in each of the MoC

GDP 3.1-0001

and management of risk

type to drive the level of verification required

AzSPU-GEN-PRC-001-A2

Page 11 of 102

Document

Document Title

Notes

number

AzSPU Guidance on Technical

Hazard and Risk Processes to

MoC Appendix 1

Used to assess the MoC risk level

be used within MoC Appendix

Segment Recommended

Definitions For Modifications Which Alter The Operation Of

SRP 5.0-0001

Practice for Engineering

Existing Equipment

Management

5.1

Risk Levels

Risk ranking is a GDP 3.1-0001 matrix guided representation of the single most significant risk identified during a

risk assessment of the hazards introduced by the change. This includes design risks and extraordinary

implementation risks.

5.1.1 Insignificant Risk

Do not require an MoC

See the specific MoC decision tree for guidance

5.1.2 Risk level 1- White

Change identified as low risk has little or no impact on process safety or operations (Level 1 White as defined in

the OMS risk matrix (GDP 3.1 001 Annex 3 risk matrix)), no deviation from company engineering standards (ETP or

STP), minor organizational impact and minimal business risk.

See the specific MoC type for minimum sign off requirements

5.1.3 Risk Level 2- Turquoise

Change identified as risk level 2 (turquoise) has minimum impact on process safety or operations (Level 2

Turquoise as defined in the OMS risk matrix (GDP 3.1 001 Annex 3 risk matrix)), may have a degree of technical

complexity and minimal business risk.

See the specific MoC type sign minimum sign off requirements

5.1.4 Risk Level 3 - Blue

Change identified as risk level 3 (blue) has the potential for significant impact on process safety or operations

(Level 3 Blue as defined in the OMS risk matrix (GDP 3.1 001 Annex 3 risk matrix)))), significant organizational impact

or significant business risk.

See the specific MoC type for minimum sign off requirements

5.1.5 Risk Level 4- Purple

Change identified as risk level 4 (purple) has the potential for catastrophic impact on process safety or operations

(Level 4 Purple and above as defined in the OMS risk matrix (GDP 3.1 001 Annex 3 risk matrix))

See the specific MoC type for minimum sign off requirements

6 Priority

Document

Document Title

Notes

number

This tool is the same as the one used for EQ and is used to

MOC-FRM-008

MoC prioritization tool

ensure that all MoCs are consistently categorized and prioritized

Priority ranking is a GDP 3.1-0001 matrix guided representation of the importance of the change. The ranking is

selected from the matrix based on the information provided in the Justification section of the eMOC.

AzSPU-GEN-PRC-001-A2

Page 12 of 102

To assist work prioritization it is mandated that the MoC is given a priority. Prioritization is to be determined using

the IFP prioritization tool which aligns with MAXIMO and EQ.

7 Competency and Training

Competency for MoC has two areas; knowledge of how to use the e-MoC tool, and role knowledge to be able to

execute the intent of MoC

 E-MoC Tool.

The tool is a software based system and is relatively intuitive. Online training and assessment will be

required for all new users and recommended for existing users

Additional training will be available on request.

 MoC Role Knowledge.

Critical to this process is the Key Verifier who confirms the MoC roles to individuals. They are making the

judgment if the individual has the competency, experience and authority to execute the role as per the

responsibilities identified within the roles and responsibilities list of each MoC type

To assist with this, each area is to have a register of persons that have been assessed as competent to

complete the management of change process as a verifier / reviewer/ approver/ authorizer for each MoC

type and location

Training and assessment is a normal part of role development. It is the responsibility of line management to

assure the competency of their personnel

 Persons required to confirm that GOC elements are adequately completed are to have GOC training and

assessment (see MoC type for guidance for which MoC types require GOC)

Note: it is a requirement that those who coordinate technical MoC will have completed GOC training and assessment

Applicable to

This document is applicable to the following job functions:

Note: Due to the range of different job titles within the Operating areas at the time of writing, the Job functions have had to be

rationalized to align the procedure with the e-MoC tool.

MoC Group

Typical Job Function

(DC&I) AFFM

D&C ADVANCE FLUIDS FACILITY MANAGER

KCAD Discipline Responsible Engineers (ELECTRICAL/ INST/ CONTROL/ SIS/ MECHANICAL ETC)

(DC&I) DRE (DISCIPLINE) (KCAD)

(as found in the TA/ DRE register)

(DC&I) DRE (INSTRUMENT/

KCAD Discipline Responsible Engineers (instrumentation / control and safety instrumented system)

CONTROL/ SIS) (KCAD)

(as found in the TA/ DRE register)

(DC&I) EIA

D&C EQUIPMENT INTEGRITY ASSURANCE

(DC&I) EM (DISCIPLINE)

D&C ENGINEERING MANAGER(DRILLING / COMPLETIONS/ INTERVENTIONS ETC)

(DC&I) ENG (DISCIPLINE)

D&C ENGINEER (DRILLING / COMPLETIONS/ INTERVENTIONS ETC)

(DC&I) ENG CHALLENGER

D&C CHALLENGER ENGINEER

(DC&I) ENG Snr (DISCIPLINE)

D&C Senior ENGINEER (DRILLING / COMPLETIONS/ INTERVENTIONS ETC)

(DC&I) ENGINEER (KCAD)

KCAD ENGINEER

(DC&I) ENGINEER (SYSTEMS)

KCAD SYSTEMS ENGINEER (DRILL VIEW ETC)

(KCAD)

(DC&I) ETL (DISCIPLINE)

D&C ENGINEERING TEAM LEADER (DRILLING / COMPLETIONS/ INTERVENTIONS ETC)

(DC&I) HSE TL

HSE TEAM LEADER D&C

(DC&I) MAINT SUPERINTENDANT

KCAD MAINTENACE SUPERINTENDANT

(KCAD)

(DC&I) MAINT

KCAD MAINTENANCE SUPERVISOR

SUPERVISOR(KCAD)

(DC&I) RIG

KCAD RIG SUPERINTENDANT

SUPERINTENDANT(KCAD)

(DC&I) RMS

D&C RIG MAINTENANCE SPECIALIST

(DC&I) RMTL

D&C RIG MAINTENANCE TEAM LEADER

D&C TECHNICAL AUTHORITY ARE EMPLOYED IN VARIOUS ACTIVITIES WHERE APPROVE & TA

(DC&I) TA

WILL BE ADDED BEHIND THE MAIN JOB TITLE

(DC&I) TA INSTRUMENT/

KCAD TECHNICAL AUTHROITY FOR INSTRUMENT CONTROL SAFETY INSTRUMENTED SYSTEMS

CONTROL /SIS (KCAD)

(as found in the TA/ DRE register)

(DC&I) TL ENG (KCAD)

KCAD ENGINEERING TEAM LEADER

(DC&I) TL MAINT (KCAD)

KCAD MAINTENANCE TEAM LEADER

(DC&I) VP & WEA

D&C VICE PRESIDENT & WELL ENGINEERING AUTHORITY

(DC&I) WITL

D&C WELL INTEGRITY TEAM LEADER

(DC&I) WOM

D&C WELL OPERATIONS MANAGER

(DC&I) WSL

D&C WELL SITE LEADER

AzSPU-GEN-PRC-001-A2

Page 13 of 102

MoC Group

Typical Job Function

(DC&I) WSL SNR

D&C SENIOR WELL SITE LEADER

(DC&I) WTL

D&C WELLS TEAM LEADER

ACET Administrator

ACET DATA CONTROL

ACET Systems Lead

(OPERATIONS) AREA INSPECTION AUTHORITY

AIA

(MIDSTREAM SANGACHAL) AREA INSPECTION AUTHORITY

(MIDSTREAM Export systems (Az/ Geo/Turk)); SENIOR ASSET INSPECTION ENGINEER

Area Operations Manager Shah Deniz

Area Operations Manager Azeri

Area Operations Manager DWG/Chirag

AOM

Sangachal Terminal AOM

Azerbaijan Exports AOM

Exports Systems Manager

Base Management Manager

Production and Res Perf. TL

BMM

Manager, Base Management

DWG Base Mgmt TL

DOCUMENT AUTHORITY

Final authority on documentation

Document control will maintain documentation data base (document numbering and version

DOCUMENT COORDINATOR

control)

DOCUMENT CUSTODIAN

Will maintain the document

OWNS THE DOCUMENT AND IS RESPONSIBLE TO ENSURE THAT IT IS APPROPRIATELY

DOCUMENT OWNER

MAINTAINED

DISCIPLINE RESPONSIBLE ENGINEERS (ELECTRICAL/ INST/ CONTROL/ SIS/ MECHANICAL ETC)

DRE (DISCIPLINE)

(as found in the TA/ DRE register)

DRE (ELECTRICAL)

DISCIPLINE RESPONSIBLE ENGINEER ELECTRICAL (as found in the TA/ DRE register)

DRE (INSTRUMENT/ CONTROL/

DISCIPLINE RESPONSIBLE ENGINEER INSTRUMENT / CONTROL / SAFETY INSTRUMENTED

SIS)

SYSTEMS (as found in the TA/ DRE register)

DRE (MECHANICAL)

DISCIPLINE RESPONSIBLE ENGINEER MECHANICAL (as found in the TA/ DRE register)

DRE (PRODUCTION CHEMIST)

DISCIPLINE RESPONSIBLE ENGINEER PRODUCTION CHEMIST (as found in the TA/ DRE register)

E&P VP

EXPLORATION AND PRODUCTION SEGMENT VICE PRESIDENT

ENGINEERING AUTHORITY

CONTROLS THE MASTER EQUIPMENT LIST AS HELD IN EWAREHOUSE

Eng & Data Coordinator

Offshore Data Lead

Project Data Coordinator

ENG DATA COORDINATOR

Eng & Data Coordinator

Eng & Data Mgmt Team Leader

Midstream Data Lead

ENGINEER (DISCIPLINE)

ENGINEERS WITHIN THE ORGANISATION

(OPERATIONS) ABB CONTRACTOR

(MIDSTREAM SANGACHAL) ICSS SPECIALIST

ENGINEER (SYSTEMS)

(MIDSTREAM EXPORTS AZERBAIJAN) ABB CONTRACTOR

OPERATIONS:

ENVIRONMENTAL ADVISOR (CHIRAG & DWG)

ENVIRONMENTAL ADVISOR (AZERI)

ENVIRONMENTAL ADVISOR (SD & LOGISTICS)

MIDSTREAM Sangachal;

ST ENVIRONMENT ADVISOR

ENVIRONMENTAL ADVISOR

MIDSTREAM EXPORTS AZERBAIJAN;

AZ EXP ENVIROMENT ADVISOR

MIDSTREAM EXPORTS GEORGIA

GEO EXP ENVIRONMENT OFFICER

OPERATIONS:

Offshore installation manager (Azeri/ Chirag & DWG/ SDA)

MIDSTREAM Sangachal:

Operations superintendent (gas / oil/ utilities)

MIDSTREAM Export systems (Az/ Geo/Turk);

Export operations superintendant

Facility Manager

MIDSTREAM Exports Azerbaijan:

PSA2/IPA1 Site Controller

RoW and BV Operations Supervisors

WREP Site Controllers

MIDSTREAM Exports Georgia:

OPERATIONS SUPERVISOR SUPSA TERMINAL

AzSPU-GEN-PRC-001-A2

Page 14 of 102

MoC Group

Typical Job Function

PSG1 & AREA 72 SITE CONTROLLER

PSG2 & AREA 75 SITE CONTROLLER

A80 & EDDF SUPERVISOR

WREP SUPERVISOR GEORGIA OPS PS15, PRS1 PRS2

WREP SUPERVISOR GEORGIA OPS, PS11 PS 13

AGT ROW SUPERVISOR

WREP ROW SUPERVISOR

OPERATIONS:

Offshore operations engineer

MIDSTREAM Sangachal:

N/A facility manager will complete this function

MIDSTREAM Export systems (Az/ Geo/Turk);

Facility Ops Engineer

Operations engineer

MIDSTREAM Exports Azerbaijan:

N/A facility manager will complete this function

MIDSTREAM Exports Georgia:

N/A facility manager will complete this function

OPERATIONS:

OTL (Azeri/ Chirag & DWG/ SDA)

MIDSTREAM Sangachal:

AREA AUTHORITY (OPS SUPER, OIL)

MIDSTREAM Export systems (Az/ Geo/Turk);

Operations engineer (FACILITY MANAGER)

FACITLIY OPS SUPERVISORS

MIDSTREAM Exports Azerbaijan:

PSA2 OPERATIONS SUPERVISORS

IPA1 OPERATIONS SUPERVISORS

RoW and BV Operations Supervisors (FACILITY MANAGER)

WREP Site Controllers ((FACILITY MANAGER)

MIDSTREAM Exports Georgia:

N/A facility manager will complete this function

(OPERATIONS) GOC ENGINEER

(MIDSTREAM SANGACHAL) GOC COORDINATOR

GOC COORDINATOR

(MIDSTREAM EXPORTS AZERBAIJAN) SENIOR GOC ENGINEER

(MIDSTREAM EXPORTS AZERBAIJAN) N/A

H&S Team Leader Shah Deniz

H&S Team Leader Azeri

H&S Team Leader Logistics/Infrastructure

Az Exp H&S Team Leader

H&S TL/ ENV & COMPLIANCE TL

Geo Exp H&S Team Leader

ST Site H&S Advisor TL

H&S Team Leader Chirag & DWG

H&S Team Leader

HR MANAGER

Human resources manager

HR SPECIALIST

Human resources specialist

HSE Compliance Advisors within AzSPU HSE Compliance Team

HSE Compliance Advisor

ST Compliance Advisor

HSE COMPLIANCE ADVISOR

Az Exp Compliance Lead

HSE Compliance Specialist

Offshore Compliance Advisor

Waste Management H&S Advisor

Logistics/Infrastructure H&S Lead

HSEA

Chirag & DWG H&S Advisor

Geo Exp Site H&S Advisor TL

AzSPU-GEN-PRC-001-A2

Page 15 of 102

MoC Group

Typical Job Function

MARINE AUTHORITY

MAINTENANCE ENGINEER IN THE RELIABLITY MAINTENANCE TEAM

MAINTENANCE ENGINEER

IN MID STREAM NOT APPLYING GMS THEN THIS MAY BE THE MAINTENANCE SUPERVISOR

MANAGER

DEPARTMENT MANAGER

MOC/EQ ADVISOR

MOC/ EQ TEAM

MOC SYSTEMS TEAM LEADER

OMA

OPERATIONS MARINE AUTHORITY

RMM

Reservoir Management Manager

SENIOR Inspection Engineer

Senior inspection engineers as contracted

(contractor)

SETA

Global Segment Engineering Technical Authority

SPUL

STRATEGIC PERFORMANCE UNIT LEADER

TECHNICAL AUTHORITY MATERIALS & CORROSION MANAGEMENT (as found in the TA/ DRE

TA (CORROSION)

DISCIPLINE TECHNICAL AUTHORITIES (ELECTRICAL/ INST/ CONTROL/ SIS/ MECHANICAL ETC)

TA (DISCIPLINE)

(as found in the TA/ DRE register)

TA (INPSECTION)

TECHNICAL AUTHORITY INSPECTION (as found in the TA/ DRE register)

TA (PROCESS SAFETY)

PROCESS SAFETY TECHNCIAL AUTHORITY

TA (PROCESS)

TECHNICAL AUTHORITY PROCESS (as found in the TA/ DRE register)

TEAM LEADER

TL- IT&S

IT&S team leader and business information manager

BIM OFFSHORE OPERATIONS AND DRILLING

BIM FUNCTIONS

TL- IT&S BIM

BIM MIDSTREAM

BIM RESOURCES

OPERATIONS:

AESTL (AZERI/ CHIRAG & DWG/ SDA)

DISCIPLINE ENGINEERING TL

MIDSTREAM SANGACHAL:

ENGINEERING MANAGER SANGACHAL TERMINAL

TL-Eng

MIDSTREAM Export systems (Az/ Geo/Turk);

ENGINEERING MANAGER

MIDSTREAM Exports Azerbaijan:

N/A

MIDSTREAM Exports Georgia:

N/A

(COD) ENGINEERING MANAGER (SMALL PROJECTS)

TL-MODS

(OPERATIONS) PROJECTS AND MODS TL

VICE PRESIDENT

DRE (PRISM)

DISCIPLINE RESPONSIBLE ENGINEER FOR PRISM SYSTEMS (as found in the TA/ DRE register)

ENGINEER (PIN)

PIN SUPPORT ENGINEER

APPLICATIONS MANAGER (IT&S)

REGIONAL FIELD DIGITAL

INFRASTRUCTURE MANAGER

REGIONAL FIELD DIGITAL INFRASTRUCTURE MANAGER (IT&S)

(IT&S)

MAXIMO maintenance coordinator

MAXIMO maintenance coordinator (activity planning team)

Operations;

Site Scheduler CA

Site Scheduler WA

Site Scheduler EA

Site Scheduler DWG

Site Scheduler CHIRAG

Site Scheduler SHAH DENIZ

MIDSTREAM SANGACHAL;

Site Scheduler

MAINTENANCE SCHEDULER (GAS)

MAINTENANCE PLANNER (OIL)

MIDSTREAM EXPORTS SYSTEMS;

N/A

MID STREEAM EXPORTS AZERBAIJAN

PLANNER / SCHEDULER

MID STREAM EXPORTS AZERBAIJAN

PLANNER

DRE(PROCESS)

DISCPLINE REPSONSIBLE ENGINEER FOR PROCESS (as found in the TA/ DRE register)

TA (PROD CHEMIST & FLOW

TECHNICAL AUTHORITY PRODUCTION CHEMIST & FLOW ASSURANCE (as found in the TA/ DRE

ASSURANCE)

AzSPU-GEN-PRC-001-A2

Page 16 of 102

8 Abbreviations and Definitions

This table explains any terminology used within the text that is considered to require clarification. This can be useful

in simplifying the text by assigning abbreviations for repetitive terms.

ACC

Authorization for Chemical Change

ADES

Contracting company for Sumgayit Waste disposal Site 2

AWS

Contacting company for Sumgayit Waste disposal Site 2

BHA

Bottom Hole Assembly

BiL

Botas International Ltd - the BTC operator in Turkey

BTC

Baku Tbilisi Ceyhan oil export pipeline

CMMS

Computerized Maintenance Management system

CSM

Contacting company for logistics supply Base at SPS

D,C&I

Drilling, Completions and Interventions

DCT

Digital Communication Technology

DRE

Discipline Responsible Engineer

Engineering Authority

Emergency change

Change which is required for safe operation in these cases a formal MoC will be raised within 96hrs.

e-MoC

Electronic management of change database tool

ESD

Emergency Shut Down

ETP

Engineering Technical Practice

F&G

Fire and Gas

GOC

Guidance on Certification

HAZOP

Hazard and Operability Study

HOD

Head of discipline

HSSE

Heath Safety Security Environment

Job Plan

Maint

Maintenance

MoC

Management of Change

Mods

Modifications

Ops

Operations

P&ID

Piping and instrument diagram

Permanent change

Change that will be in place for more than 90 days

PFD

Process flow diagram

Planned Maintenance

PSV

Pressure Safety Valve

PUL

Performance Unit Leader; the operating area manager

SAFOP

Safety and Operability

SCE

Safety Critical Equipment

SCP

South Caucasus gas export Pipeline

SIL

Safety Integrity Level

SNR

Senior

Technical Authority

TS (Expert)

Technical Specialist (Expert) with respect to PSCM issues.

Temporary Change

Change that is intended to be in place for less than 90 days.

Team Leader

TTMHC

Contracting company for Sumgayit Waste disposal Site 1

WREP

Western Route Export Pipeline

WSL

Well site leader

Vice President AzSPU

E&P VP

GOBAL SEGEMENT VICE PRESIDENT E&P

ACET

Asset Condition Evaluation Tool

SDA

Shah Deniz Alpha

PRISM

Production Reporting and Information Systems Management

9 References

Document number

Document title

Applies to

MoC register

AzSPU

Technical, process software,

GP 48-02

Hazard and Operability (HAZOP) study

chemical

Technical, process software,

AZ-GP 48-02-1

Hazard and Operability (HAZOP) study (AzSPU STP)

chemical

MOC-FRM-003

Technical MoC document check list

Technical

AzSPU-GEN-PRC-001-A2

Page 18 of 102

Document number

Document title

Applies to

MOC-FRM-008

MoC prioritization tool

AzSPU

Process software MoC change impact assessment &

MOC-FRM-009

Process software

document checklist

MOC-FRM-011

Chemical MoC check list

Chemical

MOC-FRM-013

Tag request from

Technical,Process software

MOC-FRM-014

Maintenance MOC PM and JP change form

Maintenance

MOC-FRM-015

Maint MoC PSV deferral

Maintenance

MOC-FRM-019

Organization MoC handover form

Organizational

MOC-FRM-020

Organization MoC risk and mitigation

Organizational

MOC-FRM-021

Organization MoC risk matrix

Organizational

MOC-FRM-022

Organization MoC close out review

Organizational

MOC-FRM-023

MoC audit template

AzSPU

MOC-FRM-024

Tech MoC PSSR check list

Technical

MOC-FRM-025

HSSE Compliance Form

Technical, chemical

Recommended practice for the risk-based inspection (RBI)

MOC-FRM-GN-008

Maintenance

of relief valves

SHDU-ENG-PRC-001

Weight change procedure for Shah Deniz platform

AzSPU

UNIF ENG PRC 142

Weight change procedure for ACG platforms

AzSPU

UNIF-ENG- REG-021

Production chemical register

Chemical

Engineering maintenance common documents

UNIF-ENG-PRC-022

implementation procedure

UNIF-ENG-REG-005

EA/TA/DRE register

AzSPU

UNIF-ENG-WCS-001

Weight change sheet

Technical, chemical

UNIF-ITS- REG-001

AzSPU software applications register

IT&S

UNIF-OPS-PRC-001

Documentum document control procedure

Document

Technical, process software,

BP-CDZZZZ-PM-GLN-0001

Guidance on certification (GOC)

chemical

AzSPU HSE document management procedure and HSSE

AZSPU-HSSE-DOC-00025-2

Document

document template

Safety Critical Equipment (SCE) Management Strategy in

Guidance on how to identify SCE

AzSPU-GP-32-3001

AzSPU

equipment

MOC-FRM-026

Documentum controlled document template

Document

AzSPU Guidance on Technical Hazard and Risk Processes to

MoC Appendix 1

AzSPU

be used within MoC Appendix 1

AzSPU-GEN-PRC-001-A2

Page 19 of 102

10 Specific Guidance - Technical MoC

Technical Change is a permanent, temporary or emergency physical change that affects process or facilities of the BP operated

operating areas.

10.1 Technical MoC - Roles and Responsibilities

THOSE IDENTIFED BY A * ARE A MINIMUM REQUIREMENT FOR RISK LEVEL 1

Risk

MoC Stage /Role

JOB FUNCTION

Responsibility

Level

Create the eMOC choosing the affected Area and Facility and will choose the correct template for the MoC type process to be

followed (the use of a technical template is a mandatory requirement).

Will identify the scope of work (identifies the change which identifies and describes all work necessary to produce the change.

The scope establishes the tone for the remainder of the planning efforts and therefore should be sufficiently detailed.).

Will provide a justification for the work (this section details why the change is required)

Will provide details of other options considered.

Where the change is required due to some other business process, Engineering Query, incident report etc, the initiator should

ANYONE

reference this process.

Initiate

(IF AN EQ REQUIRES A MOC

1/2/3/4

The initiator is required to identify the Change Verifier (Facility Manager & TL Eng) as per the specific guidance for the

THEN THE EQ RESPONDER

technical MoC.

SHOULD INITIATE THE MOC)

The initiator is required to suggest a priority as per the definition in this procedure

The initiator will attach all relevant documentation as applicable to MoC for information at REV A (later versions may be used if

available)

The EQ system is used by the operating area operations teams to formally raise technical questions and should be linked if

available. Operating areas may cancel an MoC that has not been agreed using the EQ or other operating area system.

AzSPU-GEN-PRC-001-A2

Page 20 of 102

Risk

MoC Stage /Role

JOB FUNCTION

Responsibility

Level

Verify or cancel MoC on behalf of the local operations

The initiator is required to identify other reviewers and approvers and authorizers as defined as a minimum requirement under

FACILITY MANAGER

1/2/3/4

each MoC type

Confirm level of priority using the prioritization tool based on the anticipated benefit of the change

(If the change is to be rejected) Will cancel the MoC giving a reason

Verify or cancel MoC on behalf of the local operations, confirm the risk level

It should be noted verification should not be given until the person (s) nominated as responsible for the detail design has

completed all the necessary activities to ensure that

 The change is described clearly and adequately avoid any possible confusion

 The justification for the change is clear and adequate

 All options have been considered and documented in the MoC (as appropriate)

 Budget is approved and a cost center is identified (as appropriate)

 Any post start up reviews that may be required to assess the success of the change (as appropriate) have been

identified.

 All persons who are required to execute the various stages of the MoC have been identified

 Priority level as per the IFP matrix has been confirmed

 Person responsible for the detailed design and will ensure that all a full design work pack is assembled and attached

with all document marked up REV A dated and signed

*TL- ENG

1/2/3/4

 The full scope of work is agreed and appropriate documentation is in place

(KEY VERIFIER)

 Identify any hazards and assess risk associated with change as per the OMS requirements

Verify

Note the Engineer nominated for design should always be identified as a verifier

Once the design is in place is responsible to identify hazard and assess risk using the appropriate management of risk process

(GRP3.1-001 selection of Hazards Evaluation & Risk assessment techniques) this process should involve the appropriate

reviews as required, this should be done with appropriate persons around a table. This allows the key verifier to confirm or

change the risk level (this includes deviations from company or industry standards or practices and any compliance issues).

Details of the risk assessment process used and a summary of the results will be recorded in the risk statement in the MoC

initiation page. Detail record will be attached or linked to the MoC.

To ensure that the hazard identification and risk assessment process is formally recorded and attached or linked to the MoC

for future reference

If the change is to be rejected will cancel the MoC giving a reason

Accountable for all identified requirements at this stage of the MoC

*ENGINEER (DISCIPLINE)

Responsible for the detail design associated with the change and will not verify the MoC until this has been provided.

Nominated person or persons

Will ensure that all affected drawings are checked out from documentum as required by this procedure.

1/2/3/4

responsible for the detailed

design as assigned by the TL

-Eng

1/2/3/4

TL-MODS

Verify or cancel Brownfield MoC Identify the Brownfield Coordinator

Verify or cancel Risk level 3 or 4 MoC

3/4

AOM

If the change is to be rejected will cancel the MoC giving a reason

AzSPU-GEN-PRC-001-A2

Page 21 of 102

Risk

MoC Stage /Role

JOB FUNCTION

Responsibility

Level

To hold the MoC by checking the hold tick box the MoC until all information and data is fully available

To manage the MoC through the process ensuring that correct persons are notified, that comments are answered and the MoC

is properly planned, executed and closed out (as part of this will facilitate any interaction between reviews and designers)

To ensure that all documents as required by the MoC are properly filed and organized (documents to be sectioned by, for

design(rev A )/ for construction(rev C) /red line (R), red line as-built (R with as built stamp) Note that drawings attached for

information will need to be in Documentum MoC folder named for review/ information

Note that for drawings to be actioned by DCMT will need to be transferred to an MoC folder named For Issue.

Note that for data and maintenance / inspection requirements documents (request forms, tdt‟s) need to be added to

Documentum MoC folder, Eng Data & Maintenance & Inspection to be actioned by the MAXIMO Maintenance Coordinator and

Coordinator

1/2/3/4

ANYONE AUTHORIZED

the Eng Data Coordinator

To ensure that all pre-implementation and post implementation actions have been identified and completed.

The Coordinator will also raise Chemical/ Software MoC as required to support the Technical MoC (note that data /

maintenance and document changes that form part of the Technical MoC do not require an additional MoC to be raised)

To ensure that all tags, line numbers and cable numbers have been booked out of eWarehouse

To ensure that all equipment has been properly identified and tags, cable numbers and line numbers have been reserved in

eWarehouse. All necessary information is fed back before authorization

To ensure that the any weight changes associated with platform loading are identified recorded and submitted. Governing

procedures SHDU-ENG-PRC-001 and UNIF ENG PRC -142

The primary technical reviewer and will review against statutory and ETP requirements and engineering practice. All discipline

1/2/3/4

*DRE (DISCIPLINE)

to be included as required. Any changes affecting the P&ID‟s or PFD‟s must be reviewed by a DRE (Process)

Platform Weight changes must be reviewed by the DRE (structures)

1/2/3/4

HSEA

As required For changes affecting HSSE issues

1/2/3/4

AIA

Changes affecting static mechanical equipment future inspection requirements (including piping)

1/2/3/4

TA (PROCESS SAFETY)

Must review if a HAZOP is required

Reviewer

1/2/3/4

FACILITY OPS ENGINEER

As required for changes affecting the process operability

1/2/3/4

OMA

Must review for changes containing a Marine Element

Will communicate on-site operational changes to the HSE Compliance Advisors through completion of the first section of the

*H&S TL / ENV &

1/2/3/4

HSE Compliance Form and will update the facility APS list (if relevant) Will add a pre -implementation action for the HSE

COMPLIANCE TL

Compliance Advisor to determine and advise any compliance implications.

Independent Discipline Technical Review of `Medium and Risk level 3 (blue) MoC. Will not start the review process until the

2/3/4

TA-DISCIPLINE

Discipline Responsible Engineer has done the initial review.

1/2/3/4

*TL-ENG

Confirms that actions raised during the review stage have been addressed to their satisfaction

Approves for execution under control of operations team confirming that construction may start using normal site control

1/2/3/4

*FACILITY MANAGER

procedures.

1/2/3/4

TL-MODS

Approves Brownfield MoC

1/2/3/4

Approves changes containing a Marine Element

Approve

3/4

AOM

Operating area Approval Risk level 3 or 4 MoC

3/4

Engineering services manager

Independent Approval Risk level 3 or 4 MoC

3/4

Independent Approval Risk level 3 or 4 MoC

Independent Approval for Risk level 4 MoC

E&P VP OR CHIEF ENGINEER

Independent Approval for Risk level 4 MoC

AzSPU-GEN-PRC-001-A2

Page 22 of 102

Risk

MoC Stage /Role

JOB FUNCTION

Responsibility

Level

To ensure that all drawings and formal procedures requested have been checked out of documentum against the MoC

To ensure that there is a construction work pack and all necessary GOC certificates have been generated and pre-populated

with the data from eWarehouse

To ensure that any Software changes have been captured by a Process Software MoC and the MoC link attached to the

Technical MoC

To ensure that any Chemical changes have been captured by a Chemical MoC and the MoC link attached to the technical MoC

To confirms Tags / Line numbers / Cable numbers have been reserved and associated design data has been given to the ENG

& DATA COORDINATOR

1/2/3/4

*COORDINATOR

To confirms that any weight changes have been recorded and submitted. Governing procedures SHDU-ENG-PRC-001 and UNIF

ENG PRC -142

All pre start up checks and GOC documentation has been completed. The SH1 form with punch lists have been signed and that

there are no out standing

“A punchlist items” on the punch list

To ensure that affected drawings have been marked up as redlined drawings, stamped AS BUILT dated/ signed / Job Title

To ensure that all supplementary MoCs have Post Implement close out actions attached

To confirm that all redlined “ As built “REV R documents have been placed in the documentum MoC folder For Issue

To ensure that the HAZARD identification / RISK assessment process can be accessed from the MoC (if the MoC form isn‟t

used then a link is to be provided)

Pre Implement

To apply maintenance requirements as per generic maintenance strategy and maintenance manuals. Identify maintenance to

be planned including job plans, frequency, first start dates, locations any drawings to be linked to MAXIMO. The maintenance

1/2/3/4

MAINTENANCE ENGINEER

requirements will be attached to the MoC to allow the MAXIMO maintenance coordinator to clearly understand what needs to

be uploaded into MAXIMO

To review the construction pack including the resource and scheduling that have been identified as required by the maximo

1/2/3/4

*MTL

work order to support this activity

To apply inspection requirements as per integrity strategy and will identify job plans, frequency, first start dates, locations any

1/2/3/4

AIA

drawings to be linked to MAXIMO. The MAXIMO schedule requirements will be attached to the MoC to allow the MAXIMO

maintenance coordinator to clearly understand what needs to be uploaded into MAXIMO

To ensure that all eWarehouse data has been identified, supplied and uploaded in to eWarehouse (identified by the MoC

1/2/3/4

ENG DATA COORDINATOR

number). (The identification of tags, cable and line data early is important to allow the other process that require this data to

be operated correctly- it is anticipated that data is as built)

Ensure that all appropriate GOC requirements have be identified and certification is available in the construction pack (as

1/2/3/4

GOC COORDINATOR

required)

To review the operational changes communicated in the HSE Compliance Form and facilitate the process to determine whether

1/2/3/4

HSE COMPLIANCE ADVISOR

there are any compliance implications, this may lead to update of Compliance Task Manager (CMT) tasks

The authorizer is accountable for ensuring that all pre implement actions have been identified and closed out to their

Authorize

1/2/3/4

FACILITY MANAGER

satisfaction, before start up. Authorize MoC for startup on site.

AzSPU-GEN-PRC-001-A2

Page 23 of 102

Risk

MoC Stage /Role

JOB FUNCTION

Responsibility

Level

Ensure that all redline drawings have been reviewed and verified as REV R drawings to be actioned by DMT are in the MoC

folder named For Issue

Ensure GOC documentation is completed including any post SH1 requirements and that any outstanding “B punch list items“

have been raised as correctives in MAXIMO

1/2/3/4

*COORDINATOR

Ensure that any eWarehouse maintenance and inspection required data has been provided for the Master Equipment list,

actioned by MAXIMO Maintenance coordinator and the data will need to be transferred to an MoC folder named Eng Data,

Maintenance & Inspection

Confirm that the change performance has been acceptable and if applicable any lessons learnt are issued

1/2/3/4

COORDINATOR

Confirm temporary change in place (only applicable to temporary changes)

1/2/3/4

COORDINATOR

Confirm temporary change removed (only applicable to temporary changes)

DRE (INSTRUMENT/

1/2/3/4

Ensure that any software changes have been captured by a PROCESS SOFTWARE MoC and have been closed out

Post implement

CONTROL/ SIS)

DRE (PROCUCTION

1/2/3/4

Ensure that any CHEMICAL changes have been captured by a CHEMICAL MoC and have been closed out

CHEMIST)

Confirm that all “as built- final “ documents and procedures found in the for issue folder updated in Documentum main area

1/2/3/4

DOCUMENT COORDINATOR

and when back drafting is completed then rev Z drawings will also be upload at the next revision

Confirm that any “as built data Rev R as found in MoC folder named Eng Data, Maintenance & Inspection - is updated in

1/2/3/4

ENG DATA COORDINATOR

eWarehouse

Confirm that any “as built data final” are updated in ACET, the ACET coordinator will identity any other inspection

1/2/3/4

ACET DATA CONTROL

requirements once the RBI process has been done The inspection requirements will be attached to the MoC to allow the

MAXIMO maintenance coordinator to clearly understand what needs to be uploaded into MAXIMO

MAXIMO MAINTENANCE

Confirm that any maintenance inspection requirement identified by the maintenance Engineer or AIA have been executed in

1/2/3/4

COORDINATOR

MAXIMO

1/2/3/4

*COORDINATOR

Confirm that all post implementation actions have been completed as identified in this procedure

Close out

1/2/3/4

*MOC/ EQ TEAM

Confirm that all post implementation actions have been completed as identified in this procedure

Note: At any stage reviewers, approvers, post and pre implementation actions, may be added to the MoC, if considered necessary

Note: pre and post implementation actions can not be deleted - however in the event that the action is applicable, but due to circumstances that are out with the control of the site (ie net work

failure / documentum offline etc) the facility manager can agree to accept sign off of specific pre-implement requirements as long as they have been replicated in post implement section of the

MOC. The reason for this is to be noted in th e action comment field. The only exception to this is the requirement for GOC SH1 to be signed and all A punch list items closed

Note: All weight changes offshore in excess of 100kg should be recorded on the weight change form and submitted to the custodian of the weight change register: - Governing procedures SHDU-

ENG-PRC-001 and UNIF ENG PRC -142

Note: Installation and equipment installed on site shall be proven using the GOC technical check sheets. If the site does not have a GOC database then the MoC number will be used as the

reference number

AzSPU-GEN-PRC-001-A2

Page 24 of 102

10.2 Technical MoC - Templates

The following will be linked directly to the MoC template to assist with the uniform creation of MoC

Document number

Document Title

Applies to

Notes

TECHNICAL MoC

This is used to capture which changes are affected

MOC-FRM-003

DOCUMENT CHECK

TECHNICAL

by the MoC and should be completed before the

LIST

review

TECHNICAL MoC PSSR

Process start up safety review to be completed

MOC-FRM-024

TECHNICAL

CHECK LIST

before authorization

Used to communicate on-site operational changes to

HSSE COMPLIANCE

TECHNICAL,

the AzSPU HSE Compliance Team so that they can

MOC-FRM-025

FORM

CHEMICAL, DC&I

determine HSE compliance implications. Must be

completed before close out.

WEIGHT CHANGE

TECHNICAL,

To be completed for all weight changes on the

UNIF-ENG-WCS-001

SHEET

CHEMICAL

platforms in excess of 100kG

AZ GDP3.1-001 risk

RISK MATRIX

To be use to assess risk level, as required

matrix

10.3 Technical MoC - Risk / Hazard Guidance

Risk Level

Hazard Statement

Managed within the operating area no technical MoC required

 Like-for-like replacement (with the exception of equipment which requires a maintenance MoC to

Technical -

maintain a unique identification number (serial number) required for inspection purposes)

Insignificant

 Replacement in kind

(maintenance MoC required to update eWarehouse and any new maintenance

risk

requirements)

Managed within the Operating area - Technical MoC required

 MoC with a risk level 1 (OMS Risk Matrix)

 No or little impact on process safety.

 No change in Metallurgy

 No change in Cause and Affect table

Technical -

 No excursions from accepted operating Envelope

Risk level 1

 No detailed design requirement for a HAZID HAZOP SIL review

(white)

 No deviation from Company and/or international standards.

 MoCs that are duplicated for the purpose of repeat modifications on identical equipment but different

trains that have appropriate risk assessment review and approval on the first MoC, can be managed as

risk level 1 as long as the initial MoC that has captured the full review and approve cycle is clearly

referenced and linked

Managed within the Operating area but will have independent technical review and risk level 2 approvals. - MoC

required

 MoC with a risk level 2 (OMS Risk Matrix)

 Minimal impact on process safety.

 Require approved deviations from Company and or international standards.

 Change of service (eg changing the service of a tank from crude to produced water)

 Affects safety critical or SIL rated equipment.

Technical -

 Includes alterations to the pressure system envelope.

Risk level 2

(turquoise)

 Significant changes to the approved P&ID or PFD or C&E.

 May affect Hazardous area classification.

 Includes changes to Class 1 and Class 2 meters.

 Includes significant weight changes on the platform > 500kg.

 Includes changes to HV systems or main Electrical Distribution Systems.

AzSPU-GEN-PRC-001-A2

Page 25 of 102

Risk Level

Hazard Statement

Managed within the Operating area but will have independent technical review and risk level 3 approval. - MoC

required

 MoC with a risk level 3 (OMS Risk Matrix)

 Has significant impact on process safety.

Technical -

 Involves hot tapping / live work / diving operations.

Risk level 3

(Blue)

 Involves operation of equipment out side of normal operating parameters as identified on the P&ID or

PFD.

 Involves change to pressure relief systems.

 Require approved deviations from Group, Segment and AzSPU mandated ETP and STP‟s

Managed within the Operating area but will have independent technical review and risk level 4 approval. - MoC

Technical -

required

Risk level 4 -

 MoC with a risk level 4 (OMS Risk Matrix)

(Purple)

Note: This risk associated directly with making the change and should not be confused with MoC priority

10.4 Technical MoC - Documentation

At the heart of any change is the control of documents, procedures and drawings. Everyone needs to understand

the status of these documents at three key stages of change.

Note: It is essential that the Master document data-base is kept up to date

Stage

Requirement

All documents/drawings subject to change need to be checked out of documentum and a note

added to document data-base stating that the document/ drawing is affected by MoC ref number

Verify (Design)

Initial design document should include in the document name

- Rev A

Final design documents for review should include in the document name - Rev A

Within Documentum a MoC folder within a folder named for review / information should contain

the following

Authorisation (pre-start up)

Construction documents should include in the document name

- Rev C

As Built documents for review should include in the title - Rev R

Within Documentum a MoC folder within a folder named for issue should contain the following

Final As Built document should include in the document name

- Rev R (with an as-built stamp

Closure (post-start up)

dated and signed)

DMT will action all documents found in the “for issue folder” and updated the master document

area and action any back drafting that needs to be done.

10.5 Technical MoC - Key Indicators

 Number of days to close out an MoC after Authorization. This indicates how long it takes to get accurate

documents into the system.

 Number of MoCs authorized to start up at any one time - A high number indicates increased risk depending

on the sites ability to manage many simultaneous changes.

 Number of MoCs in Review and Approve stages - This indicates the loading on the teams.

AzSPU-GEN-PRC-001-A2

Page 26 of 102

10.6 Technical MoC - Process Flow Diagram

Technical MoC

Use template describe, detail

Identify

scope, justify estimate cost attach

the need

Anyone (if a EQ was

supporting documentation assign

for change

used the EQ responder

category, priority and risk level

yes

to initiate

canel

Confirm that the change is

FACILITY MANAGER

required and all info is included

TL -ENG

ENGINEER (DESIGN)

OTHERS AS

modify

REQUIRED

Complete the MoC detail ensuring that all effected

RISK LEVEL 3 OR 4

documents are check out from documentum

AOM

Design complete Identify hazards Assess risk

Confirm risk, category and priority identified

correctly

DRE(DISCIPLINE)

H&S TL/ ENV &

COMPLIANCE TL

Change accepted and meets

OTHERS AS

standards

REQUIRED

RISK LEVEL 2, 3 OR 4

YES

TL-ENG

FACILITY MANGER

Change accepted and all

OTHERS AS

issued addressed

REQUIRED

RISK LEVEL 3 OR 4

AOM, EA

RISK LEVEL 4

YES

VP & E&P VP

Hazard and risk has been assessed recorded in MoC

COORDINATOR

Ensure that tags / cable/ line number have been added to E-warehouse

MAINTENANCE

Ensure that child MOC that are required have been raised that weight changes reported.

ENGINEER

Maintenance / inspection requirements identified and added to the documentum

MAINTENANCE

folder for Data/ maintenance/ inspection

SUPERVISOR

AIA

ENG HSE DATA

Construction work pack with documents Rev C GOC

Ensure that all construction

CONTROLLER

certificates available

documents have been as built rev

HSE Compliance

Construct/ install/ pre commission GOC SH1 PL1 (A

R are scanned and uploaded into

Advisor

items) signed off. PSSR completed (check that any child

documentum For Issue Folder

OTHERS as required

MoC are complete if appropriate)

Commission

Ensure that all pre

Put to service

FACILITY MANAGER

implementation actions

Authorised

yes

Performance test

have been completed

Issue any lessons learnt

Ensure that all final document dated and signed are transferred to the for issue folder in

COORNINATOR

documentum and all as built data is in the data / maintenance / inspection folder

DOCUMENT

Maintenance / inspection requirements have been actioned

COORDINATOR

ENG HSE DATA

CONTROLLER

ACET DATA CONTROL

Data/ Maintenance / inspection requirements have been actioned

MAXIMO

All document have been upload in the master document area ( and back drafting arranged)

MAINTENANCE

COORDINATOR

All post implment

COORDINATOR

actions complete

MOC/EQ TEAM

yes

AzSPU-GEN-PRC-001-A2

Page 27 of 102

11 Specific Guidance - Technical MoC (DC&I Facilities)

Technical Change is a permanent, temporary or emergency change that affects drilling process or facilities of the BP operated operating areas

11.1 Technical MoC (DC&I Facilities) - Roles and Responsibilities

THOSE IDENTIFED BY A * ARE A MINIMUM REQUIREMENT FOR RISK LEVEL 1

MoC Stage/Role

Risk

Job function

Responsibility

Create the eMOC choosing the affected Area and Facility and will choose the correct template for the MoC type process to

be followed (the use of a template is a mandatory requirement).

Will identify the scope of work (identifies the change which identifies and describes all work necessary to produce the

change. The scope establishes the tone for the remainder of the planning efforts and therefore should be sufficiently

detailed.).

Will provide a justification for the work (this section details why the change is required)

*ANYONE

Will provide details of other options considered.

Initiate

(if a SEQ requires a MoC then the

Where the change is required due to some other business process, Engineering Query, incident report etc, the initiator

1/2/3/4

SEQ responder should initiate the

should reference this process.

MoC)

The initiator is required to identify the Verifiers ((DC&I) WSL & (DC&I) TL-ENG (KCAD) as per the specific guidance for the

MoC.

The initiator is required to suggest a priority as per the definition in this procedure

The initiator will attach all relevant documentation as applicable to MoC for information at REV A (LATER VERSIONS MAY

BE USED IF AVALIBLE)

The SEQ system is used by the Drilling operations teams to formally raise technical questions and should be linked if

available. A MoC that has not been agreed using the SEQ or other system may be cancelled.

AzSPU-GEN-PRC-001-A2

Page 28 of 102

Verify or cancel MoC on behalf of the local operations

1/2/3/4

*(DC&I) WSL

Confirm level of priority using the prioritization tool based on the anticipated benefit of the change

Will cancel the MoC giving a reason If the change is to be rejected.

To verify or cancel MoC on behalf of the local operations, confirm the risk level

The initiator is required to identify other reviewers and approvers and authorizers as defined as a minimum requirement

under each MoC type

It should be noted verification should not be given until the person (s) nominated as responsible for the detail design has

complete all the necessary activity to ensure that

 The change is described clearly and adequately to avoid any possible confusion

 The justification for the change is clear and adequate

 All options have been considered and documented in the MoC (as appropriate)

 Budget is approved and a cost center is identified (as appropriate)

 Any post start up reviews that may be required to assess the success of the change (as appropriate) have been

identified

 All persons who are required to execute the various stages of the MoC have been identified

 The priority level as per the IFP matrix has been confirmed

 Person responsible for the detailed design and will ensure that a full design work pack is assembled and attached

*(DC&I) TL-ENG (KCAD)

with all document marked up REV A dated and signed

1/2/3/4

Key Verifier

Note: the Engineer nominated for design should always be identified as a verifier



Verify

 The full scope of work is agreed and appropriate documentation is in place

 Identify any hazards and assess risk associated with change as per the OMS requirements

Once the design is in place is responsible to identify hazard and assess risk using the appropriate management of risk

process (GRP3.1-001 selection of Hazards Evaluation & Risk assessment techniques) this process should involve the

appropriate reviews as required, this should be done with appropriate persons around a table. Allowing the key verifier to

confirm or change the risk level (this includes deviations from company or industry standards or practices and any

compliance issues). Details of the risk assessment process used and a summary of the results will be recorded in the risk

statement in the MoC initiation page. Detail record will be attached or linked to the MoC.

To ensure that the hazard identification and risk assessment process is formally recorded and attached or linked to the

MoC for future reference

If the change is to be rejected will cancel the MoC giving a reason

Accountable for all identified requirements at this stage of the MoC

*(DC&I) ENGINEER (KCAD)

nominated person or persons

Responsible for the detail design associated with the change and will not verify the MoC until this has been provided.

1/2/3/4

responsible for the detailed design as

Will ensure that all affected drawings are checked out from documentum as required by this procedure.

assigned by the

2/3/4

(DC&I) RMTL

VERIFY OR CANCEL

3/4

(DC&I) WTL

Verify or cancel Risk level 3 or 4 MoC

3/4

(DC&I) WOM

Verify or cancel Risk level 3 or 4 MoC

AzSPU-GEN-PRC-001-A2

Page 29 of 102

To hold the MoC by checking the hold tick box the MoC until all information and data is fully available

To manage the MoC through the process ensuring that correct persons are notified, that comments are answered and the

MoC is properly planned, executed and closed out (as part of this will facilitate any interaction between reviews and

designers)

To ensure that all documents as required by the MoC are properly filed and organized (documents to be sectioned by, for

design(rev A )/ for construction(rev C) /red line (R), red line as-built (R with as built stamp) Note that drawings attached

for information will need to be in an Documentum MoC folder named for review/ information

Note that for drawings to be actioned by DCMT will need to be transferred to an MoC folder named for issue.

Note that for data and maintenance requirements documents (request forms, tdt‟s) will need to be in an Documentum MoC

Coordinator

1/2/3/4

*(DC&I) DRE (Discipline) (KCAD)

folder, Eng Data & Maintenance & Inspection to be actioned by the MAXIMO Maintenance Coordinator and the Eng HSE

Data coordinators

To ensure that all pre-implementation and post implementation actions have been identified and completed.

The Coordinator will also raise Chemical/ Software MoC as required to support the Technical MoC (note that eWarehouse /

maintenance and document changes that form part of the Technical MoC do not require an additional MoC to be raised)

To ensure that all tags, line numbers and cable numbers have been booked out of eWarehouse

To ensure that all equipment has been properly identified and tags cable numbers and line numbers have been reserved in

eWarehouse. All necessary information is fed back before authorization

Will ensure that the any weight changes associated with platform loading are identified recorded and submitted. Governing

procedures SHDU-ENG-PRC-001 and UNIF ENG PRC -142

The primary technical reviewer and will review against statutory and ETP requirements and engineering practice. All

1/2/3/4

*(DC&I) DRE (Discipline) (KCAD)

discipline to be included as required. Any changes affecting the P&ID‟s or PFD‟s must be reviewed by a DRE (Process)

Platform Weight changes must be reviewed by the DRE(structures)

Will communicate on-site operational changes to the HSE Compliance Advisors through completion of the first section of

1/2/3/4

*(DC&I) H&S TL

the HSE Compliance Form and will update the facility APS list (if relevant) Will add a pre-implementation action for the HSE

Compliance Advisor to determine and advise any compliance implications.

1/2/3/4

(DC&I) HSEA

For changes affecting HSE issues

Reviewer

(DC&I) MAINT SUPERINTENDENT

1/2/3/4

For changes affecting maintainability or operability of the equipment

(KCAD)

1/2/3/4

AIA

Changes affecting static mechanical equipment future inspection requirements. (including piping)

2/3/4

TA (process safety)

Must review if a HAZOP is required

1/2/3/4

OMA

For changes containing a Marine Element

Independent Discipline Technical Review for MoC with a risk level of greater than 2 Will not start the review process until

2/3/4

TA (DISCIPLINE)

the DRE has done the initial review

1/2/3/4

*(DC&I) TL-ENG (KCAD)

Confirms that actions raised during the review stage have been addressed.

Approves for execution under control of drilling team confirming that construction may start using normal site control

1/2

*(DC&I) WSL Snr

procedures.

1/2/3/4

For all changes containing a Marine Element

3/4

(DC&I) WTL

(DC&I) WTL SNR for Risk level 3 and 4MoC

Approve

3/4

Engineering services manager

Independent Approval Risk level 3 or 4 MoC

3/4

(DC&I) RMTL

(DC&I) Rig Maintenance Team leader)

3/4

Independent Approval for Risk level 3 and 4 MoC

Approval for Risk level 4 MoC

E&P VP

Approval for Risk level 4 MoC

AzSPU-GEN-PRC-001-A2

Page 30 of 102

To ensure that all drawings and formal procedures requested have been checked out of documentum against the MoC

To ensure that there is a construction work pack and all necessary GOC certificates have been generated and pre-

populated with the data from eWarehouse

To ensure that any Software changes have been captured by a Process Software MoC and the MoC link attached to the

Technical MoC

To ensure that any Chemical changes have been captured by a Chemical MoC and the MoC link attached to the technical

MoC

To confirm Tags / Line numbers / Cable numbers have been reserved and associated design data has been given to the

ENG DATA COORDINATORS

1/2/3/4

*COORDINATOR

To confirm that any weight changes have been recorded and submitted. Governing procedures SHDU-ENG-PRC-001 and

UNIF ENG PRC -142

All pre start up checks and GOC documentation has been completed. The SH1 form with punch lists have been signed and

that there are no outstanding

“A punch list items” on the punch list

To ensure that affected drawings have been marked up as redlined drawings stamped AS BUILT dated/ signed / Job Title

To ensure that all supplementary MoC have Post Implement close out actions attached

To Confirm that all redlined “ As built “REV R documents has been placed in the Documentum MoC folder For Issue Ensure

that the HAZARD identification / RISK assessment process can be accessed from the MoC (if the MoC form isn‟t used then a

link is to be provided

Pre Implement

To apply maintenance requirements as per generic maintenance strategy and maintenance manuals. Identify maintenance

to be planned including job plans, frequency, first start dates, locations any drawings to be linked to MAXIMO. The

1/2/3/4

(DC&I) TL- MAINT (KCAD)

maintenance requirements will be attached to the MoC to allow the MAXIMO maintenance coordinator to clearly understand

what needs to be uploaded into MAXIMO

To apply inspection requirements as per integrity strategy and will identify job plans, frequency, first start dates, locations

1/2/3/4

AIA

any drawings to be linked to MAXIMO. The MAXIMO schedule requirements will be attached to the MoC to allow the

MAXIMO maintenance coordinator to clearly understand what needs to be uploaded into MAXIMO

To review the construction pack including the resource and scheduling that have been identified requirements by the

1/2/3/4

(DC&I) TL- MAINT (KCAD)

maximo work order to support this activity

1/2/3/4

ENG DATA COORDINATOR

To ensures that all eWarehouse data has been supplied and uploaded in to eWarehouse

To ensure that all appropriate GOC requirements have be identified and certification is available in the construction pack

1/2/3/4

GOC Coordinator

(as required)

To review the operational changes communicated in the HSE Compliance Form and facilitate the process to determine

1/2/3/4

HSE COMPLIANCE ADVISOR

whether there are any compliance implications, this may lead to update of Compliance Task Manager (CTM) tasks.

*(DC&I) RIG SUPERINTENDENT

The authorizer is accountable for ensuring that all pre implement actions have been identified and closed out to their

1/2/3/4

Authorize

(KCAD)

satisfaction, before start up.

1/2/3/4

*FACILITY MANAGER

Authorize MoC for startup on site.

AzSPU-GEN-PRC-001-A2

Page 31 of 102

Ensure that all redline drawings have been reviewed and verified as REV R drawings to be actioned by DCMT are in the

1/2/3/4

*COORDINATOR

MoC folder named For Issue Ensure GOC documentation is completed including any post SH1 requirements

Confirm that the change performance has been acceptable and if applicable any lessons learnt are issued

Confirm any outstanding “B punch list items“ have been raised as correctives in maximo

Ensure that any eWarehouse maintenance and inspection required data has been provided for the Master Equipment list is

1/2/3/4

*(DC&I) TL- MAINT (KCAD

REV R “AS BUILT-final” actioned by Maximo Maintenance coordinator and the Eng Data coordinator will need to be

transferred to an MoC folder named Eng Data, Maintenance & Inspection

1/2/3/4

COORDINATOR

Confirm temporary change in place (only applicable to temporary changes)

1/2/3/4

COORDINATOR

Confirm temporary change removed (only applicable to temporary changes)

Post implement

(DC&I) DRE (INSTRUMENT/

1/2/3/4

Ensure that any software changes have been captured by a PROCESS SOFTWARE MoC and have been closed out

CONTROL/ SIS) (KCAD)

1/2/3/4

DRE (PROCUCTION CHEMIST)

Ensure that any CHEMICAL changes have been captured by a CHEMICAL MoC and have been closed out

Confirm that all “as built- final “ documents and procedures found in the for issue folder updated in Documentum main

1/2/3/4

DOCUMENT COORDINATOR

area and when back drafting is completed then rev Z drawings will also be upload at the next revision

Confirm that any “as built data Rev R as found in MoC folder named Eng Data, Maintenance & Inspection - is updated in

1/2/3/4

ENG DATA COORDINATOR

eWarehouse

Confirm that any “as built data final” are updated in ACET, the ACET coordinator will identity any other inspection

1/2/3/4

ACET DATA CONTROL

requirements once the RBI process has been done The inspection requirements will be attached to the MoC to allow the

MAXIMO maintenance coordinator to clearly understand what needs to be uploaded into MAXIMO

MAXIMO MAINTENANCE

1/2/3/4

Confirm that any maintenance inspection requirement identified have been executed in MAXIMO

COORDINATOR

1/2/3/4

*COORDINATOR

Confirm that all post implementation actions have been completed as identified in this procedure

Close out

1/2/3/4

*(DC&I) RMTL

Confirm that the Drilling operator has finished this modification to his satisfaction on behalf of BP

1/2/3/4

*MOC/ EQ TEAM

Confirm that all post implementation actions have been completed as identified in this procedure

Note: At any stage reviewers, approvers, post and pre implementation actions, may be added to the MoC, if considered necessary

Note: pre and post implementation actions can not be deleted - however in the event that the action is applicable, but due to circumstances that are out with the control of the site (ie net work

failure / documentum offline etc) the facility manager can agree to accept sign off of specific pre-implement requirements as long as they have been replicated in post implement section of the

MOC. The reason for this is to be noted in the action comment field. The only exception to this is the requirement for GOC SH1 to be signed and all A punch list items closed

Note: All weight changes offshore in excess of 100kg (should be recorded on the weight change form and submitted to the custodian of the weight change register: - Governing procedures SHDU-

ENG-PRC-001 and UNIF ENG PRC -142

Note: Installation and equipment installed on site shall be proven using the GOC technical check sheets. If the site does not have a GOC database then the MoC number will be used as the

reference number

AzSPU-GEN-PRC-001-A2

Page 32 of 102

11.2 Technical MoC (DC&I Facilities) - Templates

The following will be linked directly to the MoC template to assist with the uniform creation of MoC

Document number

Document Title

Applies to

Notes

TECHNICAL MoC

This is used to capture which changes are affected by the

MOC-FRM-003

TECHNICAL

DOCUMENT CHECK

MoC and should be completed before the review

LIST

Process start up safety review to be completed before

TECHNICAL MoC

TECHNICAL

MOC-FRM-024

authorization

PSSR CHECK LIST

Used to communicate on-site operational changes to the

TECHNICAL,

AzSPU HSE Compliance Team so that they can determine

HSSE COMPLIANCE

MOC-FRM-025

CHEMICAL, DC&I

HSE compliance implications. Must be completed before

FORM

close out

TECHNICAL,

To be completed for all weight changes on the platforms in

WEIGHT CHANGE

UNIF-ENG-WCS-001

CHEMICAL

excess of

100kG

SHEET

11.3 Technical MoC (DC&I Facilities) - Risk / Hazard Guidance

Risk Level

Hazard Statement

Managed within the operating area no technical MoC required

 Like-for-like replacement (with the exception of equipment which requires a maintenance MoC to

Technical -

maintain a unique identification number (serial number) required for inspection purposes)

Insignificant

 Replacement in kind

(maintenance MoC required to update eWarehouse and any new maintenance

Risk

requirements)

Managed within the Operating area - Technical MoC required

 MoC with a risk level 1 (OMS Risk Matrix)

 No or little impact on process safety.

Technical -

 No change in Metallurgy

Risk level 1

 No change in Cause and Affect table

(white)

 No excursions from accepted operating Envelope

 No detailed design requirement for a HAZID HAZOP SIL review

 No deviation from Company and/or international standards.

Managed within the Operating area but will have independent technical review and risk level 2 approvals. - MoC

required

 MoC with a risk level 2 (OMS Risk Matrix)

 Minimal impact on process safety.

 Require approved deviations from Company and or international standards.

 Change of service (eg changing the service of a tank from crude to produced water)

Technical -

 Affects safety critical or SIL rated equipment.

Risk level 2

(turquoise)

 Includes alterations to the pressure system envelope.

 Significant changes to the approved P&ID or PFD or C&E.

 May affect Hazardous area classification.

 Includes changes to Class 1 and Class 2 meters.

 Includes significant weight changes on the platform > 500kg.

 Includes changes to HV systems or main Electrical Distribution Systems.

AzSPU-GEN-PRC-001-A2

Page 33 of 102

Risk Level

Hazard Statement

Managed within the Operating area but will have independent technical review and risk level 3 approval. - MoC

required

 MoC with a risk level 3 (OMS Risk Matrix)

 Has significant impact on process safety.

Technical -

 Involves changes to well control equipment

Risk level 3

 Involves hot tapping / live work / diving operations.

(Blue)

 Involves operation of equipment out side of normal operating parameters as identified on the P&ID or

PFD .

 Involves change to pressure relief systems.

 Require approved deviations from Group, Segment and AzSPU mandated ETP and STP‟s

Technical -

Managed within the Operating area but will have independent technical review and risk level 4 approval. - MoC

Risk level 4 -

required

(Purple)

 MoC with a risk level 4 (OMS Risk Matrix)

Note: This risk associated directly with making the change and should not be confused with MoC priority

11.4 Technical MoC (DC&I Facilites) - Documentation

At the heart of any change is the control of documents, procedures and drawings. Everyone needs to understand

the status of these documents at three key stages of change.

Note: it is essential that the Master document data-base a is kept up to date

Stage

Requirement

All documents/drawings subject to change need to be checked out of documentum and a note

added to document data-base stating that the document/ drawing is affected by MoC ref

Verify (Design)

number

Initial design document should include in the document name

- Rev A

Final design documents for review should include in the title - Rev A

Within documentum a MoC folder within a folder named for review / information should

contain the following

Authorisation (pre-start up)

Construction documents should include in the document name

- Rev C

As Built documents for review should include in the title - Rev R

Within documentum a MoC folder within a folder named for issue should contain the following

Final As Built document should include in the document name

- Rev R (with an As-built stamp

Closure (post-start up)

dated and signed)

DCMT will action all documents found in the “for issue folder” and updated the master

document area and action any back drafting that needs to be done.

11.5 Technical MoC (DC&I Facilities) - Key Indicators

 Number of days to close out an MoC after authorized, this indicates how long it takes to get accurate

documents in the system

 Number of MoCs authorized to start up at any one time - A high number indicates increased risk depending

on the sites ability to manage many simultaneous changes

 Number of MoCs in Review and Approve stages - This indicates the loading of the facility teams

AzSPU-GEN-PRC-001-A2

Page 34 of 102

11.6 Technical MoC (DC&I Facilities) - Process Flow Diagram

Technical MoC (DC&I FACILITIES)

Use template describe, detail

Identify

scope, justify estimate cost attach

the need

supporting documentation assign

Anyone (if a SEQ was used

for change

category, priority and risk level

the SEQ responder to initiate

yes

canel

Confirm that the change is

(DC&I) WSL

required and all info is included

(DC&I) TL-ENG (KCAD)

(DC&I) ENGINEER (KCAD)

(DC&I) RMS

modify

OTHERS AS REQUIRED

Complete the MoC detail ensuring that all effected

RISK LEVEL 3 OR 4

documents are check out from documentum

(DC&I) WTL

(DC&I) WOM

Design complete Identify hazards Assess risk

Confirm risk, category and priority identified

correctly

(DC&I) DRE (DISCIPLINE)

(KCAD)

Change accepted and meets

DC&I H&S TL

standards

OTHERS AS REQUIRED

RISK LEVEL 2, 3 OR 4

YES

(DC&I) TL-ENG (KCAD)

(DC&I) WSL SNR (KCAD)

OTHERS AS REQUIRED

Change accepted and all

RISK LEVEL 3 OR 4

issued addressed

(DC&I) WTL

(DC&I) WOM

(DC&I) RMTL

YES

RISK LEVEL 4

VP & E&P VP

Hazard and risk has been assessed recorded in MoC

Ensure that tags / cable/ line number have been added to E-warehouse

COORDINATOR

Ensure that child MOC that are required have been raised that weight changes reported.

(DC&I) TL-MAINT(KCAD)

Maintenance / inspection requirements identified and added to the documentum

AIA

folder for Data/ maintenance/ inspection

ENG HSE DATA

CONTROLLER

Construction work pack with documents Rev C GOC

Ensure that all construction

HSE COMPLIANCE

certificates available

documents have been as built rev

ADVISOR

Construct/ install/ pre commission GOC SH1 PL1 (A

R are scanned and uploaded in to

documentum for review and

OTHERS

items) signed off. PSSR completed (check that any child

information folder,

MoC are complete if appropriate)

Commission

(DC&I) RIG

Ensure that all pre

Put into service

SUPERINTENDENT (KCAD)

implementation actions

Authorised

yes

Performance test

FACILITY MANAGER

have been completed

Issue any lessons learnt

Ensure that all final document dated and signed are transferred to the for issue folder in

COORNINATOR

documentum and all as built data is in the data / maintenance / inspection folder

DOCUMENT

Maintenance / inspection requirements have been actioned

COORDINATOR

ENG HSE DATA

CONTROLLER

Data/ Maintenance / inspection requirements have been actioned

ACET DATA CONTROL

All document have been upload in the master document area ( and back drafting arranged)

MAXIMO MAINTENANCE

COORDINATOR

All post implment

(DC&I) RMTL

actions complete

MOC/EQ TEAM

yes

AzSPU-GEN-PRC-001-A2

Page 35 of 102

12 Specific Guidance - Process Software MoC

Process Software MoC covers the management change associated with process software and electrical protection settings.

Note: Although a Process Software MoC can involve minor physical changes these are restricted to modifications “within the system” e.g. internal panel wiring / relays / additions of an hardwired

intertrips where the I/O for both Nodes would be existing / Firmware upgrades. All would be allowed as long as the correct review is completed by the correct reviewers. External connections to

other sub-systems should be considered to be covered under a separate technical MoC

The person who verifies these modifications needs to decide if a Technical MoC needs to be raised to cover these changes as identified by the scope, and should also consider any impact on

ancillary systems such as HVAC or F&G systems which would also required to be considered and as such would need Technical MoC.

Note: Offline back ups will be managed for each facility by the DRE (INSTRUMENT/ CONTROL/ SIS)

Note: This MoC type will be used for PRISM software changes

12.1 Process Software MoC - Roles and Responsibilities

THOSE IDENTIFED BY A * ARE A MINIMUM REQUIREMENT FOR RISK LEVEL 1

MoC Stage/

Risk

Job Function

Responsibility

Role

Create the eMOC choosing the affected Area and Facility and will choose the Process software template the use of a

template is a mandatory requirement).

*ANYONE

To identify the scope of work (identifies the change which identifies and describes all work necessary to produce the

(if EQ requires a MoC then the EQ

change. The scope establishes the tone for the remainder of the planning efforts and therefore should be sufficiently

responder should initiate the MoC)

detailed.).

To provide a justification for the work (this section details why the change is required)

Before initiating it is advised to review

To provide details of other options considered.

Initiate

1/2/3/4

the scope with the DRE

Where the change is required due to some other business process, Engineering Query, incident report etc, the initiator

(INSTRUMENT/ CONTROL/ SIS)

shall reference this process.

The initiator is required to identify the Key Verifier as identified in the procedure and identify others as required by the

procedures

ENGINEER (PIN) OR DRE (PRISM) for

To suggest priority

PRISM software changes

The EQ system is used by the operating area operations teams to formally raise technical questions and should be linked if

available. Operating areas may cancel a MoC that has not been agreed using the EQ or other operating area system.

AzSPU-GEN-PRC-001-A2

Page 36 of 102

MoC Stage/

Risk

Job Function

Responsibility

Role

To verify or cancel MoC on behalf of the local operations, confirm the risk level

It should be noted verification should not be given until the person (s) nominated as responsible for the detail design has

complete all the necessary activity to provide to ensure that (note that this may be the DRE (instrument / control/ sis) or

another)

 change is described clearly and adequately to avoid any possible confusion

 The full scope of work is agreed and appropriate documentation is in place

 The justification for the change is clear and adequate

*DRE (INSTRUMENT/ CONTROL/ SIS)

 All options have been considered and documented in the MoC (as appropriate)

 Budget is approved and a cost center is identified (as appropriate)

Or DRE (ELECTRICAL) for electrical

 Any post start up reviews that may be required to assess the success of the change (as appropriate) have been

protection changes

identified

 Identify who is required to execute the various stages of the MoC

1/2/3/4

 Priority levels are correct

ENGINEER (PIN)) OR DRE (PRISM) for

PRISM SOFTWARE CHANGES

Once the design is in place is responsible to identify hazard and assess risk using the appropriate management of risk

process (GRP3.1-001 selection of Hazards Evaluation & Risk assessment techniques) this process should involve the

(key Verifier)

appropriate reviews as required, this should be done with appropriate persons around a table. Allowing the key verifier to

confirm or change the risk level (this includes deviations from company or industry standards or practices and any

Verify

compliance issues). Details of the risk assessment process used and a summary of the results will be recorded in the risk

statement in the MoC initiation page. Detail record will be attached or linked to the MoC.

To ensure that the hazard identification and risk assessment process is formally recorded and attached or linked to the

MoC for future reference

Will cancel the MoC giving a reason, if the change is to be rejected

Accountable for all identified requirements at this stage of the MoC

*ENGINEER

Responsible for the detail design associated with the change and will not verify the MoC until this has been provided.

nominated person or persons

Will ensure that all affected drawings are checked out from documentum as required by this procedure.

1/2/3/4

responsible for the detailed design as

assigned by the verifier

1/2/3/4

TL-MODS

Verify or cancel Brownfield MoC

3/4

TL-ENG

Verify or cancel Risk level 3 or 4 MoC

AzSPU-GEN-PRC-001-A2

Page 37 of 102

MoC Stage/

Risk

Job Function

Responsibility

Role

To hold the MoC by checking the hold tick box the MoC until all information and data is fully available

To manage the MoC through the process ensuring that correct persons are notified, that comments are answered and the

MoC is properly planned, executed and closed out (as part of this will facilitate any interaction between reviews and

*DRE (INSTRUMENT/ CONTROL/ SIS)

designers)

To ensure that all documents as required by the MoC are properly filed and organized (documents to be sectioned by, for

Engineer (I&C, Systems)

design(rev A )/ for construction(rev C) /red line (R), red line as-built (R with as built stamp) Note that drawings attached

for information will need to be in an Documentum MoC folder named for review/ information. Software impact assessment

Or DRE (ELECTRICAL) for electrical

form completed and all affected documentation listed within

Coordinator

1/2/3/4

protection changes

Note that for drawings to be actioned by DCMT will need to be transferred to a documentum MoC folder named “for

issue”.

Note that for data documents (request forms, tdt‟s) will need to be in an Documentum MoC folder named “Eng Data &

ENGINEER (PIN)) OR DRE (PRISM) for

Maintenance & Inspection”, to be actioned by the MAXIMO Maintenance Coordinator and the Eng Data coordinator

PRISM SOFTWARE CHANGES

To ensure that all pre-implementation and post implementation actions have been identified and completed.

The Coordinator will also raise a Technical MoC if required and provide links between the two

To ensure that all soft tags, reserved in eWarehouse as required

and all necessary information is fed back before authorization

The primary technical reviewer and will review against statutory and ETP requirements and engineering practice. Any

changes affecting the P&ID‟s or PFD‟s must be reviewed by a DRE (Process)

Identify any Factory acceptance testing required

Review the test procedures

1/2/3/4

*DRE (DISCIPLINE)

DRE PRISM to review all PRISM software changes

Note: Software MoC that requires maintenance changes will also have a technical MoC and the DRE / maintenance

engineer shall identify maintenance requirement there.

Independent Discipline Technical Review for MoC with a risk level of greater than 2 Will not start the review process until

2/3/4

TA-DISCIPLINE

the DRE has done the initial review

Reviewer

Independent Discipline Technical Review for MoC with a risk level of greater than 2. MoC with impact on process safety

2/3/4

TA (PROCESS)

including emergency response plans or changes affecting the P&ID‟s. Will not start the review process until the DRE has

done the initial review

2/3/4

TA (process safety)

Will review any change that requires a HAZOP

PRISM SOFTWARE CHANGE

1/2/3/4

DRE (PRISM)

PRISM SERVER CHANGES WILL REVIEW

PRISM SOFTWARE CHANGE

1/2/3/4

ENGNEER (PIN)

PRISM SERVER CHANGES WILL REVIEW

DRE (INSTRUMENT/ CONTROL/ SIS)

PRISM SOFTWARE CHANGE

1/2/3/4

WILL REVIEW LDS SERVER (PIN) & CIMIO SERVER (PCN) CHANGES

PRISM SOFTWARE CHANGE

1/2/3/4

APPLICATIONS MANAGER (IT&S)

PIN INFRASTRUCTURE CHANGES & ISIS & D2D SERVER (PIN) CHANGES WILL REVIEW

AzSPU-GEN-PRC-001-A2

Page 38 of 102

MoC Stage/

Risk

Job Function

Responsibility

Role

REGIONAL FIELD DIGITAL

PRISM SOFTWARE CHANGE

1/2/3/4

INFRASTRUCTURE MANAGER (IT&S)

PIN INFRASTRUCTURE CHANGES WILL REVIEW

1/2/3/4

*FACILITY OPS ENGINEER

Approves for execution under control of operations team

1/2/3/4

TL-MODS

Approves Brownfield MoC

3/4

TL-ENG

Confirms that actions raised during the review stage have been addressed.

3/4

AOM

Operating area Approval Risk level 3 and 4 MoC

REGIONAL FIELD DIGITAL

PRISM SOFTWARE CHANGE

1/2/3/4

INFRASTRUCTURE MANAGER (IT&S)

ISIS & D2D SERVER (PIN) CHANGES WILL APPROVE

Approve

DRE SNR (INSTRUMENT/ CONTROL/

1/2/3/4

SIS)

PRISM SOFTWARE CHANGE

WILL APPROVE PRISM / PIN INFRASTRUCTURE/LDS/CIMIO SERVIER CHANGES

3/4

Engineering services manager

Independent Approval Risk level 3 or 4 MoC

3/4

Independent Approval for Risk level 3 and 4 MoC

Approval for Risk level 4 MoC

E&P VP OR CHIEF ENGINEER

Independent Approval for Risk level 4 MoC

Perform offline FAT for complex modifications (as indicated by DRE) any outstanding punchlist items are documented and

attached to the MOC

To ensure that all drawings and formal procedures identified as affected documents within MOC-FRM-009 have been

checked out of Documentum against the MoC

To ensure that there is a work pack and all necessary GOC certificates have been generated, pre-populated with the data

from eWarehouse

To ensure that any TECHNCIAL MoC is “Approved”

1/2/3/4

*COORDINATOR

To confirm SOFT Tags have been reserved and associated design data has been given to the ENG DATA COORDINATOR

All pre Software Load checks have been completed (Program versions, CPU Loading etc)

P&ID Updates have been signed off by Senior Process DRE

re Implement

Rev A Documents are updated to Rev C (post review) and attached to the MOC Folder

Ensure that the test procedure has been approved by DRE

Ensure that the HAZARD identification / RISK assessment process can be accessed from the MoC (if the MoC form isn‟t

used then a link is to be provided

1/2/3/4

ENG DATA COORDINATOR

Ensures that all new eWarehouse tags have been reserved

Ensure that all drawings and formal procedures requested have been checked out of Documentum against the MoC

1/2/3/4

DOCUMENT COORDINATOR

AzSPU-GEN-PRC-001-A2

Page 39 of 102

MoC Stage/

Risk

Job Function

Responsibility

Role

The authorizer is accountable for ensuring that all pre implement actions have been identified and closed out to their

Authorize

1/2/3/4

*FACILITY MANAGER

satisfaction and Authorizes the MoC for software down load and testing controlled by ISSOW

Confirm Down load complete

1/2/3/4

*Engineer (systems) or Engineer (PIN)

Confirm testing successful and attach test records to the MoC

Ensure that all redline drawings have been reviewed and verified as REV R drawings to be actioned by DMT are in the

MoC folder named For Issue Ensure GOC documentation is completed including any post SH1 requirements and that any

outstanding “B punch list items“ have been raised as correctives in MAXIMO

1/2/3/4

*COORDINATOR

Ensure that any eWarehouse required data has been provided for the Master Equipment list, the Eng Data coordinator will

Post implement

need it to be transferred to an MoC folder named Eng Data, Maintenance & Inspection

Confirm that the change performance has been acceptable and if applicable any lessons learnt are issued

1/2/3/4

COORDINATOR

CONFIRM TEMPORARY CHANGE IN PLACE (IF APPLICABLE)

1/2/3/4

COORDINATOR

CONFIRM TEMPORARY CHANGE REMOVED (IF APPLICABLE)

1/2/3/4

*FACILITY OPS ENGINEER

Confirm that operating guidelines procedures have been updated (If applicable)

1/2/3/4

Eng Data coordinator

Ensure that all as built data has been updated in eWarehouse

1/2/3/4

*COORDINATOR

Confirm that all post implementation actions have been completed

Close out

1/2/3/4

*MOC/ EQ TEAM

Confirm that all post implementation actions have been completed as identified in this procedure

Note: At any stage reviewers and approvers may be added to the MoC if considered necessary

Note: Any documents/data updates should be handled under the umbrella of the Technical MoC unless the Process Software MoC is stand alone.

AzSPU-GEN-PRC-001-A2

Page 40 of 102

12.2 Process Software MoC - Templates

The following will be linked directly to the MoC template to assist with the uniform creation of MoC

Document

Document Title

Applies to

Notes

number

PROCESS SOFTWARE MoC

CHANGE IMPACT

PROCESS

This software impact assessment and document check list

ASSESSMENT and

MOC-FRM-009

SOFTWARE

should be completed before authorization

document check list

combined

Note: Installation and equipment installed on site shall be proven using the GOC technical check sheets if the site does not have

a GOC database then the MoC number will be used as the reference number

12.3 Process Software MoC - Risk / Hazard Guidance

Risk Level

Hazard Statement

Managed within the Assets and don‟t required eMoC

 Corrections to error in graphics

 Correction to reports

 Modifying trend sets

 Changing tuning constants (record on separate logs)

Software - Insignificant risk

 Dead bands on alarms and trips

 Operator adjustable deviation alarms

 Coefficients for inferred flow, well flow & DP calculations which are not reported in PRS

 Offline back ups will be managed for each facility by the DRE (INSTRUMENT/ CONTROL/ SIS)

Managed within the Operating area:



MoC with a Risk level 1 (OMS Risk Matrix)



No or little impact on process safety.



No deviation from Company and or international standards.

Software - Risk Level 1 (white)



Includes adding tags or overviews to an operators display, mapping tags to a communications link

or a PLC, changing a display layout or a tag descriptor to match design documents, adjusting a

range to a transmitter, adjusting alarm settings, System Software Upgrades.

 Coefficients for inferred flow, well flow & DP calculations which are reported in PRS



Software change that is part of an approved technical MoC.

Managed within the Operating area but will have independent technical review:



MoC with a Risk level 2 (OMS Risk Matrix)



Minimal impact on process safety.



Involves changes to pressure relief systems Includes adjusting trip settings within rated technical

Software- Risk level 2

limits.

(turquoise)



Removal of trips settings



Includes a change that affects a SIL rated device.



Includes changes to the operating areas PSD, ESD or F&G logic. C&E



Changes that affect the electrical trip discrimination.

Managed within the Operating area but will have independent technical review and independent approval:



MoC with a Risk level 3 (OMS Risk Matrix)

Software- Risk level 3 (blue)



Has significant impact on process safety.



Involves operation of equipment out-with normal operating parameters as identified on the P&ID

or PFD.

Managed within the Operating area but will have independent technical review and risk level 4 approval. -

Technical - Risk level 4 (Purple)

MoC required



MoC with a risk level 4 (OMS Risk Matrix)

Note: This risk associated directly with making the change and should not be confused with MoC priority

AzSPU-GEN-PRC-001-A2

Page 41 of 102

12.4 Process Software MoC - Documentation

At the heart of any change is the control of documents, procedures, software and drawings. Everyone needs to

understand the status of these items at three key stages of change.

Note: it is essential that the Master document data-base a is kept up to date

Stage

Requirement

All documents/drawings subject to change need to be checked out of documentum and a note

added to document data-base stating that the document/ drawing is affected by MoC ref

Verify (Design)

number

Initial design document should include in the document name

- Rev A

Final design documents for review should include in the title - Rev A

Within Documentum a MoC folder within a folder named for review / information should contain

the following

Authorisation (pre-start up)

Construction documents should include in the document name

- Rev C

As Built documents for review should include in the document name - Rev R

Within Documentum a MoC folder within a folder named for issue should contain the following

Final As Built document should include in the document name

- Rev R (with an as-built stamp

Closure (post-start up)

dated and signed)

DCMT will action all documents found in the “for issue folder” and updated the master document

area and action any back drafting that needs to be done.

12.5 Process Software MoC - Key Indicators

 Number of days to close out an MoC after authorization. This indicates how long it takes to get accurate

documents into the system.

 Number of MoCs authorized to start up at any one time - A high number indicates increased risk depending

on the sites ability to manage many simultaneous changes.

 Number of MoCs in review and approve stages - This indicates the loading on the facility teams.

AzSPU-GEN-PRC-001-A2

Page 42 of 102

12.6 Process Software MoC - Process Flow Diagram

Process Software MoC

Use template describe, detail

Identify

scope, justify estimate cost attach

the need

supporting documentation assign

Anyone (if an EQ was used

for change

category, priority and risk level

the EQ responder to initiate

yes

canel

Confirm that the change is

required and all info is included

DRE (INSTRUMENT/

CONTROL / SIS) OR DRE

(ELEC)

modify

Complete the MoC detail ensuring that all effected

ENGINEER

documents are check out from documentum

OTHERS AS REQUIRED

RISK LEVEL 3 OR 4

TL-ENG

Design complete Identify hazards Assess risk

RMS

Confirm risk, category and priority identified

correctly

DRE (DISCIPLINE)

Change accepted and meets

OTHERS AS REQUIRED

standards

RISK LEVEL 2, 3 OR 4

YES

FACILITY OPS ENGINEER

OTHERS AS REQUIRED

Change accepted and all

RISK LEVEL 3 OR 4

issued addressed

TL-ENG

AOM

RISK LEVEL 4

YES

VP & E&P VP

Hazard and risk has been assessed recorded in MoC

Ensure that soft tags have been added to E-warehouse

Ensure that child MOC that are required have been raised and soft tag data added to

documentum folder for Data/ maintenance/ inspection

COORDINATOR

Construction work pack with documents Rev C GOC

Ensure that all construction

documents are uploaded in to

certificates available (including test reviewed test

procedures

documentum for review and

information folder,

Construct/ install/ pre commission GOC SH1 PL1 (A

Confirm all fats and offline test

items) signed off. PSSR completed (check any technical

MoC is cross referenced for appropriate coordination)

complete

Down load software

Ensure that all pre

Commission

FACILITY MANGER

implementation actions

Authorised

yes

Put into service

have been completed

Performance test

Issue any lessons learnt

Confirm down load complete and testing is successful

Ensure that all final document dated and signed are transferred to the for issue folder in

documentum and all as built data is in the data / maintenance / inspection folder

COORDINATOR

ENGINEER (I&C,

SYSTEMS)

Data requirements have been actioned

FACILITY OPS ENGINEER

All document have been upload in the master document area

All post implment

COORDINATOR

actions complete

MOC/EQ TEAM

yes

AzSPU-GEN-PRC-001-A2

Page 43 of 102

13 Specific Guidance - Process Software MoC (DC&I Facilities)

Process Software MoC (DC&I Facilities) covers the management change associated with process software and electrical protection settings as they affect Drilling Facilities.

Note: Although a Process Software MoC can involve minor physical changes these are restricted to modifications “within the system” e.g. internal panel wiring / relays / additions of an hardwired

intertrips where the I/O for both Nodes would be existing / Firmware upgrades. All would be allowed as long as the correct review is completed by the correct reviewers. External connections to

other sub-systems should be considered to be covered under a separate technical MoC

The person who verifies these modifications needs to decide if a Technical MoC needs to be raised to cover these changes as identified by the scope, and should also consider any impact on

ancillary systems such as HVAC or F&G systems which would also required to be considered and as such would need Technical MoC.

Note: Offline back ups will be managed for each facility by the DRE (INSTRUMENT/ CONTROL/ SIS)

13.1 Process Software MoC (DC&I Facilities) - Roles and Responsibilities

THOSE IDENTIFED BY A * ARE A MINIMUM REQUIREMENT FOR RISK LEVEL 1

MoC

Risk

JOB FUNCTION

Responsibility

Stage/Role

Create the eMOC choosing the affected Area and Facility and will choose the Process software template the use of a

template is a mandatory requirement).

*ANYONE

To identify the scope of work (identifies the change which identifies and describes all work necessary to produce the

(if an SEQ requires an MoC then the

change. The scope establishes the tone for the remainder of the planning efforts and therefore should be sufficiently

SEQ responder should initiate the

detailed.).

MoC)

To provide a justification for the work (this section details why the change is required)

Initiate

To provide details of other options considered.

1/2/3/4

Before initiating it is advised to

Where the change is required due to some other business process, Engineering Query, incident report etc, the initiator shall

review the scope with the (DC&I)

reference this process.

DRE (INSTRUMENT/ CONTROL/ SIS)

The initiator is required to identify the Key Change Verifier (DC&I) DRE (instrument/ control /SIS) (KCAD) and identify

(KCAD)

others as required by the procedures

To suggest priority

The SEQ system is used by the drilling area operations teams to formally raise technical questions and should be linked if

available. Operating areas may cancel an MoC that has not been agreed using the EQ or other operating area system.

AzSPU-GEN-PRC-001-A2

Page 44 of 102

MoC

Risk

JOB FUNCTION

Responsibility

Stage/Role

Verify or cancel MoC on behalf of the local operations, confirm the risk level

It should be noted verification should not be given until the person (s) nominated as responsible for the detail design has

complete all the necessary activity to provide to ensure that (note that this may be the DRE (instrument / control/ sis) or

another)

 change is described clearly and adequate to avoid any possible confusion

 The full scope of work is agreed and appropriate documentation is in place

 The justification for the change is clear and adequate

* (DC&I) DRE (INSTRUMENT/

 That all options have been considered and documented in the MoC (as appropriate)

CONTROL/ SIS) KCAD

 That budget is approved and a cost center is identified (as appropriate)

OR (DC&I) ENGINEER (SYSTEMS)

 Identify any post start up reviews that may be required to assess the success of the change (as appropriate)

KCAD

 Identify who is required to execute various stages of the MoC

1/2/3/4

 Priority levels are correct

Or (DC&I) DRE (ELECTRICAL) (KCAD)

Once the design is in place is responsible to identify hazard and assess risk using the appropriate management of risk

for electrical protection changes

process (GRP3.1-001 selection of Hazards Evaluation & Risk assessment techniques) this process should involve the

Verify

appropriate reviews as required, this should be done with appropriate persons around a table. Allowing the key verifier to

confirm or change the risk level (this includes deviations from company or industry standards or practices and any

compliance issues). Details of the risk assessment process used and a summary of the results will be recorded in the risk

statement in the MoC initiation page. Detail record will be attached or linked to the MoC.

Ensure that the hazard identification and risk assessment process is formally recorded and attached or linked to the MoC

for future reference

If the change is to be rejected cancel the MoC giving a reason

Accountable for all identified requirements at this stage of the MoC

* (DC&I) ENGINEER (KCAD)

nominated person or persons

Responsible for the detail design associated with the change and will not verify the MoC until this has been provided.

1/2/3/4

responsible for the detailed design as

Will ensure that all affected drawings are checked out from documentum as required by this procedure.

assigned by the verifier

3/4

(DC&I) RMS

Verify or cancel Risk level 3 or 4 MoC

3/4

(DC&I)TL-ENG (KCAD)

Verify or cancel Risk level 3 or 4 MoC

To hold the MoC by checking the hold tick box the MoC until all information and data is fully available

To manage the MoC through the process ensuring that correct persons are notified, that comments are answered and the

MoC is properly planned, executed and closed out(as part of this will facilitate any interaction between reviews and

designers)

Will ensure that all documents as required by the MoC are properly filed and organized (documents to be sectioned by, for

design(rev A )/ for construction(rev C) /red line (R), red line as-built (R with as built stamp) Note that drawings attached

* (DC&I) Engineer (KCAD)

for information will need to be in an Documentum MoC folder named for review/ information

Coordinator

1/2/3/4

Note that for drawings to be actioned by DCMT will need to be transferred to a documentum MoC folder named for issue.

Note that for data documents (request forms, tdt‟s) will need to be in an Documentum MoC folder Eng Data & Maintenance

& Inspection to be actioned by the MAXIMO Maintenance Coordinator and the Eng Data coordinators

Ensure that all pre-implementation and post implementation actions have been identified and completed.

The Coordinator will also raise a Technical MoC if required

Will ensure that all soft tags, reserved in eWarehouse as required

and all necessary information is fed back before authorization

AzSPU-GEN-PRC-001-A2

Page 45 of 102

MoC

Risk

JOB FUNCTION

Responsibility

Stage/Role

The primary technical reviewer and will review against statutory and ETP requirements and engineering practice. Any

changes affecting the P&ID‟s or PFD‟s must be reviewed by a DRE (Process)

Identify any Factory acceptance testing required

1/2/3/4

* (DC&I) DRE (DISCIPLINE) (KCAD)

Review the test procedures

Note Software MoC that requires maintenance changes will also have a technical MoC and the DRE / maintenance engineer

shall identify maintenance requirement there.

* (DC&I) MAINT

1/2/3/4

Will review any change

SUPERINTENDENT(KCAD)

Reviewer

Independent Discipline Technical Review for MoC with a risk level of greater than 2 Will not start the review process until

2/3/4

TA-DISCIPLINE

the DRE has done the initial review

Independent Discipline Technical Review for MoC with a risk level of greater than 2. MoC with impact on process safety

2/3/4

TA (PROCESS)

including emergency response plans or changes affecting the P&ID‟s. Will not start the review process until the DRE has

done the initial review

1/2/3/4

TA (process safety)

Will review any change that requires a HAZOP

1/2

* (DC&I) WSL SNR

Confirms that actions raised during the review stage have been addressed.

3/4

(DC&I) TL-ENG (KCAD)

Operating area Approval Risk level 3 or 4 MoC

3/4

(DC&I) WTL

Operating area Approval Risk level 3 or 4 MoC

3/4

(DC&I) RMTL

Operating area Approval Risk level 3 or 4 MoC

Approve

3/4

Engineering services manager

Independent Approval for Risk level 3 or 4 MoC

3/4

Independent Approval for Risk level 3 or 4 MoC

Independent Approval for Risk level 4 MoC

E&P VP OR CHIEF ENGINEER

Independent Approval for Risk level 4 MoC

Perform offline FAT for complex modifications (as indicated by DRE)

Ensure that all drawings and formal procedures requested have been checked out of documentum against the MoC

Ensure that there is a work pack with all necessary construction documents, GOC certificates have been generated pre-

populated with the data from eWarehouse

Ensure that any TECHNCIAL changes have been captured by a TECHNICAL MoC and the MoC link attached to the MoC

Confirms SOFT Tags have been reserved and associated design data has been given to the ENG DATA COORDINATOR

All pre SOFTWARE LOAD checks and GOC documentation has been completed and the SH1 form with punch lists have been

signed and that there are no out standing

“A punch list items” on the punch list

1/2/3/4

*COORDINATOR

Note: after software load the system testing should be documented on a plant performance certificate (with any detailed

Pre-implement

testing documentation attached)

Ensure that affected drawings have been marked up as red lined drawings stamped AS BUILT dated/ signed / Job Title

Ensure that all supplementary MoC have Post implement close out actions attached

Confirm that all Red lined “ As built “”REV R documents in the Documentum MoC folder for issue

Ensure that the HAZARD identification / RISK assessment process can be accessed from the MoC (if the MoC form isn‟t

used then a link is to be provided)

1/2/3/4

*(DC&I) Engineer (systems) (KCAD)

Confirm that all operating guidelines procedures have been updated

1/2/3/4

ENG DATA COORDINATOR

Ensures that all EWarehouse data has been supplied and uploaded in to eWarehouse

AzSPU-GEN-PRC-001-A2

Page 46 of 102

MoC

Risk

JOB FUNCTION

Responsibility

Stage/Role

Ensure that all drawings and formal procedures requested have been checked out of documentum against the MoC

1/2/3/4

DOCUMENT COORDINATOR

Confirm that all Red lined documents and procedures are updated in Documentum

*(DC&I) RIG SUPERINTENDENT

The authorizer is accountable for ensuring that all pre implement actions have been identified and closed out to their

Authorize

1/2/3/4

(KCAD)

satisfaction and Authorizes the MoC for software down load and testing controlled by ISSOW

1/2/3/4

*(DC&I) Engineer (systems) KCAD

Confirm Down load complete

1/2/3/4

*(DC&I) Engineer (systems) KCAD)

Confirm testing successful and attach test records to the MoC

Ensure that all redline drawings have been reviewed and verified as REV R drawings to be actioned by DCMT are in the

MoC folder named For Issue

Ensure GOC documentation is completed including any post SH1 requirements and that any outstanding “B punch list

1/2/3/4

*COORDINATOR

items“ have been raised as correctives in MAXIMO

Ensure that any eWarehouse required data has been provided for the Master Equipment list, the Eng Data coordinators will

Post implement

need it to be transferred to an MoC folder named Eng Data, Maintenance & Inspection

Confirm that the change performance has been acceptable and if applicable any lessons learnt are issued

1/2/3/4

COORDINATOR

CONFIRM TEMPORARY CHANGE IN PLACE (IF APPLICABLE)

1/2/3/4

COORDINATOR

CONFIRM TEMPORARY CHANGE REMOVED (IF APPLICABLE)

Confirm that all “as built- final “ documents and procedures as found in the for issue folder updated in Documentum main

1/2/3/4

DOCUMENT Coordinator

area and when back drafting is completed then rev Z drawings will also be upload at the next revision

1/2/3/4

Eng Data coordinator

Ensure that all as built data has been updated in EWarehouse

1/2/3/4

*COORDINATOR

Confirm that all post implementation actions have been completed

Close out

1/2/3/4

*(DC&I) RMTL

Confirm that the Drilling operator has finished this modification to his satisfaction on behalf of BP.

1/2/3/4

*MOC/ EQ TEAM

Confirm that all post implementation actions have been completed as identified in this procedure

Note: At any stage reviewers and approvers may be added to the MoC if considered necessary

Note: The KCAD Minor Mod Workpack shall include all the supporting documentation relative to the change, such as: Control Narrative, Logic Diagrams, Test Procedures and GoC check sheets.

The MMWpk will be an attachment to the MoC.

AzSPU-GEN-PRC-001-A2

Page 47 of 102

13.2 Process Software MoC (DC&I Facilities) - Templates

The following will be linked directly to the MoC template to assist with the uniform creation of MoC

Document

Document Title

Applies to

Notes

number

PROCESS SOFTWARE MoC

CHANGE IMPACT

PROCESS

This software impact assessment and document check

MOC-FRM-009

ASSESSMENT and document

SOFTWARE

list should be completed before authorization

check list combined

Note: Installation and equipment installed on site shall be proven using the GOC technical check sheets if the site does not have

a GOC database then the MoC number will be used as the reference number

13.3 Process Software MoC (DC&I Facilities) - Risk / Hazard Guidance

Risk Level

Hazard Statement

Managed within the Assets and don‟t required eMoC

 Corrections to error in graphics

 Correction to reports

 Modifying trend sets

 Changing tuning constants (record on separate logs)

Software - Insignificant risk

 Dead bands on alarms and trips

 Operator adjustable deviation alarms

 Coefficients for inferred flow, well flow & DP calculations which are NOT reported in PRS

 Offline back ups will be managed for each facility by the DRE (INSTRUMENT/ CONTROL/

SIS)

Managed within the Operating area:

 MoC with a Risk level 1 (OMS Risk Matrix)

 No or little impact on process safety.

 No deviation from Company and or international standards.

Software - Risk Level 1

 Includes adding tags or overviews to an operators display, mapping tags to a

(white)

communications link or a PLC, changing a display layout or a tag descriptor to match

design documents, adjusting a range to a transmitter, adjusting alarm settings, System

Software Upgrades.

 Software change that is part of an approved technical MoC.

Managed within the Operating area but will have independent technical review:

 MoC with a Risk level 2 (OMS Risk Matrix)

 Minimal impact on process safety.

 Involves changes to pressure relief systems Includes adjusting trip settings within rated

Software- Risk level 2

technical limits.

(turquoise)

 Removal of trips settings

 Includes a change that affects a SIL rated device.

 Includes changes to the operating areas PSD, ESD or F&G logic. C&E

 Changes that affect the electrical trip discrimination.

Managed within the Operating area but will have independent technical review and independent

approval:

 MoC with a Risk level 3 (OMS Risk Matrix)

 Involves changes to the well control system.

Software- Risk level 3 (blue)

 Has significant impact on process safety.

 Involves operation of equipment out-with normal operating parameters as identified on

the P&ID or PFD.

Managed within the Operating area but will have independent technical review and risk level 4

Technical - Risk level 4

approval. - MoC required

(purple)

 MoC with a risk level 4 (OMS Risk Matrix)

Note: This risk associated directly with making the change and should not be confused with MoC priority

AzSPU-GEN-PRC-001-A2

Page 48 of 102

13.4 Process Software MoC (DC&I Facilities) - Documentation

At the heart of any change is the control of documents, procedures, software and drawings. Everyone needs to

understand the status of these items at three key stages of change.

Note: it is essential that the Master document data-base a is kept up to date

Stage

Requirement

All documents/drawings subject to change need to be checked out of Documentum and a note

added to document data-base stating that the document/ drawing is affected by MoC ref

Verify (Design)

number

Initial design document should include in the document name

- Rev A

Final design documents for review should include in the document name

- Rev A

Within Documentum a MoC folder within a folder named for review / information should contain

the following

Authorisation (pre-start up)

Construction documents should include in the document name

- Rev C

As Built documents for review should include in the title - Rev R

Within Documentum a MoC folder within a folder named for issue should contain the following

Final As Built document should include in the document name

- Rev R (with an As built stamp

Closure (post-start up)

dated and signed)

DCMT will action all documents found in the “for issue folder” and updated the master document

area and action any back drafting that needs to be done.

13.5 Process Software MoC (DC&I Facilities) - Key Indicators

 Number of days to close out a MoC after start up. This indicates how long it takes to get accurate

documents into the system.

 Number of MoC authorized to start up at any one time - A high number indicates increased risk depending

on the sites ability to manage many simultaneous changes.

 Number of MoC in review and approve stages - This indicates the loading on the facility teams.

AzSPU-GEN-PRC-001-A2

Page 49 of 102

13.6 Process Software MoC (DC&I Facilities) - Process Flow Diagram

Process Software MoC (DC&I facilities)

Use template describe, detail

Identify

scope, justify estimate cost attach

the need

supporting documentation assign

Anyone (if a SEQ was used

for change

category, priority and risk level

the SEQ responder to initiate

yes

canel

Confirm that the change is

required and all info is included

(DC&I) DRE (INSTRUMENT/

CONTROL / SIS)(KCAD) OR

(DC&I) DRE (ELEC)

modify

Complete the MoC detail ensuring that all effected

(DC&I) ENGINEER (KCAD)

documents are check out from documentum

OTHERS AS REQUIRED

RISK LEVEL 3 OR 4

(DC&I) TL-ENG (KCAD)

Design complete Identify hazards Assess risk

(DC&I) RMS

Confirm risk, category and priority identified

correctly

(DC&I) DRE (DISCIPLINE)

(KCAD)

(DC&I) MAINT

Change accepted and meets

SUPERVISOR (KCAD)

standards

OTHERS AS REQUIRED

RISK LEVEL 2, 3 OR 4

YES

(DC&I) WSL SNR

OTHERS AS REQUIRED

Change accepted and all

RISK LEVEL 3 OR 4

issued addressed

(DC&I) TL-ENG (KCAD)

(DC&I) WTL, (DC&I) RMTL

YES

RISK LEVEL 4

VP & E&P VP

Hazard and risk has been assessed recorded in MoC

Ensure that soft tags have been added to E-warehouse

Ensure that child MOC that are required have been raised and soft tag data added to

documentum folder for Data/ maintenance/ inspection

COORDINATOR

(DC&I) ENGINEER

Ensure that all construction

(SYSTEMS)( KCAD)

Construction work pack with documents Rev C GOC

documents have been as built rev

certificates available (including test reviewed test

R are scanned and uploaded in to

procedures

documentum for review and

Construct/ install/ pre commission GOC SH1 PL1 (A

information folder,

items) signed off. PSSR completed (check any technical

Confirm all fats and offline test

MoC is cross referenced for appropriate coordination)

complete

Down load software

Ensure that all pre

Commission

(DC&I) RIG

implementation actions

Authorised

yes

Put into service

SUPERINTENDENT (KCAD)

have been completed

Performance test

Issue any lessons learnt

Confirm down load complete and testing is successful

Ensure that all final document dated and signed are transferred to the for issue folder in

documentum and all as built data is in the data / maintenance / inspection folder

COORDINATOR

(DC&I) ENGINEER

(SYSTEMS)( KCAD)

Data requirements have been actioned

All document have been upload in the master document area ( and back drafting arranged)

COORDINATOR

All post implment

(DC&I) RMTL

actions complete

MOC/EQ TEAM

yes

AzSPU-GEN-PRC-001-A2

Page 50 of 102

14 Specific Guidance - Chemical MoC

A chemical change is defined as one of the following:

 Introduction of a new chemical where no chemical is currently in use.

 Removal of a chemical in use.

 Introduction of any fluid into the production stream not related to production (e.g. commission fluids, drilling

fluids etc)

 DC&I drilling fluids inclusion into the topsides will be covered by eMOC. However this will be managed as

follows:

A single temporary (annual refresh) eMOC will be put in place to cover all typical fluid flow-back

scenarios, and topsides safeguards to be in place. The individual facility and drilling operating

procedures will be updated as a result to reflect the actions to be taken in each scenario.

A hazard assessment will be conducted put in place a “Rule Set” for typical drilling fluid

flow-backs

This assessment will be refreshed annually along with the temporary MoC

Any fluid flowback not covered by the generic eMOC will be subjected to a separate eMOC prior to

the operation being conducted. The rule set for when a separate eMOC is needed can be defined,

but will be along the lines of:

New operation

New fluids

Existing fluid, but beyond defined limits (of rate/composition/total volume, etc)

 Replacing an existing chemical with a new one.

 Changing the composition of an existing chemical, including changes in concentration or generic chemistry.

 Change of use, where an existing chemical is to be used for a different duty.

 Change in injection rates outside the previously assessed range. This applies to significant changes (>20%)

and does not include minor adjustments as part of ongoing optimization.

Although the requirements are the same, a chemical trial will be implemented as a temporary e-MoC

Note: The Chemical MoC will be raised from the point of injection site. TA will ensure that reviewers (Facility Ops Engineers)

from the all affected sites (it there are any) such as Sangachal Terminal; BTC; WREP; SCP are added as needed.

Note: Although a chemical MoC can involve minor physical changes, it is not intended to replace the Technical MoC if permanent

hardware changes are required. The BP production chemist who verifies these modifications needs to decide if a Technical MoC

needs to be raised to cover these hardware changes such as changing an injection location.

Note: Any changes to Flow Assurance and Production Chemistry management strategies that do not involve a chemical change

(e.g. pigging frequency for wax management; producing under different operational conditions for hydrate management) will be

covered by Documentation MoC or Maintenance and Inspection MoC).

Note: Flow Assurance/Production Chemistry Management strategies will be covered by AzSPU Site Technical Practices and any

changes to these will be controlled by Documentation MoC.

Note: Lab procedures will be controlled by Documentation MoC.

AzSPU-GEN-PRC-001-A2

Page 51 of 102

14.1 Chemical MoC - Roles and Responsibilities

THOSE IDENTIFED BY A * ARE A MINIMUM REQUIREMENT FOR RISK LEVEL 1

MoC

Risk

Job Function

Responsibility

Stage/Role

Create the eMOC choosing the affected Area and Facility and will choose the Chemical template the use of a template is a mandatory

requirement).

Will identify the scope of work (identifies the change which identifies and describes all work necessary to produce the change. The scope

establishes the tone for the remainder of the planning efforts and therefore should be sufficiently detailed.).

*ANYONE

Will provide a justification for the work (this section details why the change is required)

(if a EQ requires an

Will provide details of other options considered.

Initiate

2/3/4

MoC then the EQ

Where the change is required due to some other business process, Engineering Query, incident report etc, the initiator shall reference this

responder should

process.

initiate the MoC)

The initiator is required to identify the Key Change Verifier DRE (production chemist) and identify others as required by the procedures

Will suggest priority

The EQ system is used by the operating area operations teams to formally raise technical questions and should be linked if available.

Operating areas may cancel an MoC that has not been agreed using the EQ or other operating area system.

AzSPU-GEN-PRC-001-A2

Page 52 of 102

MoC

Risk

Job Function

Responsibility

Stage/Role

To verify or cancel MoC on behalf of the local operations

*FACILITY OPS

2/3/4

Confirm level of priority using the prioritization tool based on the anticipated benefit of the change

ENGINEER

Will cancel the MoC giving a reason if the change is to be rejected

To verify or cancel MoC on behalf of the local operations, confirm the risk level

It should be noted verification should not be given until the detail design has completed, the verifier will ensure that

 The change is described clearly and adequate to avoid any possible confusion

 The full scope of work is agreed and appropriate documentation is in place

 The justification for the change is clear and adequate

 That all options have been considered and documented in the MoC (as appropriate)

 That budget is approved and a cost center is identified (as appropriate)

Verify

 Identify any post start up reviews that may be required to assess the success of the change (as appropriate)

 Identify who is required to execute various stages of the MoC

*DRE (PRODUCTION

 Priority levels are correct

2/3/4

CHEMIST)

Once the design is in place is responsible to identify hazard and assess risk using the appropriate management of risk process (GRP3.1-001

selection of Hazards Evaluation & Risk assessment techniques) this process should involve the appropriate reviews as required, this should

be done with appropriate persons around a table. Allowing the key verifier to confirm or change the risk level (this includes deviations

from company or industry standards or practices and any compliance issues). Details of the risk assessment process used and a summary

of the results will be recorded in the risk statement in the MoC initiation page. Detail record will be attached or linked to the MoC

To ensure that the hazard identification and risk assessment process is formally recorded and attached or linked to the MoC for future

reference

If the change is to be rejected cancel the MoC giving a reason

Accountable for all identified requirements at this stage of the MoC

AzSPU-GEN-PRC-001-A2

Page 53 of 102

MoC

Risk

Job Function

Responsibility

Stage/Role

To hold the MoC by checking the hold tick box the MoC until all information and data is fully available

To manage the MoC through the process ensuring that correct persons are notified, that comments are answered and the MoC is properly

planned, executed and closed out (as part of this will facilitate any interaction between reviews and designers)

To ensure that all documents as required by the MoC are properly filed and organized (documents to be sectioned by, for design(rev A )/

for construction(rev C) /red line (R), red line as-built (R with as built stamp) Note that drawings attached for information will need to be in

*DRE (PRODUCTION

Coordinator

2/3/4

an Documentum MoC folder named for review/ information

CHEMIST)

Note that for drawings to be actioned by DCMT will need to be transferred to an MoC folder named for issue.

To ensure that all pre-implementation and post implementation actions have been identified and completed.

The Coordinator will also raise Technical MoC as required to support the Chemical MoC (note that eWarehouse / maintenance and

document changes that form part of the technical MoC do not require additional MoC to be raised)

To ensure that the any weight changes associated with platform loading are identified recorded and submitted. Governing procedures

SHDU-ENG-PRC-001 and UNIF ENG PRC -142

*TA-(PRODUCTION

2/3/4

Review the change giving reasons for any rejection

CHEMISTRY)

*FACILITY OPS

2/3/4

Review the change giving reasons for any rejection

SUPERVISOR

*ENVIROMENTAL

2/3/4

Review the change giving reasons for any rejection with respect to the environmental impact

ADVISOR

2/3/4

*HSEA

Review the change giving reasons for any rejection

*FACILITY OPS ENG

2/3/4

Must review all changes affecting Oil or Gas export route (i.e. SCP BTC WREP)

(EXPORT)

2/3/4

*DRE (PROCESS)

Review the change giving reasons for any rejection

2/3/4

*TA (PROCESS)

Review the change giving reasons for any rejection

Will communicate on-site chemical changes to the HSE Compliance Advisors through completion of the first section of the HSE Compliance

*H&S TL / ENV &

Reviewer

2/3/4

Form and will update the facility APS list (if relevant) Will add a pre-implementation action for the HSE Compliance Advisor to determine

COMPLIANCE TL

and advise any compliance implications.

Review the construction pack and the resource and scheduling that have been identified as required by the maximo work order to support

2/3/4

MTL

this activity (if applicable)

2/3/4

TA (PROCESS safety)

To review if a HAZOP was required

2/3/4

TA-(CORROSION)

Review the change giving reasons for any rejection

2/3/4

TA-(INSPECTION)

Review the change giving reasons for any rejection

DOWN STREAM

2/3/4

FACILITY OPS

Review the change giving reasons for any rejection

ENGINEERS

Review the change giving reasons for any rejection

2/3/4

DRE (DISCIPLINE)

Platform Weight changes must be reviewed by the DRE(structures)

2/3/4

OMA

Review where the change has a Marine Element (Bulk transport by vessel)

AzSPU-GEN-PRC-001-A2

Page 54 of 102

MoC

Risk

Job Function

Responsibility

Stage/Role

2/3/4

Where the change has a Marine Element

2/3/4

*FACILITY MANAGER

APPROVE the change giving reasons for any rejection

3/4

AOM

APPROVE the change giving reasons for any rejection

3/4

APPROVE the change giving reasons for any rejection

Approve

Engineering services

3/4

Independent Approval for Risk level 3 or 4 MoC

manager

APPROVE the change giving reasons for any rejection

E&P VP OR CHIEF

APPROVE the change giving reasons for any rejection

ENGINEER

To ensure that all drawings and formal procedures requested have been checked out of documentum against the MoC

To ensure that there is a work pack

To ensure that any TECHNCIAL changes have been captured by a Technical MoC and the MoC link attached to the MoC

To ensure that affected documents have been marked up as redlined drawings, stamped AS BUILT dated/ signed / Job Title

2/3/4

*COORDINATOR

To ensure that all supplementary MoC have Post Implement close out actions attached

Pre implement

To confirm that all Red lined “As built ” REV R documents has been placed in the Documentum MoC folder for issue

To ensure that the HAZARD identification / RISK assessment process can be accessed from the MoC (if the MoC form isn‟t used then a link

is to be provided

To review the operational changes communicated in the HSE Compliance Form and facilitate the process to determine whether there are

HSE COMPLIANCE

1/2/3/4

any compliance implications, this may lead to update of Compliance Task Manager (CTM) tasks.

ADVISOR

To ensure that all pre-implementation actions have been identified and completed. Authorize MoC for startup on site.

*FACILITY OPS

Authorize

2/3/4

Site will use the normal Control of work systems for the work done on site

ENGINEER

Ensure that performance is monitored and reported

2/3/4

*COORDINATOR

Confirm that the change performance has been acceptable and if applicable any lessons learnt are issued

*DOCUMENT

Confirm that all “as built/final “ documents and procedures as found in the for issue folder updated in Documentum main area and when

2/3/4

COORDINATOR

back drafting is completed then rev Z drawings will also be upload at the next revision

Post Implement

1/2/3/4

COORDINATOR

Confirm temporary change in place (only applicable to temporary changes)

1/2/3/4

COORDINATOR

Confirm temporary change removed (only applicable to temporary changes)

2/3/4

OMA

To ensure that all changes required by the Marine Element have been closed out

To ensure that all post-implement actions have been completed and As built documents have been identified and that the production

2/3/4

*COORDINATOR

Close out

chemicals register has been updated (UNIF-ENG-REG-021)

1/2/3/4

*MOC/ EQ TEAM

Confirm that all post implementation actions have been completed as identified in this procedure

Note: At any stage reviewers approvers post and pre implementation actions may be added to the MoC, if considered necessary

Note: All weight changes offshore in excess of 100kg should be recorded on the weight change form and submitted to the custodian of the weight change register: - Governing procedures SHDU-

ENG-PRC-001 and UNIF ENG PRC -142

Note: Installation and equipment installed on site shall be proven using the GOC technical check sheets if the site does not have a GOC database then the MoC number will be used as the

reference number

AzSPU-GEN-PRC-001-A2

Page 55 of 102

14.2 Chemical MoC - Templates

The following will be linked directly to the MoC template to assist with the uniform creation of MoC

Document number

Document Title

Applies to

Notes

CHEMICAL MoC

The chemical MoC check list should be completed before

MOC-FRM-011

CHEMICAL

CHECK LIST

the MoC is closed out

Used to communicate on-site operational changes to the

HSSE COMPLIANCE

TECHNICAL,

AzSPU HSE Compliance Team so that they can determine

MOC-FRM-025

FORM

CHEMICAL, DC&I

HSE compliance implications. Must be completed before

close out.

PRODUCTION

UNIF-ENG- REG-021

CHEMICAL

To be updated before chemical MoC is closed out

CHEMICAL REGISTER

WEIGHT CHANGE

TECHNICAL,

To be completed for all weight changes on the platforms

UNIF-ENG-WCS-001

SHEET

CHEMICAL

in excess of 100kG

14.3 Chemical MoC - Risk / Hazard Guidance

Risk Level

Hazard Statement

No MoC required

Chemical- insignificant risk

Managed within the Operating area - technical MoC required

Chemical- Risk level 1

 MoC with a risk level 1 (OMS Risk Matrix)

(white)

Managed within the Operating area will have independent technical review

 MoC with a risk level 2 (OMS Risk Matrix)

 Involves the introduction (includes changes in concentration, generic chemistry)/

Chemical- Risk level 2

removal of a chemical.

(turquoise)

 Involves increasing/ reducing the injection rate (>20%) of an existing chemical.

 Involves using an existing chemical for a new duty. Will have minimal adverse impact

on process safety and technical integrity.

Managed within the Operating area but will have independent technical review and risk level 3

Chemical- Risk level 3 (blue)

approval. - MoC required

 MoC with a risk level 3 (OMS Risk Matrix)

Managed within the Operating area but will have independent technical review and risk level 4

Technical - Risk level 4 -

approval. - MoC required

(Purple)

 MoC with a risk level 4 (OMS Risk Matrix)

Note: This risk associated directly with making the change and should not be confused with MoC priority

14.4 Chemical MoC - Documentation

At the heart of any change is the control of documents, procedures and drawings. Everyone needs to understand

the status of these items at three key stages of change.

Note Documentum is the Master document data-base and it is therefore essential that this data-base is kept up to date

Stage

Requirement

All documents/drawings subject to change need to be checked out of Documentum and a note

added to document data-base stating that the document/ drawing is affected by MoC ref

Verify (Design)

number

Initial design document should include in the document name

- Rev A

Final design documents for review should include in the title - Rev A

Within Documentum a MoC folder within a folder named for review / information should contain

the following

Construction documents should include in the document name

- Rev C

Authorisation (pre-start up)

As Built documents for review should include in the title - Rev R

Authorization for Chemical Change Check List and HSSE Compliance Sheet to be completed pre

start up

AzSPU-GEN-PRC-001-A2

Page 56 of 102

Stage

Requirement

Within Documentum a MoC folder within a folder named for issue should contain the following

Final As Built document should include in the document name

- Rev R (with an As built stamp

dated and signed)

DCMT will action all documents found in the “for issue folder” and updated the master document

area and action any back drafting that needs to be done.

Lessons learned are documented.

COSHH is updated if applicable.

Closure (post-start up)

Ops Procedures is updated if applicable.

Inspection Strategy is updated if applicable.

Corrosion Management Strategy is updated if applicable.

Production Chemicals Register is updated following any chemical change.

Copies of MSDS and risk assessment documents will be distributed to: storage area; point of

use; site medical staff; site HSSE representative; facility library; facility laboratory and supplied

during transportation.

14.5 Chemical MoC - Key Indicators

 Number of days to close out an MoC after authorization. This indicates how long it takes to get accurate

documents into the system.

 Number of MoCs authorized to start up at any one time - A high number indicates increased risk depending

on the sites ability to manage many simultaneous changes.

 Number of MoCs in review and approve stages - This indicates the loading on the facility teams.

AzSPU-GEN-PRC-001-A2

Page 57 of 102

14.6 Chemical MoC - Process Flow Diagram

Chemical MoC

Use template describe, detail

Identify

scope, justify estimate cost attach

the need

supporting documentation assign

Anyone (if a EQ was used the EQ

for change

category, priority and risk level

responder to initiate

yes

canel

Confirm that the change is

required and all info is included

FACILITY OPS ENGINEER

DRE (PRODUCTION CHEMIST)

modify

Complete the MoC detail ensuring that all effected

documents are check out from documentum

Design complete Identify hazards Assess risk

Confirm risk, category and priority identified

correctly

TA (PRODUCTION CHEMISTRY),

FACILITY OPS ENGINEER

ENVIRONMENTAL ADVISOR,

Change accepted and meets

H&S TL / Env & Compliance

standards

TL FACILITY OPS ENG

(EXPORT), DRE( PROCESS,

TA(PROCESS, , OTHERS AS

YES

REQUIRED

FACILITY MANGER

OTHERS AS REQUIRED

Change accepted and all

RISK LEVEL 3 OR 4

issued addressed

AOM, EA

RISK LEVEL 4

VP, E&P VP

YES

Hazard and risk has been assessed recorded in MoC

Ensure technical MOC that are required have been raised that weight changes reported.

COORDINATOR

HSE Compliance Advisor

Ensure all documents are as built

OTHERS

Construction work pack with documents Rev C GOC

certificates available

rev R are scanned and uploaded

PSSR completed (check that any technical MoC are

in to documentum for review and

complete if appropriate)

information folder,

Commission

Ensure that all pre

Put into service

FACILITY OPS ENGINEER

implementation actions

Authorised

yes

Performance test

have been completed

Issue any lessons learnt

Ensure that all final document dated and signed are transferred to the for issue folder in

documentum

COORNINATOR

DOCUMENT COORDINATOR

ENG HSE DATA CONTROLLER

ACET DATA CONTROL

MAXIMO MAINTENANCE

All documents have been upload in the master document area

COORDINATOR

All post implment

COORDINATOR

actions complete

MOC/EQ TEAM

yes

AzSPU-GEN-PRC-001-A2

Page 58 of 102

15 Specific Guidance - Maintenance & Inspection MoC

A Maintenance MoC will be required for:

 Creation of New PM/ change of Frequency/ change of Job Plan or routestop Job Plan/change of Location or

Route Location/ Deferral or Suspension of Preventive Maintenance (PM) records in MAXIMO

Note1: If a tag has been decommissioned then suspension of related PM/WO records will be covered by the

Technical MOC. Maintenance MoC will be issued only if there is no Technical MOC.

Note2: If a PM is to be suspended then its live work orders must be cancelled in MAXIMO by adding MoC

number as a reference to the work order and attaching the list of work orders to the MOC

 Cancellation/Change of Target Completion Date (Deferral) of SCE Work Orders.

Note1: Corrective (CO) and Breakdown (BR) SCE work orders will require MoC only if they have already

Approved. SCE PM and PdM work orders will need MoC regardless of their statuses

Note2: Principally Target Dates of non-SCE Work Orders should not be changed and they should be seen as

backlog. Cancellation or deferral of significant amount of non-SCE work orders resulted by the operational

circumstances should be captured through a Maintenance MOC.

 Creation of a new Job Plan/Change to the Master Job Plan details

 Creation / Modification of a Planned Maintenance Routine (PMR or work scope document) in MAXIMO and

Document Management System (DMS)

 Creation of the new/modification of the existing Location and Equipment records in eWarehouse and

MAXIMO will be covered through respective Technical MOCs. If no Technical MoC exists then a Maintenance

MoC will be raised to capture amendment requests for the existing records.

A Maintenance MoC will not be required for updating of the following data fields

 Changes to Location/Equipment Descriptions, Location hierarchy-Parent/Child relationships, Location Priority,

GL Account

 Changes to Job Plan Descriptions, Supervisor, Materials, Durations, Resources - not applicable to master Job

Plan

 If a Technical MoC requires creation of a new/amendment of the existing maintenance subjects, like PM, JP,

PMR e.q. then Pre and Post Implementation stages of the same MoC will cover these activities. Coordinator

of the Technical MoC will identify Responsible people for these actions from “R&M” and “System and Tools”

teams. For RBI activities Inspection Engineers should be contacted. No Maintenance MoC will be initiated in

this case.

AzSPU-GEN-PRC-001-A2

Page 59 of 102

15.1 Maintenance & Inspection MoC - Roles and Responsibilities

MoC Stage /

Risk

Job Function

Responsibility

Role

To initiate the Maintenance e-MoC providing description and justification and any other information required by the change.

Initiate

1/2/3/4

ANYONE AUTHORIZED

The attached maintenance forms identify the information required maintenance change

To identify the minimum requirement for verification stage based on the below categories

Minimum requirement for Maintenance PM/JP/PMR modifications.

ME must ensure that requests are inline with Maintenance Strategy requirements. Any exclusion to the strategy is to be captured

1/2/3/4

Maintenance Engineer(ME)

for the next review of strategy documents. Standardization is to be followed as much as possible

Verifies the MOC, identifies applicable priority and risk levels, assigns responsible person for each stage of the MOC. Ensures that

necessary data is available and correct

Minimum requirement for

 Inspection (RBI) PM/JP/PMR modifications

 Deferral of Mechanical Equipment Inspection/Corrosion Activities (see Table1.4, Risk Level 2 requirements)

1/2/3/4

Area Inspection Authority

Verifies the MOC, identifies applicable priority and risk levels, assigns responsible person for each stage of the MOC. Ensures that

necessary data is available and correct

Verify

Minimum requirement for Adding/Removing Tags.

1/2/3/4

Data Coordinator

Covers updates to location / equipment details, SCE, EX, failure class, location status

If the request covers maintainable tags then ME must be added as the second verifier

Minimum requirement for Deferral/Cancellation of SCE WOs.

Facility must confirm that request for deferral/cancellation of SCE work orders is valid

1/2/3/4

Facility Ops Engineer/OOE

Verifies the MOC, identifies applicable priority and risk levels. The coordinator assigns necessary person for each stage. If the

request needs changes to Maintenance Strategy then ME must be added as the second verifier.

1/2/3/4

DRE (mechanical)

Responsible for completion of PSV deferral forms

MAXIMO maintenance coordinator will coordinate any maintenance MoC except SCE WO Cancellations and Deferrals

Maintenance Coordinator

Site Scheduler will coordinate Deferral and cancellation of SCE WO

Coordinator

1/2/3/4

or Site Scheduler

The coordinator will ensure that the provided data is enough to processes the MoC, if not then the coordinator is fully responsible

for adding names of those who can provide the required input

Minimum requirement for all maintenance strategy related MOCs and SCE Deferrals

1/2/3/4

Maintenance Engineer(ME)

Reviews change requests as per Maintenance Strategy and collects necessary justification of the SCE Deferrals, involve TAs if

required. Please note that by default all SCE deferrals will be risk ranked blue (high risk).

Provides assistance to Maintenance Engineer and TA wherever required

1/2/3/4

DRE (Discipline)

Changes affecting subsea installations must be reviewed the DRE (offshore pipelines) or DRE (subsea) including corrosion

Reviewer

protection systems and pigging

Minimum requirement for Deferral/Cancellation of SCE Inspection(RBI) WOs

To review any change to inspection /corrosion management Failure Class fields, Location Status, Deferral and Cancellation of

1/2/3/4

AIA

inspection/ corrosion management WOs, suspension of PM Creation of new PM/ JP/ PMR changes to existing PM & Route locations,

frequency, CFW, PMR Content

AzSPU-GEN-PRC-001-A2

Page 60 of 102

MoC Stage /

Risk

Job Function

Responsibility

Role

1/2/3/4

TL-SO

To review any change to subsea equipment maintenance

Independent Technical Review for Deferral and Cancellation of inspection WO (for risk level 2 (turquoise) and above) changes

2/3/4

TA-INPECTION

associated with static mechanical equipment i.e. piping, vessels, etc.

TA will not start the review process until the AIA has done the initial review

Independent Technical Review for risk level 2 (turquoise and above) changes, i.e. Deferral and Cancellation of SCE WOs,

2/3/4

TA-DISCIPLINE

suspension of PM Creation of new PM/ JP/ PMR, changes to existing PM & Route locations, frequency, CFW, PMR Content, changes

to SCE flag. TA will not start the review process until the DRE (discipline) has done the initial review.

1/2/3/4

Coordinator

Approve Maintenance change ( except SCE deferrals and cancellation)

2/3/4

FACILITY MANAGER

Minimum Requirement: Approve deferrals of SCE /or inspection/ corrosion management WO

3/4

AOM or SOM for subsea

Approve second deferrals of SCE /or inspection/ corrosion management WO

Approve

3/4

Engineering services manager

Approve second deferrals of SCE /or inspection/ corrosion management WO

3/4

Approve second deferrals of SCE /or inspection/ corrosion management WO

Approve third deferrals of SCE /or inspection/ corrosion management WO

Authorize

1/2/3/4

Coordinator

Authorize for execution.

Area scheduler changes target completion dates of SCE work orders and Start(due) dates of PMs if required, cancels SCE WOs and

suspends their PMs if required

Maximo Maintenance Coordinator updates MAXIMO with any changes related to PM/JP/PMRs

1/2/3/4

Coordinator

Close out

Data Coordinator changes location/ equipment details in eWarehouse / MAXIMO

To ensure that any final as built documentation is updated in documentum

To ensure that all post implementation actions have been completed

1/2/3/4

MOC/ EQ TEAM

Confirm that all post implementation actions have been completed as identified in this procedure

Note: At any stage reviewers and approvers may be added to the MoC if considered necessary

Note: Initiator and Verifier can be the same person

AzSPU-GEN-PRC-001-A2

Page 61 of 102

15.2 Maintenance MoC Attachments - Templates

The following will be linked directly to the MoC template to assist with the uniform creation of MoC

Document

Document Title

Notes

number

To be completed when the master equipment list is to be updated ie

MOC-FRM-013

TAG REQUEST FROM

removing or adding tags

MOC-FRM-015

MAINT MoC PSV DEFERRAL

To be completed for PSV maintenance deferral

The attached data forms will be used to uniformly capture the data for maintenance changes

 Master Equipment List Form - for changes to the master equipment register.

Note: If equipment is approved to be removed from the master equipment list then the associated maintenance may

also be removed from CMMS. New equipment should be assigned maintenance in line with the maintenance guidelines

or manufacturer‟s recommendations and approved using the eMoC maintenance form

 Safety Critical PSV‟s and SIL rated equipment will have gone through risk based analysis to establish the

inspection / testing frequency, and deferral is unlikely to be approved unless it can be shown that on similar

equipment, in the same duty, the performance can justify a deferral. To allow proper assessment, the

original assessments need to be provided with any information that would support deferral.

Note: The deferral of PSV inspection requires that the risk is reviewed using the RBI practice and this should be

attached to the deferral of maintenance MoC.

15.3 Maintenance MoC Attachments- Guidance Notes

The following will be linked directly to the MoC template to assist with the uniform creation of MoC

Document number

Document Title

Notes

RECOMMENDED PRACTICE FOR THE RISK-

MOC-FRM-GN-008

BASED INSPECTION (RBI)

Guidance on the RBI for relief valves

OF RELIEF VALVES

Guidance on how to identify SCE document

AzSPU-GP-32-3001

SCE Identification Document

Hyperlink to the document

15.4 Maintenance & Inspection MoC - Risk / Hazard Guidance

Risk Level

Hazard Statement

Managed within the Operating area: No MoC required

 Changes to Location/Equipment Descriptions, Location hierarchy -Parent/Child relationships,

Location Priority, GL Account

 Changes to Job Plan Descriptions, Supervisor, Materials, Durations, Resources - not applicable to

master Job Plan

Maintenance &

Inspection-

 If a Technical MoC requires creation of a new/amendment of the existing maintenance subjects,

Insignificant risk

like PM, JP, PMR e.q. then Pre and Post Implementation stages of the same MoC will cover these

activities. Coordinator of the Technical MoC will identify Responsible people for these actions

from “R&M” and “System and Tools” teams. For RBI activities Inspection Engineers should be

contacted. No Maintenance MoC will be initiated in this case.

AzSPU-GEN-PRC-001-A2

Page 62 of 102

Risk Level

Hazard Statement

Managed within the Operating area - MoC required

 MoC with a risk level 1 (OMS Risk Matrix)

 Includes the creation of new tags.

 Like-for-like changes which require identification unique equipment identifier (serial number) as

mandated from ETP GP 31-30 for purposes of the inspection and testing program and to provide

Maintenance &

traceability. To be identified must have a Maintenance MoC to update eWarehouse (eg Process

Inspection -Risk

level 1 (white)

Pressure Vessels, Towers, Heat Exchangers and tube bundles, Fired Heaters and Boilers, Pump

and Compressor Casings, Storage Tanks, Relief Valves, Bursting discs, Vacuum Breakers, Flare

Tips, Lifting Equipment.)

 Replacement in kind a Maintenance MoC to update eWarehouse

 Includes optimization of CMMS planning fields or deferral of non safety critical equipment

Managed within the Operating area but will have independent technical review and risk level 2 approvals. -

MoC required

 MoC with a risk level 2 (OMS Risk Matrix)

 Includes the deferral of Safety Critical Equipment

Maintenance &

 Includes the deferral or inspection and testing of mechanical static equipment (eg piping, vessels,

Inspection Risk

structures, etc)

level 2

 Includes the deferral of corrosion management activities (eg monitoring, mitigation or control eg

(turquoise)

pipeline pigging)

 Modification of the technical content of job plans

 Changing job plan frequencies.

 Application of new maintenance routines

Managed within the Operating area but will have independent technical review and risk level 3 approval. -

MoC required

 MoC with a risk level 3 (OMS Risk Matrix)

Maintenance &

 Includes the second deferral of Safety Critical Equipment

Inspection Risk

 Includes the second deferral or inspection and testing of mechanical static equipment (eg piping,

level 3 (blue)

vessels, structures, etc)

 Includes the second deferral of corrosion management activities (eg monitoring, mitigation or

control eg pipeline pigging)

Managed within the Operating area but will have independent technical review and risk level 4 approval. -

MoC required

 MoC with a risk level 4 (OMS Risk Matrix)

Maintenance &

 Includes the third deferral of Safety Critical Equipment

Inspection Risk

 Includes the third deferral or inspection and testing of mechanical static equipment (eg piping,

level 4 (Purple)

vessels, structures, etc)

 Includes the third deferral of corrosion management activities (eg monitoring, mitigation or

control eg pipeline pigging)

Note: This risk associated directly with making the change and should not be confused with MoC priority

15.5 Maintenance & Inspection MoC - Documentation

At the heart of any change is the control of documents and data. Everyone needs to understand the status of these

items at three key stages of change.

Note: Documentum is the Master document data-base, EWarehouse is the Master Equipment data-base, and MAXIMO is the

Master maintenance system. It is essential that these are kept up to date.

Stage

Requirement

Verify (Design)

Authorisation (pre-start up)

Job Plans have been updated within Documentum, E Warehouse has been updated and all

Closure (post-start up)

data required has been added.

Note Master Generic Job plans affecting other operating areas should not be changed unless all of the operating areas have

agreed the change

AzSPU-GEN-PRC-001-A2

Page 63 of 102

15.7 Maintenance & Inspection - Process Flow

Maintenance and Inspection MoC

Use template describe, detail

Identify

scope, justify attach supporting

the need

documentation assign category,

for change

Anyone

priority and risk level

yes

canel

Confirm that the change is

required and all info is included

FACILITY OPS ENGINEER

OTHERS AS REQUIRED

modify

Complete the MoC detail ensuring that all effected

documents are check out from documentum

IDENTIFY WHO IS RESPONSIBLE FOR

SIGNING OFF EACH STAGE OF THE THE MOC

Change accepted and meets

standards

DRE (DISCIPLINE)

OTHERS AS REQUIRED

YES

COORDINATOR

RISK LEVEL 3 OR 4

Change accepted and all

AOM

issued addressed

RISK LEVEL 4

VP, E&P VP

YES

ANY PRE IMPLEMENTATION ACTIONS ARE COMPLETE

COORDINATOR

AUTHORISE

ALL UPDATED TO MAXIMO COMPLETED

ALL UPDATED TO E-WAREHOUSE COMPLETED

COORNINATOR

DOCUMENT COORDINATOR

ENG HSE DATA CONTROLLER

All documents have been upload in the master document area

All post implment

COORDINATOR

actions complete

MOC/EQ TEAM

yes

AzSPU-GEN-PRC-001-A2

Page 65 of 102

16 Specific Guidance - Maintenance & Inspection MoC (DC&I Facilities)

A Maintenance MoC will be created for:

 Creation / Amendment of Frequency or Job Plan or route stop Job Plan/amendment of Location or Route

Location/ Deferral / Suspension of Preventive Maintenance (PM) record in MAXIMO