dsf 1101401 436 6300 dcc prc 0302_a1 document control procedure

7/29/2019 DSF 1101401 436 6300 DCC PRC 0302_A1 Document Control Procedure

1/36


2/36

OFFSHORE PART OF THE STEFANI-ALIVERI NATURAL GAS HIGH

PRESSURE PIPELINEContract No. 436/11

DOCUMENT CONTROL PROCEDURE

DSF-1101401-436-6300-DCC-PRC-0302

REV. A1 Page 2 / 27

INDEX

INDEX ........................................................................................................................... 2AMENDMENTS AND REVISIONS .............................................................................. 41. INTRODUCTION .................................................................................................. 5

1.1 PROJECT OVERVIEW ..............................................................................................51.2 PIPELINE SYSTEM DESCRIPTION ..........................................................................5

2. DEFINITIONS AND ABBREVIATIONS .............................................................. 62.1 DEFINITIONS .............................................................................................................62.2 ABBREVIATIONS ......................................................................................................7

3. REFERENCE RULES, CODES AND STANDARDS .......................................... 73.1 CODES AND STANDARDS .......................................................................................73.2 OWNER DOCUMENTS ..............................................................................................73.3 CONTRACTOR DOCUMENTS ..................................................................................7

4. SCOPE OF DOCUMENT ..................................................................................... 85. RESPONSIBILITIES ............................................................................................ 86. PROCEDURE ...................................................................................................... 9

6.1 ORGANIZATION OF PROJECT FILES ...................................................................106.2 HANDLING OF CORRESPONDENCE DOCUMENTS ............................................106.3 HANDLING OF TECHNICAL DOCUMENTS ...........................................................106.4 HANDLING OF INCOMING TECHNICAL DOCUMENTS ........................................12

6.4.1 Logging of Technical Documents ....................................................................126.4.2 Deciding of the Distribution List and the Necessary Actions ...........................126.4.3 Distribution of Technical Documents ...............................................................126.4.4 Examination of Technical Documents ............................................................. 126.4.5 Contractors Evaluation of Comments on Technical Documents .................... 126.4.6 Updating of the MDR .......................................................................................136.4.7 Approval of the MDR .......................................................................................136.4.8 Handling of Master Documentation .................................................................13

6.5 HANDLING OF OUTGOING TECHNICAL DOCUMENTS ......................................13


3/36




DSF-1101401-436-6300-DCC-PRC-0302

REV. A1 Page 3 / 27

6.6 TECHNICAL DOCUMENTS REFERENCES ...........................................................136.6.1 Technical Documents Template ......................................................................136.6.2 Technical Drawing Template ...........................................................................146.6.3 Technical Documents Checks .........................................................................146.6.4 Documents development phases ....................................................................14

6.7 DOCUMENT NUMBERING ......................................................................................166.7.1 Codification for Technical Documents .............................................................166.7.2 Codification for Technical Specifications .........................................................176.7.3

Codification for Drawings .................................................................................17

6.7.4 ANNEX 1 Codes for Technical Documents and Technical Specifications

Subject (D) .......................................................................................................196.7.5 ANNEX 2 Codes for Technical Document Category (E) ..............................206.7.6 Forms Records .............................................................................................206.7.7 ANNEX 3 Codes for Drawings Category ......................................................216.7.8 Sheet Number (Drawings) ...............................................................................216.7.9 Revision Number .............................................................................................22

6.8 ELECTRONIC FILING OF DOCUMENTS................................................................226.9

FINAL DOCUMENTATION ......................................................................................23

7. ATTACHMENTS ................................................................................................ 24


4/36




DSF-1101401-436-6300-DCC-PRC-0302

REV. A1 Page 4 / 27

AMENDMENTS AND REVISIONS

Amendmentand revision

Date Page DescriptionProjectManager

A1 16/12/11 All Issued for Comments/Approval


5/36




DSF-1101401-436-6300-DCC-PRC-0302

REV. A1 Page 5 / 27

1. INTRODUCTION

1.1 PROJECT OVERVIEW

Public Natural Gas System Operator (DESFA) of Greece plans to install an N.G.T.S. Offshore NaturalGas Pressure Pipeline Varnavas-Karavos (Aliveri) whose purpose will be to supply natural gas to EvviaIsland.

The southern landfall in Attiki is named Varnavas while the previous names used for this landfall are Ag.

