PDS Translator

Version: 2.1

AVEVA Solutions Limited

High Cross | Madingley Road | Cambridge | CB3 0HB | UK
Tel +44 (0)1223 556655 | Fax +44 (0)1223 556666

Contents
.............................................................................................................................. 1
I. Introduction ......................................................................................................... 4
PDS EDEN Converter ....................................................................................... 4
PDS Catalogue Extractor................................................................................. 4
PDS Translator ............................................................................................... 4
II. Getting started .................................................................................................... 5
Software requirements ................................................................................... 5
A.

Obligatory ................................................................................................................................ 5

B.

Optional ................................................................................................................................... 5
Data requirements ......................................................................................... 5

A.

Catalogue extraction ............................................................................................................... 5

B.

Piping translation..................................................................................................................... 7

C.

Equipment translation ............................................................................................................. 8

D.

Structures translation .............................................................................................................. 9

E.

Volumes translation .............................................................................................................. 10

Project conversion workflow......................................................................... 11

A.

General data flow diagram .................................................................................................... 11

B.

Piping conversion workflow .................................................................................................. 12

C.

Equipment conversion workflow .......................................................................................... 15

D.

Structures conversion workflow ........................................................................................... 16

E.

Volumetric model conversion workflow ............................................................................... 18

F.

General notes ........................................................................................................................ 19

III. Tools reference guides ..................................................................................... 20

PDS EDEN Converter tool .............................................................................. 20
PDS Catalogue Extractor tool........................................................................ 21
PDS Translator ............................................................................................. 23
A.

General settings..................................................................................................................... 24

B.

Catalogue Settings ................................................................................................................. 36

C.

Piping Settings ....................................................................................................................... 45

D.

Structures Settings ................................................................................................................ 51

E.

Volumes Settings ................................................................................................................... 53

F.

Oracle Dump files to Access DB converter ............................................................................ 55

IV. Appendixes ...................................................................................................... 56

Using tables alias mapping syntax ............................................................... 56
Conversion geometry logic from PDS DGN model to PDMS/E3D model ......... 58
A.

DGN Cone element ................................................................................................................ 59

B.

DGN Solid element ................................................................................................................ 60

C.

DGN Surface Element ............................................................................................................ 63

D.

DGN Shape, Ellipse, ComplexShape Elements....................................................................... 63

E.

DGN Line, Linestring, Arc, Complexstring, Curve Elements .................................................. 63

I. Introduction
PDS Translator is a set of tools designed to translate the project report data
produced by PDS 2011 (V12) software and in result, generate PML macro files
compatible with AVEVA Everything 3D or AVEVA PDMS applications. This consists of
the following applications:

PDS EDEN Converter

In PDS, EDEN files (or graphical commodity tables) are scripts written in a high level
language with a syntax similar to FORTRAN. Those are responsible for getting the
design data (such like physical dimensions and weights of components) from correct
tables based on input commodities, model codes and sizes. EDEN Converter tool is
converting EDEN files to produce DLL library that will be helpful in extraction crucial
components data from inputs in later process (See PDS Catalogue Extractor). The dll
generated in this step is named HLL.<project_name>.dll, and will be used when
extracting the catalogue.

PDS Catalogue Extractor

In order to save time on analyzing and processing the PDS piping catalogue input
data while generating the PDMS/E3D catalogue, the initial extraction of curtail
piping data is done as a separate step with PDS Catalogue Extractor tool.
This tool uses custom rules of reading input data, coming from the HLL.xxx.dll file
that is created by the EDEN Converter tool.

PDS Translator
This is the main tool responsible to translate the data into final PDMS/E3D elements
in form of PML macro files which can later be imported into the AVEVA project.

II. Getting started

Software requirements
A. Obligatory

Microsoft Access Database Engine 2010 Redistributable (32 bit version)

Microsoft .NET Framework 4

Bentley MicroStation any version capable of converting DGN files from

version 7 to version 8 in batch mode. Its also useful when reviewing the
quality translated model.

B. Optional
Microsoft Access comes as part of Microsoft Office package. Useful with
manual correction and review of input *.accdb or *.mdb database files.

Data requirements
The following files from PDS are required for a successful translation. Depending on
the detail level of the translation, for example if catalogue data should be translated
or not, some of these files may not be required. All required files are product of PDS
reporting system. Its crucial for PDS user to know how to produce them. Any
information about generation of following data is explained in detail in PDS
documentation (PDS Reference Data Manager and PDS Report Manager documents).
PDS Translator is designed to process data created by PDS software in version 2011
(V12). Using the data created by earlier versions may or may not result in lesser
quality of translation.

A. Catalogue extraction

Graphic commodity files Also known as EDEN files

Standard note files Also known as EDT files, code files

Piping materials class file Also known as PMC file, or table 201files

Piping commodity specification files - Also known as PCD files, or table 202
files

Piping speciality specification files (If used) Also known as PCD files, or
table 203 files

Instrument component specification files (If used) Also known as PCD files,
or table 204files

Reference file Also known as Reference.DDL file, used to describe tables:

201, 202, 203, 204, etc.

Physical data tables - Also known as DIM files, US files

Piping job specification tables - Also known as PJS files

Short material description files - Usually txt files

Long material description files - Usually txt files

Speciality material description files - Usually txt files

B. Piping translation

