GP 01-01-03S - Version 2.0.0 January 2013

Upstream CAD Requirements
Drawings, Data, and System

(UN Supplement)
GP 01-01-03S
Scope
This Global Practice Supplement (GPS) specifies additional Upstream Nigeria (UN) detail requirements
for the preparation and content of Computer Assisted Design Drafting (CAD) drawings and the CAD
system for use within Upstream onshore and offshore facilities and other Upstream process and industrial
applications.
This GPS includes UN requirements specifically for Process Flow Diagrams (PFD), Utility Flow
Diagrams (UFD), Piping and Instrumentation Diagrams (P&ID’s), plot plans, electrical schematics, 3-D
Models, control drawings, Materials of Construction (MOC), piping drawings, instrumentation drawings,
and other drawings.
GP 01-01-03S Upstream CAD Requirements Drawings, Data, and System (UN Supplement) January 2013
Table of Contents
1 Required references.............................................................................................. 7
1.1 Global Practices – ExxonMobil Engineering Practices ................................. 7
2 General CAD Systsem, Tag-centric Data, and Drawing Instructions................ 8
2.1 General......................................................................................................... 8
2.2 [Modification] CAD System ........................................................................... 8
2.3 [Addition] CAD Drawings .............................................................................. 8
3 Identification and Numbering ............................................................................... 8
4 FEED Contractor Deliverables ............................................................................. 8
5 EPC Contractor Deliverables ............................................................................... 8
6 Process Flow Diagrams (PFDs) ........................................................................... 9
7 Utility Flow Diagrams (UFDs) ............................................................................... 9
8 Piping and Instrumentation Diagrams (P&IDs) ................................................... 9
9 Line List ................................................................................................................. 9
Appendix A: Typical Representation of Instrumentation and Control Equipment

on P&IDs ................................................................................................................ 9
Appendix B: CAD Deliverables ................................................................................... 9
Appendix C: Checklist for Project Specifications ..................................................... 9
[Addition] Appendix-D: Detail Drafting Standard Process Description.................... 10
D-1. Drafting Standard Process Description ............................................................ 10

D-1.1. Drawing Number......................................................................................... 10
D-1.2. Border Sheet .............................................................................................. 11
D-1.3. Title block contents ..................................................................................... 11
D-1.4. Title Block ................................................................................................... 12
D-1.5. Drawing Units ............................................................................................. 18
D-1.6. Drawing Size .............................................................................................. 18
D-1.7. Drawing Scale ............................................................................................ 18
Upstream For ExxonMobil Use Only
Page 2 of 76 Upstream Nigeria Version 2.0.0

D-1.8. Drawing Orientation .................................................................................... 19

D-1.9. Abbreviations .............................................................................................. 19
D-1.10. Annotations ......................................................................................... 21
D-1.11. Text Size and Font Styles ................................................................... 21
D-1.12. Layers ................................................................................................. 22
D-1.13. Line Types, Colors and Line weight .................................................... 25
D-1.14. Hatch Patterns .................................................................................... 25
D-1.15. Symbol and Legend Sheet .................................................................. 26
D-1.16. Holds ................................................................................................... 26
D-1.17. Reference Drawings............................................................................ 26
D-1.18. Continuation Drawings ........................................................................ 27
D-1.19. As-Built Drawings ................................................................................ 28
D-1.20. Post IFC Drawings .............................................................................. 28
D-1.21. Demolition Drawings ........................................................................... 28
D-1.22. Redrawing in AutoCAD ....................................................................... 28
D-1.23. Revision Functions .............................................................................. 29
D-1.24. As-Built Redline Markups .................................................................... 30
D-2. Software programs ..................................................................................... 31
D-2.1. Auto LISP Routines .................................................................................... 31
D-2.2. Blocks and Attributes .................................................................................. 31
D-3. Transferring Drawing Files ......................................................................... 32
D-3.1. Drawing Submission ................................................................................... 32
D-3.2. Verification .................................................................................................. 32
[Addition] Appendix – E: PDMS Implementation Procedure................................... 33
E-1.0 Purpose ..................................................................................................... 33

E-1.1. PDMS Software .......................................................................................... 33
E-1.2. Project Initialization..................................................................................... 33
E-1.3. Area classification – Facility and Sub-facility .............................................. 34
E-1.4. Platform / Plant Model Datum ..................................................................... 35
E-1.5. Project Directory Setup............................................................................... 35
E-1.6. File naming conventions - PDMS user files ................................................ 36
E-1.6.1. Project Files ........................................................................................ 36
E-1.6.2. Program defined files .......................................................................... 37

E-1.7. Creation of the PDMS Project .................................................................... 37

E-1.8. EUN Corporate Catalog Databases............................................................ 37
E-1.9. Project Team and Databases ..................................................................... 37
E-1.9.1. Design and drawing databases ........................................................... 38
E-1.9.2. Other databases.................................................................................. 39
E-1.10. Database numbers .............................................................................. 39
E-1.11. Multiple databases .............................................................................. 39
E-1.12. PDMS User Names ............................................................................. 39
E-1.13. Extract Databases ............................................................................... 40
E-2.0 Database Maintenance............................................................................... 40
E-2.1. Database Integrity Checking ...................................................................... 41
E-2.2. Reconfiguration .......................................................................................... 41
E-2.3. Database Stamping and Merging ............................................................... 42
E-3.0 EUN Catalogs and Specifications ............................................................... 42
E-3.1. EVAR settings ............................................................................................ 43
E-3.2. Piping specifications and catalogs .............................................................. 43
E-3.3. Structural specifications and catalogs ........................................................ 45
E-3.4. Cable Tray specifications and catalogs ...................................................... 46
E-3.5. HVAC Tray specifications and catalogs...................................................... 46
E-4.0 PDMS Modeling.......................................................................................... 46
E-4.1. Discipline codes.......................................................................................... 47
E-4.2. Naming conventions ................................................................................... 47
E-4.2.1. SITE naming ....................................................................................... 47
E-4.2.2. ZONE naming ..................................................................................... 47
E-4.3. Mechanical Equipments ............................................................................. 49
E-4.4. Piping ......................................................................................................... 50
E-4.5. Civil / Structural .......................................................................................... 51
E-4.5.1. Structural model content: .................................................................... 52
E-4.5.2. Civil model content: ............................................................................. 52
E-4.5.3. Abbreviations ...................................................................................... 52
E-4.5.4. Primitive elements ............................................................................... 53
E-4.5.5. PANEL elements ................................................................................. 53
E-4.5.6. SCTN elements ................................................................................... 54
E-4.5.7. Steelwork connectivity......................................................................... 54

E-4.5.8. Columns .............................................................................................. 54

E-4.5.9. Levels (Floors and Roofs) ................................................................... 54
E-4.5.10. Gusset Plates ...................................................................................... 54
E-4.5.11. General Hierarchy ............................................................................... 54
E-4.5.12. Material take off, weight and center of gravity ..................................... 57
E-4.6. Civil............................................................................................................. 58
E-4.7. Architectural ............................................................................................... 58
E-4.8. HVAC ......................................................................................................... 58
E-4.9. Electrical and Instrumentation .................................................................... 58
E-4.10. Multi-discipline Service supports ......................................................... 61
E-4.11. Safety equipments .............................................................................. 61
E-4.12. Reserve Volumes ................................................................................ 62
E-5.0 Quality Management .................................................................................. 63
E-5.1. PDMS Specification check ......................................................................... 63
E-5.2. Data consistency check .............................................................................. 63
E-5.3. Interference check ...................................................................................... 64
E-5.4. Design Check ............................................................................................. 64
E-5.5. Process Parameters ................................................................................... 65
E-5.6. Model Status Register ................................................................................ 65
E-6.0 Model Review ............................................................................................. 66
E-6.1. Objective .................................................................................................... 66
E-6.2. Responsibilities........................................................................................... 66
E-6.2.1. COMPANY Project Team.................................................................... 66
E-6.2.2. Project Engineer.................................................................................. 66
E-6.2.3. Design Leads ...................................................................................... 66
E-6.2.4. Review Team Leader .......................................................................... 66
E-6.2.5. Model Operator ................................................................................... 66
E-6.3. Scope of Model Review .............................................................................. 67
E-6.4. Team Composition ..................................................................................... 68
E-6.5. Handling comments .................................................................................... 69
E-6.6. Internal model reviews ................................................................................ 70
E-7.0 Production of Deliverables - 2D Drafting .................................................... 71
E-7.1. Isometric Production ................................................................................... 71
E-7.2. PDMS Fonts in AutoCAD ........................................................................... 72

E-7.3. PDMS Reports............................................................................................ 72

E-7.4. Piping Material Take-Off ............................................................................. 72
E-7.5. Weight and Center of Gravity ..................................................................... 73
E-8.0 PDMS Global .............................................................................................. 74
E-9.0 Model data transfer..................................................................................... 75
E-10.0Computer Hardware and Data Backup ....................................................... 75
Record of Change ................................................................................................. 76

1 Required references
1.1 Global Practices – ExxonMobil Engineering Practices
Table 1.1 – References
GP 12-01-01S Upstream Numbering System for Project Documents Supplements
[Modification] ExxonMobil Upstream Engineering Drawing Standards

Table 1.2 – Standard Drawing Border Sheets
Upstream Border Sheet Drawings Standard Drawing Border Sheet Drawings
A1 - Imperial Standard "A1" Size Border Sheet - (Imperial Units)
A1-Metric Standard "A1" Size Border Sheet - (Metric Units)
A3-Metric Standard "A3" Size Border Sheet - (Metric Units)
A3-Metric (ILD) Standard "A3" Size Border Sheet for Instrument Loop
Diagram (ILD) - (Metric Units)
A3-Metric - Isometric Standard "A3" Size Border Sheet for Piping Isometric
(Metric Units)
Upstream PIDs - Symbols Typical Piping and Instrumentation Diagrams -

Standard Symbols and Nomenclature
NG00-EP-PDSYM-10001 - 10004 Piping and Instrumentation Diagram Symbols and Legend
(4 Sheets).

2 General CAD Systsem, Tag-centric Data, and Drawing

Instructions
2.1 General
[No Additions]
2.2 [Modification] CAD System

All 2-D drawings shall be produced using AutoCAD, and 3-D Models using PDMS (Plant Design and
Management System) versions specified in Project Specifications.
Contractor(s) is required to use the above mentioned CAD Systems with best practices for the most cost-
effective and schedule-efficient execution of the project.
2.3 [Addition] CAD Drawings

The minimum size for all orthographic drawings shall be ISO "A1" size sheets, 841 mm x 594 mm (33.1
in. x 23.4 in.), that shall produce completely legible drawings when reduced to ISO "A3" size sheets, 420
mm x 297 mm (16.54 in. x 11.69 in.). Company will supply default border sheets. Deviation from the
default border sheets will require Company approval.
Refer to Section D-1.10 of Appendix D for recommended Text Size and Font Styles.
All XREF’s shall be bound.
3 Identification and Numbering

[No Additions]
4 FEED Contractor Deliverables

[No Additions]
5 EPC Contractor Deliverables

[No Additions]

6 Process Flow Diagrams (PFDs)

[No Additions]
7 Utility Flow Diagrams (UFDs)

[No Changes]
8 Piping and Instrumentation Diagrams (P&IDs)

[No Changes]
9 Line List
[No Changes]
Appendix A: Typical Representation of Instrumentation and

Control Equipment on P&IDs
[No Changes]
Appendix B: CAD Deliverables

[No Changes]
Appendix C: Checklist for Project Specifications

[No Changes]

[Addition] Appendix-D: Detail Drafting Standard Process

Description
D-1. Drafting Standard Process Description

Drawing specifications in the Oil and Gas industry are many and vary. To keep Company drawings
consistent with industry and Upstream Nigeria requirements, this section details the drafting standards
and guidelines to achieve this goal.
D-1.1. Drawing Number

GP 12-01-01 (Upstream Numbering System for Project Technical Documents) and its supplement
GP 12-01-01S should be referred to for new drawing numbers.
Drawing sequence numbers shall be assigned by company, (The suggestion is that you contact the UN
Information Management Group through the project DCC for the sequence numbers).
Discipline leads shall determine the drawing numbers for all new drawings and communicate this to the
drawing creator or contractor.
All drawings shall be numbered in the title block accordingly. Refer to section D-1.3 & D-1.4 for details
on title block.
Drawings being revised from existing drawings maintain the same drawing number.
The drawing electronic file name shall be the same as the drawing number.
The numbering system shall be used on all technical documentation such as drawings, documents,
calculations, datasheets, design philosophies, technical manuals, lists and specifications etc.

D-1.2. Border Sheet

Standard border sheet must be obtained from supplied Design Drafting Standards package directly from
the company CAD Group.
Drafting personnel and the drawing owners are required to complete drawing border sheet content
consistently on drawings to ensure:
• Drawings should show the north arrow on the top left hand corner of the border sheet.
• Facility names/codes are shown on the top right corner of the border sheet.
Figure 1.1 - Typical Border Sheet
D-1.3. Title block contents

Drafting personnel and drawing owners must ensure that all engineering drawing’s title block includes:
Drawing title (ref section D-1.4)
Drawing number (ref section D-1.1)
Revision number (ref section D-1.23)
Contractor name, logo and address.
Drawing scale (ref section D-1.7)
Note: Drafting personnel should not explode or alter the given title block attributes.

D-1.4. Title Block

Drafting personnel shall use standard language in the three line drawing title that appears in the title block
of all engineering drawings. The drawing title shall not be changed during the normal drawing life cycle.
Drafting personnel must ensure that:
All three lines of the standard drawing title are complete to a maximum of 50 characters and spacers per
title line.
Uppercase letters are used in all words, abbreviations and acronyms in the drawing title.
Standard abbreviations are only used if necessary. Refer to table D-1.6
Figure 1.2 - Drawing Title Block
Title 1 – Drawing Type

The drawing type description is obtained by determining the drawing type. Drafting personnel must use
Company approved drawing type descriptions. Refer tables 3.1, 3.2 & 3.3 for some standard descriptions.
Title 2 – Area or Systems Description

