Fljor.: Project Requirements and

CONTRACT N° UNIT N°
STAR RAFINERI A.S.

S3ST
SHノ OF
FLJOR. AEGEAN REF:NERY
1/15
PROJECT(ARP) STAR SPECIFiCAT:ON N°
000Ⅲ A¨ PE‐ 0020002
REV 10 11 12 13 14
Project lT requirements and Electronic Deliverable

instruction
灘剛
STAR RAFINERI A.S. CONTRACT N°
AEGEAN REFINERY PROJECT (ARP) S3ST
SH/OF
Project IT requirements and 2/15
Electronic Deliverable STAR SPECIFICATION N°
instruction 000-A-PE-0020002
REV 0 1 2 3 4
TABLE OF CONTENTS
1 General ....................................................................................................................................3
1.1 Scope ..........................................................................................................................3
1.2 Basic Description.........................................................................................................3
1.3 Automation Plan ..........................................................................................................3
1.4 References ..................................................................................................................3
2 IT REQUIREMENTS ................................................................................................................5
2.1 Network Requirements................................................................................................5
2.2 Information Security requirements ..............................................................................5
2.3 Communication ...........................................................................................................5
2.4 IT Requirements for Resident team ............................................................................6
2.5 Site IT Infrastructure....................................................................................................6
3 SOFTWARE APPLICATIONS..................................................................................................7
3.1 2D CAD .......................................................................................................................7
3.2 3D MODEL ..................................................................................................................8
3.3 Instrument Database .................................................................................................10
3.4 Electrical Database ...................................................................................................11
3.5 Line List Data ............................................................................................................11
3.6 Mechanical Equipment List .......................................................................................11
4 ELECTRONIC DELIVERABLES AND FORMATS.................................................................12
4.1 Document Requirements...........................................................................................12
4.2 Additional drawing requirements ...............................................................................13
4.3 Data Handling............................................................................................................13
4.4 Metadata ...................................................................................................................14
4.5 TAG-Document relationships ....................................................................................15
SH/OF
REV 0 1 2 3 4
1 GENERAL
1.1 Scope
The purpose of this specification is to define the Contractor’s automation requirements
with respect to electronic deliverables, electronic deliverable formats and required
software applications to create the electronic deliverables. Additionally, this specification
outlines the requirements for implementation of the automation systems.
All electronic deliverables shall be consolidated at the conclusion of the project for delivery
to Owner. Contractor is responsible for managing all documents and deliverables
produced and or updated as part of the Services of the Project. The requirements outlined
in this specification shall also apply to all Contractor’s vendors and Subcontractors.
1.2 Basic Description

This specification shall serve as the guideline for Contractor in both conducting the work
and preparing the engineering deliverables. Documents are required to be delivered to the
Owner at various milestones during the Project and at the conclusion of the Project. Any
additional cost or schedule impact resulting from deviations of this specification will fully be
at the expense of the Contractor.
1.3 Automation Plan

The Contractor shall submit to the Owner an Automation Plan providing the details of how
the Contractor will execute the Project in accordance with the requirements defined in this
specification.
1.4 References
Table 1 – Abbreviations
Abbreviation Description
CAD Computer-Assisted Design
EDMS Electronic Document Management System
EPC Engineering, Procurement and Construction
PDF Portable Document Format
PFD Process Flow Diagram
P&ID Piping & Instrumentation Diagram
PDS Integraph Plant Design System
SP3D Integraph SmartPlant 3D
SPE Integraph SmartPlant Electrical
SPI Integraph SmartPlant Instrumentation
Table 2 - References to Specifications

SH/OF
REV 0 1 2 3 4
Number Description
000-A-PE-0020001 Owner Drawing and Document numbering
000-A-PE-0020003 Handling of Engineering and Design documents
000-A-PE-0020005 3D-Model Review and Required Content of a 3D-Model
000-L-PE-0020001 Line list Preparation Instructions
000-J-PE-0020002 Minimum requirements for SPI database
SH/OF
REV 0 1 2 3 4
2 IT REQUIREMENTS
2.1 Network Requirements

As part of the automation plan Contractor shall provide an overview of the Project Area
Network proposed for use on the project. This overview shall encompass all work
locations and should include:
 Proposed links including type and speed.
 Network devices including servers, switches and other required hardware.
 Back up application and devices.
 Owner facilities (refer to 2.4)
