USER’S MANUAL VERSION V3.

4
May 2014
DISCLAIMER:

Although Addsys has attempted to provide accurate information in this

document, Addsys assumes no responsibility for the accuracy of the
information. Addsys may change its contents without prior notice.

This document contains confidential information property of Addsys. No

part of this publication may be reproduced or transmitted in any form
without prior written consent of Addsys.

EDITORIAL CONTROL

Edition Date Comments

1.0 03/04/2014 Initial Edition
2.0 22/05/2014 New Editorial Functions

ATLAN V3.4 2/227 Ed 2.0

TABLE OF CONTENTS

1 INTRODUCTION ................................................................................................... 7
1.1 SYSTEM REQUIREMENTS ........................................................................... 7
1.2 INSTALLATION .............................................................................................. 7
2 LICENCE SETUP .................................................................................................. 9
3 WORKING PROCESS ......................................................................................... 13
4 BASIC CONCEPTS AND TERMS ....................................................................... 16
4.1 WORKING ENVIRONMENT ......................................................................... 16
5 GETTING STARTED ........................................................................................... 17
5.1 CREATE A NEW PROJECT ......................................................................... 17
5.2 WORKING ON A PROJECT ......................................................................... 19
5.2.1 Open a Project....................................................................................... 19
5.2.2 Insert a new Device ............................................................................... 19
5.2.3 Edit a Device ......................................................................................... 22
5.2.4 Delete a Device ..................................................................................... 22
5.2.5 Locate a Device ..................................................................................... 22
5.2.6 Connecting Devices ............................................................................... 22
5.2.7 Multisource and Multitarget Connections ............................................... 24
5.2.8 Edit a Connection .................................................................................. 25
5.2.9 Delete a Connection .............................................................................. 26
5.2.10 Grouped connections............................................................................. 26
5.3 DRAWING FACILITIES ................................................................................ 27
5.3.1 Edition Mode.......................................................................................... 27
5.3.2 Zooming ................................................................................................ 27
5.3.3 Project overview window ....................................................................... 27
5.3.4 Grid ....................................................................................................... 27
5.3.5 Tiptool.................................................................................................... 27
5.3.6 Views ..................................................................................................... 27
5.3.7 Multiple Working Areas .......................................................................... 28
5.3.8 Undo/Redo ............................................................................................ 28
5.3.9 Selecting Devices and Connections....................................................... 28
5.3.10 Dragging devices ................................................................................... 29
5.3.11 Redrawing connections ......................................................................... 29
5.3.12 Manual redrawing of connections .......................................................... 29
5.3.13 Inserting background images ................................................................. 30
5.3.14 Insert user’s text box.............................................................................. 30
5.3.15 Aligning devices..................................................................................... 30
5.3.15 Re-dimensioning of devices ...................................................................... 30
5.4 IEC 61850 SPECIFIC FUNCTIONALITIES ................................................... 31
5.4.1 DataSet Definition .................................................................................. 32
5.4.2 DataSet Edition...................................................................................... 34
5.4.3 Reports Definition .................................................................................. 35
5.4.4 Reports Edition ...................................................................................... 36
5.4.5 Logs Definition ....................................................................................... 37
5.4.6 Logs Edition ........................................................................................... 38
5.4.7 GSE Control Block Definition ................................................................. 39
5.4.8 GSE Control Block Edition ..................................................................... 40
5.4.9 SMV Control Block Definition ................................................................. 41
5.4.10 SMV Control Block Edition ..................................................................... 42
5.4.11 GOOSE connections ............................................................................. 42
5.4.12 SMV Connections .................................................................................. 45
5.4.13 MMS connections .................................................................................. 47
5.4.14 Hybrid IEC 61850 Connections .............................................................. 50
5.4.15 Other Functions ..................................................................................... 51

ATLAN V3.4 3/227 Ed 2.0

 5.5 Communication Configuration ....................................................................... 52
6 LOGICAL FUNCTIONS ....................................................................................... 54
6.1 LOGICAL FUNCTION LIBRARY ................................................................... 54
6.1.1 Logical Function Editor .......................................................................... 54
6.1.2 Logical Functions edition process .......................................................... 57
6.2 USING LOGICAL FUNCTIONS .................................................................... 57
6.2.1 Adding Logical Functions ....................................................................... 57
6.2.2 Mapping Logical Functions .................................................................... 59
7 LOGICAL FUNCTIONS SIMULATOR .................................................................. 64
7.1 PREPARING THE SIMULATION .................................................................. 64
7.1.1 Generation of test scenes ...................................................................... 65
7.2 SIMULATION PROCESS ............................................................................. 67
7.2.1 Signals assignment................................................................................ 68
7.2.2 Control points ........................................................................................ 68
7.2.3 Introduction of delays............................................................................. 69
7.3 SIMULTANEOUS SIMULATION OF SEVERAL LOGICAL FUNCTIONS ...... 70
7.4 SIMULATION OF GENERIC LOGICAL FUNCTIONS ................................... 71
7.5 SIMULATION MODES .................................................................................. 72
7.6 ANALYSIS OF RESULTS ............................................................................. 72
7.6.1 Presentation of continuous simulation results ........................................ 72
7.6.2 Presentation of Step-by-step results ...................................................... 74
7.7 DOCUMENTING SIMULATION RESULTS ................................................... 77
8 MAPPING OF TELECONTROL DATA BASES .................................................... 78
8.1 IMPORT OF THE TC_BD FILE..................................................................... 79
8.2 BD_TC FILE MODIFICATION....................................................................... 80
8.3 MAPPING OF TELECONTROL SIGNALS .................................................... 81
8.4 ASSOCIATION OF THE TC_BD FILE .......................................................... 81
8.5 ASSOCIATION OF TERMINALS TO SIGNALS ............................................ 82
8.6 ASSOCIATION OF IEDs............................................................................... 83
8.7 CONNECTIONS ASSOCIATED TO TELECONTROL .................................. 84
8.8 DRAWING OF CONNECTIONS ................................................................... 86
9 DOCUMENTATION ............................................................................................. 87
9.1 PROJECT DRAWINGS ................................................................................ 87
9.1.1 Drawing edition environment ................................................................. 87
9.2 CUSTOM FRAME DRAWINGS .................................................................... 92
9.3 LOGICAL FUNCTIONS DOCUMENTATION ................................................ 93
9.4 CONNECTIONS LISTS ................................................................................ 93
9.5 GSE AND SMV CONNECTIONS LISTS ....................................................... 94
9.6 MMS CONNECTIONS LISTS ....................................................................... 95
9.7 LIST OF OUT-OF-STANDARD LOGICAL CONNECTIONS ......................... 96
9.8 LISTING OF DEVICES ................................................................................. 96
9.9 DOCUMENTATION OF TELECONTROL DATABASES ............................... 97
9.10 VIEWING OF VLAN’s ................................................................................... 98
9.10.1 Documentation of VLAN’s ...................................................................... 99
9.10.2 VLANs viewer tools................................................................................ 99
9.11 VIEWING AND PRINTING DOCUMENTS .................................................. 102
9.11.1 Viewing of IEC 61850 files ................................................................... 102
9.12 Viewing svg files ......................................................................................... 104
10 DOCUMENTATION OF IEC 61850 FILES ..................................................... 105
11 TRACEABILITY AND CONTROL OF DOCUMENTATION ............................. 106
11.1 DOCUMENT MANAGEMENT PROCESS .................................................. 106
11.1.1 Users ................................................................................................... 107
11.2 New Project Creation .................................................................................. 107
11.2.1 Editing a Project .................................................................................. 108
11.2.2 Signing a Project ................................................................................. 108

ATLAN V3.4 4/227 Ed 2.0

 11.2.3 Rules to create new versions and revisions ......................................... 109
11.2.4 Signing Documents.............................................................................. 110
11.2.5 Verifying Signatures............................................................................. 111
11.2.6 Log Diary ............................................................................................. 115
11.3 CONTROL OF CHANGES.......................................................................... 116
11.3.1 Documenting deleted devices and connections ................................... 117
11.3.2 Documenting added devices and connections ..................................... 117
12 DEVICES CONFIGURATION......................................................................... 118
12.1 LOGICAL FUNCTIONS CONFIGURATION ................................................ 118
12.2 CONFIGURATION OF THE COMMUNICATIONS ...................................... 119
12.3 IEC 61850 DEVICES CONFIGURATION ................................................... 120
12.4 SSD FILE GENERATION ........................................................................... 121
12.4.1 Semantic selection............................................................................... 122
12.4.2 Selection of bays and voltage levels .................................................... 123
12.4.3 ssd file content..................................................................................... 124
12.4.4 Specific considerations ........................................................................ 125
12.4.5 Configuration errors ............................................................................. 126
12.4.6 Bays Highlight...................................................................................... 127
12.5 CONFIGURATION OF OTHER DEVICES .................................................. 127
13 LIBRARY OF DEVICES ................................................................................. 128
13.1 GENERIC CLASSES .................................................................................. 128
13.1.1 Project Generic Classes ...................................................................... 129
13.2 CREATION OF NEW DEVICES ................................................................. 129
13.2.1 Rules for the creation of images associated to IEDS ........................... 139
13.3 Generic devices definition ........................................................................... 140
13.4 Virtual Devices definition............................................................................. 140
13.5 DEVICES LIBRARY MANAGEMENT ......................................................... 141
13.6 DEVICES LIBRARY DOCUMENTATION ................................................... 142
14 CONNECTIONS LIBRARY............................................................................. 144
14.1 NEW CONNECTIONS CREATION ............................................................. 144
14.2 CONNECTIONS LIBRARY MANAGEMENT ............................................... 145
14.3 CONNECTIONS LIBRARY DOCUMENTATION ......................................... 145
15 NAMES AND SEMANTIC RULES .................................................................. 146
15.1 STRUCTURE AND FORMAT OF NAMES .................................................. 146
15.1.1 Elementary classes.............................................................................. 146
15.1.2 Basic fields’ classes ............................................................................. 147
15.1.3 Composed names’ classes .................................................................. 148
15.2 STRUCTURE AND CONFIGURATION OF THE DICTIONARY .................. 149
15.2.1 Generic copying rules .......................................................................... 150
15.3 AUTOMATIC GENERATION OF NAMES ................................................... 151
15.3.1 Names of IEDs .................................................................................... 151
15.3.2 Names of connections ......................................................................... 152
15.4 NAMES OF INTERNAL VARIABLES IEC 61850 ........................................ 152
15.4.1 Configuration ....................................................................................... 153
15.5 OBJECTS AUTOMATIC NAMING FUNCTION ........................................... 153
15.6 IMPORT AND EXPORT OF NAME RULES ................................................ 154
15.7 DICTIONARY DOCUMENTATION ............................................................. 154
16 INFORMATION IMPORT AND EXPORT ....................................................... 155
16.1 EXPORT OF FILES .................................................................................... 155
16.1.1 Export of XML Files ............................................................................. 158
16.2 IMPORT OF FILES ..................................................................................... 158
16.3 EXPORT OF LIBRARIES ........................................................................... 159
16.4 IMPORT OF LIBRARIES ............................................................................ 162
17 PROJECT ADMINISTRATION ....................................................................... 165
17.1 PROJECT ARCHIVE .................................................................................. 165

ATLAN V3.4 5/227 Ed 2.0

 17.2 BACKUP ..................................................................................................... 165
17.3 BACKUP RECOVERING ............................................................................ 165
17.4 ARCHIVED PROJECT RECOVERING ....................................................... 166
18 ATLAN’s ADMINISTRATION AND CONFIGURATION FUNCTIONS ............. 167
18.1 CONFIGURATION OF ATLAN ................................................................... 167
18.2 DELETION OF CORRUPTED IEDs ............................................................ 167
18.3 CERTIFICATES CREATION ...................................................................... 168
18.4 PROJECT BACKUP RECOVERING........................................................... 168
18.5 LANGUAGE SELECTION........................................................................... 169
18.6 PREFERENCES ......................................................................................... 169
18.7 IEC 61850 FILE VALIDATION .................................................................... 170
19 TEMPLATE DATA BOX CREATION .............................................................. 171
19.1 TRACING OF SEPARATION LINES........................................................... 172
19.2 TEXT AND IMAGE DEFINITION ................................................................ 173
19.3 TEXT AND IMAGE INSERTION ................................................................. 174
19.4 ADDITIONAL EDITION FUNCTIONS ......................................................... 177
19.4.1 Contents deletion ................................................................................. 177
19.4.2 Preview................................................................................................ 178
19.4.3 Templates edition ................................................................................ 179
19.4.4 Texts alignment ................................................................................... 180
19.4.5 Background image insertion ................................................................ 181
19.4.6 Zoom level ........................................................................................... 182
20 CUSTOMISED FRAMES ............................................................................... 183
21 IMPORT OF PROJECTS ............................................................................... 185
21.1 Project import from Web ............................................................................. 186
21.1.1 Device import....................................................................................... 187
21.1.2 Connection import ............................................................................... 188
21.1.3 Logical Function import ........................................................................ 188
21.1.4 Generic classes import ........................................................................ 189
21.1.5 icd files import...................................................................................... 190
21.1.6 Telecontrol Data Base import .............................................................. 190
21.1.7 Project import ...................................................................................... 190
22 EXPORT OF COMPLETE PROJECT............................................................. 191
22.1 Possible error messages (critical and minor) .............................................. 192
23 DETAILED ENGINEERING ............................................................................ 197
23.1 INTRODUCTION ........................................................................................ 197
23.2 MAIN FUNCTIONS ..................................................................................... 197
24 ANNEX A. INSTALLATION DETAILS ............................................................ 198
25 ANNEX B. EXAMPLE OF CREATION OF NAME AND SEMANTIC RULES .. 200
26 ANNEX C. EXAMPLE OF CREATION OF A DO/DA ALIAS DICTIONARY .... 210
27 ANNEX D. EXAMPLE OF IMPORT OF A PROJECT ..................................... 213
28 ANNEX E. TERMINALS TEMPLATE QUICK GUIDE ..................................... 221
28.1 Columns structure....................................................................................... 221
28.2 Recommendations ...................................................................................... 223
28.3 Solutions to Errors ...................................................................................... 224

ATLAN V3.4 6/227 Ed 2.0

1 INTRODUCTION
Thank you for using ATLAN, the substation engineering and documentation tool which
provides a state-of-the-art working tool able to integrate legacy technologies with the
new IEC 61850 standard in a friendly working environment.

The substation engineering process has experienced a number of changes due to the
introduction of new protection and control technologies. This has involved a gradual
reduction of the information contained in the substation project which drives to a loss of
knowledge. ATLAN has been designed to prevent this effect providing a working
environment that allows working criteria and methods to be unified thus facilitating
knowledge transmission inside the company.

ATLAN provides a working methodology that allows traditional drawings and wiring lists
to be generated providing, at the same time, the configuration files for the IEC 61850
substation devices. The tool is able to differentiate physical wires, which have only
documental information, from logical connections and their associated configuration
parameters that have to be contained in the configuration files. Thanks to this, it is
possible to work on a unified environment with a common information repository from
which all the documentation and configuration files are generated.

1.1 SYSTEM REQUIREMENTS

Operating System Requirements
* Intel® Pentium® III or higher processor
* Microsoft® Windows® 8, 8.1, Windows® 7, Vista; Windows XP Professional, Home
Edition, or Tablet PC Edition with Service Pack 2; Microsoft Windows 2000 with Service
Pack 4; Windows 2003 Server or higher.
* 512MB of RAM (1GB or higher recommended)

Technical Requirements
* Java: jdk 1.6 from Sun Microsystems Incorporated
* Adobe Reader 7.0 or higher from Adobe Systems Incorporated
* 100 MB of available hard-disk space (without object libraries)
* A screen resolution equal or higher than 1280x1024 or 1400x900 pixels is
recommended

1.2 INSTALLATION
To install ATLAN, invoke the file “ATLANInstall.exe” included in the CD and follow the
instructions.

Once the installation process is completed, the ATLAN icon will appear in your desktop.

If you are already using ATLAN, it is mandatory to uninstall previous version before
proceeding with the new installation.

When ATLAN is started up for the first time, the user has to set the path of the Java
machine and the pdf reader. Once this is done, ATLAN is ready to be used.

ATTENTION! ATLAN requires that your computer be configured with the following
applications or complements:

ATLAN V3.4 7/227 Ed 2.0

 - Java machine properly registered in the operating system. On the contrary,
ATLAN will not be able to start up.
“jdk” java environment. Electronic signatures and document management
require the java jdk environment properly installed and registered. If you do not
have the jdk java environment, you can download a free license from
http://www.oracle.com/technetwork/java/javase/downloads/index.html.
- Install this application following the installer instructions.
- Pdf reader. To view documents generated by ATLAN requires a pdf file viewer to
be installed. If you do not have the pdf reader, you can download a free license
from http://www.adobe.com/es/products/reader/. Install this application following
the installer instructions.

Once the jdk environment is properly installed in your computer you have to set the jdk
java path. This has to be done the first time ATLAN is run. To set the path, click “Explore”
and select the “Bin” folder inside the jdk folder.

Once ATLAN installation is completed, you have to run ATLAN to register the licence as
explained in chapter 2. Once the licence is properly activated, you have to define your
own working environment as described in section 18.1.

ATLAN V3.4 8/227 Ed 2.0

2 LICENCE SETUP
To install ATLAN’s licence, it is necessary to follow the licence generation and installation
procedure. This procedure can only be carried out by the Administrator. It consists of
three steps:

1. Install ATLAN following the instructions of the installer as described in previous

chapter.
2. Generate the activation code. Once ATLAN is installed the following window is
shown

Click on “Generate activation file” and the following Windows will be opened. Fill
in the required data including the serial number provided with the CD.

Clicking on “Generate”, the file “LicenseActivativationFile.txt” will be generated.

This file is stored in ATLAN main path, C:\AtlanGraphEditor as default path. This
file has to be sent by email to license@atlan61850.com.

It is possible to send this email automatically by clicking “Send”.

Include a valid email address in the former dialog box and any additional
comments in the second box.

ATLAN V3.4 9/227 Ed 2.0

 You will receive an email with the file “License<name>.lic” (The term <name> will
contain the name entered in the former questionnaire).

This file has to be extracted from the email and stored in any folder. It is advised
to save it in the default ATLAN folder C:\AtlanEditorGrafico. Once you have the
file stored, you can proceed to validate the licence.

3. Licence installation. Restart ATLAN and the following Window will be shown.

Click on “Licence Activation”. If the “publicCerts.store” file is not stored in the

ATLAN root folder, the following window will be shown.

The file can be browsed by clicking on “OK”. Once the file is manually located,
the licence installation wizard will be automatically started.

ATLAN V3.4 10/227 Ed 2.0

 Choose the option Install a licence certificate and click “Next”. The following
window will be shown.

Locate the file “License<name>.lic” and click on “Install the licence certificate”.
The result of the operation will be shown. By clicking on “Next”, the Licence data
will be shown.

ATLAN V3.4 11/227 Ed 2.0

 The licence installation process will be completed by clicking on “Finish”. It is
necessary to restart ATLAN to load the licence. From this moment on, ATLAN is
fully operative.

ATLAN V3.4 12/227 Ed 2.0

3 WORKING PROCESS
The following figure shows the components of the substation engineering,
documentation and configuration process, in the most general case of using IEC 61850
IEDs together with traditional IEDs.

ATLAN generates the models of standard IEDs – and equipment in general – that will be
used in a project. The generation of new models of devices and connexions, as well as
the maintenance of the database of those models, is described in chapter 13.

IEDs
MODEL
IED.icd GENERATOR
IED.icd

IEDs
LIBRARY

DOCUMENT
FRAMEWORK
LAN
VLAN
CONF
ENGINEERING
AND DESIGN
DOCUMENTATION RULES
TOOL
LOGICAL
FUNCTIONS
CONF COMMUNICATION
CRITERIA

PROTECTION PROJ.scd
SETTINGS
IED1.cid PROJECT
IED2.cid DOCUMENTATION
IEDn.cid DOC
OTHER
SETTINGS DOC
DOC
IEDs 61850
CONFIGURATION
FILES
IEDs
CONFIGURATOR

IED1
IED2

IEDn

Substation design is carried out in the graphical working environment using standard
models, the documentation framework and the design rules.

Following this procedure, the substation-engineering project is developed in a unified

working environment with a single information repository for which the following
documents are generated:

ATLAN V3.4 13/227 Ed 2.0

 - Project documentation. Including drawing, wiring lists, material lists, etc. See
chapter 9.
- Communication configuration information. LANs, Routers, VLAN’s, etc. See
section 5.5.
- Logical Functions configuration. See chapter 6.
- IEC 61850 files configuration. See chapter 12.

Physical connexion information can be exported to Excel file using the detail engineering
facilities. Physical information of the project can be exported to an XML file that can be
transferred to a construction tool. See detailed engineering manual for more details.

Configuration information is transferred to proprietary configuration applications where

additional settings might need to be introduced to form the final configuration files that
have to be downloaded into every IED in the substation.

The development of a project comprises the following steps:

1. Project creation. See section 5.1.

2. IED’s library review. Before starting the project, it is advisable to verify that the
device, connection and logical function libraries contain the components required
to implement the project. If any component is missing, please follow the
instructions indicated in section 6.1 and chapter 13.
3. Insert IEDs and other components. It is recommended to insert the IED and other
components before proceeding to lay connections since the automatic
connections routing algorithm will produce a better layout and the need for
manual redrawing will be reduced. See section 5.2 for details on how to insert
IEDs and components.
4. Physical connection. See section 5.2.6.
5. Logical Connections. Logical connections can only be established between IEDs
once the communication connection between them has been defined. See
sections 5.2.6 and 5.4.
6. IEC 61850 IED’s data structure configuration. See section 5.4.
7. IEC 61850 Connections. See sections 5.4.11, 5.4.13 and 5.4.7.
8. Logical Functions mapping. All the connections of the projects have to be defined
before proceeding to map the Logical Functions. See section 6.2.2.
9. Telecontrol database mapping. See chapter 8.
10. Documents generation. See chapter 9.
11. Configuration generation. See chapter 12.

ATLAN working environment is a very flexible tool that allows different types of projects
to be implemented:

1. Specification projects. The purpose of these projects is to produce the functional

specification of a substation. This specification may be generic and therefore be
used as a reference to develop similar projects or a more detailed specification
that may be the initial step of an engineering project.
2. Generic Engineering projects. The purpose of these projects is the
implementation of the basic engineering of a substation. These projects include
all the necessary details to fully depict the functionality of the substation. The
degree of detail may be defined by the user.
3. Detailed engineering projects. This type of projects develops all the details of the
connexion between substation devices. From the basic engineering project, a
limitless number of detailed projects can be created in order to show every
implementation detail that may be required for the construction, commissioning
and maintenance of the substation.

ATLAN V3.4 14/227 Ed 2.0

ATLAN V3.0 and all the following version includes advanced functionalities for substation
specification. In the new IEC 61850 working environment, it is possible to generate the
ssd file from the single wire diagram and the functional association between single wire
elements and Logical Nodes.

It is also possible to define specifications for substation that combines legacy

technologies with IEC 61850 devices. See section 12.4 for a detailed description of the
functionality and related facilities.

ATLAN V3.4 15/227 Ed 2.0

4 BASIC CONCEPTS AND TERMS

4.1 WORKING ENVIRONMENT

ATLAN provides a working environment divided into three areas:
- Working area. This zone is used to draw the project inserting devices and
drawing connections.
- Objects library area. It contains the models of the IEDs, connections and Logical
Functions that will be used to develop the project.
- Project overview area. It shows the whole project. The grey zone shows the
contents of the working area.

Project overview Working area

Library area

A Menu bar and a Tool bar provide access to ATLAN functions and facilities.

By placing the cursor over every function icon, a description of its functionality is
automatically shown.

WARNING: The aspect of the windows and dialog boxes shown in this manual may
change depending on the operating system configuration. In any case, the contents will
remain the same.

ATLAN V3.4 16/227 Ed 2.0

5 GETTING STARTED

5.1 CREATE A NEW PROJECT

To create a new project use the submenu “New Project” of the menu “File” or click the
icon of the function bar. This function is only available when there is no project in use.

The following window allows all the data required to start up a project to be fulfilled.

In addition to the name of the new project, the following information needs to be
introduced:
- User data including name, password and level of every user.
- The name of user’s custom views. These views will be applied to IEDs and other
devices.
- The name of user’s connection views. These views will be applied to connections.

User views can only be defined when the project is created. It is advisable to create
enough views in order to have flexibility when generating documentation.

Connexion views can be created at any moment during the life of the project.

Multiple instances of both user and connection views can be created by choosing the
number of instance in the box “Multiple instances”. Views created using this method will
be identified by the name follow by an ordinal number.

Once the project is created, it has to be stored in the desired location. The internal data
structure of the project is automatically generated, including all the information related to
its associated versions and revisions.

ATLAN V3.4 17/227 Ed 2.0

The following step is the creation of users’ signatures by selecting the “Preferences”
submenu in the “Tools” menu, which will provide access to a pop-up window as that
shown next.

Once all the signatures have been generated, the project has to be saved to store
signatures and related information. Now the project is ready to be used by the Author.

Connections’ views can be added, modified of deleted at any time during the edition of
a project by selecting submenu “Add Connections Views” within the “Tools” menu, which
provides access to the following window.

A new project has to be created not only for the design of a substation-engineering
project but also for the creation of a functional specification.

ATLAN V3.4 18/227 Ed 2.0

5.2 WORKING ON A PROJECT
To work on a project you have to open an existing project or define a new one. You can
only work on an existing project if you have the User name and the key information.

5.2.1 Open a Project

To open a project you can choose the “Open” submenu in the “File” menu or click on the
icon. A window to explore files will be automatically opened.

Once the project is located and opened,

it will be loaded in ATLAN working area.
Users need then to log in introducing
their Name, Key and Level. By clicking
on “Accept”, the project will be ready to
be used.

5.2.2 Insert a new Device

To insert a new device, you have to choose the device
to be inserted by clicking on it in the device library;
then every time you click on the working area, a new
device of that type will be inserted on the point where
you have clicked. The multiple items insertion process
is stopped either when you select the edition mode by
clicking on the icon, or when you select any of the
elements of the project by clicking on them.

When a new device is inserted, a dialog window pops-

up to allow particular information of the device to be
entered. There are three different types of devices:

- Simple device. To incorporate the device to

the project, a unique name has to be given and
the device has to be associated to at least one
of the views of the project.

By setting the “Label creation without visibility”,

option the device will be replaced by a label
when the active views have not been
associated to it.

The “Remarks” field allows comments and

explanatory notes to be incorporated. These notes are shown when the tool-tip
is activated.

ATLAN V3.4 19/227 Ed 2.0

 - Multifunctional devices. The internal functionality of these devices is represented
by means of ANSI codes. At least one code has to be selected.

It is advisable to select only the codes related to the project in order to simplify
and clarify drawings and other type of documentation.

For those devices with communication

capabilities, the communication parameters
can be configured as explained in next
paragraph.

- IEC 61850 devices. The internal functionality

of these devices is represented by means of
Logical Nodes (LN’s). At least one LN has to
be selected.

It is recommended to select only the LNs

related to the project in order to simplify and
clarify drawings and other type of
documentation.

When the automatic name insertion function

is enabled, it is not possible to introduce the
name of the inserted device. See chapter 15
for detailed operation of this functionality.

Communication configuration parameters

can be set by clicking on “Communication
parameters”. The configuration of
communication parameters can be
introduced at any moment during the
production of the project, before generating
the configuration files.

The following pop-up window is opened to allow the parameters of every port to
be set.

To introduce common parameters click on “Multiple edition”.

To configure all the parameters of a port, click on the corresponding “Edit” button.

The following pop-up window is opened to allow the parameters of the port to be set.

ATLAN V3.4 20/227 Ed 2.0

When the automatic insertion of names is active, it may be not possible to introduce the
names of the devices. See chapter 15 for details on this functionality.

When the communication port supports IEC 61850 communications, the parameter
“ApName” can be configured as specified by the standard IEC 61850-6.

If the icd file of IED model has preconfigured information, it is possible to use these
parameters by clicking the button “ICD Data”. The following window will be opened
showing the list of all the “ConnectedAP” blocks of the icd file.

