0% found this document useful (0 votes)
36 views12 pages

Document Coding Procedure for Solar Project

This document outlines the coding procedure for documents related to the Jizzakh/Samarkand 220MWac Solar Power Project in Uzbekistan. It divides documents into three parts - correspondences, design documents, and general documents - and provides coding structures for each. Correspondences like letters and meeting minutes will be coded by project, issuer, receiver, document type, and sequential number. Design documents will strictly follow the PMC's coding requirements. General documents will be coded by project, discipline, document type, and sequential number. The coding procedures are meant to systematically organize the large volume of documentation for the substantial solar power project.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
36 views12 pages

Document Coding Procedure for Solar Project

This document outlines the coding procedure for documents related to the Jizzakh/Samarkand 220MWac Solar Power Project in Uzbekistan. It divides documents into three parts - correspondences, design documents, and general documents - and provides coding structures for each. Correspondences like letters and meeting minutes will be coded by project, issuer, receiver, document type, and sequential number. Design documents will strictly follow the PMC's coding requirements. General documents will be coded by project, discipline, document type, and sequential number. The coding procedures are meant to systematically organize the large volume of documentation for the substantial solar power project.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Project:

Jizzakh/Samarkand 220MWac Solar Power Project

Owner: PMC: EPC Contractor:


Main consultant

Dongfang Electric
“NUR JIZZAKH SOLAR
GOPA - International International Corporation
PV”PE LLC -M
Energy Consultants GmbH - DEC

Sub-consultant

JURU ENERGY

CONSULTING LLC

Document Information

Document Title Document Coding Procedure

Masdar Document Number

DEC Document Number NJS/SKD-EPC-PMC-TRA-00001

Rev. 02

Date Submitted 2023-2-3

Prepared by Name Xiao Hong Sign

Approved by Name Zhu Bo Sign

Issued Purpose For Review For Info



Last Rev. Reply Date Status Code 2

Document Revision Box

Rev. Date Originator Approver Description

01

02

03
Document Coding
Procedure
Dongfang Electric International Corporation

Jizzakh/Samarkand 220MWac Solar Power Project

NJS/SKD-EPC-PMC-TRA-00001

2022-11-07
Table of Contents
1. Introduction.................................................................................................................................................4
2. Document coding Procedure for Jizzakh/Samarkand 220MWac Solar Power Project.............................4
2.1 Correspondences..............................................................................................................................5
2.2 Design Documents............................................................................................................................5
2.3 General Documents...........................................................................................................................7

JZK/SMK-EPC-PMC-PM-DC-001 Document Numbering Procedure


1. Introduction

The purpose of this document is to define and introduce the documents coding procedure to be
used for various kinds of documents submitted by the EPC Contractor (Dongfang Electric
International Corporation, DEC) to the Owner (“NUR JIZZAKH SOLAR PV”PE LLC-M) and the PMC
(GOPA - International Energy Consultants GmbH-GOPA) for review or for information only. In this
Project, the Electrical Document Management Systems (EDMS) are required to be used for
submissions.
Email or any other system/software pointed by the PMC, to be used for the submissions of the overall
documents for the Jizzakh/Samarkand 220MWac Solar Power Plant, including the PV part and the PIF
part.
In this document, a detailed description of the documents coding procedure for the project
management documents and design documents submitted by DEC will be given for the Jizzakh /
Samarkand 220MWac Solar Power Plant. For the design documents, due to the coding procedure
shall strictly follow PMC’s requirements.

2. Document Coding Procedure for Jizzakh/Samarkand 220MWac


Solar Power Project

The documents for Jizzakh/Samarkand 220MWac Solar Power Plant, including the PV part and the
PIF part, will be divided into three parts.

