08-Annex F PDMS Naming Conventions

ADDITIONAL TECHNICAL REQUIREMENTS
DOCUMENTATION FOR OPERATIONS (DFO)
ANNEX F – PDMS Naming Convention
Document No.: Rev.: Page:
Classification Code:
Originator: Tag No.: System No. : Area Code:
Document Title: PDMS Naming Convention
Information: Viewpoint of the PDMS Users in Norway
01 06.12.2007 Issued for implementation KOE
Rev. Issue Description Made Chk'd Disc. Proj.

Date by by Appr. Appr.
DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

4314 05 29.04.2008 Director Plant & Equipment Information
ANNEX F – PDMS Naming Convention – Page 1 of 44

1 Introduction 4
2 General Information 4
2.1 Discipline Long Code.........................................................................................................4
2.2 Discipline Short code.........................................................................................................5
2.3 Responsible Code............................................................................................................. 6
2.3.1 Project Short Code............................................................................................................ 6
2.3.2 Reserved Contractor Codes..............................................................................................7
2.3.3 Location Code................................................................................................................... 8
3 Databases 9
3.1 General............................................................................................................................. 9
3.2 Master databases.............................................................................................................. 9
3.3 Team naming and use.......................................................................................................9
3.4 Database naming............................................................................................................ 10
3.5 Database Content Type...................................................................................................10
3.6 Database description.......................................................................................................11
3.7 MDB required content......................................................................................................12
4 Design hierarchy and naming conventions 13
4.1 General Principles...........................................................................................................13
4.2 Special characters in PDMS names................................................................................13
4.3 PDMS Design DB Hierarchy – SITE Level......................................................................13
4.3.1 SITE Name Syntax..........................................................................................................13
4.4 PDMS Design DB Hierarchy – ZONE Level....................................................................14
4.4.1 ZONE Name Syntax........................................................................................................14
4.4.2 Future Design.................................................................................................................. 14
4.4.3 General Zone Sub Set Codes..........................................................................................15
4.4.4 Subset Codes for PDMS – Piping....................................................................................15
4.4.5 Subset Codes for PDMS – HVAC....................................................................................16
4.4.6 Subset Codes for PDMS – Mechanical............................................................................16
4.4.7 Subset Codes for PDMS – Structural..............................................................................18
4.4.8 Subset Codes for PDMS – Architectural..........................................................................19
4.4.9 Subset Codes for PDMS – Electrical...............................................................................20
4.4.10 Subset Codes for PDMS – Instrumentation.................................................................21
4.4.11 Subset Codes for PDMS – Telecom............................................................................22
4.4.12 Subset Codes for PDMS – Safety................................................................................22
4.4.13 Subset Codes for PDMS – Civil...................................................................................23
4.4.14 Subset Codes for PDMS – Scanning...........................................................................24
4.4.15 Subset Codes for PDMS – Pipe Support.....................................................................25
4.5 PDMS Design Hierarchy – Sub-ZONE Level...................................................................25
4.5.1 Sub-ZONE Name Syntax................................................................................................25
4.5.2 Pipe Supports.................................................................................................................. 27


4.5.3 Skids and package tags..................................................................................................28

4.6 Modifying existing tag......................................................................................................28
5 Name standard for administrative elements29
5.1 Locations......................................................................................................................... 29
5.2 Update Events.................................................................................................................29
6 Working in the project HIERARCHY 30
6.1 General........................................................................................................................... 30
6.2 EXECUTING MAJOR PROJECTS..................................................................................30
6.3 EXECUTING MMO PROJECTS.....................................................................................30
7 CATALOGUE AND SPECIFICATIONS 31
7.1 General........................................................................................................................... 31
7.2 Naming conventions........................................................................................................31
7.2.1 SPWL Name Syntax........................................................................................................31
7.2.2 SPEC Name Syntax........................................................................................................31
7.2.3 Spec Component Name Syntax......................................................................................32
8 Attributes and user defined attributes (UDA) 33
8.1 User Defined Attributes....................................................................................................33
8.1.1 General........................................................................................................................... 33
8.1.2 Common User Defined Attributes....................................................................................34
8.2 Standard Attributes and common UDAs for SITE elements.............................................39
8.3 Required Attributes and common UDAs for ZONE elements..........................................39
9 LevelS, ObstructionS and RESERVED VOLUMES 40
9.1 Level................................................................................................................................ 40
9.2 Obstruction...................................................................................................................... 40
9.3 Reserved Volumes and Areas.........................................................................................40
10 As-Built MODELING and demolition 42
11 Definitions 43
11.1 Definitions....................................................................................................................... 43
11.2 Abbreviations...................................................................................................................44
12 Modifications to previous version 45


1 INTRODUCTION
The scope for this document is to define a set of conventions that shall be used for a PDMS project in
order to make it easier for several parties to update or extract information from the same model.
The operator (customer) is being referred to as the Company, while the design work is being carried
out by one or more Contractors. See also section 8, Definitions.
The document is meant to cover both the engineering and operation phase of a plant’s lifecycle. In the
operation phase there will be an as-built version of the model, but it may also in parallel be several
modification projects that are being carried out in the same model.
2 GENERAL INFORMATION
2.1 Discipline Long Code

The following Discipline Long Codes shall be used in the PDMS Project:
Discipline
Description
Long Code
ARCH Architectural
CIVI Civil
ELEC Electrical
HVAC HVAC
INST Instrumentation
MECH Mechanical
PIPE Piping
PSUP Pipe Support
SAFE Safety
STRU Structural
TELE Telecom
GENE General*
IMPL Implanted Models*
SCAN Scanning*
* The codes may be used in special cases
The Discipline Long Codes shall be used in:
 Site Name
 Site Description
 Zone Name
 Zone Description
 Team Description


 Database Description
 Spec World (SPWL) Name
Note that the Norsok discipline codes, like N for Structural are not used in PDMS.
2.2 Discipline Short code

The Discipline Short code is the first letter of the Discipline Long code, except for Safety, Scanning
and Pipe Support. In addition, the letter “G” is used for multidiscipline data.
Discipline Short Code

Discipline
Description
Short Code
A Architectural
C Civil
E Electrical
H HVAC
I Instrumentation
M Mechanical
P Piping
Z Pipe Support
F Safety
S Structural
T Telecom
G Multi discipline
The Discipline Short code shall be used in:
 Team Name
 Database name


2.3 Responsible Code

A Responsible Code may be added to the name to avoid naming conflicts, or to clearly define who is
responsible for the information. The Responsible Code shall be separated from the rest of the name
with the underscore character “_”, and it shall be removed from the name when the modification is
implemented into the As-Built hierarchy.
The Responsible Code will normally be a Project Short Code but in some cases the Contractor Code
will be used. If it is required to split the different parts of the Responsible Code, a dash “-“ shall be
used.
The MMO scope will normally be assigned the responsible code “MMO”
As-built data and databases will not have Responsible Code.
2.3.1 Project Short Code

Project Short Code is a short version of the official Project name. A Project may be a project
constructing entire platform topside, a major modification project, or maybe a small study.
The Project Short Code is determined by the Hub Administrator. The Project Short Code is used in
database naming, and the design hierarchy naming convention. Its purpose is to clearly separate the
Project scope from the As-Built design in the model, and from other Projects using the model.
Project Short Code is normally not identical to the PDMS Project Code.
Example of Project Short Codes:

Name Predefined Value
MMO Topside/Onshore Maintenance and Modifications Project
ALVE Alve Project on Norne
SFLL Statfjord Late Life Project
KFGC Kollsnes Flash Gas and Condensate Project
TYR Tyrihans Project on Kristin
EKM EKOM


2.3.2 Reserved Contractor Codes
Contractor Contractor company Reserved DB numbers

code
AK Aker Kværner
AL Allseas
AU Aveva UK
AV Aker Verdal
BR Brown and Root
FA Fabricom
FW Foster Wheelers
FU Fugro Ltd
HD Hitec
HI Heerema
JP JP Kenny
LE Leirvik
LI Linde
KD KCA Deutag
MH Marine Hvac
MO Mollier
OD Odfjell Drilling
PH Peder Halvorsen Industrier
PR Prosafe
RE Reinertsen Engineering
SC Sørco
SD Scan Power
SW SeaWell
SE Semco
SH Strachen & Hensaw
SM Seipem
SO Sørco
ST Statoil
SU Subsea 7
VA Aibel
WG Wood Group
CP Conoco Phillips