Extracted catalogue file If generated with PDS Catalogue Extractor tool, it will
contain PDS catalogue data from processed inputs in form of *.ACCDB (Access
database) file

MTO Database file/s One or more *.MDB or *.ACCDB (Access database) files
containing tables required for this process:
o

PDTABLE_12 Piping Segments Table

PDTABLE_34 Piping Components Table

PDTABLE_50 Piping/Tubing Table

PDTABLE_67 Instrument Components Table

PDTABLE_80 Pipe Supports Table

PDTABLE_110 Gaskets Table

PDTABLE_120 Bolts and Nuts Table

PDTABLE_130 Welds Table

PDTABLE_170 Geometric Data Table

PDTABLE_205 Short Material Table

PDTABLE_215 Long Material Table

PDTABLE_250 Standard Notes Table

PDTABLE_900 Model Data Table

PDTABLE_920 Attribute Data Table

Piping DGN Files Piping Model Graphic Files

Piping DRV Files Piping Model Label files (optional)

C. Equipment translation

MTO Database file/s One or more *.MDB or *.ACCDB (Access database files)
containing tables required for this process:
o

PDTABLE_21 Equipment Group Table

PDTABLE_22 Equipment Nozzle Table

PDTABLE_23 Equipment Nozzle Extended Table (optional)

PDTABLE_900 Model Data Table

Equipment DGN Files Equipment Model Graphic Files

Equipment DRV Files Equipment Model Label files (optional)

D. Structures translation

MTO Database file/s One or more *.MDB or *.ACCDB (Access database files)
containing tables required for this process:

PDTABLE_500 Model Data Table

PDTABLE_532 Linear Member Table

PDTABLE_533 Cross Section Table

PDTABLE_534 Linear Member Coordinates Table

PDTABLE_536 3D (Solid) Member Coordinates Table

PDTABLE_538 3D (Solid) Member Geometry Table

Structures DGN Files Structures Model Graphic Files (optional). Useful to have
for comparison with translated model

Structures DRV Files Structures Model Label Files (optional)

E. Volumes translation

Any discipline model DGN Files Piping, Equipment, Structures, Railways, etc.
model graphic files

Any discipline model DRV Files Piping, Equipment, Structures, Railways, etc. model
label files very useful when presenting translated volumetric model elements
hierarchy with names and attributes (optional).

Project conversion workflow

The following diagram describes the translation process, and what files are used by
which part of the data translation:

A. General data flow diagram

Figure 1 PDS Translator data flow diagram

B. Piping conversion workflow

1) Use the PDS Eden Converter to create HLL.DLL file:
a. Run PDS Eden Converter application
b. Fill all required fields.
c. Click on the Generate button
d. If in Log Viewer will inform user about Build FAILED, then conversion
problems has to be sorted out manually using text editor for each of files
mentioned in log messages.
Note: Described step can be done assuming that user got Graphical commodity
tables along with other input files. If those files are not delivered with project input
data or user already has reliable HLL.DLL file from different project, this step can be
skipped.
2) Use the PDS Catalogue Extractor create intermediate database.
a. Run PDS Catalogue Extractor application
b. Fill input and output fields
Table 1Obligatory and optional fields for "PDS Catalogue Extractor"

Obligatory fields

Optional fields

PJS table files directory

DDL file path

US table files directory

PSS file path

Note files director

Taps file path

PCD files directory

Material description file

paths

PMC file path

HLL DLL file path (path to the library
generated by PDS Eden Converter)
Access DB file path
c. Click on Generate button
Note: This step can be skipped if user doesnt want to use Generate from extracted
components option in later PDS Translator step.
3) Check if DGN files for piping are in version 8. Version 7 are not supported. If not
then convert them using external tool (Bentley Micro Station is recommended).
4) Use the PDS Translator create PML macros for piping.
a. Create new configuration or open already created configuration from file.

b. Fill in the Project name field, optionally fill in Description field

in tab General > Information.
c. In tab General -> Disciplines - select:
-

Generate from extracted components This is optional if user had

generated extracted components database and wants to make use from
seed components in PDMS/E3D

Generate from piping model components

Piping

d. In tab General -> Inputs:

-

Fill out the MTO table definitions, for required tables by selecting the
MTO database or manual selection of input tables.

Required tables for piping:

Table 2 Aliases and table descriptions required to translate piping model.

Table Alias

Description

MOD

The table contains model data.

SEG

The table contains segment data.

CMP

The table contains component data.

PIP

The table contains piping data.

INS

The table contains instrument data.

SUP

The table contains pipe support data.

GSK

The table contains gasket data.

BLT

The table contains bolt data.

WLD

The table contains weld data.

POS

The table contains coordinate data.

e. In tab General -> Outputs - fill in the fields:

-

Output Folder

Log Folder

Intermediate data

f. In tab General -> DGN - Set DGN to PDMS/E3D levels mapping or use defaults.
g. In tab Catalogue -> Inputs - Fill out the extracted components data sources
definitions by selecting the database generated by PDS Catalogue Extractor or
manual edition in Extracted component data source defs window.
h. In tab Piping -> Inputs - Fill in DGN files folder field.
i. In tab Piping -> Settings - Select the models which will be included in
processing.

If table isnt visible, check table with alias MOD when doing step 4.d , then try
to refresh.
j.

Click on Generate button after providing all required inputs.

k.

Import macros:

Drag and drop 0_LEXI_UWRL_MAIN file from output location to Lexicon

