Attachment Xii.c - Project Document Numbering Procedure
Attachment Xii.c - Project Document Numbering Procedure
A. Aliyeva/ A. Trifonova/
02 09.12.2023 AFU Approved for Use M. Mirsaidov
M. Vorontsova E. Ali
A. Trifonova/
01 13.01.2022 AFU Approved for Use A. Krasnev M. Mirsaidov
E. Ali
A. Trifonova/
00 13.03.2022 AFU Approved for Use D. Aleksandrov M. Mirsaidov
E. Ali
REV DATE STATUS ISSUE PURPOSE ISSUED BY REVIEWED BY APPROVED BY
This document is property of the COMPANY and it shall not be disclosed to third parties, or reproduced, without permission of the COMPANY.
This document is tracked by Integrated Document Management System (IDMS). When it is printed, it shall be considered as “For information only”.
The controlled copy is the IDMS version, and thus, it is the document holder’s responsibility to make sure that the latest version is in use.
Block 10 Project
Disclaimer
Copying this document without the permission of LUKOIL Overseas Iraq Exploration B.V. is
not permitted.
CONTENTS
1. INTRODUCTION ................................................................................................................... 5
1.1. Overview ........................................................................................................................ 5
1.2. Purpose ........................................................................................................................... 6
1.3. Scope .............................................................................................................................. 6
1.4. Terms and Abbreviations ................................................................................................ 6
2. RESPONSIBILITIES............................................................................................................... 8
2.1 The Company Document Control (LOIE DCC) ............................................................. 8
2.2 Contractor representative ................................................................................................ 8
3. DOCUMENT NUMBERING .................................................................................................. 9
3.1 General .............................................................................................................................. 9
o Rules of Numbering ........................................................................................................ 9
o Document Types ............................................................................................................. 9
3.1.1 Engineering Document Numbering ................................................................................. 9
3.1.2 Vendor/Supplier Document Numbering ........................................................................ 11
3.1.3 Isometrics Document Numbering .................................................................................. 12
3.1.4 Technical Queries, Requests for Information Document Numbering ............................. 13
3.1.5 Transmittals Document Numbering............................................................................... 13
4. CODE DESCRIPTION .......................................................................................................... 16
4.1 Company Code................................................................................................................. 16
4.2 Contract Territory Code ................................................................................................... 16
4.3 Originator Code ............................................................................................................... 17
4.3.1 Company Originator Code ............................................................................................ 17
4.3.2 Contractor Originator Code ........................................................................................... 17
4.4. Production Facility Code ................................................................................................. 18
4.5 Production System Code .................................................................................................. 18
4.6 Discipline Code................................................................................................................ 19
4.7 Document Type Code....................................................................................................... 19
4.8 Document Sequential Number .......................................................................................... 20
4.9 Revision Number ............................................................................................................. 20
4.10 Revision Status............................................................................................................... 20
4.11 Document Language ...................................................................................................... 20
1. INTRODUCTION
1.1. Overview
LUKOIL Overseas Iraq Exploration B.V. was appointed to serve as Operator to conduct Petroleum
Operations under provisions of the Exploration, Development and Production Service Contract
(EDPSC) for Block 10 between Thi-Qar Oil Company, as the First Party, and LUKOIL Overseas
Iraq Exploration B.V., and INPEX SOUTH IRAQ, Ltd., as the Second Party.
Block 10 Contract Area is located in the southern part of Iraq at the junction of the provinces of
Thi-Qar and Muthanna. The Eridu oil field is located approximately 210 km to the northwest of the
city of Basra, 150 km to the west of the West Qurna-2 field, and 50 km to the west of the city of
Nasiriya.
The approximate local population living in Eridu oil field is 15,000 people. Most of the population
lives in the northern part of the oil field along Highway No. 8 Samawa – Nasiriya and on both sides
of the Euphrates River. Several villages and numerous separated settlements are located in the
territory of the field. The main center of population is Al Khidhir located to the northwest and Batha
to the northeast of the Eridu site.
Block 10 location map is shown in Figure 1-1.
1.2. Purpose
The Project Document Numbering Procedure (hereinafter the Procedure) establishes a
standardized approach for assigning unique identifiers to project documents within the Company's
document control system. This ensures systematic organization, traceability, and efficient document
management throughout the project lifecycle.
the Procedure defines the unique requirements to numbering of documentation developed by
LUKOIL Overseas Iraq Exploration B.V. (hereinafter Company) and Contractors issued in the
framework of project engineering documents of capital construction projects.
This Procedure does not cover the requirements to numbering of organizational-administrative,
legal and reference-information documentation.
1.3. Scope
The Procedure is a mandatory attachment to any contract, and its requirements shall be applied to
documents developed by either the Company or contractor(s), including documents generated by
subcontractors and third parties, in every project.
This Procedure is based on the Project Engineering Documentation Numbering Specification 8903-
0000-LOSC-00-000-IM-PP-00005 which is defines the unique requirements to numbering of
documentation of LUKOIL Overseas Group Companies developed and issued in the framework of
capital construction projects. The code directories listed in this procedure are applicable to IDMS
LUKOIL Co-Users. Modifying or duplicating existing codes is strictly prohibited, and any addition
of new codes must be approved with IDMS Co-User Company.
This Procedure is not intended to control the requirements of management, legal, contractual, and
financial documents numbering.
Name Description
Controlled Document A document registered in IDMS
Name Description
IDMS Integrated Documentation Management System
2. RESPONSIBILITIES
3. DOCUMENT NUMBERING
3.1 General
• In order to be managed correctly within IDMS, it is essential that each document is properly
identified in accordance with this Procedure;
• All Documents are identified by a set of attributes. The document numbering system consists
of mandatory and additional type of attributes. Mandatory attributes are required to establish
the electronic file name of the document, additional attributes are required to be added to
IDMS document registration form and if required to be shown within the document title
page or drawing title block;
• Document number is unique and attached to the document for the entire life of the document.
The number of cancelled or superseded document cannot be re-used.
o Rules of Numbering
The following rules must be adhered to identify each document:
• Codes will use Arabian numbers (0-9) or
• Upper Case Roman letters (A-Z).
• Codes are separated by a hyphen [-] symbol, defining fields.
• Codes have a fixed quantity of characters.
• Underscore [_] is used to separate the document number from the revision code.
• Use of any other letter, number and symbol is not allowed for document numbering.
• Uniqueness of document number is achieved by the means of combination of all mandatory
codes.
o Document Types
Corporation
1. 8019 4 (numeric) Always used Refer to 4.1
Code
Contract
2. 0191 4 (numeric) Always used Refer to 4.2
Territory Code
Company 4 (alpha or
3. LOIE Always used Refer to IDMS
Originator code alphanumeric)
12. Project stage FEED 10 (alpha) Always used Refer to sec. 4.12
Contract
13. 20 (alphanumeric) Always used
Number
Originator Specify
14. Document 50 (alphanumeric)
Number if required
Specify
15. Tag Numbers 50 (alphanumeric)
if required
The daily, weekly, monthly and other progress reports shall be numbered as shown above and issued
to Project Team for Information with IFI revision status and numeric revision codes (refer to
Attachment 6).
Corporation
1. 8019 4 (numeric) Always used Refer to 4.1
Code
Contract
2. 0191 4 (numeric) Always used Refer to 4.2
Territory Code
Production
3. 22 2 (numeric) Always used Refer to Attachment 1
Facility Code
01ABC4
5. PO number 12 (alphanumeric) Always used Contractor to provide
567890
Vendor
6. C01 3 (alphanumeric) Always used Refer to Attachment 5
Document Code
Sequence
7. NNNNN 5 (numeric) Always used Assigned by Contractor
Number
Specify
8. Sheet Number 001 3 (numeric) Assigned by Contractor
if required
Additional Attributes to be used for Transmittal only and not for Document Numbering
Corporation
1. 8019 4 (numeric) Always used Refer to 4.1
Code
Contract
2. 0191 4 (numeric) Always used Refer to 4.2
Territory Code
Production
3. 22 2 (numeric) Always used Refer to Attachment 1
Facility Code
Production
4. 540 3 (numeric) Always used Refer to Attachment 2
System Code
Document Type
5. DI 2 (alpha) Always used Refer to Attachment 4
Code
Train / Well
7. 00 2 (numeric) Always used Assigned by Contractor
Number
Contract
7. 20 (alphanumeric) Optional
Number
Contractor
8. Document 50 (alphanumeric) Optional
Number
Example of document number:
8019-0191-LOIE-XXXX-TE-12345
Transmittals shall be generated automatically by IDMS system.
4. CODE DESCRIPTION
Code Name
8019 LUKOIL Overseas Iraq Exploration B.V.
Code Name
0190 Block 10 Contract Area
0191 Block 10 Project, Eridu Oilfield Development/ Pilot Production
0192 Block 10 Project, Eridu Full Field Development
The comprehensive list of Company Originator codes is accessible on the IDMS Dashboard.
Code Name
LOIE LUKOIL Overseas Iraq Exploration B.V.
The Contractor is required to use the unique Originator Code for all documents within the scope of
the Contract (Service Order / Work Order / Call-Off).
Contractor Originator Code is assigned manually or automatically depending on Document Control
System by Contractor’s Engineering Department upon document creation.
In accordance with the Company's language policy, English (EN) is the primary language for all
documentation.
The Document Language is expressed using standard language codes "EN" for English.
Code Description
ALL Relevant to all Project Phases
Document is associated to the Construction phase of the project (As-built
AB
documents)
CM Pre-commissioning
CN Construction
CO Commissioning
CS Conceptual Stage
DD Detailed Design
EPC Engineering, Procurement and Construction
ESA Engineering Services Agreement
FEED Front End Engineering Design
MoC Management of Change
OP Operations
Pre-FEED Feasibility study
4.16 PO Numbering
PO Numbering refers to the systematic assignment of unique identifiers to Purchase Orders issued
by the Contractor for procurement purposes.
The primary purpose of PO Numbering is to establish a standardized method for identifying and
tracking individual Purchase Orders throughout the procurement process.
PO Numbers are assigned at the creation of each Purchase Order by the Contractor Procurement
Department. Each Purchase Order receives a unique identifier for easy reference.
PO Number is a twelve (12) character alpha numeric code which shall be provided by Contractor.
If Contractor’s SAP code is less than 12 characters, Contractor will prefix a zero in SAP to make
the code 12 characters (e.g. if Contractor’s SAP code is 12ABC6789 then Contractor shall use the
PO number as 00012ABC6789).
If Contractor’s SAP code is greater than 12 characters, then Contractor shall truncate the preceding
number to make it 12 characters (e.g. if Contractor’s SAP code is 1234ABC456789, then Contactor
shall use the PO number 234ABC456789).
At all times PO Number shall be fixed to 12 digits/characters only.
For easy identification of contractors managing multiple POs, PO number as per the structure below
may be used within the twelve (12) character alphanumeric code:
• Characters 1, 2 are reserved for “PO”;
• Characters 3, 4, 5, 6 are used for Originator Code to identify the Contractor managing the
PO;
• Characters 7, 8 are used to identify the Discipline Code of the PO;
Uncontrolled copy if printed Page 22 of 70
Block 10 Project
• Characters 9, 10, 11, 12 are used for PO number as per Contractor’s SAP code.
For example, PO number 1234 for Contractor ABCD related to Instrument discipline shall be as
follows: POABCDIN1234.
The assigned PO Number must be prominently displayed on all documents, communications, and
records related to the specific Purchase Order. This ensures accurate tracking and streamlined
management within the document control system.
The process of introducing a new code begins when there is a significant requirement, such as for
a facility code, system code, document type, discipline, or any other relevant attributes. Any
personnel, including Project Managers, Document Originators, or Department Managers, can
submit an email request for a new code to LOIE DCC. The request should be documented,
specifying the type of code, the required title, and its intended purpose.
In the context of utilizing a shared code catalog with LMEL, LOIE DCC is required to seek approval
from LMEL DCC when adding a new code. This rule applies reciprocally.
6 GENERAL REQUIREMENTS
Note: The column "Applicable for LOIE" is introduced only as a guidance to the user. The case
where "No" is mentioned now may be used at a later date, upon request to LOIE DCC.
The list of Production Facility Codes is dynamic, please refer to IDMS to view the latest Originator
codes.
11 Wells Yes
12 Cluster sites, well pads Yes
13 Automated gas metering unit No
14 Gathering station (satellite) No
15 Booster pump station Yes
16 Group pumping station No
17 Water distribution unit No
20 Oil and gas processing facilities Yes
71 Railways No
72 Motor roads No
AR Architecture Yes
CI Civil Yes
CM Pre-commissioning Yes
CN Construction Yes
CO Commissioning Yes
EV Environment Yes
EW Earthworks Yes
HI Heat insulation No
IX Index Yes
MK Marketing Yes
MS Mechanical - Static No
PC Process No
PN Planning Yes
PQ Procurement Yes
PR Public Relations No
SE Security Yes
TP Transportation Yes
WH Warehouse Yes
Document
Description
Type Code
AC Acceptance Certificate
AG Agenda
BD Basis of Design
BE Bid Evaluations
CC Calculation
CE Cost Estimate
CL Check List
CM Cause-effect Matrix
CO Close-out Report
CR Cost Report
CT Chart
CV Conversation Log
Document
Description
Type Code
DC Design Criteria
DG Design Guide
DO Drawings –Routing Plan, Cross-section (use for cables and line facilities)
DS Data Sheet
Document
Description
Type Code
DZ Defect Notice
EL Equipment List
EM E-mail
EX Executive summary
FC Flow Chart
FD Final Documentation
FM Form
FR Feasibility Report
FX Facsimile
GL Guidelines
HC Handover Certificate
IA Interface Agreement
ID Interface Dossier
IN Instruction
IX Index
Document
Description
Type Code
LS List / Table
LT Letter
ME Memo
ML (3 D) Model
MM Minutes of Meeting
MN Manual
MP Map
MS Method Statement
MX Matrix
NC Non-Conformance Report
NT Notes
PC Progress Certificate
Document
Description
Type Code
PG Program
PH Philosophy
PL Punch List
PM Permit / License
PN Plans
PO Purchase Order
PP Procedures
PQ Pre-Qualification
PS Purchase Specification
RF Reference
RG Register
RL Regulation
Document
Description
Type Code
RP Report / Investigation
RQ Requisition
RT Job Card
SD Systemization Definition
SG Strategies
SI Site Instruction
SK Sketch
SL Spares List
SP Specification
SQ Site Query
ST Standards
SW Scope of work
TC Test Certificates
TD Training Documents
TL Test Plan
Document
Description
Type Code
TN Technical Note
TP Test Procedures
TQ Technical Query
TR Technical Requirement
WI Work Instruction
WN Warranty Notification
WP Work Pack
The following is a list of items that can be requested at the post award stage to enable the review
for manufacture to be provided and will be determined by the Vendor Data Requirements List
(VDRL):
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Applicable for
Vendor Code Description
LOIE - YES / NO
Attachment 6.1 List of revision codes and document statuses for Project documents
Revision
Issue status Revision description Comments
code
IFR Issued for Review These codes are applied during all phases and used to record a document revision that
has passed the Contractor internal review and is submitted to Company, as well as
B, C, D
documents developed by Company which have passed the intra-disciplinary check
IFA Issued for Approval and issued for Company for review (IFR) or approval (IFA).
Issued for
IFI This code is used for documents issued to provide information.
Information
This code is applied to documents issued during Pre-FEED and FEED phases with
00, 01... AFD Approved for Design
review completed and all relevant comments incorporated.
Approved for This code is applied to documents issued during EPC phase with review completed
AFC
Construction and all relevant comments incorporated.
This code is applied to documents issued during EPC phase with review completed
Approved for
AFP and all relevant comments incorporated.
Procurement
This code is applied to documents issued by Company business units or Contractor
for applicable project deliverables. The code can be applied for final revisions of the
AFU Approved for Use
documents issued during Pre-FEED/ FEED/ DD/ EPC stages.
Issued for Enquiry The code is used for enquiries for information, technical queries and proposals to
IFE potential vendors of equipment, material, etc.
(Request)
These codes are applied when previously approved AFC/ IFI drawing or text
IFR Issued for Review
document requires to be re-issued for Review/ Approval e.g. in case the drawing/ text
0A, 0B, 0C document needs Company’s approval prior to being used on site for Construction
1A, 1B, 1C purpose. The next revision for these documents would be 01 if its 0A, 0B, 0C and 02
IFA Issued for Approval if its 1A, 1B, 1C.
This code is applied to documents issued after the AFC and prior to As-Built for
R1 RLE Redline verification on changes made on AFC.
This code is applied during EPC stage and used to record a revision of as-Built
X1, X2... AB As-Built Documents documents.
This code is used for documents which are no longer valid as they are replaced by
Y SUP Superseded one or several new documents.
Z CAN Cancelled This code is used for cancelled Documents which are no longer valid or required.
Attachment 6.2 List of revision codes and document statuses for Vendor documents
This code is applied to Vendor documents which are approved by Contractor but issued to
IFR Issued for Review Company for review/ comment (where required), these documents are agreed when the
Vendor creates the Vendor Document Schedule/ register (C01).
00, 01... This code is applied to Vendor documents that require company’s approval as agreed
IFA Issued for Approval between Company and Contractor in Vendor Document Schedule/register (C01), e.g. C01,
ITP, Data sheet P&ID.
IFI Issued for Information This code is used for Vendor documents to provide information.