2.3.3 Location Code
Location codes are defined as the contractor code and normally the first letter of the geographical
location of the satellite. Typical codes are defined below:
Location Code Company Location

VAS Aibel Stavanger
AKO Aker Kværner Oslo
RET Reinertsen Trondheim
FAS Fabricom Stavanger
This is not an absolute rule, and it is up to the HUB administrator to create unique 3 letter location
codes used throughout the company’s global projects. Same code to be used across all projects.


3 DATABASES
3.1 General
In general there shall be one database for each Discipline and Area. If the number of databases
needs to be reduced, several areas for the same discipline may be included in the same database, or
disciplines may be grouped in the following way:
 Piping-Mechanical
 HVAC
 Structural-Architect
 Pipe Support
 Electrical, Instrumentation, Telecom and Safety
 Laser Scanning (where relevant)
For Team names and Database names only, each discipline is represented by a single character, the
Discipline Short code. See chapter 2.2.
3.2 Master databases

Aveva’s MAS-projects shall not be modified.
Master Project databases shall have database number 3000 or greater, and the number shall be
agreed with the model owner.
3.3 Team naming and use

The following naming convention shall be used for Teams:
As-built database Team name: ASB+<Group>+<Discipline Short Code>
Project database Team name: <Group>+<Discipline Short Code>
Group Description
DES Designers
DRA Drafters
ADM Administrators
Example of Team names:
ASBDESP - As-Built design Team for PIPE

DESP - Project design Team for PIPE
If needed, Discipline Short codes may be combined to form multi-discipline Teams.

DESPM - Project Team for PIPE-MECH


3.4 Database naming

Naming convention for Databases:
<Team>/<PDMS Type>-<Discipline Short code>-<Scope>-<Responsible Code>
PDMS Type is the type according to the PDMS manual (DESI, PADD, DICT, CATA, ..)
For multidiscipline databases, several Discipline Short Codes may be combined, like “EITF”. The
code “G” may be used to represent all disciplines. Note that not all team names contain the same
disciplines as in the database name after the “/”. This is because the database name informs of the
contents, while the team name relates to user access.
Scope will normally be an Area Code for design databases. Multiple Areas shall have a dash as
separator (M11-M12-M14).
Database Name Description

DESPM/DESI-PM-A00- Design database for Pipe and Mechanical, in area A00 for project
KFGC KFGC
DESPM/DESI-PM-A44- Design database for Piping and Mechanical in area A44, A45 and A46
A45-A45-KFGC for project KFGC
ASBDESPM/DESI-PM-A44 As-Built database for Piping and Mechanical in area a44.
ADMP/CATA-P-A00 Catalogue database for Piping All areas
DRAPM/PADD-PM-A00- Draft database for Piping And Mechanical in area A00 for project
KFGC KFGC
ADMG/LEXI-G-A00 Lexicon database for all disciplines and all area
3.5 Database Content Type

The term “Content-Type” is used in the database description to classify the database contents, and to
give additional information to PDMS Administrators about how the database is to be used in the
PDMS Project and in the creation and maintenance of MDBs.
Content-Type Description of Content-Type

[ASB] As-built. Contains information to show the As-Built model
[PRO] Project. Information relating to an ongoing project. And volume occupying
studies.
[MPx] <LOC> Master Project. Contains a Master Project database copy from PDMS Projects
like MAS. <=LOC> is the single Primary Location for the database, to know
where it is updated from.
[SCA] Scanning.
[RST] <LOC> Restricted. Contains information not to be distributed to all Locations. <LOC> is a
list of locations to have the database.
[TMP] <LOC> Temporary. Info only useful to a single Contractor company, like testing design,
own measure data or Contractor-specific application databases. <LOC> is a list
of locations to have the database. Non volume occupying studies.
[ARC] Void. Historical/archived info or older studies. Normally not distributed.
[EXT] Extract database.
[DEL] To be deleted.


The database description (see chapter 3.6) shall contain Content-Type in order to help maintain
MDBs, and guide the PDMS Administrators in allocation, deallocation and primary location-
modification in PDMS Admin.
3.6 Database description

Database description shall be used consistently across the PDMS Projects. The description is used to
classify the contents of the database in order to aid the PDMS Administrator in the maintenance of the
MDBs at his location.
Database description shall be constructed in the following way:
[Content-Type] <LOC1> project, discipline in area, for owner, date by Administrator
Content-Type: see chapter 3.5.

project is either “As-Built” or a descriptive project name to help find information about the project at a
later date Example: SFLL:Statfjord Late Life
discipline is the Discipline Long Code, “all disciplines” may be used.
area is the Area code, “all areas” may be used.
owner is the contractor or company using the data in the database during project execution.
date is the date the database was created, or description modified
Administrator is the name of the PDMS administrator responsible for creating or modifying the
description.
For As-Built design databases, project is set to “As-Built” in order to format the description correctly
with commas. For As-built databases owning company shall always be Company.
Master Project database description shall be constructed in the following way:
[Content-Type] <Contractor (or Company)> Master Project <Discipline Long Code> optional text
optional text can be like Spec, Properties, Dictionary, Catalogue, Templates or similar, making it easier
to understand the database contents.
1
Location is only used if Content-Type is [MPx], [TMP] or [RST], see chapter 3.5.
 for [MPx]-databases, use the Primary Location LocID, like <=AKS>
 for [TMP] and [RST]-databases, a list of locations may be used, like <VAB,VAO,RET>


3.7 MDB required content

Each location shall have a main MDB, with the same name as the PDMS Project Code, i.e. the
Heidrun PDMS Project with PDMS Project code HEI shall have a MDB named /HEI.
In order to show the complete 3D CAD model including ongoing Projects, the main MDB at each
location shall contain all databases of Content-Type [ASB], [PRO], [MPx] and [DMP], except:
 PADD and ISOD-databases are not required.

 [MPx]-design (DESI) databases usually contain Contractor-specific templates, and are not
required.
DICT-databases from other Contractors are optional, and are usually of type [MPx]. Note that to
complete the Company UDAs regularely (see chapter 8), it is necessary to have the Company DICT-
database with the required Company UDAs in the MDB.
It is especcially important to have the Reserved Volume database (like teamname/DESI-G-A00-
RESERVED) in the MDB. See chapter 9.3.


4 DESIGN HIERARCHY AND NAMING CONVENTIONS
4.1 General Principles

As opposed to the technical tag hierarchy, that is primarily system-based, the 3D CAD hierarchy
structure is area based with plant area divisions and secondarily system-based at a lower level where
possible.
PDMS SITEs shall normally contain data for a discipline within a project Area. The Discipline Long
Code shall always be used in Site names.
PDMS ZONEs are used to group the different object types for a Site. The Discipline Long Code shall
always be used Zone names.
The PDMS SITE with area “A00 - General” (or similar), shall only be used when it is not otherwise
possible or useful to place the element in a more specific area.
4.2 Special characters in PDMS names

The dash character ( - ) shall be used as a delimiter between different parts of Site, Zone and
elements, like Area and Discipline. The dash character ( - ) shall only appear as a natural part of an
ENS Tag name in PIPE and EQUI names, and shall not be used as a delimiter between Tag name
and Area.
For Site and Zone names, the underscore character (_) shall be used only as a delimiter between the
Area-Discpline part and the Responsible Code part. For PIPE elements, the underscore character (_)
shall be used only as a delimiter between the ENS Tag Name, the Area Area part, and the
Responsible Code part. For EQUI elements, the underscore character (_) shall be used only as a
delimiter between the ENS Tag Name part, and the Responsible Code part.
In some ENS documents, Tag names contain one or more special characters, like the blank character
(space). In such cases, each single special character in the PDMS element name shall be replaced
by a period character (.).
4.3 PDMS Design DB Hierarchy – SITE Level

A SITE contains data for a discipline in an Area. Areas are defined by the projects Coding Standard,
and in some cases Areas may be combined or split into sub-Areas in the PDMS model.
4.3.1 SITE Name Syntax

SITE name shall always contain plant Area code, Discipline Long Code and the Responsible Code to
distinguish project data from As-Built data and other projects, including studies, and locations:
<Area Code>-<Discipline Long Code>_<Responsible Code*>
*As-built data does not have a Responsible Code.
Examples:
C04-PIPE - Piping design in Area C04

C04-PIPE_TYR - Piping design in the Tyrihans Project, Area C04
M14-STRU_KFGC - Structural design in the KFGC Project, area M14
M14-STRU_KFGC-MUM - Structural design in KFGC Project by Mumbai, area M14,


