94 sec c - part ii - 4.11 engineering data management_ rev0

8/17/2019 94 Sec C - Part II - 4.11 Engineering Data Management_ Rev0

1/31

INVITATION TO BID

TENDER PACKAGE N°16A – 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)

SCOPE OF WORK-Part II – 4.11 ENGINEERING DATA MANAGEMENT

Section: C

Rev: 0

Page: 1 of 31

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

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 (FORDETAILED DESIGN ENGINEERING) ..................................................................................31


2/31

INVITATION TO BID




Section: C

Rev: 0

Page: 2 of 31


4.11 ENGINEERING DATA MANAGEMENT

4.11.1 PURPOSE

This Chapter outlines the requirements for engineering design tools and datamanagement for the whole duration of the PROJECT.

Should conflicts or inconsistencies be discovered by CONTRACTOR betweenthis Chapter and other specifications and requirements of the SCOPE OF WORKor the PROJECT DOCUMENTATION, CONTRACTOR shall advise OWNER in atimely manner, in writing. OWNER shall promptly, and formally instructCONTRACTOR how to proceed, and CONTRACTOR shall comply withOWNER’s instruction (refer to Section C – Part II – Chapter 23.0 ADMINISTRATION INSTRUCTIONS).

4.11.2 GENERAL

CONTRACTOR shall nominate a Project Information Manager (or equivalentposition) to coordinate CONTRACTOR’s information systems set-up, datacollection and HANDOVER tasks.

The required data shall be formatted, prepared and delivered in accordance withOWNER’s requirements as detailed in the overall architecture and P-EDMSBooks 2 & 3 provided in the attachments 4.11-C, 4.11-D and 4.11-E of thisChapter. In case of any deviation, CONTRACTOR shall comply with concessionrequest procedure as per Section C - Part II - Chapter 23.0 ADMINISTRATIONINSTRUCTIONS.

CONTRACTOR is responsible for the receipt, review and integration of the dataproduced by the SUB-CONTRACTORS and VENDORS into its design systemsand registers.

Data held in CONTRACTOR’s intelligent design systems shall be provided toOWNER, as specified in this Chapter.

OWNER reserves its right to update the databases requirements beforeCOMMENCEMENT DATE. In that case, CONTRACTOR shall not be entitled toany additional cost or EXTENSION OF TIME.


3/31

INVITATION TO BID




Section: C

Rev: 0

Page: 3 of 31


4.11.3 DATA MANAGEMENT PROCEDURES

CONTRACTOR shall develop for the PROJECT, as minimum, the followingprocedures in compliance with PROJECT SPECIFICATION and P-EDMS Book 2and 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 ensuringthat OWNER’s data requirements as specified in this Chapter, are met;

• An implementation plan for each SmartPlant tool used by CONTRACTORcovering, 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 charactersets);

• 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 PROJECTSPECIFICATION;

• Data management reports templates;

• Data maintenance procedure (such as database constraint checks,database maintenance, duplicate items check);

• List of OWNER approved deviations from PROJECTDOCUMENTATION and approved customisations applied to thedatabase from the delivery of the FEED data to the PROVISIONAL ACCEPTANCE.


4/31

INVITATION TO BID




Section: C

Rev: 0

Page: 4 of 31


4.11.4 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, standardcomponent definitions in the piping, instrumentation, electrical, steelstructure and HVAC disciplines, using OWNER material coding standard aswill be provided in SDB format;

• Intergraph SmartSketch for 2D CAD drawing. In the case whereCONTRACTOR would use other 2D software (such as AutoCAD orMicrostation), CONTRACTOR shall request OWNER’s approval.

CONTRACTOR shall use the latest released versions of such CAD systems withapplicable tested patches if any, at commencement of the WORK.CONTRACTOR shall seek prior approval from OWNER for actual versions andpatch 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 andsofware requirements for the SmartPlant tools suite.

CONTRACTOR shall use the SPPID, SPI, SPEL and SP3D seed files providedby OWNER to standardise the software across the whole RAPID PROJECT.

The system hierarchy, Plant Breakdown Structure (PBS), for IntergraphSmartPlant tools shall be created in accordance with GOOD ENGINEERINGPRACTICES but must comply with the RAPID PROJECT’s overall structure using3 levels. First level shall be designated for plant, second level is designated for

