Power Systems Control

Spectrum Power™ 4
Version 4.70

ERS-SCADA-2015-KFW

Functional Specification
ICCP Data Link
F-CA01 Version 2.6.1.0, Restricted July 2017
Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

We reserve the right to make technical alterations. The information contained in the figures is not binding.
It is expressly forbidden to pass on or copy this document or to make use of or communicate the information it
contains without the appropriate authority to do so.

Anyone contravening this provision will be liable to pay damages.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 2 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

Proprietary Notice
Spectrum Power™ 4 is a registered trademark of Siemens.

All trademarks used in this publication can be trademarks the use of which by third parties for their own
purposes could violate the rights of their owners.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 3 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

Revision History

Version Date Author/ Department Approver/Department Modifications

Esterhammer Arno
2.6.1.0 July 2017 Adaptations for ERS
RC-AT EM DG
Gabriele Pflanzer/
2.6.0.0 August 2013 Correction tue to SPR 44894
IC SG EA SOL
Helmuth Schwarzjirg/ Release 4.70
2.5.0.0 August 2011
CT DC E Addition due to SYS-NF9 (Secure ICCP)
Helmuth Schwarzjirg/
2.4.0.0 April 2010 Addition due to SPR41485
CT DC E
2.2.0.0 May 2006 Minor corrections (SPR 36466)
2.1.0.0 January 2006 Formal adaptation to release 4.5
2.0.0.0 March 2004 Adaptation to release 4.4
1.3.0.0 October 2001 Additions in Release 4.3.3.
1.2.0.0 October 2001 Minor corrections
1.1.0.0 August 2001 Updated
1.0.0.0 August 1998 First edition

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 4 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

Table of Content

1 Introduction ....................................................................................................................................................... 7
1.1 ICCP Communications Protocol (TASE.2) ................................................................................................ 8
1.2 ICCP Associations...................................................................................................................................10
1.3 Bilateral Tables........................................................................................................................................10
1.4 Objects and Services ..............................................................................................................................11
1.4.1 Data Value Objects and Services ......................................................................................................11
1.4.2 Account Objects .................................................................................................................................11
1.4.3 Data Sets/Transfer Sets ....................................................................................................................11
1.4.4 Transfer Group...................................................................................................................................12
1.4.5 Device Objects/Services ....................................................................................................................12
1.4.6 Information Buffer Objects .................................................................................................................12
1.5 Data Transfer Mechanisms .....................................................................................................................13
1.5.1 Periodic Data .....................................................................................................................................13
1.5.2 Event Data .........................................................................................................................................13
1.5.3 Exception Data...................................................................................................................................13
1.6 Protocol Implementation Conformance Statement (PICS) .....................................................................14
1.6.1 Basic Protocol and Services ..............................................................................................................15
1.7 Object Models .........................................................................................................................................21
1.8 Architecture .............................................................................................................................................23
1.9 Inter-Networking Considerations .............................................................................................................23
1.10 The ICCP Model ................................................................................................................................24
1.10.1 ICCP Associations .........................................................................................................................25
1.10.2 Bilateral Tables (Agreements) .......................................................................................................26
1.10.3 Data Value Objects and Services ..................................................................................................27
1.10.4 Data Set Objects and Services ......................................................................................................27
1.10.5 Information Message Objects and Services ..................................................................................27
1.10.6 Transfer Set Objects and Services ................................................................................................28
1.10.7 Data Transfer Mechanisms ............................................................................................................29
1.10.7.1 One Shot Data .......................................................................................................................29
1.10.7.2 Periodic Data .........................................................................................................................29
1.10.7.3 Event Data .............................................................................................................................29
1.10.7.4 Exception Data.......................................................................................................................29
1.10.8 Special Transfer Objects ...............................................................................................................30
1.10.9 Device Objects/Services. ...............................................................................................................30
2 Functional Overview .......................................................................................................................................31
3 Functional Description ....................................................................................................................................32
3.1 Basic Services (Block 1) .........................................................................................................................32
3.1.1 Client Functions .................................................................................................................................32
3.1.2 Server Functions ................................................................................................................................33
3.2 Conditions (Block 2) ................................................................................................................................34
3.3 Information Messages (Block 4)..............................................................................................................34
3.4 Device Control (Block 5) .........................................................................................................................35
4 ICCP Configuration.........................................................................................................................................36
4.1 ICCP Start-Up .........................................................................................................................................36
5 Redundancy Characteristics ..........................................................................................................................37
6 User Interface .................................................................................................................................................38
A ICCP Configuration.........................................................................................................................................39
B Interface Overview..........................................................................................................................................40
B.1 Computer Network Management................................................................................................................40
B.2 Softbus/CNM ..............................................................................................................................................40
B.3 Operational Database .................................................................................................................................40

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 5 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

B.4 Application Database ..................................................................................................................................41

B.5 SDM Interface .............................................................................................................................................41
C Sample Displays .............................................................................................................................................42
C.1 Common Data Link Status and Control Display .........................................................................................42
C.2 Set Data Status and Control Display ..........................................................................................................43

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 6 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1 Introduction
The Spectrum Power™ 4 function ICCP Data Link provides bi-directional data exchange over wide area
networks (WANs) between the local control center and other remote control centers using the Inter Control
Center Communications Protocol (ICCP). Examples of other control centers include neighboring utilities, power
pools, regional control centers, and non-utility generators. Data exchanged may include realtime information,
such as analog values, status indications and operator messages. Data exchange occurs between a
SCADA/EMS/DMS host of one control center and the host of another control center. The data exchange path
may traverse one or more intervening communications processors.

ICCP has been designed to provide a general purpose communication protocol for use within the utility industry.
The ICCP standards are “companion standards” of the Manufacturing Message Specification (MMS) and ICCP
is a user of MMS services. The intent of ICCP is to provide a standard protocol for data exchange between
control centers.

The ICCP protocol is an International Standard and the official name is “TASE.2” (Telecontrol Application
Service Element, part 2). The names “TASE.2” and “ICCP” are synonymous. “ICCP” will be used throughout this
document.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 7 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.1 ICCP Communications Protocol (TASE.2)

The Inter-control Center Communications Protocol (ICCP referred to as TASE.2 in IEC vernacular) allows for
data exchange over Wide Area Networks (WANs) between a utility control center and other control centers,
utilities, power pools, regional control centers, and Non-utility generators or any other computer systems that
also use ICCP. ICCP data exchange consists of real-time power system monitoring and control data.
In the sample configuration below, ICCP links are configured between Spectrum Power™ 4 Sites A to B and be-
tween SINAUT Spectrum Site A to a Foreign System Site C. Communications between servers is done using
routers and other network equipment that support TCP/IP or OSI communications (even though OSI is
supported, OSI is not recommended due to its decline of use in the industry).
Sites B and C (Figure 1) must define the respective bilateral tables prior to exchanging data. The bilateral table
consists of agreements between two control centers on the type of data that will be exchanged and other
communication characteristics such as data transfer volume and frequency.
The ICCP data link supports a redundant configuration utilizing dual Communication Servers. A redundant con-
figuration supports two physically separate paths between the Spectrum Power™ 4 system and the remote sys-
tem to provide back-up in the event the primary data path becomes unavailable.

