Internal ABB document

MicroSCADA Pro SYS600

Bay Duplicator User Guide

hgghhh

ABB Power Grids Doc name: MicroSCADA Pro SYS600

Status
9AKK99999999 of document Draft
Issued by
department: XX Project name: SYS600 ADDON

Date: 2.5.2017 Doc. Type: XYZ

Lag.: En Creator name:

Revision: 1.0 Distribution External

Page: 1/7
Contents

0 REVISION HISTORY -------------------------------------------------------------------------------------------------- 3

1 INTRODUCTION ------------------------------------------------------------------------------------------------------- 4

2 USAGE-------------------------------------------------------------------------------------------------------------------- 6

2.1 WORKFLOW ------------------------------------------------------------------------------------------------------------ 6

2.2 SELECTING SOURCE--------------------------------------------------------------------------------------------------- 6
1.1.1. EXISTING PROCESS OBJECTS IN APPLICATION ----------------------------------------------------------------- 6

3 CONFIGURATION ----------------------------------------------------------------------------------------------------- 7

3.1 GENERAL---------------------------------------------------------------------------------------------------------------- 7

Printed copies are uncontrolled copis. This version is current as of May 2, 2017. Doc name: MicroSCADA Pro SYS600
For latest version check www.abb.com Dep: XX-XX
CCP No.: 9AKK99999999
Date: May 2, 2017
Page: 2/7
0 Revision History
Date Version Description/Changes Written by Approved
by

02.05.2017 1.0 First version AnBr

Printed copies are uncontrolled copis. This version is current as of May 2, 2017. Doc name: MicroSCADA Pro SYS600
For latest version check www.abb.com Dep: XX-XX
CCP No.: 9AKK99999999
Date: May 2, 2017
Page: 3/7
1 Introduction
Bay Duplicator Tool (BDT) copies process objects from one source bay to one or
several destination bays. The tool can also update certain attributes of process
objects, for example, updating the OX text of the source to all destination objects.

The source can be either a bay from the current application, or a collection of
objects stored in an SDB-file using the Import/Export Tool.

The destination bay must of course be modified for naming and addressing. This is
done in three steps:

1. Set the new Object Identifier

2. Change the addressing. This can be either by setting a new UN and new IED
name (IEC61850), or by setting an Object Address offset (RTU type solutions).
3. Set the Logical Name naming format. This can be either determined by the
Object Identifiers using SCL Importer tool settings, or by using a format string to
create unique names for process objects.

For successful duplication, it is important that the Logical Naming is well structured,
for example using the Object Identifiers. If the names are entered in an unstructured
way, the tool will have difficulties duplicating these.

When installing the SYS600 Addon package, an icon is created on page 2 in Tool
Manager (Application Objects tab)

Printed copies are uncontrolled copis. This version is current as of May 2, 2017. Doc name: MicroSCADA Pro SYS600
For latest version check www.abb.com Dep: XX-XX
CCP No.: 9AKK99999999
Date: May 2, 2017
Page: 4/7
Printed copies are uncontrolled copis. This version is current as of May 2, 2017. Doc name: MicroSCADA Pro SYS600
For latest version check www.abb.com Dep: XX-XX
CCP No.: 9AKK99999999
Date: May 2, 2017
Page: 5/7
2 Usage

2.1 Workflow

Shortly, the workflow is:

1. Set the source bay either by selecting using the OI-selector or an SDB-file using file selector.
2. Add first destination bay. Set the new Object Identifiers and addressing.
3. Determine Logical Naming. You can use Object Identifiers or a customized format string.
4. Check preview of the destination Bay. If there are no errors in naming or addressing you can
continue, otherwise you have to revise the faulty areas. For example, if the Object Identifier is
causing duplicate object names (NAME:INDEX NOT UNIQUE), you may have to use an LN
format string instead.
5. Make duplicates of the first destination bay and change Object Identifiers and addressing.
6. For more details, check the global setting ‘Create log files’.
7. Include the destination bays you want to update/create.
8. Click RUN!
9. Right-click on each destination bay and view log file or check process database.

2.2 Selecting source

1.1.1. Existing process objects in application

Printed copies are uncontrolled copis. This version is current as of May 2, 2017. Doc name: MicroSCADA Pro SYS600
For latest version check www.abb.com Dep: XX-XX
CCP No.: 9AKK99999999
Date: May 2, 2017
Page: 6/7
3 Configuration

3.1 General

Printed copies are uncontrolled copis. This version is current as of May 2, 2017. Doc name: MicroSCADA Pro SYS600
For latest version check www.abb.com Dep: XX-XX
CCP No.: 9AKK99999999
Date: May 2, 2017
Page: 7/7