04.1 User Manual PDA5 - 0

User manual for
Plant Design & Allocation 5.0

ABB Switzerland Ltd.
No. of sh.
Prep. SEASY/Z Per-Olov Andersson 2000-01-29
Appr. SEASY/Z Gunnar Arvestål User Manual 93
Resp. dept. SEASY/Z Plant Design & Allocation 5.0
Document number Lang. Rev. ind. Sheet
ABB Automation and Drives 3BSE020288D0005 en A i

TEMPLATE: D2H_NORM.DOT; FILENAME: USER MANUAL PDA5_0.DOC; PRINTDATE: 3/7/2007 6:16:00 PM; SAVEDATE: 3/7/2007 6:15:00 PM
Contents
1. INTRODUCTION..........................................................................................................5
1.1 General ................................................................................................................................................................... 5
1.2 Workflow................................................................................................................................................................ 5
1.2.1 Workflow for PDA administrator ..................................................................................................................... 6
1.2.2 Workflow for PDA user.................................................................................................................................... 6
1.3 Help......................................................................................................................................................................... 8
2. MAIN FUNCTIONS ......................................................................................................8

2.1 Starting up for the first time................................................................................................................................. 8
2.2 New Project ............................................................................................................................................................ 9
2.3 Project Setup ........................................................................................................................................................ 10

2.3.1 Project details ................................................................................................................................................. 10
2.3.2 Supplier........................................................................................................................................................... 11
2.3.3 Document details ............................................................................................................................................ 11
2.4 Revisions............................................................................................................................................................... 12
2.4.1 New revision................................................................................................................................................... 12
2.4.2 Copy revision.................................................................................................................................................. 12
2.4.3 Support Web (not more supported in PDA BM 3.1) ...................................................................................... 13
2.5 General form functions ....................................................................................................................................... 13

2.5.1 View ............................................................................................................................................................... 13
2.5.2 Move and resize fields .................................................................................................................................... 15
2.5.3 Save Form....................................................................................................................................................... 15
2.5.4 Sort ................................................................................................................................................................. 15
2.5.5 Filter By/Excluding selection ......................................................................................................................... 16
2.5.6 Filter ............................................................................................................................................................... 16
2.5.7 Apply/Remove filter ....................................................................................................................................... 17
2.5.8 Saved Filters ................................................................................................................................................... 17
2.5.8.1 Import Filters ........................................................................................................................................... 18
2.5.9 Fill Down........................................................................................................................................................ 19
2.5.10 Series Fill Down ........................................................................................................................................... 19
2.5.11 Undo Fill Down ............................................................................................................................................ 20
2.5.12 Replace ......................................................................................................................................................... 20
No. of sh.
ABB Automation and Drives 3BSE020288D0005 en A i

2.5.13 Expression Builder........................................................................................................................................ 20
2.5.14 Copy Paste .................................................................................................................................................... 22
2.5.15 Sub Forms..................................................................................................................................................... 22
2.5.15.1 How to build new subforms................................................................................................................... 23
2.5.16 Freeze Columns ............................................................................................................................................ 23
2.5.17 Find............................................................................................................................................................... 23
2.5.18 Select File(s) to Work With .......................................................................................................................... 24
2.5.19 Navigator (no more Supported in PDA 3.1) ................................................................................................. 24
2.5.20 Filtering Reports ........................................................................................................................................... 24
2.5.21 Compact database ......................................................................................................................................... 25
2.5.22 Default Values .............................................................................................................................................. 25
2.6 Import................................................................................................................................................................... 26
2.6.1 Supplier Data format....................................................................................................................................... 26
2.6.1.1 Importing data including I/O allocation................................................................................................... 26
2.6.2 Select Files to import ...................................................................................................................................... 26
2.6.3 Merging files................................................................................................................................................... 28
2.6.4 Preview data ................................................................................................................................................... 29
2.6.5 Mapping.......................................................................................................................................................... 30
2.6.5.1 Automatic mapping ................................................................................................................................. 31
2.6.5.2 Manual mapping ...................................................................................................................................... 31
2.6.6 Export data to file ........................................................................................................................................... 31
2.6.7 Add new fields in customer data..................................................................................................................... 32
2.6.8 Add new field in Database.............................................................................................................................. 32
2.6.9 Test Structure.................................................................................................................................................. 34
2.6.10 Error log........................................................................................................................................................ 34
2.6.11 Suggested procedure for mapping form use ................................................................................................. 35
2.6.11.1 Importing revised customer data............................................................................................................ 36
2.7 Validation ............................................................................................................................................................. 36
2.8 Compare ............................................................................................................................................................... 38

2.8.1 Merge revisions .............................................................................................................................................. 40
2.8.2 Compare I/O allocation................................................................................................................................... 41
2.9 Edit data ............................................................................................................................................................... 41

2.9.1 Copy I/O allocation......................................................................................................................................... 41
2.9.2 I/O allocation .................................................................................................................................................. 42
2.9.2.1 Controller Level....................................................................................................................................... 43
2.9.2.2 S100 Boards............................................................................................................................................. 43
2.9.2.3 Reports showing I/O allocation ............................................................................................................... 45
2.9.2.4 S800 Boards............................................................................................................................................. 46
2.9.2.5 Labels for S800 I/O ................................................................................................................................. 46
2.9.2.6 Not connected Boards.............................................................................................................................. 47
2.9.2.7 Signal Pool............................................................................................................................................... 48
2.9.2.8 Allocate Signals to Boards....................................................................................................................... 49
2.9.3 ADG (no more supported in PDA BMI 3.1)................................................................................................... 49
2.9.4 Board .............................................................................................................................................................. 50
2.9.4.1 Board Info................................................................................................................................................ 50
2.9.4.2 Import Board Types ................................................................................................................................. 50
2.9.4.3 Connection Unit....................................................................................................................................... 52
2.9.4.4 Import Connection Unit Types ................................................................................................................ 52
2.9.5 Generate Signals ............................................................................................................................................. 53
2.9.5.1 Signal Library .......................................................................................................................................... 53
2.9.5.2 Import Signal libraries from other projects.............................................................................................. 54
No. of sh.
ABB Automation and Drives 3BSE020288D0005 en A ii

2.9.5.3 Abbreviation ............................................................................................................................................ 55
2.9.5.4 Process Objects........................................................................................................................................ 57
2.9.6 Signal.............................................................................................................................................................. 59
2.9.7 Soft Signals..................................................................................................................................................... 60
2.9.8 Loops .............................................................................................................................................................. 60
2.9.9 Solutions ......................................................................................................................................................... 61
2.9.9.1 Build and Export Scriptfiles .................................................................................................................... 62
2.10 Budget................................................................................................................................................................. 63
2.10.1 Signal budget ................................................................................................................................................ 64
2.10.2 Spare Calculation.......................................................................................................................................... 64
2.11 Export ................................................................................................................................................................. 65

2.11.1.1 Export Revision ..................................................................................................................................... 65
2.11.1.2 Export Table/Query ............................................................................................................................... 66
2.12 Control Builder M Interface............................................................................................................................. 68

2.12.1 Project defaults ............................................................................................................................................. 68
2.13 System Administration...................................................................................................................................... 69

2.13.1 Security......................................................................................................................................................... 69
2.13.2 General ......................................................................................................................................................... 69
2.13.3 Agree on the data format and contents with the Customer/subcontractor .................................................... 70
2.13.4 Create a new database................................................................................................................................... 70
2.13.5 Add new fields to the database. .................................................................................................................... 70
2.13.5.1 Import Object......................................................................................................................................... 71
2.13.6 Create new validation queries....................................................................................................................... 71
2.13.7 Create new forms.......................................................................................................................................... 72
2.13.7.1 Rebuild Form(s)..................................................................................................................................... 72
2.13.8 Create new reports ........................................................................................................................................ 73
2.13.9 Create new queries........................................................................................................................................ 74
2.13.10 Add new Forms, Reports and Queries into PDA ........................................................................................ 74
2.13.11 Fill in budget values for the agreed number of Signals .............................................................................. 75
2.13.12 Distribute project specific forms and reports to project members .............................................................. 75
2.13.13 File location ................................................................................................................................................ 75
2.13.14 Create Category .......................................................................................................................................... 76
2.13.15 Compact Database ...................................................................................................................................... 77
2.13.16 Data structure.............................................................................................................................................. 77
3. APPENDIX.................................................................................................................78
3.1 Supplier Data ....................................................................................................................................................... 78
3.1.1 Instrument schedule ........................................................................................................................................ 79
3.1.2 I/O schedule/ Signal........................................................................................................................................ 79
3.1.3 I/O allocation / Node, Bus, Station and Board................................................................................................ 79
3.1.4 Software specification / Loop ......................................................................................................................... 79
3.1.5 Definition of fields.......................................................................................................................................... 80
3.1.5.1 List of attributes....................................................................................................................................... 80
3.1.5.2 Data types ................................................................................................................................................ 80
3.1.6 Handling Revised Customer Data................................................................................................................... 80
3.2 Validation Queries............................................................................................................................................... 83

3.2.1.1 Boards...................................................................................................................................................... 83
3.2.1.2 Bus ........................................................................................................................................................... 84
No. of sh.
ABB Automation and Drives 3BSE020288D0005 en A iii

3.2.1.3 Loops (MOD only) .................................................................................................................................. 84
3.2.1.4 Process Objects........................................................................................................................................ 86
3.2.1.5 Node......................................................................................................................................................... 86
3.2.1.6 Signals ..................................................................................................................................................... 87
3.2.1.7 Soft Signal ............................................................................................................................................... 89
3.2.1.8 Signal path ............................................................................................................................................... 89
3.2.1.9 Station...................................................................................................................................................... 89
4. GLOSSARY OF TERMS............................................................................................90
5. INDEX ........................................................................................................................91
No. of sh.
ABB Automation and Drives 3BSE020288D0005 en A iv

1. Introduction
1.1 General
Plant Design & Allocation 3.1 can import customer data in Excel or Lotus
format, and map it to internal PDA names. PDA can also validate and
compare the different versions of data, coming from customer or created
during the engineering process.
The output from this tool is OCS data for AEW. In AEW the data is used
to build up the OCS structure in STB and to add parameters in PAR.
It is also possible to export/import data directly to/from FCB, using a .bax
file.
There is also an output to ADG/CAD to automatically build circuit
diagrams in AutoCAD.
For MOD users scriptfiles are built with parameters for Typical Solutions
in Engineering Station.
The flexible export can also be used to downstream Design & Production
processes.
1.2 Workflow
The workflow below is only to be seen upon as a sample of how to use
the tool. There are a lot of different options depending of the scope of
delivery etc.
To make the use of the tool effective and to achieve a common way of
working each LABB is recommended to make their own workflow
describing how to use the tool.
There are two different workflows described.
The first workflow describes the administrative part and that is done by
the PDA administrator.
The second workflow describes a possible workflow for the engineer
using PDA.
ABB Automation and Drives 3BSE020288D0005 en A 5

1.2.1 Workflow for PDA administrator
Below you will find a sample workflow for the administrator. All items
are optional and the items can be performed in almost any order.
Libraries User Interfaces etc.
Solutions for Forms

Build and maintain the solutions Build new forms and maintain
PDA. These solutions are used standard forms to suit the
generate scriptfiles for needs.
solutions in AS500ES
only).
Reports
Build newreportsand
Solutions in Signal the standardreportsto suit the
Build and maintain solutions project needs
PDA. The solutions are used
generate signals based on
Objects.
Validation
Select the validationqueries to use
in the project. Add project specific
Board queries.
Maintain the library of board
and Connection unit types and
needed add new board types for
project.
Project specific
Define the attributes needed for
different categories of data,
adding project specific attributes
the standard set of
1.2.2 Workflow for PDA user

Below you will find a sample workflow. Many of the items are optional
and are depending of scope of supply. Some of the items may be repeated
at different stages of the working process, e.g. validation will be
performed both after import and after doing the I/O allocation.

Setup Project & Incorporate Engineering Output
Data
New Project Generate Signals CBM Integration

Create a new database to store Generate signals based on Export IO Hardware, Signals,
the project data in. Process Objects and Library Groups and Process Objects to
objects. the 800xA Control Builder.
Exchange Format
Define the attribute names and I/O Allocation
data types for exchange of data. Allocate Signals to Boards.
Generate Circuits
Generate circuit diagram
Project Details Bulk Data handling (Consumer Circuits) showing the
Fill in general information for Add and edit Board data, Signal complete wiring signal and
the project, like e.g. document data and Process object data, power of an object (e.g. Motor,
headers. using the special designed bulk or Transmitter)
data functions in PDA.
Import
Import data in Excel, Lotus
Flexible Export
format or from HDRS I/O calculation Export data in flexible format
Check the quantity of I/O’s and e.g. to feed local tools.
Mapping compare them to the budget
Map customer attribute names to figures
internal PDA names.
ELCAD Consumer Circuits
Copy Revision Define Circuit Templates,
Use this function to create and Process Object and Signal
archive copies of data to always Parameters used to generate
have the original Customer data drwaings for ELCAD.
available to e.g. compare
revisions. (see: PDA BMI 3.1 User Manual
for details)
Validate
Validation of data. Reports can
Sofware Design for Control
be printed out, showing the
Builder M
detected errors from the
Define SW Libraries and
validation. It is also possible to
view the errors in List format Parameters for the Control
Modules to be created.
and directly correct them.
(see: PDA BMI 3.1 User Manual
Compare for details)
Compare different versions od
data to detect changes, e.g. detect
changes in customer data from
one revision to another.

