Integrated Project Execution Integrated Project Execution: User Guide

Integrated Project Execution
User Guide
Issue 1.0
Ref: User Guide

V1.0
PLEASE NOTE:
AVEVA has a policy of continuing product development: therefore, the information contained
in this document may be subject to change without notice.
AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS

DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
While every effort has been made to verify the accuracy of this document, AVEVA Solutions
shall not be liable for errors contained herein or direct, indirect, special, incidental or
consequential damages in connection with the furnishing, performance or use of this
material.
This manual provides documentation relating to products which you may not have access to
or which may not be licensed to you. For further information on which Products are licensed
to you please refer to your licence conditions.
 Copyright 2003 AVEVA Solutions Limited
All rights reserved. No part of this document may be reproduced, stored in a retrieval
system or transmitted, in any form or by any means, electronic, mechanical, photocopying,
recording or otherwise, without prior written permission of AVEVA Solutions.
The software programs described in this document are confidential information and
proprietary products of AVEVA Solutions Ltd or its licensors.
For details of AVEVA worldwide sales and support offices, see our website at
http://www.aveva.com/
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB
VANTAGE Integrated Project Execution User Guide
ISSUE HISTORY
Date Issue No Remarks
15-Jul-03 1.0 First Issue
vipe user doc.doc Page 3 of 73

Table of Contents
1. INTRODUCTION.......................................................................................................................... 7
1.1 Background................................................................................................................................... 7
1.2 Document Purpose..................................................................................................................... 10
1.3 Document Organisation and Content......................................................................................... 10
2. INSTALLATION ISSUES............................................................................................................ 12
2.1 VPD............................................................................................................................................. 12
2.2 VPE P&ID ................................................................................................................................... 12
2.3 VPE and VPRM.......................................................................................................................... 12
2.4 Version Dependencies ............................................................................................................... 13
3. CONFIGURATION ..................................................................................................................... 14
3.1 VPD............................................................................................................................................. 14
3.2 VPE P&ID ................................................................................................................................... 14
3.3 VPE Workbench......................................................................................................................... 14
3.4 VPRM.......................................................................................................................................... 14
4. INTEGRATED BUSINESS PROCESSES OVERVIEW ............................................................ 15

4.1 P&ID / Design Integrity ............................................................................................................... 15
4.2 Engineered Item Requisitioning and Procurement.................................................................... 15
4.3 Piping Catalogue and Specifications Alignment ........................................................................ 16
4.4 Piping P&ID Material Take Off (MTO)........................................................................................ 16
4.5 Design / Layout Integrity............................................................................................................. 17
4.6 Piping Bulk Material Take Off..................................................................................................... 17
4.7 Piping Isometric Material Take Off ............................................................................................. 18
4.8 Instrument Hook-Up Material Take Off ...................................................................................... 18
5. INTEGRATED BUSINESS PROCESSES DETAIL ................................................................... 19

5.1 P&ID / Design Integrity ............................................................................................................... 19
5.1.1 Overview ...................................................................................................................... 19
5.1.2 Procedures .................................................................................................................. 19
5.1.2.1 VPE P&ID: Produce P&IDs ...............................................................................19
5.1.2.2 VPE: Maintain Engineering Design Data............................................................20
5.1.2.3 VPE: Issue Engineering Design Data ................................................................20
5.1.3 Interfaces ..................................................................................................................... 20
5.1.3.1 VPE P&ID to VPE: P&ID Data...........................................................................20
5.1.3.2 VPE to VPE P&ID: Released Design Data .........................................................21
5.1.4 Points to Note .............................................................................................................. 22
5.2 Engineered Item Requisitioning and Procurement (VPE / VPRM)............................................ 23
5.2.1 Overview ...................................................................................................................... 23
5.2.2 Procedures .................................................................................................................. 23
5.2.2.1 VPRM & VPE: Categorise Engineered Items for Requisitioning Purposes ............23
5.2.2.2 VPRM & VPE: Maintain Engineered Item List for Requisitioning Purposes ...........24

5.2.2.3 VPRM & VPE: Maintain Requisition & Purchase Order Details for Eng’d Items.....24
5.2.3 Interfaces ..................................................................................................................... 24
5.2.3.1 VPRM to VPE: Engineered Item Material Requisition Identifiers ..........................24
5.2.3.2 VPE to VPRM: Engineered Items ......................................................................25
5.2.3.3 VPRM to VPE: Engineered Item Requisition & PO Data .....................................26
5.2.4 Points to Note .............................................................................................................. 27
5.3 Piping Catalogues and Specifications Alignment (VPD / VPE / VPRM) ................................... 28
5.3.1 Overview ...................................................................................................................... 28
5.3.2 Procedures .................................................................................................................. 28
5.3.2.1 PDMS & VPRM: Catalogue Maintenance...........................................................28
5.3.2.2 VPE & VPRM: Pipe Specification Summary Maintenance...................................29
5.3.2.3 VPRM & PDMS: Pipe Specification Detail Maintenance......................................29
5.3.3 Interfaces ..................................................................................................................... 30
5.3.3.1 PDMS to VPRM: PDMS CATREF Masks...........................................................30
5.3.3.2 VPE to VPRM: Pipe Specification Summary Details ...........................................30
5.3.3.3 VPRM to PDMS: Cats and Specs Data..............................................................32
5.3.4 Points to Note .............................................................................................................. 33
5.4 Piping P&ID MTO (VPE / VPRM) ............................................................................................... 34
5.4.1 Overview ...................................................................................................................... 34
5.4.2 Procedures .................................................................................................................. 34
5.4.2.1 VPE: Maintain Process Line Design Data ..........................................................34
5.4.2.2 VPRM: Maintain Process Line List.....................................................................34
5.4.2.3 VPRM: Produce P&ID MTO ..............................................................................34
5.4.3 Interfaces ..................................................................................................................... 35
5.4.3.1 VPE to VPRM: Process Line Data.....................................................................35
5.4.4 Points to Note .............................................................................................................. 36
5.5 Design / Layout Integrity (VPD / VPE) ....................................................................................... 37
5.5.1 Overview ...................................................................................................................... 37
5.6 Piping Bulk MTO (VPD / VPRM) ................................................................................................ 38
5.6.1 Overview ...................................................................................................................... 38
5.6.2 Procedures .................................................................................................................. 38
5.6.2.1 VPE & VPRM: Process Line List Maintenance ...................................................38
5.6.2.2 PDMS & VPRM: Piping Bulk MTO Maintenance.................................................38
5.6.3 Interfaces ..................................................................................................................... 39
5.6.3.2 PDMS to VPRM: Piping Bulk MTO ....................................................................40
5.6.4 Points to Note .............................................................................................................. 41
5.7 Piping Isometric MTO (VPD / VPRM) ........................................................................................ 42
5.7.1 Overview ...................................................................................................................... 42
5.7.2 Procedures .................................................................................................................. 42
5.7.2.1 VPE & VPRM: Process Line List Maintenance ...................................................42
5.7.2.2 PDMS & VPRM: Piping Isometric MTO Maintenance..........................................42
5.7.3 Interfaces ..................................................................................................................... 43
5.7.3.2 PDMS to VPRM: Piping Isometric MTO .............................................................43

5.7.4 Points to Note .............................................................................................................. 44

5.8 Instrument Hook-Up Material Take Off ...................................................................................... 45
5.8.1 Overview ...................................................................................................................... 45
5.8.2 Procedures .................................................................................................................. 45
5.8.2.1 VPRM: Maintain Instrument Hook-Ups as Standard Assemblies ..........................45
5.8.2.2 VPE: Maintain Instrument Design Data..............................................................45
5.8.2.3 VPRM: Maintain Instrument Hook-Up MTO ........................................................45
5.8.3 Interfaces ..................................................................................................................... 46
5.8.3.1 VPE to VPRM: Instrument Hook-Up Details .......................................................46
5.8.4 Points to Note .............................................................................................................. 47
6. APPENDICES ............................................................................................................................ 48
6.1 Integrated Business Processes Detail ....................................................................................... 48
6.2 VPE P&ID & VPE Workbench Configuration............................................................................. 50
6.2.1 ‘Local’........................................................................................................................... 50
6.2.2 ‘Shared’........................................................................................................................ 51
6.3 VPD / VPRM Piping Integration ................................................................................................. 52
6.3.1 Concepts...................................................................................................................... 53
6.3.1.1 Catalogue and Specifications Alignment .............................................................53
6.3.1.2 Bulk MTO Interface ...........................................................................................54
6.3.1.3 Isometric MTO Interface ....................................................................................54
6.3.2 VPRM Configuration.................................................................................................... 57
6.3.2.1 Material Catalogue ............................................................................................57
6.3.2.2 Specification Production ....................................................................................57
6.3.3 PDMS Configuration.................................................................................................... 58
6.3.3.1 PDMS Project Number ......................................................................................58
6.3.3.2 Managing Bolts.................................................................................................58
6.3.3.3 Pipe Specification Attributes ..............................................................................58
6.3.3.4 PDMS Option File Settings ................................................................................58
6.3.3.5 Pipe Attributes ..................................................................................................60
6.3.4 Interface Configuration ................................................................................................ 62
6.3.5 PDMS Design Procedures .......................................................................................... 65
6.3.5.1 Design Database ..............................................................................................65
6.3.5.2 Fabrication Database ........................................................................................66
6.3.5.3 Tagged / Named Items ......................................................................................66
6.3.6 Generating MTO on PDMS Projects with non-VPRM Specifications......................... 68
6.3.7 VPRM MTO Text File Format...................................................................................... 71
6.3.7.1 General ............................................................................................................71
6.3.7.2 Record Types ...................................................................................................71
6.3.7.3 Batch Record Definition .....................................................................................71
6.3.7.4 Line Record Definition .......................................................................................71
6.3.7.5 Section Record Definition ..................................................................................72
6.3.7.6 Component Record Definition ............................................................................72

1. INTRODUCTION
1.1 Background
IPE (Integrated Project Execution) is the term used to describe the collaboration of all parties
and applications involved in the execution of EPC (Engineering, Procurement, and
Construction) process plant projects.
It is universally accepted that IPE delivers significant benefits to both the Engineering Contractor
and the Owner-Operator in terms of improved quality and reduced timescales. Indeed, IPE is
now often seen as crucial to the viability of Engineering Contractors. An effective IPE solution
involves three key elements:
Easily Accessible Information
The availability of current and correct information to all project personal is crucial to effective
project execution. It is particularly important that this is achieved without relying on complex
application expertise.
A key feature of VANTAGE Enterprise NET (VNET) delivers this capability.
Global Execution
For Engineering Contractors to remain competitive, today’s projects invariably involve the
interaction of personnel from several different locations including those from low cost centres.
Each individual VANTAGE application has been designed to enable this in a responsive and
cost-effective manner.
Data Integration
Integrating data is a difficult task due to the fact that an EPC project involves:
• A lengthy and complex workflow
Process Dept Engineering Dept

1. Process Design (Civil, Structural, Mechanical,
Piping, Electrical, Instruments) Main thrust
1. Mechanical Design
2. Physical Design for IPE
3. Material Requirements
Primary Processes
Conceptual Operations &
Detail Design Procurement Construction Commissioning
Design Maintenance
Support Processes
Planning
Materials Management
Document Management and Control
Progress & Productivity
Cost Management
Project Management
EPC / OO EPC OO

• Many departments and personnel, eg
Chief Executive
Sales VP Engineering VP Operations VP Finance VP
Project Manager
Engineering Project Controls Procurement Construction

Manager Manager Manager Manager
Process Structural Planning Purchasing Fabrication
Piping Mechanical Cost Expediting Erection

Control
Electrical Instruments Inspection Installation
Progress
Document Weight Shipping Commis-
Control Control sioning
Sub-
Project Engineers Contracts
• And, huge amounts of evolving data and large numbers of evolving documents, eg on a
medium sized project:
Vessels / Tanks 25
Equipment Exchangers 12
Pumps 60
Pipe Length 20,000 M

Pipe Fittings 15,000
Pipe Valves 2,500
Material
Insrument Loops 1,200
Instrument Cable 80,000 M
Electrical Cable 100,000 M
Engineering Documents 6,000

Piping Isometrics 1,000
Documents Vendor Documents 6,000
Requisitions 120
Purchase Orders 150
The effective integration of the computer applications utilised during a project’s lifecycle is
crucial in minimizing error and re-work and maximizing the speed of response to change.
Integrating applications developed by different parties (in-house and commercial products)
utilising different IT architectures is time-consuming, complex, and difficult to maintain.

The base VANTAGE products are:

VPD: VANTAGE Plant Design
VPE: VANTAGE Plant Engineering
VPRM: VANTAGE Project Resource Management.
When implemented together, they form a significant portion of the strategic applications utilised
by the Engineering Contractor and are delivered with significant ready-made integration thus
eliminating the need for time and resource to be expended in the data integration exercise.
Project Resource Management Plant Design Plant Engineering Third Party Applications
Project Controls Planning Design Progress Cost Management
Engineering Engineering Engineering Procurement Construction

Design Layout Requirements
Design Document Control 3D Model
Buying
(Planning, Distribution, Production Monitoring) Review
P&IDs Piping Construction

Expediting
Specifications Planning
Management
Process
Mechanical Bulk Inventory
Data
Multi-Discipline Inspection
Material Take Off Control
Piping 3D Modelling
Requisition Construction
Instruments Shipping
Production Progress
Electrical
Vendor Documents
Commissioning
2D / 3D Integrity (Planning, Distribution, Production Monitoring)
Document Vault
Materials Management Planning and Monitoring
Project Management Executive Information (Decision Making Support)
Thus IPE, in the context of this document, relates to implementing an IPE solution involving the
integration of two or more of the VANTAGE base products (ie inter-product integration) taking
into account that each of the individual products already provides a significant degree of
integration both within the functionality they provide (internal integration) and with other
applications (external integration).
The VANTAGE IPE solution has been designed specifically to integrate the total engineering
workflow throughout the four major multi-discipline phases, ie
• P&ID production (VPE P&ID)
• Engineering design data development (VPE Workbench)
• 3D modelling (VPD PDMS)
• Materials Management (VPRM).
It is based on the following principles:
• Single-source data entry
• Best-practice workflow
• Pro-active change management
• A VNET friendly environment.

As a consequence, the benefits accrued by the customer implementing the total VANTAGE IPE
solution are significantly greater than those delivered by the VANTAGE products in isolation.
Internal Product to Product External

Integration Integration Integration
VPD VPD
Data Access VNET Data Collaboration
In-built - Stress Analysis
multi-discipline - Structural Design
plant layout design VPE VPE P&ID VPRM - Geometry exchange
integrity / consistency Intelligent - etc
Engineering P&IDs Materials
VPE Design Management VPE
Data
In-built - Process simulators
multi-discipline Document - Feed data
P&ID, process and VPD Control - Design tools
Engineering
eng'g design data Model Mgmt - Operations
Data
integrity / consistency 2D/3D - Maintenance
Management Project
Integrity - etc
Controls
VPRM Engineering VPRM
In-built VPD PDMS Project - Estimating
Design
multi-department Tools Multi-Discipline Management - Planning
materials mgmt and 3D Model - Document Mgmt
project controls data - Timesheets
integrity / consistency - Financials
Data Access VNET Data Collaboration
- etc
1.2 Document Purpose

