PRJ-PJL-PRC-007

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

SMARTPLANT ENGINEERING APPLICATIONS &

DRAFTING (CAD) STANDARD

PROCEDURE

APPROVAL

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 1 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

REVISION HISTORY

Rev No.

Issue Date

Revision Description

Valid Until Date

21 FEB 2018 Merged North Plant PRJ-PJL-PRC-007 Rev. 00 &

21 FEB 2021

CADD Coordination Procedure 01.50.05.04 Rev. 6 with South Plant T16-X01-143-236 Rev. 6; Also replaces North Plant Database requirements specification for the Intergraph Applications Rev.1

25 APR 2021 Minor revisions to procedure

26 APR 2024

Section 10 - Revised SmartPlant Database Revision Control

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 2 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

CONTENTS

1 GENERAL … 6

1.1 Purpose … 6 1.2 Scope … 6

1.3 Criticality … 6 1.4 Key Risks and Controls … 6 1.5 Classification … 7

1.6 Compliance … 7 1.7 Roles and Responsibilities… 7

2 SMARTPLANT APPLICATIONS … 8

2.1 Electronic Master … 8 3 PROCESS DESIGN … 9

3.1 Software Version… 9 3.2 Format of Deliverables … 9 3.3 Plant Structure… 9

3.4 Symbols, Font, & Logo… 9 3.5 Attributes…10

3.6 Tag Numbering Convention …10

3.7 Vendor Data …10 3.8 Data Accuracy…10

3.9 As-Built …10 3.10 Existing SmartPlant P&ID’s…10 3.11 Deliverables …11 INSTRUMENTATION DESIGN …13

4.1 Software Version…13

4.2 Format of Deliverables …13 4.3 Plant Structure…13 4.4 Intsrument Index and Alarm List …13 Instrument Data Sheets…14 4.5 4.6 Loop Drawings …14 4.7 Hook Up and Material List …14

4.8 Wiring Details …14 4.9 Attributes (User defined fields) …14

4.10 Tag Naming Convention …14

4.11 Accuracy …14 4.12 As-Built …15

4.13 Existing Smart Instrumentation Database …15

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 3 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

4.14 Deliverables …15

5 ELECTRICAL DESIGN …17

5.1 Software Version…17

5.2 Format of Deliverables …17 5.3 Plant Structure…17

5.4 Reference Data …17 5.5 Attributes…17

5.6 Tag Numbering Convention …18 5.7 Accuracy …18 5.8 As-Built …18 5.9 Existing Smartplant Electrical Database …18 5.10 SPEL Deliverables …18 6 3D DESIGN …20

6.1 SP3D General Requirements …20 Objects Requiring Exact Geometry Representation …20 6.1.1

6.1.2

Objects requiring approx. Geometry Representation Envelopes …21

6.2 System Names …21 6.3 Format of Deliverables …21

6.4 Plant Structure…21

6.5 Reference Data …21 6.6 Units of Measure…21

6.7 Attributes…22 6.8 Naming Convention …22 6.9 Accuracy …22 6.10 SP3D Piping Requirements…23 6.11 SP3D Instrumentation Requirements …23 6.12 SP3D Equipment Requirements …23

6.13 SP3D Civil/Concrete/Structure Requirements …24 6.14 SP3D Electrical Requirements…24

6.15 SP3D Fire Protection/Fire Fighting system requirements …24 6.16 SP3D Miscellaneous Requirements …24 6.17 Existing SmartPlant 3D Models …25

6.18 Deliverables …25 7 PDS 3D DESIGN …27

7.1 PDS 3D General Requirements …27

7.2 Existing PDS 3D Models …27 8 3D MODEL REVIEW …28

8.1 General Requirements …28

8.2 SPR Deliverables …29

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 4 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

9 DATABASE COLLABORATION…30

9.1 Software Version…30

9.2 Format of Deliverables …30

9.3 Plant Structure…30 10 SMARTPLANT DATABASE REVISIONS CONTROL …31

11 2D CAD DRAWINGS…33

11.1 Formats for Deliverables …33 11.2 Software Version…33 11.3 2D Drawing Standards…33 11.4 2D Drawing Sizes …34 11.5 Revision Numbering …34

11.6 Revision Clouds …34 11.7 Existing 2D CAD files …35

APPENDICES …36

Appendix 1 – References and Relevant Documents …36 Appendix 2 – Glossary of Terms: Definitions, Acronyms and Abbreviations …37

Appendix 3 – Typical COMPANY Drawing Titleblock (Sample) …38

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 5 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

1 GENERAL

PURPOSE

1.1 This procedure describes the COMPANY drafting standards for the COMPANY from basic 2D drawings to the engineering databases. This includes the setup and utilization of the individual SmartPlant Applications and their related database deliverables at handover to COMPANY. This procedure applies both internally and to all external parties performing work for COMPANY.

SCOPE

1.2 This procedure is applicable to all Engineering drawings including the use of the individual SmartPlant Applications to be produced and/or modified for all COMPANY projects.

Smaller projects such as Category-V & VI projects may able to produce deliverables using only CAD 2D drawings. Such cases require verification and acceptance in writing by COMPANY in order to define the platforms software and databases to be used.

SmartPlant Foundation may be used as the delivery mechanism for handover of all integrated Intergraph applications, with complete metadata relationships including tag number, system, model, manufacturer, etc. Aveva Net may also be accepted.

SmartPlant Foundation and SmartPlant based engineering design tools shall be configured in accordance with the COMPANY requirements defined in this document and shall include plant/area/unit definitions, vault names, definitions of the datasheets (especially the datasheet formats), and CAD symbols used to seed the new project.

The PMT shall consult with the Technical Documentation & Drafting Services Division to ensure exactly what standards shall apply to their project. CONTRACTOR shall request and receive written confirmation from the COMPANY Head of Technical Documentation & Drafting Services for any deviations from this standard.

1.3

CRITICALITY

This Procedure has been determined to be a Low Criticality document.

Criticality Level : Low

KEY RISKS AND CONTROLS

1.4 The key risks and controls associated with this procedure are listed below.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 6 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

Key Risks

Key Controls

•

Intergraph application setup guidelines have been defined.

• Customization requirements have been

defined.

• End user shall refer to COMPANY EDMS for

latest revision of the document.

• Standards have been clearly identified.

