Documents and Communications Codification Procedure

Contratista/Contractor:
DOCUMENTS AND COMMUNICATIONS CODIFICATION

PROCEDURE
Código Cliente Emisor/Issuer:
Rev 01 Client Code TSKD-002549-00-DPR-PO-0001
Fecha Código Interno TSK TSKD-002549-00-DPR-PO-0001
11/05/23 TSK Internal Code
Date
Código Suministrador
Pg. 1 / 15 -
Supplier Code
CLIENTE/CLIENT
Compañía de Electricidad de San Pedro de Macorís, S.A. (ENERGAS)
PROYECTO/PROJECT
ENERGAS COMBINED CYCLE POWER PLANT- UNIT 40 PROJECT
SAN PEDRO DE MACORÍS – REP. DOMINICANA
SELLOS/STAMPS:
01 SECOND ISSUE SAD CCC AAD 12/05/23

00 FIRST ISSUE SAD CCC AAD 09/03/23
DESCRIPCIÓN EMITIDO COMPROBADO APROBADO FECHA
REV
DESCRIPTION ISSUED CHECKED APPROVED DATE
Este documento no puede ser reproducido ni comunicado a terceros sin la autorización de TSK y está sujeto a confidencialidad.
This document must not be copied or disclosed to third parties without TSK consent and is subject to confidentiality.
ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

PROCEDURE
Date
Pg. 2 / 15 -
Supplier Code
REGISTRO DE CAMBIOS/DOCUMENT HISTORY
FECHA SECCIONES / PÁRRAFOS AFECTADOS RAZONES PARA CAMBIO

REV
DATE SECTIONS / PARAGRAPHS AFFECTED REASON/S FOR CHANGE/MODIFICATION
00 09/03/23 ALL FIRST ISSUE
01 12/05/23 Indicated sections NEW ISSUERS, DISCIPLINES AND DOC TYPES

PROCEDURE
Date
Pg. 3 / 15 -
Supplier Code
TABLE OF CONTENTS
1 INTRODUCTION .............................................................................................................................. 5
1.1 GENERAL PROJECT DESCRIPTION ............................................................................................. 5
1.2 PURPOSE................................................................................................................................. 5
1.3 CONFIDENTIALITY .................................................................................................................... 5
2 DOCUMENTATION CODING PROCEDURE ......................................................................................... 6
2.1 CODIFICATION ......................................................................................................................... 6
2.2 FILE NAMES ........................................................................................................................... 11
2.2.1 DOCUMENTS ISSUED BY TSK ................................................................................................... 11
2.2.2 VENDORS ................................................................................................................................. 11
2.2.3 TSK COMMENTS ...................................................................................................................... 12
2.2.4 CLIENT COMMENTS ................................................................................................................. 12
2.3 COMMUNICATIONS ............................................................................................................... 13
2.4 AUTHOMATIC NOTIFICATIONS ............................................................................................... 13

PROCEDURE
Date
Pg. 4 / 15 -
Supplier Code
LIST OF TABLES
Table 1. Code structure ..................................................................................................................................... 6
Table 2. Issuer Code........................................................................................................................................... 6
Table 3. Project Code......................................................................................................................................... 7
Table 4. Area Code............................................................................................................................................. 7
Table 5. Discipline Code..................................................................................................................................... 8
Table 6. Document Type .................................................................................................................................... 8
Table 7. Allocation of sequential numbers by discipline ................................................................................. 10
Table 8. Breakdown of sequentials in civil and process disciplines ................................................................ 11
Table 9. Status codes ....................................................................................................................................... 12
Table 10. Communications structure code ..................................................................................................... 13
Table 11. Notifications code structure ............................................................................................................ 14

