94 Sec C - Part II - 4.11 Engineering Data Management - Rev0

INVITATION TO BID
TENDER PACKAGE N16A DESIGN COMPETITION FOR RE-FEED, ENGINEERING,

PROCUREMENT, CONSTRUCTION AND COMMISSIONING OF THE EFFLUENT
TREATMENT PLANT FOR RAPID PROJECT
(TENDER N: RAPID/CTC/36-2014-P16A)
Section: C
SCOPE OF WORK
Part II 4.11 ENGINEERING DATA MANAGEMENT
Rev: 0
Page: 1 of 31
INDEX
4.11
ENGINEERING DATA MANAGEMENT ...................................................................2
4.11.1
PURPOSE ................................................................................................................2
4.11.2
GENERAL ................................................................................................................2
4.11.3
DATA MANAGEMENT PROCEDURES ....................................................................3
4.11.4
ENGINEERING DESIGN TOOLS .............................................................................4
4.11.4.1 SmartPlant P&ID (SPPID) .........................................................................................6

4.11.4.2 SmartPlant Instrumentation (SPI)..............................................................................9
4.11.4.3 SmartPlant Electrical (SPEL) ..................................................................................12
4.11.4.4 SmartPlant 3D (SP3D) ............................................................................................16
4.11.4.5 SmartPlant Review (SPR) .......................................................................................19
4.11.4.6 2D CAD Drawings ...................................................................................................21
4.11.5
TAG REGISTERS...................................................................................................22
4.11.6
TAG NUMBER ALLOCATION ................................................................................23
4.11.7
DOCUMENTATION AND DATA QUALITY ASSURANCE AND QUALITY CONTROL

23
ATTACHMENT 4.11-A DELIVERABLES AND AUTHORING TOOLS................................25

ATTACHMENT 4.11-B SMARTPLANT 3D MODEL CONTENT .........................................26
ATTACHMENT 4.11-C - EPCC HANDOVER & WORK PROCESS ARCHITECTURE .........29
ATTACHMENT 4.11-D P-EDMS ASSET TAG NUMBERING CONVENTION ....................30
ATTACHMENT 4.11-E P-EDMS HANDOVER TECHNICAL SPECIFICATION GUIDE (FOR
DETAILED DESIGN ENGINEERING) ..................................................................................31
94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx
INVITATION TO BID
Section: C
SCOPE OF WORK
4.11
ENGINEERING DATA MANAGEMENT
4.11.1
PURPOSE
Rev: 0
Page: 2 of 31
This Chapter outlines the requirements for engineering design tools and data
management for the whole duration of the PROJECT.
Should conflicts or inconsistencies be discovered by CONTRACTOR between
this Chapter and other specifications and requirements of the SCOPE OF WORK
or the PROJECT DOCUMENTATION, CONTRACTOR shall advise OWNER in a
timely manner, in writing. OWNER shall promptly, and formally instruct
CONTRACTOR how to proceed, and CONTRACTOR shall comply with
OWNERs instruction (refer to Section C Part II Chapter 23.0
ADMINISTRATION INSTRUCTIONS).
4.11.2
GENERAL
CONTRACTOR shall nominate a Project Information Manager (or equivalent
position) to coordinate CONTRACTORs information systems set-up, data
collection and HANDOVER tasks.
The required data shall be formatted, prepared and delivered in accordance with
OWNERs requirements as detailed in the overall architecture and P-EDMS
Books 2 & 3 provided in the attachments 4.11-C, 4.11-D and 4.11-E of this
Chapter. In case of any deviation, CONTRACTOR shall comply with concession
request procedure as per Section C - Part II - Chapter 23.0 ADMINISTRATION
INSTRUCTIONS.
CONTRACTOR is responsible for the receipt, review and integration of the data
produced by the SUB-CONTRACTORS and VENDORS into its design systems
and registers.
Data held in CONTRACTORs intelligent design systems shall be provided to
OWNER, as specified in this Chapter.
OWNER reserves its right to update the databases requirements before
COMMENCEMENT DATE. In that case, CONTRACTOR shall not be entitled to
any additional cost or EXTENSION OF TIME.
INVITATION TO BID
Section: C
SCOPE OF WORK
4.11.3
Rev: 0
Page: 3 of 31
DATA MANAGEMENT PROCEDURES

CONTRACTOR shall develop for the PROJECT, as minimum, the following
procedures in compliance with PROJECT SPECIFICATION and P-EDMS Book 2
and Book 3 (refer to Attachment 4.11-D and 4.11-E):
A Data Management Plan that outlines the work processes, responsibilities,

schedule and resources to be implemented by CONTRACTOR for ensuring
that OWNERs data requirements as specified in this Chapter, are met;
An implementation plan for each SmartPlant tool used by CONTRACTOR

covering, as minimum, the following items:
Roles and responsibilities of key database personnel (administrator,

lead designer);
Software and database versions;
Set-up information (such as Oracle instance name, Oracle character

sets);
Details of all servers used for the PROJECT;
Plant hierarchy (PBS) structure;
Instructions for designers for use of correct symbols and labels;
Instructions for resolving any inconsistencies between data;
Set-up of output reports;
Back-up and disaster recovery procedure;
List of attributes to be populated, in accordance with PROJECT

SPECIFICATION;
Data management reports templates;
Data maintenance procedure (such as database constraint checks,

database maintenance, duplicate items check);
List
of
OWNER
approved
deviations
from
PROJECT
DOCUMENTATION and approved customisations applied to the
database from the delivery of the FEED data to the PROVISIONAL
ACCEPTANCE.
INVITATION TO BID
Section: C
SCOPE OF WORK
4.11.4
Rev: 0
Page: 4 of 31
ENGINEERING DESIGN TOOLS