Drag and drop 1_PROP_CMPW_BATCH file from output location ->

Catalogue to Paragon (Property World has to be current element)

Drag and drop 2_PARA_PIPE_CATA_SEED file from output location ->

Catalogue to Paragon (optional)

Drag and drop 3_PARA_CATA_BATCH file from output location -> Catalogue
to Paragon

Drag and drop 4_PARA_SPEC_BATCH file from output location -> Catalogue
to Paragon

Drag and drop 5_PARA_MISC_BATCH file from output location -> Catalogue
to Paragon

Drag and drop BATCH file from output location -> Piping to Design

Note 1: Importing PML macros is much faster in TTY mode so it is advised to use it.
Note 2: If user had already generated catalogue using current settings and wants to
repeat only the process of generating model data then tick out the Generate from
options in General -> Disciplines tab.

C. Equipment conversion workflow

1. Check if DGN files for equipment are in version 8. Version 7 are not supported. If
not then convert them using external tool (Bentley Micro Station is
recommended).
2. Create new configuration or open existing from file.
3. Fill in the Project Name field, and optionally fill in Description field
in tab General > Information.
4. In tab General -> Disciplines select Equipment
5. In tab General -> Inputs - Fill out the MTO table definitions, for required tables
by selecting the MTO database or manual selection of input tables.

Table 3 Aliases and table descriptions required to translate equipment model.

Table Alias

Description

EQU

The table contains equipment data.

NOZ

The table contains nozzle data.

MOD

The table contains model data.

6. In tab General -> Outputs - Fill in the fields:

Output folder

Log folder

Intermediate data

7. In tab Equipment -> Settings - Select the models which will be processed.
If table isnt visible, check table with alias MOD when doing step 5, then try to
refresh.
8. Click on Generate button after providing all required inputs.
9. Import macros

Drag and drop 0_LEXI_UWRL_EQUI file from output location to Lexicon

Drag and drop batch file from output location ->Equipment to Design.

D. Structures conversion workflow

1. Create new configuration or open existing from file.
2. Fill in the Project Name field, and optionally fill in Description field
in tab General > Information.
3. In tab General -> Disciplines Select:

Generate from structure model components

Structures

4. In tab General -> Inputs - Fill out the MTO table definitions, for required tables
by selecting the MTO database or manual selection of input tables.

Table 4 Aliases and table descriptions required to translate structures model.

Table Alias

Description

SMOD

The table contains model data of structures.

LIM

The table contains linear member.

CRS

The table contains cross section data.

LMC

The table contains linear member coordinate.

SLD

The table contains solid data.

SGD

The table contains structures geometry data.

5. In tab General -> Outputs - Fill in the fields:

Output folder

Log Folder

Intermediate data

6. In tab Structures -> Settings - Select the models which will be processed.
If table isnt visible, check table with alias SMOD when doing step 4, then try to
refresh.
7. Click on Generate button after providing all required inputs.
8. Import macros

Drag and drop 0_LEXI_UWRL_MAIN file from output location to Lexicon

Drag and drop 2_PARA_STRU_CATA_SEED file from output location ->

Catalogue to Paragon (optional)

Drag and drop 3_PARA_CATA_BATCH file from output location -> Catalogue
to Paragon

Drag and drop 4_PARA_SPEC_BATCH file from output location -> Catalogue
to Paragon

Drag and drop BATCH file from output location -> Structures to Design

Note 1: If user had already generated catalogue using current settings and wants to
repeat only the process of generating model data then tick out the Generate from
options in General -> Disciplines tab.

E. Volumetric model conversion workflow

1. Create new configuration or open existing from file.
2. Fill in the Project Name field, and optionally fill in Description field
in tab General > Information.
3. In tab General -> Disciplines Select:

Volumes

4. In tab General -> Outputs - Fill in the fields:

Output folder

Log folder

Intermediate data

5. In tab Volumes ->Settings - Add DGN files, from which volumetric model will be
generated.
Optionally tick the checkbox Add information from DRV files.
6. Click on Generate button after providing all required inputs.
7. Import macros:

Drag and drop 0_LEXI_UWRL_MAIN file from output location to Lexicon.

Drag and drop BATCH file from output location -> Volumes to Design.

F. General notes

Combination of disciplines processing can be also done on one session.

For greater time saving, good tip is first, generate only the data related with
Catalogue and Specification Discipline (Piping/Structure catalogues) with Design
Piping/Structures disciplines at first run. Then on any later sessions only
Piping/Structures disciplines. Piping/Structure disciplines will use last generated
Intermediate specification data.

Equipment and Volume disciplines are currently working without intermediate

data.

III. Tools reference guides

PDS EDEN Converter tool
a

d
e

Figure 2 PDS EDEN Converter Tool

a) Clean build checkbox - If its:

-

Checked: conversion process is starting from beginning

Unchecked: conversion process is building library if graphic

commodity tables are converted. Otherwise it starts the conversion
process.

b) EDEN files directory path - Graphic commodity tables (EDEN tables) path
c) HLL file directory - path where HLL file will be saved.
d) Project name Name of the project that commodity tables are coming from.
e) Log viewer - displays feedback from the application
f) Open file dialog
g) X Button - Clear textbox field
h) Generate button - Starting conversion process.
i)

Stop button - allows interrupt this process is enabled during conversion

process.

PDS Catalogue Extractor tool

a
b
c
d