1.3 Help
To help you to use Plant Design & Allocation there is some help
functionality available. This document is a description of how to handle
the application and it is structured in the same way as the application is
structured. The best way to use this manual would be to have PDA
running on a PC as you read this manual. There are a lot of pictures in the
manual that you recognise if you run the application e.g. all forms are
available in the help file. This document is available as a Microsoft Word
document named PDAHELP.DOC. All documentation is available for
download on the support Web. The easiest way to get to the support web
is to use the hyperlink available in PDA, at the bottom of the main menu.
To view the online-help in PDA press the F1 key. This will take you to
the page that is relevant to the form in which the cursor is currently
placed. The online-help is based on the same text as this manual.
It is also possible to click the icon above to start the online-help in PDA.
Use Index or Contents to find the information that you are looking for.
Note!
The Help available from the Help menu is the normal Microsoft Access
Help, that also can be very useful.
2. Main functions
2.1 Starting up for the first time

On starting the PDA for the first time the first thing to do is to set-up the
file locations. Selecting the Project Detail TAB, at the top of the PDA
Menu form, displays a form with the button that is used for this
File Location

This form is used to define default locations. The default paths are e.g.
used when browsing for files to import etc.
Export To, Default path for Export, e.g. when exporting data in Excel
format
Import From, Default path for Import, starts at this location when
browsing for customer data
Project-data, Default paths for new projects
Systemfiles, Location of the application database (pda_3_1_2002.mdb)
Note: For other file types see: PDA BMI 3.1 User Manual
2.2 New Project
Use New Project button under Project Detail tab, to create a new project.
Select type of project. Two types of project templates are delivered with
PDA, MOD 300 and Master. There can also be locally built templates that
e.g. have been modified to suit a specific Business.
Browse to the path where you want to store the project and enter project
name in the File name field, (the extension “.mdb” will be filled in
automatically), then select Open.
By default the project will be stored as setup in file locations above (in
c:\pda\project, as delivered, but it is up to the user where to store it). If
more than one person wants to work with the same project, store it on a
network disk.

Use Select Project to select an existing project to work with. Either
double click on the database (.mdb) file or single click and then select
Open.
The selected project path and filename will then appear in the window
above the buttons.
2.3 Project Setup
This form is used to set up Document Header/Footer and suppliers.
2.3.1 Project details
Use this form to fill in data to be used in headers and footers of the reports
and forms.
If the project has multiple order numbers there are two options, either
leave the field blank and fill in order number in the cover sheet instead or
correct the field before printing out a report.

2.3.2 Supplier
Fill in Suppliers from which data shall be imported.

Note!
The predefined supplier System that already exists should be left in place.
The description field for Supplier could e.g. be used to fill in which type
of data the supplier is supposed to supply. The purpose of filling in the
supplier is that mapping of customer names and internal names are stored
with the supplier. Next time data is imported from the same supplier the
default mapping is the mapping used previously, for the same supplier.
2.3.3 Document details
This form allows the user to change the titles, document number and
revision Id etc. for the reports.
Note!
It is only reports where Dockind is Report that are valid. The other reports
are for internal use ore use header data from another source. Locally built
reports will also be available in this form.
Field Name Description Label in footer
ObjectName Name of the report in PDA
Doc_Id Unique identification of a document Doc.No.
Approved Dept. and name of person that has approved document Appr.
DocKind Classification of document to it’s content and form of present. Doc.Kind
Title1 Title of document Title (row1)
Title2 Title of document Title (row2)
Prep Department of person who created doc. and date when created Prep.by
Based Number of source document when applicable Based On
Status Revision status Appr.
Designation1 Document designation 1 See 9ADA354 Doc.Des. (row1)
Designation2 Document designation 2 See 9ADA354 Doc.Des. (row2)
IDesignation 1 Item Designation 1 ItemDes. (row1)
IDesignation 2 Item Designation 2 ItemDes. (row2)
Rev Revision index Rev.Ind

2.4 Revisions
The PDA can work with multiple revisions of project data for each
project.
Make sure you select the correct project and revision before working with
the data. The revision can be selected from any tab in the main menu.
Current revision, the current revision, use drop down menu to select
another revision. Double-click in the field to be able to change the name
of the revision.
Created Date/Time, date and time when the revision was created and
also the username
Description, a description field to make it easier to distinguish between
the revisions
2.4.1 New revision
Select New Revision to create a new, empty, revision Index.
The default value for the Revision Note follows the ABB standard
starting with "-" and then A, B…. Etc. You can change the Revision Note
to anything you want to use by double clicking in the Current Revision
field. You can change to a different revision by selecting the drop down
menu in the Current Revision field.
You may wish to create new revisions when you import new customer
data or when you reach a freeze point in the project and you want to issue
data for downstream activities.
2.4.2 Copy revision

This function is used to make a copy of the selected revision. The purpose
of this is to separate the original requirements and the changes. It is up to
the user if changes are done directly to customer data or not.

If the customer's revision is called A the new revision will as default be
called A/1 to make clear as to which revision it belongs. The new revision
will automatically become the current revision. By using the Select
File(s) to Work with form the copy can be limited to the selected files.
It is advisable that immediately after an import activity, have a copy of
the imported revision made and work continued on the copy. The original
imported revision can then be kept as an archive copy for comparison
purposes etc.
The “Copy I/O allocation” form will allow you to copy data from an old
revision to a new/empty revision. Alternatively data can be exported from
the old revision and then re-imported into the new revision.
2.4.3 Support Web (not more supported in PDA BM 3.1)
2.5 General form functions

To support flexible forms and powerful bulk data handling a set of
functions are available in PDA. The functions can be found using right
mouse button in the current form. Only the functions available for that
specific form are visible.
2.5.1 View
The view function enables building flexible views of the forms to work
efficiently. The views are built up per form so the views will differ from
form to form. Some views are delivered with PDA but it is also easy to
add project specific views and even personal views.
The views include both filters and layout of the forms. E.g. in the I/O
allocation form it could be useful to build a view showing not allocated
analogue input signals. This view could then include a filter showing only
not allocated analogue input signals. The view could then only show the
fields that are interesting in this specific project, sorted and ordered in an
efficient way for a specific operation.

Selecting a view e.g. “AI Signals not allocated” will show all unallocated
analogue input signals and the valid fields for that type of signals.
<Refresh List> is used in forms including subforms e.g. the I/O
allocation form, to refresh the available view depending on which form is
current. Click in the form where you want to apply a view, select
<Refresh List> to show the available view for the selected form.
<Clear Filters> will keep the selected layout of the form but remove the
filter if there are any. E.g. if Clear Filters is selected using view
“Unallocated AIS” all signals will be available but the layout will be the
same. To add the filter again simply select “Unallocated AIS” again.
<Modify Setting> is used to modify views or to build new views. The
following form will pop up.
Select the fields you want to see , the All/None buttons can be used to
speed up the selection. Select Update View to modify the view according
to the changes done. If the form is closed without selecting Update View
the screen will still be updated with the modification but the view will not
be updated. This could be useful for temporary changes.

Views can be imported from libraries or other projects by selecting import
on right mouse button in this form, click in the grey area of the form.
Delete view is used to delete views that are not to be used any more.
Create View is used to build up new view for different operations. The
proposed workflow for building a new view is as follow.
1 Build up the filters and sorting using the Filter by Selection or Filter
functions and the sort function, to show the valid records for the view.
2 Select <Modify View> to get into the above form. Select the columns
to be shown.
3 Select Create View and type in the name of the new view at the
bottom of the form and then close the form.
4 Modify the order of the fields and the size of the fields in the
displayed view. Then select <Modify Setting> and Update View to
save these settings to the view.
Step 1 and 4 are optional if all records are to be shown and the standard
length and order of the fields are to be used.
2.5.2 Move and resize fields

All fields can be moved around and resized or hidden to suite different
purposes. To move Field(s) Select the header of the Column(s) to move
and drag the fields with the left button of the mouse activated. To resize
columns left-click the right side of the column header and drag it to
correct size or double-click it to automatically size it to fit.
Note!
If a form do not seem to have been updated/refreshed then use the F9 key
(refresh). The Refresh command updates only data that already exists in
your datasheet or form. It doesn't reorder records, display new records, or
remove deleted records or records that no longer meet the specified
criteria. To perform those actions, requery the records by pressing
SHIFT+F9
2.5.3 Save Form
Use Save Form to save the form settings e.g. the location of a subform. It
can be found under Forms Setting... in right mouse button menu.
To save the settings to the view use the view <Modify Setting>.
2.5.4 Sort

Sort Ascending. Sorts records based on the selected column(s) in
ascending order (0 to 9, A to Z), subsequent sorts replace previous sorts.
To undo a sort, choose Apply/Remove Filter.
Sort Descending. Sorts records based on the selected column(s) in
descending order (9 to 0, Z to A). If more than one column is selected the
sorting is done is done on all columns starting from the left column.
Subsequent sorts replace previous sorts. To undo a sort, choose
Apply/Remove Filter.
2.5.5 Filter By/Excluding selection
Filter By Selection, right-click on the value to be filtered by. A click on

e.g. SignalType DIS will show all signals of that type.
Filter Excluding selection, right-click on the value to be excluded in the
filter. A click on e.g. SignalType DIS will show signals of all types
except DIS e.g. DOS, AOS and AIS.
2.5.6 Filter
Filter function is used to build more complex filters than Filter by

selection. Right-click on the field that you want to build a filter on and
select Filter. Filter can be built on more than one field.
The first field shows the field to build the filter on, as default the field that
was selected when the filter was activated from will be used. The second
field shows to operator to be used with the criteria, the following fields
are available.

The last field is used for the criteria. In the sample above all SigTags
starting with either H1 or H2 will be shown. If more than one expression
is defined for the same column it is an OR criteria between the
expressions as in the sample above.
By Criteria will activate the filter.
Use Show all filters to show all active filters on any field, including
filters belonging to the selected view. All filters built or activated from
here will be available from Filter Save function.
If more than one column is filtered there is an AND criteria between the
columns. If e.g. SigTag is filtered for DIS and Node for N1, only signals
that fulfil both criteria’s will be shown.
2.5.7 Apply/Remove filter
Use Apply/Remove filter to remove all active filters or to apply the last
used filter if there are no filter activated. If a filter is activated a text string
Filtered is shown to the right of the record selector in each form.
Note!
If two different subforms are filtered and then one of the filters is
removed, then the text filtered will be removed in both sub forms. This
can be very confusing since the subform is filtered but it is not indicated
that this is the case. This is a bug in Access. Click Apply/Remove filter
in the subform where it is missing, to see the text filtered again.
2.5.8 Saved Filters
The Saved Filters function makes it possible to save filters and to be able
to reuse them. It can be very time saving to build up a set of filters for
different frequent operations.

As soon as the Filter function is used the above form is updated. If Filter
By/Excluding Selection is used this form will only be updated if the
Filter function is opened and criteria button is pressed. Also the sorting
functions can be included in the filters but also here it will only be
updated if the Filter function is opened and criteria is pressed.
Description, used to name filters that are to be reused
Add Filter, a double-click in this field will add the selected filter to the
current filter. The contents of the field is the filter in SQL format, built up
as described above
Replace Filter, a double-click in this field will replace the current filter
with the selected filter. The contents of the field is the filter in SQL
format.
Order By, sorting order. All filters are stored locally per user but it is
possible to import filters from other user by using Import From
described below.
The Saved Filters function can be used in combination with the View
function. If there is a filter included in the view e.g. for DI signals the
Saved Filters will be added to these filters.
2.5.8.1 Import Filters

The Filters can be imported from other projects or from specific Library
projects.
Select Import From right-button menu.

Use Browse to select the project to import from.
Overwrite Record determine if the imported objects shall overwrite the

existing objects in case they already exist. If a duplicate is detected during
import and Overwrite is not selected an error message will appear
informing you that the object not will be imported.
Select button will show all available objects of the correct type in the
selected database.
2.5.9 Fill Down
A function to fill down a value from current record to all records below.
Right-Click the value to be used and select Fill Down, all records below
the current record will be updated. Use this function in combination with
the filter and sorting functions to only update a limited number of records.
Use Undo Fill Down undo the last Fill Down.
If it is not possible to undo the operation a popup message will appear
before the Fill Down is performed to make it possible to cancel the action.
The function also works with combo boxes and check boxes.
2.5.10 Series Fill Down
A function to fill down a value from current record to all records below
and at the same time increase the value with 1. Right-Click the value to be
used and select Series Fill Down, all records below the current record
will be updated. If Series Fill Down is used on value such as X20:1 the
records below will get the values X20:2, X20:3 etc. Use this function in

combination with the filter and sorting functions to only update a limited
number of records. Use Undo Fill Down undo the last Fill Down.
If it is not possible to undo the operation a popup message will appear
before the Fill Down is performed to make it possible to cancel the action.
2.5.11 Undo Fill Down
Use Undo Fill Down to undo the last Fill Down or Series Fill Down
performed. If during the Fill down operation, the system detects that it is
not possible to undo the operation a popup message will appear before the
Fill Down is performed to make it possible to cancel the action.
2.5.12 Replace
The Replace function can be used to replace strings or part of strings in a

field.
In the sample above the string CLOSE is replaced with OPEN, since
Match Whole Field is not selected it will find strings where CLOSE is
only a part of the string e.g. OP_CLOSE will be changed to OP_OPEN.
It is also possible to look for spaces, or any other characters or strings,
within a text field and replace or remove them.
For example to remove spaces: click in correct field and open replace
function; make sure “Match Whole Field “ is not ticked; type a space into
the Find What; field do not type anything in the Replace With; field
then press Find Next - Replace. This is very useful for removing spaces
from fields where space might lead to problems.
2.5.13 Expression Builder
Expression Builder is used to update values in a field using Access

standard expressions. It is also possible to place the values in a calculated
field instead of updating an existing field.

