PDMS IMPLEMENTATION PROCEDURE

Equipment Description: N/A

Tag/Item numbers(s): N/A

Rev. Date By Chkd Appr. Status Revision reason for issue description

Shell Project No.: HP-3000-QAT Contractor name: Unit:

CB&I 0-0000
Contractor Project No.: 5887
Contractor Contract No.: PI-095 Sheet: 1 of 32 PCWBS: OZ
Contractor Doc No: Contractor Doc ID:
PEARL GTL PROJECT Orig. Org.: 153130-000-PI-P18-0003 4953
QATAR CB&I
Project Doc No: T-4.155.792 Rev.: 2
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

CB&I Status and Revision

Issued for
2 19-Sept-07 NC TL AJT/DJW
Implementation
Issued for Internal
1 8-June-07 MB RD PB-F
review
CB&I Client
Rev Date Purpose of Issue By Check
Approved Approved

INPUTS
Document Number Title Status
IMS-03-01-01-TG-05 Multi-Discipline Implementation of 3D CAD Systems Rev 1
IMS-03-01-01-TG-PI-37 Pipe Support Methodology Onshore Rev 0
DEP 30.10.05.11-Gen Shell DEP Plant Model Construction and Review N/A
T-4.200.288 3D Model Management & Coordination Guidelines Rev 0
153130-000-PR-W47- Process Engineering Flow Scheme Harbour Legend Rev 1
0024-03 (T-4.154.257) Sheet 3 of 4 General Notes and Abbreviations
T-13.370.002 Process Engineering Flow Scheme General Notes Rev G
and Abbreviations Piping & Instrument Symbols

CB&I REVISION NOTES AND HOLDS

Revision Description of Changes & Holds
1 Issued for Internal Review.
Hold 1 Manual Valve Tagging Page 19.
Hold 2 Pipe Support Naming Convention Page 18
2 Issued for Implementation.
Generally Updated Holds 1 & 2 removed.
Hold 3 PDMS Work Instructions Document. Page 19
Hold 4 Process Valve Numbering. Page 20

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 2 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

Executive Summary

The purpose of this document is to define the management and control of the 3D PDMS Model
and to ensure that a structured and consistent approach is adopted across all Engineering
Design Disciplines for the Shell Pearl Tanks (SPT) Project. This document will be modified and
updated on a continual basis as the project is developed.

ABBREVIATIONS
The following abbreviations and definitions are used throughout this procedure:-
Bar Menu Toolbar at the top of the PDMS window.
Coordinates All coordinates are in millimetres unless otherwise noted.
DB PDMS Database.
MDB Multiple database – Group of PDMS databases.
Monitor PDMS Monitor Module used to select the PDMS MDB/Module.
Design Module Module within the PDMS system used to build the 3D Model.
Draft Module Module within the PDMS system used to generate drawings of the
3D Model.
Isodraft Module within the PDMS system used to produce Piping/Electrical
& Instrument isometrics from the 3D Model.
PDMS Vantage Plant Design Management System.
PDMS CAD Person responsible for the Administration of the PDMS project.
Coordinator
Aveva REVIEW Software to enable “walk through” of the complete 3D CAD Model
UDA User Defined Attribute.
VPRM VANTAGE Project Resource Management
VPD VANTAGE Plant Design
MDS Multi Discipline Supports
RFSU1 Ready for Start Up 1
RFSU2 Ready for Start Up 2
RFSU3 Ready for Start Up 3
RFSU4 Ready for Start Up 4
PEFS Process Engineering Flow Scheme
PMC Project Management Contractor

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 3 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

Contents
PURPOSE ...................................................................................................................................... 6
1.1 Brief Project Description........................................................................................... 6
1.2 Scope of Document ................................................................................................... 6
2. PDMS ADMINISTRATION.................................................................................................... 6
2.1 Responsibilities ......................................................................................................... 6
2.2 Entry to PDMS ............................................................................................................ 6
2.3 MDB............................................................................................................................. 7
2.4 User names and Passwords ..................................................................................... 7
2.5 Detail Model MDB....................................................................................................... 7
3. ALL DISCIPLINES................................................................................................................ 8
3.1 Sites and Zones Names............................................................................................. 8
3.2 Site and Zone Positions and Orientations............................................................. 13
3.3 Area Code Attributes ............................................................................................... 13
3.4 Purpose and :DCODE Attributes ............................................................................ 13
3.5 :Revcol Attributes .................................................................................................... 14
3.6 Scratch Sites and Zones ......................................................................................... 14
4. PIPING ................................................................................................................................ 14
4.1 Piping Zone Names.................................................................................................. 14
4.2 Pipe Names............................................................................................................... 14
4.3 Pipe Attributes ......................................................................................................... 14
4.4 Isometric Data .......................................................................................................... 14
4.5 Pipe Supports........................................................................................................... 14
4.6 Valve Data................................................................................................................. 14
5. PROCESS AND SAFETY EQUIPMENT ............................................................................ 14
5.1 Equipment Zone Names .......................................................................................... 14
5.2 Equipment Names.................................................................................................... 14
5.3 Equipment Datum’s ................................................................................................. 14
6. CIVIL,STRUCTURAL & MARINE (CSM) ........................................................................... 14
6.1 CSM Zone naming.................................................................................................... 14
6.2 Structure and Framework Names........................................................................... 14
6.3 Framework Attributes.............................................................................................. 14
7. INSTRUMENT/ELECTRICAL/TELECOMS (EIT) ............................................................... 14
7.1 EIT Zone Naming...................................................................................................... 14
7.2 EIT Component Naming .......................................................................................... 14
8. PDMS MODEL STATUS .................................................................................................... 14
8.1 General Progress Monitoring ................................................................................. 14
8.2 Clash Check of the PDMS model............................................................................ 14
9. DRAWING PRODUCTION ................................................................................................. 14
9.1 Draft........................................................................................................................... 14
9.2 Drawing Files............................................................................................................ 14
9.3 Piping Isometrics ..................................................................................................... 14
10. DESIGN REVIEWS ............................................................................................................. 14
11. AVEVA REVIEW................................................................................................................. 14
12. SOFTWARE INTERFACE/SUPPORT................................................................................ 14
12.1 Applications ............................................................................................................. 14
13. JETSTREAM NAVISWORKS............................................................................................. 14

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 4 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

