eni spa

COMPANY TECHNICAL STANDARD

INFORMATION SUBMISSION

06219.VAR.LCI.STD
Rev.01 - December 2016

Previous identification code

06219.CAE.GEN.SDS
Rev.01 – December 2016

GENERAL NOTE This Re-coding does not affect the document content.
TO THE Documents traceability is guaranteed by the unchanged document
DOCUMENT RE-
number.
CODING
Any cross-reference between documents remains unaffected.
/
La presente ricodifica non ha effetto sul contenuto del documento.
NOTA
GENERALE
La rintracciabilità dei documenti è garantita dal numero di documento
ALLA che resta immodificato.
RICODIFICA I riferimenti incrociati fra i vari documenti rimangono validi.

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di Eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is property of Eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 3 of 16

Consulted Distribution List

Date Name Surname/Business Unit COMPANY

December 2016 A. Marceglia /MECC/TEIN Eni/PMEC/TA&E

December 2016 M. Fumagalli /TESA/TEIN Eni/PMEC/TA&E
December 2016 S. Gariboldi /INSU Eni/PMEC/TA&E
December 2016 N. Martinenghi /INSU Eni/PMEC/TA&E
December 2016 M. Ronchini /SECO/SMECO Eni/PMEC/OE&C

Informed Distribution List

Date Name Surname/Business Unit COMPANY

December 2016 M. Barbieri /TA&E Eni/PMEC

December 2016 L. A. Cambiaso /TEIN Eni/PMEC/TA&E
December 2016 M. Bacchini /FATA Eni/PMEC/TA&E
December 2016 M. Oddone /SMECO Eni/PMEC/OE&C

REVISION TRACKING

Rev 00: Actual revision is of 13 pages – First Emission

Date: February 2011

Rev 01: Actual revision is of 18 pages

Revision to comply with LCI Requirements
Date: September 2016

INFORMATION REQUEST

Eni personnel can access COMPANY standard repository at:

http://wwweandp.eni.it/TSServices/ITEM/Standards-/Normalizat/Documents-/index.asp

External user shall refer to the Project Engineer Manager.

For information about the content of this standard, please refer to responsible and accountable
person as per above RACIE table or to Technical Authority coordinator (COETA).

HIERARCHY OF REGULATIONS

1. Local Regulations of the Country where the equipment is installed;

2. Project Specifications and Data Sheets;
3. COMPANY General Specifications;
4. International Codes & Standards

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 4 of 16

1 GENERAL ............................................................................................................. 5
1.1 SCOPE ............................................................................................................ 5
1.2 DEFINITIONS ................................................................................................... 5
1.3 ACRONYMS ...................................................................................................... 5
1.4 ROLES AND RESPONSIBILITIES ......................................................................... 6
2 REFERENCE REGULATIONS.................................................................................. 6
2.1 EUROPEAN REFERENCE REGULATIONS................................................................ 6
2.2 CEE REGULATIONS ........................................................................................... 6
2.3 REFERENCE DOCUMENTS AND PROGRAMS .......................................................... 6
3 INFORMATION SUBMISSION OBJECTIVES .......................................................... 7
4 INFORMATION SUBMISSION STRATEGY ............................................................. 8
4.1 SUBMISSION TEST ........................................................................................... 8
4.2 PROGRESSIVE SUBMISSION .............................................................................. 9
4.3 FINAL HANDOVER ............................................................................................ 9
4.4 DELIVERABLES SUBMISSION SUMMARY ............................................................ 11
5 HIGH LEVEL SOLUTION AND PROCESS WORKFLOW .......................................... 12
5.1 DATA SUBMISSION ........................................................................................ 12
5.2 DOCUMENTS SUBMISSION .............................................................................. 13
5.3 DATA VALIDATION ......................................................................................... 14
6 SUBMISSION TIMING ....................................................................................... 16
6.1 ENGINEERING PLANT DATA ............................................................................. 16
6.2 PROCUREMENT DATA & VENDOR DATA ............................................................. 16

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 5 of 16