g
m
h
n
i
o
j
k

r
q

Figure 3 PDS Catalogue Extractor tool

a) PJS table files directory - Piping job specification tables, that defines the
characteristics, properties, design standards, and company practices
associated with piping commodity items.
b) DIM table files directory Input dimension data of components.
c) Note files directory - Contains the code list.
d) PCD files directory - Piping commodity data files directory
e) DDL file path
f) PMC file path table of available specifications with additional attributes
g) PSS file path
h) Taps file path - the neutral file for tap properties data
i)

HLL DLL file path - DLL file generated by PDS EDEN Converter

j)

Short material descriptions file - Contains the short material descriptions for
commodity items.

k) Tap material descriptions file

l)

Long material descriptions file - Contains the long material descriptions for
commodity items.

m) Pipe support material descriptions file

n) Instrument material descriptions file
o) Specialty material descriptions file Contains the material descriptions for
specialty items.
p) Access DB file path - Output database file path
q) Log viewer - displays feedback from the application
r) Generate button starts generation of extracted catalogue in form of Access
database.
s) Stop button - Allows interrupt this process, is enabled during generation
process,
t) Open file dialog
u) Folder browse dialog

Note: The following fields are optional:

-

PSS file path

Taps file path

Short material descriptions file

Tap material descriptions file

Long material descriptions file

Pipe support material descriptions file

Instrument material descriptions file

Specialty material descriptions file

PDS Translator
c

d
b

Figure 4 PDS Translator main window

a) Configuration menu - Allows to save, open, create new configuration or exit

application.
b) Tools menu - Contains additional tools that might be useful in data
translation.
c) Help menu - Contains documentation and information about application.
d) Tabs containing settings for the various disciplines.
e) Log viewer - Displays feedback from the application.
f) Generate button - Starts translation process from PDS data to PDMS/E3D
project, for selected disciplines.
g) Show Output button - If in tab General -> Outputs field Output folder is
set, button will open the output directory.
h) Stop button - Button is enabled during translation process, allows to
interrupt this process.

A. General settings
This tab contains settings that apply to all disciplines.

General -> Information

The tab contains basic information about configuration.

a
b
c
d
e
f

Figure 5 General ->Information window settings

a) Created By - Information about author of the configuration

b) Creation Date - Date of configuration creation.
c) Project name Name of project
d) Project Version Version of PDS Translator application used in creation of
configuration
e) Project Location f) Description - Project description (this field is not required)

Note: Project name cannot contain any gaps, should be as short as possible.
Project name is environment variable, with can be used in setting mapping.
(Fill out the project name field is obligatory for all disciplines)

General -> Disciplines

This tab contains settings about disciplines that will be created.

a
b
h

c
d
e
f
g

Figure 6 Selection window disciplines

Discipline are divided into two groups:

I) Catalogue and specification
a)

Generate from extracted components this option is only useful when

user has generated extracted catalogue using PDS Catalogue Extraction
tool.

b)

Generate from piping model components this option will process all
piping models from table 900 in search of unique components and
generate resulting catalogue and specifications based on current
mapping. Each unique component geometry representation will be
taken from model related DGN file.

c)

Generate from structure model components this option will use

structural model section profiles table 533 from MTO database in order
to produce PDMS/E3D structural catalogue and specification.

II) Design model

d)

Generate piping - this option will generate selected piping models

referencing to generated piping specification.

e)

Generate equipment this option will generate selected equipment

models.

f)

Generate structures this option will generate selected structural

models. referencing to generated structural specification

g)

Generate volumes - this discipline will translate only geometry model

from DNG files.

Note: Use only selected models checkbox (h) Option is possible to change when
Generate from piping model component is selected. It allows to generate
components only from models selected in tab Piping -> Settings. If the checkbox
is unticked, all models are involved in components generation process.

General -> Inputs

The tab contains inputs setting used during generation process.

Figure 7 General -> Input tab.

a)

Load from MTO DB button - Allows choose MTO database file. It will try
to match the tables from selected MTO to required table aliases.

b) MTO data sources Edit button - Showing dialog where the table data
sources can be manually adjusted.

MTO data sources dialog

This dialog allows to manual assignment and conversion input tables from one or
multiple access database files. Conversion of table is required if columns in it have
different data types than expected.
a
b
c

d
Figure 8 MTO data sources dialog with example data.

a) Table name column - Table name from input database file.

b) Source file path column MTO database file path. Double clicking on cell in
this column will allow to select input database and later the table name.
c) Column shows if table is correct. There are three possible states:
- Correct table everything is in order with the table.
- Convert - At least one column has wrong data type. After clicking
Convert button, table will be converted to correct format and saved in
new DB file. The path to the source file will be adjusted to the new DB.
- Incorrect table - the reason for this is incorrect table name or lack of at
least one required column in it.
d) Stop button Allows to abort table conversion process.
e) Convert all button - Convert all tables which can be converted.
f) Table alias Alias of the table (Short name, max of 4 characters, describes
type of table).

g) Data type column - Type of data source, click on cell in this column begins
"selection database and table name" process, that allows to choose data type,
source file and table name.
Note 1: Table aliases are used when configuring the mapping attributes from PDS
tables to PDMS/E3D element attributes.
Note 2: Its not necessary to have all tables available if you want to start translation
only for one discipline. The table below shows which aliases (tables) are required for
specific disciplines:
Table 5 Table contains information about required tables for various disciplines.

