Professional Documents
Culture Documents
Customer PGGA
Main contractor
Order
Plant
Equipment
Title
Title Ref.
des.
Resp. dept.
PGGA-AE12
Doc. no. Language Rev.
Sheet 1
ABB Switzerland Ltd SM20170906 EN 0
No. sheets 10
Print: 28/09/2017 File: RTU Engineering Guideline_Rev0_Draft.docm ; Rev. 0
© Copyright 2011 ABB. All rights reserved. Ó ABB 2014
Contents
1. Introduction ............................................................................................................................ 3
2. Engineering Workflow............................................................................................................ 3
2.1 Excel formatting ........................................................................................................... 4
2.2 Excel Arrangement ...................................................................................................... 5
2.2.1 Column Arrangement for I/O sheet ............................................ 5
2.2.2 Column Arrangement for Sublines ............................................. 6
2.2.3 Signal type arrangement for I/O sheet ....................................... 7
2.2.4 Signal type arrangement for Sublines ........................................ 8
2.3 Process Object identification definition ......................................................................... 9
2.4 Changes in Network Tree ............................................................................................ 9
2.5 File Naming .................................................................................................................. 9
2.6 Excel Example ........................................................................................................... 10
1. Introduction
When exchanging engineering files between engineers and even between organization it is important
that all files were produced according certain standards. This allows efficient collaboration and supports
the prevention of errors and misunderstandings.
The following standard is according CH PGGA needs.
2. Engineering Workflow
RTUtil supports in newer releases the export of excel sheets with automatic excel interface. This leads to
the option to engineer signals in RTUtil directly. But CH PGGA has the strict standard to work for signal
engineering with the standard excel file only! Therefore do signal engineering only in the excel file.
CH PGGA standard workflow starts with the setup in RTUtil for network and hardware tree. Then an excel
export is done creating the standard excel file. From this moment on all changes doable in the excel file
are also done in the excel file.
To allow efficient signal engineering the standard excel file is formatted and the signals in the sheets are
arranged. (Since exporting is overwriting format and arrangements within the excel file, additional excel
exports shall not be used and RTUtil signal engineering shall not be done since this will require a further
excel exports)
Output of a RTU Engineering is therefore always an RTUtil file and an Excel file containing the latest signal
database and proper format.
Assign a color for each column group. Following column groups may exist: Signal and process
information, Archive, PLC assignments, HW assignments, communication lines, etc.
Assign colors for signal groups. For example signal types, Signals per hardware modules
2) Then Put the archive information, stating with archive enabling and Archive name
3) PLC assignments
4) Logic Functions
6) Host lines
2) Then Put the archive information, starting with archive enabling and Archive name
3) PLC assignments
1) I/O signal matching I/O cards starting with card on lowest rack address
Prepare Spare signals for available hardware ports. Disable RTUtil import for Spare signals.
4) SEV / SCC
System events and commands shall be configured only in excel as well and are defined in the I/O
sheet.
OI Standard:
OI1: 5
OI2: 5
OI3: 5
OI4: 8
OI5: 3
This is the standard OI configuration. Project specific OI may be defined and must be defined as
input for work packages.
The file name is for every project as follows and the file name is the same for all RTU files:
[customer]_[station].xxx
Example:
Unique_F_TS55.xlsx Unique_F_TS56.xlsx
Revision