Note the use of the underscore character to separate the As-Built Site name from the Project Site
name.
See chapter 8 for Site attributes.
4.4 PDMS Design DB Hierarchy – ZONE Level

A ZONE contains data broken down into logical subset for a SITE depending on discipline, identifying
type of design. Also see chapter 8.3 for Zone attributes.
4.4.1 ZONE Name Syntax

ZONE name syntax shall contain plant Area code, Discipline Long code, Subset Code and the Project
Short Code to distinguish project data from As-Built data and other projects, including studies, and
locations:
<Area Code>-<Discipline Long Code>-<Subset Code*>_<Responsible Code**>
Example:
C04-MECH-EQUIPMENT*_AAA**
Area Code
Discipline Long Code
Subset Code
Responsible Code
Other Examples:
C04-PIPE-43 - All As-Built Pipes in system 43 (Flare) in Area C04

C04-PIPE-43_KFGC - All system 43 Pipes in the KFGC Project in Area C04
P21-ELEC-PUSHBUTTON - All Electrical Push Buttons in area P21
P21-ELEC-PUSHBUTTONS_TYR
– All Electrical Junction-Boxes in the Tyrihans Project in Area P21
M14-STRU-DECKSTRUCTURE - Deck Structure elements in Area M14
* The described subset code shall be used. New subset codes may be approved if needed by
contractor.
**As-built data does not have a Responsible Code, so here the As-Built zone shall be:
C04-MECH-EQUIPMENT
4.4.2 Future Design

FUTURE-zones may be used in the design phase, but shall not be used in the as-built model. Instead
the future design shall be placed in a project (non-As-Built) database with content type [PRO], with a
separate Site and Zone-hiearchy containing a Responsible Code identifying the Project Short Code
for the future design. In other words, the future design shall be treated as a separate Project.
When such a future design is out of date or the design is determined not to be realized, Administrator
is responsible for removing the database from the MDBs and set its content-type to [VOI]. This will
make the volume available for other projects.


4.4.3 General Zone Sub Set Codes

The table describing the zone naming consists of 3 columns.
The first column gives as-built zone names. These will be available in the as-built databases. No other
zone names shall be used in as-built design without prior accept by company.
The second column gives possible project zones. Not all project zones will be used in a single project.
Contractor may use a selection of project zones or use the as-built names in the project databases.
Any extra need for project zones must be communicated to Company. More than one might be
included in the as-built zone as indicated in the table. The responsible code shall be added to the
project zone name for modification projects.
Description consists of the discipline long code and a descriptive text.
In the working hierarchy, the site area code might be an overall code and the zone area code a sub
area. In as-built, the zones are to be includes as the split in the as-built hierarchy.
4.4.4 Subset Codes for PDMS – Piping

ann is the Area Code inherited from the Site Area Code or Sub area. Also see table “Subset Codes for
PDMS – Piping” in the relevant appendix.
Tag is skid tag number.
## is the Piping system code from the relevant ENS document
system description is the piping system description from the relevant ENS document
Piping Zones
As-Built Project Description
ann-PIPE-## ann-PIPE-##(_rspc) PIPE - System ## - system description
ann-PIPE-MISC ann-PIPE-MISC(_rspc) PIPE - Miscellaneous
ann-PIPE-## ann-PIPE-{tag}(_rspc) PIPE – Vendor Piping for {tag}
NA ann-PIPE-TIEIN(_rspc) PIPE – Tie In
NA *3) ann-PIPE-EXISTING(_rspc) PIPE – As-Built remodeled.
NA *3) ann-PIPE-FUTURE(_rspc) PIPE - Future
NA ann-PIPE-DEMOLITION(_rspc) PIPE - Demolition
NA ann-PIPE-TEMPxxx(_rspc) *1) PIPE - Temp
*1) The characters xxx at the end of the TEMP-zone name shall be replaced by an explanatory text
for the Temporary zone. Temporary design shall normally be placed in separate, deferred [TMP]-type
databases provided by the Hub Administrator.
*2) May be included in the mechanical hierarchy in the project phase as part of a skid.
*3) Agree As-Built with Company


4.4.5 Subset Codes for PDMS – HVAC

ann is the Area Code inherited from the Site Area Code or Sub Area .
HVAC Zones
ann-HVAC-EQUIPMENT ann-HVAC-EQUIPMENT(_rspc) HVAC - Equipment
ann-HVAC-EXTRACTXX ann-HVAC-EXTRACTXX(_rspc) HVAC - System ## - system description
ann-HVAC-SUPPLYXX ann-HVAC-SUPPLYXX (_rspc) HVAC - System ## - system description
ann-HVAC-RESIRCULATEDXX ann-HVAC-RESIRCULATEDXX(_rspc) HVAC - System ## - system description
ann-HVAC-MISC ann-HVAC-MISC(_rspc) HVAC - Miscellaneous
ann-HVAC-EXISTING ann-HVAC-EXISTING (_rspc) *2) HVAC – Remodeled As-Built.

NA ann-HVAC-FUTURE(_rspc) *2) HVAC - Future
NA ann-HVAC-DEMOLITION(_rspc) HVAC - Demolition
NA ann-HVAC-TEMPxxx1(_rspc)*) HVAC - Temp
4.4.6 Subset Codes for PDMS – Mechanical

ann is the Area Code inherited from the Site Area Code or Sub Area
Mechanical Zones
ann-MECH-ACCESSROUTE ann-MECH-ACCESSROUTE(_rspc) MECH – Access Routes
ann-MECH-MAIN (_rspc) MECH – Access Routes Main
ann-MECH-MAINLAYDOWN(_rspc) MECH – Access Routes Main Lay-down
ann-MECH-PROCESS(_rspc) MECH – Access Routes Process
ann-MECH-UPPER(_rspc) MECH – Access Routes Upper
ann-MECH-SEC(_rspc) MECH – Access Routes Secondary
ann-MECH-SECPROCESS (_rspc) MECH – Access Routes Secondary Process
ann-MECH-SECUPPER(_rspc) MECH – Access Routes Secondary Upper
ann-MECH-DRAINBOX *2) Ann-MECH-DRAINBO(_rspc) MECH – Drain Box
ann-MECH-EQUIPMENT ann-MECH-EQUIPMENT(_rspc) MECH – Mechanical Equipment
ann-MECH-UTILITYSTATION ann-MECH-UTILITYSTATION(_rspc) MECH – Utility Stations
ann-MECH-MISC ann-MECH-MISC(_rspc) MECH - Miscellaneous
ann-MECH-MATERIALHANDLING *2) ann-MECH-LUG(_rspc) MECH – Lifting Lugs
ann-MECH-MONORAIL(_rspc) MECH – Mono Rails
ann-MECH-INDECKTANK *2) ann-MECH-INDECKTANK(_rspc) MECH – In-deck Tank


ann-MECH-{tag} *8) ann-MECH-{tag}(_rspc) MECH – Skid for {tag}
NA ann-MECH-PLATFORM *3) (_rspc) MECH - Platforms
NA ann-MECH-PEOPLE(_rspc) MECH - People
NA ann-MECH-RESERVEDVOLUME(_rspc) MECH – Reserved Volumes

NA ann-MECH-DECK(_rspc) *3) MECH – Deck
NA ann-MECH-LADDER(_rspc) *3) MECH – Ladder
NA ann-MECH-STAIR(_rspc) *3) MECH – Stair
NA ann-MECH-FOUNDATION(_rspc) *4) MECH – Foundation
NA ann-MECH-INSTRUMENT(_rspc) *5) MECH – Instruments
NA ann-MECH-ARCHITECT(_rspc) *6) MECH – Architect
NA ann-MECH-SAFETY(_rspc) *7) MECH – Safety
NA ann-MECH-ESCAPEROUTES *7) MECH – Escape Routes

NA ann-MECH-EXISTING(_rspc) *9) MECH -– Remodeled As-Built.
NA ann-MECH-FUTURE(_rspc) *9) MECH - Future
NA ann-MECH-DEMOLITION(_rspc) MECH - Demolition
NA ann-MECHC-TEMPxxx(_rspc) 1*) MECH- Temp
*2) Might be included in Structural as-built hierarchy
*3) Included in structural as-built hierarchy
*4) Included in Civil as-built hierarchy
*5) Included in Instrument as-built hierarchy
*6) Included in Architect as-built hierarchy
*7) Included in Safety as-built hierarchy
*8) For modeling skids with pipes and structures