The first part is correspondences (letter,MOM and report etc.), including:

 Letters between the EPC Contractor (DEC) and the Owner (M);
 Letters between the EPC Contractor ((DEC) and the Owner’s PMC (GOPA/JURU);
 MoMs for Jizzakh/Samarkan 220MWac Solar Power Plant.

The second part is design and technical documents, including:

 Drawings originated by the EPC Contractor’s design institutes or manufacturers, including all
kinds of drawings, calculation reports, lists and technical specifications produced by the
EPC Contractor or his sub-contractors in civil, electrical and other scopes.

The third part is general documents, including:

 General documents originated by the EPC Contractor or his sub-contractors, such as


project management documents, quality documents, HSE documents, schedule
documents, etc.

For correspondences, design and general documents, the numbers will be defined and used:

 Document Number to the EPC Contractor, defined by the rules given by the Owner/PMC;
4/8
 Contractor Document Number, defined by the EPC Contractor based on this document
control system’s rules.

2.1 Correspondences
A Correspondence Number is an alphanumerically code subdivided into 5 Ordinal Sections and having
the following appearance. All official communications between DEC (EPC Contractor), GOPA/JURU
(PMC) and “NUR JIZZAKH / SAMARKAND SOLAR PV” PE LLC shall be codified according to the
following codification procedure:

PPP-EEE-RRR-TOD-NNNNN

Where:
 PPP: Project Name Abbreviation, such as NJS / SKD
 EEE: means the issuer codified according to table 2.1.1;
 RRR: means the receiver codified according to table 2.1.1;
 TOD: means the type of document, according to table 2.1.2;
 NNN: represents the sequential number of 5 digits, from 00001 to 99999
 Subject: a brief description of the subject of the communication shall be given.
ISSUER OR RECEIVER NAME CODE
“NUR JIZZAKH SOLAR PV” FE
LLC / “NUR SARMARKAND JVC
SOLAR PV” FE LLC
GOPA/JURU (PMC) PMC
DEC(EPC Contractor) DEC
Table 2.1.1 Issuer and receiver codification
TYPE OF DOCUMENT CODE
Transmittal TRA
Minutes of Meeting MOM
Letter LTR
Weekly Progress Report WPR
Monthly Progress Report MPR
Comment Resolution Sheet CRS
Material/Equipment Inspection Reports M/EIR
Technical Query Requests TQR
Non-Conformity Report NCR

Table 2.1.2 Type of document

5/8
2.2 Site Correspondences
All official communications between DEC (EPC Contractor), GOPA/JURU (PMC) and “NUR JIZZAKH /
SAMARKAND SOLAR PV” PE LLC shall be codified according to the following codification procedure:
PPP-EEE-RRR-SSS-QQQ-TOD-MM-NNN (SKD-DEC-PMC-ZC-CVL-RFI-00-0001)
Where:
 PPP: Project Name Abbreviation, such as NJS / SKD 2.1.1;
 EEE: means the Contractor codified according to table 2.1.1;
 RRR: means the receiver codified according to table 2.1.1;
 SSS: means the subcontractor codified according to table 2.1.1;
 QQQ: means the discipline codified according to table 2.1.2;
 TOD: means the type of document, according to table 2.1.2;
 MM: represents the buildings of 2 digits, from 01 to 99
 NNN: represents the sequential number of 4 digits, from 0001 to 9999
 Subject: a brief description of the subject of the communication shall be given.
ISSUER OR RECEIVER NAME CODE
“NUR JIZZAKH SOLAR PV” FE
LLC / “NUR SARMARKAND JVC
SOLAR PV” FE LLC
GOPA/JURU (PMC) PMC
DEC(EPC Contractor) DEC
PowerChina Hebei HB
Sinohydro SH
Doctor Energy DE
Sistronik ST
Zecca ZECCA ZC
Cc5 CC5 CC
General GN
Table 2.1.1 Issuer and receiver codification
TYPE OF DOCUMENT CODE
Request for Inspection RFI
ACT ACT
Material incoming control ACT MACT
Material Approval Request MAR
Material Request for Inspection MRI
Field Change Request FCR
Civil CVL
Electrical ELE
6/8
Mechanical MEC
Table 2.1.2 Type of document

Buildings Name CODE


General 00
Control Building 01
Fire-fighting pump house 02
Gate house 03
Fire water tanks 04
Autotransformer 05
Auxiliary transformer 06
Switchyard 220kV 07
SVG/Capacitor Bank 08
Oil pit 09
Oil-water separation system 10
Sewage treatment system 11
Artesian well with pump house 12
Diesel generator 13
Table 2.1.3 Buildings Identification

2.3 Design Documents

A Design Document Number is unique and has the following template:

PPP-EEE-YY-DDD-BBB-NNNN-AA

PROJECT NAME – ISSUER – LOCATION – DISCIPLINE-DOCUMENT TYPE-REVISION-


NUMBERING

EXAMPLE: NJS-DEC-SS-ELE-DRA-0001-01 (SKD-DEC-HV-CVL-CAR-0002-01)

Code Description Full List

PPP Name of Project NJS / SKD

EEE Issuer DEC

Location (2 alphanumerical) SS Step-up Station


YY - 00 is used unless defined HV Zone of High Voltage equipment
elsewhere and will apply to all PV Zone of PV Plant

7/8
GEN General Layout
CVL Civil
ELE Electrical
Code of Discipline (3
GEO Geology, Geophysics, Geotechnics
alphanumerical)
DDD SCA SCADA / Control System
- 00 is used unless defined
PVC Photovoltaic
elsewhere and will apply to all
MEP Mechanical Electrical pipeline (HVAC, Fire-
Fighting, Fire-Detection, Water supply, etc.)
EQP Equipment Document
CAR Calculations Report
REP Report
DRA Drawing
Document Type (3 alphanumerical) EML Equipment & Material List
BBB
SHT Data Sheet
TSP Technical Specification

Sequential Number (4 digits)


- 0000 is reserved to the list of
NNNN Range 0001-9999
documents
- 9xx is reserved for MOM and MEM

AA Revision Number (2 digits) Range 01-99

2.4 General Documents

For General Document Numbering are defined for general documents such as project management
documents, quality documents, HSE documents, schedule documents, etc.
A Design Document Number is unique and has the following template:

PPP - EEE -XXX -TYP - ZZZ - AA

Code Description Full List

PPP Project Identifier NJS/SKD


JVC - JV Company
EEE Document Originator GOPA/JURU - PMC
DEC - EPC Contractor

8/8
PRM - Project Management
ENG - Engineering
COM - Commercial
Code of Discipline (3 PRO - Procurement
alphanumerical) LOG - Logistics
XXX - 00 is used unless defined SCM - Site Construction Management
elsewhere and will apply to all COT - Commissioning & Testing
OPR - Operation & Maintenance
QAC - Quality Assurance / Control
HSE - Health / Safety / Security / Environmental

9/8
GEA - General Affair
PEP - Project Execution Plan
PIM - Permits & Interface Management

EMS - Equipment & Material Specification


FIN - Finance
MPR - Milestone Payment Request

PRO - Procurement Order


REN - Equipment & Material Release Notice

PAL Packing list


MAI Materials Inspection
DEN - Delivery Notice

CMP - Construction Management Plan


Document Type (3
PSC - Progress Schedule Control
TYP alphanumerical)
HUR - Human Resources
DOC - Document Control
MES - Materials & Equipment Storage

CTP - Commissioning & Testing Programme/Procedure


CTR - Commissioning & Testing Report

OMM - Operation & Maintenance Manual

QCP - Quality Control Plan


INP - Inspection Plan
FAR - Factory Acceptance Test Report
ITP - Inspection Test Plan
ITR - Inspection Test Report
CER - Certificate
HMP - HSE Management Plan
SOS - Security of Site

10/8
Sequential Number (3 digits)
- 000 is reserved to the list of
ZZZ documents Range 001-999
- 9xx is reserved for MOM and
MEM

Revision Number (optional) (2


AA Range 01-99
digits)

2.5 Classification and Status of Documentation

Each document shall be marked up with documentation classification (for approval, for review, or for
reference) based upon the classification guidelines as follows:

CLASS DESCRIPTION

The Contractor may not proceed with the Works that are the
Class 1 – Approval subject of the documentation until approval has been obtained
from the Company.

The Contractor may proceed with the Works but all Company
Class 2 - Review
comments shall be incorporated, and document shall be re-
submitted back for verification by Company.

Class 3 - Reference The Company reserves the right to comment, but the Contractor
Only may proceed with the Works that are the subject of the
documentation.

The document after review by PMC will be marked as below


CRS – Document code – Document name
In which, CRS means Comment Resolution Sheet issued by PMC.
Class 1 and class 2 documentation shall be returned with a return code clearly shown to indicate
the documentation status and the required action, as below:

Code Description

Reviewed and acceptable to issue as final with no modification or update required.


1
The Contractor retains responsibility for quality and accuracy of documentation.

Reviewed and acceptable to issue as final, subject to the identified modifications


and updates being included within the final revision. Where the Contractor
2 disagrees with, or requires clarification of the Company comment then these must
be resolved with the Company before proceeding with the next revision. The
Contractor retains responsibility for quality and accuracy of documentation.

Previously submitted comments have not been included. Documentation is to be


3
resubmitted with comments included.
11/8
Code Description

Documentation is significantly short of expected content or quality. Documentation


4
is rejected and to be resubmitted.

Documentation identified as not critical thus not reviewed, and shall only be
5 retained as for information. The Contractor retains responsibility for quality and
accuracy of documentation.

2.6 Document revisions

The following procedure will be followed to track the changes performed in the different documents,
depending on the document type as described hereinafter.
The identification of changes will be limited to the changes performed between two consecutive
revisions, that is, previous revision changes will not be tracked.
In drawings, changes will be identified with revision clouds.
For text documents, the sections with changes will be highlighted in blue color text or by equivalent
change tracking system. For lists, each list item will have an independent number and revision control cell.
Any change will be identified shading the cell in yellow and updating the revision status of the affected row
of data (when applicable). When a row of data needs to be deleted, the information will be crossed off and
will be identified shading the cell in red. In the next revision, the information will be erased but the item
number and revision will be kept.
In case of documents (f.i., drawings) that include a revision control sheet detailing the revision status of
each sheet of the document, each sheet that compose the document may have different revision.
In other cases, that is, documents with several sheets but without a revision control sheet, the whole
document will have only one revision.

12/8

You might also like