Figure 1 Sample ICCP Configuration

Spectrum
Power4 RTU Front End SCADA
(Site A) Server Server

ICCP Spectrum
Power4
(Site B)
ICCP
RTU Front End
Server
ICCP
Other
System SCADA
Server
Other
Control Center
(Site C)

A key component of the ICCP protocol is the Manufacturing Message Specification (MMS). By definition, MMS
is an ISO standard for communicating information between intelligent devices in a manufacturing environment
over networks based upon the OSI reference model (MMS technology has also been applied to areas other
than manufacturing including weather instrument control, radar control, inter-utility data exchange, electric utility
substation control, etc.). The ICCP protocol relies on the ISO MMS services (and hence the underlying MMS
protocol) to implement the exchange of data between computer systems.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 8 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

The ICCP protocol defines a standardized method of using MMS services for transferring data between
systems. Data is represented by object instances and the ICCP Services and Protocol Specification defines
object instances. The ICCP object models represent objects for data transfer between systems. Data
transmission using ICCP can be configured using the Spectrum Power™ 4 Source Data Manager (SDM). The
values to be defined include the communication partners, the information to transfer, and the access rights. All
input is immediately (on-line) valid upon activation.
The ICCP Conformance Blocks supported by Spectrum Power™ 4 are summarized below:
 Block 1 - Basic Services - Consists of the transfer of real-time cyclic data.
 Block 2 - Conditional Transfers - Consists of the transfer of real-time data by exception.
 Block 4 - Information Messages - Information Messages consists of the transfer of messages between
operators at the local and remote control center.
 Block 5 - Device Control - Supports the ability to issue supervisory control operations from the local control
center to the remote system.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 9 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.2 ICCP Associations

The ICCP association concept is based upon the MMS model. Associations occur between two ICCP instances
and are typically long lasting. The associations are usually established when the two instances initiate and
remain in place as long as the instances continue to run and the communications connections between the
associations remain intact. ICCP instances normally remain running until an exception condition (e.g., off-line
maintenance, error, operator shutdown, etc.) occurs.

1.3 Bilateral Tables

A Bilateral Agreement is usually a document developed by two control centers which includes the objects (i.e.
data and control objects) which each is willing to make available to the other. For each object, the Bilateral
Agreement specifies its name, type, and the access control permissions by other control centers. The Bilateral
Agreement does not specify when and how often to receive which data from the remote control center.
In Spectrum Power™ 4, Bilateral Agreement information is stored in a bilateral table, which is defined through
the Source Data Manager (SDM). The Bilateral Table information for a data object identifies the access
methods for that object by each client. Access methods (permissions) for an object may be different for different
clients, for example, for the same object, one client may have read/write access, another may have read
access, and a third may have no access. Transfer Conditions for a data object identify the conditions under
which the object will be transmitted to a client.
In Spectrum Power™ 4, the configuration of Bilateral Table and Transfer Condition information, like all
configuration information, are entered through the SDM graphical user interface provided with the system. This
configuration information is transferred into the run-time operational database used by the ICCP run-time
software.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 10 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.4 Objects and Services

1.4.1 Data Value Objects and Services
Data Value objects represent the values of control center data objects. Data Value objects consist of analog,
digital, and control points. Data Value Objects are included in ICCP Conformance Blocks 1 and 2.
Data Set Objects are ordered lists of Data Value objects maintained by the ICCP server. Access control
permission for Data Value objects is checked by the server. These objects are created by request from an ICCP
client. Data Set Objects are included in ICCP Conformance Block 1 and 2.

1.4.2 Account Objects

Account objects represent information on interchange scheduling and general accounting information.
Generally, schedule refers to an interchange schedule. The ICCP specification expands the definition of
schedule to include exchange of hourly data for control center management and information about outages and
planned outages. In ICCP context, exchanging schedules also means exchanging generation, actual
interchange, loads, and price information. The three main types of account objects supported are Transfer
Account, Device Outage and General Data Report. Account Objects are included in ICCP Conformance
Block8.

1.4.3 Data Sets/Transfer Sets

Some ICCP objects may be arranged into more complex data structures call data sets for transfer periodically,
on change of state, or in response to certain server events. Data Set Objects are designed to allow
implementation of these more complex data transfers.
Associated with each Data Set is a Transfer Set object that is a set of transmission parameters that define the
conditions under which the data set will be sent to the client. These parameters and conditions vary, depending
upon what type of data is being transferred. For example, Transfer Set Objects have transfer conditions that
include interval time-out, value change, and integrity time out. They have transmission parameters such as start
time, report interval, integrity check, and a report by exception condition that informs the server to include only
changed. A buffer time is included which allows the server to be instructed to wait for a time interval after an
event occurs before transmitting, potentially combining subsequent occurrences into a single transmission.
Transfer Reports are created by the ICCP server and sent to the ICCP client when a predefined condition
occurs involving an object associated with a Transfer Set object. The ICCP server monitors conditions for all
enabled Transfer Set objects. Transfer Reports contain the new data values for the associated Data Value
objects.
The Condition Monitoring for the Data Set Transfer Sets is included in ICCP Conformance Block 1 and 2.
Spectrum Power™ 4 ICCP uses a Data Set creation algorithm whereby the client attempts to establish its Data
Sets on the ICCP server. If this fails, the client checks which of its points are missing from the server and the re-
sultant findings are placed in the console error log. The client will then redefine its Data Sets with only valid
objects and attempt to re-establish the association with the server.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 11 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.4.4 Transfer Group

Spectrum Power™ 4 ICCP uses a container call a transfer group to which is given characteristics that control
when the data in the group will be transferred from the server. A transfer group is composed of one or more
data objects. Transfer groups are divided up into dataset objects and transfer set objects as defined by the
ICCP protocol.
Transfer groups can be divided into two categories according to the conditions that will cause the data in the
group to be transferred:
 Periodic: Transfer is controlled by a timer associated with the transfer group.
 By event: Transfer is triggered by a change in the value of one of the data objects in the transfer group. By
event is commonly called Report By Event.
A transfer group can be defined as Report by Exception. Data transfer occurs for the data objects that have
changed.

1.4.5 Device Objects/Services

