AD274 732 G 00006 - Rev.3

FEED & EPC COMPETITION FOR BELBAZEM BLOCK
FIELD DEVELOPMENT PROJECT

3D PDMS MODELLING PROCEDURE
COMPANY Project No.
AD274
COMPANY DOC. No. AD274-732-G-00006 Rev. 3
CONTRACTOR Project No.
P8353 CONTRACTOR DOC. No. 8353-E-PD-0001 Rev. 3
SUMMARY OF DOCUMENT REVISIONS

Rev. Date Section
Revision Description
No. Revised Revised
1 31/03/2019 N/A Issued for review
2 15/05/2019 Issued for Approval
3 19/06/2019 Issued for Design
2 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

COMPANY Project No.
AD274
TABLE OF CONTENTS
1. INTRODUCTION................................................................................................................... 5
2. PROJECT OBJECTIVE ........................................................................................................ 5
3. PROJECT SCOPE ................................................................................................................ 5
4. ABBREVIATIONS AND DEFINITIONS................................................................................. 6
4.1 ABBREVIATIONS ........................................................................................................................... 6
4.2 DEFINITIONS................................................................................................................................ 7
5. PROJECT CODES AND STANDARDS ................................................................................ 7
6. REFERENCE DOCUMENTS ................................................................................................ 8
7. RESPONSIBILITIES ............................................................................................................. 8
7.1 PDMS ADMIN ............................................................................................................................. 8
7.2 DESIGNER / CHECKER IS RESPONSIBLE FOR: ................................................................................ 9
8. RESPONSIBILITIES ............................................................................................................. 9
9. PROJECT DISTRIBUTION / ORGANIZATION ................................................................... 12
9.1 PROJECT ENTITIES NAMING .......................................................................................................12
9.2 SITE NAMING .............................................................................................................................15
9.3 DB TYPE...................................................................................................................................16
9.4 DISCIPLINE CODE ......................................................................................................................16
9.5 ZONE NAMING ...........................................................................................................................17
10. PROCEDURES AND PRACTICES ..................................................................................... 21
10.1 SOFTWARE WITH VERSIONS .......................................................................................................21
10.2 W ORKING UNITS........................................................................................................................21
10.3 MATERIAL CONTROL ..................................................................................................................22
11. AS-BUILTING ..................................................................................................................... 22
12. MODEL ORIGIN - COORDINATE SYSTEM ....................................................................... 22
13. PDMS ISO NUMBER. FORMAT ......................................................................................... 24
14. DRAFT ................................................................................................................................ 24
15. MODEL STATUS/INTER-DISCIPLINE CHECK .................................................................. 24
15.1 MODELING PROGRESS / REVIEW ................................................................................................24
15.2 TYPE OF REVIEW .......................................................................................................................26
16. MODELLING OF ONSHORE FACILITY ............................................................................. 26
16.1 SITE NAMING .............................................................................................................................26
16.2 PIPING MODELING .....................................................................................................................26
16.3 CIVIL & STRUCTURAL MODELING ................................................................................................37
16.4 ELECTRICAL MODELING .............................................................................................................39

COMPANY Project No.
AD274
16.5 INSTRUMENTATION MODELING....................................................................................................41

16.6 TELECOM MODELING .................................................................................................................43
16.7 W ORKING PRACTICES ................................................................................................................45

COMPANY Project No.
AD274
1. INTRODUCTION
The Al Yasat Petroleum Operations Company Ltd (COMPANY) is a joint venture between Abu Dhabi
National Oil Company (ADNOC) and China National Petroleum Corporation International - Hong Kong
(CNPCI). Belbazem Block fields are the fields in offshore concession area of COMPANY.
Belbazem Block fields consists of three oil bearing structures viz. Belbazem, Umm Al Salsal and Umm Al
Dholou, located 20-50 km from Zirku Island as shown in Figure 1. These fields are located 120 km to the
Northwest of Abu Dhabi.
Figure 1 – Facility Location
2. PROJECT OBJECTIVE
The objective of the PROJECT is to achieve safe and economic oil production of 45 MBD (annual
average) with Stream Day Production Rate as 120% of Plateau Production, accounting for well & facility
downtime from Belbazem Block Fields, while maintaining reservoir pressure support with water
injection. First oil targeted in Q1 2021.
3. PROJECT SCOPE
The scope of the PROJECT is to develop the FEED SERVICES for the Belbazem Block Field
Development. The Belbazem Block field development project shall encompass three wellhead towers
(WHT) located at the Belbazem (WHT-BB), Umm Al Dholou (WHT-UAD) and Umm Al Salsal (WHT-UAS)
locations. These shall deliver production fluids to new onshore facilities at Zirku Island adjacent to the
existing SARB plant. These new facilities shall process oil, gas and water streams for export via the
existing Satah Al Razoot (SARB) plant export/disposal routes.

COMPANY Project No.
AD274
Water injection facilities shall be provided to deliver pressure support to the Belbazem Block reservoirs.
The development concept is schematically depicted in Figure 2 below:
Figure 2 – Development Concept
4. ABBREVIATIONS AND DEFINITIONS
4.1 Abbreviations
ADNOC Abu Dhabi National Oil Company

EPC Engineering, Procurement & Construction
FEED Front End Engineering Design
PD Project Director
SPM Senior Project Manager
PM Project Manager
PQAM Project Quality Assurance Manager
PHSEM Project Health, Safety and Environment Manager
SPEM / PEM Senior Project Engineering Manager / Project Engineering Manager
QCP Quality Control Procedure
DC Documents Controller
ITP Inspection Test Plan
PO Purchase Order
COMPANY Project No.
AD274
NDMS NPCC Document Management System

EDMS Electronic Document Management System
PDMS Plant Design Management System
Administrator PDMS / Clash Manager Administrator
CAD Computer Aided Design
MDB Multi Database
MDS Multi-Discipline Supports
NW NavisWorks
PSV Pressure Safety Valve
VPRM Vantage Plant Resource Management
WBS Work Breakdown Structure
4.2 Definitions
The Following definitions apply to terms used within this document:
COMPANY Al Yasat Petroleum Operation Company Limited (Al Yasat)
PROJECT FEED and EPC Competition for Belbazem Block Field Development
Project
PMT Project Management Team
PMC Project Management Consultant appointed by the COMPANY to provide

Project Management Consultancy services for the PROJECT
SERVICES means the works and services to be performed under the

AGREEMENT, as further described in the SCOPE OF SERVICES and
which includes provision of the FEED DOCUMENTATION and any other
deliverables specified in the AGREEMENT (including the EPC BID).
SUBCONTRACTOR means any PERSON to whom execution of any part of the SERVICES
is subcontracted by the CONTRACTOR or to whom the CONTRACTOR
proposes to subcontract any part of the EPC WORKS if awarded the
EPC CONTRACT, and includes the legal successors or permitted
assigns of such person.
CONTRACTOR FEED/Design competition Contractor appointed by COMPANY to

perform SCOPE OF SERVICES for the PROJECT.
VENDOR Person, firms, partnerships, companies, bodies, entities or a

combination thereof who are providing GOODS
For all other Definitions refer to General Terms and conditions of the AGREEMENT.
5. PROJECT CODES AND STANDARDS
CONTRACTOR shall comply and ensure compliance from its SUBCONTRACTORS with UAE
Legislation and Environmental Regulations, applicable internationals Laws & Regulations, ADNOC

COMPANY Project No.
AD274
Guidelines/Codes of Practice, COMPANY Specifications and Standards, COMPANY HSE Regulations

and Standards, and relevant International Codes & Standards.
Only latest versions of all applicable Codes, Specifications & Standards shall be used by the
CONTRACTOR and SUBCONTRACTORS.
Where equal but conflicting requirements are identified between regulations, codes and standards,
the order of precedence shall be:
1. UAE Statutory Legislation and Regulations
2. ADNOC HSE Regulations, Standards and Codes of practice
3. ADNOC Offshore HSE Regulations
4. Project Data Sheets
5. Project Specifications and Standards
6. Approved Amendments to ADNOC Offshore Engineering Specifications, Standards and
Procedures
7. ADNOC Offshore Engineering Specifications, Standards and Procedures
8. ADNOC Offshore Guidelines, Procedures & Codes of Practice
9. International Codes & Standards
6. REFERENCE DOCUMENTS
Reference shall be made to the following documents:
DOCUMENT NUMBER DESCRIPTION

COMPANY AGREEMENT Number AY/PE/01/2018
AD274-732-G-00002 (8353-A-PD-0001) Engineering Execution Plan

AD274-732-G-00004 (8353-A-PR-0001) Engineering Deliverable Register
Codes of Practices for Plant Design (CP-
CP-00 Rev. 1a
00 Rev. 1a)
AD274-732-G-00003 (8353-E-PD-0002) 3D PDMS Model Review Procedure
A0-ENG-N-SL-001 Rev.2 Status list for Technical Standards
7. RESPONSIBILITIES
7.1 PDMS Admin

 The PDMS administrator is responsible for:
 Establishing reference coordinate and datum system
 Creation of project Areas and Models.
 Establishing file naming conventions as per ADNOC/ COMPANY procedure.

COMPANY Project No.
AD274
 Preparation and loading of specs, catalogues and libraries.

 Creation of Pipe Supports as per project Pipe Support Standard.
 Responsible for checking that PDMS Spec database is in line with the AFC PMS, valve
datasheets, etc.
 Creation and management of catalogue/spec component request and source for piping
component dimensional information.
 Drawing and Isometric Setup in compliance to CP-00
 Creation and updating the Design review Sessions.

 Running different type of reports like: clash reports, MTO reports, etc at periodic intervals.
 Backup and retrieval of the models.

 Create all applicable attributes required for data extraction and isometric generation.
 Interfacing with Information Technology Manager for technical hardware.
 Maintaining the Catalogue/Spec log and its follow-up.
 Ensure that all model review files are updated daily.
7.2 Designer / Checker is Responsible for:
 Reviews and updates the model with respect to the latest inputs, clash free environment, plant
