Вы находитесь на странице: 1из 46

Spectrum PowerTM 7

Training
ICCP Basic/Modelling

Restricted © Siemens AG 2013 All rights reserved. Answers for infrastructure and cities.
Page 1
Spectrum PowerTM 7
Content

 Goals of this module


 Introduction to ICCP
 IEC Standards and ICCP
 ICCP model
 ICCP in SINAUT Spectrum

Restricted © Siemens AG 2013 All rights reserved.


Page 2
Spectrum PowerTM 7
Goals

The topics covered in the overview are intended to :

 Introduce ICCP - what is ICCP, when can I use it ?


 Give an example of ICCP in Spectrum
 Summarize the evolution of the ICCP standard
 Show how ICCP fits into the ISO/OSI 7 layer model
 Introduce the ICCP model
 Introduce ICCP telegram types
 Explain a Bilateral Agreement
 Introduce MMSEASE

Restricted © Siemens AG 2013 All rights reserved.


Page 3
Introduction
Overview

Spectrum 7
SCADA (Site A)
apps. IMM

CA
(ICCP)

CA
WAN
or permanent lines (ICCP)

SCADA
apps.

ICCP
IMM
Non-Siemens
system
(Site C)
Spectrum 7 (Site B)
Restricted © Siemens AG 2013 All rights reserved.
Page 4
Introduction
Overview

In the past, de-facto standard protocols for communication between control centers
have been established, e.g., ELCOM90 in Europe and WSCC in North America.

Recently, the ICCP protocol defined within the EPRI project UCA (Utility
Communication Architecture) has gained so much significance that it is defined as
an international standard (IEC870-6 TASE2) and is now existing in parallel to
ELCOM90 (IEC870-6 TASE1).

Restricted © Siemens AG 2013 All rights reserved.


Page 5
Introduction
Overview

The inter control center communications protocol (ICCP) is designed to allow data
exchange over wide area networks (WANs) between a utility control center and
other control centers.

Examples of other control centers include neighbouring utilities, power pools,


regional control centers, and non-utility generators.

Exchanged data may include realtime and historical power system data, such as
measured values, interchange scheduling data, energy accounting data, and
operator messages.

Restricted © Siemens AG 2013 All rights reserved.


Page 6
Introduction
Overview

Data exchange occurs between a SCADA/EMS server of one control center and the
server of another control center.

The ICCP server is responsible for access control when a client requests data. One
ICCP server may interact with several clients.

Access control of data elements between control centers is implemented through


so-called ‘Bilateral Agreements’. A bilateral agreement is a document negotiated by
two control centers which includes the elements (i.e., data and control elements)
that each is willing to transmit to the other.

Restricted © Siemens AG 2013 All rights reserved.


Page 7
Introduction
What is ICCP ?

• ICCP stands for Inter-Control Center Communication Protocol

• TASE.2 means Telecontrol Application Service Element

• The data exchanged may include real-time and historical power system data
such as measured values, status indications, alarms, counter values, switching
commands, setpoints, operator messages and so forth.

• The ICCP standards are companion standards of the Manufacturing Message


Standards (MMS) and ICCP is a user of MMS services.

• The intention was to provide a standard, internationally recognized protocol,


which built upon the many existing data exchange protocols in order to simplify
the problems of data exchange between control centers.

Restricted © Siemens AG 2013 All rights reserved.


Page 8
Introduction
Scope

TASE.2 (ICCP) is defined for communications:

between control centers of


energy-, gas- and water systems

between distribution and generation control centers

between control centers and substations

and in principle open for other application areas

Restricted © Siemens AG 2013 All rights reserved.


Page 9
Introduction
Communication Services

TASE.2 (ICCP) covers communication services for:


installation of connections including authentication
transmission of real-time and historical data
exchange of scheduling information
transmission of ASCII-strings or binary code
definition / transmission of data groups
• selection of data objects (out of Bilateral Table)
• definition of transmission conditions

Restricted © Siemens AG 2013 All rights reserved.


Page 10
Introduction
Object Model

TASE.2 (ICCP) object model:


open object model based on MMS
(Manufacturing Message Specification)
• clear method for data structuring
• self-description of data (Browser)
• new data objects definable (object model)
often used data types are already defined
application oriented names used as identifiers

Restricted © Siemens AG 2013 All rights reserved.


Page 11
IEC-Standards and ICCP
Overview of IEC-Standards for Telecontrol protocols
Telecontrol protocols

IEC 870-5-... IEC 870-6-...

IEC 870-5-101 TASE.1


Companion standard for Inter-Control Center
basic telecontrol tasks Communications
(derived from ELCOM90)

IEC 870-5-102 TASE.2


Companion standard for Inter-Control Center
transmission of Communications
integrated totals (based on ICCP)

