RIPRA VÁŠ PDMS PARTNER


TR2231 - PDMS 3D CAD model requirements

14.11.2012 16:59

PDMS 3D CAD model requirements

  1. Objective, target group and provision
    1. Objective
    2. Target group
    3. Provision
  2. General Requirements
    1. PDMS version and Scope
    2. Contractor in-house work procedure
    3. Discipline Codes
    4. Project Code
  3. Requirements for Roles and Responsibilities
    1. General
    2. Global
    3. Teams & Databases
    4. User and MDB administration
    5. Regular Expunge of Users
    6. Reconfiguration
    7. Catalogues & Specifications
  4. Requirements to Database schedule
    1. As-Built databases
    2. Project databases
    3. Master Project databases
    4. Team naming and use
    5. Database naming
    6. Content-Type in database description
    7. Database description
    8. MDB required content
  5. Requirements to Project deliverables
    1. Required project deliverables
    2. 3D-model Report
    3. Performing As-Built updates of the PDMS 3D model
  6. Requirements to As-Built hierarchy
    1. As-Built hierarchy
    2. SITE and ZONE Name Syntax
    3. List of legal As-Built Zones
    4. As-Built Tagged Elements
    5. Special characters in PDMS names
    6. UDAs to be completed at As-Built
  7. Requirements to Project hierarchy
    1. Task-Based modelling
    2. Project SITE and ZONE Name Syntax
    3. Examples of using Task-based Site naming convention
    4. Legal Project Zones
    5. Tag names for elements below Zone level
  8. Requirements to Catalogue and specifications
    1. General
    2. Naming conventions, Piping
  9. Requirements to User Defined Attributes (UDA)
    1. User Defined Attributes in PDMS Lexicon
  10. Requirements to Level and Obstructions volumes
    1. Level
    2. Obstruction
    3. Required use of level and obstruction
    4. Visibility of non-essential design
    5. User-Defined Equipment Types
  11. Additional information
    1. Definitions and abbreviations
    2. Changes from previous version
    3. References

1 Objective, target group and provision

1.1 Objective

The objective of this document is to describe the best practice procedures for handling Company PDMS Global 3D CAD models.

1.2 Target group

The Target group is everyone involved in creating or updating technical information for handover to Company.

1.3 Provision

This document is provided for in Life Cycle Information (LCI), Technical requirements and standards (TR3110).

2 General Requirements

2.1 PDMS version and Scope

Contractor shall use a PDMS and PDMS Global software version compatible with the Company PDMS Global 3D CAD model. The Company PDMS Global 3D CAD model shall be used for all engineering, modification and installation activities, as part of Life Cycle Information (LCI) for the Facility. Encryption shall not be used in the PDMS Global 3D CAD model.

2.2 Contractor in-house work procedure

Contractors that are conducting a scope of work for Company using a PDMS Global 3D CAD model shall have established an in-house work procedure. This procedure shall be ready to be presented to Company before start of modelling.

This procedure shall as a minimum contain information about and 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 PDMS 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 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 collision clash checking using PDMS Clasher or similar in-house applications
  • How the Contractors designers shall use the query-command “Q DESC OF DBREF” in PDMS Design on Site, Zone and sub-Zone elements to get information about which project the relevant database is detailing, and which Contractor is responsible for the design data in question

2.3 Discipline Codes The following Discipline Long Codes and Short Codes shall be used in the PDMS Project:

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

Table 1: Discipline Codes in PDMS

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

2.4 Project Code

Every ongoing or completed project issued by Company using a PDMS Global 3D CAD model shall have a unique project code to identify the design model elements created or modified by the project. This code is assigned by the Hub Administrator.

The project code shall be used on:

  • All Site and Zone element names in the project
  • All database names and descriptions containing the project 3D model
  • A Company User Defined Attribute on all Tag (sub-Zone) elements at As-Built of the project

Example Project Codes:

  • KFGC: Kollsnes Flash Gas & Condensate project
  • HNPG: Heimdal New Power Generator project
  • TRBGI: Troll B Gas Injection project
  • SLBK: Sleipner B Compression project

3 Requirements for Roles and Responsibilities

3.1 General