4.4.7 Subset Codes for PDMS – Structural
The main principle is that everything belonging to a structure is defined with the structure. Hence the
hand railing and access ladder for a platform belongs to the platform, an in-deck tank belongs to the
deck etc. However a equipment support belong to a separate zone as the deck normally is secondary
steel and the support is outfitting.
ann is the Area Code inherited from the Site Area Code or sub area.
Structural Zones
ann-STRU-NODE ann-STRU-NODE(_rspc) STRU - NODE
ann-STRU-CA(_rspc) STRU – NODE Caste
ann-STRU-BU(_rspc) STRU – NODE Built Up
ann-STRU-DECKGIRDER ann-STRU-DECKGIRDER(_rspc) STRU - Deck Girders
ann-STRU-TRUSS ann-STRU-TRUSS(_rspc) STRU - Trusses
ann-STRU-TRUSSBRIDGE(_rspc) STRU – Truss Bridge
ann-STRU-TRUSSTUBULAR(_rspc) STRU - TRUSSTUBULAR
ann-STRU-CRANEPEDESTAL ann-STRU-CRANEPEDESTAL(_rspc) STRU – Crane Pedestal
ann-STRU- ann-STRU-DECKSTRUCTURE(_rspc) STRU – Deck ink Stiffeners, Railing and Flexibarriers
DECKSTRUCTURE
ann-STRU-INFILL(_rspc) STRU – Infill steel
ann-STRU-UPPERFLOOR(_rspc) STRU – Upper Floor
ann-STRU-MEZZDECK(_rspc) STRU – Mezzanine Deck
ann-STRU-FLOORBEAM(_rspc) STRU – Floor Beam
ann-STRU-DECKFRAMING(_rspc) STRU – Deck Framing
ann-STRU-INTEGRATEDTANK(_rspc) STRU – Integrated Tank
ann-STRU-WALL ann-STRU-WALL(_rspc) STRU – Bulk Head and Structural Wall ink Stiffeners
ann-STRU-BLASTWALL(_rspc) STRU – Blast Wall
ann-STRU-CLADDING(_rspc) STRU – Cladding
ann-STRU-WEAPROTSTRU(_rspc) STRU – Weather Protection Structure
ann-STRU-FLARETOWER ann-STRU-FLARETOWER(_rspc) STRU – Flare Tower
ann-STRU-SUPPORT ann-STRU-SUPPORT(_rspc) STRU – Equipment and Wall Support
ann-STRU-SUPPIDSIGN(_rspc) STRU – Id Sign Support
ann-STRU-SUPPARCWALL(_rspc) STRU – Architectural Wall Support
ann-STRU-SUPPEQLE1(_rspc) STRU – Equipment Support Less or Equal 1 Ton
ann-STRU-SUPPEQGT10(_rspc) STRU – Equipment Support Greater Than 1 Ton
ann-STRU-SUPPEQGT1LT10(_rspc) STRU – Equipment Support Gt 1 Lt 10 Ton
ann-STRU- SUPPEQGT10(_rspc) STRU – Equipment Support Greater Than 10 Ton
ann-STRU- SUPPAIREXHAUST(_rspc) STRU – Air Exhaust Support
ann-STRU- SUPPCAISON(_rspc) STRU –Caisson Support
ann-STRU- JSUPACK(_rspc) STRU – J tube Support
ann-STRU- CRANEBOOMREST(_rspc) STRU – Crane Boom Rest
ann-STRU-SUPLIFEBOAT(_rspc) STRU – Life Boat Supports
ann-STRU-PLATFORM ann-STRU-PLATFORM(_rspc) STRU – Large and Minor Access Platforms ink
railing, stairs and ladders.


ann-STRU-DROPPEDOBJECT(_rspc) STRU – Dropped Object Protection

ann-STRU-EXTERNALPLATFORM(_rspc) STRU – External Platforms
ann-STRU-INTERNALPLATFORM(_rspc) STRU – Internal Platforms
ann-STRU- ACCESSMAINPLATFORM(_rspc) STRU – Main Access Platforms
ann-STRU-MEZZANINEPLATFORM(_rspc) STRU – Mezzanine Platforms
ann-STRU-ACCMAINPLATFORMGT10(_rspc) STRU – Main Access Platform Gt 10 Ton
ann-STRU-EXTWALKWAY ann-STRU- EXTWALKWAY(_rspc) STRU – External Walkways and Escape Tunnels
ann-STRU-MECHHANDLING ann-STRU-MECHHANDLING(_rspc) STRU – Monorails and Lifting Lugs
ann-STRU-MONORAIL(_rspc) STRU – Monorails
ann-STRU-RUNWAYBEAM(_rspc) STRU – Runway beams
ann-STRU-LIFTINGLUG(_rspc) STRU – Lifting Lugs
ann-STRU-MAINLUG(_rspc) STRU – Main Lugs
ann-STRU-PIPERACK ann-STRU-PIPERACK(_rspc) STRU – Pipe Racks
ann-STRU-MAJOURPIPERACK(_rspc) STRU – Major Pipe Rack
ann-STRU-MINORPIPERACK(_rspc) STRU – Minor Pipe Rack
ann-STRU-ACCESS ann-STRU-ACCESS(_rspc) STRU – Access Stairs and Ladders between Deck
ann-STRU-LADDERSTAIR(_rspc) STRU – Ladders and Stairs
ann-STRU-EXTERNALSTAIR(_rspc) STRU – External Stairs
ann-STRU-LADDERTOACESSSPLTF(_rspc) STRU –
ann-STRU-STAIRTOWER ann-STRU-INTERNALSTAIR(_rspc) STRU – Stair Tower
ann-STRU-GRIDSYSTEM ann-STRU-GRIDSYSTEM(_rspc) STRU – Starters and Brackets for EIT Trays and
Equipment, Scaffolding Lugs
ann-STRU-ELECTROBRACKETS(_rspc) STRU –
ann-STRU-MISC ann-STRU-MISC(_rspc) STRU – Miscellaneous
ann-STRU-JACKET Ann-STRU-JACKET(_rspc)
NA ann-STRU-GRILLAGE(_rspc) STRU – Grillage and Sea Fastening
NA ann-STRU-TEMPSTEEL(_rspc) STRU – Temporary Steel
NA ann-STRU-FUTURE(_rspc) *2) STRU - Future
NA ann-STRU-DEMOLITION(_rspc) STRU - Demolition
NA ann-STRU-TEMPxxx(_rspc) 1*) STRU- Temp
NA ann-STRU-EXISTING(_rspc) 2*) STRU-Remodeled As-Built
For use in As-built Sites only, shall only be used after Company approval:
Only by approval
Zone Description
ann-STRU-OUTFITTING STRU - Outfitting
ann-STRU-PRIMARYMAINSTEEL STRU - Primary Mainsteel


Only by approval
Zone Description
ann-STRU-SECONDARYSTEEL STRU - Secondary steel
4.4.8 Subset Codes for PDMS – Architectural

ann is the Area Code inherited from the Site Area Code .
Architectual Zones
ann-ARCH-ESCAPETUNNEL ann-ARCH-ESCAPETUNNEL(_rspc) ARCH – Escape Tunnel
ann-ARCH-CEILING ann-ARCH-CEILING(_rspc) ARCH – Ceiling
ann-ARCH-FLOOR ann-ARCH-FLOOR(_rspc) ARCH – Floor
ann-ARCH-FURNITURE ann-ARCH-FURNITURE(_rspc) ARCH – Furniture
ann-ARCH-STAIR ann-ARCH-STAIR(_rspc) ARCH – Stair
ann-ARCH-WALL ann-ARCH-WALL(_rspc) ARCH – Walls
NA ann-ARCH-EXISTING(_rspc) *2) ARCH - Existing Architect Copied from As-Built or
remodeled.
NA ann-ARCH-DEMOLITION(_rspc) ARCH – Demolition
NA ann-ARCH-FUTURE(_rspc) *2) ARCH – Future
NA ann-ARCH-TEMP(_rspc)xxx *1) ARCH – Temp
4.4.9 Subset Codes for PDMS – Electrical