operations and maintainability and maintainability inspects ability, and access for corrosion
monitoring.”
 Extracting the drawing/isometrics & annotation.
 Resolving clashes.
 Runs data consistency checks.
 Manages engineering interface between various disciplines.

 Ensures drawings issued for IDC & AFC are updated in the model and are clash free.
 Ensures compliance to CP-00 and other relevant standards and specifications.
 Ensures attributes are populated with relevant data.
 Accurate 3D Modelling and data input as required by each discipline
8. RESPONSIBILITIES
MODELING RESPONSIBILITIES
Structural Discipline
 PDMS modeling shall include all details for which FEED engineering drawings are generated
including standard details.

COMPANY Project No.
AD274
 Primary and Secondary and tertiary steelwork like jacket legs, cones, piles, mud mats, stringers
etc.,
 Floor plate including penetrations, Sleeves.
 Stairs, Ladders, Hand Rails, Plating, Grating, holding chains, swing ropes.
 Helideck with all markings, obstacle sector volumes, safety nets etc.
 Equipment Supports, Valve access platforms, secondary access platforms Mobile platforms,
Special Pipe Supports etc.
 Material handling equipment such as Monorails, Pad eye, Pulling Posts beam clamps, hatches
etc.
 Reserve volumes for all installation activities, material handling activities and tolerances, etc..,
 Jacket modeling including all attachments, nodes, clamps, guides etc.
 Hatches, access opening with protective barriers.
 LER’s and technical building.
 Special supports for pipe, Tray & HVAC, equipment supports.
Piping Discipline
Equipment
 All Itemized Equipments With logical equipment origin.
 Packaged items shall be modelled as Box volume
 All Nozzles and manhole covers as per P&ID.
 Withdrawal areas and dropout zones for main equipments as as box volume.
 Access volume and swing volume to be modeled as Box volume.
 Davit for manhole covers and heavy flanges.
 Space requirement for Door/Hinged closure/Manhole opening to be modeled as soft envelopes.
 Envelops for Operation, maintenance, Hoist movement, Material Handling ways, laydown
areas, Drop zones & Storages areas.
 Access Platforms connected to the vessels.
Piping
 4” & above size as per the approved P&ID and line list, PMS, Deck layout drawings, datasheets,
and insulation specifications, etc.
 4” & above size in-line items to be modeled and tagged, Control valves, Actuators, Safety valves,
drains and vents, instrument connections like PI, TI etc.
 Vessel trims piping as Box volume
 Insulation/Personnel protection to be modeled.
 4” & above size Pipe supports.
 Bolts removal envelops to ensure no captive bolts and space for torqueing / tensioning
equipment.
 Conductors / risers
COMPANY Project No.
AD274
 Temperature Gauges and Corrosion coupons to be modeled with the soft envelope.
 Temporary Conductors/Risers (deck level) which will be modeled permanently by
structure discipline later stage of the project.
 Material handling equipment & material handling volume blocks based on the material handling
studies to avoid all clashes/hazards. Accessibility volumes for operation and maintenance.
 Soft envelops for future facilities, retrieval tools, etc.
 4” & above size piping shall be modeled as one Pipe as per P&ID line number. The pipe shall be
owned by the Zone in which it originates and run continuously to its final destination, as per the
P&ID
 For quarter turn valves, leaver orientation envelope shall be modeled as soft envelopes.
 All maintenance / operational volumes shall be modeled as box volumes. This includes as
minimum laydown areas, primary and secondary escape routes, doors, material handling ways,
monorail trolleys movement, hatches etc.
Architectural Discipline
 All buildings complete with walls, doors / windows and opening swing Volume.
 Fire, smoke & gas detectors, Control Panels.
E&I Discipline
 All E&I equipment, Radio mast/tower
 Electrical and Instrument items and Telecom.
 Electrical and Instrument cable trays and tube trays.
 Cable tray supports and tube trays.
 Local Panels such as HSSS, SDB’s, LCP’s (if any).
 Panel door opening space and all around space requirement if any to be modeled as soft
envelopes.
 Junction boxes / marshaling boxes, Distribution box, termination box, Analyzer panels,
Instrument stanchions, air volume tanks etc.
 Offline field instrument and instrument supports / shade.
 Telecom devices in LER & outdoor & equipment supports in LER & switchgear room.
 Accessories for valve actuators. J-tube.
 Lighting fixtures, power sockets, switches, Nav-aid.
 CCTV equipment including cameras, stands, PA systems, beacons, wash bottles, telephones
etc.
HVAC:
 HVAC Ductwork
 HVAC Equipment, Piping with in-line items / accessories.
 All supports and insulation.
 Chilled water piping, including pipe supports, in-line items, and accessories.
 Ductwork and chilled water piping insulation outline.
 Chilled water valves and gauges, instruments, valve actuators.
COMPANY Project No.
AD274
 Motorized dampers, including damper actuators.

 HVAC power and control panels, duct & pipe insulations
HSE Discipline
 Itemized Equipments (Includes Safety, evacuation, Clean Agent Piping & Firefighting equipment,
Safety equipment, Life Boats, Monorail, Davits for life rafts, Life Buoy etc.).
 Escape route volume with indicators to be modeled as as Box volume.
 Electrical and Instrument Items Including Fire & Gas devices (Sounder, Flashing Beacons) PA
system, Telecom.
 Fire water spray network deluge
 Windsock(s).
 Firefighting system fire ring main routing, hydrants, block valves, fixed water monitors, and hose
reels, foam skid and deluge valve manifolds.
 Safety showers and eye wash fountains.
 Safety signs, and muster area.
 Electrical discipline modeling responsibilities.
 Civil & underground discipline missing add with all the required details for COMPANY’s review.
Civil & Structural:

 Foundations – Buildings, Equipment’s, Shelters etc.,
 Structural steel – Primary members
 Grating & Chequered plate
 Technological structures, Pipe racks
 Stair Case
 Ladders and Safety Cages
 Mono rail beams
 Access platforms, Handrails & Ladders.
 Shelter and Buildings
 Equipment pit
 Grading, Embankments, Roads, Fencing, Gates & Drainage network
9. PROJECT DISTRIBUTION / ORGANIZATION

This section describes in detail the PDMS project set-up and also describes the naming convention
which will be followed throughout the project.
9.1 Project Entities Naming

9.1.1 WHT UAS,UAD & BB
One MDBs is created for each platform.

COMPANY Project No.
AD274
MDB’s:
MDB Name MDB Description
UAS UAS WELLHEAD TOWER
UAD UAD WELLHEAD TOWER
BB BB WELLHEAD TOWER
The following are the project Design, Draft DB’s (names, description, type and numbers):
DB’s:
DB Name DB NUMER DB Description TYPE
uasDESEQUI01 60000 DB For UAS-Wellhead Tower- Equipment DESI
uasDESSUPP01 60010 DB For UAS-Wellhead Tower Support DESI
uasDESHVAC01 60020 DB For UAS-Wellhead Tower HVAC DESI
uasDESHSE01 60030 DB For UAS-Wellhead Tower Safety DESI
uasDESINST01 60040 DB For UAS-Wellhead Tower Instrument DESI
uasDESELEC01 60050 DB For UAS-Wellhead Tower Electrical DESI
uasDESARCH01 60100 DB For UAS-Wellhead Tower Acrhitecture DESI
uasDESPIPE01 60101 DB For UAS-Wellhead Tower - Piping DESI
uasDESSTRU01 60111 DB For UAS-Wellhead Tower – Structures DESI
uasDESJCKT01 60111 DB For UAS-Wellhead Tower – Jacket DESI
uasDRASUPP01 60541 Draft DB For UAS-Wellhead Tower Support PADD
uasDRAINST01 60531 Draft DB For UAS-Wellhead Tower Instrument PADD
uasDRAELEC01 60521 Draft DB For UAS-Wellhead Tower Electrical PADD
uasDRASTRU01 60511 Draft DB For UAS-Wellhead Tower Structure PADD
uasDRAPIPE01 60501 Draft DB For UAS-Wellhead Tower Pipe PADD

uadDESEQUI01 70000 DB For UAD-Wellhead Tower- Equipment DESI
uadDESSUPP01 70010 DB For UAD-Wellhead Tower Support DESI
uadDESHVAC01 70020 DB For UAD-Wellhead Tower HVAC DESI
uadDESHSE01 70030 DB For UAD-Wellhead Tower Safety DESI
uadDESINST01 70040 DB For UAD-Wellhead Tower Instrument DESI
uadDESELEC01 70050 DB For UAD-Wellhead Tower Electrical DESI
uadDESARCH01 70100 DB For UAD-Wellhead Tower Acrhitecture DESI
uadDESPIPE01 70101 DB For UAD-Wellhead Tower - Piping DESI
uadDESSTRU01 70111 DB For UAD-Wellhead Tower – Structures DESI
uadDESJCKT01 70111 DB For UAD-Wellhead Tower – Jacket DESI

COMPANY Project No.
AD274
uadDRASUPP01 70541 Draft DB For UAD-Wellhead Tower Support PADD

uadDRAINST01 70531 Draft DB For UAD-Wellhead Tower Instrument PADD
uadDRAELEC01 70521 Draft DB For UAD-Wellhead Tower Electrical PADD
uadDRASTRU01 70511 Draft DB For UAD-Wellhead Tower Structure PADD
uadDRAPIPE01 70501 Draft DB For UAD-Wellhead Tower Pipe PADD
bbDESEQUI01 80000 DB For BB-Wellhead Tower- Equipment DESI
bbDESSUPP01 80010 DB For BB-Wellhead Tower Support DESI
bbDESHVAC01 80020 DB For BB-Wellhead Tower HVAC DESI
bbDESHSE01 80030 DB For BB-Wellhead Tower Safety DESI
bbDESINST01 80040 DB For BB-Wellhead Tower Instrument DESI
bbDESELEC01 80050 DB For BB-Wellhead Tower Electrical DESI
bbDESARCH01 80100 DB For BB-Wellhead Tower Acrhitecture DESI
bbDESPIPE01 80101 DB For BB-Wellhead Tower - Piping DESI
bbDESSTRU01 80111 DB For BB-Wellhead Tower – Structures DESI
bbDESJCKT01 80111 DB For BB-Wellhead Tower – Jacket DESI
bbDRASUPP01 80541 Draft DB For BB-Wellhead Tower Support PADD
bbDRAINST01 80531 Draft DB For BB-Wellhead Tower Instrument PADD
bbDRAELEC01 80521 Draft DB For BB-Wellhead Tower Electrical PADD
bbDRASTRU01 80511 Draft DB For BB-Wellhead Tower Structure PADD
bbDRAPIPE01 80501 Draft DB For BB-Wellhead Tower Pipe PADD
9.1.2 BOF
One MDB is created for the Belbazem Onshore facility
MDB’s:
MDB Name MDB Description
BOF BELBAZEM ONSHORE FACILITY