This document is aimed at the relevant person in a customers’ organisation who has
responsibility for an integrated IT environment or more specifically, for ensuring that when two
or more of the VANTAGE products are being used during project execution, the benefits of the
VANTAGE IPE solution can be realised. Its purpose is to identify decisions that need to taken,
and procedures that need to be followed, with respect to IPE.
This document should be read in conjunction with:
• VANTAGE Product documentation
• The VANTAGE Compatibility Matrix (published on the AVEVA web support page)
Duplication between IPE and product documentation has only been introduced where absolutely
necessary for clarification purposes.
1.3 Document Organisation and Content

The document is organised as follows:
Section 2: General Installation Issues
This section describes general issues that need to be considered when installing a product for
IPE purposes as opposed to stand-alone application. Installation issues relating to software
required for a specific interface is described when discussing that interface.
Section 3: General Configuration Issues
This section describes general issues that need to be considered when configuring VANTAGE
products for IPE purposes as opposed to stand-alone application. Configuration of software
required for a specific interface is described when discussing that interface.

Section 4: Integrated Business Processes (IBPs) Overview

This section provides an overview of the integrated business processes currently supported by
the VANTAGE IPE solution. The purpose of each IBP is documented.
Section 5: Integrated Business Processes Detail
This section describes each IBP in turn and in detail. It is organised as follows:
1. Overview
An overview of the IBP with a workflow diagram that summarises the procedures and
interfaces involved.
2. Procedures
The detailed procedures to be followed to execute this IBP.
3. Interfaces
Documentation describing each of the interfaces that comprise the IBP organised as follows:
a. Purpose: The role this interface plays in the overall process
b. Installation: Installation instructions for software required for this interface
c. Configuration: Any specific product configuration required for this interface
d. Interface Execution: How the interface is executed
e. Data Processing: How the data involved is processed by the interface
f. Interface Methodology: How the interface works from a technical point of view (for
information and trouble-shooting purposes)
4. Points to Note
Any further points to be considered when utilising the IBP are described here.
Section 6: Appendices

2. INSTALLATION ISSUES
2.1 VPD
There are no specific installation requirements when installing VPD.
2.2 VPE P&ID

When installing VPE P&ID for IPE working, the information messages regarding associated
products and components need to be addressed. See the following example install message:
Here, VPE P&ID can still be installed even though an associated product is not present.
However, its absence will prevent use as part of the VANTAGE IPE solution.
2.3 VPE and VPRM

There are no specific installation requirements when installing VPE and VPRM.
The VPE and VPRM databases are totally separate and are assumed to reside on different
servers. However, this is not a requirement; there are constraints, eg versions of the Oracle
software.
The majority of the interfaces between the two products operate by means of neutral, shared
tables (known as “buffer tables”). These tables are present in both the VPE and VPRM
databases. The product sourcing the data populates the relevant buffer table at key events and
the receiving product accesses and transfers the data via a database link.
All necessary tables and procedures are created by the respective installation procedures.
Setting up the database links is covered in the configuration section of this document.
If the VPE and VPRM Workbench databases are resident on non-networked machines, pseudo
databases should be created on each machine, ie a pseudo VPE database should be created
on the VPRM machine and vice-versa. These pseudo databases should contain only the six
interface buffer tables: ensc01, ensc02, ensc04, ensc06, scen03 and scen05. The database
links established in the real VPE and VPRM databases need to reference their pseudo
databases. Finally, external procedures should be used to action periodic exports:
• From the real VPE database to the VPE pseudo database on the VPRM machine for tables
ensc01, ensc02, ensc04 and ensc06
• And from the real VPRM database to the VPRM pseudo database on the VPE machine for
tables scen03 and scen05.
The frequency of the exports should be determined by individual installations and activity on the
project.

2.4 Version Dependencies

This documentation assumes latest versions of VANTAGE products.
Third party product versions and operating systems, etc need to be considered.
Refer to the IPE compatibility documentation for details.

3. CONFIGURATION
3.1 VPD
Following installation, no general configuration is required for VPD for IPE purposes.
Configuration required specific to individual interfaces is included in the subsequent sections
within this document that relate to the interface concerned.
3.2 VPE P&ID

For full functionality such as ‘Save to Model from VPE P&ID’ to work, which uses the client
server mechanism, even on the web based version of VPE Workbench, certain files and paths
must be correctly defined and in place. Important files, paths and entries, and their locations
are shown in the Appendix entitled “VPE P&ID & VPE Workbench Configuration”.
3.3 VPE Workbench

Data is transferred between VPE and VPRM on a project basis. Each VPE project needs to be
configured to point to the corresponding VPRM Oracle Database and Project. The VPE and
VPRM project numbers must be the same.
The link is created by using the following form:
VPE>Interfaces>VPRM>Setup>General Data
Enter the following data:
• In the “Project Number” field, enter the number of the VPRM project with which the transfer
link is to be established. The data in this field cannot be edited once it has been entered.
• In the “Password” field, enter the password of a relevant VPRM System Administrator. This
establishes that the transfer link has been authorised.
When the above fields are completed, the “VPRM Connect String” field can be completed with
the file name and location of the VPRM database. The data in this field cannot be edited.
3.4 VPRM
Data is transferred between VPRM and VPE on a project basis. Each VPRM project needs to
be configured to point to the corresponding VPE Oracle Database and Project. The VPE and
VPRM project numbers must be the same.
The link is created by using the following screen:
VPRM>SYSADM>Screens>Create Dataset>Create/Re-Register Dataset
Hit the “Create VPE Interface…” button and enter the following data:
• VPE Username: The Oracle username of the owner of the interface tables
• VPE Password: The password for the above
• VPE Service Name: The tnsnames alias for the database where VPE resides
• VPE Database Link: A unique name given to the database link.

4. INTEGRATED BUSINESS PROCESSES OVERVIEW

Currently, VANTAGE IPE offers eight integrated business processes (IBPs) as illustrated in the
following diagram:
VPE VPE 2 VPD VPRM

P&ID Integrated Engineered Item Integrated Integrated
Requisitioning 3
Intelligent Engineering Plant Layout Design Materials
& Procurement Piping Cats & Specs
P&IDs Design Alignment
Management
VPD PDMS and

VPRM Interface
4
Piping P&ID MTO
5
Design / Layout
Integrity
VPE
Model Object Manager
1 6
P&ID / Design Piping Bulk MTO
Integrity
VPD PDMS and
VPRM Interface
VPE
Connectivity Manager
7
VPE Piping Isometric MTO
Comparator
VPD PDMS and
VPRM Interface
8
Instrument Hook-Up
Material Take Off
A detailed version of this diagram is included in the Appendix entitled “Integrated Business
Processes Detail”. It illustrates the total procedurised workflow and all interfaces involved.
4.1 P&ID / Design Integrity

The purpose of this IBP is to maximise the integrity of information shown on P&IDs with detailed
engineering design data.
This is achieved within an efficient work process that eliminates the needs to re-enter the same
data on P&IDs and in the VPE engineering design database whilst ensuring data consistency.
It assumes that when using VANTAGE:
• VPE P&ID is the tool used for P&ID production
• VPE Workbench is the tool used to identify and manage engineering design data.
Specifically, this IBP provides:
• Population of the VPE engineering design database with P&ID data that has been validated
and resolved (ie all connectivity issues have been validated)
• The ability to include data developed in VPE on the P&ID.
4.2 Engineered Item Requisitioning and Procurement

The purpose of this IBP is to maximise integrity between:
• Engineered items (ie tagged items from the Equipment List and Instrument Index) identified
within the VPE engineering design data (including that shown on the P&ID on the
assumption that the P&ID / Design Integrity process has been used)

• And, engineered items included within VPRM requisitions and purchase orders.
This is achieved within an efficient work process eliminating the need to re-enter the same data
at the various stages in the life cycle of an engineered item.
• VPE is the tool utilised for identifying and managing engineered items in terms of the
equipment list and instrument index
• VPRM is the tool utilised to acquire (requisition, procure, etc) engineered items.
The process will:
• Help ensure that engineered items acquired using VPRM are consistent with engineered
items identified within the VPE engineering design database
• Enable VPE to store and display requisition and purchase order information derived directly
from VPRM.
4.3 Piping Catalogue and Specifications Alignment

The purpose of this IBP is to maximise the integrity between:
• Pipe specifications identified within the VPE engineering design data (including those shown
on the P&ID on the assumption that the P&ID / Design Integrity process has been used)
• And, pipe specifications used for material take off purposes within VPRM
• And, pipe specifications used for 3D Modelling purposes within VPD PDMS.
This is achieved within an efficient work process which includes significantly reduction in the
effort and expertise required to produce PDMS pipe specifications.
• VPE is the tool utilised for identifying and managing engineered objects in terms of the pipe
specifications
• VPRM is the tool utilised to produce pipe specifications for both material take off purposes
and PDMS 3D modelling purposes.
• VPD is the tool used for 3D modelling.
The process will ensure that:
• Pipe specification data within VPE, VPRM and PDMS is totally consistent
• Material identification within VPRM and PDMS is totally consistent in terms of part numbers
and their attributes (eg descriptions and weights).
It is a key stage in subsequent integrated business processes (Piping Bulk MTO and Piping
Isometric MTO) for ensuring material consistency between piping material data in PDMS (eg
isometrics) and VPRM (material take off and subsequently requisitions, purchase orders, site
material control, etc) in terms of components and their quantities.
Note that the use of VPE in this IBP is optional.
4.4 Piping P&ID Material Take Off (MTO)

Whilst piping MTO can be undertaken at any stage in the life of a project, it is traditionally
carried out at three defined stages. These are referred to as:
• Preliminary or P&ID
Because of long deliveries it is usually necessary to identify material requirements at an
early stage. This MTO is made according to information available at the time. It is standard
practice to develop P&IDs and piping routing diagrams to a sufficient level of detail such that
material can be identified to a construction control area, its appropriate delivery point, and to
its line number.
• Intermediate or Bulk
This MTO is essentially an update of the P&ID MTO using better developed information,
ideally sourced from the 3D Model.

• Final or Isometric
This MTO usually includes the production of isometric drawings from the 3D Model.
This IBP supports the P&ID (or preliminary) MTO process undertaken in VPRM.
Its purpose is to ensure that the P&ID MTO undertaken in VPRM has consistency and integrity
with VPE engineering design data (including that shown on the P&ID on the assumption that the
P&ID / Design Integrity process has been used).
This is achieved within an efficient work process eliminating the need to re-enter process line
data for MTO purposes.
• VPE is the tool utilised for identifying and managing engineered objects in terms of process
lines
• VPRM is the tool utilised to produce material take off.
Currently, this IBP will help ensure that the process lines used for VPRM MTO are totally
consistent with those identified within the VPE Engineering design data (and therefore on the
P&IDs). Thus, the IBP will help ensure that an MTO has been undertaken for all lines identified
on the P&ID and not for lines that are not identified on the P&IDs (unless the user chooses to
consciously do otherwise).
A further potential development will be to ensure consistency of MTO items with items shown on
the P&ID.
4.5 Design / Layout Integrity

The purpose of this IBP is to maximise integrity between:
• Engineering objects (engineered items and process lines) identified and detailed within the
VPE engineering design data (including that shown on the P&ID on the assumption that the
P&ID / Design Integrity process has been used)
• And, the equivalent engineering objects modelled in PDMS.
This is achieved within an efficient work process:
• Eliminating the need to re-enter engineered item process line data for 3D modelling
purposes
• Enabling effective management of engineering objects throughout their engineering life
cycle
• Enabling quicker and more accurate checking of the 3D model design (eg piping isometrics)
against the P&ID.
• VPE is the tool utilised for identifying and managing engineering objects in terms of the
equipment list, instrument index, and process line list
• PDMS is the tool utilised for 3D modelling purposes.
4.6 Piping Bulk Material Take Off

This IBP supports the Bulk (or intermediate) MTO process undertaken in VPRM.
Its purpose is to ensure that the Bulk MTO undertaken in VPRM:
• Has consistency and integrity with VPE engineering design data (including that shown on
the P&ID on the assumption that the P&ID / Design Integrity process has been used)
• Is populated with the latest design data available from the 3D Model.
data and component details for MTO purposes.
lines

• PDMS is the tool used for 3D modelling (note that VPRM contains similar functionality for
use when using Intergraph’s PDS product for 3D modelling)
• VPRM is the tool utilised to produce the pipe specifications for both material take off
purposes in VPRM and 3D modelling purposes in PDMS
4.7 Piping Isometric Material Take Off

This IBP supports the Isometric (or final) MTO process undertaken in VPRM.
Its purpose is to ensure that the Isometric MTO undertaken in VPRM:
• Has consistency and integrity with VPE engineering design data (including that shown on
the P&ID on the assumption that the P&ID / Design Integrity process has been used)
• Is populated with the final design data available from the 3D Model, ie the MTO in VPRM
(which can subsequently be used for requisitioning, procurement, and site material control
purposes) is totally consistent with that on the isometric bill of material.
data and component details for MTO purposes.
lines
• PDMS is the tool used for 3D modelling (note that VPRM contains similar functionality for
use when using Intergraph’s PDS product for 3D modelling)
• VPRM is the tool utilised to produce the pipe specifications for both material take off
purposes in VPRM and 3D modelling purposes in PDMS
4.8 Instrument Hook-Up Material Take Off

This IBP supports the instrument hook-up MTO process undertaken in VPRM.
Its purpose is to ensure total consistency between:
• Hook-ups identified for instruments within the VPE engineering design data
• And, the material take off recorded in VPRM to satisfy the hook-ups.
This is achieved within an efficient work process eliminating the need to re-enter hook-up data
for MTO purposes other than an initial multi-project set-up requirement.
• VPE is the tool utilised for identifying and managing engineered objects in terms of
instruments and their hook-ups
• VPRM is the tool utilised to produce instrument hook-up material take off.
This is achieved by defining:
• Instrument hook-up material in the VPRM material catalogue
• And, instrument hook-ups as VPRM standard assemblies.

5. INTEGRATED BUSINESS PROCESSES DETAIL
5.1 P&ID / Design Integrity
5.1.1 Overview
The following diagram illustrates the integrated process for ensuring P&ID / Design integrity.
VPE P&ID: Produce P&IDs

p1a) Draft P&IDs
p1b) Save P&ID data to Plant
Connectivity Model (Save to Model)
p1c) Check PCM integrity (Resolve i1
Differences) P&ID Data
> P&IDs
VPE Workbench: Issue P&ID Data

p2a) Add process lines and eng'd
items not derived from P&ID
p2b) Maintain process line and
engineered item design data
p3a) Release / delete process lines
and engineered items i2
Released Design Data
> Equipment List, Instrument

Index, Process Line List, etc
The process comprises:

• Three procedures:
1. VPE P&ID: Produce P&IDs
2. VPE: Maintain engineering design data
3. VPE: Issue engineering design data
• Two interfaces:
1. VPE P&ID to VPE: P&ID Data
2. VPE to VPE P&ID: Released Design Data
5.1.2 Procedures
5.1.2.1 VPE P&ID: Produce P&IDs

