DACO Management of Change 2023 (Rev. 01)

Classification: Internal Use
Dammam Airport Company (DACO) Doc. Reference.:
[Company common document] Issue:
Management of Change Doc. Effective Date: January 05, 2023

XXXXXXXX Doc. Review Date: …………………..
PROCEDURE Page: 1 of 24
CONTENTS
SECTION DESCRIPTION
1.0 PURPOSE
2.0 SCOPE
3.0 GLOSSARY, FORMULAE & DEFINITIONS
4.0 ACCOUNTABLE POSITIONS AND SPECIFIC RESPONSIBILITIES
5.0 METHOD
6.0 CONTINUAL IMPROVEMENT
7.0 COMPETENCY REQUIREMENT
8.0 IMPORTANT LINKS
9.0 CONTROL OF RECORDS
10.0 ATTACHMENTS/APPENDICES
1. PURPOSE:

The purpose of this management system is to provide the minimum requirements for effectively
managing changes to a facility over its lifetime from design, construction, operation,
decommissioning, mothballing and demolition. The MOC standard helps ensure that any changes do
not inadvertently introduce new hazards or unknowingly increase the risk of prospected hazards.
The airport environment is constantly evolving in response to the changing requirements of the
aviation business and the process of continual improvement. It is critical that such changes must be
considered in alignment with DACO safety policy and objectives.
It is crucial then to consult the concerned group of staff to assess whether the new circumstances
impact upon the safety of the workplace before these changes can be introduced into the airport
environment. Thereafter, such changes must be communicated in a clear and unambiguous manner
within a suitable period of time for the change to be discussed and assimilated.
MOC is about identifying potential hazards that a change can introduce, then assessing the risks
associated with these hazards, and systematically addressing them.
Any change to airport, process or people could introduce risk. In addition, changes can have
unintended or unsuspected consequences. A review of incidents across industry indicates that
ineffective MOC processes can result in:
 Change management that focuses on the expected benefits without properly considering the
possible risks;
 A tendency to focus on technical change rather than all types of change e.g., organizational,
materials and legal and regulatory requirements;
 Failure to communicate changes to the people affected by the change;
 Failure to update or revise key documents such as operating procedures; and
 Failure to address all relevant aspects of a change, which is a factor in many incidents and poor
business decisions.
Therefore, a formal process that is used to manage any change from conception through to
implementation is essential to identifying foreseeable potential hazards and managing their risks.
The MOC process is not a way to capture or explore ideas. Before initiating an MOC in the MOC
system, the following activities should be completed.
 Discuss it with the right people, for example your line manager.
 An indication from them that it’s feasible and that money and people are available to complete
the change.
 Agreement from them that it should be progressed through MOC. This agreement is then
formally documented in the MOC system.
2. SCOPE:

2.1. This management system applies to the functions when changes to existing approved
manufacturers/suppliers are made for DACO facilities.
2.2. The scope of this management system applies to permanent, temporary, emergency, software (IT)
changes and temporary repairs to any facility owned and/or operated and maintained by DACO.
MOC is not required for replacements in kind.
2.3. For managing other non-design changes, please refer to the following DACO management system:
 Management of Personnel and Organization Change
 Operating Procedures
 Maintenance Procedures
 Emergency response plan, procedure and change in location of emergency response
equipment
3. GLOSSARY, FORMULAE & DEFINITIONS
Glossary Definition
FMD Field Maintenance Department

EMT President and directors
Operation Operation Department
PED Process Engineering Department
AED Asset Engineering department
AIR Asset Integrity Reliability
ALA Asset Life Assessment
APM Asset Preventative Maintenance
CDP Concept Development Package
FEED Front End Engineering Design
Design change Design change is defined as any replacement, modification,
addition, associated with change. A direct “replacement in kind”
is not covered by this procedure and is to be handled with final
drawings.
E&PM Engineering & Project Management
Essential Operations Personnel Positions or functions within the process/facility that are
required to maintain safe working conditions, the absence of
whom could result in a major incident. For example, Control
room operations staff.
E&PM Shared Services - Engineering & Project Management

Glossary Definition
EHSS Environmental Health, Safety and Security

IFC Issued for Construction Engineering Package
Management Support Relevant Affiliate Management Authority as applicable and
mandated by the affiliate
MM Materials Management (SAP)
MOC Management of Change
PE Project Engineer
PHA Process Hazards Analysis
SHEMS Safety Health Environment Management Standard
SMP Standard Maintenance Procedure
Evaluation Engineer Process engineer, static engineer, EHSS engineers, QA etc for
technical study
4. ACCOUNTABLE POSITIONS AND SPECIFIC RESPONSIBILITIES :
The following positions are assigned to the following responsibility to ensure compliance to this
management system.
Responsibility Assignment Matrix, indicating the Responsible, Accountable, Consulted and Informed
(RACI) roles for high-level activities.
Management
Stakeholders
Engineering
Committee
Chairman
CEO PT
Middle
DACO
Safety
MOC
Activity Description
Management system development A I R C I