PROCEDURE
Date
Pg. 5 / 15 -
Supplier Code
1 INTRODUCTION
1.1 GENERAL PROJECT DESCRIPTION
ENERGAS has decided to build and operate a new combined cycle in San Pedro de Macorís, República
Dominicana. TSK has been awarded as EPC contractor for this project.
The New Power Plant proposed basically consists in the installation of one 1x1 multi shaft unit, consisting of:
• One (1) Gas Turbine (GT), General Electric (GE) 6F.03 model and corresponding generators, 60 Hz.
• One (1) Dual Pressure water/steam cycle with one (1) Heat Recovery Steam Generator (HRSG), its
auxiliaries, exhaust stack and silencer.
• One (1) Steam Turbine and Generator (STG), 60 Hz.
• One (1) Surface Steam Condenser for the steam turbine exhaust steam.
• One (1) Cooling Tower as Main Cooling Water System
• All the rest of related BOP systems, including all auxiliary Mechanical, Electrical and Control
equipment necessary.
1.2 PURPOSE
The purpose of this document is to establish the procedure to be followed for the codification and
management of documents and communications issued throughout the life of the project.
1.3 CONFIDENTIALITY
Any document exchanged, whether in digital format or on paper, (including this specification) shall be kept
in strict confidentiality by the VENDOR. It is strictly forbidden to extract or reproduce any part of said
documents

PROCEDURE
Date
Pg. 6 / 15 -
Supplier Code
2 DOCUMENTATION CODING PROCEDURE

2.1 CODIFICATION
The document codes shall follow the structure below:
Table 1. Code structure
PROJECT
ISSUER AREA DISCIPLINE DOC TYPE NUMBER
CODE
CCCC - PPPPPP - AA - DDD - TT - NNNN
Where:
• EEEE: is the issuer codified according to Table 2. Issuer Code

• 002549: Is the reference code for the Project. This is common to every document. Table 3. Project
Code
• AA: This refers to the project areas described in Table 4. Area Code
• DDD: This code refers to the discipline. The potential disciplines are listed in Table 5. Discipline Code
• TT: This refers to the document type to which the document belongs to as per Table 6. Document
Type
• YYYY: This is a sequential number given to every document belonging to the same area, discipline,
and document type.
Table 2. Issuer Code
CODE ISSUER
ENERGAS ENER
PROJECT MANAGEMENT TSKG
ENGINEERING TSKI
E&IC TSKE
CONSTRUCTION TSKC
OPERATION, MAINTENANCE & COMMISSIONING TSKS
TECNOLOGY TSKT

PROCEDURE
Date
Pg. 7 / 15 -
Supplier Code
CODE ISSUER
QUALITY TSKQ
HSE TSKH
DOCUMENTATION TSKD
PURCHASING TSKP
LOGISTICS TSKL
ACTIVATION TSKA
MATERIALS TSKM
SUBCONTRACTORS TSKB
SCHEDULING & COST CONTROLLING TSKO
VENDORS SXXX(1)
SUBCONTRACTORS CXXX(1)
s(1): consecutive number assigned to each vendor or contractor (starting with 001) after the award
Table 3. Project Code
PROJECT CODE
CCC ENERGAS 40 UNIT 002549
Table 4. Area Code
AREA CODE
GENERAL 00
HV EQUIPMENT 10
NEW SUBSTATION 11
EXTENSION OF EXISTING SUBSTATION 12
PLANT INTERCONNECTION HV LINE 13
NEW SUBSTATION INTERCONNECTION HV LINE 14

PROCEDURE
Date
Pg. 8 / 15 -
Supplier Code
Table 5. Discipline Code
DISCIPLINE CODE
PROJECT MANAGEMENT DPR
QUALITY QAC
SAFETY AND ENVIRONMENTAL STANDARDS HSE
PROCESS PRC
CIVIL WORKS, STRUCTURE & ARCHITECTURE CSA
MECHANICAL MEC
PIPING TUB
ELECTRICAL ELC
INSTRUMENTATION INS
CONTROL CTR
LOGISTICS LOG
COMMISSIONING PEM
PERFORMANCE TEC
CONSTRUCTION CON
OPERATION AND MAINTENANCE OYM
SCHEDULING PLN
Table 6. Document Type
DOCUMENT TYPE CODE