a. The P&ID is drafted in VPE P&ID.
b. As and when appropriate, as decided by the user, the P&ID is in effect “issued” by means of
the VPE “Save to Model” function which activates the following interface:
i1: P&ID Data
A copy of the drawing should also be saved into the database so that it is available for use
by VPE Comparator or VPE Connectivity Manager in conjunction with VPE PDMS firstly to
assist in building the 3D model, and subsequently to assist in comparing the content of the
P&ID with that of the 3D model for integrity purposes.
c. The final stage in the procedure is to check the integrity of the transferred P&ID data, ie
resolve differences.

5.1.2.2 VPE: Maintain Engineering Design Data

a. Having established the P&ID data in VPE as the basis for the managed engineering design
data, the VPE user may add any engineering objects (engineered items and process lines)
that are not derived from the P&ID.
b. The VPE engineer is then in a position to add and maintain detailed engineering design
data.
5.1.2.3 VPE: Issue Engineering Design Data

a. The design data for each engineered item and process line is released or deleted as and
when appropriate by utilising the release / delete process. This data is then made available
for inclusion on the P&ID via the interface:
i2: Released Design Data
5.1.3 Interfaces
5.1.3.1 VPE P&ID to VPE: P&ID Data

a. Purpose
This interface enables the user to validate the integrity of P&ID information and transfer key
information to VPE Workbench to provide a sound foundation for the development of the
engineering design data.
b. Installation
The interface is delivered as an integral part of VPE – no additional installation is required.
c. Configuration
No configuration is required.
d. Interface Execution
The connection and transfer process is a manual mechanism. Unconstrained, it can be
invoked on demand and will succeed providing the data is sufficiently complete. Any user
can action the transfer but the connection to the database is constrained by a VPE login.
In VPE P&ID, first establish the connection to the desired database as described in the
product documentation.
When connected to the database, the ‘Save To Model’ action is invoked from the user
interface. This starts the Save to Model utility 1. The Save to Model dialogue is a form
providing the settings and feedback for the validation and save processes. Validation details
provide a log of the progress and give warnings, which allow the save to continue, and
errors, which will prevent completion of the save.
e. Data Processing
All actual and logical engineering objects on the P&ID and their attributes (properties) are
transferred. Connectivity is implied by the arrangement in the file and by ownership. Certain
annotation is transferred where it provides a trigger or enhancement to the engineering
information, eg a sheet connector, which contributes to the connected model.
Validation checks the objects to see if they are valid object types, with names and
connectivity or ownership to suit the VPE model schema.
1
If the connection to the database is not established the ‘Save to Model’ action will start the Save To
Model utility, validate the drawing data and create the intermediate files in the file system. The options for
Load and Verification are not available in the Save to Model dialogue. It will not pass that data into VPE
Workbench.

A resolve action can be triggered in the VPE database.

f. Interface Methodology
Transfer is on the basis of 12 output files, which are delimited text files. A single drawing
‘sheet’ is the unit of transfer. Transferring part of a P&ID network is not possible. The action
invokes a separate ‘Save to Model’ software process. The files are parsed and the collected
data is loaded into VPE tables. The action uses a Client/Server’ mechanism even in the
web based architecture VPE version but there is no need for a local VPE installation, just an
Oracle client. It uses the existence of the tnsnames file to establish database connection.
The transfer makes use of a discrete set of properties required by VPE that it formulates into
the 12 files. Additional ‘user defined’ properties are transferred via an additional (13th) text
file, with the extension “.usd”, to a special table in VPE. A representation of the drawing can
also be saved with the text files for later use with Design / Layout Integrity IBP.
5.1.3.2 VPE to VPE P&ID: Released Design Data

a. Purpose
To populate the P&ID drawing with additional properties, captured from the VPE engineering
design data, where they originated.
b. Installation
The interface is delivered as integral part of VPE – no additional installation is required.
c. Configuration
Some properties for plant items will not originate in the P&ID. These, created directly in the
engineering design database, are made available for display on the P&ID.
When a plant item is selected in VPE P&ID, providing an equivalent engineering object
exists in the connected database, ie one with the same name, then, with an action from a
right button menu selection, the properties for that item will be displayed in a separate tab in
the properties dialogue. By adding a label to the drawing and associating the label with the
plant item, the properties are then assigned to the contents of the label. If the plant item is
deselected on the diagram then the properties will no longer be displayed and thus not
available for assignment. If another item is selected then its properties will be available and
so on. The properties, once assigned to a plant item and displayed in a label, can be
updated from a right button menu action at the P&ID. This retrieves the latest information
content from the database for that item and property
e. Data Processing
The association is made on the basis of a matching engineering object in the drawing and
the database. The matching criteria is ‘engineering name’ (tag). All the properties are
provided at the drawing for user selection and added to the diagram by selection and
assignment to a label.
The basis of the ‘transfer’ is achieved by capturing the data content for an object on the
drawing, from the released tables of VPE Workbench. The action can only take place where
there is a database “connected” to the P&ID. The process uses a “Client/Server”
mechanism even in the web-based architecture VPE version but there is no need for a local
VPE installation, just an Oracle client. It uses the existence of the tnsnames file to establish
database connection. The data collection is carried out via the VPE Workbench Read API
and the result loaded into the properties dialogue in the P&ID application. The information

can only be pasted and displayed via pre-defined labels. Updates can be actioned from
within the P&ID user interface.
5.1.4 Points to Note

1. P&ID Data Interface
a. Equipment can only be loaded to VPE Workbench. Resolve will not be carried out 2.
b. Only whole sheets can be transferred (see above).
c. Unnamed plant items on the P&ID will be ignored in the transfer.
2. Released Design Data
a. The information can only be permanently displayed using labels on the diagram.
b. The information, and thus the label, is associated with a named plant item on the
diagram that corresponds to a named plant item in the VPE Workbench engineering
model.
c. The data is not automatically updated by the provider, an update is initiated by the
receiver, ie at the P&ID.
2
At Version 4.4

5.2 Engineered Item Requisitioning and Procurement (VPE / VPRM)
5.2.1 Overview
The following diagram illustrates the integrated business process for engineered item
requisitioning and procurement.
VPE Workbench VPRM

p1b) Continue to maintain engineered i1 p1a) Set-up and maintain Material
item design data including assigning Eng'd Item Material Requisition Identifiers (MR-Ids)
MR-Ids to engineered items Requsition Identifiers
VPE Workbench VPRM

i2
p2a) Release / Delete engineered p2b) Maintain Engineered Item List
Engineered Item
items
Design Details
> Data Sheets, Equipment List,

Instrument Index, etc
VPE Workbench VPRM

i3
p3c) Maintain requisition and p3a) Requisition engineered items
Engineered Item
purchase order data p3b) Procure engineered items
Requisition & PO Data
p3d) View / report engineered item
requisition and purchase order data
> Engineered Item Requisitions
and Purchase Orders, etc

1. VPRM & VPE: Categorise engineered items for requisitioning purposes
2. VPRM & VPE: Maintain engineered item data
3. VPRM & VPE: Requisition and procure engineered items.
• Three interfaces:
1. VPRM to VPE: Engineered Item Material Requisition Identifiers
2. VPE to VPRM: Engineered Item Design Details
3. VPRM to VPE: Engineered Item Requisition and Purchase Order Data
5.2.2 Procedures
5.2.2.1 VPRM & VPE: Categorise Engineered Items for Requisitioning Purposes
VANTAGE uses “Material Requisition Identifiers (MR -Ids)” to identify groupings of like material
that are likely to be available from a single vendor and therefore are likely to be included on one
requisition. Assigning an MR -Id to each engineered item enables the automatic generation of
the material contents of a requisition (ie as a default, all items with the same MR -Id are included
in the same requisition) thereby eliminating the need for a user to assign items to requisitions on
an item-by-item basis. Assigning MR -IDs also enables engineered items to be classified for
requisitioning purposes without knowledge of actual requisition numbers.
a. MR-Ids are set up and maintained in VPRM.
b. Best practice workflow is for MR -Ids to be assigned to engineered items in VPE at the time
the engineer is defining the engineered item in terms of its design data. To achieve this in
the most efficient manner, MR -Ids are made available to the VPE user from VPRM by
means of the interface:
i1: Engineered Item Requisition Identifiers

This interface provides the VPE engineer with a list of valid MR -IDs. Once configured, this
interface is automatic, ie no manual intervention is required.
Assigning MR -IDs to engineered items in VPE is carried out in either the Process module or
the relevant discipline module.
5.2.2.2 VPRM & VPE: Maintain Engineered Item List for Requisitioning Purposes
Within VANTAGE, VPE is the source for the list of valid engineered items but VPRM requires its
own Engineered Item List (referred to by VPRM as the Process Tag List) for general materials
management purposes and more specifically for controlling the engineered item requisition
process.
a. As engineered items are released or deleted in VPE by the owning discipline (either Process
or the relevant discipline), relevant details are made available for VPRM purposes. MR -Ids
should be assigned to engineered items prior to their release.
b. The VPRM Engineered Item List is maintained by the user executing the following interface
as and when required by the user:
i2: Engineered Item Design Details
Executing the interface processes the data into VPRM in accordance with a set of rules.
5.2.2.3 VPRM & VPE: Maintain Requisition & Purchase Order Details for Eng’d Items
There is often a requirement in VPE to store and output requisition and purchase order data for
engineered items, for example on the instrument list and datasheets.
This is achieved by transferring requisition and purchase order data from VPRM to VPE via the
interface:
a. As requisitions are issued in VPRM, relevant details are made available for VPE purposes.
b. As purchase orders are issued to the Vendor in VPRM, relevant details are made available
for VPE purposes.
c. Requisition and purchase order data is maintained in VPE by executing the following
interface as and when required by the user:
i3: Engineered Item Requisition and PO Data
Executing the interface results in the requisition and purchase order data being stored in the
VPE database.
d. The processed data is now available for viewing and reporting within VPE.
5.2.3 Interfaces
5.2.3.1 VPRM to VPE: Engineered Item Material Requisition Identifiers

a. Purpose
To make available a list of valid MR -IDs for the VPE engineer to use when assigning them to
engineered items.
b. Installation
The interface is delivered as an integral part of VPE and VPRM – no additional installation is
required.
c. Configuration
Log on to the VPE database using SQL and execute the script:
scen_views.sql
Executing this script provides the VPE user with access to view the MR -ID information.

Following configuration, this interface is automatic, ie no action is required in either VPE or
VPRM.
e. Data Processing
There is no processing of the data, ie it is used by VPE exactly as provided by VPRM.
The interface is enabled by means of a shared “buffer table” known as ‘SCEN03’ that is:
• Automatically populated with MR -Ids and descriptions as and when the data is
maintained in VPRM
• Automatically used to provide a ‘List of Values’ in VPE.
5.2.3.2 VPE to VPRM: Engineered Items

a. Purpose
To ensure compatibility between the engineered items in VPE (the source) and the
engineered item list in VPRM (referred to as the process tag list) that drives the process for
requisitioning items in VPRM.
b. Installation
required.
c. Configuration
This interface is executed from VPRM using the following screen:
VPRM>ADMIN>Interfaces>VPRM Interface
It is recommended that this interface be executed on a regular basis, ideally following the
release or deletion of any item in VPE. More specifically, it should be executed prior to
requisition production in VPRM.
The following options are available:
‘Full’ or ‘Partial’ Transfer
The ‘Full’ option processes all released items from VPE to VPRM, while the ‘Partial’
option processed only those items that have been added or changed since the last time
a transfer took place.
As a general rule, the ‘Partial’ option should always be used as this requires less
processing effort and therefore will execute more quickly than the ‘Full’ option.
The ‘Full’ option is for use following the failure of a ‘Partial’ run due to system failure.
Create Project Items
This checkbox should always be checked. The un-checked option is provided for use in
circumstances where the VPE user is not assigning MR -Ids – see points to note.
Change Tag Description
This checkbox allows a project to select whether responsibility for the engineered item
description is that of the VPE user (Design Engineer) or VPRM user (Requisitioning
Engineer):
• If the checkbox is checked then descriptions are controlled by VPE and therefore are
updated on transfer

• If the checkbox is not checked then the description in VPRM will not be updated on
transfer and it will be the responsibility of the VPRM user to maintain them.
As a general rule, it is recommended that this check box is ‘Checked’, ie VPE is treated
as the ‘master’ or the ‘source’ for the descriptions of engineered items.
e. Data Processing
Executing the interface will take the relevant VPE engineered item data and process it into
VPRM according to a set of rules. During processing, error and warning messages may be
generated. These are viewed using the following screen:
VPRM>ADMIN>Interfaces>VPRM Interface Audit
They must always be checked and actioned appropriately.
The rules by which the data is processed are documented in the VPRM Project
Administration On-Line Guide.
The interface is enabled by means of a shared “buffer table” known as ‘ENSC01’ that is:
• Automatically populated with details as and when engineered items are released and
deleted in VPE. The information for each item is time stamped which is how VPRM
recognises changed data when a ‘Partial’ transfer is executed.
• Read from by VPRM as and when the interface is executed.
5.2.3.3 VPRM to VPE: Engineered Item Requisition & PO Data

a. Purpose
To enable VPE to store and display requisition and purchase order information derived
directly from VPRM.
b. Installation
required.
c. Configuration
This interface is executed from VPE using the following screen:
VPE/Instruments/Utilities/Import Requisitions
It is recommended that this interface be run on a regular basis, ideally following the issue
(first and subsequent) of any Requisition or Purchase Order in VPRM. Note that project
personnel can be automatically notified by e-mail as and when requisitions and purchase are
issued in VPRM.
Two options are available: ‘Full’ and ‘Partial’ transfer. The ‘Full’ option processes all
requisition and purchase order details that have been added or changed since the last time
the interface was executed.
As a general rule, the ‘Partial’ option should always be used as this requires less processing
effort and therefore will execute more quickly than the ‘Full’ option.
e. Data Processing
There is no processing of the data, ie it is used by VPE exactly as provided by VPRM.
However, if the requisition or purchase order has been cancelled or the engineered item has
been removed from a requisition or purchase order then the requisition or purchase order
details are deleted from VPE.

The interface is enabled by means of a “buffer table” known as ‘SCEN03’ that is:
• Automatically populated with details as and when requisitions and purchase orders are
issued in VPRM. The information for each item is time stamped which is how VPE
recognises changed data when a ‘Partial’ transfer is executed.
• Read from by VPE as and when the interface is executed.

1. MR-ID Maintenance
Whilst not recommended, MR -IDs can also be assigned to engineered items within VPRM.
If this procedure is followed, the need for the Engineered Item Material Requisition Identifiers
interface is eliminated.
Whilst not recommended, the VPE user can assign MR -IDs that have not been derived from
VPRM, ie the VPE user can create them. In this case, the Engineered Item Design Details
interface ensures integrity is maintained between VPE and VPRM by creating the MR -ID in
VPRM and highlighting this fact to the VPRM user.
MR-IDs cannot be renamed or deleted in either VPRM or VPE.
2. Engineered Item List Maintenance
Setting an engineered item to ‘Undelete’ in VPE will not result in the item being recreated in
VPRM on transfer. Currently, this situation needs to be handled manually.
3. Requisition and Purchase Order Details Maintenance
VPRM requisition and purchase order details are maintained in VPE for instruments only.