The area or systems description accurately describes the area or system, e.g., legal descriptions,
equipment descriptions and building description.
Title 3 – Additional Description

Shall be used for additional information as required e.g. sheet numbers.

Table D-1.3 - Civil / Structural drawing descriptions
Title Optional Prefix Description (Mandatory)

AREA FIELD MAP
CIVIL KEY PLAN
GRADING
ROAD CROSS DETAILS
SUBGRADE CUT AND FILL
CLEARING AND GRUBBING
DRILLING RIG GRADING
FOUNDATION LOCATION PLAN
GRADING
SUBGRADE CUT AND FILL
GRADING PROFILE
GRADING
SECTIONS
ROAD CROSS
CABLE TRAY SUPPORT
CHAIN LINK FENCE
FRAMING
INSTALLATION
PIPE SUPPORT
PIPELINE SUPPORT
PLATFORM DETAILS
STANDARD
TYPICAL
ANCHOR BLOCK
FOUNDATION
PILING
HVAC
CABLE TRAY SUPPORT
FRAMING
PIPE SUPPORT
PIPELINE SUPPORT ELEVATIONS
PLATFORM
BUILDING
HVAC
CABLE TRAY SUPPORT
CHAIN LINK FENCE
FRAMING
PIPE SUPPORT
PIPELINE SUPPORT
PIPERACK FRAMING
PLAN
PLATFORM
FOUNDATION
PILING
FLOOR
BUILDING
HVAC
ROOF FRAMING
SKID FRAMING
CABLE TRAY SUPPORT
FRAMING
PIPE SUPPORT SECTIONS
PIPELINE SUPPORT
PLATFORM

Table D-1.4 - Electrical & Instrumentation drawing descriptions

INSTRUMENTATION DETAILS
ANALOG MULTIPLEXER
AREA CLASSIFICATION
CONTROL SYSTEM ARCHITECTURE
LOOP DIAGRAMS
EMERGENCY SHUTDOWN SCHEMATICS
FIRE ALARM SYSTEM
FIBRE OPTIC SYSTEM
HIGH SPEED COUNTER INPUTS
SEQUENCING STATUS
SPECIAL CONTROL INPUTS
SPECIAL CONTROL OUTPUTS
THERMOCOUPLE INPUTS
THREE-LINE AC SCHEMATICS
CATHODIC PROTECTION DETAILS
CATHODIC PROTECTION PLAN
CATHODIC PROTECTION SCHEMATICS
INSTRUMENT LOOP DIAGRAMS
ELECTRICAL VENDOR DRAWING
INSTRUMENTATION VENDOR DRAWING
ANALOG INPUTS
ANALOG OUTPUTS
CONTROL SCHEMATICS
DISCRETE INPUTS
VOLTAGE / CURRENT RANGE
DISCRETE OUTPUTS
ISOLATED OUTPUTS
MOTOR CONTROL SCHEMATICS
SINGLE LINE DIAGRAM
COMMUNICATION
CONTROL SYSTEM BLOCK DIAGRAM
ELECTRICAL
CONTROL SCHEMATICS
HEAT TRACING ISOMETRIC
LAYOUT
COVER SHEET
DRAWING INDEX
KEYPLAN
ELECTRICAL LEGEND
INSTRUMENTATION LAYOUT
GROUNDNG LAYOUT
CABLE TRAY LAYOUT
CABLE TRAY ELEVATIONS
CABLE TRAY SUPPORT
CONTROL
HEAT TRACING
INSTALLATION DETAILS
INSTRUMENTATION
STANDARD
TYPICAL
FIRE ALARM
SYSTEM
UPS
CONTACTOR PANEL
INTERCONNECTION
JUNCTION BOX
WIRING DIAGRAM
PANEL
TERMINAL BOX
TRANSMITTER
ALARM AND EMERGENCY PROCESS SHUTDOWN KEY
CATHODIC PROTECTION DETAILS
CATHODIC PROTECTION PLAN
CATHODIC PROTECTION SCHEMATICS

Table D1.5 - Mechanical / Piping / Process drawing descriptions

COVER SHEET
KEYPLAN
MECHANICAL
DRAWING INDEX
AREA FIELD MAP
BLOCK FLOW DIAGRAM
P&ID LEGEND
PIPING AND INSTRUMENTATION DIAGRAM
PROCESS FLOW DIAGRAM
HEAT AND MATERIAL BALANCES
TIE-IN LIST
SPECIALITY ITEM LIST
ELECTRICAL CONTROL ALARM AND STATUS
PRESURE VESSEL DETAILS
STORAGE TANK DETAILS
HEAT EXCHANGER DETAILS
HEATER DETAILS
FIRE SYSTEM
PIPING ARRANGEMENT
PIPING SECTIONS
WELLHEAD DETAILS
DRILLING DETAILS
MATERIAL HANDLING DETAILS
PUMP AND COMPRESSOR SPECIFICATIONS
MATERIAL LIST
PROCESSING EQUIPMENT DETAILS
FITTING DETAILS
VALVES DETAILS
MECHANICAL VENDOR DRAWING
EQUIPMENT LOCATION
INSTALLATION
OVERALL PLOT
PLOT
SITE PLAN
HVAC
HEAT TRACING
PIPING
UNDER GROUND PIPING
COIL
HEAT TRACING
SCHEDULE
LINE
PIPELINE
HVAC
MEASUREMENT FLOW SCHEMATICS
METERING
HVAC
HEAT TRACING
INSTALLATION
PIPING
STANDARD
DETAILS
TYPICAL
BEND
PIPELINE
S-BEND
CROSSING


HEAT TRACING
ELEVATIONS
PIPING
HEAT TRACING
LAYOUT
PIPING
PIPE ANCHOR
PIPE SHOE
PIPE GUIDE
PIPE RESTRAINT
DUMMY SUPPORT
BASE SUPPORT DETAILS
HANGER ROD
STIFFENER PLATE
TRUNNION SUPPORT
SLIDE PLATE
SPRING SUPPORT
EQUIPMENT LOCATION
INSTALLATION
OVERALL PLOT
PLOT
SITE PLAN
HVAC
HEAT TRACING
PIPING
UNDER GROUND PIPING
COIL
HEAT TRACING
SCHEDULE
LINE
PIPELINE
HVAC
MEASUREMENT FLOW SCHEMATICS
METERING
HVAC
HEAT TRACING
INSTALLATION
PIPING
STANDARD
DETAILS
TYPICAL
BEND
PIPELINE
S-BEND
CROSSING
HEAT TRACING
ELEVATIONS
PIPING
HEAT TRACING
LAYOUT
PIPING
PIPE ANCHOR
PIPE SHOE
PIPE GUIDE
PIPE RESTRAINT
DUMMY SUPPORT
BASE SUPPORT DETAILS
HANGER ROD
STIFFENER PLATE
TRUNNION SUPPORT
SLIDE PLATE
SPRING SUPPORT

Due to the limited amount of space in drawing title blocks, drafting personnel should use abbreviations
and acronyms to include as much pertinent information as possible.
The following list (table D-1.6) of standard abbreviations shall be used in engineering drawing titles.
Table D-1.6 - Drawing title standard abbreviations
Abbreviation Description Abbreviation Description

& and LAB laboratory
lease automatic custody
A/G above ground LACT
transfer
ANN annunciator LH left hand
ANT antennae LPG liquefied petroleum gas
AUX auxiliary LTG lighting
ASSY assembly LVP low vapor pressure
BAT battery MCC motor control center
BFW boiler feed water MISC miscellaneous
BLDG building MOV motor operated valve
BS&W basic sediment and water MUX multiplexer
CDP central distribution panel NE north east
CNTL control NGL natural gas liquid
CNTL PNL control panel NPS nominal pipe size
COMP compressor NW north west
COND condensate P/L pipeline
CPF central processing facility PDC power distribution centre
programmable logic
CPU central processing unit PLC
controller
CRT cathode ray tube PNL panel
CS carbon steel PSD pressure shut down
CSS cyclic steam simulation PWR power
restricted development
DCS distributed control system RDA
area
DEHY dehydration REGEN regeneration
DEM demolition RH right hand
resistance temperature
DIST distribution RTD
device
ELEC electrical RTU remote terminal unit
ESD emergency shutdown SAT satellite
supervisory control and
ESP electrical submersible pump SCADA
data acquisition
FSU froth settling unit SCH schedule
FWKO free water knock out drum SE south east
GEN generator SEP separator
GND ground SRU solvent recovery unit
HP horse power STN station
HT heat tracing SUB substation
HTR heater SW south west
heating ventilating and air
HVAC SWGR switchgear
conditioning
I/F interface SYS system
I/O input/output TB terminal box
IDR inter discipline review TG turbine generator
IFA issued for approval TNS transformer
IFC issued for construction TOG top of grating
IFD issued for demolition TOS top of steel
IFE issued for engineering TWP township
IFR issued for review TX transmitter


IFS issued for survey U/G underground
uninterruptible power
IGF induced gas flotation UPS
supply
INFRA infrastructure VAC voltage alternating current
INJ injection VGC vent gas compressor
INT integral VSD variable speed drive
INV inverter WAC weak acid caution
JB junction box
D-1.5. Drawing Units

Imperial unit system shall be used for drafting and dimensioning unless otherwise specified.
Architectural unit should be used for all linear measurements and decimal degree for angular
measurement in AutoCAD.
D-1.6. Drawing Size

ISO A1 shall be used for all scaled drawings. ISO A3 sheets shall only be used if the plot of drawing is
completely legible or in the case of industry standard acceptance i.e. Piping isometrics, Loop diagrams
etc.
Company will supply standard border sheets for ISO A1 and ISO A3 drawings. Deviation from these
default border sheets will require Company approval.
D-1.7. Drawing Scale

Drawing scales are used to show information as clearly as possible at the required level of detail. Specific
drawing types use specific scales consistently. Drawing scales shall be chosen that reflect standard
industry usage e.g. piping plot 3/8” = 1’-0”.
All details and layouts shall be drawn to scale 1:1 using model space mode. Two acceptable methods can
be used for sizing the border.
Using only Model space for drawing details and drawing border etc. The border is scaled up to the size of
drawing to be plotted i.e. if the drawing is to be plotted to a scale of 1:200, the drawing border should be
scaled up 200 times.
Using AutoCAD Paper space and model space methods. Paper space should be used for drawing border
and title blocks and Model space for drawing details.
Note: However, where multiple scales are required in a drawing, paper space should be used.

Table D-1.7 – Examples of standard drawing scales
Imperial units Metric Units

1/8” = 1’-0” 1=5
3/8” = 1’-0” 1 = 10
1/16” = 1’-0” 1 = 50
1/32” = 1’-0” 1 = 100
1/64” = 1’-0” 1 = 200
1” = 1’-0” 1 = 500
3” = 1’-0” 1 = 1000
Drawing scales shall be shown in the space provided in the title block. If more than one scale is used in a
single drawing, it should be shown directly below each detail/plan/section and shown “NOTED” in the
title block.
Schematic drawings need not be drawn to a scale. The finished drawing shall be on smallest size drawing
that is clearly legible. In the title block it should be noted as “NTS” for scale.
A graphic scale bar shall be provided on all scaled drawings to allow scale measurements on reduced
size prints as shown below.
Figure 1.3 - A typical graphic scale bar
D-1.8. Drawing Orientation

All plan drawings shall have a North Arrow symbol, which should be located at the top left corner of the
sheet.
All Plan drawings for the project shall normally be oriented with Plant/Platform North towards the top of
the sheet. Where necessary due to drawing arrangement considerations, Platform North may be towards
the left side of the sheet, but shall be common on all major plan drawings.
D-1.9. Abbreviations
In order to save time and drawing space, words may be abbreviated, except in cases where confusion or
ambiguity might occur. Only abbreviations listed in table 4.9 herein or in ASME Y1.1 shall be permitted.
Title blocks shall not contain abbreviations except in cases where lack of space precludes spelling out the
entire word. Refer to table 4.6 for title block abbreviations.

Table D-1.8 – Some standard abbreviations

AB Anchor bolt F Fahrenheit
American Institute of Steel Construction
AISC F&D Flanged and dished
(9th Ed)
ALLOW Allowance Allowable FF Flat face
ANSI American National Standards Institute F-F Face to face
API American Petroleum Institute APPENDIX Appendix
APPROX Approximately FIN Finish
ASA American Standard Association FLG Flange
ASB Asbestos FOF Face of flange
American Society of Mechanical
ASME FPT Female pipe thread
Engineers
ASTM American Society of testing & Material FS Far side, forged steel
AVG Average ft Foot, feet
BAT Battery ft3 Cubic feet
BBE Bevel both end FW Field weld
BBL Barrel FW Fillet weld
BC Between centers G Gram
BEV Bevel GA Gauge
BLD Blind GAL Gallon
BLDG Building GALV Galvanized
BLE Bevel large end GG Gauge glass
BOP Bottom of pipe GOL Gauge of outstanding leg
BOT Bottom GPD Gallon per day
BRKT Bracket GPM Gallon per minute
BTU British Thermal Unit GR Grade
BW Bevel weld HD Head
BWG Birmingham Wire Gauge HEMI Hemispherical
C Centigrade HEX Hexagonal
C to C Center to center HH Hand hole
CA Corrosion allowance HL Hole
CCW Counter clockwise HR Hot-rolled
CFM Cubic foot per HT Heat treatment
CFW Continuous fillet weld HVY Heavy
CG Center of gravity ID Inside Diameter
CHGR Charger IN Inches
CL Centerline INCL Including, included
CL to CL Centerline to Centerline INT Internal
CM Centimeter JE Joint efficiency
CO Company KG Kilogram
CONC Concentric Reducer L Liter
CORR Corrosion Allowance LB Pound
CPLG Coupling LBF Pound force
CRED Concrete Reducer LG Long
CRS Cold-rolled Steel LIN Linear
CS Carbon steel LR Long radius
CTR Center LWN Long welding neck
CU Cubic M Meter
CW Clockwise MAINT Maintenance
CWT Hundred weight MAT'L Material
Maximum allowable
DC Down Comer MAWP
Working Pressure
DIA Diameter MAX Maximum
DIM Dimension MB Machine bolt
DP Design Practice MH Manhole
DTL Detail MIN Minimum