CONTRACTOR shall use the following, but not limited, 2D and 3D Computer
Aided Design (CAD) systems as engineering design tools:
Intergraph SmartPlant P&ID (SPPID) for P&ID drawings;
Intergraph SmartPlant Instrumentation (SPI) for instrumentation design;
Intergraph SmartPlant Electrical (SPEL) for electrical design;
Intergraph SmartPlant 3D (SP3D) for 3D modeling;
SmartPlant Isometric for isometric drawings;
Intergraph SmartPlant Review (SPR);
Intergraph SmartPlant Reference Data for piping specifications, standard

component definitions in the piping, instrumentation, electrical, steel
structure and HVAC disciplines, using OWNER material coding standard as
will be provided in SDB format;
Intergraph SmartSketch for 2D CAD drawing. In the case where

CONTRACTOR would use other 2D software (such as AutoCAD or
Microstation), CONTRACTOR shall request OWNERs approval.
CONTRACTOR shall use the latest released versions of such CAD systems with
applicable tested patches if any, at commencement of the WORK.
CONTRACTOR shall seek prior approval from OWNER for actual versions and
patch releases to be used in the PROJECT.
CONTRACTOR shall use the compatible version of Oracle database for all
engineering design tools except for SP3D that will be using MSSQL.
CONTRACTOR shall follow INTERGRAPH recommendations for hardware and
sofware requirements for the SmartPlant tools suite.
CONTRACTOR shall use the SPPID, SPI, SPEL and SP3D seed files provided
by OWNER to standardise the software across the whole RAPID PROJECT.
The system hierarchy, Plant Breakdown Structure (PBS), for Intergraph
SmartPlant tools shall be created in accordance with GOOD ENGINEERING
PRACTICES but must comply with the RAPID PROJECTs overall structure using
3 levels. First level shall be designated for plant, second level is designated for
functional area and third/lowest level is designated for functional unit.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 5 of 31
This structure including levels names and descriptions shall be approved by

OWNER.
CONTRACTOR shall ensure the PBS is consistent across all project information
and design tools during the whole PROJECT duration and in the P-EDMS system
accordingly.
CONTRACTOR shall not make changes to the PBS hierarchy without
documenting the change and getting approval from OWNER for the change.
CONTRACTOR shall follow the PROJECT SPECIFICATIONS for plant

components identification and numbering, applicable codifications and unit of
measures in its databases and registers:
Project Procedure
Numbering;
Project Specification Electrical Material Identification and Numbering

Specification;
Project Specification
Specification;
Section C - Part II Chapter 4.0 ENGINEERING GENERAL - Attachment

4-B - Mandatory Codification;
Project Procedure Units of Measurement.
Equipment
and
Instrument
Material
Identification
Identification
and
and
Numbering
CONTRACTOR shall follow the PROJECT SPECIFICATIONS and P-EDMS Book

2 and Book 3 (refer to Attachment 4.11-D and 4.11-E) for data population inside
its design systems.
To maintain a consistent configuration across CONTRACTOR and OTHER

CONTRACTORS a procedure will be implemented by OWNER to manage
modifications impacting the SmartPlant tools. The items that will be managed by
OWNER are, but not limited to, modifications of:
The reference data (rules, formats, symbols & labels, catalogs, libraries);
The select list;
The properties.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 6 of 31
CONTRACTOR shall not make modifications to such items. In case of deviation,

modification/ addition, CONTRACTOR shall comply with the concession request
procedure in accordance with Section C - Part II - Chapter 23.0
ADMINISTRATION INSTRUCTIONS.
4.11.4.1
SMARTPLANT P&ID (SPPID)

CONTRACTOR shall use Intergraphs SmartPlant P&ID software, for the purpose
of creating intelligent P&ID drawings in P-EDMS. CONTRACTOR shall use the
PROJECT DOCUMENTATION database and comply with the seed files provided
by OWNER in PROJECT DOCUMENTATION,
CONTRACTOR shall redraw VENDORs P&IDs in the SmartPlant P&ID database
with the same drafting standards as all other SmartPlant P&IDs.
Border templates and title blocks for the P&IDs should be customised to match
OWNERs border standards which CONTRACTOR shall obtain from OWNER so
as to avoid reproducing them.
CONTRACTOR shall use the P&IDs legend sheet of all symbols provided in the
PROJECT SPECIFICATIONS.
CONTRACTOR shall use, for the creation of all P&IDs, the P&ID reference data
(such as symbols, templates, assemblies, report templates, rules, insulation
specification), as delivered with the SmartPlant P&ID seed file provided by
OWNER.
CONTRACTOR shall not make changes to the seed file. In such case,
CONTRACTOR shall comply with concession request procedure as described in
Section C - Part II - Chapter 23.0 ADMINISTRATION INSTRUCTIONS. Any
changes on the seed file shall be synchronised with OWNER.
In the event that an appropriate P&ID symbol, label or attribute does not exist
within the software-delivered reference data and is required for the WORK,
CONTRACTOR shall obtain OWNERs approval to use such symbol, label or
attribute.
CONTRACTOR shall use the SmartPlant P&ID Arial Narrow font for items, notes,
labels, general notes and similar items in order to optimise the space inside
P&IDs drawing.
CONTRACTOR shall set up its SmartPlant P&ID consistency rules in accordance
with the GOOD ENGINEERING PRACTICES.
CONTRACTOR shall resolve or approve all design inconsistencies, including the
CONTRACTORs inter-discipline data inconsistencies used in the P&IDs as part
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 7 of 31
of their normal work process. CONTRACTOR shall conduct database quality