Apostoli or Grammatiko. The northern landfall in Evvia is named Karavos which is also indicated asAliveri landfall.

The maximum water depth along the 20 Gas Pipeline route is approx. 70m (MSL).

Figure 1-1 Natural Gas Pressure Pipeline Varnavas-Karavos route layout

1.2 PIPELINE SYSTEM DESCRIPTION

The offshore pipeline system consist of an 20 Natural Gas High Pressure Pipeline from the battery limitat Varnavas landfall, Attiki to the battery limit at Karavos landfall at Evvia island. The length of the new20 Natural Gas High Pressure Pipeline is about 14.2 km. The 20 Natural Gas High Pressure Pipeline

will consist of the two offshore sections, joined together offshore by Above Water Tie In method.

The Varnavas side offshore pipeline section commences at the KP -0.020 and finishes at AWTI Targetpoint at KP 13.360 in water depth of 31.2m. Along the pipeline section route, maximum water depth is70m.

The Karavos side offshore pipeline section commences at the KP 14.205 and finishes at AWTI Targetpoint at KP 13.360 in water depth of 31.2m. Along the pipeline section route, maximum water depth is31.2m.

Both pipeline sections will be manufactured from carbon steel with internal corrosion coating.


6/36




DSF-1101401-436-6300-DCC-PRC-0302

REV. A1 Page 6 / 27

2. DEFINITIONS AND ABBREVIATIONS

2.1 DEFINITIONS

The following definitions will be applicable in this document:

CONTRACTOR CONSORTIUM SAIPEM - ELTER

OWNER DESFA HELLENIC GAS TRANSMISSION SYSTEM OPERATOR S.A.

PROJECTDetailed Engineering, Procurement Of Materials & Construction Of TheOffshore Part Of The Stefani-Aliveri Natural Gas High Pressure Pipeline

PROJECT MANAGERMeans, respectively, the entity and the person appointed by OWNER toprovide project management services

SITE Means the lands, waters and other places on, under, in or through whichthe WORKS are to be performed including offshore installations, floatingconstruction equipment, vessels (including the area covered byapproved anchor patterns) design offices, workshops and places whereequipment, materials or supplies are being obtained, storied or used forthe purposes of the CONTRACT and any and all other places where thePERMANENT WORKS are to be executed and to which PLANT andMaterials are to be delivered and any other places as may be specifiedin the CONTRACT as forming part of the SITE.

SUBCONTRACTOR Selected Sub-Contractor to perform the work described in this document

SUPERVISING ENGINEER Means the company(ies) appointed by OWNER to carry out theConstruction Supervision duties, as well as the review of the detaileddesign issued by CONTRACTOR, as defined in Clause 2 hereof and inother CONTRACT DOCUMENTS

WORKS Means all CONTRACTORs services and supplies to be rendered andPLANT furnished in accordance with the CONTRACT including bothTEMPORARY WORKS and PERMANENT WORKS. Without limitation toitems set out in the CONTRACT DOCUMENTS, the WORKS includeeverything of whatever nature that is required for the achievement of theobjective of the CONTRACT, except for any exclusion that arespecifically itemized in the CONTRACT DOCUMENTS


7/36




DSF-1101401-436-6300-DCC-PRC-0302

REV. A1 Page 7 / 27

2.2 ABBREVIATIONS

DC Document Controller

MDR Master Document Register

PE Project Engineer

CPM Contractor Project Manager

CIM Contractor Installation Manager

CEM Contractor Engineering ManagerPMT Project Management Team

3. REFERENCE RULES, CODES AND STANDARDS

3.1 CODES AND STANDARDS

Ref Document Number Title

/1/ ISO 9001:2000 Quality management system - Requirements

3.2 OWNER DOCUMENTS


Specifications

/2/ APENDIX F Contractor Documents Requirements

/3/ DC-028Review/Approval of Contractors Technical Documentsusing Document Approval Form

3.3 CONTRACTOR DOCUMENTS



8/36




DSF-1101401-436-6300-DCC-PRC-0302

REV. A1 Page 8 / 27

Procedures

/4/ WI-SMS-PCON-100-E Documentation Management

/5/DSF-1101401-436-6300-QAC-MAN-0200

Overall Quality Manual

/6/DSF-1101401-436-6300-PRM-MAN-0100

Project Overview Manual

/7/ WI-SMS-INST-101-EOffshore Installation Engineering Documentsand Approval

/8/ WI-SMS-OOFS-111-EWork Instruction Offshore AS BUILTdocumentation