COMPANY Project No.
AD274
Db Naming Convention shall be as per below
DB name:
PIPE / DESI_501_CIU
Unit / Service Code (i.e. CIU = Chemical Injection Unit - Refer table
below)
Area Code (code for plant name as per ADMA-OPCO convention ,

Refer table below)
PDMS Activity (i.e. DESI = Design, DRA = Draft, etc.)
Discipline (i.e. PIPE = Piping, STRU = Structural, etc.)
DB Description: Piping Design DB for Compression Platform Chemical Injection Unit
S. Unit
No. MDB Code Area Description Area Code
1 BOF 604 BB Produceed Water Treatment PWT
2 BOF 615 BB Utility Water (SWRO) SWR
3 BOF 622 BB Power generation (GTG) GTG
4 BOF 623 BB Hot Oil System (Optional) HOS
5 BOF 732 Belbazem Onshore Facility BOF
6 BOF 733 Belbazem Water Injection Facility WIP
Belbazem Well Fluid Pig Receiver and
7 BOF 734 MPFM PTA
8 BOF 735 Switchgear, Substation SSN
9 BOF 601 Existing Pipe rack in SARB EPR
Existing Pipe Sleeper/Rack and Tank
10 BOF 625 farm EPS
DB Area numbers are maintained as default. (000)

The range of DB numbers used for PROJECT setup are mentioned below
Piping Design DBs / Draft DBs – 500 to 599
Civil & Structural , UG Design DBs / Draft DBs – 600 to 699
Instrumentation & Telecom Design DBs / Draft DBs – 700 to 799
Electrical Design DBs / Draft DBs – 800 to 899
Project Library DBs – 400 to 499
9.2 Site Naming
Sites shall be created and named in line with the respective DB for all disciplines with the Datum
Point and Purpose set for it. Site naming shall be in the following format:

COMPANY Project No.
AD274
Site Name: = XXXPIPE

Where PIPE = Discipline Code
XXX = Area number / MDB name
E.g. name of Site for Piping in uas area (BHD Wellhead Tower Platform) shall be:
/ uasPIPE.
9.3 DB Type
Data Base Type Abbreviation

Design (DESI) DES
Draft (PADD) DRA
Catalogue (CATA) CAT
Properties (PROP) PRO
Dictionary (DICT) DIC
ISODRAFT (ISOD) ISO
Schematic (SCHE) SCH
Engineering (ENGI) ENG
9.4 Discipline Code
Sr. No. Discipline Description Codes

.1 Structure (topside) Structural Discipline STRU
2 Structure (Jacket) Structural Discipline JCKT
3 Architecture Architecture ARCH
4 Civil, Structural & UG Civil CIVL
5 Support Support SUPP
6 Equipment Mechanical Discipline EQUI
7 Piping Mechanical Discipline PIPE
8 Instrumentation Instrumentation Discipline INST
9 Electrical Electrical Discipline ELEC
10 HVAC HVAC HVAC
9 Safety HSE discipline HSE
10 General General Purpose GEN
PDMS Administration
11 Catalogue CATA
Discipline

COMPANY Project No.
AD274
9.5 Zone Naming
Zone naming is discipline based and will vary as per the discipline need. All zones created shall be
named appropriately and to follow the explained convention.
9.5.1 Pipe Zone Naming
All pipes shall be modeled in proper zone which is based on process service code. The zone name
shall be as follows:
/uasPIPE/NNNN e.g. /uasPIPE/CO

Process Service Code
Site Name (Area Number + Discipline Code)
E.g. Pipe having service code “CO” shall be created in zone /uasPIPE/CO.
Detailed hierarchy as follows:
Site > /uasPIPE
Zone> /uasPIPE/CO
Zone> /uasPIPE/LO
Zone> /uasPIPE/PW
> /CO-16”-AC0NA0-1234AD
> /CO-18”-AC0NA0-2345AD
> /CO-20”-AC0NA0-3456AD

COMPANY Project No.
AD274
9.5.2 Equipment Zone Naming
All mechanical equipment (with proper origin) shall be modelled under equipment zone which shall
be deck based. Where equipment crosses into multiple decks it shall be modelled under deck on
which it rests. The zone naming shall be as follows:
uasEQUI/NNNN e.g. /uasEQUI/Deck name

Deck name (where necessary)
Site Name (Area Number + Discipline Code)
Future equipment shall be created in separate zone as follows:
/uasEQUI/FUTURE e.g. /uasEQUI/FUTURE
Site name
Detailed hierarchy as follows:

/uasEQUI/DECK NAME For modelling Mechanical equipment.
/uasEQUI/PACKAGE: For modelling Mechanical package unit.
Detail Hierarchy for structure are as follows:

Site > /uasEQUI
Zone> /uasEQUI/MAINDECK
Zone> /uasEQUI/PACKAGE
/EQUI> /uas-C-1234
NOZZ> /uas-C-1234/N1 /EQUI> /uas-P-1234
NOZZ> /uas-C-1234/N2 /EQUI> /uas-T-1234
SUBE> /uas-C-1234/Platform-Clips /EQUI> /uas-V-1234
SUBE> /uas-C-1234/Ladder-Clips
SUBE> /uas-C-1234/Supp-Clips
SUBE> /uas-C-1234/Earthing-Boss
SUBE> /uas-C-1234/Name-Plate
SUBE> /uas-C-1234/Fixed-Saddle
SUBE> /uas-C-1234/Sliding-Saddle
SUBE> /uas-C-1234/Davit-XXX (Each davit to be SUBE and named appropriately)
SUBE> /uas-C-1234/Boot
SUBE> /uas-C-1234/Rein-Pad
SUBE> /uas-C-1234/Insulation
SUBE> /uas-C-1234/Access-Way/ Platfrom
SUBE> /uas-C-1234/Reserved-Volume
SUBE> /uas-C-1234/Reserved-Volume: Area /volume required/ reserved for operation and

maintenance of the equipment.
9.5.3 Nozzle Naming
Nozzle names shall be equipment tag/nozzle number. e.g. /uas-C-1234/N1

COMPANY Project No.
AD274
9.5.4 Civil/UG/Structure Zones
Zone naming for Civil/ Structure shall be as follows:
/uasSTRU/HELI DECK: Abbreviation HDK

/uasSTRU/VALVE ACCESS DECK: Abbreviation VAD.
/uasSTRU/STRUCT: Abbreviation MDK
/uasSTRU/CELLAR DECK: Abbreviation CDK

Site > /uasSTRU
Zone> /uasSTRU/ MAIN DECK
/STRU>MDK/STRUCTURE For modelling main structure.
/STRU>MDK/SUPPORT For modelling all supports.
/STRU>MDK/LAD-STAIR For modelling ladder & staircase.
/STRU>MDK/HANDRAIL For modelling handrail.
/STRU>MDK/GRATING For modelling grating/ flooring.
Deck abbreviations shall be

used at /STRU> level and below
/FRMW>MDK/BEAM
/FRMW>MDK/BRACING
/FRMW>MDK/HANDRAIL
All sections (SCTN) under framework shall be properly tagged.

Items like stiffeners shall be clubbed together and created under sub-framework and tagged
appropriately (as per the structure they belong to).
Similar convention shall be followed for Jacket.

COMPANY Project No.
AD274
9.5.5 Electrical Zones

Zone naming for Electrical shall be as follows:
/uasELEC/CABLE_TRAY-HI: For modelling Electrical high voltage cable tray.
/uasELEC/CABLE_TRAY-LO: For modelling Electrical low voltage cable tray.
/uasELEC/EQUI-Deck Name: For modelling Electrical equipment (Transformer, Panels,
DB, Bus duct etc.) based on deck.
/uasELEC/SMALL-POWER-EQUIP: For modelling Electrical lighting fixture & poles etc.
/uasELEC/EHT-SYSTEM: For modelling Electrical heat tracing equipment.
Local Control Stations (LCSs), NAV AIDS
Site > /ELECuas
Zone> /uasELEC/CABLE_TRAY-HI
Zone> /uasELEC/CABLE_TRAY-LO
Zone> /uasELEC/EQUI-Deck Name /PIPE> CABLE_TRAY-HI-150
/PIPE> CABLE_TRAY-HI-200
Local Control Stations (LCSs), NAV AIDS
/STRU> DBs
/STRU> RTU
/STRU> PANELS
/STRU> TRANSFORMER
/STRU> SWITCH-GEAR
All equipment shall be created with proper origin.
9.5.6 Instrument Zones

Zone naming for Instrument shall be as follows:
/uasINST/F&G: For modelling fire and gas detector.
/uasINST/EQUI: For modelling instrument equipment.
/uasINST/TEL-EQUIP: For modelling telecom equipment, CCTV, PA system.
/uasINST/MANIFOLD: For modelling instrument air manifold.
/uasINST/CABLE-TRAY: For modelling instrument cable tray.
/uasINST/V-BOTTLE: For modelling Volume bottle.

Site > /uasINST
Zone> /uasINST/CABLE_TRAY
Zone> /uasINST/EQUI
/PIPE> CABLE_TRAY-150
/STRU> JBOX
/STRU> MBOX
/STRU> LOC-PANEL
/STRU> ANA-PANEL
/STRU> STANCHIONS