14. PMC DATA TRANSFER..................................................................................................... 14

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 5 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

PURPOSE
The purpose of this document is to define the management and control of the 3D
PDMS Model and to ensure that a structured and consistent approach is adopted
across all Engineering Design Disciplines for the Pearl GTL Project. This document will
be developed and updated on a continual basis as the project is developed.
This document should be read in conjunction with the Multi-Discipline Implementation
of 3D CAD Systems IMS - IMS-03-01-01-TG-05

1.1 Brief Project Description

The Qatar Shell GTL Limited (QSGTL), Pearl Project is a grass-roots development of a
Gas to Liquids (GTL) Facility located at Ras Laffan Industrial City (RLC), on the North-
East Coast of Qatar. The facility comprises 2 x 70,000 bpd GTL trains producing clean
hydrocarbon products, e.g., Light Detergent Feedstock (LDF), Liquid Petroleum Gas
(LPG) Naphtha, Gas oil, Lube Base Oils for export. The plant is planned to be ready for
a phased start up in 2010 and 2011.
The tankage portion of the Project comprises two tank farm complexes one located on-
site and one offsite at the harbour area facility. The tank farm complex at each location
consists of the following:
Onsite: Thirty-two (32) Storage Tanks plus associated Pumping Equipment,
Piping Instrument, Electrical and Civil Engineering works including a Field
Auxiliary Room (FAR) and an Electrical Substation.
Offsite: Six (6) Storage Tanks plus associated Pumping Equipment, Piping
Instrument, Electrical and Civil Engineering works including a Field
Auxiliary Room (FAR) and an Electrical Substation.

1.2 Scope of Document

The standards identified in this document will form the Layout and Piping Group Basis
of Design.
Within RFSU-1 the more stringent standards and guidelines of Ras Laffan City (RLC)
and Qatar Gas Petroleum Company (QGPC) shall be applied.
Within RFSU-2,3 and 4 the Shell DEP’s shall be applied.

2. PDMS ADMINISTRATION

2.1 Responsibilities
The project PDMS CAD Coordinator will be responsible for the administration and
control of the PDMS model. The Lead Discipline Engineers are responsible for the
Management and Technical Content of the 3D model.
Project Engineering is responsible for the co-ordination of the Formal Design Model
Reviews.

2.2 Entry to PDMS

The Pearl GTL Project will utilise Windows XP Network and PDMS 11.6sp3.
PDMS is started using Desktop/pdms 11.6 CB&I
Project: SPT

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 6 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

2.3 MDB
The project will be set-up to use multi-write access for all Design and Draft databases.
Access to the model will be controlled by the PDMS CAD Coordinator or his deputy.

2.4 User names and Passwords

The PDMS CAD Coordinator will create all User Names and Passwords and allocate
users the appropriate access rights to the Pearl GTL Project PDMS 3D model. The
User name will consist of the first four letters of the Users surname followed by the first
letter of the forename i.e.
Bilbo Baggins -PDMS User Name will be BAGGB
Passwords will initially be allocated by the CAD Coordinator and can be changed by
the user in Monitor at any time

2.5 Detail Model MDB

The MDB naming convention for the Detail Design phase of the project has been
created to allow multi-discipline access to the model in a controlled manner.
The MDB naming convention is as follows :-

MDB Name Content

RFSU1 All Plant Areas RFSU 1
RFSU2 All Plant Areas RFSU 2
RFSU3 All Plant Areas RFSU 3
RFSU4 All Plant Areas RFSU 4
SPTCAT Catalogue and Specifications
DRAFT-PIPING(1) Piping Drawing Production Area RFSU 1
DRAFT-PIPING(2) Piping Drawing Production Area RFSU 2
DRAFT-PIPING(3) Piping Drawing Production Area RFSU 3
DRAFT-PIPING(4) Piping Drawing Production Area RFSU 4
DRAFT-CIVIL&STRU(1) Civil and Structural Drawing Production Area RFSU 1
DRAFT-CIVIL&STRU(2) Civil and Structural Drawing Production Area RFSU 2
DRAFT-CIVIL&STRU(3) Civil and Structural Drawing Production Area RFSU 3
DRAFT-CIVIL&STRU(4) Civil and Structural Drawing Production Area RFSU 4
DRAFT-E&I(1) Electrical & Instruments Drawing Production RFSU 1
DRAFT-E&I(2-4) Electrical & Instruments Drawing Production RFSU 2-4
DRAFT-SUPPORTS(1) MDS Drawing Production Area RFSU 1
DRAFT-SUPPORTS(2) MDS Drawing Production Area RFSU 2
DRAFT-SUPPORTS(3) MDS Drawing Production Area RFSU 3
DRAFT-SUPPORTS(4) MDS Drawing Production Area RFSU 4

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 7 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

3. ALL DISCIPLINES

3.1 Sites and Zones Names

3.1.1 Detail Model Site Names

Site names for the Detail Design model are based on a combination of the Construction
Main/Sub Area name as described in the attached sketches and the Discipline/Activity
name.
e.g. 201-PIPE where 201 is the area number and PIPE is the discipline.
By default there will be a single Site for each discipline in each Construction Main/Sub
Areas.
RFSU1

3.1.2 RFSU 1 Construction Areas

/101 Gas Tank 19161T-03

/102 Kerosene Tank 19161T-02

/103 Naptha Tank 19161T-01

/104 Distillate Slops Tanks 19171T-01 & 19197T-01

/105 Substation & Firewater Tank 19130-B01,19147-B01,19133T-01

/106 Firewater

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 8 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

/107 Pump Area (North & South)

/108 Not used

/109 Not used

/110 Not used

/111 Not used

/112 Not used

/113 Not used

/114 PipeTrack (East, North/South)

RFSU2, 3 & 4

3.1.3 RFSU 2 Construction Areas

/201 Tank 0T-8684

/202 Tanks 0T-8641 & 0T-8642

/203 Tank 0T-8652

/204 Tank 0T-8651

/205 Tanks 0T-8654 & 0T-8661

/206 Tank 0T-8631

/207 Tank 0T-8632

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 9 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

/208 Pump Area No.1 (Area 201/202)

/209 Pump Area No.2 (Area 203/204)