DWG Drawing MK Mark
EA Each MK'D Marked
EL Elevation ML Match line
ELL Elbow MLW Mean low water
EQ Equal, equally MM Millimeter
Million Standard Cubic
ERED Eccentric Reducer MMSCF
Feet
ETC Et cetera MPT Male pipe thread
Thousand standard cubic
EXT External MSCF
Feet
PL Plate
D-1.10. Annotations
All dimensions shall be in imperial units (i.e., feet and inches). However metric dimensions can also be
displayed when required as alternate units (in parenthesis) provided they do not crowd the drawing.
Sufficient dimensions shall be given for positioning the equipment, piping, structure and building.
Dimensions need to be sufficient for the fabricator / erector to complete the work.
Plan views shall show most of the dimensional information. Duplication of dimensions across different
views in the same drawing shall be avoided as this may lead to errors in case of revisions to drawings.
Consistency in dimensions shall be checked and maintained across all drawings.
Decimals of a foot shall not be used for dimensions except for survey drawings. All out of scale
dimensions shall be noted as “NTS” along with the dimension value.
Dimension style “MPN” as supplied in the title blocks shall be used and must not be exploded or
overridden for scaled drawings
Dimensions must not be exploded or overridden for scaled drawings
D-1.11. Text Size and Font Styles

Use specific text sizes, font and styles when creating drawings to ensure consistency among drawings.
Only “romans” font shall be used on all drawings. Third party font files shall not be used unless otherwise
approved. PDMS 2D drawings should use only PDMS supplied auto draft fonts. Drafting personnel shall
have those fonts mapped in to AutoCAD while working on drawings generated from PDMS Draft.
Table D-1.9 - Text Height (Schematic Drawings)
Text height (mm)

Description Font A1 A3
General text, material lists, dimension text, notes Romans 3.0 2.5
Subtitles, headings, labels, match-line text Romans 4.5 3.5

View, section and elevation notations Romans 4.5 3.5
Note: For Process drawings (P&IDs, PFDs, etc.) use table below;
Text height (mm)
Description Font A1
General text, material lists, dimension text, notes Romans 2.5
Subtitles, headings, labels, match-line text Romans 3.5
View, section and elevation notations Romans 3.5
Text Height (Scaled Drawings)

Text height A1
Description Font Imperial Metric
General text, material lists, dimension text, notes Romans 1/8” 3.0
Subtitles, headings, labels, match-line text Romans 3/16” 4.5
View, section and elevation notations Romans 3/16” 4.5
Text width factor of the drawing title of standard border may be changed depending upon length of the
text. All texts and symbols should be legible when printed on ISO A3 sheets. It should be ensured that
text is not obscured, overlapped by drawing details, dimensions, call-out lines etc.
Proper justifications should be used to locate the texts aesthetically in the drawing. Vertical texts shall
have an orientation of 90° in AutoCAD.
Attributed text and blocks should not be exploded.
The following method can be used to calculate text heights for scaled drawings.
Drawing text height = Standard text height x Plotting scale factor.

For example, a plotting scale of [1/8” = 1’-0”], plotting scale factor is 96.
Therefore the drawing text height will be 1/8” x 96 = 12”.
D-1.12. Layers
Layers shall be used in engineering AutoCAD drawings to show different types of technical information
consistently. This makes the drawings easier to read, interpret and revise. Additionally, selective
information can be presented by displaying certain layers and not others. Approved layers are embedded
within the title blocks.
It must be ensured that colors of all entities created must be set to “BYLAYER”. All leader lines must be
drawn with a continuous line type and text leaders must be on the same layer as the text.
Drafting personnel must create engineering drawings using approved layering groups. Layering groups
for different disciplines are shown in table 4.12 through table 4.17

Table D-1.11 - Common Layer Group
Layer Colour Line Types Description

G-Revcloud Magenta (6) Continuous Revision clouds for current revision on drawings
G-SoW Cloud White (7) Phantom All Scope of Work (SoW) Cloud
G-Hatch White (7) Continuous All hatch patterns
G-DimLine Cyan (4) Continuous All dimension text and lines
G-Text Red (1) Continuous All Texts
G-Fittings Cyan (4) Continuous All Fittings
G-Border Cyan (4) Continuous Title block and attributes
G-Viewport Cyan (4) Continuous All Paper space Viewports
G-Grid Colour (9) Continuous All grid lines
G-MatchLine Cyan (4) Phantom All Match lines
G-CenterLine Yellow (2) Center All Centerlines
G-Symbols Cyan (4) Continuous All Symbols
Table D-1.12 - Mechanical Layer Group

M-Road Yellow (2) Continuous All Roads and trails
M-Equipment Blue (5) Continuous All Equipment (Vessels, pumps, tanks, boilers)
M-Instrument Magenta (6) Continuous Lines and Symbols associated with instrumentation
M-Electrical Magenta (6) Continuous Lines and symbols associated with Electrical
M-Piping Green (3) Continuous All Piping
M-Structural Cyan (4) Continuous All Structural
Table D-1.13 - Piping Layer Group

L-Support Yellow (2) Continuous All Piping Supports
L-Piping Green (3) Continuous All Piping
L-Equipment Blue (5) Continuous All Equipment (Vessels, pumps, tanks, boilers)
L-Instrument Magenta (6) Continuous Lines and Symbols associated with instrumentation
L-Electrical Magenta (6) Continuous Lines and symbols associated with Electrical
Table D-1.14 - Process Layer Group

P-Major line Blue (5) Continuous All major process lines
P-Minor line Yellow (2) Continuous All minor process lines
P-Equipment Blue (5) Continuous All Equipment (Vessels, pumps, tanks, boilers)
P-Instrumentation Magenta (6) Continuous Lines and Symbols associated with instrumentation
P-Skid limit Cyan (4) Continuous Skid limits

Table D-1.15 - Electrical and Instrumentation Layer Group

E-Cable tray Yellow (2) Continuous All cable trays
E-Bus bar Blue (5) Continuous Bus bar
E-Cathodic Cyan (4) Continuous Cathodic protection information
E-Cable Yellow (2) Continuous Conduits, cables and associated outlet boxes
E-Wiring Red (1) Continuous Lines and symbols associated with field wiring
E-Grounding Cyan (4) Continuous Grounding
E-Powerline Blue (5) Continuous All power lines
I-Pneumatic Magenta (6) Pneumatic linetype All Pneumatic lines
I-Hydraulic Magenta (6) Hydraulic linetype All Hydraulic lines
I-Electronic Magenta (6) Electronic linetype All Electronic lines
Table D-1.16 - Structural Layer Group

S-Beams Green (3) Continuous All Beams
S-Plates Green (3) Continuous All Plates
S-Channels Green (3) Continuous All Channels
S-Columns Green (3) Continuous All Columns
S-Concrete Yellow (2) Continuous All Concrete blocks
S-Handrails Yellow (2) Continuous All Handrails
S-Grating White (7) Continuous All Grating
S-Conductor Green (3) Continuous All Conductors
Table D-1.17 - Architectural Layer Group

A-Wall Blue (5) Continuous All Wall
A-Windows White (7) Continuous All Windows
A-Doors White (7) Continuous All Doors
A-Roof Red (1) Continuous All Roof
A-Rafter Gray (253) Continuous All Rafter
A-Purlin Gray (253) Continuous All Purlin
A-Reinforcement Magenta (6) Continuous All Reinforcement
A-Fence White (7) Fenceline1 All Fence line
A-Furniture Magenta (6) Continuous All Furniture
A-Sanitary Wares Magenta (6) Continuous All Sanitary Wares
A-Hatch White (7) Fenceline1 All Hatch lines

D-1.13. Line Types, Colors and Line weight

Approved line types for Company Engineering drawings are as shown below.
Figure 1.4 – Sample Line Types
D-1.14. Hatch Patterns

Drafting personnel will use standard AutoCAD cross-hatch patterns.
Figure 1.5 – Some Sample Hatch patterns

D-1.15. Symbol and Legend Sheet

Drafting personnel should use standard symbols and legend drawings to maintain control, consistency and
accuracy in engineering drawings. Symbols are used on drawings to identify equipments and to represent
quantities.
Legend sheet contain approved symbols that represent the various equipment families used in specific
engineering disciplines.
Attachments 1 – 3 are company approved legend sheets.
D-1.16. Holds
Drawing area which is not finalized or pending information is marked in reverse cloud withhold number
as shown below. Reason for hold is to be listed in title block area under HOLD subtitle.
Figure 1.6 – Hold mark example
D-1.17. Reference Drawings

Reference drawings, sometimes referred to as related drawings, are drawings to which another drawing
refers, i.e., a cross-reference. They are used when clarification or additional information is needed.
Drafting personnel must ensure that all reference drawings have complete drawing numbers and titles
(Title 1 and 2) in the reference drawing area of the title block.

D-1.18. Continuation Drawings

Drafting personnel must use continuation drawing match lines (phantom line types) and drawing numbers
to identify the drawing containing relevant information.
Drafting personnel must ensure that all drawing match line cross-reference have complete drawing
numbers.
P & ID Drafting personnel must note the points below:
• Show processes and service streams entering or leaving a drawing using large hollow arrowheads
• Continuation drawing numbers must be within the arrow head.
• Ensure that continuation P&ID’s have drawing numbers in the format (<Facility code> -
<document type> - <sequence number>)
Write the conveyed process above the arrowhead (1st line)

Write the origin or destination above the arrowhead (2nd line)
Figure 1.7 – Drawing continuation match line
Figure 1.8 – P & ID continuation line

D-1.19. As-Built Drawings

“Pre-design site verification” mark-up information shall be formally incorporated into a new revision of
the original document.
Mark-up information during the construction /erection / installation / site verification shall be formally
incorporated into a new revision of original document as post-construction as-built.
Typically areas that are affected by the project scope are updated in as-built. In such cases a note in the
title block shall be added stating that “This drawing has been partially as-built only in areas affected by
the project scope.”
Refer to section 4.2 for as-built revisions to be used.
D-1.20. Post IFC Drawings

All changes to drawings made to original IFC drawings will be indicated with revision clouds and
revision triangles. At final Post-IFC deliverables, only the final revision cloud triangle will be retained
until the drawings are as-built at project completion.
Note: Changes to IFC drawings shall be documented in a log for Construction Contractor. The log shall
include a list of all drawings and a description of the changes made between the previous and current IFC
release.
D-1.21. Demolition Drawings

Demolition drawings are provided to construction contractor to clarify demolition requirements.
Demolition drawings shall be prepared from pre-design as-built drawings.
Same drawing number as the base drawing with a suffix “DEMO” to the drawing number shall be used to
identify and distinguish a demolition drawing from a modification drawing. Hatch lines shall be used to
identify sections, equipment, pipes or steel members to be removed and cut lines should be clearly
identified.
Demolition drawings shall not be provided to IMG for inclusion in to Master database at the end of the
project.
D-1.22. Redrawing in AutoCAD

If a manual drawing is being redrawn on AutoCAD. It shall be handled as a new revision. For example, if
a manual drawing is revision 3 and is being redrawn, the new revision will read,
REV 4 REDRAWN ON AUTOCAD
The previous revisions are carried through to the redrawn AutoCAD drawing.

D-1.23. Revision Functions

Two revision functions must not be combined. Each function must have its own revision.
For example:
REV 0 12-12-88 ISSUED FOR CONSTRUCTION

REV 50 26-01-90 AS-BUILT
REV 51 07-06-96 REDRAWN ON AUTOCAD
REV 51-A 10-06-96 PRE-DESIGN AS-BUILT
REV 51-A1 12-06-96 ISSUED FOR PRELIMINARY REVIEW
Revision Block Style
The date format must always be DD-MM-YY (Day, Month, Year e.g. 22-05-96)
Punctuation, such as periods, slashes, commas between characters must not be used.
Revision Initials
Drafting personnel will electronically insert the appropriate initials, with no spaces, in the BY, CHK’D
and APP’D columns in the revision block.
Manual initials shall be inserted in the APP’D columns on the original legal copy of a drawing, after
completing their tasks.
Revision Clouds and Triangles

Ensure all revisions required after the initial “Rev n-0, Issued for construction”, are highlighted by a
revision cloud and identified by a revision triangle located within the highlighted area.
Leave all clouds for a particular revision on the drawing until the drawing is revised again.
Minor Changes
There is no need to insert revision clouds if there are only minor changes, such as spelling corrections or
notes that have been moved to another location on the same drawing.
Title block area

Revision clouds should not be inserted in the title block area of a drawing when a change has been made.
This avoids crowding and decreased legibility. A revision triangle should be placed in the right hand side
of the subject revised.
All engineering drawings shall be prepared to provide clear, concise and correct information in a
consistent and self-explanatory format suitable to convey the designer’s intentions unambiguously to the
fabricator or vendor.
As much as possible the drawing review should be done without cross referencing multiple drawings.

Checking Procedure
Every engineering drawing must be checked within its discipline by a checker other than the drawing
originator before proceeding to the next document checking level.
The checker must ensure that,

• Technical inputs are accurate, adequate and reflect conformance with design input documents.
• Drafting of symbols, texts, fonts, drawing format and units are in accordance with specification.
• Drawing numbering, file naming is consistent with Company Global practice.
• References and continuation drawing numbers are correct.
• “HOLD” marking done on unconfirmed information.
• Information from related drawings is checked.
For detailed checking procedure, refer to discipline drawing checking procedures.

Markup Procedure
Markups shall be legible to allow for easy reading of text or drawing beneath. Highlighters or
color pencils/pens may be used for this purpose.
All checking comment / markup on drawings shall use the following color coding:
Red – Addition / change as marked

Green – Delete
Blue – Comments
For further information refer to the Redline Markup Procedure.
D-1.24. As-Built Redline Markups