COMPANY Project No.
AD274
9.5.7 Safety Zones
Zone naming for HSE shall be as follows:
/uasHSE/EQUI: For modelling fire fighting & safety equipment.

/uasHSE/ESCAPE-ROUTE: For modelling escape routes.
/uasHSE/LAYDOWN: For modelling laydown area.
/uasHSE/ACCESS: For modelling access and maintenance volume.

Site > /uas HSE
Zone> /uasHSE/EQUI
/EQUI> Lifeboat-001(assigned tag shall be used)

/EQUI> Lifebouy-001
Equipment Origin:
All equipment shall have a logical origin which can aid in its placement. Following are examples of
origin for some equipment.
Horizontal Vessel - Centre of tan line near fixed support.

Vertical Vessel - Centre of bottom tan line.
Heat Exchanger - Intersection of heat exchanger centerline and inlet/ outlet nozzle.
E&I Cabinets/ Panels - Centre bottom of panel.
10. PROCEDURES AND PRACTICES
The following sections describe the configuration of PDMS stations, software used and general
procedures to be used in the preparation of 3D model.
10.1 Software with Versions

Operating System : Windows 7, Service Pack 1
PDMS : Version 12.1.SP4
MDS : Version 12.1.SP4/In house supporting modelling software
Naviswork : Autodesk Navisworks Simulate 2014
Version: 10.0.0.84082
10.2 Working Units
The following units shall be used:
Nominal Pipe Size : inches
Unit’s length : mm
Angle : degree
COMPANY Project No.
AD274
10.3 Material Control

The unique material Commodity Codes from our Material Management System (PROMAT) is
incorporated into PDMS model so that BOM is extracted from any hierarchy of the model into our
fabrication spool generator software (Spoolgen); the spool-wise BOM is extracted from Spoolgen and
loaded into our Material Management System.
11. AS-BUILTING
During execution of the PROJECT, certain changes may be carried out by the erecting group in
order to avoid the undetected interference, to accommodate material substitution to suit site
conditions.
All marked drawings (isometric, GAD etc.) with site changes are handed over to engineering for
updating the 3D PDMS model.
12. MODEL ORIGIN - COORDINATE SYSTEM
The project monument for WHT UAS ,UAD,BB shall be defined as follows while creating the project
and shall not be changed for the duration of the project.
Wrt*
Northing = 100000.000
Easting = 100000.000
Elevation = 0.000

COMPANY Project No.
AD274
Platforms:
For all Platforms Model, the South-West coordinate of the Jacket at TOJ (Top of Jacket) shall be
considered at
Northing = 100000 mm
Easting = 100000 mm
Elevation = Actual Elevation from MSL (Mean Sea Level) 0.0 @ MSL
(PLANT NORTH)
NORTHING 100000 MM
EASTING 100000 MM
ELEVATION Actual Elevation
Note: With a separate MDB for each unit.
The project monument for BOF (Belbazem Onshore facility):

Wrt*
Northing = 2000.000m 2,753,735.000 (UTM)
Easting = 2000.000m 708,065.000 (UTM)
Elevation = 100.000m 26.850 Local Chart Datum (LCD)

COMPANY Project No.
AD274
13. PDMS ISO NUMBER. FORMAT
Pipe naming in PDMS shall be as per P&ID tag which will also be the Isometric drawing number (this
is a condition, consider deletion)
PDMS ISO no. will be in the following format.
XX-XX-XXXX-XXXX
Line Seq. No
Spec. Name
Line Size
Fluid Code
14. DRAFT
DRAFT is the drawing production module of the AVEVA PDMS platform. It allows the user to
generate fully annotated engineering drawings directly from data in the 3D design model, created
from the DESIGN module. Drawings can be easily updated to reflect changes in the design model.
All layouts shall be extracted from the model. Dimensioning & annotation shall be done in draft and
shall be intelligent. The extent of annotation and quality of the drawing shall be as per CP-00 part 3.
Zone based layers shall be created and all items within the zone shall be placed in the same layer.
The DRAFT database is a tree structure, which for reference purposes is illustrated in DRAFT
Database.
The World is the top element. The next level down in the structure is a Department. The World can
own several Departments, which are known as its Members, and the World is known as the Owner of
the Departments.
Departments will own project Registries, which will own Drawings, which will own Sheets.
15. MODEL STATUS/INTER-DISCIPLINE CHECK

15.1 Modeling Progress / Review
Model will be checked against line list and P&ID for it’s completeness.
Monthly review will be conducted by PEM to check the progress and same will be reflected on
progress report.
3D-CAD Design Review shall be performed using a large screen having a high resolution.
Navisworks software will be used to ‘Walkthrough’ the model. Each unit or section to be reviewed
shall be of a manageable size such that no undue time is lost generating the views.
COMPANY Project No.
AD274
Plot plan drawing, PFDs, VENDOR Package Drawings and P&IDS that have been used for
developing the model shall be available to each attendee.
COMPANY and CONTRACTOR personnel from the following disciplines should be in attendance at
45% and 90% model reviews:
 Process
 Integrity/Corrosion
 Operations
 Maintenance
 Plant Layout and Piping
 Mechanical
 HSE
 Civil/Structural/Architectural/HVAC
 Projects
 Electrical
 Instrumentation
The client model review shall take place at 45% and 90% of model completion. The schedule for this
shall be decided by the PEM in consultation with the Lead Discipline Engineers and client.
Clash check shall be run and clashes resolved prior to 45% and 90% review.
Any necessary changes shall be agreed upon and recorded with reference numbers to avoid
misunderstanding.
Documents
Following documents shall be prepared and kept ready for the Design Review session:
 Latest copy of the PFD and P&IDs;

 Tie-in schedule;
 Safety layouts;
 Equipment List;
 Electrical layouts, e.g. cable tray layouts, lighting layouts, NAV AIDs layout, etc
 Equipment layouts;
 Plot Plans;
 Comment recording Sheet.
Handling of Comments
The model review includes whether the level of model completion is in line with the requirement.
Shortcomings in the degree of completion shall be highlighted and, after updating, model shall be
checked in the next review, or in an additional review depending on the degree of incompleteness.
NOTE: Refer COMPANY Doc.: AD274-732-G-00007 “3D PDMS MODEL REVIEW PROCEDURE”
COMPANY Project No.
AD274
Inter-Discipline Check
Piping Designer will be notified in case of any changes from the structural side, so necessary action
will be taken for any routing changes required; if any changes applied by Piping Discipline E&I
designers will be notified to carry on any modification required on their cable trays.
Clash check is scheduled throughout the job by different disciplines and if any clash occurs,
concerned discipline will work it out with the involved discipline to clear the clash if the source
discipline requires other discipline action to taken.
15.2 Type of Review
Engineering Review: An item by item review of the model against P&ID’s and vendor data. The item
will depend on the discipline e.g. lines for piping, trays & panels for electrical or equipment for
mechanical.
Functional Review: A review of the model by the operations, construction and onshore and offshore
project representatives for conformance to pre-ability, maintainability, safe constructability, design
specifications as well as any enhancements or items for cost reduction.
16. MODELLING OF ONSHORE FACILITY
Belbazem Onshore facilities FEED model shall consists of following contents and hierarchy structure.
16.1 Site Naming
Sites shall be created and named in line with the respective DB for all disciplines with the Datum
Point and Purpose set for it. Site naming shall be in the following format:
Site Name: = ZXXXYYY

Where
Z = Discipline Code (Piping – P, Civil -C, Electrical – E, Instrumentation- J, Telecom - T)
XXX = Unit Code (Refer 9.1.2)
YYY = Area Code ( Refer 9.1.2)
E.g. name of Site for Piping in BOF area (Belbazem Onshore Facility) shall be:
/ P732BOF.
16.2 Piping Modeling
16.2.1 Necessity of Piping Modeling

Piping modeling activity is performed to achieve the following
1. To route the pipe.
2. To reserve the piping space for clash checking
3. To extract the accurate MTO

COMPANY Project No.
AD274
16.2.2 Standard Piping Zones
Piping SITEs start with “P” and have following default ZONEs:
Typical Piping Zones Purpose Descriptions
/PXXXXXX/PIPE-ABCD PIPE For modeling of piping, ABCD: Piping Class
/PXXXXXX/PIPE-EQUI PIPE For modeling vessel trim lines
For studying pipe routings which are not finalized
/PXXXXX/PIPE-STUDY PSTY
yet
For modeling of temporary pipe supports which
/PXXXXX/PIPE-SUPPORT TPSP
will be designed by Civil / Structure Discipline
For modeling of pipes which are in vendor scope
/PXXXXX/PIPE-VENDOR PIPV
of work
/PXXXXX/PIPE-TEMP PTMP For modeling of Temporary items
/PXXXXX/EQUIP EQUI For modeling of Mechanical Equipment
The Piping PDMS model shall include:

1. Pipe sizes of 4” & above for Process, Utility and underground piping
2. 4” & above size Valves including operators with their actual dimensions and orientations
3. 4” & above size pipe supports
4. 4” & above piping special items
5. All In/on line instruments for pipe sizes 4” & above
6. Equipment trims (valves, blank flanges, instruments)
7. Sampling connections provision
The Piping Designers shall be responsible for the piping modeling.

The following preferred sequence of input should be followed when modeling Piping within PDMS:
a. Underground piping systems
b. Platform and access requirements
c. Critical lines according to stress requirements or long lead material delivery, large then small
bore
d. Large bore non - critical process lines
e. Small bore non - critical process lines
f. All non - critical utility lines
g. Vessel or equipment trim
16.2.3 Naming Conventions
The naming convention mentioned below shall be followed for the Piping Sites, Zones, Pipes, and
Branches. Consistent naming conventions throughout the model will help during manipulation and
navigation through the model in PDMS as well as in NW.
The names to be used are mostly on the higher PDMS levels such as SITE, ZONE, PIPE and BRAN.
However, also some lower level PDMS items will get a name according to the P&IDS tag number such
as instruments or special piping items (SP).
Under no circumstances any element other than PIPE shall be modelled under the Piping Zone.
Special characters like @, $, # and ! shall never be used in a name.