The ICCP model defines device objects for use in ICCP Conformance Block 5.
Spectrum Power™ 4 ICCP supports the device object Operate operation. An Operate request includes a com-
mand for the Device object. Once the Block 5 operate command is sent, the completion is reported through
Block 2 as a change of value event for the associated devices data value object.
Spectrum Power™ 4 ICCP supports the device object Select operation when acting as a server.

1.4.6 Information Buffer Objects

Information Buffer Objects represent text data to be sent to a remote center. Information Buffer Objects have at-
tributes identifying the messages, the type of data, and attributes to be used by the peer (remote) system in
interpreting the contents of the data. The local references attribute may contain information such as the identity
of a receiving process, identity of a logger, a printer, etc.
Actual transfer of Information Message (IM) Objects is accomplished via Transfer Set Object Services.
Specifically, the Information Message transfer is initiated via the IM Transfer Set Object. Condition monitoring of
the IM Transfer Set then causes the Transfer Report of the Information Message Objects to be generated and
sent to the client.
Information Buffer Objects are included in ICCP Conformance Block 4.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 12 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.5 Data Transfer Mechanisms

Three mechanisms are used to exchange data:
 Periodic Data
 Event Data
 Exception Data

1.5.1 Periodic Data

Periodic transfer mechanisms transfer a set of object values within a strict time interval. The client may invoke
the Create Data Set operation to create a new Data Set object. For Data Set Objects, the client then chooses a
Transfer Set object to control the exchange and then invokes the Start Transfer operation. The server then
reports the requested values until the Periodic Data operation is disabled by the client with a Stop Transfer
operation (or until the server is terminated).

1.5.2 Event Data

The Event Data mechanism is very similar to Periodic Data; the difference is that the server transfers the data
values every time any of a set of event conditions occurs at the server control center. Set up is similar to
Periodic Data, except the client specifies a combination of event conditions within the transmission parameters.
Possible event conditions include:
 Change in any of the status points of the Data Set object.
 Status or analog data quality change for any point in the Data Set object.
The client may request that event conditions be buffered over a specified time interval so that a quickly
occurring sequence of event conditions will cause only a single transfer.

1.5.3 Exception Data

The Exception Data mechanism is the same as for Periodic Data except that only those data values that have
changed since the last report are transmitted. “Change” implies status change, an analog value change, or a
quality code state change. The transmission parameter for a Data Set object used with the Exception Data
mechanism may specify an integrity check time interval which specifies an interval at which the server will report
all values in the Data Set object regardless of their changed state.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 13 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.6 Protocol Implementation Conformance Statement (PICS)

This section contains tables that describe various ICCP features and whether Spectrum Power™ 4 ICCP
supports the features. The tables are directly related to those that can be found in the publication IEC 870-6-
503 TASE.2 Services and Protocol, Version 1996-08.

Also the Version 2000-08 is supported, but with the following restrictions.

Table 1 Restrictions of TASE 2 Version 2000-08

Spectrum Power 4 ICCP
TASE.2 V2000-08

Additions Client Server

Extended time stamps for data values providing millisecond resolution Y Y
Tag values in datasets N N
AllChanges reported for RBE Data Set Transfer Sets N N

Each row in a table includes a description of the feature, an indication of whether the feature is classified as a
mandatory (m) or optional (o) feature, an indication that Spectrum Power™ 4 ICCP does (Y) or does not (N)
support the feature when operating either in client or server modes. Sometimes the mandatory/optional
indication is supplemented by the addition of a number that indicates with which conformance block the feature
is associated. Furthermore, for a given feature the mandatory/optional indication may be broken into two values
separated by a comma. In such cases, the left indication applies to operation in the client mode and the second
one applies to operation in the server mode.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 14 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.6.1 Basic Protocol and Services

The tables in this section show basic protocol and services.

Table 2 TASE.2 Conformance Building Blocks

Spectrum Power 4 ICCP

Conformance Mandatory or Client Server

Building Block Optional
Basic Services m Y Y
Extended Conditions o Y Y
Blocked Transfers o N N
Information Message o Y Y
Device Control o Y Y
Programs o N N
Events o N N
Accounts o Y Y
Time Series o N N

Table 3 Association Management

Spectrum Power 4 ICCP

Association Management Mandatory or Client Server

Optional
Supported Features m1 Y Y
QOS o Y Y
Associate Operation m1 Y Y
Conclude Operation m1 Y Y
Abort Operation m1 Y Y

Table 4 Data Value

Spectrum Power 4 ICCP

Data Values Mandatory or Client Server

Optional
Data Value Model m1 Y Y
VCC-specific scope m1, o Y Y
ICC-specific scope m1, o Y N
Get Data Value Operation o, m1 Y Y1
Set Data Value Operation o, m1 Y Y1
Get Data Value Names Operation o, m1 N Y1
Get Data Value Type Operation o, m1 N Y1
1 These features are supported at the lower levels of the code, but there is no UI support for them in the Spectrum Power 4 product.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 15 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

Table 5 Data Sets

Spectrum Power 4 ICCP

Data Sets Mandatory or Client Server

Optional
Data Set Model m1 Y Y
VCC-specific scope m1, o Y Y
ICC-specific scope m1, o Y N
Create Data Set Operation o Y2 Y
Delete Data Set Operation o Y2 Y2
Get Data Set Element Values Operation o, m1 Y2 Y2
Set Data Set Element Values Operation o, m1 N Y2
Get Data Set Names Operation o, m1 Y2 Y2
Get Data Set Element Names Operation o, m1 N Y2
2 These features are used during normal product operation, but there is no UI support for them in the Spectrum
Power 4 product.

Table 6 Accounts
Spectrum Power 4 ICCP

Accounts Mandatory or Client Server

Optional
Account Model m8 Y Y
Query Operation m8 Y Y

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 16 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

Table 7 Data Set Transfer Sets

Spectrum Power 4 ICCP

DS Transfer Sets Mandatory or Client Server

Optional
Data Set Transfer Set Mode m1 Y Y
Stop Transfer Operation m1 Y Y
Start Transfer Operation m1 Y Y
Get Next DSTransfer Set Operation m1 Y Y
IntervalTimeOut o, m1 Y Y
ObjectChange o, m2 Y Y
OperatorRequest o, m1 N N1
IntegrityTimeout o, m2 Y Y
OtherExternalEvent o, m1 Y Y
EventCodeRequested o, m1 Y Y
StartTime m1 Y Y
Interval m1 Y Y
TLE o, m2 Y Y
BufferTime o, m2 Y Y
Integrity Check o, m2 Y Y
DSConditions Requested o, m1 Y Y
Block Data o, m3 Y Y
Critical o, m2 Y Y
RBE o, m2 Y Y

Table 8 Time Series Transfer Set Objects

Spectrum Power 4 ICCP

Time Series Transfer Set Objects Mandatory or Client Server

