Professional Documents
Culture Documents
Rev. No: 0
Document Approval Form (DAF)
Date of issue : 25 04 2016
PREPARED BY
Signature
Name Bartek Zonjek A.T. Kearney, Project Manager
Date 24/03/2016
REVIEWED BY
Signature
Tahir Ahmad Zahoor
Abbas Hamid Abbas Al-Mazroui
Coordinator/Controller II, Majed Mahmoud Saleh
Name Projects, GM Office, Manager PMC Marafiq
Manager, Fuel & Facility Storage
Project
Projects
Date
Signature
Name
Date
APPROVED BY
Signature
Sultan Turki Al-Ruhaili
Name VP Engineering and Project (Acting) Marafiq
Date
ISSUED BY
Signature
Ali Abdulali Al-Marzooq
Name Assessor , IMS
Date May 9, 2017
DISTRIBUTION LIST
Document classification
Internal use
Date : 25 04 2016
CONTENTS
1 PURPOSE ......................................................................................................................................................... 2
2 SCOPE .............................................................................................................................................................. 3
4 VALIDITY .......................................................................................................................................................... 8
5 RESPONSIBILITIES ............................................................................................................................................ 9
6 PROCEDURE ................................................................................................................................................... 10
ANY EXCEPTIONS IN FOLLOWING THIS PROCEDURE SHALL BE DOCUMENTED & APPROVED BY THE
APPROVAL AUTHORITY (CORRESPONDING TO THE STAGE OF THE PROJECT) BEFORE COMMENCING
AN EDMS THAT IS NOT MARAFIQ PROPERTY .............................................................................. 11
Date : 25 04 2016
1 Purpose
The purpose of this procedure is to define the process of project document management for the
Marafiq projects. This procedure describes:
Date : 25 04 2016
2 Scope
This procedure is applicable to all Capital Expenditure Projects funded and executed by
MARAFIQ, including New Facilities / Expansions, BMRR (Balancing, Modernization,
Rehabilitation and Replacement) and HSE Mandatory compliance type projects.
Date : 25 04 2016
Date : 25 04 2016
FF : Finish to Finish
FS : Finish to Start
FID : Final Investment Decision
FVA : Functional Value Analysis
HSE : Health, Safety and Environment
HCIS : High Commission of Industrial Security
IAI : Initial Acceptance Inspection
IFC : Issued for Construction
IK : In Kingdom
IRR : Internal Rate of Return
ITP : Inspection Test Plan
KPI : Key Performance Indicator
LAR : Land Allocation Request
LL : Lessons Learned
LLC : Lessons Learned Coordinator
MC : Mechanical Completion
MCC : Mechanical Completion Certificate
MCI : Mechanical Completion Inspection
MDR : Master Deliverables Register
MEL : Master Equipment List
MIRA : MARAFIQ Integrated Risk Assessment
NCR : Non Conformance Reporting
NOPAT : Normal Operating Profit After Tax
NPV : Net Present Value
NPVR : Net Present Value Ratio
NTP : Notice to Proceed
OIP : Operation Implementation Plan
OOK : Out of Kingdom
P&C : Procurement & Contracting
P&ID : Piping & Instrumentation Diagram
P&L : Profit & Loss (financial statement showing revenues, costs and profit / loss)
PAP : Permit Application Package
PEL : Primary Equipment List
PES : Project Execution Strategy
PEP : Project Execution Plan
PFD : Process Flow Diagram
PIP : Project Implementation Plan
PIR : Post Implementation Review
PL : Punch List
PM : Project Manager
PMC : Project Management Consultancy
PMI : Project Management Institute
PO : Purchase Order
PPE : Personal Protective Equipment
PR : Purchase Requisition
PROPRIETARY NOTICE IMPORTANT
THIS DOCUMENT CONTAINS INFORMATION PROPRIETARY TO MARAFIQ. ANY DISCLOSURE Only document with stamps are considered official.
OR USE IS EXPRESSLY PROHIBITED EXCEPT UPON WRITTEN PERMISSION BY MARAFIQ.
Power and Water Utility Company for Document ID No: MVEP-1-CE-602
Jubail and Yanbu
Page: 6 of 21
Date : 25 04 2016
Date : 25 04 2016
3.2 Definitions
Capital expenditure (Capex): Refer to Document ID # MFMP-1-FI-014: Fixed Assets & Capital
Expenditure Procedure - Classification of Expenses as CAPEX and OPEX for the definition
of Capital Expenditure
Business Unit (BU): Refer to Document ID # MVFP-1-AC-015: Fixed Asset & Capital
Expenditure Procedure Capitalization of Fixed Assets (Section: 3.9) for the definition of
Business Unit (BU)
Accountability (A): The individual who has the authority to say "Yes" or "No" to the task and who
has the power to veto over all other involved in the task. For any given task, only one person is
held Accountable.
Responsibility (R): The individual who performs the task is considered "Responsible" for the
action or implementation. The degree of responsibility is defined by the ACOUNTABLE person
based on the Responsible scope and capability. More than one person may share responsibility
for the action or implementation.
Consultancy (C): The individual with whom there should be actual discussion or other
communication prior to making a final decision or taking action. There may be more than one
person who should be consulted for a given task.
Information (I): An individual who is advised (via written report, for example) after a decision is
made or an action taken. There may be more than one person who must be informed.
Date : 25 04 2016
4 Validity
This procedure is valid until a subsequent revision is warranted for business needs.
Date : 25 04 2016
5 Responsibilities
In each of the project stages, Project Support Department is responsible and accountable of
implementation of this procedure with support of stage gate owner.
Across all the stages, all project Marafiq stakeholders (FPD/BDD, TSD, PE, PJ, BU, P&C, others)
are responsible for ensuring that the project documents are in the format defined by this
procedure. Marafiq respective stakeholders, needs to assure that also the PMCs, Contractors,
other key partners are following this Project Document Management procedure, and especially
for:
Date : 25 04 2016
6 Procedure
6.1 Document Control policy
6.1.1 The management of project documents as outlined in this procedure shall also follow the
requirements of Procedure MCFP-1-IM-001 - Document Control Procedure, with the
following specifications / additions:
6.1.2 EDMS (Electronic Document Management System): usage of EDMS for DOC
management control is essential for all large projects. Marafiq can use, for projects
purposes, its own or PMC or Contractors EDMS, as long as the following conditions are
abide:
Marafiq will define and control the access rights for the EDMS for all parties involved
(Marafiq own personnel, PMC, contractors, etc). Marafiq will have access to all project
documents. As per practical reasons, within the limits defined by Marafiq, its partners
will assign a coordinator that will administer access rights for users coming from their
organizations. Any risks regarding potential leakage of sensitive information (e.g.
costs, contractors performance, negotiations, etc) will be carefully assessed and
mitigated by Marafiq
Date : 25 04 2016
All project documents & EDMS records will be the property of Marafiq & contractors
shall transfer control to Marafiq request, providing Marafiq with full access to all Project
documents (e.g. by copying on DVDs, CDs etc.)Internet based EDMS systems shall
be deployed with high security standards. Any risks should be assessed and mitigated
by assigned Marafiq Document Controller
Any exceptions in following this procedure shall be documented & approved by the
Approval authority (corresponding to the stage of the project) before commencing
an EDMS that is not Marafiq property
Document numbering and version: The Marafiq document numbering system shall be
adopted for all documentation developed across the project stages, starting with
Scouting Study phase. The numbering system will apply to Marafiq, and also to PMCs,
EPC Contractors and other key stakeholders. All parties shall follow the numbering
and all of their documentation as submitted to Marafiq shall be numbered accordingly.
See appendix
Descriptive name: All documents should have titles with keywords which may be easily
searched upon (e.g. a contract should have contractor name in the title and main
scope
File status, e.g. Draft, Issued for information, etc. For details see appendix
6.2.2 Overall, each document name will follow the format: File number_Descriptive name_File
status
Document Controller shall set up and maintain hard-copy files of PMC / Vendor /
Partner Documents
Date : 25 04 2016
Document Controller shall monitor the flow of PMC / Vendor / Partner Documents to
ensure that responses are received within the specified turnaround time
Document Controller needs to establish and maintain controls to satisfy the
requirements of receipt, distribution, and return of PMC / Vendor / Partner Documents
6.3.2 The processes involved to control of all incoming and outgoing project documentation
received at site is governed by the work instruction MYTW-1-PM-002 Control of Project
Documentation, including:
6.3.3 All other project documentation, even if not specifically included in point 6.2.1, shall follow
this procedure (numbering, document transmittal see appendix-, file structure see
chapter 6.3, etc)
6.3.4 A master file of incoming / outgoing controlled & external documentation (including
approved documentation) shall be maintained by the Project document coordinator
(Scouting and Feasibility study phase) and Document Controller (FED and Execution
stages).
6.4.1 All major and mega projects shall have a common project folder structure (L1-L3) as per
the appendix. For minor projects it is compulsory only L1 and L2, but it is recommended to
have also the L3 (as per Appendix). Additional levels of detail will be added depending on
project size, scope, other specifics
Date : 25 04 2016
6.4.3 Level 2 will match the key groups of Stages deliverables, and will include additional folder
for General Project management, (see Appendix)
6.4.4 Level 3 will follow the Stages deliverables, and shall be adjusted in order to fit the needs of
the project (see recommendation of structure in Appendix; to be modified in practice if
there is strong reasoning for further customization)
6.4.5 Access to folders will be based on user rights (on file server, web access, etc) to be
controlled by the Document Controller
6.5.1 All original documents Shall be stored in a central location within each office, and shall be
administered by Document Controller (DC).
6.5.2 All electronically stored data on the electronic filing system shall be backed up on a
regular basis (typically weekly) with storage of backup media on site and off site.
6.5.3 Where project documentation stored on computer local drives where a Local Area
Network (LAN) connection is not available, the DC is responsible for backing up all data
onto a portable drive at the end of each business week (as a minimum) but ideally at the
end of each business day. Previous back-up records can be over-written by the new
back-up records. For security reasons, if back-up is manual, it is recommended that
always will be maintained the last 5 back-ups
6.5.4 Where data is commercially/technically sensitive, this data shall be password protected or
restricted insofar as is achievable with the particular software. Backups shall be securely
stored
6.5.5 The type of the data will determine the security measures necessary. For example,
commercially sensitive information shall be retained either under lock and key, or
password protected in the case of electronic data. Where information loss would be
critical, additional security measures such as fire-proof cabinets shall be utilized
Date : 25 04 2016
6.6.1 The close out process should be performed as per the dedicated procedure MPRP-1-PJ-
407 - Project Close-Out. A project close out team shall be established to govern & track
the transfer & transmission of deliverables from contractor to Marafiq. Document Controller
shall become key members of the team by tracking & reporting the progressive status of
deliverables
6.6.2 During Close Out phase all project documentation shall be transmitted to TSD for
document management & archiving
6.6.3 Final versions of all key project deliverables including engineering drawings, data sheets,
spreadsheets, drawing register, manuals, procedures, tests & commissioning records,
QA/QC records, electronic correspondence, Subcontracts, accounting ledgers, facsimile
and process charts, shall be prepared in one of the following formats approved by Marafiq:
6.6.4 All electronic files to be handed over shall be scanned by the latest available virus
software before submittal to Marafiq
6.6.5 The compression and decompression programs including all necessary program
documentation shall accompany drawings handed over in compressed form.
Date : 25 04 2016
7 Documents Referred
MCFP-1-IM-001 - Document Control Procedure
MVFP-1-AC-015: Fixed Asset & Capital Expenditure Procedure Capitalization of Fixed Assets
8 Materials/Equipment Needed
N/A
Date : 25 04 2016
9 Forms/Format/Flowcharts Used
9.1 Flowchart
Date : 25 04 2016
9.2 Forms
Date : 25 04 2016
10 Annexes Attached
DISCIPLINE CODE
Code Description
A Architectural (building)
C Civil & Landscaping
D Document Control
E Electrical
F Fire Protection & HSE
G General
H Heating, Ventilation, Air-conditioning (HVAC)
I Instrumentation and controls
L Piping
M Mechanical
N Project Management
O Operation & Maintenance
P Process engineering
R Procurement
S Structural
T Telecom
U Infrastructure & utilities
W Project Services
Z Construction
Date : 25 04 2016
DOCUMENT TYPE
Code Description
1 Drawings / Diagrams / Details
2 Specifications
3 Schedules / Lists
4 Data Sheets
5 Calculations
6 Reports
7 Manuals
Date : 25 04 2016
L1 L2 L3
Stage 1-7 (same L2 and L3 for all stages)
Date : 25 04 2016