IEC 870-5-103
Companion standard for
protection communication

IEC 870-5-104
Network access for
IEC 870-5-101 using
standard transport profiles
Restricted © Siemens AG 2013 All rights reserved.
Page 12
IEC-Standards and ICCP
Cooperation in standardization

IEC TC 57 EPRI
WG 07 UCA WSCC IDEC

ICCP
Inter-Control Center Communications Protocol
IEC 870-5-101 ELCOM

TASE.2
Telecontrol Application Service Element 2

Restricted © Siemens AG 2013 All rights reserved.


Page 13
IEC-Standards and ICCP
Protocol architectures in IEC 870

User process IEC 870- 5 IEC 870-6

7 Application Application Application TASE.2

6 Presentation Presentation

5 Session Session

4 Transport Transport ISO/OSI-


Standards
3 Network Network

2 Link Link Link

1 Physical Physical Physical

Restricted © Siemens AG 2013 All rights reserved.


Page 14
IEC-Standards and ICCP
Protocol architecture IEC 870-6

Application Interface

IEC 870-6 TASE.2


7 ISO 9506 MMS
ISO 8650/2 ACSE, ROSE, RTSE
6 ISO 8823 / 8824 / 8825 Presentation
5 ISO 8072 Session
4 ISO 8072 Transport (Class 4, 2, 0) or TCP
IS - IS ES - IS
3 ISO 8473 Network or IP ISO 8208
2 Token Ring
Ethernet Fiber X.25
LAN
LAN LAN WAN
1
Restricted © Siemens AG 2013 All rights reserved.
Page 15
The ICCP Model
Client - Server - Model

Control Center A Control Center B

Request
Client Server
Response
Process Association Process
Request
Server Client
Response

Each side may be client and/or server


The client sends requests to the server
The server proofs authorization of client requests
and responses if permitted

Restricted © Siemens AG 2013 All rights reserved.


Page 16
The ICCP Model
Bilateral Agreement

Bilateral Agreement
For access For access
from B to A from A to B

Control Center A Control Center B


For access from B: For access from A:
Bilateral Table: Bilateral Table:
Per Object: Per Object:
• Name ICCP Name • Name
• Typ • Typ
• Access rights • Access rights

Restricted © Siemens AG 2013 All rights reserved.


Page 17
The ICCP Model
Associations

Control Center A Control Center B

Bilateral Bilateral
Table Table
Association 1
Client Client

Server Server

Control Center n
Association n

Restricted © Siemens AG 2013 All rights reserved.


Page 18
The ICCP Model
Server - Services and Objects

TASE.2 - Server
Services Objects Real World:
Request • Association
Operations • Data Value • Indications
Response
• Data Set • Analogs
• Transfer Set • Counter values
• Account • Commands
Report
Actions • Device • Protection data
• Program • Schedules
• Event • ASCII-strings
Events a.s.o.
Mapping

Restricted © Siemens AG 2013 All rights reserved.


Page 19
The ICCP Model
Conformance Building Blocks (CCB)

Block 1: Basic Services


• Definition of data groups
• Definition of transmission conditions
• Requested transmission of data objects or data groups
• Periodic transmission of data objects or data groups

Block 2: Extended Data Set Condition Monitoring


• Event driven transmission in case of changes
An additional report concerning cause of transmission is possible

Restricted © Siemens AG 2013 All rights reserved.


Page 20
The ICCP Model
Conformance Building Blocks (CCB)

Block 3: Blocked Transfer


• Transmission of blocked, unstructured data
Block 4: Information Messages
• Transmission of messages (ASCII-Strings)
or binary code
Block 5: Device Control
• Transmission of commands or set-points
Block 6: Programs
• Program control (start, stop,reset)

Restricted © Siemens AG 2013 All rights reserved.


Page 21
The ICCP Model
Conformance Building Blocks (CCB)

Block 7: Events
• Special event definition and transmission
Block 8: Accounts
• Exchange of schedules for energy transfer
Block 9: Time Series
• Transmission of historical data

Restricted © Siemens AG 2013 All rights reserved.


Page 22
ICCP in Spectrum
Conformance Blocks available

Block Description Spectrum Remark


Release 7
1 Basic Services yes
2 Extended Data Set yes
Condition Monitoring
3 Blocked Transfer no
4 Information Messages yes
5 Device Control yes
6 Programs no
7 Events no
8 Accounts yes only archive data,
no schedules
9 Time Series no

Restricted © Siemens AG 2013 All rights reserved.


Page 23
ICCP In Spectrum
Redundancy

SDM RTC UI

router router

CA1 PC
CA2
F
PC SB

router router

CC_remote

Restricted © Siemens AG 2013 All rights reserved.


Page 24
ICCP In Spectrum
Extra Hardware/Software Requirements