System awareness training to all stakeholders A I R C I
Recognition of change awareness A R C C I
MOC Committee Review and Approval - C I A C
Management system implementation A R C I R
Documentation and record keeping I A R C I

Management
Stakeholders
Engineering
Committee
Chairman
CEO PT
Middle
DACO
Safety
MOC
Activity Description
Reporting and reviewing KPIs I C A C I

Stewardship of MOC quality A I R C I
Training and competence I A R C I
Table 4.1 - Responsibility Assignment Matrix
5. TECHNICAL MOC PROCESS:
5.1 GENERAL PROCESS:
It is the responsibility of all MOC participants to assure they are competent to

perform the tasks assigned and to stop the job if unsafe conditions are
observed.
Technical MOCs should only be initiated when the Initiator believes the change
specifications are final and ready for implementation. Table 1 describes the

Technical MOC stages and the primary responsibilities of the roles within each
stage. These stages are conducted sequentially.
Technical MOC Stages
 BLUE FONT represents activities common to all MOC Types
 BLACK ITALIC FONT represents activities specific to, or providing

greater detail regarding, this MOC Type only
Initiate Initiator
 Identify change. Initiator should be the

person most familiar
 Determine the type of the MOC. with the change.
 Identify, and communicate change to, Key

Stakeholders.
 Conduct the appropriate Risk

Assessment(s).
 Initiate the MOC in the MOC system,

completing all fields accurately.
 Compile and load all supporting

documentation and impacted documents into
the MOC system.
 Participate in activities that support the MOC

process, as needed.
 Determine the duration of the MOC

(permanent or temporary).
 Identify and red line controlled documents

affected by the change.
 Select an approved Technical MOC

Coordinator.
 Add all known Pre-Approval, Pre-Startup,

and Post-Startup Actions and assign to
Responsible Parties including Document

Controller (Stage 2)

5.1. SPECIFIC RESPONSIBILITIES
4.1.1 MANAGEMENT SPONSOR (SHEMC CHAIRMAN)
 Proper functioning of the system OMS-317.

 Steward’s system performance to higher management.
 Reviews system status with administrator and DACO.
 Sets system goals and establishes performance measures.
 Reviews and approves changes to the system.
4.1.2 ELEMENT ADMINISTRATOR
 To Develop/review/update an effective system OMS-317.

 Ensuring this system is applied effectively throughout DACO.
 Coordinate with Technical review committee members and communicate the Concerned about their
responsibilities for effectively implementing the system.
 Controlling the MOC Procedure and maintaining a record all changes.
 Monitor implementation of the procedure.
 Provide feedback to DACO Committee on Status of implementation and identify areas of
improvement.
 Participate in the OMS self-audit and other DACO Audits and develop action plan based on audit
findings.
 User training for the procedures.
4.1.3 INITIATOR (E-MOC AUTHORIZED EMPLOYEE)
 Area owner shall initiate e-MOC Request.

 Employee is responsible for application of DACO MOC procedures. If required, he can take
assistance from the relevant SHEM-09 administrator.
 Reports to his supervisor about the incidents when MOC systems had been violated.
 Be familiar with the e-MOC initiation process.
4.1.4 ITIATOR SUPERVISOR

 Validate the change description, justification and approve in e-MOC system

4.1.5 PLANT MANAGEMENT TEAM (PMT)
 Review the proposed change with initiator/initiator’s supervisor /his team.

 Arrange a meeting among his team Run & Maintain for preliminary screening
 PMT to lead the Run & Maintain team to provide initiation package
 Preliminary screening of MOC requests by review change description, purpose, justification,
EHSS impacts, PHA, Reliability in design, asset information and business goals.
 Decide the priority for change
 To coordinate with PSM to perform PHA for all MOC’s as required based on Appendix#5
 Coordinate area Monthly meeting to review the MOC initiation-tracking list (MOC Database)
during one of the fixed agenda meetings.
 Ensure with supervisors if all operators are trained on the SOP before the PSSR
 Support the PSSR Team leader for PSSR activities and Punch-List activities.
 After ensuring all A Punch lists are completed, coordinate with the PSSR team leader for his
signature on Punch list/ follow-up Items.
 Ensure all the "A" punch list items is completed.
 For non-operational area, area owner to form a team to prepare initiation package