1 GENERAL
COMPANY requires access to correct information as early as possible in order to manage and
prepare the final handover, develop maintenance/inspection plans, evaluate and purchase
spares, familiarization/training etc. COMPANY requires to have this information available from
CONTRACTOR during the entire project life cycle and as a final handover.

1.1 SCOPE
The scope of this document consists in describing the management of information, data and
document from CONTRACTOR to COMPANY in terms of activities, roles and responsibilities for
the collection, organization and transmission during the Project Phases and handover.

1.2 DEFINITIONS
Term Description
The party that initiates the project and ultimately pays for its
design and construction. COMPANY will generally specify
COMPANY technical requirements. The term “COMPANY” also includes
agents or consultants authorized to act for, and on behalf of,
COMPANY.
An acceptance of legal relations between two or more parties
CONTRACTOR
for the transfer of goods or services for value.
EDMS Electronic Document Management System
EMIMS Template Excel Templates for Information Submission to EMIMS

1.3 ACRONYMS
Term/Abbreviation Description
CAD Computer Aided Design
CMMS Computerized Maintenance Management System
Documento Elenco Operativo Documenti (Facilities Document
DEOD
List)
Engineering Document Approval Management (COMPANY
EDAM
Document Management System)
EDMS Electronic Document Management System
ENS Engineering Numbering System
EMIMS Engineering Master Information Management System
LCI Life Cycle Information
MDR Master Document Register
MTO Material Take-Off
OPD Opportunity and Project Development
P&ID Process and Instrumentation Diagram
PBS Plant Breakdown Structure
PDF Portable Document Format
SW Software
TA ENI Technical Authorities
TBD To Be Defined

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 6 of 16

1.4 ROLES AND RESPONSIBILITIES

This section identifies roles and responsibilities in relation to the data and key documents
references collection and transmission to COMPANY.
Under the provisions of scope and contract from COMPANY, CONTRACTOR shall review and
comply with the instructions set out in this document before starting any activity subject to
this scope and correlated EMIMS data transfer.
Any variations and exceptions shall be agreed with COMPANY before the commencement of
activities by CONTRACTOR.

2 REFERENCE REGULATIONS

2.1 EUROPEAN REFERENCE REGULATIONS

None applicable.

2.2 CEE REGULATIONS

None applicable.

2.3 REFERENCE DOCUMENTS AND PROGRAMS

REF DOC. NUMBER TITLE

[1] 28080.DOC.GEN.SDS Facilities Life Cycle Information Management Procedure
Data Model Of Plant Components Data And Key
[2] 20203.DOC.GEN.SDS
Document
Maintenance Management Data From Vendors and EPC
[3] 27954.MAN.GEN.SDS
CONTRACTORs
Technical documentation required during the project
[4] 27605.VAR.GEN.SDS
development phase
[5] 28081.DOC.GEN.SDS Standard Rules For As Built Preparation

[6] 27608.DOC.GEN.SDS Document Management Procedure

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 7 of 16

3 INFORMATION SUBMISSION OBJECTIVES

It is COMPANY requirement to manage a progressive Handover process (Monthly Base) to have
a punctual information submission essential to avoid any possible delay in the project schedule
and to limit any negative impact on the facilities start-up and operation.

In order to achieve this goal, COMPANY has identified a minimum set of information that shall
be submitted regularly and loaded into COMPANY systems EMIMS.

The information subject to the defined processes in this procedure is classified as:

• Project Data: all data produced during the project

• Documentation/Data: documents and related data produced during the project
• Project Tools Data: applications adopted for the project
• Final Data Handover
• Input Native Files

Each of the above listed information shall be transferred according to a specific mode and a
defined schedule, as indicated in the following table:

Information Minimum Transfer Schedule

Project Data Progressive Submission ( Monthly Base )
Progressive Submission as per document management
Documentation
procedure
Project Tools Final Handover
Final Data Handover Final Handover
Input Native Files Final Handover