The button “Show” will open a window with the content of the “ConnectedAP” chosen.

Clicking on “Accept” preconfigured data information will be automatically loaded in its

corresponding place. The user can freely modify any of the loaded parameters.

ATLAN V3.4 21/227 Ed 2.0

For every communication port, it is possible to define a Multicast Ethernet address filter
to prevent multicast Ethernet frames to be flooded all over the network – thus limiting the
scope of GOOSE messages and controlling the traffic in the LAN –.

5.2.3 Edit a Device

Select the device to be edited and click on the “Edit” contextual menu. The corresponding
dialog pop-up window is shown thus allowing the original data to be changed by the user.

When the automatic name insertion function is enabled, some limitations in the name
editing may apply. See chapter 15 for more details.

5.2.4 Delete a Device

Select the device and press the “Sup” key or click on the icon

All the connections related to this device will be automatically deleted.

Multiple devices can be deleted by selecting them and following the same procedure. All
the Logical Functions totally or partially mapped to this device will also be deleted.

This action cannot be undone. If a wrong device has been deleted, quit ATLAN and open
the project again to recover previous state of the project.

5.2.5 Locate a Device

Select the “Search” submenu of the “Edit” menu to locate a device or a connection. The
corresponding device or connection will be selected and highlighted.

5.2.6 Connecting Devices

To define the connection between two or more devices, the type of connection has to be
chosen from the Connections library. There are three generic types of connections:
- Point-to-Point.
- Multi-source. Several devices are connected to the same destination device.
- Multi-target. One device is connected to several destination devices.

Connections model the interchange of information between devices, either by means of

physical signals – like binary signals, analogue currents and voltages, etc. – or by means
of protocols including the different IEC 61850 communication modes.

Consequently, there are different modes of every one of the above-mentioned generic
types:

- Physical connections. They model Binary signals, Currents and Voltages.

ATLAN V3.4 22/227 Ed 2.0

 To create a new connection, select the
connection type, click on the origin of the
connection and drag the mouse over the
destination device. The following pop-up
window is opened to allow the introduction
of the parameters of the connection.

The “Connection” block shows the

physical ports that will be used in every
device to establish a connection. Both
ports have to be physically compatible.

The “Label” field in the Identification area

identifies the connection, whereas the “Alias”
field is the short name shown on the drawings of
the project.

If the “Visibility” checkbox is not selected, the

connection will not be shown on the drawings.

If the “Connection list” checkbox is not selected,

the connection will not be shown on the connection list.

Click on the “Views” button to select the

connection views that will be shown for the
connection.

Click on “Accept” to finalise the connection

definition process. A line will automatically be
drawn between the origin and destination device.
The aspect and colour of the line depends on the
definition of the line model chosen from the
connection library, as described in section 14.1.

- Logical Connections. They model the interchange of information by means of

different IEC 61850 protocols.

These connections require the same information than the physical connections
explained in previous paragraph.

Logical connections have to be established between functional associations like

an ANSI function or between logical nodes for those devices that do not have a
valid .icd file. This type of connections can also be used to specify relations
between LNs during the specification of a substation.

Logical connections require that both devices origin and destination have a
communication port connected to a LAN or directly connecting both devices.

ATLAN V3.4 23/227 Ed 2.0

 - Hybrid Logical Connections. They
model the interchange of information
between an internal function of a
device and a physical terminal of
other device through a physical
terminal of the origin IED. They are
formed by two parts: the first one
describes the relation between the
internal function of the device,
modelled by and ANSI code or a
Logical Node, and a physical terminal
on that device. The second part models a physical connection between the two
terminals of the interconnected devices.

- Double Hybrid Connection. They

model the interchange of
information between internal
functions – or logical blocks – from
different devices, which use
physical signals, logical or
analogical, to interchange such
information.

If one of the connected IEDs is an

IEC 61850 device, the “Load Data
Object” is activated allowing the
object that has to interact with the
physical interface to be defined. See section 5.4 for more details.

- IEC 61850 connections. There are three types of IEC 61850 connections:
o MMS
o GOOSE
o SMV

IEC 61850 connections are logical connections with and extra field of specific IEC
61850 information. See section 5.4 for detailed information.

5.2.7 Multisource and Multitarget Connections

When a signal has to be connected to more than one device, Multisource or Multitarget
connections have to be used. Multisource connections allow several outputs to be
connected to a single input. Multitarget connections allow one output to be connected to
several devices.

To create such connections, the desired connection type has to be chosen from the
connection library. By clicking on the origin of the connection and while holding the right
button dragging the mouse to reach one of the devices to be connected. While dragging
the mouse a line will be drawn showing the actual origin of the connection. The following
window will be show after releasing the right button of the mouse over the target device.

ATLAN V3.4 24/227 Ed 2.0

“Connection” and “Identification” blocks can be filled as per other connection types. The
block “Multiconnection – Target” allows other connection participant to be included.

The block “Target Device list” shows all the devices of the project. Devices associated
to this connection have to be selected by clicking the name of the device and clicking on
the button “>>”. This will add the selected device in the “Target Devices” block.

Select the connection terminal of every device associated to this connection by selecting
the device clicking on his name on the “Target Device” block. The available connection
terminal of the selected device will be shown on the block “Connection Point”. Click on
the terminal that has to be associated to this connection. This operation has to be
repeated for every device associated to the connection.

5.2.8 Edit a Connection

Select the desired connection and activate the contextual menu by clicking on the right
button of the mouse. When the “Edit” menu is selected, a pop-up dialog window is shown.
The contents of the windows depend on the connection type. Only those parameters that
can be changed are active.

When editing Multisource and Multitarget connection a new button “Create new
Connections” allows new devices to be associated to this connection. By clicking this
button, the following window is opened.

ATLAN V3.4 25/227 Ed 2.0

Following the process depicted above, new devices can be added to the connection.

5.2.9 Delete a Connection

Select the connection and press the key “Sup” or click on the icon.

5.2.10 Grouped connections

Several point-to-point connections between two devices can be grouped in such a way
that they can be visualised as a single connection,
yielding to simplified connection drawings while not
losing any piece of the information to be finally
included in the project. In addition, such information
will always remain available to develop more
detailed designs.

Two connections can be grouped by selecting them and activating the contextual menu
“Join Connections”. A unique name has to be given to the group.

By activating the “Individual Visibility” box, all the corresponding connections will be
shown separately – i.e., as if they were not grouped –.Also, when selecting any of the
separate connections and disabling this option, they are shown again as a single
connection. Multiple point-to-multipoint connections that have the same origin and
destinations can also be grouped into a common connection. By activating the contextual
menu “Join multiple connections”, the following
window with all the connections that share the
same connection points – which can therefore be
grouped into a same connection – is displayed.

Once the connections to be grouped are

selected, the design process is identical to that
previously described for point-to-point
connections.

ATLAN V3.4 26/227 Ed 2.0

5.3 DRAWING FACILITIES

5.3.1 Edition Mode

By clicking on the icon, the devices insertion mode becomes disabled and edition and
drawing functionalities become activated. This mode is automatically disabled when a
device of the library is selected.

5.3.2 Zooming
The zoom can be continuously controlled by turning the mouse’s wheel. The following
functional icons permit also to control the zoom:

- Resizes the project so that it fits in the working area

- Resizes the area selected with the mouse so that it fits in the working area
- Increases the zoom factor
- Decreases the zoom factor

5.3.3 Project overview window

The overview window contains a whole view of the project. The grey square zone shows
the part of the project presented on the working area. The grey square can be dragged
by holding the right button of the mouse. The view shown on the working area follows
the movement of the grey square zone, which can be dragged with the mouse.

5.3.4 Grid
The grid can be activated as desired in order to facilitate the precise placement of the
devices in the working area. The grid can
be activated by clicking the icon. Grid
resolution can be set at the “Preferences”
submenu in the “Tools” menu.

5.3.5 Tooltip
The Tooltip help function permits to
visualise the relevant information of the
device or connection over which the
mouse is placed at any time. This function
becomes enabled or disabled,
correspondingly, by clicking on the icon.

5.3.6 Views
ATLAN provides simplified views of the
project. The views are classified in
standard views and user defined views. By
activating a view, only the devices
associated to that view are shown on the
working area. Connections between these
devices are also shown. Connections
between the devices in a view and other
devices not included in that view are shown as labels, if the corresponding option has
been activated.

ATLAN V3.4 27/227 Ed 2.0

The devices included in a project are unique, and they are only shown on the views to
which they have been associated during the design. If a device is displaced in a particular
view, it will also be automatically moved in the rest of views. Only labels belong to a
particular view. They can thus be freely moved without that it has any effect on the aspect
of the rest of the views in the project. It is required to save the project in order to maintain
the labels in the same position where they appear in the active view at each moment.

5.3.7 Multiple Working Areas

When the project has a large number of components and Bays, it is possible to define
new working areas; a bay o a group of elements can be created in every area. All the
areas belong to the same project so when drawing are created several working areas
can be included.

By choosing the submenu “View – Open New Scheme” a dialog box is opened allowing
the name of the new working area to be defined.

It is possible to define connections between elements placed in different working areas.

The new connection is started as usual. When the connection line is shown, click on the
tap of the working area containing the destination device. The selected working area is
opened so that the connection can be finished as usual.

Once the connection is finished, a label will be shown including the IED origin
information.

When a drawing including devices from more than one working area is produced, the
connections between devices originally placed in different working areas will be shown
as straight lines.

5.3.8 Undo/Redo
The icon undoes the last action.

The icon redoes the last action.

These actions are limited to graphical modifications such as connection redrawing, node
dragging, etc.

5.3.9 Selecting Devices and Connections

Devices can be selected in the following ways:
- By clicking on the device. Devices with functional blocks such as ANSI codes or
Logical Nodes will be shown in dark grey colour; while simple devices will be
highlighted in green.

- To select several devices at the same time, click on one of them and, holding the
“Shift” key pressed, click on every one of the rest of devices to be selected. The
selected devices will be also shown in dark grey colour.

By using the “Search” function and entering the name of the device, the device
will be also shown in dark grey.
Connections can be selected in the following ways:
- Place the cursor over the connection until the pointer change to , then click and
the connection will be highlighted in green.

ATLAN V3.4 28/227 Ed 2.0

 - Selecting the alias of the connection, by clicking on its name.
- By using the “Search” function and entering the name of the connection. The
selected connection will be displayed in dark grey.

Multiple elements – devices and/or connections – can be selected by drawing a rectangle

in the working area, holding the left button of the mouse while dragging it. All the
elements inside the rectangle will be selected.

5.3.10 Dragging devices

By selecting a device, it can be dragged by holding the left button of the mouse while
dragging the mouse towards the desired position.

When moving a device, all its connections will remain attached to it – and will be
automatically redrawn –. This may cause the loss of the correct appearance of the
connections, which may require the redrawing of some of them. It is recommended to
place all the devices in their final locations before drawing the corresponding
connections.

The icon allows blocking the functionality of automatic rerouting of connections.

Depending on how the devices and the connections are placed on the working area, the
blocking function can facilitate the process of moving a device while maintaining the
appearance of the physical connections.

5.3.11 Redrawing connections

Redraws the selected connections.

Redraws all the connections.

Redraws the selected connection using special rerouting algorithm. This allows
straight connections to be drawn crossing over other devices. This may be useful to draw
single wire diagrams.

5.3.12 Manual redrawing of connections

Automatic redrawing of connections is carried out by means of routing algorithms that
consider the physical distribution of the connections in an equitable way, the minimum
distance between them, etc. The result may not be statically adequate or may not
properly reflect the functionality of the project, and users can always redraw manually
certain connections. This can be done by means of the following facilities:

- Changing the connection point of the connection line in the origin or destination
device. Click on the connection point and drag the mouse holding the left button
pressed. All the connection points of the device will be highlighted in red colour.
Move the line to the new connection point holding the left button of the mouse.
When the device has been created with forced terminal points, it is not possible
to change connection points.
- Adding bending points. Click on the point of the connection where the new
bending point has to be added.
- Moving connections segments. Click on a bending point and move the mouse
holding the left button.
- Deleting bending points. Select the connection and click on the bending point to
delete. Press key “Del” to delete.

ATLAN V3.4 29/227 Ed 2.0

It must be considered that ATLAN draws connections in orthogonal mode.

5.3.13 Inserting background images

By activating the “Insert” submenu in the “Edition” menu, background images in bitmap
or jpeg format can be inserted in the project. This functionality can be used to show main
distribution boxes or other auxiliary devices.

5.3.14 Insert user’s text box

The legend of a project and Author’s comments or notes can be inserted by means of
text blocks.

By clicking on icon , a framed text block is inserted in the project.

By clicking on icon , an unframed text block is inserted in the project.

To introduce or modify the text of a block, click on the block with the right button of the
mouse and select the “Edit Generic Name” contextual menu.

Return lines are introduced by pressing the “Shift+Return” keys simultaneously. The text
insertion is completed by pressing the Return key.

The font and the size of the inserted text can be defined in the “Preferences” submenu
located in the “Tools” menu. See section 18.6.

5.3.15 Aligning devices

By selecting the “Align nodes” submenu in the “Edit” menu, a set of preselected devices
can be aligned horizontally or vertically. It has to be considered that the selected devices
will be automatically moved in order to get them aligned with the desired position, so it
may be necessary to have some free space around them to prevent device overlapping.

5.3.15 Re-dimensioning of devices

Simple devices that have an associated image can be manually re-dimensioned.

By selecting the device to be modified and clicking on the right button of the mouse, it
becomes activated the contextual menu which contains the device re-dimensioning
functionality.

ATLAN V3.4 30/227 Ed 2.0

This option can be especially applicable for elements like lines, which may need to be
longer or shorter than the default size.

Devices can be re-dimensioned in all directions.

It is possible that, when re-dimensioning a device, its labels can only be relocated in
positions that are not appropriate for, for instance, developing documents. This is due to
the positioning of the labels when loading the device. In that case, the correct positioning
of the labels can be achieved by closing the project and re-opening it after having re-
dimensioned the devices.

The re-dimensioning functionality can be disabled from the same contextual menu, and
it is also automatically disabled when closing the project.

5.4 IEC 61850 SPECIFIC FUNCTIONALITIES

The following facilities can only be used with IEC 61850 compliant devices whose
models, therefore, include a valid icd or cid file. See section 13.2 for further details on
IEC 61850 device modelling.

IEDs that are modelled according to the IEC 61850 standard have associated an icd or
cid file. It describes the capabilities of the device according to the definition of the
standard. When such an IED is instantiated in a project, a cid file is automatically
generated for every particular instance. This file will store all the configuration data that
can be defined in ATLAN:

- IP address and other communication’s configuration parameters.

- Datasets. In IEC 61850 IEDs, a new submenu in their contextual menu can be
activated in order to visualise, edit or create Datasets. When activating these
functions a new window of type XML explorer is displayed.

ATLAN V3.4 31/227 Ed 2.0

 - Reports and Logs. As in the previous case, a new specific menu allows new
Reports and Logs to be visualised, edited or deleted from the existing Datasets.

When the icd file of the device does not have information regarding Datasets, Reports
or Logs defined – or when such information is incomplete –, users will need to define the
Datasets one by one in order to be able to define, afterwards, the Reports and the Logs
from those Datasets. It is recommended to define the Datasets, Reports and Logs before
carrying out the connections of a project. Hence, the information of a project needs to be
specified in the following order:
- Define all the Datasets.
- Define the Report controls and Log controls.
- Define the GSE controls if GOOSE messages are to be used in the project.

Users have to be aware of the limitations of the IEC 61850 device being configured.
Namely, the maximum number of Datasets, Reports and Logs, as well as its rules or any
other specific limitations – related to the data structure of the device –, as ATLAN does
not have the detailed specification of every particular IEC 61850 device and its main task
is limited to verify that the standard is fulfilled in the broader sense. ATLAN verifies the
service definition block of the icd file against the server data model. User is informed
about device capabilities detecting any mismatch between service declaration and
configured services in the server. Every time cid file is edited, the following pop-up
window informs the user about capabilities and limitation of the device.

If the user chooses to keep detected limitations, ATLAN will not allow new elements to
be created if they are out of the capabilities of the device. On the contrary, if the user
clicks “NO, I want to ignore validations” it will be possible to create new elements without
any limitation. User has to be sure about the real capabilities of the device in order to
prevent the creation of a file that will not be supported by the device.

IMPORTANT NOTE: icd and cid files cannot be edited using Windows notepad or other
text editor. By editing with these tools the file will be corrupted. It will not pass the
validation process and the scd file produced will not be IEC 61850-6 compliant.

5.4.1 DataSet Definition

To define a new DataSet in an IEC 61850 device, open the contextual submenu “Edit
cid” must be used. The following pop-up window will be automatically displayed:

ATLAN V3.4 32/227 Ed 2.0

To create a new Dataset, select the LN where the DataSet has to be located and click
on “Create Data Set”. A new area will be enabled on the bottom-right part of the window,
with the dialogue fields required to introduce the information of the new Dataset.

It has to be considered that the buttons to create, modify or delete control block are
automatically activated depending on its possible use according to the standard IEC
61850-6.

Once the name and the description of the new DataSet introduced, the DO’s or DA’s that
will constitute the DataSet must be selected. A DO or DA is selected by browsing the
tree-folder of the cid. Once found and selected, such data is added to the DataSet by
clicking on the “Load Data Object” button. In the case of any mistake – or at any time if
required –, a DO or DA can be deleted by means of selecting it from the list and then
clicking on the “Remove Data Object” button. DO and DA can also be selected by
choosing a LN and selecting the Do and DA from the combo lists of the block DO/DA.

The information of the LN where the DataSet is being created is presented at the box
“LN information”.

The contents of the Datasheet can be visualised by clicking on “Show”, after which the
following window is displayed.

ATLAN V3.4 33/227 Ed 2.0

If the structure is correct, the new DataSet is stored by clicking on the “Save” button. It
is recommended to verify the compliance of the new file to the IEC 61850 standard by
clicking on “Validate”.

By clicking on the “Refresh Tree” button, the contents of the new cid file are shown.

All the information will be automatically stored when the project is saved.

5.4.2 DataSet Edition

When the content of a DataSet is incomplete o erroneous it is possible to edit it to delete
errors or add missing data.

Select DataSet that has to be edited by browsing the data tree. Once the DataSet is
selected, click on “Edit data Set”. If the selected DataSet is not being used by any Control
block, the following window will be opened.

ATLAN V3.4 34/227 Ed 2.0

The content of the DataSet being edited is shown on the right side of the window. In the
upper part, the actual DataSet content is shown. To remove any of the data, it has to be
selected and the “Remove FCDA” button has to be clicked.

To add more data to the DataSet, the same procedure as for DataSet creation has to be
followed. That is to say, select the data from the tree and click on “Load Data Object”.

When the DataSet selected for edition is already associated to any kind of Control Block,
A window with actual configuration will be shown. The user has to determine if this
operation can be executed in function of the engineering process carry out in the project.

By Clicking “Accept” the following notice will be shown describing the limitations that will
be applied to the edition process in order to keep the coherence of cid file content.

5.4.3 Reports Definition

To define a new Report, at least a DataSet has to be already defined in the icd/cid file of
the selected device.

To create a new Report, the LN where the Data Report will be created must be selected
first from the tree-folder. Then, after clicking on the “Create Report Control” button, a
new area with the dialogue fields required to introduce the information of the new Report
will be enabled on the bottom-right part of the window.

ATLAN V3.4 35/227 Ed 2.0

The attributes of the Report, such as the trigger options and the rest of optional fields,
can be completed by introducing the required values in the corresponding dialog boxes.

Click on “Accept” to store the new Report. A new window will automatically show the
contents of the Report in scd format, allowing users to verify the correctness of the
structure and the information. The cid file of the device will be automatically updated with
this information when saving the project.

It is recommended to verify the compliance of the new file to the IEC 61850 standard by
clicking on the “Validate” button.

By clicking on button “Refresh Tree”, the contents of the new generated cid file are
shown.

5.4.4 Reports Edition

When the configuration parameters of a Report has no DataSet associated or any of it
attributes is not correct, it is possible to edit it to modify its attributes.

Select the Report that has to be edited by browsing the data tree. Once the Report is
selected, click on “Edit Report Control”. If the selected Report is not associated to any
already existing connection, the following window will be opened.

ATLAN V3.4 36/227 Ed 2.0

Any of the Report attributes can be modified by opening the corresponding attribute list.

When the Report to be edited is already associated to a connection, the following

message will be shown. The user has to determine if the edition process can be
completed or the connection associated to the edited Report has to be deleted.

The following notice will be shown describing the limitations that will be applied to the
edition process in order to keep the coherence of the project.

5.4.5 Logs Definition

To define a new Log, at least a DataSet has to be already defined in the icd/cid file of
the selected device.

To create a new Log, the LN where the Log will be created must be selected first from
the tree-folder. Then, after clicking on the “Create Log Control” button, a new area with
the dialogue fields required to introduce the information of the new Log will be enabled
on the bottom-right part of the window.

ATLAN V3.4 37/227 Ed 2.0

Attributes and trigger options have to be introduced using the corresponding dialog
boxes.

The attributes of the Log, such as the trigger options and the rest of optional fields, can
be completed by introducing the required values in the corresponding dialog boxes.
Click on “Accept” to store the new Log. A new window will automatically show the
contents of the Log, allowing users to verify the correctness of the structure and the
information. The cid file of the device will be automatically updated with this information
when saving the project.

It is recommended to verify the compliance of the new file to the IEC 61850 standard by
clicking on the “Validate” button.

By clicking on button “Refresh Tree”, the contents of the new generated cid file are
shown.

5.4.6 Logs Edition

When the configuration parameters of a Log has no DataSet associated or any of it
attributes is not correct, it is possible to edit it to modify its attributes.

Select the Log that has to be edited by browsing the data tree. Once the Log is selected,
click on “Edit Log Control”. If the selected Log is not associated to any already existing
connection, the following window will be opened.

ATLAN V3.4 38/227 Ed 2.0

Any of the Log attributes can be modified by opening the corresponding attribute list.

When the Log to be edited is already associated to a connection, the following message
will be shown. The user has to determine if the edition process can be completed or the
connection associated to the edited Log has to be deleted.

The following notice will be shown describing the limitations that will be applied to the
edition process in order to keep the coherence of the project.

5.4.7 GSE Control Block Definition

To define a new GSE Control Block, at least a DataSet has to be already defined in a
LLN0 of the icd/cid file of the device.

To create a new GSE Control Block, select the LLN0 where the GSE Control Block will
be located and click on “Create GSE Control”. A new frame will be opened to allow the
introduction of the information of the new GSE Control Block.

ATLAN V3.4 39/227 Ed 2.0

Once all the related information has been introduced, click on “Save” to store the new
GSE Control Block. A window will show the contents of the DataSet to allow users to
verify its correctness. Click on the “Refresh Tree” button to view the contents of the new
file. The new cid file will be permanently stored when the project is saved.

5.4.8 GSE Control Block Edition

When the configuration parameters of a GSE Control Block has no DataSet associated
or any of it attributes is not correct, it is possible to edit it to modify its attributes.

Select the GSE Control Block that has to be edited by browsing the data tree. Once the
GSE Control Block is selected, click on “Edit GSE Control”. If the selected GSE Control
Block is not associated to any already existing connection, the following window will be
opened.

Using this window, the attributes can be modified or a new DataSet can be assigned to
the GSE Control Block.

When the GSE Control Block to be edited is already associated to a connection, the
following message will be shown. The user has to determine if the edition process can

ATLAN V3.4 40/227 Ed 2.0

be completed or the connection associated to the edited GSE Control Block has to be
deleted.

The following notice will be shown describing the limitations that will be applied to the
edition process in order to keep the coherence of the project.

5.4.9 SMV Control Block Definition

To define a new SMV Control Block, at least a DataSet has to be already defined in a
LLN0 of the icd/cid file of the device.

To create a new SMV Control Block, select the LLN0 where the SMV Control Block will
be located and click on “Create SMV Control”. A new frame will be opened to allow the
introduction of the information of the new SMV Control Block.

Once all the related information has been introduced, click on “Save” to store the new
SMV Control Block. A window will show the contents of the DataSet to allow users to
verify its correctness. Click on the “Refresh Tree” button to view the contents of the new
file. The new cid file will be permanently stored when the project is saved.

NOTE: It cannot be defined a new SMV Control Block in a LLN0 when a GSE Control
Block already exists as specify in IEC 61850-6. This will produce a non-compliant scd
file.

ATLAN V3.4 41/227 Ed 2.0

5.4.10 SMV Control Block Edition
When the configuration parameters of a SMV Control Block has no DataSet associated
or any of it attributes is not correct, it is possible to edit it to modify its attributes.

Select the SMV Control Block that has to be edited by browsing the data tree. Once the
SMV Control Block is selected, click on “Edit SMV Control”. If the selected SMV Control
Block is not associated to any already existing connection, the following window will be
opened.

Using this window, the attributes can be modified or a new DataSet can be assigned to
the SMV Control Block.

When the SMV Control Block that is being edited is already associated to a SMV
connection, a warning message will be shown. The user has to determine if the
modification will affect the coherence of the related connection. The edition process
should not modify any of the parameters of the SMV connection. If any of these
parameters has to be modified, the SMV connection will have to be deleted.

5.4.11 GOOSE connections

GOOSE connections represent peer-to-peer information interchange as specified by the
standard IEC 61850. The origin device is the publisher of the information contents in the
“GSE Control Block” whereas the destination, which may be one or several devices, are
the receiver of this information. Therefore, it is very important the way in which the
connections are drawn since they have to be drawn from origin to destination.

Although only the LLN0 can generate this type of messages, in order to make the drawing
more illustrative of its real functionality the connection can be drawn from any LN of the
origin device to any of the LNs of the destination device.

When establishing a GSE connection between a source LN and one or more

destinations, a pop-up window as that shown next will be displayed.

These connections will be documented in the scd file.

In the “Connection” block, the “Connection point” field must indicate the Ethernet port –
for each IED – through which both devices communicate. Both communication ports

ATLAN V3.4 42/227 Ed 2.0

have to be connected in the same Ethernet LAN – ATLAN performs an automatic
verification of communication connections between both IEDs to be connected –.

The “Communication parameters” block allows the specific GOOSE communication

parameters to be set. If the icd file of IED model has preconfigured information, it is
possible to use these parameters by clicking the button “ICD Data”. Preconfigured data
will be automatically loaded into the connection window. The user can freely modify any
of these parameters.

The “Information” block shows the information that the source LN transmits. Such
information is composed of a “GSE Control Block”. At this point, it can be selected a
“GSE Control Block” defined in the LN0 of the LD in which the LN origin of the connection
is allocated, or any other “GSE Control Block” of the IED, independently of the LN0 that
contains it.

The symbol shows that the selected GSE Control Block is not assigned to any other
GOOSE connection and therefore, can be used in the definition of the actual GOOSE
connection. On the contrary, the symbol shows that the GSE Control Block chosen is
already assigned to other GOOSE connection thus it cannot be assigned to any other
GOOSE.

GOOSE connections can be established in multicast mode; that is, from a source to
several destinations. In this case, the following pop-up window is displayed.

ATLAN V3.4 43/227 Ed 2.0

A Multitarget connection is defined as any other multiconnection. In this case, it is
necessary to define the connection terminal, which must be of type communications
(Ethernet), as ATLAN verifies that all the terminals are connected to the same LAN in
order to avoid GOOSE being defined between IEDs that have not Ethernet connectivity.

The type of information transmitted by the GOOSE message associated to this

connection is that defined in one of the “GSE Control Block” of the LD’s LN0 in which the
origin LN of the connection is included. Although this is the most common procedure, it
is also possible to use any other “GSE Control Block” defined in another LN0 of the same
device. In this case, it is necessary to select the “Explore IED” option in order to be able
to locate the desired “GSE Control Block”.

ATLAN V3.4 44/227 Ed 2.0

In the case that the transmitted block contains a data set for which not all the data are
relevant for the receiver of the information, it is possible to select the data that need to
be received. In addition, it is possible to define the way in which the received data must
be processed as well as with which DO the data interact. This sort of information is not
reflected in the .scd file, although it is generated a specific document that allows to
appropriately configure the devices by using their specific configuration software.