/9/ WI-SMS-INST-112-E Work Instruction Preparation of Drawings

/10/ WI-SMS-INST-104-EWork Instruction Installation methods / designcontrol

4. SCOPE OF DOCUMENT

This procedure describes the system for handling the documents concerning the OFFSHORE PART OFTHE STEFANI-ALIVERI NATURAL GAS HIGH PRESSURE PIPELINE PROJECT.

The objective is to guarantee the traceability, distribution, monitoring, disposal when necessary, and thesafekeeping of the Documents.

5. RESPONSIBILITIES

The DC is the focal point for the control of the Project Documentation during the whole project life.

The mission of the DC is to insure the implementation of Project Document Control within the Project as

follows:

To make available the applicable project documentation to the project team (including Owner

Subcontractors, Partners);

To manage all project documentation flow (paper and electronic)

The Document controller responsibilities include:

Assigning on the request of the originator, a unique identification number for all project documents(including Subcontractors documents);


9/36




DSF-1101401-436-6300-DCC-PRC-0302

REV. A1 Page 9 / 27

Listing and controlling Project documents number within the project MDR;

Only the duly endorsed documents (signed and approved by CONTRACTORs responsible persons)are sent to OWNER for review/approval;

That all transmittals are duly indentified, numbered and filed ;

Issuing Transmittals;

Ensures that the MDR is updated and that transmittals and reports are issued embracing alldocuments generated in-house and by Vendor/Subcontractors or Third Parties during the ProjectLife (Engineering documents, Project Procedures, Queries, Vendor documents, OWNER) ;

That the MDR is updated on daily basis with the support of the PMT and available on the Projectdrive in the last revision;

All documents are available to CONTRACTOR interested personnel, at any utilization point ;

To upload all the issued documents on the FTP server that CONTRACTOR has set up in order toexchange the Project documentation with the OWNER, or to send all the documents and transmittalsby e-mail, and to send all the transmittals by fax;

Information flow within the Project Team about documents status;

Ensuring the collection of final AS BUILT and transmission to OWNER;

To alert of any delays in pending documentation.

ProjectTeam shall comply with this procedure and shall assist the DC in number assignment.

6. PROCEDURE

The project Document Control System includes:

receipt;

issuing;

numbering

logging;

distribution;

Document flowchart is shown in chapter 6.3.

All incoming and outgoing transmittals and documents shall be transmitted at the following address:

Mr. Giorgio Danieli

Contractor Project Manager

e-mail: [email protected]


10/36




DSF-1101401-436-6300-DCC-PRC-0302

REV. A1 Page 10 / 27

Mrs. Lorena Jerkovic

Document Controller

51000 Rijeka, A. Colonnella 2, Croatia

Tel.: 00 385 51 651 908

Fax: 00 385 51 651 940

e-mail: [email protected]

6.1 ORGANIZATION OF PROJECT FILES

The CPM in collaboration with the DC shall establish the list of the incoming and outgoing files, and therelated logs:

for the OWNER;

On the basis of any other classifications the PM wishes to use.

This system shall be kept active, and updated with any new items, for the entire duration of this project.

The DC carries out the following activities:

organises the file,

labels the back of the file volumes, to facilitate consultation,

Prepares the logs and keeps them updated.

6.2 HANDLING OF CORRESPONDENCE DOCUMENTS

All correspondence between CONTRACTOR and OWNER should be approved and signed by CPM, whodecides the distribution list and necessary actions.

6.3 HANDLING OF TECHNICAL DOCUMENTS

Management of CONTRACTORs project Technical documents should be carried out accordingly to itsQuality System and the following flow chart:


11/36




DSF-1101401-436-6300-DCC-PRC-0302


Flow chartCoveringdocuments

Consequent actions Action by

IDC Form

Discipline check

Interdisciplinary check

Archiving documents

Updating MDR

Contractor

transmittal

Sending / receiving documentsInsert OWNER comments

Archiving transmittals

Updating LOGs

Contractor

Documents review andcomment / approve

Sending / receiving documents

OWNER(when required)

transmittal

Sending documents

Archiving documents

Updating MDR

Updating LOGs

Contractor

Implementation of documentsAll involved

persons

All documents issued for this project shall be signed by the Originator (Prepared), Checker (Verified) andCONTRACTORs Project Manager (Approved), in the absence of the CPM, all documents can be signed byCIM or CEM.

