TR2231 AVEVA Plant CAD Model Requirements Ver4

Governing document Classification: Internal
AVEVA Plant CAD model requirements
Operation and maintenance (OM)

Technical and professional requirement, TR2231, Final Ver. 4, valid from 2013-10-01
Owner: Chif Eng Ops TPD TEX FOT
Validity area: Corporate technical requirements/On- and offshore

Governing document: AVEVA Plant CAD model requirements Classification: Internal
1 Objective, target group and provision ............................................................................................................... 4

1.1 Objective .................................................................................................................................................... 4
1.2 Target group .............................................................................................................................................. 4
1.3 Provision .................................................................................................................................................... 4
2 General principles ................................................................................................................................................ 4
2.1 AVEVA Plant and Global version .............................................................................................................. 4
2.2 3D model area coding................................................................................................................................ 5
2.3 Contractor work procedure ........................................................................................................................ 5
2.4 Project Identifier ......................................................................................................................................... 5
3 General Requirements ......................................................................................................................................... 6
3.1 Discipline codes ......................................................................................................................................... 6
3.2 Teams and databases ............................................................................................................................... 6
3.3 User and MDB administration.................................................................................................................... 6
3.4 Regular expunge of users ......................................................................................................................... 7
3.5 Reconfiguration .......................................................................................................................................... 7
3.6 Catalogues and specifications ................................................................................................................... 7
3.7 Language characters ................................................................................................................................. 7
4 Requirements to database schedule.................................................................................................................. 7
4.1 As-built databases ..................................................................................................................................... 7
4.2 Project databases ...................................................................................................................................... 7
4.3 Master project databases .......................................................................................................................... 8
4.4 Team naming and use ............................................................................................................................... 8
4.5 Database naming ....................................................................................................................................... 8
4.6 Content – Type in database description .................................................................................................... 9
4.7 Content of Maintenance and Modifications databases ............................................................................. 9
4.8 Copy from as-built databases .................................................................................................................... 9
4.9 Database description ................................................................................................................................. 9
4.10 MDB required content .............................................................................................................................. 10
5 Requirements to project deliverables .............................................................................................................. 10
5.1 Required project deliverables .................................................................................................................. 10
5.2 3D Model Report ...................................................................................................................................... 11
5.3 Model updates requirements of the AVEVA Plant 3D model.................................................................. 11
5.4 Greenfield model requirements ............................................................................................................... 12
5.5 Import design in AVEVA Plant from other 3D applications ..................................................................... 12
6 Requirements to As Built hierarchy ................................................................................................................. 12
6.1 3D model content ..................................................................................................................................... 12
6.2 As Built hierarchy ..................................................................................................................................... 12
6.3 SITE and ZONE name syntax ................................................................................................................. 13
6.4 List of legal As Built ZONEs .................................................................................................................... 13
6.5 As Built tagged elements ......................................................................................................................... 17
6.6 Special characters in AVEVA Plant names ............................................................................................. 20
6.7 UDAs to be completed at As Built ........................................................................................................... 21
6.8 As Built skid/package modelling .............................................................................................................. 21
7 Requirements to project hierarchy ................................................................................................................... 23
7.1 Task – based modelling ........................................................................................................................... 23
7.2 Project SITE and ZONE name syntax ..................................................................................................... 23
7.3 Legal Project Zones ................................................................................................................................. 23
7.4 Tag names for elements below ZONE level ............................................................................................ 24
7.5 UDAs to be completed in the project ....................................................................................................... 24
7.6 Use of project UDETs .............................................................................................................................. 25
7.7 Datestamp ................................................................................................................................................ 25
7.8 Model Encryption ..................................................................................................................................... 25
7.9 Data Access Control ................................................................................................................................ 25
8 Requirements to catalogue and specifications .............................................................................................. 25
8.1 General .................................................................................................................................................... 25
8.2 Naming conventions piping specs ........................................................................................................... 25
9 Requirements to level and obstruction volumes ............................................................................................ 26
9.1 Level......................................................................................................................................................... 26
Operation and maintenance (OM), Technical and professional requirement, TR2231, Final Ver. 4,
valid from 2013-10-01
Page 2 of 29
9.2 Obstruction ............................................................................................................................................... 26

9.3 Required use of level and obstruction ..................................................................................................... 26
9.4 Visibility of non – essential design ........................................................................................................... 27
10 Additional information ....................................................................................................................................... 27
10.1 Definitions and abbreviations .................................................................................................................. 27
10.2 Changes from previous version ............................................................................................................... 29
10.3 References ............................................................................................................................................... 29
Page 3 of 29
1 Objective, target group and provision
1.1 Objective
The objective of this document is to describe the best practice procedures for handling Company AVEVA
Plant Global 3D CAD models.
1.2 Target group

The Target group is everyone involved in creating or updating layout information.
1.3 Provision
This document is provided for in TR3110 Life Cycle Information (LCI), Technical requirements and
standards.
2 General principles
2.1 AVEVA Plant and Global version
Contractor shall use AVEVA Plant and AVEVA Global software version compatible with the Company
version.
Company is the Hub administrator and is responsible for creating and allocating.
 Teams
 Databases
 Extracts
 Locations
Company is responsible of setting up scheduled updates between the Hub and the contractors first
satellite in the Global project hierarchy.
Contractor shall receive and setup the Company Master Project (MPX) satellite for each of the locations
the contractor is responsible for if this is required for project execution. The MPX project contains
catalogue and specification databases required to display the model and requires a Global daemon
running in a working state.
Contractor shall ensure that their project Global daemon runs continuously in a working state at
contractors location, including at contractors sub-locations.
Contractor shall set up and execute daily scheduled updates between contractors first location and any
sub-locations in the Global hierarchy.
The AVEVA Plant 3D model shall be continuously updated to reflect the daily work progress according to
this document and TR2381. Contractor is responsible for managing all aspects of the design for
completing the work as required.
3D CAD data is published in Company systems to continuously follow up project activities in all phases.
Page 4 of 29
2.2 3D model area coding

Area codes in the 3D model shall be in according to requirements in ENS and shall be agreed upon with
Company prior to use. Contractor shall supply an illustrative drawing of the plant showing the area code
build up of the plant together with Contractors work procedure.
2.3 Contractor work procedure

Contractors shall establish a modelling work procedure which shall be delivered to Company.
The procedure shall as a minimum contain information about procedure for the subjects:
 Which person(s) or group at contractor is responsible for performing as-built.
 The procedure and method contractor designers uses when performing as-built updates of the
project scope of work.
 When as-built is to be performed by contractor.
 Naming convention in the design model, for SITE, ZONE and below ZONE level.
 Which person(s) is responsible for subdividing the Scope of Work into tasks in the project model.
 The person(s) at contractor responsible for restarting the AVEVA Plant Global daemon.
 The person(s) at contractor responsible for managing MDBs and assist in the allocation and
deallocation of databases to contractor.
 Where contractor designers shall place temporary design and where they shall place visible project