By clicking on the “Edit received data” button, it is displayed a pop-up window as that
shown next where, on the upper left area, the contents of the “GSE Control Block” are
shown for each of the IED associated; and, at the tree-folder on the right, it is shown the
selected IED.

By clicking on button “Add”, it is created an association between the received data and
the selected DO.

By clicking on “Delete”, the list of associations is deleted.

DO/DA can be selected directly from the data structure tree or by clicking the LN and
choosing DO/DA from their combo lists.

Multitarget GOOSE connections can be modify adding new devices as described in

section 5.2.8.

5.4.12 SMV Connections

SMV connections model information interchange between per devices as specified by
IEC 61850-9-2. The device publishing the information is normally a Merging Unit. It
publishes the information contained in the SMV Control Block whereas the subscribed
device receive and process this information. Consequently, it is very important to draw

ATLAN V3.4 45/227 Ed 2.0

properly the connection starting from the publishing device and ending at the device that
will subscribe to it.

These type of connections will be documented at the scd file so the corresponding XML
code will be automatically generated.

After drawing a connection, the following pop-up window will be shown.

The “Connection” block allows the communication port to be selected. Both, source and
target ports have to be connected at the same LAN.

The “Communication parameters” block allows defining the communication configuration

parameters. If the icd file of IED model has preconfigured information, it is possible to
use these parameters by clicking the button “ICD Data”. Preconfigured data will be
automatically loaded into the connection window. The user can freely modify any of these
parameters.

The “Information” block shows the reference of the information to be published by this
connection. The SMV Control Block allows selecting the desired Control Block. The icon
shows that the SMV Control Block selected is not being used by any other SMV
connection otherwise the icon will be displayed.

By clicking the button “Edit received data” the window of the following figure is opened.
The left part shows the content of the “SMV Control Block” whereas the right part shows
the cid file of the IED subscribing to this connection.

ATLAN V3.4 46/227 Ed 2.0

By selecting a DO/DA on the left part and a DO/DA on the right part and clicking on “Add”
a new association is defined.

Clicking on “Remove” the association will be deleted.

SMV connections can also be defined as multicast. The way multicast SMV connections
are defined is like for multicast GOOSE.

5.4.13 MMS connections

MMS connections represent client-server information interchange as specified by the
standard IEC 61850. The origin device is the client whereas the destination device acts
as the server. Therefore, it is very important to draw the connection in the appropriate
direction. That is, from origin to destination, or which is the same, from client to server.
In this case, the information shown is the one provided by the server to the client, and
therefore the one that is contained in the server (or destination node).

MMS connections are run time established between client and server. Therefore, MMS
connections are not included in the scd file. They are included in ATLAN for
documentation purposes. Thanks to this, it is possible to document the implementation
and functionality of some protection and control functions showing the use and
functionality of reports and Logs.

When a new MMS connection is drawn between two IEDs, the following pop-up window
is opened:

ATLAN V3.4 47/227 Ed 2.0

The connection and identification blocks have the same functionality as for the rest of
connection types.

In the “Connection” area, the Connection point field must contain, in each case, the
Ethernet port through which both IEDs communicate themselves. Both ports must be
connected to the same LAN, as the system verifies the communications for every
connection between two IEDs.

The “Information” block defines the Data Object, DataSet, Report or Log that is located
at the server device and will be access by the client. Data can be access in the following
ways:

1. A DataObject of the LN where the connection is attached. Opening the Data

Object list, all the DO of the LN will be shown. Only one DO can be chosen.
2. A Data Set of the LN where the connection is attached. Opening the Data set list,
all the DataSets of the LN will be shown by their name. Clicking “View Data Set”
the contents of the selected DataSet will be shown in a pop-up window.

ATLAN V3.4 48/227 Ed 2.0

 3. A Report of the LN where the connection is attached. Opening the Report list, all
the Reports of the LN will be shown by their name. Clicking “View Report Control”
the contents of the selected Report will be shown in a pop-up window.

4. A Log of the LN where the connection is attached. As per report.

5. If the data is not located in the LN, it is possible to use any other data of the IED.
Clicking “Explore IED” a pop-up window will show the data structure of the IED
including DataSets, Reports and Logs. Browsing the IED any DO, DataSet, report
or Log can be chosen. The selected element will be included with the whole path
/Accesspoint/LD/LN/Data). This facility may be used when a LN has several
instances and only one is shown in order to simplify the diagram.

ATLAN V3.4 49/227 Ed 2.0

Selecting a piece of data, Data Set or Report, does not restrict the selection made to
participate in another connection of any type. That is to say, several MMS connections
can be established over a same Data Set and, in addition, that Data Set can form part of
one or several GSE connections.

WARNING: These facilities have been made available for advanced users with in-depth
knowledge of the IEC 61850 standard. It is strongly recommended to verify the
correctness of DataSet, Reports, Logs, GSEControl and their associated connections
against the IEC 61850 standard and the real limitations of the devices that will implement
the project.

By clicking on “Edit Received Data” the contents of the “Report Control” is shown in a
pop-up window. If the data block transmitted by the MMS message contains some data
not relevant for the receiver side – who is acting as server – it is possible to select only
the data that has to be received. This information is not included in the scd file, although
a specific document is generated to allow devices to be properly configured using their
proprietary application.

By clicking “Remove Received Data”, the former data filtering is disabled allowing all the
data of the “Report Control” to be received.

5.4.14 Hybrid IEC 61850 Connections

For those hybrid connections in which there are IEC 61850 LNs involved, the “Load Data
Object” functionality is active. This permits to select the Data Object associated to such
signal.

ATLAN V3.4 50/227 Ed 2.0

The information block shows the DO associated with the physical connection.

5.4.15 Other Functions

For IEC 61850 devices, by selecting the contextual device menu “Details”, the following
pop-up window is displayed, where the hierarchy of the LN structure is shown.

ATLAN V3.4 51/227 Ed 2.0

5.5 Communication Configuration
ATLAN provides the functions and facilities to model communication devices used to
implement the internal communication infrastructure as
well as the devices used to communicate the substation
with other locations.

One key requirement of IEC 61850 substations is the

correct substation communication infrastructure
definition and configuration. ATLAN provides a set of
functions that helps and simplify the configuration of
communicating IEDs, Ethernet Switches and Router. By
using these facilities, it can be verified if the GOOSE,
SV and MMS connections can be supported by the
communication infrastructure defined in the project.

In addition, ATLAN provides facilities to document all

the configuration parameters, most of which must finally
be included in the substation configuration scd file.

For all the IEC 61850 devices as well as for other IEDs
with Ethernet ports, ATLAN provides control on the
connectivity features of the communication
infrastructure. Every Ethernet port has to be associated
to a LAN number. GOOSE connections can only be established between IEDs
connected to the same LAN.

When a new device with Ethernet Switching capabilities is inserted in the project, a
unique LAN identifier “LANID” has to be provided – every Ethernet Switch is regarded
as a unique LAN, unless it is connected to another Switch –. Therefore, every time that
a new Ethernet Switch is inserted, as it is not yet connected to any other Switch, ATLAN
considers that a new LAN is inserted in the project. Consequently, every new Switch
requires a unique LAN identifier (“LANID”) in the corresponding field. If a LANID has
already been assigned previously, the system will display the following error message.

When two Ethernet Switches are connected, they become a single LAN so they have to
have the same LAN identifier. Once the connection between two independent Ethernet
Switches have been defined the following pop-up window will be shown

The common LAN identifier has to be chosen from the identifier list.

It is possible to modify the configuration of the LANs of the project by using the menu
“Tools – Configuration – LANs Configuration”.

ATLAN V3.4 52/227 Ed 2.0

When this function is activated, the following pop-up window – which contains a summary
of all the IEDs defined as Ethernet Switches at that time – is displayed. This window also
lists all the existing LAN’s in the project, with their corresponding identifiers.

By means of this window, users can change all LAN Identifiers at once.

By clicking on the “Verify” button, configuration errors are checked. This function verifies
those errors that may drive to miss operation of IEC 61850 communications such as
connected IEDs with different LAN identifier, IEDs attached to the same LAN but not
connected, etc. A report is automatically generated.

The designer of the project should determine the most suitable solution for the reported
errors.

ATLAN V3.4 53/227 Ed 2.0

6 LOGICAL FUNCTIONS
ATLAN provides a powerful environment to define, test and document the logic that
implements some protection and automatic functions.

ATLAN Logical Functions framework provides a set of tools that cover the full lifecycle
of substation protection and automation logical functions. This working environment
comprises the following facilities:

- A library of generic Logical Function

- A specific working environment to define new generic Logical Functions
- A logical simulator to check the functionality of the logical functions
- A powerful set of tools to map the generic Logical Function to a real
implementation
- A logical simulator to check the functionality of the final implementation
- A set of tools to thoroughly document the process and the results

6.1 LOGICAL FUNCTION LIBRARY

WARNING: These functions are only available if you have an ATLAN licence including
Logical Simulator package.

ATLAN licence includes few examples of Logical Functions that may not be adequate
for real implementations. These examples can be used following the instructions of
section 6.2. New Logical Functions can be defined by the user following the instruction
in section 6.1.1.

The new Logical Functions created by the user will be stored in the Logical Function
Library. They can be structured in functional groups or families according to the criteria
of the user, without any limitation.

Library management functions provide facilities to modify the folder hierarchy where
Logical functions will be stored.

6.1.1 Logical Function Editor

The process of creation of a new logical function is carried out through the Logical
Functions edition tool included in ATLAN, which is activated by clicking on the icon on
the bar tool. To be able to use this tool it is not necessary to start a new project.

By clicking this icon, the Logical Editor Window is opened on a new window, allowing
users either to select an existing function from the library or to create a new function from
scratch.

ATLAN V3.4 54/227 Ed 2.0

Once the logical functions editor is initiated, a new Logical Function can be defined from
scratch. Existing Logical Function can also be edited in the same way.

By clicking on the icon it starts the procedure of definition of a new Logical Function.
Once the name is entered, users can start the process of defining a new Logical Function
as described next.

A new Logical Function can be created from an existing one

by using the “File – Open” submenu or by clicking on the
icon at the bar menu. A pop-up window will be automatically
opened, allowing users to select any function within the
logical functions library, being able to freely browse the
functions tree-folder without any limitation. Once selected,
to edit the logical function just click on button “Open”.

During the process of edition of a logical function, when

“Save” or “Save as” is invoked for the first time a pop-up
window showing the user’s Logical Functions tree-folders is
displayed. The user can select in which functions’ folder the new function has to be saved
or it can create a new folder anywhere in the tree by clicking on button “Create folder”.

ATLAN V3.4 55/227 Ed 2.0

The “Remove Folder” button allows users to delete any
folder previously created by means of the “Create folder”
button. Folders can only be deleted when they are empty.

To delete a folder, select it and click on the “Delete Folder”

button.

When saving the logical function, empty folders will be

automatically deleted and therefore there will never exist
folders that do not contain logical functions.

Only the user’s logical functions tree is shown in this

window, as this is the area where new logical functions
can be saved.

Once a name has been assigned to the logical function during the edition process, new
data will not need to be entered every time that the “Save” function is used, as the system
will use the data introduced when invoking the “Save” function for the first time. Users
will not be able to overwrite an existing Logical Function.

The “File” menu contains the “Remove Logical Function” functionality, which permits to
delete those functions that are not required any more. The use of this function is
restricted to ATLAN’s Administrator, reason why it is required to know the password of
the Administrator to be able to remove an existing logical function.

Once deleted all the logical functions contained in a folder, it is not necessary to delete
the folder as it will be automatically removed by system, as explained before.

Logical Functions provided with ATLAN’s licence are not shown in this window, since
they are stored in a protected area and cannot be deleted.

ATLAN V3.4 56/227 Ed 2.0

6.1.2 Logical Functions edition process
Logical functions’ creation and edition working environment is similar to that for the
creation of engineering projects. On the left hand side of the window, there are the
different elements that can be used during the definition of functions. After selecting any
of them, the selection made can be inserted into the graphical edition zone just by clicking
on the exact point of the screen where such element needs to be instantiated.

There is no need for a library of connections, as connections are automatically carried

out by ATLAN in the automatic insertion of elements mode by holding the left button of
the mouse pressed and dragging it from the origin element to the destination element.

User notes, comments and legends can be added by means of text blocks – framed or
unframed –. To add a block of text, click either on icon if the block needs to be framed,
or on icon if it needs to be unframed.

The rest of drawing functions – such as zoom, grid, etc. – are also available for this
working environment.

It is important to consider that the layout of the components of a graphical function, as

well as its appearance, are those which will be kept in the final documentation of such
function; consequently, it is at the moment of creating a logical function when it must be
borne in mind how it has to look like in its final documentation. The icon activates the
edition mode, which blocks the library of elements of logical functions and permits to
modify the placement of the elements and the shape of the connections.

Once a logical function saved in the library, it will not be able to be modified. The same
applies when a logical function is used in a project. Its graphical appearance cannot be
changed.

Once terminated the edition process of a Logical Function, it is recommended to make

use of the verifying function, by clicking on the icon. This function verifies that all the
inputs and outputs are connected and that there is not any logical element with and
output not connected.

Before exiting the logical functions edition environment, the carried out design must be
saved, otherwise all the modifications performed since the last time that the design was
saved will be lost.

In order to save a logical function, use the “Save” submenu or click on the icon. Any
time that a function is saved, a new name must be assigned to it.

6.2 USING LOGICAL FUNCTIONS

By selecting the “Show Logical Functions” icon, the library of functions becomes
activated and the working area is split in two parts, the lower one showing the logical
functions included in the project.

6.2.1 Adding Logical Functions

To add a Logical Function follow the procedure indicated next:

- Activate the Logical Function window by clicking on the icon

ATLAN V3.4 57/227 Ed 2.0

 - Choose the Logical Function that requires to be added by clicking on its name in
the library of logical functions
- Click on the Logical Function working area with the right button of the mouse and
chose the “Add logical function” menu. The next window will be automatically
displayed.

- Assign a unique name to the new function.

- If the logical function will be implemented by a single device, tick the “Individual
assignment” option and select the device by which it will be implemented by
clicking on the scroll-down menu. This will simplify the mapping produce
described in the following chapter.

The function will be automatically created in a new folder within the Logical Function
area. All the elements that have not been yet mapped will appear highlighted in red
colour.

Once the new function has been added, its logical generic components, inputs, outputs
and logical elements need to be mapped to the signals of the project and to the IEDs
that will implement such logical elements in the final design.

ATLAN V3.4 58/227 Ed 2.0

Those Logical Functions that have already been mapped in the system can be deleted
using of the contextual menu that appears by placing the cursor over the logical functions
zone and clicking on the mouse right button.

6.2.2 Mapping Logical Functions

Mapping a Logical Function is the process required to associate to each of the
components, logical elements, input or output signals, and internal connections of such
a function, the devices and the signals of the project that will implement the function.

When initiating the process of mapping a logical function, all its components appear
highlighted in red colour. As the components become assigned to devices and signals
of the project, their colour changes to black and every one of them adopts the name of
the device or the signal by which is implemented in the project. At the same time, when
selecting an element of the logical function, it becomes highlighted in green colour, in
the same way that the associated device becomes highlighted in green or grey in a
project, for IEDs with internal functions.

The previous figure shows a logical function that has not been mapped yet, and therefore
all its components are highlighted in red colour.

The mapping process can be carried out either by assigning all the elements of the
Logical Function to a same device – as it has been described previously –, or by
distributing the Logical Function among several devices in the project.

The process of mapping or assigning the elements of a logical function to devices and
signals in a project must be carried out by following the next sequence of steps:

1. Assignment of the logical elements to project devices.

Click with the right button of the mouse on one of the logical elements and choose
the “Device Assignment” context menu. The following window will be displayed:

ATLAN V3.4 59/227 Ed 2.0

 By means of this window, it can be defined whether the functional element will be
implemented by a wired logical function, or by one of the IEDs shown in the
“Device:” list.

When clicking on the “Accept” button, the logical element adopts the name of the
IED that implements it, and the IED as well as the logical element are shown in
green colour.

This process has to be repeated for every element of the function. Connection
between logical elements associated to the same IED will not require mapping
and will change its colour to black automatically, as shown in next image.

ATLAN V3.4 60/227 Ed 2.0

 During the mapping process and until the following mapping process or stage is
not initiated, any error can be mended by mapping the element over a different
IED. Once the following mapping process starts, it is not possible to modify device
assignments, reason why it is recommended to check the set of assignments
made, before initiating the following mapping stage.

The mapping of logical elements to wired logic requires a direct mapping over a
multi-source connection with exactly the same number of terminals as the wired
logical element. All the logical elements connected to the wired logical element
have to be previously mapped before proceeding to map the wired logical
function. “Multi-source wired connection” describes the wiring of several inputs or
outputs in parallel or in series. The equivalent function, AND or OR respectively,
indicates the wiring type.

By selecting option “Wired Logical Function” on the device assignment window,

the next window is automatically displayed, showing the list of all the possible
connections that can be implemented by means of the wired function being
mapped. ATLAN will verify that the selected connection fulfils the above-
mentioned requirements.

2. Assignment of input and output signals.

Click with the right button of the mouse on any of the input or output signals of
the logical function and chose the context menu “Sign Assignment”. The following
pop-up window is then shown.

ATLAN V3.4 61/227 Ed 2.0

 The “Sign assignment” window contains all the inputs and outputs of the logical
function being mapped. For each of them, the IED that contains the signal needs
to be selected from the first pop-down list, and the terminal related to the signal
being mapped must be chosen from the second pop-down list.

The contents of the first list depends on the assignment of functions; for example,
when the function to which the input or the output is connected is a wired function,
all the IEDs of the project are listed; whereas if the function has been assigned
to a single IED, only that IED appears in the list.

When signal to be assigned is a logical signal, the corresponding “Logical” box

must be selected on. After doing so, all the logical nodes containing any of all the
possible logical signals will appear in the first list. Once the logical node selected
in the second list, all the internal variables of such node will be included in the
second list, being possible to select to select that variable which will remain
associated to the input or the output being mapped. When a DO is selected from
the combo list, the associated attributes are shown.

2.1 Assignment of three-phase signals.

During the definition of Logical Functions, three-phase signals can be
represented by separate poles in such a way that they form sets of three inputs
or three outputs. However, in the design of the project these signals are
represented by a unique signal and a single connection, internally broken down
in three single wire connections according to the corresponding IED application
guide. Consequently, the three signals that form the three-phase signal must be
mapped to a unique signal, which must be of type three-phase, in the design.
When such a mapping is performed, the next window, which allows users to
customise the identification of every three-phase signal, is automatically
displayed.

The identification label of every phase can be defined according to documentation

criteria.

3. Assignment of internal connections.

ATLAN V3.4 62/227 Ed 2.0

 When two elements of a logical function are associated to different IEDs and are
at the same time linked by internal connections of the logical function, it is
necessary to define the way in which they will be connected.

To perform such an assignment, select the connection and, by means of a right-

click, chose the “Connection Assignment” option in the context menu. The
following pop-up window is then shown.

This window displays the connections that have been defined between the source
and destination devices, to which the two logical elements to be connected have
been assigned.

When a Logical Function has been successfully mapped, all its elements are
shown in black.

When the cursor is left over an input or output of a Logical Function, if the Tooltip
function is activated the name of the assigned signal is shown, whether the
physical connection name or the IEC 61850 Do/Da path name.

ATLAN V3.4 63/227 Ed 2.0

7 LOGICAL FUNCTIONS SIMULATOR
WARNING: These functions are only available if you have an ATLAN licence that
includes the Logical Simulator package.

ATLAN includes a simulation functionality that allows users to carry out time-discrete
binary simulation sessions for the Logical Functions included in a project. This permits
to perform a functional evaluation of all the logics included in a project, allowing users to
have exact knowledge in advance of their respective eventual time responses.

The simulation process is of functional type, which allows evaluating the behaviour of
the logical functions when binary digital signals are injected in their inputs. The evaluation
of the responses is discrete in time, and its resolution can be user defined.

ATLAN allows different simulation environments for every Logical Function to be saved.
Thanks to this, once a Logical Function is validated in the library of functions, it is possible
to verify the correct behaviour of different implementations of that function in different
projects.

7.1 PREPARING THE SIMULATION

The preparation stage of the simulation process consists of selecting the function or
functions that require to be simulated; as well as defining the excitation traces, the
duration and temporal resolution of the simulations, and the response times of the
participating elements. The excitation signals of the simulation can be formed from the
basic traces of the system, as well as from complex traces previously stored in the library
of simulation traces.

Only those logical functions that are completely mapped – i.e., having all their
components and connections displayed in black colour – can be simulated. Also,
simulations can only be carried out if the project has been saved after completing the
mapping process. If a logical function has been mapped but the project has not been
saved, the system will produce errors if attempting to perform its simulation.

The flowchart depicted below shows the stages of the simulation process in detail. When
the simulation menu is selected, a new window is displayed showing on its bottom left
part the logical functions that have been defined in the project. This window also allows
users to select the logical functions one by one or to load them on the left side of the
simulation environment.

Provided that they are interconnected, it is possible to simulate several logical functions
in a row.

The next step consists of defining the test scene, which is based on the excitation trace
of the simulation. Existing traces can be used or new ones can be created by selecting
“New Trace”. This new trace can be also saved for further simulations.

ATLAN V3.4 64/227 Ed 2.0

 NEW Time scale
SIMULATION COMMON
PARAMETERS

LOGICAL
FUNCTION
SELECTION

YES
NEW TRACE?

NO

Start from the begining

modify existing trace CREATE
CHOOSE
NEW
TRACE DB
TRACE

Map trace SIGNALS

to physical MAPPING
signals

Set general elements delay

SET & specific delays
SPECIFIC
DELAY

START
SIMULATION

Once the trace is selected, each of the generic signals in the trace must be mapped one
by one to the real signals of the logical functions that need to be simulated. As well as it
happens in the mapping process of logical functions, the assigned signals change colour.
The simulation of the logical function will not be able to be performed unless the function
has all its inputs assigned to signals of the traces. It is possible to assign more than one
input to the same trace, as well as allowing that input signals that has not been assigned
any trace signal to become assigned with a logical “0” signal.

7.1.1 Generation of test scenes

Test scenes or signal traces define the shape of the wave; that is, the temporal evolution
of any of the signals applied to the inputs of the logical functions to be simulated.
The simulation working environment provides a set of basic signals from which complex
traces can be defined. These basic signals are as follows:
- Signal always set to “0”. A continuous cero signal.
- Signal always set to “1”. A continuous one signal.
- Transition “0-1”. A transition from cero to one. The transition instant of time can
be set in the “Initial value” box.
- Transition “1-0”. A transition from one to cero. The transition instant of time can
be set in the “Initial value” box.
- Positive “0-1-0” pulse. The initial time and the duration of the pulse can be user
defined.
- Negative “0-1-0” pulse. The initial time and the duration of the pulse can be user
defined.

ATLAN V3.4 65/227 Ed 2.0

 - Multiple pulses. Random sequences with more than four states. Users can define
the duration of every state.
- Clock. Periodic signal. Users can define the duration of the cero state and of the
one state.

Signals with flanks allow users to configure – by means of a dialogue window – the
instant in which the flanks occur.

From the individual signals, there can be defined the test scenes – or the set of individual
signals that define flaws and typical operations of the system –.

The following figures illustrate the process of definition of a new simulation scene.

ATLAN V3.4 66/227 Ed 2.0

It will be possible to save in the database both the new individual signals resulting from
the parameterisation of the generic signals, and the test scenes formed by a set of
individual signals.

7.2 SIMULATION PROCESS

The simulator is activated by selecting the “Simulator” submenu in the “Tools” menu.
When the simulation process is initiated, the window shown in the following figure is
displayed:

ATLAN V3.4 67/227 Ed 2.0

To initiate the simulation process it is required to carry out the next sequence of steps:

- Define the total time of the simulation, in milliseconds.

- Select one of the traces shown in the “Use trace” pop-down menu, or define a
new trace by clicking on the “New trace” button. If a new trace is defined, once
the trace definition process is finished the new trace will be included in the “Use
trace” pop-down menu, after which it will be able to be selected.
- Select the Logical Function (LF) that requires to be simulated among those that
have been already mapped in the current project. When the simulator is invoked
from the library of Logical Functions, the functions included in that library are
shown on the bottom right window – as described in chapter 4 –.
- Assign the signals of the trace to each of the inputs of the LF to be simulated, as
described in section 7.2.1.
- Define the intermediate control points which permit to visualise the evolution of
the internal signals of the LF, simulated as described in section 7.2.2.
- Assign the required delays to each of the functional blocks, as described in
section 7.2.3.
- Execute the simulation, by clicking on the “Simulate” button for a whole
continuous simulation, or on the “Step by step” button for a step-by-step
simulation. In both cases, the simulation progression bar will be shown. Once the
simulation process terminated, a new window is displayed showing the results of
the simulation, as described in section 7.4.

7.2.1 Signals assignment

Once the simulation traces are created, it is required to map each of the input signals of
the Logical Function to be simulated. This mapping process is performed in a similar way
to the mapping of Logical Functions in a project. Input signals not assigned to any trace
signal will be always set to the logical “0” state in this case. The window with the context
menu of the logical function to be simulated is opened by a right-click on the window of
the logical function. This context menu provides access to the system functions that
control the zoom; to the insertion of delays; and to the signals assignment. By selecting
the “Signal assignment” submenu, the window shown next is displayed, where it can be
selected the trace signal that must be assigned to each input of the Logical Function.

7.2.2 Control points

It is possible to include control points in any of the outputs of the logical elements of the
Logical Functions to be simulated.

ATLAN V3.4 68/227 Ed 2.0

ATLAN assigns automatically a unique identifier to every control point. During the
simulation, a graphical signal will be generated showing the temporal evolution of the
signal in the control point.
The inclusion of new control points is activated by right-clicking on the logical element in
which it is required to add the control point. If that element has already a control point, a
new menu including the option of de-activating it, as well as of selecting all the control
points, is displayed. The logical elements that have a control point are shown highlighted
in green colour.

Each control point indicates the value of the output of the element to which it is
associated. Therefore, those elements having signals from terminals in their outputs
cannot be assigned to control points, as it would be redundant.

7.2.3 Introduction of delays

The last step for the preparation of a simulation consists of assigning specific delay
values to the elements in the design that are considered to introduce significant delays,
or to those elements related to the correct functioning of the simulated function – for
instance, internal timers and input or output signals–.

It is possible to assign a common delay to all the logical gates. When selecting the
corresponding submenu, the “Insert general delay” window is displayed, where it can be
assigned the delay that will be applied to all the gates. This delay does not apply to the
logical elements that have own delay parameters, as for example the timers.

By selecting the “Insert delay” submenu, the window shown in the next figure, where
users can customise the delay of every single logical element, is displayed.

By placing the cursor over the box of one element, this becomes highlighted in green
colour, so that the element being configured every time can be easily identified.

ATLAN V3.4 69/227 Ed 2.0

Those elements having internal timers can be individually programmed and are not
affected by general delays – as these apply only to logical elements that not have own
delay –.

By right-clicking over a logical element with own delay, a contextual menu that contains
the “Insert special parameters” submenu is displayed. When selecting that submenu, the
following pop-up window is shown, where the timing value can be introduced.

7.3 SIMULTANEOUS SIMULATION OF SEVERAL LOGICAL FUNCTIONS

ATLAN’s simulations environment allows simulating several LFs in a row when they are
linked to each other in a project; that is, when one or several outputs of one function are
concatenated with inputs of another function. In this case, the simulator is capable of
simulating the whole set as if it was a single LF.

In order to perform a simultaneous simulation of several LFs it is required to select the

“Multiple Logical Functions” box. This permits to link all the functions as required by
repeating the process of adding each time a different function to whole the set. Once all
the functions concatenated, the viability of such simulation must be validated by clicking
on the “Validate” button. By doing so, the system verifies that all the functions in the set
are linked by at least one connection. If the system finds out that the first LF is not linked
to the rest of the functions, the whole process must be started again. When any of the

ATLAN V3.4 70/227 Ed 2.0