Utilization of wrong database / application version
Using wrong deliverable templates and report / database customization will lead to rework and delay of project information handover.
Duplication and/or uncontrolled access of critical plant data
Inconsistent standard of data making it difficult for the end user to read
Supplying wrong standard format of data that COMPANY is unable to utilize.

Table 1 - Key Risks and Controls

1.5 CLASSIFICATION This procedure has been classified as Internal based on INF-ISG-POL-001 Information Classification Policy.

1.6 COMPLIANCE

All projects shall comply with the applicable database setup requirements as defined in this procedure for the effective handover to COMPANY to ensure safe and reliable operation and maintenance of the plant / facility throughout its operational life cycle.

It is important to note that not all these standards may apply for every project. COMPANY fully understands that this procedure is scalable depending on the project. During the initial phase, any queries regarding any standard additions or omissions to this document may be discussed and agreed on. This shall be done in conjunction with the COMPANY’s Project Management Team and the Head of Technical Documentation & Drafting Services.

Compliance with this procedure is verifiable by Technical Documentation & Drafting Services Division at any time during project execution.

1.7 ROLES AND RESPONSIBILITIES

Role and responsibilities related to this procedure are defined in Section 1.6 of Procedure PRJ-PJL-PRC-006 (Project Information Handover).

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 7 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

SMARTPLANT APPLICATIONS

COMPANY has standardized on Intergraph SmartPlant Enterprise (SPE) suite of software applications for the use in all engineering projects.

CONTRACTOR shall use the SmartPlant applications as listed below during the EPC/PCI phase of the project.

Instrumentation Design - Smartplant Instrumentation (SPI)

• Process Design - SmartPlant P&ID (SPPID) • • Electrical Design - SmartPlant Electrical (SPEL) • 3D Design - SmartPlant 3D (S3D) • Legacy 3D Design - PDS 3D (PDS3D) • 3D Model Review - SmartPlant Review (SPR) • Database Collaboration - SmartPlant Foundation (SPF) or Aveva

Any drawings that cannot be extracted from the above SmartPlant databases may then be produced in 2D flat file format in AutoCAD (DWG) or Microstation (DGN). No raster drawings (Image files) from the CONTRACTOR shall be accepted without the native file. CONTRACTOR shall also ensure effort is made with vendors and sub-contrators to supply their native files as part of the deliverables.

2.1

ELECTRONIC MASTER

The SmartPlant application databases, used to generate the related individual document deliverables, shall be considered the Master. The databases shall be updated in case modifications to the generated documents have to be applied. New document versions shall be extracted from the native database source.

To ensure the integrity of the SmartPlant databases are maintained, all output files should be created in PDF format so that if any changes are made, the master SmartPlant database is required. An example of this is the extraction of a P&ID from the SmartPlant database. It should be extracted as a PDF file and not as a Microstation or Smartsketch native file.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 8 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

PROCESS DESIGN

CONTRACTOR shall use SmartPlant P&ID (SPPID) software to generate intelligent P&ID drawings.

3.1

SOFTWARE VERSION

Unless otherwise specified by COMPANY, CONTRACTOR shall use the latest available version and service pack of SPPID for the creation of all related deliverables. Exact version to be used by CONTRACTOR needs to be confirmed with the Head of Technical Documentation & Drafting Services in writing via a letter or project memo before starting any work. This version shall be established and consistently applied across the project. Any change of version or service pack including application of hot fixes is subject to approval by COMPANY Head of Technical Documentation & Drafting Services. CONTRACTOR shall use a compatible version of the Oracle database used by COMPANY. The standard Oracle character set is “AL32UTF8” and shall be confirmed before the start of the project.

3.2

FORMAT OF DELIVERABLES

For all SPPID generated documents and reports, CONTRACTOR shall either use COMPANY- provided templates, or customize border templates and title blocks to match COMPANY border and title block size. Refer Appendix –3 (Typical)

CONTRACTOR shall obtain approval from the Head of Technical Documentation & Drafting Services before utilizing customized templates.

3.3

PLANT STRUCTURE

Project plant structure shall comply with the Plant-Area-Unit (PAU) or Plant-Area-System hierarchy of the SPPID SmartPlant Engineering Manager (SPEM) module. Approved COMPANY Hierarchy shall be obtained from COMPANY.

Project setup shall be sent to the Head of Technical Documentation & Drafting Services for approval before starting the actual drafting process. Drawings shall be created at unit level only. COMPANY may also supply existing data dictionary template/s (DDT) to setup project (s).

3.4

SYMBOLS, FONT, & LOGO

It is COMPANY intention to use ANSI-based P&ID symbol reference data to the maximum extent possible. COMPANY reference data shall be provided to CONTRACTOR and include, but is not limited to: symbols, templates, assemblies, report templates, rules, and insulation specifications. CONTRACTOR shall make every attempt to utilize ANSI-based reference data for the creation of all P&IDs. In the event that an appropriate ANSI-based symbol is not available within the delivered reference data, CONTRACTOR shall create such symbol based on project requirements. Projects changes on existing facilities shall use P&ID symbols as indicated in each asset / facility P&ID legend sheets. COMPANY shall review and approve all CONTRACTOR created symbols data, before applying in the project. Unless otherwise

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 9 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

specified, CONTRACTOR shall use the SPPID default font. All logos shall be made of CAD entities, not image files, and shading will be done using cross-hatching, hatching or patterns.

3.5

ATTRIBUTES

CONTRACTOR shall create new user-defined attributes based on the project requirement, and add same to the data dictionary under the relevant category.

CONTRACTOR shall provide complete attribute data for each P&ID component.

3.6

TAG NUMBERING CONVENTION

CONTRACTOR shall adhere to COMPANY Tag Numbering Philosophy Procedure.

3.7

VENDOR DATA

All Vendor P&ID data shall be incorporated by CONTRACTOR within the SPPID project. This may require CONTRACTOR to redraw vendor P&ID’s into SmartPlant P&ID if vendor does not supply their P&IDs in SPPID.

3.8

DATA ACCURACY

Prior to handover to COMPANY, CONTRACTOR shall remove all temporary information (i.e. test drawings, test symbols and assemblies, temporary filters, reports) from the SPPID database.

CONTRACTOR shall use the SPPID “Re-create P&ID from database” functionality before final handover to COMPANY. CONTRACTOR shall ensure the delivered SPPID data is free from database exceptions and orphan entries.