4.1.6 AREA SR. MANAGER
 Technical Evaluation of the changes with the qualified and experienced resources (Evaluation
Engineers, etc.) for meeting the intended objective, business goals and approve/disapproval of
technical study performed.
 Provide resources from operations for project design review, EHSS reviews, procedure
development, training, PSSR, Turnover, commissioning, start-up and MOC Closure.
 Review permanent, Temporary, Emergency and EHSS MOC status with emphasis on expiry
date as part of PMT weekly meeting
 Review and give concurrence to cancel the MOC's if not required.
 Authorized commissioning after completion of PSSR punch ‘A’ items.
4.1.7 OPERATIONS SPECIALIST

 Provide Operations input during the project design review for operability, maintainability,
constructability, human factors, HAZOP, inherent safety reviews with the project team at
appropriate times like, (design reviews during detail engineering), equipment selection, etc.

 Support the construction activities by providing operations input on continuous basis.

 Develop procedure for the facility operation. Conduct operator training with the help of Area
Training coordinator and maintain the records.
 Communicate all changes to affected employees and area owners.
 Steward and lead the Pre-Start up Safety Review (PSSR) process prior to turnover acceptance
and commissioning of the project. Ensure all “B punch” items on MOC are completed
4.1.8 MOC COORDINATOR/ANALYST

 Fully understand and follow documentation related requirements for SHEM-09 and SHEM-01.
 Maintain Bi-Weekly MOC committee rhythm. Ad hoc meetings may be requested based on
plant needs/emergency.
 Be familiar with MOC Initiation flow chart and Assign area tracking number by plant MOC
focal point
 Assign MOC numbers, create MOC file folder and maintain up to date MOC database in the
portal.
 Emergency changes are numbered, logged, and tracked for closeout within the validity period
of the emergency change.
 Reviews the quality of MOC packages requirement prior to the MOC committee meeting.
 Issue the Approved MOC packages & supporting department transmittal packages and track the
packages for closeout.
 Issue the MOC Tracking report as per the system requirements.
 Track and follow up the MOC request status until MOC close out though e-MOC.
 Inform to the initiator about the status of MOC request.
 Issue the MOC package with agenda of meeting and invitation to MOC committee members
before one week.
 Records the proceedings of the MOC meetings and issues the Minutes of meeting to all MOC
committee members, MOC administrator and Element administrator.
 Coordinate with Assigned Engineer to review the MOC with operations, engineers and
specialist before the Initial MOC approval and Final MOC approval.
 Receive the Approved MOC package for MOC implementation coordination.
 Ensure operation jobs on respective MOC, and MOC forms are completed before the PSSR
 Final closeout of the MOC after closing the MOC is through respective Assigned Engineer.
4.1.9 MOC COMMITTEE

 MOC Committee charter and members to be nominated by technical director in consultation
with SHEMC chairman.

 MOC committee chairman shall be Sr. Manager from technical division, back up to be of Sr.
Manager Position.
 MOC committee members shall be as per section 5.4.2.
 Committee to review and approve changes considering EHSS, currently plant operation, design
and PSM.
 Committee to ensure minimum requirements are met as per FM-VD01-349
 Committee reviews and approves the design changes to ensure the elements of MOC are
effectively controlled.
 Committee reviews and approves initiations based on technical justifications.
 Committee approvals are also needed for carrying out high risk activities for the projects e.g.,
hot taps, changes to cathodic protections, major process tie-ins, and temporary repairs.
 Review & ensure that all EHSS factors are considered in the implementation phase of MOC
 Recommends HAZOP Or other EHSS Reviews and ensures comments are resolved.
 Steward’s temporary, Emergency and EHSS MOC status.
4.1.10 MOC COMMITTEE CHAIRMAN

 Leads the meeting and decide to continue or adjourned meeting based on the minimum quorum
as decide in section 5.4.2.
 Approval of the change been requested.
 Decides on the applicability of the MOC procedures for the changes.
 Stewards the MOC Committee performance to site SHEMC.
 Ensure the quality of documents/drawing are completed as per FM-VD01-349
 Facilitates SHEM-09 requirements and other related SHEMS compliance and ensures all
related SHEM forms are completed/initiated as applicable.
4.1.11 PROCESS SAFETY MANAGEMENT (PSM)

 PSM shall be consulted for review and recommendation on PHA assessment form FM-VD03-
617.
 PSM to facilitate and ensure quality of initial/final PHA.
 PSM to track and monitor closure and validation of all PHA recommendations prior to PSSR.
4.1.12 EXECUTION OF MOC’S

 For execution and closeout of MOC’s refer to OMS-214
5 METHOD:
5.1 RECOGNITION OF A CHANGE