The main purpose is to collect all the information during the course of the project as the
information becomes available in order to have a final set of comprehensive and consistent
information at the handover stage.

For this purpose, strict coordination is essential in order to set-up and manage the project tools
and all the processes required to collect and transfer the information efficiently. As specified in
the referenced document [1], CONTRACTOR shall appoint a single reference for the information
submission activity and enough resources to ensure that the configuration and change
management tasks are properly carried out and do not compromise the overall work execution.

For all third parties, including Subcontractors, electronic information will be submitted to
COMPANY via CONTRACTOR and shall be treated as formal documents with associated
metadata.

An LCI transfer or sharing procedure with COMPANY’s systems shall be established during the
first issue of the LCI plan as indicated in the reference document [1]. The procedure shall
include transfer methods, information logistics, systems involved, responsibilities, milestones,
quality controls, errors reporting and error rectification procedures.
A test transfer of electronic information shall be carried out as soon as possible to verify the
data transfer procedures. This shall include all relevant digital formats types.

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 8 of 16

4 INFORMATION SUBMISSION STRATEGY

Information shall be handed over progressively from CONTRACTOR to COMPANY during the
project execution. In order to achieve the complete handover, COMPANY has identified a
guideline composed by the following three submission stages:

• Submission Test;
• Progressive Submission;
• Final Handover.

Each project shall issue and keep up-to-date a document defining the methodologies and
planning, including transfer method, information logistics, systems involved, responsibilities,
milestones, quality control, error reporting and error rectification procedures.
This document shall describe submission in terms of:

• Data submission into EMIMS tool;

• Documents submission into EDAM tool;
• Project Native Tools Backup.

4.1 SUBMISSION TEST

This phase represents a test for the processes and applications involved in the data and
documents submission to COMPANY. It will involve all Project tools and Indexes but only a
limited set of information. In this phase the information shall be submitted to COMPANY along
with all the data available in the systems and shall be carried out as soon as possible to verify
the data.
Due to the preliminary engineering at this stage, the complete data consistency does not have
to be ensured yet by CONTRACTOR.

The main goals of this phase are:

• Verify the information submission processes

• Verify that CONTRACTOR adheres correctly to COMPANY’s numbering procedure
• Verify that the Project Tools have been configured and used according to COMPANY
indications.

This phase is based on CONTRACTOR’s work processes, with a main focus on:

1. Management of documents data sources;

2. Setting a method to gather all this kind of info;
3. Establishing an internal data validation in order to cope with problems as soon as they
appear, such as inappropriate measurements, data inconsistencies, etc.;
4. Production of datasets to be delivered to COMPANY;
5. Validation of submitted information on COMPANY’s systems;
6. Production of consistent reporting;
7. Uploading of accurate data on COMPANY’s systems;
8. Addressing actions about inconsistent data.

The above list corrective shall prove CONTRACTOR’s capability meat COMPANY’s needs across
the overall submission process.

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 9 of 16

4.2 PROGRESSIVE SUBMISSION

This phase includes the process that CONTRACTOR shall put in place during the project
execution and maintain until Final Handover. Data submission shall take place across different
project disciplines and functions.

CONTRACTOR shall submit for COMPANY approval a project set of documents to define the
Information Submission Schedule aligned with project deliverables schedule. CONTRACTOR
shall submit project data to COMPANY using EMIMS functions on a monthly basis and a final
set for handover.

4.3 FINAL HANDOVER

This step has to encompass all the COMPANY’s data and documentation requirements. It should
certify that CONTRACTOR’s activities have been completed and fully documented.

This step represents the Final information submission and occurs at the end of the project
activities, including all Engineering, Procurement and Construction information and project
documentation, in as-built status. Considering the final status of the engineering stage, the
complete data consistency has to be ensured by CONTRACTOR: please refer to the paragraph
6.4 “Data validation” for more details about information consistency requirements.

Final Handover can be split into three macro-areas:

1. Final Handover of documentation;