rest of the functions is found to be isolated, the system inhibits it and the simultaneous
simulation of the rest of the functions can still be carried out.

Once the validation passed, the process of preparing the simulation for each of the single
functions involved in the simultaneous simulation needs to be continued. That is:

- Signals assignment. For every LF, it must be carried out the assignment of
signals as explained in section 7.2.1. Inputs coming from another LF cannot be
assigned to signals of the trace, and for this reason they will appear inhibited in
the signals assignment window.
- Control points. For every LF, control points can be selected as described in
section 7.2.2.
- Introduction of delays. For every LF, delays can be introduced as described in
section 7.2.3.

From this point, the simulation process continues as described in chapters 6 and 7.

7.4 SIMULATION OF GENERIC LOGICAL FUNCTIONS

In order to simulate a Logical Function from the library it is required to enter in the Logical
Functions editor, either by means of the icon on the function bar or by selecting the
“Simulator” submenu in the “Tools” menu.

The following window is displayed when the simulation editor is activated:

This window allows the definition of the simulation parameters. The simulation process
is exactly the same as that described in section 7.2.

ATLAN V3.4 71/227 Ed 2.0

7.5 SIMULATION MODES
STEP BY STEP
When clicking on the “Step by step” button in the Simulator Editor window, it starts the
calculation of the simulation results. ATLAN performs this calculation in such a way that,
once it is finished, the result can be visualised step-by-step; that is, the simulation
progresses up to the next change of state of an input or an output signal, or up to the
next control point. The state of the inputs, outputs and control points is shown
simultaneously by means of a colour code: Red for state “1”; Blue for state “0”; and Black
when the state is unknown. By this means, it is possible to analyse the progress of the
signals inside the LF.

COMPLETE SIMULATION
When clicking on the “Simulate” button, the simulation is executed for the configured
simulation time or until there is no signals activity, whichever first happens. The
simulation results window shows the chronogram of the outputs. By moving the cursors,
the time between state changes can be measured.

When clicking on the “Save” button, the simulation results are stored in document format.
The resulting document contains a display of the traces as well as all the information of
the function simulated in the usual format in which Logical Functions are documented.

7.6 ANALYSIS OF RESULTS

There are two manners of presenting the simulation results, depending on the way that
the simulation has been carried out – i.e., continuous or step-by-step –.

7.6.1 Presentation of continuous simulation results

When the calculation of the simulation results is finished, a window as that shown in the
next figure is displayed showing the simulated LF and the obtained results. By activating
the contextual menu on the upper part of the area where the results of the simulation are
shown, users can access a set of graphical functions that allow analysing in detail the
obtained result. The functions available are:

- Zoom in. This menu contains submenus “All axes”, “Horizontal axis”, and “Vertical
axis”. By means of them, it is possible to adjust the size of the traces in one or
both axes. By dragging the mouse from left to right and holding the left button
pressed, the original size is re-established. By drawing a window in the signals
traces area, a zoom-in of the selected area is applied.
- Zoom out. This function has exactly the same menus as the zoom in function. In
this case, the size of the signals traces is decreased.
- Automatic scale. It allows adjusting the size of the signals to the horizontal axis,
the vertical axis, or both.
- Cursors. To be able to work with cursors they need to be defined first. This can
be done by selecting the “Create cursors” submenu. Two cursors positioned at
25% and at 75% of the horizontal scale are created, as shown in the next figure.

ATLAN V3.4 72/227 Ed 2.0

The “Cursors interval” pop-up window shows the time difference between both cursors.
The additional functions related to cursors are:
o Activate initial cursor. It places the initial cursor in the position (x-axis projection)
in which a left-click is done.
o Activate final cursor. As before, but with the final cursor.
o Insert cursors. A pop-up window is displayed to set the exact instant of time where
each cursor must be positioned.

o Delete cursors. It allows deleting the cursors.

o Zoom cursors. It zooms (full screen) into the area included between both cursors.

It is possible to store the results, so that they can be analysed at any time by initiating
the simulator and selecting the “Open” function. When doing so, the analysis window is
displayed with the results of the selected simulation.

When very complex simulations involving a large number of signals are performed, it is
possible to define a customised configuration of the signals display. Thanks to this, it is
possible to create reports or documents that contain a predefined subset of the signals
involved in a complex simulation. This capability can be relevant and illustrative of details
of a part of the whole simulation that may require specific documentation.

In order to create a customised view of the result of a simulation, it is required to click on

the “Select scene” button. Then the following pop-up window is displayed, where it is
possible to select the subset of signals to be visualised. The “Shift” key allows selecting
a range, whereas the “CTRL” key permits to select signals one by one. Once the signals
to be included in the graph have been selected, click on the “Accept” button to visualise
the new graph. The “Restore scene” key permits to go back to the previous situation.

ATLAN V3.4 73/227 Ed 2.0

The cursors, zooms or any other visualisation option can be used after selecting the
subset of signals. In addition, documents containing only the selected signals can be
generated.

In addition, user can define the order in which the signals are presented by clicking on
button “Sort signals”. This can make easier to establish relationships between events.

The result of a simulation can be saved as a trace, which at the same time can be used
as excitation signals in new simulations.

By clicking on button “Save trace”, the following window is displayed, where users can
select the signals to be part of the new trace.

7.6.2 Presentation of Step-by-step results

When the step-by-step simulation finishes, a window as that shown next is displayed,
where the simulated LF and the obtained results are shown.

ATLAN V3.4 74/227 Ed 2.0

This window shows the initial state of the simulation. By clicking on button “Continue” the
simulation progresses to the next change of state of any of the signals.

The lower part of the window depicts how signals progress by means of a colour code,
active signals at a given time being shown in red colour; inactive signals in blue; and

ATLAN V3.4 75/227 Ed 2.0

unknown states in black. To be able to visualise the state of the internal logical elements
of a LF, it is first required to activate the control points.

Once the simulation is finished, by activating the contextual menu on the upper part of
the window – where the traces of the simulation results are shown –, users can access
a set of graphical functions that allow analysing in detail the obtained result. The
available functions are:

- Zoom in. This menu contains submenus “All axes”, “Horizontal axis”, and “Vertical
axis”. By means of them, it is possible to adjust the size of the traces in one or
both axes. By dragging the mouse from left to right and holding the left button
pressed, the original size is re-established. By drawing a rectangle in the signals
traces area, a zoom in is applied to the selected area.
- Zoom out. This function has exactly the same menus as the zoom in function. In
this case, the size of the signals traces is decreased.
- Insert cursor. It allows inserting a cursor in the selected instant of time. The lower
part of the screen shows the logical state by means of the colour code.
- Automatic scale. It allows adjusting the size of the signals to the horizontal axis,
the vertical axis, or both.
- Cursor. It includes submenus “Enable”, “Disable” and “Delete cursor”. Once the
cursor enabled, when clicking over the graph, the cursor is positioned over the
selected point and, on the lower part of the window, the corresponding state of
the logic is displayed.

Unlike complete simulations, step-by-step simulations do not allow analysing time

intervals between cursors, as in complete simulations the cursor is used to indicate every
instant of time of the internal states of the logic along the simulation time (see next figure).

ATLAN V3.4 76/227 Ed 2.0

7.7 DOCUMENTING SIMULATION RESULTS
It is possible to generate a report, in pdf format, documenting the result of the simulation.
This report shows the simulated LF displaying the inserted control points; the traces of
excitation; and the signals at the outputs and at the measurement points – i.e., control
points –. In addition, users can enter comments related to the simulation and to the result,
by means of a text field that has no size limitation.

The result of the simulation can be stored in file format so that new analyses can be
performed afterwards; and new reports containing different aspects of the results can
also be generated.

ATLAN V3.4 77/227 Ed 2.0

8 MAPPING OF TELECONTROL DATA BASES

Telecontrol devices, such as RTU’s, need to be programmed with information and

configuration settings that would be coherent with the Control Centres’ Databases
(DDBB). This is achieved by configuring such devices with a Telecontrol Database that
includes all the information required to be able to relate appropriately the name of the
signals in the substation, with the definition of points in the SCADA system.

The Telecontrol databases mapping functionality makes possible to use normalised

Telecontrol databases in projects carried out with ATLAN, in such a way that the integrity
and coherence of the contents of such Database with the signals in the substation is
always guaranteed, ensuring by this means that projects are developed according to the
particular Telecontrol specifications.

ATLAN starts the process from a database file that includes the IEDs terminals and the
name of the signals involved in Telecontrol. From this information, establishes
appropriated associations so that the connections linked to Telecontrol can be drawn
automatically.

This works process follows the next stages:

1. Import of the databases. The Telecontrol database (TC_DB) file is imported.
There will be a database file, TC_DB, for every remote Telecontrol unit (RTU).
2. Modification of the TC_DB. When the project does not match exactly that what it
is defined in the imported TC_DB file, the Author will be able to delete the
unnecessary signals, and save the changes so that they can be included in
subsequent documentation.
3. Update of the TC_DB file. From the original TC_DB file and the documentation
associated to changes, the administrator of the Telecontrol DDBB will need to
create a new file, externally to ATLAN. This new file will need to be imported
again to the project, after which the work process is reinitiated. Once the imported
file has the signals of the project, the mapping process can be started.
4. Adaptation of the TC_DB into ATLAN. If the devices described in the TC_DB do
not match with those used in the project, it will be necessary to perform an
intermediate operation in order to get the file adapted. This operation is carried
out by means of the “Telecontrol Database Interpreter” function within the Import
submenu.
5. Mapping of signals. It is carried out in three stages:
a. Association of the RTU terminals with the terminals defined in the TC_DB.
When an exact match is found, this association is carried out
automatically; otherwise, it will need to be performed signal by signal.
b. Association of the devices defined in the TC_DB with the devices of the
project.
c. Association of the signals with the terminals of the controlled devices,
according to the specification of the TC_DB.
6. Drawing of the connections. Once the associations ended, it is possible to draw
the physical and/or the logical signals defined in the TC_DB. Users can select
the signals that require to be drawn in the basic engineering. When opening a
detailed drawing, it will also be possible to add connections from the TC_DB.

Note: As the Telecontrol Database file is generated by a specific tool that is external to
ATLAN, any modification performed in such file will interrupt the process just described
and the generation of a new TC_DB file, by means of the same tool, will be required. In
consequence, it is important to verify that the TC_DB has all the signals of the project
before starting the work process in ATLAN.

ATLAN V3.4 78/227 Ed 2.0

8.1 IMPORT OF THE TC_BD FILE
The import of TC_DB files will be performed by means a new submenu in the
“Communications” menu.

When selecting the “Communications – Import – Telecontrol data base” submenu, an

explore window that will allow selecting the file to import will be opened.

The import process includes a verification of the format of the TC_DB file. This
verification just checks if all the mandatory fields are properly defined:
- Type of signal. P/L. Physical or Logical
- Type of associated element
- Name of associated element
- Signal description
- Connector
- Terminal

ATLAN V3.4 79/227 Ed 2.0

In the case that the TC_DB does not comply with the format, the system will display the
corresponding error message and the import process will be automatically interrupted.

The files imported by means of this menu will be stored in the “tlcLib” folder that will
become automatically created in ATLAN folder when performing the importation.

As many TC_DB files as required will be able to be imported, whereas it will only be able
to exist one dictionary of signals file in every project.

8.2 BD_TC FILE MODIFICATION

If the TC_DB file contains a distribution of devices that does not match with the project,
it will be necessary to modify it.

When activating the “Interpreter Telecontrol data base”, it will be displayed an explore
window that will allow selecting the TC_DB file to be processed. Once selected, the
following window showing the contents of the file will be opened.

By double-clicking on “Element name”, the name can be edited in order to adapt it to the
distribution of the IEDs of the project.

By clicking on “Accept” it is automatically generated a Telecontrol database file in “.tta”

format. This file will need to be used to perform the next mapping steps, as it is described
in the following sections.

ATLAN V3.4 80/227 Ed 2.0

8.3 MAPPING OF TELECONTROL SIGNALS
The signals mapping process need to follow the steps indicated next:
- Association of a TC_DB to an IED of the project. (Usually the RTU of the position).
- Association of terminals to signals.
- Association of controlled elements such as circuit breakers, section switches, etc.
- Association of elements terminals associated to signals.

The first step is carried out from the context menu “Associate Telecontrol data base file”,
as described in the next section. The rest of the steps are performed from the
“Telecontrol Associations” context menu, which opens three windows in sequence – one
for each of the steps previously indicated –. It will not be possible to go from a current
stage to the next unless the former is totally completed. If any of the steps cannot be
completed, it will be necessary to generate the corresponding documentation in order to
be able of modifying the TC_DB file and restart the process with the new file.

8.4 ASSOCIATION OF THE TC_BD FILE

TC_DB files can only be associated to IEDs that have been modelled with that property.
See chapter 13 for more details about the modelling process.

For this type of IEDs, when activating the context menu by right-clicking on the IED, it is
displayed the new submenu “Association Telecontrol data base file”.

When selecting this submenu, it will be opened an explore window that allows selecting
the TC_DB corresponding to such IED.

After selecting the desired file, ATLAN carries out a compatibility verification test at
terminal level. The selected file must not have more signals than the number of terminals
available in the IED. In the case that the number of terminals is smaller to the number of
signals to be mapped, it will be displayed the next message error and the mapping
process will become interrupted.

ATLAN V3.4 81/227 Ed 2.0

8.5 ASSOCIATION OF TERMINALS TO SIGNALS
The mapping process must be performed once all the IEDs have been instantiated in the
project and it has been verified that the TC_DB file exactly matches the project.

Once the TC_DB file correctly associated, it is displayed a table that allows associating
the RTU terminals to the Telecontrol signals defined in the TC_DB file.

Before initiating the association process, it is important to verify if all the signals shown
in the table correspond to those signals required to implement the project. In the case
that it is necessary to delete or add signals to/from the table, the deletion/addition must
be carried out first; the generation of a new TC_DB file needs to be instantiated; and
then the process has to be reinitiated.

In first place, ATLAN verifies exact concordances and maps automatically the names of
the terminals that match with those indicated in the TC_DB file. These signals are shown
highlighted in green colour in the table.

Those terminals for which there is not any match will remain highlighted in yellow colour.
By mean of the “Up” and “Down” buttons, , it will be possible to establish the
appropriate associations. When clicking in “Document generation” the system will
approve the association although the names do not match. It will be generated a
document showing the correspondences of name and from that moment the internal
names of the RTU model will be used. The terminals associated in a forced manner will
remain highlighted in green colour.

By clicking on the “Accept” button it is performed a process of data validation. If all the
associated terminals are not found, the system will display the following error message.

ATLAN V3.4 82/227 Ed 2.0

If the validation is performed correctly, the system will display the following message and
afterwards will show the IEDs association window.

8.6 ASSOCIATION OF IEDs

When the association of terminals is completed satisfactorily, it is automatically opened
the association of IED’s window.

As for the previous case, those devices whose name matches with the name indicated
in the TC_DB file are highlighted in green colour. The devices for which there is not name
match remain highlighted in yellow colour.

It will be possible to arrange adequately the devices by selecting the device to be moved
in the table and using the buttons in order to place it in the desired row. When
clicking on the “Device rename” button, the selected device will automatically change its
name by the name indicated in the TC_DB file and then it will pass to be highlighted in
green colour.

In the case that any of the names indicated in the TC_DB file cannot be used in the
project, users will be able to generate associated documentation where it will be shown,
in yellow colour, the devices that have not been correctly defined in the TC_DB file. The
process will need to be interrupted and once there is access to a new TC_DB file that
includes the applied modifications, the association process will be to be reinitiated.

ATLAN V3.4 83/227 Ed 2.0

Once the associations completed and all the elements highlighted in green colour, by
clicking on the “Accept” button the associations are saved. Then the system will display
the window of terminals associations of destination equipment as described in the next
section.

8.7 CONNECTIONS ASSOCIATED TO TELECONTROL

The association of the Telecontrol signals to the terminals of the IEDs related to the RTU
performed in two stages: Firstly, it takes place the physical signals association; and
secondly that of the logical signals. In order to associate logical signals is necessary that
there exist beforehand communication links between both devices – in a similar way as
required for other sort of logical signals, as MMS or GOOSE –.

For the physical signals – identified by the “F” acronym in the “Signal Type” column –,
by clicking on the element placed in the same row under the “Terminals” column it gets
displayed a “Combo” drop down menu that shows the current free terminals in the
corresponding device shown under the “Element name” column. In the “Combo” menu,
it must be selected the terminal where the signal indicated under the column
“Description” will be cabled.

When the model of the destination IED includes in the “comments” field of each terminal
the name of the Telecontrol signal, it will be carried out an automatic association between
the signal and the terminal.

For the logical signal – identified by the ”L” acronym in the “Signal type” column –, by
clicking in each of the rows of the “Terminals” column it becomes displayed a “Combo”
menu that shows the communication ports. Logical signals will need to be mapped over
the communication port that it is used for routing the protocol by means of which the
signal is transmitted.

ATLAN V3.4 84/227 Ed 2.0

In the case that the devices are not connected through communication ports, it will be
displayed the following error message.

When the association process is completed and the “Accept” button is pressed, ATLAN
checks automatically that all the signals have a terminal associated. In the case that any
of the terminals has not been associated, the following error message will be displayed.

The association process cannot be terminated unless all the terminals are assigned. If
the process is cancelled for any reason, it will be necessary to start it again from the
beginning.

Once the association process finished, it can be performed the automatic drawing of the
connections included in the TC Database. If it is detected any sort of error that requires
changes in the TC_DB file, all the connections established automatically by the system
must be deleted. Then, the context menu “TLC Association” must be selected, after
which it will be shown the following dialog box.

By clicking on the “Remove” button, the associated file is deleted and the association
process can be initiated as described in the previous sections.

ATLAN V3.4 85/227 Ed 2.0

8.8 DRAWING OF CONNECTIONS
The assignment of terminals to Telecontrol signals causes that the terminals involved
become regarded as “used” and therefore they will not be available to be used in manual
connections.

Telecontrol signals can only be drawn automatically. That is, the table of connections
associated to the drawing of signals can be opened by means of the context menu of the
device to which it has been associated the TC_DB file.

Activate the signal that requires to be drawn by checking the corresponding selection
box on. The connection will be automatically drawn. These connections adopt the name
of the signal. Their name cannot be modified manually. These connections will not
become associated to any view of connections. Their assignment must be carried out
manually.

The drawing of signals can be performed in the basic engineering tool and in any detailed
drawing, which allows the Author of the project to decide which level of detail is shown
in each drawing. Connections drawn in the basic engineering of the project will be treated
as the rest of connections, reason why they will be able to be exported to those detailed
drawings in which they need to be shown.

Drawn signals will be shown with their selection box checked on in the “Telecontrol
connections drawn” table.

If any of those connections is manually deleted, then its check box will become
automatically deselected and the connection will then be able to be drawn again if
selected in subsequent stages of the design.

ATLAN V3.4 86/227 Ed 2.0

9 DOCUMENTATION
ATLAN’s working environment includes a set of functions to create documents, devised
to generate all the documented information required for every project.

The generated documents can be classified in two categories: drawings, and list of
connections. Both options can be selected from the “Documentation” menu. The
generation of the documents is based upon the corresponding documentation templates.
These templates define the format of each type of document to be generated, and
contain the size, text orientation, drawing area, data box, etc. By means of the
configuration menu, the format of every type of document can be defined, as well as new
formats can be created.

LFs have specific documentation templates that permit to generate documents

containing the details of the function being documented.

9.1 PROJECT DRAWINGS

The generation of drawings – as documents of a project – is activated by means of
submenu “Generate document” in the
“Documentation” menu. This submenu allows
generating project drawings as documents.

ATLAN’s functionality related to the control and

documentation of the changes introduced in a project
every time it is reviewed is described in section 11.3.

When the option of generating project documents is

selected, the following pop-up window is displayed:

In this window, the documentation template that will provide

the eventual format of the document, the views and the
working areas or “Taps” that need to be included in the
document can be selected.

When clicking on the “Accept” button, a new window with the

drawing edition working environment is displayed.

9.1.1 Drawing edition environment

The edition environment contains all the graphical elements of
the document to be generated and allows inserting additional
text comments as well as the data box. In addition, it is possible
to modify the drawing final size as well as to rearrange the
positions of the elements and the connection lines, if desired.
It is not possible to delete any element of the drawing, nor
changing the names of its elements. This guarantees that the
drawing reproduces exactly the contents of the project.

ATLAN V3.4 87/227 Ed 2.0

Zoom factor is shown on the tool bar in order to help the production of different drawing
with the same scale so the size of symbols will be the same.

The functions included in the edition working area are:

Save the drawing creating a pdf document

Increase the drawing size
Decrease the drawing size
Fit a selection to the window size
Fit the drawing to the paper size
Redraw automatically all the connections
Redraw the selected connection
Undo
Redo
Set the grid on/off
Insert text block without frame
Insert text block with frame
Insert the frame and data block as defined by the selected documentation template,
showing the effective drawing area.

The system’s data box is inserted by default. Using the menu “Tools – Choose template”
or clicking the icon , any previously user defined data box can be selected. See
chapter 19 for additional details on how to create and maintain customised template data
boxes.

In order to produce a drawing’s document it is advised to follow the next steps:

1. Arrange devices’ and connections’ layout and size so that they have the desired
appearance.
2. Add the drawing frame and the data box by clicking on the icon.
3. Reduce the size of the drawing to be able to visualise its final appearance.

ATLAN V3.4 88/227 Ed 2.0

 4. Save the document by clicking on the icon.

The size and final appearance of the drawing contained in the document can be adjusted
in two steps. When generating the drawing, neither its frame nor the data box is shown.
The window adopts the size equivalent to that of the paper size previously selected in
the frame. The size of the drawing can be modified by means of the zoom functionalities
so that it can be adjusted to the paper size selected. When inserting the frame, the size
of the drawing cannot be modified. Also, from that moment on the zoom functions just
modify the view of the document on the screen, but not its actual size. If the size and/or
the position of the drawing are not appropriate, the frame can be disabled so that the
size of the drawing can be modified.

In order to move a whole drawing, all its elements must be selected first, and then
dragged as required by holding the right button of the mouse pressed.

Once the drawing has the required size and position, the frame and the data box must
be inserted by clicking on icon .

From that moment on, it is shown the effective area of the drawing considering the paper
size, margins and size of the data box. This area is shown by a dotted outline, as it can
be seen in the following figure. The outline can be removed just by clicking again on the
icon, so that the size or the position of the drawing can be again modified as desired.

It is the responsibility of the Editor of the document to place all the elements of the
drawing, IEDs and connections inside the dotted area as those parts being outside this
area. Elements placed outside the drawing area will not be drawn, or will be hidden by
the data box.

ATLAN V3.4 89/227 Ed 2.0

The drawings of a project can be generated at any moment of the substation design. In
intermediate phases of the design, the drawing generation functionality can be useful to
supervise the progress of the whole design. All documents generated during this stage
are just drafts and cannot be signed nor approved – all of them are shown with the
watermark “DRAFT”, as it can be appreciated in the next figure –.

ATLAN V3.4 90/227 Ed 2.0

It is not allowed to save a document if the drawing does not fit within the frame.

Once the edition process is finished, the resulting document can be saved by using the
icon, after which it is opened the following pop-up window, which allows entering the
file name and the type of document to be generated. Documents can be generated
whether in pdf or svg format.

ATLAN V3.4 91/227 Ed 2.0

When clicking on the “Save” button in the previous case, the file will be generated with
the specified name. Before generating the file, the following pop-up window will be shown
to allow the user filling in data block.

That file will be stored in the documentation folder of the corresponding project. When
the file generated is a draft, this will be stored in the folder of project drafts. Once a
current version of the project is closed, it will not be possible to generate new draft
documents, although the generated documents will also remain available in the
documentation folder of the project.
The procedure to view and print documents is described in section 9.10.

If at the time of saving a document it is required that the user fills-in any of the fields of
the data box, a pop-up window allowing the introduction of the required data will be
displayed. Those data that can be automatically documented – such as the name of the
project, version or revision – will not appear on this window, as the related information
will be automatically inserted in the corresponding field of the data box. See chapter 19
for additional information regarding data boxes functionality.

Documents can be exported outside ATLAN’s working environment as described in

chapter 16.

When the user wants to quit the drawing editorial session before ending the edition job,
it is possible to save the job by using the submenu “File – Temporarily Save”. The job
will be saved and the project automatically closed. When opening the project again,
editorial job can be continued.

9.2 CUSTOM FRAME DRAWINGS

It is possible to produce drawings using custom defined frames. The procedure is as
described in previous chapter.

When the menu “Generate frame drawing” is selected, the following window is opened.

ATLAN V3.4 92/227 Ed 2.0

The frame to be used to produce the drawing has to be chosen form the list shown on
the box “Frame”.

All the frames shown on this list has been ´previously generated following the procedure
explained at chapter 20.

9.3 LOGICAL FUNCTIONS DOCUMENTATION

All the Logical Functions included in a project can be documented by using the “Logical
Function documentation” submenu in the “Documentation” menu. When selecting this
option the following pop-up window is displayed, where
the LF to be documented and the documentation
template to be used can be selected.

Once the desired options selected, the corresponding

document will be generated in pdf format and it will be
stored together with the rest of the documents of the
project.

9.4 CONNECTIONS LISTS

ATLAN’s working environment also allows the generation of documents that include
listings of the connections defined in a project. These lists can be classified by concepts
and contents.

ATLAN V3.4 93/227 Ed 2.0

 By selecting the “Generate document with connection List” submenu in the
“Documentation” menu, the window shown in the following figure is first displayed. In
this window, users can select the searching criteria to work as a filter over the set of
connections defined in the project.

As result of the “Search” defined by means of the previous window, a set of

connections will be shown as in the following figure.

The list shows the connections classified according to their type. The boxes on the
header block allow selecting the fields that will form the generated document, together
with the template and the chosen type of document.

By entering a name in the “Name:” field and clicking on the “Accept” button, a pdf
document with the selected information becomes generated and subsequently stored
together with the rest of the documentation of the project.

9.5 GSE AND SMV CONNECTIONS LISTS

It is possible with ATLAN to generate lists of GSE and/or SMV connections. These
connections represent the interchange of information between IEC 61850 devices.

ATLAN V3.4 94/227 Ed 2.0

By using the “Generate document with connection List GSE-SMV” submenu in the
“Documentation” menu, it can be generated the list of the GSE – SMV connections
defined in the project.

When selecting that submenu, the following pop-up window is shown:

This list shows the GSE – SMV connections. From the selection boxes on the header
block, users can select the fields that will form the document generated, together with
the template and the type of document having been chosen.

By entering a name in the “Name:” field and clicking on the “Accept” button, a pdf
document with the selected information becomes generated; once generated, the
document is stored together with the rest of the documentation of the project.

9.6 MMS CONNECTIONS LISTS

It is possible with ATLAN to generate lists of the MMS connections. These connections
represent the interchange of information between IEC 61850 devices in client-server
mode, using the MMS protocol.

The list of the MMS connections in a project is generated by using the “Generate a
document with connection List MMS” submenu in the “Documentation” menu.

When activating that submenu, the following pop-up window is displayed:

This list shows the MMS connections defined in the project. From the selection boxes on
the header block, users can select the fields that will form the document generated,
together with the template and the type of document having been chosen.

By entering a name in the “Name:” field and clicking on the “Accept” button, a pdf
document with the selected information becomes generated; once generated, the
document is stored together with the rest of the documentation of the project.

ATLAN V3.4 95/227 Ed 2.0

9.7 LIST OF OUT-OF-STANDARD LOGICAL CONNECTIONS
Just as it is described in section 12.2, the IEC 61850 devices for which there does not
exists any valid .icd or .cid file can be modelled in terms of Logical Nodes; but the
interconnections carried out between them cannot be included in the .scd file.
Nevertheless, instead of that it is possible to generate a document with the list of all the
signals that will need to be manually programmed in the configuration of the devices.

That document will be generated by selecting the “Connection list without SCD” submenu
in the “Documentation” menu.

9.8 LISTING OF DEVICES

By means of the “Device list” submenu in the “Documentation” menu, it can be generated
a document that includes the listing of all the devices used in the project. When selecting
this submenu, the following pop-up window is displayed, allowing further filtering criteria
for searching information to be added.