5.3 Piping Catalogues and Specifications Alignment (VPD / VPE / VPRM)
5.3.1 Overview
Before utilising this IBP, reference should be made to the Appendix entitled “VPD / VPRM
Piping Integration”.
The following diagram illustrates the integrated business process for aligning piping catalogue
and specification data between the three base VANTAGE products.
PDMS VPRM
p1a) Maintain catalogue i1 p1c) Import CATREF Mask details
p1b) Export CATREF Mask details PDMS CATREF p1d) Map VPRM and PDMS
Masks catalogues
VPE Workbench VPRM

p2a) Continue to maintain process line i2 p2c) Import Pipe Specification
design data Pipe Specification Summary
p2b) Release / Delete process lines Summary Details
> Process Line List, etc

PDMS VPRM
p3b) Import catalogue data & specs p3a) Develop and approve specs
i3) Cats & Specs Data
> Pipe Specifications

1. PDMS & VPRM: Catalogue maintenance
2. VPE & VPRM: Pipe specification summary maintenance
3. VPRM & PDMS: Pipe specification detail maintenance
• Three interfaces:
1. PDMS to VPRM: PDMS CATREF Masks
2. VPE to VPRM: Pipe Specification Summary
3. VPRM to PDMS: Catalogue and Pipe Specification Data
5.3.2 Procedures
5.3.2.1 PDMS & VPRM: Catalogue Maintenance

In order for VPRM to generate the PDMS pipe specifications and associated data, components
within the VPRM and PDMS Catalogues need to be mapped.
The key mapping is between the VPRM Commodity Code / Part Number and the PDMS
CATREF. The process is made quick and efficient by the provision of functionality to map
VPRM components to a CATREF mask. To aid this process, CATREF details can be
transferred from PDMS for use as a List of Values (LoV) within VPRM via an interface which
involves generating a text file from PDMS and importing it into VPRM as described below. It
should be executed regularly as and when CATREFs are created in PDMS.
a. The PDMS Catalogue is maintained in the conventional manner (defining CATREFs, etc) to
include all components that are required by the pipe specifications.
b. The first stage in executing the PDMS CATREF Mask Interface is to generate a text file from
PDMS. The required structure of the data within the text file consists of multiple records of
three fields that are separated by one or more spaces - the last field may contain embedded
spaces:

Field Description
GTYPE Mandatory
Maximum 4 A/N characters
CATREF Mask Mandatory
Maximum 50 A/N characters
More likely a partial CATREF, but may also be a full CATREF
CATREF Mask Maximum 120 A/N characters
Description Optional
eg
CAP AAKC200 CAP LONG ANSI B16.9 BW
ELBO AAEA200 ELBOW LR ANSI B16.9 BW
A PDMS report template is provided to extract this file. It is named:
vprm_catrefs.tmp.
By default, it is located in the Interface directory:
C:\AVEVA\PDMS_VPRM\pdmsui\REPORTS\TEMPLATES.
Alternatively, the template can be copied into the PDMS template directory:
PDMSUSER\REPORTS\TEMPLATES
To access this template the user selects:
PDMS>Paragon>Utilities>Reports>Modify
The template is then selected using the File Browser from the relevant director.
c. The second stage in executing the PDMS CATREF Mask Interface is to import the text file
into VPRM via the interface:
i1: PDMS CATREF Masks
The interface should be run regularly in order to ensure the CATREFs LoV in VPRM reflects
the CATREFs currently defined in the PDMS project.
d. Finally, the VPRM Catalogue is maintained in the conventional manner (commodity codes,
part numbers, etc) to include all components that are required by the pipe specifications; this
includes mapping VPRM components to PDMS components making use of the CATREFs
list of values provided by this interface.
5.3.2.2 VPE & VPRM: Pipe Specification Summary Maintenance

This optional procedure ensures that pipe specifications used in VPRM (and therefore PDMS)
are identically named to those detailed in VPE (and VPE P&ID), the source system for this
information. It is achieved by transferring specification data from VPE to VPRM.
a. Process line design data is maintained in VPE in the conventional manner.
b. As process lines are released and deleted in VPE, relevant specification details are made
available for VPRM purposes.
c. The specification details are maintained in VPRM by executing the following interface as
and when required by the user via the interface:
i2: Specification Summary
5.3.2.3 VPRM & PDMS: Pipe Specification Detail Maintenance

This procedure ensures total consistency between the pipe specs in VPRM and PDMS.
a. Within VPRM, pipe specifications are detailed for both VPRM and PDMS purposes. When
the specification has been assigned the status of “Approved”, PDMS transfer files can be
requested using the screen:

VPRM>SPEC>Screens>Interfaces>PDMS Data Transfer

Select the specification required for transfer, and hit the transfer specification button. This
will create the appropriate files in the directory identified in the directory field.
The Specification Details file will always be produced. The other three files (Component
Description Details, Bolt Details, Component Weight Details) will be produced if VPRM
detects the need to update PDMS with the data concerned. However, if a number of
specifications are being transferred it is recommended that a full description file be
generated.
Facilities are also provided to transfer all description, bolt, and weight data independently of
generating the specification file should it be required.
Whenever transfer files are generated, the relevant PDMS user should be informed in order
that the import process is actioned. This is best achieved using VPRM’s automatic
notification facilities.
This form is also used to generate the Bolt Data and Client Part Number files that are
optionally used during isometric production.
b. Import the transfer files into PDMS via the interface:
i3: Cats and Specs Data
If used, the Bolt Data and Client Part Number files need to be copied into the appropriate
folder as defined when configuring the Isometric MTO interface.
5.3.3 Interfaces
5.3.3.1 PDMS to VPRM: PDMS CATREF Masks

a. Purpose
To ensure the availability of, and quick and easy access to, correct CATREF data in VPRM.
b. Installation
The interface is delivered as an integral part of VPRM – no additional installation is required.
c. Configuration
See Appendix entitled “VPD / VPRM Piping Integration”.
The interface is executed from VPRM using the following screen:
VPRM>MCAT>Interfaces>PDMS CATREF Masks
Hitting the “Import” button replaces all records. A completion message identifies the number
of records originally and currently, plus a breakdown of records rejected (if any). To identify
an erroneous record, review the input file and screen display simultaneously.
e. Data Processing
There is no processing of the data, ie it is used by VPPRM exactly as provided by PDMS in
the text file.
The interface is enabled by a text file load procedure in VPRM.
5.3.3.2 VPE to VPRM: Pipe Specification Summary Details

a. Purpose
To ensure compatibility between the pipe spec names in VPE and VPRM, ie that specs
developed in VPRM have integrity with specs detailed in the engineering design database
(VPE) and on the P&ID (VPE P&ID).

b. Installation
required.
c. Configuration
This interface is executed from VPRM using the following screen:
VPRM>SPEC>Interfaces>VPE – VPRM Interface
It is recommended that this interface be run on a regular basis to capture all the pipe
specifications that have been released or deleted in VPE.
The following option is available:
a transfer took place.
e. Data Processing
Following interface execution the Pipe Specifications will be transferred from VPE to VPRM
in accordance with the following set of rules:
VPE Status = Released
• Spec does not exist in VPRM
• New spec created in VPRM with identification that it has been sourced from VPE
• Status set to ‘Registered’
• Specification description automatically set to ‘Added from Spec Summary Interface’
followed by the transfer date
• Process Description set to “Pipe Material Description” as defined in VPE.
• Spec exists in VPRM
• If VPRM status is ‘Working’, then it is updated to indicate it has been sourced from
VPE with amended descriptions
• If VPRM status is ‘Checked’ then it is re-set to ‘Working’ and updated accordingly.
• Any ‘Approved’ copies are not updated.
VPE Status = Deleted
• Spec does not exist in VPRM
• No action taken
• Spec exists in VPRM
• If the spec is not ‘Approved’, and the spec has not been used on the Process Line
List or for MTO, then the spec is deleted from VPRM
• If the spec has been Approved or used on the Process Line List or for MTO, then it is
not deleted but it is no longer identified as being sourced from VPE.
During processing, error and warning messages may be generated. These are viewed
using the following screen:
VPRM>SPEC>Interfaces>VPRM Interface Audit
They must always be checked and actioned appropriately.

• Automatically populated with details as and when the relevant engineering objects are
released and deleted in VPE. The information for each specification is time stamped
which is how VPRM recognises changed data when a ‘Partial’ transfer is executed.
5.3.3.3 VPRM to PDMS: Cats and Specs Data

a. Purpose
This interface ensures compatibility between the pipe specifications in PDMS and VPRM.
b. Installation
This interface requires the VPD PDMS to VPRM Interface to be installed as described in the
Release Bulletin that accompanies the software.
c. Configuration
See appendix entitled “VPD / VPRM Piping Integration”.
This interface is executed from PDMS using the following form:
PDMS>Paragon>Utilities>VPRM-PDMS File Loader
Simply select the files that need to be imported and they will be processed in the correct
sequence, ie
1. Component Description Details (Paragon)
2. Bolt Details (Paragon)
3. Component Weight Details (Propcon)
4. Specification Details (Specon)
Alternatively, conventional PDMS macro import facilities can be used by entering the
relevant PDMS module and running the file on the command line using “$m/filename”.
e. Data Processing
The data is processed in the conventional PDMS macro manner.
A log file is available to check for any loading errors.
When the specification details have been successfully run, a message will be printed to the
screen “Spec Updated, Please check the limbo spec for any deleted components”.
The sequence of events for a specification import into PDMS is:
• Rename any elements that have been changed in VPRM; a part number change may
cause this
• Unlock any locked SPCOM elements; these are elements that are deemed to be PDMS
elements only.
• Remove all elements to limbo spec
• Import all specification elements from VPRM; this will transfer them from limbo spec into
the main specification
• Lock all elements unlocked in the previous two stages
• All elements that remain in limbo spec are elements that have been deleted for the main
specification.
The interface is enabled by VPRM creating standard PDMS macro’s that are then imported
into PDMS using standard PDMS macro import facilities via a loader form which ensures the
macro’s are loaded in the correct sequence.


1. Updating Specification Components in PDMS
Part numbers that have been changed in the specification will be automatically updated in
the design database; the PDMS user needs to ensure any consequential layout changes are
made.

5.4 Piping P&ID MTO (VPE / VPRM)
5.4.1 Overview
The following diagram illustrates the integrated business process that supports the P&ID MTO
undertaken in VPRM, traditionally referred to as “Preliminary MTO”:
VPE Workbench VPRM

p1a) Continue to maintain process line p2a) Maintain Process Line List
design data i1
p1b) Release / Delete process lines Process Line Data
VPRM
> Process Line List, etc p3a) Produce P&ID MTO
> MTO Reports, etc

1. VPE: Maintain process line design data
2. VPRM: Maintain process line list
3. VPRM: Produce P&ID MTO
• One interface:
1. VPE to VPRM: Process Line Data
5.4.2 Procedures
5.4.2.1 VPE: Maintain Process Line Design Data

a. The process line engineering design data is maintained in the conventional manner within
VPE Workbench.
b. As and when the process line data is ready for issue, it is released (or deleted) in the
conventional manner.
5.4.2.2 VPRM: Maintain Process Line List

a. The process line list in VPRM, which is the starting point and controlling mechanism for
VPRM MTO, is maintained by executing the following interface:
i1: Process Line Data
Having ensured that the VPRM process line list reflects the VPE process line list (and thus,
lines on the P&IDs) detailing the MTO is currently a manual process. Facilities are available
in VPRM to compare the lines for which MTO has been undertaken with lines on the process
line list.
5.4.2.3 VPRM: Produce P&ID MTO

a. The user is now in a position to detail P&ID (or “preliminary”) MTO.

5.4.3 Interfaces
5.4.3.1 VPE to VPRM: Process Line Data

a. Purpose
This interface ensures compatibility and integrity between the process line list maintained in
VPE (and therefore the lines identified on the P&IDs) and the process lines for which a P&ID
MTO is undertaken.
b. Installation
required.
c. Configuration
Process line data can be created in VPE and/or VPRM.
Best practice workflow is to originate the Process Line data in VPE then use this interface to
transfer the lines to VPRM, thus ensuring consistency. The interface should then continue
to be used to update lines already created in VPRM, with data from VPE.
The Process Line information transfer is made on-demand from VPRM using the following
screen:
VPRM>PMTO>Screens>Interfaces>VPRM Interface
The transfer is best run regularly to capture changes in VPE – as a minimum upon formal
issue of P&IDs.
a transfer took place. The user may re-specify the time and date from which processing
is to be actioned.
e. Data Processing
When this interface is run, process line information will be transferred from VPE to VPRM.
VPE Status = Released
• Line does not exist in VPRM (ie no VPRM line found with the VPE SIN (System Item
Number) of the line being imported and no matching process line number found)
• New line created in VPRM for the given VPE SIN with the following significant
attributes:
• VPE SIN and “Sourced from VPE” flag
• Process Line Number (The VPRM process line number by concatenating the
VPE “Process” and “Line Sequence Number” fields with a “hyphen” delimiter.
If this VPRM process line number has already been used against a different
VPE SIN, then a numerical suffix is added to maintain uniqueness. This
method of re-identification ensures the efficiency of VPRM searching and
sorting; process line numbers often begin with ‘Size’ in VPE, resulting in
illogical sorting within VPRM.)

• Pipe Specification (if the spec does not already exist in VPRM, then it will be
automatically created)
• Process Area (if the process area does not already exist in VPRM, then it will
be automatically created)
• P&ID Number
• Line Description (concatenation of VPE fields “Line Source” and “Line
Destination” with a separator of “to”)
• Insulation Code (VPE field “Insulation Type”) and Thickness
• Tracing Type
• Paint Code (VPE field “Paint Spec”)
• Line exists in VPRM (ie VPRM line found with the VPE SIN (System Item Number) of the
line being imported or matching process line number)
• If the line has no MTO
• The VPRM line and its associated attributes are updated
• If the line has MTO and there are changes to spec, insulation spec and / or process
area
• No updating takes place and a warning is issued
• If the line has MTO and there are no changes to spec, insulation spec and / or
process area
• The VPRM line and its associated attributes are updated
VPE Status = Deleted
• Line does not exist in VPRM (no VPRM line found with the VPE SIN (System Item
Number) of the line being imported and no matching process line number found)
• No action taken
• Line exists in VPRM (VPRM line found with the VPE SIN (System Item Number) of the
line being imported or matching process line number)
• If the line has no MTO
• The VPRM line is deleted
• If the line has MTO
• The indication that is has been sourced from VPE is deleted but its associated
attributes are left unchanged.
• Automatically populated with details as and when the relevant engineering objects
(process lines) are released and deleted in VPE. The information for each object is time
stamped which is how VPRM recognises changed data when a ‘Partial’ transfer is
executed.

1. Process Line Data
If VPRM receives data from VPE that exceeds VPRM’s maximum allowable number of
characters then the data will be truncated. Processing will continue with appropriate warning
message being issued.
If, on transfer, a line is found to have no spec defined in VPE, then VPRM will ignore the line
and an appropriate error message will be issued.