checks periodically during engineering development, to ensure that
CONTRACTORs inter-discipline engineering data is consistent between each
deliverable.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 8 of 31
CONTRACTOR shall fill in all applicable attributes to the fullest extent for all P&ID
components, such as pipe runs, equipment, inline instruments. This is to ensure
that OWNER receives the complete and meaningful P&ID data in SmartPlant
P&ID format. CONTRACTOR is required to submit a complete list of properties
that will be filled in when creating the P&IDs.
CONTRACTOR shall ensure that P&ID instrument tags associate with and
correspond to the appropriate instrument loops. This is a firm requirement of
OWNER and will be strictly enforced.
CONTRACTOR shall follow the requirement defined in the PROJECT
SPECIFICATION for tag naming conventions regarding P&ID instrument tags,
instrument loop tags, EQUIPMENT tags, and line tags. Tag numbers must be
entered identically within tag indexes and 3D model to ensure traceability across
all applications.
CONTRACTOR shall follow GOOD ENGINEERING PRACTICES for
implementing P&ID face value information, such as labels, annotations,
descriptions, notes, sizes, as detailed in the standards.
CONTRACTOR shall ensure that, where applicable, all process LICENSOR
PFDs and P&IDs are submitted in SmartPlant P&ID format.
SPPID Database delivery

CONTRACTOR shall deliver to OWNER the resulting P&IDs and all associated
database archives, reference data, templates and any customised macros,
scripts used on the PROJECT at the following milestones: issue of P&IDs in IFR,
IFD, IFC and As-Built status.
CONTRACTOR shall remove all temporary drawings such as test drawings, test
symbols and assemblies, temporary filters, reports, from the SmartPlant P&ID
data, before delivering such P&IDs and associated documents to OWNER.
CONTRACTOR shall use the SmartPlant P&ID Re-Create P&ID from Database
functionality before final CONTRACTORs checking and delivery to OWNER.
CONTRACTOR shall ensure that the delivered SmartPlant P&ID data is free of
any database exceptions and orphan entries. CONTRACTOR shall run all
appropriate utilities as delivered with the software for identifying and resolving
database issues.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 9 of 31
CONTRACTOR shall provide, before PROVISIONAL ACCEPTANCE, a back-up

of the SmartPlant P&ID site and plant, with work share and project disabled. The
back-up shall include, the P&ID reference data (such as symbols, templates,
assemblies, report templates, rules, insulation specifications, modified DLLs)
used with the P&ID database.
CONTRACTOR shall provide a document specifying customisations carried out in
reference data, data dictionary, formats, rules, and reports.
CONTRACTOR shall provide any modified source code for all DLLs that were
created for the SmartPlant P&ID project and must highlight the modifications vis-vis delivered code. This code shall be sufficiently documented in accordance
with GOOD ENGINEERING PRACTICES, for the complete understanding by
OWNER. It is a strict requirement that all code be issued to OWNER shall further
enable the recompilation of the binary DLLs and shall allow continuation of use of
the SmartPlant P&ID database throughout the term of the CONTRACT and
beyond.
CONTRACTOR shall sufficiently document any deviation from PROJECT
SPECIFICATION approved during the CONTRACT and store such document in
P-EDMS residing at OWNER.
4.11.4.2
SMARTPLANT INSTRUMENTATION (SPI)

CONTRACTOR shall use SmartPlant Instrumentation software for the creation
and management of all instrumentation deliverables, including field
instrumentation and fire & gas devices, in accordance with Project Specification
Instrument Engineering Database Specification (SPI). CONTRACTOR shall
use the PROJECT DOCUMENTATION database and comply with the seed file
provided by OWNER in PROJECT DOCUMENTATION.
The PBS structure definition contained within SmartPlant Instrumentation shall be
aligned with the one in SmartPlant Engineering Manager, but SPI will use SPI
Admin Module to manage the PBS. No additional definitions can be made that
are not identical to those defined in the SmartPlant Engineering Manager. Each
instrument tags unit number shall match exactly with the SmartPlant P&ID when
referring to official issue of P&ID.
CONTRACTOR shall use the naming conventions for tags as defined in the
PROJECT SPECIFICATION.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 10 of 31
CONTRACTOR shall use the same service description on the instrument data
sheets as the control system point description. Standard abbreviations shall apply
in accordance with Section C - SCOPE OF WORK and PROJECT
SPECIFICATION.
CONTRACTOR shall use all border file templates, title blocks for the various
instrumentation documents, and reports in accordance with PROJECT
SPECIFICATION. CONTRACTOR shall customise all the instrument specification
sheets to meet OWNERs instrument data sheet standard. CONTRACTOR shall
obtain such instrument data sheets standards from OWNER so as to avoid
reproducing them. If the instrument data sheet standards are not available, the
default templates in SmartPlant Instrumentation are to be used. In case of any
deviation to these standards, CONTRACTOR shall comply with the concession
request procedure described in Section C - Part II - Chapter 23.0
CONTRACTOR shall utilise the SPI seed file as provided by OWNER for the
creation of all instrumentations.
CONTRACTOR shall not make changes to the seed file without documenting the
change and getting approval from OWNER, in compliance with the concession
request procedure described in Section C - Part II - Chapter 23.0
ADMINISTRATION INSTRUCTIONS. Any changes on the seed file shall be
synchronised with OWNER.
CONTRACTOR shall follow the GOOD ENGINEERING PRACTICES for setting
up SmartPlant Instrumentation consistency rules.
CONTRACTOR shall resolve or approve all design inconsistencies including the
CONTRACTORs inter-discipline data inconsistencies used in the SmartPlant
Instrumentation as part of their normal work process. CONTRACTOR shall
conduct periodically database quality checks, during engineering development, to
ensure that CONTRACTORs inter-discipline engineering data is consistent
between each deliverable.
CONTRACTOR will populate the SmartPlant Instrumentation data, and include all
the various available modules such as index, instrument specifications, wiring,
loop drawing, hook-up, as defined in Attachment 4.11-A Deliverables and
authoring tools, and in accordance with PROJECT DOCUMENTATION. All
spare capacity such as free terminals and wires to be registered, not just those
used by the development.
CONTRACTOR shall generate from SPI instrumentation deliverables in
accordance with Attachment 4.11-A Deliverables and authoring tools. Any
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 11 of 31
deviation from this request is required in writing and must be approved by