Drafting personnel shall refer to NG00-MP-BPDCC-0070003(Drawing Revision Procedure) for
guidelines about creating and managing redline markups documentation generated by Company
as well as updating and issuing of as-built.

D-2. Software programs

Drawings should be produced using AutoCAD version specified by Company. Any programs /
utilities that affect portability of electronic files shall not be used. If essential and required, it shall
be submitted for approval.
D-2.1. Auto LISP Routines

LISP routines are written to interact with AutoCAD and modify or create entities in the drawing
database. Using LISP routines saves time when creating / editing a drawing.
LISP routines / utilities that are essential to work with drawings shall be submitted along with
instructions.
D-2.2. Blocks and Attributes

Drawing instances which appears frequently in the drawing shall be inserted as blocks. For
example, valves, instruments, special items etc in P & ID drawings.
Where ever possible texts associated with blocks shall be defined as attributes. This facilitates
data extraction from the drawing database.

D-3. Transferring Drawing Files

To ensure that drawing files can be tracked, transferred easily and efficiently, drafting personnel should
name the engineering drawings consistently.
D-3.1. Drawing Submission

Drawing creator or contractor must ensure that the following are done before submitting electronic copies
to Company.
The electronic drawing files are purged of all unused layers, text styles and line types to reduce the size
of the file for quicker exporting and importing.
• All XREF’s shall be bound.

• Drawing shall be in zoom extents.
• Set to Paper space mode.
• Drawing should not contain any frozen layers.
D-3.2. Verification
The followings aspects of the drawing must be verified to ensure compliance:
Drawing size and scale

Drawing format and title block
Layers
Text size, font
Line types, color
Dimensioning / annotations
Legends and symbol standards
Document numbering
Revision procedure

[Addition] Appendix – E: PDMS Implementation Procedure
E-1.0 Purpose
Plant Design and Management System (PDMS) is a 3D modeling software that has been adopted by
COMPANY as a standard design engineering tool for its facilities.
The implementation of PDMS is a part of ongoing effort to improve the quality and integrity of
engineering solutions. Benefits, such as good productivity, less field reworks, clash reductions, accurate
material reporting, minimal material wastage and maximum drawing productions have been realized. This
procedure is intended to further improve the use of PDMS and enhance the quality of Engineering using
PDMS.
The benefit gained by using PDMS during Engineering and Construction phases is being extended to
Operation and Maintenance of facility. Ultimately it is envisaged that 3D models will play a role in
supporting the entire life of facility or plant.
E-1.1. PDMS Software

Project Management Team shall specify the PDMS software version to be used for the project in
contractual requirements. Contractor shall use compatible version to COMPANY PDMS. Under no
circumstances shall any new version be used without formal validation and written permission from the
COMPANY.
When the PDMS software is used in a project, it is essential that the same version is maintained for the
duration of the project. Under no circumstances shall a new version of the software be implemented in the
project, without prior agreement from the COMPANY. However this condition does not apply to minor
or maintenance upgrades or patches.
E-1.2. Project Initialization

The Contractor PDMS coordinator is responsible for creating the PDMS project directories and for
identifying PDMS users to the network system administrator to get required user access rights.
After the creation of the PDMS project directories, PDMS coordinator together with Contractor Project
Engineer, Discipline leads and PDMS Administrator will review the overall project requirement in order
to establish the optimum project database working environment. In particular the following criteria shall
be considered:
• Project program
• Manpower requirements
• Degree of complexity

• Geographical configuration of the facility / plant

• Construction / fabrication program requirements
• Overall project strategy
• Computer hardware / software
• Database size and structure
• Owner requirement
• Construction datum (This will be the datum adopted for the PDMS model)
PDMS Coordinator shall prepare a PDMS Implementation checklist following the above criteria and
provide same to the project discipline leads. The project discipline leads shall complete and return this
form to the PDMS Coordinator. Once the above data has been assessed and the project requirements are
established, PDMS Coordinator and PDMS Administrator shall initialize the PDMS project in accordance
with this section. A PDMS Implementation Procedure shall be developed in line with this procedure and
all deviations shall be documented for necessary approval.
E-1.3. Area classification – Facility and Sub-facility
A concept of Facility and Sub-facility shall be used to break down a complex project.
For example (figure E-1.2), the development program contains a Wellhead platform (facility QA), a
Process Platform (facility QP) which is connected by bridge. Bridge can be added to either of the projects
depending upon installation / fabrication contract and priority. Each facility is further divided into sub-
facilities level wise or module wise as shown in the example.
Each of this facility shall be setup as a different PDMS project with bridge databases shared to both
projects. Catalogue project shall be setup as a separate project and databases shall be referenced to both
design projects as shown in the sketch (figure E-1.1) below:
Facility QP Facility QA
PDMS Model PDMS Model
Project EUN
Catalogs catalogs
Figure E-1.1 – A typical PDMS Project Structure

Figure E-1.2 – Example of an offshore complex showing facility and sub-facilities
E-1.4. Platform / Plant Model Datum

Geographical / structural elements should be benchmarked as Model datum. This point may be referred to
as East 100000mm, North 100000mm i.e. E-100.000, N-100.000 for metric units or E-100’, N-100’ for
imperial units
E-1.5. Project Directory Setup

All files created or used by PDMS must be stored in specific project directories. The naming conventions
of directories and files described in this procedure will be suitable for all PDMS projects. The directory
structure and any additional special requirements to this procedure will be identified at the start of a
project and documented as part of Project PDMS Implementation procedure. The PDMS coordinator is
responsible for the creation and naming of directories and must ensure that all project file names adhere to
this procedure.
COMPANY PDMS Administrator and Coordinator shall select a three digit alphabetical logical code for
the PDMS project. This code shall be unique and shall be checked against current and archived projects.
The following guidelines shall be followed while selecting the code:
• GP12-01-01S (Upstream Numbering System for Project Technical Documents – MPN

Supplement), Table-1 shall be referred to derive facility / plant code.
• A prefix ‘X’ shall be added if the code is of two digits.
• Numerical codes shall be replaced with alphabets logically. Ex. a for 1, b for 2 etc.

For example,
• IDOHO-A wellhead platform code is BA as per Table-1. Thus PDMS code for that facility shall
be ‘xba’
• EDOP-12 wellhead platform code is Q12 and PDMS code shall be ‘qab’
A typical project directory structure is detailed below for an example project code “abc”:
abc contains all folders for PDMS project abc

abc\abc000 PDMS project databases
abc\eun000 EXXONMOBIL UPSTREAM NIGERIA catalog databases
abc\abciso Isodraft directories
abc\abcpic Draft picture files
abc\abcmac Inter-DB connection macros
abc\abcrep\templates Project report templates
abc\abcrep\report Project reports
abc\abcinfo Administrative reports
abc\abcreview\macro Review export macro files
abc\abcreview\model Review model files
E-1.6. File naming conventions - PDMS user files

Files contained within a user’s personal directory are named by the user, because they are not project
related, and will be given a suitable name by the user. All users are responsible for their personal
directories, and for deleting unwanted files. All project specific files must be stored in the project
directory.
E-1.6.1. Project Files

Project files must be stored in the relevant project directory. Since all project users will access these files,
the following file suffices must be used denoting the type of file.
*.plt draft or isodraft plot file

*.tmp temporary file
*.mac PML macro file
*.rep report template file
*.dat data file
*.dcn datacon file
*.txt ASCII file
*.mes message file
*.dxf DXF transfer file
*.dic database integrity check file
*.rvm review model file
*.rvs review status file

The naming convention for all other files will comply with the Project PDMS Implementation Procedure.
E-1.6.2. Program defined files
Under no circumstances shall program defined files or filenames be edited or changed. These files may
include Aveva application files / project default files or customized utilities that are deployed for a
project.
File types may be as illustrated below:
*.mac PML general macros

*.pmlfnc PML function definition
*.pmlfrm PML form definition file
*.pmlobj PML object definition file
*.pmldat PML data files
E-1.7. Creation of the PDMS Project

Standard Aveva scripts or contractor’s customized scripts can be used to create a project. Once the PDMS
project has been created, the SYSTEM password must be changed from default SYSTEM/XXXXXX.
Only PDMS Coordinator and PDMS Admin shall have access to the password, which shall be kept
confidential throughout the life of the project.
E-1.8. EUN Corporate Catalog Databases

COMPANY shall supply its corporate PDMS catalog/specs databases (EUN) to the contractor.
Administrative access/rights for these PDMS databases shall not be provided. COMPANY PDMS
Administrator shall assist the contractor to make database reference of the required EUN catalog
databases into their PDMS design project. Or contractor shall make use of the template design project
(supplied along with the catalogs) where the catalogs are already linked in.
COMPANY forbids contractor from making any changes to EUN project databases. In the event of
modifications required to EUN databases, contactor shall do a formal request to COMPANY PDMS
Administrator or shall copy the catalog instances to the design project catalog database to modify.
For more details on EUN catalogs and specifications please refer to section E-3.0
E-1.9. Project Team and Databases

Contractor shall follow the following conventions to create teams and databases so that their content and
purpose can be easily identified.
All design and drawing databases shall have multi write access.

E-1.9.1. Design and drawing databases

The PDMS design model databases are named using the following format:
Design databases -> p DE WOR/ p DE - rr – ss
Draft databases -> p DR WOR / p DR - rr
Where,
p – Single digit discipline code as per table E-2.3.

rr – Double digit facility identification.
ss – Double digit sub-facility code as per table E-2.4 (XX – if database used for all sub facilities)
Code Discipline
C Civil / Architectural
E Electrical
H HVAC
I Instrumentation
L Piping
M Mechanical
N Structural
R Reserve Volumes
S Safety / Loss Control
X Service supports
Table E-1.3 – Model discipline codes
Code Sub-Facility
LD Lower Deck
MD Main Deck
CD Cellar Deck
SD Sub Cellar Deck / Sump Deck
MZ Mezzanine Deck
BR Bridge
HD Helideck
JK Jacket
TS Topsides
Table E-1.4 – Typical sub-facility codes for an Off-shore platform
Hook-up area names shall start with prefix H (or K), followed by numbers from 1 to 9.
For example, in a PDMS project called xqp,

LDEWOR/LDE-QP-MD - Piping design database for Main Deck of facility QP

NDEWOR/NDE-QP-JK - Structural design database for Jacket of facility QP
LDRWOR/LDR-QP - Piping drawings for facility QP
XDEWOR/XDE-QP-MD - Support database for Main Deck of facility QP
E-1.9.2. Other databases

The following naming shall be followed for other project databases:
CATWOR/CATA All project specific specs and catalogs

CATWOR/DICT All project specific UDA definitions
CATWOR/PROP All project specific property definitions
CATWOR/DESI Cataloguing Design database (optional)
CATWOR/PADD Cataloguing Draft database (optional)
E-1.10. Database numbers

Each database is stored as a single file, stored in the project directory. The filenames have the format,
xxxnnnn_mmmm
Where,
xxx - PDMS project code.

Nnnn - is a number from 1 to 5999.
mmmm – is the extract number
Database numbers 6000 to 6999 are reserved for Upstream Nigeria databases and 7000 and above for
Aveva databases. Contractor shall use database numbers from 1 to 5999 for PDMS design project
E-1.11. Multiple databases

To control what data a user can see, databases are grouped into Multiple Databases (MDBs). A project
shall contain at least one design MDB /DESI and a draft MDB /DWG.
Projects containing more than a single facility can have MDBs for each facility to reduce number of
databases in a single MDB. /DESI-xx or /DWG-xx shall be created where xx is the facility code and
adding only relevant design or draft databases.
Draft databases shall not be added to a design MDB (i.e. /DESI).
A cataloguing MDB /CATA shall also be created. Only CATA, DICT, PROP and cataloguing design,
draft databases shall be added to this MDB.

E-1.12. PDMS User Names

Users are defined by identifiers and passwords. User identifiers shall be the same as LAN ID supplied by
IT department.
If the use of longer LAN IDs are not practical (for example LAN ID is longer than 6 digits), short names
of designers shall be used.
A READONLY (password READONLY) user shall be created for general purpose. This user shall have a
read only access to the model.
All design users shall be GENERAL users. Data Access Control (DAC) shall be used to control access to
different disciplines, model areas and restrict extent of modifications.
E-1.13. Extract Databases

Extract databases can be created from an existing databases. Standard extracts shall be used with explicit
claims only for Global Projects. No significant data shall be held in extract DB without issuing them to
Master DB. An extract database shall not own any extract databases.
Use of extract database shall be restricted for non-global projects. Refer to section E-8.0 for more details
on global project management.

E-2.0 Database Maintenance

PDMS model data is stored in Databases by DABACON (Data Base Constructor) which is used to
construct, navigate and interrogate a database structure. The following reasons may cause DABACON
failure and hence resulting in a corrupt database.
• Error in the network.

• Error while copying databases resulting truncated databases
• Insufficient disk space or network storage quota.
• Deletion of database which is referenced by another database
• Reconfiguration of database without updating references
• Undetected Dabacon errors
It is important that any data corruption that occurs is detected as quickly as possible so that corrective
measures can be taken. PDMS Administrator is responsible for carrying out such actions on a regular
basis and not just when an immediate need arises.
E-2.1. Database Integrity Checking

The PDMS Database Integrity Checker, DICE, checks the internal structure of project databases and
reports any inconsistencies or faults within them.
PDMS Administrator shall be responsible for initial setup of a script to automatically check the integrity
of PDMS model on a daily basis. This will identify any possible database corruption and ensure that the
backup data can be restored with minimal detriment to the project.
Databases with serious structural errors shall be fixed by Reconfiguration.
E-2.2. Reconfiguration
PDMS database Reconfiguration can be used in the following cases:
• To combine databases by copying parts of one into another

• To transfer databases between different projects
• To fix or recover the corrupt databases
Enough care shall be taken while using Reconfiguration to recover a corrupt database. All databases have
external references to other databases. Improper use of Reconfiguration process may lead to loss of
references and hence the data.
It shall be a good practice to see that no users are accessing the databases and make a backup of all
databases. SAMEREF option shall be used while recovering a corrupt database since it keeps same
element reference name. It will keep all database cross references intact. The following example shows
use of SAMEREF option:

Please note that, for the use of SAMEREF option the database need to be deleted after dumping data to a
neutral file. So, care must be taken to note down the database number before deleting the database to
recreate it with the same number.
FROM DB LDEWOR/LDE-QP-MD
TO FILE /F1 /F2
RCFCOPY ALL
RECONFIGURE
DELETE DB LDEWOR/LDE-QP-MD
CREATE DB LDEWOR/LDE-QP-MD DESI DBNO nn
FROM FILE /F1 /F2

TO DB LDEWOR/LDE-QP-MD
RECONFIG SAMEREF
E-2.3. Database Stamping and Merging

A PDMS session enables history of changes to the databases to be recorded. A new session number is
created each time a user saves work or while switching modules for each modified database. Sessions are
numbered for each database. These sessions are useful to compare current data with some previous
sessions or date and query the session in which attributes and elements are changed.
Database sessions shall be stamped to mark specific milestones so that changes thereafter can be tracked
and highlighted.
When a new session is made, the changed data is appended to the end of the database file. Appending
updated data to files will increase the disk space required. Large database files may lead to slow response
and also lead to database corruption. If this is a problem the intermediate sessions shall be merged after
doing a date stamping.

E-3.0 EUN Catalogs and Specifications

ExxonMobil Upstream Nigeria (EUN) catalogs and specifications were developed by AVEVA as a
contractor. EUN PDMS databases contain Piping, Structural, HVAC and Cable tray Specifications and
Catalogs.
EUN PDMS databases shall be updated or modified only by COMPANY PDMS Administrator or anyone
authorized by the COMPANY. ExxonMobil Global Practice (GP) approved changes / modifications shall
be updated to those databases as and when change happens. COMPANY PDMS Administrator shall
maintain a revision control register stating the revision, date and description of changes/additions done to
databases. Project specific requirements shall not be added / updated to the EUN databases.
User /Admin access rights for EUN project shall not be provided to contractor unless otherwise approved
by the COMPANY.
Database numbers 6000 and above are reserved for EUN databases. These numbers shall not be used
while setting up a design project.
E-3.1. EVAR settings

Supplied EUN databases shall be referenced to a PDMS design project. Contractor is not allowed to copy
the reference databases to the design project. Contractor’s evars.bat file shall be updated to add eun000
variable
The following figure describes how the catalogs shall be linked to a design project.
COMPANY Supplied
catalog databases Design project
EUN Local
CATA DB
Figure E-3.1 Catalog database link to design project
Contractor shall use supplied template project (EUT) databases to setup a new design project. EUN
databases are already linked into this template project. Contractor shall take COMPANY PDMS
Administrator help to link EUN databases to an existing design project.
Supplied Catalog databases folders (eun000) shall be held within design project folder. Refer to section
E-1.5 for PDMS project folder setup details.

E-3.2. Piping specifications and catalogs
EUN PDMS databases contain 53 Upstream Piping material classes. The following list shows the piping
specifications available.
PDMS
No Class Rating Material
Name
1 A45A 125 GRE Ameron 2000M A45A
2 A45B 125 Cu-Ni, SS (dry system) and GRE 2000M A45B
3 A45C 125 SS, GRE 2000M A45C
4 A1 150 CS A1
5 A3 150 CS Galvanized A3
6 A5 150 LTCS A5
7 A6 150 CS A6
8 A7 150 LTCS A7
9 A11 150 SS A11
10 A13 150 SS A13
11 A15 150 SS A15
12 A32 150 Cu-Ni, CS Cement Lined A32
13 B1 300 CS B1
14 B5 300 LTCS B5
15 B6 300 CS B6
16 B7 300 LTCS B7
17 B11 300 SS B11
18 B13 300 SS B13
19 B15 300 SS B15
20 D1 600 CS D1
21 D5 600 LTCS D5
22 D6 600 CS D6
23 D7 600 LTCS D7
24 D11 600 SS D11
25 D13 600 SS D13
26 D15 600 SS D15
27 E1 900 CS E1
28 E5 900 LTCS E5
29 E6 900 CS E6
30 E7 900 LTCS E7
31 E11 900 SS E11
32 E15 900 SS E15
33 F1 1500 CS F1
34 F5 1500 LTCS F5
35 F6 1500 CS F6
36 F7 1500 LTCS F7
37 F11 1500 SS F11
38 F15 1500 SS F15
39 G1 2500 CS G1

PDMS
No Class Rating Material
Name
40 G5 2500 LTCS G5
41 G6 2500 CS G6
42 G7 2500 LTCS G7
43 G11 2500 SS G11
44 API5000 5000 CS (Sweet services) API5KS
45 API5000 5000 CS (Sour services) API5KU
46 API5000 5000 High Alloy (Wet Sour) API5KW
47 MA1 150 CS MA1
48 MA3 150 CS Galvanized MA3
49 MA11 150 SS MA11
50 MA32 150 Cu-Ni MA32
51 MA45 150 GRE Ameron 2000M MA45
52 MB32 300 Cu-Ni MB32
53 MD1 600 CS MD1
Table E-3.2 – List of available PDMS Piping specifications
All above piping specifications are coded into databases using a pipe thickness for corrosion allowance of
3mm (or 0mm if 3mm is not available as per GP 03-20-01 to GP 03-20-16)
Contractor shall copy required specifications to local project catalog database with a new name by adding
a suffix to denote the corrosion allowance being used. The corrosion allowance code shall be as per table
E-3.3. For example A1, 150# Carbon steel specification for corrosion allowance of 3.0mm shall be copied
name named as A1E.
Corrosion allowance is not applicable to non-metallic piping classes.
Corrosion
Allowance Code
mm in
0 0 A
1.25 0.05 B
1.50 0.06 C
2.50 0.10 D
3.0 0.12 E
3.75 0.15 F
4.0 0.157 G
5.0 0.20 H
6.25 0.25 I
Table E-3.3 – Corrosion allowance suffix codes
All project specific changes like additions / deletion / modification of specification components shall be
done in local catalog database. Local project specifications shall be reported out in a format suitable for

QA/QC and a material engineer shall do a detailed checking. PDMS specification shall not have any
component with ambiguous description or component that should not be used by the project.
E-3.3. Structural specifications and catalogs

EUN PDMS catalog project is using Aveva master structural catalogs and specifications. Any new
profiles required for project shall be requested to COMPANY PDMS administrator or shall be built in
project catalog database.
E-3.4. Cable Tray specifications and catalogs

Aveva master cable tray specifications and catalogs are used in EUN catalogs. Additions or modifications
shall be requested to COMPANY PDMS Administrator.
E-3.5. HVAC Tray specifications and catalogs

Aveva master HVAC duct specifications and catalogs are used in EUN catalogs. Additions or
modifications shall be requested to COMPANY PDMS Administrator.

E-4.0 PDMS Modeling

This section defines the method of working and requirements for each discipline, when modeling in
PDMS. The requirements defined in the following sections are mandatory, unless the Project PDMS
Implementation procedure states otherwise. Proper application, not command syntaxes shall be used for
all modeling activities that write to the PDMS database. It is important that proper attributes are filled in
as defined in this section.
Any exceptions to the conventions mentioned herein must be approved by the COMPANY.
E-4.1. Discipline codes

PDMS Administrator is responsible for setting up proper discipline codes to PDMS SITEs. Discipline
codes shall be according to table E-1.3.
E-4.2. Naming conventions

E-4.2.1. SITE naming
PDMS Administrator is responsible for creating and naming SITEs in accordance with the following
naming convention.
<discipline code><facility code><sub-facility code><function code>
Where,
Discipline code – as per table E-1.3

Facility code – as per GP 12-01-01S Table -1
Sub-facility code– as decided by the project, refer to section E-1.3 for more details
Function code – a code denoting the function of that SITE, refer table below.
Code Description
D Deck / plant installed items
E Existing items
U Underground items (onshore)
X Hook-up items
V Vendor items
F Future items
S Study design / Temporary design
Table E-4.1 – Function codes for SITE

Site name examples,
/LQPMDD – Deck installed Piping for facility QP, sub-facility MD.

/LQPMDX – Hook-up Piping for facility QP, sub-facility MD.

/LQPMDV – Piping done by vendor for facility QP, sub-facility MD.

/NQPJKD – Jacket structure for facility QP.
Note: All above functional SITEs may be within a Database. So, a database may contain more than a
SITE.
E-4.2.2. ZONE naming

The naming format below shall be used for Zones in general,
<SITE name> - <functional code>
Typical functional codes are listed below:
Discipline Code Description

L various Process service code shall be used.
M EQU Mechanical equipment packages
M VES Pressure vessels
M PUM Pumps
M STR Additional structural parts of package items
M MIS Miscellaneous tagged items
N COL Columns
N BRC Vertical, horizontal bracings
N DPS Structural primary steel
N DSS Secondary deck steel
N DPL Deck plating / grating / handrails
N PLT Service platforms
N SEQ Equipment support steel
N SPR Pipe racks , structural supports for piping
N ASL Access stairs & ladders
N SMH All material handling structures – monorail, davit etc
N MIS Miscellaneous structures
E EQU All equipments
E TRA Cable trays and ladders
E CJB Control panels and junction boxes
E LGT Lighting fixtures
I EQU All equipments
I TRA Cable trays and ladders
I CJB Control panels and junction boxes
H EQU All HVAC equipments
H DUC All HAVC ducts
S EQU All safety equipments
S ESC Escape route
R VOD General Piping void area
R COM Coaming
R MHA Material Handling Accessories
R TRM Trimmer beams for pipe supports and tray supports

R PLT Preliminary reserve volume for service platform

R ACC Reserve volume for access, maintenance
R LAY Reserve volume for platform Lay down area
X PIP Piping supports
X ELE Electrical cable tray supports
X INS Instrumentation cable tray supports
X HVA HAVC duct supports
C STR Architectural structures
C FIT Architectural fittings
Table E-4.2 – Function codes for ZONE
E-4.3. Mechanical Equipments

All mechanical equipments, pressure vessels etc. shall be modeled using PDMS equipment module and
shall be tagged as per P&ID.
All equipments shall be modeled with enough details to enable space reservations for clash checks. All
major parts shall be modeled to exact available dimensions. Equipment internals shall not be modeled
unless otherwise it is essential for design.
All nozzle connections to piping shall be modeled and tagged as below:
<equipment tag> / <nozzle tag as per P&ID>
For example, for an equipment /V-1001, nozzle N1 shall be tagged as /V-1001/N1.
Vessel access man-ways and hand holes shall be modeled with exact dimensions with required access
reserve volumes. Tube bundle removal volume for heat exchanges, heaters, and cartridge / filter basket
removal space for filters shall be modeled. All obstruction volumes shall be under SUBE named as
<equipment tag>/OBST.
Vessel / Equipment insulation / fireproofing shall be modeled with correct thickness under SUBE
<equipment tag>/INSU.
Support or ladder clips on vessels/columns shall be modeled to exact dimensions under a separate SUBE
named as <equipment tag>/CLIP.
Structural beams / profiles, ladders of a package item shall be modeled accordingly in STR zone with
structure name as <equipment tag>/STRU. Origin of STRU shall be same as corresponding equipment.
The equipment datum / origin location shall be as per the table below:
Equipment Type Datum location

Vertical pressure vessels Bottom tan line
Horizontal pressure vessels Intersection of vessel center line and fixed support

saddle
Intersection of vessel center line and fixed support
Heat exchangers
saddle
Pumps Intersection of suction & discharge nozzles
Compressor packages As marked by vendor
Should be decided by package engineer & shall be
Other equipment packages
indicated in the vendor drawing
Table E-4.3 – Equipment datum / origin locations
Origin of all sub-equipments (except COG sub equipment) under equipments shall be E0, N0, and U0
with respect to Equipment datum, i.e. SUBE origin shall be same as EQUI origin.
Equipment or package center of gravity (COG) shall be modeled as a SUBE <equipment tag>/COG. Two
dishes shall be modeled to make a sphere of max diameter 50mm. The origin of this SUBE carrying
COG shall be located at COG point of the Equipment.
EQUI & SUBEquipments shall be modeled with default orientation of ‘Y is North and Z is Up’. PDMS
Administrator shall generate a report of all equipments and shall take necessary action to re-orient them.
The following attributes shall be filled to equipments (EQUI),
Modeling status code (code as per progress measuring procedure for the
:Pstatus
project if any)
:Mdsn Mechanical datasheet number
:Mdsr Mechanical datasheet revision
:Vdrname Vendor name
:Vdrgno Vendor drawing number
:Vdrgrev Vendor drawing revision
Weight of the item. If no accurate data is available package engineer shall
:Weight
estimate the weight.
:Hold Hold (True or False)
:Holddesc Description / reason for the hold
The following attributes shall be filled to nozzles (NOZZ),
:Hold Hold (True or False)

:Holddesc Description / reason for the hold
:TieInNo Tie-in number

E-4.4. Piping
PDMS Piping module shall be used to model all piping / pipelines and vessel trims.
All piping starting from ½” shall be modeled with proper piping specification and insulation / tracing
specifications. Piping shall be complete, accurate and must comply with P & ID.
Pipes shall be named according to line numbers indicated in P&ID. If piping is classified under different
area, area codes shall be used as prefix as below,
<area code> / <line number as per P&ID>
Inline instruments, SP-items, Valves etc. shall be tagged as per P & ID.
Following guidelines shall be followed while modeling piping:
• AutoClash should be switched ‘ON’ while modeling.
• Proper ISPEC/TSPEC spec shall be used to model insulation or tracing. TEMP attribute in PIPE
and BRANCH level shall be set to proper temperature to select correct insulation thickness.
• Piping within equipment / vendor package shall be modeled if determined necessary by piping
design and if certified vendor data is available.
• Different piping specs shall not be under a single line number. Process department shall provide a
new line number after the spec break. If the spec break contains no significant pipe run (for
example, only gasket, spectacle blind connected to equipment nozzle or a drain connection) then
a new branch shall be created for those components. The branch PSPEC shall be set properly so
that spec break mark appears in the design isometric.
• Pipes passing from one sub-facility to another shall be split at a natural or logical break point only
if there is any fabrication/installation requirement such as in modular design / construction.
Otherwise pipes shall not be split.
• Point 3 of TEE and OLET in sloped lines shall be oriented up or down for rising or dropping
branch connections using command syntax “DIR AND P3 is UP” or DOWN.
• Pipe branch open ends (HCON/TCON) for vent or drain shall be set as VENT or DRAN.
• All deck penetration, wall penetration or beam penetrations shall be modeled using appropriate
ATTA.
• In no case shall MTOComponent attribute be set to OFF. If required to be switched off, MTOC
DOTD or DOTU shall be used.
• Data consistency check for a pipe shall not produce any errors. PDMS Admin shall prepare a list
of approved errors / warnings.

