27608E00

Eni S.p.A. 27608.DOC.GEN.
SDS
Exploration & Production Division Rev.1 - March 2010
Page 2 of 32
INDEX
1. FOREWORD ...................................................................................................................................3
1.1 References ......................................................................................................................................3
1.2 Software to edit documents .............................................................................................................3
1.3 Acronyms ........................................................................................................................................4
1.4 Glossary ..........................................................................................................................................4
2. SCOPE............................................................................................................................................7
3. REQUIREMENTS AND DELIVERABLES DEPENDENT ON CONTRACTORS AND
VENDORS ......................................................................................................................................7
4. ISTRUCTIONS FOR THE CONTRACTORS ..................................................................................8
4.1 Interdisciplinary documents .............................................................................................................8
4.2 Indication of code and name of facilities and subfacilities ...............................................................8
4.3 Communication of the names of Company representatives ............................................................9
4.4 Disciplines for the progress of the engineering activities.................................................................9
4.5 Instructions for sending the documentation...................................................................................10
4.6 Data Loading Files for DED, DEOD and TRANSMITTAL IN .........................................................11
5. DOCUMENT PROGRESS REPORT (DPR) .................................................................................12
APPENDIX 1 DOCUMENTO ELENCO DOCUMENTI (DED) – FACILITY DOCUMENT LIST ...........................13
APPENDIX 2 DOCUMENTO ELENCO OPERATIVO DOCUMENTI (DEOD).....................................................14
APPENDIX 3 TRANSMITTAL IN ........................................................................................................................16
APPENDIX 4 TRANSMITTAL OUT ....................................................................................................................17
APPENDIX 5 COMMENT SHEET.......................................................................................................................18
APPENDIX 6 DOCUMENT PROGRESS REPORT (DPR) .................................................................................19
APPENDIX 7 INTERDISCIPLINARY DOCUMENTS ..........................................................................................20
APPENDIX 8 DOCUMENTS PRODUCED BY DIFFERENT CONTRACTORS IN DIFFERENT PROJECT
PHASES .......................................................................................................................................21
APPENDIX 9 USE OF % WEIGHTS TO ELABORATE THE % PHYSICAL PROGRESS OF THE
TECHNICAL DOCUMENTATION.................................................................................................22
ATTACHMENT 1 DED (Facility Document List) ....................................................................................................27
ATTACHMENT 2 DEOD............................................................................................................................................30
ATTACHMENT 3 TEMPLATE TRANSMITTAL IN (facsimile) .................................................................................31
ATTACHMENT 4 TEMPLATE TRANSMITTAL OUT (facsimile) .............................................................................32
Eni S.p.A. 27608.DOC.GEN.SDS
Page 3 of 32
1. FOREWORD
An effective check of the technical documentation produced for a facility by contractors and vendors is a necessary
condition to guarantee an ordered development of all project activities: purchase, constructions, inspections, pre-
commissioning, commissioning, hand over, production, maintenance, decommissioning.
For this purpose this document indicates the contractual requirements dependent on contractors and vendors, to
allow the Company to manage the technical documentation as per its procedures.
The approval cycle of technical documentation will be managed through a shared document information system:
EDAM.
1.1 References
Ref. Code Title Content
This specification explains how to identify

“Technical documents
documents and how to manage project phases,
1 20189.COO.GEN.SDS identification and title
validity status and revision index.
block”
It also indicates the title blocks to be used.
This specification contains a list of typical
titles of technical documents.
For each document it is indicated first
“Technical documentation emission’s phase and following foreseen
required during the validity status, the classifications to be used
2 27605.VAR.GEN.SDS
project development in the document ID (design phase, discipline,
phase” type and subtype).
The contractor is required to verify the fitness of
titles to the object of the contract and to request
modifications and integrations.
The scope of this document is to define the

functional units required in the design of
hydrocarbon production and treatment
installations.
06215.DOC.GEN.SDS “FACILITY FUNCTIONAL
3 Moreover the document defines the function of
UNITS”
each unit, its main components and indicates
the functional units with which it has a physical
interface.
1.2 Software to edit documents
Document Type Software Name File extension
Drawings AutoCAD / Microstation .dwg / .dgn / .dri / others

Documents Microsoft Word 97 / 2000 / XP .doc
Data Sheets Microsoft Excel 97 / 2000 / XP .xls
Various Acrobat Writer .pdf

Page 4 of 32
1.3 Acronyms
EDAM Engineering Document Approval Management