COMPANY Project No.
AD274
16.2.4 Naming Conventions for Pipes and Branches and Vessel Trims
Pipe
Pipes shall be modelled under the respective Sites and respective Piping Zones as per their piping
class. Generally Pipes levels follow naming convention below:
[Service]-[Seq. No. based on P&ID]-[WBS]-[ISO Sheet No.]
Example: CO-1000-BOF-01
Branch
The branch names for the branches below the above pipe shall be
[Pipe Name]/B1, /B2, /B3 …
Example: CO-1000-BOF-01/B1, CO-1000-BOF-01/B2….
Each branch has its own insulation and/or tracing specifications, so when the insulation or tracing
specification changes a new branch has to be created. Because of the fact, that the insulation thickness
changes when the temperature of a pipe changes, designer is obliged to split the Pipe in Branches per
temperature.
Vessel Trim (Pipe)
Separate Zone as shown in Piping Zone list table “/PXXXXX/PIPE-EQUI” should be used for creating
Vessel Trims.
For each Nozzle of the equipment one PIPE element should be created so that Isometric can be
generated at the Pipe Level. In case of Level Instruments more than one nozzle can be covered under
one pipe. Note that isometric can be generated at pipe level only if all the branches are having
continuity. The name of the Pipe for the vessel trim shall be
VT-XXXX-NN–WBS-Sheet No
XXXXX is the Vessel trim number / Equipment number
NN is the nozzle number N1, N2 …
16.2.5 Naming Conventions for Instruments and Specialties

Instruments
The Instrument shall be named as per the Tag specified in the P&IDS. For offline instruments
(transmitters only) piping shall add a suffix “.” to avoid clashes with instrument tag numbers.
Special Items
The Special Item shall be named as per the tag specified in the P&IDS.
16.2.6 VPRM MTO Attributes Setting

In brief, piping specifications shall be prepared in VPRM. PDMS transfer files from approved
specifications shall be created which will be loaded into PDMS by Administrator.
Piping MTO should be derived from PDMS model which will be imported into VPRM for further
processing. The Attributes for VPRM (FPLINE and FAREA) should be filled & checked before loading
MTO into VPRM.
FAREA shall be filled with Area Code (Split WBS / Construction Area No.) “XX”
FPLINE for Pipes shall be as per isometric Line ID.
16.2.7 Piping Tie-In Points Modeling

For all the tie-in points, the corresponding terminal flange shall be named as per the Tie-in tag. This will
help to identify the Tie-in-point in the NW. An attachment (ATTA) with attribute Stext set to the Tie in
tag shall be placed at the terminal point for Isometric drawing requirement. If required, portion of existing
piping will also be modelled to show more details of existing piping arrangement. MTO of existing piping
shall be switched OFF (MTOC & MTOT)

COMPANY Project No.
AD274
16.2.8 Interfaces of Process, Underground and Pipe Rack Piping

The different type of models have been created like Process Piping model, Pipe Rack models and
Underground models.
16.2.9 Interface point between Process Piping and Rack Piping

In general Pipe rack model shall consist of straight pipes except the piping loops. Any line, which comes
from, the process piping unit/ model on the pipe rack, shall be modelled up to the first weld point of the
pipe rack line as shown below
In case of branch off from the pipe rack header again the break shall be the first weld point for
the large bore piping 2” and above either on the olet or on the tee as shown below

COMPANY Project No.
AD274
In case of branch off from the pipe rack header for the small bore piping the break shall be the
first weld at the bend of the pipe spool as shown below
In case of line coming from the process unit on the pipe rack, if the line crosses only one
column and then returns back to the process unit, then the same line shall be modelled under
the process unit even though it occupies the rack space. This is shown below for better clarity

COMPANY Project No.
AD274
Model break for control valve assemblies modelled inside and outside pipe rack shall be done
as described below.
If a control valve assembly is located outside the pipe rack, then the same shall be modelled in
the process piping model of that particular area and the break point shall be the weld on the
down comer and the riser elbow weld as shown below
However, if the control valve assembly is located within the volume of pipe rack then the entire
assembly shall be modelled in the pipe rack model.
Break for air cooler to rack piping shall be same as the large bore piping. The moment air
cooler piping enters the pipe rack; the first weld point on the elbow / branch point of olet or tee
shall be the break point between the rack and the air cooler piping.
Piping on the top most tier of pipe rack which will have the PSV piping and valve/ control valve
stations shall be considered as process piping only.

COMPANY Project No.
AD274
16.2.10 Interface point between Aboveground and Underground Piping
Above Ground and Underground piping modeling shall be done in their respective model
allocated for the modeling. In no case any part of aboveground piping shall be modelled in
underground piping model. The model break shall be as shown below
16.2.11 Identification of Buried and Non-buried Piping
Identification of Buried and Non-Buried part of underground piping is essential to calculate the
complete length of pipe which is buried and this also helps in exactly identifying how much
length of pipe requires cathodic protection.
To identify the buried portion of the pipe an ATTA shall be put on the pipe on the location that
pipe is passing through grade level. “Stext” for this attachment point shall be set as “GRADE
LEVEL”. The “ATTYP” attribute of ATTA should be set to ‘CCCC’ so the Grade Level Point
comes dimensioned on the isometric.

COMPANY Project No.
AD274
16.2.12 Piping Designer’s Checklist

Following checks shall be carried out in PDMS 3D model:
‐ The pipes are modelled as per proper size and Piping spec as mentioned in the P&IDS.
‐ The components under the pipe are all within the specified specifications.
‐ The instruments and other special components are correctly selected.
‐ The Branch Head and Tail are placed as per the process flow specified in the P&IDS.
‐ Check that Spec at pipe & branch level is same.
‐ Check that HSTUBE of all the branches is set.
‐ The Pipe and Branches are named and the required attributes are set on the pipe and
branch level as per the project specifications.
‐ Check that angle of elbows is properly set (Elbow 90 should not be cut under 45DEG).
‐ The Instruments and Special Items on the Pipe are named as per the project specified
naming conventions.
‐ All relevant supports are modelled and tags are marked.
‐ Check that all secondary supports are properly named.
‐ Check minimum spool length of pipes and weld gaps according to the project design
basis.
‐ Check bolt length for insulating gasket items.
‐ Check for out of spec items.
‐ Check that NAME attribute of all valves are set.
‐ There is No Data Inconsistencies for the Pipe modelled.
‐ Check that insulation is correctly set.
‐ Purpose attribute is set for all zones & all zones have proper names.
‐ The pipe is clash free and clearances with other field elements/Pipes are within the
acceptable range.
‐ P&ID changes shall be identified & reviewed by concerned area engineer and will be
communicated to PDMS designer for updating the model.
Changes in PDMS Specifications
When specification updates are done within VPRM, items, which have been deleted or
updated, shall be highlighted by the PDMS Coordinator. The PDMS Users shall revisit the
deleted / updated item for the necessary actions.

COMPANY Project No.
AD274
Missing Components in Catalogue

Missing components cases shall be reported to Administrator. The Designers can use a
Dummy component to reserve the space with the: HOLD attribute of such components set to
TRUE.
Administrator shall report such lists to Cataloging Core team, once the catalogs are added to
the PDMS Specifications, Designers shall receive a notification from Administrator and shall
update the Design Model or replace (reselect) the Dummy components used. The: HOLD
attribute is now to be unset once the right component is in place.
16.2.13 Data Consistency Check

Designers shall be responsible for performing a data consistency check on each pipe at
completion of its respective input. The designer shall correct all errors and or inconsistencies
reported. The designer shall ensure that:
‐ Adjacent items are connected
‐ Connection types are compatible
‐ Bores are consistent
‐ No gaps exist in the pipe and all branches are within the network
‐ Components are geometrically aligned
‐ All branch connections are made and complete
‐ All vessels connections are made and complete
‐ Tube lengths are acceptable
‐ Elbow angles are acceptable
‐ No items are referring to /LIMBOSPEC
16.2.14 Piping Equipment Modeling
16.2.14.1 Necessity of Equipment Modeling

The following are the major advantages of equipment modeling
1. To build volumes to report clashes
2. To check locations of equipment in conjunction with other inputs
3. Proper nozzle, cleat and platform orientation
16.2.14.2 Standard Piping Equipment Zones

Piping Equipment ZONEs start with “P” and have following default naming convention:
Typical Piping Purpose
Zones Descriptions
/PXXXXX/EQUIP EQUI For modeling equipment

COMPANY Project No.
AD274
There is a dedicated Piping equipment ZONE for each Split WBS, designers shall refer to PDMS AREA
CLASSIFICATION for each MDB. XXXXX stands for Area Short Codes which are listed in this drawing.
The Piping Equipment PDMS model shall include:
1. All equipment shown on equipment list with nozzles, manholes & hand-holes
2. Motors for Pumps, Compressors and Air Coolers
3. Equipment base plates but not foundations or plinths
4. Davits with support attachment
5. Packaged items shall be modelled as Box volume
6. Preliminary Platforms, Ladder/ cages, stairways & handrails attached to equipment
7. Safety showers as Box volume
8. Vessel clips (for supports)
9. Hydrants/ monitors/ fire hose boxes
10. Future equipment as Box volume.
11. Envelopes for Drop outs, Access, Safety, fire zones and other maintenance areas
12. Monorail for maintenance
13. Crain, Forklifts and Operators as required
14. Buildings as Box volume
The DESC attribute of equipment should be set to show the description in the equipment list or data
sheet. Note that this attribute is printed in Nozzle Orientation sheet. Equipment which has more than
one tag number, like pump and motor, shall be modelled as separate items.
Package units & its auxiliary equipment will be modelled to indicate basic shape & configuration with
more emphasize on the terminal points and to allow review of operability and maintenance. The
equipment should be created to represent and block proper space in the PDMS model. The tie in Points
should be created as per the tie in List in the Vendor drawing.
16.2.14.3 Equipment Nozzles Categories and Naming Conventions
Nozzles shall be modelled under relevant SUBE:

[EQUI NAME]/NOZZ
Petrofac Standard PDMS Nozzle catalogue and specifications shall be utilized which include different
sizes, ratings and facings of the following standards:
‐ ASME B16.5
‐ ASME B16.47 Series A & B
‐ API 605
‐ MSS SP-44
Nozzles assemblies including, nozzle, blind flange, with davit or hinged (different types) and obstruction
volume are available in the library.

COMPANY Project No.
AD274
The Equipment shall get names that are the same as those indicated on the P&IDs and equipment data
sheets such as N1, N2, M1…
Equipment Datum Points (Origin)

Equipment shall be positioned at the appropriate coordinates according to the plot plan. Origin or datum
point has to be set for all equipment according to the following guide lines. Note that in specific cases,
origin shall be set SUBE as well based on the requirements.
The origin of the equipment should be same as reference line considered in the drawings like Plot Plans
or Nozzle orientation sheets. For example, in columns the Tan-line should be considered as the Origin
of the equipment. This will enable the users in placing the nozzles in PDMS model as per the
dimensions in the vendor drawing.
Equipment origin shall be set in Equipment application via Modify>Equipment Origin>ID Point to identify
a point or Explicit to define datum point explicitly. It is applicable to SUBE as well (Modify>Sub-
Equipment Origin…)
16.2.14.4 Equipment Nozzle Reports

Equipment nozzle reports shall be extracted using the standard templates available under the
%PDMSUI%REPORTS\TEMPLATES. The extracted reports shall be checked against the latest
Datasheets / vendor drawings and shall be preserved for further reference. The isometric checker shall
use these checked reports to verify the nozzle data on the isometric drawings.
16.2.15 Primitives Drawing Levels

The equipment shall be modelled to accurate size & shape to the extent required to indicate space
occupied and to allow review of operability, maintenance & access. The level attribute of these
primitives should be set to ‘0 10’ (by default it is set to 0 10) and obstruction attribute should be 2
(default is 2 or Hard). Modeling of equipment shall include items like Nameplate, Lifting lugs, Earth
cleat, Body / break flange.
16.2.16 Equipment Insulation, Fire Proofing and Obstruction Volume

If equipment is insulated, then suitable primitives which envelope the equipment & project by an amount
equal to insulation thickness should be modelled . The ‘LEVEL’ attribute of such primitives should be set
to 8 10 & ‘OBST” should be 1 (Soft). Equipment insulation shall be modelled under SUBE with the
following naming convention:
[EQUI NAME]/INSULATION
If the equipment like columns have fireproofing, then suitable primitives should be modelled which
envelope the equipment & project by an amount equal to thickness of fireproofing. The ‘LEVEL’ attribute

COMPANY Project No.
AD274
of such primitive should be set to 0 10 & ‘OBST’ should be 2 (Hard). Equipment fireproofing shall be
modelled under SUBE with the following naming convention:
[EQUI NAME]/FIREPROOF
Box volume like tube bundle removal space, path representing the manhole cover movement, Davit
movement path, Agitator removal space etc. should also be modelled . The ‘LEVEL’ attribute of such
primitives should be set to 8 10 & ‘OBST” should be 1 (Soft). Such equipment obstruction volumes shall
be modelled under SUBE with the following naming convention:
[EQUI NAME]/OBSTRUCTION
If the equipment or any of its internals requires space for Operation or maintenance activities, then
suitable primitives should be modelled in the proper level of hierarchy. These primitives should occupy
the area / volume to be blocked in PDMS model. The ‘LEVEL’ attribute of such primitives should be set
to 8 10 & ‘OBST” attribute should be set to 2 (Hard).
16.3 Civil & Structural Modeling
16.3.1 Necessity of Civil & Structural Modeling

This modeling is necessary to get the following
1. To model all structural, civil and underground components
2. To generate the 3D output for clash checking
3. To generate Civil/ Structural general arrangement drawings / Plans
4. To generate neutral file (SDNF) for structural detailing software for fabrication
5. To generate MTO of steel members and concrete work
16.3.2 Standard Civil & Structural Zones

Civil & Structural SITEs start with “C” and have following default ZONEs:
Typical Civil/Structure Zone Purpose Descriptions

/CXXXXX/ACCESS ACCE For modeling of access
/CXXXXX/FND-RACK-SLEEPER FNDS For modeling foundations of Racks and Sleepers
For modeling foundations of Technological
/CXXXXX/FND-TECH-STRU FNDS
Structures
For modeling foundations of Miscellaneous
/CXXXXX/FND-MISC FNDS
Structures like Platform, Pipe Supports.
/CXXXXX/FND-EQUI FNDS For modeling foundation of Equipment
/CXXXXX/FND-SHELTER FNDS For modeling foundations of Shelters
/CXXXXX/FND-BUILDING FNDS For modeling foundations of Building
/CXXXXX/LADDER CLAD For modeling Ladders
/CXXXXX/PAVING PAVI For modeling Paving
/CXXXXX/PIPE-SUPPORT PSUP For modeling pipe supports designed by civil
/CXXXXX/PLATFORM PLTF For modeling platforms
/CXXXXX/PRIMARY CPRI For modeling primary elements
/CXXXXX/SECONDARY CSEC For modeling secondary elements
/CXXXXX/STAIRCASES CSTR For modeling stair cases
/CXXXXX/STRU-RACK STRU For modeling structures – Pipe Racks

COMPANY Project No.
AD274
Typical Civil/Structure Zone Purpose Descriptions

/CXXXXX/STRU-SHELTER STRU For modeling structures – Shelters
/CXXXXX/STRU-BUILDING STRU For modeling structures – Buildings
/CXXXXX/ROADS ROAD For modeling roads
/CXXXXX/TRAY-SUPPORT TSUP For modeling tray supports
/CXXXXX/PIPE-SLEEVE PSLV For modeling pipe sleeves
/CXXXXX/DUCTBANK DBNK For modeling duct banks
For modeling Underground Piping under Civil
/CXXXXX/PIPE-UG CPIP Scope like OWS, AOC, COC, Storm water
channels etc.
/CXXXXX/PITS PITS For modeling Pits,Valve pit and catch pit
/CXXXXX/HANDRAIL HNDR For modeling Handrails
/CXXXXX/TRENCH CTRE For modeling Trenches of Civil Scope
/CXXXXX/DYKE DYKE For modeling Dykes
/CXXXXX/FIREPROOFING FIPR For representing Fireproof thickness
/CXXXXX/GRADE GRAD For modeling grades
/CXXXXX/CULVERT CULV For modeling culverts
/CXXXXX/FENCE FENC For modeling fence
/CXXXXX/UG-CIVIL CUGC For Modeling Sump,Manhole and catch Basin
/CXXXXX/RETAINING WALL CREW For Modeling Retaining Wall
There is a dedicated Civil / Structural SITE for each Split WBS, designers shall refer to PDMS AREA
Split WBS No. and Area Short Code shall be assigned to each Area.
Additional Civil & Structure Zones may be created by designers upon Administrator’s approval and the
PROJECT requirements.
The Civil / Structural PDMS model shall include:

1. Reinforced Concrete Structures (Primary and Secondary beams and columns)
2. Steel Structures & Pipe Racks (Primary and Secondary beams and columns)
3. Horizontal and Vertical Bracing
4. Base Plates
5. Fire Proofing
6. Moment connections (Haunches / Gusset plates)
7. Pad eyes
8. Pipes and Cable tray Supports
9. Platforms, Stairways, Walkways, Handrails and Ladders & Cages
10. Grating and chequered plates
11. Lighting fittings local supports for handrail mounted fittings
12. Foundation, Footings & Bases
13. Ground beams
14. Slabs & Paved areas
15. Equipment Pads
16. Walls, Concrete bunds, Curbs & Retaining Walls

COMPANY Project No.
AD274
17. Sleepers
18. Building (Box by default unless PROJECT specs demand details in the model)
19. Sumps
20. Concrete pits, Valve pits & Earth Pits
21. Manholes
22. Catch basins
23. Sanitary Manholes
24. Inspection Chambers
25. Pipe Trench
26. Cable Trench for Electrical Instrumentation and Telecom disciplines
27. Culverts
28. UG piping (OWS, AOC/COC, Drainage & Sewerage lines)
29. Fence Lines
30. Roads
31. Storm water channels
16.4 Electrical Modeling
16.4.1 Necessity of Electrical Cable trays and Equipment modeling

The following are the major advantages of electrical cable trays and installations modeling:
1. To route the cable trays/ Trench/ Duct banks / Sleeves
2. To build volumes to report the clash
4. To extract the MTO
5. To extract the drawing
16.4.2 Standard Electrical Zones

Electrical SITEs start with “E” and have following default ZONEs:
Typical Zone Name Purpose Descriptions

For modeling Electrical
/EXXXXX/CABLE-TRAYS-PERFORATED ETRY
Perforated Cable Trays
For modelling electrical ladder
/EXXXXX/CABLE-TRAYS-LADDER ETRY
cable Trays
For Modeling Electrical directly
/EXXXXX/TRENCHES ETRE
buried Trenches
For modelling electrical
/EXXXXX/MCT EMCT
Multiple Cables Transit
For Modeling Electrical
/EXXXXX/CONCRETE-TRENCHES-DUCT-
ECTR Preliminary Duct Banks and
BANK
Concrete Trench
For modeling electrical Pull
/EXXXXX/PULL-PIT EPIT
Pits
For modeling electrical HDPE
/EXXXXX/HDPE-DUCT EHDP
ducts and sub ducts
For modeling Electrical Battery
/EXXXXX/LIGHTING-BATTERYBACKUP LITB Backup Lighting Fixtures
Poles, JBS, Switches
For modelling Electrical
/EXXXXX/DISTRIBUTION-BOARD EEQU
distribution boards
/EXXXXX/CONVENIENCE-SOCKET EEQU
Convenience Socket

COMPANY Project No.
AD274