functional area and third/lowest level is designated for functional unit.


5/31

INVITATION TO BID




Section: C

Rev: 0

Page: 5 of 31


This structure including levels names and descriptions shall be approved byOWNER.

CONTRACTOR shall ensure the PBS is consistent across all project informationand design tools during the whole PROJECT duration and in the P-EDMS systemaccordingly.

CONTRACTOR shall not make changes to the PBS hierarchy withoutdocumenting the change and getting approval from OWNER for the change.

CONTRACTOR shall follow the PROJECT SPECIFICATIONS for plantcomponents identification and numbering, applicable codifications and unit ofmeasures in its databases and registers:

• “Project Procedure – Equipment and Material Identification andNumbering”;

• “Project Specification – Electrical Material Identification and Numbering

Specification”;

• “Project Specification – Instrument Identification and NumberingSpecification”;

• Section C - Part II – Chapter 4.0 ENGINEERING GENERAL - Attachment4-B - Mandatory Codification;

• “Project Procedure – Units of Measurement”.

CONTRACTOR shall follow the PROJECT SPECIFICATIONS and P-EDMS Book2 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 OTHERCONTRACTORS a procedure will be implemented by OWNER to managemodifications impacting the SmartPlant tools. The items that will be managed byOWNER are, but not limited to, modifications of:

• The reference data (rules, formats, symbols & labels, catalogs, libraries);

• The select list;

• The properties.


6/31

INVITATION TO BID




Section: C

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 requestprocedure in accordance with Section C - Part II - Chapter 23.0 ADMINISTRATION INSTRUCTIONS.

4.11.4.1 SMARTPLANT P&ID (SPPID)

CONTRACTOR shall use Intergraph’s SmartPlant P&ID software, for the purposeof creating intelligent P&ID drawings in P-EDMS. CONTRACTOR shall use thePROJECT DOCUMENTATION database and comply with the seed files providedby OWNER in PROJECT DOCUMENTATION,

CONTRACTOR shall redraw VENDOR’s P&IDs in the SmartPlant P&ID databasewith the same drafting standards as all other SmartPlant P&IDs.

Border templates and title blocks for the P&IDs should be customised to matchOWNER’s border standards which CONTRACTOR shall obtain from OWNER soas to avoid reproducing them.

CONTRACTOR shall use the P&ID’s legend sheet of all symbols provided in thePROJECT SPECIFICATIONS.

CONTRACTOR shall use, for the creation of all P&IDs, the P&ID reference data(such as symbols, templates, assemblies, report templates, rules, insulationspecification), as delivered with the SmartPlant P&ID seed file provided byOWNER.

CONTRACTOR shall not make changes to the seed file. In such case,CONTRACTOR shall comply with concession request procedure as described inSection C - Part II - Chapter 23.0 ADMINISTRATION INSTRUCTIONS. Anychanges on the seed file shall be synchronised with OWNER.

In the event that an appropriate P&ID symbol, label or attribute does not existwithin the software-delivered reference data and is required for the WORK,CONTRACTOR shall obtain OWNER’s approval to use such symbol, label orattribute.

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 insideP&ID’s drawing.

CONTRACTOR shall set up its SmartPlant P&ID consistency rules in accordancewith the GOOD ENGINEERING PRACTICES.

CONTRACTOR shall resolve or approve all design inconsistencies, including theCONTRACTOR’s inter-discipline data inconsistencies used in the P&IDs as part


7/31

INVITATION TO BID




Section: C

Rev: 0

Page: 7 of 31


of their normal work process. CONTRACTOR shall conduct database qualitychecks periodically during engineering development, to ensure thatCONTRACTOR’s inter-discipline engineering data is consistent between eachdeliverable.


8/31

INVITATION TO BID




Section: C

Rev: 0

Page: 8 of 31


CONTRACTOR shall fill in all applicable attributes to the fullest extent for all P&IDcomponents, such as pipe runs, equipment, inline instruments. This is to ensurethat OWNER receives the complete and meaningful P&ID data in SmartPlantP&ID format. CONTRACTOR is required to submit a complete list of propertiesthat will be filled in when creating the P&ID’s.