OWNER before any WORK relating thereto can commence.
CONTRACTOR shall generate all loop drawings using Enhanced Smart Loop
functionality available within SPI. Where required for readability, CONTRACTOR
shall use the reports generated by Enhanced Smart Loop to manually adjust the
loop drawings and locations can be saved in the database.
All instrument indexes and I/O lists for VENDOR packages data shall be
populated into the database. Wiring information or VENDOR package data when
connected to a system supplied by CONTRACTOR (such as MAC, MMS) shall
be keyed into SmartPlant Instrumentation and the resulting deliverables be
issued from SmartPlant Instrumentation for construction purposes.
CONTRACTOR shall provide official data sheets for control valves and flow
elements from SPI.
CONTRACTOR shall use SPI to store the data for the alarm and controller setpoint summary. This data shall be passed to the main control system as the
starting point for configuration. A work process shall be put in place by
CONTRACTOR to ensure that the alarm and set point data is kept in
synchronisation with the DCS/PLC systems if applicable. P-EDMS shall be the
record of copy for these data. The management of change, once in use by the
OWNERs operations and maintenance personnel, will have wrapped around
these data.
CONTRACTOR shall use the CAD symbols customised for the PROJECT in
Enhanced Smart Loop format.
If CONTRACTOR uses user-defined fields a summary of this usage should be
submitted to OWNER. This shall be a separate document describing its use to
ensure that the methodology is continued by OWNER in the operations and
maintenance of the FACILITY. This document shall be stored in P-EDMS at
OWNER and be easily available to all SmartPlant Instrumentation users.
It is a strict requirement that CONTRACTOR deliver to OWNER an As-Built
SmartPlant Instrumentation database with all associated files.
SPI Database delivery

CONTRACTOR shall provide a SmartPlant Instrumentation site and plant full
backup at following milestones: issue of Instrument Index in IFR, IFD, IFC and
As-Built status.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 12 of 31
CONTRACTOR shall ensure that the delivered SmartPlant Instrumentation data

is free of any database exceptions and orphan entries.
CONTRACTOR shall remove all test data, test CAD blocks, temporary browser
views, temporary reports, etc. from the SmartPlant Instrumentation database and
system directories before delivering such SPI database to OWNER.
CONTRACTOR shall deliver the SmartPlant Instrumentation database in a
Watcom backup format. CONTRACTOR shall run the appropriate utilities as
delivered with SmartPlant Instrumentation for identifying and resolving database
issues such as CheckDB. CONTRACTOR shall provide the log file from this
utility showing that there are no errors. It is CONTRACTORs responsibility to fix
such errors.
CONTRACTOR shall provide all of the following:
CAD blocks, symbols, border templates, title block PSRs;
Customised PSR files for reports and datasheet templates;
Document specifying
SPECIFICATION.
all
approved
deviations
from
PROJECT
Such electronic deliverables will be made available on the DVD media including
an index for the content contained on the DVD.
4.11.4.3
SMARTPLANT ELECTRICAL (SPEL)

CONTRACTOR shall use SmartPlant Electrical software for the creation and
management of the electrical database and deliverables in accordance with the
Project Specification Smart Plant Electrical Database Administration and
Structure which is part of the PROJECT DOCUMENTATION. CONTRACTOR
shall use the PROJECT DOCUMENTATION database and comply with the seed
file provided by OWNER in PROJECT DOCUMENTATION.
Border templates and title blocks for the schematics shall be customised by
CONTRACTOR to match OWNERs border standards which CONTRACTOR
shall obtain from OWNER so as to avoid reproducing them before any WORK
starts.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 13 of 31
CONTRACTOR shall use the electrical reference database and the reference
data (such as symbols, schematic blocks, report templates) from the seed files
provided by OWNER.
CONTRACTOR shall use SmartPlant Electrical default font (Arial) for
deliverables.
CONTRACTOR shall use SmartPlant Electrical to create the following electrical

deliverables:
Electrical consumer list;
Load schedules;
Load balance;
Switchgear schedules;
Electrical equipment list;
All electrical cable schedules.
CONTRACTOR shall comply with Attachment 4.11-A Deliverables and authoring

tools. CONTRACTOR shall submit any exceptions to OWNER in writing which
must be review and approved by OWNER, at OWNERs absolute discretion,
before starting work. For any deviation, CONTRACTOR shall comply with the
concession request procedure described in Section C - Part II - Chapter 23.0
CONTRACTOR may need to create new user-defined attributes. Any new
required attributes shall be approved by OWNER before being added to the data
dictionary under relevant categories. A summary of added attributes shall be
submitted as a separate document describing such attributes.
CONTRACTOR shall implement tag naming conventions for various electrical
items, such as cable, motor, transformer, as per the Project Specification Electrical Material Identification and Numbering Specification which is part of the
PROJECT DOCUMENTATION.
CONTRACTOR shall utilise the SPEL seed file as provided by OWNER for the
creation of all electrical.
CONTRACTOR shall not make changes to the seed file without documenting the
change and getting approval from OWNER for the change. Any changes on the
seed file shall be synchronised with OWNER.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 14 of 31

inter-discipline data inconsistencies used in the SmartPlant Electrical as part of
their normal work process.
up SmartPlant Electrical consistency rules. Database quality checks will be
conducted periodically throughout the PROJECT by CONTRACTOR to ensure
that inter-discipline engineering data is consistent per deliverable across the
WORK.
CONTRACTOR shall fill in all applicable attributes fully for all indexed tags. This
shall ensure that OWNER receives the complete and meaningful SPEL project
database.
CONTRACTOR shall deliver all electrical datasheets and non-SmartPlant
Electrical deliverables as documents which will be loaded into P-EDMS.
CONTRACTOR shall relate the electrical tag number to the electrical documents
using the template provided by OWNER in PROJECT DOCUMENTATION. This
is required to load the data and documents into OWNERs P-EDMS system.
SPEL Database delivery