MINUTES AC
RELEASES FOR SHIPMENT AE
CALCULATIONS CL
CERTIFICATES CR
CLARIFICATION REQUEST DC
ELECTRICAL DIAGRAMS AND SKETCHES DE
PROCESS DIAGRAMS DG
INSTRUMENTATION AND CONTROL DIAGRAMS DI
MECHANICAL DIAGRAMS DM

PROCEDURE
Date
Pg. 9 / 15 -
Supplier Code
DOSSIERS DO
DESIGN BASIS DS
MECHANIC STRUCTURE EM
TECHNICAL SPECIFICATIONS ET
TECHNICAL EVALUATIONS EV
DATA SHEETS HD
TRANSMITTAL SHEETS HT
REPORTS IN
LETTERS LR
LISTS LT
DESCRIPTIONS ME
CONCRETE BIM MODELS MH
STEEL STRUCTURE BIM MODELS MS
ARCHITECTURE BIM MODELS MA
BUILDING FACILITIES BIM MODELS MI
EARTHWORKS AND UNDERGROUND
NETWORKS BIM MODELS MT
GENERAL BIM MODELS MG
EMAILS ML
MANUALS MN
NON-CONFORMITIES NC
TECHNICAL NOTES NT
CHANGE ORDERS OC
PLANNING PA
CIVIL DRAWINGS PC
ELECTRICAL DRAWINGS PE
GENERAL DRAWINGS PG
INSTRUMENTATION AND CONTROL DRAWINGS PI
PLANS PL
MECHANICAL DRAWINGS PM
PROCEDURES PO
PROTOCOLS PR
PROCEDURE
Date
Pg. 10 / 15 -
Supplier Code
PIPING DRAWINGS PT
CLAIM RC
REQUEST FOR INFORMATION RI
REQUEST FOR QUOTATION RQ
REQUEST FOR PURCHASE RP
CHANGE REQUEST SC
SITE INSTRUCTION ST
STANDARDS SW
MISCELLANEOUS VV
In general, and whenever possible, the same sequential number shall be assigned to documents of the same
discipline which refer to a common content
Table 7. Allocation of sequential numbers by discipline
DISCIPLINE DOCUMENT TYPE CONTENT

CSA CL, PC, LT, 3D Calculations*, drawings and BOQs
CTR DI, LT, NT Diagrams, lists, functional descriptions
PRC CL, DG, DI, LT Calculations, PFDs, PIDs, Line Lists
ELC ET, LT, HD, PE, DE Specification, lists, data sheets, drawings and diagrams
INS ET, EV, RQ, RP Specification, Technical evaluations and purchase requests
MEC ET, EV, HD, RQ, RP Specification, technical evaluations and purchase requests
TUB ET, EV, LT, HD,RQ, RP Specification, technical evaluations, MTOs, purchase requests
(*) Whenever foundations and structure shall keep together in the same document, it shall take the
foundations code.
NOTE 1: I&C documents shall have the same sequential number as process documents belonging to
the same system
NOTE 2: for those equipments which require a specific quality specification, it shall have the same
sequential number as the technical specification issued by the engineering team.
Civil documents shall be broken down as follows.

PROCEDURE
Date
Pg. 11 / 15 -
Supplier Code
Table 8. Breakdown of sequentials in civil and process disciplines
DISCIPLINE NUMBER CONTENT

000X General documents (to be allocated 10 by 10)
020X Underground network
030X Buildings
CSA/PRC 1XXX Fuel Gas
2XXX W-S Cycle
3XXX Auxiliary Equipments
4XXX Electrical Equipments
2.2 FILE NAMES