Design Inconsistencies shall be managed as follows:

• CONTRACTOR shall either resolve, or approve all design inconsistencies in the P&IDs.

• CONTRACTOR shall execute all appropriate utilities delivered with the software for the

identification and resolution of database issues.

3.9

AS-BUILT

All new P&IDs created by CONTRACTOR for the project will be developed in a new SPPID project. Prior to final handover, CONTRACTOR shall ensure all P&IDs are in As-Built status.

3.10 EXISTING SMARTPLANT P&ID’S

The requirement and method of the SmartPlant P&ID database shall vary depending on the project. CONTRACTOR may request an existing COMPANY SmartPlant P&ID database to assist them with their project. This may require check out of the database by the COMPANY Head of Technical Documentation & Drafting Services. Coordination shall be documented as to how this checked out database is controlled. Depending on contractor’s scope of work, various controls will be placed on the activities of this database. The COMPANY ultimately controls the “master” data and CONTRACTOR shall abide by the controls put in place and shall deliver the changes in the database as prescribed by the COMPANY. Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 10 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

3.11 DELIVERABLES

CONTRACTOR shall handover the “output” deliverables as defined in COMPANY’s Projects Document Support Division. The handover of deliverables specific for the SmartPlant P&ID database shall include the following:

• A fully populated SmartPlant P&ID backup database and plant with work share and project disabled, including the P&ID Reference Data (symbols, templates, assemblies, report templates, rules, insulation spec, modified .dlls, etc.) used with the P&ID database on completion of the as-built activity

• A document describing the SPPID overall database - This will include a complete description of the P&ID’s and all work performed in the database. Items such as specifying customizations carried out in reference data, data dictionary, formats, rules, and reports shall be included.

• Use the SmartPlant P&ID “Re-Create P&ID from Database” functionality before final

QA&QC and delivery to COMPANY.

• Ensure that the delivered SmartPlant P&ID data is free of any database exceptions and

orphan entries and produce report for verification.

• The following list of output files shall be included with the delivery of the SmartPlant database. Please note only the P&ID’s will be extracted to the COMPANY EDMS system and handed over to the Head of Technical Documentation & Drafting Services Division. All other documents as described below are for database verification purposes only.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 11 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

Type of Documents / Drawings

Purpose

COMPANY Template Applicable

File Output Format

Upload in EDMS

P&IDs

Category-1

Yes

PDF

Yes

Instrument List

Equipment List

Valve List

Line List

Customization Document

Deviation of standards Report

Database Information / Verification

DB Cleanup Constraint Report

Database Verification

Error List Report

Database Verification

New user-defined attributes

COMPANY Application DB Checklist

Database Dictionary Verification

Table 2 - SPPID Output Files

Yes

Excel

Yes

Excel

Yes

Excel

Yes

Excel

Word

Excel

Word

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 12 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

INSTRUMENTATION DESIGN

CONTRACTOR shall use Smartplant instrumentation design data, including fire and gas detection and telecommunication.

(SPI) software to create all

Instrumentation

4.1

SOFTWARE VERSION

Unless otherwise specified by COMPANY, CONTRACTOR shall use the latest available version and service pack of SI for the creation of all related deliverables. Exact version to be used by CONTRACTOR needs to be confirmed with the Head of Technical Documentation & Drafting Services in writing via a letter or project memo before starting any work. This version shall be established and consistently applied across the project.

Any change of version or service pack including application of hot fixes is subject to approval by the Head of Technical Documentation & Drafting Services.

CONTRACTOR shall use a compatible version of the Oracle database used by COMPANY. The standard Oracle character set is “AL32UTF8” and shall be confirmed before start of project.

4.2

FORMAT OF DELIVERABLES

For all SPI generated documents and reports, CONTRACTOR shall either use COMPANY provided templates, or customize border templates and title blocks to match COMPANY border and title block size.

CONTRACTOR shall obtain approval from the Head of Technical Documentation & Drafting Services before utilizing customized templates.

4.3

PLANT STRUCTURE

Project plant structure shall comply with the Plant-Area-Unit (PAU) hierarchy of SPI. All creation and update activities shall be executed at the lowest level of the adopted SPI Plant Breakdown Structure (PBS). Approved COMPANY Hierarchy shall be obtained from COMPANY.

Project setup shall be sent to the Head of Technical Documentation & Drafting Services for approval before starting the actual drafting process. Drawings shall be created at unit level only.

4.4

INTSRUMENT INDEX AND ALARM LIST

CONTRACTOR shall generate all Instrument Index and Alarm List in customized PSR format to comply with COMPANY required data column header. Skid vendor or third party CONTRACTOR Instrument Tags and design data must be included in SPI database. COMPANY shall review and approve all CONTRACTOR created Alarm set point lists before applying in the project.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 13 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

4.5

INSTRUMENT DATA SHEETS

CONTRACTOR shall customize all instrument specification sheets to comply with COMPANY instrument datasheet standard. To avoid re-work, CONTRACTOR shall verify with COMPANY the availability of these datasheets. COMPANY shall review and approve all CONTRACTOR created datasheets before applying in the project.

4.6

LOOP DRAWINGS

CONTRACTOR shall generate all loop drawings using the SPI Enhanced Smart Loop (ESL) functionality. No manual CAD loops or manual adjustments of generated loops are permitted.

4.7

HOOK UP AND MATERIAL LIST

CONTRACTOR shall generate instrument mounting details using the SPI Hook Up functionality, ensuring compliance with COMPANY standard. CONTRACTOR shall customize all required CAD blocks in Smartsketch format.

4.8

WIRING DETAILS

CONTRACTOR shall completely perform Wiring and Connection details in SPI Wiring Module from field instrument to system cabinets. It is required to import data from System vendor this includes but not limited to; software tags and hardware wiring details into SPI.

4.9

ATTRIBUTES (USER DEFINED FIELDS)

CONTRACTOR shall use required User-Defined Fields (UDF) for relevant categories. CONTRACTOR shall submit a summary of the UDFs as a separate document. COMPANY shall review and approve all CONTRACTOR suggested use of UDF.

4.10 TAG NAMING CONVENTION

CONTRACTOR shall adhere to COMPANY Equipment Numbering Philosophy Procedure.

4.11 ACCURACY