CONTRACTOR must remove all temporary drawings such as test drawings, test
symbols, temporary filters, reports from the SmartPlant Electrical database,
before delivering such SPEL database to OWNER.
CONTRACTOR shall ensure that the delivered SmartPlant Electrical data is free
of any database exceptions and orphan entries.
CONTRACTOR shall provide a SmartPlant Electrical site and plant backup
(Electrical Consumers List, Electrical Cable Schedule, Electrical Power Balance)
used with SPEL project data at several intermediate revisions during the design
up to the final revision.
Back-up shall contain the reference data (such as reference schema, templates,
symbols, schematic blocks, formats, and rules).
CONTRACTOR shall document the customisation carried out by CONTRACTOR
in all reference data, data dictionary, formats, rules, and reports.
CONTRACTOR shall document any approved deviations from PROJECT
SPECIFICATION.
The above electronic deliverables must be made available on DVD media with an
index of contents.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 15 of 31
INVITATION TO BID
Section: C
SCOPE OF WORK
4.11.4.4
Rev: 0
Page: 16 of 31
SMARTPLANT 3D (SP3D)
CONTRACTOR shall use SmartPlant 3D software for the creation and
management of the 3D model deliverables.
SmartPlant 3D Catalog (Reference Data) name shall be the PROJECT name with
the appendix _Catalog. The SmartPlant 3D Catalog shall be created or checked
and reviewed in compliance with PROJECT SECIFICATION, on process, piping,
civil/structural, electrical & instrumentation. Dimensional tolerances must be
specified, for example main structure +/- 10 mm, piping +/- 50 mm, field
EQUIPMENT +/- 250 mm.
CONTRACTOR shall use GOOD ENGINEERING PRACTICES to determine
additional attribute requirements for components such as EQUIPMENT and pipe
runs.
CONTRACTOR shall follow GOOD ENGINEERING PRACTICES for setting up
SmartPlant 3D consistency rules.
inter-discipline data inconsistencies used in the SmartPlant Instrumentation as
part of their normal work process. CONTRACTOR shall conduct database quality
checks periodically throughout the PROJECT to ensure that inter-discipline
engineering data is consistent between each deliverable.
The SmartPlant 3D reference data shall be customised in accordance PROJECT
SPECIFICATION. This may include components such as piping MATERIAL
classes, piping commodity data, instrument data, specialty data, tap data, piping
assemblies. CONTRACTOR shall follow naming conventions and standards
defined in Section C - SCOPE OF WORK and in PROJECT SPECIFICATION for
piping MATERIALS classes. These piping MATERIAL classes and all associated
files shall be delivered to OWNER in a loadable format.
In addition, any reference data files in relation to components such as electrical
cable trays, ducting, steel structures, civil works, hangers & supports shall be
delivered to OWNER in loadable formats to enable bulk loading to the source
application. Once loaded they shall be void of errors or missing information.
CONTRACTOR shall be responsible to correct such errors or missing information
and must amend and re-submit the files until approved by OWNER.
CONTRACTOR shall maintain an up-to-date record of all modifications made to
the catalog which shall be accessible to OWNER.
CONTRACTOR shall report to OWNER each addition made to the catalog.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 17 of 31
CONTRACTOR shall send an approval request to OWNER if CONTRACTOR

identifies the need to modify the standard catalog delivered by Intergraph.
Any creation needed by CONTRACTOR in the catalog for piping specifications,
cable trays specifications, structure beams and code lists (such as fluid codes,
insulation codes) shall be approved by OWNER before implementation.
CONTRACTOR shall use naming conventions for components such as
EQUIPMENT, nozzles, line number, line ID, columns, beams. These naming
conventions should be in accordance with Section C - SCOPE OF WORK and
the PROJECT SPECIFICATION using the full tag number and be identical to that
assigned to tags in other SmartPlant applications such as SmartPlant P&ID,
SmartPlant Instrumentation and SmartPlant Electrical.
CONTRACTOR shall issue an As-Built SmartPlant 3D data model based on
OWNER requirements.
The SmartPlant 3D model must be populated sufficiently to produce required
documents, such as isometrics, plan and elevation drawings as well as Material
Take-Offs.
The modeling extent will be in accordance with GOOD ENGINEERING
PRACTICES and as OWNER requirement indicated in Attachment 4.11-B of this
Chapter in complement of PTS standard 30.10.05.11(Jan-08) Plant model
construction and review.
CONTRACTOR shall use, for the modelisation of civil structure, a software
compatible with SP3D and with softwares used by VENDORS for detailed
drawings / shop drawings (ie. TEKLA).
CONTRACTOR shall model primary civil/structural members in SP3D and
transfer the data to civil structure software for detailing via CIS/2 interface.
Progressive detailing and modifications completed in civil structure software, shall
be imported into SP3D via CIS/2 interface for ongoing clash detection and
drawing production purposes. The final delivery of civil/structural database shall
comprise of both the SP3D database as well as the detailed civil structure
software model databases.
CONTRACTOR shall model VENDOR packages from 2D CAD drawing files,
where VENDOR is unable to provide a SP3D file for incorporation into
CONTRACTORs 3D model.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 18 of 31
SP3D Database delivery

CONTRACTOR shall provide a SmartPlant 3D full back-up at following
milestones: 30%, 60%, 90%, at status Issued for Construction and at status AsBuilt of the 3D model.
The SP3D deliverables shall include, but is not limited to:
Complete SmartPlant 3D project backup performed from the SmartPlant3D