/EXXXXX/EARTHING EEQU
earthing
/EXXXXX/LCS/PUSHBUTTON EEQU
LCS/Pushbutton
For modelling Power Junction
/EXXXXX/PJB EEQU
Boxes
/EXXXXX/WELDING-SOCKET EEQU
Welding Socket
Equipment out of Substations
/EXXXXX/EQUIP-PLANT EEQU (Distribution Board, Socket,
Push Button Station,
WSO,RCU,LCS,CSO)
Equipment within Substations
/EXXXXX/EQUIP-SUBSTATION EEQU (Transformers, Panels, DBs,
RCUs, LCS, WSO, CSO, Bus
duct etc)
For modeling temporary cable
/EXXXXX/TRAY-SUPPORT TTSP
tray supports
Electrical Heat tracing
/EXXXXX/EHT-SYSTEM EEHT
Equipment
/EXXXXX/EHT-TRAYS ETRY Electrical Heat tracing Trays
/EXXXXX/ELEC-TEMP ETMP
Temporary items
For modelling Electrical MOV
/EXXXXX/ELEC-MOV-ISOLATORS EMOV
Isolators
/EXXXXX/SLEEVES ESLV
Sleeves
/EXXXXX/LIGHTING-NORMAL LITN Normal Lighting Fixtures
/EXXXXX/LIGHTING-EMERGENCY LITE Emergency Lighting Fixtures
There is a dedicated Electrical SITE for each Split WBS; designers shall refer to PDMS AREA
Additional Electrical Zones may be created by designers upon Administrator’s approval and the project
requirements.
The Electrical PDMS model shall include:
1. All Cable Trays outside the building.
2. Miscellaneous cable trays where clash check is needed
3. Directly Buried Cable Trenches/ Duct Bank
4. Conduits
5. Local control stations, Convenience Sockets, Welding Receptacles & Power Junction Boxes
6. Lighting fixtures with mounting arrangement
7. Lighting poles with preliminary foundations
8. Small power, outdoor distribution board
COMPANY Project No.
AD274
9. Earth bus bar & earth pit

10. Cathodic protection equipment
11. Equipment inside substations
12. Heat tracing equipment such as power JBs, thermostat JBs
13. Transformers & Busducts
14. Motor space heat isolator
16.4.3 Electrical Cable Trays Modeling
Tray zones shall be utilized for tray modeling.

Wherever the electrical cables are buried without concrete trenches, these shall be modelled by
Electrical. Electrical concrete trenches shall be modelled as temporary model by Electrical that will be
shared with Civil later as IDIT to be finalized and designed and finally modelled by Civil.

If designers face any missing components, cases shall be reported to Administrator. The designers can
use a Dummy component to reserve the space; once the catalogs are added to the PDMS
Specifications, Designers shall receive a notification from Administrator and shall update the Design
Model or replace (reselect) the Dummy components used.
16.4.4 Naming Conventions for Electrical Cable Trays and Installations
Tagging of Electrical cable trays shall be done as described in the project electrical symbol and legend
Sheet. Cable tray tag (NAME) shall be entered after modeling the tray at main (CWAY) level.
Installations shall be named as per project equipment tagging procedure.

16.5 Instrumentation Modeling

16.5.1 Necessity of Instrumentation Cable trays and Installations Modeling
The following are the major advantages of Instrumentation Cable trays and Installations modeling
1. To route the cable trays/ trench and duct banks
16.5.2 Standard Instrumentation Zones

Instrumentation SITEs start with “J” and have following default ZONEs:
/JXXXXX/MAIN-TRAYS-
ITRY For modeling Instrument Perforated Cable Trays
PERFORATED
/JXXXXX/MAIN-TRAYS-
ITRY For modeling Instrument Ladder Cable Trays
LADDER
/JXXXXX/BRANCH-TRAY- For modeling branch Perforated cable tray, if there is
ITRY
PERFORATED project requirement
/JXXXXX/BRANCH-TRAY- For modeling branch Ladder cable tray, if there is
ITRY
LADDER project requirement
/JXXXXX/SLEEVES ISLV For modeling Instrument Sleeves
/JXXXXX/TRENCHES ITRE For modeling Instrument Trenches
/JXXXXX/CONCRETE- ICTR For Modeling Instrument Preliminary Duct Banks and
TRENCHES-DUCT-BANK Concrete Trench
COMPANY Project No.
AD274

/JXXXXX/MCT IMCT For modelling Instrument Multiple Cables Transit
/JXXXXX/HANDHOLE IHOL For modeling Instrument Handhole
/JXXXXX/MANHOLE IMOL For modeling Instrument Manhole
/JXXXXX/PULL-PIT IPIT For modeling Instrument Pull Pits
/JXXXXX/HDPE-DUCT JHDP For modeling Instrument HDPE ducts and sub ducts
/JXXXXX/MANIFOLD IAIR For modeling Instrument Air manifolds
/JXXXXX/TRAY-SUPPORT TTSP For modeling temporary cable tray supports
/JXXXXX/F&G-EQ FGEQ For modeling F&G Instrument Items
/JXXXXX/F&G-JB FGJB For modeling F&G Junction Boxes
/JXXXXX/INSTRUMENTS INST For modeling Instruments
/JXXXXX/JUNCTION-BOX IJBX For modeling Instrument Junction Boxes
/JXXXXX/VOLUME-BOTTLE IVBT For modeling Volume Bottles
/JXXXXX/MISC IMSC For modeling Instrument Miscellaneous
/JXXXXX/VENDOR IVEN For modelling Instrument Vendor Scope
For Temporary Modeling of Instrument required
/JXXXXX/INST-FNDS IFND
Foundations
/JXXXXX/TEMP JTMP For Modeling Instrument Temporary items
There is a dedicated Instrumentation SITE for each Split WBS, designers shall refer to PDMS AREA
Additional Instrumentation zones may be created by designers upon Administrator’s approval and the
project requirements.
Instrumentation PDMS model shall include:

1. Cable Trays 300mm wide and above outside the building.
2. Directly Buried Instrument Cable Trenches/ Preliminary Duct Banks and Concrete Trenches
3. Analyzer house/ Enclosures
4. Junction Boxes for Process and Fire & Gas (With volume boxes for maintenance)
5. Box volumes shall be modelled for Instruments/Junction box for maintenance /personnel access
6. Instrument field control panels with access volumes for door opening/maintenance
16.5.3 Instrumentation Cable Trays Modeling

The Designers can use a Dummy component to reserve the space; once the catalogs are added to the
PDMS Specifications, Designers shall receive a notification from Administrator and shall update the
Design Model or replace (reselect) the Dummy components used.

COMPANY Project No.
AD274
16.5.4 Naming Conventions for Instrumentation Cable Trays and Installations

Tagging of Instrumentation cable tray/ Trench shall be done as described in the Instrumentation Legend
Sheet applicable for defined project at main (CWAY) level.
Installations shall be named as per project equipment tagging procedure and Instrument Equipment list/
schedule.
16.6 Telecom Modeling

16.6.1 Necessity of Telecom Cable trays and Installations Modeling
The following are the major advantages of Telecom Cable Trays and Installations modeling
1. To route the cable trays
16.6.2 Standard Telecom Zones

Telecom SITEs start with “T” and have following default ZONEs:
For modeling Telephone
/TXXXXX/CABLE-TRAYS-TEL-PERFORATED TTRY and LAN Perforated Cable
Trays
/TXXXXX/CABLE-TRAYS-TEL-LADDER TTRY and LAN Ladder Cable
Trays
/TXXXXX/TRENCHES-TEL TTRE
and LAN Trenches
For modeling Security &
/TXXXXX/CABLE-TRAYS-SEC-
TTRY PAGA Perforated Cable
PERFORATED
Trays
/TXXXXX/CABLE-TRAYS-SEC-LADDER TTRY
PAGA Ladder Cable Trays
/TXXXXX/TRENCHES-SEC TTRE
PAGA Trenches
For modelling Telecom
/TXXXXX/MCT TMCT
Multiple Cables Transit
For Modeling Telecom
/TXXXXX/CONCRETE-TRENCHES-DUCT- Preliminary Duct Banks and
TCTR
BANK-TEL Concrete Trench
(Telephone and LAN)
For Modeling Telecom
/TXXXXX/CONCRETE-TRENCHES-DUCT- Preliminary Duct Banks and
TCTR
BANK-SEC Concrete Trench (Security
& PAGA)
/TXXXXX/EQUIP-TEL TEQU
and LAN Equipment
/TXXXXX/EQUIP-SEC TEQU
PAGA Equipment
/TXXXXX/TJB-TEL TJBX
Junction Boxes
/TXXXXX/TJB-SEC TJBX For modeling Security

COMPANY Project No.
AD274

Junction Boxes
For modeling temporary
/TXXXXX/TRAY-SUPPORT TTSP
cable tray supports
For Temporary Modeling of
/TXXXXX/TELE-FNDS TFND Telecom required
Foundations
For modeling Telecom
/TXXXXX/HANDHOLE THOL
Handhole
/TXXXXX/MANHOLE TMOL
Manhole
For modeling Telecom Pull
/TXXXXX/PULL-PIT TPIT
Pits
/TXXXXX/HDPE-DUCT THDP
HDPE ducts and sub ducts
/TXXXXX/SLEEVES-TEL TSLV
and LAN Sleeves
/TXXXXX/SLEEVES-SEC TSLV
PAGA Sleeves
/TXXXXX/VENDOR TVEN
Vendor Scope
/TXXXXX/MISC TMSC
Miscellaneous
There is a dedicated Telecom SITE for each Split WBS, designers shall refer to PDMS AREA
Additional Telecom Zones may be created by designers upon Administrator’s approval and the project
requirements.
The Telecom PDMS model shall include:
1. Cable Trays 300mm wide and above outside the building and less than 150 mm (if needed)
inside the building
2. Directly Buried Telecom Cable Trenches/ Duct Bank
3. Conduits
4. Loudspeakers, poles and Loudspeaker Junction boxes
5. Telephone Junction box
6. Beacons, Sounders and Visual Alarm
7. Telecom devices such as Masts, CCTV Camera, acoustic hood and associate supports
8. CCTV camera junction boxes and towers
9. PAGA Marshaling box
10. Supporting arrangement for field equipment
11. Conduits below paving and inside foundations
12. Telephone stations
13. Telephone cabinets
14. ACS and IDS devices
15. Equipment support stanchions
16. Maintenance and winterization box volumes where applicable