CONTRACTOR shall ensure that P&ID instrument tags associate with andcorrespond to the appropriate instrument loops. This is a firm requirement ofOWNER and will be strictly enforced.

CONTRACTOR shall follow the requirement defined in the PROJECTSPECIFICATION for tag naming conventions regarding P&ID instrument tags,instrument loop tags, EQUIPMENT tags, and line tags. Tag numbers must beentered identically within tag indexes and 3D model to ensure traceability acrossall applications.

CONTRACTOR shall follow GOOD ENGINEERING PRACTICES forimplementing 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 LICENSORPFDs and P&IDs are submitted in SmartPlant P&ID format.

SPPID Database delivery

CONTRACTOR shall deliver to OWNER the resulting P&IDs and all associateddatabase 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, testsymbols and assemblies, temporary filters, reports, from the SmartPlant P&IDdata, 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 CONTRACTOR’s checking and delivery to OWNER.

CONTRACTOR shall ensure that the delivered SmartPlant P&ID data is free ofany database exceptions and orphan entries. CONTRACTOR shall run allappropriate utilities as delivered with the software for identifying and resolving

database issues.


9/31

INVITATION TO BID




Section: C

Rev: 0

Page: 9 of 31


CONTRACTOR shall provide, before PROVISIONAL ACCEPTANCE, a back-upof the SmartPlant P&ID site and plant, with work share and project disabled. Theback-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 inreference data, data dictionary, formats, rules, and reports.

CONTRACTOR shall provide any modified source code for all DLLs that werecreated for the SmartPlant P&ID project and must highlight the modifications vis-à-vis delivered code. This code shall be sufficiently documented in accordancewith GOOD ENGINEERING PRACTICES, for the complete understanding byOWNER. It is a strict requirement that all code be issued to OWNER shall furtherenable the recompilation of the binary DLLs and shall allow continuation of use ofthe SmartPlant P&ID database throughout the term of the CONTRACT andbeyond.

CONTRACTOR shall sufficiently document any deviation from PROJECTSPECIFICATION approved during the CONTRACT and store such document inP-EDMS residing at OWNER.

4.11.4.2 SMARTPLANT INSTRUMENTATION (SPI)

CONTRACTOR shall use SmartPlant Instrumentation software for the creationand management of all instrumentation deliverables, including fieldinstrumentation 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 fileprovided by OWNER in PROJECT DOCUMENTATION.

The PBS structure definition contained within SmartPlant Instrumentation shall bealigned with the one in SmartPlant Engineering Manager, but SPI will use SPI Admin Module to manage the PBS. No additional definitions can be made thatare not identical to those defined in the SmartPlant Engineering Manager. Eachinstrument tags unit number shall match exactly with the SmartPlant P&ID whenreferring to official issue of P&ID.

CONTRACTOR shall use the naming conventions for tags as defined in thePROJECT SPECIFICATION.


10/31

INVITATION TO BID




Section: C

Rev: 0

Page: 10 of 31


CONTRACTOR shall use the same service description on the instrument datasheets as the control system point description. Standard abbreviations shall applyin accordance with Section C - SCOPE OF WORK and PROJECTSPECIFICATION.

CONTRACTOR shall use all border file templates, title blocks for the variousinstrumentation documents, and reports in accordance with PROJECTSPECIFICATION. CONTRACTOR shall customise all the instrument specificationsheets to meet OWNER’s instrument data sheet standard. CONTRACTOR shallobtain such instrument data sheets standards from OWNER so as to avoidreproducing them. If the instrument data sheet standards are not available, thedefault templates in SmartPlant Instrumentation are to be used. In case of anydeviation to these standards, CONTRACTOR shall comply with the concessionrequest procedure described in Section C - Part II - Chapter 23.0 ADMINISTRATION INSTRUCTIONS.

CONTRACTOR shall utilise the SPI seed file as provided by OWNER for thecreation of all instrumentations.

CONTRACTOR shall not make changes to the seed file without documenting thechange and getting approval from OWNER, in compliance with the concessionrequest procedure described in Section C - Part II - Chapter 23.0 ADMINISTRATION INSTRUCTIONS. Any changes on the seed file shall besynchronised with OWNER.