All documents issued by SUBCONTRACTOR shall go through their document control and approval process

before being sent to the CONTRACTOR.

All transfers of documentation should be accompanied with established Transmittal form.

Project documents shall be approved by OWNER.

START

Document issued forcomments/approval /reissued / revised by

Contractor

OWNERcomments

NO

YES

Document issuedapproved forconstruction

END

Insert OWNERcomments


12/36




DSF-1101401-436-6300-DCC-PRC-0302


6.4 HANDLING OF INCOMING TECHNICAL DOCUMENTS

The handling of the incoming technical documents includes the following activities:

Logging,

Deciding the distribution list and necessary actions,

Distribution.

Archiving

6.4.1 Logging of Technical Documents

Logging of the technical documents is DC responsibilities and has to do the following actions:

LOG the Document in MDR or other registers

check the technical documents by the list of documents on the transmittal form;

record the transmittal form and file the original, updating the Transmittal Log IN (FORM-DESFA-003 );

return to the sender, when required, a copy of the transmittal form signed for receipt;

The DC turns over all incoming technical documents to the CPM.

6.4.2 Deciding of the Distributi on List and the Necessary Actions

The CPM examines the incoming external documents and indicates the distribution list, specifying the action

requested by Project Team members for each document if its necessary.

6.4.3 Distribut ion of Technical Documents

The DC distributes the technical documents as per the distribution list so that they return to the CPM with theinformation requested.

6.4.4 Examination of Technical Documents

The persons indicated by the CPM examine received technical documents and carry out the requestedactions. Comments to the technical documents have to be written, using Comment sheet form.

The documents, with the comments incorporated, have to be returned to the DC.

6.4.5 Contractors Evaluation of Comments on Technical Documents

The CPM, or person indicated by CPM, after evaluating the comments received on the technical documents,decides to:

reject the documents, returning them with the comments to the originator for the preparation of anew revision;

Approve them, upon approval document should be sent to OWNER for review/approval;

Approve them, upon approval document should be issued for IFC (Issued for Construction) tothe OWNER.

The OWNER evaluates the documents and returns them as R Reviewed, WC - reviewed with comments,


13/36




DSF-1101401-436-6300-DCC-PRC-0302


orRWMC Reviewed with Minor Comments.

6.4.6 Updating of the MDR

The DC updates the MDR, on the basis of the CPMs instructions, throughout the life of the project, preparingeach time a new revision to be issued.

6.4.7 Approval of the MDR

The CPM approves the MDR, after the PE has checked the document.

The DC arranges the distribution of the updated MDR to all Project Team members, and to any otherspecified by CPM, including the OWNER.

MDR will be issued to OWNER on monthly basis.

6.4.8 Handling of Master Documentation

The DC organises, manages, and keeps the master documentation up to date replacing each document withthe latest revision. Prior revisions shall be stamped SUPERSEDED

6.5 HANDLING OF OUTGOING TECHNICAL DOCUMENTS

The DC handles all outgoing technical documentation, prepared according to this Procedure, and approvedby the CPM, in the following manner:

files the document originals;

prepares the Transmittal form (FORM-DESFA-001), which is to be sent to the receiver;

updates the Transmittal Log OUT (FORM-DESFA-002) and MDR Take the different numbers and filing system for outgoing documentation to the OWNER, and

the other one for outgoing documentation to the Subcontractors.

6.6 TECHNICAL DOCUMENTS REFERENCES

All Technical documents shall be written in the English and shall bear the Project references, as displayed onthe cover of this document and as described below in detail.

6.6.1 Technical Documents Template

A Technical document cover page and title block format, will display the following:

Project Title OFFSHORE PART OF THE STEFANI-ALIVERI NATURAL GAS HIGHPRESSURE PIPELINE

Owner Logo, Main Contractor Logo, Contractor Logo;

Title of Document

Document Number;

Issue Date and Revision number, Description of issue;

Area for Originator, Checker and Engineering and OWNER approval sign-offs

The Technical document Template is shown inAttachment 1 and it is prepared in Word format.

Project Document, shall always include as minimum the following sections (drawings excluded):


14/36




DSF-1101401-436-6300-DCC-PRC-0302


Each Technical Document shall contain the table Revision Status Log which shall be positioned after pagewith table of contents.

6.6.2 Technical Drawing Template

Technical Drawing Template used for the Drawings in this Project corresponds to the requirements ofCONTRACTORs document system.