Once the additional filtering criteria have been set, click on the “Search” button to
continue. The following window containing the tracked information will be then displayed.

Introducing a unique name and clicking on “Accept”, a document with the selected
information is produced.

ATLAN V3.4 96/227 Ed 2.0

9.9 DOCUMENTATION OF TELECONTROL DATABASES
The “Telecontrol documentation” submenu allows generating a document that describes
the mapping of the Telecontrol Database over the devices showing, in addition, the
connections that have been established automatically by the system.

By selecting the previous submenu, it is automatically displayed a window that shows all
the devices of the project that have associated a Telecontrol Database.

By selecting the device and clicking on “Accept”, it is shown the mapping information
regarding Telecontrol signals.

By clicking on “Document generation”, it is automatically generated a document with all

the information contained in the previous window.

During the mapping process, it is possible to generate the following listings:

- Listing of file with not associated signals. It is generated on user demand when
the association process is interrupted.
- Listing of file with not associated IEDs. It is generated on user demand when the
association process is interrupted.
- Listing of Telecontrol signals. It generates a list that includes the IED identifier
and the RTU type, in the header of the page; and, in the columns, the following
fields:
o RTU terminal
o Signal name
o Type: Physical or Logical
o Controlled IED name
o Controlled IED terminal

ATLAN V3.4 97/227 Ed 2.0

9.10 VIEWING OF VLAN’s
This functionality makes possible to view graphically and document the different VLAN’s
that need to be supported by every LAN in the project, as well as the GOOSE messages
associated to each VLAN; and also to generate all the documentation associated to the
corresponding configuration.

ATLAN functions related to documentation of VLAN’s are included in submenu “LAN

Viewer”, within the “Documentation” menu.

By selecting this menu, ATLAN generates automatically a list of the VLAN’s defined in
the project. This information is obtained from the configuration parameters of the GOOSE
messages. In consequence, if all the parameters of the GOOSE connections have not
been previously configured, the information presented by means of these menus may be
incomplete.

By activating the “LAN Viewer” submenu, it is shown the list of VLAN’s. When a VLAN is
selected, it is opened a new working environment in which it can be seen all the IEDs
that are interconnected in that VLAN, as well as the Ethernet Switches that form the
VLAN. Once that window is displayed, it will be possible to work at VLAN level.

Once it is selected the information to be presented, it is displayed a window that shows

the devices involved, as well as the corresponding communication interconnections.

Next figure shows the appearance of the VLAN’s working environment.

This drawing will show the Switches of the selected LAN and all the IEDs connected to
the Switches through the communication ports. Only the physical connections of
communication will be shown.

ATLAN V3.4 98/227 Ed 2.0

Its way of working is exactly the same as that of the generation of drawings. In this case,
from the “View” menu it is possible to select the VLAN’s that result from the configuration
of the GOOSE messages by means of the “Select VLAN’s GOOSE” submenu; as well
as the VLAN’s defined specifically by the user by means of the “Select Non-61850
VLAN’s” menu. These VLAN’s are defined from the “Tools – Define new VLAN” menu,
as described in section 9.9.2.

9.10.1 Documentation of VLAN’s

Documentation functions in the LAN’s viewer allow generating the documents associated
to a selected LAN. The “Documentation” menu contains the following submenus:

- Generate Document. Generates the drawing of the selected LAN with the VLAN’s
views that have been selected. As for the generation of drawings, it is necessary
to add the frame of the document as a previous step to generation of the
document by clicking on icon . By modifying the scale of the zoom, it can be
visualised the aspect of the document that will be generated.

- Listings of VLAN’s. By activating this submenu, it is displayed a dialog box that

permits to select the VLAN. One this selected, it will be automatically generated
the file that contains the list of the IEDs that participate in the VLAN, as well as
the GOOSE messages that are associated to that VLAN.

- Listings of non-61850 VLAN’s. By activating this submenu, it is displayed a dialog

box that permits to select the VLAN. One this selected, it will be automatically
generated the file that contains the list of the IEDs that participate in the VLAN,
together with the comments associated to that VLAN.

- Listings of Devices included in the LAN. It generates automatically a list that

includes all the devices with functionality of Ethernet Switch that form the selected
LAN.

- Configuration List. It generates a document that contains the configuration

parameters of the devices that form the selected LAN – that is, the Ethernet
Switches as well as the connected IEDs –. If any of these devices has not been
previously configured – and therefore does not have associated any configuration
parameter –, it will not be included in this document.

- Select template. It allows selecting the documentation template that will be

applied to the drawing. The templates that are shown in the drop-down menu are
those generated by means of the preferences menu.

9.10.2 VLANs viewer tools

The LAN’s working environment contains a set of specific tools that allow defining and
maintaining those VLAN’s that are not associated to GOOSE messages.

The “Tools” menu contains submenus: “Define new VLAN” and “Edit Created VLAN”.
These menus apply only to VLAN’s that are not related to GOOSE messages.

ATLAN V3.4 99/227 Ed 2.0

Definition of new VLAN

By selecting submenu “Tools – Define new VLAN”, the following form is displayed:

The definition of a new VLAN requires introducing the following information:

- Participant IEDs. All the IEDs that are connected to the LAN are shown in the list
of IEDs. In this list, the IEDs that participate in the new VLAN need to be selected.

- VLAN Identification.

- Comments. Free text field. They will be shown by activating the Tooltip and place
the cursor over the new VLAN.

By clicking on the “Accept” button, the new IEDs selected will be shown in the drawing
as well as the LAN connections of the new IEDs and the newly defined VLAN will be
automatically drawn.

Edition of Created VLANs

By selecting submenu “Tools – Edit created VLAN”, it is possible to add or remove IEDs
associated to Created VLANs.

By selecting this function, it is displayed the following window, where the IEDs that
participate in the VLAN.

In order to modify VLAN participants it is necessary to perform again the selection of the
IEDs involved and then click on “Modify”.

By clicking on the “Remove” button, the selected VLAN will be deleted.

ATLAN V3.4 100/227 Ed 2.0

ATLAN V3.4 101/227 Ed 2.0
9.11 VIEWING AND PRINTING DOCUMENTS
The documents of the project can be visualised by using the “Open documentation”
submenu in the “Tools” menu.

Documents are classified by types. Select a file and click on “Open” to view it, or just
double click on it.

9.11.1 Viewing of IEC 61850 files

The “Open 61850 file” submenu within the “Tools” menu shows the files generated by
configuring the IEC 61850 devices of the project.

The following pop-up window is opened when activating this function.

ATLAN V3.4 102/227 Ed 2.0

Selecting one file from the list first, this can be opened either with ATLAN’s XML viewer
or with the viewer associated to the operating system (see previous figure).

The “Open 61850 file” window also includes the “Validate” button, by means of which it
is possible to validate any of the files included in the list.

It is possible to validate the file against three different version of the standard. The
following window allows the version to be chosen.

If the system finds any error during the validation of a selected file, the following pop-up
window is displayed.

By clicking on the “Details” button, it is displayed a window that shows the type of errors
and their possible cause.

ATLAN V3.4 103/227 Ed 2.0

The details of the causes and the corresponding solutions for the types of errors that can
be encountered during the validation of 61850 files are described in the “Considerations
for the edition and the configuration of IEC 61850 files” manual.

9.12 Viewing svg files

By opening the submenu “Tools – Open SVG Documentation” all the documents
generated in svg format are shown. To open any document just double click on the
desired document name or select it by clicking on the name and click on the button
“Open”. The file will be opened using the default svg viewer.

ATLAN V3.4 104/227 Ed 2.0

10 DOCUMENTATION OF IEC 61850 FILES
ATLAN’s working environment includes a specific documentation facility for the .cid and
.scd files of the project.

By selecting the “SCD list” submenu in the “Documentation” menu it is displayed the
following pop-up window, which allows users to define the contents of the documentation
that requires to be generated.

The Data type block in the “SCD list” window is used to define the type of information to
be included in the document. Select the boxes of the information that has to be included
in the document.

The “Range” block defines whether the document will include the whole .scd file; only
.scd data related to an IED; or just .scd data included in a Logical Device or in a Logical
Node.

By entering a name for the document and clicking on the “Create Documentation” button,
an intelligible pdf file with the selected information will be automatically created, together
with its XML code.

ATLAN V3.4 105/227 Ed 2.0

11 TRACEABILITY AND CONTROL OF DOCUMENTATION
ATLAN provides a number of internal functions and user’s facilities to guarantee the
integrity and authenticity of the projects and all their associated documents, which
facilitate the maintenance of the documents and the traceability of the projects.
Documents’ management and control is internally based upon the electronic signatures
of the authorised users of a project.

11.1 DOCUMENT MANAGEMENT PROCESS

The control of the document management is carried out from the project’s signature and
from the identification of the user that signs the project.

From the moment in which a project has been signed, it gets blocked and all the
generated documents become definitive as well as identified with the version and the
revision of the project from which they have adopted the information.

The following figure shows the simplified document management process.

PROJECT
NEW DRAFT
XYZ EDITION
PROJECT DOCUMENTS
Vn.0

Vn+1.0 Project AUTHOR

is generated SIGNS
PROJECT
Project and Docs
are stored
PROJECT
DATA BASE

DOC
GENERATION
PDF
WORD

REVIEWER REVIEWER
A new project MODIFY SIGNS
V1.r+1 is PROJECT PROJECT
generated

A new Project
Vn+1.0 is generated APPROVER
SIGNS
PROJECT

PROJECT
AUTHOR SIGNS UNDER EDITION
PROJECT EDITION

PROJECT
COMPLETED

AUTHOR
MODIFIES
PROJECT

As shown in the previous diagram, the project management process starts the creation
of a new project by the Administrator. The new project is identified with the V0.0 version
and once it is signed by the Author, it will be stored in the file structure of the project,

ATLAN V3.4 106/227 Ed 2.0

depicted in the previous figure as Project Data Base. From this moment on, all the
documents created during the edition process will take the version and revision of the
project.

The following sections depict the details of this process.

11.1.1 Users
There are four types of users in ATLAN:

- Administrator. It is a very specific user entitled to carry out ATLAN configuration

functions, as he can carry out a set of tasks oriented to the configuration of the
application and the creation of new projects. The functions exclusively associated
to the Administrator are:
o Creation of a new project.
o Definition and authorisation of users for every a project.
o Signature generation.
o Device and Logical Functions libraries administration.
- Author. Produces the projects and their associated documents. It can set
preferences and frameworks to be used in the documents of the project, as well
as edit and create new templates of documentation in a project.
- Reviewer. Reviews the projects and is entitled to modify them only if they have
already been signed by the Author.
- Approver. He can only sing a project, and all its associated documents, in order
to approve it. No changes at all can be introduced by the Approver.

The Administrator is unique for every ATLAN licence. A password is required to activate
administrator menus when installing the application.

The Author, Reviewer and Approver are unique for every project. They are defined by
the Administrator when a new project is created.

11.2 New Project Creation

To create a new project use the “File – New
Project” menu or click on the icon on the
functions bar. This function can only be used by
the Administrator. The following pop-window is
shown to enter the information related to the
project, such as user’s views, connection views,
and the Author, Reviewer and Approver.

It is recommended to create user views enough

so that the creation of customised drawings can
be flexible (see section 9.1).

Once the project has been created, the

Administrator must save it in the predetermined
location. By doing so, the system automatically
creates the tree-folder and the data structure
that permit to store all the sets of information
related to the project, including all its associated versions and revisions.

ATLAN V3.4 107/227 Ed 2.0

The following step is the creation of the users’ signatures, which can be done by selecting
the “Preferences” submenu in the “Tools” menu. This gives access to the following pop-
up window.

Once the signatures of the project have been created it is necessary to save the project
in order to store the information associated with the signatures. Once this done, the
Author can work on the project.

11.2.1 Editing a Project

To start the edition process of an existing project, the user has
to login introducing the name, key and type of user.

The edition of a project by the Author does not have any effect
on the traceability.

The Reviewer can only edit a project already signed by the

Author. This will automatically generate a new revision when
the project is saved.

The Approver cannot edit projects. He can only sign projects

already signed by the Author and the Reviewer.

11.2.2 Signing a Project

The signature of a project certifies that it has not been modified. It is the base of the
traceability process, as a project that has been signed is stored as a finished project over
which all sort of documents can be generated, regardless the version of the project
having been signed and stored.

The signature of the project guarantees its integrity and certifies that the user has signed,
accepts and/or becomes responsible for the created documentation.
The signature of a project by the Author, Reviewer and Approver modifies the version
and revision identifiers, and automatically creates the tree-folder where all its information
and the documents are stored as they are generated.

ATLAN V3.4 108/227 Ed 2.0

The signatures must be introduced in the pre-established sequence; that is, the Author
must sign first; then the Reviewer; and finally the Approver.

To sign a project use the “Tools – Sign” menu or click on icon . This gives access to
the following pop-up window, which allows signing the project or the documents with the
same version and revision as the project, having been generated prior to the introduction
of the signatures of the Author, Reviewer and Approver.

11.2.3 Rules to create new versions and revisions

ATLAN manages automatically the creation of new versions and revisions of the
projects, according to the introduced signatures and to the modifications carried out
by the Author or the Reviewer. The rules applied to create new versions and revisions
are as follows:
- A new project starts in a draft identified as V0.0. Only the Author can modify the
project as many times as required. These modifications do not change the version
and revision id.
- When the Author sings a project, it becomes read-only and a copy of the project
is automatically created with the Id Vx.0, where “x” is the version ordinal and “0”
is the revision ordinal. For instance, when the first draft is signed the project
version V1.0 becomes automatically generated.
- Therefore, the Reviewer has to start its work over a version with revision number
“0”, as this is signed by the Author. If the reviewer does not introduce any change
over the version generated by the Author and signs the project, the Id of the
project will not be changed. For example, if the Reviewer opens and signs the
V1.0, the identifier does not change and only the sign of the Reviewer is added.
- If the reviewer modifies the project, a new revision will be automatically created
when the project is saved. In our case, it would be the V1.1. Every time the
reviewer introduces a new modification, the revision identifier will be incremented
by one.
- A project modified by the reviewer, i.e. V1.1, has to be signed again by the Author
in order to acknowledge the changes. This will generate a new version with Id
Vx.0. (V2.0 in the example). This version must be signed by the Author, Reviewer
and Approver so that it becomes definitive. The only difference between versions
V1.1 and V2.0 is that the latter has been signed at least by the Author. The
contents are identical.
- If the Reviewer detects a relevant fault or mistake in the last version, he can
always continue working over a previous version (if it exists). If, for instance, the
Reviewer modifies version V1.0 existing V2.0, when he saves the changes the
V2.1 version will be automatically generated.

ATLAN V3.4 109/227 Ed 2.0

Electronic signatures are used at internal level by the application in order to control the
flow in the document management process; as well as so that ATLAN’s users can verify
at any time the integrity of the projects and the authenticity of the generated documents.

ATLAN keeps a register of the project, consisting in a chronological listing of the events
of creation in the project, with their dates. In this file it is also registered the date of
creation of all the documents associated to the project, including the drafts. This file can
be exported and visualised by selecting the “See Loogbook” submenu in the “Tools”
menu.

11.2.4 Signing Documents

Documents take the signatures from the project where they proceed from, as for the
process of design it is guaranteed that the information cannot be changed and therefore
all the documents are an accurate reflection of the information contained in the project.

Drawings generated before introducing the signatures of the Reviewer and the Approver
can be signed subsequently, always that any modification has been introduced in the
project – and thus this maintains its version and revision identifiers. In such a case, the
“Signed” submenu must be used – or the icon on the tools bar clicked – to select the
document(s) to be signed, as shown in the next figure.

Once the document has been signed by the Author, Reviewer and Approver the following
pop-up window is displayed, where the fields of the data box can be defined.

The signature of a draft document does not erase the draft but generates a new
document with the same name, followed by the “signed” indicator. In such a document,
the watermark “Draft” has been eliminated, and the fields in the data box have been filled
in with the data introduced by the user; system’s default data if applicable; and the visible
data of the signatures. In addition, the document has been signed with the electronic
signatures of the Author, Reviewer and Approver, and for this reason its integrity can be
verified at any time.

ATLAN V3.4 110/227 Ed 2.0

When a new document is generated from a totally signed project, there is no need to
sign it since it automatically takes the signatures of the project when the new document
is saved.

When a customised data box is used – see the data box definition tool described in
chapter 19 –, the introduction of data related to the data box is carried out by means of
a window that contains the form to enter the data defined in the data box. The number
of inputs and format of the form depends on the definition enter by the user.

Documentation related to Logical Functions and connection lists that have been
generated before the signature of the project cannot be signed again. To be able
introduce different signatures it is required to generate the documents again so that the
new signatures and the information of the data box can be introduced as explained
previously.

11.2.5 Verifying Signatures

The menu “Tools – Verify” allows project and documents signatures to be verified.

By activating this function, the following pop-up window is shown. It is possible to verify
the whole project or any of the documents of the project.

ATLAN V3.4 111/227 Ed 2.0

The previous figure shows an example in which the project to be verified had not been
previously signed. Consequently, the system informs about that situation.

The next figure shows the verification of a document that contains three valid signatures,
which certifies that the document has not been modified since it was generated.

Note that the “Verify document” option has been selected – and then the required has
been chosen from the corresponding pop-down menu – in the “Verify” area on the upper
part of the window.

ATLAN V3.4 112/227 Ed 2.0

As it can be seen in the example shown in the next figure, the “Verify” window shows,
for every signature of the Author, the date in which it was signed and additional data
corresponding to the certificate of the signature.

It is also possible to verify the signatures of the project selecting “Verify Project”. The
result will be shown as seen in the following window:

ATLAN V3.4 113/227 Ed 2.0

When the project has been signed by Author, Reviewer and Approver the signature
verification provides the following information.

If the project contains any document that has not been signed, a pop-up window as that
shown next will be displayed.

ATLAN V3.4 114/227 Ed 2.0

11.2.6 Log Diary

ATLAN provides a log of the project activity. The log records chronologically all the
operations performed over the life of the project.

Basic operations such as opening, saving, closing or signing projects can be recorded
together with the identification of the user who has carried them out and the timestamp
of the event.

Selecting the menu “Tools – See notes” the following log information will be displayed:

ATLAN V3.4 115/227 Ed 2.0

11.3 CONTROL OF CHANGES
ATLAN provides functions to control and document the changes introduced in a project
every time it is reviewed.

Deleted elements, devices or connections, are highlighted in yellow whilst added

elements are highlighted in red.

This function is always activated. Hence, the information required to document changes
is automatically stored by the system and always available for the user. Therefore,
changes can be documented when required.

The graphical control of changes becomes operative once the Author finishes and signs
the project. At that moment, it is generated the V1.0 version, over which the Reviewer
must work. All the changes carried out by the Reviewer over version V1.0 are registered
in such a way that when the Reviewer saves the changes – thus the V1.1 version being
generated – all the elements and connections added and/or deleted will be able to be
automatically generated by the system. This documentation can be generated by the
Author as well as by the Reviewer.

Once the changes are accepted by the Author and he signs version V1.1, the V2.0
version will be automatically generated. If new modifications arose, the process would
start over again.

ATLAN V3.4 116/227 Ed 2.0

11.3.1 Documenting deleted devices and connections
The “Documentation – Generate creation document” submenu opens a documentation
environment similar to that described in section 9.1.1, where the elements and
connections that have been deleted are shown highlighted in yellow colour.

The edit functions available in this environment are exactly the same as those described
in section 9.1.1.

11.3.2 Documenting added devices and connections

The “Documentation – Generate creation document” submenu opens a documentation
environment similar to that described in section 9.1.1, where the elements and
connections that have been added are shown highlighted in red colour.

From the documentation of changes window, lists of added or deleted connections can
be generated by activating the “Documentation” menu. This provides access to the
submenus that allow creating list of connections and of added or deleted devices, as well
as of the logical functions implied. These documents keep the same format as those
generated for the project.

ATLAN V3.4 117/227 Ed 2.0

12 DEVICES CONFIGURATION
The configuration of the devices included in a project should be carried out once this has
been completely finished. ATLAN provides a number of functions to configure the
devices included in the project. All these functions are enclosed under the “Tools -
Configuration” menu.

The configuration process implies the generation of a set of files that define the
communication scheme of the project, and the connections between the devices and the
Logical Functions having been mapped to every device. In projects that include IEC
61850 devices, all the .cid files, the .scd file and the ssd file will be generated.

The process of generating the files and the documentation of the configurations can only
be carried out by the Author. Configuration files can be generated at any time; that is,
regardless the project has not been signed, it has been partially signed or it has been
definitely approved. The corresponding generated files and documents include the
signatures of the project, and for this reason, their authenticity and traceability must be
verified.

12.1 LOGICAL FUNCTIONS CONFIGURATION

The configuration of Logical Functions implies a specific compilation process that is
performed in several stages. On one hand, those LFs implemented by several devices
must be split into the part that has to be executed by every device. On the other hand,
IEDs involved in several LFs, total or partially, must receive a unique configuration file.
This is why it is necessary to create a file that groups those parts of the LF’s implemented
by every IED. Once the file of the logic that every IED must implement is obtained, the
XML file that represents such logic can be generated so that it can be imported by other
applications.

The function used to configure LFs generates information that is documented in graphical
format. In these documents, ATLAN creates automatically the graph of all the logical
elements that require to be configured on the selected IED. Such diagram will be able to
be used by the programmer of the IED in order to – by means of the configuration tool
proprietary of every IED – program all the logical elements involved in the implementation
of the different LFs configured in the project.

By selecting the “Tool – Configuration - Devices” submenu, the following pop-window is

displayed:

ATLAN V3.4 118/227 Ed 2.0

The configuration process consists of two parts: the configuration of the LFs; and the
generation of the IEC 61850 configuration files.

The configuration files of the LFs can be generated in a single stage by selecting the
option “Configure all devices”. This will generate a configuration file in pdf format.

When putting the service into service as well as if specific tests for a LF or debugging of
the interactions between LFs are required, it is possible to generate the configuration of
an IED in an individual manner, being also possible to select the LFs that require to be
programmed with the configuration files.

By clicking on the “Generate” button, the corresponding files will be generated according
to the selection carried out.

12.2 CONFIGURATION OF THE COMMUNICATIONS

A crucial aspect for the correct operation of an IEC 61850 substation is the appropriate
definition and configuration of the communications.

ATLAN includes a set of functions that allow users to configure IEDs as well as Ethernet
Switches in such a way that it can be verified whether the GSE or MMS connections
defined along the design of a project are feasible for the communication system or not.
In addition, an important part of the configuration data must be included in the .scd

ATLAN V3.4 119/227 Ed 2.0

substation configuration file. This configuration is carried out as the project is developed.
The configuration parameters of each IED need to be introduced as described in section
5.5.

Once the project is finished, it can be generated a text file that includes the configuration
data of those devices which include communication functions.

By selecting the “Communications” submenu in the “Configuration” menu, the following

pop-up window is displayed in order to introduce the name of the document to be
generated.

12.3 IEC 61850 DEVICES CONFIGURATION

The IEC 61850 device configuration function’s main objective is the generation of the
.scd substation configuration file. This file includes the information of all the IEC 61850
IEDs involved in the project; their communication data; and the GOOSE signals having
been configured. To be able to generate this file, it is necessary that the GOOSE or GSE
and SMV connections in general have been previously carried out, which at the same
time requires that the IEDs involved have been configured with the appropriate data
structure in terms of DataSet, GSEcontrol, Reports and Logs. This configuration can
either come defined in the .icd file or the .cid file used in order to define the generic model
of the IED, or it can also be defined manually by means of the functionalities included in
ATLAN for that purpose, as it is described in section 5.4.

The process of configuration of devices IEC 61850 consists of two parts: the generation
of the .scd file that includes all the data being relevant within the IEC 61850 environment;
and the generation of each of the IED’ configuration .cid files. This latter part is optional,
as it depends on the capabilities of the own IED configuration tools; that is, whether such
tools are able to work with the .scd file, or on the contrary they need a particular file for
every IED.

Next figure shows the possibilities offered by ATLAN at the time of generating the IEC
61850 configuration. The upper “SCD files content” block is used to define whether the
.scd file must include the part related to the description of the substation and if it is
required to generate individual configuration files for every IED. If so, the lower “IED’s
individual configuration” block allows selecting the IEDs for which it is required to
generate a .cid file.

Once all the options selected, the configuration files are automatically generated by
clicking on the “Generate” button.

ATLAN V3.4 120/227 Ed 2.0

12.4 SSD FILE GENERATION
The generation of the ssd file is carried out in two phases:
1. Single-wire diagram generation. Single-wire diagram is created using standard
ATLAN resources as described in previous chapters. From the single-wire
diagram and the configuration parameters of the devices used to create the
single-wire diagram, the part of the ssd file that describes the high voltage
apparatus and their topology is automatically generated.
2. Functional description. The second phase consists of the definition of the
functionality associated to the single-wire diagram components by adding LNs to
the diagram and defining their functional association.

The ssd file can be generated before the project is finished as it can be used as
specification or formal and functional documentation of the single-wire project.

It is important to understand the role of every configuration parameter used in the

creation of the ssd file and how these parameters are mapped in the ssd file fields in
order to make the file useful and understandable for external users.

Once the single-wire design is finished, all the LNs or IEDs containing LNs that will have
functional relations have been defined, the process depicted in the following paragraphs
has to be followed.

ATLAN V3.4 121/227 Ed 2.0

By clicking on the folder “SSD file generation” of the menu “Device Configuration”, the
following window is opened. The name of the ssd file has to be introduced to generate
the ssd file.

Clicking on “Generate SSD”, the file generation process is started up as described in the
following paragraphs and sections.

Clicking on “Edit” it is possible to resume a former LN assignation process. In this case,

the LN assignation window will be shown including the data already introduced in
previous sessions.

The “Edit” button will only be active if a former session has been stopped without the ssd
file being generated.

12.4.1 Semantic selection

It is possible to choose which of the three semantics defined by the IEC 61850 in its
different releases has to be used in the process of creation of the ssd file.

ATLAN V3.4 122/227 Ed 2.0

The semantic version determines the way generic classes are defined. That is to say,
how voltages and current levels are expressed. If the units of voltages and currents are
not exactly defined as indicated by the standard, they are not going to be properly coded
and therefore the ssd file will not represent the single-wire diagram configuration.

It is important to consider that ATLAN determines substation voltage levels automatically

from the voltages defined in the single-wire equipment using the semantic rules defined
by the IEC 61850 standard. Consequently, it is mandatory that the voltage levels of the
single-wire equipment be expressed in kV and its associated generic class have been
defined using the correct semantic in terms of spaces, capital and small letters, etc.

12.4.2 Selection of bays and voltage levels

ATLAN allows choosing which part of the single-wire diagram will be included in the
specification. Thank to this, it is possible to generate the specification of single bay of a
project or the specification of every bay in separate files.

The lower part of the window allows voltage levels to be renamed using a standard
notation or the proprietary location chosen by the user. It is important to consider that
the voltage list is automatically generated by ATLAN from the internal information of the
models and IEDs used in the project. If a voltage level is not included in this list, IEDs
configuration and models definition has to be checked.

ATLAN V3.4 123/227 Ed 2.0

The name used to identify voltage levels is fully opened, that is to say, it may be a string
of any length. Nevertheless, it is recommended to a standard notation to make the
understanding of the project easier to third parties external to the project design.

The association of an IED to a Bay is determined form the user view associated to every
IED. That is to say, all the IEDs associated to the same user’s view and the same voltage
level will form a bay. The same given to a view can be freely chosen by the user. These
views have to be generated when the project is created.

12.4.3 ssd file content

The components and concepts required for the generation of the ssd file are
automatically discovered by ATLAN by reading project information and specifically
single-wire components and configuration parameters. All the elements identified are
shown on the following window that is used to carry out functional mapping of single-wire
devices to LNs.

The left part of the window shows all the elements that will be added in the ssd. The
upper part of the block “SSD Elements” shows substation Bays, voltage levels, etc
whereas the lower part shows the equipment associated to the upper selected element.