Discipline

Require table (Table alias)

Extracted components

---

Piping model

MOD, SEG, CMP, PIP, INS, SUP, GSK

components
Structure Model

SMOD, LIM, CRS, LMC, SLD, SGD

components
Piping

MOD, SEG, CMP, PIP, INS, SUP, GSK, BLT, WLD, POS

Equipment

MOD, EQU, NOZ

Structures

SMOD, LIM, CRS, LMC, SLD, SGD

Volumes

---

Selection of Access database file and table from this file.

1) Select database file (*.accdb or *.mdb) using open file dialog
Click on file witch you want to select the table from (a). Click on open button
(b).

Figure 9 Open file dialog

2) After selecting the database file. Select table name dialog will apear:

a
b

Figure 10 Select table name dialog.

Figure 11 Select table name dialog

displaying list of available tables.

3) Click on the combo box field (a) to display the list of available table
4) Select one of the tables you want to choose.
5) Click on Select button. Select button is enabled when one of tables is
selected.

General -> Outputs

This tab allows to set and modify directories, where output data files will be stored
after being generated by the application.

d
b
e

Figure 12 General -> Outputs tab.

a) Output folder Main directory where output subfolders and files will be
placed (See Note 1).
b) Log Folder - Directory where log files will be stored.
c) Intermediate data Path to the Intermediate database. The Intermediate
database is creating during generating catalogue (See Note 2).
d) Buttons displays Browse for folder dialogue.
e) Button displays Save File dialogue.
Note 1: It is a good practice to set the output folder name to same as PDS project
name.
Note 2: Intermediate database is being generated when catalogue adapter is
generating the PML macros related with Catalogue and specification. Later in the
process, this database is used by design discipline adapters as a help information
about available components and specifications.

General -> DGN

Figure 13 this tab allows mapping levels from PDS to PDMS/E3D.

a) PDS level no column - Level in PDS ( level 0 is default)

b) AVEVA level from column - The lower bound of the range (Default range in
PDMS/E3D is between 0 and 10 but can be higher if necessary)
c) AVEVA level to column - The upper bound of the range (Default range in
PDMS/E3D is between 0 and 10 but can be higher if necessary)
d) Load default button - Load default mapping (all layers are always visible)
This user interface allows to map DGN level of processed geometries to PDMS/E3D
level ranges.
Levels in PDS allows to hide less important elements from model e.g. insulation,
obstruction shapes or detail geometries. In DGN files each graphical element is
assigned to the corresponding level. The level is integer number bigger than zero.
The user specifies which level to be visible and which hidden.
In in PDMS each geometry primitive element has level attribute set to the range,
within which the element is visible, e.g. If element visibility range is set from 0 to 10
and if the representation level of PDMS/E3D application is set to number 6 (within

element levels), it will be visible for the user, otherwise is hidden. Below is example
of using levels in DGN and its converted equivalent in PDMS/E3:
Level: 42

Level: 20

Figure 14 Example element in DGN with marked levels.

Obstruction of DGN geometry in on level 42 and actual geometry is on level 20. So

the PDMS/E3D mapping for level 20 could be set from 0 to 10 and for level 42 from 7 to 10. Below pictures shows the geometry DGN converted to PDMS/E3D with
such level mapping applied:

Figure 16 Element presented on figure 9

converted to PDMS geometry with level mapping
applied. Representation level set to 6

Obstruction
shape is
hidden
Representation
level set on 6

Figure 15 Same element but with

Representation level set to 7

Obstruction
shape is
visible

Representation
level set on 7 for
others

B. Catalogue Settings
This tab contains inputs settings that will be used during the catalogue generation
process.

Catalogue -> Inputs

This tab contains inputs settings for catalogue discipline.

Figure 19 Catalogue inputs tab

a)

Load from ACCDB button - Allows choose extracted components

database. Application will detect the tables from selected database and
automatically fill out the table data sources.

b) Extracted component data sources Edit button - Showing dialog where

each table data source can be manually adjusted.
Note 1: In order to get extracted components database user needs to go through
the process related with PDS Catalogue Extractor tool.

Dialog window with extracted component data sources definition settings

Figure 18 Extracted component data sources definitions dialog with example data.

a)

Table name column - Table name from extracted component data file,
whose path is specified in column Source file path.

b) Source file path column - Extracted component data file path. Double click
on cell in this column begins "selection database and table name" process,
that allows choose data type, source file and table name.
c) Data type column - Type of data source, click on cell in this column begins
"selection database and table name" process, that allows choose data type,
source file and table name.

Catalogue -> Mapping

The tab Catalogue -> Mapping is divided into two tabs. First tab allows to set
mapping for the piping catalogue, second tab allows to set mapping for the
structures catalogue. The Load default button (d) allows you to restore default
settings for current mapping tab.
a

Figure 19 Piping catalogue mapping tab

Both discipline tabs are divided into 3 columns:

a) PDS Piping/Structure components mapping column The column contains a
table with a collection of available mappings with properties.
Orange rows are default mappings (these mappings cant be removed), if
processed commodity item cant be assigned to any non-default mapping, it
will be assigned to the default.
By right-clicking on this table you can bring the menu with adding and
removing of mappings.
The table contains four columns:

Mapping description Name of mapping. Acts as information for the

user about applied mapping.

Src table Alias of source table

Available aliases of tables for piping:
o

CMP

INS