Optional
Time Series Transfer Set Model m9 N N
Get Next TSTransfer Set Operation m9 N N
EndTimeArrived o, m9 N N
ReportIntervalTimeOut o, m9 N N
OperatorRequest o, m9 N N

1 There is no UI support for this in the Spectrum Power 4 product.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 17 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

Table 9 Transfer Account Transfer Set Objects

Spectrum Power 4 ICCP

Transfer Account Transfer Set Objects Mandatory or Client Server

Optional
Transfer Account Transfer Set Model m8 Y Y
BeforeTheHour o, m8 N4 N4
DispatchUpdate o, m8 N4 N4
DuringTheHour o, m8 N4 N4
AfterTheHour o, m8 N4 N4
ActualDataUpdate o, m8 N4 N4
PastHours o, m8 N4 N4
ObjectChange o, m8 Y4 Y4
OperatorRequest o, m8 Y4 Y4
4 These features are supported in the lower layers, but not in theSpectrum Power™ 4 product's block 8 sample application.
This application accepts all block 8 objects. That is, it,ccepts objects under all of the eight conditions listed here.
It also sends all objects requested by a remote node, independent of these eight conditions

Table 10 Information Message Objects

Spectrum Power 4 ICCP

Information Message Objects Mandatory or Client Server

Optional
Information Message Transfer Set Model m4 Y Y

Table 11 Special Transfer Set Objects

Spectrum Power 4 ICCP

Special Transfer Set Objects Mandatory or Client Server

Optional
Transfer Set Name o, m1 Y Y
Next DSTransfer Set o Y Y
Next TSTransfer Set o N N
Event CodeDetected o, m1 Y Y
DSConditionsDetected o, m1 Y Y
TSConditionsDetected o, m1 N N
TAConditionsDetected o, m1 N N
Transfer Set Time Stamp o, m1 Y Y

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 18 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

Table 12 Devices
Spectrum Power 4 ICCP

Devices Mandatory or Client Server

Optional
Device model m5 Y Y
Select Operation m5 N Y
Operate Operation m5 Y Y
Get Tag o N N
Set Tag o N N
Timeout Action o, m7 Y5 Y5
Local Reset Action o Y5 Y5
Success Action o, m7 Y5 Y5
Failure Action o, m7 Y5 Y5
5 These four actions are provided but without use of block 7 facilities.

Table 13 Programs
Spectrum Power 4 ICCP

Programs Mandatory or Client Server

Optional
Program Model m6 N N
Start Operation m6 N N
Stop Operation m6 N N
Resume Operation m6 N N
Reset Operation m6 N N
Reset Operation m6 N N
Kill Operation m6 N N
Get Program Attributes Operation o, m6 N N

Table 14 Event Enrollments

Spectrum Power 4 ICCP

Event Enrollments Mandatory or Client Server

Optional
Event Enrollment Model m7 N N
Create Event Enrollment Operation m7 N N
Delete Event Enrollment Operation o, m7 N N
Get Event Enrollment Attribute Operation o, m7 N N

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 19 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

Table 15 Event Conditions

Spectrum Power 4 ICCP

Event Conditions Mandatory or Client Server

Optional
Event Condition Model m7 N N
Event Notification Action m7 N N

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 20 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.7 Object Models

The tables in this section show the object modeles.

Table 16 Supervisory Control and Data Acquisition

Spectrum Power 4 ICCP

Supervisory Control And Data Mandatory or Client Server

Acquisition Optional
IndicationPoint Object m1 Y Y
ControlPoint Object m5 Y Y
ProtectionEquipment Event Object o N N

Table 17 Transfer Accounts

Spectrum Power 4 ICCP

Transfer Accounts Mandatory or Client Server

Optional
TransferAccount Object m8 Y Y
TransmissionSeqment Object m8 N N
ProfileValue Object m8 N N
AccountRequest Object 0 Y Y

Table 18 Device Outage

Spectrum Power 4 ICCP

Device Outage Mandatory or Client-CS Server-CS

Optional
Device Outage Object O Y Y

Table 19 Information Message

Spectrum Power 4 ICCP

Information Message Mandatory or Client Server

Optional
Information Message m4 Y Y

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 21 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

Table 20 Power Plan

Spectrum Power 4 ICCP

Power Plant Mandatory or Client-CS Server-CS

Optional
AvailabilityReport Object o Y Y
RealTimeStatus Object o Y Y
ForecastSchedule Object o Y Y
Curve Object o Y Y
Power System Dynamic Object o N N

Table 21 General Data Report

Spectrum Power 4 ICCP

Information Message Mandatory or Client Server

Optional
General Data Report Object O Y Y

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 22 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.8 Architecture
The ICCP protocol makes use of the underlying MMS protocol to implement data exchange between control
centers. When depicted in the traditional OSI seven layer reference model, the relationships of Spectrum
Power™ 4, ICCP, MMS, and the remainder of the OSI stack are as shown in Figure 1. A lower layer TCP/IP
stack can also be used if the upper layer software is configured to use the RFC1006 recommendation.
RFC1006 is the request For Comment recommendation that allows upper layer OSI applications to use the
lower layer IP protocol.

The ICCP protocol can also be run in secure mode using the Transport Layer Security (TLS) protocol over a
TCP/IP connection. The ICCP application can also be configured to use Application Authentication to further
secure and authenticate the connection between the local and remote node. ICCP, in secure mode, uses
standard PKI (Public Key Infrastructure) methods for authentication and encryption of the data exchange
between local and remote ICCP nodes.

Figure 2 Protocol Relationships

Control Center Applications

(Spectrum Power™ 4)

ICCP
7
MMS
ACSE

6 Presentation

5 Session

4 Transport

3 Network

2 Data Link

1 Physical

1.9 Inter-Networking Considerations

Considerable flexibility is available in selecting a network to connect computers which will use ICCP to
exchange data. The network may be private, or public, point-to-point, packet switched, or meshed. The usual
issues of adequate protocol support, routing functionality, redundancy, security, and service reliability are
important considerations in network design.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 23 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.10 The ICCP Model

ICCP specifications describe an “informal ICCP Model” as an aid to understanding the ICCP protocol and the
context in which it is designed to operate. This model of a control center includes a number of classes of
applications, all of which need not be present. These include EMS/SCADA, DMS/Load Management, User
Interface (UI), and others. An individual control center, in its interactions with other control centers, may act as
client, server, or both. Regardless of the architecture of the system in use at a control center, when acting as a
server, the control center appears as a singular entity to clients. A server control center may interact with
multiple clients.

Data exchange between control centers is governed by the rules and restrictions defined in a Bilateral
Agreement, which typically restricts the client’s view of a control center to a subset of the data that actually
exists at that center. A Bilateral Agreement is the result of negotiations between two control centers. It defines
the information that each control center is willing to exchange, i.e. the data elements to be accessed and the
means by which they are accessed. The Bilateral Agreement is implemented within the software as a Bilateral
Table. In Spectrum Power™ 4 Bilateral Table information is entered into the database using Oracle Forms.