2.2.1 DOCUMENTS ISSUED BY TSK
Files shall be named according to the project code given in the Master Document List and followed by revision
number (and version if applicable).
EEEE-002549-AA-DDD-TT-YYYY-RR-V
• REVISIONS (RR): Revisions shall be numerical starting by 00. To keep traceability, each submission of
a document or drawing shall correspond to a new revision that shall be recorded on the “changes
history record” and clearly identified by revision clouds.
• VERSIONS (V): Versions shall be alphabetical starting by A. They shall be used only for engineering
documents to identify internal versions.
Example:
Revision one of the Data Sheet for a mechanical equipment, issued by the Mechanical Engineering
Department, being this document the second Data Sheet of the Mechanical Discipline:
TSKI-002549-02-MEC-HD-0002-01-A
2.2.2 VENDORS
Suppliers and subcontractors do not work with versions, so their files shall be named as follows:
SXXX-002549-AA-DDD-TT-YYYY-RR

PROCEDURE
Date
Pg. 12 / 15 -
Supplier Code
• REVISIONS (RR): Revisions shall be numerical starting by 00. To keep traceability, each submission of
a document or drawing shall correspond to a new revision that shall be recorded on the “changes history
record” and clearly identified by revision clouds.
2.2.3 TSK COMMENTS
Comments shall be identified in the file name, including the status acronym after the code and revision
number (and version if applicable).
Table 9. Status codes
REVIEW STATUS CODE
REVIEWED WITHOUT COMMENTS RSC
REVIEWED WITH COMMENTS RCC
INFORMATION INF
REJECTED RZD
For example:
Supplier document approved by TSKI
S001-002549-00-AAA-BB-XXXX-00_RSC
2.2.4 CLIENT COMMENTS
For documents reviewed by the client, comments shall include the editor before the status. Responses to
client shall be codified in the same way.
For example:
Document issued by TSK reviewed by Client with no comments.
TSKI-002549-00-AAA-BB-XXXX-00-A_ENER_RSC_00
TSK replies to CLIENT comments, when applicable, shall be coded as follow:
TSKI-002549-00-AAA-BB-XXXX-00-A_TSKI_RCC_00
Whenever the CLIENT wishes to reply to TSK, the file from the client shall be coded as follows:
TSKI-002549-00-AAA-BB-XXXX-00-A_ENER_RCC_01

PROCEDURE
Date
Pg. 13 / 15 -
Supplier Code
2.3 COMMUNICATIONS
Official communications shall be written in English.
Communications between the parties will be codified to keep traceability.
Table 10. Communications structure code
PROJECT SEQUENTIAL
ISSUER RECIPIENT DATE TYPE SUBJECT
CODE NUMBER
002549 - CCCC - CCCC - AAAAMMDD - NNNN - TD : XXXX
Where:
• PROJECT: 002549
• ISSUER: as per Table 2. Issuer Code
• RECIPIENT: as per Table 2. Issuer Code
• DATE: AAAAMMDD format
• SEQUENTIAL NUMBER: numbers shall be assigned to each communication between the same ISSUER
and RECIPIENT starting by 0001.
• TYPE: Letter (LR) or Email (ML)
• SUBJECT: Brief description of the content
E.g. Call for the Kick-off meeting
002549-TSKG-ENER-20230303-0001-ML: KoM
Communications shall be sent to the people included in the matrix distribution agreed during the KoM.
Responses shall not be recodified.
2.4 AUTHOMATIC NOTIFICATIONS
All documentation issues and comments recordings will be managed through ENOVIA, which will launch daily
notifications reporting the documents that have suffered changes in their status, grouping them by FOLDER
and ISSUER/RECIPIENT.

PROCEDURE
Date
Pg. 14 / 15 -
Supplier Code
Engineering folder will be broken down into the different disciplines and/or areas to ensure the correct
distribution of the workflows.
Notifications are sent from plm@grupotsk.com by email, every morning at 7:00 CET (Central European Time).
Subject codification shall be coded as follows:
Table 11. Notifications code structure
PROJECT SEQUENTIAL
FOLDER ISSUER RECIPIENT DATE
CODE NUMBER
PPPPPP - AAA - CCCC - CCCC - AAAAMMDD - NNNN
Where:
• 002549: reference code for the Project. It is fixed in all documents.