/210 Pump Area No.3 (Area 204/205)

/211 Pump Area No.4 (Area 206/207)

/212 General Area (Firewater,Future & Access)

/213 Not used

/214 PipeTrack (South, East/West local to Area 203 – 207)

3.1.4 RFSU 3 Construction Areas

/301 Tanks 1T-8802A&B (Hot Slops)

/302 Tank 0T-7601 & Tank 0T-8230

/303 Tanks 2T-8802A&B (Hot Slops)

/304 Not Used

/305 Tank 0T-8801A&B (Cold Slops)

/306 Not Used

/307 Tank 8851 (Sour Slops)

/308 PipeTrack (North/South local to Area 301/302/303)

/309 PipeTrack (North/South local to Area 305/307),Pumps & Air Cooler

/310 Not used

/311 Not used

/312 General Area (Firewater,Future & Access)

/313 Not used

/314 PipeTrack (South, East/West local to Area 301/302)

3.1.5 RFSU 4 Construction Areas

/401 Tank 0T-8672, 0T-8673 & 0T-8678

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 10 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

/402 Tank 0T-8676 & Tank 0T-8677

/403 Tank 0T-8671, 0T-8674, 0T-8675 & 0T-8679

/404 Pump Area No.1 (Area 403)

/405 Tank 0T-8681, 0T-8683 & 0T-8687

/406 Tank 0T-8682, 0T-8685 & 0T-8686

/407 Not used

/408 Not used

/409 Not used

/410 Not used

/411 Not used

/412 General Area (Firewater,Future & Access)

/413 PipeTrack (Dog legged local to Area 403/404/405)

/414 PipeTrack (East, North/South local to Area402/404/405/406)

Default Sites have been created for the following areas:

/100-ARCH Architectural Site for RFSU1

/100-CIVIL Civil Site for RFSU1

/100-E&IT Elec/Inst Site for RFSU1

/100-ELEC Elec Site for RFSU1

/101-CIVIL Civil Site for RFSU1 area 101

/101-EQUI Mechanical Equipment Site for RFSU 1 area 101

/101-PIPE Piping Site for RFSU 1 area 101

/101-STRC Structural Site for RFSU1 area 101

/101-SUPP Supports Site for RFSU1 area 101

Repeated for areas 102 – 114 (Civil, Equi, Pipe, Strc & Supp)

/200-ARCH Architectural Site for RFSU2

/200-CIVIL Civil Site for RFSU 2

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 11 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

/200-E&IT E&I Site for RFSU 2

/200-ELEC Electrical Site for RFSU 2

/200-STRC Structural Site for RFSU 2

/201-CIVIL Civil Site for RFSU 2 Area 201

/201-EQUI Mechanical/equipment Site for RFSU 2 Area 201

/201-PIPE Piping Site for RFSU 2 Area 201

/201-STRC Structural Site for RFSU 2 Area 201

/201-SUPP Supports Site for RFSU 2 Area 201

Repeated for areas 202 – 214 (Civil, Equi, Pipe, Strc & Supp)

/300-ARCH Architectural Site for RFSU 3

/300-CIVIL Civil Site for RFSU 3

/300-ELEC Electrical Site for RFSU 3

/300-INST Instrument Site for RFSU 3

/301-CIVIL Civil Site for RFSU 3 Area 301

/301-EQUI Mechanical/Equipment Site for RFSU 3 Area 301

/301-PIPE Piping Site for RFSU 3 Area 301

/301-STRC Structural Site for RFSU 3 Area 301

/301-SUPP Supports Site for RFSU 3 Area 301

Repeated for areas 302 – 314 (Civil, Equi, Pipe, Strc & Supp)

/400-ARCH Architectural Site for RFSU 4

/400-CIVIL Civil Site for RFSU 4

/400-ELEC Electrical Site for RFSU 4

/400-INST Instrument Site for RFSU 4

/401-CIVIL Civil Site for RFSU 4 Area 401

/401-EQUI Mechanical/Equipment Site for RFSU 4 Area 401

/401-PIPE Piping Site for RFSU 4 Area 401

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 12 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

/401-STRC Structural Site for RFSU 4 Area 401

/401-SUPP Supports Site for RFSU 4 Area 0401

Repeated for areas 402 – 414 (Civil, Equi, Pipe, Strc & Supp)

3.1.6 Zone Names

Zones Names will be the same as the Site Name with a suffix to denote the Zone
content e.g. /101-PIPE-OD
Zone name suffixes are detailed in the discipline specific sections of this document.

3.2 Site and Zone Positions and Orientations.

All sites and Zones are to be orientated Y is N and Z is U, no deviation from this will be
permitted. The Project Site Datum is to be used for all modelling and deliverables
therefore all site and ZONE positions shall be set as follows:
Sites East 0 North 0 UP 0
Zones East 0 North 0 UP 0
The RFSU1 Site Datum is at E. 236609.6163 N. 460592.0245 U. 1.70 (relative to
Ras Laffan Industrial City Qatar National Grid Co-Ordinates)
The RFSU2/3/4 Site Datum is at E. 227800.920 N. 460584.436 U. 0 (relative to Ras
Laffan Industrial City Qatar National Grid Co-Ordinates)
Plant North is 27.95 from True North
Elevation 100000 is equal to the High Point of paving elevation relative to Ras
Laffan Industrial City Co-ordinates.

All Coordinates quoted on drawings shall be in millimeters relative to PDMS

WORLD Coordinates.

3.3 Area Code Attributes

To enable the Clash manager and the progress reports to function correctly all Sites
and Zones must have the :AREACODE attributes set in accordance with the
Construction Areas listed in section 3.1 above. e.g. 103 for the Naptha Tank Area.

3.4 Purpose and :DCODE Attributes

To enable the Clash manager and the templates for Reports and Drawing production to
function correctly all Site and Zones must have both the PURP, and :DCODE,
attributes set in accordance with the conventions outlined below:
Purpose Attributes at Site and Zone

Purpose Discipline/Activity
ARCH Architectural
CIVI Civils
POWE Electrical Equipment
TRAY Telecoms, Electrical and Inst. Cable Rack
DUCT Heating, Ventilation & Air Conditioning Ductwork

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 13 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

INST Instrument off-line equipment