The CONTRACTOR Technical Drawing Template is shown inAttachment 2 and it is prepared in AutoCAD2004 (DWG) format. In case that newer AutoCAD is used, drawing will be always saved in 2004 format.

Drawing identification table placed in the bottom right side of the template shall be filled according to thisprocedure.

6.6.3 Technical Documents Checks

Each Technical document prepared utilising the Technical document Template, shall be checked as follows.

Self-Check Check made by the Originator on his own work.

On completion of the document the Originator shall sign off the original document in order to confirmthe correctness of his work. One clean copy shall be forwarded at this stage to the respective LeadDiscipline Engineer for further processing.

Discipline Check Check made by a Discipline Specialist (Checker).Discipline Check shall be carried out by the Discipline function. A qualified person, different form theoriginator, shall subject each design deliverable to a Discipline Check.

Inter-discipline Check if required.Check regarding item(s) interfacing with other design disciplines, performed by the respectiveDiscipline Specialist.The PE shall be responsible for deciding which documents shall be subject to IDC and by whichdisciplines.

6.6.4 Documents development phases

Phases of document development shall be defined, as it is described bellow:

PHASE PROGRESS

Start Date of the document 0%

Issued for Internal Review 10%

Issued for Comments / Approval (IFA) 60%

Issued for Construction (IFC) 100%


15/36




DSF-1101401-436-6300-DCC-PRC-0302


NOTE: Documents issued for Information (I1) shall be issued to OWNER after Internal Review cycle and willhave 100% progress.

Engineering documents shall be issued with status clearly indicated in the description column of title block asfollows:

Issued (or Re-issued in case of any further rev ) for Internal Review

Issued (or Re-issued in case of any further rev ) for comments / approval

Issued (or Re-issued in case of any further rev ) for construction

OWNER will review and comment on the document within maximum of 10 calendar days. Urgent documents

may require shorter review period, but it shall never be less than two working days.

Documents / drawings returned by OWNER with comments shall be reviewed by relevant Originator.

Whenever these comments can be incorporated without further questions the document / drawing shall berevised by the Originator, rechecked by the Checker approved by CPM and issued as Issued forconstruction.

Upon document issue in new revision, the previous one shall be stamped SUPERSEDED.


16/36




DSF-1101401-436-6300-DCC-PRC-0302


6.7 DOCUMENT NUMBERING

Control of issued documents is established through the Master Document register (MDR).

Each technical document (drawings, specifications, calculations, technical reports) originated for this Projectby CONTRACTOR and by its SUBCONTRACTORS shall be assigned with an unequivocal OWNERsidentification number as per the scheme as follows:

6.7.1 Codification for Technical Documents

Document code as per the following structure:

A B C D E - F

(A) Project Code: DSF-1101401

(B) Contract No.: 436

(C) Unit No.: 6300

(D) Document subject according to Annex 1

(E) Document category according to Annex 2

(F) Document Serial Number

Example:

DSF-1101401-436-6300-CNV-STU-001


17/36




DSF-1101401-436-6300-DCC-PRC-0302


6.7.2 Codification for Technical Specifi cations

Specification code as per the following structure:

A B C D E



(C) Specification Code: SPC

(D) Specification subject according to Annex 1

(E) Specification Serial Number:

1XX for Material Technical Specifications

2XX for Job Technical Specifications

Example:

DSF-1101401-436-SPC-CON-201

6.7.3 Codification for Drawings

Drawing code as per the following structure:

A B C D E - F



(C) Unit Code: 6300

Note: In case of Issue of Standard Drawings the above Unit Number shall be replaced by the code STD.


18/36




DSF-1101401-436-6300-DCC-PRC-0302


(D) XXX/ZZ

The first part XXX designates this drawing Category according to the Annex 3 and the second part ZZdesignates the Drawing Subject and is valid only for the category 55 (pipeline plans and longitudinalsections) as follows:

01 for recording plans

02 for longitudinal sections

(E) Drawing Size:

0 for drawing standard size A0





N for non-standard size drawings

(F) Drawing Serial Number:

a.) For the Drawings category 03 (Annex 3) as follows:

001, 002 etc. for Engineering Flow Diagrams

101, 102 etc. for Process Flow, Utility Balance, Block Flow Diagrams

201, 202 etc. for Materials of Construction diagrams

301, 302 etc. for Design Pressure / Temperature Diagrams

401, 402 etc. for packaged Unit Diagrams