• DDD: folder where documents are located
• EEEE: is the issuer code according to Table 2. Issuer Code
• RRRR: is the recipient code according to Table 2. Issuer Code
• YYYYMMDD: is the communication date. The order to be followed will be always YYYY (year) MM
(month) DD (day).
Notifications shall contain at least the project code, title, revision, and status. If necessary, they will include
other information required such as “client issue purpose”.
E.g.: first issue of documents coding procedure

PROCEDURE
Date
Pg. 15 / 15 -
Supplier Code
“Client code” will remain empty when it is the same as “internal code”.

Documents and Communications Codification Procedure

Uploaded by

Document Information

Original Title

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

Documents and Communications Codification Procedure

Uploaded by

Copyright:

Available Formats

Contratista/Contractor:

DOCUMENTS AND COMMUNICATIONS CODIFICATION

ENERGAS COMBINED CYCLE POWER PLANT- UNIT 40 PROJECT

SAN PEDRO DE MACORÍS – REP. DOMINICANA

01 SECOND ISSUE SAD CCC AAD 12/05/23

ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

REGISTRO DE CAMBIOS/DOCUMENT HISTORY

FECHA SECCIONES / PÁRRAFOS AFECTADOS RAZONES PARA CAMBIO

00 09/03/23 ALL FIRST ISSUE

01 12/05/23 Indicated sections NEW ISSUERS, DISCIPLINES AND DOC TYPES

ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

1.1 GENERAL PROJECT DESCRIPTION ............................................................................................. 5

1.3 CONFIDENTIALITY .................................................................................................................... 5

2 DOCUMENTATION CODING PROCEDURE ......................................................................................... 6

2.1 CODIFICATION ......................................................................................................................... 6

2.2 FILE NAMES ........................................................................................................................... 11

2.2.1 DOCUMENTS ISSUED BY TSK ................................................................................................... 11

2.2.2 VENDORS ................................................................................................................................. 11

2.2.3 TSK COMMENTS ...................................................................................................................... 12

2.2.4 CLIENT COMMENTS ................................................................................................................. 12

2.3 COMMUNICATIONS ............................................................................................................... 13

2.4 AUTHOMATIC NOTIFICATIONS ............................................................................................... 13

ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

Table 1. Code structure ..................................................................................................................................... 6

Table 2. Issuer Code........................................................................................................................................... 6

Table 3. Project Code......................................................................................................................................... 7

Table 4. Area Code............................................................................................................................................. 7

Table 5. Discipline Code..................................................................................................................................... 8

Table 6. Document Type .................................................................................................................................... 8

Table 7. Allocation of sequential numbers by discipline ................................................................................. 10

Table 8. Breakdown of sequentials in civil and process disciplines ................................................................ 11

Table 9. Status codes ....................................................................................................................................... 12

Table 10. Communications structure code ..................................................................................................... 13

Table 11. Notifications code structure ............................................................................................................ 14

ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

2 DOCUMENTATION CODING PROCEDURE

The document codes shall follow the structure below:

Table 1. Code structure

CCCC - PPPPPP - AA - DDD - TT - NNNN

• EEEE: is the issuer codified according to Table 2. Issuer Code

Table 2. Issuer Code

PROJECT MANAGEMENT TSKG

OPERATION, MAINTENANCE & COMMISSIONING TSKS

ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

SCHEDULING & COST CONTROLLING TSKO

Table 3. Project Code

Table 4. Area Code

EXTENSION OF EXISTING SUBSTATION 12

PLANT INTERCONNECTION HV LINE 13

NEW SUBSTATION INTERCONNECTION HV LINE 14

ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

Table 5. Discipline Code

Table 6. Document Type

DOCUMENT TYPE CODE

ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

Table 7. Allocation of sequential numbers by discipline

DISCIPLINE DOCUMENT TYPE CONTENT

Civil documents shall be broken down as follows.

ENERGAS COMBINED CYCLE POWER PLANT - UNIT 40 PROJECT Version A

Table 8. Breakdown of sequentials in civil and process disciplines

DISCIPLINE NUMBER CONTENT

2.2 FILE NAMES