5.5 Design / Layout Integrity (VPD / VPE)
5.5.1 Overview
VPD Connectivity Manager (previously VPE Comparator) enables:
• Key information regarding engineering objects identified in VPE Workbench (process lines
and engineered items) to be transferred to PDMS such that that the 3D modelling can be
initiated utilising data which is consistent with that used in engineering design
• Comparison between 3D data (PDMS) and 2D data (VPE) to ensure integrity between the
layout and design data (including that on the P&ID). It can be used to compare one pipe, an
area of a P&ID or a complete P&ID. A report is produced which highlights the differences in
sequencing between the P&ID and the Model. This is usually carried out prior to isometric
production.
VPD Model Object Manager enables the monitoring of progress and status made in completing
engineering objects in terms of both engineering design (VPE) and plant layout (PDMS).
Full details are provided in the product documentation.

5.6 Piping Bulk MTO (VPD / VPRM)
5.6.1 Overview
The following diagram illustrates the integrated business process for creating or updating VPRM
MTO with MTO data from PDMS prior to isometric production – this process supports what is
traditionally referred to as “Intermediate MTO”:
VPE Workbench VPRM

p1a) Continue to maintain process line p1c) Continue to maintain Process
design data i1 Line List

VPD PDMS VPRM
p2a) Continue to develop 3D Model i2 p2c) Import piping bulk MTO
p2b) Generate piping bulk MTO Piping Bulk MTO p2d) Produce intermediate MTO
> General Arrangements, etc > MTO Reports, etc
This process comprises:

• Two procedures:
1. VPE & VPRM: Process Line List Maintenance
2. PDMS & VPRM: Piping Bulk MTO Maintenance
• Two interfaces:
2. PDMS to VPRM: Piping Bulk MTO
5.6.2 Procedures
5.6.2.1 VPE & VPRM: Process Line List Maintenance

The procedures involved are described in the Piping P&ID MTO IBP section of this document.
5.6.2.2 PDMS & VPRM: Piping Bulk MTO Maintenance

a. The pipework within the 3D model is developed in the conventional manner taking into
account that:
• Pipes need to be assigned certain attributes which will subsequently be used by the
interface which transfers MTO from PDMS to VPRM. The attributes concerned are
detailed below in the configuration section of the “VPD PDMS to VPRM: Piping Bulk
MTO” interface
• The interface relies on various conventions being followed when modelling the pipe work
in PDMS. These conventions are detailed in Appendix 6.4.
b. As and when required, VPRM piping MTO can be created or updated by means of the
following interface:
i2: Piping Bulk MTO
Executing this interface produces a text file in the appropriate format for import to VPRM.
c. The PDMS-produced piping bulk MTO text file is imported into VPRM using the following
screen:
VPRM>PMTO>Screens>Interface>Process Batch MTO

Firstly, the PDMS-generated MTO file needs to be loaded into the VPRM database:
• Enter the directory (folder) in which the PDMS generated MTO file is located.
• Click on the “Load Batch MTO Files” button
• Select the file/s from the MTO File Previewer screen (note that the browser will allow
selection of one file by clicking with the mouse, or additional files by use of Ctrl-click,
shift-click and shift-Ctrl-click in the conventional Windows manner)
• Click on the “OK” button
• Click on “Create Batch” button.
The MTO can now be processed in accordance with the following options:
Create Process Lines
This check box should be left unchecked – when using the VANTAGE IPE solution,
process lines should only be created using the VPE Process Line interface.
Create Tags
Validate Only
It is recommended that import files are firstly validated only and then processed. Thus,
on the first occasion that a file is processed into VPRM, it is recommended that this
check box should be checked. This enables the user to check and eliminate any error
and warning message prior to processing the file when this check box should be
unchecked.
Automatically Confirm
If MTO for the batch of lines concerned is being created in VPRM for the first time then
this check box should be checked.
If MTO for the batch of lines concerned is being updated then the user should:
• Check the box if it is required to overwrite the existing MTO
• Leave the check box unchecked if further analysis is required in VPRM prior to
deciding whether or not the MTO being imported is in a more developed state than
that already resident in VPRM. Where appropriate, the confirm process will need to
be actioned via VPRM screens in the conventional manner.
Ignore MTO for any Section with Invalid Components
This option allows the user to choose whether or not the import process will ignore lines
that contain invalid components (an error message is displayed against the rejected
sections). If the batch has been fully validated prior to processing as recommended
above then this will not be necessary. Therefore, this check box should be left
unchecked.
Actual /Estimate
As a general rule, the type of MTO should be set to “Estimate”.
Processing is initiated by hitting the “Process Batch Data” button. The results should
always be checked by hitting the “Review Validation” button – note that a report can be
produced.
5.6.3 Interfaces

This interface is described in the Piping P&ID MTO IBP section of this document.

5.6.3.2 PDMS to VPRM: Piping Bulk MTO

a. Purpose
This interface transfers pre-isometric MTO from PDMS to VPRM.
b. Installation
This interface requires the VPD PDMS to VPRM Interface to be installed as described in the
Release Bulletin that accompanies the software. However note that installation should
already have been completed to support the Piping Cats and Specs Alignment IBP.
c. Configuration
Configuration requirements are described in the appendix entitled “VPD / VPRM Piping
Integration”.
The interface is executed from the form:
PDMS>Design>Pipework>Utilities>VPRM Bulk MTO
This form enables the user to select the pipes for which an MTO extraction is required and
the parameters for the extraction process:
Directory
This is the directory (folder) into which the MTO extraction file/s will be placed. This will
default to the PDMSUSER directory, as defined by the environment variable
PDMSUSER. The user may change this to an existing directory by typing the value in. If
the directory does not exist, the directory will be reset to the PDMSUSER directory.
File
This is the name of the file into which the MTO will be extracted. It will default to
“bulkmto.dat”. The user may change this to any filename required. If the “One File per
MTO” option is selected, then this field will be greyed out and not available to the user.
Consolidated into Single File
This option directs the interface to place the MTO for all identified pipes into a single file
(named as described above).
One File per MTO
This option directs the interface to create individual files for each line identified. The file
names used will be named as the “Mto Line Ref attribute” of the pipe, suffixed by “-0”.
CofG Co-ords On / Off
This option enables the user to specify whether or not each component record in the
MTO extraction file should be output with Centre of Gravity coordinates. The default is
“Off” which will result in all like-components being consolidated with a multi-quantity.
The option should be set to ‘On’ only if the project requires component CofG coordinates
in VPRM for weight control purposes, etc.
Add, Remove and Remove All
These buttons enables the user to modify the contents of the detail list, ie the pipes for
which MO is to be extracted.
Log
This display will detail any messages regarding the extraction process.
Processing is initiated by hitting the “Apply” button.
e. Data Processing
There is no communication with VPRM when producing this file.

MTO for each pipe is detailed as “Unsectioned”, ie the VPRM section number is set to “00”.
No bolting MTO is transferred.
The interface software is executed using PML.

1. PDMS Modelling Conventions
This IBP relies on various conventions being followed when modelling the pipe work in
PDMS. These conventions are detailed in the appendix entitled “VPD / VPRM Piping
Integration”.
2. MTO Updates
Within VPRM, imported MTO will supersede existing MTO based on a match of
“Construction Area” and “Process Line Number”.

5.7 Piping Isometric MTO (VPD / VPRM)
5.7.1 Overview
The following diagram illustrates the integrated business process for creating or updating VPRM
MTO with MTO data from PDMS at the time of isometric production – this process supports
what is traditionally referred to as “Final MTO”:
VPE Workbench VPRM

design data i1
Line List

VPD PDMS VPRM
p2a) Continue to develop 3D Model i2 p2c) Import piping isometric MTO
p2b) Generate piping isometrics Piping Isometric MTO p2d) Produce final MTO
> Piping Isometrics, etc > MTO Reports, etc
This process comprises:

• Two procedures:
1. VPE & VPRM: Process Line List Maintenance
2. PDMS & VPRM: Piping Isometric MTO Maintenance
• Two interfaces:
2. PDMS to VPRM: Piping Isometric MTO
5.7.2 Procedures
5.7.2.1 VPE & VPRM: Process Line List Maintenance

The procedures involved are described in the Piping P&ID MTO IBP section of this document..
5.7.2.2 PDMS & VPRM: Piping Isometric MTO Maintenance

a. The pipework within the 3D model is developed in the conventional manner taking into
account that:
• Pipes need to be assigned certain attributes that will subsequently be used by the
interface that transfers isometric MTO from PDMS to VPRM. The attributes concerned
are detailed below in the configuration section of the “VPD PDMS to VPRM: Piping
Isometric MTO” interface
• The interface relies on various conventions being followed when modelling the pipe work
in PDMS. These conventions are detailed the appendix entitled “VPD / VPRM Piping
Integration”..
b. As piping isometrics are produced, VPRM piping MTO can be created or updated by means
of the following interface:
i2: Piping Isometric MTO
Executing this interface produces a text file in the appropriate format for import to VPRM.
c. The PDMS-produced piping bulk MTO text file is imported into VPRM using the following
screen:

VPRM>PMTO>Screens>Interface>Process Batch MTO

Firstly, the PDMS-generated MTO file needs to be loaded into the VPRM database:
• Enter the directory (folder) in which the PDMS generated MTO file is located.
• Click on the “Load Batch MTO Files” button
• Select the file/s from the MTO File Previewer screen (note that the browser will allow
selection of one file by clicking with the mouse, or additional files by use of Ctrl-click,
shift-click and shift-Ctrl-click in the conventional Windows manner)
• Click on the “OK” button
• Click on “Create Batch” button.
The MTO can now be processed in accordance with the following options:
Create Process Lines
Create Tags
Validate Only
It is recommended that import files are firstly validated only and then processed. Thus,
on the first occasion that a file is processed into VPRM, it is recommended that this
check box should be checked. This enables the user to check and eliminate any error
and warning message prior to processing the file when this check box should be
unchecked.
Automatically Confirm
This check box should always be checked in order to give each line section a status of
“Confirmed” thus making it automatically available for transfer to the VPRM Site Material
Control module for construction scheduling purposes.
Ignore MTO for any Section with Invalid Components
This option allows the user to choose whether or not the import process will ignore lines
that contain invalid components (an error message is displayed against the rejected
sections). If the batch has been fully validated prior to processing as recommended
above then this will not be necessary. Therefore, this check box should be left
unchecked.
Actual /Estimate
The type of MTO should be set to “Actual”.
Processing is initiated by hitting the “Process Batch Data” button. The results should
always be checked by hitting the “Review Validation” button – note that a report can be
produced.
5.7.3 Interfaces

This interface is described in the Piping P&ID MTO IBP section of this document.
5.7.3.2 PDMS to VPRM: Piping Isometric MTO

a. Purpose
This interface transfers isometric MTO from PDMS to VPRM.

b. Installation
This interface requires the VPD (PDMS) VPRM Interface to be installed as described in the
Release Bulletin that accompanies the software. However note that installation should
already have been completed to support the Piping Cats and Specs Alignment IBP.
c. Configuration
Configuration requirements are described in the appendix entitled “VPD / VPRM Piping
Integration”.
Isodraft is used in the conventional manner, either interactively or in batch mode.
The PDMS Batch Macro facility in PDMS allows the Isometric MTO extraction to be run as a
background task, which can be run at a later off-peak time. To produce the batch macro
instead of an Isometric the user in PDMS Isodraft must set the “Produce” option button on
the Standard Isometric form. When the user selects Batch macro and clicks on the Apply
button on the Standard Isometric form, the Batch Macro form appears, which enables the
user to specify the macro filename. The macro file lists all the Pipes to be detailed together
with a call to the selected options file and batch PML function. The file does not include the
system commands to submit a batch job, nor does it include the commands to enter the
PDMS project or set-up the PDMS environment. See example below:
Isodraft
options default
$M/%SAMISO%/STD/VPRM.MET
call !!vprmbatchprocess('0','/100-B-1')
detail PIPE /100-B-1
monitor
$
Note that if using the Fabrication Database then the Material List option “Spool Numbers
from Database” must be used.
e. Data Processing
See the appendix entitled “VPD / VPRM Piping Integration”.
The MTO produced is “Sectioned”, “Actual” MTO.
See the appendix entitled “VPD / VPRM Piping Integration”.

1. PDMS Modelling Conventions
This IBP relies on various conventions being followed when modelling the pipe work in
PDMS. These conventions are detailed in the appendix entitled “VPD / VPRM Piping
Integration”.
2. MTO Updates
Within VPRM, imported MTO will update existing MTO based on a match of “Construction
Area” and “Process Line Number”. Note that MTO that already exists in VPRM will only be
superseded when the used manually identifies the line as being “Approved”, ie that all
sections for the Area/Line concerned have been received.

5.8 Instrument Hook-Up Material Take Off
5.8.1 Overview
The following diagram illustrates the integrated business process for producing instrument hook-
up material take off in VPRM from data derived from VPE.
VPRM
p1a) Maintain standard assemblies as
instrument hook-ups
VPE Workbench VPRM

i1
p2a) Assign hook-ups to instruments p3a) Import hook-up details
Instrument Hook-Up
p2b) Release / Delete instruments p3b) Produce hook-up MTO
Details
> Instrument Data Sheets, etc > MTO Reports, etc

1. VPRM: Maintain Instrument Hook-Ups as Standard Assemblies
2. VPE: Maintain Instrument Design Data
3. VPRM: Maintain Instrument Hook-Up MTO
• One interface:
1. VPE to VPRM: Instrument Hook-Up Details
5.8.2 Procedures
5.8.2.1 VPRM: Maintain Instrument Hook-Ups as Standard Assemblies

a. This IBP relies on a standard assembly being created in VPRM for each instrument hook-up
on the project. The standard assembly should have a name that is identical to the hook-up
number and contain the relevant material that will have already been identified in the VPRM
Material Catalogue.
5.8.2.2 VPE: Maintain Instrument Design Data

a. Hook-ups should be assigned to instruments in the conventional VPE manner.
b. Instruments are released and issued in the conventional VPE manner.
5.8.2.3 VPRM: Maintain Instrument Hook-Up MTO

a. As and when it is required to create / maintain instrument hook-up MTO in VPRM, the
following interface needs to be executed:
i1: Instrument Hook-Up Details
b. Generally speaking, no further MTO work should be required in VPRM; however, the user
may perform any manual adjustments required.

5.8.3 Interfaces
5.8.3.1 VPE to VPRM: Instrument Hook-Up Details

a. Purpose
To transfer instrument hook-up details from VPE to VPRM to enable a material take-off to be
performed and subsequently to ensure efficient requisitioning and purchasing procedures for
Instrument Hook-ups.
b. Installation
required.
c. Configuration
VPE
Before hook-ups can be allocated to instruments, a Drawing Type needs to be created to
identify all Hook-up Drawings. Additionally, all hook-up drawings need to be registered in
the Document List.
VPRM
MTO requires assigning to a construction area which VPE cannot usually supply. The user
has two options:
• Identify a default Construction Area is to be used for all hook-up MTO units prior to
interface execution. This is set using the following screen:
VPRM>GMTO>Screens>Project Parameters
• Do not identify a default Construction Area - as a consequence a VPRM Construction
Area will be used that is the process area defined in VPE against the Instrument. If the
VPE process area does not exist in VPRM as a construction area then the interface will
create it.
The interface is executed from VPRM using the following screen:
VPRM>GMTO>Screens>Interface>VPRM Interface
The ‘Full’ option processes hook-up MTO for all instruments that have been released
and deleted, while the ‘Partial’ option processed only those instruments that have been
released and deleted since the last time a transfer took place or for which hook-up
details have been changed.
e. Data Processing
Providing the hook-up/s concerned exist as a standard assembly in VPRM, an MTO unit is
created for each instrument named HU-Tag_number containing the relevant material derived
from the standard assembly/ies concerned
The construction area is assigned to the MTO unit based on the configuration decision (see
above).
Where more than one hook-up has been assigned to the same instrument in VPE, only one
MTO unit will be created in VPRM, however, materials for both hook-up assemblies will be
listed in the MTO unit.