PIP

PSU

GSK

Available alias of table for structures:

o

CRS

Seed CATE defs Allows to create and modify the seed definition.
(Look at point 2.2.1 for piping and at point 2.2.2 for structures)

Mapping filter Conditions which have to be met, to use current

mapping for processed commodity items. In order to edit filter rules
user needs to modify to Properties column. Described further.
By clicking cell in this column, you can add or remove rule in the Filter
Properties column.

b) PDMS/E3D component hierarchy column This column shows destination

component hierarchy tree in Paragon for particular component mapping.
Nodes CatalogueWorldDef and PropertyWorldDef are mandatory and cant be
removed.
Most of nodes have properties table (Except: CatalogueWorldDef,
PropertyWorldDef).
c) Properties column Properties of currently selected cell or tree node. Below
are shown two different properties tables:

Rule column can modify, add

or remove rules for mappings

Figure 20 Example "Filter Properties" table for Mapping filter cell. Note: Rules can
be added or removed by right mouse click

Column shows PDMS/E3D

Column show

Column informing

Column informing if

Column show attribute

attribute name that the

PDMS/E3D

if mapping is user

its obligatory

value mapping syntax

mapping is applied to.

attribute type

defined attribute

attribute mapping

Figure 21 Example "Definition Properties" table for DTSEDef node. Note: Attribute mappings can be added or removed by
right mouse click

Seed CATE definitions for piping

d
e

g
Figure 22 Seed CATE definitions dialog for piping

Figure 23 Parameters tab showing example of seed component parameters mapping

a) Seed CATE name Name of Seed CATE element. Seed category element
should be defined in Paragon manually.
b) SCOM name Name of seed SCOM element
c) DTSE name Name of seed DTSE element
d) SDTE name Name of seed SDTE element
e) PDS filters Conditions which have to be met for translator, to use current
seed component in generation of component for PDS commodity
f) Parameters List of parameter mappings, which have to be added to seed.
g) Transformations The tab allows to add modifier of offset and rotation
element.

h) Type column Type of value.

Available types:
NONE should be used with word variables
DIST should be used with dimension variables
ANGL should be used with angle variables
i)

Value column - Contains syntax which defines mapped value of an attribute

for each parameter.

Note 1: Names of SEED CATE, SCOM, DTSE and SDTE should match to names in
SEED components macro PML file.
Note 2: Transformations are useful when seed component is defined in
PDMS/E3D catalogue with different orientation standard than its PDS equivalent
component. For example: In PDMS a TEE type component is usually defined that
P1 connection is always pointing to X axis, P2 is always pointing to X axis and
P3 is usually pointing to Y axis. If PDS version of TEE has being defined
differently and theres no transformation applied for seed component that will be
used as PDMS version TEE, this will result in TEE elements oriented incorrectly in
Translated design model.

Seed STCA definitions for structures

a

h
g

Figure 24 Seed STCA definitions for structures with example data.

a) Seed STCA name - Name of Seed STCA element.

b) SPRF name Name of seed SPRF element
c) DTSE name Name of seed DTSE element
d) Orientation flip These option allow to modify the orientation flip.
e) Orientation angle: These option allow to modify the orientation angle.
f) Parameters - Table of parameter mappings, which has to be added to seed.
g) Type column - Type of value.
Available types:

NONE should be used with word variables

DIST should be used with dimension variables

ANGL should be used with angle variables

h) Value column Contains syntax which defines mapped value of an attribute

for each parameter.
i)

PLINE mappings Mapping from PDS cardinal points to AVEVA PKEYs

Specification question definitions

Figure 25 Specifications question definition dialog

a) Attr name Name representing the PDMS/E3D specification question.

b) Default answer Default answer for question (numerical)
c) Answer syntax Answer for question mapping (numerical)
d) Default text answer Default text answer for question (numerical).
e) Text answer Text answer for question mapping (numerical)
Note 1: See the PDMS/E3D documentation for typical question combinations for
particular component specifications
Note 2: Make sure that for numerical answer (also default) mapped PDS table
alias attribute is not type of string.

C. Piping Settings
This tab contains setting related with piping discipline specifics.

Piping -> Inputs

This tab contains inputs setting for the piping discipline.

Figure 26 Piping inputs tab

a) DGN files folder - Path to the folder, which contains DGN files related with
piping discipline.
b) Button which prompts for directory where Piping DGN files are.

Piping -> Mapping

The tab Piping -> Mapping is divided into two parts. First part (a) contains the
simple hierarchy representation of piping model in design. Second part (b) contains
properties of the selected element in hierarchy. User can modify, add or delete
element specific or user defined attributes.
The Load default button (c) allows you to restore default settings for current
mapping tab.
a

Figure 27 Piping mapping tab

Piping -> Settings

This tab contains list of models which can be used in piping generation process.
Models and partition numbers are being read from table 900(alias MOD) of MTO
database.
a
b
c
d
e

Figure 28 Piping settings tab

a) Column contains checkboxes indicating which models will be included in

processing. Unselected models would be skipped.
b) Model Name column - Contains names of models taken from 'MOD' table
(Only those with discipline_no = 1).
c) Partition no column partition number related with model no. Also taken
from MOD table
d) Has DGN column - Information on whether there is a DGN file related with
specific model,
in the directory set in Piping -> Inputs
e) Has DRV column - Information on whether there is a DRV file related with
specific model,
in the directory set in Piping -> Inputs
Note: DGN files are matched with models by name. If DGN file is unavailable for a
model, selection the model will be impossible and the model will be skipped.