CONTRACTOR shall create complete SPI project data to cover all modules to generate the defined SPI deliverables. CONTRACTOR shall handover a complete SPI database which enables COMPANY to utilize SPI to generate required deliverables from the database. CONTRACTOR shall ensure the delivered SPI data is free from database exceptions.

CONTRACTOR shall run all appropriate utilities delivered with SPI in order to identify and resolve issues. Prior to handover, CONTRACTOR shall remove all test information, like test CAD blocks, temporary browser views and reports, from the SPI database.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 14 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

4.12 AS-BUILT

CONTRACTOR is required to create and maintain a new SPI project database for projects that are creating new Instrumentation data. Prior to final handover CONTRACTOR shall ensure that all SPI data is fully compliant with COMPANY as-built requirements.

For modifications related to existing SPI instrumentation data, PDF files (.pdf) will be provided to CONTRACTOR for Red Line Markup (RLMU) purpose during the project phase.

As-Built process for existing SPI data will follow the As-Built process as defined in COMPANY Project Technical Information (PTI) Procedure (PRJ-PJL-PRC-006).

4.13 EXISTING SMART INSTRUMENTATION DATABASE

The requirement and method of the Smartplant Instrumentation database shall vary depending on the project CONTRACTOR may request an existing COMPANY Smartplant Instrumentation database to assist them with their project. This may require check out of the database by the COMPANY Head of Technical Documentation & Drafting Services. Coordination shall be documented as to how this checked out database is controlled. Depending on contractor’s scope of work, various controls will be placed on the activities of this database. The COMPANY ultimately controls the “master” data and CONTRACTOR shall abide by the controls put in place and shall deliver the changes in the database as prescribed by the COMPANY.

4.14 DELIVERABLES

CONTRACTOR shall handover the “output” deliverables as defined in COMPANY Technical Documentation & Drafting Services Division. The handover of deliverables specific for the Smartplant Instrumentation database shall be sent to the Head of Technical Documentation & Drafting Services and include the following:

• A fully populated Smart Instrumentation database

• A document describing the SPI overall database - This will include the software versions, uploading instructions, drawing outputs, and database customization details.

• The delivered Smartplant Instrumentation data is free of any database exceptions and

orphan entries, temporary files or temporary working areas.

• The following list of output files shall be included with the delivery of the SmartPlant database. Please note the list of output files that will be extracted to the COMPANY EDMS system and handed over to the Head of Technical Documentation & Drafting Services. All other documents as described below are for database verification purposes only.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 15 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

Type of Documents / Drawings

Purpose

Instrument Index

Category-2 Drawings

Alarm Set Point List

Category-1 Drawing

Instrument Data Sheets

Category-2 Drawings

Process Data Sheets

Category-2 Drawings

Instrument Loop Drawings

Category-2 Drawings

Wiring Diagrams

Category-2 Drawings

I/O Report/List

Category-2 Drawings

Hook Up and Bill of Materials

Category-2 Drawings

COMPANY Template Applicable

File Output Format

Upload in EDMS

Yes

PDF

Yes

Instrument Cable Schedule

Category-2 Drawings

Yes

PDF

Yes

Deviation of Standards Report

Database Information / Verification

DB Cleanup Constraint Report

Database Verification

Error List Report

Database Verification

New user-defined attributes

Database Dictionary Verification

Table 3 - SPI Output Files

Word

Excel

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 16 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

ELECTRICAL DESIGN

CONTRACTOR shall use SmartPlant Electrical (SPEL) software to create all electrical design data.

5.1

SOFTWARE VERSION

Unless otherwise specified by COMPANY, CONTRACTOR shall use the latest available version and service pack of SPEL for the creation of all related deliverables. Exact version to be used by CONTRACTOR needs to be confirmed with the Head of Technical Documentation & Drafting Services in writing via a letter or project memo before starting any work. This version shall be established and consistently applied across the project.

Any change of version or service pack including application of hot fixes is subject to approval by the Head of Technical Documentation & Drafting Services.

CONTRACTOR shall use a compatible version of the Oracle database used by COMPANY. The standard Oracle character set is “AL32UTF8” and shall be confirmed before start of project.

5.2

FORMAT OF DELIVERABLES

For all SPEL generated documents and reports, CONTRACTOR shall either use COMPANY provided templates, or customize border templates and title blocks to match COMPANY border and title block.

CONTRACTOR shall obtain approval from the Technical Documentation & Drafting Services before utilizing customized templates.

5.3

PLANT STRUCTURE

Project plant structure shall comply with the Plant-Area-Unit (PAU) hierarchy of SPEL. Approved COMPANY Hierarchy shall be obtained from COMPANY.

Project setup shall be sent to the Head of Technical Documentation & Drafting Services for approval before starting the actual drafting process. Drawings shall be created at unit level only.

5.4

REFERENCE DATA

CONTRACTOR shall create an electrical reference database and reference data in compliance with COMPANY standards. Where COMPANY standards are not available CONTRACTOR shall utilize default SPEL reference data.

5.5

ATTRIBUTES

CONTRACTOR shall create new user-defined attributes based on the project requirement, and add same to the data dictionary under the relevant category. This shall be done under reference item types and project item types. As part of the deliverables CONTRACTOR shall submit a summary of added attributes within a separate document.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 17 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

5.6

TAG NUMBERING CONVENTION

CONTRACTOR shall adhere to COMPANY Equipment Numbering Philosophy Procedure.

5.7

ACCURACY

CONTRACTOR shall remove all temporary information, like test drawings, test symbols, assemblies, temporary filters and reports, from the SPEL database. CONTRACTOR shall ensure the delivered SPEL database is free from database exceptions.

5.8

AS-BUILT

CONTRACTOR is required to create and maintain a new SPEL project database for projects that are creating new electrical data. Prior to final handover CONTRACTOR shall ensure that all SPEL data is fully compliant with COMPANY as-built requirements.

5.9 EXISTING SMARTPLANT ELECTRICAL DATABASE

The requirement and method of the SmartPlant Electrical database shall vary depending on the project CONTRACTOR may request an existing COMPANY SmartPlant Electrical database to assist them with their project. This will require check out of the database by the COMPANY Head of Technical Documentation & Drafting Services. Coordination shall be documented as to how this checked out database is controlled. Depending on contractor’s scope of work, various controls will be placed on the activities of this database. The COMPANY ultimately controls the “master” data and CONTRACTOR shall abide by the controls put in place and shall deliver the changes in the database as prescribed by the COMPANY.