Electrical Zones
ann-ELEC-HVLADDER *3) ann-ELEC-HVLADDER(_rspc) ELEC – High Voltage Ladder, 1000 V and above
-ann-ELEC-LVLADDER *4) ann-ELEC-LVLADDER(_rspc) ELEC – Low Voltage Ladder, Upto 1000V
ann-ELEC-LVLADDER ann-ELEC-FIELDTRAY(_rspc) ELEC – Low Voltage Field tray
ann-ELEC-HTJBOX ann-ELEC-HTJBOX(_rspc) ELEC – Heat Tracing Junction Box
ann-ELEC-SPOWEMERG *2) *5) ann-ELEC-SPOWEMERG(_rspc) ELEC - Lighting & Small Power Emergency
ann-ELEC-SPOWNORM *2) *6) ann-ELEC-SPOWNORM(_rspc) ELEC - Lighting & Small Power Normal
ann-ELEC-SPOWUPS *2) *7) ann-ELEC-SPOWUPS(_rspc) ELEC - Lighting & Small Power UPS
ann-ELEC-SOCKETOUTLET ann-ELEC-SOCKETOUTLET(_rspc) ELEC - Socket Outlets 690 V for welding.
ann-ELEC-PUSHBUTTONS ann-ELEC-PUSHBUTTONS(_rspc) ELEC – Push Buttons
ann-ELEC-EQUIPMENT ann-ELEC-EQUIPMENT(_rspc) ELEC – Tagged Equipment
ann-ELEC-HEATER(_rspc) ELEC – Heater
ann-ELEC-EQEARTHING(_rspc) ELEC – Earthing
ann-ELEC-EQMOTOR(_rspc) ELEC – Motor


ann-ELEC-EQHVEQUIPROOM (_rspc) ELEC – High Voltage Equipment Room

ann-ELEC-EQLVEQUIPROOM(_rspc) ELEC – Low Voltage Equipment Room
ann-ELEC-EQTRANSFORMERROOM(_rspc) ELEC – Transformer Room
ann-ELEC-EQSWGROOM(_rspc) ELEC – Switch Gear Room
ann-ELEC-MISC ann-ELEC-MISC(_rspc) ELEC – Miscellaneous
ann-ELEC-JBPAD ann-ELEC-JBPAD(_rspc) ELEC – JB Pad
NA ann-ELEC-EXISTING(_rspc) *6) ELEC – Remodeled As-Built.
NA ann-ELEC-SUPP(_rspc) ELEC – Support Grid
NA ann-ELEC-DEMOLITION(_rspc) ELEC - Demolition
NA ann-ELEC-FUTURE(_rspc) *6) ELEC - Future
NA ann-ELEC-TEMPXXX(_rspc) *1) ELEC - Temporary
*2) Relevant junction boxes included
*3) Norsok system 1
*4) Norsok system 3
*5) Norsok system 82
4.4.10 Subset Codes for PDMS – Instrumentation

Instrument Zones
ann-INST-LADDER *2) ann-INST-LADDER(_rspc) INST – Cable Ladder Instrument
ann-INST-LADDER ann-INST-FIELDTRAY(_rspc) INST – Field Tray
ann-INST-CENTRALEQUIP ann-INST-CENTRALEQUIP(_rspc) INST – Central Equipment
ann-INST-CER-EQUI(_rspc) INST – Central Equipment Room
ann-INST-LER-EQUI(_rspc) INST – Local Equipment Room
ann-INST-TER-EQUI(_rspc) INST – T Equipment Room
ann-INST-MCR-EQUI(_rspc) INST – M Equipment Room
ann-INST-FIELDEQUIP ann-INST-FIELDEQUIP(_rspc) INST – Field Equipment
ann-INST-FIELDCONTRPANE (_rspc) INST – Field Control Panel
ann-INST-SAMPLESTATION(_rspc) INST – Sample Station
ann-INST-RIOI/OCABINETS(_rspc) INST – IO Cabinets
ann-INST-INSTRUMENTOFFLINE(_rspc) INST – Instrument
ann-INST-AIRMANIFOLD(_rspc) INST – Air manifolds
ann-INST-REMOTEIO(_rspc) INST – Remote IO


ann-INST-JUNCTIONBOX(_rspc) INST – Junction Boxes

ann-INST-MISC ann-INST-MISC(_rspc) INST – Miscellaneous
NA ann-INST-EXISTING(_rspc) *3) INST – Existing Instrument Cable Ladder Copied
from As-Built or remodeled.
NA ann-INST-DEMOLITION(_rspc) INST - Demolition
NA ann-INST-FUTURE(_rspc) *3) INST - Future
NA ann-INST-TEMPxxx(_rspc) *1) INST - Temporary
*2) Ladder contains Instrument and Telecom cables. Norsok system 3
4.4.11 Subset Codes for PDMS – Telecom

ann is the Area Code inherited from the Site Area Code or sub area
Instrument Zones
ann-TELE-CENTRALEQUIP ann-TELE-CENTRALEQUIP(_rspc) TELE – Central Equipment
ann-TELE-CER-EQUI(_rspc) TELE – Central Equipment Room
ann-TELE-LER-EQUI(_rspc) TELE – Local Equipment Room
ann-TELE-TER-EQUI(_rspc) TELE – T Equipment Room
ann-TELE-BUR-DP(_rspc) TELE – BUR-DP
ann-TELE-EARTHING(_rspc) TELE – Earthing
ann-TELE-FIELDEQUIP ann-TELE-FIELDEQUIP(_rspc) TELE – Field Equipment
ann-TELE-JUNCTIONBOX(_rspc) TELE – Junction Box
ann-TELE-CCTV(_rspc) TELE – CCTV Cameras
ann-TELE-LAN(_rspc) TELE – LAN
ann-ITELE-ENT(_rspc) TELE –ENT
ann-TELE-GMDSS(_rspc) TELE - GMDSS
ann-TELE-PABX(_rspc) TELE - PABX
Ann-TELE-RADAR(_rspc) TELE - Radar
ann-TELE-STAND(_rspc) TELE- Stands
ann-TELE-PA(_rspc) TELE- Public Announcement and Alarm
ann-TELE-ANTENNA(_rspc) TELE- Antenna
ann-TELE-MISC ann-TELE-MISC(_rspc) TELE – Miscellaneous
NA ann-TELE-DEMOLITION(_rspc) TELE - Demolition
NA ann-TELE-EXXISTING(_rspc) *2) TELE – Remodeled As-Built
NA ann-TELE-FUTURE(_rspc) *2) TELE - Future
NA ann-TELE-TEMPxxx(_rspc) *1) TELE - Temporary


*2) Agree As-Built with Company.
4.4.12 Subset Codes for PDMS – Safety

Safety Zones
ann-SAFE-DETECTORS *2) ann-SAFE-DETECTORS(_rspc) SAFE – Detector Beam
ann-SAFE-EQUIPMENT ann-SAFE-EQUIPMENT(_rspc) SAFE – Equipment
ann-SAFE-SMALLEQUIPMENT(_rspc) SAFE – Small Equipment
ann-SAFE-CONTROLPANEL(_rspc) SAFE – Control Panel
ann-SAFE-LIFESAVING(_rspc) SAFE – Life Saving Equipment
ann-SAFE-FIREFIGHT(_rspc) SAFE – Fire Fighting Equipment
ann-SAFE-EXTINGUISHER(_rspc) SAFE – Fire Extinguisher
ann-SAFE--FIREAREA ann-SAFE-FIREAREA(_rspc) SAFE – Fire Area
ann-SAFE-ESCAPEROUTES ann-SAFE-ESCAPEROUTES(_rspc) SAFE – Escape Routes
ann-SAFE-JUNCTIONBOX ann-SAFE-JUNCTIONBOX(_rspc) SAFE – Junction Box
ann-INST-MISC ann-TELE-MISC(_rspc) TELE – Miscellaneous
NA ann-TELE-EXISTINGE(_rspc) *3) TELE –Remodeled As-Built
*2) Junction boxes may be modeled in the same zone as detectors
4.4.13 Subset Codes for PDMS – Civil

Civil Sites are used only for onshore Process Plant PDMS Projects. ann is the Area Code inherited
from the Site Area Code or sub area.
Civil Zones


ann-CIVI-BASEPLATE ann-CIVI-BASEPLATE(_rspc) CIVI – Baseplate

ann-CIVI-EQUIPMENT ann-CIVI-EQUIPMENT(_rspc) CIVI – Equipment
ann-CIVI-FOUNDATION ann-CIVI-FOUNDATION(_rspc) CIVI – Foundationt
ann-CIVI-ROAD ann-CIVI-ROAD(_rspc) CIVI – Road
ann-CIVI-CONCRETESTRUCT ann-CIVI-CONCRETESTRUCT(_rspc) CIVI – Concrete Structure
ann-CIVI-MISC ann-CIVI-MISC(_rspc) CIVI – Miscellaneous
NA ann-TELE-EXISTING(_rspc) *2) TELE – Remodeled As-Built
databases provided by the Hub Administrator