EDC Engineering Document Controller
FEM Facility Engineering Manager
DPR Document Progress Report
OPDS Opportunity and Project Development System
KOM Kick Off Meeting
OPDS Opportunity and Project Development System
DED Documento Elenco Documenti (Facility Document List)
DEOD Documento Elenco Operativo Documenti (Operating Document List)
1.4 Glossary
WORD DESCRIPTION
The Company is the party that initiates the project and ultimately pays for its design and
Company
construction.
The Contractor is the party which carries out all or part of the design, procurement,
Contractor
commissioning, production and maintenance of a facility.
The Vendor is the party which sells equipment and services to perform the duties
Vendor specified by the contractor, by supplying also the related data and documents in the as
built state.
Document ID Technical document code (according to spec 20189.DOC.GEN.SDS).
It is the document for the formal approval of the technical documentation of the facility to
be submitted in the contract.
It shall contain: title code, Company document ID, document title, contractor document
ID, functional unit, validity status.
DED
It must be sent for approval at the beginning of the planning activities.
(Documento Elenco
Every time a document is added or modified, the DED shall be revised and sent to
Documenti)
Company for approval with an increased revision.
The other information (revision index, issue date, document size, number of sheets) shall
Facility Document List
be sent to Company, with an increased revision, at the formal closing of each phase.
The revision description and the transmittal sending reason shall be “Final issue for end
See APPENDIX 1
of phase”.
The document shall be compiled in excel format to allow the Company to insert the data
directly in EDAM.
This document shall be always sent with a transmittal.
DEOD
The DEOD is not a document but a set of data, which allows the managing of the
(Documento Elenco
planning and the check of the approval cycle of the technical documentation in the
Operativo Documenti)
information system EDAM.
It shall be sent in excel format with a transmittal.
See APPENDIX 2
It is a code which identifies the issues of document in the different OPDS and
Validity Status engineering phases. It expresses the state of completeness and reliability of a document,
by allowing its use in one of the project/design phases.
It means the check activity performed by the Company on a document.
The DEOD shall indicate for each document the foreseen surveillance type for each
validity status.
Surveillance SURVEILLANCE TYPE

Code Description
I Information
A Approval
N No Surveillance
Page 5 of 32
INFORMATION
For the documents to be sent for information, in order to check the % physical progress,
it is requested the scheduled and the actual date of the transmittal IN (file date).
For these document it is not requested any reply.
APPROVAL
For the documents to be submitted for approval, in order to check the % physical
progress, it is requested the planned and the actual date of the transmittal OUT (file
date), in which the Company approves or approves with comments the document.
After the Company’s approval, these documents shall be sent in final issue with the
revision index incremented.
NO SURVEILLANCE
The documents with no surveillance are not relevant for the check of the % physical
progress. For these documents it is not requested a planned issued date.
They will be sent at the end of each phase.
Examples of these documents are: documents produced by constructors and other
documents at Company’s discretion.
The date of the transmittal file and of the e-mail shall be the same.
It is the reason for which a contractor sends the documents with a transmittal IN.
SENDING REASON
Code Description
Sending Reason I For Information
C For Comments
A For Approval
Final Emission
F
(after Company’s approval with incremented revision)
As indicated in APPENDIX 1, at the end of each planning phase, the contractor will send
the DED, completed with all data and a copy of all documents with sending reason “Final
Sending of
issue for end of phase”.
documentation at the
The final documentation of each phase will be delivered to the Company on a CD/DVD
end of a phase
or other information support.
The Company could also request the dispatch of paper copies.
It is the Company’s formal answer to the documents sent for approval.

This answer is inserted in the comment sheet of the document and it is reported in the
transmittal OUT.
A – APPROVED
All “approved” documents shall be re-issued with the revision index increased. The
revision description shall be “Final emission”.
The approval shall be stated by a signature of the Company in the document title block
or by the inclusion in the revision description of the transmittal OUT number and date.
pproval Status
B – APPROVED WITH COMMENTS
For the documents “approved with comments” the contractor shall operate as above,
after having implemented the comments.
C – NOT APPROVED
For the documents “not approved” the contractor shall resubmit a new revision “For
approval”.
The Company could include in the comment sheet the reason/comments for the non
approval.
It is an excel file required to contractors, which notifies the sending of documents.