CONTRACTOR shall follow the GOOD ENGINEERING PRACTICES for settingup SmartPlant Instrumentation consistency rules.

CONTRACTOR shall resolve or approve all design inconsistencies including theCONTRACTOR’s inter-discipline data inconsistencies used in the SmartPlant

Instrumentation as part of their normal work process. CONTRACTOR shallconduct periodically database quality checks, during engineering development, toensure that CONTRACTOR’s inter-discipline engineering data is consistentbetween each deliverable.

CONTRACTOR will populate the SmartPlant Instrumentation data, and include allthe various available modules such as index, instrument specifications, wiring,loop drawing, hook-up, as defined in Attachment 4.11-A “Deliverables andauthoring tools”, and in accordance with PROJECT DOCUMENTATION. Allspare capacity such as free terminals and wires to be registered, not just thoseused by the development.

CONTRACTOR shall generate from SPI instrumentation deliverables inaccordance with Attachment 4.11-A “Deliverables and authoring tools”. Any


11/31

INVITATION TO BID




Section: C

Rev: 0

Page: 11 of 31


deviation from this request is required in writing and must be approved byOWNER 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, CONTRACTORshall use the reports generated by “Enhanced Smart Loop” to manually adjust theloop drawings and locations can be saved in the database.

All instrument indexes and I/O lists for VENDOR packages data shall bepopulated into the database. Wiring information or VENDOR package data whenconnected to a system supplied by CONTRACTOR (such as MAC, MMS) shallbe keyed into SmartPlant Instrumentation and the resulting deliverables beissued from SmartPlant Instrumentation for construction purposes.

CONTRACTOR shall provide official data sheets for control valves and flowelements from SPI.

CONTRACTOR shall use SPI to store the data for the alarm and controller set-

point summary. This data shall be passed to the main control system as thestarting point for configuration. A work process shall be put in place byCONTRACTOR to ensure that the alarm and set point data is kept insynchronisation 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 theOWNER’s operations and maintenance personnel, will have wrapped aroundthese 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 toensure that the methodology is continued by OWNER in the operations andmaintenance of the FACILITY. This document shall be stored in P-EDMS atOWNER and be easily available to all SmartPlant Instrumentation users.

It is a strict requirement that CONTRACTOR deliver to OWNER an As-BuiltSmartPlant 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.


12/31

INVITATION TO BID




Section: C

Rev: 0

Page: 12 of 31


CONTRACTOR shall ensure that the delivered SmartPlant Instrumentation datais free of any database exceptions and orphan entries.

CONTRACTOR shall remove all test data, test CAD blocks, temporary browserviews, temporary reports, etc. from the SmartPlant Instrumentation database andsystem directories before delivering such SPI database to OWNER.

CONTRACTOR shall deliver the SmartPlant Instrumentation database in aWatcom backup format. CONTRACTOR shall run the appropriate utilities asdelivered with SmartPlant Instrumentation for identifying and resolving databaseissues such as “CheckDB.” CONTRACTOR shall provide the log file from thisutility showing that there are no errors. It is CONTRACTOR’s responsibility to fixsuch 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 all approved deviations from PROJECTSPECIFICATION.

Such electronic deliverables will be made available on the DVD media includingan index for the content contained on the DVD.

4.11.4.3 SMARTPLANT ELECTRICAL (SPEL)

CONTRACTOR shall use SmartPlant Electrical software for the creation andmanagement of the electrical database and deliverables in accordance with the“Project Specification – Smart Plant Electrical Database Administration andStructure” which is part of the PROJECT DOCUMENTATION. CONTRACTORshall use the PROJECT DOCUMENTATION database and comply with the seedfile provided by OWNER in PROJECT DOCUMENTATION.

Border templates and title blocks for the schematics shall be customised byCONTRACTOR to match OWNER’s border standards which CONTRACTORshall obtain from OWNER so as to avoid reproducing them before any WORK

starts.


13/31

INVITATION TO BID




Section: C

Rev: 0

Page: 13 of 31