In the model, ICCP itself consists of one or more processes which perform the communications that allow
control centers to acquire data, change data, and control devices. The ICCP specification defines the services
and protocol necessary for performing the communication between these processes.

The ICCP model defines a number of operations and actions. An operation is associated with an ICCP client
request and an immediate ICCP server response. An example of an operation is the “CreateDataSet” operation,
which the client uses to request that the server create a data set - see also Section 1.10.4 below. An action is
associated with an ICCP server report. It is, unlike an operation, initiated by the server. An example of an action
is a “Transfer Report” which a server sends to a client when certain server side conditions are met - see also
chapter ‘Transfer Set Objects and Services’.

ICCP specifications divide ICCP functionality into “Conformance Blocks”, the contents of which are defined by
the specification. Every ICCP implementation which claims conformance to ICCP must fully support
Conformance Block 1. Conformance to each block is specified in terms of client, server or both.

The following summarizes which ICCP Conformance Blocks are currently supported by Spectrum Power™ 4:
 Basic Services (ICCP Block 1)
 Conditions (ICCP Block 2)
 Information Messages (ICCP Block 4)
 Device Control (ICCP Block 5)

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 24 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.10.1 ICCP Associations

ICCP associations correspond to ICCP connections or links at run time. The ICCP association concept is based
upon the MMS model. Associations occur between two ICCP instances. Associations are typically long lasting.
The association is established when one ICCP instance is a listener and the second instance is the initiator. The
ICCP initiator sends the association request to the listener. The association remains in place as long as the
instances continue to run and the communications connection between them remain intact. ICCP instances
normally remain running until an exception condition (i.e., off-line maintenance, error, operator shutdown, etc.)
occurs.

Three ICCP operations are defined for managing associations:

 Associate is used by an ICCP initiator to establish an association. Whether the client or server initiates the
association is a configuration issue; the initiator of an association may be a client, server, or both.
 Note: Some vendors require separate associations for each of the connections Client-Server and Server-
Client. The Spectrum Power™ 4 ICCP implementation allows for a single association to handle data
exchange in both directions. It also allows for a single association to be set up for the Client-Server
connection and a separate association to be set up for the Server-Client connection, so that the Spectrum
Power™ 4 solution is interoperable with all other vendors regarding this issue.
 Conclude is used to terminate an association and may be used by either the client or server.
 Abort is used to terminate an association when failures have occurred in the underlying communications
mechanisms. Abort may be used by either the client or server.

The Conclude and Abort services are considered to be both operations and actions since either a server or
client may invoke them.

 Note:
In order to successfully establish an association, both sites have to use/support the same ICCP Version.
Currently Spectrum Power™ 4 supports the following ICCP Versions: 5.0, 5.1, 5.1CDV, 5.2, 5.2CDV, 6.0,
1996-04, and 1996-08

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 25 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.10.2 Bilateral Tables (Agreements)

A Bilateral Agreement is a document that is negotiated by two control centers and contains the objects (i.e. data
and control objects) which each control center is willing to transmit to the other. For each object, the Bilateral
Agreement specifies its name, type, and the access control permissions for the other control center. The
Bilateral Agreement does not specify when and how often to receive each data from the remote control center.
That information is part of the client local configuration.

There must be a Bilateral Agreement for each remote ICCP system.

Access control is the responsibility of the ICCP server; the server validates all client requests for data before
honoring them. The ICCP protocol defines no mechanism for exchanging access control permissions and allows
the implementer the freedom to implement access control. The ICCP specification does recognize that there is a
need for a server to notify a client concerning access violations and that there are obvious interoperability
considerations. Therefore, the ICCP specification does standardize methods for signaling access violations.

In order for these Bilateral Agreements to be represented within control center software such as ICCP, the
names of the data objects, devices, etc. must be maintained in physical data structures within the ICCP server.
These data structures are called Bilateral Tables. Upon initiation of an association, the ICCP server consults the
Bilateral Table for the client control center to ensure that an appropriate Bilateral Agreement exists with the
client control center. Figure 2 is a conceptual diagram of a Bilateral Table structure for Data Values. Similar
tables would exist for Transfer Data, Devices, and other objects. Basically, each item in the Bilateral Table has
an identifier (acting as an address) and associated permissions (like read and write).

Table 22 Data Value Bilateral Table

Identifier 1 Identifier 1 permissions

Identifier 2 Identifier 2 permissions

Identifier 3 Identifier 3 permissions

Identifier n Identifier n permissions

So, the Bilateral Table information for a data object identifies the access methods for that object by each client.
 Note:
The access methods for an object may be different for different clients. Transfer Conditions for a data object
identify the conditions under which the object will be transmitted to a client.

In Spectrum Power™ 4, the configuration of Bilateral Table and Transfer Condition information are defined via
the Source Data Management (SDM) subsystem.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 26 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.10.3 Data Value Objects and Services

Data Value objects represent the values of control center data objects. In Spectrum Power™ 4, these Data
Value objects may be any SCADA objects including analog points, digital points, control points and text
messages.

All operations on Data Value objects are checked for access control permission by the ICCP server. Four ICCP
operations are supported for Data Value objects:
 Get Data Value
 Set Data Value
 Get Data Value Names
 Get Data Value Type

There are no ICCP actions associated with Data Value Objects.

Data Value Objects are included in ICCP conformance Block 1.

1.10.4 Data Set Objects and Services

Data Set Objects are ordered lists of Data Value objects maintained by the ICCP server. As such, access
control permission is checked by the server as for Data Value objects. According to the ICCP specification,
these objects may be created by the ICCP server with or without a request to do so by an ICCP client. Spectrum
Power™ 4 supports creation of these objects by request of a client; object creation on the server by an
administrator (i.e. predefined data set) is not supported.

Six ICCP operations are supported for Data Set Objects:

 Create Data Set
 Delete Data Set
 Get Data Set Element Values
 Set Data Set Element Values
 Get Data Set Names
Get Data Set Element Names

There are no ICCP actions associated with Data Set Objects.

Data Set Objects are included in ICCP conformance Block 1.

1.10.5 Information Message Objects and Services

Information Message Objects represent the text messages to be exchanged between control centers. The
Information Message Objects have attributes identifying the messages, the type of data, and an attribute to be
interpreted by the local system. The local references can be used to identify the receiving process.

The actual transfer of Information Message Objects is accomplished via Transfer Set Object Services (see
below). Specifically, the Information Message transfer is initiated via the IM Transfer Set Object. Condition
monitoring of the IM Transfer Set then causes the Transfer Report of the Information Message Objects to be
generated and sent to the client.