5.10 SPEL DELIVERABLES

• A fully populated SmartPlant Electrical database

• A document describing the SPEL overall database - This will include the software versions, uploading instructions, drawing outputs, and database customization details.

• The delivered SmartPlant Electrical data is free of any database exceptions and orphan

entries, temporary files or working areas.

• The following list of output files shall be included with the delivery of the SmartPlant database. Please note the list of output files that will be extracted to the COMPANY EDMS system and handed over to the Head of Technical Documentation & Drafting Services Division. All other documents as described below are for database verification purposes only.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 18 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

Type of Documents / Drawings

Purpose

Single Line Diagrams

Category-1 Drawing

Schematic Diagram

Category-2 Drawings

COMPANY Template Applicable

File Output Format

Upload in EDMS

Yes

PDF

Yes

Load List

Data sheet

Category-2 Drawings

Yes

Excel/PDF

Yes

Category-2 Drawings

Yes

Excel/PDF

Yes

Electrical Cable List

Category-2 Drawings

Yes

Excel/PDF

Yes

Electrical Equipment List

Category-2 Drawings

Deviation of Standards Report

Database Information / Verification

DB Cleanup Constraint Report

Database Verification

Error List Report

Database Verification

New user-defined attributes

Database Dictionary Verification Table 4 - SPEL Output Files

Excel

Word

Excel

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 19 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

3D DESIGN

CONTRACTOR shall use SmartPlant 3D (SP3D, also called Smart 3D) software and associated software packages to create:

• 3D Model of the plant •

Associated reference database

CONTRACTOR shall deliver an As-Built 3D Model as per the scope of work defined within the contract. The 3D Model shall be structured so that disciplines (and discipline sub -sets) are represented individually. This shall be achieved by assigning levels (or equivalent), making it practicable to graphically show:

• Each level individually • Combinations of the various plant components

The 3D Model shall include all vendor packages in the same level of detail as CONTRACTOR data.

The 3D Model shall comply with COMPANY requirements as detailed in the sections below.

6.1

SP3D GENERAL REQUIREMENTS

6.1.1

OBJECTS REQUIRING EXACT GEOMETRY REPRESENTATION

• Pipelines • All critical pipelines requiring stress calculations, and all others (All sizes) • Valve dimensions only (appearance represented by envelope) • Cable tray • Ducting • Structural steel/nodes/Gusset Plates • Risers • Underground piping • Underground Cable Trench and Duct Bank • Terrain model

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 20 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

6.1.2

OBJECTS REQUIRING APPROX. GEOMETRY REPRESENTATION ENVELOPES

Instruments

• Main equipment (except for nozzles/connections, to be exact geometry) • Handling/access routes (To be transparent) • Welds (field and shop welds to be distinguished by differing symbols) • Valves • • Cable routing nodes • Electrical field equipment • Electrical lighting and field equipment • Junction boxes • Escape routes • Firefighting equipment • Doors / windows / ceilings / floors • Vendor packages

6.2

SYSTEM NAMES

The SP3D plant database name shall be the project name. The SP3D catalog (reference data) name shall be the project name with the appendix “Catalog”

6.3

FORMAT OF DELIVERABLES

For all SP3D generated documents and reports, CONTRACTOR shall customize border templates and title blocks to match COMPANY border and title block.

To avoid re-work, CONTRACTOR shall obtain approval from COMPANY in case of customized templates.

6.4

PLANT STRUCTURE

The SP3D Project plant structure for all disciplines shall comply with the Plant-Area-Unit (PAU) system hierarchy.

6.5

REFERENCE DATA

CONTRACTOR shall customize the following SP3D reference data for COMPANY

• Piping material classes • Piping commodity data • • Specialty data • Piping assemblies

Instrument data

6.6

UNITS OF MEASURE

CONTRACTOR shall use ‘mixed units’ including:

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 21 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

• Linear dimension (mm) • Nominal piping diameter (inches) • Temperature (degrees Celsius) • Pressure (psig / barg)

6.7

ATTRIBUTES

CONTRACTOR shall use the following attributes to devise SP3D model names and descriptions:

• Discipline code • SP3D module code • SP3D area name • Sequence number

6.8

NAMING CONVENTION

CONTRACTOR shall adhere to COMPANY Tag Numbering Philosophy Procedure for all components.

6.9

ACCURACY

Prior to handover, CONTRACTOR shall ensure that the delivered data is in As-Built condition, not corrupted and does not contain inconsistencies. The following checks shall be performed:

• Temporary files and directories shall be removed prior to delivery. • SP3D Database Consistency Check report shall be run without reporting

inconsistencies.

• SP3D To-Do-List shall be empty, where practicable.

Piping isometrics shall be extracted successfully for all pipelines; lines that fail to ex tract correctly need to be modified prior to delivery.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 22 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

6.10 SP3D PIPING REQUIREMENTS

CONTRACTOR shall model the following piping and piping components:

• 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 as on P&ID

• Valves including hand wheels, actuators, etc. • 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. • Vendor piping shall be modeled with proper material specification.

6.11 SP3D INSTRUMENTATION REQUIREMENTS

CONTRACTOR shall model the following instrumentation components:

• All in-line field instrument, control valves, and on-off valves including telecom field

equipment

• All process connections for instrument on piping and equipment • Offline field instrument as point locations, directional field equipment to show

orientation Junction boxes, analyzer houses, and local control panels

• • All major process attributes and identification attributes will be captured

6.12 SP3D EQUIPMENT REQUIREMENTS

CONTRACTOR shall model the following equipment components:

• 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 • Major proprietary items and ancillary equipment • Equipment envelops • The minimum attribute requirements for equipment are equipment number, insulation thickness, and description. The minimum required nozzle attributes are tag number, size, pressure rating, end prep, and pipe material class.

• Opening swing direction for hand hole, manhole, strainer and larger size nozzles that

require davit.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 23 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

6.13 SP3D CIVIL/CONCRETE/STRUCTURE REQUIREMENTS CONTRACTOR shall model the following:

• Site: terrain • Drainage and sewerage: routing outline and level, drips, manhole, catch basin, and

pits

• Foundation: outline, top, and bottom level • Concrete: outline, top, and bottom level • Steel: beams, columns, bracings, fireproofing, all floors with top and bottom level, stairs, platforms, ladders, hoisting beams, gusset plates, and handrails. Major sections will have to be labeled. Welds and non-welded connections.