design.
 Where contractor designers shall place remodelled design from drawings (“exist modelling”).
 The person(s) at contractor responsible for creating new SITEs during project execution.
 The procedure for multidiscipline collision clash checking using AVEVA Plant clasher or similar in-
house applications.
 How the contractors designers ensure that they are working in the correct SITE and ZONE.
 How the contractors designers shall identify demolition in the project phase.
 Describe the use of the PDMS Global model during the engineering and fabrication phase
including the design release mechanism between contractors.
 Describe the fabrication procedure and method in relations with the use of the 3d model.
 Describe inter-contractor coordination procedure methods and responsibilities.
2.4 Project Identifier

Every project on the plant shall have a unique project identifier assigned by Company 3D cad
administrator.
The project identifier shall be used on:

• All SITE and ZONE element names in the project.
• All database names and descriptions containing the project.
Note: For Greenfield project see Greenfield model requirements.
Page 5 of 29
3 General Requirements
3.1 Discipline codes

The following discipline long codes and short codes shall be used in the 3D model:
Table 1: Discipline codes in AVEVA Plant

Discipline long code Discipline short code Description
ARCH A Architectural
CIVI C Civil
ELEC E Electrical
HVAC H HVAC
INST I Instrumentation
MECH M Mechanical
PIPE P Piping
PSUP Z Pipe Support
SAFE F Safety
STRU S Structural
TELE T Telecom
GENE G General
The discipline long code shall be used in:

 SITE name
 SITE description
 ZONE name
 ZONE description
 Team description
 Database description
 Spec World (SPWL) name
The discipline short code shall be used in:

 Team name
 Database name
3.2 Teams and databases

All teams and databases shall be created by Company. Database numbers are allocated by Company,
and the database file number shall be the same as the database number.
3.3 User and MDB administration

Contractor is responsible for establishing and administering the users and MDBs for contractor satellite
locations including sub-satellite locations.
Contractor is responsible for the MDB content required for completing the work. This includes databases
containing work from other contractors.
Contractor shall on request by Company, remove databases from MDBs and remove any claims from
databases required for service by Company or other contractors.
Page 6 of 29
3.4 Regular expunge of users

Once per day, contractor shall expunge all users at his locations and sub-contractor locations in the 3D
models using the “Expunge”-command (Expunge All Users and Claimlists) to remove any AVEVA Plant
“dead users” and clear all claimlists.
If the contractor CAD servers does not perform automatic removal of operating system file locks
immediately after an expunge and after each user exit from the AVEVA Plant application, contractor shall
also set up and execute a scheduled file lock removal after the scheduled expunge, to allow updates and
service on the 3D model databases.
3.5 Reconfiguration
Contractor is responsible for conducting own required reconfiguration. Company shall on request provide
databases for the reconfiguration.
3.6 Catalogues and specifications

Contractor is responsible for establishing and managing catalogues and specifications to complete the
work as required.
3.7 Language characters

Letters used in AVEVA Plant Names shall be from the 26 letters in the English alphabet only in addition to
the alpha numbers 0-9.
4 Requirements to database schedule
4.1 As-built databases

The as-built databases shall contain the as-built data transferred from projects. These databases shall be
accessible to all users of the 3D model. Disciplines shall be grouped into the following combinations for as-
built design databases if individual discipline databases are not required:
 Piping-Mechanical
 HVAC
 Structural-Architect
 Pipe Support
 Electrical, Instrumentation, Telecom and Safety
For team names and database names only, each discipline is represented by a single character, the
discipline short code.
As-built databases shall have database numbers lower than 3000.
4.2 Project databases

Project databases will be created by Company based on project requirements in cooperation with
contractor. Project database name shall contain a suffix identifying the contractor or the project.
Project databases shall have database number lower than 3000.
Page 7 of 29
4.3 Master project databases

Foreign databases shall not be used in Company 3D model, except from the MPX Project. Any eventual
databases from contractor master projects or any Aveva supplied master project databases shall be
copied into the MPX Project when needed, and distributed as foreign databases by including them into the
relevant 3D model.
Master project databases shall have database number 3000 or greater, and the number shall be agreed
with Company.
4.4 Team naming and use

Company 3D model shall contain separate Company teams for as-built databases and project databases.
As-built database team name: ASB+DES+<discipline short code>
Project database team name: DES+<discipline short code>
Example team names:
ASBDESPM - as-built team for PIPE-MECH

DESG - project design team for all disciplines (general)
Where useful, discipline short codes may be combined to form multi-discipline teams, like DESPM for
PIPE-MECH design.
4.5 Database naming

As-built design databases shall be named:
<team>/<database type>-<discipline short code>-<area>
Area shall be a facility legal area from the Engineering Numbering System for the facility.
The discipline short code can be combined for multi-discipline databases, like PM for PIPE-MECH design
databases.
Project design databases shall be named:
<team>/<database type>-<discipline short code>-<area>-<Project Identifier>-<contractor code>
Area shall be a facility legal area from the Engineering Numbering System for the facility. Depending on
the scope of the database, area may be a specific facility area, a group of areas like D00 for all drilling
areas, or a general “all areas” code like A00.
Contractor code, usually the contractor Global satellite location code, is only requiredfor databases in
projects executed at more than one AVEVA Global Plant location.
Page 8 of 29
4.6 Content – Type in database description

The term “Content-Type” database is used in the database description to classify the database contents,
and to give additional information to AVEVA Plant administrators and designers about how the database is
to be used in the 3D model, and in the creation and maintenance of MDBs.
Content-Type governs allocation and MDB-content requirements.
Table 2: Database Content-Type

Content-Type Description of Content-Type
[ASB] As-built. Contains information to show the as-built model.
Distributed to all contractors. Shall be current in the main MDB for
visibility and clash detection purposes.
[PRO] Project. Information relating to an on-going Detail Engineering
project, fabrication project or a FEED-project. Distributed to all
contractors.
[MPX] Master Project. Contains a master project database copy from
contractor master projects. Shall be current in the main MDB if
CATA or PROP-database, and current databases shall be
distributed to all contractors in order to show the complete model.
[STU] Study. Normally a Concept or Feasibility study project. Design in
this database only visible where database is primary. Usually not
distributed. Normally deferred in main MDB, which means not visible
and not available for clash detection.
[EXT] Extract database. Distributed only to the master location and to its
master database primary locations
[TMP] Temporary. Info only useful to a single contractor, like testing
design, own measure data or contractor-specific application
databases. Usually not distributed. Shall be deferred in main MDB if
present on location. Usually not visible and not available for clash
detection.
4.7 Content of Maintenance and Modifications databases

All Maintenance & Modification tasks and studies shall be located in [PRO] Content-Type databases.
Maintenance & Modification tasks that do not proceed to an implementation phase shall be transferred to a
[TMP] Content-Type database created for this purpose after agreement with Company.
4.8 Copy from as-built databases

If required, as-built database content not planned to be modified shall only be copied to a [TMP] Content-
Type database. All As-built design planned to be modified can be copied to a project [PRO] Content-Type
database.
4.9 Database description