• Vessel trims shall be modeled as individual pipe with tag number per P & ID and service code
shall be VT.
E-4.5. Civil / Structural

In general, the PDMS model should be organized to facilitate the use of appropriate applications,
optimize the performance of required tasks and maximize the structural model’s data extraction
capability.
Structural items are modeled in PDMS to fulfill four major functions: structural drawing production,
reference (back ground/foreground for piping plans, model reviews etc.), clash detection and material
take-offs. Each of these functions may be present in a particular project with differing levels of details
needed of each function. The types and location of project, the layout, and the piping modeling hierarchy
also affect the structural modeling procedure. All of these factors make it extremely difficult to specify a
global structural modeling procedure that is both functional and economical. Instead, a specific example
will be presented that should be followed whenever possible. In all cases the Project PDMS
Implementation Procedure shall specify all required conventions; the level of detail needed in the
modeled elements, and thus supersedes any requirements presented herein.
For the purpose of this document, structural items are classified as all steel catalog elements and concrete
elements such as foundations, elevated slabs, ground floor slabs inside of buildings/structures, structural
walls etc. for both offshore & onshore plants.
E-4.5.1. Structural model content:

The following items shall be modeled in a steel work database:
• Columns and bracings

• Primary & secondary steel
• Access / service platforms
• Pipe racks / supports
• Equipment supports
• Gusset plates, stiffeners
• Stairs, Ladders
• Plating, grating and handrails
E-4.5.2. Civil model content:

The following items shall be modeled in a civil work database:
• Column and equipment pedestals or piers

• Foundations including piling, pile caps, mats, strip footings and spread footings
• Concrete slabs
• Concrete pads
• Trenches
• Sumps and pits
• Closed and open drain channels

• Underground gravity flow or sewer piping
E-4.5.3. Abbreviations
Civil / structural technical names shall be used to name PDMS elements to denote the content of the
model. The abbreviations shall be uniform over the full project and shall be documented in Project PDMS
Implementation Procedure.
The following list of abbreviations may be used in element names.
FLR Floor or roof level, is a collection of objects representing a level in a structure.

FRMW Framing or framework element is a collection of SCTNs grouped together.
Girder elements designed as an approximately horizontal element that is
GIRD
connected to a POST, COLU or HANG element at either or both sides.
GRAT Grating elements
GUSS Gusset plate elements
Hanger element is as an approximately vertical element that hangs from
HANG
another element.
Horizontal Brace element is as an approximately horizontal planar element that
HBRA
is primarily an axial load carrying member.
Mat element is an approximately horizontal planar element such as footing for
MAT
a column pedestal, tank pad, etc.
MONO Monorail element is as an element used for monorail or crane rail functions
Pad element, is an approximately horizontal planar element such as an
PAD
equipment pad, stair pad, ladder pad, etc.
Pedestal element, is vertical portion of a support for a structural column or
PEDS
equipment.
PL Plate element
Platform is a collection of objects representing a level in a structure that is too
PLTF
small to be classified as a FLR such as an equipment platform.
Post element, is approximately vertical element that does not have a grid name
POST
and is primarily an axial load carrying member.
PR Pipe Rack elements
Sub-floor element, is a collection of objects represent a portion of floor or roof
SBFL
level that requires special or different treatment than the surrounding level.
SLAB Slab element is an horizontal planar element including openings
TREN Trench elements
TRUS Truss element is a collection of objects that make a truss
Vertical brace element is a vertical planar element that is primarily an axial
VBRA
load carrying member.
WALL Wall element is a vertical planar element including openings.
E-4.5.4. Primitive elements

When using primitives to model structural elements, avoid orienting the primitives away from the default
(Y is North and Z is Up) as much as possible. Use PANE, EXTR or NXTR elements shall be done where

possible instead of multiple BOX or NBOX. This enables extraction of MTO and weight / COG for those
elements.
E-4.5.5. PANEL elements

Planar structural objects such as plating, grating, slabs, walls etc., shall be represented by PANEL
especially when these items contain openings or penetrations where FITTINGS could be used. The
PANEL’s LOOP vertices must be input in a clockwise order. For horizontal PANELs such as slabs,
grating etc., the justification shall be set to DTOP. For wall PANELs set the justification attributes to
reflect the outside face of the wall.
E-4.5.6. SCTN elements
Vertical SCTNs shall be input in a manner consistent with structural geometry. Horizontal SCTNs shall
input south to north or West to East as appropriate whenever possible. The MEML attribute must be equal
to JUSL attribute at all times.
E-4.5.7. Steelwork connectivity

Steel connectivity shall be used only if the contractor has the proper joints and fitting catalogs. Otherwise,
significant components of joint / fittings shall be modeled using steel primitives.
E-4.5.8. Columns
All of the named columns for each building/structure must be included in a separate FRMW. This allows
the PNODEs and multi-pieced columns (spliced) to be handled as one unit. Each of the FRMWs should
be named similarly (i.e. /COL_A-1 or /COL_DA-3.5, etc.). The first SCTN in each FRMW should be
named with column mark (i.e. in FRMW /COL_A-1 the first SCTN should be named /A-1). Once the
columns are started being used for reference in the drawings or referenced by other disciplines, the
column SCTN and FRMW should only be modified. It shall not be deleted and remodeled.
E-4.5.9. Levels (Floors and Roofs)

Floor and roof levels should be modeled as STRUs (depending on size and complexity). For steel framed
floors, the STRU should be prepositioned with Z coordinate set equal to TOS elevation before any
FRMW are created under the STRU. This allows the user to easily query the relative POS of any SCTNs.
For example, a STRU with a TOG elevation of 5000mm and 25mm thick grating should have a POS of
E0 N0 U4975mm. The POS of SCTNs directly supporting the grating would give a zero elevation
difference. Sloping roof of STRUs should be set to the high point of roof elevation.
E-4.5.10. Gusset Plates

The area around the intersections of the bracing members and columns or breams should be avoided when
routing pipe, conduit etc. The structural PDMS designer should obtain plate sizes and locations from the
engineer and shall input the gusset plates manually. The gusset plate elements should be grouped by floor,
gridline and truss member etc.

E-4.5.11. General Hierarchy

Depending upon on the size and type of the project, each deck or building may need to be in a separate
database and or SITE. The following example (fig E-4.4) shows a typical hierarchy structure of an
‘offshore’ platform. Project PDMS Implementation Procedure shall specify hierarchy structure for the
project in detail in line with this procedure.
The following key points shall be noted:
• SITEs are created and named by PDMS admin and shall not be modified by the user.
• Zones shall be created by PDMS designers and origin shall be E0 N0 U0.
• All child elements shall contain ZONE names as prefix.
• All element names shall be in descending order of importance.
• Service platform or Floors STRU shall contain all SCTN, Plating/grating and handrails under
separate FRMW (within same STRU).
• Ladders and stairs shall be numbered consecutively through the area or building.
• Platforms provided by equipment vendor or that is integral with equipment are to be modeled in
Mechanical database.

SITE /NQPMDD
ZONE /NQPMDD-DPS
STRU /NQPMDD-DPS/TOS_EL10.000
FRMW /NQPMDD-DPS/TOS_EL10.000/FRMW
ZONE /NQPMDD-DSS
STRU /NQPMDD-DSS/TOS_EL10.000
FRMW /NQPMDD-DSS/TOS_EL10.000/FRMW
ZONE /NQPMDD-COL
STRU /NQPMDD-COL/STRU
FRMW /NQPMDD-COL/A-1/FRMW
SCTN /NQPMDD-COL/A-1
ZONE /NQPMDD-PLT
STRU /NQPMDD-PLT/V-1001
FRMW /NQPMDD-PLT/V-1001/FRMW
FRMW /NQPMDD-PLT/V-1001/GRAT
FRMW /NQPMDD-PLT/V-1001/HR
ZONE /NQPMDD-DPL
STRU /NQPMDD-DPL/TOS_EL10.000
FRMW /NQPMDD-DPL/TOS_EL10.000/PL
FRMW /NQPMDD-DPL/TOS_EL10.000/HR
ZONE /NQPMDD-BRC
STRU /NQPMDD-BRC/ROW_1
STRU /NQPMDD-BRC/ROW_A
Figure E-4.4 – Typical hierarchy for offshore structural elements (continued in fig E-4.5)

SITE
ZONE /NQPMDD-ASL
STRU /NQPMDD-ASL/LAD/1
STRU /NQPMDD-ASL/LAD/2
STRU /NQPMDD-ASL/STA/1
ZONE /NQPMDD-SEQ
STRU /NQPMDD-SEQ/V-1001
STRU /NQPMDD-SEQ/V-1002
ZONE /NQPMDD-SPR
STRU /NQPMDD-SPR/TOS_EL.14.000/NS
STRU /NQPMDD-SPR/TOS_EL.14.000/EW
ZONE /NQPMDD-SMH
STRU /NQPMDD-SMH/MONORAIL_BOS_15.500
STRU /NQPMDD-SMH/V-1001/DAVIT
STRU /NQPMDD-SMH/V-1001/STRU
Figure E-4.5 – Typical hierarchy for offshore structural elements.
E-4.5.12. Material take off, weight and center of gravity

PDMS structural model shall often be used to report materials, weight of structure and center of gravity
(COG).
To enable accurate reporting the following should be taken care of while modeling,
• Matref attribute for SCTN and PANE elements should be set. Matref contains material density
value which should be set according to material type and grade.

• SCTNs should be trimmed properly at connections / joints to avoid extra material.
• Non-structural primitives (for ex box, cylinders) shall not be used to represent structural
elements. Material, weight and COG reporting cannot be done for non-structural elements.
E-4.6. Civil
A similar hierarchy structure as described in section E-4.5 shall be followed and defined in Project PDMS
Implementation Procedure.
Column footings shall be modeled with enough details to check interferences between equipment
foundations or underground piping. Ground sloping shall be modeled with enough accuracy to enable
piping design to get proper elevations.
Obstruction volumes shall be modeled as reserve volumes for existing underground cables, pipes or other
type of voids.
E-4.7. Architectural
Architectural elements should be modeled as separate structures within the zone and clearly named to
identify the element concerned. The hierarchy and naming should follow the format shown in the
structural section whenever possible.
A detailed architectural hierarchy shall be defined in the Project PDMS Implementation Procedure.
E-4.8. HVAC
The purpose of this section is to ensure a common approach to the input of HVAC into the PDMS model.
The hierarchy and naming will follow the similar format of Piping (section E-4.4) for HVAC Ducts and
Mechanical equipment (section E-4.3) for HVAC Equipment. All HVAC equipment and ductwork must
be modeled using the HVAC applications.
On projects where contractor is not responsible for HVAC ductwork design and no accurate design data is
available, space shall be reserved by using PDMS equipment primitives. Enough soft volumes shall be
modeled for insulation flanging, supports, inline instrument and maintenance or access area on equipment
cabinets and personnel access.
E-4.9. Electrical and Instrumentation

The purpose of this section is to ensure a common approach for designers to input Electrical and
Instrumentation items into the PDMS model.
E & I group is responsible for providing vendor information to PDMS Administrator / Coordinator for
inline instruments. Piping is responsible for placement of these items and proper sizing based on vendor
information received from E&I engineers. Refer to the piping section for more details on inline items.
Instrument engineers are responsible for checking the location and orientation of all inline instruments.

All electrical and instrument items described below shall be modeled by E&I designers with the exception
of inline instruments.
• Cable trays (4” and above) and associated supports

• Cable Penetrations (Multi cable transits)
• Underground duct banks
• Channels
• Substations
• Conduits in critical locations (2” and larger)
• Transformers
• Substations
• Control panels
• Control stations
• Lighting panels
• Lighting panel transformers
• Lighting fixtures
• Analyzer House
• I/O Equipment (DCS/PLC)
• Control Room Equipment
• Instrument and Electrical terminal or junction boxes
• Annunciator panels
• Off-line Instruments like Fire gas detectors (including line of vision), CCTV camera etc.
• Support stands for field devices
Cable trays are modeled with proper tray or ladder specs detailed enough to reserve space and extract
MTO. Tray main (PIPE) shall be named as given below:
<site name> / <prefix> - <serial number>
Where,
<site name> PDMS SITE name containing the tray

<prefix> code which may describe the function of tray, refer table below.
< serial number> a sequential number or reference number from E & I design.
EH High voltage cables

EL Low voltage
PS Power supply cables
LG Lighting cables
CN Control cables
TC Communication cables
Table E-4.6 – Cable tray function codes
If a tray numbering system is used for the project, same shall be used instead of the above defined.

Junction boxes, Control panels shall be modeled as STRU with enough details for accessing and opening
of panel doors etc. STRU origin shall be on the supporting point uniformly and shall be used to query or
report their locations. STRU shall have a FRMW for modeling SCTN elements for support of JB /
Control panels. SUBS shall be used to model primitives to hold panels. Model shall enable MTO
extraction for JB / Control panel support sections. The following naming shall be followed:
<site name> / <tag number>
<tag number> - is the JB / Control panels (CPL) identification number used in layout design.
For example:
STRU – IQPMDD/CPL-1001
FRMW– IQPMDD/CPL-1001/STRU
SUBS – IQPMDD/CPL-1001/PANEL1
SUBS – IQPMDD/CPL-1001/PANEL2
All lighting fixtures shall be modeled as STRU with enough details to represent the shape / size and with
enough obstruction volume for accessing / maintenance. Mounting pole shall be modeled as standard
structural tubes or profiles. Each lighting fixture (SUBS) shall be given enough description (type of
fitting, wattage etc.) for MTO extraction.
<site name> / <tag number>
<tag number> - is the identification tag used in the layout or shall be as following:
<functional code> - <serial number>
Where the functional code is as below:
HS High pressure sodium