• Stanchion: outline • Underground cable duct: routing, outline, and top and bottom level trenches • Underground conduits: outline • Buildings: outline incl. doors, floors, ceilings, walls

6.14 SP3D ELECTRICAL REQUIREMENTS

CONTRACTOR shall model the following electrical components:

• Outline for Electrical motors, lighting fixtures, junction boxes, cable routes (such as trays, trenches, and conduits) local control station, local panel, lighting panel, cable routing nodes and socket outlets, CCTV

• Transformers, sub-station: outline

6.15 SP3D FIRE PROTECTION/FIRE FIGHTING SYSTEM REQUIREMENTS CONTRACTOR shall model the following:

• Spray systems • Fire ring main routing, hydrants, block valves, fixed water monitors, and hose reels • Fire alarm push buttons • Fire detectors • Deluge valve manifolds

6.16 SP3D MISCELLANEOUS REQUIREMENTS CONTRACTOR shall model the following:

• Safety showers and wash fountains • Anodes, HVAC ducting and welds, Escape routes, handling and access routes. (To be

transparent)

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 24 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

6.17 EXISTING SMARTPLANT 3D MODELS

PMT may request an existing COMPANY SmartPlant 3D models to assist them with their project. This will require check out of the database by the Head of Technical Documentation & Drafting Services. Coordination shall be documented as to how this checked out database is controlled. Depending on contractor’s scope of work, various controls will be placed on the activities of this database. The COMPANY ultimately controls the “master” data and CONTRACTOR shall abide by the controls put in place and shall deliver the changes in the database as prescribed by the COMPANY deliverables.

6.18 DELIVERABLES

The handover of deliverables specific for the SmartPlant 3D database shall be sent to the Head of Technical Documentation & Drafting Services and include the following:

• A fully populated SmartPlant 3D database

• A document describing the SP3D overall database - This will include a complete description of the work performed in the database. Items such as specifying customizations carried out in reference data, data dictionary, formats, rules, and reports shall be included.

• Temporary information, models, pipelines, equipment, etc. shall be removed before

delivery.

• The following list of output files shall be included with the delivery of the SmartPlant 3D database. Please note only the Isometrics and General Arrangement drawings will be extracted from the 3D model to the COMPANY EDMS system and handed over to the Head of Technical Documentation & Drafting Services. All other documents as described below are for database verification purposes only.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 25 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

Type of Documents / Drawings

Purpose

COMPANY Template Applicable

File Output Format

Upload in EDMS

Isometric drawings (all types)

Category-3 Drawings

General Arrangement Drawings

Category-3 Drawings

Equipment General Arrangements

Category-3 Drawings

Yes

Native/PDF

Yes

Piping Plan Drawings

Category-3 Drawings

Yes

Native/PDF

Yes

MTO/Quantities

Database Information

SmartPlant Walkthrough

Material Take Off

Line List

Equipment List

Deviation of Standards Report

Design Reviews Sessions

Database Information / Verification

Complete Catalog Verification Report Database Verification

Final Database Consistency Check Reports (Zero inconsistencies)

Database Verification

Final Project To-Do-List Report

Database Verification

Final Interference Check Report with zero clashes

Database Verification

Table 5 - SP3D Output Files

Native/PDF

SPR

Excel

Word

Excel

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 26 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

PDS 3D DESIGN

Legacy PDS 3D is no longer accepted as it has been replaced by S3D. It is mentioned in this procedure since Qatargas has a legacy of 100’s of PDS 3D models for their existing facilities. In some cases where the project is minor, the existing PDS 3D model may be used to capture the updates of this project. This will require check out and approval of the database by the COMPANY Head of Technical Documentation & Drafting Services.

7.1

PDS 3D GENERAL REQUIREMENTS

All general requirements and deliverables shall be identical to SmartPlant 3D requirements. This shall be reviewed in detail as PDS 3D & SP3D do have different requirements.

7.2

EXISTING PDS 3D MODELS

COMPANY has a large legacy of existing PDS 3D model CONTRACTOR may use as reference material or as part of their new data. CONTRACTOR may request an existing COMPANY PDS 3D models to assist them with their project. This will require check out of the database by the COMPANY Head of Technical Documentation & Drafting Services. Coordination shall be documented as to how this checked out database is controlled. Depending on contractor’s scope of work, various controls will be placed on the activities of this database. The COMPANY ultimately controls the “master” data and CONTRACTOR shall abide by the controls put in place and shall deliver the changes in the database as prescribed by the COMPANY deliverables.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 27 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

3D MODEL REVIEW

Design review shall take place using the latest available software version of SmartPlant Review (SPR), and related add-on modules. It may be agreed upon by all parties that AutoDesk Navisworks may be used for convenient purposes during model reviews. It shall be noted though that all Navisworks files shall be generated from a SmartPlant Review session and both saved.

8.1

GENERAL REQUIREMENTS

The SmartPlant Review visualization environment is for interactively reviewing designs and identifying problems graphically.

Access to associated project data by moving the mouse over objects in the view shall 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 – Datasheets ▪ Animations – Maintenance instructions ▪ Microsoft Excel – Material lists

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 28 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

8.2

SPR DELIVERABLES

SPR files shall be generated for all 3D work. A typical project will require one overall SmartPlant review session and also individual SmartPlant review sessions for complex areas or units. SmartPlant review sessions should also be cleaned up to ensure the re are no orphaned items in the display and that maintenance envelopes and temporary structures are turned off. CONTRACTOR shall handover the deliverables to the Head of Technical Documentation & Drafting Services.

Type of Outputs

Purpose

COMPANY Template Applicable

File Output Format

Upload in EDMS

All SmartPlant Review Sessions

Walk Throughs

All Navisworks Sessions

Walk Throughs

.SPR

.NWD

Table 6 - SPR Output Files

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 29 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

9 DATABASE COLLABORATION

CONTRACTOR shall use SmartPlant Foundation (SPF) software to integrate all the discipline SmartPlant databases. Alternatively, Qatargas will also accept Aveva Net as the collaboration tool for the SmartPlant Applications. The main purpose for this integration is to ensure all the SmartPlant databases are consistent and compatible.

SOFTWARE VERSION

9.1 Unless otherwise specified by COMPANY, CONTRACTOR shall use the latest available version and service pack of SPF for the creation of all related deliverables. Exact version to be used by CONTRACTOR needs to be confirmed with the Head of Technical Documentation & Drafting Services in writing via a letter or project memo before starting any work. This version shall be established and consistently applied across the project.