Database description shall be used consistently in the 3D models. The description is used to classify the
contents of the database in order to aid the AVEVA Plant administrator in the maintenance of the MDBs at
his location.
For as-built design databases, the database description shall be:
[Content-Type] as-built, discipline in area, for owning Company, date by Company admin
Page 9 of 29
 discipline: Is the discipline long code (“all disciplines” may be used)

 area: Is the area code
 owning Company: Shall always be Company
 date: Is the date the database was created, or description modified
 Company admin: Is the Company short name of the Company AVEVA Plant administrator
responsible for creating or modifying the description.
For project design databases, database description shall be:
[Content-Type] procode: project, discipline in area, for owning Company, date by Company admin
 procode: the Project Identifier

 project: Is a descriptive project name
 owning Company: Is the project contractor
4.10 MDB required content

Each location shall have a main MDB, with the same name as the AVEVA Plant 3D model code, i.e. the
ABC AVEVA Plant 3D model shall have a MDB named /ABC. The purpose of this requirement is to ensure
that each contractor has at least one MDB showing the entire design model including on-going projects at
other contractors.
The main MDB shall as a minimum contain:

 All [ASB] design databases
 All [PRO] design databases
 All [ASB] catalogue and properties databases
 All [PRO] catalogue and properties databases
 All [MPx] catalogue and properties databases
 The Company main dictionary database ADMIN/DICT-OPE
This requirement also ensures that contractors designers have at least one MDB where they shall conduct
clash detection to detect volume collisions with on-going projects from other contractors or other locations
within the same contractor Company.
5 Requirements to project deliverables
5.1 Required project deliverables

Depending on the type of project executed by contractor, the following deliverables shall be handed over
to Company:
Feasibility study or Concept study:

 Single AVEVA Plant design database containing the 3D study model
 3D-model report, see 5.2
Pre-Engineering or FEED-project:
 One or more AVEVA Plant design databases containing the 3D project model
 3D-model report, see chapter 5.2
Detail Engineering and fabrication project:

Page 10 of 29
 Contractor shall perform as-built updates of the detail engineering design, including demolition. No
3D model report required
Reference databases (CATA, PROP) required to show the design shall remain in the AVEVA Plant 3D
model.
5.2 3D Model Report

The 3D model report shall be a short text document explaining the 3D model delivered in the study or the
project design databases. The purpose of the report is to help future users of the study or the project
model, both Company and contractor users, understanding the different parts of the deliverable.
For studies and FEED-projects, the 3D model report shall ensure consistency between the delivered 3D
model and the official study report delivered to Company.
The 3D-model report shall contain the following information:

 Study or FEED-project name
 Study or FEED-project actual start date and actual end date
 Contractor name
 Contractor project manager
 Company project manager
 Contractor Aveva Plant administrator
 Contractor 3D CAD coordinator or lead 3D designer
 List of SITE and ZONE names containing the study design model
 Explanations of which SITEs-ZONEs contain separate options or cases (if relevant)
 List of SITE and ZONE names containing design which is not part of what is intended to be built in
the facility, like installation study sequences or voided parts of the study design
 Any naming convention deviating from the naming convention in this TR document
List of reference databases (CATA, PROP) required showing the design
5.3 Model updates requirements of the AVEVA Plant 3D model

The as-built model shall be updated to reflect all changes by contractor in the project.
Elements demolished in the facility shall be removed from the as-built model.
Elements in the existing facility modified by the project contractor shall be modified in the as-built model.
Temporary elements shall not appear in the as-built model, except any “Temporary Steel” elements which
remain physically present in the facility.
As-Built branches shall be connected to the correct as-built equipment nozzle.
All elements shall be data consistent according to AVEVA Plant documentation, and all elements delivered
shall pass the AVEVA data consistency check.
Contractor shall ensure that PIPE, BRANCH and BRANCH members and NOZZLE elements are data
consistent and form an interconnecting piping network according to AVEVA Plant manuals.
Structural fitting-type and node elements shall have correctly set cross references. This also applies to
Structural pipe support elements.
Page 11 of 29
No elements with reference to a Cats&Specs element shall have an unset reference. All Cats&Specs
elements used shall be data consistent and without errors.
It shall be possible to add all elements created or modified by the project to the AVEVA Plant 3D window
without any error messages being displayed in the command line and delaying this process.
The resulting 3D CAD model shall be modelled using AVEVA Plant Design applications, like pipework,
equipment and structural applications.
Any project identifier attached to the element name shall be removed, and the element name shall be the
correct as-built name. All required UDAs shall be set.
Regardless of ZONE or SITE used during the project execution, the new sub-zone element (EQUI, PIPE,
STRU and similar) shall appear in the correct as-built ZONE and SITE in the as-built model.
5.4 Greenfield model requirements

For detail Greenfield projects (after DG3) the 3D model hierarchy shall be in accordance with the project
hierarchy given in chapter 7. In cases where the Greenfield project will benefit from using the as-built
naming requirements given in chapter 6 instead, this practice shall be agreed upon with Company at
LCI 0.
Studies and future design shall be modelled in separate study databases.
For the detail and fabrication phase (after DG3), SITEs and ZONEs shall be set up with an as-built 3D
model hierarchy. Databases shall be set up like an as-built model, but shall have [PRO] Content-Type
database description. SITE and ZONE naming in the project model shall be according to as-built hierarchy
if only one contractor is modeling the facility.
If more than one contractor is modeling, the additional contractors shall identify its design by adding a
Company suffix or a project identifier to the SITE and ZONE name. Studies and future design shall be
modelled in separate databases, following a study naming convention. Temporary design shall be
modeled in [TMP] Content-Type database.
Deviations from the as-built hierarchy shall be agreed with Company before implementation.
5.5 Import design in AVEVA Plant from other 3D applications

Imported design representing normally reference-driven elements such as nozzles, structural sections and
piping components, shall be driven by AVEVA Catalogue and Specification elements.
6 Requirements to As Built hierarchy
6.1 3D model content

The content of the 3D modell shall be according to TR2381
6.2 As Built hierarchy

The as-built design model shall be organised into an area-discipline based SITE-ZONE hierarchy, where
the SITE shall contain all elements for a discipline in a given facility area.
Page 12 of 29
6.3 SITE and ZONE name syntax

SITE name in the as-built model shall be: <area code>-<discipline long code>
The description attribute of the SITE shall be: <discipline long code>-<area>-<area description>
Example SITE name: C04-PIPE

Example SITE description: “PIPE - C04 - Fire water area south”
The SITE contains ZONEs further subdividing the as-built design model for that area and discipline.
ZONE name in the as-built model shall be: <area code>-<discipline long code>-<Subset Code>
Example ZONE name: C04-MECH-EQUIPMENT