TELE Telecoms
PIPE Piping Pipework
EQUI Process Vessels and Facilities
SAFE Personnel Safety and Escape Route
SUPP Multi- Discipline Supports
STRC Structural Steelwork
UNDE Underground Utilities and Pipework
ACST Access Stairs and Ladders
LIGH Lighting
NONE Unclassified
ACCE Maintenance Access Volumes

:Dcode Attributes at Site and Zone

:Dcode Discipline /Activity

EEEF Electrical Equipment – Future
EEEQ Electrical Equipment
EEFE Electrical Field Equipment
EEJU Jumps - Elroute
EELI Lighting
EERA Racking
EETR Transits
CRSU Cable Rack supports
EEPN Electrical Penetration
EFEQ Safety Equipment
EFEF Safety Equipment - Future
EFFW Firewater pipes
EHGE HVAC General Extract System
EHGS HVAC General Supply System
EHTE HVAC Toilet Extract System
EHPR HVAC Pressure Relief System
EHWE HVAC Workshop Extract System
EHPL HVAC Plumbing system
EHPC HVAC Plumbing Centrelines
EIEF Instruments Equipment - Future
EIEQ Instruments Equipment
EIFG Instruments Fire & Gas Equipment
ELFF Architectural Floor Finishes
ELEW Architectural External Walls
ELIW Architectural Internal Walls
EMEF Mechanical/Process Equipment - Future
EMEQ Mechanical/Process Equipment
EPER Escape Routes
EPLA Lay down Areas
PFCL Piping Future (Centreline)
EPPI Piping
PICL Piping (Double + Centreline)
EPEX Pipe Supports
EPPN Piping Penetrations
ESAC Access Stairs & Ladders
ESPL Structural Plating

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 14 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

ESPD Structural Primary Steel ( Deck Members)

ESPT Structural Primary Steel (Truss Members)
ESSS Structural Secondary Steel
ESST Structural Staircase Structures
ESTS Structural Tertiary Steel
ESWW Structural Walkway Structures
ETEF Telecom Equipment Future
ETEQ Telecom Equipment
ETFE Telecom Field equipment
EPUG Gravity Piping Modelled by Civil
ECFO Civil Foundations & Underground
ECST Civil Structures
ECGW Civil Ground Model & Earthworks
EPCI Civil Paving
EPCV Civil Fence
EPCR Civil Roads

The forms and menus should be used to create all Sites and Zones and the above
attributes set using the Attributes Forms to ensure down stream activities such as
Clash management and Drawing production work correctly.

3.5 :Revcol Attributes

To enable the control of exported data from the PDMS 3D CAD Model to Aveva
Review to function correctly all Zones must have the :Revcol attribute set.
A Project specific configuration file will define the colours to be assigned to particular
Zone content data.
The colour coding for Exported data will follow that as defined in the Shell DEP
30.10.05.11-Gen.
:Revcol Colour Description
unset N/A Excluded
ARCH 12 Mid Grey Architectural
CIVB 12 Mid Grey Civil Buildings & Sub Stations
CIVE 12 Mid Grey Civil Equipment
CIVF 15 Light Grey Civil Foundations
CIVM 3 Orange Civil Marine
CIVP 1 Black Civil Piping Contaminated
CIVS 13 Dark Grey Civil Structural
CIVT 15 Light Grey Civil Trenches
CIVW 13 Dark Grey Civil Roads, Ditches and Bunds
EASC 4 Yellow Escape , Walkways and Mechanical Lay down
ELEC 5 Bright Green Electrical
EQUI 15 Light Grey Equipment
INST 2 Red Instruments
LAND 25 Fawn Topography and Ground Model
PAVE 15 Light Grey Paving and Prepared Levels
PIPE 9 Brown Civil Piping Uncontaminated
ROAD 13 Dark Grey Roadways
STRU 12 Mid Grey Structure
SUPP 14 Blue Pipe Supports
TRAY 20 Bright Blue Cable Racking
VEHI 4 Yellow Vehicles and Personnel

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 15 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

For Piping Zones the data will be automatically generated by the Process Fluid Code
Process Fluid Code Colour Description
0A,1A,2A & AI 10 White Air
0B,1B,2B,GV & VA 1 Black Relief
0D,1D,2D & OD 1 Black Drain
0G,1G,2G & GI 3 Orange Inert Gas
0F,1F,2F,OG & OK 4 Yellow Fuel Gas / Fuel Oil
0S,1S & 2S 2 Red Steam
0P,1P,2P,ON & OW 5 Bright Green Process
0H,1H & 2H 9 Brown Hot Oil
0W,1W,2W,WD,WF & WS 14 Blue Water

3.6 Scratch Sites and Zones

Scratch Sites and Zones are temporary areas for offline study work and database
information shall be archived via DB Listings, then removed (or deleted) so as to not
impact the Review updates or Online Autoclashing. Purpose and :dcode attributes will
be left unset so as to not impact on downstream activities such as Progress monitoring
and Design Model Reviews. These items will not have the :Revcol uda set.

4. PIPING
The Layout and Piping Group are responsible for the generation of the Piping Model,
also the overall space management of the PDMS 3D CAD Model. All Pipework shall be
modelled using the graphical user interface called from the Piping Bar Menu. In-
particular all Sites Zones and Pipes must be created using the appropriate forms and
menus in order to set the correct attributes for Names, MTO and Isometric information.
There will be one PDMS Pipe per Isometric, therefore, Isodraft will not split isometrics
automatically and split ATTAS must NOT be used.
A utility exists in the Piping application Utilities>Split an Existing Pipe to aid the
breakdown of Isometrics.

4.1 Piping Zone Names

Pipework will be modelled in Zones named the same as the Site name with a suffix of
the service identifier e.g. /101-PIPE-OD , /201-PIPE-0P, /201-PIPE-0P-TRIM
Service identifiers will be in accordance with the PEFS Legend drawings 153130-000-
PR-W47-0024-03 (T-4.154.257) for RFSU1 and T-13.370.002 for RFSU2, 3 & 4.

4.2 Pipe Names

To ensure consistency and accuracy for the material transfer to VPRM the
Create>Pipe form must be used at all times. To change the name of existing Pipes the
Modify>Name>Whole form must be used.
Pipe names on the PEFS will be in-accordance with the Project Numbering Procedure.