Foe example the expressions can be used to e.g. combine fields or to
divide one field into two fields. To select a function double-click on the
functions and fields to be used in the expression, make sure to follow the
syntax that appears after selecting a function.
The last used expressions are available to select from the dropdown menu
in the field where the expressions are built up.
LEFT, returns a Variant (String) containing a specified number of
characters from the left side of a string.
RIGHT, returns a Variant (String) containing a specified number of
characters from the right side of a string.
MID, returns a Variant (String) containing a specified number of
characters from a string.
NULL, gives the field the value NULL
INSTR, Returns a Variant (Long) specifying the position of the first
occurrence of one string within another.
IIF, Returns the result one of two expressions, depending on the
evaluation of a conditional expression. The first expression is used if the
criteria is true.
VAL, Returns the numbers contained in a string as a numeric value of
appropriate type.
STR, Returns a Variant (String) representation of a number.
CHR, Returns a String containing the character associated with the
specified character code.
STRING, Returns a Variant (String) containing a repeating character
string of the length specified.
SPACE, Returns a Variant (String) consisting of the specified number of
spaces.
TRIM, LTRIM, RTRIM, Returns a Variant (String) containing a copy
of a specified string without leading spaces (LTrim), trailing spaces
(RTrim), or both leading and trailing spaces (Trim).
TIME, Returns a Variant (Date) indicating the current system time.
DATE, Returns a Variant (Date) containing the current system date.
UCASE, Returns a Variant (String) containing the specified string,
converted to uppercase.
LCASE, Returns a String that has been converted to lowercase.

FORMAT, Returns a Variant (String) containing an expression formatted
according to instructions contained in a format expression.
For more detailed information regarding the functions use MS Access
help, which can be found in the Help menu.
Calculated fields, is a function that makes it possible to add a field in the
form where the value in the field is based on the expression built up in
Expression builder. Build an expression that gives the wanted result, in
the sample above the calculated field EN_H2 will be “1” if HI_LIM2 is
not Null.
Select Calculated Field and type in a suitable name for the field in
FieldName, press enter and the OK button.
Close the current form and select Rebuild Form from Template before
opening the form again, the new calculated field will then be available by
selecting in the wanted view.
Any existing calculated fields can be modified or deleted using
Expression builder. The form must be rebuilt after each change.
2.5.14 Copy Paste
The name PDA Copy/PDA Paste indicates that this is not a standard
copy paste function.
The PDA Copy function makes it possible to copy one or more signals,
Loops or Process Objects. The copy can be done within the same revision
or between revisions in the same project.
Use the record selector to select the signal(s) to copy, click the right-
mouse button and select Copy Signals. The selected signals will be
copied and the signal Name (SigTag) will have the same name as the
copied signal(s) with a “$” added in the beginning. Filter for signals like $
and give the copied signals a correct name.
Warning do not use [Ctrl] +[C] to copy signals, Loops or Process Objects
it will not work.
2.5.15 Sub Forms
The Sub Form function (that can be found under Design..) makes it
possible to view selectable subforms from the main forms. PDA will be
delivered with some subforms e.g. in Process Objects form and I/O
allocation form and then it is up to the administrator or user to build
subforms suitable for the local organisation.

To activate existing subforms just select SubForms with a right-mouse
click in a form that contains subforms e.g. I/O allocation form and select
the subform(s) you want to see. When the subform first is opened another
record has to be selected in the mainform to show something in the
subform.
The subforms can be minimised and resized, the size and location will be
remembered if Save Form is used. Save Form can be found in right
mouse button menu under Forms Setting.. Close the form by deselecting
it in the Subform field select.
2.5.15.1 How to build new subforms

The first step is to build a suitable subform, which is a standard Access
form. The form must be built on a separate query, it will not work
correctly if the query is included in the form. A recommendation is to
name the form Subform:+ descriptive name to be able to identify the
subforms.
Select Sub Forms from the right-mouse button menu.
Select, select if the subform shall be visible or not.
Datasheet, select if the subform shall be shown in Datasheet view or
Form View, the recommendation is datasheet view.
Sub Form name, select the sub form to use, all forms are available
SubKey1, select the field to be used for the relation to the main form, all
fields for selected subform are shown
SubKey2, the second SubKey if more than one key is to be used
MainKey1, select the field to be used for the relation to the Sub form, all
fields for selected Main form are shown. The values must be the same as
in the subform to build up the relation, the field names do not have to be
the same.
MainKey2, the second MainKey if more than one key is to be used.
2.5.16 Freeze Columns

Use Freeze on the toolbar to freeze the selected columns on the left side
of the window to prevent them from scrolling off the screen.
2.5.17 Find
Use Find in the toolbar to search for a string, such as Signal tagname in a
datasheet or form.
Some of the above functions can be activated both from the right-mouse
button, the toolbar or the menu.
The recommendation is to use the right-mouse button menu where
available, to activate the functions. By using the right-mouse button menu
it is always clear in the current form, which menu options exist.

2.5.18 Select File(s) to Work With
The Select File(s) to Work With makes it possible to filter which “Files”
to work with in the forms, as default all files are selected. If the project
has two different suppliers of data, this filter can be used to only work
with signals from one customer at the time during the I/O allocation.
2.5.19 Navigator (no more Supported in PDA 3.1)
2.5.20 Filtering Reports

It is possible to filter all the available reports. The function makes it
possible to add a user defined filter on any of the reports. Select Filter in
the right mouse menu in the print preview form.
Description, is used to give the filter a name. Use the record selector at
the bottom of the form to switch between the existing filter for the report.
The filters are saved per report.
FieldName, the name of the field to filter on. This is the name in the
query and it can differ from the name in the report.
Operator, the operator to be used for the criteria.
Criteria, the criteria.
Clear/Apply Filter, is used to switch between with and without filter.

Use above filter, activates the selected filter. Examine the result in the
report before printing it.
2.5.21 Compact database

To maintain the performance the databases should be compacted on a
regular basis.
This menu item can be found beside

the starting icon for PDA 3.1. This function is open for all users and it
will repair and compact the application database.
2.5.22 Default Values

This function enable you to define temporary default values to be used
when updating the data. Double-click in the field where you want to use
the default value.
The default values can be either text that is directly typed in or

expressions that pick up values from the other fields in the form. To use
Expressions select Build Expressions from the right mouse menu in the
above form.
To use the default values just select the default value to use and then
double-click in the field where to paste it. The default values are stored
per field per form and can be reused when ever you want.
Signal, shows all available signals. Can be useful when using signal
names in Process objects or Loops. If
Pro.Obj, shows all available Processobjects. Can be useful when using
Process object names in Signals or Loops. If [Process].[Name] is used in
the Build Expressions it will pick up the value from this field.
Node and Filter, is used to show only a limited number of Signals and
Process Objects. If [Signal].[SigTag] is used in the Build Expressions it
will pick up the value from this field.

Default Value can be used in combination with Fill Down and Series
Fill Down and will then take the values from the selected default value.
2.6 Import
2.6.1 Supplier Data format

The PDA requires that import data is of a specified format (see appendix
1) to pass the PDA internal validation checks and ensure that the data
relationships within the PDA are correct.
It is important that the rules given in appendix 1 are followed.
• If supplier is providing I/O schedules only then signals only would be
imported.
• If supplier is providing Loop data, Loops and Signals must be
imported with cross-reference in signals to Loops. The field
LoopName in Signals shall include the Loop that the signal belongs to.
• Make sure that the customers data field names do not include illegal
characters i.e. “spaces”, “/” and “.”. Also during the import do not use
these characters if you create new fields.
2.6.1.1 Importing data including I/O allocation

To import data including I/O allocation follow this procedure:
First import the Board data that should include a unique identity of the
board. The unique identity of the board have to be built up by using one
or more of the following fields, Node (Controller), Bus (LAN), Station
(if S800 I/O) and Designation. If all fields are filled in then the OCS
structure will be built up completely but if e.g. only board Designation is
used the signals still will be allocated to the boards but the Node, Bus and
Station will have to be added in PDA.
During import select Aut.Gen. Structure in the mapping form to
automatically build up the Node, Bus, Station structure.
The next step is to import the Signal data. Signal data must include the
same unique identification as for the Board, using one or more of the
fields, Node (Controller), Bus (LAN), Station (if S800 I/O) and
Designation. Channel have also to be included.
2.6.2 Select Files to import

Before you start importing data, make sure you have selected the correct
project and revision.
ImportObject is used to define which type of data you are about to
import e.g. Signal data or Board data etc.
Supplier defines the supplier for current category, the PDA will then
identify which mapping for customer names to internal names to use,
providing this category/supplier combination has been used previously. If
this combination of category/supplier has not been used before, then you
will create the mapping in one of the next stages.
Use Browse to select the FileName to import. Select the file you wish to
import and press the Import button. The Following formats are possible to
import, Excel (*.xls),and Lotus (*.wk?). If you want to import other
formats please import the files to Excel first and save them in Excel 5.0
format.
It is possible to have more than one supplier per category and also more
than one file per supplier. The combination of Category +Supplier
+Filename must be unique. In most of the forms in PDA it is possible to
choose to work with all files or only one file at the time. This makes it
possible to e.g. do I/O allocation only on signals from one file. As default
all files are included.
Note!
SigTag have to be unique within the whole revision, not only within a
file.
The Description field can be used to describe the imported files.
Once you have selected ImportObject, Supplier and FileName the
Select will be marked up. If you proceed past this point, but then return to
it later, you will have to manually tick select”. You can now proceed to
the next stage by selecting the Next button.

Once a file has been successfully imported or signals have been created
in PDA, the Imported field will identify this by showing a tick.
To delete all data in PDA coming from a file that has been imported,
select the file to delete using the record selector for the file and then press
the delete button.
To delete a whole revision, use the form record selector and then press the
delete button. Deleting like this will remove all data for the file selected
from the current revision of the project. You may wish to do this if you
have made a mistake in the import and want to re-import the data.
View Mapping will bring up the following form.
In this form it is possible to view the default mapping. It is also possible

to delete mapping that has been done by mistake. Use record selector to
select the rows to delete and press the Delete key.
HDRS Import is used to directly import data from HOLCIM HDRS
Database.
2.6.3 Merging files
Merge files is used to merge two files into one

file. The function can be used if some signals have been created as if
supplied by system and these signals should have belonged to a specific
supplier.
Select the file to merge from and select Merge Files. The merged file will
as default inherit the File Name and description from the target file
selected to merge into.

2.6.4 Preview data
In the listbox Spreadsheet type different versions of Excel or Lotus can

be selected for the file to be imported
First line includes fieldnames is selected as default, deselect it if the
fieldnames are not included in the file.
Range is to be used if only a part of the file shall be imported. In the
bottom of the form you can scroll through the contents of the file to
determine the format.
If Back is chosen nothing is imported and you will go back to the
previous screen. Select Next to go to next step of the import procedure
where the mapping is defined.

2.6.5 Mapping
In the upper part of this form you can see the customer data with the
customer attribute names. The lower part of the form is used to perform
the mapping of customer names to PDA internal names.
By using the filter function it is possible to import only a part of the data.
Only the visible data will be imported.
It is possible to modify the customer data during import into PDA.
Examples of possible operations:
• Split one column into two or more columns.
• Concatenate two or more fields into one field.
• Update values using the Expression Builder or doing it manually. E.g.
if Loops and Signal data is mixed the same file the file can be
imported twice, first to import the Signal columns and then to import
the Loop values. This can also be useful if customer I/O allocation is
provided as a signal list only.
Mapping is used so that the customer can use different field names to
those in the PDA, thus the PDA Queries, Forms, and Reports can remain
consistent for different projects, customers, and suppliers. Also, because
the mapping is stored, data validation reports (see later) can be printed
using customer names or internal names.

The mapping is stored for each category/supplier combination. After the
initial mapping has been done all subsequent imports using the same
category/supplier combination will automatically display the previously
used mapping. If on a subsequent import you decide not to import a
previously imported field then the mapping for this field will remain as
per the previous import. Also if you mistakenly map a customer field, that
you do not want to import, use View Mapping button to delete a mapping.
2.6.5.1 Automatic mapping

If the customer field corresponds to the field name used by PDA, the
mapping will be done automatically. Be careful to check that the customer
fields are used for the same purpose as the internal fields. The purpose of
the fields inside PDA is described in the description field. The fields do
not have to be in any specific order. The automatic mapping can be
changed manually.
2.6.5.2 Manual mapping

Customer field names that do not have any corresponding field names in
PDA have to be mapped manually using the Internal Name combo box.
There are a number of free fields that could be used to import attributes
that do not have a pre-defined function within the PDA. Fields that are
not mapped will not be imported into PDA.
The next time an import is done from the same supplier the mapping will
be automatically filled in and no further mapping is required, as long as
no changes have been made to the format.
Data type and length will be checked during import. If Write Error Log
is not selected and data of wrong data type or length is detected during the
import the user has three options, skip field, skip row or interrupt the
import. If Write Error Log is selected the errors will appear in the
error log.
2.6.6 Export data to file
It is possible to manipulate customer data at this stage of the

import. By using the Filter/Update function on the upper form fields can be
concatenated, truncated etc. Use the Export Data button to save the changed file
in the chosen file format before importing it. The purpose of saving the customer
data as this stage could be to make it possible to store the changes done before
importing the data. So if you have to go back you can import from this saved
file, containing the changes, rather than import from the original file and re-do
all the changes.

Select format for the file e.g. Excel format. Select location for the file by
using the Browse button.
2.6.7 Add new fields in customer data
Use the Customer Name New Field

button to create a new field in customer data during import. The purpose
of creating a new field could be to add a field concatenating values from
two or more fields into a new field.
Give the new field a suitable name.
2.6.8 Add new field in Database
Use the Internal Name Table Setup button

to create a new field in the project database during import. The added fields will
store the imported data in the project database.
To be able to see the data in the different forms select Rebuild Form
from Template before opening the forms.

This form will enable you to add Name and Type size and Description for
the new field.
By pressing the Advanced button the options below becomes available.
Here it is possible to define default values, validation rules etc. It is also