Contractor is responsible for managing the design for completing the Work as required. Contractor shall use a PDMS Global Satellite Location, with a daily on-line connection to the Company PDMS Global Hub. Company is the Hub Administrator, and is responsible for creating and allocating Teams, Databases, Extracts and Locations.

3.2 Global

Contractor shall ensure that their PDMS Global daemon runs continously in a working state at Contractors location, including at Contractors sub-satellite locations and other satellite locations involved in the scope of work.

Contractor shall set up and execute daily Scheduled Global Updates between Contractors location and any locations below Contractors location in the PDMS Global hierarchy.

Contractor shall receive and establish an MPX Company Master Project satelite for each of the locations Contractor is responsible for. The MPX project contains Catalogue and reference databases required to show the model. The MPX project satelite requires a PDMS Global deamon in a working state in addition to any required for the scope of work.

Contractor shall have separate design databases where project design shall be conducted. At predetermined intervals in the project, Contractor shall conduct an As-Built update of the project design, by receiving write access to the As-Built model (As-Built databases).

3.3 Teams & Databases

All teams and databases shall be created by the Hub Administrator. Database numbers are allocated by Hub Administrator. The database file number shall be the same as the database number.

3.4 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 Hub Administrator, detach databases from MDBs and remove any claims from databases required for service by Company or other Contractors.

3.5 Regular Expunge of Users

Once per day, Contractor shall Expunge all Users at his Locations and sub-contractor Locations in all Company PDMS Global 3D CAD models using the “Expunge”-command (Expunge All Users) to clear any PDMS “dead user”-claimlists.

If the Contractor CAD-servers does not perform automatic removal of operating system file locks immediately after such an Expunge and after each User Exit from PDMS, Contractor shall also set up and execute a scheduled file lock removal after the scheduled Expunge, to allow updates and service on the PDMS Global 3D CAD model files.

3.6 Reconfiguration

Contractor is responsible for conducting own required reconfiguration, including completing As-Built as required. Hub Administrator shall on request provide either permanent or temporary databases for the reconfiguration if required.

3.7 Catalogues & Specifications

Contractor is responsible for establishing and managing Catalogues and Specifications to complete the Work as required.

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 Global model. Disciplines shall be grouped into the following combinations for As-Built design databases:

  • 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. See chapter 2.3.

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 numbers lower than 3000.

4.3 Master Project databases

Foreign databases shall not be used in Company PDMS Global 3D CAD model, except from the Company Master Project named MPX. Any eventual databases from Contractor Master Projects or the Aveva Master Project (MAS) shall be copied into the Company PDMS Master Project MPX when needed, and distributed as Foreign databases by Including them into the relevant PDMS Global 3D CAD model.

Master Project databases shall have database number 3000 or greater, and the number shall be agreed with Hub Administrator.

4.4 Team naming and use

Company PDMS Global 3D CAD 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>/<PDMS Type>-<Discipline Short code>-<Area>

 

Area shall be a Facility legal area from the Engineering Numbering System or Code Manual 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.

The Discipline Short code shall be combined for multi-discipline databases, like PM for PIPE-MECH design databases.

Project design databases shall be named:

<Team>/<PDMS Type>-<Discipline Short code>-<Area>-<Project code>-<Contractor code>

Contractor code, usually the Contractor Global satelite Location code, is only necessary for databases in projects executed at more than one PDMS Global Location.

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 PDMS Administrators about how the database is to be used in the PDMS 3D CAD model, and in the creation and maintenance of MDBs.

