Spectrum Powercc Scada: Reference Guide

Spectrum PowerCC
SCADA
Reference Guide
Release 07 / 2005
SPC-RG-SCADA-04.1.02
Spectrum PowerCC
SCADA
2 Copyright © Siemens AG 2005. All rights reserved. Release 07 / 2005

Spectrum PowerCC
SCADA
Warning Conventions Table 0.1: Warning Conventions

Level Symbol Level Text Definition
1 DANGER DANGER indicates an imminently hazardous situa-
tion which, if not avoided, will result in death or seri-
ous injury
2 WARNING WARNING indicates a potentially hazardous situation

which, if not avoided, could result in death or serious
injury.
3 CAUTION CAUTION used with the safety alert symbol indicates

a potentially hazardous situation which, if not
avoided, may result in minor or moderate injury.
4 CAUTION CAUTION used without safety alert symbol indicates

a potentially hazardous situation which, if not
avoided, may result in property damage.
5 NOTICE NOTICE used without the safety alert symbol indi-
cates a potential situation which, if not avoided, may
result in an undesirable result or state.
(6) NOTE A note is a tip. The user does not need to follow this
statement. However he will have advantages if he
does.
Qualified Personnel Only competent and authorized personnel should work with this product after
becoming thoroughly familiar with all warnings, safety notices, operating instructions
and maintenance procedures.
Use as described The product must not be used for any other purposes than that described in the
technical documentation. If it is used together with third-party devices and
components, these must be recommended or approved by Siemens. The successful
and safe operation of this product is dependent on adequate transportation and proper
handling , storage, installation, operation and maintenance.
Disclaimer Siemens AG shall not be liable for any incidental or consequential damages resulting
from the performance or use of this product.
This document has undergone extensive technical approval before being released.
We review this document at regular intervals, and include appropriate amendments in
subsequent issues. While every effort has been made to keep the information herein
as accurate and up to date as possible, Siemens Energy Automation assumes no
responsibility for errors or omissions or for damages resulting from the use of the
information contained herein. The content of this document is for information only and
in consequence, Siemens cannot take over liability resulting in any way from the use of
this document or parts thereof.
Release 07 / 2005 Copyright © Siemens AG 2005. All rights reserved. 3

Spectrum PowerCC
SCADA
These contents shall not become part of or modify any prior or existing agreement,
commitment or relationship. The sales contract contains the entire obligations of
Siemens. The warranty contained in the contract between the parties is the sole
warranty of Siemens. Any statements contained herein do not create new warranties
or modify the existing warranty.
Siemens AG reserves the right to update this documentation from time to time and
especially to adapt it to the current status of the product Spectrum PowerCC or to
change it without prior notice.
Copyright Copyright © Siemens AG 2005. All rights reserved
This document is protected by German Copyright law and international contracts as

intellectual property of the Siemens AG. The document contains confidential
information of Siemens AG which are protected by patent, copyright, trademarks or
otherwise as inventions, trademarks or creations of Siemens AG. The reproduction,
duplication, transmission or use of this documents or its contents is not permitted
without express prior written consent of the Siemens AG .
Safety Notes This manual does not constitute a complete catalog of all safety measures required for
operating the product in question because special operating conditions might require
additional measures. For application specific safety measures refer to the respective
project documentation. However, it does contain notes that must be adhered to for
your own personal safety and to avoid damage to property. These notes are
highlighted with a warning triangle and different keywords indicating different degrees
of danger as stated in the Warning Conventions.
Trademarks Spectrum PowerCC® is a registered trademark of Siemens AG. An unauthorised use

is not permitted.
The remaining descriptions in this documentation/information could be trademarks, the

use of which by third parties for their aims could infringe upon the owner’s rights.

Spectrum PowerCC
SCADA

Spectrum PowerCC
SCADA
History
Version Date Modification
3.1.0/Draft Apr-2003 Additions/Modifications according to new functionalities in Pow-

04/03 erCC 3.1.
3.1.0/ May-2003 Final document edition.
Release
05/03
3.1.0/Draft May-2003 Updated according to review comments and new engineering
05/03 tasks.
3.1 Aug-2003 Formal adjustment 3.1
4.0 July-2004 Update to SPC 4.0
4.1.0 Jan-2005 Update for SPC 4.1
4.1.1 May-2005 Corrections due to SPC400012089, SPC400012761
4.1.2 July-2005 Correction due to SPC400010556

Spectrum PowerCC
SCADA
Preface
Purpose This Reference Guide provides detailed reference and procedural information about
the graphical-based and tabular-based Supervisory Control and Data Acquisition
(SCADA) user interface views. This Reference Guide is designed to be used as a
reference in daily work as well as for initial system setup.
Audience This Reference Guide is intended to provide detailed reference and end user
functionality information about the SCADA user interfaces. Each volume in this
Reference Guide is designed and written to provide information to users within two
categories of specific audience types:
• Dispatcher/Operator
• Data Engineer
Prerequisites This Reference Guide is designed and written based on the assumption that readers
are already familiar with Windows, the Spectrum PowerCC product concepts, system
startup/shutdown, Information Model Manager (IMM) functions and editor navigation.
When applicable, other Spectrum PowerCC documents may be referenced as sources

for additional or more detailed information. Specifically, readers are strongly
encouraged to read or reference the following Spectrum PowerCC documents and
third-party product manuals:
• Spectrum PowerCC SCADA Technical Specification
• Spectrum PowerCC Information Model Management Technical Specification /

Information Model Management Reference Guide
• Spectrum PowerCC CFE Technical Specification/CFE Reference Guide
• Spectrum PowerCC ICCP Technical Specification/ICCP Reference Guide
• Spectrum PowerCC System Management Technical Specification/System

Management Reference Guide
• Siemens WinCC User Guide
• Siemens WinCC Getting Started Tutorial
Organization
Volume Contents

Spectrum PowerCC
SCADA
Volume 1- User Interface The user interface volume contains the functional organiza-
tion and descriptions of module dialogs and their constitu-
ent elements. It includes basic procedures for using module
functionality.
Intended Audience: Dispatchers/Operators/Systems Engi-
neers, Data Entry Technicians/Field Data Modelers, Mar-
keting/Sales
Volume 2- Engineering The engineering volume provides procedures to customize
modules. This includes parameterization and software set-
tings (configurable time-outs, limits, etc.) as well as data
entry and information not covered in the Spectrum Pow-
erCC Installation Guide.
It describes procedures to create or modify module-specific
customization parameters, displays (graphic or tabular) and
data entry and reports (content and generation)
Intended Audience: Service and Systems Engineers, Sys-
tem Configuration Technicians, System Support Users
Related Product The following table provides the titles and brief content descriptions of documents
Documents contained in the Spectrum PowerCC documentation set:
Title Contents
Product Overview Describes the current version of Spectrum PowerCC and
includes the purpose of the release, high-level summaries
of additional or modified product modules and any addi-
tional information helpful to a reader.
Technical Specifications Describe the functionality a product provides and how it is
implemented at a high level.
Installation Guide Provides detailed hardware and software installation and
configuration instructions. Hardware includes system and
Spectrum PowerCC components. Software includes third
party products and Spectrum PowerCC components.
Reference Guides Instruct users in how to apply the functionalities identified
in the individual technical specifications and serve as prod-
uct module reference sources.

Spectrum PowerCC
SCADA
Table of Content
Volume 1 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