possible to add a combobox to give selectable values in the forms.
The Add field/s form shows all fields that you are about to add. Double-
click on a field to check/modify it, before selecting Create/Modify to add
the fields.
Using the Include Field button in will bring up all new fields from the
Excelfile that you are about to import. The fields as default gets the same
name as in customer file and the datatype is Text 255 as default. Modify
the fields by double-click in the form above and changing the values in
the Create/Modify.. form. Delete the item you not want to create. Select
Create/Modify to add all remaining fields.
Include Field.., will include all fields in the Excel file

(that not already exist in PDA) you are about to import and add the fields
in the Add field(s) form above. As default the fields will be set to Text
255 but can modified by double-clicking the field to modify.
This could e.g. be very useful when importing a new category of data.

2.6.9 Test Structure
Test Structure button is used to perform a test of the

data structure. Run the check to define problems with the structure before
trying to import the data.
In sample above duplicate SigTag names have been identified. It is

possible to correct the error directly in this form and then run the Test
Structure again. It is also possible to use the Filter/Update function in
this form to support the correction of the errors. See in chapter Filtering
and Update functions on how to use the PDA Filter/Update function. It
is not possible to delete rows in this form, use the filtering function
described earlier in this chapter to prevent their import.
If something goes wrong during import, just click the Back button.
Nothing has been imported so far, so there is no problem to change the
settings up to now.
When everything is set up correctly just click the Import button. At this
point the data is imported into the project database.
2.6.10 Error log
Write Error Log creates an error log for the errors

that appears during import. If the error report is not selected, error
messages will popup during the import.
The error log shows all errors detected during import. View the logfile
before completing the import of data. The next time the logfile is updated,
the old logfile is overwritten. If the logfile is to be saved, please use “File
/ Save As” and give it a new name, alternatively the file can be printed.

After studying the error log it is time to decide if data shall be imported
into PDA, or if modifications are to be done before import. If No is
selected, the import is aborted and the import reverts back to the previous
step. If Yes is selected, the data is kept in project database.
2.6.11 Suggested procedure for mapping form use

The following gives a suggested procedure for use of the mapping form.
The actual procedure you use depends upon how closely the customer’s
data matches the project data structure. If the advice given in appendix 1
is accurately followed then you only need to click Import and Yes on the
mapping form.
If the data structure is not as suggested, then you will have to modify the
data using the mapping form and perform some or all of the procedure
below.
1. Create new customer fields if required
Example 1: If the tag name is provided in the customer data as 3 separate
fields (PREFIX, LOOP NUMBER, SUFFIX) we need it in the project
database as one field so we need to create a new customer field to hold
this data.
Example 2: If a customer field contains data which we require as two
internal fields, then create two new customer fields to hold this data. (E.g.
Cable and pair data may be in one field from customer.)
2. Use filter functions to populate data in new customer fields
Example 1: Use Expression Builder to concatenate [PREFIX] & [LOOP
NUMBER] & [SUFFIX] and then update the new “extrafield” with this
value.
3. Use filter functions to DELETE unwanted records from data set
Example 1: If importing a file to Signal that contains signal and loop
records, use filter to identify the loop records, then select all of them and
delete them from the data set. Then remove filter, you are now left with
your required data set.
Note!
The customer file is not effected and the procedure has to be repeated to
generate the Loop table.
4. Save data
Save the new data set to a file, so that if you need to repeat the procedure
you can import from this new file instead of the original and you do not
have to repeat the above procedures.

5. MAP customer fields to internal fields
This mapping will be remembered by PDA when you leave the mapping
form, so that during next import most or all of the mapping is already
done. Also add any new internal fields if necessary. To be able to see the
data in the different forms select Automatic include new fields before
opening the forms.
6. Test structure
Run the test structure and correct any errors in the data. Remember that
data updates can be carried out on this error form manually and using the
filter features. However in order to delete records you must return to the
mapping form.
7. Read Error log on Note pad
Check the error log and correct any errors using the mapping form.
8. Accept the Import
Click YES to accept the import or NO to reject it.
Note!
If rejected because of customer data inconsistencies then you can use the
saved data file (from point 4 above) as the starting file for a new import.
This will save time.
2.6.11.1 Importing revised customer data

The functions described above are used to import revised customer data
as well as new data, however this throws up revision control issues that
must be dealt with by the projects own quality control procedures.
Appendix 2 offers advice on a work procedure for handling revised
customer data.
2.7 Validation
The data that comes from the customer or has been manually entered has
to be validated. Some of the validations in PDA are a pre step of the
checks in other tools e.g. FCB. The goal with these checks is to detect
errors at the earliest stage.

Use Select File(s) to Work with to select the files to validate. If the
purpose of the validation is to validate the data from one supplier, select
the files from that supplier, otherwise select all files.
In the list box Query Name you will find all the available checks. If
project specific checks have been made they will also be available for
selection. The checks have been named with object types first to indicate
which objects they will work on. E.g. "Board, check type" will check the
type on the Board objects. Select the checks that you would like to run.
You have two options how to display the errors, the List view and the
Report.
The “List” option will present all errors in list format.

The errors detected can be corrected directly in this form. It takes a while
to open the form because all mapping data is read.
If you choose to run a Report you must first select the

report in the “Report Name” section of the validation form.
The selected queries and reports will be used as the default next time the
Validation form is opened.
Select Customer Name if customer names of the

attributes shall be used in the reports. If Customer Name is not selected
the internal attribute names will be used ("ABB names").
Appendix 3 gives a description of all validation queries that are supplied
with the PDA.
The System Administration section of this manual explains how new
validation queries and reports can be built and included in the displayed
list. Queries can also be removed to provide project specific validation.

2.8 Compare
The comparison function is used to detect the deviation between revisions

of data. It can be more than one set of e.g. signal within a revision and
these sets of signals are called files below due to the files that they
originally came from.
The files to compare can either be files that come directly from the
customer or files that have been edited in PDA. The normal use would be
to detect the deviation when a new revision comes from the customer, but
can also be used to compare the first revision with the latest to see what
has happened since the first revision for e.g. economical reasons. The
form will appear step by step as you fill it in.
Select the file to compare.
Select the revision to compare with. Only revisions that contain files of
the selected category will appear.
Select the file to compare with, e.g. there can be multiple Signal files
from different suppliers to select from. In Old File select the file to

compare with. Only files of the selected category and selected revision
will be available.
In Field(s) to Compare it is possible to limit the compare to specific

fields. By clicking All, all available fields will be displayed. This is also
the default setting. If you do not want to compare some fields, just mark
up the fields to compare. The reason for not selecting all fields could be to
limit the report to a reasonable size.
Then select Keyfield(s), one or more fields shall make a unique key for
the compare function, the key fields must be included in Field(s) to
compare. Typical keys are SigTag for Signals and Node + Designation
for Boards. The latest used keyfield appears as default value.
When the fields have been defined, just press the Compare button. In the
counter the detected number of changes can be seen.
Use the Report button to look at the changes.

The report shows New Rows, Deleted Rows and Changed Rows. For
Changed Rows the new and old values are shown for the changed
attributes.
Use the List button to see the changes in a form.
It is possible to make modifications in this form e.g. to copy values from

the old revision to the new revision. To update a field with Compared
value, just move the field to update beside Compared_Value and use
copy paste function or PDA Filter/Update function for update. See in
chapter Filtering and Update functions how to use the PDA
Filter/Update function. To update more than single values use the Merge
function described below.
2.8.1 Merge revisions

This function makes it possible to merge revision. If a new revision
comes from customer and in the mean time engineering has been done on
the previous revision , there is a job to be done to merge these revisions,
either include customers changes in the version you have been working
on, or include your engineering in the customers new revision. Select the
file that you want to have as base for the revision merge.
Run a compare to detect the differences between the files.

Do a Filter by Selection on Changed Row(s) to see all changed rows
Use a filter in the FieldName column to filter out the fields to update, you
can see the values in field Compared_Value.
It is also possible to use filters in other columns, e.g. filter for empty
fields in Current_Value to only update empty fields.
Select Merge Version in toolbar, and the selected rows will be updated
with the values from field Compared_Value.
2.8.2 Compare I/O allocation

It is possible to compare the I/O allocation but since the I/O allocation
needs data from both Signal and Channel it require a specific procedure to
do it.
Use Export to export out Signal Query, this query export out the needed
data for the compare. The file is named Compare1 as default.
Import the file and select category Compare.
Do the same operation for the revision to compare with.
Run Compare and select file Compare.
2.9 Edit data
This form shows a set of forms and reports and queries for editing data.
The forms are grouped depending on usage. e.g. under the tab Loop are
all forms and reports for editing Loop data. PDA comes with a set of
forms, reports and queries for different purposes but a number of local
forms, reports and queries will probably be added. The locally created
forms, reports and queries will be shown together with the PDA set of
forms and reports. New forms and reports can be produced for a specific
project or even for a specific user.
2.9.1 Copy I/O allocation
Copy I/O allocation form is used to copy the I/O allocation from one
revision to another. If a new revision comes from the customer and you
have already done the I/O allocation on the previous revision, this

function allows you to update the new revision with the I/O allocation
from previous version. The I/O allocation will only be updated for signals
that exist in both versions, for new signals the I/O allocation will not be
done and for deleted signals it can not be updated.
Note!
Node and Designation have to be the same to make it possible to copy the
I/O allocation.
2.9.2 I/O allocation

Note: Control Builder M specific information on IO allocation e.g. for
S800 IO can be found in the PDA BMI 3.1 User Manual
Use the Select File(s) to Work with form to select the file(s) to do the I/O
allocation on. To work with only one supplier, just select all files from
that supplier.

2.9.2.1 Controller Level
Add Nodes and Buses using this subform. To delete a Node, select the
Node to delete and press Delete button. If a Node is deleted the
corresponding Bus and Station will be deleted, the Boards belonging to
the Node will appear under Not Connected tab.
Use the record selectors to select the Node and Bus to work with before
selecting S100/Trio or S800. Only Boards/Blocks from the selected Node
and Bus will appear in the Board forms. There is no Subsystem level.
Note!
The Node = Controller. Therefore the Subsystem and Controller should
be implied within the Node Name, e.g. Controller Subsystem and
Controller could have the Node Name CS1_1.
2.9.2.2 S100 Boards
To define a Board, select a board type from the combo box.

When a new board is defined a default Connection Unit need to be
selected. The default connection unit is defined in Board form and can be
changed by clicking in the ConnectionUnit field and selecting one of the
available connection units for that specific board type.
Designation will automatically be filled in. Designation is built up based
on Board Concept and a counter using next free number per concept.
Position have to be manually filled in. Sort the boards and use Series fill
down to update position. (This field was automatically updated in PDA
2.0 but due to too many different rules how to update the field, the
automatic function have been removed.)
The ChannelForm will show the number of channels and the channel
types for the selected Board. To delete a Board, select the Board(s) to
delete with the record selector and press the delete key. If there are
signals allocated to a board that has been deleted, these signals will be
free.
The channels marked as Spare Channels in the channel form will not be
allocated. The default setting of the spare channels is done in the Board
form but it can be modified in this form.
Report
A report Summary of S100 I/O sets is available to show the total number
of I/O sets used.
PLC I/O (MOD only)

PLC I/O must be allocated in the same way as hardwired I/O.
It is recommended that one board type should be created for analogue
signals per link per controller and one board type for digital signals per
link per controller (see Board Types later).
For MOD 300 you will have to make sure in your board type definition
that multiple serial links on the same controller do not have the same
channels defined. This is because MOD300 has only one analogue table
and only one digital table for PLC I/O per controller regardless of the
number of serial links on that controller. Each board type can then be
uniquely allocated to the correct Bus with a maximum of one analogue
and one digital board per Bus. (Leave the position number as created
when you allocate the board to the Bus, the PDA uses this to calculate the
Designation for the board.) By doing as above this will ensure that you
cannot allocate more than one PLC signal to one channel.
Two default PLC I/O boards are provided with the PDA, PLC A with
1000 analogue channels and PLC D with 1000 digital channels. You
should create your unique PLC “boards” via the “Board info” form, see
below, and then cut and paste the required amount of channels from PLC
A or PLC D. If you need more than 1000 channels per serial link then you
will have to append new rows manually. Alternatively, if you have many
channels to define, you may find it best to create the Board tables in
EXCEL, import them into the PDA, then build an append query to add
them to the Board Type table. If you do this, ensure that you first create
the correct entry in the Board Info Table. Defining a Board, without any
channels, using the Board Info Tab under the Board Form is the best way
to do this.

2.9.2.3 Reports showing I/O allocation
Different standard reports are available for viewing the I/O allocation.
The I/O allocation per Board report shows the allocated signals per
board. Even free channels are visible.
The I/O allocation sorted on Signal shows all signals with allocation
information, the signals are sorted on SigTag.
All reports can be filtered to show the wanted records. The sample above
can e.g. be filtered to only show Node N1. See Filtering Reports in
General Functions chapter.

2.9.2.4 S800 Boards
For S800 I/O the Station level is included. A Station must be created to be
able to add Boards. Only Boards for the current Station will be shown,
use the record selector to select the Station to work with.
To define a Board, select a board type from the combo box.
When a new board is defined a default Connection Unit need to be
selected. The default connection unit is defined in Board form and can be
changed by clicking in the ConnectionUnit field and selecting one of the
available connection units for that specific board type.
Designation will automatically be filled in. Designation is built up based
on Board Concept and a counter using next free number per concept.
Position have to be manually filled in. Sort the boards and use Series fill
down to update position. (This field was automatically updated in PDA
2.0 but due to too many different rules how to update the field, the
automatic function have been removed.)
The ChannelForm will show the number of channels and the channel
types for the selected Board. To delete a Board, select the Board(s) to
delete with the record selector and press the delete key. If there are
signals allocated to a board that has been deleted, these signals will be
free.
The channels marked as Spare Channels in the channel form will not be
allocated. The default setting of the spare channels is done in the Board
form but it can be modified in this form.
Report
A report Summary of S800 I/O sets is available to show the total number
of I/O sets used.
2.9.2.5 Labels for S800 I/O