b.) For all other drawings: Serial Number

Example:

DSF-1101401-436-6300-93-2-001


19/36




DSF-1101401-436-6300-DCC-PRC-0302


6.7.4 ANNEX 1 Codes for Technical Documents and Technical Specifications Subject(D)

The following are the letters for the types of technical documents (3) to be used in the documentsidentification code:

D

ADM Administration

COA Coating

CON Construction

CPR Cathodic Protection

DCC Document Control

ENV Environmental

GEO Geological

GET Geotechnical

NAV Naval

NDT Non Destructive Testing

PCO Project Control

PLN Pipeline (Natural Gas Service)

POS Positioning

PRC Procurement

PRJ Project Engineering

PRM Project Management

QAC Quality Assurance / Control

SAF Safety

SEI Seismic

STA Stress Analysis

STR Structural (Steel Structures)

SUR Survey

TOP Topographical

WEL Welding


20/36




DSF-1101401-436-6300-DCC-PRC-0302


6.7.5 ANNEX 2 Codes for Technical Document Category (E)

The following are the letters for the types of technical documents (3) to be used in the documentsidentification code:

E

CHT Chart

CLC Calculation

DAB Data Book

DAT Data Sheet

IND IndexLST List

MAN Manual

MST Method Statement

MTO Material Take Off

PHL Philosophy

PLN Plan

PRC Procedure

REG Register

REP Report

REQ RequisitionSCH Schedule

SHT Sheet

SOW Scope of Work

SPE Specification

STU Study

GEN General Document

6.7.6 Forms Records

Forms Records shall be numbered as follows:

DESFA FORM-xxx

xxx progressive number


21/36




DSF-1101401-436-6300-DCC-PRC-0302


6.7.7 ANNEX 3 Codes for Drawings Category

D

01 Plot Plan and elevations

46 Steel Structures

55 Pipeline plans & Longitudinal sections

59 Pipe Supports

78 Cathodic Protection

89 Pre-commissioning (heads, layouts,)

90 Rigging Laouyts

91 Survey dwgs Scale 1:1000

92 Survey dwgs Details



95 Survey maps

96 Anchor Patterns

97 Vessels Equipment, Layouts

98 Pipeline installation aids (heads, clamps,)

99 Installation sequence drawings (story boards)

6.7.8 Sheet Number (Drawings)

Each drawing issued regarding this procedure shall contain sheet number. Sheet number shall consist of twonumerical digit starting from "01".


22/36




DSF-1101401-436-6300-DCC-PRC-0302


6.7.9 Revision Number

Documents circulated internally for review / comments can be assigned with revision number 0 (zero) (textin the description of revision shall be Issued for Internal Review).

Document ready to be submitted to the OWNER for comments / approval, it shall be assigned with revisionnumberA1 (text in the description of revision shall be Issued for Comments / Approval). In case of re-submission of a document following the OWNER comments subsequent numbers (i.e. A2, A3.,) shall beassigned until the document is finally approved.

Once the document has been approved by the OWNER, it shall be re-issued with revision code C1 (text inthe description of revision shall be Approved for Construction). In case of re-submission of a documentfollowing the OWNER comments subsequent numbers (i.e. C2, C3.) shall be assigned until the document isfinally approved.

Document ready to be submitted to the OWNER for Info, it shall be assigned with revision numberI1 (textin the description of revision shall be Issued for Information). CONTRACTOR does not expect commentson such documents, but in case of required changes document will be issued in next revision (I2, I3, etc.).

6.8 ELECTRONIC FILING OF DOCUMENTS

All documents shall be stored in the computer system, in the OFFSHORE PART OF THE STEFANI-ALIVERINATURAL GAS HIGH PRESSURE PIPELINE Project dedicated area.

The document number together with the revision number shall constitute the name of the electronic file ofeach document, for example:

DSF-1101401-436-6300-SAF-MAN-0400_A1.doc

All drawings shall be stored in AutoCAD 2004 version. The drawing number together with the sheet numberand revision number shall constitute the name of the electronic file of each drawing, for example:

DSF-1101401-436-6300-5501-3-0700_A1.dwg


23/36




DSF-1101401-436-6300-DCC-PRC-0302


6.9 FINAL DOCUMENTATION

Prior to issue the final As-Built document/drawings CONTRACTOR shall submit to OWNER forreview/comments As-Built documents/drawings.