It contains the data of the transmittal and a list of the sent documents, indicating for each
TRANSMITTAL IN document all the data of APPENDIX 3.
This file shall consist of a record for the transmittal and a record for each document
See APPENDIX 3 attached to the transmittal.
For the actual % progress curve, the transmittal IN date is considered as actual for
documents sent for information.
Page 6 of 32
It is a file issued by the Company, containing the approval status assigned to each
document.
TRANSMITTAL OUT It transmits the comment sheets, one for each document.
The Company could also attach documents to complete the comment sheet.
See APPENDIX 4 For the actual % progress curve, for documents to be submitted for approval, the date of
the transmittal OUT with approval status “approved” or “approved with comments” is
taken as actual date.
File issued by the Company, transmitted to the contractor, attached to a transmittal OUT.
COMMENT SHEET
It reports the document ID, its revision and its approval status.
It contains the comments of the disciplines and the general comments related to that
See APPENDIX 5
document.
It is a consultation report that doesn’t require approval by the Company.
DOCUMENT POGRESS It is issued by the contractor at each cut off date (each month) and sent attached to the
REPORT Monthly Report.
(DPR) It provides the complete situation of the planning, emission and approval of the
documents.
See APPENDIX 6 It also shows the % physical planned and actual progress of the documents, using the
data taken from Appendixes from 1 to 5.
It consists of the validity status and of a progressive numeric value (starting from 00).
Revision Index
When the validity status changes, the numbering restarts from 00.
Company
A technical engineering department of the Company.
Discipline
Document
A discipline defined in Ref. 1
Discipline
Contract One of the disciplines defined during the KOM to compile the distribution matrix and to
Discipline get the progress.
% weight
of the discipline For each discipline during the KOM, it is agreed the % weight within the contract.
in the contract
% weight
of document
For each document, it is indicated a % weight within the discipline.
within the discipline of
the contract
% weight
of a validity status For each validity status of a document, it is indicated a % weight within the document.
within a document
It is the date in which the requested surveillance has been implemented.
For documents with no surveillance, it is the actual emission date of the document.
Actual date
For documents sent for information, it is the actual transmittal IN date.
For documents to be submitted for approval, it is the actual transmittal OUT date with
approval status “approved” or “approved with comments”.
It is indicated in the DEOD and it will be used by the Company to check the respect of
the planning of the received documentation.
Planned date For documents with no surveillance, it is the planned emission date of the document.
For documents sent for information, it is the planned transmittal IN date.
For documents to be submitted for approval, it is the planned transmittal OUT date with
approval status “approved” or “approved with comments”.
The methodology for the measurement and the reporting of the full life % planned and
Full life % physical
actual physical progress is described in APPENDIX 9.
progress measurement
The documents with no surveillance aren’t relevant for the progress.
Page 7 of 32
2. SCOPE
Scope of this document is to give a detailed definition of the deliverables and requirements requested to
contractors and vendors for the planning and the management of the technical documentation issued in a
contract for a facility.
3. REQUIREMENTS AND DELIVERABLES DEPENDENT ON CONTRACTORS AND VENDORS
• Application of the identification procedures for engineering documents, defined in the specification
20189.COO.GEN.SDS (Ref 1).
This specification defines: technical documents identification, document revision index, revision validity status
and title blocks.
• Sending, with transmittal IN, of the DED file (Facility Document List) for approval.
In this file it is reported the list of documents to be issued and the relative validity status (APPENDIX 1).
• Sending, with transmittal IN, of the DEOD file (APPENDIX 2), compiled only for the document “Facility
Document List”.
• Sending, with transmittal IN, after the approval of the “Facility Document List”, of the DEOD file (APPENDIX 2),
compiled with all documents listed in the Facility Document List.
The data shall include: surveillance type for each validity status, foreseen sending date for information or
foreseen approval date through transmittal OUT.
With these data, it can be compiled the total % (percent) planned progress curve.
• Sending, with transmittal IN, of the planned documents, indicating sending reason, revision index and data of
the documents (APPENDIX 3).
• Sending of the updated version of the Document Progress Report, attached to the Monthly Report.
Page 8 of 32
4. ISTRUCTIONS FOR THE CONTRACTORS
During the Kick Off Meeting (KOM) the Company will inform the contractor of the following data, to ensure the
respect of the requirements mentioned in previous paragraph for the approval of the technical documentation.
4.1 Interdisciplinary documents
The interdisciplinary documents, which shall be adopted in the engineering activities (see APPENDIX 7), will be
delivered from the EDC to the contractor on information support (CD Rom).
4.2 Indication of code and name of facilities and sub-facilities
Facility
It is a code which identifies a facility (plant or plants groups) assigned by ENI E&P to ensure the documents
retrieval.
The code can have from 1 to 6 alphanumeric characters.
e.g.
Facility Code Facility Name
0544 Barbara Platform T2
Sub-facility
It is a code which identifies a part/section of a facility defined on the basis of functional/geographical criteria, as
Storage Unit, Gas Dehydration, Power Generation, Sulphur recovery, cluster, sealine.
The code shall have 2 alphanumeric characters.
e.g.
Sub-Facility Code Sub-Facility Name
1A Barbara Platform T2 – Cluster A
Assignment of ranges of alphanumerical codes
The single contractor will assign alphanumeric ranges to his direct subcontractors and vendors.
The use of alphabetical characters, in particular in the first two positions, allows the definition of several gaps.
In case of a facility with more contractors or in which it is planned an emission of documents by the Company,
the assignment of the first level range shall be assigned by the Company.
Assignment of code to vendor/contractor
It is a registry code of vendors assigned by Company to contractors/vendors.

This code, managed by the engineering materials management department, ill be used in the transmittal IN ID
and guarantee the uniqueness of a contractor/vendor.
Page 9 of 32
4.3 Communication of the names of Company representatives
The contractor will be informed about the names of Company’s people with following roles:
He approves the planned documents list with relative validity status

DPM
and the emissions of comment sheets of documents with a relevant
(Deputy Project Manager)
impact on times, costs, quality.
FEM He approves the transmittals OUT and the comment sheets of

(Facility Engineering Manager) those documents not to be submitted for approval by DPM.
Interdisciplinary function, he consolidates and integrates the