Key:- A = Alpha Character N = Numerical Character

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 16 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

RFSU 1
NN NNN AA NNNN SG NNNNN A

Pipe Size (Imperial)

Process Area Code
Fluid Code
Sequential Number
Shell Global
Line Spec
Insulation Spec

The PDMS pipe name will be an abbreviated version of the Process Line number
as per the example shown below:
Process Line Number: 6 191 OD 0001 SG 11011 N
The PDMS Line number 101-OD1910001-01
Where 101 is the Construction Area Number
OD is the Process Fluid Code
191 is the Process Area Code
0001 is the Sequential Number
01 is the Line Suffix (Used to identify split Isometrics
I.E. Sheet Number(s) )
PDMS Line Numbering for Equipment Trim Isometrics will follow a similar convention to
the above based on Process Line Numbers identified on the Process PEFS.
RFSU 2/3/4
NNN - N A NN NNNN - NNNNN - A

Pipe Size (Metric)

Train Code
Fluid Code
Unit Number
Sequential Number
Line Spec
Insulation Spec

Process Line Number 600-0P860534-11011-N

The PDMS Line number 201-0P860534-01
Where 201 is the Construction Area Number
0 is the Train Code
P is the Process Fluid Code
86 is the Unit Number
0534 is the Line Sequence Number
Project Doc No:T-4.155.792 Rev 2
Uncontrolled if printed Page 17 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

01 is the Line Suffix (Used to identify split Isometrics i.e. Sheet

Number(s) )
PDMS Line Numbering for Equipment Trim Isometrics will follow a similar convention to
the above based on Process Line Numbers identified on the Process PEFS.
All Pipes must have a suffix therefore any Process lines that are not split into any
Isometrics will have a suffix 01.

• Line Specification
• Insulation Spec

• Line Size (e.g. 6/150)

• Construction Area Number (e.g.
101)
• Line Sequential Number (e.g.
0001)

• Service Identifier

• Iso Sheet Numbers (e.g. 01)

• System Number (e.g. 80)

4.3 Pipe Attributes

The Following Attributes must be set using the Pipe Attributes Form
Attribute Description
Temp Operating Temperature (from Line List)
:Hold TRUE (If line Contains a Hold) or FALSE
:Holddesc Short Description of Hold
:crev Current Revision
:Lpid PEFS Drawing Number
:Scrit Stress Critical
:Stress Stress Relieved
:Elrstartctp Stress Sketch Number
:Elrendctp Project Drawing Number
:pga Line List Number
:Ab-cond PCWBS Number
Project Doc No:T-4.155.792 Rev 2
Uncontrolled if printed Page 18 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

:focus Document I/D Number

Further more specific detailed listings of additional attributes and methods of working
will be defined in the PDMS Model Work Instructions Document (HOLD 3)

4.4 Isometric Data

Prior to Isometric production, the Isometric Signature Form should be populated at
Pipe level to complete the Approval, Title Block Information and Revision Status of the
Isometric as shown below:

This Form is called from Utilities>Pipework>Isometric>Signatures on the top Bar

menu when in the Piping Application.

4.5 Pipe Supports

The Pipe support application MDS Design>Multidiscipline Supports… will be used to
create all Pipe Supports, they will be of a multi discipline type i.e. the Support Frame
may support more than just Piping items

4.5.1 Pipe Support Names

All supports shall be numbered sequentially with a unique number prefixed by
Construction Area and a code representing either a pipe support, cable racking support
or HVAC ducting support e.g. 101/PS/0001. Pipe Support numbers within RFSU2
Construction Area 214 may exceed 9999, Therefore FOR THIS AREA ONLY Pipe
Support Numbering will start at 00001. Pipe Support numbers and associated
information will be allocated using a Project defined Access Database Pipe Support
Control Systems.

4.5.2 Pipe Support Drawing Data

Pipe Support Drawings will only be produced for Specials that fall outside the
parameters of the Standards. Prior to Pipe Support Drawing Production, the Pipe
Support Form should be populated at Structure level to complete the Approval, Title
Block Information and Revision Status of the Pipe Support Drawing as shown below:

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 19 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

This Form is called from Utilities>Multi Discipline Supports>Utilities>MDS Draft

Attributes on the top Bar menu when in the Multi Discipline Support Application.

4.6 Valve Data

Process valves where not identified by an Instrument/SP Tag Number shall be
numbered in accordance with the project numbering procedure. I.E HOLD4 as marked
up on the PEFS. The Valve tags are required on the Isometric drawings, therefore
MUST be added to the model using the :Part attribute on the valve.
i.e. :PART ‘HOLD4’
Extra Information Associated with Valves that need to appear as text on the isometrics
should be added using the :COMMENT Attribute.
i.e. :Comment ‘LO’

5. PROCESS AND SAFETY EQUIPMENT

The Layout and Piping Group are responsible for the generation of the Process
Equipment model and Access/maintenance volumes. In addition, they will be
responsible for modelling the Safety Equipment and Escape Route volumes in
conjunction with the Safety Group.

5.1 Equipment Zone Names

Equipment will be modelled in Zones named the same as the Site name with a suffix of
Equipment Type e.g. /101-EQUI-PROCESS

Suffix Description
PROCESS Process Equipment
SAFETY Safety Equipment
ESCAPE Escape Routes
ACCESS Lay down Areas and Access/Maintenance
Volumes
FUTURE Future Equipment

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 20 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

5.2 Equipment Names

Equipment will be named in the PDMS model in-accordance with the Project
Numbering Procedure.
Typical examples would be 19161T02 for RFSU1 and 0T-8652 for RFSU2/3&4
Nozzles shall take the equipment name with a suffix for the Nozzle tag i.e.
19161T02-N1 and 0T-8652-N1 where N1 is the nozzle tag.

5.2.1 PDMS Drawing and Obstruction Levels

Type Drawing Level Obstruction Level
Detail Representation 0 - 10 2
Overall Obstruction Volume ( If applicable) 8 - 10 2
Withdrawal Areas or Access Volumes 8 - 10 1

5.3 Equipment Datum’s

Equipment Type PDMS Origin

Vertical Origin / Horizontal Origin

Vertical Vessels Bottom Tan line / Centerline of Vessel

Horizontal Vessels Centerline of Vessel / Centerline of Fixed Saddle