The mid part the IEDs of the project and the right part the LNs of the IED selected in the
middle part. The LNs contained in an IED may have been defined from a valid icd file or
defined using ATLAN library tools.

It is important to remember that ATLAN cannot work with isolated LNs. A LN is a

functional component of an IED so if the author wants to specify a project in terms of

ATLAN V3.4 124/227 Ed 2.0

LNs, he has to define IEDs with a single LN inside. These IEDs will be inserted in the
ssd file as “virtual” IEDs.

Functional association between single-wire equipment and LNs is carried out following
the next procedure:

1. Select a single-wire component in the left upper side of the window

2. Select the equipment in the left lower side.
3. Select the associated IED that will perform a related function on the central
window
4. Select the LN that will perform the functionality on the right part of the window
5. Click on “Add” to create the association. A new line will be added in the lower list
6. Repeat the above-mention process for every functional association

If the process has to be halted before defining all the functional association, click on
“Save” and finish the session clicking on “Cancel”. The process can be resumed starting
up the ssd generation process again and clicking on “Edit”.

Non-assigned LNs will be automatically assigned to the substation.

12.4.4 Specific considerations

This section describes specific considerations that have to be taken into account when
defining models and specification projects.

Voltage Levels
Voltage levels are automatically determined from the voltage configuration of the IEDs
that have their “Functional Association” Field activated.

Out of Power Transformers, all the elements of a bay have to have the same voltage
level. Otherwise, an error will be reported and the generation of the ssd file will be
aborted.

Bay
A bay includes all the elements that have the same voltage level and are associated to
the same user’s view. The name of the common view is used as bay identifier.

The name of a Bay cannot be associated to several elements with different voltage
levels.

If any IED does not comply with this rules, an error message will be generated nad the
generation of the ssd file will be aborted.

Current and voltage transformers

When current and voltage transformers are modelled using three-phase connections, it
is possible to assign a LN to every phase including the neutral connector. In this case,
every winding will be identified by adding the letters “A”, “B”, “C” and “N”.

Power Transformers
Power transformers have a specific procedure. The voltage of every high voltage winding
is used it to a voltage level.

ATLAN V3.4 125/227 Ed 2.0

Bus Bars
Bus bars are modelled in ATLAN as a special IED that has a single connection terminal
accepting unlimited connections.

In order to include the bus bars as an element of the single-wire diagram and therefore,
be part of the ssd file, it is mandatory to model this special IED with the proprietary
functional code “BUSB” (Bus Bar).

12.4.5 Configuration errors

ATLAN is an open working environment that may work and combine different
technologies in a single project so it is important to consider that when working in an IEC
61850 environment the following considerations has to be taken into account.

Device naming
Even though IED naming in ATLAN is fully open, In an IEC 61850 project, naming of
IEDs containing LNs have to start with a character [A-Z, a-z]. Otherwise, when the
validation of the ssd file will report the following error:

Error: cvc-pattern-valid: Value '52_Interruptor_LNs_NO_ICD' is not facet-valid with

respect to pattern '[A-Z,a-z][0-9,A-Z,a-z,_]*' for type 'tIEDName'.

Error: cvc-attribute.3: The value '52_Interruptor_LNs_NO_ICD' of attribute 'iedName' on

element 'LNode' is not valid with respect to its type, 'tIEDName'.

Single-wire verification errors

It is not possible to create an ssd file without at least a Bay and at least a voltage level.
If these elements are not included, the following error will be reported:

Error: cvc-complex-type.2.4.b: The content of element 'VoltageLevel' is not complete.

One of '{"http://www.iec.ch/61850/2003/SCL":Bay}' is expected.

LNs identification
LNs are identified using three attributes lnClass, lnInst and prefix. When generating the
ssd file, the attribute prefix is not taken into account so if there are two or more IEDs with
the same lnClass and lnInst the validation process of the ssd file will report LN repeated
and will generate the following error:

Error: cvc-identity-constraint.4.1: Duplicate unique value

[1,MMXU,MICOM_P545_Mapped,,] declared for identity constraint
"uniqueLNodeInSubEquipment" of element "SubEquipment".

Practical example : LN1 -> lnClass = MMXU, lnInst = 1, prefix = Dif

LN1 -> lnClass = MMXU, lnInst = 1, prefix = Rms

NOTE: This case can only happen when the IED model is created from an icd file. IEDs
modelled using ATLAN library cannot produce this error. Please, check icd syntax in
case of finding this error.

ATLAN V3.4 126/227 Ed 2.0

12.4.6 Bays Highlight
Once the ssd file has been generated, primary devices and its associated Logical Nodes
can be highlighted to verify in a graphical way the association described by the ssd file.

By clicking the icon of the tool bar a list of the project bay will be displayed allowing
the user to choose the bays to highlight. Once selected the primary devices and its
associated Logical Nodes, they will be coloured as shown in the figure.

The edition of the project can only continue when this function is deactivated as advised
by the message.

12.5 CONFIGURATION OF OTHER DEVICES

ATLAN’s working environment provides specific functions for the IEC 61850 devices for
which their icd or cid file is not available. These devices can be connected to other IEC
61850 devices by defining MMS or GOOSE connections between their Logical Nodes. It
is not possible to include such information in the .scd file, as this is not available.
However, these connections will also remain documented in the system.

ATLAN includes a special function which makes possible to document this sort of
connections. Then, from the generated document, it will be possible to configure the
devices by using the proprietary configuration tools of each of them.

By selecting the “Lists of connections without scd” submenu in the “Documentation”

menu, it is generated the document referred in the previous paragraph.

ATLAN V3.4 127/227 Ed 2.0

13 LIBRARY OF DEVICES
ATLAN provides a powerful set of tools to define any type of device without practically
any limitation.

ATLAN’s libraries include devices which model all type of IEDs; connections; and Logical
Functions. The editor of objects permits to create new devices and connections, either
from scratch or from other existing objects. Anyhow, the created devices and
connections are based upon ATLAN’s generic classes and hence inherit their properties,
which are complemented with the information entered at the time of creating the element.

The elements created are stored in the library of objects in the form of a hierarchical tree
with the structure defined by the user.

The generation, edition or administration of devices is blocked when a project is opened,

due to the possible generation of errors when generic classes of the project are used
instead of ATLAN’s general library. To be able to perform the actions described in this
section, if opened, a project must be closed first.

13.1 GENERIC CLASSES

IEDs inherit their basic properties from the generic classes. ATLAN’s classes define the
basic functionality of the working environment and therefore they cannot be modified.
However, users can create other generic classes which can be applied either to the
working environment of the system or just to a project in particular.

The editable generic classes that can be user modified or extended are:

- “Voltage Levels”. Voltage levels in the substation. This information will be used
to generate the substation description file according to the IEC 61850 standard.
- “Terminal Voltage”. Voltage/Current levels at the terminals. The values
introduced in this list will be used in order to analyse the compatibility of the
terminal to be connected. It is possible to define voltage/current levels as a range
of values. The range is specified with the syntax “<Min.Value>-<Max
Value><Units>”; for instance, “10-50V” defines a terminal that can accept
voltages between 10 to 50 Volts. It is important to consider that space between
characters is not allowed. Compatibility is checked by matching string so 12v is
not compatible with 12V. It is important to check that units, multiplers and ranges
are properly written.
- “Protocols”. Communication protocols. This list is used to verify the compatibility
of the communication connections.
- ANSI codes.

The setting of new values can be carried out by selecting the “Generic Classes” submenu
within the “Library” menu.

ATLAN V3.4 128/227 Ed 2.0

Although any voltage level can be introduced, it is recommended that the subsequent
units follow the syntax of the IEC 61850 standard so that the project’s description files
can be correctly generated.

By clicking on the “Save” button, the new values are stored in the library of objects. It is
required to restart ATLAN to get new settings operative every time that they are modified.

13.1.1 Project Generic Classes

The submenu “Generic Classes of the Project” shows the classes that have been loaded
when opening the project. These classes cannot be modified.

When a new generic class is defined, it will be available to the project the next time the
project will be opened.

13.2 CREATION OF NEW DEVICES

The generation of new devices in the library of objects is a process that must be
performed from the general to the specific. That is, if required, new generic classes must
be created in first place; and then, new devices can be defined from them.
Once the generic classes required to define an IED are available, the definition process
can be initiated.

By selecting the “IED editor – New IED” submenu in the “Libraries” menu, a pop-up
window as that shown in the following window is displayed. This window is made up four
sheets, which become sequentially active as filling in the data fields in previous sheets.

ATLAN V3.4 129/227 Ed 2.0

The creation of a new class of IED is a sequential process whose four phases need to
be completed as it goes along. The next figure shows the initial data that define the new
class of IED.

- Name. It indicates the generic name of the device being created.

- Description. Free text that describes the device.
- Communication capacity. It indicates whether the device has capacity of Ethernet
communication, and therefore can constitute a local network. There are two
options:
o Ethernet Switch. Device with several Ethernet ports that interconnects
subnetworks which, in fact, form a single local network.
o Router. Device with several Ethernet ports that works in Layer 3 and it is
therefore able to interconnect local networks, which may not constitute or
be in the same LAN, being hence the VLAN’s in each of them separated.
IEDs with communication capacity, that is, with Ethernet or serial ports require
that, when they are used in a project, the MAC and IP addresses; the mask of
every port; and the gateway address are defined, as these data must be included
in the .scd file afterwards.
- Type. It indicates the internal functionality of the device.
o Simple. It applies to devices that do not have internal functions – or it is
not useful to model them as they are not relevant for the projects in which
the model of the device will be used –. For example, a traditional voltage
transformer will be modelled as a unique block (black box), and therefore
it will require this option to be selected.
o Multifunction. It applies to those IEDs that contain protection and control
functions as well as automatisms defined according to the IEEE C37.2
standard. For these devices, the protection functions are identified by
means of the codes stated in the standard and there can be established
hybrid connections that describe which physical element – circuit breaker
for instance – is controlled by a determinate function. These sub-functions

ATLAN V3.4 130/227 Ed 2.0

 behave as Logical Nodes. The functions that must be included in the
model are selected from the list. At this point, it needs to be remarked that
the model must contain all the functions that can be implemented by the
equipment being modelled. When the model is used in a project, the
functions that require to be used can be selected. Those functions will be
shown in the project and therefore they will be the functions which will be
able to be interconnected with the rest of the elements in the project.
o IEC 61850. It applies to IEDs that fulfil the IEC 61850 standard and also
for the definition of “Virtual” devices used to create IEC 61850 substation
specification projects as described in section 13.3. The functional
characteristics of IEC 61850 devices are defined in their associated .icd
file. To define this type of devices, it is just needed to associate their
corresponding .icd file indicating its path – or using the “Explore” button
to locate it. Once the file located, it must be validated by clicking on the
“Validate” button. If the file is not compliant with the semantics indicated
in the standard, the model will not be able to be created. In this case,
there exist two possibilities: create a model of type simple; or create a
multifunction model in which there will appear the logical nodes but not
the internal variables. This device will not be able to be included in the
.scd file, although its connections will be stated in the “Connections
pending to be programmed” list. From this file, it will be possible to define
such connections by using a proprietary configuration tool. In order to
create such file, it is required to click on the “Validate” button without
having selected any file previously. After this, the validating window,
where the “Create new file” button will be able to be selected, will be
displayed. In order to create this file it is necessary to identify the Logical
Nodes that require being included. When using this IED in a project it will
be possible to establish logical or hybrid connections, although such
connections will not be modelled in the .scd file. Instead, it will be
generated a list of connections which must be programmed outside
ATLAN’s environment.

It must be emphasised that the model must contain all the Logical Nodes
that the modelled device can support. When the model is used in a
project, the Logical Nodes wished to be shown can be selected. They will
be shown in the project and therefore will be able to be interconnected
with the rest of the elements of the project. The window used to create a
model allows the insertion of several instances of a same LN.
- Image. In every project, IEDs are represented by means of an image. This image
is a JPEG file that must be included either indicating its name and path or using
the “Explore” button to locate it. If a user needs to have access to rotated views,
they must be selected previously.
- Voltage level. It indicates the voltage level or levels that the IED being modelled
can be used with. It can be a fix value, normally in the case of elemental IEDs, or
selectable within the range of voltage levels of the project.

ATLAN V3.4 131/227 Ed 2.0

 - IEC 61850 functional association. By selecting this option, the IED will appear in
the substation descriptive part in the .scd file. It must be selected the functional
grouping option within the list of options shown in the dialogue box. If this function
is not filled in, the element will not be included in the descriptive part of the .scd
file.
- Application guide. It allows selecting the model’s application guide.

In order to be able to correctly form the descriptive part of the substation .scd file it is
required that the primary elements and the IEDs not being IEC 61850 have a normalised
functional association (Bay, equipment, subequipment, connectivity node, terminal, etc.),
as it is specified in IEC 61850-6 (Fig 10) (List in page 88). With regard to this point, it
must be possible to distinguish between Ethernet Switches that form “Subnetworks”, or
routers that interconnect them.

Many protections do not allow internal connections between Logical Nodes as they are
prefixed by the device’s internal design. In the case that this functionality is supported by
the IED being modelled, the “Internal connections LNs” box must be selected. When this
functionality is not supported, the connections between LN’s will not be able to be drawn.
On the opposite case, they will be able to be drawn although their addition to the
configuration of the device will depend on the device own capabilities. In the case that it
is not possible to add such connections in the configuration file, they will be included in
the list of logical connections still to be established.

Once the introduction of all the information is finished, the “Terminals” sheet becomes
active by clicking on the “Next” button.

ATLAN V3.4 132/227 Ed 2.0

Terminals can be defined one by one, or by groups when all of them are of the same
type.

In order to introduce a group of 8 entries, their characteristics must be selected and also
the number of instances needs to be incremented to 8. Automatically, 8 terminals will be
generated with the same name, followed by an ordinal from 1 to 8.

The terminals generated are shown in the lower list. To eliminate a terminal incorrectly
introduced, just select it and click on the “Delete” button.

It is possible that the manufacturer of an IED provides a XML file that describes the
physical terminals. In this case, by clicking on the “Import” button the terminals described
in the XML file will be added to list of terminals. Users can accept the list or introduce
modifications.

For IEDs that are modelled according to images or drawings in which the connections
must be established in specific points, it is necessary to select the “Forced physical
connection” option. In this case, the terminal number will appear in the list of assigned
terminals. The terminals will need to be introduced in such a way that the terminal
number matches with the position of the image in which the corresponding signal must
be connected. See section 13.2.1.

Certain devices, especially those of electrical type as bars, may have not in fact particular
connection terminals or their modelling not being relevant for the engineering of the
project. For this reason, they can be modelled with the “Limitless terminals” characteristic
by clicking on the corresponding box. In this case, there can be connected as many
devices as it is required as ATLAN does not limit the number of connections – always
that all of them correspond to one same type of terminal –.

The terminals included in the list of assigned terminals can be sorted by using the up
and down keys. The order in the list determines the order in which there will appear the
terminals in the documentation of the device.

By placing the cursor over a terminal, an info box shows all its properties.

ATLAN V3.4 133/227 Ed 2.0

If there is available a XML file describing the terminals of the device to be modelled, it is
possible to download such information by clicking on the “Load terminals (XML)” button.

By activating this function, it gets displayed an explore window that allows selecting the
terminals description XML file. Before initiating the download of the information, it is
performed an automatic verification of the format and the contents of the file. If the
verification results to be correct, the list of assigned terminals becomes automatically
updated. The use of this facility is not an impediment to being able to add or delete
terminals in the list. Also, to be able of implementing this function, there must not be
assigned terminals.

ATLAN includes also the functionality of generating; editing and loading templates of
terminals in .xls format.

Options “Define Terminals Template” and “Edit Terminals Template” within submenu
“IED Editor” in the “Libraries” main menu allow generating and editing terminals
templates in .xls format, respectively.

ATLAN V3.4 134/227 Ed 2.0

When the “Define Terminals Template” option is selected, it becomes automatically
opened a .xls file with a blank terminals template.

When the “Edit Terminals Template” option is selected, it gets displayed a window as
that shown next, where it just needs to be selected the desired template and then the
“Accept” button be clicked in order to get automatically opened the .xls file that needs to
be edited.

Note: Annex E contains a ‘Quick guide for the use of the Terminals Template’.

If it already exists a .xls file with a description of the terminals of the IED being modelled,
it also is possible to load such information just by clicking on the “Load terminals (XLS)”
button.

When this function is activated, it is displayed the following window, where it can be
selected any of the templates available in the “Select the Template required” area; as
well as it is possible to import another existing template by clicking on button “Explore”.

ATLAN V3.4 135/227 Ed 2.0

If the “Accept” button is pressed without having selected previously any template on the
previous window, the following error message will be displayed.

Also, if despite having selected a template any error occurs during the loading process,
it will be displayed an error message as that shown next, with a description of the errors
that need to be corrected.

If after having selected a terminals template and pressed the “Accept” button the loading
process takes place correctly, the terminals loaded will be shown in the “Assigned
terminals” area, as it is illustrated next.

ATLAN V3.4 136/227 Ed 2.0

Similarly as when loading an .xml terminals description file, the functionality of loading
terminals by means of an existing terminals .xls template does not stop users from being
able to add or delete terminals in the list. This functionality can only be used before any
terminal be manually defined.

Once the “Next” button pressed, the introduced data will be saved and the “Logical
Functions” window will be activated. If a user detects that any parameter from the
previous window has not been configured, by clicking on the “Previous” button it is
possible to go back to the previous window without losing any of the data introduced so
far.

The Logical Functions window permits to define the capabilities that the IED has for the
implementation of Logical Functions; that is, whether the IED can carry out this type of
functions and it has any limitation – functional as well as regarding the size and the
complexity of the function to be implemented –.

ATLAN V3.4 137/227 Ed 2.0

In first place, it must be defined whether the IED supports Logical Functions. In the
affirmative case, it must be indicated whether it exists any sort of limitation, either in the
number of logical elements that can be mapped or in the type of logical element. The
“Maximum Logical element number” box being empty indicates unlimited capacity.

Once the “Next” button is pressed, the introduced data are saved and it becomes
activated the “Documentation” window.

The “Documentation” window allows generating an index card with the data of the new
element in the library.

Finally, when clicking on the “Save” button the system carries out a verifications of the
whole set of data in order to ensure the integrity of the new class generated; and a pop-

ATLAN V3.4 138/227 Ed 2.0

up window as that shown next, which allows storing in the library of objects the created
element, is displayed.

The “Remove folder” button allows deleting any of the folders. Folders can only be
deleted when they are empty.
When saving a new IED, empty folders will be automatically deleted.

13.2.1 Rules for the creation of images associated to IEDS

The images used to represent IEDs in ATLAN graphic environment are graphical files
that can be obtained from drawings, icons, photos, scanning images or any other
method. They can be produced using any drawing or editing tool. In order to achieve a
correct execution, from the esthetical point of view – including the orthogonality of the
connections and the relative size of the different components –, of the graphical
representation of the projects, it is very important that the models of the IEDs have
associated images that follow a set of specific rules in such a way that all the alignments
and the orthogonality of the connections result to be perfect.

In order to achieve a compromise between the quality of the graphs and the amount of
memory used, it is recommended that the size of the images be not above 100x100
pixels. 70x70 pixels is the recommended size. In fact, there is not real limitation in the
size, although large size objects will generate drawings with higher order of detail that
will need much more memory, possibly slowing down the application. It must also be
noted that the coexistence in the same project of elements with very diverse sizes makes
that it is not possible to visualise all their details in a same view. Consequently, it is
recommended that all the objects have associated drawings with similar sizes.

From a graphical point of view, the size of an object determines its number of different
points of connection. Exactly, the connection points are placed at a distance of 8 pixels
on each of the sides of the object. The number of points of connection determines the
number of connections that can be located in different places along the contour of the
object. There is not limitation regarding the placement of two different connections in the
same connection point, although this might make that the drawing does not reflect clearly
the functionality of the project. In objects with free connections, the point of connection
is not related to the terminal being used. For this reason, two connections located in the
same connection point will not be connected to the same terminal although the graphical
appearance indicates so, unless both of them constitute a multiple-connection with
several origins or several destinations.

ATLAN V3.4 139/227 Ed 2.0

There can be defined objects with fix and forced connection points by selecting the
“Forced physical connection” option. In this case, the arrangement of the connection
points follows the rule shown in the figure, where the connection points are separated by
8 pixels. This type of configuration applies when the image of the object represents a
block diagram or an internal diagram of the device being modelled. In this case, the
connection lines of the object’s internal diagram must match exactly with the pixel
assigned to the point of connection so that continuity can be in this way appreciated
between the external connection and the internal diagram. Just as it has been described
before, the association of each terminal to its point of connection is fixed in such a way
that the object’s internal diagram will pass to form part of the drawing of the project,
without introducing any discontinuity.

13.3 Generic devices definition

ATLAN working environment can be used to create substation specification projects.
When the specification is a generic one, the models used to define the project should
also represent generic functionalities instead of models representing existing off-the-
shelf equipment.

ATLAN libraries allow any type of device to be defined. Connection terminal may
represent whether real connection point or the specification of signal generated or
processed by the device.

In the IEC 61850 environment, it is possible to model “Virtual” devices for specification
purpose only. These models may contain from one to a limitless number of LNs. All the
device models must have at least one connection terminal. It is advisable to include at
least a communication port so that communication links such as GOOSE or SV signals
might be defined for specification purposes only.

13.4 Virtual Devices definition

ATLAN working environment allows substation specification to be created from virtual
elements representing the Logical Nodes defined by the standard IEC 61850.

An object library not included in the basic license is available containing the LNs defined
in the standard and its extensions. ATLAN basic license includes some specific functions
to define virtual models.

Complete functionality to produce a specification from virtual models is provided in the

license ATLAN-SPEC.

ATLAN V3.4 140/227 Ed 2.0

13.5 DEVICES LIBRARY MANAGEMENT
The library of objects can be maintained by means of submenus “Edit” and “Delete” –
IEDs or Connections –.

By selecting the “Edit IED” submenu, the following pop-up window is displayed, where
one of the IEDs in the library of objects can be selected.

By selecting the IED that requires to be edited and clicking on the “Open” button, a pop-
up window similar to that shown in section 13.2 will be displayed, with the data of the
IED being edited. Users will be able to modify those data that are not correct, and also
will be able to use that IED to create a similar one by just modifying those data that make
them different.
This process is carried out as described in section 13.2. The IED that has been modified
cannot be saved with the same name in the same folder. That is, the modified IED must
be saved either with another name, or with the same name in another folder.

By selecting the “Modify connection” submenu, a pop-up window similar to the former
one is displayed, in which it is shown the library of connections. By selecting the
connection that requires to be edited and clicking on the “Open” button, a pop-up window
similar to that shown in section 14.1 is displayed showing the data of the selected
connection. Users will be able to modify those data that are not correct, and also will be
able to use that connection to create a similar one by just modifying those data that make
them different.

The process of saving in the library the connection modified is similar to that described
for the case of the IEDs.

It is possible to delete elements from the library of objects, either IEDs or connections,
by selecting the corresponding submenu, after which it is displayed a pop-up window
similar to that shown in the following figure.

ATLAN V3.4 141/227 Ed 2.0

To delete an element in the library, such element must be selected first and then the
“Delete” button pressed. The use of this function is restricted to the Administrator, and
for this reason it is required to know the Administrator key to undertake the deletion.

The “Move” function allows users to move an object from one folder to another one. By
means of this function, the objects that have been validated in the “User” zone can be
moved to the “System” zone.

The “Administrate IED” submenu allows users to maintain the structure and contents of
the library of IEDs. Selecting the “Administrate IED” submenu, the following pop-up
window is displayed.

The library of devices is split in two parts: the user part identified by the root folder “User”;
and the system part identified by the root folder “System”.

New device models can only be saved in the user part.

The Administrator can move the modelled data from
the user part to the system part when he considers
that they are proved enough and therefore they
became normalised in the company. A device can be
moved by selecting it and clicking on “Move”.
Previously, it must have been introduced the
Administrator key.

Any device can be deleted from the library. This

operation permanently deletes the device. To archive
or backup devices, use export functionality as
described in section 16.3.

13.6 DEVICES LIBRARY DOCUMENTATION

The “Library documentation – Devices documentation” submenu, allows the generation
of a complete documentation of all the objects included in the library.

ATLAN V3.4 142/227 Ed 2.0

By selecting this menu, it is possible to document the devices; connections; dictionaries
of names; and alias.

When selecting the documentation of devices the following pop-up window is displayed.
The documentation of the selected elements will be generated. It is possible to generate
the documentation of the whole library by selecting the
root folder, as well as it is possible to generated the
documentation of spare devices; of part of the library by
selecting a group (Primary elements, for example); or of
a single element.

By selecting the “Enclose application guides” option, the

documentation generated will include the application
guide of each device always that at the time of creating
the model an application guide file has been associated.

By clicking on the “Create PDF” button, it is generated

a pdf file that contains all the data of the objects
selected.

ATLAN V3.4 143/227 Ed 2.0

14 CONNECTIONS LIBRARY

14.1 NEW CONNECTIONS CREATION

Connections between IEDs are carried out on the basis of nine types of basic connectors,
which are grouped in three categories: physical, logical and hybrid. For each category,
point-to-point as well as multisource and multidestination connections can be
established.

Based on these generic classes of connectors, ATLAN’s specific connectors can be

defined. Such connectors only differ in their type of line, width and colour so that it results
easier to identify the functionality of every signal in the project and in the generated
documentation.

By selecting the “New connection” submenu, the following pop-up window is displayed,
allowing users to create new connections.

The “Functional association” area at the bottom of the window applies only when working
in an IEC 61850 environment. By means of the “It must appear in SCD file” option, it is
possible to define whether a new connection will participate in the functional description
of the substation included in the .scd file.

By clicking on button “Save”, it is displayed a pop-up window as that shown next, which
allows users to save a created element in the library of objects.

ATLAN V3.4 144/227 Ed 2.0

The folder where the new connection requires to be saved must be selected or, if the
new connection belongs to a new type of connections, a new folder for that new type
must be first created by means of the “Create folder” button.

14.2 CONNECTIONS LIBRARY MANAGEMENT

The management of the library of connections follows the same procedure as that for
the management of the library of devices.

14.3 CONNECTIONS LIBRARY DOCUMENTATION

The procedure to generate a complete documentation of the library of connections is
similar to the counterpart procedure described in section 13.6 for the library of devices.
Unlike the library of devices, connections are documented in a single document that
comprises all the connections in the library.

ATLAN V3.4 145/227 Ed 2.0

15 NAMES AND SEMANTIC RULES
ATLAN’s working environment includes the capability of – as one of its functionalities –
having several sets of names for the devices and their internal variables.

In addition, it is possible to define the semantic rules used for automatic name
generation. By this means, users can easily have access to documentation containing
familiar nomenclature, which at the same time maintains IEC 61850 specification naming
structure.

This functionality allows, in addition, carrying out copy/paste commands, with automatic
re-naming of devices and variables.

15.1 STRUCTURE AND FORMAT OF NAMES

ATLAN’s objects external names can be created from system users’ particular criteria.

Names are formed from composed name classes, which define the rules for automatic
naming creation; the format; and the contents of each of the name fields.

An object final name is made of by one or several – (n) – basic fields. These, at the same
time, are more elementary classes which, as for the previous case, define the rules for
automatically creating each of the fields, and its format.

The basic fields of the names are thus defined from elementary classes. The latter can
be fixed, as well as user defined.

15.1.1 Elementary classes

Elementary classes represent the atomic elements, from which more complex classes
are obtained. ATLAN works with the following elementary classes:

- Integer. Integer number that represents a constant value. Range 0..32,000. (*)
- Free integer. Field allowing manual introduction of an integer number.
- Numeric incremental. Integer that can be modified by an incremental or
decremental operator. Range 0..32,000
- String. Series of fixed characters. Range 1 to 256 characters. (*)
- String incremental. String whose last character can be modified by an
incremental or decremental operator. (*)
- Free string. Field that allows manual introduction of a string.
- Referenced string (pointer). The string assigned to this class is selected from a
list of names of the project, such as:
o <Project name>
o <Project views’ name>
o <User views’ name>
- Fields separator. Character used for field separation. It corresponds to a string,
used for delimiting fields in a visual manner. (*)
- Incremental/decremental operator. It increments or decrements the preceding
integer or string, always that they can be incremented/decremented.