2. Final Handover of native drawings, systems and models;
3. Final Handover of data.

The Final Handover shall be considered complete when the following requirements are met:

• Loading data on COMPANY’s systems without errors;

• Delivery of native engineering applications backups;
• Delivery of documents in final native version, along with operation manuals for the
Operations team.

CONTRACTOR's commitments shall be completed when all required INFORMATION has been
received and accepted by COMPANY. All vital and essential non-compliance items shall be
closed out before the final INFORMATION Package acceptance.

Information handover includes:

• Formatted excel files populated with Project Data – EMIMS Template V5R0.
• As-built data EMIMS Template.
• Project backup of native engineering applications ( 3D and 2D Models ). For each
applications it is required a descriptive set of documentations.
• Project documentation in EDAM

With reference to COMPANY document [1] CONTRACTOR shall guarantee that the final LCI
reflects the as-built status of the facilities at the take-over by Operations.

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 10 of 16

4.3.1 Final Handover of Documentation

The final handover shall include all the documentation produced during the project life cycle as
listed in the referenced document [4] with all documentation in latest emission and in As-Built
status.

The table below summarize the requirements for the final handover:

Document Set Requirement

As-built status for the documents listed in the referenced
Project Documentation
procedure [4]
All project documents listed in referenced procedure [4]
Project Documentation
loaded in COMPANY’s system EDAM
Electronic file in pdf format (text searchable) and the
Project Documentation
electronic source file used to generate the pdf.
Project Documentation Delivered in a paper format if required by project
When paper copy documents are the only format
available they shall be scanned into text searchable pdf
Paper Documentation
format. Paper copy is also subject to handover to
COMPANY.
Final DED version containing all the documents
DED Document submitted to COMPANY. This document shall be handed
over in source electronic format.
Final DEOD version containing the final status of
DEOD Document documentation produced. This document shall be
handed over in source electronic format.
Containing all the documentation required in the
Final Dossier
referenced procedure [4]

4.3.2 Final Handover Intelligent Drawings and Models

CONTRACTOR shall deliver the as-built populated engineering database and other related
databases used, such as 3D Model, P&ID, Electrical, Instrumentation and other applications in
accordance with the agreed transfer format and schedule.

4.3.3 Final Handover of data

CONTRACTOR shall ensure that the final information submission shall be compliant with the
LCI Requirements listed in this document and in the other referenced documents.
CONTRACTOR shall deliver a final set of excel files populated with the Project Tools information
and Indexes in as-built status.

COMPANY shall review the INFORMATION provided by CONTRACTOR to ensure compliance with
the CONTRACT in terms of Data Quality, Consistency and Completeness.
The outcomes of this review will be notified to CONTRACTOR; CONTRACTOR shall revert
comments within one (1) month from receipt of COMPANY's comments, unless otherwise
approved by COMPANY.

COMPANY’s final review is not a substitute for CONTRACTOR's own quality control system and
does not relieve CONTRACTOR from any responsibilities related to the quality of procedures,
activities and delivery times. This final review shall only be conducted after CONTRACTOR has
carried out a documented an internal quality control on the INFORMATION HANDOVER package.
CONTRACTOR shall close-out all vital and essential non-conformance items before COMPANY
accepts the final HANDOVER package.

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 11 of 16

4.4 DELIVERABLES SUBMISSION SUMMARY

4.4.1 Information Delivery Formats

CONTRACTOR shall deliver to COMPANY the native format file and, where stated, autocad
format and portable document format (PDF) versions of the formal documents.
The table below illustrates examples of the deliverables formats:

Formal
Information
Native File Format Deliverable
Type
Format
Deliverables from In General the native file format is the database itself. PDF/Native
Project Tools Documents produced directly from the database may be
delivered as PDF files. Documents which are edited
externally shall be delivered in the appropriate file format
listed in this table. For example, layout drawings
produced from the 3D model if edited externally shall be
developed in AutoCAD or SmartPlant 3D tools.
P&ID Drawings The native file format is the tool adopted for the Project PDF/Autocad
but for the final delivery the P&ID shall be delivered also
in Autocad format.
Documents (Single MS Word PDF/Native
format) MS Excel –CSV format
MS PowerPoint
Other agreed formats (e.g. Visio)
Web based applications supporting Windows Explorer
Documents These are documents that have been created in several PDF/Native
(Multi formats – applications as above. The multiple native files shall be
e.g. Word, Excel, placed together in a zip file as the native format for the
Visio) document. Note that embedded files shall not be used.
Engineering Data Database or Excel and in native design system format. PDF/Native
Engineering design Engineering design models e.g. process and other PDF/Native
models specialist modelling and analysis/ design packages Native
format of specific package, (e.g. HYSIS, STAAD, SESAM).
3D Models Design Navisworks Freedom viewable format Native
Review Native Design Review

Native files handed over to COMPANY shall not include embedded or external links to additional
data and/or files unless they conform to COMPANY requirements. If non-standard font sets are
used, a standard font shall be substituted or a copy of the non-standard font set shall be
supplied to COMPANY.
Documents supplied by SubCONTRACTOR shall be subject to the same requirements as those
supplied by CONTRACTOR.

4.4.2 Digital Delivery Requirements

In general, all LCI information shall be transferred in digital format and loaded in COMPANY
indicated systems. No hard copy of documentation shall be delivered unless otherwise specified
and requested by the Project. The digital version shall be considered the original format of the
information. All changes to the LCI Information shall be performed on the digital original file.

4.4.3 Language
In General documents and drawings shall be in English language; where specified some
documents (for example documentation for local authorities) should be in the Project local
language.

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 12 of 16

5 HIGH LEVEL SOLUTION AND PROCESS WORKFLOW

5.1 DATA SUBMISSION

The overall process for data submission is shown in the Figures here below:

EMIMS

PROJECT STAGING AREA

Action Description
CONTRACTOR extracts the data from its engineering systems according to
1 COMPANY templates and requirements. CONTRACTOR performs data quality
check

2 CONTRACTOR uploads the data in a COMPANY System (EMIMS Staging Area).

3 CONTRACTOR performs quality check in EMIMS

If check is positive, CONTRACTOR submits EMIMS Templates to COMPANY for

3a
data validation ( see Action 4 )

In case of failure, CONTRACTOR returns the data for re-elaboration ( see Action
3b
1)

4 COMPANY performs data validation.

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 13 of 16

5.2 DOCUMENTS SUBMISSION

The overall process for documents submission shall be compliance with ref. [6] as shown in
the Figures here below:

Action Description
CONTRACTOR systems produce:
• DEOD template, contains information related to all information delivered
1
by CONTRACTOR.
• Documents and Data required by COMPANY
CONTRACTOR performs DEOD Template quality check and submits to COMPANY
2
Approval

If check is negative and in case of failure, CONTRACTOR returns the data for re-
3a
elaboration ( see Action 1 )

If check is positive, CONTRACTOR sends documents, metadata and DEOD

3b
Template requested by COMPANY ( see Action 4)

4 COMPANY validates DEOD and upload into EDAM.

Every DEOD change shall be tracked according to the above workflow.

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 14 of 16

5.3 DATA VALIDATION

CONTRACTOR is responsible for the quality of information (data, documents and model)
delivered to COMPANY through excel formatted files for COMPANY EMIMS population purposes.

CONTRACTOR has to ensure the consistency and quality of the data via two levels of analysis:

1) Vertical Checks: these checks are focused on the single project tools, checking the
quality and the consistency of the data considering one-by-one tool

2) Cross Checks: these checks target multiple databases of project tools, checking the
quality and the consistency of the data across them.

3) The following picture gives an example of the meaning of vertical and cross check
analysis:

Vertical Checks Cross Checks

CONTRACTOR shall provide COMPANY a detailed description of the operating procedures to be