2.2 Information Security requirements

Technical data and information received from Owner is proprietary and is subject to the
conditions of the contract. Contractor shall submit as part of the automation plan
procedures addressing:
 Project area access and security.
 Server Room access and security.
 Network access policy, including but not limited to granting and control of project user
access/logon to systems.
 Backups and offsite storage of project data
2.2.1 Virus protection

Contractor shall submit to Owner for approval as part of their plan procedures addressing
how information will be protected against virus attack. Scope shall include:
 Desktops.
 Laptops.
 Servers.
Data sent electronically from Contractor and suppliers to Owner shall be free from viruses.
2.3 Communication
2.3.1 Electronic Mail

Contractor to list which Electronic Mail System will be used for Mail correspondence within
the Contractor organization (especially to list the limitations like file size of attachments).
Microsoft Outlook will be used by the Owner. Lotus Notes Mail will be used by the PMC.
SH/OF
REV 0 1 2 3 4
2.4 IT Requirements for Resident team

Contractor shall supply the following IT services for Owner personnel located at
Contractor’s office during the project:
 Contractor shall provide a high speed Internet connection with a minimum bandwidth
of 10Mbps to allow the Owner personnel to setup a Virtual Private Network (VPN) to
the Owner Network.
 Contractor shall provide qualified IT Technical support as required. Contractor
support staff shall assist Owner personnel.
 Contractor shall provide Owner access to the Contractor’s Document Management
system for document review. Documents issued for review should be in pdf format.
 Contractor shall provide Telephone with international access rights for each Owner
personnel member.
 Contractor shall provide facilities for video conferencing, remote model & P&ID
reviews etc.
 Contractor shall provide Printing, Scanning and Copying facilities for Owner personnel
members (Color printing and Black and White printing).
2.4.1 Video Conference System