Router(s) (typically from Cisco) required for WAN connection


MMSEASE license(s) needed (from Sisco)
CA servers for ICCP (2 for SB redundancy)
ICCP can be bundled with RTC which saves cost of CA servers

Restricted © Siemens AG 2013 All rights reserved.


Page 25
ICCP In Spectrum
Configuration steps

The configuration of ICCP in Spectrum requires the following steps :


The installation and configuration of MMSEASE (from Sisco) - an ASCII file is
edited (osill2.cfg)
Import of an XML file with the basic (standard) ICCP configuration.
The Transfer of this data to the Spectrum ODB (Copy 1).
The Activation of the data in the Spectrum ODB (Copy 0) so that the ICCP
processes receive the new data.
The configuration of certain ASCII files for Block 4 and / or Block 8.

Restricted © Siemens AG 2013 All rights reserved.


Page 26
ICCP Modelling and Configuration

• Configuration Overview

• ICCP Modelling in IMM

• Sisco – Stack – Configuration

• ICCP Troubleshooting

Restricted © Siemens AG 2013 All rights reserved.


Page 27
ICCP Configuration Steps

TASE.2 (ICCP) object model: open object model based on MMS (Manufacturing
Message Specification)

Configuration Steps:
- Installation of MMSEASE (Sisco)
- ICCP Data Modelling in IMM
- Parameterization of MMSEASE: /usr/sisco/network/siscostackcfg.xml

Restricted © Siemens AG 2013 All rights reserved.


Page 28
Installation of MMSEASE

(Will be done by Administrator)

as root on ICCP Server (Blockfunction UCS):


cd /home/s/sadm/inst/X86lx/bs_scripts
./IU71mmsease install
-> follow instructions
-> select secure or non-secure
-> check output if Sisco Library needs to be copied
-> Sisco Software can be found in directory /usr/sisco
-> Sisco Configuration File and Binaries can be found in /usr/sisco/network

Restricted © Siemens AG 2013 All rights reserved.


Page 29
-> Activate Sisco License (/usr/sisco/license)
ICCP Instance Tree in IMM

Restricted © Siemens AG 2013 All rights reserved.


Page 30
IMM: IcRemoteCenter

Remote Name

Intiator or Listener

Iccp Blocks(1 and 2 are


always true)

Bilateral Table version


Iccp Version

Iccp Domain Name

Restricted © Siemens AG 2013 All rights reserved.


Page 31
IMM: IcLink

Link Name

Local AR Name
Remote AR Name
Service Quality

Restricted © Siemens AG 2013 All rights reserved.


Page 32
IMM: IcServerBlock1And2Container
IcServerBlock1And2Object

ICCP Object Name ICCP DataType ICCP Scope

Restricted © Siemens AG 2013 All rights reserved.


Page 33
IMM: IcClientBlock1And2Container

Group Name

Transfer Interval

Service Quality

Transfer Type

Restricted © Siemens AG 2013 All rights reserved.


Page 34
IMM: IcClientBlock1And2Object

ICCP Scope

ICCP Object Name ICCP DataType

Restricted © Siemens AG 2013 All rights reserved.


Page 35
IMM: ICCP Block 5

Restricted © Siemens AG 2013 All rights reserved.


Page 36
IMM: ICCP Block 4

Restricted © Siemens AG 2013 All rights reserved.


Page 37
ICCP ODB Relations

ICLOCAL -> ICCP System (local)


ICRMOTE -> Remote
ICLINK -> Link
ICBLT -> IcServerBlock1And2Object (Access)
ICGROUP -> IcClientBlock1And2Container (Transfer Group)
ICXFRC -> IcClientBlock1And2Object (Transfer Object)
ICDEV -> ICCP Block 5 (Device Object, both directions)
ICCINFO / ICSINFO -> ICCP Block 4 (Messages, Transfer and Access)

CLESNIM -> ICCP Network Image (dynamic on ICCP Server)


CLESOBJ -> Dynamic collection of client-datapoints on RTC

Restricted © Siemens AG 2013 All rights reserved.


Page 38
Sisco: Overview

On the local system, the relation ICLINK contains one Local_AR and up to four
Remote_AR names.
These act like pointers to the file /usr/sisco/network/
In the siscostackcfg.xml file, the local software port for the ICCP association is
defined by so-called selectors, (PSEL, SSEL and TSEL).
The Psel, Ssel and Tsel numbers of the Local_AR must be the same as those of
the Remote_AR on the remote system.

Likewise, the Psel, Ssel and Tsel numbers of the Remote_ARs on the local system
must be those of the Local_AR of the remote system.
The IP addresses of the Remote system are also parameterized under the “List of
AR Names” fields of the siscostackcfg.xml.

Restricted © Siemens AG 2013 All rights reserved.


Page 39
Sisco: ICLINK / siscostackcfg.xml