The final As-Built drawings must fully conform to the final arrangement. The final As-Built drawings shall bebased on the drawings issued for construction but shall include modifications, alterations, corrections orremarks concerning changes effected during construction.

Documents to be included in the Asbuilt shall be defined by issuing As built Dossier Index (Doc. No. DSF-1101401-436-6300-PCO-IND-0303) and shall be sent to OWNER for approval.

Subcontractor shall submit to CONTRACTOR a proposed Index of As-Built Documentation for approval priorcommencement of the Supply of the Work.

CONTRACTOR shall also submit to OWNER the final As-built drawings and documents in digital file formin CD-ROMs. The drawings shall be submitted in standard DXF or DWG format for AutoCAD latest release.All other final Technical Documentation (reports, tables, lists, etc) shall be also submitted in MicrosoftOffice Word/Excel files.


24/36




DSF-1101401-436-6300-DCC-PRC-0302


7. ATTACHMENTS

Attachment 1 Technical Document Template - Word format for technical documents consisting more than 1page (pages 7)

Attachment 2 Technical Drawing Template AutoCAD format (pages 1/1)

Attachment 3 Transmittal Form (page 1)


25/36

Attachment 1 Technical document Template


26/36



DOCUMENT TITLE

DSF-1101401-436-6300-xxx-xxx-xxxx

REV. X Page 1 / 7

DOCUMENT TITLE

Rev Date Descripti on of Revision Prepared Checked Approved Owner


27/36



DOCUMENT TITLE

DSF-1101401-436-6300-xxx-xxx-xxxx

REV. X Page 2 / 7

INDEX

1. INTRODUCTION ...................................................................................................................... 41.1 PROJECT OVERVIEW ..................................................................................................... 41.2 PIPELINE SYSTEM DESCRIPTION ................................................................................. 4

2. DEFINITIONS AND ABBREVIATIONS .................................................................................... 52.1 DEFINITIONS ................................................................................................................... 52.2 ABBREVIATIONS ............................................................................................................. 62.3 REFERENCES .................................................................................................................. 6

3. RESPONSIBILITIES AND OBLIGATIONS ............................................................................... 64. SCOPE OF DOCUMENT ......................................................................................................... 65. HEADING 01 (PROCEDURE DESCRIPTION) ........................................................................ 7

5.1 HEADING02 (STYLE HEADING 02, FONT: ARIAL 10PT) ............................................... 75.1.1. TITLE 03 (STYLE HEADING 03, FONT: ARIAL 10PT) .............................................. 7

6. ATTACHMENTS ....................................................................................................................... 7


28/36



DOCUMENT TITLE

DSF-1101401-436-6300-xxx-xxx-xxxx

REV. X Page 3 / 7

AMENDMENTS AND REVISIONS

Amendmentand revision

Date Page Description


29/36



DOCUMENT TITLE

DSF-1101401-436-6300-xxx-xxx-xxxx

REV. X Page 4 / 7

1. INTRODUCTION

1.1 PROJECT OVERVIEW

Public Natural Gas System Operator (DESFA) of Greece plans to install an N.G.T.S. Offshore Natural GasPressure Pipeline Varnavas-Karavos (Aliveri) whose purpose will be to supply natural gas to Evvia island.

The southern landfall in Attiki is named Varnavas while the previous names used for this landfall are Ag.Apostoli or Grammatiko. The northern landfall in Evvia is named Karavos which is also indicated as Aliverilandfall.

The maximum water depth along the 20 Gas Pipeline route is approx. 70m (MSL).

Figure 1-1 Natural Gas Pressure Pipeline Varnavas-Karavos route layout

1.2 PIPELINE SYSTEM DESCRIPTION

The offshore pipeline system consist of an 20 Natural Gas High Pressure Pipeline from the battery limitat Varnavas landfall, Attiki to the battery limit at Karavos landfall at Evvia island. The length of the new20 Natural Gas High Pressure Pipeline is about 14.2 km. The 20 Natural Gas High Pressure Pipelinewill consist of the two offshore sections, joined together offshore by Above Water Tie In method.

The Varnavas side offshore pipeline section commences at the KP -0.020 and finishes at AWTI Targetpoint at KP 13.360 in water depth of 31.2m. Along the pipeline section route, maximum water depth is

70m.

The Karavos side offshore pipeline section commences at the KP 14.205 and finishes at AWTI Targetpoint at KP 13.360 in water depth of 31.2m. Along the pipeline section route, maximum water depth is31.2m.

