Escolar Documentos
Profissional Documentos
Cultura Documentos
Training
ICCP Basic/Modelling
Restricted © Siemens AG 2013 All rights reserved. Answers for infrastructure and cities.
Page 1
Spectrum PowerTM 7
Content
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).
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.
Exchanged data may include realtime and historical power system data, such as
measured values, interchange scheduling data, energy accounting data, and
operator messages.
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.
• 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.
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
6 Presentation Presentation
5 Session Session
Application Interface
Request
Client Server
Response
Process Association Process
Request
Server Client
Response
Bilateral Agreement
For access For access
from B to A from A to B
Bilateral Bilateral
Table Table
Association 1
Client Client
Server Server
Control Center n
Association n
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
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
SDM RTC UI
router router
CA1 PC
CA2
F
PC SB
router router
CC_remote
• Configuration Overview
• ICCP Troubleshooting
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
Remote Name
Intiator or Listener
Link Name
Local AR Name
Remote AR Name
Service Quality
Group Name
Transfer Interval
Service Quality
Transfer Type
ICCP Scope
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.
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
<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
<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>
UCS server
clesm
CLESNIM
(image)
Snap_l siscostackcfg.cfg
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. Answers for infrastructure and cities.
Page 46