Centrifugal Pumps Centerline of Pump / Centerline of Pump Discharge

Nozzle
Vertical Pumps Bottom of Base Plate / Centerline of Pump

Loading Arms Underside of Arm / Centerline of Arm

Shell / Tube Exchangers Centerline of Exchanger / Centerline of Fixed

Saddle
Plate Exchangers Underside of Base plate / Face of Inlet (Outlet )
Nozzles
Equipment Packages Underside of Skid / South West corner of Package
Skid
Compressor Packages Centerline of Shaft / Centerline of Discharge Nozzle

Gas Turbines Packages Underside of South West corner of South West

Support
Pig Receivers (Launchers ) Centerline of Equipment / Underside of Fixed
Saddle
Square Storage Tanks Underside of Tank / South West corner of Tank

Circular Storage Tanks Underside of Tank / Centerline of Tank

All Safety Cabinets and Safety Showers etc are to be located by underside of South
West Corner.

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 21 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

All Electrical / Instrument cabinets and Junction Boxes are to be located by underside
of South West corner.
Wherever possible Vendor Drawings are to be marked with the origin that we require or
the Model Datum point should match the Datum point defined by the Vendor Drawing.
These identical locations will help in relation to the more complex items such as
Compressor Skids.

6. CIVIL,STRUCTURAL & MARINE (CSM)

The Civil, Structural & Marine (CSM) Group are responsible for the generation of the
Ground Model, Civil, Structural, Marine and Architectural elements of the Model. The
detail model content will include Concrete Structures, Supports, Foundations, Piling,
Paving, Culverts, Underground Ducts, Cable Trenches & Pipework. Also Building
Structures, Earthworks/Ground Model, Roads & Fencing. Additionally Primary,
Secondary, Tertiary Structural Steelwork, Ladders, Platforms, Handrails, Staircases &
Fireproofing.

6.1 CSM Zone naming

CSM will be modelled in Zones named the same as the site name with a suffix
e.g. /101-STRC-PLTF, /101-CIVIL-PAVG & /200-CIVIL-BUIL
Where the suffix is a description of the Zone content i.e.
Suffix Description
BUIL Architectural Buildings
PLTF Structural Platform Steel
PRAK Structural Pipe Rack Steel
SUPP Structural Pipe Support Steel
GRAD Civil Grading
FENC Civil Security Fencing
ROAD Civil Roads Flat/Sloping
DRAN Civil Surface Drainage Gulley’s
PAVG Civil Primary/Secondary Paving
CULV Civil Culverts
RAMP Civil Road Ramps
FNDS Civil Equipment/Structure Foundations
TRNC Civil Trenches/Service Ducts
SLEP Civil Sleepers
PIPE Civil Underground Pipe Drainage
DMHL Civil Manholes
PITS Civil Equipment/Valve Pits
GRND Civil Ground works/Topography

6.2 Structure and Framework Names

In principle there will be one Structure (STRU) in the Design Database for each
drawing deliverable. The CSM discipline naming conventions for each STRU are based
on the Construction Area number, and a description of the Design Element.
Construction Area Numbers and categories are defined in Section 3 of this procedure.

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 22 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

6.3 Framework Attributes

The material reference attribute must be set for all Framework and Sub-framework
members.
This will be used to calculate Weight and Centre of Gravity Reports.
Use the Modify>Material Form to select and set material types i.e.

7. INSTRUMENT/ELECTRICAL/TELECOMS (EIT)
The EIT Group is responsible for the generation of the Electrical, Instrument and
Telecoms Model. The detail model content will be will include Trenching, EIT Cable
Racks, Electrical Equipment & Switchgear, LER and Switch rooms, Instrument
Junction Boxes, Equipment, Gas Detectors, Telecoms, Lighting and CCTV.

7.1 EIT Zone Naming

In general EIT Equipment and Cable Racks will modelled in Zones named the same
as the Site name with a suffix of the Purpose e.g. /100-ELEC-ELEC & /201-INST-EQUI
Where the suffix is a description of the Zone content i.e.

Suffix Description

LER Local Equipment Rooms

RACK Cable Racks

JUNCTION Junction Boxes

ALARMS Alarms

PUSH-BUTTONS Shutdown buttons

FIRE-GAS Fire and Gas Detectors

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 23 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

EQUI Equipment

MISC Miscellaneous Equipment

TELECOMS Telecoms/CCTV

TRENCH Trenches

7.2 EIT Component Naming

Generally items will be named as they are identified on the equipment list or Instrument
index or PEFS, in line with Project Numbering Procedure, exceptions will be items
which are not within the scope of these documents which will be named as follows:

7.2.1 Ladder/Cable Racks

Example AA-BBB-CCC

Duty Sequence
L1 = HV
L2 = LV Area code
J1 = Inst. Non-IS
J2 = Inst IS
W1 = Telecom

Ladder racks shall be named at pipe level, only one branch per pipe is permitted.
Branches shall be named Pipe Name-01. All branches shall begin and end with a weld.

8. PDMS MODEL STATUS

8.1 General Progress Monitoring

The PDMS Model Progress will be based on the achievement of discipline checkpoints
for each significant element within the database such as Equipment, Pipe etc.
The Status attribute (UDA :STATUS) within the model are discipline based and
described below:-
Discipline Code Description
(Model Type)
All Disciplines – A Preliminary Model and Location based on Footprint Data
Equipment (EQUI) from the Equipment List, catalogues etc.
B Updated to bid data
C Updated to Preliminary vendor data
D Updated to Status A vendor data
E Updated to Status F Vendor Data and Design Checks
complete

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 24 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

Piping A Line Input to Model (Point to Point Routing) to preliminary

( PIPE) PEFS and basic process data.

B1 Line routed head to tail to “A2” (HAZOP) PEFS, vendor bid

or catalogue data.

B2 All branches and components added ready for stress &

supports. Clash free.
AFD PEFS and E&I data included
C Routed to updated AFD PEFS where applicable, vendor
data code A, Clash & DATACON free. Ready for checking
D Pipe supports & stress complete. Clash & DATACON free,
checked.
E AFC Checked isometric issued, (Hold Free )

Pipe Supports C1 Preliminary pipe support design

(STRU)
C2 Pipe supports designed to code B2 piping, & preliminary
stress comments.