A system shall be in place to establish ‘what constitutes a change’ and ensure employees and
contractors are trained to differentiate between a ‘Replacement in Kind’ and a ‘Replacement
not in Kind’. Refer to examples in Attachment-7: Examples of “Replacement in Kind” and
“Replacement not in Kind”
5.2 INITIATION OF A CHANGE

Changes (permanent, temporary and emergency) shall be requested using e-MOC system.
Refer to Appendix-G
Appendix #A: For Permanent change workflow
Appendix #B: For Temporary change workflow
Appendix #C: For Emergency change workflow
5.3 MANDATORY REQUIREMENTS FOR MOC INITIATION.
Refer to FM-VD01-349
5.4 CATEGORIZATION OF A CHANGE

Changes shall be categorized as:
5.4.1 Design change – All changes (addition, deletion and modification), with the
exception of Replacements-in-Kind, shall be managed through MOC. Below
are change examples.
5.4.2 Process/laboratory chemicals, product, additives, catalysts and their
packaging including change in chemical manufacturer/supplier
5.4.3 Formulation change that will lead to change in properties of product
5.4.4 Hardware/equipment including piping rearrangements, materials of
construction, specifications and emergency response equipment.
5.4.5 Process control and emergency shutdown (ESD) hardware, computer
software/programs & set point change.
5.4.6 Safe upper and lower limits (COP) i.e. operation outside of the pre-established
safe upper and lower limits.
5.4.7 Deviations from design standards
5.4.8 Equipment unavailability not anticipated in process design
5.4.9 Electrical equipment e.g. transformer, power distribution, cabling, drives and
protections
5.4.10 Plant capacity
5.4.11 EHSS critical equipment, instrument and devices list
5.4.12 Car-seal and blinds list for normal operation
5.4.13 Permanent buildings and/or its use e.g. occupancy
5.4.14 Placement of trailers, porta cabins, tents etc.
5.4.15 Decommissioning, mothballing, demolition
5.4.16 Temporary repairs

5.4.17 Security hardware and software

5.4.18 Manufacturer of process equipment change e.g. pumps, compressor, control
valve, heat exchanger etc. with same specification
5.4.19 For Replacement in Kind & Replacement not in Kind Refer Appendix-F.
5.4.20 For replacement with same specification refer Appendix-D
5.4.21 MOC Chairman shall approve plant material replacements with same
specifications and supplier change only. Please refer to Appendix-7
Replacement with same specifications.
5.4.22 Emergency response plan, procedure, location of emergency response
equipment change (refer to SHEM-11.01)
5.4.23 Operating and maintenance procedure change (refer to SHEM-03.01 and
03.02)
5.4.24 Organizational and Personnel Change (refer to OMS-123)
5.5 DESIGN CHANGES REVIEW AND APPROVAL METHODOLOGY

5.5.1 MOC Committee charter and members to be nominated by technical director in
consultation with SHEMC chairman.
5.5.2 MOC committee chairman shall be Sr. Manager from technical division, back up to be
of Sr. Manager Position.
5.5.3 MOC Review Committee:
The MOC Committee for design (permanent, temporary and emergency) changes shall
include the following experienced personnel with a minimum as Sr. Engineer (with
minimum 2 years’ experience in DACO).
Minimum quorum
 EHSS Engineer
 Process safety Engineer
 Operation Excellence
 Maintenance Excellence
 Process Engineer
 Relevant discipline engineer
Relevant discipline engineer shall be as per the scope of change determined by the MOC
coordinator as per below:
 Mechanical Engineer static

 Mechanical Engineer rotating
 Instrument Engineer
 Control System Engineer
 Electrical Engineer
MOC Chairman shall ensure that minimum quorum is available to proceed with change
approval.

MOC coordinator shall initiate the meeting invite & facilitate documentation & reporting.
5.6 MOC COMMITTEE SHALL REVIEW FOR DESIGN CHANGES