CONTRACTOR shall use the electrical reference database and the referencedata (such as symbols, schematic blocks, report templates) from the seed filesprovided by OWNER.

CONTRACTOR shall use SmartPlant Electrical default font (Arial) fordeliverables.

CONTRACTOR shall use SmartPlant Electrical to create the following electricaldeliverables:

• 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 authoringtools”. CONTRACTOR shall submit any exceptions to OWNER in writing whichmust be review and approved by OWNER, at OWNER’s absolute discretion,before starting work. For any deviation, CONTRACTOR shall comply with theconcession request procedure described in Section C - Part II - Chapter 23.0 ADMINISTRATION INSTRUCTIONS.

CONTRACTOR may need to create new user-defined attributes. Any newrequired attributes shall be approved by OWNER before being added to the datadictionary under relevant categories. A summary of added attributes shall besubmitted as a separate document describing such attributes.

CONTRACTOR shall implement tag naming conventions for various electricalitems, such as cable, motor, transformer, as per the “Project Specification - Electrical Material Identification and Numbering Specification” which is part of thePROJECT DOCUMENTATION.

CONTRACTOR shall utilise the SPEL seed file as provided by OWNER for thecreation of all electrical.

CONTRACTOR shall not make changes to the seed file without documenting thechange and getting approval from OWNER for the change. Any changes on theseed file shall be synchronised with OWNER.


14/31

INVITATION TO BID




Section: C

Rev: 0

Page: 14 of 31


CONTRACTOR shall resolve or approve all design inconsistencies including theinter-discipline data inconsistencies used in the SmartPlant Electrical as part oftheir normal work process.

CONTRACTOR shall follow the GOOD ENGINEERING PRACTICES for settingup SmartPlant Electrical consistency rules. Database quality checks will beconducted periodically throughout the PROJECT by CONTRACTOR to ensurethat inter-discipline engineering data is consistent per deliverable across theWORK.

CONTRACTOR shall fill in all applicable attributes fully for all indexed tags. Thisshall ensure that OWNER receives the complete and meaningful SPEL projectdatabase.

CONTRACTOR shall deliver all electrical datasheets and non-SmartPlantElectrical deliverables as documents which will be loaded into P-EDMS.CONTRACTOR shall relate the electrical tag number to the electrical documentsusing the template provided by OWNER in PROJECT DOCUMENTATION. This

is required to load the data and documents into OWNER’s P-EDMS system.

SPEL Database delivery

CONTRACTOR must remove all temporary drawings such as test drawings, testsymbols, 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 freeof 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 designup 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 CONTRACTORin 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 anindex of contents.


15/31

INVITATION TO BID




Section: C

Rev: 0

Page: 15 of 31



16/31

INVITATION TO BID




Section: C

Rev: 0

Page: 16 of 31


4.11.4.4 SMARTPLANT 3D (SP3D)

CONTRACTOR shall use SmartPlant 3D software for the creation andmanagement of the 3D model deliverables.

SmartPlant 3D Catalog (Reference Data) name shall be the PROJECT name withthe appendix “_Catalog. The SmartPlant 3D Catalog shall be created or checkedand reviewed in compliance with PROJECT SECIFICATION, on process, piping,civil/structural, electrical & instrumentation. Dimensional tolerances must bespecified, for example main structure +/- 10 mm, piping +/- 50 mm, fieldEQUIPMENT +/- 250 mm.

CONTRACTOR shall use GOOD ENGINEERING PRACTICES to determineadditional attribute requirements for components such as EQUIPMENT and piperuns.

CONTRACTOR shall follow GOOD ENGINEERING PRACTICES for setting upSmartPlant 3D consistency rules.

CONTRACTOR shall resolve or approve all design inconsistencies including theinter-discipline data inconsistencies used in the SmartPlant Instrumentation aspart of their normal work process. CONTRACTOR shall conduct database qualitychecks periodically throughout the PROJECT to ensure that inter-disciplineengineering data is consistent between each deliverable.

The SmartPlant 3D reference data shall be customised in accordance PROJECTSPECIFICATION. This may include components such as piping MATERIALclasses, piping commodity data, instrument data, specialty data, tap data, pipingassemblies. CONTRACTOR shall follow naming conventions and standardsdefined in Section C - SCOPE OF WORK and in PROJECT SPECIFICATION for