A report is available to print out labels for S800 I/O.
All reports can be filtered to show the wanted records. This report can e.g. be
filtered on LocDes. See Filtering Reports in General Functions chapter.

Print out the report and cut it according to the lines, the labels will then fit
on to the S800 I/Os.
2.9.2.6 Not connected Boards
It is possible to import non allocated boards or to create boards before the

Node, Bus and Station are defined. These boards will end up in this form.
The Boards can be allocated by selecting Node, Bus and Station. A click
in either of the fields Node, Bus or Station will bring up the following
form.
Select Node, Bus and Station, as the Boards are allocated they will
disappear from this form and appear in the S100 or S800 form.
User Comments
Be aware that the PDA calculates the designation for a board only once,
when the board is first created. The calculation for this is defined in form
Board - Board Definition - Board Designation, (see later). If you allocate
signals to a board and then subsequently move the board, say by changing
its position or cut and pasting it to another Bus, the designation is not

updated. The signals will remain allocated to the board at its new
position, but if you try to decode the designation value from the signal
pool you may end up looking at the wrong board.
Note!
If you are using clusters for S800 I/O then you must enter the “Cluster”
number for each board and check the “Position” number is the position
within the cluster. The Designation has been calculated using the
automatically produced Position number and this will always be unique
within the Station so the Designation will be unique for the project. Of
course because you have changed the position number the designation
cannot be decoded to get to the correct board.
The allocated signals will be shown in the channel form.
2.9.2.7 Signal Pool
All Signals are displayed in the Signal Pool. See in chapter Bulk Data
Handling how to use the PDA Filter/Update functions. As an example a
filter on empty ChanNum field will show all signals that not have been
allocated. You can add, delete, or modify signals from the signal pool. To
add new signals, type in the new signal after the last existing signal. To
delete signals, select the signals in the Signal Pool and press Delete key
User Comments (MOD)


Be aware that the Chan_Num reference shown in the signal pool is not
always the CCF software channel number. The CCF software channel
number is called SWChannel within the PDA. For most boards the
Chan_Num and the SWChannel are the same, however for the TRIO
6231B current source module they will be different. This is because both
of these have a mixture of inputs and outputs on the same board, they
therefore have an output channel 1 and an input channel 1 etc. The
Chan_Num field is used to uniquely define each channel of the board and
is required for the PDA structure to work correctly. The SWChannel is
only unique when combined with the channel type. For example for the
TRIO 6231B current source board, with 4 AIN’s and 2 AOT’s: AIN1 =
Chan_Num 1 and SWChannel 1; AOT1 = Chan_Num 5 and
SWChannel 1. It is important that your Typical Solution definitions
reference the SWChannel not the Chan_Num. The same may apply to
PLC I/O boards depending upon how you have defined them; e.g. with
analogue and digital signals on the same board, though this is not advised;
or if you have more than one serial link in the same controller, (see PLC
I/O above).
2.9.2.8 Allocate Signals to Boards

Select S100/Trio or S800 boards using the tabs. Click on the board that
you want to allocate a signal to. Select signal(s) you want to allocate, in
the Signal Pool, use a View that only shows not allocated signals.
You can allocate more than one signal simultaneously by selecting all the
signals you wish to allocate, up to the number of signals for the board
type you have selected. If more than the number of available channels are
selected the extra signals will not be allocated.
Select Allocate Signal from the right-button menu. The signal will be
allocated to the first free channel of the selected board. If you want to
allocate the signal(s) to a specific channel, just select that channel, then
select the signal(s) you wish to allocate and click on the “ Allocate
Signals” icon.
To free an allocated signal, select the Signal(s) in the signal Channel sub-
form and select Free Signal from right-button menu, or do the same
operation in the Signal Subform.
When you allocate a signal to a board, SigTag is copied to Channel table.
2.9.3 ADG (no more supported in PDA BMI 3.1)

ADG is an optional add on to PDA. ADG/CAD support automatic
generation of circuit diagram sheet for CAEE. Study ADG/CAD Users
Manual 3BSE012755-100 to learn how to use it.

2.9.4 Board
2.9.4.1 Board Info
This form is used to modify the existing board types or to add new Board
Types.
The following attributes are available:
Type: Board type
I/O Type: the board type must belong to either S100/TRIO/SERIAL or
S800
Description: field for description of the board type.
Concept, Board concept used e.g. for FCB
Chan_Num: unique channel number
Spare, select if there are any channels that not shall be allocated. This
will be the default setting and it can then be modified as the boards are
created.
SWChannel: for some Trio blocks and PLC I/O the channel number may
not be unique, this field is shown in the board sub-form of the I/O
allocation form. This is the channel number reference that is used in the
CCF software and this should be referenced in your Typical Solution
definitions, not the Chan Num.
Type: the type of signal that is to be allocated to the channel, e.g. AIS for
analogue input signals (AIN for MOD users).
Connection Unit, the valid connection units for current Board Type.
Default Connection Unit, the connection Unit that will be created as
default when a Board of current type is created
Variant, the default variant for the Connection Unit e.g. CURR or
VOLT.
Use navigation button at the bottom of the form to add new Board Types
after the last existing type.
2.9.4.2 Import Board Types

The Boards can be imported from other projects or from specific Library
projects.

Select Import From right-button menu.

Select button will show all available object of the correct type and the
following form will appear.

2.9.4.3 Connection Unit
This form is used to modify the existing Connection Unit types or to add
new Connection Unit Types..
The following attributes are available:
Type: Connection Unit type
Description: field for description of the Connection Unit type.
Chan: unique channel number
Signal Type: the type of signal that is to be allocated to the channel, e.g.
AIS for analogue input signals(AIN for MOD users).
Variant, the variant for the Connection Unit e.g. CURR or VOLT.
Term_Name, Terminal Name for connection enclosures
Term_Type, Terminal type describes the usage of a terminal e.g. <SIG>
for signal <+> for operating voltage
Symbol_Alias, an alias name for the symbol used in the CAEE
environment
Conn_Mode, define if the wire should be handled in the wiring system.
1=Yes, 0=No
2.9.4.4 Import Connection Unit Types

The Connection Units can be imported from other projects or from
specific Library projects.
Select Import From from right-button menu.

Select button will show all available object of the correct type and the
2.9.5 Generate Signals
2.9.5.1 Signal Library

Signal Library is the base fore generating signals from Process Objects.
The form is divided into two parts, the upper part is the HW Signals and
lower part is the SW Signals.
SignalLibId, is the name of the function.
Description, used to describe the function, it is shown in the Process
Object form
NameExtension, the names of the generated signals (SigTag) are built up
of Process Object field NameSig and this field.
All Signals fields are available in Signal Library.
2.9.5.2 Import Signal libraries from other projects

The Signal Libraries can be imported from other projects or from specific
Library projects.

Select button will show all available objects of the correct type and the
Tick the objects to import in Select Row field.
2.9.5.3 Abbreviation
The Abbreviation form is used to define how to build up the Signal

names during the Generate Signals operation. The NameExtensions
entered in are available in the SWSignals and HWSignals forms.
Normally there are some naming rules that have to be followed and these
should then be imported into this form.
It is not mandatory to use this form at all, it is possible to type in the
extension directly in SW Signals and HW Signals.
The following fields exist.
NameExtension, unique identifier for Abbreviation.
SigType, the value will be copied into the same field in Signal Library
Description, the value will be copied into the same field in Signal Library
Import Abbreviations

The Abbreviations can be imported from other projects or from specific
Library projects.

Select button will show all available objects of the correct type. Select the
wanted NameExtensions.
The Abbreviations can be imported from other projects or from specific
Library projects.

2.9.5.4 Process Objects
The following fields in the Process Objects have a special meaning when
generating signals.
Select, determine for which Process Objects Signals are to be generated
NameSig, name of the process object. It will be a part of the name of the
generated signals.
SigLibId, Signal Library to be used when generating the signals.
Subforms
Four Subforms are available in the Process Object form.
SignalData shows all generated signals for the current Process Object.
All fields for the signals are available and it is possible to work in this
form also. Data is only shown in this form after generating the signals.
Signal Lib Data, shows the contents in SigLib for the current Process
Objects. It is the field SignalLibId that determine what is shown.
Two similar forms are available for SW Signals.
All the Bulk Data functions are available in the Process Object form, read
the Bulk Data Handling chapter to see available functions. Specific to
this form are the following functions.
The Copy To function is used to copy data from Process Objects to

Signals when generating signals based on Process Objects. Right-click in

the field to be copied and select Copy To and either HW Signal Defaults
or SW Signal Defaults .
Copy Process Object Field, is the field to copy from, automatically filled
in.
Paste in Signal Default, select the Signal field in the Signal default table
that the value shall be copied into.
Copy from Current record and down, if this is ticked all records from
current and down will be updated, if it is not ticked all records will be
updated.
The copied values end up in the Hardware/Software Signal Defaults

form. This form is a subform of Process Objects form By clicking a
Process Object the corresponding Signal Defaults will be shown. Signal
defaults can also be filled in manually. When signals are generated or
updated all signals will get the values from the corresponding Process
Object. Signal Default values always override values from Signal Library.
If Delete signal, when delete process Object is ticked, all signals

belonging to a process object will be deleted when the Process Object is
deleted. Signals belong to a Process Object, if they are generated from a
Process Object or if they have been manually created and then allocated
to a Process Object.
How signals are generated
The attributes for the generated signals are built up the following way.
SigTag = [Process Object:NameSig] [SignalLib:NameExtension] e.g. if
Process Object: Name = H1
SignalLib: Name Extension = _OP_CLOSE_
Then SigTag will be H1_OP_CLOSE.

The other attributes comes either from HW/SW Signal Defaults or from
HW/SW Signal Defaults and Signal Library, depending on the Mode
option. If the same attribute exists both in Signal Library and in Signal
Defaults, then the Signal Defaults value will overwrite the Signal
Library value.

Three different Modes are available when generating signals.
Append/Update from Signal Default is to be used when working with
Signal Defaults to update values in signals belonging to a specific Process
Object. Values from Signal Default will be added to the signals belonging
to the selected Process Objects. Existing values in signals will be
overwritten.
If some of the selected Process Objects not have been generated before,
the signals will be generated and after that updated with the values from
Signal Default. Only SignalName will be taken from the SignalLibrary all
other fields will be empty.
Append/Update from HW/SW Signal Default and Sig Lib works the
same as the above alternative but it also update signals with all values
from the Signal Library.
Note!
All work done on the signals will be overwritten except for the I/O
allocation.
Append/overwrite HW/SW Signal Default and Sig Lib, is to be used
when generating signals from scratch or if the rules for the name of the
signals have been changed in SignalLibrary or in Abbreviation.
All signals generated from the selected Process Objects and also manually
created signals that have been allocated to the Process Objects, will be
deleted and regenerated. After the signals have been generated all values
from Signal Default will be added to the signals belonging to the Process
Objects, for the selected Process Objects.
Note!
All work done on the signals will be overwritten including the I/O
allocation.
Use the Generate button in the form or on right-click menu to generate

signals for the selected Process Objects using the selected Mode.
2.9.6 Signal
This is the main form for editing signal data.
The data can be presented in form view or datasheet view by clicking the
appropriate icon in the tool bar at the top of the form.

Most of the forms can be shown both in Form view and datasheet view.
The layout of the Form views are delivered as default setting and
normally they have to be modified to suit the local needs.
All the Bulk Data functions are available in the Signal form, read the
Bulk Data Handling chapter to see available functions.
2.9.7 Soft Signals

The Soft Signals can be displayed in different views, the views
corresponds to the supported types of soft signals.
2.9.8 Loops
Loops are no more supported in PDA BMI 3.1 but replaced with similar
functions and fields for the Process Objects.

2.9.9 Solutions
See PDA BMI 3.1 User Manual for a detailed description on solutions
such as:
• Control Builder M Integration

• Generate ELCAD Consumer Circuit
The purpose of this function is to export MOD parameters for Typical

Solutions in Engineering Station. These are the steps.

2.9.9.1 Build and Export Scriptfiles
This form is used to build the script files and export them.
Export name is used to select the Solutions to generate.
CCF Anchor is used to select which Anchors to include in the script
files. One scriptfile is built for each solution type. The content of the
scriptfile depends upon which CCF Anchors you have selected to include.
It is essential that you have completed the I/O allocation, since the values
can be picked up from Board, Node etc
The location of where the loops will be built in the E.S. database is
determined by the Anchor field in the loops table.
Export mode defines how the parameter shall be handled in Engineering

Station.
Update is to be used if you only want to update parameter values in
existing Solutions.
Overwrite will update existing solutions and build new solutions. Be
aware that to overwrite a solution the E.S. will first delete the existing
matching solution templates and their children. Therefore if you have a
common control block for several solutions defined as part of your typical

solution and you use "Overwrite", all solutions below this control block
will be deleted. So for these cases use "Keep" mode instead.
Keep will only build new solutions and not overwrite existing ones
Export to, Location, defines where to export the scriptfile to. The files
are automatically named .“Sol_<solution name>.SCR”. If you build
script files on a node basis, be sure put the files for each node in a
separate directory, or rename the files before exporting the next node
files. You need to do this because the file name is only based on the
solution name, not the node name, and so the next node files will
overwrite the original files.
Show Scriptfile, brings up the scriptfile after generation.

Write Log File, determine weather a scriptfile shall be produced or not.
Clear Log File, determine if the contents in the logfile shall be cleared before
adding the result from current generation. If Clear Log File is not selected, the
result from latest generation will be found at the end of the text file.
Build Script, starts building the scriptfile.
Select Viewer, makes it possible to select the preferred text editor to use when
examining the scriptfile. Look for the .exe file of the preferred viewer.
Solution Name, is used to defining the naming convention for the

solution instance under the solution pool. As default the solutions will be
named <LoopName>_SOL
2.10 Budget
The budget form consist of two different parts. The Signal budget form
that allows users to define the expected number of I/O for the project and
compare this to the actual number of I/O and the spare calculation form
that calculates the spare channels.
Go into the Select File(s) to Work with form to select the file to do the
calculation on. One or more files can be selected.