Any change of version or service pack including application of hot fixes is subject to approval by the Head of Technical Documentation & Drafting Services.

CONTRACTOR shall use a compatible version of the Oracle database used by COMPANY. The standard Oracle character set is “AL32UTF8” and shall be confirmed before start of project.

9.2

FORMAT OF DELIVERABLES

For all SPF generated documents and reports, CONTRACTOR shall either use COMPANY provided templates, or customize border templates and title blocks to match COMPANY border and title block.

CONTRACTOR shall obtain approval from the Head of Technical Documentation & Drafting Services before utilizing customized templates.

9.3

PLANT STRUCTURE

CONTRACTOR shall develop mapping between SmartPlant applications for smooth synchronization publishing into SPF. The detailed mapping template shall be developed and agreed upon before project kickoff between CONTRACTOR and COMPANY.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 30 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

10 SMARTPLANT DATABASE REVISIONS CONTROL Brown field projects often require a CONTRACTOR to update data that is stored in the company’s various existing SmartPlant databases. These databases include the following company standards :

Hexagon (Intergraph) PDS 3D Hexagon (Intergraph) S3D Hexagon (Intergraph) SPPID Hexagon (Intergraph) SPI Hexagon (Intergraph) SPEL

Legacy 3D model SmartPlant 3D Model SmartPlant P&ID database Smartplant Instrumentation database SmartPlant Electrical database

Major Projects

Major projects shall develop new SmartPlant databases for all the SmartPlant applications for their specific project. They shall follow the Qatargas SmartPlant Engineering Applications And Drafting (CAD) Standard PRJ-PJL-PRC-007. They may also request SEED files, template files, border files, & existing SPPID databases to assist them with setting up their new SmartPlant databases. They also shall confirm with Qatargas in writing the latest approved software versions for each application. For example, if a major project is going to revise an existing brownfield SPPID database, they shall request a check out copy of it from Qatargas company and then may make it their own database by adding their major project work to it. At project end, they will hand the SPPID database back to Qatargas.

Minor Projects

For revisions to SmartPlant databases for minor projects, there are multiple solutions to best accommodate the Contracting company and Qatargas requirements. Ultimately it is up to Qatargas to approve which of these methods best apply to the specific project. The CONTRACTOR must obtain in writing the approved method of updating these SmartPlant databases prior to the commencement of revising this data.

• Large Size Minor Projects

As similar with major projects, large minor projects shall develop new SmartPlant databases for all the SmartPlant applications for their specific project. They shall follow the Qatargas SmartPlant Engineering Applications And Drafting (CAD) Standard PRJ-PJL-PRC-007. They may also request SEED files, template files, border files, and existing SPPID databases to assist them with setting up their new SmartPlant databases. They also shall confirm with Qatargas in writing the latest approved software versions for each application. For example, if a minor project is going to revise an existing brownfield SPPID database, they shall request a check out copy of it from Qatargas company and then may make it their own database by adding their minor project work to it. At project end, they will hand the SPPID database back to Qatargas.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 31 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

• Medium Size Minor Projects

Medium size minor projects will be required to develop their data in existing SmartPlant databases for all the SmartPlant applications for their specific project. CONTRACTOR shall request a check out copy of the SmartPlant database from Qatargas company and then they may revise it adding their project data. Qatargas will determine the best method to share this database and supply instructions of how the CONTRACTOR may update and return it. SmartPlant Database workshare is the desired method to accommodate the editing of a single database between the Company and the CONTRACTOR . Qatargas will supply and enforce all standards, versions, and customization are maintained to ensure the database may be imported back into the master database at project end.

• Small Size Minor Projects

Qatargas understands that possible small projects, contractor’s will find it not practical to update existing data in the SmartPlant databases. Updates may be done outside these databases using traditional basic 2D cad applications such as AutoCAD for these small projects. All data may be revised and submitted to the COMPANY in this basic 2D format. For example, the CONTRACTOR may request 6 SmartPlant P&ID’s for check out of the SmartPlant database and will receive them in their desired format such as Smartsketch format (IGR), AutoCAD format (DWG), or Microstation format (DGN). They may then update these 2D files and submit them back to Qatargas at project end. Qatargas will then recreate these into the SmartPlant P&ID data. Please note this method is the least desired method as it requires duplication of work. CONTRACTOR is required to get pre-approval in writing for this method to be used. In general, a small project will be creating or revising less than 10 P&IDs for their proje ct. While the above example is for SPPID, it may also apply to SI, SPEL, and S3D.

In conclusion, Qatargas will work with the CONTRACTOR to best determine what method shall be used to share and revise the SmartPlant data. Every project is different and may require a specific method to assist the CONTRACTOR yet ensure Qatargas is receiving valid data. Different methods may be applied for the different SmartPlant databases. In the end, it will benefit both the CONTRACTOR and the company if an agreed and approved methodology is developed at project commencement to move forward on how to revise and share the SmartPlant databases.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 32 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

11 2D CAD DRAWINGS

11.1 FORMATS FOR DELIVERABLES

2D CAD files (Non-intelligent database files) shall only be accepted if they may not be generated by one of the SmartPlant Databases. The following three CAD formats shall be accepted:

AutoCAD File (DWG)

Microstation File (DGN)

Smartsketch File (IGR)

All drawings shall be delivered as a native file. No other type of native 2D CAD files may be accepted without written approval from the COMPANY Head of Technical Documentation & Drafting Services. Raster files shall not be accepted unless it is mutually agreed the native file is not available. The efile name shall match exactly the drawing file name. All drawings should be cleaned up before delivery. No reference files are allowed. No data outside the border area is allowed. All drawings should be compacted and cleaned of data allowing the e-file to be the smallest possible size. Only one CAD drawing may be contained in one electronic file. All drawing files should be saved in such a way that when opened, the whole drawing fills the screen.

11.2 SOFTWARE VERSION

Unless otherwise specified by COMPANY, CONTRACTOR shall use the latest available version for all related deliverables. Exact version to be used by CONTRACTOR needs to be confirmed with the Head of Technical Documentation & Drafting Services in writing via a letter or project memo before starting any work. This version shall be established and consistently applied across the project.

11.3 2D DRAWING STANDARDS