The Contractor shall make available a video conference system that supports SIP or
H.323 video protocol.
The system should be able to communicate with a Tandberg video conference system:
 Tandberg C40 system (with two 52" LCD screens)
 Tandberg 1700MXP system (with 20" screen)
2.5 Site IT Infrastructure

The Contractor is responsible for the IT infrastructure on the Construction site for
Contractor, Subcontractors and the Liaison team located in the Contractor site office. The
Contractor shall arrange for sufficient Data connections, Voice circuits, Hardware and
Software to execute the work.
SH/OF
REV 0 1 2 3 4
3 SOFTWARE APPLICATIONS
Contractors shall use the following software applications and versions:
Table 3 - Software applications, versions and formats

Type Software Application Version Final Format
Drawings AutoCAD 2007, 2008, pdf and dwg
2009
Spreadsheets Microsoft Excel 2007 pdf and xls
Textual Documents Microsoft Word 2007 pdf and doc
Lists / Databases Microsoft Access 2007 mdb
Databases Oracle 10gR2 Complete archive
Portable document format Adobe PDF format 9.0 or higher pdf
Instrument Database SmartPlant Instrumentation (SPI) 2009 Complete archive
Electrical Database SmartPlant Electrical (SPE) 2009 Complete archive
Electrical System Analysis ETAP 7.5 Complete archive
3D Model PDS V11 Complete archive
SmartPlant 3D (SP3D) 2009
Model review SmartPlant Review 2008 vue & mdb & mdb2
Drawings (extracted from Microstation V7 or V8 dgn (intermediate)
3D model) dwg (final)
Schedules Primavera P6
Contractor shall comply with all requirements to implement the Owner approved versions
of the project applications.
Any deviations or alternatives from the above listed software applications, versions or
formats must have prior approval from the Owner.
Contractor shall provide native formats of all final project deliverables.
New versions of the above listed applications may be released during the life cycle of the
Work.
All decisions to implement newer versions of the project applications will be at the
discretion of the Owner.
Versions selected shall be identical for all locations.
3.1 2D CAD
3.1.1 General
AutoCAD shall be used to create the 2D drawings of the Facilities with the exception of
drawings developed using 3D software. 2D drawings include the following:
 Process Flow Diagrams (PFD)
 Material Selection Diagrams (MSD)
 Piping & Instrumentation Diagrams (P&ID)
 All other drawings not generated from 3D systems.
SH/OF
REV 0 1 2 3 4
3.1.2 Symbology and Settings

Contractor is to provide detailed documentation pertaining to level symbology and settings
used during the development of any 2D Drawing. This document must be handed over as
part of the project execution plan after contract award.
3.1.3 Border Files

Standard project border files will be provided.
3.1.4 CAD deliverables

The following items are considered to be part of the CAD deliverables that the Contractor
shall deliver electronically to Owner.
 All block and cell library files
 All font libraries and font resource files
 All AutoCAD line style resource files
3.1.5 Drawing units

Drawing units shall be set to meters. In case of Microstation drawings units to be set to
1000 mm per meter and 100 units per mm
Contractor shall verify the drawing units of the delivered FEED drawings. The Contractor
shall modify the drawing units to make them consistent with this specification.
Note: final Drawing units to be agreed during start of EPC
3.2 3D MODEL
3.2.1 General
Contractor shall develop a 3D electronic model of the facilities.
 The 3D model shall be a complete representation of the plant design, including spatial
configuration, database content, drawing production, document meta-data, etc.
 The 3D model shall be utilized during design, constructability reviews, construction
sequencing reviews, and for operator training.
 The 3D model shall be delivered to the Owner (as built) prior to the start of
commissioning of each Plant for operator training purposes.
The 3D modeling system must be used to produce required documents like isometrics,
plan and elevation drawings, etc., as well as piping material take-offs.
One of the main objectives of the 3D model is interference checking and data integrity to
reduce the rework during construction to a minimum. This means that all physical objects
that are part of these drawings, reports and/or interference checking will need to be
modeled.
Contractor shall prepare a clash detection procedure, including proposed construction
tolerances and submit to Owner for approval.
SH/OF
REV 0 1 2 3 4
3.2.2 System & Version

The 3D Model shall be developed using Intergraph PDS or SP3D. Use of an alternative
system and version must be agreed upon by the Owner, before project start.
SmartPlant review 2008 shall be used for all model reviews.
3.2.3 Symbology and Settings

The 3D CAD based design system shall consist of the standard design platform provided
with Intergraph’s 3D software application. This system includes the standard level
assignments, cells and database as defined within that application.
Contractor is to provide detailed documentation pertaining to level symbology and settings
used during the development of the 3D model. This document must be handed over as
part of the project execution plan after contract award.
3.2.4 Design Boundaries

Overall Plant Model Design Boundaries are: To be defined during start of EPC
Plant monument: To be defined during start of EPC
For details see CSA reference documentation. Contractor shall prepare a drawing defining
the partitions physical boundaries.
3.2.5 Working units

Working Units:
 Master units = m
 Sub units = mm
Resolution:
 Sub Units = 1000
 Positional Units = 100
Note: final working units to be agreed during start of EPC
3.2.6 3D Model Content

3D Model content shall include all special items as identified in the Model Review Matrix at
the milestone dates as indicated in specification 000-A-PE-0020005 - “3D-Model Review
and Required Content of a 3D-Model”.
3.2.7 Coordinate System

All 3D models shall be based on the STAR coordinate / elevation system.
SH/OF
REV 0 1 2 3 4
3.2.8 Extracted 2D Drawings

Extracted 2D drawings shall be in Microstation format. Final format shall be AutoCAD.
 All drawings must be provided at handover with all reference files merged
 Line and Font resource files must also be provided
3.2.9 Border Files

Standard project border files will be provided. The Supplied border file can be modified by
Contractor in origin to suit 3D design Application after Companies approval.
3.2.10 Model Data Handover

Additional requirements at data handover
 The 3D model shall be delivered to the Owner as a full (PDS) Archive, including all
relevant files.
 The final Smart Plant Review session, in both VUE format
3.3 Instrument Database

Contractor shall use the Smart Plant Instrumentation (SPI) application software from
Intergraph to produce and manage an integrated system for instrumentation design and
engineering.
The Contractor shall configure SPI in accordance with the applicable project standards
and issue the configuration template for review.
The Contractor shall deliver to Owner a SPI database at project completion which is as-
built, uniform and consistent for all units of the Refinery.
As a minimum, the following documents shall be developed in SPI in accordance with
Owner’s approved format and templates:
 Instrument Engineering Index – “Instrument Index”
 Instrument Design Index
 Instrument Datasheets
 Wiring Schedules and Cable Schedules
 Junction Box Schedule
 Loop Diagrams
 Construction Work Package Identification for each Instrument item
For other SPI requirements refer to Specification 000-J-PE-0020002 - Minimum

requirements for SPI database.
The content of the database and documents as listed above, shall include all 3rd party
deliveries, such as Package Units, HVAC etc.
SH/OF
REV 0 1 2 3 4
3.4 Electrical Database

Contractor shall use the Smart Plant Electrical (SPE) application software from Intergraph
to produce and manage an integrated system for electrical design and engineering.
The Contractor shall configure SPE in accordance with the applicable project standards
and issue the configuration template for review.
The Contractor shall deliver a SPE database at project completion which is as-built,
uniform and consistent for all units of the Refinery.
As a minimum, the following deliverables shall be prepared in SPE:
 Electrical Load Lists
 Electrical Equipment Lists
 Electrical Cable Lists
 Low Voltage Electrical Cable Sizing Calculations
 34.5 / 11 and 6.3 kV Electrical Cable Sizing Calculations
 Power Center Switchgear Schedule
 Motor Control Centers Schedule
3.5 Line List Data

Contractor shall deliver a Line List in Excel format. Refer to 000-L-PE-0020001 Line list
Preparation Instructions.
3.6 Mechanical Equipment List

Contractor shall deliver an Equipment list in Excel format.
SH/OF
REV 0 1 2 3 4
4 ELECTRONIC DELIVERABLES AND FORMATS

Information created during the project is of value for the engineering, operations and
maintenance of a process plant during its lifecycle.
Electronic documents shall be transferred to the Owner upon completion of Work in a
format as listed in Table 3. If formats do not comply with the requirements defined in this
document then a Conversion Strategy must be put forward with the bid and agreed upon
by the Owner.
4.1 Document Requirements

The following general requirements apply for all documents:
 Hyper links within a document are not accepted
 A structured engineering index will be part of handover data (refer to 4.4.1)
 A structured vendor index will be part of handover data (refer to 4.4.1)
 All text must be none cursive and legible
4.1.1 Vendor and Supplier documents

Vendor documents will be constrained to the same format constraints as the Contractor as
defined in this document.
 Contractor is responsible for the quality of the Vendor data.
 All Vendor drawing and document numbers shall be unique.
All vendor information shall be issued to Owner in an electronic format.
4.1.2 Document Numbering and File names

Contractor shall comply with the project numbering of documents as described in project
specification 000-A-PE-002001.
SH/OF
REV 0 1 2 3 4
4.1.3 PDF file requirements

PDF files shall be converted with Acrobat software converters. Textual documents and
multiple page documents shall always be converted to PDF, and not be scanned. The one
exception to this requirement is signed documents. In the event a signed document is to
be issued, the signed sheet may be scanned with all other sheets in the document
requiring electronic conversion to PDF.
File conversions
 Be fully compatible with the standard Adobe Acrobat Reader
 Documents must be clear and easy to read
 Not include any third party file compression
 No external references to text fonts are allowed
 Pages & drawings correctly orientated
 Fast Web View optimized
 Fully indexed and searchable text content
 For documents over 25 pages chapters to be defined by book marks
 Page numbering shown in the Acrobat Reader must match with page number of the
document in the PDF file.
 Documents with attachments (appendix, Annex, etc.) should be sent as one merged
PDF file.
Files scanned to PDF format

 Have a resolution not less than 300 DPI
 Shall be scanned at the documents original size.
 Have orientation same as on the original document
 Documents must be clear and easy to read.
4.2 Additional drawing requirements

Additional requirements to be provided at data handover for CAD drawings:
 Any specific line or text resource files which have been used by the Contractor to
create the drawings
 All handed over drawings must be consistent with the level symbology document as
provided by the Contractor after contract award.
 No reference file attachments allowed. All reference shall be part of the drawing.
 Block and cell libraries used
4.3 Data Handling

To ensure data is provided in a consistent and ready to use manner, transferred data must
meet the following requirements:
 Virus checked by sender.
 Compressed or archived files are not accepted
 Transfers of digital information shall always be accompanied by a detailed index
detailing the contents of the digital delivery.
SH/OF
REV 0 1 2 3 4
4.3.1 Accepted methods of Data Transfer

The following transfer methods must be used:
 DVD-ROM formatted according to ISO 13346 standard and with UDF (Universal Disc
Format) supported by Microsoft Windows operating system
4.4 Metadata
Below are several tables of metadata information in the form of Database Tables. Each
Contractor shall deliver the metadata for each document including Tag-Document
relationships in a MS-Access database.
Table 4 - Format of Database Tables
Table Name: Sample
Attribute # 1 data Type Attribute # 1 description
Attribute # n data Type Attribute # n description
4.4.1 Document & Drawing Index

For all the electronic and hard copy documents deliverables, the Contractor must submit a
Document & Drawing Index with full Metadata describing such documents.
Table 5
Table Name: Document
File Name Text Saved file name with extension (refer to 000-A-PE-
0020001 chapter 4)
STAR Doc number Text STAR Document number (refer to 000-A-PE-0020001)
Contr. Doc number Text Contractor, Supplier or Vendor Doc number
Sheet number Text Optional sheet number
Document Title Text Document Title
Group code Text Group code (refer to 000-A-PE-0020001)
Drawing code Text Drawing Type (refer to 000-A-PE-0020001)
Revision Text Revision number
Issue date Date Revision date
Reason for issue Text Reason for issue
Unit Number Unit Number
Section Number Unit Section number
Paper Size Text A0, A1, A2, A3, A4
PO number Text
Tag number Text Tag number For multiple tags refer to Tag-Document
relationship (Table 6)
Vendor or Text Vendor or Contractor name
Contractor name
Discipline Text Discipline name
Transmittal number Text Transmittal number
Project Code Text To be defined by STAR
SH/OF
REV 0 1 2 3 4
4.5 TAG-Document relationships

The Contractor must capture and deliver all Document-Tag relationships.
Table 6:
Table Name: Document-TAG Relationships
Document TAG
Owner Doc Text Owner Document number
Number Example: 100-A-AB-0500123
Tag number Text Tag number
Example: 100-E-008A
The document number must be the same as listed in the Document & Drawing Index. All
major and minor Tag’s shall be captured. Tag numbers must be the same as listed in SPI,
SPE, Mechanical Equipment list and Line List.
End of Specification

Fljor.: Project Requirements and

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fljor.: Project Requirements and

Uploaded by

Copyright:

Available Formats

CONTRACT N° UNIT N°

STAR RAFINERI A.S.

Project lT requirements and Electronic Deliverable

1.2 Basic Description

1.3 Automation Plan

Table 2 - References to Specifications

2.1 Network Requirements

2.2 Information Security requirements

2.2.1 Virus protection

2.3.1 Electronic Mail

2.4 IT Requirements for Resident team

2.4.1 Video Conference System

2.5 Site IT Infrastructure

Table 3 - Software applications, versions and formats

3.1.2 Symbology and Settings

3.1.3 Border Files

3.1.4 CAD deliverables

3.1.5 Drawing units

3.2.2 System & Version

3.2.3 Symbology and Settings

3.2.4 Design Boundaries

3.2.5 Working units

Note: final working units to be agreed during start of EPC

3.2.6 3D Model Content

3.2.7 Coordinate System

3.2.8 Extracted 2D Drawings

3.2.9 Border Files

3.2.10 Model Data Handover

3.3 Instrument Database

For other SPI requirements refer to Specification 000-J-PE-0020002 - Minimum

3.4 Electrical Database

3.5 Line List Data

3.6 Mechanical Equipment List

4 ELECTRONIC DELIVERABLES AND FORMATS

4.1 Document Requirements

4.1.1 Vendor and Supplier documents

All vendor information shall be issued to Owner in an electronic format.

4.1.2 Document Numbering and File names

4.1.3 PDF file requirements

Files scanned to PDF format

4.2 Additional drawing requirements

4.3 Data Handling

4.3.1 Accepted methods of Data Transfer

4.4.1 Document & Drawing Index

4.5 TAG-Document relationships

You might also like