comments elaborated by disciplines and compiles the final
Focal Point
comment sheet.
Generally the Focal Point is the owner of the document.
Technical management function, he manages and distributes the
EDC documents during the approval cycle. He verifies the correct
(Engineering Document Controller) application of internal normalization/interdisciplinary documents.
He verifies that the contractor has a person with the same role.
They are responsible for the technical follow up of the contract and
Discipline Specialists compile the comments of their area of expertise sending them to
the Focal Point.
4.4 Disciplines for the progress of the engineering activities
During the KOM it will be agreed the list of the disciplines adopted for the progress of the contract engineering
activities and the % weight of each discipline.
It can also be agreed a correspondence table among:
1) Contract disciplines
2) Disciplines indicated in Ref.1
3) Company engineering departments
Page 10 of 32
4.5 Instructions for sending the documentation
During the KOM the parties will agree the way of sending technical documents and relative transmittals (through e-
mail or information platform).
It will be put in evidence the contractual scheduling to reply to the documents sent for approval.
The documents sent for approval shall be sent in advance in respect to the planned date.
For example, if the contractual planned date for the approval is 1 June and the scheduling is 15 days, the transmittal
IN shall not be later than 15 May.
It will be also agreed the methodology for sending documents (paper copies or CD/DVD) in correspondence of each
end of phase.
Transmissions from Contractor to Company
All the documents subject to surveillance shall be sent with a Transmittal IN.
Each transmission shall be composed by:
1) Transmittal file generated by the contractor’s information procedures. The name of this file shall been as below
indicated.
2) Transmittal excel file, including the record data of the transmittal and a record data for each transmitted
document (see APPENDIX 3).
3) The documents listed in the Transmittal.
The name of the Transmittal IN shall be:
IN-XXXXXX-YYY-ENI-NNNNN
Where:
XXXXXX Facility code
YYY Contractor’s Code, assigned by vendor’s registry office MIAP (see KOM)
NNNNN Sequential number
Transmissions from Company to Contractor
The transmittal OUT will be issued only for the documents sent for approval, the documents sent for information
don’t require any reply.
On the transmittal OUT, it will be indicated the approval status of the document (approved, approved with comments,
not approved).
The name of the Transmittal OUT shall be:
OUT-XXXXXX-ENI-YYY-NNNNN
Where:
XXXXXX Facility code
YYY Contractor’s Code, assigned by vendor’s registry office MIAP (see KOM)
NNNNN Sequential number
Comment Sheet
This document reports in detail, for each single document sent for approval, the comments elaborated by the
Company disciplines and the complete comment of the technical responsible of the document approval.
In the comment sheet, it is assigned the approval status code, which will be also reported in the transmittal OUT (see
APPENDIX 5).
The file name of the Comment Sheet shall be:
CS_XXXXXXXXXXXXXXXXX_XXXX_XX
Where:
CS Comment Sheet
XXXXXXXXXXXXXXXXX ENI Document Number
XXXX Validity Status
XX Revision
Page 11 of 32
Comment sheet contractor’s reply (if any)
The contractor can use the received comment sheet for optional communications/remarks that will not be part of the
approval cycle, falling within the correspondence relative to the technical documentation.
The file name shall be:
CS_XX_XXXXXXXXXXXXXXXXX_XXXX_XX
Where:
CS_XX Comment Sheet Revision
XXXXXXXXXXXXXXXXX ENI Document Number
XXXX Validity Status
XX Revision
4.6 Data Loading Files for DED, DEOD and TRANSMITTAL IN
The data will be loaded in EDAM from the excel files DED, DEOD and TRANSMITTAL IN.
During the KOM, the contractors will receive the corresponding three loading files.
Page 12 of 32
5. DOCUMENT PROGRESS REPORT (DPR)
The contractor is required to compile periodically (normally each month) a report called DPR (Document Progress
Report), in which it is reported:
• Data available from file DED (Facility Document List)

• Data available from file DEOD
• Data available from Transmittals IN
• Data available from Transmittals OUT
During the KOM, it will be agreed the DPR template and the periodicity of the updating (cut off).
The report shall not be approved by the Company; it is normally attached to the Monthly Report.
In APPENDIX 6, it is reported the list of the data to be inserted in the DPR.

Page 13 of 32
APPENDIX 1 DOCUMENTO ELENCO DOCUMENTI (DED) – FACILITY DOCUMENT LIST
The document “Documento Elenco Documenti” of a facility is a technical document that shall be managed in
accordance to Ref.1, with a cover page and a page dedicated to the revisions’ description.
It shall be issued in final emission in correspondence of each project phase’s end.
A project phase is considered closed when all documents with validity status correspondent to a phase have
satisfied the requested surveillance.
The data to be submitted for approval (and to be obligatory compiled) are those relative to the columns with the
grey highlighted headings, while the data of the columns with the not highlighted headings shall be sent in
correspondence of the end of each project phase (see table below).
Following the descriptions of the headers:
ID Progressive numbers
Document Title Code Identification code of the document title (in accordance with Ref. 2)
Contract Discipline One of the disciplines defined during the KOM for the distribution and the
progress report
Company Document ID Company Document Identification Code (in accordance with Ref. 1)
Contractor Document ID Contractor Document Identification Code
Company Document Title Document title, consistent with the title code
Revision Index It is composed by Validity Status + Revision Number
Functional Unit One of the functional units, defined in document 06215.DOC.GEN.SDS
Issue Date Emission date of the document (reported on the document title block)
Document Size Printable format of the document (e.g. A4, A1, etc…)
Nr of sheets Number of sheets of the document
Notes Notes
The data in the above table will be reported in landscape disposition with possible changes limited to the columns’
width.
The titles of the documents shall not be cut.
If a document shall be issued with more than one validity status, it shall be entered in more rows (one row for each
validity status). When the validity status changes, the sequential number shall restart from 00.
The data of this document shall be reported in the Document Progress Report.
Page 14 of 32
APPENDIX 2 DOCUMENTO ELENCO OPERATIVO DOCUMENTI (DEOD)
The DEOD is not a document, but a set of data, which allows the managing of the planning and the check of the
approval cycle of the technical documentation in the information system EDAM.
The data set of the DEOD dedicated to the surveillance doesn’t require formal approval by the Company and it
shall be an excel file.
The Company can, at any time, request for modifications or integrations.
The data shall be reported in the Document Progress Report.
Following the standard template in excel:
Company Work Package 1