(*) Indicated elementary classes need to be user defined. The rest are by default system
defined.

ATLAN V3.4 146/227 Ed 2.0

Several types of separators can be defined.

Incremental operators are system-reserved characters, and therefore cannot be user

modified.

Sub-menu “Edit elementary classes”, at menu “Libraries”, is used to define elementary

classes.

Navigation among classes’ screens is possible by means of buttons ‘<<’ ‘>>’.

15.1.2 Basic fields’ classes

They constitute each of the fields of ATLAN’s objects names.

These classes can be defined from elementary classes by selecting:

- The number of basic elements.
- The type of basic element of each of the components, which can be fixed fields,
variable fields, incremental operators; or any of the elementary classes available
at the library.

ATLAN V3.4 147/227 Ed 2.0

A basic field of type “Combo” will also be able to be defined. A Combo has a drop-down
list of types. This facility allows assigning different names to an IED, depending on its
position in the design. Contents of the drop-down list can be specified when defining a
Combo.

Sub-menu “Edit basic classes”, at menu “Libraries”, is used to define basic classes.

15.1.3 Composed names’ classes

These classes are used to define the names of ATLAN objects.

ATLAN’s objects names are formed by one or several basic fields. Next section
describes how different formats of composed names – for each object type – can be
defined.

Sub-menu “Edit names dictionary”, at menu “Libraries”, is used to define composed

names.

ATLAN V3.4 148/227 Ed 2.0

15.2 STRUCTURE AND CONFIGURATION OF THE DICTIONARY
In ATLAN, there are two dictionaries: that of the library of classes; and that of the IEC
61850 Data alias.

The dictionary of classes stores the rules used to form the names. It also establishes the
relations among each of the object classes included at ATLAN’s library of IEDs &
connections, and the classes of composed names. This is carried out in such a way that
a semantic rule corresponds to each of the object classes, so that a unique name can
be obtained for each of their instances. I.e., the dictionary of classes sets up which rule
to be used in order to name a project new element, whether an IED or a connection.

Rules to create names can be modified at any time. Modifying a rule does not have any
effect on the name of IEDs or connections already instantiated in a project. It will only
apply to elements added after the modification of the rule(s).

In addition, ATLAN includes the functionality – developed for copy/paste instances of

existing elements (IEDs, connections, etcetera) within the design of a project – of letting
the user to choose which fields of a main rule will be used by the system to automate the
name generation when copying an element. This meaning that, if for example there is an
incremental numeric within the rule and that is the chosen field, the numeric will be
automatically incremented by the system, and external help will not be required in order
to create the new name. If, for example, the user chose a field of type constant – within
the same main rule –, it is clear that the system would not be able to automatically assign
a new name to the element copied into the project. In that case, the system would warn
the user not to use such a sort of field for the automatic naming purpose.

ATLAN V3.4 149/227 Ed 2.0

By clicking on button “Generate RC” at previous window, the new window shown below
– related to “Copying Rules” – is opened, where users can define the field of the name
that the system will use to automate the copying process.

15.2.1 Generic copying rules

It is also possible to define a copying rule to be applied generically. Such a rule will apply
to any copied element which does not have associated any customised copying rule.
The generic rule will add a field of type separator and a second field of type incremental,
at the end of the name structure of the original element.

ATLAN V3.4 150/227 Ed 2.0

Submenu “Copying rules” is used to access the window where the user can select one
of the separators defined at the library and one of the incremental operators, as shown
in next figure.

By this means, the separator and the incremental selected will be added to the name of
the original object, any time that an IED or a connection are copied within a project.

15.3 AUTOMATIC GENERATION OF NAMES

15.3.1 Names of IEDs

Any IED generic Class can have associated a composed name class. That is, any of the
elements at the library of IEDs can have associated a rule for the composition of its
name.

If the automatic naming functionality is activated – which is achieved by clicking on icon

, any time that an IED is instantiated its name will be generated automatically, as long
as the associated rule allows it. I.e., always that, if the system needs to complete some
of the name fields, the name structure does not have any field requiring manual or semi-
automatic intervention. On the opposite case, the system will open the next window,
where the required information can be introduced.

ATLAN V3.4 151/227 Ed 2.0

Once the data at the active fields introduced, the system will generate the name of the
IED, and the IED’s instantiation window will be opened.

When generating names using predefined rules, automate copy/paste functions will be
possible always that copy rules have been previously assigned.

15.3.2 Names of connections

As for the previous case, any generic Class of connection can be associated to a
composed name class. Although these names may not be associated to external names
in the dictionary, it is necessary to activate this functionality so that the copy/paste
functions yield unique and syntactically correct names.

15.4 NAMES OF INTERNAL VARIABLES IEC 61850

LNs internal variables follow the syntax defined at IEC 61850, and are stored with all the
sequence of names defined at the standard – from the IED name to the DO or DataSet
–. Therefore, in order to get a correct copy/paste function, it is required that the IED
names are generated by means of one or several name generation rules. This is because
an IED needs to be renamed when instantiated by using the copy/paste function, which
means that not only the name should change automatically, but also all its internal
variables.

A specific dictionary will be used to perform the translation from

AccessPoint/Server/LD/LN/DO to a free name. Such an assignment will be carried out
for each object model having a valid icd file. In this way, instead of presenting the variable
in its original format according to the standard – “<IEDname>/AccessPoint/Server/LN
Prot/LN PDIS1/ DO Str” –, it will be presented “Start 21”.

ATLAN V3.4 152/227 Ed 2.0

Not all the internal variables of the icd file will necessarily need a name assignment. The
DO’s not having a name assigned will be presented with IEC 61850’s nomenclature.

When setting a name definition at object library level, the new definition will apply to all
the projects which subsequently use that object.

The use of this function can be set on and off by clicking on icon at the tools bar.

15.4.1 Configuration
A different window for each class type will be used to configure the classes defined in
previous sections, as shown before.

Once the composed names’ classes defined, the objects of the library will be associated
to one of the classes previously defined. Such an association will be carried out in three
stages: the first part for the classes of IEDs; the following for the connections; and the
third sort of association, for the internal variables of the LNs. The latter only allows
defining a unique criterion for all the variables of the IEDs 61850. Once such an
association defined, each time that a MMS or a GOOSE is established – assuming of
course that all the variables that take part in the connection have been defined – it will
be possible to work with the defined names instead of with the internal variables.

15.5 OBJECTS AUTOMATIC NAMING FUNCTION

Automatic naming of objects can be activated by means of an icon placed at the function
icons’ bar. Once activated, ATLAN creates automatically the names of the objects, when
instantiating an IED or creating a new connection. Names created automatically cannot
be modified.

The following window is displayed, when the rules for names generation include any field
that needs manual introduction of names or numbers.

ATLAN V3.4 153/227 Ed 2.0

Names of IEDs generated by means of a semantic rule can only be edited if any of their
fields has been generated manually. In such a case, the following window is displayed.

In this case, only those fields allowing manual introduction will be enabled.

15.6 IMPORT AND EXPORT OF NAME RULES

It is possible to import and/or export the rules used for name creation; and the dictionaries
of rules assignment – in the same way as for the rest of components of ATLAN’s libraries
–. See sections 16.3 and 16.4 in next chapter.

Any import function must be implemented before starting the design process of a project,
so that every time a new device is defined, a name can automatically be associated to
it.

15.7 DICTIONARY DOCUMENTATION

Two types of pdf documents will be able to be obtained:

- List with the contents of the dictionary.

- List with the rules of names creation (name classes).

ATLAN V3.4 154/227 Ed 2.0

16 INFORMATION IMPORT AND EXPORT
Data exchange between ATLAN and some other related applications – such as
documental databases, proprietary configuration tools, and etcetera – is carried out by
means of a set of specific functions, which allow the control of the information
exchanged, and also guarantee project tracking and integrity.

16.1 EXPORT OF FILES

By means of ATLAN’s export function, project files can be extracted and copied into
another folders or applications. When selecting submenu “Export files” at menu
“Communication”, all the export files associated to the current active project can be seen
in a window as shown in next figure.

On the left hand side, all the documents and documentation files of a project are
classified by types.

Users can choose one, several or all files to be transmitted. Also the transmission mode,
which can be:

1. Copy to folders at another computer on the same domain.

2. FTP/SFTP transfer to another computer data repository with IP connectivity.

In order to either select or deselect all the files, there are two icons on the top part of the
left window:

ATLAN V3.4 155/227 Ed 2.0

 Selects all files
Deselects all files
Icon is used for file transmission.
By clicking on the system folders label, the path where the selected files will be exported
– within the same computer or to another one on the domain – can be selected:

and a window to enter the path will be displayed:

Navigation within the directory, either to upper or lower folder levels, it is possible by
means of the icons on the tools bar, or by double-clicking on the corresponding folder:

Icons on the tools bar give access to the following specific functions:

Discharge selection
Refresh present directory
Rename selection
Create new directory
Change directory
Remove selection
Go up one level

In order to make use of the FTP transfer facility, its function parameters need to be
configured. This can be done by selecting option “Connect to FTP server” at main menu
“File”, which will give access to the following configuration window:

ATLAN V3.4 156/227 Ed 2.0

Fields at previous window must be filled in with the parameters provided by the FTP
server administrator.

Once the connection established, the selected files can be exported by double-clicking
on the send icon .

In order to make a SFTP connection, the process would be the same, although it would
require entering additional parameters related to this type of connection:

The active server can be disconnected by selecting “Disconnect server” at menu “File”.

At menu “File”, there is a list with the last servers’ connections. By clicking on any of their
labels and introducing the required parameters, it is an easy and quick way of accessing
to them. For example, if a connection to a FTP server has been previously established,
the system will only request the password, as the rest of the parameters will have been
stored.

ATLAN V3.4 157/227 Ed 2.0

Menu “Options” – together with its submenus – can be used to make some adjustments
and also to set some of the parameters of the FTP/SFTP connections.

From menu “Bookmarks”, most used connections can be administrated. For example, a
frequently used FTP connection can be created, its parameters set, and then saved, in
order to easily have access to it. Old connections, which are not used anymore, can also
be deleted:

16.1.1 Export of XML Files

Once a project has been signed by the Author, Reviewer and Approver, it is possible to
carry out an export to a XML file with structure and format compatible with “Electrical
Designer”.

To do so, after getting the project signed, it is required to activate the “Communication
 Detail Engineering  Export project – Detail Engineering” submenu, by means of
which the XML description file of the project is automatically generated.

Once the process finished, it will be generated a XML file named “<project
name>EngDet”, which will be saved in the “Signed” folder of the corresponding project
version.

16.2 IMPORT OF FILES

This allows importing, into a specific folder, a previously exported project. Then the
project file should be uncompressed, as it would be done when recovering a backup
copy, although with the additional facility of being able to do it from a FTP/SFTP server
that could be used as centraliser of the copies of a project.

Once uncompressed, ATLAN can open and work with that project, as for any other
project.

ATLAN V3.4 158/227 Ed 2.0

The process is similar to that described to export files, although that in this case only one
project file can be imported at a time.

16.3 EXPORT OF LIBRARIES

Libraries can be exchanged among ATLAN users by means of export and import
processes.

When a library – of objects as well as of FL’s – is exported, it is created an intermediate

file, which contains the library description in XML format and also the documents
associated to that library – such as components documentation in pdf format, or
simulation results, in the case of FL’s –. Such a file is stored in a specific file exchange
folder, so that other users can access to it.

ATLAN V3.4 159/227 Ed 2.0

It is also possible to export only part of a library. That is, only one element, a group of
elements hierarchically related – for example, all the existing protection models –, or
several related or independent groups.

ATLAN V3.4 160/227 Ed 2.0

ATLAN V3.4 161/227 Ed 2.0
In all those cases, a file name, which identifies the exported library, needs to be
introduced.

16.4 IMPORT OF LIBRARIES

The import process starts from the library description file. ATLAN interprets this file, and
once its contents are validated, its components are added to the library of the licence
that carries out the imports. In case of detecting names duplicates, the system informs
the user – who must then choose whether to add the new element, or to keep the existing
one –.

ATLAN V3.4 162/227 Ed 2.0

Once a file selected, clicking on the “Import” button gives access to the following window
– which classifies the elements of a library in different types –.

The import process starts after selecting the desired elements in each group, and clicking
on the “Import” button.

A library can also be imported by selecting the corresponding submenu. In this case, the
following window is displayed – where the differences between the components of the
library to be imported and the components of the local library are shown –.

It is also possible to select the group of elements to be imported.

ATLAN V3.4 163/227 Ed 2.0

ATLAN V3.4 164/227 Ed 2.0
17 PROJECT ADMINISTRATION
Functions related to project administration can be found grouped in submenu “Tools –
Project Backup”. The following options will be shown when selecting this submenu:

- Archive
- Backup
- Recover

In order to exchange projects between remote users it is required to use the functions
related to files exchange, described in chapter 16.

17.1 PROJECT ARCHIVE

This function is used to store a project at memory units within the user’s network. The
project and all its associated documents are stored in a data repository created by the
user, when choosing this function. All the files associated to the project are then
automatically deleted from the user’s computer.

17.2 BACKUP
The backup function allows storing a project as for the previous case, except that now
project files will not be deleted from the user’s computer. Both projects – the filed in the
data repository and the one kept by the user – remain associated in such a way that
automatic and coherent information retrieval can be carried out afterwards.

The backup copy contains the Author, date and comments.

17.3 BACKUP RECOVERING

This function allows recovering a filed project; and also restoring a project from a
previous backup copy.

First, the existing backup copy to be restored must be selected.

When clicking on button “Recover”, it is displayed a window which shows the differences
between the current project and the project to be recovered. By this means, the user can
decide whether to retrieve a project backup or not.

ATLAN V3.4 165/227 Ed 2.0

17.4 ARCHIVED PROJECT RECOVERING
This function can only be executed from the administrator menu. When selecting
submenu “Administrator – Backup – Recover project”, it is displayed a window which
shows all previously archived projects, which are hence subject to be recovered.

By clicking on button “Recover”, an explorer window is displayed in order to indicate the

folder in which the project should be stored.

ATLAN V3.4 166/227 Ed 2.0

18 ATLAN’s ADMINISTRATION AND CONFIGURATION FUNCTIONS
ATLAN’s administration functions are allocated at menu “Admin”. This menu is only
activated if ATLAN is initiated in administrator mode. The admin password requested by
the initial window is “ATLAN61850”.

18.1 CONFIGURATION OF ATLAN

ATLAN must be configured when it is
initiated for the first time. Also, its
configuration needs to be updated anytime
that the applications associated to ATLAN –
such as the pdf files reader, java’s executing
environment, the path directory for file
storing, or the system default logo path – are
modified. This can be done by selecting the
“Configure tool” submenu in the “Admin”
menu, after which it is displayed the
following window.

The selected logo will apply to the template data box used by default. User defined data
boxes must include their own logo – which can only be changed by editing the template
data box –.

A tooltip with a brief explanation of the meaning for each of the variables is displayed by
placing the mouse cursor on any of the variables’ labels.

The configurable variables are:

- Logo: Image used by default when generating documentation and also in the
templates.
- Main path: Path accessed by default either when opening or saving a project.
- Java-Home: Path where JDK is installed. JDK is required for project and
documents signature. The complete path down to file/bin must be included. The
path by default is C:\Program files\Java\jdk1.6.0_12\bin
- XML viewer: If XML files visualisation software is available, ATLAN users can
visualise XML files as cid or scd files. Windows Internet Explorer is suggested by
default: C:\Program files\Internet Explorer\iexplore.exe
- Adobe: The PDF files visualisation program available must be indicated –
whether it is the free version or the extended version of Acrobat Reader –.
- Identification of created elements in change control documentation.
- Identification of deleted elements in change control documentation.

18.2 DELETION OF CORRUPTED IEDs

In case of IED file corruption for any reason – hence its utilisation being impossible –,
the system Administrator can delete the corrupted files from the library by means of the
following window, which is displayed by accessing submenu “Delete erroneous IEDs”.

ATLAN V3.4 167/227 Ed 2.0

18.3 CERTIFICATES CREATION
User certificates are required to create the electronic signature of a project, and of all its
associated documents. Certificates must be
generated or linked when a new project is
created. If for any reason such certificates
have not been previously generated or are not
available, the system administrator can
generate them again by means of submenu
“Certificates creation”. By selecting this
submenu, the following window is displayed.
Note that its functionality is exactly the same
as described in section 5.1, at chapter 5.

18.4 PROJECT BACKUP RECOVERING

When saving a completed project by means of function “Archive”, it is stored at the
selected software repository, and deleted permanently from the computer. If for any
reason it should be necessary to recover either all or part of the information of a project,
submenu “Recover Project” at menu “Admin” must be used. The following window is then
displayed, showing all the saved projects.

By selecting one of the projects and clicking on “Recover”, an Explorer window will be
opened in order to select the location where the recovered project will be installed.

ATLAN V3.4 168/227 Ed 2.0

18.5 LANGUAGE SELECTION
ATLAN includes also the possibility of language selection. The present version of the
tool has only Spanish and English languages available. When changing the language,
ATLAN needs re-initialization in order to get the language change applied.

Certain notice messages generated by the operating system are always shown in the
system’s language.

18.6 PREFERENCES
Certain functioning parameters, such as the format and the appearance of the
documents; the shape and the colour of the connections; etcetera; can be modified at
ATLAN by means of submenu “Preferences”.

This submenu is available for all ATLAN users.

Menu “Edition” can be used to configure the type and the size of the blocks of text; and
also the grid squared pattern which determines the resolution available to place objects
(IEDs, connections, etc.) within a drawing.

It is recommended not to activate grids with squared patterns lower than 10 points, as it
would require high amounts of memory and then ATLAN’s operation would slow down.
Menu “Documentation” can be used to create documentation templates.

A name and a series of characteristics must be

associated to a template. Afterwards, a new
template is stored in the system by clicking on
“Save”. It is also possible to modify existing
templates by selecting one of them from the drop-
down list.

Menu “Connections” can be used to modify the

appearance of the connections at the library.

By means of this utility, the shape and the colour

of the system’s basic connections can be
modified. It does not have any effect on the
connections defined by users, when new library connections are created.

ATLAN V3.4 169/227 Ed 2.0

Modifications of system connections appearance will only affect the project in which they
are carried out, whereas library defined connections are available for all projects.

18.7 IEC 61850 FILE VALIDATION

Any scl file can be validated using the submenu “Validate 6850 files” even though this
file is not used in any project or model.

By selecting this function a window is opened allowing browsing the file to be validated.
Once the file is selected, the validation can be carried out against any of the three
versions of the standard.

The result is shown in same way and format as per other validation functions.

ATLAN V3.4 170/227 Ed 2.0

19 TEMPLATE DATA BOX CREATION
ATLAN’s working environment includes a tool which allows new templates to be defined.
By this means, a different template format can be associated to each project; and also
drawings can be generated with several – even user defined – template formats, within
the same project.

By clicking on icon at the tools bar, the template creation environment is opened.
Inside this environment, the following window is used to define the general parameters
of a new template:

- Document format within which the template will be framed (I.e., A4 Horizontal,
A3 Horizontal, etcetera)
- Personalisation of template labels and contents
- Initial number of rows and columns
- Template size

By clicking on “Accept”, data are stored and a template with the number of rows and
columns indicated is created.

The graph environment has a set of tools which allows the graphical edition of a template.
A description of those basic tools is presented in next sections.

Templates size is expressed in pixels. There are three different template models
available. These are combined with the several paper sizes as follows:
- A4 Horizontal: it is used for listings of connections and devices; also for drawings
with that size and orientation. Its size is 842 x 80 pixels.
- A4 Vertical: it is used for drawings with that size and orientation. Its size is 595 x
154 pixels.
- Letter Horizontal: it is used for listings of connections and devices; also for
drawings with that size and orientation. Its size is 792 x 74 pixels.
- Letter Vertical: it is used for drawings with that size and orientation. Its size is 612
x 154 pixels.
- General: it is used for other sizes of drawings (i.e., A3, A2, A1, A0 and Tabloid,
horizontal or vertical). Its size is 550 x 250 pixels.

ATLAN V3.4 171/227 Ed 2.0

19.1 TRACING OF SEPARATION LINES
By clicking on icon , new separation horizontal or vertical lines can be defined.

A line is drawn by pressing the mouse right button and dragging the mouse from the
initial to the final point. Separation lines are always orthogonal and are automatically
delimited within the template frame.
If when tracing a line it crosses another line, and the distance between the end of the
drown line and the existing one is less than 5 pixels, the line will be terminated at the
existing one.

Separation lines not beginning and ending on the template frame must be traced from
the exact initial and final points. By clicking on icon , the line tracing using coordinates
tool is activated, as shown in the following window.

As lines are always orthogonal, this tool only allows to define increments for one of the
coordinates – either x or y –. The example shown above will draw a horizontal line
between points (0,100) and (200,100).

New lines are shown in black colour.

Position boxes indicate the cursor position in pixels.

The conversion to real measurements depends on the chosen paper size and margins.
For example, a template of type A4 Horizontal will be created with 842 x 80 pixels. The
template will be afterwards adapted to the page size and margins. If an A4 stencil has
been generated with a margin of 15 mm in all its sides, and if the page size is 297 x 210
mm, the template size will be 297-15-15 = 267 mm.

In this case, the equivalence between pixels and mm is of 267 to 842. Therefore, the
measurement of each pixel will be 0.3171 mm.

The generic formula which converts pixels into millimetres is:

Page size (mm) - right margin (mm) - left margin (mm)

The page size corresponds to 842 pixels in Horizontal and to 595 pixels in Vertical. The
template proportions are kept regardless of its size.

Templates within page formats A3 Vertical and larger – as they do not fit within the page
width – always keep its original proportions of 550 x 250 pixels, regardless of the
margins. The exact unit conversion is 2.8357 pixels/mm. Thus, 550 pixels correspond
to 193.95 mm.

ATLAN V3.4 172/227 Ed 2.0

By clicking on icon , the function which allows deleting any previously created
separation line is activated. A line will be automatically deleted by clicking on it, when
the delete function is active.

A new separation line can also be automatically generated using the cursor. By pressing
buttons “CTRL – A” simultaneously, the cursor colour will change from green to yellow
indicating that the system has taken the cursor position as the initial position of the new
separation line. Then, by moving the cursor to the desired final position and afterwards
pressing buttons “CTRL – A” simultaneously, the new line will be automatically drawn
from the initial to the final position.

19.2 TEXT AND IMAGE DEFINITION

Once the template internal divisions have been completed, the contents within each of
the boxes must be defined. To use specific texts, or to insert images or new logos, it is
required to activate the submenu “Add Labels” at menu “Edit” in the template definition
environment. By means of the following window, it will be possible to introduce new texts;
referenced values; or images.

ATLAN V3.4 173/227 Ed 2.0

Note: the functionality ‘Insert Background image’ allows inserting images even when their
size is larger than recommended.

19.3 TEXT AND IMAGE INSERTION

Three insertion options – as shown at the bottom of the following figure – can be
accessed when activating the text insertion tool by clicking on icon .

ATLAN V3.4 174/227 Ed 2.0

 - Select option “Labels Position” to insert a fixed text. Then, by opening the
associated list in the active box, choose the text type to be inserted and click on
the exact position of the corresponding box, where the text should start from. Text
size and colour can be modified by means of the boxes placed on the right hand
side.

- Select option “Values Position” to insert a referred value. Then, by opening the
associated list in the active box, choose the value type to be inserted. Click on
the exact position of the corresponding box, where the value should be placed.
The value identification will be shown in the template and, at the moment of
signing a document which makes use of this template, the system will request
the user to introduce the value or the text that should be included in the data box
associated. For more details, see section 10.2.4.

ATLAN V3.4 175/227 Ed 2.0

Note: the box containing the value should be appropriately dimensioned, as the whole
length of the text inserted when signing the document should fit within the selected area,
without invading another template boxes. At the editor, only the text initial position is
shown. The final total length of the text will be unknown by the system.

- Select option “Images Position” to insert an image. Then, by opening the

associated list in the active box, choose the image to be inserted. To delimit the
area within which the image should be framed, press the mouse right button and
move the mouse to generate the corresponding rectangle as desired.

ATLAN V3.4 176/227 Ed 2.0

Note: the image will be automatically scaled so that it takes up all the space at the
delimited surface. It is not guaranteed that the image proportions are kept.

19.4 ADDITIONAL EDITION FUNCTIONS

19.4.1 Contents deletion

It is possible to keep updated the list of texts and images, by deleting the templates which
are not yet useful or necessaries. To do so, use the menu “Edition – Remove Template
Text/Images”, select any of them and click on “Delete”.

ATLAN V3.4 177/227 Ed 2.0

19.4.2 Preview
A preview of how a template looks like can be obtained at any time during its definition.
It is also possible to make a zoom in order to visualise the design details of a template.

Depending on the original image resolution and the template size, zoomed in images
can show low resolution. Anyhow, the will be shown with its original resolution at the real
template.

ATLAN V3.4 178/227 Ed 2.0

19.4.3 Templates edition
It is possible to modify an existing template, always that it has been user created. System
templates cannot be modified.

By selecting menu “Load Template”, the following window allows the selection of the
template which requires to be modified.

ATLAN V3.4 179/227 Ed 2.0

By selecting a template and clicking on “Accept”, the template edition environment is
opened for the selected template. A given template can be modified by using the
template edition and creation tools described in previous sections, in order to correct
errors detected in an existing template or to create a new one.

19.4.4 Texts alignment

The text alignment facility allows texts of the template to be horizontally or vertically
aligned. To do so, once the texts introduced, a checkbox to indicate which text will be
used as alignment pattern must be chosen. Also, horizontal or vertical orientation must
be selected together with the texts to be aligned (blue colour), always referred to the text
pattern.

ATLAN V3.4 180/227 Ed 2.0

19.4.5 Background image insertion
In order to make the construction of templates easier, ATLAN allows inserting
background images in a template. Separation lines and logos should have been
previously created within the image – this constituting, therefore, a whole entity in the
template –.

Texts – fixed and variable – could be inserted above the image, although fixed texts
could be part of the background image.

An example of background image could be:

It is recommended to dimension the background image with the same aspect ratio than
the template. That is, for an A4 Horizontal template an image of 842 x 80 pixels – or
similar – should be used. If, for example, an image of 1000 x 100 pixels is used, this
will need to be automatically resized in order to fit within the dimensions of the template,
and this might change the width of any of the lines, to a point that the background image
might not be able to be shown on the edition window, as shown in the next example.

ATLAN V3.4 181/227 Ed 2.0

Due to the fact that the image used has a size larger than 840 pixels, when adapting it
to the size of the template it seems that it lacks of a vertical line on the left side. However,
at the time of generating the template data box the original image is used and therefore
its own appearance is maintained.

19.4.6 Zoom level

The zoom level can be changed along the process of generating a template, although
such a change implies the deletion of the historical; that is, the possibility of “Undo” or
“Redo” is lost.

ATLAN V3.4 182/227 Ed 2.0

20 CUSTOMISED FRAMES
Customised frame functionality allows drawings using predefined frames to be produced.
Custom frames can be produced using any other drawing tool.

By clicking the icon a new working environment is opened. This tool allows new custom
frames to be imported and integrated in the drawing production process.

To start this process the image of the custom frame has to be available in any of the
following formats: gif, jpg, jpeg or svg.

After clicking the icon the following window is opened.

Click on “Explore” to find the file that contains the image of the
custom frame to be used. Once the file is selected, size of
paper, format and margins have to be defined.

Clicking on “Accept” the image of the selected frame will be

displayed and the edition process will start.

Clicking the icon the area were the drawing has to be fitted can be set. Clink on the
upper left corner of the desired drawing area and holding the left button drag the mouse
to the desired lower right corner. If the lower part of the drawing area is not visible, the
drawing can be moved using the keyboard arrow keys.

Clicking on the icon the area of the data block can be defined. Use the same procedure
as described before to define the area were the data block has to be fitted.