2.10.1 Signal budget
This form can be set up by the System Administrator to fit the project. In
the default setting above, the I/O are divided by Supplier, Type of signal
and Plant Area. The administrator can change the fields to use. Divide the
I/O in the way it has been defined for the project and put in the budget
figures. When the form is opened the Not Updated indicates that the data
is not updated. Press the Update button to calculate the Actual amount of
I/O. If Actual is bigger than Budget then the deviation figures are in red.
Use the Preview button to print/view the report.
2.10.2 Spare Calculation

This form shows the spare channels and it can be divided per Node, Bus,
Station and TypeCh. Not every field have to be filled in.
TypeCh, channel type on the board (not signal type).
TotalCh, the total number of channels for the selected criteria.
FreeCh, number of channels not allocated for the selected criteria.
Free%, free channels as percentage of total number of channels for the
selected criteria.
When the form is opened the Not Updated indicates that the data is not
updated. Press the Update button to calculate the number of spare
channels. Use the Preview button to print out the report.

2.11 Export
The Export utilities allow two options: Export Category and Export
Table/Query.
2.11.1.1 Export Revision
Export Revision allows the export of data into one file per PDA category
i.e. Node, Bus, Station, Board, Signal and Loop. Use Select File(s) to
Work with form, to select the files to export.
There can be different purposes to export the data from PDA. One purpose
is to export the data to the next step in the process. Another purpose could
be to export the data to work with, to another tool e.g. Excel. After editing
the data in Excel or Lotus 1.2.3 the data can be imported again and if the
headers are not changed the mapping will be done automatically. If
SYSTEM is selected as supplier, after importing the data the supplier can
be changed back to original supplier name.
Export to, format, defines the format to export the data in e.g. Excel or
Delimited.
Export to, location, the path where to export to. Use Browse to select the
path.
Export, use this button to execute the Export. The button is only enabled
when Export to Format has been selected. File name and path for the
exported file(s) will be shown on screen after export.

2.11.1.2 Export Table/Query
Export Table/Query makes it possible to build user defined queries and

exports their output in e.g. Excel format.
Select Table/Query to Export listbox shows all existing tables and select
queries. The listbox below shows the Tables/Queries that have been used
before. Double-click in the listbox to make one of the previously used
queries current.
Note!
When you build a new query the PDA has to be closed and then re-opened
for the query to appear in the list.
Export to, format, defines the format to export the data in e.g. Excel or
Delimited.
path.

This form is used to produce a list of the definition of fields with
descriptions to distribute to the customer, as per appendix 1.
Select Category to Export, is used to select the Categories to include.
Signal and Loop would be the most common Categories. If I/O allocation
is to be done by the customer at least Board has to be included. By
clicking in the Import Object field the fields for the selected object will
be shown below.
Field included, will show all available fields for the selected object. If
project specific fields have been added by the system admin they will be
included in the list. To make it easier for the customer to understand what
he is supposed to supply, just select the fields that will be supplied by the
customer.
path.
Create Structure, creates the same information as in Field included
when exported.
Create Table, creates a table for customer to fill in data in.
Note!
Spreadsheets are exported as Workbook but at imported as separate sheet
files.

2.12 Control Builder M Interface
The Control Builder M Interface is used to export data to Control Builder
M. For more details see PDA BMI 3.1 User Manual.
2.12.1 Project defaults

The project defaults are defined in two different forms FCB Valid Type
HW for I/O signals and boards and FCB Valid Type SW for soft signals
This is a part of FCB Valid Type HW form, a similar form FCB Valid
Type SW is available for the “Soft signals”
Concept, board types and Signal types.
BoardTypeID, the value exported/Imported as Board Type. AI in the
BAX file is e.g. converted to DSAI_110 when imported to PDA.
It is possible in PDA to add project default values that will be exported to

FCB and these overrides the default values in FCB. This function exist for
HW signals like AIS DIS and for SW signals like AIC and DIC and for
Boards. The properties defined in project default are the properties that
will be possible to export. This means that if a property not exist in
the Project Default library it will not be possible to export it.
Note!
The default values for S100 Boards are taken from AI, AO, DI and DO
when exporting the data. The values in e.g. DSAI_110, DSDI_110A etc
are only used during import.

Property, name of the property in FCB. Only properties existing here are
possible to export to FCB.
FCBDefaultValue, the default value in FCB. It is shown only to indicate
what the value will be used in FCB if no value is exported from PDA.
DefaultValue, is used to set project specific default values to override the
default values in FCB. The default value will only be used for exported
objects where the value is null, the values from Signals/SoftSignals will
always override the default values.
2.13 System Administration
2.13.1 Security
There are three different kind of users in PDA, pda, pdaadmin and
viewer. All functions under this section requires system administration
authority.
The pda user can work with the base data like signals loops etc. The
pdaadmin can e.g. build new Solutions or add new types of boards. The
viewer can only view the data and print out reports.
See System Administrators guide 3BSE020288D0006 how to log in as
Administrator.
2.13.2 General
When a new project is set up there are a number of things that should be
done to adapt PDA to that specific project. The base for the modification is
the agreement regarding which data that will be supplied by the
customer/subcontractor and in which format this data will be delivered.
Below is a list of items to consider when setting up a new project,
followed by a description how to perform the different items.
1. Agree on the data format and contents with the

Customer/subcontractor
2. Create a new database for the project
3. Add new fields to the database to match what is to be delivered from
Customer/subcontractor and also for internal usage
4. Import Object, Forms, Reports, Queries and Code can be imported
from other Projects or Library projects.
5. Select the validation queries that are to be used in the project using
Select Form. Create new validation queries with the project specific
values if needed.
6. Create new forms for manipulating the data
7. Create new queries
8. Create new reports

9. Add new forms and reports in PDA
10. Fill in budget values for the agreed number of signals in I/O budget
form
11. Distribute project specific forms and reports to project members
2.13.3 Agree on the data format and contents with the

Customer/subcontractor
If it is possible to get an agreement regarding data format and contents
this will save a lot of effort later on in the project when data comes from
the customer. Information regarding proposed fields and format can be
found in attachment 1. A description of the fields can also be exported out
from PDA using Export Import Information.
2.13.4 Create a new database

Plant Design & Allocation consists of three different databases/.mdb files:
Pda.mdb,application database, queries, forms, reports and modules and
some tables for validation reports, compare etc.
MASTERdb.mdb or MODdb.mdb, database that is copied when a new project
is created. The database contains all tables except the above. This
database shall only be updated if the changes are valid for all new
projects. It is also possible to build variants of these databases for
different types of projects.
<project>.mdb when a new database is created in PDA it is generated as
a copy of the selected project master and will then be modified to fit the
current project. There is one database per project, this is the database
where project specific fields shall be added.
2.13.5 Add new fields to the database.

Decide in which database the fields are to be added, see above.
Open the database where the fields are to be added, use Exclusive mode.
Open the table in design mode in which the new fields is required.
Add Field name, Data type and Description. Use the description field to
make clear the users understand the purpose of the field.
Some fields have description (Not map). These fields are used internally
in PDA, do not delete these fields.
Do not forget to update the forms in which the new fields shall appear,
use Rebuild Form from Template function to modify the forms.

2.13.5.1 Import Object
It is possible to import any object from either another active project or a

specific Library project.
Update from DB, browse for the database to import the object from.
Update Query, Form, Report, Macro and Code To DB, current PDA
application database.
Update Table To DB, current project database.
ObjectName, Name of the object to import.
ObjectType, type of object, query, Form Code etc.
Select, tick the objects to import.
2.13.6 Create new validation queries

PDA is delivered with a set of standard queries for validation of the
entered data. All project specific validation queries are to be added
following the guidelines below.

The above query is used to check for invalid characters in Loop Name.
When building a new query it is recommended to copy one of the existing
queries and modify it. After modifying the query, rename it so that the
name describes the purpose of the query. All validation queries are
append queries, the detected errors are added to a table named Error.
The following fields are mandatory in the validation queries:
UniqueID All rows in all tables have a unique ID, this is used to
identify the rows.
ErrorText This field is used to describe the error. There are two
different ways to add the error message. The first alternative is to use the
function ErrorMsg (<ErrorNo>). Add a error message in table ErrorMsg
and a unique number for each message. Refer to the ErrorNo in the query.
The other alternative is to type in the error message directly in the query.
ImportObjectID Is used to identify which table the error originated from.
The field exists in all tables.
The other fields are used for validating the data. See also Building
queries.
2.13.7 Create new forms

Use Rebuild Form(s) function or standard Access to build new Forms.
See Add user defined Forms and Reports, how to make the reports
appear in correct form.
2.13.7.1 Rebuild Form(s)

This function makes it possible to rebuild existing forms or to build new
forms based on existing templates.

Available Forms, shows all existing forms in the database, including
locally added forms.
Template form, shows the name of the template that the selected form
is built on. Not all forms are built on a template.
Popup/Modal form, determine how the form shall appear. Subforms
normally are in Popup form.
Delete Form, delete the selected form.
Copy Form, copy the selected form and prompts for a new name.
Rebuild, this function rebuilds the selected form based on the template
and the contents in the current database. If e.g. new fields have been
included in Signals table and some of the old fields have been removed
then this function will rebuild the form to fit the table. This function only
works for forms that are based on a template, if there is no template it is
still possible to include new fields from the tables but not to remove fields
or modify fields.
Rebuild all, rebuild all forms that are based on a template. This function
will take a while to perform, around 20-60 minutes.
2.13.8 Create new reports

All reports shall be located in PDA.MDB. The easiest way is normally to
copy one of the existing reports and modify it, this will give you the
correct footer etc. The reports are built using the standard Access report
generator, see building queries in Access. See Add user defined Forms
and Reports, how to make the reports appear in correct form.

2.13.9 Create new queries
Build all new queries based on the queries below, instead of building the
queries based on the tables. These queries will automatically only pick up
data from the current revision.
Node Query =Current revision of Node information
Bus Query =Current revision of Bus information
Station Query =Current revision of Station information
Station Include Local =Current revision of all Station includes
"0" for local I/O.
Board Query =Current revision of mixed S100/S800
Board information
Board S100/Trio Query =Current revision of S100/Trio board
information
Board S800 Query =Current revision of S800 board
information
Signal Query =Current revision of Signal
information
Soft signal Query =Current revision of Signal
information
Loop Query =Current revision of Loop
information
Allocated Data with Loops =Current revision of data from all tables.
Only signals allocated to boards and to
Loops will be visible.
Allocated Data without Loops =Current revision of data from all tables.
Only signals allocated to boards will be
visible. The signals do not have to be
allocated to Loops to appear.
2.13.10 Add new Forms, Reports and Queries into PDA

Select the tab Other under Edit Data, and open form Select Form.
This form is used to add locally built Forms, Reports and Queries under
the existing Tabs. The left side of the form shows all existing Forms,
Reports or Queries. The right side of the form shows the Forms, Reports
or Queries under each Tab.

Select a tab on the right side to place a new Form or Report under,
Double-click the new Form/Report/Query on the left side to add it.
Double-click the existing Form/Report/Query to remove it.
2.13.11 Fill in budget values for the agreed number of Signals

If the number of signals is a part of the agreement with the customer, then
the agreed number of signals can be entered as budget figures in the
Budget form and the Spare calculation can also be set up. Read more
about how to handle this in the section on Budget.
2.13.12 Distribute project specific forms and reports to project members

The easiest and most safe way of delivering the new Queries, Reports and
Forms to the project members is to distribute the updated PDA.MDB file.
It is also possible to use the standard import functionality in PDA to
import the new Queries, Reports and Forms. Persons working in more
than one project can either have the Queries, Reports and Forms for all
projects in the same database or have one PDA.MDB database per
project.
2.13.13 File location
This form is used to define default locations. The default paths are e.g.
used when browsing for files to import etc.
ADGSourceDir, Location of temporary files used as input source for the
ADG generator
Base Library, Location of Base Library information for the ADG
generator (normally not changed)
Default path to elMaster config, path to elMaster Configuration file.
Default path to elMaster Template, path to elMaster Template file.
Export To, Default path for Export, e.g. when exporting data in Excel
format
FCB Export/Import, default path for FCB Export/Import, e.g. the
DBDATA catalogue under correct Node.
Import From, Default path for Import, starts at this location when
browsing for customer data

Project-data, Default paths for new projects
Systemfiles, Location of the application database (pda.mdb) Paths for
ADG/CAD users.
2.13.14 Create Category

PDA is delivered with a number of data categories like Signals, Loops
etc. These categories are not always enough there could be a need for new
categories. To support adding new categories PDA have a Create
Category function. The function can be found under the Other tab.
The following functions will be automatically built up if the Create
Category form is filled in.
A Table will be created for the new data category.
The Import function including mapping will handle the new category.
The Compare function will handle the new category.
The Export function will enable export of the new category.
A Template will be added to build forms from.
ImportObjectID, a character to uniquely identify the category

Import Object, name of the new category shown in e.g. Import/ Export
TableName, name of the table to store data in (normally same as
Category)
Create order, used when generating structure during import (normally
next free number)
Visible, if the category should be available in import (normally Yes)
Export, if it should be possible to export the category (normally Yes)
IndexFieldName, keyfield used for Category (one or more fields that
makes a row unique)
Select Create to create the new category, you will be prompted to close
PDA to enable updating the tables.
Use the Rebuild Form function to build up Form(s) based on the available
template. The needed fields can either be added during the Import or by
using the Table Setup function.

2.13.15 Compact Database
To maintain the performance the databases should be compacted on a
regular basis.
This menu item can be found beside