Title 2
Eni Document ID 3
Validity Status 4
Location 5
General Document Data Contractor Document ID 6
Surveillance Type 7
Document Type Code 8
Facility Functional Unit 9
Vendor 10
Contract Discipline Name 11
Document weight in the discipline 12
Validity Status weight in the document 13
Budgeting
Document Weight 14
Document Weight Man-hours 15
Document inzialization - Planned date 16
Issued for internal review (IDC) - Planned date 17
(First) Issue for comments (C) - Planned date 18
Planning for documents with surveillance
(First) Issue for comments (C) - Replanned date 19

(First) Issue for comments (C)- Actual date 20
(First) Issue for approval (A)- Planned date 21
(First) Issue for approval (A) - Replanned date 22
Surveillance type A - Approval
(First) Issue for approval (A) - Actual date 23
Approval - Planned date (Mandatory) 24
Approval - Replanned date (Mandatory) 25
Approval - Actual date 26
Final issue (F) - Planned date 27
Final issue (F) - Replanned date 28
Final issue (F) - Actual date 29
Issued for information - Planned date 30
Surveillance type I - Information Issued for information - Replanned date 31
Issued for information - Actual date 32
Page 15 of 32
The data in the highlighted columns are taken from the DED (APPENDIX 1).
Following are reported the descriptions of the not highlighted headings.
1 Company Work Package It is the company work package for the project planning
2 Title Title of the document
3 Eni Document ID According to ENI Document numbering (ref. 1)
4 Validity Status According to ENI Document numbering (ref. 1)
5 Location Geographical reference (onshore / offshore)
6 Contractor Document ID According to Contractor document numbering
7 Surveillance Type See glossary (paragraph 1.4)
8 Document Type Code See ref. 2
9 Facility Functional Unit See ref. 3
Business name of the vendor (sub-contractors) that has
10 Vendor
issued the document
One of the contract discipline acknowledged in KoM.
11 Contract Discipline Name During the KoM the % of each contract discipline in the
contract shall also be defined.
12 Document weight in the discipline See appendix 9
13 Validity Status weight in the document See appendix 9
It is the product of contract discipline weight in the
contract X document weight in the discipline X validity
14 Document Weight
status in the document; see appendix 9.
It is a calculated value.
Man-hours declared by contractor for issuing a document
15 Document Weight Man-hours in a validity status. In this case lines 12, 13 & 14 are
calculated and not assumed.
16 Document inzialization - Planned date
17 Issued for internal review (IDC) - Planned date
18 (First) Issue for comments (C) - Planned date
19 (First) Issue for comments (C) - Replanned date
20 (First) Issue for comments (C) - Actual date
21 (First) Issue for approval (A) - Planned date
22 (First) Issue for approval (A) - Replanned date
23 (First) Issue for approval (A) - Actual date Actual dates shall be provided by contractors in case they
24 Approval - Planned date (Mandatory) are not imported directly from EDAM.
The dates to be planned will be agreed during the KoM.
25 Approval - Replanned date (Mandatory)
26 Approval - Actual date
27 Final issue (F) - Planned date
28 Final issue (F) - Replanned date
29 Final issue (F) - Actual date
30 Issued for information - Planned date (Mandatory)
31 Issued for information - Replanned date (Mandatory)
32 Issued for information - Actual date
Page 16 of 32
APPENDIX 3 TRANSMITTAL IN
The documents to be submitted for surveillance are sent to Company with a transmittal IN.
The transmittal is an excel file, which contains 2 records (see below).
The position of the data in the cells shall be respected, in order to allow the automatic loading in EDAM.
DATA SET OF TRANSMITTAL IN
Transmittal
Transmittal Transmittal
IN Facility Contract Project Contractor
IN ID IN Date
Description
Following are reported the indications on the columns’ headings:
Transmittal IN ID Transmittal IN Identification number

Transmittal Date Date in which the e-mail is sent
Transmittal Description Content of the transmittal (e.g. documents, TQ, etc…)
Facility Facility Name
Contract Contract number (assigned by the Company)
Project OPDS Project name (assigned by the Company)
Contractor Contractor Business name
DATA SET OF THE DOCUMENTS ATTACHED TO THE TRANSMITTAL IN
ENI Document Document

Validity Revision Sending Issue Document
File Name Document page printable
Status index Reason date file type
ID number format
Each document shall be reported on one row.
The data of the not highlighted columns’ headings are taken from the APPENDIX 2.
File Name File name of the attached document

ENI Document ID ENI E&P Identification number of the attached document
Validity Status Validity status of the attached document
Revision index Revision Index of the attached document
Sending reason Sending reason for the attached document: for
comments, for information, for approval, final issue
Issue Date Emission date of the attached document, reported on its
title block
Document page number Number of sheets of the attached document
Document printable Format Format of the attached document
File extension File Type of the attached document
The data of these two records shall be reported in the Document Progress Report.
Page 17 of 32
APPENDIX 4 TRANSMITTAL OUT
The Company performs his surveillance through the emission of a comment sheet for each examined document.
The comment sheets are sent with a transmittal OUT.
EDAM compiles automatically all the data inserting the Company answers.
In the transmittal OUT following information are reported:
Heading
Facility code ENI E&P code, in accordance to Ref. 1

Facility name
Project Code
Project Name
Country
Location
Contractor
Contract ID assigned by the Company
Transmittal OUT ID
Sheet number
Date
Table
ID Progressive number to identify the rows (one row for each document)
Documentation References Reference Documentation