project management environment;
Complete backup of the project Symbols share, including complete

backup of the directory structures for drawings and reports created from
SmartPlant 3D. This includes but is not limited to:
Customised/added symbol definitions;
Symbol executables (.dll files);
Symbol source codes;
SolidEdge files;
Symbol 2D files;
Drawing border files;
Drawing view style definitions;
Drawing label definitions;
Final extracted isometric drawings;
Ortho drawings;
Reports.
Secondary Archive:
ZIP file MSSQL/Oracle server database backup files for site, site schema,
plant model, catalog, and catalog schema;
All MS Excel catalog bulk load files for all disciplines. It is mandatory that
these files reflect hundred (100) percent of the catalog database (such that
the entire catalog contents can be recreated by bulk loading these files).
The following reports are required to be submitted:
Final interference check report;
INVITATION TO BID
Section: C
SCOPE OF WORK
Final database consistency check report;
Complete catalog verification report;
Final project to-do-list report;
Line list report.
Rev: 0
Page: 19 of 31
SP3D Data Checks and Clean-up

CONTRACTOR shall ensure that the delivered data is not corrupted and/or
contains inconsistencies before delivery to OWNER. As a minimum, the following
checks and clean-up shall be performed:
General:
Temporary files and directories shall be removed prior to delivery to

OWNER.
SmartPlant 3D database consistency check report should be run without

reporting inconsistencies.
The SmartPlant 3D to-do-list shall be empty.
Piping:
4.11.4.5
Piping isometrics must be extracted successfully for all pipelines.

CONTRACTOR must modify any lines that fail to extract correctly prior to
delivery to OWNER.
SMARTPLANT REVIEW (SPR)

CONTRACTOR shall use SmartPlant Review software for the different 3D
reviews (for engineering, construction, or maintenance reviews).
The acceptable 3D model deliverables are Intergraphs SmartPlant 3D models
provided in Intergraphs SmartPlant Review software VUE format.
The software shall be capable of reviewing models within CONTRACTORs
Office environment or at any location as agreed by OWNER. The software shall
be capable to display the entire plant model and associated data at any remote
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 20 of 31
location, totally independent of the office network. The software will support a
modular approach to additional functionality.
The SmartPlant Review visualisation environment is for interactively reviewing
designs and identifying problems graphically. Real-time, high-resolution dynamic
navigation enables a variety of 3D motions, including:
Walk-throughs;
Fly-throughs;
Fly-arounds ;
Other path or dynamics-based motions via mouse or other input devices;
Encircle an object;
Set far and near clipping planes.
Access associated project data by moving the mouse over objects in the view.
Include the following abilities:
Associate tags or markers with objects, and save the view for later recall;
Display object attributes;
Associate new text and data with an object;
Query objects-based attribute data;
Measure and display the minimum distances between any two objects;
Save and recall attribute queries;
Allow attribute queries to control view display.
Attach external data file to any object. External data files include but are not
limited to:
Notepad data annotation
Microsoft Word data sheets
Animations maintenance instructions
Microsoft Excel MATERIAL lists
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 21 of 31
The software will support a basic viewer and a modular approach to adding
functionality. Add-on modules will include:
Construction module for dynamic collision detection, creating image files,

and overall PROJECT management. Also include integration of the
SCHEDULE by linking to Primavera or Microsoft Project planning tools.
API module with programming libraries to customise SmartPlant Review for

your enterprise.
Collaboration module that allows multiple users to view and interrogate the
model simultaneously.
On-site Drawing Generation modules for intelligent hidden-line display.
Photo Realism module takes still images to a new level of quality.
Point Cloud Integrator module for the display of existing condition data
captured from laser scanners.
Simulation and visual effects for creating animations and motion studies.
Deliverables
Deliverables will include:
4.11.4.6
Snapshots of the main view at any size;
High-quality still images;
Camera motion animations;
Constructability plans;
At defined milestones full model view files;
2D CAD DRAWINGS
CONTRACTOR shall use Smartsketch for the creation and management of any
2D CAD drawing types that are not covered by the other SmartPlant suite of
tools. Such drawings may include, but are not limited to, plot plans, layouts,
EQUIPMENT details, mounting details, cable tray reports.
up the drawing environment, including directory structures, file naming
conventions, and the location of symbol libraries and other reference data.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 22 of 31
Border templates and title blocks for the 2D CAD drawings are required to be
customised by CONTRACTOR to match OWNERs border standards, which
CONTRACTOR shall obtain from OWNER, so as to avoid reproducing them
before any WORK begins.
CONTRACTOR shall follow CAD drafting in accordance with PROJECT
SPECIFICATION, including standard such as fonts, line styles, hatching styles
when creating 2D CAD drawings with SmartSketch.
Deliverables
CONTRACTOR shall provide a back-up of all drawing native files, including any
associated reference data (such as symbols, drawing templates, report
templates) and any linked files (such as office documents, images)
The above electronic deliverables must be made available on DVD or CD media
with an index of contents.
4.11.5
TAG REGISTERS
CONTRACTOR shall deliver to OWNER the following listed tag and EQUIPMENT
registers for loading into P-EDMS on rare and unusual cases where the tag is not
registered in the Intergraph SmartPlant design tools, as well as in cases where
the required properties are not provided in the CONTRACTOR Intergraph
SmartPlant design tools:
Tag - Anode Index;
Tag - Blind List;
Tag - Cable Schedule;
Tag - Ducting Schedule;
Tag - Fire and Gas Field Devices Index;
Tag - Flange Management Register;
Tag - Heat Tracing Cable Index;
Tag - Instrument Index ICS Connected field items;
Tag - Instrument Index Field Items not Connected to ICS;
Tag - Instrument Index Soft Tags;
Tag - Junction Box Schedule;
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 23 of 31
Tag - Lifting Equipment Register;
Tag - Line List;
Tag - Manual Valve Index;
Tag - Master Equipment List;
Tag - Pipe Support Index;
Tag - Programmable Controller Software and Hardware Register;
Tag - Safety Valve Register;
Tag - Special Piping Item Index;
Tag - Telecom Field Index.
OWNER will provide to CONTRACTOR templates for these registers.
4.11.6
TAG NUMBER ALLOCATION