the starting icon for PDA 3.1. This function is open for all users and it
will repair and compact the application database.
To compact the project database use the normal Access function. Open up
PDA with shift key down, this will open the PDA database without
starting the application. Close down the PDA database and open up the
project you are about to compact. Run Compact Database and Repair
Database that can be found under Tools and Database Utilities.
2.13.16 Data structure

The core of the data structure looks as the picture below when PDA is
delivered.
Use Relationships in Tools menu to see the current structure.

3. Appendix
3.1 Supplier Data

Supplier data is to be provided in various files, these can be in various
Excel or Lotus 1.2.3 formats.
It will be up to the project manager to agree with the client which files
will be supplied and which will be ABB/System supplied. Also the
project manager will have to agree as to which fields within these files
will be supplier provided or ABB/System provided.
It may be that the supplier cannot provide the files in the required format.
It will then be required that ABB modify the supplier’s data to conform to
the required format.
As well as conforming to the specified format in order for the import to
work certain fields will be compulsory i.e. every record must contain a
valid entry for these fields. The fields will be specified as:
Mandatory (M)
Optional (O)
• Also certain fields will have to be unique and these may be:
a) Unique within project (U)
b) Unique within Node/Controller (N)
c) Unique within Bus/LAN (B)
Of course within a project it will be necessary to make other fields

compulsory to have the data make sense.
PDA provides for the import of following categories
• Signal data
• Loop data
• Board data (including TRIO block and remote I/O)
• Station data (for S800 I/O)

• Bus (LAN) data
• Node (Controller) data
PDA can provide a list of all attributes and a description of them to
explain for the customer which information we expect. By using the
Exchange Format function in PDA it is also possible to produce an
Excelfile with all fields in for the customer to fill in.
3.1.1 Instrument schedule

If the supplier is providing an Instrument Schedule only, then it will be
necessary for ABB to break this down into the required categories for
import to the PDA.
3.1.2 I/O schedule/ Signal

If the supplier is to provide an I/O schedule this must be a list of all
signals to be connected to the system and include additional parameters as
specified in the Signal requirements. Any serial and PLC I/O must be
included.
3.1.3 I/O allocation / Node, Bus, Station and Board

If the supplier is to provide the I/O allocation, all signals must be
allocated and the following files with their additional parameters must be
completed as specified and as separate files.
• Signal data
• Board data (including TRIO block and remote I/O)
• Station data (for S800 I/O)
• Bus (LAN) data
• Node (Controller) data
3.1.4 Software specification / Loop

If the supplier is to provide Software/Display Loop names then the Loop
file must be provided. Every signal that enters the system must have an
associated Loop name.
Note!
Several signals may have same Loop name. In addition, software only
Loops must be specified. The Loops specified would normally be these
shown on P&ID's as Indicators or Control loops etc. Internal MOD300
Loops required to achieve desired function should not be specified.
The Project Manager should then agree which additional loop parameters
are to be provided by the supplier and which ABB are to supply. It can
also be that the supplier can provide a rule for ABB to automatically
generate the data.

3.1.5 Definition of fields
Use the Data Exchange tab in PDA to produce an Excel file with the
correct attribute names.
3.1.5.1 List of attributes

In previous version of PDA a list of the attributes where included in this
manual but since it tends to be more locally added attributes it is better to
print out an Excel file that really shows the correct attributes.
3.1.5.2 Data types

Long (long integer) variables are stored as signed 32-bit (4-byte) numbers
ranging in value from -2,147,483,648 to 2,147,483,647. The type-
declaration character for Long is the ampersand (&).
Double (double-precision floating-point) variables are stored as IEEE 64-

bit (8-byte) floating-point numbers ranging in value from -
1.79769313486232E308 to -4.94065645841247E-324 for negative values
and from 4.94065645841247E-324 to 1.79769313486232E308 for
positive values.
3.1.6 Handling Revised Customer Data.

When we receive new customer data it comes in three forms (at least):
1. A complete new issue of all records and data, this includes the very
first issue.
2. An issue of new records (signals or loops) which were not in the
original release. Say the original list did not contain the signals for a serial
link and now he gives you these signals.
3. An issue of new data for existing records. Say customer originally
issued signals without range data and now he sends the range data.
How do we deal with these issues in the PDA?
1. For the first completed issue, we create a new revision in the PDA then
import the data in the normal manner. Then make a copy for comparisons
with later revisions. I suggest that you use one naming scheme for
imported customer data, e.g. A,B,C....... and another for the ABB working
databases, e.g. 1,2,3..... (double click on revision note to change it).
Copies of the ABB databases would then be 1/1, 2/1 etc.
2. For a complete re-issue of data we need to see what data has been
changed in order to decide whether it is better to:
a) Work with this new issue, import it, and update it with the data we
have manually entered into the previous issue.
b) Continue with the current PDA revision, (containing our manually
entered data), and update this with the new issue of data.
Before you start I advise that you make a copy of your current revision,
go to copy and make a backup. (In this example let us call the current
working version “1” and the copy “1/1”). Now create a new revision, via

the Project Details form, you can rename it if you prefer (double click on
revision note after the new revision has been created to rename a
revision).
Import the new customer data into this new revision, in the normal
manner. (Let us call this “B”)
Make a copy of this as imported since you may update this version later.
(Let us call this “B/1”)
Now we need to see what data the customer has changed since the last
revision he sent us, (which we called “A” at the time). Ensure that the
new imported files (B) are the current revision then go to compare and
compare the “new” customer data revision (B) with the “old” customer
data revision (A) that you saved on the previous import. Print the report.
The compare feature works by comparing one selected file in the current
revision with one selected file from the old revision, and will only
compare files of the same category. So you will have to repeat this for
each file and category combination.
Next we need to see how much data we have added to the PDA since the
previous issue of customer data.
Select your current working revision of the PDA, (1).
Go to compare and compare the “new” current working data revision (1)
with the same “old” customer data revision (A) that you saved on the
previous import. Print the report.
You should now have enough information to decide whether it is better to
update the new customer data or the current working copy.
You can do the update one of three ways
1. Manually enter the data to the correct revision.
2. Use the compare function and the filter update feature to update the
correct version.
3. Write your own update query.
4. The I/O allocation can be copied from the current working revision to
the newly imported customer revision using the I/O allocation copy
feature, under I/O allocation.
Select the version you have decided will now become the current working
version (either “B” or “1”)
1. Manual updates.
Use the reports of changes and perform the updates manually.
2. To use the compare list to perform the updates.
Before you do this it is probably best to use the copy I/O allocation
feature first, so that the number of changes subsequently identified are
reduced. Use compare to compare the previous working version (1) and
the recently imported new issue (B). Ensuring that the version you want
to update to is the currently selected version i.e. the “new” in the
compare.
Run the List function.
Use the filter functions to update the data (one field/column at a time).
To do this place the cursor in the List form field called “Fieldname”, on
any record that shows the field you wish to update, and then “filter by
selection”. This displays only records with changes in this fieldname.
Then place the cursor in the field you wish to update, reselect the filter
and enter [Old] in the update section of the filter, then press “Update by

Criteria”. This will then update all records to the “old” data, (note for
“old” read “from” and for “new” read “to”), where there has been a
change in this field.
3. If you chose to write your own update queries it is probably best to use
normal Access to import the customer’s new data as a new table. Then
ensure that the version you want to update to is the selected version. Write
your update queries to update the following queries. This will ensure that
you are updating the correct version. Signal Query, Loop Query, Board
Query, Station Query, Bus Query, Node Query.
Do not append to these queries or any table unless you are very sure you
understand all the relationships within the PDA. See below for appending
new records.
Once you have completed the updates make sure you have the correct
revision notes for the different versions for your project procedures,
rename them as above if you need to.
Now ensure the project team is aware of which version they are to work
with, for example it may be necessary for the panel engineer to complete
his work with the old version before he starts re-engineering with new
data.
4. If you have received an issue of new records, which are not in the
current project you need to append these records into the correct tables.
These records may be sent to you as a separate file or they may be
included with existing records that you can identify and filter out during
the import.
To append these new records:
First make a copy of your original data with the copy feature.
Then ensure that these records are in a file with a name you have not
previously used, i.e. rename file if necessary (this is because the PDA
must have a unique reference for category, supplier, filename when
importing).
Then carry out the import in the usual way.
Then ensure the versions are named correctly for your procedures, by
renaming the copy and the current if necessary, and ensure the project
team know which version they should use.
You can now use compare to identify the new records, print out a report
and inform the project team.
5. If you receive an issue of new data for existing records you will want to
update these records with the new data after first identifying the changes.
This data may have been missing from the original issue or agreed with
the client that it would be provided later, or indeed you may have
exported a query, using export and asked the client to fill in the missing
data from this subset. This is often the case for software loop parameters.
In all these cases you should follow the procedure as in 2 above for a
complete re-issue, but in this case you will definitely update the current
version with the new data. Also you may wish to give the imported new
data a revision note number that is very different from the normal revision
notes defined in your procedures, e.g. “NewRangeData1”

3.2 Validation Queries
3.2.1.1 Boards
Board, check Board Type
This validation query checks that the board type entered during I/O
allocation is a valid type, as defined in the Board Info table. These types
are defined in Edit Data – Board Definition – Board Info.
Board, check Duplicate Address

Checks that address is unique within Bus + Station.
Board, check Duplicate Position

Checks that Positions is unique within Bus+Station.
Board, Check Fields for leading spaces

This validation queries check for leading spaces in all TEXT fields.
Board, check Position, Station and Cluster

This validation query checks that:
Position is not greater than 12
Station is not greater than 24
Position is not greater than 12
Board, Check S100 addresses are valid for board type.

This validation query checks that the Address values for S100 I/O boards
are within the valid range for the board type as defined in the MOD300
manuals.
Note!
The values entered in the PDA should be in Hexadecimal.
Board, I/O allocation, PLC Duplicate Channels in Node (MOD only)

This validation query checks for PLC I/O boards which are allocated to
the same node and have duplicate analogue channels or have duplicate
digital channels. The MOD300 has only one Analogue I/O table and one
Digital I/O table per node for PLC I/O. If you have more than one serial
link on a node it is possible that you have allocated two or more PLC I/O
boards with the same Analogue or Digital channels. Check the guidelines
given in the User manual for creating PLC I/O boards.
This query uses sub-query “BoardDataAll”
Board, Mandatory fields (Node, Designation and LibRef1)


This validation query checks that the fields Node, Designation and
LibRef1 are filled in.
3.2.1.2 Bus
Bus, Check Fields for leading spaces
3.2.1.3 Loops (MOD only)
Loop, Check Alarm Limits, Ranges & Initial Setpoint are valid.
This validation query checks that the HIENGUNLIM (High Range) is
greater than the LOENGUNLIM (Low Range), for loops which have an
IndCntrlDev type not equal to “D”. It also checks, for all loops, that the
alarm limits are set with appropriate values i.e.
LOENGUNLIM<=LOLO_LIMIT<=LO_LIMIT<=HI_LIMIT<=HIHI_LI
MIT<= HIENGUNLIM.
It ignores any NULL values in the Alarm limits, but will list any records
with NULL in the HIENGUNLIM or the LOENGUNLIM fields.
It also checks, for all loops, that the INIT_SPNT (Initial Setpoint) is
within the loop range.
Loop, Check Alarm Priorities and Enables are set.

This validation query checks that the Alarm Enable and the Alarm
Priority fields have valid entries where an associated alarm limit has been
specified. If the alarm limit is not specified (i.e. it is NULL) then the
associated Enable and Priority fields are not checked.
The valid entry for the Enable field is “YES”, (although “NO” is also a
valid entry for MOD300 it is unlikely that this is required when an alarm
limit has been specified, and so this value is considered invalid for this
test).
The valid entries for the Alarm Priority fields are “STD” “MED”
”HIGH”.
All analogue alarms are checked, including deviation and output alarms.
Loop, Check Device Types are valid.

It depends upon how you have defined your typical solutions as to
whether or not you need to run this check. If you have defined one typical
solution per device type, then you will not need to pass the device type as
a parameter, and so you do not need to enter data in this field, thus there is
no need to run the validation query. If however you use a generic device
loop as your typical solution and pass the device type as a parameter then
you should run this validation check.
The validation check checks all loops irrespective of their IndCntrlDev
entry, this will help identify any analogue or device loops that have
become mixed up.

It then checks the DEVICETYPE field of loops for invalid types as
defined in the MOD300 CCF manual.
I.E.
Is Not Null And <>"0_IN_2_C_OUT" And <>"0_IN_1_C_OUT" And
<>"0_IN_1_M_OUT" And <>"0_IN_2_M_OUT" And
<>"1_IN_1_C_OUT" And <>"1_IN_2_M_OUT" And
<>"2_IN_1_C_OUT" And <>"2_IN_2_C_OUT" And
<>"2_IN_2_M_OUT" And <>"4_IN_2_C_OUT" And <>"1_IN_0_OUT"
And <>"2_IN_0_OUT" And <>"3_IN_0_OUT" And <>"4_IN_0_OUT"
And <>"USER_DEFINED" And <>"SPECIAL"
Loop, Check Fields for leading spaces

The loop query contains too many fields for Access to run as a single
query so the 3 queries “subQ1-Def-Loop, Check Fields for leading
spaces”, “subQ2-Def-Loop, Check Fields for leading spaces”, and
“subQ3-Def-Loop, Check Fields for leading spaces” work together to
check all fields.
Loop, Check for Loops without associated signals

This validation query checks for Loops that have not been directly
allocated to signals.
This may be acceptable for software only loops or loops whose input
signal is part of another loop e.g. Totalisers.
If Loops are identified check for spelling mistakes (especially 0 instead of
O), and also leading spaces.
Loop, Check Loop TREND_RATE (1) for valid values.

This validation query checks for NULL values in the TREND_RATE and
the PROC_RATE fields of Loops and also checks that the
TREND_RATE value is one from the valid list of values
0,6,12,60,120,360,720,1440,2880.
This query will not test loops whose IndCntrlDev field is set to “D”.
Loop, Check Loop TREND_RATE (2) is >= to PROC_RATE.