MV Mercury vapor
FL Fluorescent
IN Incandescent
EX EXIT lighting
EM Emergency lighting
Table E-4.7 – Lighting fixture function codes
For example:
STRU - EQPMDD/HS-001, Desc ‘High pressure sodium, bracket mounted type-1’

FRMW – EQPMDD/HS-001/STRU
SUBS – EQPMDD/HS-001/FIX-1, Desc ‘High pressure sodium, 150W’
SUBS – EQPMDD/HS-001/FIX-2, Desc ‘High Pressure sodium, 74W’

The above naming conventions may not always meet requirements across different projects. If a new code
is required it shall be added and naming conventions are amended accordingly.
E-4.10. Multi-discipline Service supports

Piping, Cable trays and HVAC duct supports shall be modeled using Aveva’s Multi-Discipline Supports
(MDS) application. If not, contractor can use any customized support application / utility which can
model all types of primary support attachments (catalog instances). Pipe support model should be detail
enough to produce reports and drawings.
Primary supports include attachments to the lines such as U-bolts, clamps, pipe shoes, pads, guides,
anchors etc. Secondary supports are the standard structural support frames using Aveva structural
catalogs.
Support model shall have enough details to develop support drawing, extract MTO and do interference
checks. Model shall be used to check support requirements, adequacy and optimization / sharing of
supports between different disciplines i.e. sharing supports between pipes, trays and ducts.
Piping discipline is responsible for modeling of pipe supports and generation of drawings. Structural
discipline shall check the adequacy of the support members and configuration, if the load on support is
more than 2MT. A similar process shall be followed for tray and duct supports. Piping discipline shall
check and optimize supports between different disciplines i.e., tray and duct supports.
E-4.11. Safety equipments

All safety equipments indicated on safety equipment layout shall be modeled and tagged as shown in the
layout. The safety equipments but not limited to the following shall be modeled,
• Hose reel
• Fire monitor
• AFFF hose reel
• Fire extinguishers
• Fire blankets
• Life raft
• Life buoy
• Escape rope
• Life jacket
• Life boat
• Safety shower & Eye wash
• Primary / Secondary escape route
Escape routes shall be modeled as PIPEs and BRANches using EUN’s “ER” Spec. Equipment primitives
shall not be used unless otherwise the required configuration or shape can’t be achieved by using ER
Spec.
The naming of the escape route shall be as below:

<site name> / <functional code>
Where, functional codes shall be PRI for primary and SEC for secondary route.
For example,
PIPE - /LPMDD/ESC/PRI
BRAN - /LPMDD/ESC/PRI/B13
E-4.12. Reserve Volumes
All access ways, maintenance space, lay down area, material handling space and other void areas shall be
modeled as EQUI.
Service / access platforms for equipment or instrumentation access shall be modeled by piping designer as
a preliminary design and shall be used as input for structural discipline. Piping designer shall check and
delete this reserve volume once structural designer designs the platform.
Volumes shall be modeled under specific zones depending upon their function as shown below:
ACC General access way

PLT Service platform reserve volume ( * )
VOD Piping void area
LAY Lay down area
COM Coaming ( * )
MHA Material handling accessories
TRM Trimmer beams for piping / tray support ( * )
Table E-4.8 – Reserve volume function codes
Naming of reserve volumes shall be as below:
<site name> / <functional code> / <description>
Where,
<functional code> - is the code as in table above.
<description> - small description to explain the purpose of the volume.
Functional codes marked “* “in the table E-4.8 above are valid only for study model. Upon confirmation
of the study, the same shall be replaced by proper design by the structural discipline in correct hierarchy.

E-5.0 Quality Management

In order to ensure that all construction deliverables generated from PDMS achieve a high standard of
dimensional accuracy, multi discipline design coordination and constructability, formal quality checks
must be executed across all engineering and design activities.
The following checks shall be implemented in a PDMS design project.
E-5.1. PDMS Specification check

PDMS Administrator shall be responsible for performing all specification checks. Structural steel, cable
tray and HAVC duct specifications are standard Aveva specifications. Hence a check may not be
required. But this exception doesn’t release the contractor’s responsibility to fix the errors if found.
All piping / insulation / tracing specifications shall be checked thoroughly by PDMS Administrator with
the help of Piping Material Engineer before any formal extraction of Isometrics or MTO. PDMS
administrator shall produce a report of piping classes in a suitable format to be checked by Material
Engineer against latest Piping class GPs. The following should at least be checked:
• Component description
• Material description
• Suitable codes / standards
• Branch table – branch fittings
• Pipe thickness / schedule
• Pipe, fitting and structural profile weights
All irrelevant items shall be removed and spec should be completed as per GP.
Piping specification check prints shall be filed and preserved for Quality Audit.
E-5.2. Data consistency check

A formal Design Data Consistency check (DATACON) shall be done for all piping sites before extraction
of piping isometrics. The checks shall include the following:
• Compatibility of connection
• Adjacent items are connected and no gaps exist
• Connected components are not skewed with respect to one another
• Piping component bores are consistent
• Branches are properly terminated
• Pipe cut lengths are not less than acceptable minimum
• Angles of elbows and pulled bends are within set limits in the Piping spec
PDMS piping designer is responsible for the preliminary DATACON check for all pipes under his
responsibility.

PDMS Administrator shall do a formal run of DATACON and output shall be saved in to file for
checking.
PDMS coordinator shall be responsible for making sure all pipes are error free and are good to generate
final isometrics. He shall maintain a list of acceptable errors or warnings which are not design errors.
Structural elements need not be DATACON checked.
E-5.3. Interference check

As a rule, PDMS designers should use AutoClash feature while doing design. In exceptional cases
AutoClash may put off. In this case a formal clash check should be done after completing the
modifications.
It is the responsibility of the PDMS Administrator to do formal clash checks for all design disciplines.
Piping, Mechanical and E & I model must be clash checked. Structural design may not need a formal
clash check since all connections produce clashes. Instead, designers shall do a check using manual clash
check on screen and visual check adding volume around the structure.
Aveva “ClashManager” or any other Clash management utility that has options to run, view and approve
the clashes shall be used. PDMS Administrator shall do frequent Spatial Map updates for all databases to
avoid spurious results.
A formal clash report shall be available with proper approval status while issuing piping design isometrics
for construction. No piping isometric shall be issued with unapproved clashes. Corrective action must be
taken to resolve the clash before issuing isometrics.
Project PDMS Implementation Procedure shall clearly define the procedure to identify and approve /
resolve clashes.
E-5.4. Design Check

Formal design quality checks shall be executed across all engineering disciplines in accordance with
Engineering Department procedures. The timing and sequence of formal design quality checks must be
implemented at predetermined milestones, commensurate with specific design development stages and
the progressive release of major multi-discipline design drawings and documents for both internal and
construction issues in accordance with project plan.
Drawings which are developed outside of PDMS environment such as structural drawings shall be first
modeled in PDMS to conform the design. A simple drawing extraction shall be done for that design and
further annotation / amendment shall be in other applications such as AutoCAD.
All drawings which are developed outside of PDMS environment shall be checked against PDMS model
for their conformity before a formal issue.

E-5.5. Process Parameters

All process parameters from the line list shall be transferred to PDMS model through an automated
transfer. Manual updating shall be avoided to eliminate errors. A standardized format shall be used to
transfer the values using MS Excel or PML macros.
E-5.6. Model Status Register

PDMS coordinator is responsible for maintaining a Model Status Register for all disciplines. Equipment /
Piping register shall be detailed with all equipment tags and line numbers listed. The following shall be
listed as a minimum:
• Design status of the item.
• Equipment / Instrument vendor name, drawing number and revision
• Holds and comments with reasons
• Catalogue or specification items under hold

E-6.0 Model Review

E-6.1. Objective
It is COMPANY policy to conduct model reviews with contractors on projects that are utilizing PDMS
for design. The model reviews shall be for the purpose of reviewing progress, obtaining design approval,
and verifying adherence to procedures, specifications and design practices.
This section provides guidelines as to when and how a model review should be conducted.
Aveva’s Review Reality application shall be used for conducting Model Reviews.
E-6.2. Responsibilities
E-6.2.1. COMPANY Project Team
COMPANY Project Management Team shall be responsible for scheduling formal model reviews as per
guidelines in this section.
E-6.2.2. Project Engineer

Contractor’s Project Engineer shall be responsible for arranging for all model reviews and issuing model
review agenda. He shall be responsible for obtaining correct representation of all disciplines or parties. In
addition, Project Engineer or his representative (comment recorder) shall be responsible to make notes of
all review comments or suggestions.
E-6.2.3. Design Leads
Contractor’s design leads shall be responsible for the following:
• Providing an updated Model Register – Piping lead

• Providing general arrangement drawings – Piping lead
• Ensuring the model is ready for review – Piping lead / PDMS Coordinator
• Participate in all model reviews – All design leads or representatives
• Provide P & ID’s for areas to be reviewed. – Process lead
E-6.2.4. Review Team Leader

Piping Design lead shall act as Review Team Lead as he is well conversant with all aspects of the layout.
He shall guide the audience through the model with the assistance of model operator. The team leader
shall be responsible for the efficiency of the review process, the adequacy of comments made and the
subsequent follow-up.
E-6.2.5. Model Operator

The model or system operator shall be familiar with the technical content of the model and the computer
system. He should understand the technical terms used in petrochemical and refinery technology.

E-6.3. Scope of Model Review

Reviews of the model shall take place at least when the model is 30%, 60% and 90% complete. The
review schedules may vary depending upon the project execution strategy. But reviews shall be enough to
ascertain that the model is fit for the purpose.
The items listed below should have been completed for these model reviews:
Model 30% complete:

• Location, orientation of all equipment and all reserved volumes.
• Structures – Steel and concrete.
• Major piping that determines equipment positions.
• Packaged equipments and orientation.
• Escape routes defined and marked.
• Pipe racks and main pipe support structures.
• Main electrical and instrumentation cable trays.
• Building outlines – control room, analyzer houses, switch room etc.
• Concrete slabs, paving and roads.
• Outline of underground electrical and instrumentation trenches.
• Underground sewer systems and collection & separation systems.
Model 60% complete:

• The actions resulting from the 30% model review.
• All other piping largely completed.
• Orientation of ladder, stairs, platforms on vessels and columns
• Platforms for valves and equipment operation.
• Permanent cranes and hoisting beams.
• Final dimensions of primary steel structures and other steel constructions.
• Secondary steel works and bracing.
• Safety equipment locations like eye wash, safety showers.
• Major and special pipe supports
• Local operational panels
• Firefighting systems – hydrant, monitor, water spray systems etc.
• Instrument transmitters and outlines of junction boxes, panels and cabinets.
• Above ground instrumentation and electrical tray routing.
• Outlines of steam tracing manifolds.
Model 90% complete:

• The actions resulting from 60% model review
• The model shall be substantially complete, including instrumentation. Final comments shall be
made at this stage.

E-6.4. Team Composition

To prevent specialist sub-meetings during a model review which distract the attention of other team
members, teams should be formed of members with a common interest in the subject under review. The
number of required team depends on the progress of the model.
At least the following disciplines shall be represented in a review team, depending on the progress of the
model:
For a 30% review:
• Projects
• Process technology
• Piping and Mechanical
• Civil / Structural
• Technical safety and operability
• Operations
• Maintenance
The team may occasionally be extended by a rotating equipment or mechanical representative, especially
if extraordinarily large pieces of rotating or mechanical equipment need to be installed or maintained.
Furthermore, it is advisable to consult other relevant specialists at an early stage of model design if
required (e.g. for solids handling, slurry transport etc.).
The 30% model review shall be concluded with a statement describing which aspects are considered to be
frozen at this stage. For a list of these aspects, reference is made to section E-6.3.
For a 60% model review, teams shall review the model for operability and safety, and engineering and
maintenance.
Operations and Safety review shall be comprise of the following disciplines:

• Projects
• Process Technology
• Technical safety and operability
• Operations
Engineering and Maintenance review shall be done by:

• Projects
• Structural
• Electrical and Instrumentation
• Maintenance
More teams with additional discipline representatives may be formed depending upon the nature of
process under view. These teams may include, for example a representative from fire-safety and rotating
equipment disciplines.

Agreed comments from 30% review shall be a part of model review.
A detailed check of major process / utility piping systems shall be done with respect to P&ID. A check of
process design reflected in the P&ID’s shall be avoided during the model review, but if the model review
leads to more economically attractive solutions without jeopardizing the design functionality and safety,
this change may be implemented and P&ID shall be made consistent with the model. However such
changes shall be brought to the attention of the Project Manager.
The 60% model review shall be concluded with a statement describing which aspects are considered to be
frozen at this stage. For a list of these aspects, reference is made to section E-7.3.
For a 90% model review, the composition of the main review team should be identical as it is for 60%
model review. The team shall review the model on the added details such as the location of junction
boxes, instrumentation, sample point locations and steam manifolds etc. Further agreed comments from
60% reviews shall be reviewed.
E-6.5. Handling comments

After each review, the team shall decide if the level of completeness of the model is in line with the
requirements defined in section 9.3. Shortcomings in the degree of completeness of model shall be
highlighted and after correction, checked in the next review, or in an additional review depending on the
degree of incompleteness.
Screen shots of the model shall be taken showing clearly the items under comment. The picture file names
shall be according to the comment number and shall be attached along with the model review comments.
Figure below is a typical format for model review comment register.
Sl Description of Reference Tag Comment Action

Area Status Remarks
No comment or Screen Shot by by
Table E-6.1 – Typical format for model review comment register
The columns in the above format shall be filled in as below:
• Area – Area or Sub facility identification
• Description of comment shall be unambiguous, enough to describe the problem or suggestion