All tag number allocation will be controlled and provided by OWNER based on
numbering format as defined in the PROJECT SPECIFICATION.
OWNER will reserve and provide the tag list for each CONTRACTOR to use. In
the event that the tag number list provided is not enough during PROJECT
execution, CONTRACTOR shall request OWNER to provide new batch of tag
reservation list.
4.11.7
DOCUMENTATION AND DATA QUALITY ASSURANCE AND QUALITY

CONTROL
CONTRACTOR shall provide in PROJECT Quality Management Plan (PQMP)
the Quality Assurance program requirement and Quality Control activities to
ensure fulfilment of PROJECT SPECIFICATION for document and data
management. The PROJECT Quality Management Plan will detail
CONTRACTOR's internal data gathering, data quality management processes
and handover procedures.
The CONTRACTOR is responsible for the quality of the WORK and shall take all
reasonable measures to ensure that data received from the SUBCONTRACTORS and VENDORS is:
Complete; and,
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 24 of 31
Consistent with / across the defined SCOPE OF WORK and PROJECT

SPECIFICATION.
CONTRACTOR as part of its QA/QC programs shall ensure that cross application
data validation is carried out and reports extracted and submitted to ensure cross
application data consistency. Exception reports are to be submitted to OWNER
for information, review and/or approval where required. These consistency
reports shall be produced using automated processes without manual
intervention to update the reports. OWNER reserves its right to inspect and
approve the consistency and exception reporting processes.
CONTRACTORs Quality Assurance program requirement shall address specific
practices, resources and sequence of activities relevant to management and
control of the whole documentation of the PROJECT. CONTRACTOR shall refer
to the details stated in Section C - Part II Chapter 14.0 QUALITY
MANAGEMENT REQUIREMENTS.
END OF CHAPTER
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 25 of 31
ATTACHMENT 4.11-A DELIVERABLES AND AUTHORING TOOLS
CONTRACTOR Deliverables and Authoring Tools

Document Type*
Design Tool Source
Equipment Datasheet
Process Flow Diagram
P&ID
Line List/Line Designation Table
Master Equipment List
Instrument Index I/O List
Hook-Up Drawings
Instrument Loop Drawings
Wiring Diagrams
Instrument Process Data Sheet
Instrument Data Sheet
Dimensional Data Sheet
Cable Schedule
Excel format
SmartPlant P&ID
SmartPlant P&ID
SmartPlant P&ID
SmartPlant P&ID
SmartPlant Instrumentation
SmartPlant Instrumentation (optional)
SmartPlant Instrumentation and SmartPlant
Electrical
Junction Box Schedule
Calculation Sheet
SmartPlant Instrumentation (optional)
Electrical Consumer List
SmartPlant Electrical
Load Schedules
Load Balance
Switchgear Schedules
Electrical Equipment List
ISO Drawings
SmartPlant 3D
Ortho Drawings
SmartPlant 3D
All other 2D CAD drawings (Foundation, SmartSketch or AutoCAD or Microstation
Plot Plants, Mounting details, Cable Tray
reports,
Mechanical
Layouts,
Architectural, Site Layout, etc.)
CONTRACTOR shall submit a concession request to OWNER for approval in
case of documents and drawings which cannot be produced using SmartPlant
tools (refer to Section C Part II Chapter 23.0 ADMINISTRATION
INSTRUCTION for further information on concession request).
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 26 of 31
ATTACHMENT 4.11-B SMARTPLANT 3D MODEL CONTENT

The model shall be detailed, fully to scale, reflecting engineering progress,
containing all items and facilities applicable to this PROJECT. The modeling
extent includes but is not limited to the information provided below.
CONTRACTOR shall model VENDOR packages to the same level of detail as the
rest of the WORK if applicable.
Piping:
The following piping and piping components shall be modeled:
All process and utility piping including all piping components, all welds to be
included. Shop and field welds to be distinguished by separate symbols.
Nozzles to be shown with nozzle number as on P&ID;
Valves including hand wheels, actuators, and other accessories;
Piping accessories, such as strainers and steam traps;
Underground piping;
Pipe supports;
Jacketed pipes;
Insulation outline;
All major process attributes and identification attributes will be captured.
Instrumentation:
The following instrumentation components shall be modeled:
Cable trays / ladders (150mm wide and above);
All in-line field instrument, control valves, and on-off valves;
All process connections for instrument on piping and equipment;
Online field instruments, level instruments;.
Offline field instrument including mounting stands;
Junction boxes and local control panels;
Analysers, sampling systems / panels and analyser houses
All Fire & Gas Devices, including mounting stands;
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 27 of 31
Telecom field devices, including mounting stands (outdoor PA speakers

and GA sirens, outdoor CCTV cameras, outdoor telephones);
All identification attributes will be captured.
EQUIPMENT:
EQUIPMENt models should be kept as simple as possible, while still showing a
reasonable representation of the EQUIPMENT for presentation and interference
detection. EQUIPMENT parametric shall be used whenever possible.
Equipment outline shapes and nozzles;
Ducts, platforms, support columns, and stacks;
Packaged equipment; outline of all tagged equipment and valves.

Packaged equipment model will include associated components (such as
piping, instrumentation) represented within same
philosophy than
equipment (as simple as possible, for presentation and interference
detection);
Major proprietary items and ancillary equipment;
Equipment envelops.
The minimum attribute requirements for EQUIPMENT are EQUIPMENT number,