If the Process Area or the P&ID number assigned to the instrument in VPE is amended (and
a hook-up has been allocated to the item) then the MTO unit in VPRM will be amended
accordingly.
If a hook-up is deleted from an Instrument or the Instrument is deleted in VPE and the MTO
unit already exists in VPRM, the MTO unit will not be deleted although the quantity of the
materials will be set to zero.
• Automatically populated with details as and when the relevant engineering objects are
released and deleted in VPE. The information for each specification is time stamped
which is how VPRM recognises changed data when a ‘Partial’ transfer is executed.

6. APPENDICES
6.1 Integrated Business Processes Detail

1. P&ID / Design Integrity Key
VPE P&ID: Produce P&IDs Product
VANTAGE PE VANTAGE PD VANTAGE PRM
p1a) Draft P&IDs Activity
p1b) Save P&ID data to Plant
Connectivity Model (Save to Model) Key VANTAGE PE VANTAGE PD VANTAGE PRM
p1c) Check PCM integrity (Resolve i1 Outputs
Differences) P&ID Data
Dataflow Workflow
> P&IDs Flows
VPE Workbench: Issue P&ID Data Interface Data Interface Data

Interfaces (database to database) (via data file)
p2a) Add process lines and eng'd
items not derived from P&ID
p2b) Maintain process line and
engineered item design data
p3a) Release / delete process lines
and engineered items i2
Released Design Data
> Equipment List, Instrument

Index, Process Line List, etc
2. Engineered Item Requisitioning & Procurement

VPE Workbench VPRM
p1b) Continue to maintain engineered i1 p1a) Set-up and maintain Material
item design data including assigning Eng'd Item Material Requisition Identifiers (MR-Ids)
MR-Ids to engineered items Requsition Identifiers
VPE Workbench VPRM

i2
p2a) Release / Delete engineered p2b) Maintain Engineered Item List
Engineered Item
items
Design Details

VPE Workbench VPRM

i3
p3c) Maintain requisition and p3a) Requisition engineered items
Engineered Item
purchase order data p3b) Procure engineered items
Requisition & PO Data
p3d) View / report engineered item
requisition and purchase order data
> Engineered Item Requisitions
and Purchase Orders, etc
3. Piping Cats & Specs Alignment PDMS VPRM

p1a) Maintain catalogue i1 p1c) Import CATREF Mask details
p1b) Export CATREF Mask details PDMS CATREF p1d) Map VPRM and PDMS
Masks catalogues
VPE Workbench VPRM

p2a) Continue to maintain process line i2 p2c) Import Pipe Specification
design data Pipe Specification Summary
p2b) Release / Delete process lines Summary Details

PDMS VPRM
p3b) Import catalogue data & specs p3a) Develop and approve specs
i3) Cats & Specs Data
> Pipe Specifications

4. Piping P&ID Material Take Off

VPE Workbench VPRM
p1a) Continue to maintain process line p2a) Maintain Process Line List
design data i1
VPRM
> Process Line List, etc p3a) Produce P&ID MTO
> MTO Reports, etc
5. Design / Layout Integrity

VPE Workbench VPD Model Management
p1a) Assign PDMS refs to P&ID items i1 1) Build lines and equipment
Line / Eng'd Item Data
VPD PDMS
1) Develop 3D Model
VPD Model Management

1) Check P&ID/3D model integrity
6. Piping Bulk Material Take Off

VPE Workbench VPRM

VPD PDMS VPRM
p2a) Continue to develop 3D Model i2 p2c) Import piping bulk MTO
p2b) Generate piping bulk MTO Piping Bulk MTO p2d) Produce intermediate MTO
> General Arrangements, etc > MTO Reports, etc
7. Piping Isometric Material Take Off

VPE Workbench VPRM

VPD PDMS VPRM
p2a) Continue to develop 3D Model i2 p2c) Import piping isometric MTO
p2b) Generate piping isometrics Piping Isometric MTO p2d) Produce final MTO
> Piping Isometrics, etc > MTO Reports, etc
8. Instrument Hook-Up Material Take Off VPRM

p1a) Maintain standard assemblies as
instrument hook-ups
VPE Workbench VPRM

i1
p2a) Assign hook-ups to instruments p3a) Import hook-up details
Instrument Hook-Up
p2b) Release / Delete instruments p3b) Produce hook-up MTO
Details
> Instrument Data Sheets, etc > MTO Reports, etc

6.2 VPE P&ID & VPE Workbench Configuration
6.2.1 ‘Local’
Mapped Drive Project IPE001 Apps .

‘Load’ Files
X:\...[this machine] mapped to AutoCAD
D:\...[this machine] Microstation
Data Drawings Files
Files
TNSNAMES.ora
TNSNAMES.ora
VPE.ini
Database Server Web Server VPE.ini
Oracle 8.1.7 (Middle Tier) Local Machine
Ethernet
Remote Host
Ethernet
TNSNAMES.ora TNSNAMES.ora
VPE.ini VPE.ini
Apps . Local Machine Laptop Computer Apps.

AutoCAD Project IPE001 Files: Project IPE001 AutoCAD
‘Load’ Files pjc.x509 ‘Load’ Files
Microstation Microstation
Drawings Apps.: Drawings
Oracle Runtime 7.3 [Oracle client/server]
JInitiator 1.1.8 [Oracle web client]
Registry:
…\HKEY_LOCAL_MACHINE\SOFTWARE\\CADCENTRE LTD\VANTAGE VANTAGE_CONFIG = [location of Vantage .ini file]
…\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE TNSADMIN = location of TNSNAMES.ora file
Mapped Drive
X:\ [this machine] mapped to X:\ [web server]
URL
http:// [location of the web server connection to the project database]
TNSNAMES.ora
For the project database - Host = [the database server name]
Local ‘clients’

6.2.2 ‘Shared’
Project IPE001 Mapped Drive

‘Load’ Files X:\...[this machine] mapped to
D:\...[this machine] Apps.
Data AutoCAD
Drawings Files
TNSNAMES.ora Microstation
Database Server Web Server VPE.ini
Local Machine
Oracle 8.1.7 (Middle Tier)
Ethernet
Remote Host
Ethernet
TNSNAMES.ora TNSNAMES.ora
VPE.ini VPE.ini
Apps. Files: Laptop Computer Apps.

Local Machine
AutoCAD pjc.x509 AutoCAD
Microstation Microstation
Apps.:
Oracle Runtime [Oracle client/server]
JInitiator [Oracle web client]
Registry:
…\HKEY_LOCAL_MACHINE\SOFTWARE\\CADCENTRE LTD\VANTAGE VANTAGE_CONFIG = [location of Vantage .ini file]
…\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE TNSADMIN = location of TNSNAMES.ora file
Mapped Drive
X:\ [this machine] mapped to X:\ [web server]
URL
http:// [location of the web server connection to the project database]
TNSNAMES.ora
For the project database - Host = [the database server name]
Local ‘Clients’

6.3 VPD / VPRM Piping Integration

For the piping discipline, VPD and VPRM have been designed to operate in an integrated
manner in terms of the following interfaces:
1. VPRM to PDMS: Catalogue and Specification Data
2. PDMS to VPRM: Bulk MTO
3. PDMS to VPRM: Isometric MTO

6.3.1 Concepts
6.3.1.1 Catalogue and Specifications Alignment

a. Overview
This functionality relies on an association being maintained in the VPRM Material Catalogue
between VPRM material item references and equivalent references used by PDMS
Catalogues. This is referred to as “mapping”. Several PDMS Catalogues can be supported
from one VPRM Material Catalogue via the use of separate “PDMS Instances”.
When created, a VPRM part number is associated with a CATREF, the PDMS equivalent to
a VPRM Part Number. A CATREF is defined by a GTYPE and a Selector Set. A GTYPE is
an identifier for a generic group of components. A Selector Set is an associated group of
selectors, ie attributes of a CATREF. Finally, a Symbol Key (Skey) is associated with the
GTYPE to identify the drawing symbol that will be used on PDMS Isometric drawings to
represent the CATREF. Selectors, Symbol Keys by Gtype, and Selectors by Gtype are
supplied with the VPRM product. CATREFs can be imported into VPRM.
VPRM is then used to generate PDMS pipe specifications and supporting catalogue data at
the same time that pipe specifications are generated for VPRM P&ID MTO purposes. The
data is generated in the form of macro text files that are then imported into PDMS.
VPRM caters for both “old” and “new” bolting functionality within PDMS.
Up to four macro text files are generated:
File Content File Name PDMS Module

Specification Details project_spec_rev_yymmddhhmmss.txt Specon
Component Description Details project_paragon_yymmddhhmmss.txt Paragon
Bolt Details project_bollist_yymmddhhmmss.txt Paragon
Component Weight Details project_Propcon_yymmddhhmmss.txt Propcon
In the file name:
project = VPRM Project Number
spec = VPRM pipe specification name
rev = Pipe specification revision number
yymmddhhmmss = date/ time stamp.
Note that:
1. Specification details are always transferred in full. If the specification already exists in
PDMS, its components are transferred to the limbo spec first. This arrangement enables
transfer of particular revisions of a specification to be skipped, if required.
2. Part number descriptions and bolt details for the specification are automatically
transferred and update previously transferred data, if any exists.
3. To prevent frequent truncation of VPRM part number descriptions on transfer to PDMS,
the first 119 characters are held in HDTE-RTEXT, and the next 119 characters are
passed to HMTE-XTEXT.
4. The generation of the component weight details file is optional based on VPRM
configuration.
b. PDMS SPREFs
VPRM generated SPREFs have the following format for components other than bolts:
/spec/partno:shortcode,pipesize1, pipesize2, pipesize3
where
spec = Pipe Specification Name
partno = VPRM Part Number - a unique component identifier

shortcode = VPRM Specification Short Code

pipesize1 = VPRM Specification Key Size 1
Pipesize1 and 2 are present for multi-size/end components only, eg tees.
A colon (:) delimiter is used following the part number to activate the conventional
PDMS facility for eliminating the remaining characters when outputting part numbers
on to the isometric bill of material.
Examples:
/A1A/PP00123:P,100
100 mm ns pipe with a VPRM part number of PP00123 and Short Code of P on
spec A1A
/C150/PT00123:T,100,50
100 mm ns x 50 mm ns tee with a VPRM part number of PT00123 and Short
Code of T on spec C150.
VPRM generated SPREFs have the following format for bolts:
/spec/commodity code:bolt dia in mm:shortcode,spec size
where
commodity code = VPRM Commodity Code
Examples:
/A1A/PNA1A1AJCAB7AA:19:B,200
/A1A/PNA1A1AJCAB7AA:16:B,100
c. PDMS Pipe Specification Maintenance
The IBP is designed with the intention that pipe specifications are maintained in PDMS only
via the interface with VPRM, ie there should be no need for any manipulation of pipe
specifications using standard PDMS functionality.
Furthermore, when MTO is subsequently transferred from PDMS to VPRM, the interface
checks that the part number on the isometric is the same as that which was generated by
VPRM by comparing it with the part number on the VPRM pipe specification using the Short
Code and Spec Key sizes.
6.3.1.2 Bulk MTO Interface

a. Overview
MTO can be generated for material management purposes at any time during the
development of the PDMS 3D model; this is designed specifically for maintaining pre-final
isometric (or “intermediate”) MTO in VPRM.
The interface is a PML application which when executed outputs an MTO text file with
content and format that enables easy import to VPRM.
Currently, it does not cater for bolting MTO.
b. SPREF Format
The Bulk MTO IBP relies on the SPREF being in the format generated by VPRM when
producing pipe specifications.
6.3.1.3 Isometric MTO Interface

a. Overview
MTO is generated for materials management purposes at the time of isometric production;
this has been designed specifically for maintaining isometric (or “final”) MTO in VPRM.

The interface is supplied as an overlay release to the standard PDMS applications such that
when isometrics are produced using Isodraft, the bill of material includes VPRM-sourced
part numbers and descriptions and an MTO text file is output with content and format that
enables easy import to VPRM.
It is a set of applicationware and software. The applicationware enables configuration of the
interface and the software modifies the intermediate data file passed to Isodraw. It ensures
that the isometric bill of material and VPRM MTO File produced are consistent. The MTO
file has content and format that allows easy import to VPRM. The diagram below shows the
interface methodology.
PDMS IsoDraft
Initial
Intermediate Data File
VPRM
PDMS IsoDraw
+ Interface
Bolt Client Part Number

Data File Data File
PDMS Final
Material Control File Isometric Intermediate Data File
Drawings
VPRM MTO File
Following installation and configuration, the interface executes automatically as Isodraft is

used to produce isometrics.
During execution, the interface needs to access VPRM data in order to include bolt part
numbers and client part numbers (if relevant to the project) on the isometric bill of material.
VPRM access for bolt part numbers is required as a result of PDMS calculating bolt lengths
during isometric production that are fundamental in determining the VPRM part number for
the bolts which cannot be pre-determined on the pipe specification.
The Client Part Number (CPN) functionality enables CPNs to be maintained in VPRM only
and substituted in place of VPRM part numbers at the last possible moment, ie as isometrics
are being produced. (Alternatively, VPRM can be requested to generate PDMS
specifications with CPNs in place of VPRM part numbers – this is not recommended as it
requires PDMS specifications to be re-produced whenever CPNs are updated.)
Access to VPRM data can be achieved by direct access to the VPRM database (preferred)
and/or access to data files containing the relevant data. The method of access is defined
when the interface is configured. The use of VPRM data files enables the interface to
operate successfully in cases where the VPRM Database is not accessible (either
temporarily due to system failure or permanently, for example if PDMS is being run at the
construction site and a link to the VPRM database is not practical).
The data files required are a standard VPRM output.

The bolt data file produced contains records for all bolts in the material catalogue used by
the project in the following format:
VPRM Part No:Commodity Code:Diameter:Bolt Length
The client part number data file produced contains any VPRM part number referenced by an
approved specification and its associated client part number in the format:
VPRM Part No:Client Part No
If no bolt part number is found then the VPRM Commodity Code is used for the present and
the appropriate corrective action needs to be taken prior to re-processing the isometric.
If no client part number has been specified, then the VPRM part number (prefixed with “*!?”)
is used for the present and the appropriate corrective action needs to be taken prior to re-
processing the isometric.
The modified final intermediate data file (including the substituted part numbers) can be
produced if required.
b. SPREF Format
The Isometric MTO IBP works best if the SPREF is in the format generated by VPRM when
producing pipe specifications. However, it is also designed to work with projects where the
PDMS pipe specifications are not in the format that VPRM produces and use a size-
independent part numbering system. Refer to the section below entitled “Generating MTO
on PDMS Projects with non-VPRM Specifications”.