5.6.1 Review the technical justification/need/basis for the change
5.6.2 Review and approve changes (permanent, temporary and emergency) to ensure that
hazards and potential impacts on human health, safety, or the environment
associated with the proposed change are identified and assessed, and that the
recommended protections and risk mitigation actions are adequate. Evaluate
applicability of hazard identification techniques identified in SHEM-
02.01/02.02/02.03.
5.6.3 Establish the change routing and approval requirements for temporary, permanent
and emergency changes
5.6.4 Ensure that a formal Process Hazard Analysis (PHA) is conducted in accordance
with Process Safety Risk Assessment standard (SHEM-02.01) for all changes.
Where it is not possible to conduct a PHA, due to the nature of change, a
justification shall be documented as part of the MOC process changes. Please refer
to Appendix- E when a PHA is needed. The PHA methodology will be decided by
the MOC in consultation with the Process Safety Engineer or PHA Team Leader.
5.6.5 Ensure that the change is in accordance with DACO Engineering standards,
applicable codes and standards, manufacturer’s recommendations, good
engineering practices and local legislations
5.6.6 Ensure that EHSS documentation, operating, maintenance and emergency response
procedures which need to be updated has been identified
5.6.7 Ensure that any required training in accordance with Training & Competencies
management system (OMS-131) has been identified
5.6.8 Specify provisions for the acceptance of ownership of any new equipment
5.6.9 Ensure the need to conduct a PSSR is identified. A PSSR shall be conducted for
changes that require an update to process EHS documentation and for all design
changes to the plant facilities or process
5.6.10 Ensure EHSS Critical equipment, instrumentation, devices & systems identification
is done in accordance with applicable SHEM standards
5.6.11 Ensure equipment criticality assessment is identified and updated in accordance
with Asset Performance management system(OMS-433) to determine final
criticality ranking of the equipment
5.6.12 Ensure relevant APM methodology studies (RCM/RBI/RIS) is identified in
accordance with Asset Performance management system (OMS-433) to
generate/revise the maintenance strategy (PM) for new or modified equipment
5.6.13 Ensure need for energy and sustainability evaluation study is identified for new and
modified equipment and process changes/modifications in accordance with Energy
Management system (OMS-423)
5.6.14 Ensure the change comply with all regulatory and permit requirements and
processes, as applicable
5.6.15 The MOC committee shall review and approve all the design changes as specified
above. The MOC committee shall formally meet to review the change and a

periodic meeting schedule of the MOC should be developed. The MOC Chairman
shall approve each change after review by the MOC committee.
5.6.16 MOC committee review actions and approval shall be documented. Review actions
shall be tracked to completion.
5.6.17 MOC committee chairman shall verify and confirm that the area owner shall not
start on safety and fire protection related work until HCIS approval for the final
design and equipment. The HCIS shall have the right to reject any non-compliant
equipment, system, or suppliers. In case any equipment, system, or supplier is
rejected by HCIS, the FO shall replace it with one that is approved or submit
additional details for justification of approval.
The MOC review and approval should be a 2-step process. The first step
identifies the impact of the change and what needs to be done to approve the
change e.g. conduct PHA according to HAZOP methodology, check load on pipe
racks etc. The second step ensures that all assessments are complete before final
MOC approval is given

5.7 TEMPORARY CHANGES

Duration and Extension of Temporary Changes
5.7.1 All temporary changes shall specify a predetermined time limit for their duration
with the maximum limit being one year.
5.7.2 Risk assessment to be provided as part of initiation.
5.7.3 Initiation package as per checklist to be provided (FM-VD01-349)
5.7.4 The duration of the temporary change shall be as short as possible to accomplish
its intent. The predetermined limit can be shown as a date or as an event that
must occur before the change is removed (e.g. time to complete temporary
change, quantity of material produced, batch cycles completed, etc.).
5.7.5 Once the time limit or specified event is complete, the temporary change shall be
removed or converted to a permanent change. The conversion to a permanent
change will close the temporary change. The removal of all temporary changes
and conversion to a permanent change shall be documented and communicated to
all affected personnel
5.7.6 If an extension of the temporary change is required, the MOC committee shall
review and approve the extension prior to the expiry of time limit. Temporary
change extensions shall require a reassessment of the risk and shall be
documented and communicated to all affected personnel. Extensions beyond the
first extension (Overall 2 years of temporary MOC) shall be approved at a level
above the MOC committee, which is EHSS Committee.
5.7.7 If a temporary change is required to be converted to a permanent change, a new
MOC request shall be submitted for review and approval in accordance with
permanent change requirements
5.7.8 PSSR shall be done during the implementation of temporary change
5.7.9 PSSR shall be done when temporary change period is completed and reverted to
original design.
5.7.10 Refer Appendix-B

5.8 EMERGENCY CHANGES

Situations may arise when a change must be made quickly, for example; cases that
represent an immediate danger to life, potential for major equipment and property damage,
major production loss, major off-spec production or serious environmental impacts. For
these special cases the normal process of MOC may be modified to suit the circumstances,
with the following considerations:
5.8.1 Shift manager shall review the change for risk and obtain technical concurrence
(SME, EHSS/Process Safety & Operations Management) before approving &
executing the change. A PSSR shall be triggered before executing the change
5.8.2 An e-MOC request shall be submitted for the emergency change to be reviewed
and approved by the MOC committee the next working day. MOC committee
chairman to evaluate and ensure the emergency MOC raised falls under the
above mentioned criteria.
5.8.3 The change shall be converted to a temporary or permanent change the next
working day
5.8.4 The emergency change shall be recorded in the operator shift logbook
5.8.5 Affected personnel shall be informed prior to implementing the emergency
change. Shift supervisors shall ensure that all affected personnel are informed
about the change prior to starting their work in subsequent shifts
5.8.6 MOC shall be presented next working day to MOC committee for review and
approval
5.8.7 MOC committee shall review and approve/reject the change based on risk
evaluated during implementation.
5.8.8 Rejected emergency MOC by MOC committee shall be reverted back to original
condition
5.8.9 Documentation of emergency changes shall include a summary of why the
change is needed to be done on an emergency basis, the planned duration,
procedures, the process followed to review the emergency change, including
personnel involved, and any other information necessary to safely implement the
change
5.8.10 Refer Appendix-C
5.9 MOC REVIEW AND APPROVAL REQUIREMENTS