insulation thickness, and a description. The minimum required nozzle attributes
are tag number, size, pressure rating, end prep, and pipe MATERIAL class. The
equipment tag numbers are to be the same as used by other SmartPlant
applications.
Civil/Concrete/Structure:
Site: terrain;
Drainage and sewerage: routing outline and level, drips, manhole, catch
basin, and pits;
Foundation: outline, top, and bottom level;
Civil Concrete items: outline, top, and bottom level;
Steel and Concrete Structure including those designed by the VENDORS:

beams, columns, bracings, fireproofing, all floors with top and bottom level,
stairs, platforms, ladders, pipe racks, pipe sleepers, Equipment
shed/shelters, hoisting beams, and handrails. Major sections will have to be
labeled;
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 28 of 31
Stanchion: outline;
Underground cable duct: routing, outline, and top and bottom level
trenches;
Underground conduits: outline;
Buildings/accommodation/living quarters: outline including doors, floors,

ceilings, walls.
Electrical:
Outline for electrical motors, lighting fixtures, junction boxes, cable routes
(such as trays and trenches), local control station, local panel, lighting
panel, cable routing nodes and socket outlets, CCTV;
Transformers, sub-station: outline.
Fire Protection/Fire-fighting Systems:
Spray systems piping routing and nozzles;
Fire ring main routing, hydrants, block valves, fixed water monitors, and
hose reels;
Fire alarm push buttons;
Fire and Gas devices;
Deluge valve manifolds.
Miscellaneous:
Safety showers and wash fountains;
Anodes, HVAC ducting and welds;
Escape routes, handling/maintenance and access routes;
Any other features deemed necessary for clarifying the design,

construction, operation and maintenance requirements as well as clash
detection during engineering.
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 29 of 31
ATTACHMENT 4.11-C - EPCC HANDOVER & WORK PROCESS

ARCHITECTURE
(2 pages)
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 30 of 31
ATTACHMENT 4.11-D P-EDMS ASSET TAG NUMBERING CONVENTION

PEDMS-EDO-GEN-STD-000-0002 - Version 1.1 - August 2012 (48 pages)
INVITATION TO BID
Section: C
SCOPE OF WORK
Rev: 0
Page: 31 of 31
ATTACHMENT 4.11-E P-EDMS HANDOVER TECHNICAL SPECIFICATION

GUIDE (FOR DETAILED DESIGN ENGINEERING)
PEDMS-EDO-GEN-STD-000-0003 - Version 1.1 - August 2012 (41 pages)

94 Sec C - Part II - 4.11 Engineering Data Management - Rev0

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

94 Sec C - Part II - 4.11 Engineering Data Management - Rev0

Încărcat de

Drepturi de autor:

Formate disponibile

INVITATION TO BID

TENDER PACKAGE N16A DESIGN COMPETITION FOR RE-FEED, ENGINEERING,

ENGINEERING DATA MANAGEMENT ...................................................................2

DATA MANAGEMENT PROCEDURES ....................................................................3

ENGINEERING DESIGN TOOLS .............................................................................4

4.11.4.1 SmartPlant P&ID (SPPID) .........................................................................................6

TAG NUMBER ALLOCATION ................................................................................23

DOCUMENTATION AND DATA QUALITY ASSURANCE AND QUALITY CONTROL

ATTACHMENT 4.11-A DELIVERABLES AND AUTHORING TOOLS................................25

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

ENGINEERING DATA MANAGEMENT

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

DATA MANAGEMENT PROCEDURES

A Data Management Plan that outlines the work processes, responsibilities,

An implementation plan for each SmartPlant tool used by CONTRACTOR

Roles and responsibilities of key database personnel (administrator,

Software and database versions;

Set-up information (such as Oracle instance name, Oracle character

Details of all servers used for the PROJECT;

Plant hierarchy (PBS) structure;

Instructions for designers for use of correct symbols and labels;

Instructions for resolving any inconsistencies between data;

Set-up of output reports;

Back-up and disaster recovery procedure;

List of attributes to be populated, in accordance with PROJECT

Data management reports templates;

Data maintenance procedure (such as database constraint checks,

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

ENGINEERING DESIGN TOOLS

Intergraph SmartPlant P&ID (SPPID) for P&ID drawings;

Intergraph SmartPlant Instrumentation (SPI) for instrumentation design;

Intergraph SmartPlant Electrical (SPEL) for electrical design;

Intergraph SmartPlant 3D (SP3D) for 3D modeling;

SmartPlant Isometric for isometric drawings;

Intergraph SmartPlant Review (SPR);

Intergraph SmartPlant Reference Data for piping specifications, standard

Intergraph SmartSketch for 2D CAD drawing. In the case where

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

This structure including levels names and descriptions shall be approved by

CONTRACTOR shall follow the PROJECT SPECIFICATIONS for plant

Project Specification Electrical Material Identification and Numbering

Section C - Part II Chapter 4.0 ENGINEERING GENERAL - Attachment

Project Procedure Units of Measurement.

CONTRACTOR shall follow the PROJECT SPECIFICATIONS and P-EDMS Book

To maintain a consistent configuration across CONTRACTOR and OTHER

The select list;

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

CONTRACTOR shall not make modifications to such items. In case of deviation,

SMARTPLANT P&ID (SPPID)

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

of their normal work process. CONTRACTOR shall conduct database quality

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

SPPID Database delivery

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

CONTRACTOR shall provide, before PROVISIONAL ACCEPTANCE, a back-up

SMARTPLANT INSTRUMENTATION (SPI)

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

deviation from this request is required in writing and must be approved by

SPI Database delivery

94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0.docx

CONTRACTOR shall ensure that the delivered SmartPlant Instrumentation data