E Support designed to piping code D, stress comments,

modelled, checked, Clash free, detail drawings if required
issued AFC. All calculations finalised and model Clash free

Civil A Preliminary Underground services routings, earthworks,

(STRU) roads and paving.
B Intermediate Underground services routings,
earthworks, roads and paving layouts.
C Approved for MTO/Design (AFD)
D Approved for Construction – Clash Free ( with holds)
E All Civil and underground services elements modelled
to AFC, Clash Free. All layouts, underground services
isometrics and detail drawings approved for
Construction (no Holds)
Civil/Structural A Members positioned to preliminary layout
(STRU)
B Members Positioned to intermediate layout
C Approved for MTO/Design (AFD)
D Approved for Construction – Clash Free ( with holds)
E Approved for Construction – Clash Free

E & I - Racking A Preliminary rack route modelled

(PIPE)
C Rack Modelled to AFD Status
E Rack Modelled to AFC, Clash Free,

ARCH A Initial Model of External Envelopes, External Doors, Panels

(STRU) and Hatches. Initial Modelling of Internal room divisions
C Model update to AFD Status including service/structural
Penetrations
Project Doc No:T-4.155.792 Rev 2
Uncontrolled if printed Page 25 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

E AFC Model Clash Free

Safety A Escape Routes modelled for Preliminary Platform Layouts

(STRU)
C Escape Routes updated for AFD layouts
E Escape Routes modelled for AFC Layouts, Clash Free
HVAC A Initial Modelling of HVAC Equipment to Preliminary Data
(EQUI)
C Updated to selected vendor Data
E Final Vendor Data, Clash Free
HVAC A Initial Modelling of primary systems for Space Reservation
Ducting and Inline
Equipment
C Input to AFD D&ID’s
E Final vendor Data, AFC D&ID’s Clash Free

8.2 Clash Check of the PDMS model

8.2.1 Responsibilities
The Layout and Piping Group have overall responsibility for the Space management of
the PDMS Model
It is the PDMS CAD Coordinators responsibility to set-up and maintain the Formal
Clash Management Database (VPD Clash Manager). The database shall be updated
at regular intervals and in accordance with project milestones.
To ensure that all clashes are detected and rectified as early in the design process as
possible, Clash checking must be considered as an ongoing part of the design process.
Typically Online Clash checks should be run individually on significant Elements of the
Model when ever they have been modelled, modified or moved i.e. Equipment, Pipes,
Frameworks
It is the Lead Discipline Engineers responsibility to ensure that Designers are running
Interactive Clash Checks as applicable to ensure a Clash free model. In addition, it is
the Lead Engineers responsibility to ensure that Nominated Designers/Engineers
(Clash Coordinators) clear/approve all clashes within the Formal Clash Management
Database.
Its is the Designers responsibility to Run Clash checks regularly using the On-line
Clash functionality within the Design Model.
In addition, Lead Engineers shall ensure that all design items forming part of an AFD or
AFC issue, such as Structural Layouts, Piping Isometrics etc. must be clash free before
the drawings are issued.
The clearance and/or approval of clashes shall be the responsibility of the offending
discipline in accordance with the matrix below:

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 26 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

Clash Discipline
With Elec. HVAC Arch. Piping Struc/ Safety Inst. Tele Equi Supp.
Civil
Elec Elec Elec Elec Piping Elec Elec Elec Elec Piping Supp
HVAC Elec HVAC HVAC Piping HVAC HVAC Inst Tele Piping Supp
Arch. Elec HVAC Arch Piping Struc Safety Inst Tele Piping Supp
Piping Piping Piping Piping Piping Piping* Piping Piping Piping Piping Supp
Struct/ Elec HVAC Struc Piping Struc Struc Inst Tele Piping Supp
Civil
Safety Elec HVAC Safety Piping Struc Safety Inst Tele Piping Supp
Inst Elec Inst Inst Piping Inst Inst Inst Inst Piping Supp
Tele. Elec Tele Tele Piping Tele Tele Inst Tele Piping Supp
Equi. Piping Piping Piping Piping Piping Piping Piping Piping Piping Supp
Supp. Supp Supp Supp Supp Supp Supp Supp Supp Supp Supp

For example a clash between Structural and Piping must be actioned by the discipline
in the box marked * in the matrix i.e. Piping.

8.2.2 Formal Clash Management

Designers shall use on-line clash management (as applicable) to ensure the model is
Clash Free.
However, should some clashes not be resolved in this way they will be detected in the
Formal Clash Runs, in the Clash Management Database.
The Clash Manager is called from inside PDMS via the menu below:
Utilities>Clash Manager Start Up
Clashes identified within Clash Manager will be resolved by the relevant discipline in
accordance with the matrix above. Clashes that are difficult to resolve and that need
more work in the model must be flagged as ‘PENDING’ with a relevant comment until a
solution is identified/actioned. Clashes that will be solved by further development of the
Model i.e. Floor penetrations etc. must be flagged ‘CONDITIONAL’ with an appropriate
comment. Clashes that are acceptable from a design or modelling perspective such as
Soft – Soft clashes can be ‘APPROVED’ with an appropriate comment.
It should be noted that the Username and Date is recorded when any Clash is flagged
APPROVED, CONDITIONAL or PENDING
The Clash management Database will be updated by the CAD Coordinator on a
daily/weekly basis.

9. DRAWING PRODUCTION

9.1 Draft
The PDMS CAD Coordinator will create one Draft Drawing Database and the
necessary Department and Registry hierarchy for every Design Database/Site.
The PDMS 3D CAD Model will be used to generate all discipline deliverable drawing
backgrounds with database generated dimensioning and labelling as appropriate.
Then, if required, export into Autocad can be carried out providing that any further
detailing does not require model input. If this is the case, Disciplines are responsible to
Project Doc No:T-4.155.792 Rev 2
Uncontrolled if printed Page 27 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

ensure that appropriate volumes are retrospectively generated in the PDMS 3D CAD
Model.
All drawings shall be produced using the drawing templates provided by using the
CREATE>DRAWING>FROM TEMPLATE Option from the ‘Draft General’ bar menu.
Drawings will be named in accordance with the Project SPT Numbering Procedure on
the Create Drawing Form i.e.