Equipment Settings
This tab contains setting related with equipment discipline, used during generation
process.

Equipment -> Inputs

This tab contains inputs setting for the equipment discipline.

Figure 29 Equipment inputs tab

a
a) DGN Files Folder - Path to the folder, which contains DGN files for equipment.

b) Button which prompts for folder where Equipment DGN files are.

Equipment -> Mapping

Currently mapping for equipment discipline elements can only be done by
modifying the configuration separate configuration file

Equipment -> Settings

This tab contains list of models which be used in equipment generation process.
Models and partition numbers are also being read from table 900(alias MOD) of
MTO database.
a
b
c
d
e

Figure 30 Equipment settings tab

a) Column contains checkboxes indicating which models will be included in

processing. Unselected models would be skipped.
b) Model name column - Contains names of models taken from 'MOD' table
(Only those with discipline no = 2).
c) Partition no column partition number related with model no. Also taken
from MOD table
d) Has DGN column - Information on whether there is a DGN file related with
specific model,
in the directory set in Piping -> Inputs
e) Has DRV column - Information on whether there is a DRV file related with
specific model,
in the directory set in Piping -> Inputs

Note: DGN files are matched with models by name. If DGN file is unavailable for a
model, selection the model will be impossible and the model will be skipped.

D. Structures Settings
This tab contains inputs setting for the equipment discipline, used during
generation process.

Structures -> Settings

This tab contains list of models which be used in structures generation process.
Models and model index numbers are specifically being read from table 500(alias
SMOD) of MTO database.

a
b
c

Figure 31 Structures settings tab

a) Column contains checkboxes indicating which models will be included in

processing. Unselected models will be skipped.
b) Model name column - Contains names of models taken from 'SMOD' table
c) Model index no column Value related with model name in MTO database

Structures -> Mapping

This tab is divided into two parts. First part (a) contains the simple hierarchy
representation of structure model in design. Second part (b) contains properties of
the selected element in hierarchy. User can modify, add or delete element specific or
user defined attributes.
The Load default button (c) allows you to restore default settings for current
mapping tab.
a

Figure 32 Structures mapping tab

E. Volumes Settings
This tab contains settings specific for the volumes discipline, used during
generation process.

Volumes -> Settings

This tab contains list of DGNs which be used in volumetric model generation
process.
a
b
c

d
e
f

Figure 33Volume settings tab

a) DGN file name column DGN name without extension.

b) Has DRV column - Information if the DGN file has DRV file in the same
directory.
c) DGN file path
d) Add DGNs from folder button - Showing dialog enabling add DGNs to list.
e) Remove all button - Removing all DGNs from list.
f) Add information from DRV file checkbox If selected, Program will try to read
DRV files related with DGN files and include attributes related with DGN
graphical element to resulting PDMS/E3D model.

Volumes -> Mapping

The tab Volumes -> Mapping is divided into two parts. First part displays PDS
element types which attributes can be mapped (a).Second part (b) allows to add,
remove and modify the mapping for PDMS/E3D element attributes specific with each
element type.
The Setup (c) button is a helping gadget which allows you to get all unique
attributes from selected DRV file, and add these attribute to the Element definition
properties as UDAs. A good practice is to select that DRV file which will actually have
any element attributes of particular type.

The Load default button (d) allows you to restore default settings for current
mapping tab.
a

c
d
Figure 34 Volumes Mapping tab

F. Oracle Dump files to Access DB converter

This tool allows user to convert Oracle database *.dmp file to *.accdb database file
(used in PDS Translator). To convert enter input (a) and output (b) path and click
Convert (c)
a
b

Figure 35 Oracle to Access converter dialog

IV. Appendixes
Using tables alias mapping syntax
PDS translator forces user to assign MTO and Catalogue Extraction tables to aliases
while configuring the input data sources.
Table aliases are helpful when user wants to map processed PDS element attribute
from certain table column to resulting element attribute in PDMS/E3D.
For each table alias there will be number of variables available representing the
column names of table behind its alias.
Example:
For table alias MOD (table 900 in MTO), 13 variables will exist which can be used in
setting the PDMS/E3D elements attribute mapping:
MOD.system_unique_no
MOD.model_index_no
MOD.extract_last_date
MOD.extract_fail_date
MOD.model_no
MOD.discipline_no

Etc.
If table behind the alias will contain any non-standard columns. Those will also be
available as variables.
Important note is that in each table alias variables have their scopes in discipline
mapping user interfaces. So for example, you shouldnt use MOD alias variables
when configuring mapping for Design Structure Elements hierarchy. Or using CRS
(cross section component data for structures) in Piping Catalogue Mapping

hierarchy. Along with table alias variables, there are some special variables available
for specific interfaces such as:
-

AvProjectName Global Variable for which value is taken from project

name in General -> Information settings

AvBranchNo Variable specific for Design Piping Elements hierarchy

mapping, useful when naming branch elements.

AvConnType{number} Variable specific for Catalogue Piping Elements

hierarchy, it contains AVEVA standard connection types translated
using configuration available in General -> Settings bookmark.

It is useful to deduct table alias variables from example usage in default