4.4.14 Subset Codes for PDMS – Scanning

Scanning can be implemented as point clouds or by remodeling based on the point cloud. If the
remodeling is based on proper discipline elements as for a project model, it shall be implemented in
the As-Built hierarchy as described in previous section.
Models remodeled in Cyclone or similar systems and converted electronically to PDMS using general
primitives shall generally be sorted into three main discipline groups:
 Piping, Mechanical, HVAC

 Structural, Architectural, Pipe Support
 Electrical, Instrumentation, Telecom, Safety
Typical site name structure will be:
Site: ann-IMPL desc: IMPL – {Area Code}

Zone ann-IMPL-PMH-{text} desc: IMPL – PIPE, MECH and HVAC – {Descriptive text}
ann-IMPL-SAZ desc: IMPL – STRU, ARCH and SUPP – {Descriptive text}
ann-IMPL-EITF desc: IMPL – ELEC, INST, TELE and SAFE – {Descriptive text}
Typical Zone text: LQEI20070910

PMO04103390-20070723
Typical Description: LQEI Interface scanned 20070910

PMO04103390 Area Around 27-KZ001 scanned 20070723
Point clouds made available directly in PDMS shall be implemented as follows:
Site: ann-SCAN desc: SCAN – {Area Code}

Zone ann-SCAN-{text} desc: SCAN – {Descriptive text}
The text in the zone name shall be a short version of the description but both descriptive with
reference to job number/responsible code and date:
Typical Zone text: LQEI20070910
PMO04103390-20070723
Typical Description: LQEI Interface scanned 20070910

PMO04103390 Area Around 27-KZ001 scanned 20070723


4.4.15 Subset Codes for PDMS – Pipe Support

Pipe Support Zone names are left to Contractor use, since Zone name may be affected by
Contractor-specific PDMS Pipe Support applications. If not affected by such applications, the Zone
name shall be:
<Area Code >-PSUP-SUPPORT
Example Zone name:
{ann}-PSUP-SUPPORT
description ‘PSUP’
It is recommended that there is a logical connection between the Pipe Support-element in the Pipe
Support Zone and the Pipe Support ATTA-element in the PIPE in the Piping Zone.
4.5 PDMS Design Hierarchy – Sub-ZONE Level

All tagged elements shall be represented by legal ZONE members, legal PIPE and HVAC BRAN
members, FRMW, FRMW members and SUBEQUPMENT. Under no circumstances shall a primitive
be tagged.
4.5.1 Sub-ZONE Name Syntax

Also see chapters 8 for Sub-ZONE element attributes. UDA’s
Tagged Equipment, Field Equipment, manual valves and junction boxes
All tagged elements shall have the actual tag number as name attribute (with the exception of piping
line tags ) for As-Built data:
<ENS Tag No>_<Responsible Code*>
The ENS Tag No is the Tag number from the relevant ENS document.
Examples
21-PC01A(M) - Mechanical Tag (As-Built)

20PA201 - Mechanical Tag (As-Built)
20PA201_TYR - Same Tag modified by the Tyrihans Project
No tagged element shall be represented with primitives alone. All sub-ZONE elements shall include
geometry. No “empty” elements allowed.
PDMS NOZZ elements representing Tagged Equipment Nozzles in the model shall be named:
<ENS Equipment Tag No>/<Nozzle No>_<Responsible Code*>
Nozzle No is written like “N1”, and is the Nozzle number from the P&ID or Equipment Drawing.


Examples
20PA201/N3 - Nozzle 3 of Tag 20PA201 (As-Built)

20PA201/N3_TYR - Same Nozzle on a Tag modified by the Tyrihans Project
When naming model elements for clarity ie. A compressor hood,

Naming different parts of a equipment for clarity the following naming convention shall be used:
<tag>/<descriptive text>
27KA207/HOOD
*As-Built equipment shall not have a Responsible Code. Responsible code only used when naming
conflict.
Tagged Pipes
Pipes shall be sufficiently identified at PIPE name level to make it a unique element i.e. a combination
of system number, sequence number, area code, suffix and possibly product service code according
to the ENS document.
Generally:
<ENS Tag short name>_<Area code >- <Suffix>_<Responsible Code*>
Suffix will generally be used to avoid naming conflicts when a pipe visits the same area more than
once. In addition the following suffixes may be used:
Z Hookup
X Installed on deck before lifting
Suffix may only be used when needed to make pipe name unique.
The <ENS Tag short name> shall be similar to the shorter Pipe Tag shown in some ENS documents,
and is a short form of the full Line Tag Number/Piping Line Number. If ENS Tag short name is not
described, contractor needs to agree short name with Company.
Example As-Built Pipe from Veslefrikk:
Line number from the ENS document: 12”-PL-21022-BC21A

PDMS Pipe in area DK02: PL-21022_DK02-A
Note that the Veslefrikk ENS document requires the use of Product Service code to make the Line
number unique. The part in bold characters (PL-21022) is the ENS Tag short name in this case.
Example As-Built Pipe from Kristin:
Line number from ENS document: 50L0501-0400WS-AR71


PDMS Pipe in area C2: 50L0501_C2-A
Note that the Kristin ENS document does not require the use of Product Service code to make the
Line number unique. Note the appearance of the letter L between System number and Sequence
number. The part in bold characters (50L0501) is the ENS Tag short name in this case.
Other Examples
43L0250_M14-A - As-Built Pipe 43L0250 in Area M14

43L0250_M22 -A - As-Built Pipe 43L0250 continues in Area M22
43L0250_M14-A_SFLL
- Pipe 43L0250 in Area M14, modified by the Statfjord Late Life Project
Special items
Special Items shall usually be named by their Tag name as other Tagged items. In cases where there
is more than one element in PDMS using the same Special Item number, use a Suffix to separate the
different Special Item elements in the PDMS Project.
Such duplicate elements representing one of many equal Special Items, shall be named:
<Special Item>_<Suffix>_<Responsible Code*>
where the Suffix after the delimiter ( _ ) is used to separate all elements with the same Special item
name.
* As-Built SI elements shall not have a Responsible Code reference.
Examples
SI0019_001 - First instance of this Special Item number in the PDMS model
SI0019_002 - Second instance of this Special Item number in the PDMS model
SI0019_004_ALVE - Fourth instance of this S.I., modified by the Alve Project
4.5.2 Pipe Supports

The Pipe Support shall be represented with an ATTA in the PIPE-element, representing the location of
the connection to the Pipe Support structure in the Pipe. The ATTA shall be named like:
<ENS Pipe Support Name>/<Suffix A-Z>_<Responsible Code*>
Examples:
PS-M14-4255/A - For Pipe Support PS-M14-4255, connection to first Pipe
PS-M14-4255/B - For Pipe Support PS-M14-4255, connection to second Pipe
A33-997-590/A - For Pipe Support A33-997-590
Note that the Pipe Support name is determined by the relevant ENS document number and follows
the Pipe Support naming convention for the relevant PDMS model.


4.5.3 Skids and package tags

Supplier information shall be incorporated into Contractor 3D CAD model.
A skid might be modeled as a ZONE named ann-MECH-{tag} where {tag} is the package tag. Below
the zone, a EQUIPMENT is holding the package tag. Below the equipment, there are sub equipments
holding tags on the skid. Under the zone there will be a possibility of a STRU holding structural
elements, and PIPE elements as required. Untagged items remain unnamed as primitives or SUB
EQUIPMENT.
*1) Pipes might be modeled in the piping hierarchy.
4.6 Modifying existing tag

When modifying existing tagged equipment or Piping, a copy of the tagged item shall be made from
the As-Built hierarchy and placed in the project hierarchy.
The original As-Built element shall not be modified until As-Built modeling is conducted.
The purpose is to maintain the As-Built model until elements have physically been modified offshore
or at the onshore Process plant.
Only the required design elements for the modification shall be copied. The tagged element shall be
made unique from the As-Built tag by adding the Responsible Code to the name element.


5 NAME STANDARD FOR ADMINISTRATIVE ELEMENTS
5.1 Locations
Locations will be named with a logical name describing the responsible company and its location. A
typical name will be:
CostainManchester.
The three letter satellite identification code shall be set to the location code described above.
5.2 Update Events