carried out in order to ensure the Information Quality of the design process, during the entire
Engineering phase.

CONTACTOR can cover these topics as part of the Information Management and Consistency
Specification, including:

a) Data Integrity checking tools and procedures

b) Data Completeness checking tools and procedures
c) Detailed procedures for handing over data, receiving error reports and correcting
errors
d) Control of TAG numbers
e) Data validation methods
f) Change control and other procedures for assuring data integrity
g) Error trapping and reporting

Therefore, along with the specification and during the Project handover phases, CONTRACTOR
has to provide COMPANY a set of checking reports, proving the performed verifications and the
quality of the data.

Here below an example of a checking report to be provided to ensure the consistency and
quality of the item TAGs:

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 15 of 16

Actions Vertical Cross

Check Check
Check naming rules consistency with Project Tag Numbering
√
Procedure
Check null/not null tags √
Check duplicated item tags √
Check tags presence between P&ID and 3D design tools
√
(Equipment tags that exist in P&ID and that are missing in 3D)
Check tags presence between 3D and P&ID design tools
√
(Equipment tags that exist in 3D and that are missing in P&ID)

However, COMPANY is aware that the quality of the Engineering information depends on the
project progress and that the data global consistency can be ensured in the “as built” phase
only.

The following table summarizes the minimum COMPANY expected results, in accordance with
the handover phases defined in chapter 5 “Information Submission Strategy”:

Handover Required Consistency Level

Phase Vertical Check Cross Check
Handover test TAG consistency and quality TAG consistency and quality
Final Handover All data belonging to excel for All data belonging to excel for
EMIMS population must be EMIMS population must be
validated in terms of consistency validated in terms of consistency
and quality and quality

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.
eni spa 06219. CAE.GEN.SDS
Rev. 01 – December 2016
Pag. 16 of 16

6 SUBMISSION TIMING
CONTRACTOR shall define a schedule for the submission of information to COMPANY.

The issue of any revision of Project and Operations documents shall include the submission of
the relevant subset of information in the format and manner defined in the present COMPANY
Specification.

At Project milestones, complete packages of information shall be submitted according to the

milestone scope of work.

CONTRACTOR shall prepare the submission plan in accordance with the principles contained in
the transfer schedule guidelines described in the following paragraphs.

The table below summarizes the requirements:

Information Type Submission Schedule Data included

Engineering Data On monthly basis Includes all CONTRACTOR’s or
Subcontractor’s engineering
data. Data should be available
when the design is in Approved
For Design , Approved For
Construction ( AFC ) or Issued
For Order ( IFO )
Procurement & Vendor Data On monthly basis As soon as a relevant document
arrives, CONTRACTOR should
provide COMPANY with a set of
metadata about systems.
Data should be provided when
the purchase order has been
issued.

6.1 ENGINEERING PLANT DATA

The information required in this paragraph is mainly referring to the “Engineering Plant data”
described in ref. [2].
COMPANY has linked the information progressive submission to the issuing of P&IDs where
many other documents and lists containing relevant information have already issued.
CONTRACTOR shall submit the information to COMPANY based on the official issuing of P&IDs
starting from the first revision and then at every new issue of the P&IDs.
In addition to P&IDs documents, CONTRACTOR shall provide Excel templates as indicated in
the lists in ref. [2].

6.2 PROCUREMENT DATA & VENDOR DATA

The information in this paragraph makes reference to the “Vendor & Manufacturer data”
described in ref. [2].
In order to manage the expediting and inspection activities, during the project execution
CONTRACTOR shall submit to COMPANY on a monthly basis the information regarding the
Purchase Order issued.
This information shall be submitted using the Excel template defined in ref. [2].

ENGINEERING COMPANY STANDARD

Documento riservato di proprietà di eni spa. Esso non sarà mostrato a terzi né utilizzato per scopi diversi da quelli per i quali è stato inviato.
This document is the property of eni spa. It shall neither be shown to third parties nor used for purposes other than those for which it has been sent.