configurations provided.
Other important notes:
After configuring syntax for name attributes of elements in PDMS/E3D, its possible
that while processing step, application will not generate some elements due to too
long name attribute variables being produced. In that case user needs to reconfigure
the names attribute mappings for problematic elements to somehow shorten the
name attribute values. Also while configuring name attributes values syntax user
should take care about uniqueness of produced names.
In general, careless mapping may result in undefined behavior.

Conversion geometry logic from PDS DGN model to

PDMS/E3D model
Each geometry conversion process begins by checking the type of DGN graphical
element. According to its type, there are various tests which will try to deduce the
equivalent type in PDMS/E3D primitive. Below is shown what conditions must be
fulfilled for DGN geometry element to be translated to particular type of PDMS/E3D
primitive. If the element cant be translated to any primitive, it will be converted to
STL Format and created in destination PDMS/E3D model as GENPRIM element.
The STL format is a 3d representation of geometry in form of triangle mesh.
STL files to PDMS/E3D are imported by using the command IMP $!SatImportPath.
Where !SatImportPath is path to STL file.

A. DGN Cone element

In PDMS/E3D it can be represented as types of cones:
-

Cylinder (SCYL/CYLI)

Cone (LSNO/ CONE)

Snout (LSNO/ SNOU)

Figure 36 Example cone in DGN. Markings on image:

-C1/C2 center point of top or bottom plane.
- R1/R2 radius of top or bottom circle

Below is a table which contains conditions of Cone conversions:

Table 6 Conditions that must be fulfilled, to translate cone from DGN element to proper type in PDMS/E3D

Equivalent in
Element in

Radius R1 and R2
Vector from C1 to

Cone

PDMS/E3D

Conditions to be fulfilled

DGN

are the same.

C2 are parallel to

Radius R1 and R2

bottom and top

arent the same.

circle.

Radius R1 or R2 is
close to zero.

Vector from C1 to C2 arent parallel to

bottom and top circle.

Paragon

Design

SCYL

CYLI

LSNO

CONE

SCON

CONE

LSNO

SNOU

B. DGN Solid element

Solid in DGN contains two type of objects, boundaries and rules.
Boundaries determine shape on first and second plane Rule determine how
boundaries are connected to each other.
The boundaries may contain list of point, line, arcs, shape (set of points).
In DGN Solid element can be translated using two types of strategies:
a) Where rules are lines. In that case, possible resulting PDMS/E3D primitives
will be:
-

Box (LPYR / BOX)

Pyramid (LPYR / PYRA )

Extrusion (EXTR)

Cylinder (SCYL / CYLI )

Figure 37 Example solid in DGN where, rules are lines. Markings on the image:
-R1 R4 rules line
-B1/B2 boundaries

Table 7 Conditions that must be fulfilled, to translate solid (where rules are lines) from DGN element to proper type in
PDMS/E3D

designation in
Element in DGN

PDMS/E3D

Conditions to be fulfilled

Paragon

Design

Boundaries
have the
Boundaries
are
Boundaries

Solid

rectangular.

are parallel

same

LPYR

BOX

LPYR

PYRA

SCYL

CYLI

dimensions.
Boundaries
have the
different
dimensions.

Boundaries are circular.

If the above conditions
aren't met.

EXTR

b) Where rules are arcs. In that case, possible resulting PDMS/E3D primitives will
be:
-

Dish (SDSH / DISH)

Sphere (SSPH / 2xDISH1)

Revolution (REVO)

Circular torus (SCTO / CTOR)

Figure 38 Example solid in DGN where, rules are arcs. Markings on the image:
-C1 / C2 center point of top or bottom plane.
- r1 / r2 radius of top or bottom circle
-R1 R4 rules line
-B1/B2 boundaries
Table 8 Conditions that must be fulfilled, to translate solid (where rules are arcs) from DGN to proper type in PDMS/E3D

Equivalent in
Element in DGN

PDMS/E3D

Conditions to be fulfilled

All rules and

Boundary angle is

boundaries have

180 deg.

Paragon

Design

SDSH

DISH

SSPH

2x DISH1

SCTO

CTOR

common center.

Solid

AND There is a

Boundary angle is

circle in the base

360 deg.
Boundaries have the

Boundaries are

same center.

circular and have

Boundaries havent

the same radius.

same center.
Boundaries are shape and their numbers is
2.

Two Dish with the same center point and radius but different orientation

REVO

C. DGN Surface Element

Surface in DGN contains boundaries and rules same as solid.
Surface with more than one types of rules are converted to STL format. Otherwise:
-

If all rules are arcs, surface is converted same way as solid.

If all rules are lines, below in table are shown conditions to be fulfilled to
convert to correct type.

Table 9 Conditions that must be fulfilled, to translate surface (Where rules are lines) from DGN to proper type in PDMS/E3D

Equivalent in
Element in DGN

PDMS/E3D

Conditions to be fulfilled

Paragon
Boundaries are
Boundaries are

rectangular.

Design

LPYR

BOX

shape and
Surface

their numbers is 2.

Boundaries arent
rectangular.

All boundaries are line.

EXTR

Boundaries are complex shape

D. DGN Shape, Ellipse, ComplexShape Elements

These types in DGN are 2d shapes in 3d shapes, Closest primitive possible to
represent such geometries will be thin extrusions (with minimum height set)
PDMS/E3D.

E. DGN Line, Linestring, Arc, Complexstring, Curve Elements

These types of DGN geometry are converted to PDMS/E3D DRAW elements.