5.9.1 All permanent MOC shall go through two MOC committee approval process:
5.9.1.1 The MOC Committee shall provide initial approval based on the documents
submitted as per checklist FM-VD01-349.
5.9.1.2 Final approval shall be provided upon completion of Front End Engineering
(FEED) where applicable.

5.9.2 Permanent and temporary changes shall be implemented only after the MOC
committee members have reviewed and approved the change
5.9.3 Temporary repairs shall be implemented only after designated members have
reviewed and approved (as per FM-VD01-348) the repair and risk assessment
conducted
5.10 SAFER
5.10.1 An MOC shall not be implemented if risk is still at ‘Major Risk’ level after
mitigation action. Major risk items identified in MOC shall be mitigated to
‘Insignificant Risk’ level or ALARP (with approvals for the level of risk) before
implementing or commissioning such MOCs.
5.10.2 MOCs with ‘Significant’ or ‘Minor’ residual risk levels shall be implemented
only with formal approvals in accordance with SHEM-02.00.
5.10.3 MOC can be implemented if the residual risk is at ‘Insignificant Risk’ level.
5.11 CHANGE COMMUNICATION

All affected personnel shall be informed about the change prior to the change startup
including removal of temporary change and conversion of temporary change to permanent
by area owner.
5.12 MOC CLOSURE

5.12.1 Temporary changes shall be closed within specified time limit (12 months). If the
extension is required then an extension shall be raised.
5.12.2 All permanent changes shall be tracked and closed out within 180 days of the
implementation of change.
5.12.3 All changes must be physically complete and all changes to process safety
information, reliability, maintenance and operating documentation (e.g. P&IDs,
PFDs, etc.) shall be complete before closing out an MOC.
5.12.4 All PSSR actions must be completed before closing out the MOC
5.12.5 MOC close out form shall be filled FM-VD03-583
5.13 NEW FACILITIES

For new facilities, the authority designated by AR-RAZI shall approve the process design
of the facility. Once the new facility is released for construction, any change to its process
design shall be carried out in accordance to this management system.
5.14 LEGAL AND REGULATORY REQUIREMENTS

MOC Committee/Project engineer shall ensure compliance of all applicable local, national,

and state/regional regulations and requirements and all international standards and treaties,
as applicable.
Legal & compliance requirements shall include but are not limited to the following:
 General Authority of Meteorology & Environment Protection (GAMEP).

 Royal commission Environmental Regulations (RCER)
 Ministry of Labor (MOL) – IH Regulations
 Ministry of Health (MOH) – IH Regulations
 Saudi Arabia Standards Organization (SASO) – IH Regulations
 Civil Defense IH Regulations
 High Commission for Industrial Security (HCIS)
 King Abdulaziz City for Science and Technology (KACST)
 King Abdullah City for Atomic and Renewable Energy (KACARE).
Other Requirements.
 UNO and International Treaties as applicable and feasible.
 SABIC OMS Standards
 RC-14001
 ISO 14001
 OHSAS 18001
 Community requirements as feasible.
 Costumer and stakeholder requirements, as applicable.
 Gulf Petrochemicals & Chemicals Association (GPCA)
 Montreal Protocol
 Kyoto Protocol
 Chemical Weapons Convention
 Basel Convention
The applicable legal and other compliance requirements shall be identified in the EHSS
Legal and Other Compliance Requirements Registry (PR-VD01-023-H).
If an instance of regulatory non-compliance is identified by any employee, the EHSS
Incident reporting procedure will be used to address the non-compliance.
EHSS Security & GR section shall keep, maintain & renew Industrial and commercial
licenses.
EHSS Environment team shall maintain Environment Permit to Operate (EPO) records
6.0 CONTINUAL IMPROVEMENT:
Element or sub element leader shall document, track and report performance improvement, of the
below KPIs including any associated corrective and preventive actions, and then communicate them to