COMPANY shall provide various standard SEED files such as border files, title block standards, drawing sizes, scaling, etc. Refer Appendix –3 (Typical) For specific electronic drafting standards such as line weights, line styles, colors, fonts, and drawing layouts, COMPANY allows CONTRACTOR to use his best practices to develop the drawings. Although for revisions to existing COMPANY drawings, CONTRACTOR is expected to matchup the existing attributes for consistency purposes.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 33 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

11.4 2D DRAWING SIZES

All drawings shall be in A1 / A3 / A4 size. The preferred A1 size drawing content and layout shall be such that when printed to A3 size, the drawing remains legible. Exceptions to this may be applied for drawings like overall plot plans / diagram subject to COMPANY written approval. The use of A0 size (1189x841 mm) shall be the exception, and is only permitted for scaled plot plans where clarity and legibility may be a problem. A0 size drawing content and layout shall be such that when print to A2 size (594x420 mm), the drawing remains completely legible. The dimensions are as follows:

A0 : 1189mm X 841mm

A1 : 841mm X 594mm

A3 : 420mm X 297mm

A4 : 210mm x 297mm

11.5 REVISION NUMBERING

CONTRACTOR shall follow the COMPANY Document Numbering Procedure for revision numbering of new documents.

11.6 REVISION CLOUDS All changes under the revisions on the drawing shall be highlighted by a revision cloud and identified by a revision triangle location within, or adjacent to the revision cloud. This triangle number will be identical to the revision number located in the revision block and the revision number block at the bottom right corner of the title block (if applicable).

It is not a requirement to insert revision clouds in the following cases:

• On new drawings handed over to COMPANY (revision clouds and revision

triangle shall not be used)

•

If there are only minor changes, such as spelling corrections or notes that have been moved to another location on the same drawing

If there is any changes anywhere in the title block

• Revision cloud shall not be used for schedules or lists (i.e. Line List, Cable schedule, Alarm Set Point List etc.). However, a revision triangle shall be placed on the left or right side of updated row/column.

Previous revision clouds and revision triangle must be removed once a new revision has occurred. revision triangle

If found the existing drawings needs to be updated as part of the project scope, a scope cloud mark shall be used to indicate changes affected under the scope of work. This scope cloud MUST be retained until the final CAD data delivery to the COMPANY.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 34 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

11.7 EXISTING 2D CAD FILES

CONTRACTOR shall submit the check-out request to obtain a native file format for updating or revising. COMPANY shall check out the drawings/document to perform a document update based on the check-out request. However, revisions to existing COMPANY drawing/ documents will not be accepted unless there was check-out performed earlier.

If any new sheets are to be created, the existing drawing number shall be follow ed or only new sheet numbers are to be assigned. New drawings are only to be created if there are no existing drawings/documents are showing the required information. Creation of new documents to indicate changes in an existing facility will not be accepte d.

CONTRACTOR shall maintain the native final format and standards on the checked out drawing unless specified different by the COMPANY. Basic internal CAD file structure such as levels, colors, line styles, and weights shall be matched and maintained. If CONTRACTOR encounters any critical drawings in raster format which are to be updated as part of a project, CONTRACTOR shall re-draw them in the appropriate native format, and include them in final data delivery.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 35 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

APPENDICES

APPENDIX 1 – REFERENCES AND RELEVANT DOCUMENTS

Number

Title

PRJ-PJL-PRC-004

Facilities Engineering and Vendor Document Numbering

PRJ-PJL-PRC-005

Facilities System and Unit Number Codes and Descriptions

PRJ-PJL-PRC-006

Project Information Handover Procedure

PRJ-PJL-PRC-008

COMPANY Equipment Numbering Philosophy procedure

PRJ-PJL-PRC-034

Engineering Drawings Redlining Procedure

PRJ-PJL-PRC-048

Facilities Documentation Metadata Requirements

PRJ-PJL-PRC-049

Project Information Handover, Verification and Acceptance

PRJ-PJL-PRC-071

Integrity Critical Documents Ownership & Approval Procedure

N/A

COMPANY Hierarchy Plant-Area-Unit (PAU)

COMPANY Drafting (CAD) Procedure Handover Checklist

COMPANY Current Drafting Software Versions

Please request to COMPANY Technical Documentation & Drafting Services Division to obtain any of these document numbers and copies. These standards and procedures may have changed.

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 36 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

APPENDIX 2 – GLOSSARY OF TERMS: DEFINITIONS, ACRONYMS AND ABBREVIATIONS

Term

AIL

CAD

Description

Asset Information Lifecycle

Computed Aided Design

Projects Document Support Division

COMPANY

Qatargas Operating Company Ltd.

CWR

DFO

EDMS

EPC

HDD

ILD

ISO

MOC

OTS

P&ID

PBS

PCI

PDS 3D

PFD / UFD

PMT

QA&QC

RDB

RLMU

CAD Work Request

Document for Operations

Electronic Documents Management System

Engineering Procurement and Construction

Hard Drive Disk

Instrument Loop Diagram

Isometric

Management of Change

Operation Technical Support

Piping & Instrumentation Diagram

Plant Breakdown Structure

Procurement Construction and Installation

Intergraph 3D Model

Process Flow Diagram / Utility Flow Diagram

Project Management Team

Quality Assurance & Quality Check

Reference Database

Red Line Mark Up

SLD / OLD

Single Line Diagram / One Line Diagram

SPI

SPEL

SPF

SPPID

SP3D

SPR

Smartplant Instrumentation Database

SmartPlant Electrical Database

SmartPlant Foundation

SmartPlant P&ID Database

SmartPlant 3D Model

SmartPlant Review

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 37 of 38

Classification: Internal

UNCONTROLLED IF PRINTED PRJ-PJL-PRC-007 Procedure

APPENDIX 3 – TYPICAL COMPANY DRAWING TITLEBLOCK (SAMPLE) COMPANY title blocks are project specific, and shall be obtained from COMPANY drawing office before start the work.

Typical COMPANY drawing title block

Typical COMPANY drawing CONTRACTOR title block

Effective 26 APR 2021

•SmartPlant Engineering Applications And Drafting (CAD) Standard Procedure• Rev 01 • Criticality Level: Low • Classification: Internal •

Page 38 of 38

Project: Q-21699 - Saipem COMP2 Folder: RFQ Files

Infinity

Explorer

Graph View

Backlinks