6.3.2 VPRM Configuration
6.3.2.1 Material Catalogue

The VPRM Material Catalogue can support more than one PDMS Catalogue. So if several
projects are being executed with different PDMS Catalogues then the mapping of VPRM and
PDMS items can be maintained in the same VPRM Material Catalogue.
This is achieved by defining the mapping for each PDMS Catalogue within separate PDMS
“Instances” defined within the VPRM Material Catalogue via screen:
VPRM>MCAT>Administration>3D Modeller Instances.
6.3.2.2 Specification Production

It is necessary to configure VPRM project for PDMS integration purposes. This is undertaken
by using screen:
VPRM>SPEC>Screens>Reference Data>Project Parameters
This screen is also used to specify:
• The VPRM Material Catalogue PDMS Instance being used
• The version of PDMS being used (if the version being used is not found in the List of Values,
then use the latest shown)
• Whether the project requires weights to be transferred to PDMS
• Whether the PDMS project is using “New Bolting”.

6.3.3 PDMS Configuration
6.3.3.1 PDMS Project Number

Before PDMS Piping Bulk and Isometric MTO Interfaces can be used, the PDMS Project
Number must be identical to the VPRM Project Number. This is set by using the following form:
PDMS>ADMIN>Project Information form
To change Project Number, the user selects Number from the option list on the Set Attributes
section of the form.
6.3.3.2 Managing Bolts

In both VPRM and PDMS, bolts are managed for a pipe specification as standard components.
However, for PDMS there is a centralised Standard Bolt List that is common to all specifications.
The list is used to associate a 'Single-Bolt' (SBOL) identity with external attributes of Length and
Diameter, and Quantity per flange as detailed in the VPRM-generated Bolt Table.
The SBOL refers to a Dimension Table, held in PDMS. The Dimension Table details the
available lengths for particular bolt diameters. If the dimension table names are of the form
'DIA-n-IMPERIAL-LENGTHS' or 'DIA-n-METRIC', in which 'n' is the bolt diameter, bolt detail
macros are generated without user intervention. However, if the tables have other names, a
cross-reference to the appropriate table must be specified by the user for each bolt diameter.
Details within the PDMS Standard Bolt List are created and maintained by VPRM. The
Dimension Table is solely a PDMS function and it cannot be updated from VPRM. When there
is a difference in the naming convention used either in VPRM or PDMS, eg VPRM Dimension
Table named = 'DIA-M20-METRIC' and the PDMS Catalogue uses a table named M20, the
interface will fail. The recommendation to ensure compatibility is to copy or rename the PDMS
table to the VPRM Dimension Table named.
6.3.3.3 Pipe Specification Attributes

For Pipe Specifications to be loaded into PDMS the interface uses the three user-defined
attributes to store VPRM-generated pipe specification data.
UDA Name UDA Description Example

Curr-spc-iss Current Pipe Specification A2
Issue
Input-by Input By VPRM at 23-DEC-2002 11:20
STATUS Current Pipe Specification APPROVED
Status
These UDAs need to be loaded into the PDMS project. A datal file is supplied with the
installation software and should be run into Lexicon. The file is called “PDMS-VPRM-udas.mac”
and can be found the “config_files” directory, eg “C:\AVEVA\PDMS_VPRM\ config_files”.
6.3.3.4 PDMS Option File Settings

In order to ensure that the PDMS and VPRM data are compatible, some of the PDMS options
file settings need to be overridden. Even if these settings are changed in the options file, the
VPRM interface software will reset them internally.
a. Isodraft Options
Mandatory settings of Isodraft options are:

ITEMCODE LENGTH LONG

This command passes the component specification reference to IsoDraft with the
specification name as a prefix of the SPREF. The MTO Interface removes these
prefixes before isometric drawings are produced.
BOLT LENGTH ITEM OFF
This command instructs Isodraft to display bolt lengths in the description column of
the material list.
BOLT LENGTH DESCRIPTION ON
This command instructs Isodraft not to show bolt lengths in the itemcode column of
the material list
DELIMITER ATSYMBOL
Isodraft displays component part numbers on the material list. Part numbers are
constructed from the characters of each component's SPREF that precede the
delimiter symbol (by default a colon). For example the SPREF PP0001:P,100 has the
part number PP0001.
In principal, Isodraft discards all characters that occur after the delimiter.
The MTO interface is designed to read the information that occurs after the delimiter.
So it requires that Isodraft does not discard the suffix characters. The interface
removes them, after it has extracted the data that it needs.
In order to ensure that Isodraft does not discard any suffix characters, the
DELIMITER command should be used to specify a delimiter character which will not
occur in the SPREF. DELIMITER ATSYMBOL would suit most situations.
Optional settings of Isodraft options are:
ISOTYPE NONE
Used for preliminary MTO when Isometric drawings are not required. i.e. MTO only.
MATCONTROL <filename>
Filename should be specified when MTO Export Files are required. Filename should
be left blank when MTO Export Files are not required.
INSTN <SPREF or NAME>
The MTO interface always identifies instruments on isometric material lists by their
Tag Name. When instruments are specified by SPREF (using the INSTN SPREF
command) Tag Names are displayed in the itemcode column of the material
list. When instruments are specified by Tag Name (using the INSTN NAME
command) Tag Names are appended to component descriptions and the itemcode
column is left blank.
b. File Renaming
A requirement for VPRM Isometric MTO production is that the pipe renaming option is
selected to maintain consistent spool numbering when re-producing isometrics.
c. Position Text Setting
In order to pass information to VPRM from PDMS, 'Position Text' Isodraft commands are
used to set seven strings to x0 y0. Setting their position to x0 y0 means they will not be
displayed on the isometric drawing. These mandatory setting are listed below:
Position Text String Value Obtained From….

PROJECT Project Number
AREA MTO Construction Area Attribute
LINE_NO Process Line Number Attribute

Position Text String Value Obtained From….

MTO_LINE_NO Name of Pipe
DWG_NO MTO Drawing Number Attribute
DWG_REV MTO Revision Number Attribute
REF_DWG MTO Piping General Arrangement Attribute
d. Detecting The Presence Of VPRM
In order for the PDMS/VPRM interface to be executed, the interface needs to detect the
presence of APPWARE text called VPRMMTO and VPRMMTODIR. These texts are
controlled by the “Reports and Symbol File” Option form.
• VPRMMTO must be set to “On” by checking the VPRM Material Takeoff check box.
• VPRMMTODIR defines the directory (folder) where the VPRM MTO file extracted as a
result of executing the interface will be placed. Completing the Directory field sets this.
e. Fixed Length Tube
It is sometimes desirable to produce MTO for fixed length components by total purchasable
length. Electrical cable trays, for example, are often purchased by total tray length and not
by numbers of the fixed length sections from which they are modelled. The Piping MTO
Interface provides a facility which instructs Isodraw to treat FTUB components as TUBE
components.
The following Isodraw macro command enables this facility:
POSITION 'FTUB = TUBE' AT X 0 Y 0
6.3.3.5 Pipe Attributes

Both interfaces rely on data from pipe attributes utilised in the PDMS design model. The user
has the choice on using System Attributes or User Defined Attributes (UDAs) to maintain this
data. The attributes concerned are:
Description System Requirement Comment

Attribute
MTO Status Not Optional Used for information purposes only
available
MTO Farea Mandatory Should be a valid VPRM construction area
Construction
Area
Process Line Fpline Mandatory Should be a valid VPRM process line number,
Number ie must be in the same format as used by
VPRM
MTO Fdrawing Optional Used for information purposes only
Drawing
Number
MTO Frevision Optional Used for information purposes only
Revision
Number
MTO Piping Frdrawing Optional Used for information purposes only
General
Arrangement

As can be seen, there are two mandatory attributes. Note that their values do not have to pre-
exist in VPRM as there is an option when importing the PDMS MTO into VPRM to create them
automatically. However, following this practice will result in a loss of data integrity as the
VANTAGE IPE solution assumes:
• VPRM is the source for valid construction areas
• VPE or VPRM is the source for valid process line numbers
Failure to conform to these principles may result in duplicated MTO in VPRM that needs to be
addressed manually.

6.3.4 Interface Configuration

Both MTO interfaces need to be configured by defining which pipe attributes are being used to
supply data the interface requires.
Additionally, the Isometric MTO Interface needs to be configured to define the options by which
the interface will execute.
Both the attributes and options to be used are set-up in a configuration file via the form:
PDMS>Isodraft>Options>VPRM>VPRM Option Editor
To use this form, the user must be a member of the ISOADMIN Team.
The form comprises a set of fields and several buttons as described below:
Field or Button Comments

Code Suffix Delimiter This is the part number delimiter used within the PDMS SPCOM.
On the assumption that the PDMS specifications have been
produced by VPRM, this should be set to a colon (:).
Bolt Diameter Units Set to metric or imperial as required for the project.
When performing a lookup of bolt part numbers, the interface
compares PDMS and VPRM bolt lengths and diameters. The
interface's working units are whole values of millimetres (irrespective
of the units being used in PDMS). VPRM values need to be
multiplied by conversion factors and are then rounded to the nearest
integer for the purpose of comparison with PDMS values. The
standard VPRM Material Catalogue (MCATMAST) has been set up
with Bolt diameter values in 1/10ths mm and lengths in mm. Thus
entering metric or imperial will result in the following factors being
used:
Metric
Bolt Diameter Factor = 0.1
Bolt Length Factor = 1
Imperial
Bolt Diameter Factor = 0.062992125
Bolt Length Factor = 0.62992125
Bolt Length Units Set to metric or imperial as required for the project.
Shop Delivery Code The VPRM fabrication shop delivery designation code which is
equivalent to a PDMS Shop Flag set to “True” - usually “1”.
Field Delivery Code The VPRM field delivery designation code which is equivalent to a
PDMS Shop Flag set to “False” - usually “3”.
Pulling Allowance The interface can calculate a pulling allowance to pipe length
associated with pulled bends. This allowance is specified as a
percentage of actual length (eg 7.5%). It is added to the pipe length
in the Isometric BoM and MTO output file. The default is for no
allowance, ie 0.0.


VPRM Access Type The interface needs access to VPRM data in order to include part
numbers for bolts and client part numbers (if relevant to the project)
on the isometric BoM. Access to VPRM can be achieved by either
direct access to the VPRM database or access to text files containing
the relevant data. This option is used to specify the access method:
DB = VPRM database only (ie if the VPRM database is not
available then the interface will fail)
FILE = Text files
AUTO = First tries to access the VPRM database; if it is not
available then the text files will be used
VPRM Username Set to the VPRM Oracle Login Username to be used when
communicating with the VPRM database (Material Catalogue)
VPRM Password Set to the VPRM Oracle Login Password to be used when
communicating with the VPRM database (Material Catalogue)
VPRM Database Set to the VPRM Database Name in terms of the SQL*Net
Servicename.
Bolt Lookup Table The interface needs access to VPRM data in order to include part
numbers for bolts and client part numbers (if relevant to the project)
on the isometric BoM. Access to VPRM can be achieved by either
direct access to the VPRM database or access to text files containing
the relevant data. This option is used to specify the path name for
the bolt data text file. References to environment variables should be
enclosed by percent (%) characters. Example:
%HOME%/bolt_parts.tbl
Client Part No Table This option is used to specify the path name for the client part
number data text file. References to environment variables should be
enclosed by percent (%) characters. Example:
%HOME%/client_parts.tbl
Bolt Diameter EFT Usually, set to “%diam%” - interpreted as “Bolt Diameter”.
This setting supports the bolt part number lookup routine. Within the
VPRM Material Catalogue, as a general rule, bolts have two external
features (EFTs) - diameter and length. EFTs can be given any
description by the user. The standard VPRM Material Catalogue
(MCATMAST) has been set up as follows:
EFT description for bolt diameters: "Bolt Diameter"
EFT description for bolt lengths: "Length-Short"
If these EFT descriptions are changed, then set as a lower case
representation of the new description.
Bolt Length EFT Usually, set to “%length%” - interpreted as “Length-Short”.
Client Part Number Set to “VPRM” if standard VPRM part numbers are required for
Source components other than bolts on the isometric bill of material
Set to “Client” if VPRM client part numbers are required for
components other than bolts on the isometric bill of material


Client bolt number Set to “VPRM” if standard VPRM part numbers are required for bolts
source on the isometric bill of material
Set to “Client” if VPRM client part numbers are required for bolts on
the isometric bill of material
Export C of G Check the check box to output centre of gravity coordinates for each
individual component into the VPRM transfer file - usually only
required on modular projects where VPRM is being used to support
weight control software
Consolidated MTO Check the check box to consolidate all like-components into single
records with a multi-quantity within the VPRM MTO transfer file - this
option is only available if the “Export C of G” check box is unchecked
Debug Check the check box to create a debug file in the user’s working
directory – for use during error investigation only
Export Spools Check the checkbox if field spool items are required in the VPRM
MTO transfer file, ie if it is required to control spools from a materials
management aspect in VPRM.
The spool will be identified within VPRM with a part number of
“XS00001” and a tag number of the relevant element name suffixed
by a hyphen and the spool number (or the spool name if the Material
List Option “Spool Numbers from Database” has been used)
Standard Project Check the check box if PDMS is using VPRM generated
specifications.
The interface has also been designed to work in cases where the
PDMS pipe specifications are not in the format that VPRM produces
and use a size-independent part numbering system – refer to
Appendix 6.4.3 for more details
Save Transfer File Check the check box if there is a requirement to save the final
Intermediate Date File (transfer file) which will include Client or Bolt
Part Number substitution. The text file is named as the MTO file with
“-IDF” appended, eg CWS-1001-01_mto-IDF.
Access Override If the VPRM database or files cannot be accessed during a run, the
application will abort with an error.
Check the check box, if there is a requirement to ignore this problem
(should it arise) and continue without any communication with VPRM.
Attributes This button calls another form named:
VPRM Pipe Attributes
This form allows the user to select the PDMS pipe attributes (PDMS
System attributes or UDAs) from which data will be accessed.
The functionality provided enables the user to use:
- PDMS standard attributes
- Or, default UDAs as provided with the interface software
- Or, alternative UDAs that the PDMS user has already set up.
Test DB Access This button will test access to the VPRM database, using the VPRM
database/username and password stored within the form.

6.3.5 PDMS Design Procedures
6.3.5.1 Design Database

Naming Conventions
This section describes the key issues to be considered in naming pipes and the mandatory
attributes in order for the MTO interfaces to operate successfully:
• Each pipe must have an attribute of process line number (ie the line number shown on the
P&ID and Process Line List).
• Each pipe must have an attribute of construction area
• There are likely to be many pipes with the same process line number and such pipes may
exist in different databases.
• Pipe Names must be unique.
The following diagram illustrates a potential naming convention where a process line passes
through two areas. Note that:
• The pipe name comprises the process line number suffixed by the construction area number
in order to maintain uniqueness
• The process line number which VPRM requires (System Attribute Fpline) is not necessarily
in the same format as the process line as labelled on the P&ID).
Construction Area A1 Construction Area A2

Process Line 100-MD-1001-A3B
Sheet / Section 1 Sheet / Section 2 Sheet / Section 1 Sheet / Section 2
Pipe Name: 100-MD-1001-A3B-A1 Pipe Name: 100-MD-1001-A3B-A2