• Document ID ENI
• Document ID Contractor
• Document Title
Revision Index Revision Index

• Revision Number
• Validity Status
Transmittal IN Contains following data

• Transmittal ID
• Transmittal Date
• Sending Reason for the document
Approval Status Code Approval Status (assigned to the document in the comment
sheet and reported in the transmittal OUT):
A Approved
B Approved with comments
C Not Approved
Related Documents File List of possible files, integrating the comment sheet
Page 18 of 32
APPENDIX 5 COMMENT SHEET
For each document sent for approval, the Company will compile a document called “comment sheet”.
In this document it will be assigned an approval status code (A approved, B approved with comments, C not
approved) and it will be reported the comments of the single disciplines and the general comments.
Below it is reported the facsimile of a comment sheet produced by EDAM.
The comment sheet, one for each document received for approval or for comments, will be attached to a transmittal
OUT.
Comment sheet (Facsimile)
Document Title
Company Document
Number and Revision
Contractor Document
Number and revision
(*)
Approval Status code:
Transmittal OUT number: Transmittal IN number:
ENI Approver Name
(*)
A APPROVED
B APPROVED WITH COMMENTS
C NOT APPROVED
ID DISCIPLINE COMMENTS CONTRACTOR’S REPLY (IF ANY)
In the comment sheet following information are reported:
Heading:
• Project Name
• Plant Location
• Date
• Number sheet
Table:
• Document Title
• ENI E&P Document ID and revision index
• Contractor Document ID and revision index
• Approval Status Code of the document
• Transmittal OUT ID with whom the comment sheet will be transmitted
• Transmittal IN ID with whom the document has been received
• List of comments, ordered for discipline
Page 19 of 32
APPENDIX 6 DOCUMENT PROGRESS REPORT (DPR)
The DPR, also called “Master Document Register” or “Project Document Report”, contains all the data transmitted and
approved, defined in the appendixes from 1 to 5.
It provides the planned situation life time and the actual situation at the cut off date. It doesn’t require any other check.
This report shall be compiled by the contractor and shall contain following data:
• Contract
• Contractor
• Project
• Facility
• Subfacility
• Company Document ID
• Contractor Document ID
• Document Title
• Title Code (see specification 27605.VAR.GEN.SDS)
• Revision Index (validity status + revision)
• Surveillance Type for validity status
• Surveillance Discipline and progress report
• Planned emission date of the validity status
• % weight of the document in the discipline
• % weight of the validity status in the document
• Functional unit
• Sending date and transmittal IN ID
• Sending reason for each document attached to the transmittal IN
• Planned date for the emission of the validity status
• Sending date and transmittal OUT ID
• Approval Type for each document attached to the transmittal OUT
These data, ordered for discipline, document ID, validity status and revision index allow an immediate access to the
current status of the documentation and to the previous revisions’ history.
Page 20 of 32
APPENDIX 7 INTERDISCIPLINARY DOCUMENTS
Following documents are a set of technical prescriptions dedicated to the management of technical documentation and the
use of CAE “Computer Aided Engineering”.
CODE TITLE
27605.VAR.GEN.SDS Technical Documentation Required during the Project Development Phase
20189.COO.GEN.SDS Technical Documents Identification and Title Blocks (Identification Tables)
20198.COO.GEN.SDS Item numbering
06215.DOC.GEN.SDS Facility Functional Units
20259.DOC.GEN.SDS P&ID - Piping and Instrumentation Diagram
06221.DOC.ELE.PRG OLD - Electric One Line Diagram
06227.DOC.GEN.PRG Facilities Plot Plans
06222. DOC.PRC.PRG Equipment List
06223. DOC.PRC.PRG Line List
06224. DOC.PRC.PRG Hand Valve and Line Accessories List
06225. DOC.PRC.PRG Loops & Instrument List
06681.DOC.ELE.PRG Electric Loads List
06682.DOC.ELE.PRG Electric Cable List and Electric Cable Report
06784.DOC.PRC.PRG Functional Unit List
20202.DOC.GEN.PRG Model and spare parts date required from Vendors
20203.DOC.GEN.SDS Handover of plant component date and key documents for DBIMP
06214.DOC.GEN.SDS Instructions to Contractors for Information submission to DBIMP
20204.CAE.GEN.PRG Procedures for preparation of 2D CAD drawings

General procedures for preparation of 3D CAD models and deliverables
20205.CAE.GEN.PRG
production
Standard rules for preparation of 3D CAD models and deliverables production
20206.CAE.GEN.PRG
by using Intergraph PDS3D
Standard rules for preparation of 3D CAD models and deliverables production
27901.CAE.GEN.PRG
by using AVEVA Vantage PDMS
ITEM.BR.001 Overview of MIAP Information System
ITEM.BR.002 Overview of SPCPUMA Functionalities