Once the data block area have been defined, a data block design has to be associated.
Any of the previously defined data block can be used. To
associate a data block select the menu “Edition – Adjust-
Template”. The list of available data blocks will be shown.

If the desired data block is not on the list, the editor ca be

activated by clicking on “Template Editor”.

Once one data block is selected, ATLAN will verify if the format fits the assigned area
and will shows the differences express in pixels.

ATLAN V3.4 183/227 Ed 2.0

The dialog box will show the differences in pixels between the data box and the assigned
area. If the dimensions data box cannot be modified the user will have to produce a new
data box template with the proper dimensions or change the size of the assigned area.

By clicking the icon and clicking the green area, it will be erased so the user will be
able to define a new one with the proper dimensions.

If the user decide to use this data box its dimensions will be automatically modified.

Once the editorial process is finished, the new frame template has to be saved using the
menu “File – Save Frame as”.

ATLAN V3.4 184/227 Ed 2.0

21 IMPORT OF PROJECTS
ATLAN’s working environment allows the implementation of methodologies of work that
contribute to the standardisation of substations, augmenting the productivity and
decreasing the cost of the errors made during the engineering stage. The possibility of
inserting a finished project into another project under development makes possible to
achieve these objectives.

The main application of this functionality is the modular design of normalised positions
in order to be able to develop projects afterwards by inserting the normalised positions
that are required, depending on the particular design of each substation.

When initiating the import project function, the system displays a new window where it
will be possible to visualise the project that is going to be inserted. The system will verify
automatically that the IEDs and the connections used in that project are defined in
ATLAN’s library. In the event of finding any discrepancy, an errors report will be
automatically generated identifying the aspects that may cause compatibility problems
and, consequently, loss of information.

Users need then to evaluate whether the reported messages may cause loss of
information or incompatibility, and decide whether the project can be imported or not.
When clicking on the “Accept” button, the system will proceed to import the project.

In general, incompatibility problems can be solved by means of importing the libraries

previously to the project.

Only totally signed projects can be imported and thus the signatures are automatically
verified. However, the signatures and certificates of the Author, Reviewer and Approver
of the imported project will not be applied to the project under execution.

Once all the verifications carried out, a visualisation window of the project will be
displayed allowing users to check its contents.

There are two possibilities of carrying out the definitive import:

- Clicking on the icon to import the project just once.

- Clicking on the in order to import the project multiple times. In this case, it will
be possible to perform the import for an unlimited number of instances.

ATLAN V3.4 185/227 Ed 2.0

The insertion of a new project will work, from the user’s point of view, as the “Copy” and
“Paste” functions. Therefore, when inserting a new project the copy rules will be applied
to what the change of name is referred to. That is, if an IED has a copy rule, this rule will
be used; if it has not any, then the general copy rule of the project under execution will
be applied.

The .icd/.cid files of the IEDs 61850 will be included in the import process. The
documents; the simulations; and the user certificates of the inserted project will not be
copied. The Logical Functions; the template data boxes; the preferences; and the
backups will not be imported either.

The particular basic classes of the inserted project will be imported to the project under
execution, automatically and transparently to the user.

The user views of the IEDs will not be imported to the project; however, there will be
imported the views of the connections.

21.1 Project import from Web

ATLAN working environment includes a specific facility to automatically import projects
from the ATLAN technical support web page. Click on the link
http://www.pullnet.com/atlansupport/index_atlan.html to see available projects.

The file downloaded from this web page contains a project together with the library
elements required to be fully operative. Automatic import facility simplifies the process of
installation of every component associated with the project. Every type of file is
automatically extracted and process accordingly.

ATLAN V3.4 186/227 Ed 2.0

Once a project file has been downloaded from the Web, ATLAN has to be started up and
the submenu “Communication – Import – Import and Integration Complete Project”

This menu starts up a wizard that automatically will carry out the importation process
following the steps depicted in the following sections.

21.1.1 Device import

Import of devices is the first step of the process. The wizard extract, one by one, all the
devices included in the project imported showing the place of the device library where it
will be stored.

The location of the imported device in the device library cannot be modified. If the device
that is going to be imported already exists in the device library, the following warning will
be shown. The user should decide whether the existing device has to be replaced by the
imported one or keep the old device as it is.

ATLAN V3.4 187/227 Ed 2.0

21.1.2 Connection import
Once all the devices have been imported, the wizard will start the process of connection
import showing the following window:

The user has to choose one of the following three options:

- Import all the connections. This option has to be considered very carefully since
some of the already existing connection may be modified if both have the same
name.
- Import a selection. If the user knows exactly the connections used in the imported
project, he may select theses connections and use this option.
- Replace library. This option will replace existing connection libray by the library
included in the imported file. It is not advisable to use this option unless the user
has created the imported connection library previously.

21.1.3 Logical Function import

The import of LFs works like device import process.

The user has to follow the instructions given by the wizard.

ATLAN V3.4 188/227 Ed 2.0

LFs are imported one by one. The user has to validate the import of every LF.

21.1.4 Generic classes import

The next step in the process imports generic classes which defines voltage levels,
protocols, etc.

The import of generic classes works in a similar way as connection import. Similar actions
and similar decision has to me make choosing between complete import of generic
classes, import of a selection or replacement of generic classes.

ATLAN V3.4 189/227 Ed 2.0

21.1.5 icd files import
If the imported project include IEC 61850 devices, the wizard will automatically import
the associated icd files.

The user can chose which file will be imported. Nevertheless, it is strongly advisable to
import all the files otherwise some of the IEC 61850 functionality of the imported project
may crash. Furthermore, the generation of IEC 61850 configuration files may produce
corrupted files.

21.1.6 Telecontrol Data Base import

The import of Telecontrol data Base is fully automatic. The wizard will carry out the work
and inform the user when finish.

21.1.7 Project import

This is the last step of the process. The wizard will allow the final destination of the project
to be chosen.

Once the project has been imported in the indicated location, the wizard will inform and
the import process will be finished. The project is now ready to be used being all its
functionalities and properties available to the user who may continue working on this
project or use it as a template for future projects.

It is not allowed that another project with the same name of the imported project be
located in the same folder. In this case, the import process will be automatically aborted.
Consequently, before starting the project import wizard, it is very important to check if
there is another project with the same name in the folder that we want to store the
imported project. It this is the case, the existing project has to be archived or the imported
project will have to be stored in another folder. If the wizard detects that there is another
project with the same name, a warning will be reported before aborting the process.

ATLAN V3.4 190/227 Ed 2.0

22 EXPORT OF COMPLETE PROJECT
ATLAN’s working environment allows the implementation of work methods that
contribute to the standardisation of substations, which at the same time contributes to
augmenting the productivity and decreasing the costs of the errors in the design and the
engineering processes. Together with the import of projects functionality described in
chapter 20, the possibility of exporting a completed project including all its libraries allows
achieving those objectives.

The principal application of these two functionalities is to design standardised bays, in

order to be able to develop projects by inserting the standardised bays required in each
case, depending on the particular design of every substation.

Once a project completed, in order to carry out its complete exportation the project needs
to be opened in ATLAN’s working environment, as otherwise the “Export complete
Project” option in submenu “Export” within the “Communication” main menu will not be
shown activated.

Following, it will be automatically generated a .zip file in ATLAN’s library (./export

/Proyecto SSD Bis v1.zip), with the same name as the project to be exported.

ATLAN V3.4 191/227 Ed 2.0

In the case that there already exists an export .zip file with the same name, the system
will provide users with the option of replacing the existing file, or keeping it and export
the project to a.zip file with another name.

If the export process is completed correctly, the following message will be displayed.

22.1 Possible error messages (critical and minor)

In the case that errors occur during the export process, these will be either critical or
minor.

Each time that a minor error occurs during the export process, ATLAN will ask whether
to continue with the export process or not.

On the contrary, if a critical error occurs during the export process then the process will
be automatically cancelled.

The several possible error types are shown next.

- Project without Nodes or with issues found in some device. (Critical Error)

ATLAN V3.4 192/227 Ed 2.0

- ICD’s not found (Critical Error)

- Telecontrol Data Base not found (Critical Error)

ATLAN V3.4 193/227 Ed 2.0

- The .zip file cannot be created (Critical Error). It may be due to the presence of some
errored file in the project, or to not having found some source/destination route.

- Error when extracting the information from the project destination file (*.zprjexp)
(Critical Error)

- Logical Functions: One or both required file(s) missing (.flxml or/and .flygf) (Minor
Error)

ATLAN V3.4 194/227 Ed 2.0

- Connections file not found (.flxml or/and .flygf) (Minor Error)

- Generic Classes file not found (.flxml or/and .flygf) (Minor Error)

- Data box not found (Minor Error)

ATLAN V3.4 195/227 Ed 2.0

ATLAN V3.4 196/227 Ed 2.0
23 DETAILED ENGINEERING
WARNING: These functions are only available if you have an ATLAN licence including
the Detailed Engineering package.

23.1 INTRODUCTION
The Detailed Engineering package allows users to implement the particular details of the
engineering design of a substation from the corresponding basic engineering project, this
having been generated from the set of rules and procedures described in this manual.

The operation of this extension of ATLAN is completely specified in the document

“ATLAN – Detailed Engineering Manual”. The functionality of this tool provides a great
degree of flexibility. Due to this fact, when generating the detailed engineering it is
recommended to follow the sequence of steps indicated in chapter 2 of that manual.

One of the advantages to be highlighted of ATLAN’s Detailed Engineering package

stems from the possibility of being able to maintain the verification of the coherency of a
project – from the basic engineering, to the very last detail –, as thanks to this package
it is possible have access to all the documentation and information of an entire project in
a common repository of information and working environment.

Also, this functionality provides the additional advantage of being able to develop the
basic engineering of a project to the desired degree of detail and, from that point, to
export if required all the information to another detailed engineering market tool – thus
not being necessary to generate with ATLAN absolutely all the documentation of the
detailed engineering of a project–. This export process is implemented by means of a
XML interface included in ATLAN.

23.2 MAIN FUNCTIONS

ATLAN’s Detailed Engineering kit makes it possible to develop the details of the basic
engineering of a project in new specialised working environments.

Its main functions include:

- The development of generic connections.

o The tables with all the connections included in the detailed engineering of
a project can be generated by means of the table generic tool. This allows
users to define cabinet terminals and intermediate connection terminal
blocks, as well as to add text comments including details and further
information of the connection.
- The generation of detailed drawings. This function allows users:
o To open a new working environment that includes previously defined
connections – which link a set of existing IEDs –, and to extend the original
drawings with additional connections and another intermediate devices.
o To automatically generate connection lists from the detailed drawings.
o To define the hierarchy among the drawings by means of an editable
indexed scheme. Also, the relationship among all the developed drawings
can be created by means of a tree-shaped hierarchical structure.
- The generation of libraries of equipment for the detailed engineering.
- Obtaining the list of drawings of the detailed engineering, indexed according to
user defined criteria.

ATLAN V3.4 197/227 Ed 2.0

24 ANNEX A. INSTALLATION DETAILS
The correct execution of ATLAN’s environment requires the installation in your computer
of the Java jdk 1.5 or 1.6 packet from Sun Microsystems Incorporated.

WARNING! The execution of all the functions in ATLAN requires that your operating
system has the following applications of complements installed:

- Java Machine appropriately registered in the system. Otherwise, ATLAN will not
be able to initiate its execution.
- Java “jdk 1.6” environment. The functionality of documental management and of
management of electronic signatures requires that your computer has installed
the environment java jdk 1.6 update 43. If you do not have the java jdk installed
in your computer you can get a free of use licence in
http://www.oracle.com/technetwork/java/javase/downloads/index.html. Once the
file has been downloaded, install the jdk following the instructions.

ATLAN V3.2 has been certified for the version 1.6 of JDK. If you have installed a different
version, you should disable it and leave the version 1.6.

In order to disable other versions of Java (JDK 1.7 or JRE 1.7), open the “Control Panel”
Windows Start “Configuration” menu. Then double click on the “Java” input.

On the window displayed, press on the “Java” sheet.

Then click on the “See” button on the lower part of the window. The following pop-up
window will be displayed:

ATLAN V3.4 198/227 Ed 2.0

Any version of Java different from version 1.6 must be disabled (Config Java Application)
and the platform 1.6 must be activated. This must be the only product activated.

Once this done, it is required a PC restart so that the changes take place.

ATLAN V3.4 199/227 Ed 2.0

25 ANNEX B. EXAMPLE OF CREATION OF NAME AND SEMANTIC RULES

This Annex includes a practical example of creation of names and semantic rules
(chapter 15 of this manual), applied to devices and connections.

This is a practical and visual application of how to generate a simple naming and copying
rule for devices and connections. At the end, we will see an example of its application to
the creation and copy of devices and connections.

From the “Libraries – Library of Names” submenu, we can access to any of the four
stages of creation of rules.

To carry out a complete creation, the first stage will be selected: Edit Elementary classes:
The window of creation of elementary classes is then displayed. They are the
fundamental piece, the atomic elements, from which the rest of them are created. Texts
and fixed numbers will be able to be created, as well as we will be able to assign our
own separators. For example, let’s define the text ‘Addsys’ and the numeric ‘2009’ in
order to use them afterwards as fixed elements. The separators that we will use in this
case are the hyphen and the underscore. It needs to be taken into account that there are
characters that cannot be used for being system reserved for incremental and
decremental numerics and texts.

ATLAN V3.4 200/227 Ed 2.0

In order to pass onto the following level, we can save the elementary elements created
on the first stage and then open the corresponding menu; or we can click directly on the
next button ‘>>’, which allows us to save the data introduced and opens the next level of
basic classes. Here there can be performed combinations between the previous
elements and other atomic elements, such as texts and free numerics, corresponding to
an initial basic level. A maximum of up to 6 components is allowed.

In this example, it has been inserted a basic class for the IEDs and another for the
connections. Both classes consist of a fix text, a separator and a numeric incremental
(the latter to be used for the subsequent copying rule). Any combination can be carried
out, as a text or a free numeric instead of the fixed text – for example –, etc.

In the first place we will enter the name, then the number of components will need to be
chosen, we will select each one of them, and finally we will press on button “Add” so it is
aggregated to the library.

ATLAN V3.4 201/227 Ed 2.0

At the level corresponding to classes of names, we will create one for devices and
another one for connections.

Here we can carry out any combination of up to 8 basic elements. In our case, in order
not to introduce too much complexity, we create just one for devices with an only basic
element (the one formerly created) and another similar one for connections.

The sequence of steps is similar as before, firstly having to enter the name; then
choosing the number of components; selecting the required option in each one of the
columns of basic classes; and finally clicking on the “Add” button to aggregate it to the
elements of the library.

Finally, we will apply to each device the class of name that is going to be used. To do
so, on the left part of the “Classes Dictionary” window there is a tree with the devices of
the system. We will choose one; subsequently we will select the Rule of name that we
wish to apply; and then we will establish this assignment by clicking on the “Assign”
button. This assignment will be reflected on the lower part of the window, in the

ATLAN V3.4 202/227 Ed 2.0

“Dictionary”. There, we will be able to check all the devices that have been assigned with
rules of names. By selecting any of them, we will also be able to delete, as needed at
any time, rules of names (in case of detecting rules assigned to a device which do not
correspond to our requirements).; as well as to apply a copying rule to the rule, in order
to use it in the case of copying devices.

By clicking on the “Generate RC” (generate copying rule) button, we will have access to
a pop-up window in which it is fully displayed the rule that applies to the device.

ATLAN V3.4 203/227 Ed 2.0

In this window we will be able to select which field or fields will be taken into account
when copying the device. There are fields, as the separators, that are fixed and will not
be able to be selected. In our example, we choose the “IN” (incremental number) field.

The procedure would be similar for the connections, except that in that case we have a
rule of names for the labels (Rule or R), and another one for the alias (Alias Rule), being
able to define a copying rule (CR and ACR respectively) for every one of them – in a
similar way as for the devices –.

In the case of having copying rules, when the copy is carried out with devices or
connections that have such rules assigned, only the assigned fields will be used. If there
are not copying rules but there are rules of names, the latter are assigned.

At this point, it is advisable to make a last save of the information, in order not to loose
the changes.

Let’s see now some cases in which these rules of names are applied.

In the first place, it needs to be verified whether the Rule of names is activated, by means
of the icon on the icons bar. The set square’s background highlighted in grey colour
indicates that the rule is deactivated, whereas a yellow background indicates that the
rule is activated.

If the Rule of names is not active when creating new devices and connections, the fields
of the corresponding names will appear enabled so that the texts can be manually
entered.

ATLAN V3.4 204/227 Ed 2.0

If, with the rule of names having been assigned, we insert the former device in a project
the first thing that we will see is a window with the generator of names, in which it is
displayed which rule will be adopted. If there are any fields requiring data to be entered
by the user, they will appear enabled. On the contrary, those fields are only shown at
informative level and do not appear enabled. By means of the “Load data” button, we will
be able to visualise which name will be generated, bearing in mind the numeric
incremental in our case as the system will search for the corresponding value.

Once the name is shown, the device insertion window will be shown with this field
disabled and the adequate value, the rest of the fields required for the creation of the
device being able to be set:

ATLAN V3.4 205/227 Ed 2.0

In order to see how the copy of names rule operates, we can choose the device just
created and make a ‘Copy / Paste’. We can see how in our case a new device named
‘Addsys-2’ is inserted as the copy field is the numeric incremental, which is automatically
calculated.
If a free text had been chosen as copy field, it would appear the screen of the generator
of names, waiting for that field to be inserted.

For a higher degree of automation of the copy function, it is recommended to use copy
rules with automatic fields, as they make this action much easier.

ATLAN V3.4 206/227 Ed 2.0

If we insert now a connection which has a rule of names, between both devices, the
window of generation of names will be displayed in a similar way as before.

This time we will need to enter a free text, for the label as well as for the alias, depending
on the generated rule. The load of data will be double in this case, and we will finish with
“Save”.

Following, the window corresponding to the connection carried out will be displayed, with
the Label and Alias fields disabled:

ATLAN V3.4 207/227 Ed 2.0

If, finally, we make a copy of the two devices created and the corresponding
interconnection, we will get a copy of them and their connection. In this case the system
does not ask for any name, as the copying rule of all the involved elements is automatic:

For those devices and connections not having assigned any names and/or copy rules, if
a copy of them is carried out, the system will consider the copy general rule. This rule
consists in applying a suffix – made by a separator and an incremental – to the name of
the original element. In order to modify this rule, we must select the “Libraries – Library
of Names – Copy Rule” submenu.

ATLAN V3.4 208/227 Ed 2.0

Thus, applying the copy rule in the example to a device originally named ‘DeviceAtlan’,
when copying it the first copy instantiated would be named ‘DeviceAtlan-1’; a second
copy ‘DeviceAtlan-2’; and so forth. It needs to be considered that a suffix is added to the
original element, without taking into account whether this was formed with a rule or not.
For example, if we made a copy of the last device we would get a new element named
‘DeviceAtlan-2-1’.

ATLAN V3.4 209/227 Ed 2.0

26 ANNEX C. EXAMPLE OF CREATION OF A DO/DA ALIAS DICTIONARY

Following it is presented a practical example of creation of the DO’s/DA’s Alias dictionary

(chapter 15 of this manual), applied to its use for the configuration of devices and
connections (Mapping of Logical Functions).

This is a practical and visual application involving the generation of the dictionary, and
how to use it.

From the “Libraries – Naming library” submenu, we need to select the “Edit DO/DA Alias
Dictionary” option.

Following, we choose the device with which we wish to work and then we click on the
“Load data” button. Note: Those devices that have associated a valid ICD file appear
filtered in the corresponding pop-down menu.

ATLAN V3.4 210/227 Ed 2.0

In this way we obtain the tree folder of the ICD file, which can be browsed until we find
the DO that we wish to use. Following, we assign to it an alias by means of the field
meant for that purpose on the right part of the window. Once the corresponding alias
assigned, we aggregate it to the dictionary. In the corresponding area – lower right part
of the window – it will be shown the list of the aliases assigned to this device and its ICD
file. We can get the complete path of an alias element by means of a tooltip, just placing
the cursor over that alias. To insert a new alias, we select another DO and repeat the
process.

Once all the alias of the DO’s has been aggregated, we proceed with a “Save” before
leaving the window.

ATLAN V3.4 211/227 Ed 2.0

At the time of using these aliases, we can assign a new logical function to the devices
that have associated that ICD – in our example, a connection between two elements
alike, as shown in the previous figure –. Following, we map any logical function,
indicating that the device is that one dealt with previously. When we need to carry out
the signals assignment, if the inputs or the outputs are of type logic the DO’s-DA’s
associated to the origin or final element of the connection will be shown – and they will
be shown up according to their aliases if the latter have been designated –. In our
example, we set the alias ‘AlarmaProxy’ for the DO ‘Proxy’ of the LN ‘LPHD’ in the LD
‘C1’ – as it can be seen in the combo –. The following DAI does not have any alias
associated and that is why its information is displayed as obtained from the ICD file. In
this way, we can quickly assign the DO data to the mapping of logical functions.

ATLAN V3.4 212/227 Ed 2.0

27 ANNEX D. EXAMPLE OF IMPORT OF A PROJECT

The example shown next shows the import of the project ‘Test Siemens1’, from the files
that can be found in the CD provided for this purpose.

To do so, we copy the files ‘ICDSIEMENS’, ‘Libcom30-09-2209’ and ‘Librería IEDS’ in

folder C:\AtlanEditorGrafico\export.

We copy the file of the project (‘Test Siemens1_20090930_1254299239437.zprjexp’) in

C:\AtlanEditorGrafico\backup

ICD files import:

We select ICDSIEMENS

ATLAN V3.4 213/227 Ed 2.0

The result of the verification is not relevant at all in this case. So, we click on “Yes”.

Then we select and import.

IED – Devices import:

ATLAN V3.4 214/227 Ed 2.0

We choose file “Library IEDS” (same verification message)

Now we select the IEDs to be import. (In our case):

7SA522v2
7SJ635v1
Ethernet SwFO

NOTE: We will need to repeat this process as many times as IEDs to be import, unless
that they are placed in a same folder. If this was the case, we can import all the elements
in the folder at once.

ATLAN V3.4 215/227 Ed 2.0

NOTE: The images associated to the IEDs that have same names as already existing
images will be overwritten. It is important to keep a good discipline in the naming of
images in order to avoid data loss for overwriting.

ATLAN V3.4 216/227 Ed 2.0

Connections import:

We select the file of the connections to be imported (‘Libcom30-09-2009’).

ATLAN V3.4 217/227 Ed 2.0

We can import all the connections, only some of them, or replace the file of connections
of ATLAN for the new one.

Project import:

We select to project to be import, within the path C:\AtlanEditorGrafico\backup, and then

we indicate in the window on the left the location where the selected project needs to be
import:

ATLAN V3.4 218/227 Ed 2.0

  Discharge the selection

Obtaining:

Then we can open the project ‘Test Siemens1’, as shown in the following figure, and
from that point we can continue working on it in our project.

ATLAN V3.4 219/227 Ed 2.0

ATLAN V3.4 220/227 Ed 2.0
28 ANNEX E. TERMINALS TEMPLATE QUICK GUIDE

The contents in this Annex provide a description of the fields included in a Terminals
Template in .xls format and show how it can be used, by means of the following parts:

 Columns structure

 Mandatory fields

 Recommendations

 Solution of errors

28.1 Columns structure

A (Name) – Name of the Terminal; it cannot be empty (otherwise the whole row will be
ignored).

B (Desc) – Description of the Terminal

C (Comments) – Comments for the Terminal

D (Terminal Type) – Type of Terminal. There can be selected 4 types: Contact, Analog
Signal, Communication and Power Supply.

F (SubType) – SubType of Terminal. The choices of Terminal Sub-Types depend in the

Terminal Type selected in column D.

Contact: Simple, Three-phase and Non floating

Analogical Signal: Simple-phase current, Three-phase current, Single-phase

Voltage and Three-phase Voltage.

ATLAN V3.4 221/227 Ed 2.0

 Communication: Ethernet cable, Ethernet fiber, RS232, RS485....

Power Supply: Single-phase, Three-phase and Direct current.

H (Voltaje Power) – Voltage of the Terminal. It is activated only for terminals of types
Contact, Analogical Signal and Power Supply.

I (Protocol) – Protocol of the Terminal. It is activated only for terminals of type

Communication.

J (InOut) – Indicates the Input/Output of the Terminal. Possible selections are In, Out or
Bidirectional.

K (ForzedPosition) – Indicates whether the Terminal has forced position or not.

Possible selections are true or false.

ATLAN V3.4 222/227 Ed 2.0

L (Position) – Number of Forced Position of the Terminal. If the Terminal does not have
forced position this field is ignored, otherwise its number needs to be indicated.

Mandatory Fields

Columns A; D; F; H or I (depending on the Type selection); J; K; and L (the latter being

necessary to be indicated only if K is ‘true’).

28.2 Recommendations
It is recommended:

- Neither doing copy/paste nor deleting information for more than a column at a
time, as it may cause errors in the formulas or even their loss.

- Not to move cells.

- Not to try to edit those cells which are selectable, as in this case it is only allowed
to select an option from the list of options included.

- Neither attempting to create new sheets nor changing the name of existing
Sheets.

- In order to be able to import a new template, this will need to have been previously
placed in folder “/config/” of ATLAN’s tool.

- If it is wished to copy the information from a terminal to other cells, data need to
copied column by column, by means of the ‘dragging downwards’ copy option in
excel, as shown in the following examples. This process is not valid for drop-
down menus (i.e., Columns D, F, H, I, …)

ATLAN V3.4 223/227 Ed 2.0

 - In order to delete more than a Terminal, it needs to be followed a similar
procedure (i.e., undesired data should be deleted column by column).

28.3 Solutions to Errors

A list of all the possible errors that can occur during the insertion of Terminals in the IED
Editor, together with their causes and solutions, follows next.

- The Excel file selected is not Terminals Template.

- The system has not detected Terminals in the selected Template. It means
either that the .xls file does not contain any Terminal, or that the terminals that it
has have no Name.

- General error message, where the several errors found during the loading of
Terminals Template are detailed.

ATLAN V3.4 224/227 Ed 2.0

 - A Name is repeated in several Terminals. Names of Terminals cannot be
repeated.

- A Type/Subtype of a Terminal is not valid. The information regarding the Type

or Subtype of the Terminal is missing. All terminals must contain such
information.

- A Voltage is not present in ATLAN’s Generic Classes. It means that the voltage
indicated is not registered in the Generic Classes of the tool. In order to be able
to use Voltage (xxx) it is necessary to define the new value in
‘Libraries/GenericClasses/Terminal Voltage’.

ATLAN V3.4 225/227 Ed 2.0

 - A Terminal does not have a valid Voltage. The indicated Terminal does not have
Voltage at all, i.e., the cell is blank.

- A Protocol does not appear in ATLAN’s Generic Classes. It means that the
indicated protocol is not registered in the Generic Classes of the tool. In order to
be able to make use of such protocol it is required to define it first in
‘Libraries/GenericClasses/Protocols’.

- A Terminal does not have a valid Protocol assigned. The indicated Terminal
does not have any Protocol associated, i.e. the cell is blank.

- A Terminal has not Input/Output type definition.

- A Terminal has a Forced Port that is being used by another Terminal. The forced
port number needs to be exclusively unique for every Terminal; i.e., 2 terminals
cannot be connected to a same port. Only Position numbers of the Terminals with
Forced Position (i.e., Forced Position ->) are verified. The rows highlighted in
green colour in the following example do not involve any error, as although the
position number ‘10’ is repeated one of both terminals does not have Forced Port.

ATLAN V3.4 226/227 Ed 2.0

 - A Terminal does not have the Forced Port assigned. It has been detected a
Terminal with Forced Port but without any Position assigned to it. It can be the
case that either the cell is blank or the associated number is zero ‘0’. The cells
highlighted in green colour in the next example correspond to coherent data
despite having zero ‘0’ associated to the Position or having that cell in blank, as
in both cases the Terminal does not have forced position (ForcedPosition ->
‘false’).

- A Terminal has a non-numeric Forced Port assigned. It means that the indicated
Terminal is a forced Terminal but its position is not a numerical value.

ATLAN V3.4 227/227 Ed 2.0