There are no ICCP operations for Information Message Objects. For Information Message Objects, ICCP uses
Transfer Set objects and services.

There are no ICCP actions for Information Message objects.

Information Message Objects are included in ICCP Conformance Block 4.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 27 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.10.6 Transfer Set Objects and Services

Some ICCP objects (e.g. Data Sets) may be arranged into more complex data structures for transfer from the
server to the client periodically, on change of state or in response to certain server events. Transfer Set Objects
are designed to allow the implementation of these more complex data transfers.

There are three types of transfer sets:

1. Data Set Transfer Sets report the data values in a Data Set Object.
2. Transfer Accounts Transfer Sets send all data in all Transfer Account objects.
3. Information Message Transfer Sets send all messages in all Information Message Objects.

Associated with each Transfer Set object is a set of transmission parameters which define under what
conditions the data will be sent to the client. These parameters and conditions may vary, depending upon what
type of data is to be transferred. For example, Data Set Objects may have transfer conditions which include
interval time-out, value change, and integrity time out. They may have transmission parameters such as start
time, report interval, integrity check, critical report indication, and a report by exception condition which informs
the server to include only changed values and whether the data requires confirmation. A timer function is
included which allows the server to be instructed to wait for a time interval after an event occurs before
transmitting, potentially combining subsequent occurrences into a single transmission.

Each Transfer Set object also has a set of reception parameters which specify how the data should be
processed when received by the client. Reception parameters are created and used only by the client, so they
do not need to be transmitted to a server. The actual implementation of reception processing is not defined in
the ICCP specification.

Transfer Set object operations are:

 Start Transfer
 Stop Transfer
 GetNextDSTransferSetValue
 GetNextTSTransferSetValue

Transfer Set object actions are:

 Condition Monitoring
 Transfer Report

Transfer Reports are created by the ICCP server and sent to the ICCP client when a predefined condition
occurs involving an object associated with a Transfer Set object. The ICCP server monitors conditions for all
enabled Transfer Set objects. Transfer Reports contain the new data values for the associated Data Value
objects.

The Condition Monitoring for the Data Set Transfer Sets is included in ICCP Conformance Blocks 1 and 2.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 28 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.10.7 Data Transfer Mechanisms

Four mechanisms are used to exchange data:
 One Shot Data
 Periodic Data
 Event Data
 Exception Data

1.10.7.1 One Shot Data

One Shot Data mechanisms transfer data immediately. The client uses a Get operation to request one or more
current values and the server responds with the requested values.

 Note:
In Spectrum Power™ 4, one-shot requests by the local operator are not supported, but one-shot requests
from remote site are answered.

1.10.7.2 Periodic Data

Periodic transfer mechanisms transfer a set of object values within a strict time interval. The client may invoke
the Create Data Set operation to create a new Data Set object (not necessary if the Data Set object has already
been pre-defined by the Server). For Data Set Objects, the client then chooses a Transfer Set object to control
the exchange and then invokes the Start Transfer operation. The server then reports the requested values until
the Periodic Data operation is disabled by the client with a Stop Transfer operation (or until the server is
terminated).

1.10.7.3 Event Data

Event Data is transferred by the server only if any of a set of event conditions occurs at the server control
center. The client specifies a combination of event conditions within the transmission parameters. Possible
event conditions include:
1. Change of the status or value of the Data Set object.
2. Change of the quality of the Data Set object.

The client may request that event conditions be buffered over a configured time interval so that a quickly
occurring sequence of event conditions will cause only a single transfer.

1.10.7.4 Exception Data

The Exception Data mechanism is the same as for Periodic Data except that only those data values which have
changed since the last report are transmitted. “Change” implies status change, an analog value changing by
more than its deadband, or a quality code state change. The transmission parameter for a Data Set object used
with the Exception Data mechanism may specify an integrity check time interval which specifies an interval at
which the server will report all values in the Data Set object regardless of their changed state.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 29 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

1.10.8 Special Transfer Objects

Special object models are available for use with Transfer Reports to convey information about the Transfer
Report generation process:
 Transfer Set Name: the name of the transfer set which caused the report.
 Transfer Set Conditions: An array of boolean flags indicating which Transfer Condition(s) triggered the
transfer.
 Transfer Set Time Stamp: Time of report generation.
 Event Code Detected: External event condition.

If these objects are included in a Data Set object, all the Data Set Transfer Reports generated for that Data Set
object will include this information. To assist the processing of the Transfer Report of a Data Set, the ICCP client
can include these special objects in the Data Set object at its creation. Spectrum Power™ 4 does not make use
of these special objects as a client. However, for a critical Data Set, the client includes “Transfer Set Name” and
“Transfer Set Time Stamp” in its Data Set. Spectrum Power™ 4 supports these special objects as a server.

1.10.9 Device Objects/Services.

The ICCP model defines two classes of devices: Direct-Control (Non-SBO) and Select-Before-Operate (SBO).
The ICCP Device object represents only SBO devices.

Device object operations are: Select and Operate. SBO Device objects have two states: ARMED and IDLE. A
device is IDLE if it has not been successfully selected. After being selected, it remains ARMED until the client
issues an Operate request, a time-out occurs, or the Select is preempted by a local action (i.e., tagging). The
Operate request includes a command for the Device object.

The client is required to select an SBO object before operating on it; the server checks if the Device object is
available and operable (invisibly to the client) and returns a success or failure indication of the client’s select
operation.

Operations for Device objects are:

 Select (SBO objects only)
 Operate

Actions for Device objects are:

 Time-out
 Local Reset
 Success
 Failure

Device Objects are included in ICCP Conformance Block 5.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 30 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

2 Functional Overview
The basic objective of the Spectrum Power™ 4 ICCP Data Link function is to provide bi-directional SCADA data
exchange between a local EMS/SCADA system and a remote computer system which also supports ICCP.

As mentioned before, the following ICCP Blocks are currently supported by the Spectrum Power™ 4 ICCP Data
Link:
 Basic Services (ICCP Block 1)
 Conditions (ICCP Block 2)
 Information Messages (ICCP Block 4)
 Device Control (ICCP Block 5)

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 31 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

3 Functional Description
3.1 Basic Services (Block 1)
This ICCP block function is used to exchange realtime power system data between Spectrum Power™ 4 and
remote systems.

3.1.1 Client Functions

Upon association initiation, ICCP, for each transfer group defined in the configuration
 maps a transfer group into one or more data sets ensuring that no one data set exceeds the maximum
message size for a given association.
 assigns data set names based on data set contents.
 aligns defined data sets that the server retained from a previous association with the ones that are actually
needed based on current client configuration. The client defines new ones if necessary and deletes those
datasets which are not required anymore.
 reads initial values by data set name for each data set within a transfer group.
 requests a Data Set Transfer Set for each data set within a transfer group.
 writes the Data Set Transfer Set to start server condition monitoring as specified by the group definition in