Update events shall be named by adding UpdateEvent to the location name. Typical name will be:
CostainManchesterUpdateEvent


6 WORKING IN THE PROJECT HIERARCHY
6.1 General
As described before, the working hierarchy is separated from the As-Built hierarchy by adding a
responsible code. See Chapter 2.3 for more details.
6.2 EXECUTING MAJOR PROJECTS

When executing major projects, the standard rule using a responsible code will be used. A typical
piping hierarchy for project named KFGC will be:
Site: A21-PIPE_KFGC
Zone A21-PIPE-56_KFGC
6.3 EXECUTING MMO PROJECTS

When executing MMO projects, it will normally not be practical to use a responsible code for each
projects. For normal MMO work, a responsible code MMO is used. The split between different jobs
will be at zone level. The MMO responsible code will be swapped with a work order. A typical
hierarchy will be:
Site: A21-PIPE_MMO
Zone: A21-PIPE-56_MMO-004546
Only zones needed for the job will be created.


7 CATALOGUE AND SPECIFICATIONS
7.1 General
All Catalogue and Specifications components shall be incorporated and managed by the Contractor.
Company accepts on approval Contractor to use in-house master-catalogues. If Contractor does not
have a master catalogue available, the preferred Catalogue and Specifications are the Catalogue and
Specifications from the Maintenance and Modification Contractor, where available.
If Catalogues and Specifications from more than one contractor exist in the same PDMS project, a
separate MDB must be defined for each set of Contractor Cats & Specs. A separate MDB must be
used when updating the Specs because naming conflicts may exist between Catalogue Components
from different Contractors. However, this is not a problem once the Specs have been created,
because then the correct Catalogue Component will be identified by DB reference.
7.2 Naming conventions
7.2.1 SPWL Name Syntax

SPWL name syntax contains Plant Code, Discipline Long code and the Responsible Code:
<Plant code>-<Discipline Long code>_<Responsible Code>
Example SPWL from Veslefrikk A:
VFA-PIPE_AK
Plant code
Discipline Long code
Responsible Code
7.2.2 SPEC Name Syntax

SPEC name syntax contains Spec name and Responsible Code.
<SPEC Name>_<Responsible Code>
Example SPEC:
AC200_AK
SPEC Name
Responsible Code


7.2.3 Spec Component Name Syntax

SPCO name syntax contains Spec name, Responsible Code and Name
Example:
AC200_AK/ELB90200200
Spec Name
Responsible Code
Name


8 ATTRIBUTES AND USER DEFINED ATTRIBUTES (UDA)
8.1 User Defined Attributes
8.1.1 General
The common User Defined Attributes defined in this document shall be used whenever possible.
If Contractor specific UDAs are required the UDA World (UWRL), UDA Group (UGRO), and User
Defined Attribute (UDA) elements shall have names prefixed with the Contractor code or another
agreed code (e.g. OPE or CAP) to make the UDA unique.
The UDA-element in PDMS shall be named with uppercase letters, like “OPETAGNO”. No delimiter of
any kind shall be used in the UDA name. See example below.
The UDNA attribute shall be identical to the UDA element name, but in upper camel case (each part
of the name starts with a upper case). The ABLENGTH attribute value shall be equal to the UDA
Name length.
Company User Defined Attributes shall have UDA Name and UDNA attribute starting with “Ope” for
“Operator”.
Example UDA for Company Tag Number:
Name /OPETAGNO
UDNAME ‘OpeTagNo’
ABLENGTH 8
UTYPE TEXT
ULEN 120
DESCRIP ‘Operator Tag No’
ELElist PIPE EQUI VALV INST PCOM ATTA
The DICT-database with the Company UDAs shall be Current in MDBs so that designers can
complete the UDA-values on PDMS elements as required.
When Compiling UDAs in PDMS Lexicon, all DICT-databases in the PDMS Project shall be Current in
the MDB, otherwise Ukeys may not be unique. Alternatively, Contractor shall be absolutely certain
that no other UDA-elements with the same name exist in the PDMS Project. See Aveva PDMS
Lexicon Documentation.


8.1.2 Common User Defined Attributes
The following attributes shall be used whenever possible:
UDName UType ULen Descript EleList *

ZONE PIPE
ChangeRef TEXT 120 Change reference
EQUI SUBE
REST HVAC
STRU SCTN
CMPF STWALL
FITT CMFI
SBRF GWALL
FLOOR SPEC
SCOM
ChemClean TEXT 12 Chemical Cleaning PIPE
ColCode TEXT 20 Color Code PIPE
Critical LOGICAL Critical Line PIPE
Discipline TEXT 4 Long Discipline SITE

Code
HeatTrace TEXT 12 Heat Trace PIPE

PIPE
HeatTrMent LOGICAL Post Weld Heat
Treatment
ZONE PIPE
Hold LOGICAL Hold Flag
EQUI SUBE
REST HVAC
STRU SCTN
CMPF STWALL
FITT CMFI
SBFR GWALL
FLOOR SPEC
SCOM
ZONE PIPE
TEXT 120 Hold description
EQUI SUBE
REST HVAC
STRU SCTN
CMPF STWALL
FITT CMFI
SBRF GWALL
FLOOR SPEC
HoldDesc
SCOM
HoldData TEXT 120 Hold Data ZONE PIPE
EQUI SUBE


REST HVAC
STRU SCTN
CMPF STWALL
FITT CMFI SBRF
GWALL FLOOR
SPEC SCOM
LineLabel TEXT 60 PID Line Label PIPE
TEXT 25 None Destructive PIPE

NdeGroup Testing
Pedcat TEXT 25 Ped Category PIPE
PidRef TEXT 120 P&ID Reference PIPE
TEXT 25 Positive Material PIPE

PMI Identification
PressDesMax TEXT 10 Max design pressure PIPE
PressDesMin koe TEXT 10 Min design pressure PIPE
TEXT 10 Max operation PIPE

PressOperMax pressure
TEXT 10 Min operation PIPE

PressOperMin pressure
PressTestMax TEXT 10 Max test pressure PIPE
PressTestMin TEXT 10 Min test pressure PIPE

ZONE PIPE
StatusCode TEXT 20 Status code
EQUI SUBE
REST HVAC
STRU SCTN
CMPF STWALL
FITT CMFI
SBRF GWALL
FLOOR SPEC
SCOM
ZONE PIPE
StatusDesc TEXT 120 Status description
EQUI SUBE
REST HVAC
STRU SCTN
CMPF STWALL
FITT CMFI



SBRF GWALL
FLOOR SPEC
SCOM
ZONE PIPE
TEXT 120 Status Data
EQUI SUBE
REST HVAC
STRU SCTN
CMPF STWALL
FITT CMFI
SBRF GWALL
FLOOR SPEC
StatusData
SCOM
StressIsoRef TEXT 50 Stress Iso PIPE
SystemStatus TEXT 25 System Status PIPE
TEXT Max design PIPE

TempDesMax temperature
TEXT Min design PIPE

TempDesMin temperature
TEXT Max operation PIPE

TempOperMax temperature
TEXT Min operation PIPE

TempOperMin temperature
TempTestMax TEXT Max test temperature PIPE
TempTestMin TEXT Min test temperature PIPE
TestDuration TEXT 25 Test Duration PIPE
TestMedium TEXT 25 Test medium PIPE
TestPack TEXT 25 Test Pakke PIPE
WeightDry TEXT Dry weight EQUI
WeightWet TEXT Wet weight EQUI
* The UDAs may also be used for other element types if required


8.2 Standard Attributes and common UDAs for SITE elements
Name Data Type Value