1-1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
1-1.1 Standard MS Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1-1.2 Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1-1.3 Concept of Operation and Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1-1.3.1 Means of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1-1.3.2 Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1-1.3.3 Guided Operation Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1-2 CONSOLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1-2.1 PowerCC Application Toolbar (PAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1-2.2 User Authentication (Log-on/Log-off) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1-2.3 Graphic Displays (Network Diagrams) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1-2.3.1 Display Call up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1-2.3.2 Display Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1-2.3.3 Display Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1-2.3.4 Toolbar for DMS Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1-2.4 Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1-2.4.1 User Guidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1-2.4.2 Alarming in Manned Control Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1-2.4.3 Wireless Alarming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1-2.4.4 Shift Plan Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1-2.4.4.1 Update Shift Plan Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1-2.4.4.2 Export Shift Plan Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1-2.4.4.3 Import Shift Plan Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1-2.4.5 Global Audible Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1-3 GRAPHIC DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1-3.1 Coloring Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1-3.2 Interactive Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1-3.3 Switch-Over to Values of Network Applications Functions in Graphic Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Spectrum PowerCC
SCADA
1-3.4 Trend Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1-3.4.1 Menubar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1-3.4.1.1 Chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1-3.4.1.2 Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
1-3.4.1.3 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1-3.4.2 Chart Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1-3.4.3 Graphic Presentation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1-3.4.4 Measurement List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1-3.4.5 Status Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1-4 TABULAR DISPLAYS (RUNTIME EXPLORER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

1-4.1 Runtime Explorer Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1-4.2 Predefined Runtime Explorer Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1-4.2.1 Explorer View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1-4.2.2 Substation View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1-4.2.3 Marker Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1-4.2.4 Manual Update Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
1-4.2.5 CFE View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
1-4.2.6 ICCP View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1-4.2.7 OPC View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1-4.3 Ad Hoc Defined Runtime Explorer Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
1-4.4 Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1-5 MESSAGE SUMMARIES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

1-5.1 General Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
1-5.2 Alarm Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1-5.3 Alarm Test Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
1-5.4 Abnormal Status Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1-5.5 Operator Notepad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
1-5.6 Filtering of Message Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
1-5.6.1 Menubar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
1-5.6.2 Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
1-5.6.3 Tabbed Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1-5.6.3.1 Date and Source Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1-5.6.3.2 Path Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1-5.6.3.3 Advanced Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1-5.6.4 Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
1-6 SUPERVISORY CONTROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

1-6.1 Object Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
1-6.2 Single Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
1-6.3 Interlocking Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
1-6.4 Switching Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
1-7 MANUAL DATABASE MANIPULATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Spectrum PowerCC
SCADA
1-7.1 Marking and Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

1-7.2 Manual Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
1-7.2.1 Manual Updating without Manual Update Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
1-7.3 Sound Switch Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
1-7.4 Alarm Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
1-7.5 Dynamic Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
1-7.6 Manual Limit Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
1-7.7 Message Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
1-7.8 Substation Request (Substation Scan). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
1-8 REPORT GENERATOR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

1-8.1 Configure a New Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Volume 2 Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

2-1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
2-1.1 Information Model Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
2-1.2 Configuration of Real-time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
2-1.2.1 Digital Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
2-1.2.2 Analog Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
2-1.2.3 Step Positions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2-1.2.4 Fleeting Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2-1.2.5 Configure a new State Set and Create a Link to this State Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2-1.2.6 Configure a Limit Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
2-1.2.6.1 Configure a New Seasonal Limit Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
2-1.2.6.2 Configure a New Manual Limit Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
2-1.3 SCADA Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
2-2 CONSOLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

2-2.1 PAT Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
2-2.1.1 Configure a new PAT Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
2-2.1.2 Add a new Application to the PAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
2-2.1.3 Add a new Display Call Up Item to the PAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
2-2.2 User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
2-2.3 Display Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
2-2.4 Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
2-2.4.1 Alarm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
2-2.4.2 Wireless Alarming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
2-2.4.2.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
2-2.4.2.2 Wireless Alarming Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
2-2.4.2.3 Configure a Shift Team Member. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
2-2.4.2.4 Configure a Communication Device (Wireless Alarming Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
2-2.4.2.5 Communication Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
2-2.4.2.6 Configure a Service Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
2-2.4.2.7 Configure an Alarm Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Spectrum PowerCC
SCADA
2-2.4.3 Global Audible Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

2-2.5 Realtime Accumulator Processing (RAP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
2-2.5.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
2-2.5.2 Energy Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
2-2.5.3 Configure Accounting Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
2-2.6 Realtime Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
2-2.6.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
2-2.6.2 Configure a Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
2-2.6.3 Configure a Calculation Script Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
2-3 GRAPHIC DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

2-3.1 Worldmap Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
2-3.2 Display Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
2-3.3 Topological Network Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
2-3.3.1 Topology Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
2-3.3.2 General Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
2-3.3.3 Energization Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
2-3.3.4 Voltage Level Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
2-3.3.5 Loop/Parallel Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
2-3.3.6 Network Group Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
2-3.3.7 Multi Phase Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
2-3.3.8 Single Phase Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
2-3.3.9 Configure a Voltage Level Color for an Energized Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
2-3.4 Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
2-3.4.1 Trend Control Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
2-3.4.2 Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
2-3.5 Presentation Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
2-3.5.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
2-3.5.2 Configure a Presentation Logic Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
2-4 MESSAGE SUMMARIES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

2-4.1 Alarm Control Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
2-4.1.1 Column Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
2-4.1.2 Toolbar Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
2-4.1.3 Summary Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
2-4.1.4 Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
2-4.1.5 Advanced Summary Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
2-4.1.6 Configure a New Alarm Control Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
2-4.2 Message Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
2-4.2.1 Message Attributes and Associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
2-4.2.2 Message Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
2-4.2.3 Configure a New Message Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
2-4.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
2-4.4 Configure a New Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
2-4.5 Configure Group Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Spectrum PowerCC
SCADA
2-4.6 Add the Toolbar Button “Clear Summary“ to an Alarm Test Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
2-5 SUPERVISORY CONTROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

2-5.1 Interlocking Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
2-5.1.1 Configure a New Rule Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
2-5.2 Control Execution Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
2-6 MANUAL DATABASE MANIPULATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

2-6.1 Marking and Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
2-6.1.1 General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
2-6.1.2 Link a Marker Type to a Network Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
2-6.2 Manual Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
2-6.3 Alarm Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
2-6.4 Substation Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
2-7 REPORT GENERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Spectrum PowerCC
SCADA

Spectrum PowerCC Volume 1
SCADA 1-1 Introduction
Volume 1 Operations
1-1 Introduction
SCADA is a basic Spectrum PowerCC application providing power system monitoring
and control. The Spectrum PowerCC user interface conforms to Microsoft’s usability
principles.
Audience The targeted audience of Volume 1 of the SCADA Reference Guide is the daily users
of the Spectrum PowerCC SCADA application: dispatchers and operators.
1-1.1 Standard MS Windows

The Look and Feel of the Spectrum PowerCC user interface is based on the MS
Windows standard, using toolbars, buttons, menus and other common components.
Familiarity with MS Windows helps to minimize the effort required to use the Spectrum
PowerCC user interface.
The Spectrum PowerCC user interface provides:
• Standard windows

Volume 1 Spectrum PowerCC
1-1 Introduction SCADA
This figure shows Multiple Overlapping Windows
Figure 1-1.1: Multiple Windows
– Multiple applications run in multiple overlapping windows (up to 10 windows

possible)
– Windows may be placed on 1 to 4 screens per console. They may be moved

across the screens. A single window may span across multiple screens.
– One single window is active and placed in the foreground. All user entries
belong to the active window.
• Standard windows elements
This figure shows a Standard Window
Figure 1-1.2: Example of a Standard Window
– Title bar on top of the window.

– Minimize button to iconize the window.
– Maximize button (window covers all available screens of a console, but keeps
the Power Application Toolbar visible)
– Close button (window disappears from screen)
– Interactive tool bar below the title bar (number and meaning of the buttons
depends on the application)
– Status bar
– Vertical and horizontal scroll bar (automatically displayed, if current window

frame is too small to display the whole content).
• Pop-up and pull-down menus
Both menu types are context sensitive. Valid menu selections are shown in nor-
mal text. Depending on the specific application and menu, invalid selections are
either disabled (no response in case of user selection) or not displayed.
– Pull-down menus are associated with toolbar buttons, and are displayed
when the user clicks the menu title:
This figure shows a Pull Down Menu
Figure 1-1.3: Pull Down Menu
– Pop-up menus are associated with presentation objects found in diagrams,

curves, summaries and tables. They contain the menu items currently valid
for the selected object:

This figure shows a Pop Up Menu
Figure 1-1.4: Pop Up Menu
1-1.2 Online Help

Spectrum PowerCC supports the user by an electronic manual. Clicking the HELP
button in the toolbar opens the appropriate page of the Reference Guide.
1-1.3 Concept of Operation and Control

The concept of operation and control has the following structure:
• Means of operations
• Guided operation sequences
• Alarming
1-1.3.1 Means of Operations
Console The means of operations are provided on the console. For detailed information on the
console refer to Chapter 1-2 Console.
The following means are provided for operation and control:
• Power Application Toolbar (PAT)
• Graphic displays (network diagrams)
• Charts/curves
• Summaries, e.g.:
– General Summary
– Alarm Summaries

SCADA 1-2 Console
– Alarm Test Summaries
1-1.3.2 Alarming
The following means are provided for alarming:
• PAT
• Network Diagrams
• Summaries, e.g.:
– Alarm Summaries
– Alarm Test Summaries
• Runtime Explorer
• Wireless alarming (SMS, e-mail, etc.)
• Audible alarming via loudspeaker
• Global audible alarming via external devices
1-1.3.3 Guided Operation Sequences
Guided operation sequences are provided for the following tasks:
• Viewing and acknowledgement of alarms
• Viewing and modifying values (manual updating)
• Marking and tagging
• Supervisory control
• Manual substation request
• Entering message comments
• Report Generation
1-2 Console
The console consists of one alphanumeric keyboard, one mouse device, 1 to 4
monitors and a loudspeaker for audible alarming. The monitors can be deployed as
one big screen or as multiple separated screens. The mouse pointer may be freely
moved across all screens. The console is characterized by the following features:

1-2 Console SCADA
• The information in all windows is updated whenever there is a change in value or

status.
• The initial size and position of a window is defined during system configuration.
Once the window is called up, the user may resize the window or move it to a
different screen location. The new size and position of the window are saved as
the default for the next time the window is called up.
1-2.1 PowerCC Application Toolbar (PAT)

One of the screens is predefined to display the console-specific PowerCC Application
Toolbar (PAT). The PAT serves as the central application call-up bar. Additionally, the
PAT alerts the user about any alarm condition by flashing symbols (buttons).
The PowerCC Application Toolbar (PAT) may be covered by other windows and will be
automatically popped up on top for the following reasons:
• if the signalling state of an alarm summary changes, PAT will be popped up on top
• if the PAT is configured to pop-up cyclically, PAT will be popped up on top in the
configured cycle
Selection of the PAT After system run-up the user may invoke the PAT by the following steps:
• Click the icon PowerCCSSR.exe on the desktop.
The PowerCC Logon dialog opens (refer to Chapter 1-2.2 User Authentication
(Log-on/Log-off), Figure 1-2.2).
• Enter the user name and the password into the appropriate input fields and click
the button OK. The PAT is displayed on the top of the desktop:
This figure shows the PowerCC Application Toolbar (called PAT)
Figure 1-2.1: PowerCC Application Toolbar (PAT)
Right-clicking the PowerCC logo opens a pop-up menu, where the user may configure
the PAT. For detailed information on the PAT configuration refer to Chapter
2-2 Console.
1-2.2 User Authentication (Log-on/Log-off)

The user may log on to the system and log off from the system by clicking the button
Logon/Logoff on the PAT.
The user may log on to the system by entering the user name and the password. The
user name is displayed in a predefined user name list for allowed names, access rights
and assigned Areas Of Responsibility (AOR). The credentials may be entered on any
console (local, remote, solidly connected or pluggable).
The log-on process is part of the console system start-up:

SCADA 1-2 Console
• Log-on/log-off is executed by the Windows log-on process.
• Each log-on/log-off of an user is recorded in the General Summary.
• After log-on, the predefined access rights and AORs are active.
• The current user must log off the console before another user can log on.
Log-on Process The user logs on to the system by the following steps:
• Click the button Logon/Logoff on the PAT. The PowerCC Logon dialog opens:
This figure shows the PowerCC Logon Dialog Box
Figure 1-2.2: PowerCC Logon Dialog
• Enter the following values:
– User name
– Password
– Domain name (if required)
• Click the button OK.
The PowerCC Logon information dialog (Figure 1-2.3) provides the user log-on status.
The user may invoke the PowerCC Logon information dialog by clicking the button
Logon/Logoff on the PAT.

1-2 Console SCADA
This figure shows the Dialog Box Displaying the PowerCC Logon Information
Figure 1-2.3: PowerCC Logon Information Dialog
Log-off Process The user logs off from the system by clicking the button Log Off in the PowerCC Logon
information dialog.
1-2.3 Graphic Displays (Network Diagrams)
1-2.3.1 Display Call up
A graphic display may be invoked by clicking the dedicated PAT button, clicking the
dedicated menu item on the dedicated pull-down menu associated with a PAT button,
or by Drag and Drop of the respective PAT button/menu item to the desktop.
Graphic Displays may be also invoked by using the Display Search dialog (Figure
1-2.4). The Display Search dialog may be opened by selecting the menu item ’Display
Callup’ from the PAT Tools menu.
All displays may be closed by clicking the standard MS Windows Close button.

SCADA 1-2 Console
This figure shows the Display Search Dialog Used to Invoke the Graphic Displays
Figure 1-2.4: Display Search Dialog
1-2.3.2 Display Navigation
There are multiple methods provided to navigate within a worldmap (large network
diagram):
Panning • Panning within a large worldmap by using the optional navigation window. The
green rectangle of the navigation window represents the segment that is
displayed in the associated main window. The user may move around the green
rectangle having the same effect as panning in the main window.

1-2 Console SCADA
This figure shows the Worldmap (a Large Network Diagram)
Figure 1-2.5: Worldmap with Optional Navigator Window (Top Right Corner)
• Panning of the worldmap by scrolling vertically and horizontally or by a combined

wheel mouse/keyboard action.
Zooming • Zooming of the worldmap:
– Smooth zooming by wheel mouse and pressed CTRL key.
– Rectangle zooming by left mouse button and pressed CTRL key.
– Step zooming by 3 dedicated buttons in the toolbar (in, out, original size).
– During zooming, not only the presentation objects become bigger, but a new
plane with new information - formerly invisible - is overlayed. This logical
decluttering is used to keep all text strings, names, figures and symbols
readable while zooming in/out. The drawing area consists of 32 layers.
• Insertion of up to 32 layers without zooming by dedicated menu items in the layer

menu. The layer menu is located above the left part of the graphic display toolbar.
• Enabling/disabling of an individual plane for temporary better visibility.

SCADA 1-2 Console
This figure shows Two Different Views of One Worldmap
Figure 1-2.6: One Worldmap Two Views (Different Zooming Levels)
1-2.3.3 Display Printing
The user may:
• print screenshots of the selected window or the complete screen content.
• forward the diagram to a predefined printer or dedicated file.
• configure the printer properties.
1-2.3.4 Toolbar for DMS Applications
Each network diagram contains a toolbar, which supports the smooth workflow across
the complete set of DMS applications.
1-2.4 Alarming
1-2.4.1 User Guidance
The user defines the hierarchical relation between the displays by constructed buttons
within the displays and the PAT during configuration time.
In case of abnormal situations, the user is alerted by flashing alarm indicators on the
PAT and guided by them to the next hierarchical display or summary level, until he/she

1-2 Console SCADA
reaches the summary or graphic display with the presentation of the detailed faulty
device causing the alarm condition.
Generic cross associations from message summaries to graphical displays and vice
versa render fast failure tracking down to the alarm source.
1-2.4.2 Alarming in Manned Control Center
Alarms are indicated on:
• the console
– PAT
– Graphic displays (network diagrams)
– Tabular Displays (Runtime Explorer
– Summaries
• the loudspeaker in the control center (audible alarming)
• loudspeakers on other sites (global audible alarming)
Example The following example describes the flow of dialog steps when an alarm arrives in a
control center and the user acknowledges the corresponding alarm:
• The alarm in the control center is presented by
– an audible alarm
– a flashing alarm indicator on the PAT
– a flashing presentation symbol in the network diagram
– an alarm indicator in the substation view of the Runtime Explorer. The

condition ’object in alarm’ is indicated by an A in the first column.
– an alarm indicator in the appropriate Alarm Summary. The condition ’object in

alarm’ is indicated by an A in the first column.
• Click the button Silence on the PAT to switch off the audible alarm.
• Right-click the flashing presentation symbol e.g., in the corresponding network

diagram. The Object menu opens:

SCADA 1-2 Console
This figure shows the Object Menu
Figure 1-2.7: Object Menu
Note
Depending on the type of the selected object a different menu opens.
• Select the menu item Acknowledge Event from the Object menu.
The alarm is acknowledged in the network diagram as well as in the appropriate

Runtime Explorer view and in the Alarm Summary. The presentation symbol stops
flashing and the user is allowed to continue with corresponding control operations
For more information on alarm acknowledgement refer to Chapter 1-7 Manual
Database Manipulations.
1-2.4.3 Wireless Alarming
Alarms may be sent as text messages to mobiles and pagers and to a telephone as
simple voice message.
Note
Only appearing alarms are forwarded by Wireless Alarming. Disappearing alarms are
not considered.
• Activation and deactivation of wireless alarming
Wireless alarming may be (completely) activated or deactivated by clicking the

appropriate PAT button. The activation/deactivation is reported in the General
Summary. The second event to be reported in the General Summary is a failure
while sending the alarm via the specified channel because of technical problems
(e.g. sending the respective SMS failed). The third event to be reported in the
General Summary is that a message is not acknowledged in time.
• Message content
The alarm message may be built up from parts of the alarm information.
• Message filtering

1-2 Console SCADA
Alarms may be filtered by the area of response, alarm priority and alarm category.
Note
In case an acknowledgement does not arrive in time, the Spectrum PowerCC
escalation strategy looks up for the next operator on duty in a prepared standby shift
list and repeats the alarm forwarding. Acknowledgement by phones or mobiles does
not acknowledge an alarm in the corresponding Alarm Summary. It only prevents
forwarding an alarm to the next operator on duty.
The shift plan of a control center (shift team members, etc.) can be configured by the
Shift Plan Editor (Chapter 1-2.4.4 Shift Plan Editor).
1-2.4.4 Shift Plan Editor
The Shift Plan Editor allows the user to configure and update the shift plan, the shift
teams and the appropriate team members. Shift plans can be imported from/exported
to MS EXCEL sheets. The Shift Plan Editor may be invoked by the appropriate PAT
button:
This figure shows the Shift Plan Editor
Figure 1-2.8: Shift Plan Editor
Close Closes the currently selected shift plan.
Export ... Opens the Export Shift Plan dialog (refer to Chapter 1-2.4.4.2 Export Shift Plan
Dialog).

SCADA 1-2 Console
Import ... Opens the Import Shift Plan dialog (refer to Chapter 1-2.4.4.3 Import Shift Plan
Dialog).
Update from DOR ... Opens the Update Shift Plan dialog (refer to Chapter 1-2.4.4.1 Update Shift Plan
Dialog).
Exit Closes the Shift Plan Editor.
1-2.4.4.1 Update Shift Plan Dialog
This figure shows the Dialog Box for Updating the Shift Plan
Figure 1-2.9: Update Shift Plan Dialog
Start/End The user may define the time range in these fields.
OK Creates entries in the shift plan table for the specified time range.
1-2.4.4.2 Export Shift Plan Dialog
This figure shows the Dialog Box for Exporting the Shift Plan
Figure 1-2.10: Export Shift Plan Editor

1-2 Console SCADA
The Export Shift Plan dialog allows to select a path and enter a file name under which
the shift plan shall be stored.
Save Exports the shift plan into the specified EXCEL file. The user may modify the exported
file. The modified file can be imported by using the Import Shift Plan dialog (Chapter
1-2.4.4.3 Import Shift Plan Dialog).
This figure shows the Shift Plan Exported on MS Excel Sheet
Figure 1-2.11: MS Excel Sheet of an Exported Shift Plan

SCADA 1-2 Console
1-2.4.4.3 Import Shift Plan Dialog
This figure shows the Dialog Box for Importing the Shift Plan
Figure 1-2.12: Import Shift Plan Dialog
The Import Shift Plan dialog allows to select a path and a file name from which the shift
plan shall be imported.
Open Imports the shift plan from the specified EXCEL file.
1-2.4.5 Global Audible Alarming
Global Audible Alarming allows activation of alarm devices on different locations in

case of incoming alarms. Alarming hardware connected to an RTU is supported.
Note
Only appearing alarms are processed by Global Audible Alarming. Disappearing
alarms are not considered.
Global Audible Alarming can be completely enabled/disabled via the respective

buttons in the PAT. Alarm devices can be reset either locally or through a control
command initiated by a PowerCC operator.
Global Audible Alarming monitors the status of the alarm devices. It does not send
control commands if the device is already active. If the device is reset Global Audible
Alarming again sends control commands for new incoming alarms.

1-3 Graphic Displays SCADA
1-3 Graphic Displays

Calling up and using graphic displays is described in the Chapter 1-2 Console.
1-3.1 Coloring Schemes

The operator needs information about network energization, network grouping and
other information represented by color code. Spectrum PowerCC provides multiple
coloring schemes for different purposes:
• Network energization
• Voltage levels
• Network groups
• Looped/parallel network components
• Multi/single phase
The coloring schemes can be specified by clicking the appropriate toolbar buttons. For
detailed information on coloring schemes refer to the Chapter 2-3.3 Topological
Network Coloring.

SCADA 1-3 Graphic Displays
1-3.2 Interactive Tracing

This figure shows the Interactive Tracing Function
Figure 1-3.1: Interactive Tracing with the Object Menu and the Trace Menu
The tracing function serves to highlight special network situations. The tracing colors
superimpose the topological coloring schemata.
The trace menu may be selected from the object menu and shows the items as listed
below:
• All connections from selected object upstream
This trace is only possible for objects in a DMS network.

• All connections from selected object downstream

• All connections between two selected objects
This trace can be invoked for objects in DMS networks as well as EMS networks.
• All connections from/to selected object
• All connections from multiple selected objects towards the common injection

• All connections (parallel) from selected object towards multiple injections
• Connection (loop) from one side of selected object to the opposite side of the
same object

1-3.3 Switch-Over to Values of Network Applications Functions in

Graphic Displays
If Network Applications (NA) are available in the system, values of NA functions like
State Estimator or Power Flow can be displayed in network diagrams. A toolbar button
is provided to switch the display from SCADA values to values of the desired NA
function.
The following figure shows the sequence of operating steps for displaying the values of
the Power Flow function in a network diagram.
Figure 1-3.2: Display of NA Values in a Network Diagram
For selecting the NA function whose values shall be displayed in the network diagram
the button TNA has to be pressed. This opens a display with a list of NA functions.
After selection of one function a second display is opened where the desired study
case must be selected (this step is omitted if only one study case is available for the
selected function). Then all values displayed in the network diagram are switched from
the current source to the selected NA function, except for those values that have been
defined as static values. The currently selected source function is displayed in the
window title and is also indicated by a shortcut in yellow borders beside each value.
1-3.4 Trend Control

The Trend Control display allows the user to view and to create 2-dimensional plots
(charts/curves) of existing data values. The user may configure multiple parameters in
order to adapt the Look and Feel of the corresponding chart. Both real-time values and
historical data can be displayed in the Trend Control display. Basically, it is possible to
display up to 40 curves in one chart.
The Trend Control display (Figure 1-3.4) may be invoked by selecting the menu item
’Trends And Charts’ from the PAT menu ’Tools’.
The Trend Control display may be also opened by right-clicking a presentation object
(e.g., an analog value in a network diagram) and selecting the menu item Trending

from the object pop-up menu (Figure 1-3.3). After clicking the this menu item, the
Trend Control display with the appropriate chart is opened. The chart may be modified
by the user.
This figure shows the Selection of the Chart from the Object Popup Menu
Figure 1-3.3: Chart Selection from the Object Popup Menu
This figure shows the Trend Control Display
Figure 1-3.4: Trend Control Display
1-3.4.1 Menubar
The menubar of the Trend Control display includes the following menu titles:
• Chart
• Curve
• Help

1-3.4.1.1 Chart
The Chart menu provides the following menu items:
This figure shows the Chart Menu
Figure 1-3.5: Chart Menu
New Disconnects and deletes all signals, clears the curves and the axes from the chart.
Open Shows a display with the list of available chart configurations stored in the database.
The user may choose a chart configuration from this list.
Save Saves the current chart configuration.
Save as Opens a display which allows to save the current chart configuration under a new
name.
Delete Opens a display which contains a list of all stored curve configurations. One of these
configurations can be selected to be deleted.
Print Prints the current chart on the default printer.
Print to file Opens a display where the user can enter a file name, under which the current chart
configuration shall be stored (in bitmap format).
Properties Opens a display, where the user may edit chart colors and other chart-specific
properties.
Refresh Re-connects all signals in case of a failure.
Exit Closes the Trend Control display.
1-3.4.1.2 Curve
The Curve menu provides the following menu items:

This figure shows the Curve Menu
Figure 1-3.6: Curve Menu
Add Opens the Signal Settings display:
This figure shows the Trend Control Signal Settings Dialog
Figure 1-3.7: Signal Settings Dialog
The user may select an object instance from the instance tree ’Measurement’. The
selected instance is displayed in the input field below the instance tree.
Additionally, the user may select one of the following signal sources for the chart
presentation:
• SCADA
• COP (Current Operating Plan)
If the signal source SCADA has been selected, the user may specify:
• Source type
The user may select one of the following source types:

– History and Real-time
– Historical
– Real-time

– Typical day
• Typical day
In some cases it is necessary to compare values of the current day to some day(s)
in the past. Therefore the Signal Settings display provides the feature ‘Typical
day’. In addition to the current values, the user may select one or more days as
so-called typical days, defining them by the date and the start and end time (e.g.,
date 09/05/2004 6:00 AM to 09/06/2004 6:00 AM) as well as the archiving cycle
and the aggregation.
The user may select a date from the drop-down calendar field. This field is only
enabled, if the user has selected the source type ’Typical day’.
• Aggregation type
The user may select one of the following aggregation types:

– None
– Average
– Maximum
– Minimum
– Timeaverage
– End of interval
• Aggregation cycle
The user may select one of the following aggregation cycles:

– None
– 1 minute
– 3 minutes
– 5 minutes
– 15 minutes
– 30 minutes
– 1 hour
– 1 day
If the signal source COP has been selected, the user may specify:
• Schedule
• Interval (seconds, etc.)
• Number of resolutions
Paste Curve Adds the measurement that has been selected in the network diagram and copied to
the clipboard to the measurement list and adds the corresponding curve to the chart
area.
Edit Signal Opens the Signal Settings display (Figure 1-3.7). The user may edit all signal
properties described above.

Edit Display Opens the Curve Settings display for editing the layout of the currently selected curve:
This figure shows the General tab of the Trend Control Curve Settings display
Figure 1-3.8: Curve Settings Display (General Tab)
The Curve Settings display consists of three tabs: General, Limits and Flood Fill. The
figure above shows the General tab. In this tab the user may edit the curve
presentation properties (line style, color, axis label, axis scaling, etc.) of the current
curve.

The following figure shows the Limits tab of the curve settings display.
Figure 1-3.9: Curve Settings Display (Limits Tab)
In this tab the user can select which limits shall be displayed in the chart area. The list
shows all limits values defined for the selected measurement. One or several limits
can be selected and parameters for the limit line like width and color can be defined.

The following figure shows the Flood Fill tab of the curve settings display.
Figure 1-3.10: Curve Settings Display (Flood Fil Tab)
This tab allows the user to fill the area between the selected curve and another curve
or the x-axis with a selectable color and pattern.
Remove Deletes the current signal and the curve from the chart. If the axis of the curve is
unused, it is also deleted.
1-3.4.1.3 Help
The Help menu includes the menu item About. Clicking this menu item opens an
information display showing the Spectrum PowerCC version number.
1-3.4.2 Chart Area
In this area the selected curves are displayed. The user may change the graphic
representation of the curve(s) using the interactive elements below the chart area.
The vertical chart ruler specifies the instantaneous values of the curves. The
appropriate instantaneous values are displayed in the measurement list (refer to
Chapter 1-3.4.4 Measurement List).

1-4 Tabular Displays (Runtime Explorer) SCADA
The vertical chart ruler may be moved by using the ruler slider above the chart area.
1-3.4.3 Graphic Presentation Control
The user may browse through the chart and zoom in/out the curves using the
appropriate scroll/zoom buttons. The vertical chart ruler can be positioned by
specifying the date/time field ’Cursor’.
The time intervals of the chart can be specified by the fields ’Total Range’. After
clicking the button Apply, the specified time intervals are displayed in the chart.
1-3.4.4 Measurement List
The measurement list shows all appropriate pathnames of the measurement (signal)
instances of the selected curves. Additionally, the list includes the corresponding y-
axis label, the value and quality code as well as the typical day (if it is defined) of the
curve.
1-3.4.5 Status Bar
The status bar shows the chart data processing status (e.g., retrieving data).
1-4 Tabular Displays (Runtime Explorer)
1-4.1 Runtime Explorer Characteristics

The Runtime Explorer is a generic tool showing all real-time data as configured in the
engineering database. The data fields of the Runtime Explorer are currently updated
during runtime, thus providing the same information as for the network diagrams.
Note
If changes have been made in the data model and have been activated, the Runtime
Explorer has to be restarted to make the changes become visible.
Any alarm condition assigned to a network component, is shown in the Runtime

Explorer additionally to the Alarm Summary entry. The user may acknowledge one and
the same alarm condition either in the Runtime Explorer (by using the object menu) or
in the network diagram or in the corresponding Alarm Summary.

SCADA 1-4 Tabular Displays (Runtime Explorer)
Note
Each alarm must be acknowledged once only for all summaries and network
diagrams.
This figure shows the Runtime Explorer with the Switch Device Object Menu
Figure 1-4.1: Explorer View with Switch Device Object menu
The main characteristics of the Runtime Explorer are:
• All open tables are automatically updated in case of network component status
changes or any alarm condition.
• Convenient predefined and ad hoc filters focus the user’s view on the current
working area. Thus, a table of all manually updated values or currently set
markers can be easily obtained.
• No configuration work of the Runtime Explorer is necessary. It is a fully generic

tool, that automatically is defined by the data model.
• The Runtime Explorer appears similar to the familiar Windows Explorer.
– The left part shows the object tree. The object tree comprises all objects
(instances) in alphabetic order. The object tree can be expanded or collapsed
according to it’s hierarchical structure.
– The right part shows the content of the selected objects in a tabular form with
multiple columns. Each column may be sorted by clicking the column header.
• The Runtime Explorer may be invoked by selecting the menu item Runtime
Explorer from the PAT Tools menu.
• The currently displayed table may be printed by clicking the printer symbol on the
toolbar.
• The Runtime Explorer contains a toolbar below the menubar with the following
buttons (from left to right):

This figure shows the Toolbar of the Runtime Explorer
Figure 1-4.2: Runtime Explorer Toolbar
– Ad hoc filter on/off
– Explorer view
– Substation view
– Manual Update Summary
– Application data view, split into DNA and TNA applications
– TCI Summary
– CFE Summary
– OPC Summary
– ICCP Summary
– Marker Summary
– Marker selection pull-down menu, to filter the Marker Summary content
– Print button
1-4.2 Predefined Runtime Explorer Views
1-4.2.1 Explorer View
This figure shows the Explorer View of the Runtime Explorer
Figure 1-4.3: Explorer View
The table (right pane) shows all underlying objects that are assigned to the selected
object in the object tree.
The Explorer view may be invoked by clicking the appropriate Runtime Explorer
toolbar button.
The benefit of the Explorer view is the validation of the correct data model structure,
e.g., after a data error is logged.

1-4.2.2 Substation View
This figure shows the Substation View of the Runtime Explorer
Figure 1-4.4: Substation View
The table (right pane) shows current states and values of all underlying objects that
are assigned to the selected object in the object tree.
The Substation view may be invoked by clicking the appropriate Runtime Explorer
toolbar button.
The benefit of the substation view is to get the same process information (without
topology) as usually by graphic diagrams only, however with no construction effort.
The user may update, control and acknowledge alarms by selecting the appropriate
menu items from the object menu as used for graphic diagrams.
1-4.2.3 Marker Summary
This figure shows the Marker Summary View of the Runtime Explorer
Figure 1-4.5: Marker Summary
The table (right pane) shows all currently set markers of all objects that are assigned to
the selected object in the object tree.
The Marker Summary view may be invoked by clicking the appropriate Runtime
Explorer toolbar button.
The Marker Summary can be filtered according to the marker types, as shown in the
marker type menu of the Runtime Explorer toolbar.
The benefit of the Marker Summary is to get a fast and complete overview in one
single table over the currently set, scattered markers in the whole network.

1-4.2.4 Manual Update Summary
This figure shows the Manual Update Summary View of the Runtime Explorer
Figure 1-4.6: Manual Update Summary
The table (right pane) shows all current manual updates of all objects that are
assigned to the selected object in the object tree, e.g. a substation.
The Manual Update Summary view may be invoked by clicking the appropriate
Runtime Explorer toolbar button.
The benefit of the Manual Update Summary is to get a fast and complete overview in
one single table over the currently set, scattered values in the whole network. The
quality code of the manually updated values is entered and not updated as displayed
in the source quality column.
1-4.2.5 CFE View
This figure shows the CFE View of the Runtime Explorer
Figure 1-4.7: CFE View
The CFE view shows that subset of objects, whose values are acquired by the CFE
from the field. The table provides the following tab pages:
• Single
• Summary
• Failures
The CFE view may be invoked by clicking the appropriate Runtime Explorer toolbar
button.

For detailed information on CFE refer to the document “Spectrum PowerCC CFE
Reference Guide“.
1-4.2.6 ICCP View
This figure shows the ICCP View of the Runtime Explorer
Figure 1-4.8: ICCP View
The ICCP view provides the following tab pages:
• ICCP Main Display
Shows the ICCP subsystem´s overall administrative and operational status and
the administrative and operational status for each ICCP remote. It provides the
user with the capability to enable/disable ICCP and to connect/disconnect with the
listed remote systems.
• ICCP Detail Display
Shows the operational status of each ICCP link with the remote system.
• ICCP DataSet Display
Shows the administrative and operational status of transfer groups for the
selected remote control center.
The ICCP view may be invoked by clicking the appropriate Runtime Explorer toolbar
button.
For detailed information on ICCP refer to the document “Spectrum PowerCC ICCP
Reference Guide“.
1-4.2.7 OPC View
The OPC view is similar to the CFE view.

1-4.3 Ad Hoc Defined Runtime Explorer Views

The user may - additionally to the predefined filters - define ad hoc filters for further
limitation of the displayed information to best fit to the current area of interest.
The filter dialog may be invoked by clicking the menu item Filter of the View menu.
After a corresponding filter has been defined and saved, this filter may be switched on
or off by the appropriate Runtime Explorer toolbar button.
This figure shows the Filter Button
Figure 1-4.9: Filter Button (On/Off)
The ad-hoc filter may be applied on the Explorer view, the Substation view and the
Manual Update Summary.
The filter criteria may be applied on names, field resources and measurements.
This figure shows the Dialog Box Where the Filter Criteria (Search String) is Specified
Figure 1-4.10: Searching For a String (e.g., Status)
The user may enter the text string into the input field ’Name’. The wildcard character ’*’
facilitates searching in groups. The text string may be also entered by Copy & Paste
from the object tree.
The following example shows how to filter for measurements of a specific network
component (field device):

This figure shows How to Filter for Measurements of a Specific Network Component
Figure 1-4.11: Searching For a Network Component (e.g., Switch)
Single or multiple filter criteria selection is possible. After applying the filter in the
example above, all switch devices with all their child objects (derived switch types like
disconnector, load isolator, breaker, etc.) are presented.
The third tabbed page ’Measurement’ allows the user to filter for specific measurement
types, values and quality codes (allows multiple selection).

This figure shows the Measurement Filter
Figure 1-4.12: Measurement Filter
Advanced filtering can be achieved by expert filters. They can be selected by clicking
the button ’Advanced’.

Expert filters focus on value range and time range.
This figure shows the Value and Time Range Expert Filter
Figure 1-4.13: Value and Time Range Expert Filter
1-4.4 Context Menu

The Runtime Explorer provides a context-sensitive object menu for the following
views:
• Explorer view
• Substation view
• Manual Update Summary view
The object menu may be opened by right-clicking the desired instance in the instance
tree of the Runtime Explorer. Depending on the selected instance a different menu
opens.
Figure 1-4.14 shows the switch device object menu of a selected measurement of the
type ‘Valve’:

Figure 1-4.14: Switch Device Object Menu (Measurement Type 'Valve')
Clicking e.g., the menu item ’Open Close Stop’ on the switch device object menu
opens the Valve Control dialog:
This figure shows an Example of a Valve Control Dialog
Figure 1-4.15: Example of a Valve Control Dialog
The Valve Control dialog allows the user to control specific network components (e.g.,
valves), where multiple switch commands (e.g., ’Open’, ’Close’ or ’Stop’) are required.
In the table of the Valve Control dialog all possible state changes (via supervisory
control action controllable state changes) of all measurements configured as children
of the selected instance are listed in a tabular form.
Operate Executes the selected control command. This button is only enabled, if the user has
selected a control item from the list.
Note
Only one control item can be selected.

SCADA 1-5 Message Summaries
Cancel Closes the Valve Control dialog.
View Shows either all interlocking rules or all currently violated interlocking rules of the
current object.
Note
The Valve Control dialog is expanded to show the list of interlocking rules/violations, if
the user has selected the button View or if interlocking violations are returned when a
control command has been executed.
Unlock If an interlocking rule is defined as ’overrideable’, the user may override the rule.
Clicking the button Unlock enables the button Operate. The user may retry to execute
the control command.
For more information on the provided object menu items (Control State, etc.) refer to
the Chapter 1-6 Supervisory Control and the Chapter 1-7 Manual Database
Manipulations.
1-5 Message Summaries
1-5.1 General Summary

The General Summary provides the following characteristics:
• Spectrum PowerCC is delivered with one single General Summary. It is possible

to configure more than one General Summary.
• The summary content is automatically filtered according to the area(s) of

responsibility that is (are) assigned to the logged-on user.
• The summary content may be filtered by applying predefined filters (path, priority,
category). A filter specific label (e.g. substation A) is displayed on the summary
call up buttons.
• Inserting of the next incoming event:
– The next event is added as a message line on top or bottom (the user
decides by clicking on the time stamp column header) of the summary. No
sorting is necessary, the events are ranked according to their arrival time.
This is the preferred method because of performance reasons.

1-5 Message Summaries SCADA
– The next event is inserted into the summary according to it’s time stamp.
One of these two methods has to be configured.

• The new event is entered into the message archive (in addition to the summary)
and sorted according to the event’s time stamp.
• The new event is entered into all alarm summaries and - in case it differs from the
normal state - into the Abnormal Status Summary.
• The message entry is a single line text string. The constituting text string portions
are inserted into configurable columns.
• The summary may be invoked by clicking the appropriate PAT button.
• The summary content may be scrolled up and down.
• The summary content may be moved up and down (in page steps) or to the first/
last page by clicking the appropriate toolbar buttons.
• The user may decide to select the General Summary from the message archive or
from the flat list file (archive cache for performance reasons). The flat list file
contains only the most recent portion of the message archive and is organized as
a rotating buffer.
• The summary may be printed by clicking the appropriate toolbar button.
• The user may narrow or extend the column width to best fit text string length to
window size.
• The user may sort column content alphabetically by clicking the column header.
This figure shows the General Summary Selected from the Message Archive
Figure 1-5.1: General Summary
Right-clicking a message line opens the General Summary pop-up menu:

This figure shows the Popup Menu of the General Summary
Figure 1-5.2: General Summary Popup Menu
Callup Display Opens the appropriate graphic diagram (if it exists, with centered network component
as given by the message line entry).
Add/View Comment Opens the Comment dialog:
This figure shows the Comment Dialog
Figure 1-5.3: Comment Dialog
Comment Displays all user comments.
New Comment The user may enter a new comment into this input field. The maximum length of the
comment is 500 characters. The current number of characters is displayed in the
status bar of the dialog.
Add Adds the entered comment to the selected message. An indication string, e.g. ‘CO’,
the name of the user as well as the current time stamp is automatically added to the
new comment.
Note
Comments can be only added, if the user has modify access right for ‘Network
Management’.

Cancel Closes the Comment dialog.
1-5.2 Alarm Summaries

The Alarm Summaries provides the same characteristics as the General Summary
with the following exceptions and additions:
• Spectrum PowerCC is delivered with as many alarm summaries as helpful.
• Alarms are not archived. Therefore, Alarm Summaries are flat files only. The
summary length is restricted by a configurable number of alarms.
• The message line shows an additional acknowledgement indicator (column ACK).

The indicator A disappears, after the user has acknowledged this alarm.
• Each alarm must be acknowledged by the user. Each acknowledgement is

entered as an event into the General Summary. For more information on
acknowledgement refer to the Chapter 1-7 Manual Database Manipulations.
• Acknowledgement is combined with a compressing algorithm of the Alarm

Summaries. After all alarms have been acknowledged, the Alarm Summary
shows only the abnormal (alarm) status entries.
• One alarm can overwrite each other alarm.
• Group alarms can be configured for categories (e.g., ’Category1’), areas (e.g.
‘Sub A’) and the combination of category and area (e.g., ’Category1’ in ‘Sub A’).
For more information on the configuration of group alarms refer to the Chapter
2-4 Message Summaries .
This figure shows the Alarm Summary
Figure 1-5.4: Alarm Summary
Right-clicking a message line opens the Alarm Summary pop-up menu:

This figure shows the Popup Menu of the Alarm Summary
Figure 1-5.5: Alarm Summary Popup Menu
Acknowledge Acknowledges the corresponding message entry.
Callup display Described in Chapter 1-5.1 General Summary.
Add/View Comment Described in Chapter 1-5.1 General Summary.
Clear Removes the corresponding alarm message entry. This menu item is only enabled, if
the alarm is of the message class ‘AaCl’.
Delete Removes the corresponding alarm message entry. This menu item is only enabled, if
the user has modify access right for ‘System Administration’ (refer to the document
“Spectrum PowerCC System Management Reference Guide”).
1-5.3 Alarm Test Summaries

During commissioning and revision work, the equipment at site must be tested under
operational conditions. This means that the whole way from the network component
outside till the data processing in the control center must be tested and documented.
This work may be done in parallel with the normal operational work.
The (test) messages are displayed in Alarm Test Summaries without alarming and
archiving. After finishing the test operation the corresponding Alarm Summary can be
saved to document the commissioning or revision work. Afterwards the user may clear
the content of the Test Summary by clicking the appropriate toolbar button:

This figure shows the "Clear Summary" Toolbar Button and the Confirmation Dialog
Figure 1-5.6: Toolbar Button "Clear Summary" and Confirmation Dialog
Note
The toolbar button “Clear Summary” is only enabled, if the user has modify access
rights for ’Network Management’ (refer to the document “Spectrum PowerCC System
Management Reference Guide”).
1-5.4 Abnormal Status Summary

The Abnormal Status Summary provides the same characteristics as the General
Summary with the following exceptions and additions:
• The summary entries are organized in a flat file. The summary length is defined by
a configurable number of summary entries.
• Each abnormal event is entered into the summary. The corresponding normal
event removes the abnormal summary entry.
• The summary contains the abnormal states:
– Alarm state of general events, protection devices, housekeeping events, etc.
– Abnormal switch status, that is the contrary of the normal switch state as
defined in the engineering database.
– Analog values out of normal range as defined by the operating limits.

This figure shows the Summary of the Abnormal Status
Figure 1-5.7: Abnormal Status Summary
1-5.5 Operator Notepad

The operator notepad is based on a marker summary. Its layout is similar to that of an
alarm summary, but the operator notepad has additional columns and toolbar buttons
that are intended for the handling of markers. The following additional columns are
available in the operator notepad:
• Description
• History
• Reminder
• Title
For the handling of markers the following additional toolbar buttons are provided:
• Edit a note
• Acknowledge an expired reminder
• Create a general note
• Delete a marker
This figure shows an example of the operator notepad.
Figure 1-5.8: Operator Notepad
A right-click on a line in the operator notepad opens the following pop-up menu:

The following figure shows the pop-up menu of the operator notepad.
Figure 1-5.9: Operator Notepad - Pop-up Menu
Callup Display Described in Chapter 1-5.1 General Summary.
Add/View Comment Described in Chapter 1-5.1 General Summary.
Copy Copies the selected line.
Edit Note Opens the note display where the note data of the selected marker can be edited.
Acknowledge Reminder Acknowledges an expired reminder of a marker.
Create General Note Opens the note display where the data for a new general note can be entered.
Delete Marker Deletes the selected marker.
1-5.6 Filtering of Message Summaries

The user may define filter criteria to display only specific messages in the
corresponding message summary. These filter criteria can be defined in the Filter
configuration dialog. The Filter configuration dialog may be invoked by clicking the
appropriate toolbar button of the corresponding message summary.

This figure shows the Filter Configuration Dialog
Figure 1-5.10: Filter Configuration Dialog
1-5.6.1 Menubar
The menu Filter contains the following menu items:
New Creates a new filter. The selected filter is cleared and a default name ‘NewFilter’ is
inserted into the combo box ’Filter Name’.
Save Saves the current filter. If no filter name is specified, the Save Filter As dialog opens:

This figure shows the Dialog Box for Saving the Filter
Figure 1-5.11: Save Filter as Dialog
The user may enter a filter name into the input field ’Filter Name’. After clicking the
button Save, the filter is saved with the specified filter name.
Save As... Opens the Save Filter As dialog described above.
Delete Clears the current filter and removes the corresponding AlarmControlFilter instance.
After the menu item Delete was selected, a confirmation dialog opens asking the user
for confirming the deletion process.
Clear Resets all filter criteria fields.
1-5.6.2 Header
File Name The user may select a filter from this combo box. In case of creating a new filter, the
user may enter the filter name into this field.
Description The user may enter a comment for the specified filter into this input field.

1-5.6.3 Tabbed Pages
1-5.6.3.1 Date and Source Page
This figure shows the Date and Source Page
Figure 1-5.12: Date and Source Page
Data Source The user may select the data source (Alarm System or Alarm Archive) from this drop-
down list.
After selecting the data source, the user may choose one of the following kinds of time
range restriction to display messages within a specified time range.
Range From/To The user may specify the start date/time and the end date/time.
Last The user may specify the last specified number of days/hours/minutes.
No date range There are no time range restrictions. This is the default setting.
restrictions

1-5.6.3.2 Path Page
This figure shows the Page where the Path Filters may be Defined
Figure 1-5.13: Path Page
For each path column two filter criteria may be defined. The filter criteria can be linked
by a logic ‘And’ or ‘Or’.
In this example, the user searches for all messages of the substation name ‘sub a’ or
‘sub b’, where the bay name contains the strings ‘trafo’ and ‘a2’.
1-5.6.3.3 Advanced Page
This figure shows the Page where Advanced Filters may Be Defined
Figure 1-5.14: Advanced Page

Cat/Prio/MsgCl The user may select corresponding criteria for
• Category
• Priority
• Message class
from these list fields. Multiple items can be selected from one list.
Value, Ind (Indicator), The user may enter corresponding criteria into these input fields.
Comment, Status, User,
Console. In the example above, the user searches for all messages with ‘Priority 1’ or ‘Priority 2’
and where a comment is existing.
Acknowledged The user may search for acknowledged alarms (‘Yes’ is checked) or not acknowledged
alarms (‘No’ is checked).
1-5.6.4 Buttons
Activate Applies the filter configuration changes. After clicking the button, the Filter
configuration dialog is closed and the appropriate Filter On/Off toolbar button is
switched on.
Note
The button Activate is only enabled, if the filter is switched off.
OK Applies the filter configuration changes and closes the Filter configuration dialog.
Note
The button OK is enabled as soon as a filter criterion field has changed.
Cancel Closes the dialog without applying changes.
Apply Applies the filter configuration changes and applies the new filter criteria to the
summary, if the filter is already switched on.
Note
The button Apply is enabled as soon as a filter criterion field has changed.
An activated filter is visualized by the following effects in a message summary:
• The Filter On/Off toolbar button is pressed.
• The color of the table grid frame is yellow.
• The filter name is displayed in the status bar. If no filter name is specified, the text
‘Temporary filter’ is displayed.

1-6 Supervisory Control SCADA
• If the message summary shows data from the alarm archive, the additional
archive icon is displayed in the right corner of the status bar (Figure 1-5.1).
1-6 Supervisory Control
1-6.1 Object Selection

Supervisory control can be done on a selected object within a graphic display (network
diagram) or a tabular display (Runtime Explorer). Supervisory control is performed as
a sequence of several steps:
• Selection of the object by a left-click.
• Selected object is surrounded with a dashed rectangle.
• Selection of the object menu by right-clicking the corresponding object. The object
menu is context-sensitive and shows the methods currently applicable on the
selected object. The object menu is bound to the selected object. Underlying
submenus can freely be moved across the window.
This figure shows the Switch Device Object Menu
Figure 1-6.1: Switch Device Object Menu

SCADA 1-6 Supervisory Control
This figure shows the Analog Value Object Menu
Figure 1-6.2: Analog Value Object Menu
• The corresponding object can be selected on multiple consoles. However, trying

to apply one of the methods, is rejected on all other consoles.
• The control sequence can be interrupted at any step.
1-6.2 Single Control

The user selects an object (left-click) and the object menu (right-click) and the menu
item ’Control State’ from the object menu (left-click).
The Control dialog opens adjacent to the selected object. The object is surrounded by
a dashed rectangle and is ready for control.

This figure shows the Control Dialog Adjacent to the Selected Object
Figure 1-6.4: Selected Object with the Assigned Control Dialog
Depending on the selected network component, one of the following control dialogs
opens:
• Control dialog of a switch:
This figure shows the Switch Command Control Dialog
Figure 1-6.5: Switch Command Control Dialog
The drop-down list ’Control to’ shows the expected status (Open or Close), which
usually is the opposite of the current switch state.
• Control dialog of a step position device:

This figure shows the Step Up/Down Control Dialog
Figure 1-6.6: Step Up/Down Control Dialog
The current value can be specified by clicking the desired direction.
• Control dialog of a regulating device:
This figure shows the Regulating Device Control Dialog
Figure 1-6.7: Continuous Command Control Dialog with Interlocking Rules Field
The current value can be specified by clicking the desired direction.
• Control dialog for a setpoint:

This figure shows the Setpoint Control Dialog
Figure 1-6.8: Setpoint Control Dialog
The setpoint may be adjusted by a slider.
• Control dialog for manual updating:
This figure shows the Dialog for Manual Update
Figure 1-6.9: Manual Update Dialog
The value may be adjusted by a slider.
Each control action is monitored for time out. In case, that the target is not achieved in
time, the supervisory control application stops the control sequence with a hint.
Supervisory control considers the following special cases:
• The current switch status can be sent out as the desired control target.
• A setpoint can be sent.
Example The following example describes the flow of dialog steps when the user controls the
state of a switch (e.g., a circuit breaker) in a network diagram:
• Right-click the desired circuit breaker in the corresponding network diagram. The
Switch device object menu opens:

• Select the menu item Control State from the Switch device object menu. The
switch control dialog opens:
This figure shows the Assigned Control Dialog with the Selected Circuit Breaker
Figure 1-6.11: Selected Circuit Breaker with the Assigned Control Dialog
• Select the state Open from the drop-down list ’Control to’ and click the button
Operate. The selected circuit breaker is opened. The presentation logic of the
circuit breaker changes to the state ’Open’ in the network diagram:
This figure shows the Opened Circuit Breaker
Figure 1-6.12: Opened Circuit Breaker

Note
Interlocking conditions may block the control of network components (refer to Chapter
1-6.3 Interlocking Conditions)
1-6.3 Interlocking Conditions

During a supervisory action, all general, topological and special interlocking conditions
are checked. In case, at least one condition is violated, the next step is rejected, and
the interlocking condition dialog opens:
This figure shows the Interlocking Condition Dialog
Figure 1-6.13: Interlocking Conditions Dialog
View button Displays the violated interlocking conditions and the current rules.
In case, that the violated condition is configured as a ’soft’ condition, that can be
bypassed, the user may unlock the interlocking condition by clicking the button
’Unlock’ and continue with the control action.
1-6.4 Switching Sequence

The individual switching sequence is recorded and executed by the Switching
Procedure Management (SPM). For more information on SPM refer to the document
“Spectrum PowerCC Switching Procedure Management Reference Guide“.

SCADA 1-7 Manual Database Manipulations
1-7 Manual Database Manipulations

In opposition to supervisory control, the manual database manipulations have no
impact on the real field. They modify values and states in the real-time database.
1-7.1 Marking and Tagging

Markers and tags identify network components for special processing. Network
component might be switches, lines, data points, protection relays, etc. Any marker or
tag is attached to a presentation object in the corresponding tabular or graphic
displays.
The Apply Marker dialog (Figure 1-7.2) may be invoked by selecting the menu item
Apply Marker of the Switch device object menu:
The apply marker dialog allows to select an existing marker or to create a new one.

1-7 Manual Database Manipulations SCADA
This figure shows the dialog for applying a marker
Figure 1-7.2: Apply Marker Dialog
For each marker additional information can be entered. When the button Edit Note is
clicked, a display for entering note data is opened.

The following figure shows the display for entering new and modifying existing note
data
Figure 1-7.3: Note Display
In the note display a note title and a description can be entered. Additionally a
reminder can be set. This display also shows the history of the marker (when it was
created and modified) as well as the descriptions that have been entered for this
marker before.
Marked objects can be easily distinguished from non-marked ones by a predefined

character in one of the 4 corners around the network component symbol.

This figure shows the Breaker with Set Marker
Figure 1-7.4: Breaker with Set Marker 'Control Inhibit'
All currently set markers of the field are displayed in the so-called operator notepad, a
marker summary, which can be opened using the corresponding button in the PAT.
Applying and removing of a marker is entered into the General Summary and the
message archive. The message includes the user’s acronym.
Some marker types are considered as interlocking condition for supervisory control.
Those markers are called ’tags’.
Applying a marker is possible for more than one marker at a time. The Apply Marker
dialog is applied on all selected objects.
This figure shows the Selection of Multiple Objects
Figure 1-7.5: Multiple Object Selection
1-7.2 Manual Updating

The user may select the manual update dialog by clicking the menu item Manual
Update or Manual Override on the Switch device object menu (Figure 1-7.6). The
manual update dialog content is context-sensitive. There is a different content for an
analog and digital value (refer to Figure 1-7.7 and Figure 1-7.8).

This figure shows the Switch Device Object Menu - Manual Update
’Manual Override’ updates not only the analog or digital value, but implicitly applies the
marker ’Blocked’ (removed from operation) to the object. This means, if the real-time
data acquisition still works for this object, this object is not automatically updated by
the real field value. The manual value is kept until the user removes the marker.
A manually updated value is overwritten by the real field value as soon as data
acquisition of this data point starts. In opposition to the override procedure, a manually
updated value is not removed from operation automatically.
This figure shows the Digital Value Dialog - Manual Update
Figure 1-7.7: Digital Value Manual Update Dialog

This figure shows the Analog Value Dialog - Manual Update
Figure 1-7.8: Analog Value Manual Update Dialog
The analog value can either be specified by the slider or by entering the value into the
input field ’Set to’.
In case, that no update time is entered by the user, the current system time is assumed
as the update time of the status or value. Otherwise the manually entered time is
assumed as the update time.
The manual updating activity is entered into the General Summary and the Message
Archive. The message includes the user’s acronym.
Manual update is possible for more than one object at a time. The update dialogs are
applied on all selected objects.
1-7.2.1 Manual Updating without Manual Update Dialog
If one element of type "switch" or "digital measurement" is selected with the right
mousebutton, the object menu additionally contains a menu item that allows to
manually update the element state immediately without further operator input.
The following figure shows an example for an object menu for a switch device with the
menu item "Manual Update Toggle"
If the menu item "Manual Update Toggle" is selected, the manual update is performed
after selection of the menu item without displaying an additional manual update
display.

Note
If the current state of the selected element is "disturbed" or "intransit", the
corresponding manual update display is opened as described before. The same
applies if an interlocking condition occurs.
1-7.3 Sound Switch Off

This figure shows the Buttons on PAT for Switching the Sound ON or OFF
Figure 1-7.10: PAT Buttons 'Silence' and 'Audio Inhibit'
Clicking the button Silence switches off the current sound of the console’s
loudspeaker.
Clicking the button Audio Inhibit cuts off the loudspeaker for all future alarms (mute
function) until the user clicks the same symbol again.
1-7.4 Alarm Acknowledgement

The user commits to take counter actions against the abnormal situation by
acknowledging the alarm. Typically, the user switches off the sound prior to alarm
acknowledgement.
An alarm is presented to the user by:
• an audible alarm.
• a flashing alarm indicator on the PAT.
• a flashing presentation symbol in the network diagram.
• an alarm indicator in the substation view of the Runtime Explorer. The condition
’object in alarm’ is indicated by an A in the first column.
• an alarm indicator in the appropriate Alarm Summary. The condition ’object in

alarm’ is indicated by an A in the first column.
One and the same alarm may be entered into one or more summaries, graphic
displays and tabular displays. The alarm can be acknowledged either in the Alarm
Summary, in the Runtime Explorer or in the graphic displays. The acknowledgement in
the Alarm Summary causes the acknowledgement in all graphic and tabular displays
at the same time and vice versa.
The figure below shows how to acknowledge a single selected alarm in the Alarm
Summary.

This figure shows the Popup Menu for Handling Alarm
Figure 1-7.11: Alarm Handling Menu in an Alarm Summary
The following menu is used to acknowledge an alarm in a graphic display as well as in

the Runtime Explorer:
This figure shows the Switch Device Object Menu - Acknowledge Event
Acknowledgement is possible for more than one object at the same time. It is applied
on all selected objects (multiple objects in graphic displays or a block of adjacent lines
in the Alarm Summary). A whole Alarm Summary page (the visible part) can be
acknowledged by clicking the appropriate acknowledgement button on the toolbar of
the Alarm Summary.
Any acknowledgement action is entered into the General Summary and the Message
Archive. The message includes the user’s acronym.
1-7.5 Dynamic Limits

The user may define analog limit values directly in network diagrams. Right-clicking
the corresponding analog value opens the Analog value object menu:

This figure shows the Analog Value Object Menu
Figure 1-7.13: Analog Value Object Menu
Clicking the menu item Dynamic Limit opens the Dynamic limit dialog:
This figure shows the Dynamic Limit Dialog
Figure 1-7.14: Dynamic Limit Dialog
The dynamic limit dialog allows the user to create a new dynamic limit or to reset a limit
value to the default value. The user may select the corresponding limit from the drop-
down list Selected Limit, enter the new limit value into the field New Value and click the
button OK to activate the new limit value. The new limit value may be reset to the
default value by clicking the button Reset To Default.
Default limits can be configured in the Information Model Management.
1-7.6 Manual Limit Sets

In the Information Model Management it can be configured whether seasonal limit sets
shall be applied (the limit sets become active during a certain configured time period)
or whether manual limit sets shall be used. In this case limit sets can be activated
manually. For this purpose the user opens the Limit Set Display via the corresponding
button in the PAT.

This figure shows the display for selecting a manual limit set.
Figure 1-7.15: Limit Set Display
This display shows the currently active limit set as well as a list of all defined limit sets.
From the drop-down list the user can select a new limit set.
Limit sets can be configured in the Information Model Management.
1-7.7 Message Comment

Each message entry of the General Summary or the Alarm Summary may be
commented by the user by using the Comment dialog (refer to the Chapter
1-5 Message Summaries). The Comment dialog may be invoked by selecting the
menu item Add/View Comment from the General Summary or Alarm Summary pop-up
menu.
This figure shows the Popup Menu for the Alarm Summary
Figure 1-7.16: Alarm Summary Popup Menu
The opened Comment dialog allows the user to enter, to view and to modify the
comment. The comment length is not limited. The comment is inserted into the
comment column.

SCADA 1-8 Report Generator
This figure shows the General Summary Showing the Comment Column
Figure 1-7.17: General Summary showing Comment Column
Each comment is entered into the Message Archive.
1-7.8 Substation Request (Substation Scan)

The CFE automatically executes a general request to provide an up-to-date real-time
database regarding network component states.
1-8 Report Generator

The Report Generator provides the creation of reports. A report is a collection of data
organized in a tabular form.
A report is defined by:
• the data source

• the data range within the data source (selected column and filter)

1-8 Report Generator SCADA
• the template that defines the structure and the layout of the printable form. The
template contains name plates, headers and fixed test strings.
The Report Generator may be invoked by selecting the menu item Report Generator
from the PAT Tools menu:
This figure shows the Report Generator Invoked from PAT
Figure 1-8.1: Report Generator
The user may select the data source on the List pane of the Report Generator. In the
example above the HIS data source was selected.
The Tree pane shows all the available report templates (views) for the selected data
source (e.g., HIS data). The templates are predefined MS EXCEL sheets.
Clicking a template shows the available columns (of the appropriate report) in the
Work pane of the Report Generator:

This figure shows the Available Columns of a Report in the Work Pane of the Report
Generator
Figure 1-8.2: Report Generator (displaying the columns for the report 'HIS 15 min
Detail')
The user may modify the selected report template.
The following parameters may be specified:
• Show/hide a column
• Column filter criteria
Clicking the corresponding filter symbol in the report template opens a filter crite-
ria dialog. The user may specify filter criteria (e.g., ’equal’, ’greater’ or ’begins
with’) for the corresponding column.
• Column header name
The modified template can be saved by clicking the button Save.
Report Generation The user may create the report (MS EXCEL sheet) by the following steps:
• Right-click the corresponding report on the Tree pane of the Report Generator.
The Tree pane report pop-up menu opens:

This figure shows the Report Popup Menu (Tree Pane)
Figure 1-8.3: Tree Pane Report Popup Menu
• Select the menu item Generate from the Tree pane report pop-up menu. The
appropriate MS EXCEL sheet opens and displays the specified columns:
This figure shows a Report Generated on MS Excel Sheet
Figure 1-8.4: Example of a Report Generated on MS Excel Sheet
A report may be created either manually by the user or automatically on a periodic

base. For this scheduling task, the standard Windows scheduler is provided. The
following example shows how to run a report each day at 11:50.

This figure shows the First Step of the Scheduling Task Wizard
Figure 1-8.5: Scheduled Task Wizard, Step 1
This figure shows the Second Step of the Scheduling Task Wizard
Figure 1-8.6: Scheduled Task Wizard, Step 2
1-8.1 Configure a New Report

This example describes the flow of dialog steps when the user configures a new report
view (e.g., for HIS data):
• Open the Report Generator by selecting the menu item Report Generator from the
PAT Tools menu.

• Select the data source HIS in the List pane of the Report Generator. The available
HIS reports/report views are displayed in the Tree pane of the Report Generator:
This figure shows the Available Reports/Views in the Tree Pane of the Report
Generator
Figure 1-8.7: Tree pane of the Report Generator
• Right-click the report folder symbol. The Tree pane folder pop-up menu opens:
This figure shows the Popup Menu for Folders in the Tree Pane
Figure 1-8.8: Tree Pane Folder Popup Menu
• Click the menu item Add report on the Tree pane folder pop-up menu. The New
Report dialog opens:
This figure shows the Dialog Box for New Report
Figure 1-8.9: New Report Dialog
• Enter the name of the new report into the input field and click the button Ok. The
new report is displayed in the Tree pane:

This figure shows the new report in the tree pane of the Report Generator
Figure 1-8.10: Tree pane of the Report Generator (displaying the new report 'My
Report')
• Right-click the new report. The Tree pane report pop-up menu opens:
This figure shows the Popup Menu for the Report in the Tree Pane
Figure 1-8.11: Tree Pane Report Popup Menu
• Click the menu item Add view on the Tree pane report pop-up menu. The Base
View Selection dialog opens in the work pane of the Report Generator:

This figure shows the Dialog for Base View Selection
Figure 1-8.12: Base View Selection Dialog
• Select a base view from the available view list, e.g., ’Markers’ and click the button
Ok. The Report View Question dialog opens:
This figure shows the Question Dialog for Report View
Figure 1-8.13: Report View Question Dialog

• Click the button Yes. The New Report View dialog opens:
This figure shows the Dialog for New Report View
Figure 1-8.14: New Report View Dialog
• Enter the name of the new report view into the input field and click the button Ok.
The new report view is displayed in the Tree pane:
This figure shows the New Report View in the Tree Pane of the Report Generator
Figure 1-8.15: Tree Pane of the Report Generator (displaying the new report view ’My
new view’)
• Select the new report view. The View configuration dialog opens in the Work pane
of the Report Generator:

This figure shows the Dialog for Viewing the Configuration
Figure 1-8.16: View Configuration Dialog
• Modify the specified view. For instance, select the column headers ’Time stamp’,
’Value MIN’ and ’Value MAX’ and deselect the remaining items.
Only the selected column headers are displayed in the generated MS EXCEL
sheet.
• Click the button Save. A confirm dialog box opens.
• Click the button Yes to save the modified report view.
• Right-click the new report in the Tree pane of the Report Generator. The Tree
pane report pop-up menu opens.
• Click the menu item Generate on the Tree pane report pop-up menu. The
corresponding report is generated and the appropriate MS EXCEL sheet opens.

Volume 2 Engineering
2-1 Introduction
Most of the Spectrum PowerCC SCADA operation functions, described in Volume 1,
can be configured by using the Information Model Management (IMM) as described in
the Volume 2. It is assumed that the reader of this document is familiar with the
following general IMM characteristics:
• Domain Object Model (DOM)
• Job Management
• IMM instance tree concept
• Data entry, data validation, data activation
• Creation of data types, instances, attributes and associations
For more information on data modelling refer to the documents “Spectrum PowerCC
Information Model Management Reference Guide“ and “Spectrum PowerCC Data
Model Reference Guide“.

Note
Usually modifications of the data model immediately become active after activation of
the corresponding job. But some data changes need a restart of the PowerCC system
before they become active: e.g.: global parameters of the alarm system as well as
sounds.
Audience The Engineering Volume has a similar structure as the Operations Volume. The
engineering tasks are assigned to the corresponding SCADA functions. The audience
of Engineering Volume are data engineers.
2-1.1 Information Model Management

The Information Model Management provides the Information Model Manager (Figure
2-1.1) to control all data entry and engineering activities of the system. The Information
Model Manager may be invoked by selecting Start > Spectrum PowerCC > Information
Model Manager from the MS Windows Start menu or by selecting the appropriate
menu item from the PAT System menu.
This figure shows the Job Management Window in the Information Model Manager
Figure 2-1.1: Information Model Manager showing the Job Management Window
To create or edit instances, a job must be loaded on the system. The user may create
a new job or select an existing one.
Note
The instances of the job ’Real-time (RT)’ can not be modified. This job contains the
instances of the real-time system.
The following example describes the flow of dialog steps when the user creates a new
job in the IMM.
• Right-click the overview pane item ’Real-time (RT)’ in the Job Management
window. The New Job pop-up menu opens:

This figure shows the Popup Menu for the New Job
Figure 2-1.2: New Job Popup Menu
• Left-click the pop-up menu item ’New Job’. The Create New Job dialog opens
(Figure 2-1.3).
• Enter a new job name into the input field ’Job Name’ and a comment into the input
field ’Job Description’ (optional).
This figure shows the Dialog for Creating a New Job
Figure 2-1.3: Create New Job Dialog
• Click the button OK.
The first-level instances of the selected job are displayed on the overview pane of
the Information Model Manager:

This figure shows the First Level Instances of the Selected Job
Figure 2-1.4: Example of First Level Instances
The SCADA data are covered by the following instances:
• Network: Real-time data description
• Presentation: PAT and graphical displays
• General: SCADA methods
Note
To make data modification available for the real-time system, the user must activate
the corresponding job. For more information on job activation refer to the document
“Spectrum PowerCC Information Model Management Reference Guide“.
2-1.2 Configuration of Real-time Data
2-1.2.1 Digital Values
The Information Model Management is used to configure specific characteristics for

digital measurements that include:
• State Set instances
A State Set instance defines the specific states (open, close, intransit, etc.) for dig-
ital values. Each state of a State Set instance defines a text string, a value, and
the flag ’valid for control’. When defining a digital measurement, a link is created
to one State Set instance. SCADA data processing uses this instance to deter-
mine how to process the value and which text is used for event/alarm messages.
For detailed information on the configuration of a State Set instance refer to Chap-
ter 2-1.2.5 Configure a new State Set and Create a Link to this State Set.

• Normal state
Along with a link to a state set, a digital measurement may also have a ’normal
state’ designation. In this case, a link is made to one specific state from the asso-
ciated state set. SCADA data processing uses this information to create appropri-
ate messages based on whether a digital measurement is in a ’not normal’ or
’normal’ state.
• Archive collection flag
The HIS subsystem uses the archive flag to determine whether or not this value
needs to be stored in the Historical Information Storage (HIS) in case of value
change.
• Alarm priority
The alarm priority characteristic is used to define alarming characteristics for each
digital measurement.
• Message class
The message class characteristic is used to define alarming characteristics for

each digital measurement
2-1.2.2 Analog Values
The Information Model Management is used to configure analog measurement

characteristics that include:
• Measurement limits
The SCADA supervisory control and analog limit monitor use the limit information
to determine if an analog measurement is outside of the configured limits. Specific
interlock and alarm messages are generated based on this configuration data.
Measurement limits can be created directly under the corresponding measure-
ment instance of the IMM instance tree. Up to 6 limit instances are allowed for
each measurement. Each limit instance contains a single limit. These limits are
the default limits for the measurement.
Additionally, one or more limit sets can be created for each measurement. Each
limit set can contain up to as many limits as configured for the measurement. For
instance, if there are defined 6 limits for a measurement, the limit sets can contain
up to 6 limit instances. Limit instances are created as child instances of the limit
set. This means, they are located directly under the limit set in the data model.
• Archive collection rates
The HIS subsystem uses these rates to determine how often the value needs to
be collected for storage in the HIS archives.
• Alarm priority
Alarm priority is used to define alarming characteristics for each analog measure-
ment.
• Message class
Message class is used to define alarming characteristics for each analog mea-
surement.

2-1.2.3 Step Positions
The Information Model Management is used to configure step position measurement

• Control limits
The SCADA supervisory control uses the limit information to restrict the values
that can be sent to a tap position device (e.g., a transformer).
• Archive collection flags
The HIS subsystem uses the archive flag to determine whether or not a specific
value requires storage in the HIS archives in case of value change.
• Alarm priority
Alarm priority is used to define alarming characteristics for each step position
measurement.
• Message class
Message class is used to define alarming characteristics for each step position
measurement.
2-1.2.4 Fleeting Measurements
The Information Model Management is used to configure fleeting measurement

• Alarm priority
Alarm priority is used to define alarming characteristics for each fleeting measure-
ment.
• Message class
Message class is used to define alarming characteristics for each fleeting mea-
surement.
2-1.2.5 Configure a new State Set and Create a Link to this State Set
The following example describes the flow of dialog steps when the user configures a
new State Set instance (e.g., ’High - Low’) and create a link to this State Set instance in
a corresponding network instance.
• Open the Information Model Manager and create a new job.
• Browse to the instance ’.General/State Sets’ in the instance tree.
• Right-click the instance ’State Sets’. This opens the instance tree pop-up menu.
• Select New from the pop-up menu. The Type Selection dialog opens in the work
pane of the Information Model Manager:

This figure shows the display for Type Selection
Figure 2-1.5: Type Selection Display
• Select the type ’StateSet’ from the type list and click the button Create Instance.
The Single Editor opens in the work pane and shows the General page:
This figure shows the General Page of the Single Editor (StateSet)
Figure 2-1.6: General Page of the Single Editor
• Enter ’High - Low’ into the attribute value field Name. This value represents the
instance name in the instance tree. Additionally, a description/comment may be
entered into the attribute value field Description.
• Save the new instance ’High - Low’. The new instance is displayed in the instance
tree.
• Right-click the instance ’High - Low’. This opens the instance tree pop-up menu.
pane of the Information Model Manager.
• Select the type ’State’ from the type list and click the button Create Instance. The
Single Editor opens in the work pane and shows the General page:

This figure shows the General Page of the Single Editor (State)
• Enter ’High’ into the attribute value field Name. This value represents the instance
name in the instance tree. Additionally, a description/comment may be entered
into the attribute value field Description.
• Browse to the Attributes page of the Single Editor:
This figure shows the Attributes Page of the Single Editor
Figure 2-1.8: Attributes Page of the Single Editor
• Enter the following attribute values into the appropriate fields:
– Text String: e.g., ’High’
– Valid For Control: ’False’
– Value Code: ’1’
• Save the new instance ’High’. The new instance is displayed in the instance tree.
• Right-click the instance ’High - Low’. This opens the instance tree pop-up menu.
• Select the type ’State’ from the type list and click the button Create Instance. The
Single Editor opens.
• Enter ’Low’ into the attribute value field Name of the General page. This value
represents the instance name in the instance tree. Additionally, a description/
comment may be entered into the attribute value field Description.
• Browse to the Attributes page of the Single Editor.
– Text String: e.g., ’Low’

– Valid For Control: ’False’
– Value Code: ’2’
• Save the new instance ’Low’. The new instance is displayed in the instance tree.
• Browse to a network instance (e.g., ’Net-W/Zone*/Reservoir*’)
• Right-click the selected network instance. This opens the instance tree pop-up
menu.
• Select the type ’DigitalMeasurement’ from the type list and click the button Create
Instance. The Single Editor opens.
• Enter ’Status’ into the attribute value field Name of the General page. This value
• Browse to the Links page of the Single Editor:
This figure shows the Links Page of the Single Editor
Figure 2-1.9: Links Page of the Single Editor
• Create a link to the State Set instance (by Drag & Drop from the instance tree):
– Enter the new State Set instance ’High - Low’ into the association value field
StateSet.
– Enter e.g., the State instance ’High’ into the association value field
NormalState to define the normal state for this network instance.
• Save the new instance ’Status’. The new instance is displayed in the instance
tree.
• Activate the corresponding job.
2-1.2.6 Configure a Limit Set

It can be configured, whether seasonal limit sets or manual limit sets shall be used. It is
not possible to use limits sets of both types at the same time.

The following figure shows the attributes page for the SCADA configuration instance
with the parameter determining the type of limit set processing.
Figure 2-1.10: SCADA Configuration Attributes Page
After determining the type of limit set processing the appropriate limit sets (seasonal or
manual) can be configured as described in the following sections.
2-1.2.6.1 Configure a New Seasonal Limit Set
The following example describes the flow of dialog steps when the user configures a
new Limit Set instance (e.g., ’Limit Set 1’):
• Browse to a corresponding measurement instance (e.g., ’Network/Substations/

Sub A/Bay Line A1/P’) in the instance tree.
• Right-click the measurement instance ’P’. This opens the instance tree pop-up
menu.
• Select the type ’LimitSet’ from the type list and click the button Create Instance.
This figure shows the General Page of the Single Editor (LimitSet)
• Enter ’Limit Set 1’ into the attribute value field Name. This value represents the

• Save the new instance ’Limit Set 1’. The new instance is displayed as child
instance of the measurement instance ’P’ in the instance tree.
• Right-click the instance ’Limit Set 1’. This opens the instance tree pop-up menu.
• Select the type ’RuleSeason’ from the type list and click the button Create
Instance. The Single Editor opens in the work pane and shows the General page:
This figure shows the General Page of the Single Editor (RuleSeason)
• Enter e.g., ’Validity Period’ into the attribute value field Name. This value
– Season Closing Day: e.g., ’31’

– Season Closing Month: e.g., ’May’
– Season Starting Day: e.g., ’1’
– Season Starting Month: e.g., ’October’
• Save the new instance ’Validity Period’. The new instance is displayed as child
instance of the instance ’Limit Set 1’ in the instance tree.

• Select the type ’Limit’ from the type list and click the button Create Instance. The
Single Editor opens:
This figure shows the General Page of the Single Editor (Limit)
• Enter e.g., ’Seasonal High Emergency Limit’ into the attribute value field Name of
the General page. This value represents the instance name in the instance tree.
Additionally, a description/comment may be entered into the attribute value field
Description.
• Attributes page of the Single Editor Enter the following attribute values into the
appropriate fields:
– Alias Name: e.g., ’High Emergency Limit’
– Limit ID: ’High Emergency’
– Value: e.g., ’28’
• Save the new instance ’Seasonal High Emergency Limit’. The new instance is
displayed in the instance tree.
• Select the type ’Limit’ from the type list and click the button Create Instance. The

Single Editor opens.
• Enter e.g., ’Seasonal Low Emergency Limit’ into the attribute value field Name of
the General page. This value represents the instance name in the instance tree.
Additionally, a description/comment may be entered into the attribute value field
Description.
– Alias Name: e.g., ’Low Emergency Limit’
– Limit ID: ’Low Emergency’
– Value: e.g., ’-23’
• Save the new instance ’Seasonal Low Emergency Limit’. The new instance is
2-1.2.6.2 Configure a New Manual Limit Set
The following example describes the steps necessary to configure a new manual limit
set instance.
• Browse to the corresponding measurement instance in the instance tree.
• Right-click the measurement instance. The instance tree pop-up menu is opened.
• Select New from the pop-up menu. The Type Selection display is opened in the
work pane.
• Select the type LimitSet from the type list and click the button Create Instance.
• In the General page enter a name for the new manual limit set.
• In the Attributes page of the limit set instance select the limit set type, to which the
new limit set shall belong.
The following figure shows the Attributes page for a limit set instance.

• Save the new limit set instance.
• Right-click the new limit set instance. The tree pop-up menu is opened.
work pane.
• Select the type Limit from the type list and click the button Create Instance.
• In the General page enter a name for the new limit.
• In the Attributes page of the new limit instance enter an alias name, and a value
and select which kind of limit shall be replaced by this manual limit.
The following figure shows the Attributes page for a limit instance
• Save the new limit instance.
• Proceed as described for creating a manual limit replacing the 'Low Warning' limit.
2-1.3 SCADA Methods

SCADA related methods and properties may be configured in the appropriate child
instances of the first-level instance General:

SCADA 2-2 Console
This figure shows the Child Instances of First Level Instance General
Figure 2-1.18: Child Instances of the First Level Instance General
All child instances (except DayTypes-Seasons and Daylight Savings) are SCADA
relevant instances for the configuration of the associated SCADA functions.
2-2 Console
2-2.1 PAT Configuration
Customize Dialog The user may configure the PAT layout by using the Customize dialog (Figure 2-2.1).
The Customize dialog may be invoked by right-clicking the Spectrum PowerCC PAT
logo and selecting the menu item Customize from the opened PAT pop-up menu.

2-2 Console SCADA
This figure shows the Customize Dialog for Configuring the PAT Layout
Figure 2-2.1: Customize Dialog
The Customize dialog allows the user to:
• Display/hide toolbars
• Create new toolbars
• Rename toolbars
• Delete toolbars
• Move toolbars/menu items
• Enter menu titles/commands into the PAT by Drag & Drop
• Define advanced PAT layout options (e.g., toolbar size)
IMM Configuration The parameters of the PAT toolbars (e.g., menu titles, application pathnames, etc.) can
be configured by the child instances of the instance ’Presentation/Application Toolbar’:

SCADA 2-2 Console
This figure shows the Configuration Instances of PAT
Figure 2-2.2: PAT Configuration Instances
Figure 2-2.3 and Figure 2-2.4 show the configuration parameters (attribute values) of
the audio alarming toolbar buttons ’Silence’ and ’Audio Inhibit’ of the PAT. All other PAT
toolbar items are similarly configured.

2-2 Console SCADA
This figure shows the Configuration Parameters of Audio Alarming Toolbar Button
(Silence)
Figure 2-2.3: Attribute Values of the Instance 'Presentation/Application Toolbar/Audible

Alarming/Silence'
This figure shows the Configuration Parameters of the Audio Alarming Toolbar Button
(Audio Inhibit)
Figure 2-2.4: Attribute Values of the Instance 'Presentation/Application Toolbar/Audible

Alarming/Audio Inhibit'
Figure 2-2.5 shows the Audio alarming toolbar buttons ’Silence’ and ’Audio Inhibit’ on
the PAT:
This figure shows the Audio Alarming Toolbar Buttons ('Silence' and 'Audio Inhibit')
Figure 2-2.5: Audio Alarming Toolbar Buttons 'Silence' and 'Audio Inhibit'

SCADA 2-2 Console
2-2.1.1 Configure a new PAT Button
This example describes the flow of dialog steps when the user creates a new PAT
button:
• Right-click the PAT Spectrum PowerCC logo. The PAT pop-up menu opens:
This figure shows the PAT Popup Menu
Figure 2-2.6: PAT Popup Menu
• Select the menu item Customize from the PAT pop-up menu. The Customize
dialog opens:
This figure shows the Customize Dialog for Configuring the PAT Layout
Figure 2-2.7: Customize Dialog
The user may display/hide the corresponding PAT toolbar by selecting the appro-
priate item in the toolbar list of the Customize dialog. Clicking the button Rename
opens a dialog where the user may specify a new name for the selected item.
Clicking the button Delete removes the selected item from the toolbar list.
• Click the button New in the Customize dialog. The New Toolbar dialog opens:

2-2 Console SCADA
This figure shows the Dialog for New Toolbar
Figure 2-2.8: New Toolbar Dialog
• Enter a toolbar name into the field ’Toolbar name’ and click the button OK. The
new toolbar name is listed in the toolbar list of the Customize dialog. The new
toolbar is displayed on the PAT without a menu title:
This figure shows PAT Displaying the New Toolbar
Figure 2-2.9: PAT Showing the New Toolbar
• Select the Commands page in the Customize dialog:
This figure shows the Commands Page Displayed in the Customize Dialog
Figure 2-2.10: Customize Dialog Showing the Commands Page

SCADA 2-2 Console
• Select a command (e.g., the command ’Test Summary’ of the category

’Summaries-Common’) and drop it onto the new PAT toolbar. The command title
’Test Summary’ is displayed on the new PAT toolbar. The user may click this
toolbar button to invoke the appropriate alarm test summary.
This figure shows the New Toolbar Button 'Test Summary' Displayed in PAT
Figure 2-2.11: PAT Showing the New Toolbar Button 'Test Summary'
Note
The user may configure multiple buttons in a toolbar. The user may also drop
commands onto other PAT toolbars, if required.
2-2.1.2 Add a new Application to the PAT
This example describes the flow of dialog steps when the user adds a new application
menu item (e.g., MS Excel) to a PAT menu (e.g., Tools menu):
• Open the Information Model Manager and create a new job (e.g., PATConfig).
• Browse to the instance ’Presentation/Application Toolbar/Tools’ in the instance

tree.
• Right-click the instance ’Tools’. This opens a pop-up menu.

2-2 Console SCADA
This figure shows the Type Selection display
• Select the type ’UserTaskGeneric’ from the type list and click the button Create
This figure shows the General Page of the Single Editor (UserTaskGeneric)
• Enter ’MS Excel’ into the attribute value field Name. This value represents the

SCADA 2-2 Console
• Enter the following attribute values into the appropriate input fields:
– Access Right: Network Management
– Check Security Context Independent: True
– Enable User Task On PAT: Always
– Process: C:\Program Files\Microsoft Office\Office\Excel.exe
Check the corresponding pathname on the console.
– User Task Purpose: Startup
• Save the new instance ’MS Excel’. The new instance is displayed in the instance
tree.
• Open the Commands page of the Customize dialog (refer to Chapter

2-2.1.1 Configure a new PAT Button):

2-2 Console SCADA
This figure shows the Commands Page of the Customize Dialog
Figure 2-2.15: Commands Page of the Customize Dialog
• Select the command ’MS Excel’ and drop it onto the dropped-down PAT Tools
menu. The menu item ’MS Excel’ is displayed on the PAT Tools menu (Figure
2-2.16). The user may click this menu item to invoke the MS Excel application.
This figure shows the PAT Tools Menu
Figure 2-2.16: PAT Tools Menu
2-2.1.3 Add a new Display Call Up Item to the PAT
This example describes the flow of dialog steps when the user adds a new display call
up item (e.g., Sub E) to a PAT menu (e.g., Displays menu):
• Browse to the instance ’Presentation/Application Toolbar/Displays’ in the instance

tree.
• Right-click the instance ’Displays’. This opens a pop-up menu.
• Select the type ’UserTaskDisplay’ from the type list and click the button Create

SCADA 2-2 Console
This figure shows the General Page of the Single Editor (UserTaskDisplay)
• Enter ’Sub E’ into the attribute value field Name. This value represents the
• Enter the following attribute values into the appropriate input fields:
– Access Right: Network Management
– Check Security Context Independent: False
– Enable User Task On PAT: On Context Active
– Toolbar File: ModeSelectToolbar.xml
– View or Worldmap Name: Sub_E
Note
The user must enter the corresponding name of the network diagram (which should be
called up by the PAT) into the value field ’View or Worldmap Name’. The corresponding
network diagram (e.g., Sub_E) must be available in the database.
• Save the new instance ’Sub E’. The new instance is displayed in the instance tree.

2-2 Console SCADA
• Open the Commands page of the Customize dialog (refer to Chapter

2-2.1.1 Configure a new PAT Button):
This figure shows the Commands Page of the Customize Dialog
Figure 2-2.19: Commands Page of the Customize Dialog
• Select the command ’Sub E’ and drop it onto the dropped-down PAT Displays
menu. The menu item ’Sub E’ is displayed on the PAT Displays menu. The user
may click this menu item to invoke the Sub E display.
2-2.2 User Authentication

For information on user administration refer to the document “Spectrum PowerCC
System Management Reference Guide”.
2-2.3 Display Navigation

Display navigation by using the PAT or between graphic diagrams is a graphic design
issue. For more information on this topic refer to the IMM Display Building training
documents of Spectrum PowerCC.
2-2.4 Alarming
2-2.4.1 Alarm Configuration
The processes, that have to be performed after an event has arrived, are defined by
the alarm configuration instances (refer to the Chapter 2-4 Message Summaries).

SCADA 2-2 Console
2-2.4.2 Wireless Alarming
2-2.4.2.1 General
The wireless alarming configuration comprises:
• Alarm filters
Specifies the assignment of alarm messages to the corresponding shift team

members.
Valid filter parameters are:
– Priority
– Category
– Area of Responsibility (AOR)
• Communication devices (wireless alarming channels)
Specifies the used communication devices (e.g., phones, mobiles, etc.)

• Provider
Specifies the used providers (e.g., D1)

The wireless alarming configuration parameters are located underneath the instance
’.General/Wireless Alarming’:
This figure shows the Instances for Wireless Alarming Configuration
Figure 2-2.20: Wireless Alarming Configuration Instances

2-2 Console SCADA
The corresponding shift team members for wireless alarming may be configured
underneath the instance ’.General/Personnel’.
2-2.4.2.2 Wireless Alarming Instance
This instance contains all definitions for communication devices, alarm filters and
providers. Additionally it contains measurements that store the status of the shift plan,
of wireless alarming acknowledgement and whether wireless alarming is switched on
or off.
The following figure shows the attributes defined in the Wireless Alarming instance
Figure 2-2.21: Wireless Alarming - Attributes
The links page parameterizes which shift plans shall be used.
Wireless Alarming Status For displaying the status of wireless alarming in the general summary, the following
Measurements three measurements can be used:
• The shift plan management status is a digital measurement used for generating
an entry in the general summary if the currently used shift plan is not valid. A valid
shift plan must have a reserve of two days in the future. If this digital measurement
does not exist, no message is generated.

SCADA 2-2 Console
The following figure shows the attributes page of the Shift Plan Status measurement
Figure 2-2.22: Attributes Page
The following figure shows the links page of the Shift Plan Status measurement
Figure 2-2.23: Links Page
• The fleeting measurement No WA Acknowledgement is used for generating an

entry in the general summary if a message is not acknowledged by dialing in or by
acknowledgement in an alarm list.

2-2 Console SCADA
The following figure shows the attributes page of the No WA Acknowledgement

measurement
The following figure shows the links page of the No WA Acknowledgement

measurement
• The digital measurement WA Status is used for generating an entry in the general
summary if wireless alarming is turned on or off using the corresponding buttons
in the PAT.

SCADA 2-2 Console
The following figure shows the attributes page of the WA Function measurement
The following figure shows the links page of the WA Function measurement
2-2.4.2.3 Configure a Shift Team Member
This example describes the flow of dialog steps when the user configures a shift team
member:
• Browse to the instance ’.General/Personnel’ in the instance tree.
• Right-click the instance ’Personnel’. This opens the instance tree pop-up menu.

2-2 Console SCADA
This figure shows the Type Selection display for the configuration of wireless alarming
• Select the type ’Person’ from the type list and click the button Create Instance.
This figure shows the General Page of the Single Editor (Person)
• Enter e.g., ’Person 5’ into the attribute value field Name. This value represents the

SCADA 2-2 Console
Figure 2-2.30: Attributes page of the Single Editor
• Enter the corresponding attribute values (First Name, etc.) of the specified shift
team member into the appropriate fields.
• Enter the desired shift plan instances and the communication device (channel)
instances into the following association value fields (by Drag & Drop from the
instance tree):
– ShiftTask: ’.General/Shift Plans/Shift Plan - Wireless Alarming/Tasks/Task -

Gas’
– ShiftTeam: e.g., ’.General/Shift Plans/Shift Plan - Wireless Alarming/Shift

Teams/Team A’
– WAChannel: e.g., ’.General/Wireless Alarming/Communication Device/

Handy 1/SMS’

2-2 Console SCADA
For parallel alarming multiple communication device instances may be

entered into this field.
The communication device instances of the appropriate standby shift team
members may be entered into the association value fields ’First Spare WA
Channel’, etc.
Note
If the standby employee and the employee on duty are the same person, the
association value field ’First Spare WA Channel’ must be configured equal to the
association value field ’WAChannel’ to support a correct escalation strategy.
• Save the new instance ’Person 5’. The new instance is displayed in the instance
tree.
2-2.4.2.4 Configure a Communication Device (Wireless Alarming Channel)
This example describes the flow of dialog steps when the user configures a
communication device (e.g., a mobile):
• Browse to the instance ’.General/Wireless Alarming/Communication Devices’ in

the instance tree.
• Right-click the instance ’Communication Devices’. This opens the instance tree
pop-up menu.

SCADA 2-2 Console
This figure shows the Type Selection display for a communication device
• Select the type ’Communication Device’ from the type list and click the button
Create Instance. The Single Editor opens in the work pane and shows the
General page:
This figure shows the General Page of the Single Editor (Communication Device)
• Enter a value into the attribute value field Name. This value represents the
• Save the new instance. The new instance is displayed in the instance tree.
• Right-click the new instance. This opens the instance tree pop-up menu.
• Select the type ’Channel’ from the type list and click the button Create Instance.

2-2 Console SCADA
This figure shows the General Page of the Single Editor (Channel)
• Enter e.g., ’Mobile SMS’ into the attribute value field Name. This value represents
the instance name in the instance tree. Additionally, a description/comment may
be entered into the attribute value field Description.
– Channel Type: e.g., ’SMS’
The alarm message is sent by SMS to the corresponding mobile.

Valid Values: E-mail, FAX, Pager, SMS, Voice.
– Phone Number
– Provider Name: e.g., ’D1’
• Save the new instance ’Mobile SMS’. The new instance is displayed in the
instance tree.
2-2.4.2.5 Communication Device Status
If the status of a communication device shall be displayed in the general summary in

case of a disturbance, a digital measurement must be configured for the
corresponding device. The following figures show an example for the configuration of
such a measurement.

SCADA 2-2 Console
The following figure shows the attributes page for the status measurement of a
communication device
The following figure shows the links page for the status measurement of a
communication device
2-2.4.2.6 Configure a Service Provider
This example describes the flow of dialog steps when the user configures a service
provider. For each used dial-in service, e.g. to send an SMS to a mobile of a certain
provider, a provider instance has to be created.
• Browse to the instance ’.General/Wireless Alarming/Provider’ in the instance tree.
• Right-click the instance ’Provider’. This opens the instance tree pop-up menu.

2-2 Console SCADA
The following figure shows the type selection display for creating a new provider
instance
• Select the type ’Provider’ from the type list and click the button Create Instance.
The following figure shows the attributes page for a provider instance
• Enter the corresponding parameters (the figure above shows an example of a

provider instance).
• Save the new instance. The new instance is displayed in the instance tree.

SCADA 2-2 Console
2-2.4.2.7 Configure an Alarm Filter
This example describes the flow of dialog steps when the user configures an alarm
filter and assigns this filter to a task (e.g., ’Gas Prio 1’):
• Browse to the instance ’.General/Wireless Alarming/Alarm Filters’ in the instance

tree.
• Right-click the instance ’Alarm Filters’. This opens the instance tree pop-up menu.
This figure shows the Type Selection display for configuring alarm filters
• Select the type ’Wireless Alarming Filter’ from the type list and click the button
General page:
This figure shows the General Page of the Single Editor (Wireless Alarming Filter)

2-2 Console SCADA
• Enter e.g., ’Gas Prio 1’ into the attribute value field Name. This value represents
– Area Of Responsibility: e.g., ’Area A Gas’
– Area Of Responsibility is Used: ’True’
– Category is Used: ’False’
– Priority: ’Priority 1’
– Priority is Used: e.g., ’True’
• Enter the instance ’Shift Plans/Shift Plan - Wireless Alarming/Tasks/Area Gas’ into
the association value field Shift Task (by Drag & Drop from the instance tree).
• Save the new instance ’Gas Prio 1’. The new instance is displayed in the instance
tree.
2-2.4.3 Global Audible Alarming
For global audible alarming a filter has to be defined for each alarm device to decide,
which alarms shall be indicated on which alarm device.
• Browse to the instance '.General/Global Audible Alarming'.
• Right-click the instance 'Global Audible Alarming'. The instance tree pop-up menu

SCADA 2-2 Console
is opened.
work pane.
The following figure shows the Type Selection display for global audible alarming.
• Select the type 'External Audible Device' from the type list and click the button
Create Instance.
• In the General page enter a name for the new audible device.
• Browse to the Attributes page.
The following figure shows the attributes for a global audible alarming device.
• Fill in the values for responsibility area and message configuration.
• Browse to the Links page.

2-2 Console SCADA
The following figure shows the Links page for a global audible alarming device.
• Fill in the association value fields using Drag & Drop from the instance tree. If no
value is entered for the parameter 'Relevant AOR' then no filtering for AORs is
done.
2-2.5 Realtime Accumulator Processing (RAP)
2-2.5.1 General
Accumulators are transmitted from the field via the RTUs and CFE to the Realtime
Accumulator Processing (RAP). RAP starts processing of the incoming values a few
seconds after their expected arrival time (latency time 0 to 120 seconds). Scheduled
arrival is according to the predefined scan period (e.g., each 1 minute, 5 minutes, 15
minutes, 1 hour, etc.). RAP assumes that all accumulators arrive spontaneously
according to one single predefined scan period, triggered by the system time in the
substation.
2-2.5.2 Energy Accounting
All the preprocessed accumulators are forwarded to Energy Accounting, which is a

component on top of HIS.
The accumulator sources are grouped according to the three types:
• Interchange
• Load
• Generation
Each source comprises:
• Main accumulator value
• Control accumulator value
• Integrated analog value
• Authorized accumulator value
The primary objects for Energy Accounting are the accounting points (instances). An
accounting point represents a single energy measurement, which is the integration of
the instantaneous power at a point of generation, load or interchange. The integrated

SCADA 2-2 Console
energy value may be supplied directly via an accumulator measurement or it may be

computed internally by integrating an analog measurement. One of the main
configuration and maintenance tasks for Energy Accounting is defining the
accumulator measurements and/or analog measurements that supply data for the
accounting point.
For more information on Energy Accounting refer to the document “Spectrum

PowerCC Energy Accounting Technical Specification“.
Accounting points may be configured by using the Energy Accounting Wizard of the
IMM. The Energy Accounting Wizard allows the user to create accounting points and
to set up the links between the accumulator and analog measurements, a tariff rule set
and, optionally, to forecast and control areas.
2-2.5.3 Configure Accounting Points
This example describes the flow of dialog steps when the user configures two
accounting points (import and export) for main accumulator values underneath the
instance ’Areas/Tie Corridors/Tie Corridor Line A1/Tiepoint Line A1’:
• Browse to the instance ’Areas/Tie Corridors/Tie Corridor Line A1/Tiepoint Line A1’
in the instance tree.
• Right-click the instance ’Tiepoint Line A1’. This opens the instance tree pop-up
menu.
• Select Accounting Wizard from the pop-up menu. The Energy Accounting Wizard
opens in the work pane of the Information Model Manager:
This figure shows the Energy Accounting Wizard
Figure 2-2.47: Energy Accounting Wizard (Introduction Page)
• Click the button Next. The wizard step 1 opens:

2-2 Console SCADA
This figure shows Step 1 of the Energy Accounting Wizard
Figure 2-2.48: Energy Accounting Wizard (Step 1)
The wizard step 1 shows the existing accounting point underneath the selected
instance. In this step the user may define the number of export and import
accounting points (Default value for export/import: ’1’)
This figure shows Step 2 of the Energy Accounting Wizard

SCADA 2-2 Console
• Enter the export/import accounting point names in the corresponding input fields
of the column ’Accounting Point Name’ or use the predefined names. The names
represent the instance names underneath the selected instance in the instance
tree.
The following accounting point configurations may be selected from the column
’Accounting Point Configuration’:
– Main
The accounting point has one main accumulator.
– Main, Control
The accounting point has a main and a control accumulator.
– Main, Control, 1 Analogs
The accounting point has a main accumulator, a control accumulator and one
integrated analog measurement.
– Main, Control, 2 Analogs
The accounting point has a main accumulator, a control accumulator and two
integrated analog measurements.
The configuration ’Main’ is predefined.

This figure shows the Step 3 of the Energy Accounting Wizard
• Enter the corresponding accumulator measurement instances into the input fields
of the column ’Linked to’ (by Drag & Drop from the instance tree). Enter e.g., the
instance ’Network/Substations/Sub A/Bay Line A1/MWH Exp Processed’ into the
field for the raw main value type.

2-2 Console SCADA
Note
The corresponding accumulator measurement instances must not be already linked to
other accounting points.
This figure shows the Step 4 of the Energy Accounting Wizard
The user may link each accounting point to a Tariff Rule Set instance and, option-
ally, to a control and/or forecast area instance.
Enter the instance ’Accounting/_Tariff Rule Sets/Base Tariff Set’ into the input
fields of the column ’Tariff Rule Set’ (by Drag & Drop from the instance tree).
• Click the button Next. The last wizard step opens:

SCADA 2-2 Console
This figure shows the Last Step of the Energy Accounting Wizard
Figure 2-2.52: Energy Accounting Wizard (Last Step)
The last wizard step shows the configured accounting points.

Click the button Finish to complete the Energy Accounting Wizard. A message
box opens.
• Click the button OK. The accounting points are saved underneath the selected
instance ’Areas/Tie Corridors/Tie Corridor Line A1/Tiepoint Line A1’.
Note
If accounting points shall be defined for SCADA, the proceeding is similar to that
described above for Energy Accounting, but with two differences:
• accounting points are defined under the folder 'Accounting'
• no tariff sets
2-2.6 Realtime Calculation
2-2.6.1 General
Spectrum PowerCC SCADA includes a real-time calculation engine to logically or

arithmetically combine incoming real-time values as operands and to store the result
into the real-time database. The real-time values can be calculated either by using
formulas (simple calculation) or scripts (complex calculations). The formulas and
scripts can be configured in the Information Model Management.
The Information Model Management provides the Calculation Wizard, the Script
Definition Wizard, and the Script Wizard for the creation of formulas and scripts. The
wizards support the user when creating new formula/script instances to make sure that
all required attributes of the generated instances are set according to the
corresponding instance requirements. The appropriate wizard guides the user through

2-2 Console SCADA
a number of steps in the creation of a new calculation result, a new script instance or a
new script definition under the selected node.
The IMM data model describing formulas and scripts consists of two parts:
• Formula/script definition, located in the instance tree under the first-level instance
’General’.
• Specific parameters to feed the formulas/scripts together with the calculation

result, located in the instance tree under the first-level instance ’Network’.
For more information on the creation of formulas and scripts refer to the document
Spectrum PowerCC Information Model Management Reference Guide.
2-2.6.2 Configure a Calculation
This example describes the flow of dialog steps when the user configures a result
measurement (e.g., a power value calculation on the base of a constant voltage value)
underneath the instance ’Network/Substations/Sub A/ Bay Line A1’ by using the
Calculation Wizard:
• Browse to the instance ’Network/Substations/Sub A/ Bay Line A1’ in the instance

tree.
• Right-click the instance ’Bay Line A1’. This opens the instance tree pop-up menu.
• Select Calculation Wizard from the pop-up menu. The Calculation Wizard opens
in the work pane of the Information Model Manager:
This figure shows the Calculation Wizard
Figure 2-2.53: Calculation Wizard (Introduction Page)

SCADA 2-2 Console
This figure shows the Step 1 of the Calculation Wizard
Figure 2-2.54: Calculation Wizard (Step 1)
• Enter the following values into the appropriate fields:

– Result Name: e.g., ’Res P for const voltage’
This value represents the measurement instance name in the instance tree.
– Calculation: ’Pre-defined calculation’
– Calculation Rule: ’Multiplication’
– Result Type: ’AnalogMeasurement’
– Calculation Trigger: ’On Operand Change’

2-2 Console SCADA
This figure shows the Step 2 of the Calculation Wizard
Figure 2-2.55: Calculation Wizard (Step 2)
– Enter the constant value ’10000’ and the operand name ’U’ into the
appropriate fields of the row ’Multiplicand’.
– Enter the instance ’Network/Substations/Sub A/ Bay Line A1/I’ (by Drag &
Drop from the instance tree) and the operand name ’I’ into the appropriate
fields of the row ’Multiplier’.
• Click the button Finish to complete the Calculation Wizard. The result
measurement ’Res P for const voltage’ is saved underneath the selected instance
’Network/Substations/Sub A/ Bay Line A1’.
2-2.6.3 Configure a Calculation Script Execution
The following examples describe the flow of dialog steps when the user configures a
calculation script execution (e.g., an absolute value calculation (example 1) or a
storage volume calculation (example 2)) by using the calculation wizard:
Example 1 - Absolute • Open the Information Model Manager and create a new job.
Value Calculation
• Browse to the instance ’Network/Substations/Sub A/ Bay Line A1’ in the instance
tree.
• Right-click the instance ’Bay Line A1’. This opens the instance tree pop-up menu.
in the work pane of the Information Model Manager:

SCADA 2-2 Console
The following figure shows step 1 of the calculation wizard.
Figure 2-2.57: Calculation Wizard (step 1)
– Result Name: e.g., ’Absolute Value’

2-2 Console SCADA
– Calculation: ’User-defined calculation’
– Calculation Rule: ’Math: absolute(x)’
• Enter the instance ’Network/Substations/Sub A/ Bay Line A1/I’ (by Drag and Drop)
from the instance tree) into the appropriate field of the row ’x’.
• Click the button Finish to complete the Calculation Wizard. The result is saved
underneath the selected instance ’Network/Substations/Sub A/ Bay Line A1’.

SCADA 2-2 Console
The following figure shows the new calculation script instance.
Figure 2-2.59: Calculation Script Instance
Example 2 - Storage • Open the Information Model Manager and create a new job.
Volume Calculation
• Browse to the instance ’Net G/Facility X/Storage’.
• Right click the instance ’Storage’. This opens the instance tree pop-up menu.
on the work pane of the Information Model Manager.

2-2 Console SCADA
– Result Name: e.g., ’Volume of Storage’
– Calculation: ’User-defined calculation’
– Calculation Rule: ’Storage volume’

SCADA 2-2 Console
• Enter the constant values into the appropriate fields as shown in the figure above.
• Enter the instance ’Net G/Facility X/Storage/pressure’ (by Drag and Drop) from
the instance tree) into the appropriate field of the row ’c’.
• Enter the instance ’Net G/Facility X/Storage/temperature’ (by Drag and Drop) from
the instance tree) into the appropriate field of the row ’e’.
• Click the button Finish to complete the Calculation Wizard. The result is saved
underneath the selected instance.
The following figure shows the new calculation script instance.
Figure 2-2.63: Calculation Script Instance

2-3 Graphic Displays
2-3.1 Worldmap Concept

Spectrum PowerCC has implemented a worldmap concept for creation, display,
maintenance and navigation of large network diagrams. Worldmaps are network
diagrams which consist of multiple stations in a single network.
This worldmap concept offers the necessary user interface features requested by large
systems (e.g., DMS systems) where overview diagrams as well as fine granular
detailed views must be available and easy to navigate between them.
This figure shows the Worldmap Displaying Multiple Stations in a Single Network
Figure 2-3.1: Schematic Network Diagram
A worldmap is a 2-dimensional drawing plane, containing each presentation detail.

Only a small subset of the worldmap can be displayed by a view in a window on the
console’s screen. The worldmap concept provides for sophisticated methods to rapidly
navigate to that subset of details that are currently interesting for the user’s work.

This figure shows the Relation Between the Worldmap, View and Window
Figure 2-3.2: Relation Between Worldmap, View and Window
A worldmap is a 2-dimensional drawing plane, containing each presentation detail.

Only a small subset of the worldmap can be displayed by a view in a window on the
console’s screen. The worldmap concept provides for sophisticated methods to rapidly
navigate to that subset of details that are currently interesting for the operator’s work.
Note
Layers can also be used to provide additional levels of details which can be switched
on/off in the runtime system.
The worldmap concept is characterized by the features as listed below:
• The drawing area consists of 32 layers. Usually, all layers are visible together and
a display consists of a set of all layers. The layer concept helps the diagram
designer to better organize the grouping of the network components. It is possible,
however not recommended, to put all details within a single layer.
• Zooming is possible up to a zoom factor of 800 percent. While zooming, the

visibility of the displayed details (lines, text strings, symbols, etc.) is automatically
kept within visible limits by decluttering.
• Decluttering algorithm
The decluttering algorithm controls the visibility of the objects based on the speci-
fied lower and upper limits of the object sizes.
An object is visible:
– when the object size is greater than the configured lower limit and smaller
than the configured upper limit
– or the object is defined to be visible independent from the size (high

importance).

2-3.2 Display Building

Displays can be achieved by 3 methods:
• Import of graphic displays in EMF (Enhanced Meta Files), WMF (Windows Meta
Files) and SVG (Scalable Vector Graphic) file formats.
EMF and WMF file formats provide only the import of static information (e.g. back-
ground information). The SVG file format provides the import of static and
dynamic objects.
• Designing graphic displays on the drawing pane of the Graphics Designer.
• Automatic generation of graphic displays from alphanumeric data, as provided in

the engineering database, where the network components (switches, lines,
busbars, generators, transformers, etc.) are described together with their
topological connections.
The optional IMM tool Auto Display Generator runs across the database and gen-
erates graphic diagrams that can be modified and stored in the engineering data-
base.
Note
Created network diagrams are stored in the database. All Spectrum PowerCC
consoles, which are connected to this database, have access to the stored network
diagrams.
This figure shows the Graphics Designer
Figure 2-3.3: Graphics Designer
For more information on creating graphic displays refer to the document “Spectrum
PowerCC Graphics Designer Reference Guide“.

2-3.3 Topological Network Coloring
2-3.3.1 Topology Model
This figure shows the Data Relevant for Network Coloring
Figure 2-3.4: Relevant Network Data Coloring
2-3.3.2 General Settings
The different coloring schemes require different data. The following information must
be provided for all schemes:
Table 2-3.1: Common Settings

Attribute/Association To define at instances of type
DMSFlag (Attribute) TransformerWinding (only DMS network)
DMSType (Attribute) BusbarSection (only DMS network)
Phases (Attribute) PowerSystemResource (only DMS network)

NormalState (Association) DigitalMeasurement
2-3.3.3 Energization Coloring
The energization coloring scheme shows the plain energization state of the network.
The possible states of equipments (deenergized, isolated, grounded, undefined and
energized) are displayed in unique colors. The quality of the state is considered. This
means, if an equipment has a topological connection to an energizer (or ground) that
consists of disturbed switching devices, it gets a distinct color to indicate this uncertain
state.
In case the electrical phases of an equipment are detected to be of different states, the
equipment is shown in the network diagram in certain colors.
Table 2-3.2: Energization Color Scheme

State ColorUsage-Attribute of ‘Color’ Instance
Deenergized UsedForDeenergized
Isolated UsedForIsolated
Grounded UsedForGrounded
Undefined UsedForUndefined
Energized UsedForEnergized
Grounded uncertain UsedForGrounded_Uncertain
Energized uncertain UsedForEnergized_Uncertain
Undefined uncertain UsedForUndefined_Uncertain
Phases partially energized and UsedForPartEnerg
deenergized
Different states over the phases UsedForDifferentStates
(e.g. energized and grounded)
The network coloring schemes can be configured in the IMM (instance “.General/Color
Palettes/Network Coloring”).

This figure shows the Color Palette for network Coloring
Figure 2-3.5: Color Palette for Network Coloring
2-3.3.4 Voltage Level Coloring
The voltage coloring scheme shows basically the same information as the energization
coloring scheme, but for energized equipment it shows distinct colors for the single
voltage levels (up to 5 are possible). This coloring scheme requires the membership of
the network equipment to its voltage level as data input. The voltage level is defined at
field resources of the type 'TransformerWinding' and is propagated to the connected
field resources automatically. It is possible to define single switching devices as
voltage level disconnecting switches, which stop the propagation of the voltage level.
Those switches are normally open disconnectors that disconnect different voltage
levels while the network is redesigned due to operational requirements. The energized
equipment, that does not have a connection to a type ’TransformerWinding’ with an
assigned voltage level is colored in the default color.
Table 2-3.3: Voltage Level Color Scheme

Energized (as default, if voltage level is UsedForEnergized
not parametrized)
Energized on Voltage Level 1 UsedForVoltLev_1


Phases partially energized and deener- UsedForPartEnerg
gized
Different states over the phases (e.g. UsedForDifferentStates
energized and grounded)
Note
Bold printed voltage level states are additionally provided to energization color
schemes.
The following example describe the voltage level configuration:
• Navigate to the instance “Network/.Common” and create as many instances of the

type ’BaseVoltage’ as required for the corresponding network.
• Supply a value for the base voltage attribute ’NominalVoltage’.
• Link one of the color instances with the ’ColorUsage’-attribute

’UsedForVoltLev_1..5’ to the base voltage instance (Assoc. 'Color').
• Navigate to a substation (Network/Substations/<Substation Name>) and create

an instance of the type ’VoltageLevel’.
• Link the created base voltage instance to it (Assoc. 'BaseVoltage').

• Navigate to the instances of the type ’TransformerWinding’ (e.g., Network/
Substations/Sub A/Trafo A1/HighWinding) and link the respective base voltage
instance to it (Assoc. 'BaseVoltage').
• Navigate to the switching device instances that are supposed to disconnect (two)
different voltage levels.
• Set their 'DiscVoltLevel' attributes to 'true'.
• Activate the changes.
2-3.3.5 Loop/Parallel Coloring
The loop/parallel coloring scheme is mainly used to show up irregular network states
like looped network equipments or network equipments energized in parallel. It
basically shows the same information as the energization coloring, but in addition
looped and/or parallel network equipments are displayed in distinct colors.
• Definition 'Loop'
A network equipment is in a loop, when it has a closed connection to one and the
same energy source on at least two sides.
• Definition 'Parallel'

A network equipment is in parallel, when it has a closed connection to different

energy sources on at least two sides.
Table 2-3.4: Loop/Parallel Color Scheme
Energized radial UsedForEnergized
Energized in a loop UsedForEnerg_Loop
Energized parallel UsedForEnerg_Parallel
Energized in a loop and parallel at the UsedForEnerg_LoopParallel
same time
gized
Different states over the phases (e.g. UsedForPartEnerg
Note
The bold printed states are additionally provided to the energization color schemes.
2-3.3.6 Network Group Coloring
The network group coloring scheme is used to divide the network into geographical,
organizational or operational areas (so-called “network groups”). A color is assigned to
a network group. The assignment of the network components to a network group or
multiple network groups (and, thus, to the network group's color) is dynamic based on
the current switching state.
Network groups:
• Geographical: Region East, region West, etc.
• Organizational: Area of responsibility
• Operational:
– Energized by a certain feeder
– Energized by a certain energy source
– Energized by multiple energy sources
– Island detection
A network group starts at field resources that are linked to so-called “Determining
Elements” (which themselves are assigned to one and the same network group or to
different network groups). Those network group-determining field resources are either
transformer windings or connectivity nodes.

A network group ends at open switches or at field resources that are linked to so-called
“Isolating Elements”. Those network group isolating field resources are either power
transformers or (closed) switches.
If a network group is isolated within an energized part of the network and the isolated
part does not have a closed connection to another network group determining field
resource, it gets the default color for energized equipment (UsedForEnergized).
Table 2-3.5: Network Group Color Scheme

Energized (as default, if equipment UsedForEnergized
belongs to no netgroup)
Energized in netgroup Not specific
gized
Different states over the phases (e.g. UsedForPartEnerg
Note
Bold printed states are additionally provided to the energization color schemes.
The following example describe the network group configuration:
• Navigate to the instance ’Presentation/.Common/.Coloring Groups’ and create a

instance of the type ’NetworkColoringGroup’.
• Supply a value for the NetworkColoringGroup's Priority attribute.

• Link one of the color instances with the ’ColorUsage’-attribute ’NotSpecific’ to the
instance ’NetworkColoringGroup’ (Assoc. 'Color').
• Navigate to the created network coloring group instance and create an instance of
type ’DeterminingElement’.
• Link a field resource to the ’DeterminingElement’ (Assoc. 'TransformerWinding' or

'ConnectivityNode'). This is the location in the network where the propagation of
the netgroup color starts.
• Navigate to the instance ’Presentation/.Common/.Coloring Groups’ and create an

instance of the type ’IsolatingElement’.
• Link a field resource to the ’IsolatingElement’ (Assoc. 'Switch' or

'PowerTransformer'). This is the location in the network where the propagation of
the netgroup color ends.
• Activate the changes

2-3.3.7 Multi Phase Coloring
The multi phase coloring schemes are provided to show the energization state of an
electrical equipment regarding its unbalanced phase energization. The 7 possible
energized/deenergized combinations are displayed in distinct colors.
Table 2-3.6: Multi Phase Color Scheme

All phases deenergized and at least one UsedForDeenergized
phase not isolated
All phases isolated UsedForIsolated
All phases certainly grounded UsedForGrounded
Three phases (A, B and C) certainly ener- UsedForEnerg_ABC
gized
Phases A and B certainly energized, phase UsedForEnerg_AB
C deenergized
Phases A and C certainly energized, phase UsedForEnerg_AC
B deenergized
Phases B and C certainly energized, phase UsedForEnerg_BC
A deenergized
Phase A certainly energized, phases B and UsedForEnerg_A
C deenergized
Phase B certainly energized, phases A and UsedForEnerg_B
C deenergized
Phase C certainly energized, phases A and UsedForEnerg_C
B deenergized
All phases grounded and at least one phase UsedForGrounded_Uncertain
uncertainly
All phases energ./deenerg. and at least one UsedForEnergized_Uncertain
phase uncertainly
All phases undefined and at least one UsedForUndefined_Uncertain
phase uncertainly
Different states over the phases (e.g. ener- UsedForDifferentStates
gized and grounded)
Note
2-3.3.8 Single Phase Coloring
The single phase coloring scheme allows the user to show the status of a single
electrical phase. For the selected phase, it shows principally the same information as
the network group coloring. This coloring scheme is useful, if e.g., the multi phase
coloring indicates a 'Different states' status for an equipment and the user wants to
show the energization state of the single phases.
Table 2-3.7: Single Phase Color Scheme


Energized radial (as default, if phase UsedForEnergized
belongs to no netgroup)
Energized radial in netgroup Not specific (netgroup color)
Energized in a loop UsedForEnerg_Loop
Energized parallel UsedForEnerg_Parallel
Energized in a loop and parallel at the UsedForEnerg_LoopParallel
same time
Note
2-3.3.9 Configure a Voltage Level Color for an Energized Line
This example describes the flow of dialog steps when the user configures a new
voltage level color for an energized line (e.g., for 400 kV nominal voltage):
• Browse to the instance ’.General/Color Palettes/Network Coloring’ in the instance

tree.
• Right-click the instance ’Network Coloring’. This opens the instance tree pop-up
menu.

This figure shows the Type Selection Display for the voltage color configuration
• Select the type ’Color’ from the type list and click the button Create Instance. The
Color Picker opens in the work pane of the Information Model Manager:
This figure shows the Color Picker in the Work Pane of the Information Model Manager
Figure 2-3.7: Color Picker
• Enter e.g., ’Energized_Certain_Volt_6’ into the input field Name. This value
comment may be entered into the input field Documentation.
• Enter the desired color (e.g., dark green: hex code ’#008040’) into the input field
Color. The color may be also entered by using the color palette. The color palette
may be opened by clicking the button right of the input field Color.
• Save the new color instance ’Energized_Certain_Volt_6’. The new instance is

• Browse to the instance ’Network/_Base Voltages’ in the instance tree.
• Right-click the instance ’_Base Voltages’. This opens the instance tree pop-up
menu.

• Select the type ’BaseVoltage’ from the type list and click the button Create
This figure shows the General Page of the Single Editor (BaseVoltage)
• Enter ’400 kV’ into the attribute value field Name. This value represents the
• Enter ’400’ into the attribute value field Nominal Voltage.
• Browse to the Links page of the Single Editor.
• Enter the new color instance ’General/Color Palettes/Network Coloring/

Energized_Certain_Volt_6’ into the association value field Has A Color (by Drag &
Drop from the instance tree).
• Save the new base voltage instance ’400 kV’. The new instance is displayed in the
instance tree.

• Select the corresponding line instance ’Network/Lines/Netstation X - Netstation Y’

(for 400 kV nominal voltage) and browse to the Links page of the Single Editor:
This figure shows the Links Page of the Single Editor (Base Links)
• Enter the new base voltage instance ’Network/_Base Voltages/400 kV’ into the
association value field BaseVoltage (by Drag & Drop from the instance tree).
2-3.4 Trending
2-3.4.1 Trend Control Data Model
This figure shows the Trend Control Data Model
Figure 2-3.12: Trend Control Data Model
The trend control data model consists of 6 types, which contain all the necessary
attributes for storing persistent configuration parameters like background color, plot
area color, axis parameters, etc. The chart configuration is stored in the real-time
context.
The following types are defined:
• Charts
This type contains the chart objects.

• Chart
This type contains the general chart information like chart type, plot area and
background color, chart title, legend etc. It is a member of 'Charts’'.
• ChartTrend
This type contains information about the trend curve like line color, line width, data
source, which y-axis it is related to, etc. It is a member of 'Chart'.
• ChartAxis
This type contains the axis information and is used to derive the subtypes 'ChartX-
Axis' and ’ChartYAxis’. It contains axis information like grid on/off, autoscale, log
scale etc. Chart axis can contain various axes of the types ’ChartXAxis’ and
’ChartYAxis’. It also defines the position of an axis within a chart object. It is possi-
ble to place an axis on any side of a chart (left, right, bottom, top).
• ChartXAxis
Inherits its attributes from 'ChartAxis'. It may be configured as x-axis or as date/

time axis. It is also possible to define, whether an axis is the first or second axis in
case of multiple axes.
The trend control function may be configured independent from contexts. Curves of
different contexts can be compared within one common chart.
2-3.4.2 Configuration Data
Each chart may be individually configured in the IMM (context ’Application

Configuration’)
This figure shows the display with chart configuration data
Figure 2-3.13: Chart Configuration

The trend control function provides a set of basic configuration parameters which are
described below. These parameters are stored as attributes of the type ’Chart’ in the
database:
• General chart parameters
– Chart title
– Chart area background color
– Chart style
– Chart type: LineChart, BarChart etc.
• Axis parameters
– Axis title
– X-Axis: Yes/No
– Y-Axis: Yes/No
– Secondary: Yes/No (for more than one axis)
– Date/Time: Yes/No (the date/time values are displayed on the x-axis)
– Show Grid Lines: Yes/No
– Gridline color
– Tick width: long
– Minor tick width: long
• Data series parameters
– PathName: Database path of the corresponding value
– CalcMode: 5min average, 10 min average etc.
– StartTime: Date/time, Trending start time
– EndTime: Date/time, Trending end time
• Legend parameters
– LegendColor: Sets the background color of a legend
– LegendVertical: Yes/No. Legend icons in the vertical legend
– LegendHorizontal: Yes/No. Legend icons in the horizontal legend
– LegendllX: X location of the lower left legend corner (default 0.2)
– LegendllY: Y location of the lower left legend corner (default 0.2)
– IconWidth: Width of the legend icon (default 0.07)
– IconHeight: Height of the legend icon (default 0.05)
– IconGap: Gap between the icon and the next legend entry (def.0.01)
This list provides an overview of a basic configuration. If required, it may be expanded.

2-3.5 Presentation Logic
2-3.5.1 General
The presentation of network components is controlled by rules and conditions (logic

sets). Rules determine the presentation of a network component (graphical symbol,
symbol shape, color, flashing, etc.) by evaluating conditions (combinations of
component attribute values). Each operational situation or purpose is related to a
number of conditions and rules which eventually determine the appearance of a
network component for the particular situation or purpose. The conditions and rules
form a matrix of logical combinations called “decision table”. Each decision table
covers one particular operational situation or purpose.
IMM Presentation Logic The presentation of network components can be configured by the IMM Presentation
Editor Logic Editor. It is a special purpose editor used to view and edit properties of
presentation logic instances as well as to create new presentation logic instances. A
presentation logic instance defines the graphical representation of an instance
measurement (for example, a breaker) for the runtime user interface of Spectrum
PowerCC considering different operational situations or purposes. For example: a
breaker may be represented by different symbols depending on its current status.
The presentation logic instances are located underneath the instance ’Presentation/
’.Common/.Logic Sets*’ in the instance tree.
2-3.5.2 Configure a Presentation Logic Instance
presentation logic instance (e.g., Earth Fault symbol) and specifies a condition (e.g.,
Acknowledged):
• Browse to the instance ’Presentation/’.Common/Logic Sets - Electricity’ in the

instance tree.
• Right-click the instance ’Logic Sets - Electricity’. This opens the instance tree pop-
up menu.

This figure shows the type selection display for presentation logic
• Select the type ’PresentationLogic’ from the type list and click the button Create
Instance. The Presentation Logic Editor opens in the work pane and shows the
General page:
This figure shows the General Page of the Presentation Logic Editor
Figure 2-3.15: General Page of the Presentation Logic Editor
• Enter e.g., ’/Fleeting Earth Fault’ into the input field Name. This value represents
the instance name in the instance tree.
• Select ’Presentation/.Common/Operand Sets - Common/Fleeting’ from the drop-

down list Operand Set.
• Browse to the Main Area page of the Presentation Logic Editor:

This figure shows the Main Area Page of the Presentation Logic Editor
Figure 2-3.16: Main Area Page of the Presentation Logic Editor
• Double-click the table cell Figure (column Rule 0) of the decision table. The
Graphic File Browser dialog opens:
This figure shows the Graphic File Browser Dialog
Figure 2-3.17: Graphic File Browser
• Browse to the Earth Fault symbol and double-click the corresponding row of the
symbol list. The Earth Fault symbol is displayed in the table cell Figure.

This figure shows the Main Area Page of the Presentation Logic Editor Displaying the
Earth Fault Symbol
Figure 2-3.18: Main Area Page of the Presentation Logic Editor (Showing the Earth
Fault Symbol)
• Select ’Yes’ from the drop-down list of the table cell Default Rule.
This value determines the content of the presentation area related with the
respective page of the Presentation Logic Editor. When the Preview page is dis-
played, the “default rule” of each related page is evaluated and the configured
graphical symbol or formatting string is displayed on the corresponding presenta-
tion area.
Valid values:
– Yes: Respective rule is used as default rule.
– No: No default rule.
• Select e.g., ’Slow’ from the drop-down list of the table cell Blinking.
This value determines, if the specified graphic symbol blinks when it is displayed
on the runtime user interface.
Valid values:
– Slow: flashing frequency = 0.67 Hz.
– Fast: flashing frequency = 1.33 Hz.
– No: No flashing.
• Right-click a decision table row. The decision table row menu opens:

This figure shows the Decision Table Row Menu
Figure 2-3.19: Decision Table Row Menu
• Select the menu item Acknowledged. The condition Acknowledged is displayed in

the decision table:
Presentation Properties and the 'Acknowledged' Condition
Figure 2-3.20: Main Area Page of the Presentation Logic Editor (Showing the
Presentation Properties and the Condition 'Acknowledged')
• Select ’No’ from the drop-down list of the table cell Acknowledged.
Valid values:
– Yes: The specified presentation properties are active while the corresponding
message is acknowledged.
– No: The specified presentation properties are active while the corresponding
message is not acknowledged.
• Right-click the header (’Rule 0’) of the decision table. The decision table column
menu opens:

This figure shows the Decision Table Column Menu
Figure 2-3.21: Decision Table Column Menu
• Select the menu item ’Add new rule’. The new rule column ’Rule 1’ is displayed in
the decision table:
New Rule Column 'Rule 1'
Figure 2-3.22: Main Area Page of the Presentation Logic Editor (Showing the New
Rule Column 'Rule 1')
• Select ’No’ from the drop-down list of the table cell Default Rule in the column
’Rule 1’.
• Select ’No’ from the drop-down list of the table cell Blinking in the column ’Rule 1’.
• Select ’Yes’ from the drop-down list of the table cell Acknowledged in the column
’Rule 1’.
• Save the presentation instance ’Fleeting Earth Fault’.

2-4 Message Summaries

The message summaries can be configured in the IMM. The configuration parameters
are located underneath the first-level instance ’General’. The configuration comprises
alarm controls, messages and the summaries.
This figure shows the Message Summary Configuration Instances
Figure 2-4.1: Message Summary Configuration Instances

(Figure 2-4.2) shows the relation between message instances, summary instances
and alarm control instances.
This figure shows the Relation Between Message Summary and Alarm Control
Instances
Figure 2-4.2: Relation Between Message, Summary and Alarm Control Instances
2-4.1 Alarm Control Configuration

An Alarm Control instance defines the layout and the behavior of a summary (e.g., the
background color, which columns and toolbar buttons are displayed, etc.). The
(network-specific) Alarm Control instances are located underneath the instance
’.General/Alarm Configuration’ in the instance tree.
The Alarm Control instances allows the user to specify the following characteristics of
a summary:
• Column types
• Toolbar buttons
• Summary sort order
• Data source
• Advanced summary parameters (font, font size, background color, update cycle
etc.)
The following sections describes, which summary characteristics the user may
basically configure for a summary. For detailed information on the configuration/
creation of Alarm Control instances refer to Chapter 2-4.1.6 Configure a New Alarm
Control Instance.
2-4.1.1 Column Types
The user may define the following column types. The corresponding column type may
be selected on the Attributes page of the appropriate summary column instance (of the
type ’AlarmControlColum’).
Table 2-4.1: Summary Column Types

Column Type Description
Acknowledgement Acknowledgement status (e.g., ‘Q’, ‘A’).
Category Message category.

Comment Comment (e.g., ‘Overridden interlock violation’).

Console Console (e.g., ‘PC X’).
Date Only the date is displayed.
Date and Time Date and time are displayed.
Description The description of a marker is displayed.
History The history of a marker is displayed.
Indicator Indicator string (e.g., ‘TT’, to indicate a true time message).
Limit Limit (e.g., ‘High Emergency’, ‘250’).
Message Class Defines the acknowledge behavior of an alarm within an Alarm
Summary.
Reminder Displays the reminder date and time of a marker.
Title Displays the title of a marker.
User User name.
Path 1 First block of the instance pathname (e.g., ‘Substation’).
Path 2 Second block of the instance pathname (e.g., ‘Voltage level’).
Path 3 Third block of the instance pathname (e.g., ‘Bay’).
Path 4 Fourth block of the instance pathname (e.g., ‘Field resource’ or
‘Analog measurement’).
Path 5 Fifth block of the instance pathname (e.g., ‘Digital measurement’
or ’Analog limit’).
Priority Message priority.
Status Event status (e.g., ‘App’ or ‘Dis’).
Time Only the time is displayed.
Unit Analog value unit (e.g., ‘kV’).
Value Value (e.g., ‘Open’, ‘Close’, or ‘123.45’).
2-4.1.2 Toolbar Buttons
The following toolbar button instances are located underneath the instance ’./General/
Alarm Configuration/Alarm Controls - Common/_Alarm Control Buttons’. The user may
modify the instances or add new instances.
Table 2-4.2: Summary Toolbar Buttons

Toolbar Button Description
Acknowledge Page Acknowledge all visible entries.
Acknowledge Reminder Acknowledges an expired reminder of a note marker.
Acknowledge Single Acknowledge a single selected entry.
Add View Comment Call up the dialog window to add or view a comment.
Auto Scroll On_Off Enable/disable the auto scroll functionality.
Auto Update On_Off Enable/disable the auto update functionality.
Clear Alarm Clears the selected message (only possible, if the message
class is ’AaCl’).
Clear Summary Clears the content of the summary.
Create General Note Creates a new general note marker.
Delete Alarm Deletes the selected message.
Delete Marker Deletes the selected marker.
Display Callup Opens the graphic display of the selected object.

Display List Opens the dialog for runtime display configuration.

Edit Note Opens a display for viewing or editing the data of the selected
note marker.
Filter Configuration Opens the filter configuration dialog.
Filter On_Off Switches the filter on or off.
Next Not Ackowledged Alarm Jumps to the next not acknowledged message.
Page Down Browses to the next page.
Page Up Browses to the previous page.
Previous Not Ackowledged Jumps to the previous not acknowledged message.
Alarm
Print Prints the content of the summary.
Refresh Reloads the summary data.
Sort On_Off Switches the sort order on or off.
Step To End Jumps to the last entry of the summary.
Step To Top Jumps to the first entry of the summary.
2-4.1.3 Summary Sort Order
The user may define the following summary sort orders. The corresponding sort order
may be selected on the Attributes page of the appropriate Alarm Control instance (of
the type ’AlarmControl’).
Table 2-4.3: Summary Sort Order

Sort Order Description
Ascending Time The summary is sorted ascending by the time stamp.
Ascending Receive Time The summary is sorted ascending by the incoming order.
Descending Time The summary is sorted descending by the time stamp.
Descending Receive Time The summary is sorted descending by the incoming order.
2-4.1.4 Data Source
The user may define the following summary data sources. The corresponding data
source order may be selected on the Attributes page of the appropriate Alarm Control
instance (of the type ’AlarmControl’).
Table 2-4.4: Summary Data Source

Data Source Description
Alarm System The data source is the runtime alarm system.
Alarm Archive The data source is the long time archive.

2-4.1.5 Advanced Summary Parameters
The user may specify the following advanced summary parameters like the used font,
the font size or the update cycle on the Attributes page of the appropriate Alarm
Control instance (of the type ’AlarmControl’).
Table 2-4.5: Advanced Summary Parameters (Attribute Page)

Attribute Data Format Description
Acknowledge Alarm Indi- String The value is displayed in the column of the
cation column type ’Acknowledge’, if an alarm
message is acknowledged (e.g., ‘Q’).
Columns Resizeable Boolean True: the columns are resizeable.
Date Format String The value represents the date format for the
column types ’Date’ and ’Date and Time’. If
it is not defined, the system date format
(configured in the regional options) is used.
Description String Comment
Font String Used font (e.g., ‘MS Sans Serif’).
Font Size Short Integer Used font size (e.g., ‘8’).
Maximum Entries Long Integer Maximum number of entries. Only the new-
est entries are displayed, if the number of
existing messages / alarms tops this value.
Read Only Boolean True: Operator actions like acknowledging
or adding comments are not allowed (no
pop-up menu is available).
Show Column Title Boolean True: Column titles are displayed
Show Status Bar Boolean True: Status bar is displayed
Sizeable Boolean True: the summary size is changed, after
the window size has been changed.
Time Format String The value represents the date format for the
column type ’Time’. If it is not defined, the
system date format (configured in the
regional options) is used.
Unacknowledged Alarm String The value is displayed in the column of the
Indication column type ’Acknowledge’, if an alarm
message is not acknowledged (e.g., ‘A’).
Unacknowledged Alarm String This icon is additionally displayed for indi-
Indication Icon cating an unacknowledged alarm message.
Update Cycle Long Integer The value represents the cycle time of
reloading data (unit: milliseconds).
The following advanced summary parameters like the background color or the used
toolbar buttons may be specified on the Links page of the appropriate Alarm Control
instance (of the type ’AlarmControl’). These parameter values represent associations
to other instances and may be entered by Drag & Drop from the instance tree.
Table 2-4.6: Advanced Summary Parameters (Links Page)

Association Description
Alternate Background Color Defines the alternate background color of the summary.
Background Color Defines the background color of the summary.
Alarm Control Button Defines the used toolbar buttons. In this input field multiple
instances may be entered.

Summary Defines the summary instance(s) where the specified char-

acteristics are displayed. In this input field multiple instances
may be entered.
2-4.1.6 Configure a New Alarm Control Instance
This example describes the flow of dialog steps when the user configures a new Alarm
Control instance for electric network summary instances:
• Browse to the instance ’General/Alarm Configuration/Alarm Controls- Electricity’

• Right-click the instance ’Alarm Controls- Electricity’. This opens the instance tree
pop-up menu.
This figure shows the type selection display for configuring a new alarm control
instance
Figure 2-4.3: Type Selection
• Select the type ’AlarmControl’ from the type list and click the button Create

This figure shows the General Page of the Single Editor (AlarmControl)
• Enter ’E - Summary New’ into the attribute value field Name. This value
– Alarm Control Sort Order: ’Ascending Time’
– Columns Resizeable: ’True’
– Date Format: ’%m/%d/%y’
– Time Format: ’%H:%M:%S:%I’

• Enter the corresponding color instances, button instances and the summary
instance into the following association value fields (by Drag & Drop from the
instance tree):
– Alternate Background Color: e.g., ’.General/Color Group - Summaries/
General Summary - BgColor 2’
– Background Color: e.g., ’.General/Color Group - Summaries/General

Summary - BgColor 1’
– AlarmControlButton: e.g., ’.General/Alarm Configuration/Alarm Controls-

Common/_alarm Control Buttons/Sort On_off’; etc.
In this field multiple button instances may be entered.
– Summary: e.g., ’.General/Alarm Configuration/Summaries - Electricity/E -

General Summary’
• Save the new instance ’E - Summary New’. The new instance is displayed in the
instance tree.
• Right-click the instance ’E - Summary New’. This opens the instance tree pop-up
menu.
• Select the type ’AlarmControlColumn’ from the type list and click the button
General page:
This figure shows the General Page of the Single Editor (AlarmControlColumn )
• Enter e.g., ’Date Time’ into the attribute value field Name. This value represents


– Alarm Control Column Type: ’Date and Time’
– Column Title: e.g., ’Time Stamp’
– Display Order: ’1’
• Save the new instance ’Date Time’. The new instance is displayed in the instance
tree.
• Repeat the steps 12 to 18 to specify additional columns like technological

addresses (e.g., path 1 to 5) etc.
2-4.2 Message Configuration

A Message Configuration instance is used to configure all messages of an instance.
Each Message Configuration instance has an unique identification number. It has a
link to a message type for each event type. This defines the message type, which has
to be used for creating the different messages.

This figure shows the Message Configuration, Type and Summaries
Figure 2-4.9: Message Configuration and Message Types
One instance may trigger different messages, e.g., a digital measurement may be
controlled, manually updated, change spontaneously, etc.
The cause of a message (event type) may be:
• Spontaneous change (e.g., limit violation, server failure, etc.)
• Supervisory control command was sent
• Supervisory control response was received

• Supervisory control time out
• Data point was manually updated
• Marker was set
• Abnormal state message
• Operator entry (e.g., AGC)
The following sections describes, which parameters the user may basically configure
for a message. For detailed information on creating a Message Configuration instance
refer to Chapter 2-4.2.3 Configure a New Message Instance.
2-4.2.1 Message Attributes and Associations
The user may define the following message attributes on the Attributes page of the
appropriate Message Configuration instance (of the type ’MessageConfiguration’):
Table 2-4.7: Message Attributes (Attributes Page)

Message Attributes Description
Description Comment
Message Category Defines the message category (e.g., Category 1). The
value may be used for summary filtering.
Message Configuration ID Unique identification number/name of the message.
The association between a message and the message types may be configured on the
Links page of the appropriate Message Configuration instance (Table 2-4.8). The user

may enter the message type values by Drag & Drop from the instance tree. For more
information on message types refer to Chapter 2-4.2.2 Message Type.
Table 2-4.8: Message Associations (Links Page)

Association Description
Abnormal Message Type Defines the message type for abnormal state messages.
Alarm Inhibit Message Type Defines the message type for messages created while the
Alarm Inhibit tag is set.
Control Response Message Type Defines the message type for ’control response’ mes-
sages.
Control Sent Message Type Defines the message type for ’control sent’ messages.
Marker Message Type Defines the message type for ’apply marker’ messages.
Object In Test Defines the message type for messages created while the
Object In Test tag is set.
Operator Entry Message Type Defines the message type for operator entries (e.g., AGC).
Spontaneous Message Type Defines the message type for spontaneous alarms.
Time Out Message Type Defines the message type for ’time out’ messages.
Update Message Type Defines the message type for ’manual update’ messages.
2-4.2.2 Message Type
A Message Type instance is used to configure one single message. It defines the
appearance, the acknowledge behavior, all relevant summaries, etc. of a message
(e.g., a spontaneous state change of a circuit breaker).
The user may define the following message type attributes on the Attributes page of
the appropriate Message Type instance (of the type ’MessageType’):
Table 2-4.9: Message Type Attributes (Attributes Page)

Message Type Attributes Description
Description Comment
Long Term Archive Defines whether or not the message is stored in the long
term archive.
Message Class Defines the message class, refer to Table 2-5.10.
Message Priority Defines the message Priority (e.g., Priority 1). The value
may be used for summary filtering.
Message Type Indication The value may be used for summary filtering.
Table 2-4.10: Message Classes

Message Classes Description
Alarm_AD The message has an appearing and a disappearing event.
Neither the appearing nor the disappearing event need to
be acknowledged.
Alarm_Aa The message has only an appearing event, which needs
to be acknowledged (e.g., fleeting and special digital
alarms).
Alarm_AaCl The message has only an appearing event, which needs
to be acknowledged. The message is displayed in the
summary until it is removed by the user.

Alarm_AaD The message has an appearing and a disappearing event.

Only the appearing event needs to be acknowledged.
Alarm_AaDa The message has an appearing and a disappearing event.
Both need to be acknowledged (e.g., limit violation).
Alarm_Ada The message has an appearing and a disappearing event.
Only the disappearing event needs to be acknowledged.
The message type associations may be configured on the Links page of the
appropriate Message Type instance (Table 2-4.11). The user may enter the
association values by Drag & Drop from the instance tree. The appropriate color and
sound instances are located underneath the instances ’.General/Color Palettes/ Color/
Group’ and ’.General/Sounds’.
Table 2-4.11: Message Type Associations (Links Page)

Message Type Associations Description
Acknowledge Color Color of the acknowledge event (not always relevant).
Appearing Color Color of the appearing event.
Appearing Sound Sound description of the appearing event.
Disappearing Color Color of the disappearing event (not always relevant).
Disappearing Sound Sound description of the disappearing event.
Summary Summary(ies), where the message must be displayed
(refer to Section 2-5.3).
2-4.2.3 Configure a New Message Instance
message instance of ’Category 2’ for electric network instances:
• Browse to the instance ’General/Alarm Configuration/Message Config - Electricity’

• Right-click the instance ’Message Config - Electricity’. This opens the instance
tree pop-up menu.
• Select the type ’MessageConfiguration’ from the type list and click the button
General page:
This figure shows the General Page of the Single Editor (MessageConfiguration)

• Enter ’E - Message New’ into the attribute value field Name. This value represents
– Message Category: ’Category 2’
– Message Configuration ID: ’E_Message’
• Enter the corresponding message type instances of the instance ’General/Alarm

Configuration/Message Types - Electricity’ into the following association value
fields (by Drag & Drop from the instance tree):
– Abnormal Message Type: ’.General/Alarm Configuration/Message Types -

Electricity/Abnormal’
This value defines the message type for abnormal state messages.
– Alarm Inhibit Message Type: ’.General/Alarm Configuration/Message Types -

Electricity/Inhibit’

This value defines the message type for messages created while the alarm
inhibit tag is set.
– Control Response Message Type: ’.General/Alarm Configuration/Message

Types - Electricity/Ctrl Resp’
This value defines the message type for ’control response’ messages.
– Control Sent Message Type: ’.General/Alarm Configuration/Message Types -

Electricity/Ctrl Sent’
This value defines the message type for ’control sent’ messages.
– Marker Message Type: ’.General/Alarm Configuration/Message Types -

Electricity/Marker’
This value defines the message type for ’apply marker’ messages.
– Object In Test Message Type: ’.General/Alarm Configuration/Message Types

- Electricity/In Test’
This value defines the message type for messages created while the Object
In Test tag is set.
– Operator Entry Message Type: ’.General/Alarm Configuration/Message

Types - Electricity/Operator_Entry’
This value defines the message type for operator entries.
– Spontaneous Message Type: ’.General/Alarm Configuration/Message Types

- Electricity/Spont_Msg’
This value defines the message type for spontaneous alarms.
– Time Out Message Type: ’.General/Alarm Configuration/Message Types -

Electricity/Time Out’
This value defines the message type for ’time out’ messages.
– Update Message Type: ’.General/Alarm Configuration/Message Types -

Electricity/Update’
This value defines the message type for manual update messages.
• Save the new instance ’E - Message New’. The new instance is displayed in the
instance tree.
2-4.3 Summary
A Summary Instance is used to configure the general parameters of a summary, like
the maximum number of entries or the used message configuration type.
The (network-specific) Summary instances are located underneath the instance

’.General/Alarm Configuration’ in the instance tree. The user may configure the

following Summary attributes on the Attributes page of the appropriate Summary

instance:
Table 2-4.12: Summary Attributes (Attributes Page)

Summary Attributes Description
Area of Responsibility ID Unique name of the Area of Responsibility (e.g., Area A).
Description Comment
Message Configuration Name of the Message Configuration instance (refer to Sec-
tion 2-5.2). The user may also select a default message
configuration.
Number of Entries Maximum number of entries (e.g., ’1000’). This attribute is
only relevant for the summary type ’General Summary’.
Reload Summary True: the summary is reloaded at system start-up.
Summary ID Unique summary identification number.
Summary Type Refer to Table 2-5.13.
The user may configure the following summary types:
Table 2-4.13: Summary Types

Summary Types Description
General Summary This summary type is used to configure a General Sum-
mary. A General Summary is implemented as a revolving
buffer. Basically, a General Summary is persistent. This
means, that it is recovered at system start-up.
Alarm Summary This summary type is used to configure an Alarm Sum-
mary (e.g., AlarmPrio1). Basically, an Alarm Summary is
not persistent, because all relevant alarm messages are
recreated during system start-up.
Message Summary This summary type is used to configure a Message Sum-
mary (e.g., Abnormal State Summary). An entry is created,
when the message is appearing. The entry is removed,
when the message is disappearing.
2-4.4 Configure a New Summary

This example describes the configuration of a new Alarm Summary with the message
type 'Priority 4':
• Create a new Alarm Summary called 'Priority 4', e.g., by Copy & Paste of the
Alarm Summary with the message type 'Priority 3':
– Summary Type = Alarm Summary.
– Reload Summary = False.
– Number Of Entries = 0 (this attribute is only relevant for the summary type
’GeneralSummary’).
– Summary ID = 7 (next free identification number).
• Create a new Message type instance called ’MsgType_4_AaD’, e.g., by Copy &
Paste of a corresponding Message Type instance (’*_AaD’):
– Remove the link from the new Message Type instance ’MsgType_4_AaD’ to
the Alarm Summary 'Priority 3'.

– Create a link from the new Message Type instance ’MsgType_4_AaD’ to the
new Alarm Summary 'Priority 4'.
– The message class is ’Alarm_AaD’.
– Change the links to the color and sound instances, if required.
• Create a new Message Configuration instance called 'MsgConfig_4_AaD', e.g., by

Copy & Paste of a corresponding Message Configuration instance (’*_AaD’):
– Remove the link from MsgConfig_4_AaD to MsgType_3_AaD
– Create a link from MsgConfig_4_AaD to MsgType_4_AaD
Now the new Message Configuration instance 'MsgConfig_4_AaD' may be used for
e.g., limit violations with the message type ’Priority 4’. If there are also other alarms
(e.g., digital alarms) with the message type ’Priority 4’, step 2 and step 3 must be
repeated with the configuration of the appropriate message class.
2-4.5 Configure Group Alarms

Group alarms can be configured for categories (e.g., ’Category1’), areas (e.g. ‘Sub A’)
and the combination of category and area (e.g., ’Category1’ in ‘Sub A’).
Group alarm instances are linked to a state set with these values:
• 0 – No Alarms
• 1 – Active alarms
• 2 – Unacknowledged disappearing events
• 3 – Unacknowledged appearing events
The following examples describe the configuration of different group alarm indicators:
• Configure a group alarm indicator representing alarms with category 1:
Create an instance of the type ‘GroupAlarmIndicator’ somewhere in the data

model. Set the attribute ‘Category’ to Category1 and the attribute ‘Use Parent
Area’ to FALSE.
• Configure a group alarm indicator representing alarms for Sub A:
Create an instance of the type ‘GroupAlarmIndicator’ as child object of ‘Sub A’.

Set the attribute ‘Category’ to NO_Category and the attribute ‘Use Parent Area’ to
TRUE.
• Configure a group alarm indicator representing category 2 alarms for Sub B:
Create an instance of the type ‘GroupAlarmIndicator’ as child object of ‘Sub B’.

Set the attribute ‘Category’ to Category2 and the attribute ‘Use Parent Area’ to
TRUE.
• Configure a group alarm indicator representing ‘Alarm Priority 1’ summary:
Create an instance of the type ‘GroupAlarmIndicator’ as child object of ‘Alarm Pri-

ority 1’. Set the attribute ‘Category’ to NO_Category and the attribute ‘Use Parent
Area’ to TRUE.
• Configure a group alarm indicator representing category 3 alarms in ‘Alarm
Priority 2’ summary:

Create an instance of the type ‘GroupAlarmIndicator’ as child object of ‘Alarm Pri-

ority 2’. Set the attribute ‘Category’ to Category3 and the attribute ‘Use Parent
Area’ to TRUE.
2-4.6 Add the Toolbar Button “Clear Summary“ to an Alarm Test

Summary
The toolbar button “Clear Summary“ of an alarm test summary allows the user to clear
the content of the Alarm Test Summary.
• Select the tabbed page ’Links’ of the corresponding test summary instance
(Figure 2-4.11).
• Right-Click the input field ’Value’ of the association row ’AlarmControlButton’. A

pop-up menu opens.
• Select the menu item ’Add Link’ from the pop-up menu. A new input field is
displayed in the association row ’AlarmControlButton’.
• Enter the pathname of the toolbar button ’Clear Summary’ by Drag & Drop from
the instance tree.
• Save the test summary instance.
This figure shows the Configuration of the Toolbar Button "Clear Summaries"
Figure 2-4.13: Configuration of the Toolbar Button "Clear Summaries"

2-5 Supervisory Control
2-5.1 Interlocking Rules

The Information Model Management is used to define generic and topological interlock
rules for network components in the power network system.
The user may define:
• Individual Rule instances (e.g., IsIsolated, IsRemote, NotGrounded, etc.).
• An attribute for each rule, that specifies, if an operator is allowed to override the
rule.
• A Rule Set instance for each controllable equipment type in the system (e.g.,
breaker, disconnect, step position, etc.). The Rule Set instance may be linked to
multiple Rule instances.
• A violation description for each Rule instance.

This figure shows the Interlocking Rule Instances
Figure 2-5.1: Interlocking Instances

2-5.1.1 Configure a New Rule Set
This example describes the flow of dialog steps when the user configures a new Rule
Set instance (e.g., a Rule Set instance ’Generator’):
• Browse to the instance ’.General/Interlocking/Rule Sets - Electricity’ in the

instance tree.
• Right-click the instance ’Rule Sets - Electricity’. This opens the instance tree pop-
up menu.
This figure shows the type selection display for configuring a new interlocking rule set
instance
• Select the type ’InterlockingRuleSet’ from the type list and click the button Create
This figure shows the General Page of the Single Editor (InterlockingRuleSet)
Figure 2-5.3: General Page of a Single Editor

• Enter ’Generator’ into the attribute value field Name. This value represents the
This figure shows the Attributes Page of a Single Editor
Figure 2-5.4: Attributes Page of a Single Editor
• Enter the object type ’SynchronousMachine’ into the attribute value field Default
Object Type.
This figure shows the Links Page of a Single Editor
Figure 2-5.5: Links Page of a Single Editor
• Enter the desired Rule instances (e.g., IsRemote, etc.) into the association value
field Interlocking Rule (by Drag & Drop from the instance tree). The Rule
instances are located underneath the instance ’.General/Interlocking/Rules’.
• Save the new instance ’Generator’. The new instance is displayed in the instance
tree.
2-5.2 Control Execution Monitoring

Once a control request is transmitted (after proper interlock validation), the status of
the device being controlled is monitored until either the control action completes
successfully or the configured time-out period expires. Control time-out periods are
device dependent and, once defined or changed, are activated into the real-time
system.
The Information Model Management is used to define:
• Execution time-out period per device (1 - 300 seconds)
• Transmission time-out periods for control actions that may occur over a data link
to another control center

2-6 Manual Database Manipulations
2-6.1 Marking and Tagging
2-6.1.1 General
Figure 2-6.1 shows the marker/tag configuration instances:
• Network components where tags and markers can be applied (Markables Types)
• Marker types as currently configured in the instance tree (Marker Types)

This figure shows Marker/Tag Configuration Instances
Figure 2-6.1: Marker Related Instances
Note
Markers are also considered by the interlocking supervisory conditions.
2-6.1.2 Link a Marker Type to a Network Component
This example describes the flow of dialog steps when the user links a predefined
marker type to a network component (e.g., generator) and configures a markable type,
respectively:
• Browse to the instance ’General/Marker/Markable Type - Electricity’ in the

instance tree.
• Right-click the instance ’Markable Type - Electricity’. This opens the instance tree
pop-up menu.

This figure shows the type selection display for linking a marker type to a network
component
• Select the type ’MarkableObjectType’ from the type list and click the button Create
This figure shows the General Page of the Single Editor (MarkableObjectType)
• Enter ’Generator’ into the attribute value field Name. This value represents the

• Enter the object type ’SynchronousMachine’ into the attribute value field Object
Type Name.
• Enter the desired marker type instance (e.g., ’General/Marker/Marker Types/

Marker - Note’ into the association value field MarkerType (by Drag & Drop from
the instance tree).
Note
Multiple marker type instances can be entered into the association value field
MarkerType.
• Save the instance ’Generator’. The new instance is displayed in the instance tree.
2-6.2 Manual Updating

No configuration required.
2-6.3 Alarm Acknowledgement

Described in the Chapter 2-4 Message Summaries.

SCADA 2-7 Report Generation
2-6.4 Substation Request

The configuration of substation requests follows the configuration for supervisory
control. The execution control time must be set to zero to avoid time-out error
messages.
2-7 Report Generation

The report templates are stored in the database. For each category a default report is
available which contains all information about the maximal columns and filters. The
user may use this report as a 'base report' from which he/she may derive new reports.
The system configuration context contains the hierarchically structured reports:

2-7 Report Generation SCADA
This figure shows the Hierarchy of Reports in the Application Configuration Context
Figure 2-7.1: Report Hierarchy in the Application Configuration Context

This figure shows the preconfigured report instances
Figure 2-7.2: Preconfigured Report Instances
The instance ’ReportGenerator’ is the parent instance of a 8-level report hierarchy

within the instance tree. The attributes of the instance ’ReportGenerator’ are shown in
Table 2-7.1.
Table 2-7.1: Type ’ReportGenerator’

Attribute Name Description Data Type Default
Name Name of base report String
folder
ReportGeneratorLabel Label of this folder String Name of folder
The child instances of the instance ’Configurations/Global Configuration/Report

Generator’ defines the data source:
• SCADA
• HIS
• Energy Accounting
• Other project specific sources, e.g., a particular application
The data source is represented by the type ’RGCategoryFolder’. The attributes of this
type are shown in Table 2-7.2:
Table 2-7.2: Type ’RGCategoryFolder’

Name Name of base report folder String
RCCategoryFolderLa- Label of this folder, is dis- String Name of folder
bel played in the List pane of the
Report Generator

The second level is a specification of the data source and is represented by the type
’RGSubFolder’. The attributes of this type are shown in Table 2-7.3:
Table 2-7.3: Type ’RGSubFolder’

Name Name of base report folder String
RGSubFolderLabel Label of this folder, is dis- String Name of folder
played in the Tree pane of the
Report Generator
The third level contains the views on the underlying report, represented by the type
’ViewAttributes’. The attributes of this type are shown in Table 2-7.4:
Table 2-7.4: Type ’ViewAttributes’

DataType Data type of the data in the String Take from corre-
database. The following data sponding attribute
types are provided: in ‘default’ view.
- String - Date
- Integer - Long
- Floating - Double - Bool
- Short int
FilterString String which contains filter crite- String
ria for the specified attribute.
FilterPrompt Defines whether a prompt mes- Boolean False
sage box pops up at runtime
when the user starts generating
the report. In this case the user
has the possibility to assign fil-
ter criteria each time before the
report is generated.
BrowseQuery String which contains informa- String
tion about the data which is dis-
played when the user clicks on
the ‘browse’-button (descrip-
tion see later). Can be a ‘select
… from’ statement for example.
2-A Glossary
AGC Automatic Generation Control
AOR Area Of Responsibility

CCAPI Control Center Application Program Interface
An EPRI research project aiming to reduce the cost and time needed to add new
applications to an Energy Management System (EMS), and protecting the investment
in existing applications that are working effectively in an EMS. The Common
Information Model (CIM) is a result of the EPRI CCAPI project.
CFE Communications Front End
The CFE is a PC-based process interface for coupling RTUs of different manufacturers
to the Spectrum PowerCC distributed control center system.
CIM Common Information Model, IEC61970
COP Current Operating Plan
DMS Distribution Management System
DOM Domain Object Model
Event - Alarm - Message An event arises in the network field and is recorded as a message in the General
Summary. Events that have been configured as alarms, are entered as a message into
the General Summary and into appropriate Alarm Summaries. An alarm usually
requires operator acknowledgment.
HIS Historical Information System
HIS provides the capability to store, in a commercial Relational Database

Management System (RDBMS), historical data such as analog, accumulator, and
digital measurements, alarms, application messages, and historical schedule data.
ICCP Inter Control Center Communications Protocol, IEC60870-6
ICCP provides data exchange over network (WAN or LAN) between a utility control
center and other systems like power pools, regional control centers, etc.
IEC International Electrotechnical Committee
IMM Information Model Management
Marker - Tag Markers and tags are used to identify points with special processing requirements.
Markers and tags (indicators) can be manipulated during system run-time.
Tags are markers used to identify points with control restrictions.
OPC OLE (Object Linking and Embedding) for Process Control
Process data interface protocol for process communication and communication to

automation systems.
PAT Power Application Toolbar
PSOS Power System Object Server

Quality Code Quality codes are set and removed by applications in response to specific conditions
or operator actions and indicate the quality status of a data value. One code may
indicate whether a displayed value is correct and reliable (valid or invalid). If an object
value is invalid, the code indicates why. Another code may be used to indicate what
type of processing was used to create the value. For example, a value may have been
scanned from an RTU, calculated by data processing, or estimated by an application.
Quality codes are relevant to certain applications and to operators who view the values
on real-time or historical displays. Quality codes are assigned internally and stored in
generated events. Although operators / dispatchers cannot directly manipulate quality
codes, the codes provide information that users need for determining whether or not a
value is valid and, if it is invalid, the reason why.
RAP Real-time Accumulator Processing
RDBMS Relational Database Management System
SCADA Supervisory Control And Data Acquisition
SPM Switching Procedure Management
SVG Scaleable Vector Graphic file format
Web Browser A software that allows users to view content from the Internet or an Intranet.
WinCC Windows Control Center
A software package that supports Human Machine Interface (HMI) functionality for
process automation on standard PCs running Windows NT.
WMF Windows Meta Files
XDF eXchange Data Format
The eXchange Data Format (XDF) is an XML-based text (ASCII or UNICODE) format
for importing and exporting data model information and engineering data. The usage of
XML allows third party products to be used for editing and pre-validating data. Data
model extensions and engineering data can be implemented quickly and easily by
extending the XML Data Type Definitions to agree with changes made to the Spectrum
PowerCC database.
XDF is the preferred format for bulk data import to Spectrum PowerCC, both for initial
(bulk) and incremental input.
XML eXtensible Markup Language
XML is a versatile document description language. It is a text-based (ASCII or

UNICODE) meta language that provides means for defining tags to identify
components of a document.

Spectrum Powercc Scada: Reference Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Spectrum Powercc Scada: Reference Guide

Uploaded by

Copyright:

Available Formats

Spectrum PowerCC

2 Copyright © Siemens AG 2005. All rights reserved. Release 07 / 2005

Warning Conventions Table 0.1: Warning Conventions

2 WARNING WARNING indicates a potentially hazardous situation

3 CAUTION CAUTION used with the safety alert symbol indicates

4 CAUTION CAUTION used without safety alert symbol indicates

Release 07 / 2005 Copyright © Siemens AG 2005. All rights reserved. 3

Copyright Copyright © Siemens AG 2005. All rights reserved

This document is protected by German Copyright law and international contracts as

Trademarks Spectrum PowerCC® is a registered trademark of Siemens AG. An unauthorised use

The remaining descriptions in this documentation/information could be trademarks, the

4 Copyright © Siemens AG 2005. All rights reserved. Release 07 / 2005

Release 07 / 2005 Copyright © Siemens AG 2005. All rights reserved. 5

Version Date Modification

3.1.0/Draft Apr-2003 Additions/Modifications according to new functionalities in Pow-

6 Copyright © Siemens AG 2005. All rights reserved. Release 07 / 2005

When applicable, other Spectrum PowerCC documents may be referenced as sources

• Spectrum PowerCC SCADA Technical Specification

• Spectrum PowerCC Information Model Management Technical Specification /

• Spectrum PowerCC CFE Technical Specification/CFE Reference Guide

• Spectrum PowerCC ICCP Technical Specification/ICCP Reference Guide

• Spectrum PowerCC System Management Technical Specification/System

• Siemens WinCC User Guide

• Siemens WinCC Getting Started Tutorial

Release 07 / 2005 Copyright © Siemens AG 2005. All rights reserved. 7

8 Copyright © Siemens AG 2005. All rights reserved. Release 07 / 2005

Volume 1 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

1-3 GRAPHIC DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Release 07 / 2005 Copyright © Siemens AG 2005. All rights reserved. 9

1-3.4 Trend Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1-4 TABULAR DISPLAYS (RUNTIME EXPLORER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

1-5 MESSAGE SUMMARIES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

1-6 SUPERVISORY CONTROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

1-7 MANUAL DATABASE MANIPULATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

10 Copyright © Siemens AG 2005. All rights reserved. Release 07 / 2005

1-7.1 Marking and Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

1-8 REPORT GENERATOR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Volume 2 Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

2-2 CONSOLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Release 07 / 2005 Copyright © Siemens AG 2005. All rights reserved. 11

2-2.4.3 Global Audible Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

2-3 GRAPHIC DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

2-4 MESSAGE SUMMARIES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

12 Copyright © Siemens AG 2005. All rights reserved. Release 07 / 2005

2-5 SUPERVISORY CONTROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

2-6 MANUAL DATABASE MANIPULATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

2-7 REPORT GENERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Release 07 / 2005 Copyright © Siemens AG 2005. All rights reserved. 13

14 Copyright © Siemens AG 2005. All rights reserved. Release 07 / 2005

1-1.1 Standard MS Windows

The Spectrum PowerCC user interface provides:

Release 07 / 2005 Copyright © Siemens AG 2005. All rights reserved. 15

This figure shows Multiple Overlapping Windows

Figure 1-1.1: Multiple Windows

– Multiple applications run in multiple overlapping windows (up to 10 windows

– Windows may be placed on 1 to 4 screens per console. They may be moved

• Standard windows elements

This figure shows a Standard Window

Figure 1-1.2: Example of a Standard Window

– Title bar on top of the window.

16 Copyright © Siemens AG 2005. All rights reserved. Release 07 / 2005

– Minimize button to iconize the window.

– Close button (window disappears from screen)