the client configuration.

 Note:
A data set needs to be defined only on the client side. The client automatically tells the server about the
data set definitions.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 32 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

3.1.2 Server Functions

The transfer conditions supported in Block 1 are IntervalTimeOut and IntegrityTimeOut. The IntervalTimeOut
and IntegrityTimeOut are used to trigger transfer report periodically.

The ICCP Transfer Report Action is mapped into the MMS Information Report service. The Report by Exception
(RBE) attribute specifies the format of the report. For IntervalTimeOut, the transfer report can be generated with
attribute TRUE or FALSE. If RBE is set to TRUE, only the data objects that have changed since the last report
will be included in the transfer report with their object names. Otherwise, all the data objects in the data set will
be included in the transfer report.

When RBE is set to TRUE, the IntegrityTimeOut condition is used to trigger periodic transfer reports which
include the whole data set (integrity scan).

Conformance to Block 1 services is summarized in table 1 (the no’s in the client table do not reflect non-
conformance but are not usually performed by the client) :

Table 23 Block 1 Conformance

Object Services Supported by ICCP Used by ICCP Client
Server
Association Initiate yes yes
Conclude yes yes
Abort yes yes
Data Value Get Data Value yes yes
Set Data Value yes yes
Get Data Value Names yes no
Get Data Value Type yes no
Data Set Create Data Set yes yes
Delete Data Set yes yes
Get Data Set Element Values yes yes
Set Data Set Element Values yes no
Get Data Set Names yes yes
Get Data Set Element Names yes no
Transfer Set Start Transfer yes yes
Stop Transfer yes yes
Condition Monitoring - Periodic yes yes
1
Condition Monitoring - Operator Conditions yes no
2
Transfer Report (no Blocked Data ) yes yes
Next Transfer Set Get Next Data Set Transfer Set Value yes yes

 Note:
If a status change occurs (e.g. of a circuit breaker) at a remote system and this status is sent to the local
system via ICCP, the name of the corresponding remote system may be reported in the Alarm Summary of
the local system. For this functionality some additional parameterization is required.

1
The Siemens server supports the protocol elements required, but does not supply the user interface for the server operator.
2
The data blocking is the Block 3 function. Spectrum Power™ 4 does not support Block 3.
F-CA01 Version 2.6.1.0, Restricted July 2017 Page 33 of 43
Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

3.2 Conditions (Block 2)

This block function is used to exchange the realtime exception data between Spectrum Power™ 4 and remote
systems.

The client and server functions for Block 2 are the same as those for Block 1 except for the condition monitoring
of the ObjectChange. The ObjectChange is used to trigger a transfer report whenever an object within the data
set changes.

If no buffer time is specified, the ICCP Server generates the transfer report immediately. If the buffer time is
non-zero, the ICCP Server will wait for the specified buffer time before generating the transfer report. All objects
of a Transfer Set, changing within the buffer time, will be sent in one transfer report.

The function of the RBE attribute and the IntegrityTimeOut transfer condition are the same as in Block 1 and
may be used in conjunction with the ObjectChange condition.

Conformance to Block 2 services is summarized in the following Table 2.

Table 24 Block 2 Conformance

Object Services Supported by ICCP Used by ICCP Client
Server
Transfer Set Condition Monitoring - ObjectChange yes yes
Transfer Report (no Blocked Data) yes yes

3.3 Information Messages (Block 4)

After the association initially becomes active, the ICCP protocol engine will check if there are any client
information objects defined. If there are, then it will issue a StartTransfer request on the IMTransferSet to
indicate to the remote control center that it is ready to receive information messages.

The Spectrum Power™ 4 ICCP uses the UNIX file system to store the incoming Information Messages Objects.
Each information message received by the ICCP client is saved as a UNIX file. A simple Motif window
application is provided and is used by the ICCP server to create and send information messages.

Conformance to Block 4 services is summarized in the following table.

Table 25 Block 4 Conformance

Object Services Supported by ICCP Used by ICCP Client
Server
IMTransferSet Start Transfer yes yes
Stop Transfer yes yes
Information Transfer Report yes yes
Messages Objects

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 34 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

3.4 Device Control (Block 5)

In Spectrum Power™ 4 it is possible to send and receive commands via ICCP. The ICCP client sends
commands to the ICCP server which the server control center then attempts to execute. Switching of digital
values (e.g. Circuit Breakers) and analog setpoints are supported.

Conformance Block 5 services are summarized in the following table 4.

Table 26 Block 5 Conformance

Object Services Supported by ICCP Server Used by ICCP Client
Device Select yes yes
Operate yes yes
Set Tag no no
Get Tag no no
Timeout no no
Success no no
Failure no no
Local Reset no no

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 35 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

4 ICCP Configuration
The information required to configure ICCP includes the remote/link configuration, the Bilateral Agreements, and
the local client transfer conditions configuration.

 Note:
Information on the grouping of ICCP configuration information may be obtained from appendix A.

4.1 ICCP Start-Up

At the ICCP software start-up, it reads the system data, remote data and link data to setup the executing
environment within the Spectrum Power™ 4 system. It reads the accessible data objects to setup the server
function. It reads the transfer groups and the transfer objects to setup the client function. If the link is enabled,
the ICCP software will proceed to establish associations.

During the process of association establishment, the ICCP Versions, Bilateral Table ID, and the supported ICCP
features are exchanged. The remote system must support the Conformance Block 1 as a minimum.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 36 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

5 Redundancy Characteristics
The Spectrum Power™ 4 ICCP Data Link function may run redundantly on two DL servers in hot-standby mode.
As soon as the process controlling (PC) DL server fails or is caused to run down, the standby (SB) server takes
over as the process controlling server. All links are then reestablished by the new Process Control server, and
the other server attempts to take over the Standby mode. The time it takes for a complete switchover to be
completed depends on:
 How many associations are configured
 The extent (size) of the Bilateral Table for each association - i.e., how many data/transfer set definitions
must be negotiated for each remote site on association start-up.

The ICCP application is unaware and not affected by any lower layer (network) redundancy which may be in
use for WAN communications between control centers.

The SDM interface of the Spectrum Power™ 4 ICCP Data Link function ensures database consistency between
the two DL servers - see also appendix B.5 for more information on the SDM interface.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 37 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

6 User Interface
The user interface for Data Link Management is a graphical user interface (see also Appendix C) which
provides an overview of the status of data links and enables the operator to actively control each data link. This
display is intended to be used primarily by operations personnel.

This display contains the following information:

 Overall status of data link subsystem
 Administrative status of communications to each remote system (site)
 Administrative and operational status of individual links to each remote system (site).
 Administrative and operational status of individual client transfer groups.