Process Line (Fpline): MD-1001 Process Line (Fpline): MD-1001
Construction Area (Farea): A1 Construction Area (Farea): A2
Split Atta’s
The Isometric MTO Interface is unable to identify component distribution across isometric
sheets that have been split automatically by Isodraft. The interface has a restriction that
multiple sheets must be split by permanent database Split Atta's. The interface exits with an
error when automatic split points are encountered.
There is one exception to this. The interface does allow sheet splits across closed loops when
only one leg has a defined split point (see diagram).
The interface attempts to identify the location of the calculated split point. If it fails, a
consolidated MTO is exported (components not itemised individually) without Centre Of Gravity

information, and a warning message is written to the log file. The error condition can be
eliminated by ensuring that Split Atta’s are defined for both legs of the loop.
6.3.5.2 Fabrication Database

When using the fabrication database, the Spool Drawing Name can be made unique by
appending the Construction Area and Spool Drawing Number to the Process Line Number as
illustrated below. Additionally, the attributes required by the VPRM Interface (eg Farea and
Fpline) must be attributes for both the pipe and the spool drawing.
Note that when using the VPRM Isometric Interface, a spool drawing may contain a whole
process line or part of a process line; it may not contain parts of different process lines.
Construction Area A1 Construction Area A2
Process Line 100-MD-1001-A3B
Spool 1 Spool 2 Spool 1 Spool 2 Spool 1 Spool 2 Spool 1 Spool 2
Spool Drawing 1 Spool Drawing 2 Spool Drawing 1 Spool Drawing 2
Pipe Name: 100-MD-1001-A3B-A1 Pipe Name: 100-MD-1001-A3B-A2

Process Line (Fpline): MD-1001 Process Line (Fpline): MD-1001
Construction Area (Farea): A1 Construction Area (Farea): A2
Spldwg Name: 100-MD-1001-A3B-A1(1) Spldwg Name: 100-MD-1001-A3B-A1(2) Spldwg Name: 100-MD-1001-A3B-A2(1) Spldwg Name: 100-MD-1001-A3B-A2(2)
Process Line (Fpline): MD-1001 Process Line (Fpline): MD-1001 Process Line (Fpline): MD-1001 Process Line (Fpline): MD-1001
Construction Area (Farea): A1 Construction Area (Farea): A1 Construction Area (Farea): A2 Construction Area (Farea): A2
6.3.5.3 Tagged / Named Items

In order for tagged items to be successfully transferred from PDMS to VPRM via the Bulk and
Actual MTO interfaces, the PDMS designer must ‘name’ the item with the tag number required.
The interface software allows suffix characters to be appended to a ‘name’ after the delimiter
symbol (:). This permits tagged items to hold unique ‘names’ in cases where there is a
requirement for repeated tag numbers. The interface software discards the suffix characters
when writing to the VPRM MTO transfer file.
Example: Items ‘named’ in PDMS as ‘SPP001:A’ ‘SPP001:B’, will be output to VPRM as
‘SPP001’, quantity 2 off.
It should be noted that VPRM is designed to allow repeated items for bulk material only, That is,
items on VPRM’ Process Tag List must be ‘one-off’. If in doubt, this should be discussed
between the relevant PDMS and VPRM personnel.
The method by which tags are output from PDMS to the MTO transfer file is dependent on how
the specification via which the item is accessed, has been written. There are two alternatives.
1. SPREF is in VPRM format
This situation usually applies to bulk material where the specification has been produced by
VPRM.
A tagged item that has been ‘named’ in PDMS will be transferred to VPRM with the tag
number plus the same information as for any other bulk material item (ie VPRM specification
reference and part number.)
2. SPREF is not in VPRM format
This situation usually applies to engineered items, for example, instruments and piping
specials, where the specification has not been produced by VPRM.
In this case, the spref / spcom must not conform to the standard spref as generated by the
VPRM/PDMS specification interface. That is, it must not contain both a colon(:) and one or
more commas(,). Thus, the following example, which represents the standard format for a

spref generated by VPRM, cannot be used as the spref on, for example, a PDMS-generated
specification for instrument items:
Xxx:yyy,zzz where xxx, yyy and zzz are any text.
Note: Any specification element that is created in PDMS only, and not generated within
VPRM, should be locked within the PDMS database. If they are not locked, the VPRM to
PDMS transfer of the specification will leave these items in limbospec, and the user will be
required to manually enter them into the specification.
Finally, it should be noted that the identification of tagged items must be totally consistent in
PDMS and VPRM in order that VPRM’s material management facilities can operate
effectively and accurately. For example, the identification of the tagged item for ordering
purposes in VPRM must be consistent with the information received from PDMS regarding
its requirement on an isometric. In more detail:
• The tag numbers used in both systems must be identical
• VPRM requires all tagged items to have a part number – the PDMS designer can ignore
this requirement - the interface software has been designed to ensure the correct part
number is assigned on processing the PDMS/VPRM interface MTO transfer file into
VPRM.

6.3.6 Generating MTO on PDMS Projects with non-VPRM Specifications

a. Introduction
This topic describes the working procedures related to the use of VPRM and the PDMS-to-
VPRM Interface for Isometric MTO when working on ‘non-standard’ PDMS Projects.
A 'non-standard' PDMS Project is one where the PDMS pipe specifications are not in the
format that VPRM produces and use a size-independent part numbering system
b. VPRM Pipe specifications
This section is applicable if the Project has a requirement to undertake preliminary MTO
utilising VPRM pipe specifications. If this is not the case then the Project merely needs to
register the relevant pipe specifications in VPRM.
In VPRM, create pipe specifications in the conventional manner for MTO purposes (ignoring
the facilities to generate PDMS specifications) equivalent to the specifications being used in
PDMS. This may involve the creation of new VPRM Part Numbers, etc in the VPRM Material
Catalogue.
c. VPRM Client Part Number Set
In the Material Catalogue, create a Client Part Number Set that will be used to enable:
• The batch processing of MTO transfer files produced by the PDMS-to-VPRM Isometric
MTO interface for non-standard PDMS Projects
• The production of VPRM reports (eg MR and PO Scopes of Supply) with Client Part
Numbers
• The display of Client Part Numbers on VPRM screens.
All Projects relevant to the client concerned must be set up to use this Client Part Number
Set.
In the Client Part Number Set, set up equivalencies between VPRM and Client Part
Numbers using the conventional VPRM facilities using the following rules for the format of
the Client Part Number:
Single Size Components
Append the size-independent part number (eg the DuPont Stock Code) with a hyphen
followed by a character representing the size (using the standard PDMS size code
references as detailed below).
For example, a single size component (eg flange) with stock code BVBJCCA and a
nominal size of 4" or 100mm will become a part number of BVBJCCA-M.
Two Size Component (Including Tees)
Append the size-independent part number with a hyphen followed by a character
representing the first size followed by a character representing the second size (using
the standard PDMS size code references as detailed below).
For example, a two size component (eg reducer) with stock code DJFBHAC and a
nominal sizes of 4" x 3" or 100mm x 80mm will become a part number of DJFBHAC-MK.
Bolts
Append the size-independent part number with a hyphen followed by the bolt diameter
followed by another hyphen followed by the bolt length. The bolt diameter and bolt
length should be in millimetres or sixteenths of inches depending on whether the Project
is using metric or imperial nominal sizes.
For example, on an imperial Project, a bolt stock code of JKDBDCA with a 1/2" diameter
and a length of 2.1/2" will become a part number of JKDBDCA-8-40.

Size Character Nominal Size Nominal Size

(Inches) (Millimetres)
A 1/8 6
B 1/4 8
C 3/8 10
D 1/2 15
E 3/4 20
F 1 25
G 1.1/4 32
H 1.1/2 40
I 2 50
J 2.1/2 65
K 3 80
L 3.1/2 90
M 4 100
N 5 125
O 6 150
P 8 200
Q 10 250
R 12 300
S 14 350
T 16 400
U 18 450
V 20 500
W 22 550
X 24 600
Y 26 650
Z 28 700
0 30 750
1 32 800
2 34 850
3 36 900
4 38 950

5 40 1000
6 42 1050
7 44 1100
8 46 1150
9 48 1200
d. PDMS to VPRM Isometric MTO Interface

This should be run having configured the interface with the ‘non-standard’ Project option.
Using this option results in size-independent part numbers and component size details being
included in the VPRM MTO transfer file.
e. Materials Management in VPRM
All materials management activities in VPRM (eg MTO, requisitions, purchase orders, etc)
can now be undertaken in the conventional manner noting that:
• Where available, screens can be set to display/enter Client Part Numbers by using the
Client Part Number display option
• Reports can be printed with Client Part Numbers using the Client Part Numbers option
on report request parameter screens.

6.3.7 VPRM MTO Text File Format

For information purposes, the format and content of the MTO text files generated by the Bulk
and Isometric MTO Interfaces is described below.
6.3.7.1 General
• Colon (:) delimited with asterisk (*) record terminator
• Record includes all colons and it is always terminated by asterisk
• If PDMS data is longer than VPRM maximum field then the interface will truncate to VPRM
length and issue a warning message to the user.
6.3.7.2 Record Types

$B Batch record One per file
$L Line record One or more per batch record
$S Section Record One or more per line record
$C Component Record One or more per section record
6.3.7.3 Batch Record Definition

Field Description VPRM PDMS Field Comments
Requirement Completion Definition
Record Type Indicator Mandatory Mandatory '$B' Always $B
Project Number Mandatory Mandatory 8C From project text “project number”
Source Mandatory Mandatory 8C Standard project - 'PDMS'
Non-std project - 'PDMS-X'
Interface Version Optional Mandatory 6C Version number of interface program
Date/Time Mandatory Mandatory 20C dd-mm-yy hh.mn.sc
Example: $B:6261:PDMS:1r0:22-Jul-99 13.45.52*
6.3.7.4 Line Record Definition

Record Type Indicator Mandatory Mandatory '$L' Always $L
Area Mandatory Mandatory 5C :MtoArea of pipe
Process Line Number Mandatory Mandatory 32C :MtoRef of pipe
Specification Number Mandatory Mandatory 10C PSPE of pipe
MTO Line Number Optional Mandatory 32C PDMS pipe name
Insulation Optional No 1C ISPE of pipe
Tracing Optional No 1C TSPE of pipe
Painting Optional No 1C PTSP of pipe
Routing ID Optional No 1C Description, e.g. underground
Example: $L:A01:CWS-1234:D1A:CWS-1234-01::::*

6.3.7.5 Section Record Definition

Record Type Indicator Mandatory Mandatory '$S' Always $S
Section Number Mandatory Mandatory 2N Always expanded to 2 chars using
preceding 0.
00 for MTO when ISOTYPE NONE is
specified.
Drawing Number Optional Optional 32C :MtoDrwg from pipe
Drawing Revision Optional Optional 4C
Number
Reference Drawing Optional Optional 32C
Number
COG Co-ordinate: E Optional No 11N
COG Co-ordinate: N Optional No 11N
COG Co-ordinate: EL Optional No 11N
Example: $S:01:6261-CWS-1234-01:C1::::*
6.3.7.6 Component Record Definition

Record Type Indicator Mandatory Mandatory '$C' Always $C
Spec Size 1 Optional Optional 6C Not completed for Bolts
Short Code Optional Optional 3C Not completed for Bolts
Macro + Facility Optional No 1C
Part Number or Optional Mandatory 16C For non-std project, contains size-
Client Part Number independent code (e.g. clients stock
code)
For spool, contains ZS0001
Tag Number Optional Optional 25C For spool, contains spool No
Quantity Mandatory Mandatory 11,2N Units for pipe:
Meters (metric),
feet (Imperial).
Units for other parts: 'No off'
Delivery Designation Mandatory Mandatory 1N '1' through '9' PDMS interface will
allow convert True/False to numbers
Spool Number Optional No 3C
Routing ID Optional No 1C Description, e.g. underground
Insulation Mandatory Mandatory 1C 'Y' or 'N'
Tracing Mandatory Mandatory 1C 'Y' or 'N'
Painting Mandatory Mandatory 1C Always 'N'
Reference Specification Optional No 10C Not completed for Bolts
Number Only specified if part spec if different
from line spec.


COG Co-ordinate: E Optional Optional 11N Bolt COG taken as gasket COG.
Units: Mm's (metric),
1/16" (imperial).
COG Co-ordinate: N Optional Optional 11N
COG Co-ordinate: EL Optional Optional 11N
Example: $C:4:2::T::PT123::3:1:::Y:N:N::9999999:9999999:9999999*

Integrated Project Execution Integrated Project Execution: User Guide

Uploaded by

Copyright:

Available Formats

You might also like

Integrated Project Execution Integrated Project Execution: User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Integrated Project Execution Integrated Project Execution: User Guide

Uploaded by

Copyright:

Available Formats

Integrated Project Execution

Ref: User Guide

AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS

 Copyright 2003 AVEVA Solutions Limited

Date Issue No Remarks

15-Jul-03 1.0 First Issue

vipe user doc.doc Page 3 of 73

4. INTEGRATED BUSINESS PROCESSES OVERVIEW ............................................................ 15

5. INTEGRATED BUSINESS PROCESSES DETAIL ................................................................... 19

vipe user doc.doc Page 4 of 73

vipe user doc.doc Page 5 of 73

5.7.4 Points to Note .............................................................................................................. 44

vipe user doc.doc Page 6 of 73

Process Dept Engineering Dept

vipe user doc.doc Page 7 of 73

• Many departments and personnel, eg

Sales VP Engineering VP Operations VP Finance VP

Engineering Project Controls Procurement Construction

Process Structural Planning Purchasing Fabrication

Piping Mechanical Cost Expediting Erection

Pipe Length 20,000 M

Engineering Documents 6,000

vipe user doc.doc Page 8 of 73

The base VANTAGE products are:

Project Controls Planning Design Progress Cost Management

Engineering Engineering Engineering Procurement Construction

P&IDs Piping Construction

Materials Management Planning and Monitoring

Project Management Executive Information (Decision Making Support)

vipe user doc.doc Page 9 of 73

Internal Product to Product External

1.2 Document Purpose

1.3 Document Organisation and Content

vipe user doc.doc Page 10 of 73

Section 4: Integrated Business Processes (IBPs) Overview

vipe user doc.doc Page 11 of 73

2.2 VPE P&ID

2.3 VPE and VPRM

vipe user doc.doc Page 12 of 73

2.4 Version Dependencies

vipe user doc.doc Page 13 of 73

3.2 VPE P&ID

3.3 VPE Workbench

vipe user doc.doc Page 14 of 73

4. INTEGRATED BUSINESS PROCESSES OVERVIEW

VPE VPE 2 VPD VPRM

VPD PDMS and

4.1 P&ID / Design Integrity

4.2 Engineered Item Requisitioning and Procurement

vipe user doc.doc Page 15 of 73

4.3 Piping Catalogue and Specifications Alignment

4.4 Piping P&ID Material Take Off (MTO)

vipe user doc.doc Page 16 of 73

4.5 Design / Layout Integrity

4.6 Piping Bulk Material Take Off

vipe user doc.doc Page 17 of 73

4.7 Piping Isometric Material Take Off

4.8 Instrument Hook-Up Material Take Off