Record x
ICLINK
Recor
d0

CC 0
Remote Key
Link Key
link name
channel
Local AR
CC 1
Pri AR /usr/siscostackcfg.xml
Alt AR

Local AR - points to IP local info in


osill2.cfg
Pri AR - points to IP addr in osill2.cfg
Recor
dn
Alt AR - points to IP addr in osill2.cfg

Restricted © Siemens AG 2013 All rights reserved.


Page 40
Sisco: App_Network

<App_Network>
<App_Name>LINK_1 </App_Name>
<LeanT_Profile>Application</LeanT_Profile>
<Security_Profile>No Security</Security_Profile>
<AR_Matching_Profile>ARMatching</AR_Matching_Profile>
<App_AR_Name Role="Local">LOC_AR_ANLAGE1</App_AR_Name>
<App_AR_Name Role="Remote">REM_AR_ANLAGE2_1</App_AR_Name>
<App_AR_Name Role="Remote">REM_AR_ANLAGE2_2</App_AR_Name>
<Max_Mms_Pdu_Length>32000</Max_Mms_Pdu_Length>
<Max_Calling_Connections>0</Max_Calling_Connections>
<Max_Called_Connections>2</Max_Called_Connections>
</App_Network>

Link Name and Local and Remote AR Names need to match between
Sisco Configuration and IMM (ODB relation ICLINK).
locally on ICCP Server:
/usr/sisco/network/siscostackcfg.xml

Restricted © Siemens AG 2013 All rights reserved.


Page 41
Sisco: AR_Names

<AR_Name_List>
<AR_Name>
<Name>LOC_AR_ANLAGE1</Name>
<Description>for compatability with older DIBS</Description>
<AP_Title>1 3 9999 30</AP_Title>
<AE_Qualifier>30</AE_Qualifier>
<PSEL>00 00 00 01</PSEL>
<SSEL>00 03</SSEL>
<TSEL>00 03</TSEL>
<IP_Address>172.21.11.217</IP_Address>
<Authentication_Mode>AE Title</Authentication_Mode>
</AR_Name>
<AR_Name>
<Name>REM_AR_ANLAGE2_1</Name>
<Description>for compatability with older DIBS</Description>
<AP_Title>1 3 9999 27</AP_Title>
<AE_Qualifier>27</AE_Qualifier>
<PSEL>00 00 00 01</PSEL>
<SSEL>00 03</SSEL>
<TSEL>00 03</TSEL>
<IP_Address>149.3.252.106</IP_Address>
<Authentication_Mode>AE Title</Authentication_Mode>
</AR_Name>
<AR_Name>
<Name>REM_AR_ANLAGE2_2</Name>
<Description>for compatability with older DIBS</Description>
<AP_Title>1 3 9999 27</AP_Title>
<AE_Qualifier>27</AE_Qualifier>
<PSEL>00 00 00 01</PSEL>
<SSEL>00 03</SSEL>
<TSEL>00 03</TSEL>
<IP_Address>1.1.1.1</IP_Address>
<Authentication_Mode>AE Title</Authentication_Mode>
</AR_Name>
</AR_Name_List>

Restricted © Siemens AG 2013 All rights reserved.


Page 42
ICCP Processes
Data flow through ICCP Server

RTC server vasd

UCS server
clesm
CLESNIM
(image)

ICRMOTE icpe icpe …. parent process


ICLINK
etc. icr0l0,icr1l0…icrnl0 icrnl0 … child for Remote n, Link
0

Snap_l siscostackcfg.cfg

Restricted © Siemens AG 2013 All rights reserved.


Page 43
ICCP Troubleshooting:
icpe trace

Set the DEBUG level of the icpe process to 7 :


eg. sym obj icrnnn sdb 7 (relevant client process or icpe for parent process)

Move to iccp log directory :


cd /home/spsy/ICCP/icpeLogFile

Use tail to see the messages :


eg. tail -f messages

Restricted © Siemens AG 2013 All rights reserved.


Page 44
ICCP Troubleshooting:
icpe trace

You can also use the relation CLESNIM on the UCS server to check points in the
ICCP image.
Eg.
>bq
>bq#rel clesnim
>bq#.techid.noel = <noel>
>bq#.techid.info = <info>
>bq#.techid.setnr = <setnr>
>bq#read key
useful fields include :
-controllable (true/false)
-flags (Qb0) eg. 9 is actual, 11 is Not Renewed, 7 is Invalid, 5 is Blocked
-vLong - value for an indication (eg 1 is open, 2 is closed)
-vFloat - value for a measured value

Restricted © Siemens AG 2013 All rights reserved.


Page 45
Thank you for your attention!

Restricted © Siemens AG 2013 All rights reserved. Answers for infrastructure and cities.
Page 46