Survey of existing facilities through laser scanning to obtain the as-built 3D
20248.CAE.GEN.SDS
CAD model and associated date and documents
Page 21 of 32
APPENDIX 8 DOCUMENTS PRODUCED BY DIFFERENT CONTRACTORS IN DIFFERENT PROJECT PHASES
In case the different project phases are assigned to different contractors, it can happen that the same document is issued in
a validity status by a contractor and in another status by another contractor (e.g. basic and feed by a contractor, detail by a
second one and construction by a third one).
In these cases the activity performed by each contractor shall be reported in the document title block.
Each contractor in charge of the document inserts his logo, his business name, his contract number in the columns dedicated
to contractor.
The contractor, who comes after, recovers the rows with the previous revisions.
As an alternative, each contractor will issue a new document, in which he will compile the “Supersedes N/Superseded by N”
cell, reporting the reference to the original document.
Here below, it is reported an example of title block.
EX-AB 00 25/06/07 Final issue Contractor C Eni E&P
EX-CO 01 25/05/07 Final issue Contractor C Eni E&P
EX-CO 00 25/04/07 Issued for approval Contractor C Eni E&P
EX-DE 01 25/03/07 Final Issue Contractor B Eni E&P
EX-DE 00 25/02/07 Issued For Approval Contractor B Eni E&P
CD-FE 01 25/01/07 Final Issue Contractor A Eni E&P
CD-FE 00 25/12/06 Issued For Approval Contractor A Eni E&P
CD-BF 01 25/11/06 Final Issue Contractor A Eni E&P
CD-BF 00 25/10/06 Issued For Approval Contractor A Eni E&P

Validity Rev. Contractor
Prepared Checked Company
Status number Date Description Approved by business Name
by by Approval
and Approval
Revision index
Eni S.p.A. Project name Company identification
Exploration & Production

Contractors’ logo and business name Contractor identification
Note: If a document is issued for the first time
Contractor C (the one who has issued last revision) in BASIC phase (B), the phase doesn’t change
with the changing of the validity status.
Contract:
Vendor logo and business name
Vendor identification
Order N.
Facility Name Location Scale Sheet of Sheets
1:1 1 of XX
Document Title Supersedes N.
Superseded by N.
Plant Area Plant Unit
Page 22 of 32
APPENDIX 9 USE OF % WEIGHTS TO ELABORATE THE % PHYSICAL PROGRESS OF THE TECHNICAL

DOCUMENTATION
Following it is described the information methodology in EDAM to compile the actual and the planned full life % physical
progress curve.
During the KOM, the Company and the contractor agree the list of the disciplines object of the contract. This list shall match
with the list of the disciplines inserted by the Company in the approval matrix.
The engineering activities of the contract are subdivided among the disciplines, through the definition of a % weight for
each discipline.
The activities of a discipline are subdivided among the documents belonging to each discipline, indicating the % weight for
each document.
The activities of a document are subdivided among the validity status of the document, indicating the % weight for each
validity status.
The % weight of a validity status of a document in the whole contract is obtained by multiplying the % weight of the validity
status in the document, for the % weight of the document in the discipline, for the % weight of the discipline.
The planned and the actual progress % curves will have as coordinates on the y-axis the cumulative progress % from 0 to 1
and on the x-axis the time (starting from the first planned date to the last actual date).
The % weights can be assumed as proportional values to the hours spent for the production of a document or its cost.
This information methodology in EDAM can be substituted by analogue methodology of the contractor, who has in this
case, to make it available to the Company.
In order to make easier the comprehension of this methodology, it is given an example of its application, with the
construction of the two progress curves.
Page 23 of 32
Let’s suppose that the involved disciplines and their % weights in the contract are:
Mechanical 35 %
Process 25%
Electrical 10%
Instrumentation 25%
HSE (Health, Safety, Environment) 5 %
We suppose that for the MECHANICAL discipline there are 2 planned documents, with % weight respectively:
docM1 20 %
docM2 80 %
We suppose that for the PROCESS discipline there are 2 planned documents, with % weight respectively:
docP1 30 %
docP2 70 %
We suppose that for the ELECTRICAL discipline there are 2 planned documents, with % weight respectively:
docE1 25 %
docE2 75 %
We suppose that for the INSTRUMENTATION discipline there are 2 planned documents, with % weight respectively:
docS1 50%
docS2 50%
We suppose that for the HSE discipline there are 2 planned documents, with % weight respectively:
docH1 15 %
docH2 85 %
We suppose that each document will be issued in 2 validity statuses (basic e feed), with % weight respectively 60% and
40%.
In the following table it is reported the calculation to determinate the % value for each validity status, within the discipline
and within the contract.
Page 24 of 32
Weight % of Weight % of Weight % of

Planned documents and the validity the validity the validity
relative validity status status within status within status within
the document the discipline the contract
docM1 basic 60 12 4,2
docM1 feed 40 8 2,8
docM2 basic 60 48 16,8

docM2 feed 40 32 11,2
Total discipline MECHANICAL 35%
docP1 basic 60 18 4,5.

docP1 feed 40 12 3
docP2 basic 60 42 10,5

docP2 feed 40 28 7
Total discipline PROCESS 25%
docE1 basic 60 15 1,5

docE1 feed 40 10 1
docE2 basic 60 45 4,5

docE2 feed 40 30 3
Total discipline ELECTRICAL 10%
docS1 basic 60 30 7,5

docS1 feed 40 20 5
docS2 basic 60 30 7,5

docS2 feed 40 20 5
Total discipline INSTRUMENTATION 25%
docH1 basic 60 9 0,45

docH1 feed 40 6 0,3
docH2 basic 60 51 2,55

docH2 feed 40 34 1,7
Total discipline HSE 5%
TOTAL CONTRACT 100%