Content-type governs Allocation and MDB-content requirements.

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 ongoing Detail Engineering project or a FEED-project. Distributed to all Contractors. Shall be current in the main MDB for visibility and clash detection purposes.
[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 Feasibillity 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 avaiable for clash detection.
[EXT] Extract database. Usually not distributed.
[TMP] Temporary. Info only useful to a single Contractor, like testingdesign, 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 avaiable for clash detection. Reference to chapter 10.4

Table 2: Database Content-type

4.7 Database description

Database description shall be used consistently across Company’s PDMS Global 3D CAD models. 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.

For As-Built design databases, the database description shall be like:

[Content-Type] As-Built, discipline in area, for owning company, date by Company admin

  • Content-Type: see chapter 4.6.
  • discipline is the Discipline Long Code (“all disciplines” may be used)
  • Area is the Area code (“all areas” may be used)
  • owning company shall always be Company.
  • date is the date the database was created, or description modified
  • Company admin is the Company shortname of the Company PDMS administrator responsible for creating or modifying the description.

For project design databases, database description shall be like:

[Content-Type] procode: project, discipline in area, for owning company, date by Company admin

  • procode is a short version of the project name
  • project is a descriptive project name to help find information about the project at a later date
  • owning company is the company using the data in the database during project execution

4.8 MDB required content

Each location shall have a main MDB, with the same name as the PDMS Global 3D CAD model code, i.e. the Heidrun PDMS Global 3D CAD model with PDMS Global 3D CAD model code HEI shall have a MDB named /HEI. The purpose of this requirement is to ensure that each Contractor has at least one MDB showing the entire design model including ongoing 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 has at least one MDB where they shall conduct clash detection to detect volume collisions with ongoing 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 PDMS design database containing the 3D Study model
  • 3D-model report, see 5.2

Pre-Engineering or FEED-Project:

  • One or more PDMS design databases containing the 3D Project model
  • 3D-model report, see chapter 5.2

Detail Engineering project:

  • Contractor shall perform As-Built updates of the Detail Engineering design, including demolition, se chapter 5.3
  • No 3D-model report required

Reference databases (CATA, PROP) required to show the design shall always remain in the PDMS Global 3D CAD 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 Project design databases. The purpose of the report is to help future users of the Study or Project model, both Company and Contractors users, understand 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 Global PDMS 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 to show the design

5.3 Performing As-Built updates of the PDMS 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 PDMS 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 PDMS manuals.

Structural Fitting-type and Node elements shall have correctly set cross references. This also applies to Structural PIPE Support Elements.

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 PDMS 3D Window without any warnings or error messages being displayed in the Command Line and delaying this process.

The resulting PDMS Global 3D CAD model shall be modelled using PDMS Design applications, like Pipework, Equipment and Structural applications.

Any Project code attached to the element name shall be removed, and the element name shall be the correct As-Built name.

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.

6 Requirements to As-Built hierarchy

6.1 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.

6.2 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.3. 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: Y is N WRT /* and Z is U WRT World
  • Position: E 0 N 0 U 0 WRT World

6.3 List of legal As-Built Zones

In Tables 3 to 8, {area} is the legal Facility Area for the Facility.

6.3.1 General Zones

Elements in EQUIPMENT-Zones or similar shall be Tagged elements, while untagged elements may be placed in MISC-Zones. The MISC-Zone shall not be used if a more relevant Zone can be used. T

he following Zones shall be used in all Company PDMS 3D models:

Discipline Zone Name Zone Description
Piping {area}-PIPE-## PIPE - System ## - system 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
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
Electrical {area}-ELEC-HVLADDER ELEC - High Voltage Ladder(>1000V)
Electrical {area}-ELEC-LVLADDER ELEC - Low Voltage Ladder (<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

Table 3: General Zones

Example Telecom Site for Area C07 on Statfjord B:

  • C07-TELE with description attribute: TELE - C07 - Cooling & water injection area

Example Zone names under Site C07-TELE on Statfjord B:

  • 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
  • C07-TELE-PA with description attribute: TELE – Public Address & Alarm

Example Piping Site for Area M33 on Heidrun:

  • M33-PIPE with description attribute: PIPE - M33 - Process Module Weather Deck

Example Zone name for piping system 21 in Area M33 on Heidrun:

  • M33-PIPE-21 with description attribute: PIPE - System 21 - Crude Handling

6.3.2 Structural Topside

Zones to be used only in the Topside Areas in PDMS 3D models for offshore platforms:

Discipline Zone Name Zone Description
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

Table 4: Structural Topside zones

6.3.3 Structural Hull

Zones to be used only in the Hull Areas in PDMS 3D models for Production Ships and Semi-Submersibles:

Discipline Zone Name Zone Description
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

Table 5: Structural Hull zones

6.3.4 Onshore Process plants – Structure and Civil

Zones to be used only in PDMS 3D models for onshore process plants:

Discipline Zone Name Zone Description
Structural {area}-STRU-ACCESS STRU - Access
Structural {area}-STRU-EQUIPMENTSUPPORT_seqNo STRU - EquipmentSupport
Structural {area}-STRU-MAINACCESSPLATFORM_seqNo STRU - Access Structure
Structural {area}-STRU-MAJORSUPPORTSTRUCTURE_seqNo STRU - Major Support Structure
Structural {area}-STRU-MECHHANDLING STRU - Mechanical Handeling
Structural {area}-STRU-PIPERACK_seqNo STRU - PipeRack
Structural {area}-STRU-STAIRTOWER_seqNo STRU - Stair Tower

Table 6: Structural zones for Onshore

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 PDMS 3D models for onshore process plants:

Discipline Zone Name Zone Description
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

Table 7: Civil zones for Onshore

6.3.5 GBS Civil

Zone to be used only in PDMS 3D models for offshore platforms with Gravity Base Structures:

Discipline Zone Name Zone Description
Civil {area}-CIVI-GBS CIVI - Gravity Base Structure

Table 8: GBS zones

6.4 As-Built Tagged Elements

All tagged elements in the Facility shall be represented with PDMS elements directly below the Zone level, like PIPE, EQUIPMENT and STRU elements or similar.

6.4.1 Pipe Tag

Piping Line Tags shall be represented with PDMS PIPE Elements modelled with the PDMS Design Pipework application. If the Piping Line 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.

As-Built Pipe Name shall be like:

<Short Tag>_<Area>

 

where is the shortest possible yet unique part of the Line Tag from Engineering Numbering System (ENS) document or Code Manual or similar governing document for the Facility.

Example PIPE Name:

Piping Line Tag from Snorre A: 12”-PT-16D804-AD205. In this case, since Product Code is required to make Snorre A Piping Line Tags unique, the Short Tag is: PT-16D804

Pipe name requirements for specific Company Facilities (normative examples):

Facility Line Tag from ENS or Code Manual As-Built PDMS Pipe Name
Brage 0050-ZPT-15-0070-HE1-4-B 15-0070_M10
Draupner 1.5-PL-21-1001-BC12-1 PL-21-1001_M11
Grane 0150-ZMH-11-5382-LA1-00-A 11-5382_M10
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 2”-P-486001-150A01-IH 486001_XXX
Kristin 50L0501-0400WS-AR71 50L0501_C2
Kvitebjørn 50L0025-0400WS-AT750 50L0025_P22
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
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
Visund 0150-ZPT-20-1234-CD1-00-A ZPT-20-1234_CD1
Åsgard A and B 08.00-WC-40L1206-AC200-001 40L1206_M40

Table 9: Pipe Name requirements by Facility

The Short Tag part for each Line Tag example is marked in bold text in Table 9. The As-Built PDMS Pipe name examples in Table 9 consist of a Short Tag and an Area. The examples are sufficiently named to allow a successful search for the Tag in the Company Engineering Tag register (after removing the suffix “_” and the Area-part for the query).

Duplicate As-Built Pipe names

In very few cases in a Facility, a PDMS 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 like:

 

<Short Tag>_<Area>-<Suffix B to Z>

 

Example Pipe names on Kvitebjørn:

 

  • First Pipe in Area P22: 50L0025_P22
  • Second Pipe in Area P22: 50L0025_P22-B 6.4.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 like: <Special Item>/<Suffix>

6.4.3 Equipment and Equipment nozzles

Tagged Equipment for all disciplines shall be represented by PDMS EQUI elements, and the EQUI element name shall be identical to the Tagged Equipment tag name.

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 like: <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 or the Code manual.

 

Example Equipment Tag for 2nd Stage Recompression Cooler on Åsgard B: 23HJ501

Example Nozzle name: 23HJ501/N1

6.4.4 Pipe Supports

Pipe Supports in the PDMS 3D model shall have the same name as the Pipe Support name required by the ENS document or Code manual.

The Pipe Support point in the PIPE element shall be represented by an ATTA element with name like:

<Pipe Support Name>/<Suffix A to Z>

 

Example Pipe Support names:

  • PS-M16-0455/A (where M16 is the plant Area)
  • PS-M16-0455/B (second connection point to a different Pipe)
  • A33-997-590/A (where A33 is the plant Area)

The Pipe Support STRU or EQUI element (or similar) representing the Pipe Support structural elements, shall be named like: <Pipe Support Name>

In the examples used above, the Pipe Support structure shall be named:

  • PS-M16-0455
  • A33-997-590

6.4.5 Structural Tags

Structural Tags like Monorails and Lifting Lugs shall be modelled using a STRU element for each Tag. The STRU name shall be identical to the Structural Tag name.

6.4.6 Skids and Package Tags

All tags in a Skid or Package shall be represented by PDMS elements directly under Zone, and placed in the correct discipline Zone. Structural support elements shall be placed in the correct Structural Zone, with a STRU name like: <Package Tag name>_SUPPORT

6.5 Special characters in PDMS names

Elements in PDMS representing Tags shall have PDMS 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 PDMS element name shall be replaced by an underscore character. In the case of other special characters, Contractor shall clarify this with Company.

Letters used in PDMS Names shall be from the 26 letters in the English alphabet only.

6.6 UDAs to be completed at As-Built

To complete the User Defined Attributes (UDA) on the As-Built elements, Contractors main MDB (see chapter 4.8) 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 and STRU elements created or modified by the project:

All EQUI, PIPE and STRU elements:

  • :OpeProject (the combination of Operator Project Code and Task Identifier)

The purpose of completing the combination of Operator Project Code and Task Identifier on an all As- Built elements created or modified by Contractor in his project, is to create a link to the Contractor and the Project which last modified or created the As-Built element. This promotes quality assurance and traceability of the As-Built deliverables.

In addition, for PIPE elements only:

  • :OpeTagNo (Operator Tag Number)
  • :OpePidNo (Operator Process and Instrumentation Diagram drawing number)

The OpeTagNo shall be identical to the Piping Line tag number in the As-Built Plant Tag register.

In addition, for STRU elements only:

  • :OpeDrwgNo (Operator Drawing Number)

The Structural drawing number listed for this UDA shall be one that makes it possible to find additional structural drawings in the document register.

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 Task
  • A Work Package
  • A sub-project in the plant 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 PDMS Global 3D CAD 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 of the specified Task. The Site name shall contain the combination of Project Code and Task identifier.

SITE name in the Project model shall be:

<Area Code>-<Discipline Long Code>_<Project Code - Task identifier>

Example Site name: C04-PIPE_WHP-WP01

where WHP is the Project Code* for “the Wellhead project”, and WP01 is the Task name (Work Package 1)

ZONE name in the Project model shall be:

<Area Code>-<Discipline Long Code>-<Subset Code>_<Project Code - Task identifier>

Example Zone name: C04-MECH-EQUIPMENT_WHP-WP01

For Project Code, see chapter 2.4, is assigned by Hub Administrator, and is identical to the Project Code used in database name and database description, see chapter 4.7

Both SITE and ZONE Position and Orientation shall be:

  • Orientation: Y is N WRT /* and Z is U WRT World
  • Position: E 0 N 0 U 0 WRT World

Contractors designers shall use the command “Q DESC OF DBREF” in PDMS Design to find information about the Project Code in the database description for the Project design in question.

7.3 Examples of using Task-based Site naming convention

7.3.1 Detail Engineering

Example Detail Engineering Site in the Snorre A SNR-project

Area is W41, Project Code is “SNR” for Snorre Redevelopment Detail Engineering, Task identifier is WP10 (Work Package 10), the Site contains Piping design.

Site name shall be:

W41-PIPE_SNR-WP10

7.3.2 Maintenance and Modification sub-project (Detail Engineering)

Example Maintenance and Modification sub-project on Norne FPSO

A Maintenance and Modification sub-project is to install a Structural platform in area P13 on Norne. “MM” is the Project Code for the Maintenance and Modification Project. 933155 is the Task identifier for the example M&M sub-project

Site name shall be:

P13-STRU_MM-933155

7.3.3 Study project with alternatives

Example Study Project Alternatives in the Snorre Future project (SNF)

“SNFS” is the Project Code for this Study Project. WP06 is the Work Package, ALT2 is Alternative 2 in this Study, so the Task Identifier is here WP06ALT2.

Site name shall be:

A00-PIPE_SNFS-WP06ALT2

7.3.4 Combining Areas in Project Site

For Projects with a limited number of design elements, where there will be few design elements in each Project Site, Contractor may choose to use a combined-area or “all-areas” area like A00 and place all elements in a single Project Site.

Example: Maintenance and Modification sub-project 944150 contains a handful of Mechanical tags placed in three facility Areas M15, M16 and M30. In this case, all Project design can be placed in Site:

  • A00-MECH_MM-944150

instead of the tree Sites:

  • M15-MECH_MM-944150
  • M16-MECH_MM-944150
  • M30-MECH_MM-944150

with one or two tags in each Site. In this example, MM is the Project Code for the Maintenance and Modification Project, while 944150 is the Task identifier for the Maintenance and Modification subproject.

The use of Combined Area Sites is an option for Contractor, and it is allowed to both use and not use combinations within the same project.

7.3.5 Combining Disciplines in Project Site

In the same way as combined Area Sites, Contractor may combine disciplines in suitable Projects into multidiscipline Sites using GENE as Discipline Long Code.

Example: Maintenance and Modification Project 921415 contains a handful of Piping tags, a few Pipe Supports, one Mechanical Tag and two Instrument Tags, all in the same area H20. All project design can be placed in the Site:

  • H20-GENE_MM-921415 i

nstead of using the four discipline Sites:

  • H20-PIPE_MM-921415
  • H20-PSUP_MM-921415
  • H20-MECH_MM-921415
  • H20-INST_MM-921415

In this example, MM is the Project Code for the Maintenance and Modification Project, while 921415 is the Task identifier for the Maintenance and Modification sub-project.

The use of Combined Discipline Sites is an option for Contractor, and it is allowed to both use and not use combinations within the same project.

7.4 Legal Project Zones

The list of legal Project Zones is identical to the list of legal As-Built Zones in chapter 6.3.

Zone area shall be legal facility areas, and not combined Areas like “A00”.

However, if Contractor requires additional Zone names, or a different division of the Subset Codes for in his Project, he may use additional Zone names. In such cases the Zone hierarchy used shall be used consistently by Contractor during his Project Execution, and the Contractor Work Procedure shall be updated, see chapter 2.2.

Regardless of the Zone hierarchy used during the Project, Contractor shall complete As-Built documentation of his Project design using only the legal As-Built Zones.

7.5 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 Code and Task identifier if that element represents modifications of tags already existing in the As-Built model.

For new Tags in the Facility, the Project Code and Task identifier is not required in the Tag name. The naming convention for new Tags is identical to the naming convention for As-Built Tags, see chapter 6.4

7.5.1 Tag name for modified tags

Tag name for modified tags shall be:

<Tag Name from Code Manual on ENS>_<Project Code - Task identifier>

Example Tag name: Existing Junction Box modified by the Low Pressure Project, Work Package 5: 83EL102-501-B01_LPP-WP05

7.5.2 Pipe Name for modified Piping Line tags

PDMS PIPE elements in Projects shall be named like As-Built Pipes, see chapter 6.4.1.

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 Code and Task identifier as a suffix.

<Short Tag>_<Area>_<Project Code - Task identifier>

Example As-Built Pipe from Kvitebjørn in Area P22: 50L0025_P22
The same Pipe modified by Project KCU, Work Package 12: 50L0025_P22_KCU-WP12

 


 

8 Requirements to Catalogue and specifications

8.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.

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.

8.2 Naming conventions, Piping

8.2.1 Spec World Element Name Syntax

SPWL name syntax shall contain Discipline Long code, Facility code, and an Abbreviated Contractor name:

<Discipline Long Code>-<Facility Code>-<Content>_<Abbreviated Contractot name>

Example SPWL from Veslefrikk A: PIPE-VFA-SPEC_AK

8.2.2 Specification Name Syntax

SPEC element name shall contain spec name and Abbreviated Contractor name.

<SPEC Name>_<Abbreviated Contractot name>

Example SPEC: AC200_AK

8.2.3 Selector Name Syntax

SELE name shall contain Spec name, Abreviated 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 like:

<SPEC Name>_<Abbreviated Contractot name>/<GTYPE>

Example first level SELE: AC200_AK/ELBO

9 Requirements to User Defined Attributes (UDA)

9.1 User Defined Attributes in PDMS Lexicon

The UDA World (UWRL) and UDA Group (UGRO) and User Defined Attribute (UDA)-elements in PDMS shall have names and UDNA starting with an Abbreviated Contractor name. The UDA-element in PDMS shall be named with capital letters at the start of words in the name, and otherwise non-capital 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. 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”. Abbreviated Contractor name shall be in capital letters.

Example UDA for Company Tag Number:

  • UDA 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.

10 Requirements to Level and Obstructions volumes

10.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

Example (from Aveva Cats&Specs training)
A manual valve is represented in detail, with hand wheel and valve externals using level 1-6 and OBST 0, and with two simplified cylinders with level 8-10 and OBST 2 for Clash Detection purposes.

10.2 Obstruction

The obstruction value for design elements shall be set to allow Clash Detection in the PDMS 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.

10.3 Required use of level and obstruction

10.3.1 Escape Routes

Escape Routes in the model shall be represented by EQUI elements with at least two PDMS 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.

10.3.2 Access Routes

Access Routes shall be represented similar as Escape Routes, but shall be placed in the zone {area}- MECH-ACCESSROUTE instead of the zone {area}-SAFE-ESCAPEROUTE.

10.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.

10.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 PDMS 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.

10.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 as per chapter 10.4.

10.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 temporary design, shall not be placed in a [PRO]-database. Such elements shall be placed in a suitable [TMP]-database which only the Contractor company designers can see. 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.5 User-Defined Equipment Types

User-Defined Element Types (UDETs) shall not be used in Company PDMS Global 3D CAD models.

11 Additional information

11.1 Definitions and abbreviations

Facility

Offshore Production platform, Semi-submersibles, Floating production ships (FPSO), and onshore Process Plants owned by Company.

PDMS Global

Software system delivered by AVEVA used to distribute and update PDMS 3D CAD models between locations like engineering offices and fabrication yards.

PDMS Global Hub

The Hub is the location where the overall PDMS 3D CAD model administration takes place.

PDMS Global Satellite

A Satellite is an office location outside the Hub where the PDMS 3D CAD model is to be distributed on a scheduled (daily) basis. Usually a contractor company office, but may be a Company Site office.

As-built

Last revision of an LCI item updated to reflect the true status of completed work with relation to specified tolerances.

Theoretic As-Built Versus As-Is

The 3D CAD model reflects a theoretic As-Built as the Company’s dimensional tolerances for the Contractor’s As-Built modelling typical result in deviations from the real Facility object locations.

Laser scan data as a supplement to the 3D CAD model gives the As-Is i.e. the total picture of the true As- Built. Even when the 3D CAD model is defined to be first-class As-Built, the laser scan data supplement representing the As-Is becomes essential as the 3D CAD 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.

Hub Administrator

Organisation responsible for administering the PDMS Global Hub location. Company is the Hub Administrator.

Master Project

A Contractor or Company PDMS 3D CAD model which functions as a library for common PDMS information to be used in other PDMS 3D CAD models. The master project typically contains catalogue information, drawing templates and UDA definitions.

  • CAD - Computer Aided Design
  • ENS - Engineering Numbering System, equivalent to the Coding system in a Code Manual
  • LCI - Life Cycle Information
  • MDB - Multiple Database, collection of PDMS databases in the PDMS Project
  • MPX - Company Master Project
  • PDMS - Plant Design Management System
  • UDA - User Defined Attribute in PDMS

11.2 Changes from previous version

11.2.1 Changes from version 1:

  • requirement for Contractor to use Task Based modelling during project execution
  • modified Site and Zone naming convention, and the legal Zone list
  • requirement for Contractor to supply a 3D-model report explaining his project model
  • clarified the requirements for the contents of the Contractor PDMS Work Procedure
  • clarified the requirements for Level and Obstruction use  reduced the number of User Defined Attributes to be completed by Contractor
  • new database content-type [STU] for Studies
  • facility-specific Pipe Name requirement listed as normative examples instead of in appendices

11.3 References

  • TR3110 Life Cycle Information (LCI) - Technical requirements and standards
  • TR0053 LCI Requirements - Engineering Contractor
  • TR0054 LCI Requirements - Supplier
  • TR0055 LCI Requirements - Fabrication
  • TR0056 LCI Requirements - Reference
  • TR0057 LCI Requirements - Digital formats

—————

Zpět