with references to related documents or drawings

• Reference tag numbers shall be mentioned or Screen shot numbers shall be referred if any.
• Identification of team member who made the comment shall be noted for future follow up.
• Party or discipline responsible for taking remedy action.
• Status of the comment while following up – CLOSED or OPEN.
• Additional remarks like reason for closing the comment or reason for rejecting the comment.
The comments shall be projected on the screen, so that the text of the comment is mutually agreed with
the concerned parties.
Once the model review is concluded a formal distribution of Model Review comment shall be done along
with necessary attachments.
E-6.6. Internal model reviews

Contractor shall conduct regular internal reviews of the model to check design progress and resolve any
technical issue among disciplines. Piping design leads (Contractor and Company) shall take lead of the
internal reviews and shall request the presence of other disciplines as required. The frequency of the
model reviews shall be determined taking into consideration the design phase, rate of changes, schedule
of formal design reviews and size of the project.
Internal design review shall be conducted at least once a month. All internal technical issues should be
reviewed and resolved during the internal model reviews as much as possible. Any unresolved issues shall
be documented and presented during the following formal design review.
The Project PDMS Implementation Procedure shall contain the details and plans for the internal reviews.

E-7.0 Production of Deliverables - 2D Drafting

2D Drawings in a 3D project are just graphical representation of the 3D model. Drawings can be
generated for selected elements in a selected area with required representation style using PDMS draft
module.
Contractor shall use supplied back sheet, representation styles, and symbols to create the drawing. If a
particular symbol or style is not found, the same shall be created by the contractor.
PDMS intelligent texts shall be used to annotate or label line numbers, elevations, tag numbers or any
attribute data. Hard coded texts shall not be used instead of tag no’s. PDMS Automatic drawing
production (ADP) may be used for creating and updating drawings.
The following drawings shall be generated and maintained in PDMS draft module,
• Equipment layout, elevation with full annotations and equipment list.

• Piping plans, elevations and sections with annotations for major equipments and piping.
• Piping support arrangement drawings; with minimum annotations.
• Pipe support drawings
Since PDMS 2D drafting has its own limitations, many drawings can’t be completed without transferring
them to external 2D applications like AutoCAD. Enough care shall be taken not to lose the scaling or
dimensional information / intelligence transferred from PDMS. If possible the PDMS data shall be kept as
a block or external reference drawing (xref), so that revision updates from PDMS can be done easily.
The following drawings shall be generated from PDMS and may be transferred to external 2D packages
for annotations/modifications:
• Equipment / vessel nozzle orientation sketches.

• Structural framing plans, sections, elevations etc.
• E & I cable tray layouts
• Instrument location drawings
• Electrical layouts
• Safety drawings – Escape routes, Safety equipment location drawings
• HVAC duct layouts
E-7.1. Isometric Production

All piping isometrics shall be produced from PDMS Isodraft module. Design isometrics shall be
completely annotated with bill of materials. Contractor shall use supplied back sheet and option files to
generate the Isometrics with required modifications to suit the project. PDMS produced isometrics
SHALL NOT be edited externally.
PDMS plot files and DXF files for final issue of Isometrics shall be saved and maintained in project
folders. Isometric file names shall be named according to PDMS pipe name and sheet number.

Isometrics for Stress analysis purposes shall be generated from PDMS Isodraft. Necessary annotations
shall be done in external 2D applications.
Piping system isometrics shall be generated by using PDMS Isodraft. If Isodraft can’t handle complex
systems, such systems shall be broken down to simpler sub-systems for the purpose of Isometric
generation.
E-7.2. PDMS Fonts in AutoCAD

AutoCAD replaces unknown PDMS text fonts with AutoCAD standard fonts which will lead to text
overlaps or texts running off the title blocks. PDMS Autodraft fonts shall be mapped in AutoCAD to open
PDMS generated 2D drawings.
AutoCAD command ‘PREFERENCES’ is used to map fonts to support file search path. Click on ‘Add’
button and then ‘Browse’ button to select ‘Autodraftfonts’ subfolder in PDMS program folders. Restart
AutoCAD to open the drawings.
E-7.3. PDMS Reports

PDMS reporting feature shall be used to extract PDMS data in list and report format. Contractor shall
compose standard templates for these purposes and save them in project folder. PDMS reporting shall be
used for the following cases:
• Equipment lists
• PDMS line lists
• Inline instrument list
• Piping special item list
• Material take-off
• Center of gravity
• Weight control report
• Model Progress report
PDMS reporting can be used for many other reports. It’s the responsibility of the PDMS Administrator /
Coordinator to judge and guide for proper reporting.
E-7.4. Piping Material Take-Off

Piping material reporting is a critical part of any project since reporting should be accurate and free of
errors. MTO tolerances and allowances made in the design that are reflected in the Design Isometrics
should be taken care of in the reporting. The following are such example cases:
• Hook-up / site / field fit welding allowances

• Loose flange allowance
• Components switched off in Design - MTOC Off or DOTD etc.
• Pipes (TUBI) switched off in Design – MTOT Off or DOTD etc.

• Material references – MTOREF

• Bolt material
PDMS reporting feature from Design module can be used for limited reporting since it can’t take care of
above cases.
A comprehensive material reporting can be done by the use of PDMS Isodraft. Contractor shall use
PDMS Isodraft for all formal issue of Piping MTO.
Bolt materials shall be extracted by using Bolt reporting feature in Isodraft if a separate reporting is
required.
If Isometric generation is failing, then the material extraction will be incomplete. Log files generated shall
be checked for any fails or errors. It will be important to check inconsistencies (DATACON) or design
errors before extracting material using Isodraft. A cross-check of PDMS line list with MTO shall be done
to make sure that all PDMS lines are included in the MTO.
E-7.5. Weight and Center of Gravity

Weight and center of gravity reporting for offshore platforms shall be made by using PDMS reporting.
The following reports shall be generated from PDMS model:
• Structural – Structural model shall be as explained in section E-4.5.12. Report shall extract NWEI
and NCOFG.
• Equipments – All Mechanical Equipments / Packages shall have Weight attribute input and COG
marked. Report shall extract weight and COG sub equipment location.
• Piping – Piping fittings, SP Items, Instruments shall contain weights input in their specifications.
BRWEI and BRCOG shall be reported out to extract weight and COG respectively.
• Pipe supports – Pipe supports follow as in Structural modeling and reporting.
• E & I – E & I Equipments shall be similar to mechanical equipments to report Weight and COG.
Cable trays shall be similar to Pipes. Weight of cables shall be added to cable trays and with the
same COG.
• HVAC Ducts – Since HVAC is a parametric modeling using Aveva specification, weight should
be as per HVAC vendor drawings. Geometrical center of gravity can be reported from PDMS.
Any items that are not modeled in PDMS shall be listed and added by Discipline engineers who are
responsible for final reporting to Weight Control Report (WCR).

E-8.0 PDMS Global

PDMS Global is an extended feature of PDMS applications which allows multi-location engineering and
fabrication. PDMS Global automatically updates and synchronizes the databases in multiple locations.
PDMS Global shall be used in the following cases:
• Multi-location engineering
• Concurrent design engineering and fabrication engineering
A dedicated or shared communication link of minimum 2Mbps (megabytes per second) shall be used
between Hub and Satellite locations.
The following key notes shall be followed for Global projects:
• All Satellite locations shall be directly under Hub unless otherwise unavoidable.
• Corporate database need not be propagated.
• Frequency of database updates across locations shall be decided based on kind of work sharing
and phase of project.
• Unnecessary use of extract databases shall be avoided. Extracts shall be used if a single database
needs to be worked on two locations.
• Explicit claim type of extract databases shall be used. Owner or location UDA attributes shall be
used the control the claiming.
• All extract databases shall be issued daily or regularly.
• All locations shall do local backup of all databases.
Contractor need to submit a detailed plan / procedure to define the global activities and responsibilities
which shall include the following,
• Making the Project global

• Initialization of Hub
• Creation of locations
• Firewall configuration
• Global daemon – configuring the service
• Database allocation
• Update events
• Database de-allocation procedure
• Reconfiguring and Merging databases
• Synchronization of databases
• Deleting databases
• Database recovery
• Management of Transaction database
• Data Integrity checking
• Backing up databases
• Final model data transfer

E-9.0 Model data transfer

Contractor shall do periodical transfer of model data to COMPANY. The transfer shall include a Model
Register, Review Model and other pertinent data that are required to open, view and extract data from the
model.
Contractor shall include a Readme.txt (ASCII file) in the transfer which shall have administrative user
details and other useful instruction / information that should be followed to install the databases.
Contractor shall perform following check before a formal model transfer:
• Remove all irrelevant design data such as copy databases, study sites, temporary items etc.
• Remove / cleanup SPCOs from limbo specs.
• Perform Database Integrity Check (DICE) and fix errors.
• Merge and compact all databases
• Expunge all ghost users and cleanup database claim lists.
• Clash Report – make sure that there are no unapproved clashes.
• Datacon – make sure all PDMS pipes pass the consistency check.
E-10.0 Computer Hardware and Data Backup

PDMS Administrator and Coordinator have shared responsibility to recommend necessary hardware
specification for PDMS workstations.
User workstations shall be of minimum of below specification:
Any latest, 3.2GHz processor

4GB RAM, 120GB HDD,
128MB dedicated graphics memory
17” dual monitors
Contractor shall have a dedicated workstation for viewing Review Model with higher specification. It
shall have minimum 16GB RAM and 1GB graphics memory.
Aveva support web site shall be referred to select a compatible graphics cards.
PDMS Coordinator and Administrator are responsible to make a daily backup of PDMS databases. Daily
backups shall be kept a minimum of one month period. They shall also coordinate with IT backup
services to include PDMS projects under backup service.

Record of Change
Version 2.0.0 Date: 01/13
Location Action Description
Sections 1 Modifications & Addition of Reference: GP 12-01-02S, Upstream Border Sheet
Additions sizes & P&ID Symbols and Legend Sheets
Sections 2 Modifications Specification of applicable software. AutoCAD for 2D, and
PDMS for 3D.
Standard paper plot sizes.
Appendix D Additions Incorporated the Design Drafting Standard
Appendix E Additions Incorporated the PDMS Implementation Procedure
Section 1.2, Modifications “For Upstream Nigeria, Drawings will be in AutoCad 2000
Note (4); format”
Section 2.3, 1) Modifications Upstream Nigeria drawing size shall be Iso A1, (594mm x
841mm) versus “D” size and Iso A3, (297mm x 420mm) versus
“B” size
Location Action Initial Publish

GP 01-01-03S - Version 2.0.0 January 2013

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

GP 01-01-03S - Version 2.0.0 January 2013

Загружено:

Авторское право:

Доступные форматы

Upstream CAD Requirements

Drawings, Data, and System

4 FEED Contractor Deliverables ............................................................................. 8

5 EPC Contractor Deliverables ............................................................................... 8

6 Process Flow Diagrams (PFDs) ........................................................................... 9

7 Utility Flow Diagrams (UFDs) ............................................................................... 9

8 Piping and Instrumentation Diagrams (P&IDs) ................................................... 9

9 Line List ................................................................................................................. 9

Appendix A: Typical Representation of Instrumentation and Control Equipment

Appendix B: CAD Deliverables ................................................................................... 9

Appendix C: Checklist for Project Specifications ..................................................... 9

[Addition] Appendix-D: Detail Drafting Standard Process Description.................... 10

D-1. Drafting Standard Process Description ............................................................ 10

Upstream For ExxonMobil Use Only

Page 2 of 76 Upstream Nigeria Version 2.0.0

D-1.8. Drawing Orientation .................................................................................... 19

E-1.0 Purpose ..................................................................................................... 33

Upstream For ExxonMobil Use Only

Page 3 of 76 Upstream Nigeria Version 2.0.0

E-1.7. Creation of the PDMS Project .................................................................... 37

Upstream For ExxonMobil Use Only

Page 4 of 76 Upstream Nigeria Version 2.0.0

E-4.5.8. Columns .............................................................................................. 54

Upstream For ExxonMobil Use Only

Page 5 of 76 Upstream Nigeria Version 2.0.0

E-7.3. PDMS Reports............................................................................................ 72

Upstream For ExxonMobil Use Only

Page 6 of 76 Upstream Nigeria Version 2.0.0

Table 1.1 – References

GP 12-01-01S Upstream Numbering System for Project Documents Supplements

[Modification] ExxonMobil Upstream Engineering Drawing Standards

Upstream PIDs - Symbols Typical Piping and Instrumentation Diagrams -

Upstream For ExxonMobil Use Only

Page 7 of 76 Upstream Nigeria Version 2.0.0

2 General CAD Systsem, Tag-centric Data, and Drawing

2.2 [Modification] CAD System

2.3 [Addition] CAD Drawings

3 Identification and Numbering

4 FEED Contractor Deliverables

5 EPC Contractor Deliverables

Upstream For ExxonMobil Use Only

Page 8 of 76 Upstream Nigeria Version 2.0.0

6 Process Flow Diagrams (PFDs)

7 Utility Flow Diagrams (UFDs)

8 Piping and Instrumentation Diagrams (P&IDs)

Appendix A: Typical Representation of Instrumentation and

Appendix B: CAD Deliverables

Appendix C: Checklist for Project Specifications

Upstream For ExxonMobil Use Only

Page 9 of 76 Upstream Nigeria Version 2.0.0

[Addition] Appendix-D: Detail Drafting Standard Process

D-1. Drafting Standard Process Description

D-1.1. Drawing Number

Upstream For ExxonMobil Use Only

Page 10 of 76 Upstream Nigeria Version 2.0.0

D-1.2. Border Sheet

Figure 1.1 - Typical Border Sheet

D-1.3. Title block contents

Upstream For ExxonMobil Use Only

Page 11 of 76 Upstream Nigeria Version 2.0.0

D-1.4. Title Block

Drafting personnel must ensure that:

Figure 1.2 - Drawing Title Block

Title 1 – Drawing Type