COMPANY Project No.
AD274
16.6.3 Telecom Cable Trays Modeling

If designers face any missing components, cases shall be reported to Administrator. The Designers can
use a Dummy component to reserve the space; once the catalogs are added to the PDMS
Specifications, Designers shall receive a notification from Administrator and shall update the Design
Model or replace (reselect) the Dummy components used.
16.6.4 Naming Conventions for Telecom Cable Trays and Installations

Tagging of Instrumentation cable tray/ Trench shall be done as described in the Instrumentation Legend
Sheet applicable for defined project at main (CWAY) level.
Installations shall be named as per project equipment tagging procedure and Telecom Equipment
List/Schedule.
16.7 Working Practices

The equipment layouts and plot plan must show the construction datum for the plant. The construction
datum shall be taken as the datum point for the PDMS model. This point is generally set at SITE level;
all disciplines must work with this same point. This point (SITE Co-ordinate / Datum Point) is therefore
fixed at the beginning of each project and must not be changed by any PDMS user.
It is generally set to E 0mm N 0mm U 0mm but it shall be checked by Administrator.

The input of multi-discipline design data into the 3D model shall be progressively carried out suited to
the availability of design drawings, specifications and fitted within the Project Schedule and/or
requirements accordingly.
In order to ensure that the Design Data input into the model is being developed from current design
drawings and specifications, and to maintain proper design concurrence, records shall be maintained by
the respective Area engineers.
When performing in a Brown-Field projects, 3D model of the existing items i.e. piping, structure,
equipment & etc. should be made (or imported if it is available) according to the project requirements
under the zone “EXISTING” for every site for all disciplines.
16.7.1 Clash Checking Considerations

During the modeling activities, it is mandatory that all designers use the on-line clash utility within PDMS
on a regular daily basis. The model must be clash checked prior to any model review, internal review as
well as review with the client. It is recommended that designers use automatic (continues) on-line clash
utility.
User defined default settings for the on-line clash utility to be used for clash checking shall be as below.

COMPANY Project No.
AD274
Touch gap - 0mm

Overlap - 0mm
Clearance - 24mm
Whenever a platform is created for representing floor, operating platforms, walkways, circular platforms
in PDMS model, the program creates one soft box (OBST attribute set to 1), which is not seen (due to
the attribute level set to 4 5). The dimension of this box is same as the dimension of platform (length &
width) but the height of the box is 2100 and this box is placed over the platform box. The dimensions of
the above soft box (width & length i.e. XLEN & YLEN) shall be corrected to represent the actual
walkway, operation aisle around equipment. If this is done correctly and if the report shows clash with
such box then it will be a real clash, which needs to be reviewed. This will minimize the spurious
clashes reported.
Clash checking report shall be generated by CONTRACTOR before every model review and shared
with COMPANY, in order to provide a clash free model during model review session.
16.7.2 Color Settings

Sample color settings for the models shall be as follows, it shall be checked at the beginning of the job
by Administrator and any necessary changes shall be made to suit project specific requirements in NW
files and model reviews:
DESC ATTRIB Value LEVEL COLOR

Initial Process Piping Duty PRO Pipe Pink
Initial Utilities Piping Duty UTY Pipe Yellow green
Initial Fire Water Piping Duty FWR Pipe Magenta
AFC process piping :Status “X” Pipe Orange red
AFC Utilities piping :Status “X” Pipe Forest green
AFC Fire Water Piping :Status “X” Pipe Red
Preliminary Equipment Purpose EPR EQUI Mauve
Final Equipment :Status “X” EQUI Plum
Temporary Structure Purpose TSTR Zone Red
Temporary Platform Purpose TPLT Zone Red
Temporary staircase / ladder Purpose TLAD Zone Red
Temporary Concrete Items Purpose TLAD Zone Brown
Temporary Roads Purpose TROD Zone Khaki
Temporary Fences Purpose TFEN Zone Indigo
Temporary Walls / Sheeting Purpose TWAS Zone Violet
Temporary FFL Purpose TFFL Zone Tan
Temporary Civil UG Purpose TUDG Zone Ivory
Grade Purpose GRAD Zone Wheat
Civil structure Purpose STR STRU Steel blue
Civil platform Purpose PLT STRU Cyan
Civil staircase / ladder / handrail Purpose LSD STRU Blue
Concrete Items :Status “X” STRU Beige
COMPANY Project No.
AD274

Roads :Status “X” STRU Dark gray
Fences :Status “X” STRU Steel blue
Walls / Sheeting :Status “X” STRU Sandy brown
FFL :Status “X” STRU Bright Orange
Civil UG :Status “X” STRU Plum
Storm Water Channels Purpose SWC STRU Khaki
Initial Instrument items Purpose INST Zone Royal Blue
Initial Instrument tray Purpose ITRY Zone Light Green
Initial Instrument trench Purpose ITRE Zone Deep pink
AFC Instrument items :Status “X” STRU Blue
AFC Instrument tray :Status “X” PIPE Dark gray
AFC Instrument trench :Status “X” EQUI Tomato
Telecom Items Purpose TEQU Zone Violet
Telecom Trench Purpose TTRE Zone Magenta
Telecom Tray Purpose TTRY Zone Maroon
AFC Telecom Items :Status “X” STRU Khaki
AFC Telecom Trench :Status “X” EQUI Blue
AFC Telecom Tray :Status “X” PIPE Pink
Electrical EQUI Purpose EEQU Zone Violet
Electrical tray Purpose ETRY Zone Tomato Red
Electrical trench Purpose ETRE Zone Dark Brown
Electrical Lighting Purpose ELGT Zone Yellow
Electrical Foundations Purpose EFDN Zone Plum
Electrical Supports Purpose ESUP Zone Orange
AFC :Status “X” EQUI Gold
Electrical Equipment
AFC Electrical tray :Status “X” PIPE Pink
AFC Electrical trench :Status “X” EQUI Brown
AFC Electrical Lighting :Status “X” STRU Light gray
AFC :Status “X” EQUI Khaki
Electrical Foundations
AFC Electrical Supports :Status “X” STRU Tomato
Obstruction Purpose OBST Zone White
EXISTING (in case of brown Purpose EXST Zone Dark brown
field projects, when existing
items are modelled)
EHT-SYSTEM Purpose EEHT Zone Aquamarine
ETEMP Purpose ETMP Zone Red

COMPANY Project No.
AD274

HVAC Equipment Purpose EQUI Zone Tan
HVAC Chilled Water Piping Purpose HPIP Zone Powder blue
HVAC Ducting Purpose HVAC Zone Beige
HVAC Supports Purpose HSUP Zone Salmon
AFC HVAC Equipment :Status “X” EQUI Dark brown
AFC HVAC Chilled Water :Status “X” PIPE Khaki
Piping
AFC HVAC Ducting :Status “X” HVAC Sandy brown
AFC HVAC Supports :Status “X” EQUI Sandy brown
Escape Routes Purpose ESCR Zone Bright red

AD274 732 G 00006 - Rev.3

Uploaded by

Copyright:

Available Formats

AD274 732 G 00006 - Rev.3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AD274 732 G 00006 - Rev.3

Uploaded by

Copyright:

Available Formats

FEED & EPC COMPETITION FOR BELBAZEM BLOCK

FIELD DEVELOPMENT PROJECT

SUMMARY OF DOCUMENT REVISIONS

2 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

3 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

16.5 INSTRUMENTATION MODELING....................................................................................................41

4 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

Figure 1 – Facility Location

5 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

The development concept is schematically depicted in Figure 2 below:

Figure 2 – Development Concept

4. ABBREVIATIONS AND DEFINITIONS

ADNOC Abu Dhabi National Oil Company

NDMS NPCC Document Management System

The Following definitions apply to terms used within this document:

COMPANY Al Yasat Petroleum Operation Company Limited (Al Yasat)

PMT Project Management Team

PMC Project Management Consultant appointed by the COMPANY to provide

SERVICES means the works and services to be performed under the

CONTRACTOR FEED/Design competition Contractor appointed by COMPANY to

VENDOR Person, firms, partnerships, companies, bodies, entities or a

5. PROJECT CODES AND STANDARDS

7 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

Guidelines/Codes of Practice, COMPANY Specifications and Standards, COMPANY HSE Regulations

Reference shall be made to the following documents:

DOCUMENT NUMBER DESCRIPTION

AD274-732-G-00002 (8353-A-PD-0001) Engineering Execution Plan

A0-ENG-N-SL-001 Rev.2 Status list for Technical Standards

7.1 PDMS Admin

8 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

 Preparation and loading of specs, catalogues and libraries.

 Creation and updating the Design review Sessions.

 Backup and retrieval of the models.

 Ensure that all model review files are updated daily.

7.2 Designer / Checker is Responsible for:

 Manages engineering interface between various disciplines.

9 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

 Motorized dampers, including damper actuators.

Civil & Structural:

9. PROJECT DISTRIBUTION / ORGANIZATION

9.1 Project Entities Naming

One MDBs is created for each platform.

12 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

DB Name DB NUMER DB Description TYPE

13 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

uadDRASUPP01 70541 Draft DB For UAD-Wellhead Tower Support PADD

One MDB is created for the Belbazem Onshore facility

14 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

Db Naming Convention shall be as per below

Area Code (code for plant name as per ADMA-OPCO convention ,

PDMS Activity (i.e. DESI = Design, DRA = Draft, etc.)

Discipline (i.e. PIPE = Piping, STRU = Structural, etc.)

DB Description: Piping Design DB for Compression Platform Chemical Injection Unit

DB Area numbers are maintained as default. (000)

9.2 Site Naming

15 / 48 Uncontrolled When Printed Document Class: 1 AD274-732-G-00006_REV.3.DOCX

Site Name: = XXXPIPE

Data Base Type Abbreviation

9.4 Discipline Code