concern personnel as per the review rhythm. Problem Solving Tools & Techniques procedure (OMS-
522) shall be followed to analyze the performance of this procedure as followings;
Performance
Review Rhythm Performance Analysis
Measurement (KPI)
Yearly Audit Analysis and Analysis of
Audit Findings for 3 years referring to
Internal Audit OMS Quarterly or Yearly OMS - Documentation or Implementation
6.1.
Compliance % Management Review - Root Causes of Findings (People,
Materials, Machines Or equipment,
Environment, Documents)
Number of incidents (Class A, B and C)
with root cause caused by inadequate
MOC.
Number of MOCs not closed within 180
days of implementation
Number of changes carried out
a) 100 % Compliance to Quarterly or Yearly OMS without MOC.
6.2.
MOC Requirement Management Review
Number of temporary change
overdue MOCs with reference to
first date set.
Number of MOC Quality reviews
conducted by the Standard Leader
in a year
6.7. DACO shall establish a rhythm to review performance against this management system .The results of
these reviews shall be used as input to DACO’s continual improvement plans in accordance with
Continual Improvement Framework management system (OMS-511).
6.8. Statistical tools shall be used to analyze the performance of this management system in accordance with
Problem Solving Tools & Techniques management system (OMS-522).
6.9. DACO shall document, track and report performance improvement, as well as any associated corrective
and preventive actions, and then communicate these appropriately to organization personnel and
stakeholders on a regular basis.
7.0 COMPETENCY REQUIREMENTS:
AR-RAZI developed a competency matrix in accordance with: Training & Competencies

management system (OMS-131). The matrix shall identify the key skills and knowledge required
to successfully implement this management system. These competencies shall be mapped to
critical functional roles within the organization structure.

members/ Approvers
P HA Leader/PSSR
MOC Chairman &
Line Management
Element Leader
All employees
Competency
Leader
Development of management system Type P - - - A
Auditors training D - - - P
MOC Awareness training - - D - A
MOC Training P P D P A
Table 7.2 - Competency Matrix
Competency Types: Core Leadership Functional

Proficiency Levels: D Developing P Proficient A Advanced
8.0 IMPORTANT LINKS/REFERENCES:
Links with Other OMS Standards
Link Document
Document Title Topic of Linkage
From/To Reference
8.1 To Safer Sub Elements SHEM-02.01 Trigger PHA & other assessments

Link Document
From/To Reference
SHEM-02.02
SHEM-02.03
Pre Start Up SHE
8.2 To SHEM-06 Trigger pre-start up EHSS review
Review
Asset Performance Trigger EHSS and equipment
Management OMS-433 criticality assessment,
8.3 To
SHEM-07 conduct/review APM proactive
Asset Integrity methodologies RCM, RBI, RIS
Operating Procedure
SHEM-03.01, Temporary Operating,
Maintenance Procedure
8.4 To SHEM-03.02, Maintenance and Emergency
Emergency Response SHEM-11.01 Procedures
Preparedness
Emergency response plan and
Emergency Response
8.5 To SHEM-11.01 change in location of emergency
Preparedness
response equipment
Management of
Management of Personnel and
8.6 To Personnel and OMS-123
Organization Change
Organization
8.7 To SAFER SHEM-02 Trigger SAFER
Training and competencies

Training and
8.8 To OMS-131 requirements with change and for
Competence
this standard
Energy and sustainability
8.9 To Energy Management OMS-423
evaluation
OMS-234,
OMS-234, SHEM-01, SHEM-01, 02, 03,
02, 03, 05, 06, 07, 08, 05, 06, 07, 08,
8.10 To Identify change and trigger MOC
10,11, 12, 13,14, 15, 16, 10,11, 12, 13,14,
OMS-214, 412, 413 15, 16, OMS-214,
412, 413
Trigger MOC for redesign tasks as
Asset Performance recommended by APM proactive
8.11 To OMS-433
Management methodologies (RCM, RBI, RIS)
and RCA
Trigger MOC for
8.12 To Asset Retirement OMS-441 decommissioning, mothballing,
demolition

Link Document
From/To Reference
EHSS Incident,
Root cause analysis related to
Reporting,
8.13 From SHEM-10.00 SHEM-09, near miss related to
Classification,
lack of change recognition
Investigation & Analysis
Leadership Commitment Leadership, standard leader
8.14 From OMS-111
and Culture responsibilities
8.15 From Site Stewardship Model OMS-122 Site stewardship
Performance
8.16 From OMS-211 Performance review KPIs
Management
Management System Management system development
8.17 From OMS-231
Development and clarifications issuance
Compliance Assessment
8.18 From OMS-232 Audits and assessments
and Evaluation
Documentation and Documentation and control of
8.19 From OMS-234
Control of Records records. Updated records.
9.0 CONTROL OF RECORDS:
Retention
Record Record Record
Record Title Period Classification
Reference Keeper Location
Completed change
processing records
shall include MOC
Approval, marked
up P&ID, minutes Project
9.1 of MOC Review - Document E-MOC 5 Years Internal Use
meeting, status of Controller
actions, PSSR,
PHA and
associated
documentation
MOC quality element
9.2 - ECM 5 Years Internal Use
review administrator