This display allows the following operator actions:

 Enable/disable the entire data link subsystem (i.e., all links/all remotes)
 Enable/disable communications to an individual remote system (i.e., all links)
 Enable/disable individual links to a particular remote system(i.e., selected individual links).
 Enable/disable individual client transfer groups.
 Enable/disable secure mode communications for individual links to a particular remote system.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 38 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

A ICCP Configuration
In Spectrum Power™ 4 ICCP, the information required to configure ICCP includes the remote/link configuration,
the Bilateral Agreements, and the local client transfer conditions configuration. They are grouped into the
following data entities:
 System Data
This defines the local Spectrum Power™ 4 ICCP system. This includes information such as the Local
Control Center Name, Maximum Transfer Sets, and the Conformance Blocks that are supported.
 Remote Data
This defines a Remote Control Center that will communicate with the local Spectrum Power™ 4 ICCP
system. This includes information such as the Bilateral Table Version, Remote Control Center Name,
Remote Control Center Type, and Time-out parameters. The shortest periodic interval allowed by the
remote is also included here.
 Link Data
This defines the addresses required to establish an association between the local Spectrum Power™ 4
ICCP System and a Remote ICCP System.
 Accessible Data Objects
These are the data objects specified in the Bilateral Agreement as available for the specified remote control
centers. Each data object is associated with a Spectrum Power™ 4 technological address (TA) within the
local Spectrum Power™ 4 ICCP system. Their ICCP name, type, and access permission by a Remote
Control Center are also identified. Since only accessible objects are specified here, the access permission
can be read, write, or both. To configure these objects is equivalent to configure the ICCP server function.
 Transfer Groups
These specify the transfer conditions for a group of data objects that are to be received by the local
Spectrum Power™ 4 ICCP system from a Remote Control Center. These transfer conditions specify
whether the data is reported periodically or by exception along with the required information for each case.
 Transfer Objects
These are data items that are transferred from a Remote Control Center to the local Spectrum Power™
4system. Each Transfer Object is assigned a TA. This TA identifies where the Transfer Object values will
be stored within the local Spectrum Power™ 4 system when they are received from a Remote Control
Center. Each Transfer Object is also associated with a transfer group specifying the transfer conditions
from the remote system. To configure these objects is equivalent to configure the ICCP client function.
 Server Information Message Objects
These are the information message objects specified in the Bilateral Agreement as available for the
specified remote control centers. By default, the reference number of each Information Object is also used
by the local Spectrum Power™ 4 ICCP system to identify this object.
 Client Information Message Objects
These are the information message objects that are to be received by the local Spectrum Power™ 4 ICCP
system from a Remote Control Center. By default, the reference number of each Information Object is also
used by the local Spectrum Power™ 4 ICCP system to identify this object.
 Server Device Control Objects
These are device control objects specified in the Bilateral Agreement as available for the specified remote
control centers. Each device control object is associated with a Technological Address (TA) within the local
Spectrum Power™ 4 system. The ICCP name and data type are also identified. Also, there is an Accessible
Data Object associated with the same TA.
 Client Device Control Objects
These are items that allows the local Spectrum Power™ 4 system to control device objects in remote
control centers. Each device control object is assigned a technological address (TA) within the local
Spectrum Power™ 4 system. This TA is used by the local Spectrum Power™ 4 system to control the device
object in the remote control center.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 39 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

B Interface Overview
The following diagram provides a greatly simplified overview of the interfaces associated with the software of
the Spectrum Power™ 4 function ICCP Data Link. The ICCP protocol engine exchanges data with the remote
ICCP system via the physical connection shown in figure 1 below.

Figure 3 Spectrum Power™ 4 ICCP Data Link software interface overview

Application Data
Operational Database (UNIX File System)

Common Data Link

Spectrum Power™ 4 Application Interface
Interface Library Library
(Block 1, 2 and 5) (Block 4)

Spectrum Power™ 4
ICCP Protocol Engine Remote System(s)

The ICCP protocol engine calls Common Data Link Interface Library subroutines to access the Operational
Database (ODB). The Common Data Link Interface Library subroutines make use of the standard Softbus
mechanism.

B.1 Computer Network Management

The Spectrum Power™ 4 ICCP Data Link software uses standard Spectrum Power™ 4 mechanisms for start-
up, shutdown, and recognition of server state changes. Spectrum Power™ 4 ICCP Data Link normally runs in a
Data Link server (DL).

B.2 Softbus/CNM

Interface to other components of the Spectrum Power™ 4 system is via standard Softbus/CNM (Computer
Network Management) mechanisms.

B.3 Operational Database

The Operational Database contains realtime data transmitted by the remote systems to the Spectrum Power™
4 EMS. The SCADA data transferred via ICCP Block 1, 2 and 5 are stored in the Operational Database.

Interface to the Spectrum Power™ 4 operational data is provided by the Spectrum Power™ 4 common data link
interface library. This library is used by a number of Spectrum Power™ 4 data link products to exchange data
with the Spectrum Power™ 4 operational Database. This library provides the following functionality:
Defines (shared memory resident) Spectrum Power™ 4 database relations which permit operational data
access
Provides program interfaces which allow data link software to read and write information to the Operational
Database and receive notification of changes
Provides program interfaces for receiving notification of supervisory control actions in the local
Spectrum Power™ 4 system
Provides program interfaces for notification of changes in Spectrum Power™ 4 LAN and server status.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 40 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

B.4 Application Database

Application data refer to data which are different from the operational database. The objects in ICCP Block 4 are
stored in the Application database.

A common application interface is used to support application data base data exchange via ICCP by
applications resident at the local EMS/SCADA system. This interface allows an application to request or send
data.

B.5 SDM Interface

The SDM interface function is the mechanism to initially define and subsequently maintain the Bilateral Tables.
The SDM Interface is used to import/export the Bilateral Agreement, interactively edit the data, perform
validations and generate reports.

In addition to the Bilateral Agreement, other configurations required for ICCP, eg. the link configuration and the
client transfer condition configuration, are also maintained via SDM.

The SDM interface may also be used for on-line reconfiguration of the Spectrum Power™ 4 ICCP Data Link
function. The Spectrum Power™ 4 ICCP Data Link function restarts automatically when its configuration is
changed using SDM.

 Note:
For a detailed description of the SDM Interface please refer to User Guide U-SD06.

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 41 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

C Sample Displays
C.1 Common Data Link Status and Control Display

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 42 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved
 Spectrum Power™ 4
Functional Specification
ERS-SCADA-2015-KFW ICCP Data Link

C.2 Set Data Status and Control Display

F-CA01 Version 2.6.1.0, Restricted July 2017 Page 43 of 43

Copyright © Siemens AG 2017 - 2027. All rights reserved