piping MATERIALS classes. These piping MATERIAL classes and all associatedfiles shall be delivered to OWNER in a loadable format.

In addition, any reference data files in relation to components such as electricalcable trays, ducting, steel structures, civil works, hangers & supports shall bedelivered to OWNER in loadable formats to enable bulk loading to the sourceapplication. Once loaded they shall be void of errors or missing information.CONTRACTOR shall be responsible to correct such errors or missing informationand must amend and re-submit the files until approved by OWNER.

CONTRACTOR shall maintain an up-to-date record of all modifications made tothe catalog which shall be accessible to OWNER.

CONTRACTOR shall report to OWNER each addition made to the catalog.


17/31

INVITATION TO BID




Section: C

Rev: 0

Page: 17 of 31


CONTRACTOR shall send an approval request to OWNER if CONTRACTORidentifies 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 asEQUIPMENT, nozzles, line number, line ID, columns, beams. These namingconventions should be in accordance with Section C - SCOPE OF WORK andthe PROJECT SPECIFICATION using the full tag number and be identical to thatassigned 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 onOWNER requirements.

The SmartPlant 3D model must be populated sufficiently to produce required

documents, such as isometrics, plan and elevation drawings as well as MaterialTake-Offs.

The modeling extent will be in accordance with GOOD ENGINEERINGPRACTICES and as OWNER requirement indicated in Attachment 4.11-B of thisChapter in complement of PTS standard 30.10.05.11(Jan-08) ‘Plant modelconstruction and review’.

CONTRACTOR shall use, for the modelisation of civil structure, a softwarecompatible with SP3D and with softwares used by VENDORS for detaileddrawings / shop drawings (ie. TEKLA).

CONTRACTOR shall model primary civil/structural members in SP3D andtransfer the data to civil structure software for detailing via CIS/2 interface.Progressive detailing and modifications completed in civil structure software, shallbe imported into SP3D via CIS/2 interface for ongoing clash detection anddrawing production purposes. The final delivery of civil/structural database shallcomprise of both the SP3D database as well as the detailed civil structuresoftware model databases.

CONTRACTOR shall model VENDOR packages from 2D CAD drawing files,where VENDOR is unable to provide a SP3D file for incorporation intoCONTRACTOR’s 3D model.


18/31

INVITATION TO BID




Section: C

Rev: 0

Page: 18 of 31


SP3D Database delivery

CONTRACTOR shall provide a SmartPlant 3D full back-up at followingmilestones: 30%, 60%, 90%, at status Issued for Construction and at status As-Built of the 3D model.

The SP3D deliverables shall include, but is not limited to:

• Complete SmartPlant 3D project backup performed from the SmartPlant3Dproject management environment;

• Complete backup of the project “Symbols” share, including completebackup of the directory structures for drawings and reports created fromSmartPlant 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 Archi ve:

• 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 thatthese files reflect hundred (100) percent of the catalog database (such thatthe entire catalog contents can be recreated by bulk loading these files).

• The following reports are required to be submitted:

• Final interference check report;


19/31

INVITATION TO BID




Section: C

Rev: 0

Page: 19 of 31


• Final database consistency check report;

• Complete catalog verification report;

• Final project to-do-list report;

• Line list report.

SP3D Data Checks and Clean-up

CONTRACTOR shall ensure that the delivered data is not corrupted and/orcontains inconsistencies before delivery to OWNER. As a minimum, the followingchecks and clean-up shall be performed:

General:

•

Temporary files and directories shall be removed prior to delivery toOWNER.

• SmartPlant 3D database consistency check report should be run withoutreporting inconsistencies.

• The SmartPlant 3D to-do-list shall be empty.

Piping:

• Piping isometrics must be extracted successfully for all pipelines.CONTRACTOR must modify any lines that fail to extract correctly prior todelivery to OWNER.

4.11.4.5 SMARTPLANT REVIEW (SPR)

CONTRACTOR shall use SmartPlant Review software for the different 3Dreviews (for engineering, construction, or maintenance reviews).