Name STRING See chapter 4.3.1
Description STRING <Discipline Long Code> - <Area> - <Area
Description>
Position2 POSITION E 0 N 0 U 0 WRT World
Orientation3 ORIENTATION Y is N WRT /* and Z is U WRT World
Module STRING Area Code
:Discipline STRING Long Discipline Code
Example Site name and description from Veslefrikk A for Structural Site:
Name: /DK04-STRU
Description: ‘STRU - DK04 - Upper Mezzanine Deck Manifolds’
8.3 Required Attributes and common UDAs for ZONE elements
Name Data Type Value

Name STRING See chapter 4.4.1
Description STRING As defined in chapter 4.4
Position4 POSITION E 0 N 0 U 0 WRT World
Orientation5 ORIENTATION Y is N WRT /* and Z is U WRT World
Module STRING Sub area if required
2
Shall not be altered. Position of SITE shall always be the same as World.
3
Shall not be altered. Orientation of SITE shall always be Y-axis North and Z-axis Up with respect to World coordinates.
4
Shall not be altered. Position of ZONE shall always be the same as World.
5
Shall not be altered. Orientation of ZONE shall always be Y-axis North and Z-axis Up with respect to World coordinates.


9 LEVELS, OBSTRUCTIONS AND RESERVED VOLUMES
9.1 Level
By using Level it is possible to set individual display levels for a specific element in the model. An
element can for instance have level from 0-10 and by this be visible regardless of level display setting.
The following general rules shall apply:
 Solid objects shall be visible in design at level 6
 Solid objects shall be represented with a shape with obstruction 2
 Reserved volumes shall be modeled with obstruction 1
9.2 Obstruction
The following general rules shall apply:
 OBST 2, All solid materials

 OBST 1, All soft materials such as insulation, maintenance and reserved areas
 OBST 0, Materials modeled for info. No clash check
9.3 Reserved Volumes and Areas

For PDMS Projects where Reservation of Volumes for future projects is to be used, the reserved
volumes shall be in the Design database named:
<Teamname>/DESI-G-A00-RESERVED
where A00 is the “General”-Area found in the relevant appendix.

The database shall have a single Site /RESERVED-VOLUMES, and each Project using volume
reservation shall have a Zone with name and description:
Zone name: /RESVOL-<Responsible Code>-mmmYYYY
Description: Reserved Volume until mmm YYYY for Project <Project Name or WBS>, contact <Project
Responsible Person>, date by <created by User>
Example Zone in Snorre B:

Name: /RESVOL-IOR-Sep2007
Description: Reserved Volume until Sep 2007 for Project SNB IOR, contact aed6, 12.10.06 by kkva
Reserved Volumes shall be represented by one or more Equipment with simple Equipment primitives
with OBST 2, with level 1-6. Other Projects shall avoid using volumes which are reserved in the
Reserved Volume database.
The Reserved Volume database shall not be used for early stage Layout of Project equipment.
Instead, use a proper Project database for such Layout design.
6
additional persons may be listed


The Reserved Volume zone for a Project shall be removed as soon as possible after Project start, and
replaced by correct PDMS-elements in a Project database.


10 AS-BUILT MODELING AND DEMOLITION

If As-Built modeling is to be performed in the project, Contractor shall perform As-Built modeling of
new and modified elements in the PDMS Project during the As-Built phase of the project.
As-Built modeling may include moving design data from project databases to the correct location in
the As-Built design hierarchy, eventually allowing the project databases to be removed (not the
continuous Maintenance and Modification project). If an As-Built Site and database does not already
exist for this area, the project Site and database may be renamed to be an As-Built Site and
database.
Demolished elements shall be deleted from the model after removal.
During As-Built modeling:
 Empty Project Site and Zone elements shall be deleted

 Sub-Zone elements shall be transferred to the correct location in the As-Built hierarchy:
1. Pipe, Branch and Branch members shall be data consistent and form a
interconnecting Piping network7 in the As-Built Zone
2. Branches connected to Equipment shall be connected to the correct As-Built

Equipment Nozzle element.
 Any Project Short Codes in the element name shall be removed, and the element name shall be
changed to the correct As-Built name.
In all circumstances, data consistency shall be maintained in the Design model. Connections to As-
Built drawings shall be maintained.
7
see Aveva PDMS documentation


11 DEFINITIONS
11.1 Definitions
As-built
Last revision of an LCI item updated to reflect the true status of completed work with relation to
specified tolerances.
Satellite Administrator
Provider of one or more of the following services directly to Company; Engineering (E), Procurement
(P), Construction (C), Installation (I), Hook-Up (H), Marine and/or Commissioning.
Hub Administrator
Responsible for administering and managing the PDMS Global Hub location.
Information
Information elements in the form of drawings, documents, indexes, databases, CAD-files, 3D models
etc.
Engineering Numbering System (ENS)

Numbering system defining how tagged items and LCI documents and drawing shall be coded and
numbered to obtain a uniform structure.
Life Cycle Information (LCI)

Life Cycle Information: Information required by the Company for engineering, preparation for
operations, start-up, operation, maintenance, repair, modification and decommissioning of a plant. LCI
includes information submitted to the Company and retained by the Supplier on behalf of the
Company.
PDMS Project
The 3D PDMS CAD model. A collection of PDMS databases where the PDMS work takes place:
design modelling, drawing production, Cats & Specs work, reports and system administration.
Master Project
A single Contractor or Company PDMS Project which functions as a library for common PDMS
information to be used in other PDMS Projects. Does not contain a Design model, instead it typically
contains common catalogue information, drawing templates and UDA definitions. AVEVA supplies a
Master Project called MAS.
Supplier
Provider of a product, i.e. producer, distributor, retailer or vendor of a product. The scope delivered by
a supplier is normally defined in a purchase order or frame agreement.
Technical information
Structured plant and equipment information for offshore/onshore facilities as planned, built and
modified at all times. Technical information consists of plant-specific and equipment-specific
information. The former includes tags-register, equipment, drawings, 2D CAD and 3D models, data
sheets, certificates, descriptions, handbooks, manuals and the links between them. Equipment-
specific information includes data sheets, drawings, descriptions, spare parts lists and logistics-
related information for standard purchased equipment, which may be used in more than one place,
i.e. in more than one tag number and/or more than one plant.


11.2 Abbreviations
ABA Area Based ADP

ADP Automatic Drawing Production
CAD Computer Aided Design
ENS Engineering Numbering System
FAB (master The Fabricom Master Project
project)
LCI Life Cycle Information
LMI Laser Model Interface
MAS (master The AVEVA Master Project
project)
MDB Multiple Database, collection of PDMS databases in the PDMS Project
MPA (master The Aker Kværner Master Project
project)
MPR (master The Vetco Aibel Master Project
project)
MPx Expression used to describe all Master Projects
PDMS Plant Design Management System
REM (master The Reinertsen Master Project
project)
rspc Responsible Code
UDA User Defined Attribute in PDMS
WGE (master The Wood Group Engineering Master Project
project)


12 MODIFICATIONS TO PREVIOUS VERSION

Revision
1, Draft A First draft / Draft A


08-Annex F PDMS Naming Conventions

Uploaded by

Document Information

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

08-Annex F PDMS Naming Conventions

Uploaded by

Copyright:

Available Formats

ADDITIONAL TECHNICAL REQUIREMENTS

DOCUMENTATION FOR OPERATIONS (DFO)

ANNEX F – PDMS Naming Convention

Document No.: Rev.: Page:

Document Title: PDMS Naming Convention

Information: Viewpoint of the PDMS Users in Norway

01 06.12.2007 Issued for implementation KOE

Rev. Issue Description Made Chk'd Disc. Proj.

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 1 of 44

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 2 of 44

4.5.3 Skids and package tags..................................................................................................28

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 3 of 44

2.1 Discipline Long Code

* The codes may be used in special cases

The Discipline Long Codes shall be used in:

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 4 of 44

2.2 Discipline Short code

Discipline Short Code

The Discipline Short code shall be used in:

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 5 of 44

2.3 Responsible Code

2.3.1 Project Short Code

Example of Project Short Codes:

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 6 of 44

2.3.2 Reserved Contractor Codes

Contractor Contractor company Reserved DB numbers

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 7 of 44

2.3.3 Location Code

Location Code Company Location

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 8 of 44

3.2 Master databases

3.3 Team naming and use

Project database Team name: <Group>+<Discipline Short Code>

Example of Team names:

ASBDESP - As-Built design Team for PIPE

If needed, Discipline Short codes may be combined to form multi-discipline Teams.

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 9 of 44

3.4 Database naming

<Team>/<PDMS Type>-<Discipline Short code>-<Scope>-<Responsible Code>

Database Name Description

3.5 Database Content Type

Content-Type Description of Content-Type

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 10 of 44

3.6 Database description

Database description shall be constructed in the following way:

[Content-Type] <LOC1> project, discipline in area, for owner, date by Administrator

Content-Type: see chapter 3.5.

Master Project database description shall be constructed in the following way:

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 11 of 44

3.7 MDB required content

 PADD and ISOD-databases are not required.

DOCUMENT NO.: REVISION NO.: REVISION DATE: DOCUMENT OWNER:

ANNEX F – PDMS Naming Convention – Page 12 of 44