Both pipeline sections will be manufactured from carbon steel with internal corrosion coating.


30/36



DOCUMENT TITLE

DSF-1101401-436-6300-xxx-xxx-xxxx

REV. X Page 5 / 7

2. DEFINITIONS AND ABBREVIATIONS

2.1 DEFINITIONS

The following definitions will be applicable in this document:

CONTRACTOR CONSORTIUM SAIPEM - ELTER

OWNER

DESFA HELLENIC GAS TRANSMISSION SYSTEM OPERATOR

S.A.

PROJECTDetailed Engineering, Procurement Of Materials & Construction Of TheOffshore Part Of The Stefani-Aliveri Natural Gas High PressurePipeline

PROJECT MANAGERMeans, respectively, the entity and the person appointed by OWNER toprovide project management services

SITE Means the lands, waters and other places on, under, in or trhoughwhich the WORKS are to be performed including offshore installations,floating construction equipment, vessels (including the area covered byapproved anchor patterns) design offices, workshops and places whereequipment, materials or supplies are being obtained, storied or used forthe purposes of the CONTRACT and any and all other places where

the PERMANENT WORKS are to be executed and to which PLANTand Materials are to be delivered and any other places as may bespecified in the CONTRACT as forming part of the SITE.

SUBCONTRACTORSelected Sub-Contractor to perform the work described in thisdocument

SUPERVISING ENGINEER

Means the company(ies) appointed by OWNER to carry out theConstruction Supervision duties, as well as the review of the detaileddesign issued by CONTRACTOR, as defined in Clause 2 hereof and inother CONTRACT DOCUMENTS.

WORKS

Means all CONTRACTORs services and supplies to be rendered andPLANT furnished in accordance with the CONTRACT including bothTEMPORARY WORKS and PERMANENT WORKS. Without limitationto items set out in the CONTRACT DOCUMENTS, the WORKS include

everything of whatever nature that is required for the achievement ofthe objective of the CONTRACT, except for any exclusions that arespecifically itemized in the CONTRACT DOCUMENTS.


31/36



DOCUMENT TITLE

DSF-1101401-436-6300-xxx-xxx-xxxx

REV. X Page 6 / 7

2.2 ABBREVIATIONS

The following abbreviations will be applicable in this document:

CPM Contractor Project Manager

2.3 REFERENCES

Ref. Document No. Document Title

1

2

3

4

5

6

7

8

9

3. RESPONSIBILITIES AND OBLIGATIONS

Text (Style P1, Font: Arial 10 pt)

Bullet (Style P1, Font: Arial 10pt)

Text (Style P1, Font: Arial 10pt)

4. SCOPE OF DOCUMENT





32/36



DOCUMENT TITLE

DSF-1101401-436-6300-xxx-xxx-xxxx

REV. X Page 7 / 7

5. HEADING 01 (PROCEDURE DESCRIPTION)




5.1 HEADING02 (STYLE HEADING 02, FONT: ARIAL 10PT)




5.1.1. Title 03 (Style Heading 03, Font: ARIAL 10pt)




6. ATTACHMENTS

Attachment 1 - Text (Style P1, Font: Arial 10pt)

Attachment 2 - Text (Style P1, Font: Arial 10pt)


33/36

Attachment 2 Technical Drawing Template


34/36


35/36

Attachment 3 Transmittal Form


36/36

Date:

4= For Bid

No.off Rev. Acti on Co de Resp. Cod e

1

Transmitted by:

Date:

Received by:

Date:

Project No.: DSF-1101401

Distribution

Correspondence number:

PROJECT NAME: OFFSHORE PART OF THE STEFANI-ALIVERI NATURAL GAS HIGH PRESSURE

PIPELINE

CONTRACT No.: 436/11

To:

Address:

TRANSMITTAL FORM

Form no.: FORM-DESFA-0001

Rev. 01 DatE: 17.11.2011

Pag. 1 of 1

Title / Description

B = Approved on condition

CLIENT: DESFA- HELLENIC GAS TRANSMISSION

SYSTEM OPERATOR S.A.

Ref.No.:

Subject:

Quantity:

From: SAIPEM

PLESE SIGN AND RETURN COPY

RESPONSE CODE:

Document No.

D= No comment - For info

only

ACTION CODE:

1 = For Approval

2 = For Comment

3 = For Information

5= For Construction

6= For Design

A = Approved C= Unnaceptable