This validation query checks that the TREND_RATE is greater than or
equal to the PROC_RATE for the loop. This produces a warning, since
although it is acceptable to configure the TREND_RATE to be less than
the PROC_RATE it is not good practice.
This query will not test loops whose IndCntrlDev field is set to “D”.
Loop, Check LoopAbove is in Loops Table

Loop, Check LoopBelow is in Loops Table

Loop, Check PROC_PHASE is valid for PROC_RATE &
CCF_Baserate
This validation query checks that the PROC_PHASE (loop phase) is valid
for the PROC_RATE (loop scan rate) and CCF_Baserate. The
PROC_PHASE must be less than the PROC_RATE/CCF_Baserate.
Example a loop with a 2 second PROC_RATE and a 0.5 second
CCF_Baserate can have 4 possible phases:- 0,1,2,3.
Note!
The first phase starts at 0, (not 1).
Loop, Check Remote Setpoint Source is in Loops Table

The above three queries check that the loopnames entered in the
LoopAbove and LoopBelow and REMSTPTSRC (remote setpoint source)
fields have corresponding loops identified in the Loopname field of the
loops table.
All three validation queries make use of a sub-query called “Remove
FCM Name from Loopname”. This strips off the .fcmname from the
entry, (if it has been used), before the comparison is done, (i.e.
LIC123.AIN becomes LIC123).
Loop, Description invalid chars

This validation query checks for the following invalid characters in the
loop description field
("." "," "?" "!").
Note!
Since * is the wild card in Access the query cannot check for this.
Loop, Invalid characters in Name

This validation query checks for the following invalid characters in the
loopname field
("." "," "?" "!").
Note!
Since * is the wild card in Access the query cannot check for this.
3.2.1.4 Process Objects

Process Object, Mandatory fields (LibRef1 and FuncParent)
This validation query checks that LibRef1 and FuncParent are filled in.
3.2.1.5 Node
Node, Check Fields for leading spaces

3.2.1.6 Signals
Signal, Check Fields for leading spaces
Signal, Check for Signals without associated Loops (MOD only)

This validation query checks to see if there are any signals where the
Loopname field does not have a corresponding entry in the Loopname
field of the Loops table.
This may be acceptable if the signals are part of the project but do not
actually come into the MOD300, (i.e. are not allocated to any I/O
channels). For example the project may have to marshall some signals to
an annunciator without them ever being used in the MOD300.
If signals are identified check for spelling mistakes (especially 0 instead
of O), and also leading spaces.
Signal, Check length of description

This validation query checks that the Description field is maximum 20
characters.
Signal, Check signal types match channel types

This validation query checks for signals which have a signal type which
does not match the channel type of the board to which the signal has been
allocated. Look out for “ 1 ” or “ l ” instead of “ I ”, and “ 0 ” instead of “
O ”.
Correct spelling mistakes or re-allocate signal to correct Channel/Board.
Signal, I/O Allocation contiguous channels for loops (MOD only)

This validation query checks that loops with two signals of the same type
(e.g. DIN or DOT) have these signals allocated to contiguous channels of
the same board.
It also identifies signals where one of the signals has not been allocated.
Note!
If you have loops which have more than two signals of the same type this
query will show these as errors.
This query uses a sub-query “SignalBoardData” which in turn uses a sub-
query “BoardDataAll”.
Signal, I/O allocation, check for limit switches (MOD only)

This validation query checks that the limit switches for valves are in the
correct order for the device type and descriptor set and that they are on
contiguous channels of the same board. (It does not check for one of the
limits being unallocated. Use “Signal, I/O Allocation contiguous channels
for loops” to check for this.).

The query identifies limit switch signals as those with signal tag names
starting with ZSH, ZSL, ZIH, ZIL, ZSO, ZSC. If your data uses a
different nomenclature to this you will have to copy the query and modify
it to suit.
The query assumes you are using a 2 input device with the open limit
switch on the first channel. The query checks that ZSH is allocated to the
channel before ZSL on the same board, and similarly, ZIH before ZIL,
and ZSO before ZSC.
Signal, I/O allocation, PLC digital outputs (MOD only)

This validation query checks digital outputs that have been allocated as
PLC I/O.
If the PLC definition templets have been configured for grouped digital
outputs the MOD300 writes these in 8 bit groups. If digital output signals
from a loop are split across this boundary the result within the PLC may
give bad data. This therefore should be avoided.
The query will check for any DOT with vendor type PLC I/O and will test
if its channel number is divisible by 8 without leaving a remainder, (e.g.
8,16,24,32…….etc). If it finds such it will identify it as an error and list
all DOT signals from that loop.
Signal, I/O allocation, S800 16 channel digital boards (MOD only)

This validation query checks for signals of the same loop which are
spread across channels 8 and 9 of 16 channel digital S800 16 channel
digital I/O boards DI810 and DO810.
These types of board have two separate groups of eight channels that can
be separately powered. It is not good practice to put signals of the same
loop on separate power circuits.
Signal Mandatory field (LibRef1)

This validation query checks that the field LibRef1 is not empty.
Signal, Missing I/O allocation

This validation query checks all signals have been allocated.
Signal, ADG run before generation
This validation query checks for signal that are not allocated, device
designations that are not unique or where

device functions are used twice. It also checks for use of nonexisting
device functions.
3.2.1.7 Soft Signal

Soft Signal, Check duplicate name.
Checks if there are any duplicate names in Soft Signals. Due to
requirements from the usergroup it is allowed to have duplicate names on
the Soft Signals, but not when exporting them to FCB.
3.2.1.8 Signal path

These validation queries are used to validate the expanded data before
using the ADG/CAD generator.
Signal Path, check LocDes

This validation query checks that the field LocDes is not empty.
3.2.1.9 Station
Station, Check Fields for leading spaces
Station, Mandatory fields (LibRef1)
This validation query checks that the field LibRef1 is not empty.

4. Glossary of Terms
4.1.1.1.1 PDA
Plant Design & Allocation

Designation1 11
Designation2 11
Doc_Id 11
DocKind 11
Document details 11
5. Index E
Edit Data 41, 74, 83
Elmaster Path 9
Export 61, 62–70, 82
Export Revision 65
Export Table/Query 65–66
Export To 9, 63, 65–67, 65–67, 75
Expression Builder 20, 22, 30, 35
A F
Abbreviation 55
F1 8
Add new Forms and Reports into PDA 74
File location 8, 75
ADGSourceDir 75
file locations 8–9, 8
Allocate Signals to Boards 49
File name 9, 63, 65–67, 65–67
Apply/Remove filter 16–17
Fill Down 19–20
Approved 11
Filter 16–19, 16–19, 22, 24, 30–31, 31–35, 34–35,
Automatic mapping 31
40–41, 40, 48, 81–82, 81–82
Filter By/Excluding selection 16–18, 18
B Filter Save 17
Find 6, 8, 20, 23, 37, 44
Base Library 75
Freeze Columns 23
Based 11, 16, 22, 57, 63, 74
Board 37, 43–50, 65, 67, 74, 78–79, 82, 83–89
Board data 27, 79 G
Board Designation 47
General 5, 69
Board Info 44, 50, 83
Generate Signals 55, 59
Boards 26, 39, 43–49, 74, 88–89
Build and Export Scriptfiles 62
Bulk data handling 13, 48, 57, 60 H
help 8, 22, 84
C How to build new subforms 23
Compare 38–40, 63, 70, 81–82
Connection Unit 44, 46, 50, 52 I
Controller Level 43 I/O allocation 6, 13, 22–24, 22–27, 27, 30, 41, 45, 50,
Copy I/O allocation 13, 41, 81 59, 67, 79–80, 81, 83, 87–88, 87–89
Copy revision 12 I/O Budget 63, 70, 75
Create a new database 69 I/O Calculation 63
Create new forms 69, 72 I/O schedule/ Signal 79
Create new queries 69, 74 IDesignation 1 11
Create new reports 69, 73 IDesignation 2 11
Create new validation queries 69, 71 Import 5–6, 5, 9, 12–13, 12–13, 18–19, 26–36, 26–
Created Date/Time 12 35, 44–47, 47, 50, 52–56, 52–56, 67–71, 61, 75–
Current revision 12–13, 28, 74, 80–81 79, 75, 78–79, 80–82, 80–82
customer names 11, 27, 30, 37 Import Board Types 50
Import Connection Unit Types 52
D Import Filters 18
Import From 18–19, 18–19, 31, 35, 51, 52–56, 52–56
Data structure 34–35, 76
Import Object 69–71, 71
Data types 80
Importing revised customer data 36
Definition of fields 67, 80
Instrument schedule 79
Description 11–12, 18, 27, 31, 37, 50, 52, 55–56, 69–
internal names 11, 27, 30
70, 79–80, 86
Usermanual for Instrument Index Index • 91

L Signals 16–17, 16, 24–27, 26–27, 35, 39, 42, 44–50,
44–50, 44–50, 44–50, 52–55, 52, 57–59, 55–56,
Loop data 26, 41, 78 57–59, 69, 70, 74–75, 74–75, 79, 85, 87–88, 87–
Loop forms 60 88
Loops 26, 30, 26, 69, 74, 79, 80, 84–87, 84–85, 87 Software specification / Loop 79
Solutions 5–6, 61, 62–63, 69, 84
M Sort 15–16, 15–16
Starting up for the first time 8
Main functions 8 Station data 78
Manual mapping 31 Status 11
Mapping 11, 26–28, 30–31, 35–36, 37, 65 Sub Forms 17, 22–23, 22
Merge revisions 40 supplier 11, 26–27, 26–27, 31, 26–27, 37, 42, 64–65,
Move and resize fields 15 64–65, 78–79, 78–79, 82
multiple revisions 12 Supplier Data 26, 78
Supplier Data format 26
N System 11, 21, 37, 52, 64–65, 64–65, 67–69, 67–69,
78–79, 78–79
New Project 9, 69–70, 69
System Administration 69
New Revision 12–13, 12, 38, 40–41, 40–41, 80
Systemfiles 9, 76
Not connected Boards 47
T
O
the Select File(s) to Work with 13, 24, 37, 42, 63–65,
ObjectName 11, 71
63–65
Open 9, 20, 37, 70, 74, 88
Title1 11
Title2 11
P
PDA 5–6, 5–13, 8–9, 11–13, 22–27, 22–27, 30–31, U
30–37, 34–38, 40–41, 40, 44–49, 47–49, 65–66,
Undo Fill Down 19–20
65–66, 69–79, 69–75, 69–79, 80–82, 80–82, 83
Plant Design & Allocation 5–8, 8, 70
Prep 11 V
Preview data 29 Validate 5–6, 37, 89
Process Objects 22, 53–60, 57–59, 86 Validation 6, 26, 30, 36–37, 36–37, 69–73, 69, 71–
Project details 10, 81 72, 83–88, 83–89
Project Setup 10 Validation Queries 37, 71–72, 71–72, 83–86, 83, 86,
Project-data 9, 76 89
R W
Replace 16–18, 20 Workflow 5–6, 5
Report 10–11, 10, 34–39, 37, 39–40, 45, 64, 71–75,
71–75, 81–82, 81–82
Rev 11–13
Revision Note 12–13, 80, 82
Revisions 12, 38, 40, 80
S
S100 Boards 43
S800 Boards 46, 49
Select Files to import 26
Series Fill Down 19–20
Signal 30, 35, 38, 44–45, 44, 48–50, 48–50, 52–60,
52, 48–50, 64–65, 64–65, 67, 78–79, 78–79, 82–
88, 85, 87–88
Signal data 26, 27, 30, 59, 79
Signal Library 55–59, 55–57
Signal Pool 48–49, 48–49
Usermanual for Instrument Index Index • 92

04.1 User Manual PDA5 - 0

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

04.1 User Manual PDA5 - 0

Uploaded by

Copyright:

Available Formats

User manual for

Plant Design & Allocation 5.0

ABB Automation and Drives 3BSE020288D0005 en A i

2. MAIN FUNCTIONS ......................................................................................................8

2.2 New Project ............................................................................................................................................................ 9

2.3 Project Setup ........................................................................................................................................................ 10

2.5 General form functions ....................................................................................................................................... 13

ABB Automation and Drives 3BSE020288D0005 en A i

2.7 Validation ............................................................................................................................................................. 36

2.8 Compare ............................................................................................................................................................... 38

2.9 Edit data ............................................................................................................................................................... 41

ABB Automation and Drives 3BSE020288D0005 en A ii

2.11 Export ................................................................................................................................................................. 65

2.12 Control Builder M Interface............................................................................................................................. 68

2.13 System Administration...................................................................................................................................... 69

3.2 Validation Queries............................................................................................................................................... 83

ABB Automation and Drives 3BSE020288D0005 en A iii

ABB Automation and Drives 3BSE020288D0005 en A iv

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 5

Libraries User Interfaces etc.

Solutions for Forms

1.2.2 Workflow for PDA user

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 6

New Project Generate Signals CBM Integration

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 7

2.1 Starting up for the first time

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 8

2.2 New Project

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 9

2.3 Project Setup

This form is used to set up Document Header/Footer and suppliers.

2.3.1 Project details

ABB Automation and Drives 3BSE020288D0005 en A 10

Fill in Suppliers from which data shall be imported.

2.3.3 Document details

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 11

2.4.1 New revision

Select New Revision to create a new, empty, revision Index.

2.4.2 Copy revision

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 12

2.4.3 Support Web (not more supported in PDA BM 3.1)

2.5 General form functions

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 13

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 14

2.5.2 Move and resize fields

2.5.3 Save Form

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 15

2.5.5 Filter By/Excluding selection

Filter By Selection, right-click on the value to be filtered by. A click on

Filter function is used to build more complex filters than Filter by

Document number Lang. Rev. ind. Sheet

ABB Automation and Drives 3BSE020288D0005 en A 16

2.5.7 Apply/Remove filter