Retention
Record Record Record
Record Title Period Classification
Reference Keeper Location
Training for element

change recognition administrator
Stewardship
by site OMS element
or equivalent administrator
Annual action
plan based on
incidents, element
audits, quality administrator
review
10.0 ATTACHMENTS/APPENDICES:
Document Title Attachment

10.1 Appendix-A: Permanent MOC workflow PR-VD01-023-A
10.2 Appendix-B: Temporary MOC workflow PR-VD01-023-B
10.3 Appendix-C: Emergency MOC workflow PR-VD01-023-C
10.4 Appendix-D: Replacement with Same Specification PR-VD01-023-D
10.5 Appendix-E: When PHA is required PR-VD01-023-E
Appendix-F: Examples of ‘Replacement in kind’ and ‘Replacement Not
10.6 PR-VD01-023-F
in kind’
10.7 Appendix-G: E-MOC Method of Creation PR-VD01-023-G
10.8 Appendix-H: Legal and Regulatory requirements PR-VD01-023-H

DACO Management of Change 2023 (Rev. 01)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DACO Management of Change 2023 (Rev. 01)

Uploaded by

Copyright:

Available Formats

Classification: Internal Use

Dammam Airport Company (DACO) Doc. Reference.:

[Company common document] Issue:

Management of Change Doc. Effective Date: January 05, 2023

3.0 GLOSSARY, FORMULAE & DEFINITIONS

4.0 ACCOUNTABLE POSITIONS AND SPECIFIC RESPONSIBILITIES

6.0 CONTINUAL IMPROVEMENT

7.0 COMPETENCY REQUIREMENT

8.0 IMPORTANT LINKS

9.0 CONTROL OF RECORDS

Dammam Airport Company (DACO) Doc. Reference.:

[Company common document] Issue:

Management of Change Doc. Effective Date: January 05, 2023

Dammam Airport Company (DACO) Doc. Reference.:

[Company common document] Issue:

Management of Change Doc. Effective Date: January 05, 2023

3. GLOSSARY, FORMULAE & DEFINITIONS

FMD Field Maintenance Department

Dammam Airport Company (DACO) Doc. Reference.:

[Company common document] Issue:

Management of Change Doc. Effective Date: January 05, 2023

EHSS Environmental Health, Safety and Security

4. ACCOUNTABLE POSITIONS AND SPECIFIC RESPONSIBILITIES :

Management system development A I R C I

Dammam Airport Company (DACO) Doc. Reference.:

[Company common document] Issue:

Management of Change Doc. Effective Date: January 05, 2023

Reporting and reviewing KPIs I C A C I

5. TECHNICAL MOC PROCESS:

5.1 GENERAL PROCESS:

It is the responsibility of all MOC participants to assure they are competent to

Dammam Airport Company (DACO) Doc. Reference.:

[Company common document] Issue:

Management of Change Doc. Effective Date: January 05, 2023

Technical MOC Stages

 BLUE FONT represents activities common to all MOC Types

 BLACK ITALIC FONT represents activities specific to, or providing

 Identify change. Initiator should be the

 Identify, and communicate change to, Key

 Conduct the appropriate Risk

 Initiate the MOC in the MOC system,

 Compile and load all supporting

 Participate in activities that support the MOC

 Determine the duration of the MOC

 Identify and red line controlled documents

 Select an approved Technical MOC

 Add all known Pre-Approval, Pre-Startup,

Dammam Airport Company (DACO) Doc. Reference.:

[Company common document] Issue:

Management of Change Doc. Effective Date: January 05, 2023

Dammam Airport Company (DACO) Doc. Reference.:

[Company common document] Issue:

Management of Change Doc. Effective Date: January 05, 2023

5.1. SPECIFIC RESPONSIBILITIES

4.1.1 MANAGEMENT SPONSOR (SHEMC CHAIRMAN)

 Proper functioning of the system OMS-317.

4.1.2 ELEMENT ADMINISTRATOR

 To Develop/review/update an effective system OMS-317.

4.1.3 INITIATOR (E-MOC AUTHORIZED EMPLOYEE)

 Area owner shall initiate e-MOC Request.

4.1.4 ITIATOR SUPERVISOR

Dammam Airport Company (DACO) Doc. Reference.:

[Company common document] Issue:

Management of Change Doc. Effective Date: January 05, 2023