Professional Documents
Culture Documents
Administrator User Guide
Administrator User Guide
Administrator User Guide
PLEASE NOTE:
AVEVA Solutions 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 to which you may not have
access or which may not be licensed to you. For further information on which Products
are licensed to you please refer to your licence conditions.
For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
Table of Contents
1
1.1
1.2
2.1
2.2
4.1
4.2
4.3
4.4
4.5
5
5.1
5.2
PDMS Isodraft Module............................................................................................................ 11
5.2.1
The VPRM Options Configuration File .............................................................................. 11
5.2.2
The Check for VPRM Access ............................................................................................ 14
5.2.3
The VPRM Menu Option ................................................................................................... 17
5.2.4
How to Enable VPRM MTO............................................................................................... 30
5.2.5
Isometric Production .......................................................................................................... 31
5.2.6
Output Files ....................................................................................................................... 31
5.3
PDMS Paragon Module .......................................................................................................... 32
5.3.1
VPRM CATREF Masks ..................................................................................................... 33
5.3.2
The File Loader Form ........................................................................................................ 34
5.4
PDMS Design Module ............................................................................................................. 46
5.4.1
The Bulk Mto Form ............................................................................................................ 46
5.5
All Modules .............................................................................................................................. 52
5.5.1
Spool Drawings ................................................................................................................. 52
5.5.2
Catalogue Management .................................................................................................... 52
5.5.3
Material Length Accuracy .................................................................................................. 54
5.5.4
Material List Position Numbers.......................................................................................... 54
5.5.5
Batch Mto File management ............................................................................................. 55
5.5.6
TUBE Weight transfer from VPRM to PDMS .................................................................... 56
5.5.7
Piping Support Lugs .......................................................................................................... 57
Chapter 2 explains some principles which you need to understand before you try
to use the PDMS-VPRM Administrator functions.
Chapter 3 describes the files that are supplied with and constitute this application
Chapter 4 describes what you need to organise before the application will run
satisfactorily
AVEVA Solutions
4/57
This chapter explains some general principles which you need to understand before you
try to carry out any administrative functions within the application. It explains:
Catref Alignment
Available from within the Paragon module, this provides a method by which existing
PDMS Catalogue Component Categories (CATE) are output for use by VPRM. These
are known within VPRM as CATREF Masks and will be used to generate the Catalogue
References (CATREF) within the specifications generated by VPRM.
AVEVA Solutions
5/57
Supplied Files
The PDMS-VPRM Interface consists of several utilities, PDMSUI and PMLLIB files.
By default these components are located in the following directory where n is the version
number.
C:\AVEVA\PDMS_VPRMn
In this directory reside the following folders:config
Non-STD_Bolts.dat
olet_dtse.dat
PartListTemplate.xls
PDMS-VPRM-udas.mac
pdsc01.cfg
READ ME.PDF
exe9
exe10
exe11
pdsc01.exe
pdsc02.exe
pdsc03.exe
pdmsui
pmllib
AVEVA Solutions
6/57
PDMS prerequisites
Before the interface will function correctly, you will need to carry out several tasks.
You will need to modify this file to include a call to the PDMS to VPRM Interface
environment batch file after the standard evars call as follows.
rem Set evars for PDMS
set pdms_installed_dir=C:\AVEVA\Plant\PDMS12.0.SP6\.
call "%pdms_installed_dir%\evars" "%pdms_installed_dir%"
rem Set PDMS-VPRM Gateway specifics
set pdms-vprm_installed_dir=C:\AVEVA\PDMS-VPRM5.2
call "%pdms-vprm_installed_dir%\PDMS-VPRM_evars.bat" %pdmsvprm_installed_dir%
Sample start-up files PDMS-VPRM_pdms.bat and PDMS-VPRM_evars.bat are
supplied in the PDMS-VPRM Gateway installation folder.
AVEVA Solutions
7/57
You should load these into a suitable LEXICON database which is accessible to all
potential users of the PDMS-VPRM interfaces.
AVEVA Solutions
8/57
CMPW /IPE001_PROPCON_CMPW
AVEVA Solutions
9/57
Once the PDMS VPRM Interface application has been loaded, the PDMS modules
MONITOR, DESIGN, ISODRAFT and PARAGON will have extended menu options that
provide the relevant application functionality for each.
The details of the functionality available and what happens as you enter each module is
discussed below.
Oracle 9i Client
Oracle10g Client
Oracle11g Client
The program is run whilst the user is in the process of producing an Isometric. For further
details of this see section 5.2 which discusses the PDMS Isodraft module.
Once the existence of this file has been verified, the PDMS-VPRM Interface sets a flag,
in the form of a global variable, to indicate that the application is active for this project
and is available throughout PDMS.
!!VprmExists = true
The successful setting of this flag gives application the ability to provide further menu
options and validity checks upon the entry to other PDMS modules.
ISODRAFT
DESIGN
These options and checks are further discussed in each of the relevant sections that
appear later in this guide.
AVEVA Solutions
10/57
AVEVA Solutions
11/57
pl_project_spec = Pspec
AVEVA Solutions
12/57
pl_iso_parts_list = IPL
pl_pre_inspection = Pre-Inspection
pl_site_inspection = Site-Inspection
pl_order_no = ORDERNO
pl_template = PartListTemplate.xls
pl_pdf_printer = Acrobat Distiller
pl_pdf_converter = acrodist.exe
pl_no_components = 13
pl_position_no_cell = A2
pl_quantity_cell = D2
pl_unit_weight_cell = G2
pl_part_cell = J2
pl_dimensions_cell = AH2
pl_material_cell = BB2
pl_design_code_cell = BN2
pl_design_code_rev_cell = BZ2
pl_total_weight_cell = G15
pl_project_cell = AY16
pl_project_spec_cell = BN16
pl_pre_inspection_cell = A17
pl_revision_cell = BU22
pl_date_cell = G17
pl_prepared_by_cell = M17
pl_order_no_cell = AY17
pl_safety_class_cell = BL17
pl_quality_class_cell = BW17
pl_site_inspection_cell = A21
pl_isometric_part_list_cell = BG21
pl_page_no_cell = CA21
pl_iso_pl_no_cell = BG22
pl_no_pages_cell = CA22
pl_angle_uda = ANGLE
pipe_rule =
hvac_rule =
tray_rule =
area_attribute = Description
check_option = SELECTION
atta_atty =
pdf_options =
vprm_mds_delete/rename = YES
vprm_mds_elec_delete/rename = YES
vprm_mds_hvac_delete/rename = YES
spool_mto_line = Spool Drawing Name
spool_prefix = Spool Drawing Name
pl_angle_text = Angle
pl_radius_text = Radius
pl_paper_size = A3
macro_short_code = F
part_list_lookup =
for_req_uda =
not_for_req_value =
for_con_uda =
not_for_con_value =
weight_uda =
suppress_spec = NO
AVEVA Solutions
13/57
For full descriptions of each setting refer to the Vantage Integrated Project Execution
User Guide, section 6.3.3 PDMS Configuration
For successful operation of the application, you should copy the configuration file on a
project by project basis into the project isometric directory, for example %XXXISO%,
where XXX is the three-letter project code.
If this copy does not exist, then the application will automatically copy it for you the first
time you enter the PDMS Isodraft module, during which you will receive the following
example message.
The VPRM configuration file does not exist. A new default file will be created in
the directory C:\AVEVA\Plant\PDMS12.0.SP6\project\XXXiso
Once the configuration settings have been loaded, the application then tests the settings
that relate to the VPRM database access.
A. DB
B. FILE
C. AUTO The application first attempts a direct DB access to extract the part
numbers, but if this fails then access by FILE will be attempted.
AVEVA Solutions
14/57
A. VPRM Access by DB
For direct access the VPRM database, some elements have to be in place.
1. Oracle 9 or Oracle 10 Client must be installed on the user workstation
2. The configuration file pdsc01.cfg must have valid entries for the VPRM
Username & Password and VPRM Database Name
3. The program used to process the isometric and extract the material for VPRM,
must be available. This is supplied with the application.
C:\AVEVA\PDMS_VPRMn\exe\pdsc01.exe
The purpose of this program is two fold.
To substitute PDMS part numbers for VPRM part numbers within the Bill
of Material on the actual Isometric drawing.
The production of a file for the transfer of the Isometric Material Take-Off
to the VPRM database.
As these items are so important to a successful transfer of material data to VPRM, the
VPRM database access is tested whenever you enter the PDMS Isodraft module (in a
PDMS project that has the PDMS VPRM Interface installed).
To carry out this test, another program is supplied as part of the application.
C:\AVEVA\PDMS_VPRMn\exe\dbtest.exe
This program is executed with two arguments, being an output file for the results of the
access test and the VPRM Options Configuration File that contains the access details.
Here is an example.
%PDMSEXE%\dbtest.exe %PDMSUSER%/junkfile.chk %XXXISO%\pdsc01.cfg
The program can return one of three valid values or blank.
0
1
2
Blank If the file is empty then the test failed completely. This will probably be due
to one of three things as follows.
The appropriate Oracle Client has not been installed. In this case
you are likely to receive the system error message The dynamic
link library sqllib80.dll could not be found in the specified path
The Oracle access files TNSNAMES.ORA and SQLNET.ORA do
not exist.
The Oracle access files exist but are not in the default directory
C:\oracle\ora81\network\admin. In this case a registry entry
HKLM>ORACLE>HOMEn>TNS_ADMIN must exist and indicate
the location of the files.
AVEVA Solutions
15/57
client_part_number_lookup
bolt_part_number_lookup
You can create these files from within VPRM SPEC module via the screen
Interfaces>PDMS Data Transfer
For more details on these VPM interfaces to PDMS, see the Vantage Integrated Project
Execution User Guide.
Once the VPRM database access has been verified, the PDMS VPRM Interface
application will extend the Isodraft menu bar to include the VPRM. See the section on
The VPRM Menu Option below for details.
AVEVA Solutions
16/57
AVEVA Solutions
17/57
When the form is displayed, the status bar will inform you of the result of the VPRM
Database access test that was carried out when you entered the Isodraft module.
To use this form, change the settings as required. The form title will change to include
the symbol * and the status bar will display Modified to indicate that the settings have
not yet been saved.
If you attempt to close the form when it has already been modified, you will receive the
following message.
Click on YES of you want to close the form and save the changes
Click on NO if you want to close the form and ignore the changes
Click on CANCEL if you want to abort the closure of the form
AVEVA Solutions
18/57
To set the location of the Bolt Look-up Table and Client Part Number Table, you can
enter the path and file name directly or you can Click on the
button. The standard
PDMS File Browser form will be displayed.
To change the directory, either type a new path in the Path text entry box or navigate
using the sub-directories pane. To move one level up from the current hierarchy position,
Click on the listed sub-directory that has the suffix .. as shown for example in the
diagram above.
To choose a file, select one from the Files list. Alternatively, you can type the required
file name in the Selection text entry box.
Press the OK button. The chosen filename will be placed into the relevant field of the
VPRM Options Editor form.
AVEVA Solutions
19/57
The result of this test will be output in the status bar at the bottom of the form.
Please note that you must have saved any modifications before the test is made.
AVEVA Solutions
20/57
To use this form, select the attribute name to be used for each attribute in the
corresponding drop-down options list. The title of the main VPRM Options Editor form
will change to include the symbol * to indicate that the settings have not yet been saved.
To exit the form, Click on the
button.
To save any changed settings, select the main form menu option File>Save.
Important Note: If you are setting the attributes to produce isometrics from the spool
drawing, at this release it is important that you select all attribute settings to use the User
Definable Attributes. This is because PDMS does not have the equivalent system
attributes at the SPLDRG element. If you attempt to mix system attributes and UDAs for
a spool drawing the isometric production process will fail.
AVEVA Solutions
21/57
Construction Area
The configuration area can be stored at either the PDMS PIPE or at any component. The
advantage of setting area at component is that you are then able to model pipes that
cross physical areas. It can however, be time consuming to set the attribute correctly at
each component. It is recommended that you utilise some suitable application to carry
out this task.
The component record in the batch file contains a field that transfers the area.
Example.
$C:150:::P::PP00024::0.250:1:::N:N:N:::::Y:Y:::B50*
There are some rules that relate to this.
If the construction area is unset at component level, the Mto unit will utilise the
construction area set at the Line.
If the component construction area value is different to that set at the Line,
then a new Mto unit will be created when the Batch Mto file is loaded into
VPRM version 9.6.
The head tube of any PDMS Branch will take its area from the relevant PIPE
attribute since it does not have an attribute in its own right. All leave tube will
use the attribute of the owning component.
To utilise area at component level, all components will require a suitable attribute. The
Gateway supplied lexicon file \PdmsVprm4.2\config\PDMS-VPRM-udas.mac includes
the sample attribute named :mtoArea set for all components element
AVEVA Solutions
22/57
INST
TRAP
VTWA
VENT
The relevance for VPRM is that the PDMS Item Code holds the Part Number, which
means that you have a choice in which number you would like to be transferred to
VPRM. You can choose either the Tag Number or the Part Number, by utilising the form
VPRM Tagging which is displayed when you select the menu option Options>Tagging
as shown below.
To use this form, select either the Tag Number or the Part Number for each component
type. The title of the main VPRM Options Editor form will change to include the symbol *
to indicate that the settings have not yet been saved.
To exit the form, Click on the
button.
To save any changed settings, select the main form menu option File>Save
AVEVA Solutions
23/57
Transfer Options
There are several options that relate to material data being exported to VPRM which can
be set by utilising the form VPRM Transfer Options which is displayed when you select
the menu option Options>Transfer as shown below.
AVEVA Solutions
24/57
To use this form, select set the relevant options as described below, during which time
the title of the main VPRM Options Editor form will change to include the symbol *
indicating that the settings have not yet been saved.
To exit the form, Click on the
button.
To save any changed settings, select the main form menu option File>Save
Using this form you can set the following options.
It is possible to automatically load the Batch and Final Mto files directly into
VPRM and you can specify if the files should be automatically deleted after the
transfer is complete.
The transfer of an Mto File is carried out using the executable pdsc02.exe.
Final Isometric MTO can be produced using the VANTAGE Plant Design
Deliverable Manager product. A configuration option allows you to choose
whether isometrics are produced using PDMS Isodraft or Deliverable Manager.
The diagram below shows the workflow.
AVEVA Solutions
25/57
Issue Isometric
VPRM
MTO
File
VPRM
Process
MTO File
You can transfer the data for a standard Pipe Support ATTA to VPRM
The configuration file contains three new options.
Allow support ATTA data to be transferred
The VPRM Part Number to be used for the support
The text used for the description can be either the ATTA attribute STEX
or the catalogue description text DTXR.
Any ATTA with the attribute ATTY unset, will be treated as any other tagged
item (unless it is a PDMS MDS support) in that it must be named in the format
that adheres to the naming convention example PS-001:A
The Batch Mto file will include a tag record as shown in the following example
$T:PS-0001::*
$C::::::ZA00001:PS-0001:1:1:::N:N:N::4524:2105:0:Y:Y:::*
If the ATTA uses a SPREF in the format as required by VPRM, then that part
number will be used. Of not, then the part number as defined in the configuration
file will be used.
You can transfer the component Pulled Bends as an addition to the tube from
which they are fabricated. .
When an Isometric is produced, any pulled bend is reported as the tube within
the Isometric Material Parts List and hence do not appear in the Isodraft transfer
file.
If you wish to utilise VPRM to requisition the bend pulling activity as a distinct
from the requisition of the tube, then the bends must appear in the Batch Mto file
as a component in their own right.
If the configuration file has been set to report them, then pulled bends will
appear as a tagged item in the Bulk Batch Mto file, as shown in the following
example.
$T:PB00001-750:Radius 750 PULLED BEND API5L GR.B*
$C::::::PB00001:PB00001-750:1:1:::Y:N:N:::::Y:N:::*
AVEVA Solutions
26/57
The tag includes the radius, the catalogue description and derives the VPRM
Part Number from the SPREF as with any other component.
For Final Mto this operates in exactly the same way as described above for Bulk
Mto except that the Angle will also be reported and included in the tag name, as
shown in the following example.
$T:PB00001-60-750:Angle 60 Radius 750 PULLED BEND API5L GR.B*
$C::::::PB00001:PB00001-60-750:1:1:::Y:N:N:::::Y:N:::*
You can transfer any Elbow and Fitting Bend attributes Angle and Radius to
VPRM. To allow this the configuration file contains five new options.
Transfer Elbow and Fitting Bend angles
The angle will only be transferred if the bore is greater than this
minimum range.
The angle will only be transferred if the bore is less than this maximum
range
The angle will only be transferred if the angle is greater than this
minimum range
The angle will only be transferred if the angle is less than this maximum
range
The Batch Mto file will normally contain the following entry.
$C:150:::E::PE00052::1:1:::N:N:N::352:2105:0:Y:Y:::*
If the configuration file specifies the transfer of the cut-back and the elbow bore
and angle are between the two ranges, then the same Batch Mto file entry will
look like this.
$T:PE00052-90-229:Cut-back with Angle=90 and Radius=229*
$C:150:::E::PE00052:PE00052-90-229:1:1:::N:N:N::352:2105:0:Y:Y:::*
The angle is reported to an accuracy that will be rounded up to the next full
angle, if value behind comma is greater or equal 0,5 and rounded down to the
next full angle, if value behind comma is smaller than 0,5
Note that during the export of Bulk Mto only the Radius is transferred.
AVEVA Solutions
27/57
To use these forms, select the attributes you wish to transfer from the drop down list. The
attributes have been extracted from the component you selected in the Members List
form and as a consequence it is not possible to choose attributes that do not exist.
Pick two attributes and the values of them will be concatenated into a single value and
stored against the VPRM User Definable Attribute.
In the case of components some attributes only exist for particular generic types. To list
attributes common to all components use the Gtype All, otherwise if you require a
specific attribute for a specific Gtype then select the relevant Gtype from the drop down
list.
To select a VPRM User Definable Attribute into which the selected Pipe or Component
button and the Pipe UDA or
Attribute value will be stored in VPRM, click on the
Component UDA form will be displayed. Select the required UDA from the list and the
form will automatically be closed.
To close the form click on the top-right button
You must select at least one attribute and a VPRM User Definable Attribute for the form
to be acceptable. If this is not the case, you will receive a warning message accordingly.
AVEVA Solutions
28/57
Discipline Rules
To control the Bulk MTO collection expressions: -
AVEVA Solutions
29/57
Select a file from the Options File list and Click on the
To enable or disable the VPRM Material transfer, Click on the toggle gadget
VPRM Material Takeoff.
button.
Note that the directory location for the output files is reset to the default value of
Local
If you want the output material file and the isometric transfer file to be located in a
directory other than the local directory, enter the pathname or a suitable
environment variable in the Directory field.
Click on the
button
button
Note: For your information, the communication between Standard PDMS forms and
PDMS to VPRM forms is carried out using APPWARETEXT.
AppWareText 'VPRMMTO' 'ON' indicates whether VPRM output is required
AppWareText 'RENAME' 'ON'
AVEVA Solutions
30/57
In order to ensure compatible PDMS and VPRM data, some Option file setting have to be
overwritten when producing a Isometric material for VPRM. The PML function
!!vprmProcess is called to set these and the pre and post processing options. For further
details of the overwritten options see the Vantage Integrated Project Execution User
Guide, section 6.3.3 PDMS Configuration
mess100-B-1.log
100-B-1_mto-IDF
100-B-1_mto-1
100-B-1.cmp
AVEVA Solutions
31/57
Component Weights
Wall Thickness
Specifications
For further details of the name format of the files described above, refer to the Vantage
Integrated Project Execution User Guide, section 6.3.1 Concepts
To be able to load all file types from the one location, the interface will take several things
into account when loading the files.
The files are date stamped and therefore if there is more than one file of the same
type they will be loaded in date order, the earliest being loaded first.
The files will be loaded in the order required to suit PDMS referencing
A batch process is used to load the specification files in the Specon module,
which means you will have to specify your password.
AVEVA Solutions
32/57
4. Use this form to enter an output file name in the Filename text entry gadget (if no
path is given the default is %PDMSUSER%).
5. Enter the name of an element in the hierarchy from where you wish to extract
data (For example, the use of the word CE will extract data from the current
hierarchy position).
6. Click on the button
AVEVA Solutions
33/57
The first thing you will notice is the coloured message at the bottom of the form, notifying
you of your database access status. When you displayed the form, the application
checked your access rights to the available databases against those required for the file
load. The application will respond to this check with one of three status messages, each
of them self-explanatory
'You do not have sufficient db access to load any files'
'You do not have sufficient db access to load some files'
'You have sufficient db access to load all files'
As a consequence to the access check, the application will only ever allow you to load
files than can be loaded.
AVEVA Solutions
34/57
This is particularly important when you use the PDMS-VPRM interface for the first time.
In this situation, the application needs to given the locations where you wish each file
type to be loaded.
To select the relevant databases use the menu option Dbs>Select and which will
display the Select Database Location form.
AVEVA Solutions
35/57
The example shown displays the situation when you enter a PDMS catalogue MDB that
has never had any VPRM files loaded into it. It presents you with four sections that deal
with the loading of the description text files, the property files, the bolt files and the
specification files. We will discuss each of this in turn below.
AVEVA Solutions
36/57
Description Texts
You will notice a indicator which will show whether you have access to any catalogue
database in which to load the description files. If you have access it will appear in colour
green and display Can Load. If you do not have access it will appear in colour red and
will display Cannot Load and give a brief reason as to why not.
'CATA is R only'
the system could not find any existing CATA nor could it
find any catalogue database to which you had WRITE
access
The paragon files output from VPRM always look for an existing PDMS CATA element
into which to load the description text elements and which is named as follows.
/VPRM_project_Name_SPECGEN_CATA
e.g.
/IPE001_SPECGEN_CATA
If this element does not exist the Use Existing CATA field will remain empty as shown in
the picture above, and as a consequence the application will attempt to create it, but you
need to specify in which database. To do this select one of the available catalogue
database from the list.
Weight Property
The weight files output from VPRM always look for an existing PDMS CMPW element
into which to load the properties and which is named as follows.
/VPRM_project_Name_PROPCON_CMPW
e.g.
/IPE001_PROPCON_CMPW
As discussed in section 4.5 above, this element must exist for the application to operate
correctly. This is because a properties database is only accessible by making an existing
element current, in this case the CMPW. If this element does not exist then you will not
be able to load the properties files.
AVEVA Solutions
37/57
Bolt Tables
The bolt files output from VPRM always look for an existing PDMS BLTA element into
which to load the bolt tables and which is named as follows.
/SPECGEN_BOLT_TABLE
If this element does not exist the Use Existing BLTA field will remain empty as shown in
the picture above, and as a consequence the application will attempt to create it, but you
need to specify in which database. To do this select one of the available catalogue
database from the list.
When each PDMS standard bolt element (SBOL) is created the application will set a
reference to a non-standard bolt diameter table (DTAB), held within a PDMS length table.
If the referenced DTAB does not exist, the application will load the sample length table,
which is supplied with this application as discussed in section 3. For further information
regarding bolting in PDMS see the PDMS PARAGON Reference Manual.
Wall Thickness Tables
The Wall Thickness files output from VPRM always look for an existing PDMS TABWLD
element into which to load the Wall Thickness tables and which are named as follows.
/Standard-Wall-Thickness-Tables
/Pipe-Data-Tables
If these element do not exist the Use Existing TABWLD field will remain empty as
shown in the picture above, and as a consequence the application will attempt to create
them, but you need to specify in which database. To do this select one of the available
catalogue database from the list.
AVEVA Solutions
38/57
Specifications
The specification files from VPRM always look for an existing specification by name. If it
does not exist the application will create it, but you need to specify in which PDMS
specification world (SPWL).
To create a non-existing specification into an existing SPWL, check the Create in SPWL
toggle and select the relevant SPWL from the list.
Alternatively, to create a non-existing specification into a new SPWL, check the Create
in db toggle and select the database into which this SPWL should be created. Finally,
give the name of the new SPWL in the Name text entry box.
AVEVA Solutions
39/57
Once all file types have been loaded and on subsequent use of the application, the
Select Database Location form will look similar to that shown in the example below.
AVEVA Solutions
40/57
Notice that all required elements appear in the Use Existing text entry boxes, and that
all files can be loaded.
Note: The displayed SPWL is the first one found that already contains any one of the
specifications to be loaded in this session. If none of the specifications to be loaded
exist, then the first SPWL will be selected and you will have to reselect the one you
require if they are not one and the same.
For a user who does not have access to the relevant databases, and this will definitely
occur if these are foreign, then the Select Database Location form will appear similar to
the one shown below.
AVEVA Solutions
41/57
Notice that in this example, the application could not find any databases open in write
mode and as a consequence it would not be possible to load any files.
Using the main form you will be able to carry out the following tasks.
The form displays the files found in the directory that is shown in the Files to Process
and Location text entry box. You can change this directory in three different ways.
Manual entry
Once selected the application will find all relevant files, categorise them, sort them and
display them on the form in the relevant area.
AVEVA Solutions
42/57
Catalogue Files
Specifications
Manual entry
43/57
2. Choose how long the application waits once the batch process is initiated by
using the delay setting.
The reason for the delay is that the application has to give the batch process a chance to
enter PDMS before it can start to check whether has terminated. The time this takes will
depend on factors such as your workstation capabilities or your network setup.
During the batch run, another log file was written that includes all of the PDMS trace
during the specification load in the PDMS Specon module. This log file is located in the
same directory as the main log file and is named vprmSpecLoad.log
Note. If a specification file fails to load correctly, that file load will be aborted. Any
subsequent files that relate to the same specification will also remain unloaded. You will
need to correct the error in the failed file and reload that specification again to load all
matching unloaded files.
AVEVA Solutions
44/57
AVEVA Solutions
45/57
Using this form you will be able to carry out the following actions.
AVEVA Solutions
46/57
Manual entry
mto_area/line_reference-00
Area:
Line Ref:
A50
FW-1001-A50
A50-FW-1001-A50-00
Please note that this functionality is customer specific, requires a special version
of MDS and will require consultation with AVEVA before use.
AVEVA Solutions
47/57
The Detail List will display the Pipe Name and its Area and Line Reference.
Notice the
* symbol which denotes the fact that the detail list has not been checked for
other Pipes which fulfil the Area Combination criteria. For further details on this subject
refer to the section below entitled Search for Matching Pipes.
If either of the Area or Line Reference attributes is unset, then you will receive a warning
message accordingly.
You can select any element in the Members list, from which to find suitable Pipe
elements. For example, select a ZONE and all PIPE elements in this Zone that have set
Area and Line Reference attributes, will be added to the Detail List.
If you want to remove a Pipe from the Detail List select it and click on the button
If you want to remove all Pipes from the Detail List then click on the button
You can also Select All entries in, Remove Selected and
Remove All entries from the Detail List using a pop-up menu
available by making aright mouse click in the Detail List
AVEVA Solutions
48/57
Enter the required PDMS expression syntax into the With text entry box and press the
keyboard Enter key. Close the form with a click on the top-right button
Note: It is possible to have both the Check during Extract and the Check on Selection
options selected at the same time or neither of them selected.
AVEVA Solutions
49/57
If you utilise a PDMS expression to restrict the collection of pipe elements, then there is a
danger of excluding material that may be relevant. To assist you in ensuring that material
is not excluded, whenever a check for matching pipes is made, you will receive a warning
if any matching pipes have been excluded by the use of the expression.
These warnings will be in the form of a screen message, but if you utilise the check
functionality during the extract, then the warnings will be included in the bulk material
take-off log file.
When a pipe element has been added to the detail list and a check is made for any other
pipes matching the area and line reference combinations, the system will display the
following message if other pipes that have been found but have been excluded by the
expression used.
If you click on the YES button, then a form will be displayed that lists those pipe elements
that have the same area and line reference combination as a pipe that has been added
to the detail list, but has been excluded by the expression.
AVEVA Solutions
50/57
or use
Output Files
The Bulk Mto output file will be named in the following format.
piping_bulkMto_<date stamp>.dat
mds_bulkMto_<date stamp>.dat
Where the date stamp uses seconds, minutes, hours, day, month and year.
AVEVA Solutions
51/57
AVEVA Solutions
52/57
The VPRM screen that handles PDMS Specification References now contains two new
columns in the PDMS References section as shown below.
The new fields will be used when generating the names of PDMS
specification references.
The Bulk Mto transfer from PDMS to VPRM will be amended in order to
handle the new format of specification component (SPCO) name.
The Isometric Mto transfer from PDMS to VPRM will be amended in order
to handle the new format of SPCO name.
PDMS specification reference names will therefore be generated in the following format.
/specification_name/contractor_id/revision_code/part_no:shortcode,size1
/A1B/FRA/A1/PE00042:E0,50
NULL values will be allowed in the specification parameters
/specification_name///part_number:shortcode,size1
/A1B///PE00042:E0,50
AVEVA Solutions
53/57
AVEVA Solutions
54/57
AVEVA Solutions
55/57
AVEVA Solutions
56/57
Once this data is available, the lugs will be included in the Bulk and Final Mto file in the
same way as any other component, where the shortcode and part number are derived
from the component SPRE, as is shown in the following example.
$C:100:::LUF::LF00001::1:1:::N:N:N::3500:3390:645:Y:Y:3::202*
AVEVA Solutions
57/57