Example ZONE description: “MECH - Equipment”
The description attribute of the as-built ZONE element shall be as listed in the tables in chapter 6.4. SITE
and ZONE name shall not contain any blank characters, tabulator characters or “empty space”.
Both SITE and ZONE position and orientation shall be:

 Orientation: E 0 N 0 U 0 WRT World
 Position: Y is N WRT /* and Z is U WRT World
6.4 List of legal As Built ZONEs

In tables 3 to 8, {area} is the legal facility area for the facility.
6.4.1 General ZONEs

Elements in EQUIPMENT-ZONEs or similar shall be tagged elements, while untagged elements may be
placed in MISC-ZONE. The MISC-ZONE shall not be used if a more relevant ZONE can be used.
The following ZONEs shall be used in all 3D models:
Table 3: General ZONEs

Discipline ZONE name ZONE description
{area}-PIPE-## PIPE - System ## - system
Piping description
HVAC {area}-HVAC-DUCT HVAC - Ducting
HVAC {area}-HVAC-EQUIPMENT HVAC - Equipment
HVAC {area}-HVAC-MISC HVAC - Miscellaneous
Mechanical {area}-MECH-ACCESSROUTE MECH - Access Route
Mechanical {area}-MECH-DRAINBOXES MECH - Drain Box
Mechanical {area}-MECH-EQUIPMENT MECH - Equipment
Mechanical {area}-MECH-INDECKTANK MECH - In-Deck Tank
Mechanical {area}-MECH-MATERIALHANDLING MECH - Material Handling
Mechanical {area}-MECH-UTILITYSTATION MECH - Utility Station
Architectural {area}-ARCH-BLASTWALL ARCH - Blast Wall
Architectural {area}-ARCH-CEILING ARCH - Ceiling
Page 13 of 29
Architectural {area}-ARCH-DOOR ARCH - Door

Architectural {area}-ARCH-FLOOR ARCH - Floor
Architectural {area}-ARCH-FURNITURE ARCH - Furniture
Architectural {area}-ARCH-INSULATION ARCH - Insulation
Architectural {area}-ARCH-MISC ARCH - Miscellaneous
Architectural {area}-ARCH-STAIR ARCH - Stair
Architectural {area}-ARCH-ROOMS ARCH - Rooms
Architectural {area}-ARCH-WALL ARCH - Wall
Architectural {area}-ARCH-WINDOWS ARCH - Windows
Pipe Support {area}-PSUP-SUPPORT PSUP - Pipe Support
Electrical {area}-ELEC-EQUIPMENT ELEC - Equipment
Electrical {area}-ELEC-FIELDTRAY ELEC - Field Tray
Electrical {area}-ELEC-HEATTRACE ELEC - Heat Trace
Electrical {area}-ELEC-JUNCTIONBOX ELEC - Junction Box
Electrical {area}-ELEC-LIGHTING ELEC - Lightning
Electrical {area}-ELEC-MISC ELEC - Miscellaneous
Electrical {area}-ELEC-PUSHBUTTON ELEC - Push Botton
Electrical {area}-ELEC-SOCKETOUTLET ELEC - Socket Outlet
Electrical {area}-ELEC-SWITCH ELEC - Switches
{area}-ELEC-HVLADDER ELEC - High Voltage
Electrical Ladder(>1000V)
{area}-ELEC-LVLADDER ELEC - Low Voltage Ladder
Electrical (<1000V)
Electrical {area}-ELEC-HVCABLECHANNEL ELEC - Cable Channel High Voltage
Electrical {area}-ELEC-LVCABLECHANNEL ELEC - Cable Channel Low Voltage
Instrumentation {area}-INST-EQUIPMENT INST - Equipment
Instrumentation {area}-INST-FIELDTRAY INST - Field Tray
Instrumentation {area}-INST-JUNCTIONBOX INST - Junction Box
Instrumentation {area}-INST-LADDER INST - Cable Ladder Instrument
Instrumentation {area}-INST-MISC INST - Miscellaneous
Telecom {area}-TELE-EQUIPMENT TELE - Equipment
Telecom {area}-TELE-JUNCTIONBOX TELE - Junction Box
Telecom {area}-TELE-MISC TELE - Miscellaneous
Telecom {area}-TELE-PA TELE - Public Address & Alarm
Safety {area}-SAFE-DETECTOR SAFE - Fire & Gas Detectors
Safety {area}-SAFE-EQUIPMENT SAFE - Equipment
Safety {area}-SAFE-ESCAPEROUTE SAFE - Escape Routes
Safety {area}-SAFE-FIELDTRAY SAFE - Fire & Gas Field Tray
Safety {area}-SAFE-JUNCTIONBOX SAFE - Fire & Gas Junction Box
Safety {area}-SAFE-MISC SAFE - Miscellaneous
Example: Telecom SITE for area C07:
C07-TELE with description attribute: TELE - C07 - Cooling & water injection area
Example ZONE names under SITE C07-TELE:
C07-TELE-EQUIPMENT with description attribute: TELE – Tagged Equipment

C07-TELE-JUNCTIONBOX with description attribute: TELE - Junction Box
C07-TELE-MISC with description attribute: TELE - Miscellaneous
Page 14 of 29
C07-TELE-PA with description attribute: TELE – Public Address & Alarm
Example: Piping SITE for area M33:
M33-PIPE with description attribute: PIPE - M33 - Process Module Weather Deck
Example ZONE name for piping system 21 in area M33:
M33-PIPE-21 with description attribute: PIPE - System 21 - Crude Handling
6.4.2 Structural Topside

ZONEs to be used only in the topside areas in 3D models for offshore platforms:
Table 4: Structural Topside ZONEs

Structural {area}-STRU-ACCESS STRU - Access Stair and Ladders
Structural {area}-STRU-ACCESSPLATFORM STRU - Access Platform
Structural {area}-STRU-BRIDGE STRU - Bridge between Platforms
Structural {area}-STRU-BULKHEAD STRU - Bulkhead
Structural {area}-STRU-BUMPERGUIDE STRU - Bumper and Guide
Structural {area}-STRU-CRANEPEDESTAL STRU - Crane Pedestal
Structural {area}-STRU-DECKGIRDER STRU - Deck Girder
Structural {area}-STRU-DECKSTRUCTURE STRU - Deck Structure
Structural {area}-STRU-DROPPEDOBJECTPROTECTION STRU - Dropped Object Protection
Structural {area}-STRU-EQUIPMENTSUPPORT STRU - Equipment Support
Structural {area}-STRU-ESCAPETUNNEL STRU - Escape Tunnel
Structural {area}-STRU-FLARETOWER STRU - Flare Tower
Structural {area}-STRU-GRIDSYSTEM STRU - Gridsystem
Structural {area}-STRU-JACKET STRU - Jacket Structure
Structural {area}-STRU-LAYDOWNAREA STRU - Laydown Area
Structural {area}-STRU-LIFTSHAFT STRU - Lift Shaft
Structural {area}-STRU-MAJORSUPPORTSTRUCTURE STRU - Major Support Structure
Structural {area}-STRU-MECHHANDLING STRU - Mechanical Handling
Structural {area}-STRU-MISC STRU - Miscellaneous
Structural {area}-STRU-NODE STRU - Node (built up)
Structural {area}-STRU-PIPERACK STRU - Pipe Rack
Structural {area}-STRU-RAILING STRU - Handrail Safety barrier, flexi barrier
Structural {area}-STRU-STAIRTOWER STRU - Stair Tower
Structural {area}-STRU-TRUSS STRU - Truss
Structural {area}-STRU-WALKWAY STRU - Walkway
Structural {area}-STRU-WALL STRU - Wall
6.4.3 Structural Hull

ZONEs to be used only in the hull areas in 3D models for production ships and semi-submersibles:
Table 5: Structural Hull ZONEs

Page 15 of 29
Structural {area}-STRU-ACCESS STRU - Access Stair and Ladders

Structural {area}-STRU-ACCESSPLATFORM STRU - Access Platform
Structural {area}-STRU-ANODES STRU - Anodes
Structural {area}-STRU-BULKHEAD STRU - Bulkhead
Structural {area}-STRU-BUMPER STRU - Bumpers
Structural {area}-STRU-CAISSON STRU - Caisson
Structural {area}-STRU-CHAINTUBE STRU - Chain tube and locker
Structural {area}-STRU-DECKGIRDER STRU - Deck Girder
Structural {area}-STRU-DECKSTRUCTURE STRU - Deck Structure
Structural {area}-STRU-EQUIPMENTSUPPORT STRU - Equipment Support
Structural {area}-STRU-GRIDSYSTEM STRU - Gridsystem
Structural {area}-STRU-GUIDETUBE STRU - Guide tube and wire
Structural {area}-STRU-LIFTSHAFT STRU - Lift Shaft
Structural {area}-STRU-MECHHANDLING STRU - Mechanical Handling
Structural {area}-STRU-MISC STRU - Miscellaneous
Structural {area}-STRU-MOORINGEQUIPMENT STRU - Mooring equipment
Structural {area}-STRU-NODE STRU - Node (built up)
Structural {area}-STRU-PIPERACK STRU - Pipe Rack
Structural {area}-STRU-RISERPROTECTION STRU - Riser Protection & Support
Structural {area}-STRU-SHELL STRU - Shell
Structural {area}-STRU-SPONSON STRU - Sponsons
Structural {area}-STRU-STAIRTOWER STRU - Stair Tower
Structural {area}-STRU-TOWINGEQUIPMENT STRU - Towing equipment
Structural {area}-STRU-WEBFRAMING STRU - Web framing
6.4.4 Structural Subsea

ZONEs to be used only in 3D models for subsea, additional to legal ZONEs for structural topside (6.4.2):
Table 6: Structural Subsea ZONEs

Structural {area}-STRU-ROVPANEL STRU – Rov Panel
Structural {area}-STRU-SUCTIONANCHOR STRU – Suction Anchor
Structural {area}-STRU-TRAWLPROTECTION STRU – Trawl protection
6.4.5 Onshore Process plants – Structure and Civil

ZONEs to be used only in 3D models for onshore process plants:
Table 7: Structural ZONEs for Onshore

Structural {area}-STRU-ACCESS STRU - Access
Structural {area}-STRU-EQUIPMENTSUPPORT_seqNo STRU - EquipmentSupport
Structural {area}-STRU-MAINACCESSPLATFORM_seqNo STRU - Access Structure
{area}-STRU- STRU - Major Support
Structural MAJORSUPPORTSTRUCTURE_seqNo Structure
STRU - Mechanical
Structural {area}-STRU-MECHHANDLING Handeling
Structural {area}-STRU-PIPERACK_seqNo STRU - PipeRack
Structural {area}-STRU-STAIRTOWER_seqNo STRU - Stair Tower
Page 16 of 29
seqNo is the sequence number of the structural unit in the onshore plant. The sequence number shall be
set on all structural ZONEs containing elements of the same structural unit.
ZONEs to be used only in 3D models for onshore process plants:
Table 8: Civil ZONEs for Onshore

Civil {area}-CIVI-BASEPLATE CIVI - Base plate
Civil {area}-CIVI-BUILDING CIVI - Building
Civil {area}-CIVI-CULVERT CIVI - Culvert & Cable duct
Civil {area}-CIVI-EQUIPMENT CIVI - Equipment
Civil {area}-CIVI-FOUNDATION CIVI - Foundation
Civil {area}-CIVI-GULLY CIVI - Gully
Civil {area}-CIVI-MANHOLE CIVI - Manhole
Civil {area}-CIVI-FENCESGATES CIVI - Fences and gates
Civil {area}-CIVI-MISC CIVI - Miscellaneous
Civil {area}-CIVI-PIPE CIVI - Underground Piping
Civil {area}-CIVI-ROAD CIVI - Roads
Civil {area}-CIVI-TERRAIN CIVI - Terrain
Civil {area}-CIVI-TRENCH CIVI - Trenches
Civil {area}-CIVI-TUNNELS CIVI - Tunnels
6.4.6 GBS Civil

ZONE to be used only in 3D models for offshore platforms with Gravity Base Structures:
Table 9: GBS ZONE

Civil {area}-CIVI-GBS CIVI - Gravity Base Structure
6.5 As Built tagged elements

All tagged elements in the facility shall be represented with AVEVA Plant elements directly below the
ZONE level, like PIPE, EQUI and STRU elements or similar, with exception of in-line piping tags like
valves and instruments, in-line HVAC Duct tags and Architect wall tags like door and window fittings.
6.5.1 Piping line tag number

Piping line tag number shall be represented with AVEVA Plant PIPE elements modelled with the AVEVA
Plant Design Pipework Application. If the piping line tag number passes through more than one facility
area, one PIPE element shall be used for each area, and the PIPE element shall be placed in the correct
piping SITE and ZONE for that area.
AVEVA Plant pipe name <line tag number>_<area>
PIPE name requirements for specific Company facilities (normative examples):
Table 10: AVEVA Plant pipe name requirements by facility

Facility Piping line number from ENS AVEVA Plant pipe name
Aasta Hansteen 50L0501-0400WS-AC200 50L0501_P240
Page 17 of 29
Brage 0050-ZPT-15-0070-HE1-4-B 15-0070_M10

Bressay 50L0501-0400WS-AC200 50L0501_P100
Draupner 1.5-PL-21-1001-BC12-1 PL-21-1001_M11
Gina Krog 50L0501-0400WS-AC200 50L0501_P100
Grane 0150-ZMH-11-5382-LA1-00-A 11-5382_M10
Gudrun 8"-DM-56-804-AC02 DM-56-804_C06
Gullfaks A, B and C 12"-PL-21022X-BC21A-1 PL-21022X_M14
Heidrun 21L321-6”-PL-BC12 21L321_M33
Heimdal 0100-ZNC-257-5407-GE2-57 257-5407_M20
Huldra, Veslefrikk A and B 12”-PL-21022-BC21A PL-21022_DK04
Kalstø 4"-VF-43-2001-BS20A-0 VF-43-2001_F31
Kalundborg 6”-P-486020-150A03-IH P-486020_BLK0402
Kristin 50L0501-0400WS-AR71 50L0501_C2
Kvitebjørn 50L0025-0400WS-AT750 50L0025_P22
Kårstø 6”-PL-24-3091-AC10A-6 PL-24-3091_CA411
Mariner 50L0501-0400WS-AC200 50L0501_P100
Melkøya (Snøhvit) 6"-PL-24-3091-AC10A-6 PL-24-3091_L1
Mongstad 6”-CL-25-0218-A1AU-H CL-25-0218_A16
Njord 0200-ZML-11-0040-CA2-00-A 11-0040_D40
Norne 21L4321-6”-PL-BC12 21L4321_P12
Oseberg 0150-PT-20-1234-CD1-00 20-1234_M20
Peregrino 12”-WI-44936-FN-DI WI-44936-FN_P23
Sleipner 8"-DM-56-804-AC02 DM-56-804_C06
Snorre A 12”-PT-16D804-AD205 PT-16D804_P16
Snorre B 6"-PL-21B004-AC11S-1 21B004_P33
Statfjord A 08"-WF-30245-AT751 WF-30245_M9
Statfjord B and C 12"-PL-21022-MA20 PL-21022_CD01
Tjeldbergodden 21L176-10-MV-AC28A-1 21L176_B20
Troll A and Kollsnes 3-WF-71-0533-TAS71A WF-71-0533_C11
Troll B and C 0150-ZPV-23-2009-KA1-68-A 23-2009_M20
Valemon 13L12070-0400PW-FD201/04040Y 13L12070_P1
Visund 0150-ZPT-20-1234-CD1-00-A ZPT-20-1234_P30
Åsgard A and B 08.00-WC-40L1206-AC200-001 40L1206_M40
The pipe name for each piping line number is marked in bold text in Table 10.
Duplicate PIPE element naming
In very few cases in a facility, a AVEVA Plant PIPE will leave and re-enter an area, requiring two or more
PIPE elements in that area. In these cases, the second and any subsequent PIPEs shall be named as:
<line tag number>_<area>-<suffix B to Z>
Example AVEVA Plant line tag number:
First pipe in area P22: 50L0025_P22

Second pipe in area P22: 50L0025_P22-B
Page 18 of 29
6.5.2 In-line piping tags and special items

In-line piping tags, including instrument valves, shall have name identical to the tag name. In-line piping
tags shall be represented with sub-branch level elements like VALV or INST or similar.
Special items where the special item number is used more than once in the model shall be named as:
<special item>/<suffix>
6.5.3 Equipment and equipment nozzles

Equipment tags for all disciplines shall have name identical to the tag name and shall be represented by
EQUI elements.
The EQUI element shall contain at least one visible primitive element, at minimum a BOX element with
dimensions 100mm by 100 mm by 100 mm. The EQUI element shall be located at the correct coordinates
in the model using the tolerances listed in the governing documents in chapter 1.3. Where the exact
location is not known, approximate position shall be used.
Equipment nozzles shall be named as: <equipment name>/<suffix N1 to N#>
where suffix is the P&ID nozzle number, like “N1”, “N2” and similar, as defined by the ENS document.
Example equipment tag: 23HJ501

Example nozzle name: 23HJ501/N1
6.5.4 Pipe Supports

Pipe Supports in the 3D model shall have the same name as the Pipe Support name required by the ENS
document.
The Pipe Support point in the PIPE element shall be represented by an ATTA element with name as:
<Pipe Support name>/<Suffix A to Z>
Example Pipe Support names:
PS-M16-0455/A (where M16 is the facility area)

PS-M16-0455/B (second connection point to a different Pipe)
A33-997-590/A (where A33 is the facility area)
The Pipe Support STRU or REST representing the Pipe Support structural elements, shall be named as:
<Pipe Support name>
In the examples used above, the Pipe Support structure shall be named:
PS-M16-0455
A33-997-590
Page 19 of 29
6.5.5 Structural tags

Structural tags like monorails and lifting lugs shall be modelled with one STRU for each tag. The STRU
name shall be identical to the tag name.
6.5.6 Skid and Package tags

All tags in a skid or package shall be represented by AVEVA Plant elements directly under ZONE, and
placed in the correct discipline ZONE. For pipe inline elements representing a tag, these shall be located
below a sub PIPE element.
Structural support elements shall be placed in the correct Structural ZONE, with a STRU name as:
<package tag name>_SUPPORT
Skids according to section “As-Built skid/package modelling” can comply with Zone tag principals defined
in the section.
6.5.7 HVAC duct tag number

HVAC duct tag number shall be represented with AVEVA Plant HVAC duct elements modelled with the
AVEVA Plant HVAC Designer application. If the duct tag number passes through more than one facility
area, one duct element shall be used for each area, and the duct element shall be placed in the correct
HVAC SITE and ZONE for that area.
AVEVA Plant duct tag number shall be: <duct tag number>_<area>
Where <duct tag number> is the duct tag number from ENS.
Example HVAC duct tag number:
HVAC duct line number from ENS: 77D0026-1600x1200-S01-A12

AVEVA Plant duct tag number: 77D0026_P22 (first duct tag number in Area P22)
Duplicate HVAC element naming
In very few cases in a facility, a AVEVA Plant HVAC duct will leave and re-enter an area, requiring two or
more duct elements in that area. In these cases, the second and any subsequent ducts shall be named as:
77D0026_P22-B (second duct tag number in area P22)
6.6 Special characters in AVEVA Plant names

Elements in AVEVA Plant model representing tags shall have AVEVA Plant name identical to the tag
name.
In some ENS documents, tag names are required to contain one or more special characters, like the blank
character (space). In such cases, each special character in the AVEVA Plant model element name shall
be replaced by an underscore character. In the case of other special characters, contractor shall clarify
with Company.
Page 20 of 29
6.7 UDAs to be completed at As Built

To complete the User Defined Attributes (UDA) on the as-built elements, contractors main MDB shall
contain the database ADMIN/DICT-OPE, which contain the definitions of the required UDAs.
No later than during as-built, contractor shall set the following UDAs on all sub-zone elements, i.e. EQUI,
PIPE, STRU and REST elements created or modified by the project:
For PIPE elements only:
 :OpeLineNo (Piping/HVAC line number)

 :OpePidNo (Process and Instrumentation Diagram drawing number)
In addition, for STRU, Pipe Supports and Cable Ladders/Trays
 :OpeDrwgNo (Operator Drawing Number)
The value of the :OpeDrwgNo UDA shall be identical to the corresponding drawing number in the facility
document register.
6.8 As Built skid/package modelling

Skid/packages that comply with section “3D CAD model – Skid/Package” in the TR2381 can be modelled
in the as-built database as a multi discipline zone. The zone shall contain all design located on the
skid/package. The skid/package shall be modelled in the discipline database. For all other skid/packages
the content shall be modelled in their respectivly discipline sites and zones.
AVEVA Plant zone name shall be: <Skid tag number>
Model requirements:
 All skid/packagesub tags shall be modelled on Sub-Zone level with correct tag naming according to
project ENS.
 All valves and inline items to be modelled using AVEVA Piping Catalogue and Specification
elements.
 Pipe supports to be modelled as REST/STRU elements, structural design to be modelled as a
STRU element and piping as PIPE element each containing the discipline design. Cats&Spec
elements shall be used.
 Skid/package meta data such as datum, dry and wet CoG etc, may be added below an EQUI with
the naming syntax: DATA/<Skid tag number>
 Nozzles to be modelled as NOZZ elements using AVEVA Piping Catalogue and Specification
elements, below a common “Nozzle EQUI” element with the naming syntax: NOZZLE/<Skid tag
number>
 The skid/package outline dimensions shall be represented as an EQUI containing the overall
skid/package soft volume defined with OBST 2 and Level 8-10. The EQUI shall be named
according to the syntax: SOFTVOLUME/<Skid tag number>
 All as-built or projects UDAs shall be sett according general UDA requirements
Page 21 of 29
Example of an AVEVA Plant skid/package model hierarchy:
Page 22 of 29
7 Requirements to project hierarchy
7.1 Task – based modelling

The 3D model scope of work of all Company projects shall be subdivided into specified parts. Depending
on the project and the project management, examples of the titles of such parts are:
 A work package
 A sub-project in the facility maintenance and modification project
 Alternatives, options or cases in study projects
For reasons of simplicity, the concept “task” will be used in this chapter to describe these parts of the 3D
model scope of work.
7.2 Project SITE and ZONE name syntax

All project design in the 3D model shall be linked to a task. All design elements for a task shall be placed
in a SITE or SITEs which only contain elements related to the specified task. The SITE name shall contain
the combination of project identifier and Company defined task, or project identifier and internal contractor
code.
SITE name in the project model shall be:
<area code>-<discipline long code>_<Project Identifier- task*>
Example SITE name: C04-PIPE_XYZ-190265
Where XYZ is the Project Identifier and 190265 is the task.
*Task can be an internal contractor code or company defined task.
ZONE name in the project model shall be:
<area code>-<discipline long code>-<Subset Code>_<Project Identifier- Task>
Example ZONE name: C04-MECH-EQUIPMENT_XYZ-190265
Both SITE and ZONE Position and Orientation shall be:

 Orientation: E 0 N 0 U 0 WRT World
 Position: Y is N WRT /* and Z is U WRT World
7.3 Legal Project Zones

The list of legal project ZONEs is identical to the list of legal as-built ZONEs.
If contractor requires additional ZONE names, or a different division of the subset codes for the project,
contractor may use additional ZONE names. In such cases the ZONE hierarchy shall be used consistently
by contractor during the project execution.
Demolition shall be modelled in separate project ZONEs.

Page 23 of 29
Regardless of the ZONE hierarchy used during the project, contractor shall complete as-built
documentation of the project design using only the legal as-built ZONEs.
7.4 Tag names for elements below ZONE level

The name of elements on the level below ZONE level (i.e. PIPE, EQUI, STRU and similar) shall contain
the same Project Identifier and task if that element represents modifications of tags already existing in the
as-built model.
For new tags in the facility, the project identifier and task, or project identifier is not required in the tag
name. The naming convention for new tags is identical to the naming convention for as-built tags.
7.4.1 Tag names for modified tags

Tag name for modified tags shall be:
<tag name from ENS>_<Project Identifier-Task>
Example tag name: Existing Junction Box modified by the XYZ Project:
83EL102-501-B01_XYZ-190265
7.4.2 Pipe Name for modified Piping Line numbers

AVEVA Plant PIPE elements in projects shall be named like as-built pipes.
In the case where a project intends is to modify an existing as-built pipe, the modified pipe in the project
model shall be named with project identifier and task, or project identifier as a suffix.
< AVEVA Plant pipe name >_<area>_<Project Identifier- Task>
Example as-built pipe in area P22: 50L0025_P22
The same pipe modified by project XYZ: 50L0025_P22_XYZ-190265
7.5 UDAs to be completed in the project

To complete the User Defined Attributes (UDA), contractors main MDB shall contain the database
ADMIN/DICT-OPE, which contain the definitions of the required UDAs.
Company UDAs :OpeProjectId,:OpeProject and :OpeTask shall be set on all sub-zone elements, i.e.
elements like EQUI, PIPE, REST, STRU that represents a Tag. The UDAs shall be set when the sub-
zone element is created.
 :OpeProjectId (Project identifier)

 :OpeProject (STID Project Code)
 :OpeTask (Company defined task)
Page 24 of 29
7.6 Use of project UDETs

UDETs (User defined Element Types) can be used in the project however these shall be defined by
Company. UDETs shall be created and maintained by Company in the common UDET database
ADMIN/DICT-OPE-UDET. New UDETs can be created upon request from Contractor. UDETS shall only
replace sub-zone elements such as PIPE/EQUI/STRU.
When removing the UDET database from the MDB, non-logical situations as “Zone below Zone” or “Pipe
below Pipe” shall not occur.
7.7 Datestamp
Datestamp shall not be used in the AVEVA Plant model.
7.8 Model Encryption

Encryption shall not be used in the 3D model.
7.9 Data Access Control

DAC rules restricting the creation of SITEs and ZONEs in as-built databases can be defined by Company
when required. Any additional DAC rules shall be created by Contractor and implemented from the HUB
level by Company. Ensuring that these additional DAC rules are error free is Contractor responsibility.
8 Requirements to catalogue and specifications
8.1 General
All catalogue and specifications components shall be incorporated and managed by the contractor.
Use of Company master catalogues can be agreed with Company.
Catalogues and specifications objects shall not be removed after implementation even if not referenced by
the design model.
Catalogue and specification elements shall be named in a way that ensures that they not conflict with
other catalogue and specification elements, including those from other contractors.
8.2 Naming conventions piping specs
8.2.1 Spec World Elements Name Syntax

SPWL name syntax shall contain discipline long code, facility code, and an abbreviated contractor name:
<discipline long code>-<facility code>-<content>_<abbreviated contractor name>
Example SPWL: PIPE-ABC-SPEC_CO
8.2.2 Specification name syntax

SPEC element name shall contain spec name and abbreviated contractor name.
<SPEC name>_<abbreviated contractor name>
Page 25 of 29
Example SPEC: AC200_CO
8.2.3 Selector name syntax

SELE name shall contain Spec name, abbreviated contractor name and Gtype/descriptive text. SELE
might be left unnamed. Other disciplines shall use to the same syntax as far as possible. SELE shall be
named as:
<SPEC name>_<abbreviated contractor name>/<GTYPE>
Example first level SELE: AC200_CO/ELBO
9 Requirements to level and obstruction 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 0-10 and by this be visible regardless of level display setting.
Design elements shall use the following levels in the model:
Solid materials shall use levels 1-6

Insulation shall use level 7-10
Obstruction volumes shall use levels 8-10
9.2 Obstruction
The obstruction value for design elements shall be set to allow clash detection in the 3D model:
 OBST 2 for solid material clash representation
 OBST 1 for soft material
 OBST 0 for non-obstruction volume
A soft material is something which is not solid, but that needs to be kept clear for access purposes, such
as an operating space around the control wheel of a valve, lifting equipment volumes during lifting
operations, or maintenance access volumes for equipment. Non-obstruction volumes are typically safety
fire areas, fire water nozzle spray volumes or crane radius circles.
9.3 Required use of level and obstruction
9.3.1 Escape routes

Escape routes in the model shall be represented by a STRU or EQUI element with at least two equipment
primitive boxes, with:
 A footprint box with height 100 mm above deck or floor, with OBST 1 and level 1-6 (visible)
 A headroom box above the footprint box with the escape route actual height, with OBST 1 and
level 8-10 (hidden)
The footprint box and headroom box shall have the same width.
Page 26 of 29
9.3.2 Access routes

Escape routes in the model shall be represented by a STRU or EQUI element with at least two equipment
primitive boxes, with:
 A footprint box with height 100 mm above deck or floor, with OBST 1 and level 1-6 (visible)
 A headroom box above the footprint box with the escape route actual height, with OBST 1 and
level 8-10 (hidden)
The footprint box and headroom box shall have the same width.
9.3.3 Maintenance volumes

Elements representing maintenance volumes shall have OBST 1 and Level 8-10. These volumes reserve
the volume where equipment internals and valve internals will be positioned during maintenance.
9.3.4 Fire water nozzle coverage elements

If cone and pyramid graphical elements are placed in the model to show the volume and area that a fire
water nozzle covers, the AVEVA Plant equipment primitives used to display such nozzle coverage shall
have OBST 0 and Level 8-10 in order to be normally hidden in the model.
9.3.5 Crane radius

Design elements used to represent the radius of movement of a crane in the facility shall use level 8-10
and OBST 0. The elements representing the physical crane itself shall use level 1-6 and OBST 2.
Elements representing the same crane in various positions representing the movement of the crane during
installation procedures shall not be placed in the same database as the crane, but shall be placed in a
separate [TMP]-database for the project.
9.4 Visibility of non – essential design

Project design data representing installation studies, the movement of equipment for maintenance
handling studies, various crane positions, locally measured design or other temporary design, shall be
placed in [TMP] databases. The reason for this requirement is to prevent such design from appearing in
the design model of other contractor designers, and prevent clash detection with irrelevant items.
10 Additional information
10.1 Definitions and abbreviations

AVEVA Plant
AVEVA Plant is a common name for the Aveva 3D applications PDMS and Everything3D.
Everything3D also uses the abbreviation E3D.
AVEVA Global
Software system delivered by AVEVA used to distribute and update 3D models between locations like
engineering offices and fabrication yards.
As Built
Last revision of an LCI item updated to reflect the true status of completed work with relation to specified
tolerances.
As Built (theoretic) vs. As-Is

Page 27 of 29
The 3D model reflects a theoretic as built as the Company’s dimensional tolerances for the contractors
as built modelling typical result in deviations from the real facility object locations.
Laser scan data as a supplement to the 3D model gives the as-is i.e. the total picture of the true as built.
Even when the 3D model is defined to be first-class as built, the laser scan data supplement representing
the as-is becomes essential as the 3D model itself does not represent all the physical facility objects in
detail.
Company
Statoil ASA.
Contractor
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.
Facility
Offshore production platforms, Semi-submersibles, Floating Production Storage and Offloading ships
(FPSO), Subsea installations and Onshore process plants owned by Company.
Master Project
A contractor or Company 3D model which functions as a library for common AVEVA Plant model
information to be used in other 3D models. The master project typically contains catalogue information,
drawing templates and UDA definitions.
AVEVA Plant Global Hub

The Hub is the location where the overall 3D model administration takes place.
AVEVA Plant Global Satellite

A Satellite is an office location outside the Hub where the 3D model is to be distributed on a scheduled
(daily) basis. Usually a contractor Company office, but may be a Company Site office.
Page 28 of 29
Abbreviation:
CAD Computer Aided Design
ENS Engineering numbering system
LCI Life Cycle Information
MDB Multiple Database, collection of AVEVA Plant databases in the 3D model
MPX Company Master Project
PDMS™ AVEVA Plant Design Management System
E3D™ AVEVA Everything3D
UDA User Defined Attribute in AVEVA Plant
10.2 Changes from previous version
10.2.1 Changes from version 3:

 4.7 Content of Maintenance and Modifications databases
 6.8 Requirements for skid/package added
 7.5 Use of and definitions of Company UDAs
 7.6 & 7.7 Use of Data Access Control and use of Datestamp
 Clarification
 Document title changed
10.3 References
TR3110 Life Cycle Information (LCI), Technical Requirements and Standards
TR2381 LCI requirements
TR0052 Statoil engineering numbering system (ENS)
Page 29 of 29

TR2231 AVEVA Plant CAD Model Requirements Ver4

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

TR2231 AVEVA Plant CAD Model Requirements Ver4

Caricato da

Copyright:

Formati disponibili

Governing document Classification: Internal

AVEVA Plant CAD model requirements

Operation and maintenance (OM)

Owner: Chif Eng Ops TPD TEX FOT

Validity area: Corporate technical requirements/On- and offshore

1 Objective, target group and provision ............................................................................................................... 4

9.2 Obstruction ............................................................................................................................................... 26

1 Objective, target group and provision

1.2 Target group

2.1 AVEVA Plant and Global version

2.2 3D model area coding

2.3 Contractor work procedure

2.4 Project Identifier

The project identifier shall be used on:

3.1 Discipline codes

Table 1: Discipline codes in AVEVA Plant

The discipline long code shall be used in:

The discipline short code shall be used in:

3.2 Teams and databases

3.3 User and MDB administration

3.4 Regular expunge of users

3.6 Catalogues and specifications

3.7 Language characters

4 Requirements to database schedule

4.1 As-built databases

As-built databases shall have database numbers lower than 3000.

4.2 Project databases

Project databases shall have database number lower than 3000.

4.3 Master project databases

4.4 Team naming and use

As-built database team name: ASB+DES+<discipline short code>

Project database team name: DES+<discipline short code>

Example team names:

ASBDESPM - as-built team for PIPE-MECH

4.5 Database naming

<team>/<database type>-<discipline short code>-<area>

Project design databases shall be named:

<team>/<database type>-<discipline short code>-<area>-<Project Identifier>-<contractor code>

4.6 Content – Type in database description

Content-Type governs allocation and MDB-content requirements.

Table 2: Database Content-Type

4.7 Content of Maintenance and Modifications databases

4.8 Copy from as-built databases

4.9 Database description

For as-built design databases, the database description shall be:

 discipline: Is the discipline long code (“all disciplines” may be used)

For project design databases, database description shall be:

 procode: the Project Identifier

4.10 MDB required content

The main MDB shall as a minimum contain:

5 Requirements to project deliverables

5.1 Required project deliverables

Feasibility study or Concept study:

Detail Engineering and fabrication project:

5.2 3D Model Report

The 3D-model report shall contain the following information:

5.3 Model updates requirements of the AVEVA Plant 3D model

As-Built branches shall be connected to the correct as-built equipment nozzle.

5.4 Greenfield model requirements

5.5 Import design in AVEVA Plant from other 3D applications

6 Requirements to As Built hierarchy

6.1 3D model content

6.2 As Built hierarchy

6.3 SITE and ZONE name syntax