Page 25 of 32
Following are reported the planned and the actual dates for each validity status of the above documents.
For each month are reported the cumulative planned and actual values (total per month).
Month/year 1/2008 2/2008 3/2008 4/2008 5/2008 6/2008

pln act pln act pln act pln act pln act pln act
docM1 basic 4,2 4,2

docM1 feed 2,8 2,8
docM2 basic 16,8 16,8

docM2 feed 11,2 11,2
docP1 basic 4,5 4,5

docP1 feed 3 3
docP2 basic 10,5 10,5

docP2 feed 7 7
docE1 basic 1,5 1,5

docE1 feed 1 1
docE2 basic 4,5 4,5

docE2 feed 3 3
docS1 basic 7,5 7,5

docS1 feed 5 5
docS2 basic 7,5 7,5

docS2 feed 5 5
docH1 basic 0,45 0,45

docH1 feed 0,3 0,3
docH2 basic 2,55 2,55

docH2 feed 1,7 1,7
total for month 25,65 50,45 10,65 23,9 7,5 36,65 43,5 1,7
cum pln 25,65 76,10 100
cum act 10,65 18,15 54,8 98,3 100
Page 26 of 32
On the basis of the above mentioned data, it can be compiled the % planned and actual progress curves full life.
On the x-axis there is the time (months) and on the y-axis there are the cumulative planned and actual values at the
month.
Planned and actual % physical progress curves full life cycle
Progress % 12/2007 1/2008 2/2008 3/2008 4/2008 5/2008 6/2008
100 pln 100,00 act 100,00

95 act 98,30
90
85
80
75 pln 76,10
70
65
60
55 act 54,80
50
45
40
35
30
25 pln 25,65
20 act 18,15
15
10 act 10,65
5
0 pln 0 act 0
Page 27 of 32
ATTACHMENT 1 DED (Facility Document List)
Sheet 1 - Cover
Page 28 of 32
Sheet 2 - Index
Page 29 of 32
Sheet 3 - List
Page 30 of 32
ATTACHMENT 2 DEOD
Page 31 of 32
ATTACHMENT 3 TEMPLATE TRANSMITTAL IN (facsimile)

Page 32 of 32
ATTACHMENT 4 TEMPLATE TRANSMITTAL OUT (facsimile)

27608E00

Uploaded by

Copyright:

Available Formats

27608E00

Uploaded by

Document Information

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

27608E00

Uploaded by

Copyright:

Available Formats

Eni S.p.A. 27608.DOC.GEN.

Ref. Code Title Content

This specification explains how to identify

The scope of this document is to define the

1.2 Software to edit documents

Document Type Software Name File extension

Drawings AutoCAD / Microstation .dwg / .dgn / .dri / others

Various Acrobat Writer .pdf

EDAM Engineering Document Approval Management

Surveillance SURVEILLANCE TYPE

It is the Company’s formal answer to the documents sent for approval.

It is an excel file required to contractors, which notifies the sending of documents.

3. REQUIREMENTS AND DELIVERABLES DEPENDENT ON CONTRACTORS AND VENDORS

4. ISTRUCTIONS FOR THE CONTRACTORS

4.1 Interdisciplinary documents

4.2 Indication of code and name of facilities and sub-facilities

The code can have from 1 to 6 alphanumeric characters.

Facility Code Facility Name

0544 Barbara Platform T2

The code shall have 2 alphanumeric characters.

1A Barbara Platform T2 – Cluster A

Assignment of ranges of alphanumerical codes

Assignment of code to vendor/contractor

It is a registry code of vendors assigned by Company to contractors/vendors.

4.3 Communication of the names of Company representatives

He approves the planned documents list with relative validity status

FEM He approves the transmittals OUT and the comment sheets of

Interdisciplinary function, he consolidates and integrates the

4.4 Disciplines for the progress of the engineering activities

It can also be agreed a correspondence table among:

4.5 Instructions for sending the documentation

Transmissions from Contractor to Company

The name of the Transmittal IN shall be:

Transmissions from Company to Contractor

The name of the Transmittal OUT shall be:

The file name of the Comment Sheet shall be:

Comment sheet contractor’s reply (if any)

The file name shall be:

4.6 Data Loading Files for DED, DEOD and TRANSMITTAL IN

5. DOCUMENT PROGRESS REPORT (DPR)

• Data available from file DED (Facility Document List)

In APPENDIX 6, it is reported the list of the data to be inserted in the DPR.

APPENDIX 1 DOCUMENTO ELENCO DOCUMENTI (DED) – FACILITY DOCUMENT LIST

It shall be issued in final emission in correspondence of each project phase’s end.

Following the descriptions of the headers:

APPENDIX 2 DOCUMENTO ELENCO OPERATIVO DOCUMENTI (DEOD)

The Company can, at any time, request for modifications or integrations.

The data shall be reported in the Document Progress Report.

Following the standard template in excel:

Company Work Package 1

(First) Issue for comments (C) - Replanned date 19

Following are reported the descriptions of the not highlighted headings.

The transmittal is an excel file, which contains 2 records (see below).

DATA SET OF TRANSMITTAL IN

Following are reported the indications on the columns’ headings:

Transmittal IN ID Transmittal IN Identification number

DATA SET OF THE DOCUMENTS ATTACHED TO THE TRANSMITTAL IN

ENI Document Document

Each document shall be reported on one row.

File Name File name of the attached document