The acceptable 3D model deliverables are Intergraph’s SmartPlant 3D modelsprovided in Intergraph’s SmartPlant Review software VUE format.

The software shall be capable of reviewing models within CONTRACTOR’sOffice environment or at any location as agreed by OWNER. The software shallbe capable to display the entire plant model and associated data at any remote


20/31

INVITATION TO BID




Section: C

Rev: 0

Page: 20 of 31


location, totally independent of the office network. The software will support amodular approach to additional functionality.

The SmartPlant Review visualisation environment is for interactively reviewingdesigns and identifying problems graphically. Real-time, high-resolution dynamicnavigation 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 notlimited to:

• Notepad – data annotation

• Microsoft Word – data sheets

• Animations – maintenance instructions

• Microsoft Excel – MATERIAL lists


21/31

INVITATION TO BID




Section: C

Rev: 0

Page: 21 of 31


The software will support a basic viewer and a modular approach to addingfunctionality. Add-on modules will include:

• Construction module for dynamic collision detection, creating image files,and overall PROJECT management. Also include integration of theSCHEDULE by linking to Primavera or Microsoft Project planning tools.

•

API module with programming libraries to customise SmartPlant Review foryour enterprise.

• Collaboration module that allows multiple users to view and interrogate themodel 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 datacaptured from laser scanners.

• Simulation and visual effects for creating animations and motion studies.

Deliverables

Deliverables will include:

• Snapshots of the main view at any size;

• High-quality still images;

• Camera motion animations;

• Constructability plans;

• At defined milestones full model view files;

4.11.4.6 2D CAD DRAWINGS

CONTRACTOR shall use Smartsketch for the creation and management of any2D CAD drawing types that are not covered by the other SmartPlant suite oftools. Such drawings may include, but are not limited to, plot plans, layouts,EQUIPMENT details, mounting details, cable tray reports.

CONTRACTOR shall follow the GOOD ENGINEERING PRACTICES for setting

up the drawing environment, including directory structures, file namingconventions, and the location of symbol libraries and other reference data.


22/31

INVITATION TO BID




Section: C

Rev: 0

Page: 22 of 31


Border templates and title blocks for the 2D CAD drawings are required to becustomised by CONTRACTOR to match OWNER’s border standards, whichCONTRACTOR shall obtain from OWNER, so as to avoid reproducing thembefore any WORK begins.

CONTRACTOR shall follow CAD drafting in accordance with PROJECTSPECIFICATION, including standard such as fonts, line styles, hatching styleswhen creating 2D CAD drawings with SmartSketch.

Deliverables

CONTRACTOR shall provide a back-up of all drawing native files, including anyassociated reference data (such as symbols, drawing templates, reporttemplates) and any linked files (such as office documents, images)

The above electronic deliverables must be made available on DVD or CD mediawith an index of contents.

4.11.5 TAG REGISTERS

CONTRACTOR shall deliver to OWNER the following listed tag and EQUIPMENTregisters for loading into P-EDMS on rare and unusual cases where the tag is notregistered in the Intergraph SmartPlant design tools, as well as in cases wherethe required properties are not provided in the CONTRACTOR IntergraphSmartPlant 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;


23/31

INVITATION TO BID




Section: C

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 onnumbering format as defined in the PROJECT SPECIFICATION.

OWNER will reserve and provide the tag list for each CONTRACTOR to use. Inthe event that the tag number list provided is not enough during PROJECTexecution, CONTRACTOR shall request OWNER to provide new batch of tagreservation list.

4.11.7 DOCUMENTATION AND DATA QUALITY ASSURANCE AND QUALITYCONTROL

CONTRACTOR shall provide in PROJECT Quality Management Plan (PQMP)the Quality Assurance program requirement and Quality Control activities toensure fulfilment of PROJECT SPECIFICATION for document and datamanagement. The PROJECT Quality Management Plan will detailCONTRACTOR's internal data gathering, data quality management processesand handover procedures.

The CONTRACTOR is responsible for the quality of the WORK and shall take allreasonable measures to ensure that data received from the SUB-CONTRACTORS and VENDORS is:

• Complete; and,


24/31

INVITATION TO BID




Section: C

Rev: 0

Page: 24 of 31