All drawings will use the appropriate drawing template selected from the Drawings and
Sheet Templates form i.e.

The template will create the drawing with the default Rules Library. Any specific
drawing rules shall be created using Local Rules

9.2 Drawing Files

PDMS Plot files, DXF and PDF Files are to be stored on the Project Drive i.e.
P:\153130 – Shell Pearl GTL – Tankage set up\<Discipline>\PDMS\Drawings\<type of
drawing>
e.g. A typical Piping General Arrangement drawing would be stored in

P:\153130 – Shell Pearl GTL – Tankage set up\PIPING\PDMS\Drawings\PGA

Drawing File names are dependent on the Drawing Number and will take the format:

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 28 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

153130-000-PI-W53-0001-01-A.plt
Document File
Number Extension
Document
Revision
All Drawings issued from the PDMS model must have an AutoCAD (DXF) format
drawing file to be stored in PDOCS in accordance with project procedures.
DXF format files are generated using the DRAFT>UTILITIES>DXF CE>STANDARD
form and the file should be stored on the project drive under the respective discipline
folders until they are transferred into PDOCS.
An Adobe (PDF) Format file of the signed original Document also needs to be
generated to accompany the Electronic (DXF) master file.

9.2.1 Scale Bars

All Layout drawings will have a scale bar added. Symbol References (TMRF) as shown
below:
SCALE-1:25 for 1/25
SCALE-1:100 for 1/100
Etc.

9.3 Piping Isometrics

9.3.1 Stress Isometrics

Stress Isometrics will be generated from the DESIGN module using the
UTILITIES>CREATE ISOMETRIC
Option from the Piping Bar Menu, then select the isometric type.
Stress – for Stress Prints

9.3.2 Fabrication Isometrics

Fabrication Isometrics will be generated from the DESIGN module using the
UTILITIES>CREATE ISOMETRIC
Option from the Piping Bar Menu, then select the isometric type.
Internal – for adhoc/uncontrolled plots
Check – For Check Prints
Final – For final Prints
Note - Always produce an MTO with the production of a Final Isometric.

10. DESIGN REVIEWS

The Multi-Discipline generated PDMS 3D Model will be used under the co-ordination of
Project Engineering to enable the Design teams to carry out formal Engineering Design
Reviews at 30%, 60% and 90% completion status as indicated at the key stages on the

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 29 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

project plan. The detail breakdown of the Design Reviews will be in accordance with
Shell DEP 30.10.05.11-Gen and co-ordinated through Project Engineering.

11. AVEVA REVIEW

For full access to the complete Multi-Discipline 3D CAD Model without having the
background PDMS knowledge, full use of the AVEVA Review software will be utilised.
This will enable all relevant personnel with basic Aveva Review training to access the
current 3D CAD Model. This program uses a download of the full PDMS model which
will be updated on a weekly basis. (or sooner if required)
The files will be located on the following network drive :-
P:\153130 - Shell Pearl GTL - Tankage set up\COMMON\Review\rfsu1\SPT###
Where ### is the sequential run number i.e. 024
Filenames SPT024-30-8-2007.rvm

Project Model
Identifier File
Run Run
Number Date
SPT024-30-8-2007.rvs

Project Status
Identifier File
Run Run
Number Date

P:\153130 - Shell Pearl GTL - Tankage set up\COMMON\Review\rfsu2-4\SPT024

Filenames SPT024-30-8-2007.rvm

Project Model
Identifier File
Run Run
Number Date
SPT024-30-8-2007.rvs

Project Status
Identifier File
Run Run
Number Date

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 30 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

12. SOFTWARE INTERFACE/SUPPORT

12.1 Applications
PDMS Utilises a suit of Integrated Multi Discipline Applications and “Add On”
Applications. (MDS, Clash Manager etc)
Any problems with the Standard/Developed Applications will be brought to the attention
of the PDMS CAD Coordinator or his deputy. On no account will Users directly contact
Software Suppliers to report problems. This is due to strict procedures that are in place
between CB&I UK Limited and Software Suppliers.
Any PDMS Interface Program / Application problems will be discussed with the PDMS
CAD Coordinator or his deputy and investigated to assess “Fit for Purpose”.
On no account will Users contact or arrange demonstration with any outside Software
Suppliers without the prior consent of the CAD Section Head.

13. JETSTREAM NAVISWORKS

This utilises a free downloadable Multi Discipline 3D CAD Model viewer which can be
used to view and move around the PDMS Model using a few easy to use commands.
This program uses a converted version of the regularly updated Aveva Review files as
indicated in Section 11.
Unlike Aveva Review this is a viewer only and no measuring or tagging facilities exist
using this program.
Please contact the PDMS CAD Coordinator to install this Software.
The files will be updated at the same time as the Aveva Review files on a weekly basis.
(or sooner if required)
The files will be located on the following network drive :-
P:\153130 - Shell Pearl GTL - Tankage set up\COMMON\Navisworks\rfsu1
Filename SPT024-30-8-2007.nwd

Project Navisworks File

Identifier extension
Run Run
Number Date
P:\153130 - Shell Pearl GTL - Tankage set up\COMMON\Navisworks\rfsu2-4
Filename SPT024-30-8-2007.nwd

Project Navisworks File

Identifier extension
Run Run
Number Date

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 31 of 32
 Shell Pearl GTL Tankage Project 153130
PDMS IMPLEMENTATION PROCEDURE
153130-000-PI-P18-0003 Revision 2

14. PMC DATA TRANSFER

The Pearl GTL Project requires the ability to transfer PDMS 3D CAD Model data to and
from the PMC. The Aveva Solutions Software Implant and Explant will be used to either
export PDMS 3D Model data into .dgn format files or import PDMS data from .dgn
format files using generated import macros.
Imported data will be created in individual PDMS databases for control purposes and
will be Read Only.
Exported data will be generated by the PDMS CAD Coordinator or his deputy with
guidance from the disciplines involved. Generated data will be passed to Project
Engineering for distribution to the PMC.
The colour coding for Exported data will be in accordance with those defined in the
Shell DEP 30.10.05.11-Gen
The Project also requires that specific Navisworks file data will be uploaded on a
regular basis into the PMC “NEXUS” System.

Project Doc No:T-4.155.792 Rev 2

Uncontrolled if printed Page 32 of 32