• Consistent with / across the defined SCOPE OF WORK and PROJECTSPECIFICATION.

CONTRACTOR as part of its QA/QC programs shall ensure that cross applicationdata validation is carried out and reports extracted and submitted to ensure crossapplication data consistency. Exception reports are to be submitted to OWNERfor information, review and/or approval where required. These consistencyreports shall be produced using automated processes without manualintervention to update the reports. OWNER reserves its right to inspect andapprove the consistency and exception reporting processes.

CONTRACTOR’s Quality Assurance program requirement shall address specificpractices, resources and sequence of activities relevant to management andcontrol of the whole documentation of the PROJECT. CONTRACTOR shall referto the details stated in Section C - Part II – Chapter 14.0 QUALITYMANAGEMENT REQUIREMENTS.

END OF CHAPTER


25/31

INVITATION TO BID




Section: C

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 Excel formatProcess Flow Diagram SmartPlant P&ID

P&ID SmartPlant P&ID

Line List/Line Designation Table SmartPlant P&ID

Master Equipment List SmartPlant P&ID

Instrument Index – I/O List SmartPlant Instrumentation

Hook-Up Drawings SmartPlant Instrumentation

Instrument Loop Drawings SmartPlant Instrumentation

Wiring Diagrams SmartPlant Instrumentation

Instrument Process Data Sheet SmartPlant Instrumentation (optional)

Instrument Data Sheet SmartPlant Instrumentation

Dimensional Data Sheet SmartPlant Instrumentation

Cable Schedule SmartPlant Instrumentation and SmartPlantElectrical

Junction Box Schedule SmartPlant Instrumentation

Calculation Sheet SmartPlant Instrumentation (optional)

Electrical Consumer List SmartPlant Electrical

Load Schedules SmartPlant Electrical

Load Balance SmartPlant Electrical

Switchgear Schedules SmartPlant Electrical

Electrical Equipment List SmartPlant Electrical

ISO Drawings SmartPlant 3D

Ortho Drawings SmartPlant 3D

All other 2D CAD drawings (Foundation,Plot Plants, Mounting details, Cable Trayreports, Mechanical Layouts, Architectural, Site Layout, etc.)

SmartSketch or AutoCAD or Microstation

CONTRACTOR shall submit a concession request to OWNER for approval incase of documents and drawings which cannot be produced using SmartPlant

tools (refer to Section C – Part II – Chapter 23.0 ADMINISTRATIONINSTRUCTION for further information on concession request).


26/31

INVITATION TO BID




Section: C

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 modelingextent includes but is not limited to the information provided below.CONTRACTOR shall model VENDOR packages to the same level of detail as therest 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 beincluded. 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;


27/31

INVITATION TO BID




Section: C

Rev: 0

Page: 27 of 31


• Telecom field devices, including mounting stands (outdoor PA speakersand 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 areasonable representation of the EQUIPMENT for presentation and interferencedetection. 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 aspiping, instrumentation) represented within same philosophy thanequipment (as simple as possible, for presentation and interferencedetection);

• 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 attributesare tag number, size, pressure rating, end prep, and pipe MATERIAL class. Theequipment tag numbers are to be the same as used by other SmartPlantapplications.

Civil/Concrete/Structure:

• Site: terrain;

• Drainage and sewerage: routing outline and level, drips, manhole, catchbasin, 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, Equipmentshed/shelters, hoisting beams, and handrails. Major sections will have to belabeled;


28/31

INVITATION TO BID




Section: C

Rev: 0

Page: 28 of 31


• Stanchion: outline;

• Underground cable duct: routing, outline, and top and bottom leveltrenches;

• 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, lightingpanel, 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, andhose 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 clashdetection during engineering.


29/31

INVITATION TO BID




Section: C

Rev: 0

Page: 29 of 31


ATTACHMENT 4.11-C - EPCC HANDOVER & WORK PROCESS ARCHITECTURE

(2 pages)


30/31

INVITATION TO BID




Section: C

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)


31/31

INVITATION TO BID




Section: C

Rev: 0

Page: 31 of 31

ATTACHMENT 4.11-E – P-EDMS HANDOVER TECHNICAL SPECIFICATIONGUIDE (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

Documents