UserGd Axs4iccp 142095 PDF

AX-S4 ICCP
USER GUIDE
AXS4-ICCP-142-095
Revision 9
Systems Integration Specialists Company, Inc.

6605 19½ Mile Road, Sterling Heights, MI 48314-9921, U.S.A.
Tel: +1-586-254-0020, Fax: +1-586-254-0053
E-Mail: support@sisconet.com, URL: www.sisconet.com
© SISCO, Inc. 1999-2015

All Rights Reserved by:
Printed in U.S.A.
01/2015
AX-S4 ICCP for Windows
User’s Guide
COPYRIGHT NOTICE
© Copyright 1999-2015 Systems Integration Specialists Company Inc. All Rights Reserved.
This document is provided under license to authorized licensees only. No part of this document may be copied or
distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer
language, in any form or by any means, electronic, mechanical, magnetic, manual, or otherwise, disclosed to third
parties, except as allowed in the license agreement, without the express written consent of Systems Integration
Specialists Company Incorporated, 6605 19½ Mile Road, Sterling Heights, MI, 48314, U.S.A.
DISCLAIMER
Systems Integration Specialists Company, Inc. makes no representation or warranties with respect to the contents
of this manual and specifically disclaims any implied warranties of merchantability of fitness for any particular
purpose. Further, Systems Integration Specialists Company, Inc. reserves the right to revise this publication and to
make changes in it from time to time without obligation of Systems Integration Specialists Company, Inc. to notify
any person or organization of such revision or changes.
Revision 9
01/30/2015
TABLE OF CONTENTS
CHAPTER 1: INTRODUCTION .................................................................................................................................. 1
CHAPTER DESCRIPTIONS...................................................................................................................................................1
TERMINOLOGY ...............................................................................................................................................................2
THE AX-S4 ICCP MODEL ................................................................................................................................................4
ICONS ...........................................................................................................................................................................6
SUPPORTED FUNCTIONALITY .............................................................................................................................................7
OPC Interface .........................................................................................................................................................7
SYSTEM REQUIREMENTS ..................................................................................................................................................7
ASSUMPTIONS ...............................................................................................................................................................8
APPLICATION SUPPORT ....................................................................................................................................................9
CHAPTER 2: INSTALLATION .................................................................................................................................. 10
SETUP TASK LIST...........................................................................................................................................................10
INSTALLATION ..............................................................................................................................................................10
Manually Migrating the Database to the New XML Format ...............................................................................13
DIRECTORY STRUCTURE .................................................................................................................................................14
MULTIPLE ETHERNET ADAPTERS AND TCP/IP ....................................................................................................................15
TCP/IP (USING RFC1006) SUPPORT ...............................................................................................................................15
SISCO STACK OVERVIEW ...............................................................................................................................................15
SISCO STACK STARTUP CONSIDERATIONS .........................................................................................................................16
AX-S4 ICCP Startup Considerations ......................................................................................................................17
Running AX-S4 ICCP as a manual process ............................................................................................................18
USING THE OPC UA WRAPPER .......................................................................................................................................19
ACTIVATING THE AX-S4 ICCP PRODUCT LICENSE (NEW CUSTOMERS) ....................................................................................21
Update License or New license with no Internet Access (Activate AX-S4 ICCP (C2V))..........................................21
HASP Admin Control Center (Troubleshooting) ...................................................................................................22
License Changes ...................................................................................................................................................24
STARTING AX-S4 ICCP AS A NORMAL PROCESS .................................................................................................................24
RUNNING AX-S4 ICCP ..................................................................................................................................................25
CHAPTER 3: GETTING STARTED ............................................................................................................................ 27
HELP DESK ..................................................................................................................................................................27
How to Access the Help Desk ...............................................................................................................................27
Recent KnowledgeBase Articles ...........................................................................................................................29
How to Enter a Ticket...........................................................................................................................................30
CONFIGURATION ..........................................................................................................................................................33
USING AX-S4 ICCP AS AN ICCP SERVER...........................................................................................................................33
ICCP ADDRESSING ISSUES ..............................................................................................................................................34
REDUNDANCY ..............................................................................................................................................................34
CHAPTER 4: ICCP FUNDAMENTALS....................................................................................................................... 35
MMS AND ICCP ..........................................................................................................................................................35
VMD and Domains ...............................................................................................................................................35
Client and Server Relationship .............................................................................................................................35
Service Mapping – MMS to ICCP..........................................................................................................................36
SUPPORTED ICCP BLOCKS ..............................................................................................................................................36
Block 1 – Basic Services ........................................................................................................................................36
Block 2 – Extended Condition Monitoring............................................................................................................36
Block 3 – Blocked Transfers .................................................................................................................................36
Block 4 – Information Message ...........................................................................................................................36
Block 5 – Device Control.......................................................................................................................................37
ICCP NAMES ...............................................................................................................................................................37
ICCP DATA TYPES ........................................................................................................................................................37
Bitstring Definitions for ICCP Data Types .............................................................................................................38
DATASETS ...................................................................................................................................................................39
DATASETTRANSFERSETS ................................................................................................................................................39
DSConditions ........................................................................................................................................................39
MESSAGE HANDLING – BLOCK 4 .....................................................................................................................................41
DEVICE HANDLING – BLOCK 5 .........................................................................................................................................41
CHAPTER 5: ICCP CONFIGURATION UTILITY ......................................................................................................... 44
ICCP CONFIGURATION UTILITY........................................................................................................................................44
File .......................................................................................................................................................................45
Edit .......................................................................................................................................................................46
View .....................................................................................................................................................................47
Tools.....................................................................................................................................................................48
GENERAL PARAMETERS FORM .........................................................................................................................................50
Configuration .......................................................................................................................................................50
Spare Capacity .....................................................................................................................................................51
ICCP Services ........................................................................................................................................................51
IDENTIFICATION PARAMETERS .........................................................................................................................................52
AE Title Matching.................................................................................................................................................52
Local/Remote – Address Element Matching ........................................................................................................53
OPC PARAMETERS .......................................................................................................................................................53
Time Stamp ..........................................................................................................................................................54
User Quality .........................................................................................................................................................54
ICCP to OPC Quality Mapping ..............................................................................................................................54
DSConditionsDetected .........................................................................................................................................55
State and Quality .................................................................................................................................................55
REDUNDANCY PARAMETERS ...........................................................................................................................................55
General ................................................................................................................................................................56
Backup OPC ..........................................................................................................................................................56
Automatic Configuration Synchronization ...........................................................................................................56
Data Synchronization ...........................................................................................................................................56
Association Connect Timeout...............................................................................................................................57
RPL Connection ....................................................................................................................................................57
RPL Timers ...........................................................................................................................................................58
ADDRESSING FORM .......................................................................................................................................................58
LOCAL CONTROL CENTERS FORM .....................................................................................................................................59
Add Local Control Center .....................................................................................................................................60
Right Click Local Control Centers Options ............................................................................................................61
DATABASE OBJECT COUNTS FOR LOCAL CONTROL CENTER....................................................................................................64
Right Click Local Control Center (Name) Options ...............................................................................................64
Local Control Center Data Values ........................................................................................................................65
Local Control Center Devices................................................................................................................................67
Local Control Center Messages ............................................................................................................................69
REMOTE CONTROL CENTERS ...........................................................................................................................................70
Right Click Remote Control Centers Option .........................................................................................................70
Add a Remote Control Center ..............................................................................................................................71
Database Object Counts for Remote Control Center ...........................................................................................72
Right Click Remote Control Center .......................................................................................................................72
Remote Control Center Associations....................................................................................................................73
Right Click Associations Options .........................................................................................................................77
Remote Control Center Bilateral Tables ...............................................................................................................78
Right Click Bilateral Tables Options .....................................................................................................................79
Database Object Counts for Bilateral Table .........................................................................................................80
Database Object Counts for Server (To Remote) .................................................................................................80
Server Data Values...............................................................................................................................................81
Right Click Data Values Option ............................................................................................................................82
Server Devices ......................................................................................................................................................83
Right Click Devices Option ...................................................................................................................................84
Server Messages ..................................................................................................................................................85
Right Click Messages Option ................................................................................................................................86
Database Object Counts for Client (From Remote) ..............................................................................................87
Right Click Client (From Remote) .........................................................................................................................87
Client Data Values................................................................................................................................................91
Add a Data Value .................................................................................................................................................91
Right Click Data Values (New, Missing, Mistyped, Excluded) ..............................................................................93
Client Devices .......................................................................................................................................................93
Add a Device ........................................................................................................................................................95
Right Click Client Devices Option .........................................................................................................................95
Client Messages ...................................................................................................................................................95
Add a Message ....................................................................................................................................................97
Right Click Client Messages Option......................................................................................................................97
Client Data Sets....................................................................................................................................................98
Add Client Data Set ............................................................................................................................................100
How to Add a Block 5 object to a DataSet .........................................................................................................100
Right Click Client DataSets Option .....................................................................................................................101
Client Data Set Transfer Sets .............................................................................................................................101
Right Click Client DataSet Transfer Sets Option .................................................................................................103
Data Value Discovery .........................................................................................................................................104
Auto DSTS Parameters .......................................................................................................................................107
CHAPTER 6: BUILDING APPLICATIONS USING OPC ............................................................................................. 108
OPC GENERAL CONCEPTS ............................................................................................................................................108
OPC SERVERS ............................................................................................................................................................108
OPC ITEM STRINGS.....................................................................................................................................................108
OPC GROUP UPDATE RATE ..........................................................................................................................................108
GENERAL OPC ITEM STRINGS .......................................................................................................................................109
LOCAL AND REMOTE ITEM STRINGS ................................................................................................................................109
QUALITY FLAGS ..........................................................................................................................................................110
ICCP to OPC Quality Mapping ............................................................................................................................111
ICCP State Polarity .............................................................................................................................................112
OPC TIMESTAMP FORMAT ...........................................................................................................................................113
AX-S4 ICCP REDUNDANCY ..........................................................................................................................................113
LOCAL SERVER DATA VALUES ........................................................................................................................................116
LOCAL SERVER MESSAGES ............................................................................................................................................117
LOCAL SERVER DEVICES ...............................................................................................................................................117
LOCAL SERVER STATUS INFORMATION ............................................................................................................................117
REMOTE SERVER GENERAL INFORMATION .......................................................................................................................118
REMOTE SERVER LINK INFORMATION..............................................................................................................................118
REMOTE SERVER DATA VALUES .....................................................................................................................................119
REMOTE SERVER TRANSFER SETS ...................................................................................................................................119
REMOTE SERVER INFORMATION MESSAGES .....................................................................................................................120
REMOTE SERVER DEVICES ............................................................................................................................................120
ADD A REMOTE CONTROL CENTER CONFIGURATION..........................................................................................................120
RELOADING A REMOTE CONTROL CENTER BILATERAL TABLE ...............................................................................................120
INFORMATION MESSAGE HANDLING ..............................................................................................................................120
DEVICE HANDLING ......................................................................................................................................................122
SELECTING A REMOTE DEVICE .......................................................................................................................................123
OPERATING A REMOTE DEVICE ......................................................................................................................................123
GETTING TAG INFORMATION FROM A REMOTE DEVICE ......................................................................................................123
SETTING TAG INFORMATION OF A REMOTE DEVICE ...........................................................................................................123
AX-S4 ICCP STATISTICS ..............................................................................................................................................123
LOCAL STATUS INFORMATION .......................................................................................................................................124
LOG MASKS ...............................................................................................................................................................124
ERROR HANDLING.......................................................................................................................................................125
TEST APPLICATIONS.....................................................................................................................................................126
CHAPTER 7: REMOTE CONTROL CENTER IDENTIFICATION AND ASSOCIATION MATCHING................................. 127
AX-S4 ICCP MATCHING ALGORITHM ............................................................................................................................127
MATCHING CRITERIA ...................................................................................................................................................128
CHAPTER 8: AX-S4 ICCP REDUNDANCY SYSTEM ................................................................................................. 129
REDUNDANCY SYSTEM FEATURES...................................................................................................................................129
REDUNDANCY DEFINITIONS ..........................................................................................................................................129
Primary Node .....................................................................................................................................................129
Secondary Node .................................................................................................................................................129
Active Mode .......................................................................................................................................................130
Standby Mode....................................................................................................................................................130
Redundancy Port Link (RPL) ...............................................................................................................................130
ICCP Configuration Utility (IccpCfg) ...................................................................................................................130
REDUNDANT SYSTEM BLOCK DIAGRAM ...........................................................................................................................131
AX-S4 ICCP OPC ITEM AVAILABILITY ............................................................................................................................131
Redundancy Items .............................................................................................................................................131
Active Node ........................................................................................................................................................131
Standby Node.....................................................................................................................................................132
LOCAL ICCP DATA VALUE QUALITY DURING SWITCHOVER .................................................................................................132
REMOTE OPC ITEM VALUE QUALITY DURING SWITCHOVER ................................................................................................132
DEPLOYMENT OPTIONS................................................................................................................................................132
Deployment Option 1: Integrate With Redundancy Broker ...............................................................................133
Deployment Option 2: Redundant OPC Client Applications ...............................................................................134
REDUNDANT AX-S4 ICCP CONFIGURATION ISSUES ...........................................................................................................135
BASIC AX-S4 ICCP REDUNDANT CONFIGURATION PROCESS ...............................................................................................135
ON-LINE AX-S4 ICCP RECONFIGURATION ......................................................................................................................136
DATA SYNCHRONIZATION ISSUES ...................................................................................................................................136
Configuration Synchronization ..........................................................................................................................136
Data Synchronization Sample Startup Scenarios ...............................................................................................143
CHAPTER 9: ICCP MONITOR ............................................................................................................................... 145
DROP-DOWN MENUS .................................................................................................................................................146
Edit - Preferences ...............................................................................................................................................146
Tools - Clear Status ............................................................................................................................................148
Start Log Viewer ................................................................................................................................................148
LOCAL CONTROL CENTER OVERVIEW FORM .....................................................................................................................148
STATISTICS FORM .......................................................................................................................................................149
Server Services ...................................................................................................................................................149
Device Services ...................................................................................................................................................150
Information Messages .......................................................................................................................................150
Client Services ....................................................................................................................................................150
Information Messages .......................................................................................................................................150
REDUNDANCY SCREEN .................................................................................................................................................151
Redundancy Status ............................................................................................................................................151
LOGGING SCREEN .......................................................................................................................................................152
AX-S4 ..................................................................................................................................................................152
MI.......................................................................................................................................................................153
MMS ..................................................................................................................................................................153
MVL ....................................................................................................................................................................153
Redundancy .......................................................................................................................................................153
Security ..............................................................................................................................................................153
Right Click Logging Option .................................................................................................................................153
DATA VALUES SCREEN .................................................................................................................................................154
PROTECTION EVENTS SCREEN........................................................................................................................................155
LOCAL DEVICES ..........................................................................................................................................................156
LOCAL MESSAGES .......................................................................................................................................................157
REMOTE CONTROL CENTERS OVERVIEW..........................................................................................................................158
INDIVIDUAL REMOTE CONTROL CENTER OVERVIEW ...........................................................................................................160
Right Click on Name of Remote Control Center .................................................................................................160
Remote Control Center Statistics .......................................................................................................................161
Remote Control Center Association Overview ...................................................................................................162
Remote Control Center Association Statistics ....................................................................................................162
Remote Control Center Data Values ..................................................................................................................164
Remote Control Center Protection Events .........................................................................................................165
Remote Control Center Devices .........................................................................................................................166
Remote Control Center Messages......................................................................................................................167
REMOTE CONTROL CENTER DSTS OVERVIEW ..................................................................................................................167
Remote Control Center Individual DSTS Overview .............................................................................................168
LOCAL DATA SET TRANSFER SETS OVERVIEW ...................................................................................................................171
Local DSTS Status and Parameters ....................................................................................................................172
CHAPTER 10: AX-S4 ICCP OPC CLIENT ................................................................................................................. 173
USING AX-S4 ICCP OPC CLIENT FOR ICCP DATA MIRROR APPLICATION..........................................................................176
Example ICCP Data Mirror Using Default Configuration ...................................................................................177
USING AX-S4 ICCP OPC CLIENT FOR GATEWAY APPLICATIONS ..........................................................................................178
TIME STAMPS AND QUALITY FLAGS ..............................................................................................................................179
OPC TYPE MAPPING CONSIDERATIONS ..........................................................................................................................180
USING THE AX-S4 ICCP OPC CLIENT CONFIGURATION UTILITY ..........................................................................................182
Tools...................................................................................................................................................................183
Default OPC Tuning Parameters ........................................................................................................................183
ADD OPC SERVER DIALOG ...........................................................................................................................185
OPC GROUP DISPLAY ....................................................................................................................................185
Generic OPC Group Item Selection Form ...........................................................................................................188
OPC Group Item List Display ..............................................................................................................................189
OPC Item Mapping.............................................................................................................................................191
CHAPTER 11: EXCEL FILE IMPORT AND EXPORT ................................................................................................. 192
FUNCTIONALITY ..........................................................................................................................................................192
USING THE EXCEL OPTION FROM THE ICCP CONFIGURATION UTILITY ....................................................................................193
Export from Excel ...............................................................................................................................................193
Sample excel files ...............................................................................................................................................194
Import from Excel ..............................................................................................................................................194
ICCPEXCEL WORKBOOK COLUMNS AND VALIDATION ........................................................................................................195
Data Type mappings ..........................................................................................................................................197
MAP Info Fields ..................................................................................................................................................197
USING THE COMMAND LINE UTILITY ...............................................................................................................................198
APPENDIX A: LOG VIEWER AND LOGGING ......................................................................................................... 200
LOG FILE LOCATIONS ...................................................................................................................................................201
LOG CONFIGURATION EDITOR .......................................................................................................................................202
Standard Logging...............................................................................................................................................202
Log Control Screen .............................................................................................................................................202
AX-S4 ICCP Log Configuration XML File .............................................................................................................205
APPENDIX B: TROUBLESHOOTING...................................................................................................................... 208
PROBLEMS IN INSTALLATION .........................................................................................................................................208
PROBLEMS ESTABLISHING AN ASSOCIATION .....................................................................................................................208
RPL CONFIGURATION ISSUES ........................................................................................................................................208
HOW TO DETERMINE CURRENT VERSION ........................................................................................................................209
ERROR – UNABLE TO CREATE DATASET ............................................................................................................................210
APPENDIX C: REGISTRY PARAMETERS ................................................................................................................ 211
AX-S4 ICCP REGISTRY PARAMETERS. .............................................................................................................................211
SISCO STACK REGISTRY PARAMETERS ............................................................................................................................213
APPENDIX D: SISCO STACK CONFIGURATION ..................................................................................................... 214
SAMPLE SISCO STACK CONFIGURATION FILE ...................................................................................................................214
DESCRIPTION OF SISCO STACK CONFIGURATION XML FILE ................................................................................................217
LeanT_Profile Section.........................................................................................................................................217
Security_Profile Section .....................................................................................................................................219
AR_Matching_Profile Section ............................................................................................................................219
App_SNAP Section .............................................................................................................................................220
AR_Name Section ..............................................................................................................................................220
App_Network Section ........................................................................................................................................221
APPENDIX E: RUNNING SNAP-LITE ..................................................................................................................... 223
SNAP-LITE PARAMETERS .............................................................................................................................................224
RUN-TIME RECONFIGURATION ......................................................................................................................................225
APPENDIX F: ADDRESSING TERMINOLOGY ........................................................................................................ 226
PRESENTATION ADDRESS..............................................................................................................................................226
ACSE PARAMETERS ....................................................................................................................................................226
AR Names ..........................................................................................................................................................226
ADDRESSING CONCEPTS ...............................................................................................................................................227
Naming Authority ..............................................................................................................................................228
APPLICATION LEVEL ADDRESSING...................................................................................................................................228
AP Title ...............................................................................................................................................................228
AE Qualifier ........................................................................................................................................................228
AE Title ...............................................................................................................................................................228
Presentation Selector .........................................................................................................................................228
Session Selector .................................................................................................................................................229
Transport Selector..............................................................................................................................................229
AX-S4 ICCP User's Guide
CHAPTER 1: INTRODUCTION
AX-S4 ICCP is an OLE for Process Control (OPC) interface that provides plug-in connectivity to ICCP-TASE.2 for any
Windows application supporting OPC. With AX-S4 ICCP, any Microsoft® Windows® Software Application Package
that supports OPC can access real-time data in networked control centers and applications using the ICCP TASE.2
protocols. The AX-S4 ICCP overall architecture is illustrated below:
Figure 1: AX-S4 ICCP Overview Diagram
AX-S4 ICCP provides OPC client and server interfaces to both ICCP-TASE.2 servers and clients. This flexibility allows
AX-S4 ICCP to work with applications that support either an OPC client interface or an OPC server interface or
both.
CHAPTER DESCRIPTIONS
This manual explains how to interface OPC client applications to ICCP devices or applications through SISCO’s AX-
S4 ICCP OPC Server. The User’s Guide will explain the mechanics of the interface process. It is presented in the
following sections:
• Chapter 1: Introduction provides a brief overview, system requirements, and features supported by AX-S4
ICCP
• Chapter 2: Installation describes how to install and use AX-S4 ICCP.
1
• Chapter 3: Getting Started outlines AX-S4 features and setup options.

• Chapter 4: ICCP Fundamentals describes ICCP objects as used by AX-S4 ICCP.
• Chapter 5: AX-S4 ICCP Configuration describes the use of the ICCP Configuration Utility.
• Chapter 6: Building Applications using OPC describes how to use AX-S4 ICCP’s OPC server capabilities.
• Chapter 7: Remote Control Center Identification/Association Matching describes connection control flexibility
of AX-S4 ICCP.
• Chapter 8: AX-S4 ICCP Redundancy System describes how to use AX-S4 ICCP’s redundancy features.
• Chapter 9: AX-S4 ICCP Monitor describes a SISCO OPC client application designed for monitoring and
controlling AX-S4 ICCP. This is especially useful in systems where the AX-S4 ICCP main GUI is not available such
as rdp.
• Chapter 10: AX-S4 ICCP OPC Client Control describes hwo to use the new AX-S4 ICCP OPC Client.
• Chapter 11: Excel File Import and Export describes the functionality of how to use Excel to more efficiently
and effectively modify AX-S4 ICCP configuration.
• Appendix A: Logging describes the SISCO Log Configuration Utility and Log Viewer. It describes various
selectable log masks and illustrates sample logging for AX-S4 ICCP when different log masks are enabled.
• Appendix B: Troubleshooting explains how to troubleshoot basic problems with AX-S4 ICCP.
• Appendix C: Advanced Topics addresses AX-S4 ICCP advanced programming issues.
• Appendix D: Stack Configuration describes how to configure the new SISCO Stack using the configuration
utility.
• Appendix E: Running SNAP-Lite on Windows describes how to run the SISCO Stack.
• Appendix F: Addressing Issues explains the addressing scheme from the network and programmatic points of
view such as the Selector and AP Titles.
TERMINOLOGY
The following terms are used throughout the AX-S4 ICCP documentation:
Term Description
A connection between two ICCP Control Centers. Associations can be Client, Server, or Client
Association
and Server
This product provides the interface between control centers and applications on the ICCP
AX-S4 ICCP
network and the Windows-based Applications that can act as OPC clients.
A role assumed by an application when interacting with other applications that are assuming
Client the server role. The client role is generally assumed by an application that is making requests
for data from a server while the server is the application that “owns” the data.
Component Object Model.
COM
http://en.wikipedia.org/wiki/Component_Object_Model
Distributed Component Object Model
DCOM
http://en.wikipedia.org/wiki/Distributed_Component_Object_Model
International Organization for Standardization.
ISO
http://www.iso.org
2
Term Description
ICCP Inter-Control Centre Communications Protocol
ICCP Control
This refers to the control center or application running on a network using the ICCP (TASE.2)
Center or
protocols for communication.
Application
Manufacturing Message Specification
MMS
http://en.wikipedia.org/wiki/Manufacturing_Message_Specification
OLE (Object Linking and Embedding) for Process Control.
OPC
http://www.opcfoundation.org/
OPC Client This refers to an OPC application developed using a Software Application Package or a
Application programming tool such as Visual C++ or .Net 4.0.
Remote Desktop Protocol.
RDP
http://en.wikipedia.org/wiki/Remote_Desktop_Protocol
Stands for Redundancy Port Link – selecting a RPL link ensures proper security between two
RPL
redundant nodes.
A role assumed by an application when interacting with other applications that are assuming
Server the client role. The server role is generally assumed by an application that is the authoritative
source for data that other client applications might request access to or information about.
SISCO Stack SISCO’s MMS-Lite LEAN-T stack profile adopted for AX-S4 ICCP.
A process that is a combination of the SISCO Stack and the Secure Network Access Provider
SNAP-Lite
when Security Extensions software is installed.
Software
This refers to a front-end Windows-based product. It is used to provide the OPC functionality.
Application
Typically a SCADA, HMI, or historian product.
Package
Stands for Telecontrol Application Service Element. IECC870-6-503 TASE.2 Services and
TASE.2 Protocol V1996-08 and IEC 870-6-802 TASE.2 Object Models V2000-08.
http://en.wikipedia.org/wiki/TASE.2
User Account Control.
UAC
http://en.wikipedia.org/wiki/User_Account_Control
Extensible Markup Language. This is an international specification that specifies how to
construct “documents” (which can also be messages) that contain information. It is based
XML upon a hierarchical ASCII based tagging scheme and is in prevalent use in integration and
Internet applications.
http://en.wikipedia.org/wiki/Xml
3
THE AX-S4 ICCP MODEL
The AX-S4 ICCP Model illustrates how the various components of AX-S4 ICCP work together.
Figure 2: AX-S4 ICCP Model
AX-S4 ICCP includes the following primary components:
• AX-S4 ICCP OPC Server is the original AX-S4 ICCP interface that supports an OPC server interface for
both ICCP clients and servers. Systems that only have an OPC client interface available can continue to
use the AX-S4 ICCP OPC Server component with or without the AX-S4 ICCP OPC Client component.
• AX-S4 ICCP OPC Client (New with V6.0000) is an OPC gateway that works as an OPC Client interface for
Local Data Values. The AX-S4 ICCP OPC Client can be used to transfer data between any 2 OPC servers
similar to existing OPC bridge and gateway products available from third parties. That means the AX-S4
ICCP OPC Client can also be used for data mirroring (reflecting received remote data values to local data
values that can be accessed by other remotes) or gateways that use another OPC server protocol driver
to create a gateway between ICCP-TASE.2 and other protocols like IEC 61850, DNP3, Modbus or IEC
60870-5-10X. See Chapter 10.
• AX-S4 ICCP OPC Client Configuration Utility (New with V6.0000) is used to configure the OPC data
transfer of the AX-S4 ICCP OPC Client. See Chapter 10.
4
• ICCP Configuration Utility is used to configure the ICCP functions of the AX-S4 ICCP OPC Server such as
network addressing, remote nodes, bilateral tables, data sets, data set transfer sets, etc. The ICCP
Configuration Utility is also used to perform Excel File Imports and Exports (New with V6.0000) in
addition to the original XML file import and export capability. See Chapter 5 and Chapter 11.
ICCP Monitor is an application that allows you to monitor and control the activity of the AX-S4 ICCP OPC Server including active associations,
communications activity, data set transfer set activities, data values, redundancy status, messages, devices, devices, etc. See Chapter 9.
Figure 3: AX-S4 ICCP OPC Server Model
The AX-S4 ICCP OPC Server component provides all the core ICCP-TASE.2 functions for AX-S4 ICCP. The AX-S4 ICCP
OPC Server can work by itself to implement a complete client/server interface to ICCP-TASE.2 remote systems for
OPC client applications without using any other AX-S4 ICCP components that are not shown above. All the ICCP
functions of the AX-S4 ICCP OPC Server are configured using the ICCP Configuration Utility. Chapters 3-9 and
Chapter 11 of this document refer to the functions provided by the AX-S4 ICCP OPC Server component.
5
ICONS
The following Icons are used to represent AX-S4 ICCP and its components:
AX-S4 ICCP OPC Server – AX-S4 ICCP
ICCP Configuration Utility
ICCP Monitor
AX-S4 ICCP OPC Client (new component)
AX-S4 ICCP OPC Client Configuration Utility (new component)
OPC Test Client
SISCO Stack (new component)
Stack Configuration Utility (new component – only with AX-S4 ICCP Secure)
Log Viewer
Log Configuration Editor
6
SUPPORTED FUNCTIONALITY
OPC INTERFACE
AX-S4 ICCP adheres to the OPC Data Access (DA) Specification V3.00 (“OPC Classic and OPC Unified
Architecture (UA”). This specification can be downloaded from the OPC Foundation’s web site at
http://www.opcfoundation.org.
AX-S4 ICCP supports the following client and server side OPC interfaces:
• IOPCAsyncIO
• IOPCAsyncIO2
• IOPCAsyncIO3
• IOPCBrowse
• IOPCBrowseServerAddressSpace
• IOPCCommon
• IOPCGroupStateMgt
• IOPCGroupStateMgt2
• IOPCItemIO
• IOPCItemMgt
• IOPCItemProperties
• IOPCServer
• IOPCSyncIO
• IOPCSyncIO2
• IConnectionPointContainer
• IDataObject
• IEnumOPCItemAttributes
AX-S4 ICCP supports the following client side interface:
• IAdviseSink
• IOPCDataCallback
• IOPCShutdown
SYSTEM REQUIREMENTS
The following system requirements are required:
• Intel x86 (32 bit) or x86 (64 bite) bit based (or AMD based Intel compatible) computer with a, hard disk
with at least 2 GB free, 2GB RAM (minimum). 10GB free hard disk space an 4GB RAM is recommended.
• Windows 2003 Standard R2 32-bit, service pack 2
Windows 2008 R2 64 bit – Primary Test Operating System
Windows 7 64 bit
Windows 7 32 bit
Windows Server 2012 R2 64-bit
• AX-S4 ICCP and AX-S4 ICCP Secure have been test on VMware Workstation 10.0.3 build-1895310.
Note: AX-S4 ICCP is a 32 bit application that can run on 64 bit Operating Systems. Only TCP/IP is tested and
supported. ISO/OSI network and transport protocols are no longer supported.
7
• AXS4-ICCP-142-095-DEV or AXS4-ICCP-142-095-PAK. A Development license is required before purchasing

a PAK license.
• HASP Software license file or HASP USB dongle. Which type is determined at purchase. If using a software
license file, a permanent license file that enables the product to operate indefinitely is available by web,
or email. Please follow the installation instructions provided to obtain the permanent license file. A thirty-
day demo license file is provided with this product.
Note: Existing customers that have a Sentinel License or Sentinel USB dongle may continue to use that form
of licensing.
• An 802.3 network with TCP/IP (RFC1006).

• For Windows, 1GB of Random Access Memory (RAM) and/or hard disk space in addition to that required
by Windows processing. (The operating system swaps the contents of its RAM with the hard disk if the
RAM does not have enough memory to do all its processing). Increased memory improves the
performance of your system.
• Additional hard disk space and memory to accommodate the applications that you are running on your
system
• ICCP control centers or applications with which to communicate
• Any OPC Client supporting OPC 3.0 or OPC 2.05
• .Net 3.5 as well as Net 4.0 are required.
ASSUMPTIONS
The following assumptions are made about pre-existing knowledge:
• Familiarity with the Microsoft Windows operating environment you are using.
• Familiarity with the ICCP (Inter-Control Centre Communications Protocol – IEC 870-6-503 TASE.2 Services
and Protocol V1996-08 and IEC 870-6-802 TASE.2 Object Models V1996-08).
• Familiarity with the OPC specification and the OPC features of the OPC Client Application Software
Package you intend to use.
• The AX-S4 ICCP software will be installed on a system that meets the minimum requirements described
above.
• If using DCOM, familiarity with the proper configuration for your Operating System.
8
APPLICATION SUPPORT
This document and the associated software have been designed with the intent that the user will develop the
necessary applications. It is assumed that the user of this software will have knowledge and expertise in the
selected Application Software Package or Programming Tool.
SISCO is solely responsible for the proper operation of the AX-S4 ICCP product and not the developed Client
Application or the Application Software Package used with AX-S4 ICCP. The support available from SISCO for
AX-S4 ICCP does not include support of the OPC Client Application Software Package purchased from another
vendor.
IF SUPPORT IS NEEDED FOR AN APPLICATION SOFTWARE PACKAGE OR PROGRAMMING TOOL, YOU MUST
CONTACT THE DEVELOPER OF THAT SOFTWARE FOR SUPPORT. SISCO cannot provide support on the OPC
Client Application Software Package.
9
CHAPTER 2: INSTALLATION
The following section will provide detailed instruction for installing and using AX-S4 ICCP for Windows.
Important Notes on Upgrading from V5.0000 to V6.0000:
Before upgrading from an older version of AX-S4 ICCP-132-095 V5.0000, be sure to backup all configuration
and database files in the program data directories. Specifically the following files: iccpcfg.mdb, and
siscinf3.mdb.
You also need to backup the registry settings in the

HKEY_LOCAL_MACHINE\SOFTWARE\SISCO or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SISCO
branch.
During the upgrade of AXS4-ICCP-132-095 V5.0000 to AXS4-ICCP-142-095 V6.0000, the siscinf3.mdb and some
registry parameters will be converted to new configuration file format siscostackcfg.xml. Refer to Manually
Migrating the Database to the New XML Format.
SETUP TASK LIST

The following steps should be taken to setup and use AX-S4 ICCP:
1. Install a network adapter per the instructions that accompany it.

2. Start Windows.
3. Install the AX-S4 ICCP product. See the next paragraph for information.
4. Reboot your computer and restart Windows.
5. Make sure all information is properly configured using the supplied ICCP Configuration Utility.
6. Start AX-S4 ICCP by clicking on the Start button and selecting ProgramsSISCOAX-S4 ICCPAX-S4
ICCP. The SISCO Stack will start automatically.
7. Start an OPC Client and use OPC Commands to communicate with AX-S4 ICCP.
It is recommend to read the Installation and Configuration Guide for AX-S4 ICCP for a step-by-step guide to
using AX-S4 ICCP.
INSTALLATION
Due to extensive changes to comply with UAC requirements on the newer Operating Systems, SISCO has
moved the location of almost all SISCO installed files compared to older versions of the AX-S4 ICCP product
(V4.0059 and older). By default, the new development files are located in C:\Program Files\ SISCO\AX-S4 ICCP
or C:\Program Files (x86)\ SISCO\AX-S4 ICCP on 64 bit systems.
Configuration files are now located in the Common Application Data path. Existing configuration files (like the
iccpcfg.mdb or siscinf3.mdb) are preserved in a backup directory. The installation will convert the existing
data base files to the new format and can be found in the Common Application Data path depending on the
Windows Operating System.
It is important when migrating from V5.x of AX-S4 ICCP and V1.5000 of AX-S4 ICCP Secure, that the directory
paths not be changed in order for the migration of the configuration files to properly take place.
10
Carefully follow the steps shown below to install AX-S4 ICCP:
1. AX-S4 ICCP installation requires a user to have Adminstrator Privileges.

2. Insert the AXS4-ICCP-142-095 CD-ROM into the CD-ROM drive or click on the downloaded zip file .
If using a CD and the Autorun feature is enabled on your computer, go to Step 4. Otherwise, click on Start,
select the Run option, and type the following command:
{d}:setup where {d} designates the letter of your CD-ROM drive.
or click on Setup.exe in the zip file.
Please Note: For security reasons, you should not leave Autorun enabled on systems that are capable
of impacting the operating of power systems.
3. Serial number tracking program has been added to the installation.
Figure 4: AX-S4 ICCP Installation – Enter Serial Number
Serial numbers are used to track licensing. They have never been part of the distributed CD. It has been
difficult to determine serial numbers when there is more than one copy of AX-S4 ICCP.
Serial numbers follow the format of five numbers followed by AC4. If this is AX-S4 ICCP Secure, the suffix
is ACS4. It is recommended that you determine your serial number BEFORE you begin the installation
process. Serial numbers are displayed on the jewel case of the original CD or contained within the initial
email providing download information. If you do not know your serial number, please contact SISCO
Technical support at support@sisconet.com . If not possible, type 99999 to continue the setup without
the proper serial number.
11
Serial number will be written to the registry in the following location for future reference.
HKLM\SOFTWARE\Wow6432Node\SISCO\AX-S4 ICCP\CurrentVersion It is also stored in an ASCII file
SerialNumber.txt found in ProgramData/SISCO/AX-S4 ICCP.
4. Setup indicates three installation types:
Typical
General Installation of AX-S4 ICCP, OPC test client, ICCP Configuration Utility, ICCP Monitor, Log Viewer
and the OPC Client for AX-S4 ICCP.
Complete
Installs everything from Typical and the UA Wrapper.
Custom
Allows more flexibility in installation. It displays the following:.
Figure 5: AX-S4 ICCP Installation Features
5. When the AX-S4 ICCP Setup initializes, AX-S4 ICCP is restricted to install to a default set of folder names.
The folder names may not be changed. However, it is possible to install AXS4 ICCP to a hard drive other
than drive c.
6. The installation script will search the Windows Registry for previously installed product components and
install over the top of any existing installation. This is strongly recommended if updating the product. The
registry entries will be updated accordingly to reflect the path of currently installed AX-S4 ICCP product.
The default directory for installing SISCO products is c:\ Program Files\SISCO or
c:\ Program Files (x86)\SISCO on 64-bit systems.
7. Follow the instructions on the screen to complete the AX-S4 ICCP installation.
12
8. The installation sequence is as follows:

• All prerequisites such as the Visual C++ Redistributable, .Net 4.0
• LogViewer
• SISCO Stack, SNAP-Lite
• AX-S4 ICCP Components (AX-S4 ICCP OPC Server, ICCP Monitor, ICCP
• Configuration Utility, OPC Test Client, ICCP Test Application
• Optional OPC Client
• License driver file (used for software activation and USB dongles)
• License activation software
MANUALLY MIGRATING THE DATABASE TO THE NEW XML FORMAT

This process is automatically performed during the installation process. If installing AX-S4 ICCP Version 6.0000
as a clean install, you need to manually migrate the AR assignments found in the siscinf3.mdb database
BEFORE copying an older iccpcfg.mdb and overwriting the default iccpcfg.mdb database. All AR names and
assignments are then preserved. Wrong order causes default AR assignments to overwrite the migrated ones.
1. Start a command prompt in Administrative mode [elevated].

2. Navigate to C:\Program Files\SISCO\Network folder.
3. Type in the following command:
MigrateStack siscinf3="C:\Valid path here containing siscinf3 file….\siscinf3.mdb" SiscoStackCfg="
C:\ProgramData\SISCO\Network\Config\SiscoStackCfg.xml"
4. A successful migration will simply return the command prompt cursor to blink in the C:\Program
Files\SISCO\Network folder. No errors will display. A migration log file is produced in
C:\ProgramData\SISCO\Network folder.
5. Sample log log entries will show that the existing AR Names are skipped, and new ones added:
2014-09-16 13:33:22.610 MigrateStack/Always (Unknown -1 ThreadId=0x490 (1168))
Logging initialized

Validating Command Line Arguments

ValidArguments - Complete

Migrating Sisco Stack Configuration

MigrateArNames_SiscInf3 from file: C:\Temp\SUPPORT\ICCP\TICKETS\Ticket1731_SPIN_Erica_ICCP_ARName\siscinf3.mdb
2014-09-16 13:33:25.215 MigrateStack/Flow (Unknown -1 ThreadId=0x490 (1168))

MigrateArNames_SiscInf3: Adding AR Name 'axs4mms'

AR Name 'iccpclient' already exists, skipping

AR Name 'iccpserver' already exists, skipping

MigrateArNames_SiscInf3: Adding AR Name 'OBGS1'
13

MigrateArNames_SiscInf3: Adding AR Name 'SERVTR1'

MigrateArNames_SiscInf3 - Completed
AR Names Migrated: 3

Sisco Stack Configuration Migration – Completed
6. Now copy the user iccpcfg.mdb and replace the newly default installed one. The first time the AX-S4 ICCP
Configuration Utility is launched, it will upgrade the database to the latest format. A dialog will appear
after upgrading to confirm this.
DIRECTORY STRUCTURE
The directory structure shown is for Windows7/Server 2008/Server 2012:
Figure 6: AX-S4 ICCP Directory Stucture
Directory Path Description
\Program Files\SISCO\AX-S4 ICCP AX-S4 ICCP Program
<Common Application Data>\SISCO\AX-S4 ICCP\Config AX-S4 ICCP Client Configuration files
<Common Application Data>\SISCO\AX-S4

All AX-S4 ICCP Documentation
ICCP\Documentation
\Program Files\SISCO\Common SISCO OPCDAAuto.dll
C:\Windows\System32 or C:\Windows\SysWOW64 <WINSYSDIR>
14
Directory Path Description
\Program Files\SISCO\License SISCO License files
Sisco Software Configuration, Documentation and Log

<Common Application Data>\SISCO
files
Table 1: File Directory Paths
The <Common Application Data> path is different for various Windows Operating Systems.
Windows 2003 Application Data Common directory is:

\Documents and Settings\All Users\Application Data
Windows 7/Server 2008/Server 2012 Application Data Common directory is:

\ProgramData
MULTIPLE ETHERNET ADAPTERS AND TCP/IP
The SISCO Stack uses the underlying system to manage the TCP/IP connectivity in single or multi-card
environment. There is no additional configuration needed.
TCP/IP (USING RFC1006) SUPPORT
An Ethernet card must be installed and configured to support the Internet Protocol (TCP/IP) that provides a
compliant WINSOCK2 implementation on Windows. Normally this is done automatically when a Windows OS is
installed.
Configuring the Ethernet card is out of scope for this product.
SISCO STACK OVERVIEW
The SNAP-Lite process listens on TCP port 102 for incoming connections. All applications performing MMS/ICCP
communication must receive incoming connections through SNAP-Lite. Each application must configure a unique
set of selectors (PSEL, SSEL, and TSEL) and pass these selectors to the SNAP-Lite in a bind operation. The SNAP-Lite
process performs all necessary communication until the Presentation Connect Indication is received. Then it passes
all connection information including the TCP socket handle to the appropriate application based on the configured
selectors. The application takes over control of the TCP socket handle and performs all communication for that
connection from that point on (without interacting with SNAP-Lite).
SNAP-Lite is NOT used for outgoing TCP connections. The TCP connect requests are sent directly from each
application through the SISCO Stack library linked into AX-S4 ICCP.
Note that above description of communication flow is describing non-secure connections. For secure connections
the SNAP-Lite is used as a proxy process encrypting/decrypting data for incoming/outgoing connections. Refer to
the Installation and Configuration Guide for the Security Extensions for AXS4-ICCP for more information.
For more information on RFC 1006, please consult www.ietf.org.
15
SISCO Stack registry parameters are installed in:
HKEY_LOCAL_MACHINE\SOFTWARE\SISCO\Network and in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SISCO\Network
On 64-bit Windows the duplicated location for easy access by 32-bit applications. Identical changes to SISCO Stack
parameters should be done in both registry locations.
SISCO STACK STARTUP CONSIDERATIONS
The SISCO Stack, SNAP-Lite, can run either as a Service or as a normal process under Windows. By default on a new
installation, the Stack is installed as a Local System Service with the Startup Type option set to Automatic. This
means that the SISCO Stack service will start when system is booted and will run until it is stopped manually or the
system is shutdown.
To change the Startup option:
1. Click on Start, select Control Panel.

2. Open Administrative Tools.
3. Select Services.
4. Locate the SISCO SNAP-Lite Service and double click on it.
5. Select Startup type Automatic or Manual from the startup options.
SNAP-Lite should be run as a service. If there is any reason for the SNAP-Lite to run as a normal process it needs to
be removed from the Windows Services by running following the command from Start menu:
All ProgramsSISCOSNAP-LiteUnregister SNAP Lite Service.
When SNAP-Lite is started from the Start menu or command window, it detaches itself from the command
window and runs in the background. To stop SNAP-Lite open the Windows Task Manager, find the snap_l.exe in
the list of Processes and select End Process.
To make SNAP-Lite start as a service run the following command from Start menu:
All ProgramsSISCOSNAP-LiteRegister SNAP Lite Service.
The following execution cases of SNAP-Lite and Client/Server applications are supported. One configuration is
excluded due to Windows limitation on passing a TCP handle from SNAP-Lite to a Server application.
Server Application Accepting Connections Client Application Requesting Connections

Service or Service or
Non-Privileged Non-Privileged
Administrator Administrator
SNAP-Lite Service
Yes Yes Yes Yes
or Administrator
SNAP-Lite
No Yes Yes Yes
Non-Priviledged
Table 2: Service Privilege Levels for the SISCO Stack
16
AX-S4 ICCP STARTUP CONSIDERATIONS

AX-S4 ICCP can be run either as a Service or as a normal process under Windows. By default on a new installation,
AX-S4 ICCP is installed as a Local System Service with the Startup Type option set to Manual.
Figure 7: Services Control Panel
It can be started from the Services Control Panel. It can also be started as an automatic service. From the Services
Control panel Right click on SISCO AX-S4 ICCP and select Properties, the Startup Type can then be changed from
Manual to Automatic.
Figure 8: AX-S4 ICCP Service Properties
17
This means that the SISCO Stack service will start when system is booted and will run until it is stopped manually or
the system is shutdown.
AX-S4 ICCP can also be started by OPC Clients.
Important Note: AX-S4 ICCP is dependent on the SISCO Stack process.
RUNNING AX-S4 ICCP AS A MANUAL PROCESS
If desired, AX-S4 ICCP can be configured to run as a normal process in the COM Registry. This can be useful for
troubleshooting issue. To have AX-S4 ICCP ran as a manual process, open a command prompt and type the
following command from the directory shown:
In this case, COM will start AX-S4 ICCP as a normal process. Start AX-S4 ICCP by clicking on the Start button and
selecting All ProgramsSISCOAX-S4 ICCPAX-S4 ICCP.
Notes: These commands must be executed from the AX-S4 ICCP directory and the Command Prompt must be
started as “Run as administrator”.
If AX-S4 ICCP is run as a manual process, then the SISCO AX-S4 ICCP OPC Client must also be run as a
manual process accessed from the start menu. Both AX-S4 ICCP and the SISCO OPC Client must be run
as a service or both manual processes. Both need to run as Adminstrator.
To have AX-S4 ICCP run as a service again, open a commend prompt and type the following command:
In this case, the Service Control Manager will start AX-S4 ICCP as a service.
After invoking AX-S4 ICCP to run as a Service. To have AX-S4 ICCP run as a Service that is started automatically
when the operating system powers up, set the Startup Type option back to Automatic.
18
Figure 9: AX-S4 ICCP Service Control Panel Properties
USING THE OPC UA WRAPPER
The OPC UA Wrapper is to be used with the AX-S4 ICCP OPC Server only. There is not a UA Wrapper for the AX-S4
ICCP OPC Client. Please carefully read and follow these recommended steps:
1. Select configuration file for UA Local Directory Server [LDS]. Start the OPC Foundation UA Configuration Tool.
Run it as an Administrator.
2. Select the LDS and click on Edit.
3. Select the file in \program data\opc foundation\...
4. When it asks to overwrite this file
C:\ProgramData\OPC Foundation\Config\Opc.Ua.DiscoveryServer.Config.xml, click Yes.
5. Add the OPC UA wrapper as an application to manage, select its configuration file. On the Manage Security
tab click the Find button. Browse to the location of the Opc.Ua.ComServerWrapper.exe. On a 64 bit Windows
OS, the path is:
C:\Program Files (x86)\OPC Foundation\UA 1.02\Sample Applications\ComInterop\
Opc.Ua.ComServerWrapper.exe.
Notice the UA Configuration Tool finds the configuration file because it is installed in the same folder as the
OPC UA Wrapper. Click the OK button.
6. Generate an Application Certificate for the OPC UA Wrapper and document the location it appears in. Import
the Application certificate for the OPC UA wrapper. Click on the Manage Application tab.
7. Click Create Application Certificate button, and then change the key size of the self-signed certificate from
1024 to 2048 (a 1024 key is not as secure and not recommended), click the OK button.
19
8. Import the self-signed certificate that was created in C:\ProgramData\OPC Foundation\CertificateStores\

MachineDefault\certs\UA COM Server Wrapper [BFED1F7CD23D665FC421B081F09FBE2EC8EAA11D].der" by
the previous step. Click on the Manage Security tab. Then click on Import Certificate to Trust.
Note: This part of the .der file name changes with each time it is generated.
9. It will ask about adding the certificate to the trust list and accepting the certificate, click on Yes.
10. Stop and Start the OPC UA Local Directory Server service. This can be done by stopping and starting or by
clicking on Restart.
11. Wrap the AX-S4 ICCP COM server. Click on the Manage COM Interop tab.
12. Click on the Wrap COM Servers button.
13. Click the New button and browse to this file
Opc.Ua.ComServerWrapper.exe
14. Click the Add button and select SISCO.AXS4ICCP SISCO AX-S4 ICCP OPC Server Data Access 3.00.
15. Click the OK button, then the Close button.
16. Click OK. If the UAP COM Server Wrapper is running, restart it.
17. Using Windows Explorer, browse to the
Opc.Ua.ComServerWrapper.exe file, right click and Run As Administrator.
18. AX-S4 ICCP will start.
19. Add the OPC UA Client as an application to manage. Go to the Manage Security tab. Click the Find button.
Browse to the OPC UA Sample Client location:
C:\Program Files (x86)\OPC Foundation\UA 1.02\Sample Applications\Opc.Ua.SampleClient.exe.
Then click the OK button.

20. Add the OPC UA COM Server Wrapper's certificate to the trust list for the UA Client. Click on Select Certificate
to Trust. Highlight UA COM Server Wrapper. Click the OK button.
21. The UAP Configuration Tool should be displayed. The UA Sample Client accepts the UA COM Server Wrapper's
certificate. Click OK.
22. Add the UA Client certificate to the OPC UA Wrappers trust list by changing the application to manage from
the UA Sample Client to the UA COM Server Wrapper. Click the Select Certificate to Trust then highlight UA
Sample Client. Click OK and then OK again.
23. Start the UA Sample Client and connect it to the UA OPC Wrapper. The address space of AX-S4 ICCP is
viewable.
24. Select the drop down combo box of server to connect to. Click on <New>.
25. Click on UA COM Server Wrapper. Click OK.
26. View after clicking OK. Click the Connect button. Click OK. The Open Session dialog box will appear. Click OK
again.
27. The UA Client should connect to the UA Wrapper, the DA address space of AX-S4 ICCP will appear, Browse the
DataValues associated with UtilitySiteB.
20
ACTIVATING THE AX-S4 ICCP PRODUCT LICENSE (NEW CUSTOMERS)
Note: Users updating to latest version of AX-S4 ICCP product that have existing licensing such as a USB dongle,
or Sentinel software activation may continue to use these without re-activating the software.
The AX-S4 ICCP product uses HASP Software protection as licensed from SafeNet. This can be either a USB Dongle
or a software license that must be activated. The product when installed comes with an automatic 30 day trial
license.
Activated licenses can run on a full machine or a Virtual Machine. Using HASP, products running with an activated
license can be accessed through Remote Desktop.
If you are using a USB Dongle, attach it to an open USB port. The LED in the USB Dongle will turn red when it
detects the appropriate drivers. Customers must request a USB Dongle at the time of purchase.
For existing AX-S4 ICCP users, a Dongle Exchange Form must be filled out and a fee paid to cover the cost of the
exchange. Please contact SISCO Technical Support for more information.
If you are using a Dongle, skip the remaining software license activation steps on the following pages.
UPDATE LICENSE OR NEW LICENSE WITH NO INTERNET ACCESS (ACTIVATE AX-S4

ICCP (C2V))
To apply a new license if the machine does not have internet access, or update, modify a license for the AX-S4 ICCP
product, click on the Start button and select ProgramsSISCOAX-S4 ICCPLicenseUpdate AX-S4 ICCP (C2V)
From the Collect Key Status Information tab, there are two radio buttons.
Figure 10: Collect c2v File
21
Update of existing protection key  This option should be selected for most licensing
Installation of new protection key  This option should be selected if Cloning has been
detected
Create a *.c2v file by clicking on the Collect Information Button. Send this file to SISCO by email. Please include
the product serial number. Serial Number information is stored in two locations. VERY IMPORTANT.
SISCO will make the modifications to your license and send back a *.v2c file. Select this *.vc2 file from the Apply
License Update tab and click on the Apply Update button.
Figure 11: Apply v2c File
HASP ADMIN CONTROL CENTER (TROUBLESHOOTING)

To get information on all the HASP licenses on this machine, click on the Start button and select
ProgramsSISCOAX-S4 ICCPLicenseHASP Admin Control Center. The Sentinel License Manager Service
listens on port 1947. This Admin Control Center is used to troubleshoot licensing problems. You may be asked to
supply the following information if experiencing difficulties with the license.
22
Figure 12: Sentinel Admin Control Center Main Screen
Select the Products options to display the installed products on this machine.
Figure 13: Sentinel Admin Control Center Products Screen
Click on the Features button to get detailed information on the Features installed for this license.
Figure 14: Sentinel Admin Control Center Features Screen
23
To generate a diagnostic report, click on the Diagnostics button.
Figure 15: Sentinel Admin Control Center Diagnostics Screen
Click on Generate Report. Attach a screen shots of the Products and Features screen along with the Diagnostics
report into the ticket system.
LICENSE CHANGES
All license information is tracked in the AX-S4 ICCP log file called axs4iccp.log. There are several cases in which the
license will become invalid:
1. Adding/removing hard drive to/from the system will cause the license matching criteria to fail.
2. The AX-S4 ICCP product may have to be removed from the original machine and transferred to another.
3. The VM has been cloned and the licensing detects this. Sometimes the licensing incorrectly detects cloning.
In either case, please contact SISCO Technical Support (support@sisconet.com) and request a License Move Form
to transfer the license.
Please refer to the Knowledge Base (KB) article Common License Problems for an in-depth explanation of licensing.
Please refer to the KB Article: KB AX-S4 ICCP How HASP Detects Cloning on VMs.
STARTING AX-S4 ICCP AS A NORMAL PROCESS
To start AX-S4 ICCP, click on the Start menu button and select ProgramsSiscoAX-S4 ICCPAX-S4 ICCP. The
AX-S4 ICCP icon will appear on your taskbar.
Note: The SISCO Stack service should be configured as Automatic service; otherwise, it will need to be started
manually before AX-S4 ICCP is started.
AX-S4 ICCP is now ready to respond to OPC requests from any Software Application Package.
24
RUNNING AX-S4 ICCP
On startup, AX-S4 ICCP will load the selected configuration (see AX-S4 ICCP Configuration for more information)
and optionally establish any configured associations. In case of startup failures, examine the log files axs4iccp.log
and axs4iccp.err to determine the source of the problem. These are found in the <Common Application Data>\
SISCO\AX-S4 ICCP\Client directory. Please refer to Log Viewer and Troubleshooting.
Once AX-S4 ICCP has started successfully, maximize AX-S4 ICCP by clicking on the AX-S4 ICCP icon.
Note: If running AX-S4 ICCP as a service, the GUI cannot be displayed.
The following screen will appear with Status and Log windows:
Figure 16: AX-S4 ICCP main screen
AX-S4 ICCP Status window is shown at the top of the AX-S4 ICCP main screen. It indicates the number of current
OPC clients, the number of configured Remote Control Centers, the number of active associations, and the
selected logging mode. If the ViewStatus option is checked, status information on AX-S4 ICCP can be viewed
dynamically. If the ViewStatus option is not checked the status screen will not be displayed.
25
AX-S4 ICCP Log is displayed at the bottom. On startup, it logs licensing information such as number of days
remaining on a DEMO license. In addition, it logs all general activity to monitor ICCP and OPC activity. If
ViewActivity Log is checked, all activity related to the AX-S4 ICCP process can be viewed. If ViewActivity Log is
unchecked, the Activity Log screen will not be displayed.
Please refer to Log Viewer and Logging for more information on logging.
26
CHAPTER 3: GETTING STARTED
HELP DESK
Technical Support is handled through the SISCO Help Desk. The purchase of an AX-S4 ICCP development license
comes with one year of support and maintenance. Customer can then purchase a yearly support contract to
extend these benefits. Please contact SISCO for more information.
HOW TO ACCESS THE HELP DESK

The Help Desk is accessed through the SISCO portal. Log into the SISCO portal using your previously assigned user
name and password and the following link: https://portal.sisconet.com/default.aspx (If you do not know your
user name and password, please contact support@sisconet.com). Select the AX-S4 ICCP product from the left side
under File Libraries.
Figure 17: How to Access the Help Desk through the SISCO Portal
Please click within the green circle as shown on the screen to enter the Help Desk. This process allows a single sign
on using the same user name and password.
27
The following screen will be displayed:
Figure 18: SISCO Help Desk Main Screen
28
RECENT KNOWLEDGEBASE ARTICLES

There is a list of KB articles for AX-S4 ICCP. They are separated into the following categories:
Figure 19: Knowledge Base Articles
29
HOW TO ENTER A TICKET

To enter a ticket, click on the word Tickets in upper left. It will bring up the following form:
Figure 20: How to Enter a Ticket
The form should be filled in as follows:
Subject: Company Name followed by a short description of the problem

Ticket Type:
- Support: Requires general technical support such as general answers to questions - This is the default
- Defect: Possible error found in software
- Feature: A request for an enhancement to the existing version of the software
Product: Select the product from the drop down box  AX-S4 ICCP
Product Version: Select the Version Number from the drop down box. This is very important in order to handle
the issue.
Security Extensions Installed: Drop box indicating if running AX-S4 ICCP Secure
Customer Severity: Indicate the severity level of the ticket
- Low: Used for questions or problems that have no significant impact to operations - This is the default
- Medium: Able to use the product with some functional restrictions - No critical impact on operations
- High: Able to use the product but an important function is not available
- Critical: Cannot use the product or there is a critical impact on the customer’s operations that require an
immediate solution
30
Operating System: This is a required field and is important in diagnosing issues - This indicate Windows Operating
System and Service Pack. Many answers to problems are dependent on Operating System.
Reproducible: Indicate YES (if the problem can be re-created using a sequence of steps) or NO (if it happened only
once)
Description: List a short description of what happened. If reproducible, we need the steps taken to cause the
problem. As a description is being typed, KB articles can be suggested that may provide an answer to the question
being asked.
Figure 21: Suggested KB Article
Add Attachments: Click on the paper clip to add any log files or databases. If databases are being sent, please zip
or they will not be accepted.
Add Screen Recording: Click on the button to capture a video image of your whole screen for a limit of up to five
minutes. This feature requires JAVA to run.
Click on Submit to finish.
=============================================================================================
31
You will receive an email verification that a ticket has been submitted.
New Ticket Confirmation
Thank you for contacting the SISCO support department. Your request has been assigned the ticket number
2114.
A member of our team will review your submission as soon as possible.
If you would like to add additional information to this ticket, simply reply to this email.
To ensure proper delivery, the ticket number in brackets must be present in the subject line.
Thank You,
The SISCO Support Team!
SISCO
Figure 22: Ticket Verification
32
CONFIGURATION
The ICCP Configuration Utility (IccpCfg.exe) is the primary tool for configuring all aspects of AX-S4 ICCP. The ICCP
Configuration Utility can be used to:
• Configure network addressing

• Start AX-S4 ICCP
• Start the ICCP Monitor
• Start the AX-S4 ICCP OPC Client Control
• Start the Log Viewer and Log Configuration Editor
• Configure Associations
• Configure AX-S4 ICCP control parameters
• Configure Local Control Center objects
• Configure Remote Control Centers
Some features of the ICCP Configuration Utility are:
• Supports multiple Local Control Centers (only one can be active)

• Supports multiple Bilateral Tables
• Supports on-line reconfiguration
• Supports Client Value Discovery
• Supports Automatic Creation of DataSetTransferSets
• Can export configuration information to XML
• Can import configuration information from XML
See AX-S4 ICCP Configuration for more information.
USING AX-S4 ICCP AS AN ICCP SERVER
In order for AX-S4 ICCP to behave as an ICCP server, an OPC Client must be available to provide data. Local storage
is provided for all local data values. This data is read by and reported to configured ICCP remote control centers
without intervention by an OPC Client.
However, Information messages and some device operations require responses from an OPC Client.
The level of OPC Client responsibilities can be altered using the Auto parameters located in the AX-S4 ICCP General
Parameters of the ICCP Configuration Utility. When the Auto features are enabled, an OPC Client needs to update
the “Value” (or “State”) attribute and the Quality.CurrentSource attribute of a local Data Value. When the Auto
features are disabled, an OPC Client needs to update all local Data Value attributes. See General Parameters for
more information.
33
ICCP ADDRESSING ISSUES
The network address information for ICCP Control Centers is usually contained in the Bilateral Agreement. For
more information on Network Addressing Basics such as selectors, see Addressing Issues. To setup local and
remote network addresses using the ICCP Configuration Utility, see Addressing.
One of the fundamental responsibilities of an ICCP Server is Access Control. To correctly enforce Access Control a
server must be able to determine who is calling. This is achieved by comparing the source address of an incoming
connection with remote addresses configured locally. AX-S4 ICCP uses a set of rules for matching each element of
the network address. These rules can be modified if there are connection problems with other ICCP nodes. The
default rules are sufficient for interoperating with most other ICCP software products. See Remote Control Center
Identification/Association Matching or more information on the AX-S4 ICCP “Matching” algorithm.
REDUNDANCY
Two AX-S4 ICCP nodes can be set up as a redundant pair. The redundant pair consists of an active node and a
standby node. The active node maintains ICCP associations. The standby node waits for a failover condition. The
redundant nodes pass messages to allow the standby node to detect a failover condition in the active node. See
AX-S4 ICCP Redundancy System for more information.
Use the ICCP Configuration Utility to setup the Redundancy options. General information is required for the
redundancy connection. Several parameters are used to determine when failover occurs. Options for synchronizing
data are also available. See AX-S4 ICCP Configuration for more information on how to configure redundancy and
synchronize configuration.
OPC Item strings can be used to monitor and control the state of each node. The redundancy items strings are only
supported if AX-S4 ICCP is configured as Redundant Primary Role or Redundant Secondary Role. See Chapter 5:
Building Applications Using OPC for more information.
34
CHAPTER 4: ICCP FUNDAMENTALS
This chapter is meant to be a brief overview of ICCP functionality as it applies to configuring AX-S4 ICCP. It is not
meant to replace reading the following ICCP protocol documents:
IEC 60870-6-503 Telecontrol equipment and systems - Part 6-503: Telecontrol Protocols compatible with ISO
standards and ITU-T recommendations - TASE.2 Services and protocol
IEC 60870-6-702 Telecontrol equipment and systems - Part 6-702: Telecontrol protocols compatible with ISO
standards and ITU-T recommendations - Functional profile for providing the TASE.2 application service in end
systems
IEC 60870-6-802 Telecontrol equipment and systems - Part 6-802: Telecontrol protocols compatible with ISO
standards and ITU-T recommendations - TASE.2 Object models
SISCO offers a 2 to 3 day training program on the ICCP protocol and AX-S4 ICCP functionality. It is highly
recommended to contact SISCO at support@sisconet.com for more information. This is the most effective way of
configuring and implementing AX-S4 ICCP.
MMS AND ICCP
ICCP (TASE.2) protocol relies on a subset of services of the MMS (ISO 9506) protocol. See Wikipedia -
http://en.wikipedia.org/wiki/Manufacturing_Message_Specification.
VMD AND DOMAINS

MMS Objects exists in a VMD (Virtual Manufacturing Device). This is the main object under which all other objects
such as Variables are stored. ICCP refers to this as a VCC (Virtual Control Center). This represents the objects
present in a physical control Center. More than one Client Control Center has access to VCC objects.
Some MMS Objects exist in a localized domain. This is a subset of the VMD. ICCP refers to this as ICC. Access to ICC
specific objects is limited to only one control center.
All ICCP objects must have a specific object scope, either VCC- or ICC-.
CLIENT AND SERVER RELATIONSHIP

These terms represent the service role in ICCP. A Client is an application or device that asks for data or an action
from the server. A Server is an application or device that maintains data objects and performs operations on behalf
of clients. An application can be a Client or a Server or both depending on the operation. Clients always send a
request. Servers receive an Indication. Servers send a Response and Clients receive a Confirmation. These MMS
terms are useful in troubleshooting problems from a log file.
35
SERVICE MAPPING – MMS TO ICCP

The following table shows the relationship between services names in MMS and ICCP Services for Blocks 1 and 2.
In the AX-S4 ICCP log file, the MMS services names are displayed.
MMS ICCP
Initiate Start Association
Association
Conclude/Abort Stop Association
Read Get Data Value
Write Set Data Value
Data Value
GetNameList Get Data Value Names
GetVariableAccessAttributes Get Data Value Types
DefinNamedVariableList Create Data Set
Data Set
DeleteNamedVariableList Delete Data Set
Write Start Transfer
Data Set Transfer Set Write Stop Transfer
Information Report DSTS Report
Table 3: MMS to ICCP Service Mapping
SUPPORTED ICCP BLOCKS
The following Conformance Building Blocks (CBBs) are supported by AX-S4 ICCP:
BLOCK 1 – BASIC SERVICES

All ICCP implementations must support Block 1. Block 1 includes association establishment, Data Value and Data
Set Objects, and Data Set Transfer Set Objects.
BLOCK 2 – EXTENDED CONDITION MONITORING

Supports Report By Exception (RBE).
BLOCK 3 – BLOCKED TRANSFERS

Removes ASN.1 encoding and uses network ordering for larger bulk transfers. It is a way to reduce the number of
bytes transmitted in a Data Set. Data Value attributes are transmitted as fixed sizes in network order. This is
recommended for moving large amounts of data over a network connection.
BLOCK 4 – INFORMATION MESSAGE

Implements sending a text or binary Messages.
36
BLOCK 5 – DEVICE CONTROL

Allows select, operate, get tags, and set tags on devices that a server controls.
ICCP NAMES
Objects such as Data Values, ARs, Domains, Devices, DataSet names use ICCP Names. These follow ISO Identifier
Rules. The maximum size is 32 characters. This is a unique text string. Each name is up to 32 characters in length
consisting of alphanumeric characters (“a…z”, “A…Z”, and “0…9”), underscore (“_”) or dollar sign (“$”). The first
character must be a letter.
ICCP DATA TYPES
Below is a list of ICCP Data Types and their descriptions.
ICCP DATA TYPE DESCRIPTION

Discrete Integer 32
DiscreteQ Integer32 with Quality
DiscreteQTimeTag Integer32 with Quality and Time Stamp
DiscreteQTimeTagExtended Integer32 with Quality and Time Stamp with millisecond resolution (2000-08)
DiscreteExtended Integer32 with Quality, Timestamp and COVCounter (Change of value counter)
Real Floating Point
RealQ Float with Quality
RealQTimeTag Float with Quality and Time Stamp
RealQTimeTagExtended Float with Quality and Time Stamp with millisecond resolution (2000-08)
RealExtended Float with Quality, Timestamp, and COV Counter
State Bitstring
StateQ Bitstring with Quality
StateQTimeTagExtended Bitstring with Quality and Timestamp with millisecond resolution (2000-08)
StateExtended Bitstring with Quality, Timestamp and COVCounter
StateSupplement State Supplemental bit string
StateSupplementQ State Supplemental bit string with Quality
StateSupplementQTimeTag State Supplemental bit string with Quality and TimeStamp
StateSupplementExtended State Supplemental bit string with Quality, Timestamp and COVCounter
SingleProtectionEvent Single Event Flags bitstring with operating time and event time
PackedProtectionEvent Event Flags bitstring, PackedFlags bitstring with operating time and event time
Table 4: ICCP Data Types
37
BITSTRING DEFINITIONS FOR ICCP DATA TYPES

Below are definitions for what is contained in each data type bitstring:
State BitString contains: State BitString with quality contains:

State_hi[0], State_hi[0],
State_lo[1], State_lo[1],
unused [2], Validity_hi[2],
unused [3], Validity_lo[3],
unused [4], CurrentSource_hi[4],
unused [5], CurrentSource_lo[5],
unused [6], NormalValue[6],
unused [7] TimeStampQuality[7]
Quality BitString contains: StateSupplemental BitString contains:

unused[0], State_hi[0],
unused[1], State_lo[1],
Validity_hi[2], Tag_hi[2],
Validity_lo[3], Tag_lo[3],
CurrentSource_hi[4], ExpectedState_hi[4],
CurrentSource_lo[5], ExpectedState_lo[5],
NormalValue[6], Reserved[6],
TimeStampQuality[7] Reserved[7]
There are several types of Protection Equipment Event BitStrings:
Single Flags BitString contains: Event Flags BitString contains: Packed Flags BitString contains:
ElapsedTimeValidity[0], General[0], ElapsedTimeValidity[0],
Blocked[1], Phase1[1], Blocked[1],
Substituted[2], Phase2[2], Substituted[2],
Topical[3], Phase3[3], Topical[3],
EventValidity[4], Earth[4], EventValidity[4],
Unused[5], Reverse[5], Unused[5],
EventState_hi[6], Unused[6], Unused[6],
EventState_lo[7] Unused[7] Unused[7]
38
DATASETS
A DataSet is a listing of the Data Values packaged so that the Server can send the information to the Client in a
meaningful manner. The list of Data Values is limited by the size of the PDU. This is typically 32k but can be larger
or smaller. It is negotiated by both the Local and Remote Control Center. The list of Data Values in a Data Set is
determined by the client and stored in the Servers ICC scope as each Data Set is specific to each Client. When the
ICCP Server serves the data it is delivered using reports in the same order as defined by the Client.
DATASETTRANSFERSETS
A DataSetTransferSet (DSTS) is a list of DataValues based on certain criteria called DSConditions. The name for a
DataSetTransferSet is created by the server. DSConditions are defined by a client and are then associated with a
DataSetTransferSet name.
DSCONDITIONS
DataSet Conditions govern how DSTS are sent. These are configured in the ICCP Configuration Utility.
There are some important rules to follow when configuring DSConditions for a DSTS:
• Block 1 reports use Interval.

• Block 2 reports use BufferTime and possibly Integrity.
• Interval with RBE off functions as Integrity with RBE on. RBE (Report by Exception) is always off in Block 1
always on in Block 2.
• Integrity only used in Block 2.
• A time Value of 0 means send it now.
• Interval Time Out flag controls the Interval Timer.
• The Interval is how often the report will be sent. When RBE is set, only points changing in the Interval are
reported by name.
• Integrity Time Out flag controls the Integrity Timer.
• The Integrity is how often the entire DataSet is reported.
• Object Change flag controls the BufferTime.
• BufferTime is time interval to buffer changes before reporting to TASE.2 client.
• BufferTime starts when first Object Change condition occurs.
• If RBE is off, the entire DataSet is reported.
• If RBE is on, only current state of objects in Data Set that have changed are reported
• If BufferTime is 0, then a report is generated for each change.
• If multiple changes occur to same object during a BufferTime, only the last value is reported.
39
Figure 23: DSTS Integrity and BufferTime Example
Figure 24: DSTS Interval and RBE On Example
40
Figure 25: DSTS Interval and RBE Off Example
MESSAGE HANDLING – BLOCK 4
Information Messages provides a way to send text or binary data. This can be used by either an ICCP Client or
Server. For example, sending a text message to an historical log or an alarm to an application running on an
operator station.
The message is identified by a reference ID. The size of the message is limited by a preconfigured maximum size.
AX-S4 ICCP needs an OPC client in order to pass the message to the Remote Control Center.
Please refer to the KB article AX-S4 ICCP Sending a Block 4 Message Object for an example of how to use
Messages with AX-S4 ICCP.
DEVICE HANDLING – BLOCK 5
A device represents a real object in ICCP such as a breaker. Block 5 provides a mechanism for transferring a
‘request to operate a device’ from one ICCP implementation to another. ICCP does not directly control the device;
instead it communicates a client’s request to operate a device to the server.
ICCP retains some of the important characteristics of RTU device control. Specifically, the need to select and
validate before operation for interlocked devices and the armed-for-execution mode for a selected device.
A Control Point object represents some real world object or device. They can consist of a Command object or a Set
Point object. A Command object, such as a switching device or transformer, takes a short integer as the command
for the device. Analog and digital Set point objects such as power units take a discrete integer or float as the Set
Point value.
The ControlPoint object is used to transfer the request. It distinguishes between a device operation (COMMAND)
and the transfer of a numeric value (SETPOINT), either floating point (SetpointRealValue) or integer
(SetpointDiscreteValue).
This control request can be for non-interlocked devices (NONINTERLOCKED) or interlocked devices (INTERLOCKED).
Both command and setpoint operations can be interlocked or non-interlocked. Non-interlocked controls are
control operations that do not require select-before-operate (SBO) confirmation. These might include transformer
tap changes, raise/lower operations and digital value setpoint type operations. Interlocked controls on the other
hand, require select-before-operate confirmation for critical operations such as breaker trip/close, recloser on/off
and HLO lamp on/off.
41
For interlocked control operations, the client sends a request to operate a specified device to the server. After
checking for the existence of the device object, checking access control in the Bilateral Table, the server then
performs a local verification that the device is available for operation. The verification checks that the server
actually performs are a local implementation issue and not part of AX-S4 ICCP. The device is SELECTED and a
previously agreed to CheckBackName is provided to the client to confirm that the correct device has been
selected. A Time-out period is configured giving the length of time that the device will remain selected by the
server.
ICCP does provide a mechanism for the server to report to the client whether the desired control point is tagged.
The server reports:
0 if the device is not tagged

1 if the device is tagged open and close inhibit
2 if the device is tagged close only inhibit
The client, having received a verification of device operability and a validation of device selected, then sends a final
request to have the device operated by the server.
The server passes the operate request to the physical device and notifies the client of success or failure. The result
implies that the server made the operate request, not that the physical device actually performed the operation.
An informal description of device control can be found in 870-6-503 section 5.1.10 and a formal description can be
found in section 5.2.11. The device object model mapping can be found in section 6.15. Device operations and
action mapping to MMS including a sequence of device control diagram can be found in section 7.1.6.1. The
control point object is described in 870-6-802 section 5.1.2, the type descriptions in section 6.1.2 and the
mappings to MMS in section 7.1.2.
To Handle device operate request:
The OPC Client needs to Monitor the following:
Read Only
LocalName:DeviceOperate~CDC2_AR1.Indication
LocalName:DeviceOperate~CDC2_AR1.RemoteVCC
LocalName:DeviceOperate~CDC2_AR1.Value
Write Only
LocalName:DeviceOperate~CDC2_AR1.Status
LocalName:DeviceOperate~CDC2_AR1.SendResponse
When LocalName:DeviceOperate~CDC2_AR1.Indication is TRUE - you have received an operate request indication.

The LocalName:DeviceOperate~CDC2_AR1.RemoteVCC field contains the name of the remote control center
attempting to operate the device. The LocalName:DeviceOperate~CDC2_AR1.Value field contains the data to
operate the device.
42
After the LocalName:DeviceOperate~CDC2_AR1.Indication changes from FALSE to TRUE you are required to write
an appropriate value to the LocalName:DeviceOperate~CDC2_AR1.Status field and write a 1 to the
LocalName:DeviceOperate~CDC2_AR1.SendResponse field. This will cause AX-S4 ICCP to send the response to the
remote control center that issued the operate request. To handle incoming Operate Device requests the OPC
Client application must monitor the Indication, RemoteVCC, Value, Status, and SendResponse attributes of a
LocalControlCenter device.
When an Operate Device request is received from a remote client, the Indication attribute is set to 1, the Value is
set to the value received from the remote client and the RemoteVCC attribute is set to the name of the remote
control center requesting to operate the device.
It is the responsibility of the OPC Client application to set the Status, defined as:
0 = Success
1 = Device Does Not Exist
2 = Access Denied
3 = Device Inoperable
4 = Device Temorarily Unavailable
5 = Other error
and write a 1 to the SendResponse attribute. The AX-S4 ICCP server will return a Device Temporarily Unavailable
status if the DeviceOperate is not actively monitored by an OPC Client. Please refer to the KB article How to
Operate a Device Using Sample for an example of how to use Devices with AX-S4 ICCP.
43
CHAPTER 5: ICCP CONFIGURATION UTILITY
Objects for AX-S4 ICCP are defined using the ICCP Configuration Utility. Using this utility, configuration data is
maintained in an MS Access Database and can be exported to an XML file. AX-S4 ICCP can read the data directly
from the database or from the XML file (This option can be set in the ICCP Configuration Utility). The XML file can
be edited with any editor but it is strongly recommended that the ICCP Configuration Utility be used to ensure that
the XML file is error free.
To start the ICCP Configuration Utility, from the Start bar, select All ProgramsSISCOICCP ConfigurationICCP
Configuration. It brings up the following screen:
Figure 26: ICCP Configuration Utility Main screen
ICCP CONFIGURATION UTILITY
The ICCP Configuration Utility is used to create and maintain Local Control Center objects and Bilateral Tables for
exchanging data with Remote Control Centers. It also is used to set AX-S4 ICCP options for the ICCP server,
connection control, and redundancy control. Furthermore, the ICCP Configuration Utility can be used to configure
the SISCO OSI Stack. Before using this utility to setup Local Control Center and Remote Control Center addresses,
please see the Appendix on Addressing Issues. The following are configuration definitions available from the drop
down menu selections on the top:
44
FILE
EXPORT TO XML FILE

Exports Local Control Center information from the ICCP Configuration Database to an XML configuration file.
IMPORT TO XML FILE

Imports Local Control Center information from an XML configuration file to the ICCP Configuration Database.
EXPORT TO EXCEL
Note: A detailed explaination on how to use Excel to Import and Export from the ICCP Configuration Utility is
found in Excel File Import and Export.
Brings up a form to choose a selected Local Control Center Name from a list of all configured Local Control Centers.
The Export File indicates the name of the Microsoft Excel file (xlsx) and the path where it will reside. Selecting …
saves the file to another location. In addition to exporting all information to an Excel file, there are options to
select only one type of object to export such as LocalDataValues, LocalDevices, LocalMessages, RemoteDataValues,
RemoteDevices, and RemoteMessages.
Figure 27: Export LCC Configuration to Excel
IMPORT FROM EXCEL

Brings up a form used to import a Microsoft Excel file (xlsx) for a Local Control Center from a list of all configured
Local Control Centers. Importing the file will save it to the ICCP Configuration Database. In addition to importing all
information from an Excel file, there are options to select only one type of object to import such as
LocalDataValues, LocalDevices, LocalMessages, RemoteDataValues, RemoteDevices, and RemoteMessages.
EXIT
Exits the ICCP Configuration Utility.
45
EDIT
PREFERENCES
Figure 28: ICCP Configuration Utility Preferences screen
AR MODES - CONFIGURATION MODE

Specifies the mode of the ICCP configuration. AX-S4 ICCP uses the ICCP Configuration database (IccpCfg.mdb). The
only option for this product is AX-S4 ICCP.
GENERAL - CONFIRM ACTIONS

Checking this box will enable the display of validation message boxes with each action (“Are you sure you want to
do this?”).
DATA SET CALCULATION - CONSERVATIVE

Checking this box instructs Iccp Cfg to assume that the remote node always uses the ListOfVariables encoding
option for DSTS reports, even when this results in the report being too large to send. Most implementations
automatically switch to the more compact NamedVariableList encoding option in this case. This allows more
variables to be added to a DataSet.
TREE NAVIGATION - DOUBLE CLICK

Checking this box will require a double click on a node in the navigation tree to view a form in the right pane,
disabling the single click option.
46
VIEW
The ICCP Configuration Utility provides a great deal of user control over sizes and positions, and in the case where
these changes are not ideal the Restore and Reset menu options can be helpful.
Figure 29: ICCP Configuration Utility View Menu
RESTORE DEFAULT SIZE

Restores the ICCP Configuration Utility windows sizes, pane layouts, and position to the default. Due to the
controls used in the product, it may be necessary to restore to the default size if forms become unusable.
RESET COLUMN SIZES

Restores the ICCP Configuration Utility column sizes to default optimized sizes.
CLEAR STATUS
Clears the Status message box at the bottom of the ICCP Configuration Utility.
REFRESH
Causes the ICCP Configuration Utility to reload information from the configuration database and
reload the object trees. This is useful when the configuration data has been modified externally,
such as by an AX-S4 ICCP discovery operation.
47
TOOLS
Figure 30: ICCP Configuration Utility Tools screen
ASSOCIATION SUMMARY
This is the summary of configuration information for all associations. The following parameters can be configured
by clicking within a field and entering the new data. Some fields will have dropdown boxes from which to make a
new selection. The Esc key can be used to end the edit and return the original contents to the field.
Figure 31: ICCP Configuration Utility Association Summary screen
Local Control Center - This is the name of the Local Control Center to which the association belongs. It cannot be
edited.
Remote Control Center - This is the name of the Remote Control Center to which the association belongs. It cannot
be edited.
Association - This is the name of the association.
48
Initiate - If this parameter is set to YES, it will indicate that the Local Control Center will initiate associations with
this Remote Control Center. Set to NO, the association state will go from IDLE to LISTEN when the association is
started.
Local AR - This specifies the local AR Name used for the association. It will be highlighted in red if it is missing or
configured with an AR Name that does not exist in the database.
Remote AR - This specifies the remote AR Name used for the association. If Initiate is set to YES, the Local Control
Center will attempt to establish an association with this AR Name. It will be highlighted in red if it is missing or
configured with an AR Name that does not exist in the database.
Remote AR2, Remote AR3, Remote AR4 - Up to four remote AR Names can be selected for an association. If
Initiate is set to YES, the Local Control Center will attempt to establish an association with Remote AR. When a
connection to Remote AR cannot be established, the Local Control Center will attempt a connection with each
successive AR Name (2-4). Remote AR 2, Remote AR 3, and Remote AR 4 are optional. This is used to establish
connections to Remote Control Centers with redundancy.
COMPACT DATABASE
This will reclaim space from deleted records in the configuration database. If the amount of data values changes
(additions, deletions) are significant, it is recommended to compact the database as part of routine maintenance.
START AX-S4 ICCP

This option starts AX-S4 ICCP.
START AX-S4 ICCP OPC CLIENT CONTROL

This option starts the AX-S4 ICCP OPC Client Control. This program is an OPC Client Configuration tool supplied by
SISCO. See AX-S4 ICCP OPC Client Control for more information on the functionality of this control.
START ICCP MONITOR

This option starts the AX-S4 ICCP OPC Monitor. This program allows using Windows Client Terminal Services
(Remote Desktop Connection) and provides an improved integration of AX-S4 ICCP with the user environment. See
AX-S4 ICCP Monitor for more information on the functionality of the this program.
START LOG VIEWER

This option starts the Log Viewer. This program is used to look at logging from multiple applications in one file or
view logging remotely. See Log Viewer and Logging for more information on the functionality of the this program.
START LOG CONFIGURATION EDITOR

This option starts the Log Configuration Editor. Current log parameter settings can be modified without bringing
applications down. This allows modifying log parameters while the application is running. See Log Configuration
Editor for more information on the functionality of the this program.
49
START SECURITY CONFIGURATION UTILITY

This option is greyed out for AX-S4 ICCP. The Security Configuration Utility is provided with AX-S4 ICCP Secure only.
RELOAD STACK CONFIGURATION

This option will reload any changes made to the stack configuration such as changing parameters in the Addressing
form or adding a new AR Name.
GENERAL PARAMETERS FORM
Important Note: Changes to the General Parameters form cannot be made while AX-S4 ICCP is running.
Figure 32: ICCP Configuration Utility General Parameters form
CONFIGURATION
Source - This specifies how AX-S4 ICCP will load configured data at startup, a XML configuration file or a Local
Control Center from the ICCP Configuration database.
File Name - This is the name of an XML configuration file that AX-S4 ICCP will load at startup if Configuration
Source is XML.
Local Control Center Name - This is the name of a Local Control Center in the ICCP Configuration database that AX-
S4 ICCP will load at startup if the Configuration Source is selected as DirectDatabase.
50
SPARE CAPACITY
Called Associations - AX-S4 ICCP will setup the number of called associations based on the number of those
already configured. This parameter indicates the number of additional called associations to setup. This will allow
for adding associations to existing Remote Control Centers as well as adding new Remote Control Centers.
Calling Association - AX-S4 ICCP will setup the number of calling associations based on the number of those
already configured. This parameter indicates the number of additional calling associations to setup, which will
allow for adding associations to existing Remote Control Centers as well as adding new Remote Control Centers.
AUTO (IN SECONDS)

Increment COV - If checked, AX-S4 ICCP will automatically increment the Change of Value counter for a Local data
value each time the value is written by an OPC Client.
Time Stamp - If checked, AX-S4 ICCP will automatically update the timestamp for a Local data value each time the
value is written by an OPC Client.
Quality Flags - If checked, AX-S4 ICCP will automatically handle the quality flags associated with a Local data value
each time the value is written by an OPC Client. At startup the quality flags are set to:
Validity = INVALID
CurrentSource = configured normal source (Calculated, Entered, Estimated, Telemetered)
NormalValue = NORMAL
TimeStampQuality = VALID if Auto-TimeStamp is enabled
When an OPC Client writes the Value attribute of a Local data value, the quality flags are set:
Validity = VALID
NormalValue = NORMAL If the Value written is within configured range, else ABNORMAL.
When AX-S4 ICCP is in standby mode and the Server State Suspended flag has been checked in the redundancy
form, the quality returned will be OPC_QUALITY_OUT_OF_SERVICE.
Start Associations - If checked, AX-S4 ICCP automatically starts all configured associations when AX-S4 ICCP begins.
Device Select Timeout - Indicates the number of seconds the server will wait for an operate request before
clearing the device state. Default is 30 seconds.
ICCP SERVICES
Enable Client DV Reads - If checked, AX-S4 ICCP will issue read requests to retrieve data for OPC Clients when the
requested remote data value is not configured into a DSTransferSet. When disabled, an error is returned to the
OPC Client if the remote data value is not in a DSTransferSet.
Caution: This behavior is NOT recommended! Although possible, it is recommended that this option be DISABLED
as a poorly configured AX-S4 ICCP can flood a remote ICCP server with read requests. Polling an ICCP Server for
data can cause association instability and poor performance. Data transfers are most efficiently done using
DataSetTransferSets. If a data value is not in a DSTS and checkbox is enabled, AX-S4 ICCP will use reads when a OPC
client subscribes to the value. This results in an inefficient use of CPU and network resources and slower
throughput.
51
IDENTIFICATION PARAMETERS
Notes: Please refer to Remote Control Center Identification/Association Matching for further information
regarding the use of the following parameters.
Changes to the Identification Parameters form cannot be made while AX-S4 ICCP is running.
Figure 33: ICCP Configuration Utility Identification Parameters form
AE TITLE MATCHING
Allow Missing - When this parameter is set to not checked (default), all AE Title elements that are configured
(locally) for the AR Name must be present in the Calling and Called AE Titles. When checked, any AE elements not
sent by the Remote Control Center are treated as present and matched, regardless of whether they are configured
for the AR Name.
Allow Extra - When this parameter is set to checked (default), it is acceptable for the Remote Control Center to
send AE elements that are not configured for the AR Name. When set to not checked, all AE Title elements that are
NOT configured (locally) for the AR Name must NOT be present in the Calling and Called AE Titles.
52
LOCAL/REMOTE – ADDRESS ELEMENT MATCHING

The matching control parameters of AP Title, AE Qualifier, AP Invoke, AE Invoke, PSEL, SSEL, TSEL, and Net Address
each affect a single local or remote addressing element. If a matching control parameter is checked, then the
configured (locally) value of that parameter must match the value as received in the initiate indication.
Matching Control Parameter Default

Match Local AP Title No
Match Local AE Qualifier No
Match Local AP Invoke No
Match Local AE Invoke No
Match Local PSEL Yes
Match Local SSEL Yes
Match Local TSEL Yes
Match Local IP Address No
Match Remote AP Title Yes
Match Remote AE Qualifier Yes
Match Remote AP Invoke No
Match Remote AE Invoke No
Match Remote PSEL Yes
Match Remote SSEL Yes
Match Remote TSEL Yes
Match Remote IP Address No
Table 5: Default Addressing Matching
OPC PARAMETERS
Note: Changes to the OPC Parameters form cannot be made while AX-S4 ICCP is running.
Figure 34: ICCP Configuration Utility OPC Parameters form
53
TIME STAMP
Use ICCP Time Stamp - This option enables/disables the use of the ICCP time stamp as the OPC time stamp for any
remote data value. If the remote data value does not have an associated timestamp, the
Transfer_Set_Time_Stamp is used. The Transfer_Set_Time_Stamp specifies the time the TransferReport was
generated at the TASE.2 server.
USER QUALITY
Set OPC User Quality to ICCP Quality - When this option is enabled, the 6 bits of client data value ICCP quality is
assigned to the high 8 bits of OPC quality. This allows an OPC client to analyze ICCP quality without converting OPC
quality to ICCP quality.
Set ICCP Quality to OPC User Quality - When this option is enabled and an OPC client uses the WriteVQT interface,
the 8 bits of OPC user quality are assigned to the ICCP quality for client data values. This option allows the OPC
client to directly set the ICCP quality without the conversion of OPC quality to ICCP quality.
ICCP TO OPC QUALITY MAPPING

These options allow selecting the parts of the ICCP quality to use to convert ICCP quality to OPC quality.
OPC Quality is defined as a WORD (unsigned short integer). The low 8 bits are used to pass standard OPC quality to
an OPC Client. The high 8 bits (user quality) are available for vendor specific use.
ICCP quality is defined as 6 bits, 2 bits for validity, 2 bits for current source, 1 bit for normal value and 1 bit for
timestamp quality.
The following options are available to be checked:
Use Validity - If checked, Validity is mapped to OPC quality. The Validity attribute specifies the validity or quality of
the PointValue data it is associated with. These are based on the source system’s interpretation as follows: VALID
means the Data value is valid. HELD means previous data value has been held over. Interpretation is local.
SUSPECT means the Data value is questionable. Interpretation is local. NOTVALID means the Data value is not
valid.
Use Time Stamp Quality - If checked, TimeStampQuality is mapped to OPC quality. The TimeStampQuality
attribute has the value VALID if the current value of the TimeStamp attribute contains the time stamp of when the
value was last changed, and has the value INVALID at all other times
Use Normal Value - If checked, NormalValue is mapped to OPC quality. The NormalValue attribute reports
whether value of the point is within the normal range.
Use Current Source - If checked, CurrentSource is mapped to OPC quality. The CurrentSource attribute specifies
the current source of the data as follows: TELEMETERED means the data value was received from a telemetered
site. CALCULATED means the data value was calculated based on other data values. ENTERED means the data
value was entered manually. ESTIMATED means the data value was estimated (State Estimator, etc.)
54
DSCONDITIONSDETECTED
Include in DataFlags - The option enables/disables the inclusion of DSConditions detected in the ICCP Client Value
DataFlags item string. It includes the following:
OtherExternalEvent
IntegrityTimeOut
OperatorRequest
ObjectChange
IntervalTimeOut
STATE AND QUALITY

Combine State and Quality - The ICCP specification state data types consist of 8 bits, 2 bits for the state data and
6 bits of quality data. The
AX-S4 ICCP OPC namespace separates the bits into state and 4 quality attributes to make it easier for the user to
handle the data. If this option is enabled the state and quality bits are combined. The OPC client will receive state
data exactly as it is sent/received to/from the remote control center. This may be useful for OPC Historian
applications.
REDUNDANCY PARAMETERS
Notes: Please refer to AX-S4 ICCP Redundancy System for further information regarding the use of the following
parameters.
Changes to the Redundancy Parameters form cannot be made while AX-S4 ICCP is running.
Figure 35: ICCP Configuration Utility Redundancy Parameters form
55
GENERAL
Role -This is the redundancy role of this node. The options include Not Redundant, Redundant Primary, and
Redundant Secondary. Default is Not Redundant.
BACKUP OPC
Local Data Quality - Use this flag to set the quality of all local data values returned from a “Standby” AX-S4 ICCP
node to an OPC client. Options are Good, Uncertain, and Bad. The default is Good.
Remote Data Quality - Use this flag to set the quality of all remote data values returned from a “Standby” AX-S4
ICCP node to an OPC client. Options are Good, Uncertain, and Bad. The default is Good.
Server State Suspended - If checked and the AX-S4 ICCP node is in STANDBY, calls to the OPC Server function
GetStatus will return “SUSPENDED” instead of “RUNNING.”
AUTOMATIC CONFIGURATION SYNCHRONIZATION

Mode - The Automatic Configuration Synchronization feature can be used to keep the ICCP configuration in sync
between the active and standby nodes. Options are:
None - No automatic configuration synchronization takes place between the “Active” and “Standby” AX-S4
ICCP nodes.
Active - Automatic configuration synchronization is sync’d to the Active AX-S4 ICCP. This is the recommended
selection.
Primary - Automatic configuration synchronization is sync’d to the Primary AX-S4 ICCP.
Secondary - Automatic configuration synchronization is sync’d to the Secondary AX-S4 ICCP.
DATA SYNCHRONIZATION
The data synchronization feature can be used to keep the values of the Local and Remote ICCP objects up to date
in the Standby node. All data changes in the Active node are sent to the Standby node when the appropriate data
synchronization mode is selected. This is the level of data synchronization to enable. See Data Synchronization
Issues for more information.
Mode
Local - The “Active” AX-S4 ICCP node sends local object changes to the “Standby” AX-S4 ICCP node. This data
may or may not be current on the standby node depending on the Buffer options below and the stability of
the RPL link.
Local and Remote - The “Active” AX-S4 ICCP node sends local object changes to the “Standby” AX-S4 ICCP
node as well as values received from Remote Control Centers. This data may or may not be current on the
standby node depending on the Buffer options below and the stability of the RPL link.
Remote - The “Active” AX-S4 ICCP node sends data values received from Remote Control Centers. This data
may or may not be current on the standby node depending on the Buffer options below and the stability of
the RPL link.
Pipeline - This is the number of data sync messages that can be sent to the “Standby” node before receiving a
response.
56
Buffer Time - This is the number of milliseconds to accumulate data changes before sending a data sync message
to the “Standby” node.
Buffer Count - This is the maximum number of data changes to accumulate before sending a data sync message to
the “Standby” node.
ASSOCIATION CONNECT TIMEOUT

Enabled - This enables the link connection timeout option.
Timeout - This is the number of milliseconds that the active node is given to establish at least one ICCP Link.
Default is 60000 ms.
RPL CONNECTION
Port - This is the TCP Port number for the connection between the primary AX-S4 ICCP and the secondary AX-S4
ICCP (RPL connection). Default it 5555.
Partner IP - This is the IP Address for the RPL connection. It is only required for the Redundant Primary node.
Seal Mode - The RPL Security Seal system provides an authentication and data validation mechanism, using private
key encryption, CRC data validation, and anti-playback timestamps. There are three types of Seal Modes:
None - This allows RPL to avoid performance penalty in the case of an externally secured environment.
Fallback - This is valid only for Primary mode, allows the primary to automatically switch between SEAL and
NOSEAL modes. This mode is intended to be used when migrating to the SEAL version; the NOSEAL version is
compatible with the previous version of RPL protocol.
All - This requires the use of SEAL mode and is the default mode.
Seal Time Window - This is the maximum allowed clock time differential between clocks on each AX-S4 ICCP node.
If the difference is exceeded the RPL link will become disabled. The default is 30 seconds. Please see
troubleshooting for information on problems with Seal Time Windows.
AX-S4 ICCP defaults to using Seal Mode of ALL. If updating from an AX-S4 ICCP version BEFORE V4.0059
1. Both AXS4 ICCP systems will have to be upgraded before RPL can be reestablished or
2. After upgrading the first redundant AX-S4 ICCP system, Open the redundancy form and set the Seal mode
from ALL to None. Having a Seal Mode of None allows unsealed RPL communication with a legacy AX-S4 ICCP
system.
57
RPL TIMERS
Retry Time - This is the frequency of RPL reconnect attempts in milliseconds.
Startup Time - This is the number of milliseconds the Redundant Secondary node waits, after startup, for the RPL
connection before switching to "Active" mode.
Heartbeat Tx Period - This is the frequency, in milliseconds, of heartbeat transmissions to the partner node.
Switch to Active Delay - This is the number of milliseconds to wait before implementing a manual switchover.
ADDRESSING FORM
Figure 36: ICCP Configuration Utility Addressing form
The following parameters can be configured by clicking within a field and entering the new data. Some fields will
have dropdown boxes from which to make a new selection. If editing in a table, the Esc key can be used to end the
edit and return the original contents to the field. The Basic tab includes AR Name, IP Address, AP Title, AE
Qualifier, and Comment. The Selectors tab includes AR Name, PSEL, SSEL, and TSEL. The All tab includes all the
fields.
Information on addressing for the Remote Control Center is normally obtained from the Critical Energy
Infrastructure Information – Association Information Exchange Form. This can be found in the
C:\ProgramData\SISCO\AX-S4 ICCP\Documentation folder. It is called AIEF_ver3 3_DEWG_011614 - NEW.pdf.
Name - This is the Application Reference Name (AR Name), an ASCII string of up to 64 characters that identifies the
Application Entity (AP Title and AE Qualifier) and Presentation Address information associated with an application.
IP Address - This is the Presentation Address of the application the AR Name is representing. TCP/IP uses a host
name or a dotted decimal IP Address (for example, 204.254.125.148).
58
AP Title - This is the Application Process Title, an Object Identifier assigned by the network naming authority to
represent a particular application process. This parameter is optional, although in ICCP applications it is commonly
used.
AE Qualifier - This is an optional integer value used to qualify the Application Entity. This parameter is optional,
although in ICCP applications it is commonly used.
AP Invoke ID – This is an optional integer value used to qualify the Application Entity. It may be used in some ICCP
applications.
AE Invoke ID – This is an optional integer value used to qualify the Application Entity. It may be used in some ICCP
applications.
PSEL - This is an octet string representing the Presentation Selector. It is used to identify a Presentation SAP. Only
one local AR Name can be configured without a PSEL, SSEL, and TSEL. The maximum PSEL size is 16 octets (32 ASCII
encoded hex digits).
SSEL - This is an octet string representing the Session Selector. It is used to identify a Session SAP. Only one local
AR Name can be configured without a PSEL, SSEL, and TSEL. The maximum SSEL size is 16 octets (32 ASCII encoded
hex digits).
TSEL - This is an octet string representing the Transport Selector. It is used to identify a Transport SAP. Only one
local AR Name can be configured without a PSEL, SSEL, and TSEL. The maximum TSEL size is 32 octets (64 ASCII
encoded hex digits).
Description - This is an optional field for the user to enter a description for the local or remote AR Name. The
maximum length is 255 characters.
LOCAL CONTROL CENTERS FORM
This form is used to provide a snapshot of all configured Local Control Centers. Please note that only one Local
Control Center can be active.
Figure 37: ICCP Configuration Utility Local Control Centers form
59
edit and return the original contents to the field.
Name - This is a unique text string to identify the name of the ICCP Local Control Center.
Max MMS Message Size - This is the maximum number of bytes that can be transferred in a single MMS request.
The default is 32000. This parameter must match for both the Local and Remote Control Centers.
Max Data Sets - This is the maximum number of data sets allowed on each link. The default is 10.
Max Data Set Transfer Sets - This is the maximum number of transfer sets allowed on each link. The default is 10.
Description - This optional field indicates a description for the Local Control Center. The maximum length is 255
characters.
ADD LOCAL CONTROL CENTER

When adding a Local Control Center, the following parameters become available:
Figure 38: ICCP Configuration Utility Add Local Control Centers form
Name - This is a unique text string to identify the name of the ICCP Local Control Center.
Max MMS Message Size - This is the maximum number of bytes that can be transferred in a single MMS request.
The default is 32000. It is recommended to make this size at least 32000 in order to efficiently handle data
transfer.
60
Max Data Set Transfer Sets - This is the maximum number of transfer sets allowed on each link. The default is 10.
Description - This is an optional field for the user to enter a description for the Local Control Center. The maximum
length is 255 characters.
Derive from Remote Control Center - If this box is checked, it allows a Local Control Center to be created from a
Remote Control Center.
Select Remote Control Center - This parameter is available only when Derive from Remote Control Center is
checked. Select a Remote Control Center from which to create the Local Control Center.
RIGHT CLICK LOCAL CONTROL CENTERS OPTIONS

If you right click on the Local Control Centers name in the branch, the following options are shown:
Figure 39: ICCP Configuration Utility Right Click Local Control Centers Options
Add - Brings up the Add Local Control Center form.
Delete - Brings up a form that allows selecting from a list of available local control centers and moving those
names to the right pane for deletion.
Figure 40: ICCP Configuration Utility Delete Local Control Centers form
61
EXPORT LOCAL CONTROL CENTER CONFIGURATION TO XML FILE

The Export File indicates the name of the xml and the path where it will reside. Selecting … will allow saving the
file to another location.
Figure 41: ICCP Configuration Utility Export LCC Configuration to XML
IMPORT LOCAL CONTROL CENTER CONFIGURATION FROM XML FILE

Brings up a form used to import a xml file for a Local Control Center. Once the xml file is selected, if the exact LCC
Name is not known, Get LCC Name can be used to retrieve that information from the XML file.
Figure 42: ICCP Configuration Utility Import LCC Configuration to XML
EXPORT LOCAL CONTROL CENTER CONFIGURATION TO EXCEL
Note: A detailed explaination on how to use Excel to Import and Export from the ICCP Configuration Utility is
found in Excel File Import and Export.
The Export File indicates the name of the xlsx and the path where it will reside. Selecting … will allow saving the
file to another location. In addition to exporting all information to an Excel file, there are options to select only
one type of object to export such as LocalDataValues, LocalDevices, LocalMessages, RemoteDataValues,
62
Figure 43: ICCP Configuration Utility Export LCC Configuration to Excel
IMPORT LOCAL CONTROL CENTER CONFIGURATION FROM EXCEL

Brings up a form used to import a xlsx file for a Local Control Center from a list of all configured Local Control
Centers. Importing the file will save it to the ICCP Configuration Database. In addition to importing all information
from an Excel file, there are options to select only one type of object to import such as LocalDataValues,
LocalDevices, LocalMessages, RemoteDataValues, RemoteDevices, and RemoteMessages.
ADD LOCAL OBJECTS AS SERVER OBJECTS
If this box is checked, then the imported local objects can be added as Server Objects to a Remote Control Center.
Selecting this option, exposes two other fields:
Server Scope - Options are ICC or VCC scope.
Remote CC - Can select a specific Remote Control Center to add to or select <All> to add to all configured Remote
Control Centers.
Figure 44: ICCP Configuration Utility Import LCC Configuration to Excel
63
DATABASE OBJECT COUNTS FOR LOCAL CONTROL CENTER
Clicking on a Local Control Center name such as UtilitySiteA displays statistics on configured objects.
Figure 45: ICCP Configuration Utility Database Object Counts for LCC
Right Click Local Control Center (Name) Options

Right click on a specific Local Control Center name in the branch and the following options are available:
Figure 46: ICCP Configuration Utility LCC Right Click Options
Delete - Deletes the selection Local Control Center. All related Objects will be deleted as well.
Validate - Ensures that the Local Control Center configuration is correct syntactically. It is recommended to
perform this step after Objects are added to a Local Control Center. If Validation does not succeed, the ICCP
Configuration Utility will flag those items in error.
Set as Active LCC - Only one Local Control Center can be active at a time. Selecting this option sets the selected
Local Control Center as the Active LCC.
64
Export to XML File - Brings up a form to export the selected Local Control Center Name to an xml file. The Export
File indicates the name of the xml and the path where it will reside. Selecting … will allow saving the file to
another location.
Import from XML File - Brings up a form used to import a xml file for the Local Control Center. The Import File
indicates the name of the xml and the path where it resides.
Export to Excel - Brings up a form export the selected Local Control Center Name into an Excel file. The Export File
indicates the name of the xlsx and the path where it will reside. Selecting … will allow saving the file to another
location. In addition to exporting all information to an Excel file, there are options to select only one type of object
to export such as LocalDataValues, LocalDevices, LocalMessages, ClientDataValues, ClientDevices, and
ClientMessages.
Note: A detailed explaination on how to use Excel to Import and Export from the ICCP Configuration Utility
is found in Excel File Import and Export.
Import from Excel - Brings up a form used to import a xlsx file for the selected Local Control Center. Importing the
file will save it to the ICCP Configuration Database. In addition to importing all information from an Excel file, there
are options to select only one type of object to import such as LocalDataValues, LocalDevices, LocalMessages,
RemoteDataValues, RemoteDevices, and RemoteMessages.
Add Missing AR Names - After an ICCP configuration import, there can be AR Names referenced in associations
that are not in the IccpCfg database or in SiscoStackCfg.xml. This menu option adds the missing AR Names, which
then must be reviewed and corrected as needed.
LOCAL CONTROL CENTER DATA VALUES

This form displays Local Data Values. The parameters can be configured by clicking within a field and entering the
new data. Some fields will have dropdown boxes from which to make a new selection. If editing in a table, the Esc
key can be used to end the edit and return the original contents to the field.
Figure 47: ICCP Configuration Utility LCC Data Values form
65
Name - This is a unique text string representing the data value name.
Data Type - This is the type of the data value. Chapter 2: Getting Started has a description of all the available ICCP
Data Types.
Normal Source - This is a field required to support AutoQualityFlags. It indicates from where the data is coming.
Possible values are:
Telemetered - The data value is normally received from a telemetered site.
Calculated - The data value is normally calculated based on other data values.
Entered - The data value is normally entered manually.
Estimated - The data value is normally estimated (such as State Estimator).
Normal Min - This is an optional field required to support AutoQualityFlags. It is the smallest value considered
normal for the data value.
Normal Max - This is an optional field required to support AutoQualityFlags. It is the largest value considered
normal for this data value.
Map Info - This is used by the Excel Import/Export tools to map the data value to an OPC Server item for use with
the AX-S4 ICCP OPC Client. It is not editable.
Description - This is an optional field used to enter a description for the data value. The maximum length is 255
characters.
ADD A DATA VALUE

This dialog box is used to add a data value for the Local Control Center. To access this box:
Click on the Add button at the bottom on the panel.
Note: Server data values are not added; they are selected from the list of Local Control Center data values.
This brings up the Add Data Value dialog box.
Figure 48: ICCP Configuration Utility Add Data Value form
66
1. Enter a unique Name. All other fields are optional.

2. Click on the Insert button to add the data value. The dialog box will remain open, allowing you to add other
data values.
3. When finished, click on the OK button to save all added data values and close the dialog box, or click on the
Cancel button to discard all added data values and close the dialog box.
RIGHT CLICK DATAVALUES OPTION

Delete All - Selecting this will delete all Local Data Values.
LOCAL CONTROL CENTER DEVICES

This form displays Local Devices. The parameters can be configured by clicking within a field and entering the new
data. Some fields will have dropdown boxes from which to make a new selection. If editing in a table, the Esc key
can be used to end the edit and return the original contents to the field.
Figure 49: ICCP Configuration Utility LCC Devices form
Name - This is a text string identifying the device name.
Device Type - Indicates the device type. Valid options include Command, Real, or Discrete. Command is a 16-bit
integer, Real is a 32-bit real, and Discrete is a 16-bit integer.
SBO - If Yes, it indicates that this is a “Select-Before-Operate” device. Select-Before-Operate Device objects require
the ICCP client to select the Device object before attempting to operate on it. The server shall check if the Device
object is available and operable, and return a success or failure of the client's select required depending upon the
Device object's state.
67
Check Back ID - This is used for SBO Devices only. This attribute contains a symbolic description of the physical
object being controlled. The data is returned by the system operating the physical object to the system requesting
the operation so that the system requesting the operation can be assured the proper object has been selected.
The Check Back ID is a 16-bit integer.
Select Timeout - This is used for SBO devices only. It indicates the number of seconds the server will wait for an
operate request before clearing the device state.
Tag Enabled - Indicates that this device can be tagged. Tags are usually used to prevent or limit operation of a
device.
Description - This is an optional field used to enter a description for the device. The maximum length is 255
characters.
ADD A DEVICE
Figure 50: ICCP Configuration Utility LCC Add Device form
1. Click on the Add button at the bottom on the panel.

3. Click on the Insert button to add the device. The dialog box will remain open, allowing you to add other
devices.
4. When finished, click on the OK button to save all added devices and close the dialog box, or click on the Cancel
button to discard all added devices and close the dialog box.
5. In the right pane, click on the OK button to save changes and close the dialog box, or the Cancel button to
discard changes and close the dialog box.
RIGHT CLICK DEVICES OPTION

Delete All - Selecting this will delete all Local Devices.
68
LOCAL CONTROL CENTER MESSAGES

This form displays Local Messages. The parameters can be configured by clicking within a field and entering the
new data. Some fields will have dropdown boxes from which to make a new selection. If editing in a table, the Esc
key can be used to end the edit and return the original contents to the field.
Figure 51: ICCP Configuration Utility LCC Messages form
Info Reference - This is a unique integer used to identify the information message. It triggers the processing of the
message by the receiving system because it is found in the first variable of a Block 4 message. For example, if the
Info Reference was 29, the first variable in the report which is the Header would contain number 29 as the first
component.
Max Size (bytes) - Indicates the maximum size of the message.
Description - This is an optional field used to enter a description for the message. The maximum length is 255
characters.
RIGHT CLICK MESSAGES OPTION

Delete All - Selecting this will delete all Local Messages.
69
REMOTE CONTROL CENTERS
Clicking on the Remote Control Center Name brings up a summary form listing all the Remote Control Centers for a
specified Local Control Center. The parameters can be configured by clicking within a field and entering the new
data. Some fields will have dropdown boxes from which to make a new selection. If editing in a table, the Esc key
can be used to end the edit and return the original contents to the field.
Figure 52: ICCP Configuration Utility Remote Control Centers form
Name - This is a unique text string to identify the ICCP Remote Control Center name.
Note: The Remote Control Center name must not be the same as the Local Control Center name.
TASE.2 Version - This indicates the version of TASE.2 being used - options are 1996-08 and 2000-08.
Description - This is an optional field used to enter a description for the Remote Control Center. The maximum
length is 255 characters.
RIGHT CLICK REMOTE CONTROL CENTERS OPTION

Add - Brings up the Add a Remote Control Center form.
Delete - Brings up a form that allows selecting from a list of available remote control centers and moving those
names to the right pane for deletion.
70
Figure 53: ICCP Configuration Utility Delete Remote Control Centers form
ADD A REMOTE CONTROL CENTER

Click on Add when adding a Remote Control Center. The following additional parameters are available:
Figure 54: ICCP Configuration Utility Add Remote Control Center form
Derive from Local Control Center - If this box is checked, it allows a Remote Control Center to be created from a
Local Control Center.
Select Local Control Center - This parameter is available only when Derive from Local Control Center is checked.
Local Control Center name must be selected from which to create the Remote Control Center.
71
Default Scope - This selects a default scope for Data Values created for this Remote Control Center. Select either
ICC or VCC.
Default Client Data Value Access - This selects a default access for Data Values created for this Remote Control
Center. Select either the Read Only or Read/Write radio button.
For each configured Remote Control Center, the following forms must be configured.
DATABASE OBJECT COUNTS FOR REMOTE CONTROL CENTER

Clicking on a Remote Control Center name such as UtilitySiteB displays statistics on configured objects.
Figure 55: ICCP Configuration Utility Database Object Counts for RCC form
RIGHT CLICK REMOTE CONTROL CENTER
Figure 56: ICCP Configuration Utility Right Click on Remote Control Center
Delete - Completely removes the selected Remote Control Center and all related ICCP Objects.
Derive LCC - Allows a Local Control Center to be created from the selected Remote Control Center.
72
Figure 57: ICCP Configuration Utility Derive LCC from RCC form
LOAD INTO AX-S4 ICCP

This loads any changes to the ICCP Configuration made by the ICCP Configuration Utility into AX-S4 ICCP. Changes
that can be loaded are contained in the Local Control Centers branch and below. AX-S4 ICCP must be running in
order to exercise this option.
EXECUTE DATA VALUE DISCOVERY

If Data Value Discover is enabled in the Data Value Discovery form, this allows executing a one-shot discovery of
all objects from the Remote Control Center.
REMOTE CONTROL CENTER ASSOCIATIONS

edit and return the original contents to the field. The Basic tab includes Name, Local AR, Initiate, Retry Delay,
Remote AR, Service Role, and Description. The Remote ARs tab includes Name, and Remote ARs 2 – 4. The
Parameters tab includes Name, Max MMS Message Size, Max Requests Pending, Max Indications Pending, Max
Nesting Level, and Heartbeat. The All tab includes all the fields. AR Detail displays addressing information on a
selected AR Name.
73
BASIC TAB
Figure 58: ICCP Configuration Utility RCC Associations Basic tab
Name - This is a unique name of the link between the local control center and the remote control center. It
identifies the association.
Local AR - This specifies the Local AR Name used for the association. It will be highlighted in red if it is missing, is
configured with an AR Name that does not exist in the database, or has the same selectors as another AR Name
being used as a Local AR for the Control Center.
Initiate - If this parameter is set to Yes, it indicates that the Local Control Center will initiate associations with the
Remote Control Center. If set to No, the association state will go from IDLE to LISTEN when the association is
started.
Retry Delay - If the previous entry, Initiate, is set to Yes, this is the number of seconds to wait before retrying a
timed out association request.
Remote AR - This specifies the remote AR Name to be used for the association. If Initiate is set to Yes, the Local
Control Center will attempt to establish an association to this AR Name. It will be highlighted in red if it is missing
or configured with an AR Name that does not exist in the database. If Initiate is set to No, this AR Name will be
used to match incoming association requests.
Service Role - The Service Role is part of a Bilateral Table Agreement. It indicates the ICCP activity required for the
remote control center - Client, Server, or both Client & Server. Generally, most associations are the default Client
& Server.
Description - This is an optional field used to enter a description for the association. The maximum length is 255
characters.
74
REMOTE ARS TAB
Figure 59: ICCP Configuration Utility RCC Associations Remote ARs tab
Remote AR 2, Remote AR 3, through Remote AR12 - Up to twelve remote AR Names can be selected for an
association. If Initiate is set to Yes, the Local Control Center will attempt to establish an association with the first
Remote AR. This Remote AR is required. When a connection to Remote AR cannot be established, the Local
Control Center will attempt a connection with each successive AR Name (2 - 12). All additional Remote ARs (2 – 12)
are optional. The additional Remote ARs are used for redundant Remote Control Centers. If Initiate is set to No,
these AR Names will be used to match incoming association requests.
TIMERS TAB
Figure 60: ICCP Configuration Utility RCC Associations Timers tab
75
Initiate - If this parameter is set to Yes, it will indicate that the Local Control Center will initiate the association
with this Remote Control Center. Set to No, the association state will go from IDLE to LISTEN when the association
is started.
Initiate Retry Delay - If Initiate is set to Yes, this is the number of seconds to wait before retrying a timed out
Association request. Default is 10 seconds.
Initiate Timeout - After AX-S4 ICCP sends an Initiate Request to a remote AR Name, this is the amount of time in
seconds that AX-S4 ICCP will wait for the Initiate Response or an Abort indication to be returned. When the time
has expired, AX-S4 ICCP will Abort the outstanding connect attempt and wait the designated Initiate Retry Delay
time before reattempting to connect to the remote AR Name.
The Initiate Timeout allows a measure of control over how long the TASE.2 client will wait for a Remote site to
respond with a positive or negative Initiate Response. Default is 30 seconds.
Conclude Timeout - After AX-S4 ICCP sends a Conclude Request to a remote AR Name, this is the amount of time in
seconds that AX-S4 ICCP will wait for the Conclude Response or an Abort indication to be returned. When the time
has expired AX-S4 ICCP will Abort the outstanding conclude attempt. The Conclude Timeout allows a measure of
control over how long the TASE.2 client will wait for a Remote site to respond with a positive or negative Conclude
Response. Default is 30 seconds.
A well behaved ICCP server will respond to a Conclude Response in a timely manner. For those systems that do
not, this timer is used as a means to prevent an Association from being trapped in the Conclude Request state. The
Conclude Timeout is used to free up the association to be reused for a connection to a backup machine at the
remote site.
Heartbeat - This timer, when enabled, will send an MMS Identify request to Remote control centers to ensure a
valid TCP/IP connection. When a communication path is lost, this allows for quicker association failure detection
and recovery. Enabling this feature is recommended for redundant systems because it can speed up failover in
situations where TCP/IP socket level connections would otherwise linger. A value of 0 (the default) disables the
HeartBeat. Any other positive value is the number of seconds between heartbeats.
76
PARAMETERS TAB
Figure 61: ICCP Configuration Utility RCC Associations Parameters Tab
Max MMS Message Size - This is the maximum size of the MMS message size. It cannot exceed the Max MMS
Message Size designated for the Local Control Center.
Max Requests Pending - This is the maximum number of outstanding of ICCP Client Requests. The default is 5.
Max Indications Pending - This is the maximum number of remote requests the ICCP Server will allow. The default
is 5.
Max Nesting Level - This is the suggested maximum data structure nesting level to use. AX-S4 ICCP supports a
maximum of 10 levels of nesting. Each structure or array and each structure or array within a structure or array is
equivalent to one nesting level. The default is 5.
Right Click Associations Options

If you right click on the Associations name in the tree, the following options are available:
Delete All - Deletes All the associations belonging to the specified Remote Control Center.
Summary - Displays the Association Summary form.
77
REMOTE CONTROL CENTER BILATERAL TABLES

Bilateral Tables are the computer representation of the Bilateral Agreement. A Bilateral Agreement is an
agreement between two control centers that includes the data elements to be accessed and the means to access
them. The representation used is a local matter of the ICCP implementation. A copy of the Association
Information Exchange Form is found in the Documentation folder under AX-S4 ICCP.
edit and return the original contents to the field. The Basic tab includes Name, Bilateral Table ID, Active, Local
Domain, Remote Domain, Shortest Interval, and Description. The Block tab includes Blocks 1-9. The Options tab
includes Name, Remote Data Value Validation, Remote Data Value Get Config, and Remote Data Value Exclude
Invalid. The All tab includes all the fields.
BASIC TAB
Figure 62: ICCP Configuration Utility RCC Bilateral Tables Basic tab
Name - This is a unique text string used to identify the Bilateral Table.
Bilateral Table ID - This is the symbolic name (up to 32 characters) of the bilateral table version. This is matched to
the remote systems bilateral table version during the start of an association. If the Bilateral Table ID does not
match between the Local Control Center and the Remote Control Center the association will not be established.
Active - This parameter indicates whether the Bilateral Table should be used to communicate with the Remote
Control Center. Only one Bilateral Table may be active at a time and configuration MUST be reloaded after
changing this parameter.
Local Domain - This is the name of the domain supported by the Local Control Center for use by the remote client.
If the Domain Names do not match between the Local Control Center and the Remote Control Center the
association will not be established.
78
Remote Domain - This is the name of the domain supported by the Remote Control Center for use by the local
client. If the Domain Names do not match between the Local Control Center and the Remote Control Center the
association will not be established.
Shortest Interval - This is the shortest periodic interval (in seconds) allowed for transfer sets. The default is 1
second.
Description - This is an optional field used to enter a description for the Bilateral Table. The maximum length is 255
characters.
BLOCK 1 – BLOCK 9 TAB
Figure 63: ICCP Configuration Utility RCC Bilateral Tables Blocks form
These parameters indicate the CBB (Conformance Building Blocks) to be used when communicating with the
Remote Control Center. These are the ICCP Blocks to be included in the ICCP Server’s Supported Features. AX-S4
ICCP Supports Blocks 1, 2, 3, 4, and 5 ONLY. If the blocks supported does not match between the Local Control
Center and the Remote Control Center the association will not be established. Blocks 6, 7, 8 and 9 are currently
not implemented and cannot be used in AX-S4 ICCP.
RIGHT CLICK BILATERAL TABLES OPTIONS

If you right click on the Bilateral Tables name in the tree, the following options are available:
Delete - Deletes the Bilateral Table information.
79
DATABASE OBJECT COUNTS FOR BILATERAL TABLE

Clicking on a Bilateral Table ID such as BLT1 displays statistics on configured objects for that Remote Control
Center’s Bilateral Table.
Figure 64: ICCP Configuration Utility RCC Database Object Counts for Specific RCC Bilateral Table
DATABASE OBJECT COUNTS FOR SERVER (TO REMOTE)

Clicking on Server (To Remote) name in the branch statistics on configured Server objects for that Remote Control
Center.
Figure 65: ICCP Configuration Utility RCC Database Object Counts for Specific RCC
80
SERVER DATA VALUES
Figure 66: ICCP Configuration Utility RCC Server Database Object Counts for Specific RCC
Name - This is a text string identifying the data value name. It must be a valid Local Control Center data value. It
cannot be edited from this form.
Scope - VCC indicates that the scope of the data value is VMD specific and is global to the Local Control Center. ICC
indicates that the scope of the data value is domain specific and is limited to the domain designated for use by the
Data Type - This is the type of the data value. Editing of this field is restricted to data types that fall within the data
type of the Local Control Center data value that was selected.
Read Only - If set to Yes, this indicates that the TASE.2 client cannot modify the data value. If set to No, the value
can be Read/Write. The default is read only (Yes).
81
SELECT FROM A LIST OF LOCALLY DEFINED DATA VALUES

This screen allows you to select from a list of locally defined data values and add them to the list to be served to
the Remote Control Center.
Figure 67: ICCP Configuration Utility RCC Select Server Values
1. With the mouse, grab the menu scroll bar of the Available Data Values or the Included Data Values and scroll
up or down to view the entire list.
2. To select a data value for the Bilateral Table, double click it in the Available Data Values list or select it and
press >.
3. To remove a data value from the Bilateral Table, double click it in the Included Data Values list or select it and
press <.
4. The Scope button in the lower right hand side selects a default scope for Data Values created for this Remote
Control Center. Select either ICC or VCC.
5. Data Access button in the lower right hand side selects a default access for Data Values created for this
Remote Control Center. Select either Read Only or Read/Write radio button.
6. When finished, click on the OK button to save changes and close the dialog box, or click on the Cancel button
to discard changes and close the dialog box.
RIGHT CLICK DATA VALUES OPTION

Delete All - Deletes all the Server Data Values for that Remote Control Center.
82
SERVER DEVICES
Figure 68: ICCP Configuration Utility RCC Server Devices form
Name - This is a text string identifying the name of the device. It must reference a previously defined Local Control
Center Device. It cannot be edited.
Scope
VCC indicates that the scope of the data value is VMD specific and is global to the Local Control Center. ICC
indicates that the scope of the device is domain specific and is limited to the domain designated for use by the
Device Type - This is the type of the device. It cannot be edited.
Tag Enabled - If set to Yes, this indicates that the device can be tagged.
83
SELECT FROM A LIST OF LOCALLY DEFINED DEVICES

This screen allows selecting from a list of locally defined devices and add them to the list to be served to the
Figure 69: ICCP Configuration Utility RCC Select Server Devices
1. With the mouse, grab the menu scroll bar of the Available Devices or the Included Devices and scroll up or
down to view the entire list.
2. To select a device for the Bilateral Table, double click it in the Available Devices list or select it and press >.
3. To remove a device from the Bilateral Table, double click it in the Included Devices list or select it and press <.
4. The Scope button in the lower right hand side selects a default scope for Data Values created for this Remote
RIGHT CLICK DEVICES OPTION

Delete All - Deletes all the Server Devices for that Remote Control Center.
84
SERVER MESSAGES
Figure 70: ICCP Configuration Utility RCC Server Messages form
Info Reference - This is an integer that uniquely identifies the information message object within the given scope
and must reference a previously defined Local Control Center Message. It triggers the processing of the message
by the receiving system because it is found in the first variable of a Block 4 message. For example, if
InfoReference=29, the first variable in the report, Info_Mess_Header, would contain number 29 as the first
component of the InfoBuffHeader.
Scope - VCC indicates that the scope of the data value is VMD specific and is global to the Local Control Center. ICC
indicates that the scope of the device is domain specific and is limited to the domain designated for use by the
85
SELECT FROM A LIST OF LOCALLY DEFINED MESSAGES

This screen allows you to select from a list of locally defined messages and add them to the list to be served to the
Figure 71: ICCP Configuration Utility RCC Select Server Messages form
1. With the mouse, grab the menu scroll bar of the Available Messages or the Included Messages and scroll up or
down to view the entire list.
2. To select a Message to be served to the Remote Control Center, double click on it in the Available Messages
list or select it and press >.
3. To remove a Message from the list to be served to a Remote Control Center, double click on it in the Included
Message list or select it and press <.
4. The Scope button in the lower right hand side selects a default scope for Messages created for this Remote
RIGHT CLICK MESSAGES OPTION

Delete All - Deletes all the Server Messages for that Remote Control Center.
86
DATABASE OBJECT COUNTS FOR CLIENT (FROM REMOTE)

Clicking on Client (From Remote) name in the branch displays statistics on configured Client objects for that
Figure 72: ICCP Configuration Utility RCC Server Devices form
RIGHT CLICK CLIENT (FROM REMOTE)

Auto Assign Variables to DSTS - Data Values are that either manually entered or Discovered need to be assigned to
Data Sets and then Data Set Transfer Sets. This brings up a form to assign automatically Client Data Values based
on certain criteria.
Figure 73: ICCP Configuration Utility Auto Assign Variables to DSTS
87
Exclude Variables Already in DSTS - If this box is checked, AX-S4 ICCP will exclude any Data Values already
previously configure in a DataSetTransferSet (DSTS). If this box is not checked, then the Data Values are assigned to
the newly created DataSetTransferSets.
Association - This is the association over which the DataSetTransferSets are to be received.
Assign Device Tags – If this box is checked, Device Tags will be included in auto DSTS.
Assign Data Values by Data Type - If this box is checked –one of five options can be selected:
Real - Assigns Real, RealQ, RealQTimeTag and RealExtended Data Values into DataSets and creates
DataSetTransferSets.
Discrete - Assigns Discrete, DiscreteQ, DiscreteQTimeTag, and DiscreteExtended Data Values into DataSets and
creates DataSetTransferSets.
State - Assigns State, StateQ, StateQTimeTag and StateExtended Data Values into DataSets and creates
DataSetTransferSets.
Protection - Assigns all Protection Equipment types to DataSets and creates DataSetTransferSets.
Tag - Assigns all device Tags to DataSets and creates DataSetTransferSets (only available for TASE.2 version
2000-08).
DATASET PARAMETERS
Depending on the data type, the following parameters are displayed, but possible defaults may be different.
Max DSTS PDU Size - Indicates the maximum MMS message size. Note this value is configured before ICCP
association being established and should come from BilateralAgreement with the Remote site. However, it is
possible to misconfigure this field with a higher or lower number than the value actually negotiated when the
association takes place.
Conservative DS Data Size Calculation - If checked, Data Sets with less Data Values will be created for the same
MMS message size. The size calculation has to do with the transfer syntax used to send MMS messages produced
by long form length and indefinite length ASN.1 encodings.
Limit Data Values in DataSets - If checked, the maximum number of Data Values included in a Data Set may be
selected. If not checked, the maximum number of Data Values that will fit into a Data Set per the size calculation
algorithm will be used.
Max DVs per Data Set - This option is only available, if Limit Data Values in Data Sets is checked. It indicates the
maximum number of Data Values per Data Set that will be used.
88
SPECIAL VARIABLES
All ICCP servers have mandatory support for the listed special variables. Because AX-S4 ICCP offers Data Value
attributes based on server support for the special variables it is not possible to unselect these variables from
being added to DataSets.
Transfer Set Name - If checked, it is used to specify the MMS Named Variable Transfer_Set_Name in the
Information Report. The Transfer Set Name contains the name of the Transfer Set Object that generated the
Transfer Report. Transfer Set Name is required when the ICCP Configuration Utility selects AX-S4 ICCP
Configuration Mode. This is the Default Mode.
Transfer Set Time Stamp - If checked, it is used to specify the MMS Named Variable Transfer_Set_Time_Stamp
in the Information Report. The Transfer Set Time Stamp object value contains the GMTBasedSeconds time the
Transfer Report was generated by the ICCP server. The Transfer Set Time Stamp is required when the IccpCfg
Utility is in AX-S4 ICCP Configuration Mode.
DS Conditions Detected - If checked, it is used to specify the MMS Named Variable DSConditions_Detected in
the Information Report. The DS Conditions Detected object specifies the conditions that if they become true,
lead to the generation of the Transfer Report. DS Conditions Detected is required when the ICCP Configuration
Utility selects AX-S4 ICCP Configuration Mode. This is the Default Mode.
Event Code Detected - If checked, it is used to specify the MMS Named Variable Event_Code_Detected in the
Information Report that will contain the Event Code Detected object specifying other external event
conditions that trigger the generation of the Transfer Report.
TRANSFER SET PARAMETERS

Start Time - Indicates the start time for the ICCP server to begin Condition Monitoring. If Start Time is 0, then the
ICCP server will assume it to be its current time and will begin Condition Monitoring immediately. Default is 0.
RBE - If checked, the Report By Exception mechanism will be implemented.
All Changes Reported - For TASE.2 version 2000-08 ICCP only, Clients can create DSTS with RBE and
AllChangesReported. The resulting DSTS report can contain more than one instance of the same data value. No
changes are lost.
Critical - If checked, the Transfer Report is critical, and an acknowledgement from the ICCP Client back to the ICCP
Server is expected.
Block Data - Block Data is available if Block 3 is enabled in the Bilateral Table.
DS CONDITIONS
Interval Time Out - If checked, indicates that the ICCP Server should send a report when the Interval Time
expires.
Integrity Time Out - If checked, indicates that the ICCP Server should send a report of the entire Data Set
when the Integrity Check Time interval expires – only applies when RBE is enabled.
Object Change - If checked, indicates whether the ICCP Server should send a report – only applies when RBE is
enabled.
89
Operator Request - If checked, indicates whether the ICCP Server should send a report when an operator at
the ICCP server control center requests it.
Note: It is possible to configure AX-S4 ICCP to request this DS Condition; however AX-S4 ICCP will only
process the parameter. No current operations are available in the TASE.2 spec to allow a client to
request a transfer set.
External Event - If checked, requests for TransferSet to be sent on an external event – may not be supported
on all servers.
Interval - Allows entering the time interval between ICCP server reports. The Interval starts when the Start
Time occurs. If RBE is NOT checked, then the current state of ALL objects in the DataSet are reported when the
Interval expires. If RBE is checked, then the current state of ONLY THE CHANGED objects in the data set are
reported when the interval expires. If multiple changes occur to the same object during the Interval, then only
the final value is reported. Default is 10 seconds.
Integrity Check - May enter a time value for integrity when Integrity TimeOut and RBE conditions are used.
Default is 30 seconds.
Buffer Time - May enter the time interval for buffering the ObjectChange condition before reporting to the
ICCP Client. The Buffer Time starts when the first ObjectChange condition occurs. If RBE is NOT checked, then
the current states of ALL objects in the DataSet are reported when the Buffer Time expires. If RBE is checked,
then the current state of ONLY THE CHANGED objects in the DataSet are reported when the Buffer Time
expires. If Buffer Time is 0, then a report is generated for each change. If multiple changes occur to the same
object during the Buffer Time, then only the final value is reported. Default is 2 seconds.
TLE - May enter a time value for Time Limit for Execution. This is a time that is primarily relevant to the ICCP
Server. It is the time over which the ICCP Server has to send the DataSet Transfer Report to the ICCP Client. If
the ICCP Server anticipates that it cannot send the DSTS to the ICCP Client within the TLE time, then it will not
generate the report and will discard the data. The default is 60 seconds.
90
CLIENT DATA VALUES
Figure 74: ICCP Configuration Utility RCC Client Data Values form
SHOW ONLY UNASSIGNED DATA VALUES

This is option allows displaying assigned Data Values or unassigned Data Values (those not assigned to Data Set
Transfer Sets). Checking this box is useful to determine why certain Data Values are not showing in a DataSet and
DataSetTransferSet.
Name - This is a unique text string identifying the name of the data value. This field is editable.
Scope - VCC if the scope of the data value is global to the remote control center. ICC if the scope of the data value
is limited to the domain designated for use by the local control center.
Data Type - This is the type of the data value.
Read Only - If set to Yes, this indicates that the ICCP client cannot modify the data value. If set to No, the value can
be Read/Write. The default is read only (Yes).
Description - This is an optional field used to enter a description for the data value. The maximum length is 255
characters.
ADD A DATA VALUE

This dialog box is used to add a data value for the Remote Control Center.
91
Figure 75: ICCP Configuration Utility RCC Add Client Data Value form
1. Click on the appropriate Data Values node in the navigation tree of the left pane.
Note: Server data values are not added; they are selected from the list of Local Control Center data values.
2. Click on the Add button in the right pane to bring up the Add Data Value dialog box.
4. Click on the Insert button to add the data value. The dialog box will remain open, allowing you to add other
data values.
5. When finished, click on the OK button to save all added data values and close the dialog box, or click on the
Cancel button to discard all added data values and close the dialog box.
NEWLY DISCOVERED DATA VALUES

Newly Discovered Data Values can be categorized into four different forms displayed under the Data Values
branch.
New - This form includes newly discovered DataValues. When DataValues are found in this form, the user may
manually accept or exclude the new points. The OK button must pressed before DataValues transition to the
DataValues form when accepted or the Excluded form if excluded
Missing - DataValues appearing in this form are present in the Client’s BilateralTable but not in the Server’s
BilateralTable.
Possible reasons for the mismatch could be case sensitivity problem or an ICC, VCC scope mismatch between the
two sites. The remote control center may have also temporarily removed the visibility of the DataValue. The user
has the option of deleting the values permanently from the client BilateralTable. When mismatched problems have
been addressed and new BilateralAgreeements discovered, DataValues may automatically leave this form.
Mistyped - DataValues found in this form have some issue preventing the GetDataValues service from completing
successfully.
92
Two possible reasons that prevent a DataValue name that is known to the Client from being Read are:
1. The client expects different class (type) of data than the server is returning or
2. The server is returning a Read DataAccess error instead of a value. The form of data the client expects as well
as the form of data the server is returning are both listed in this table.
Excluded - DataValues appearing in this form have been manually excluded from the New Data Values form. They
may be left in this form - this means they will be ignored if found again in the Discovery process or they may be
moved to the DataValues form and used in DataSets etc. The purpose for configuring DataValue(s) in this form is to
identify those DataValues in a Remote Control Center that are being exposed as part of the BilateralAgreement but
the local control center is not interested in or is not capable of accessing.
RIGHT CLICK DATA VALUES (NEW, MISSING, MISTYPED, EXCLUDED)

All of these branches have the same Right Click Options.
Delete All - Deletes all the Remote Control Center’s Client Data Values or a subset of those values (New, Missing,
Mistyped, Excluded).
Save to File - Saves the information on the Remote Control Center’s Client Data Values or a subset of those values
((New, Missing, Mistyped, Excluded) to an ASCII text file. This provides a report of the Name, Scope, and Type of all
Client Data Values. This can be useful to diagnose problems with newly discovered data values.
Figure 76: ICCP Configuration Utility RCC Save Client Data Values to File
CLIENT DEVICES
93
Figure 77: ICCP Configuration Utility RCC Add Client Devices form
Name - This is a unique text string identifying the device.
Scope - VCC if the scope of the device is global to the remote control center. ICC if the scope of the device is
limited to the domain designated for use by the local control center.
Device Type - Valid options are Command, Real, or Discrete.
SBO - If set to Yes, this indicates a Select-Before-Operate (SBO) device. This means that the device must be
selected before any device operations take place.
Check Back ID - This is used for SBO Devices only. This attribute contains a symbolic description of the physical
object being controlled. The data is returned by the system operating the physical object to the system requesting
the operation so that the system requesting the operation can be assured the proper object has been selected.
The Check Back ID is a 16-bit integer.
Tag Enabled - If set to Yes, this indicates tag permission granted to the local client.
Description - This is an optional field used to enter a description for the device. The maximum length is 255
characters.
94
ADD A DEVICE
This dialog box is used to add a device for the Remote Control Center.
Figure 78: ICCP Configuration Utility RCC Add Client Device form
1. Click on the appropriate Devices node in the navigation tree of the left pane.
Note: Server devices are not added; they are selected from the list of Local Control Center devices.
2. Click on the Add button in the right pane to bring up the Add Device dialog box.
devices.
RIGHT CLICK CLIENT DEVICES OPTION

Delete All - Deletes all the Remote Control Center’s Devices.
CLIENT MESSAGES
95
Figure 79: ICCP Configuration Utility RCC Add Client Messages form
Info Reference - This is a unique integer used to identify the information message. It triggers the processing of the
message by the receiving system because it is found in the first variable of a Block 4 message. For example, if the
Info Reference was 29, the first variable in the report which is the Header would contain number 29 as the first
component.
Scope - VCC if the scope of the information message is global to the remote control center. ICC if the scope of the
information message is limited to the domain designated for use by the local control center.
Max Size - This is the maximum number of valid octets (characters) in this message. The default is 500.
the AX-S4 ICCP OPC Client. It is not editable. Use the description field.
Description - This is an optional field used to enter a description for the message. The maximum length is 255
characters.
96
ADD A MESSAGE
This dialog box is used to add a message for the Remote Control Center.
Figure 80: ICCP Configuration Utility RCC Add Client Message form
1. Click on the appropriate Devices node in the navigation tree of the left pane.
Note: Server devices are not added; they are selected from the list of Local Control Center devices.
2. Click on the Add button in the right pane to bring up the Add Device dialog box.
3. Enter a unique Info Reference. All other fields are optional.
devices.
RIGHT CLICK CLIENT MESSAGES OPTION

Delete All - Deletes all the Remote Control Center’s Client Messages.
97
CLIENT DATA SETS

Figure 81: ICCP Configuration Utility RCC Client Data Sets form
Name - This is a unique name identifying the DataSet.
Transfer Set Name - This is used to specify the MMS Named Variable in the Information Report that will contain
the name of the Transfer Set object that generated the Transfer Report. Selecting Yes will include special data
value Transfer_Set_Name in the data set.
Transfer Set Time Stamp - This is used to specify the MMS Named Variable in the Information Report that will
contain the Transfer Set Time Stamp object value that contains the time the Transfer Report was generated.
Selecting Yes will include special data value Transfer_Set_Time_Stamp in the data set.
DS Condition Detected - This is used to specify the MMS Named Variable in the Information Report that will
contain the DSConditions Detected object specifying conditions that became true, triggering the generation of the
Transfer Report. Selecting Yes will include special data value DS_Conditions_Detected in the data set.
Note: AX-S4 ICCP adds the three above special data values to each data set by default.
Event Code Detection - This is used to specify the MMS Named Variable in the Information Report that will contain
the Event Code Detected object specifying other external event condition that became true, triggering the
generation of the Transfer Report. Selecting Yes will include special data value Event_Code_Detected in the data
set.
Note: Event_Code_Detected is not used by AX-S4 ICCP.
98
Description - This is an optional field used to enter a description for the data set. The maximum length is 255
characters.
View - This button is used to view the contents of a selected data set. The screen allows viewing all the values
associated with a selected Data Set. The Data Value Name and Data Type are displayed for each. Prev and Next
buttons allow scrolling through the contents of all the Client Data Sets.
Figure 82: ICCP Configuration Utility RCC Client Data Set Variables form
Change - This button is used to display assigned data values or unassigned data values (those not assigned to Data
Transfer Sets). If the checkbox Show Only Unassigned Variables is selected, only those data values not assigned to
a Data Set are shown.
1. With the mouse, grab the menu scroll bar of the Available Variables or the Included Variable and scroll up or
down to view the entire list. The total number of Available and Included Variables is shown in parenthesis.
2. To select a Variable to be included in the Remote Control Center’s DataSet, double click on it in the Available
Variables list or select it and press >.
3. To remove a Variable to be included in the Remote Control Center’s DataSet, double click on it in the Included
Variables list or select it and press <.
4. The bar in the bottom left corner displays the total message size of the DataSet based on the Max Message
Size.
99
Figure 83: ICCP Configuration Utility RCC Change Client Data SetVariables form
ADD CLIENT DATA SET
Figure 84: ICCP Configuration Utility RCC Add Client Data Set form
Name - This is a unique name identifying the DataSet. This is the only field that is required.
Special Variables are checked by default to be included in the DataSet.
HOW TO ADD A BLOCK 5 OBJECT TO A DATASET

When the Remote Control Center’s TASE.2 Version is set to 2000-08, a Remote Control Centers Device Tag Value
and Reason can be included in a DataSet. There are two ways to add a devices Tags using the ICCP Configuration
Utility:
100
1. Statically – this means click on the Remote Control Center’s Client Data Sets. Then select a DataSet Name by
clicking on the DS name in right pane. Then click on the Change button. A new form will appear that displays
members of a specific DataSet. Device control points are listed in the left pane. Expand the Devices in the left
pane, then highlight the name of the device, then click the > button. This moves the device name to the pane
on the right. Click the OK button on the bottom of the form the save the change.
2. Device Tags can be added to a DataSet by right clicking on Client (From Remote) then Auto Assign Variables
to DSTS. A form named Auto Assign Variables to DSTS will appear. Check the check box in the upper right of
the form named Assign Device Tags. Click the OK button. DataSets and DataSetTransferSets are automatically
generated using this feature. All known Device tags will appear in one of the DataSets. Their names are
viewable from one of the DataSets found in the Client DataSets form.
RIGHT CLICK CLIENT DATASETS OPTION

Delete All - Deletes all the Remote Control Center’s DataSets.
CLIENT DATA SET TRANSFER SETS

edit and return the original contents to the field. The DS Conditions tab includes Interval Time Out, Integrity Time
Out, Object Change, Operator Request, and External Event. The All tab includes all the fields plus TLE.
BASIC TAB
The Basic tab includes Data Set, Association, Start Time, RBE, Critical, Interval, Integrity Check, Buffer Time, and
Description.
Figure 85: ICCP Configuration Utility RCC Client Data Set Transfer Sets Basic Tab
Data Set - This is the name of the data set.
101
Association - This is the name of the association previously defined in the Associations form.
Start Time - This is the time value for the TASE.2 server to begin Condition Monitoring. If Start Time is 0, then the
TASE.2 server will assume it to be its current time and will begin Condition Monitoring immediately. The default is
0.
RBE - This is a Boolean flag controlling the Report By Exception mechanism. The default, Yes, implies that the
changed objects are reported.
Critical - This is a Boolean flag controlling the type of Transfer Report. A setting of Yes means that the Transfer
Report is critical and an acknowledgement from the TASE.2 client back to the TASE.2 server is expected. The
default is No – no acknowledgement is sent.
Interval - This is the time interval between Data Set Transfer reports. The Interval starts when the Start Time
occurs. If RBE is set to No, then the current state of all objects in the data set are reported when the Interval
expires. If RBE is set to Yes, then the current state of only the changed objects in the data set are reported when
the Interval expires.
If multiple changes occur to the same object during the Interval, then only the final value is reported. The default
is 10.
Integrity Check - This is the time value for integrity check when IntegrityTimeOut and RBE conditions are used. The
default is 30.
Buffer Time - This is the time interval for buffering the ObjectChange condition before reporting to the TASE.2
client. The Buffer Time starts when the first ObjectChange condition occurs. If RBE is false, then the current states
of all objects in the Data Set are reported when the Buffer Time expires. If RBE is true, then the current state of
only the changed objects in the Data Set are reported when the Buffer Time expires. If the Buffer Time is zero, then
a report is generated for each change. If multiple changes occur to the same object during the Buffer Time, then
only the final value is reported. The default is 2.
Note: A Buffer Time of 0 can cause AX-S4 ICCP to be flooded with Data Set Transfer Reports and can affect
overall network performance.
Description - This is an optional field used to enter a description for the data set transfer set. The maximum length
is 255 characters.
DS CONDITIONS TAB
The DS Conditions tab includes Interval Time Out, Integrity Time Out, Object Change, Operator Request, and
External Event.
102
Figure 86: ICCP Configuration Utility RCC Client Data Set Transfer Sets DS Conditions Tab
Interval Time Out - This indicates whether or not the TASE.2 server should send a report when the Interval time
expires. The default is No.
Integrity Time Out - This indicates whether or not the TASE.2 server should send a report of the entire Data Set
when the Integrity Check time interval expires. This only applies when RBE is TRUE. The default is Yes.
Object Change - This indicates whether or not the TASE.2 server should send a report when any object in the Data
Set changes. Possible changes include a change of value, status, or quality flags. The default is Yes.
Operator Request - This indicates whether or not the TASE.2 server should send a report when an operator at the
TASE.2 server control center requests it. The default is No.
External Event - This indicates whether or not the TASE.2 server should send a report when any other external
event condition that is not described in the other conditions becomes true. The default is No.
ALL TAB
The All tab includes all the fields plus TLE.
TLE - This is the time value for Time Limit for Execution (in seconds). This is a time that is primarily relevant to the
TASE.2 server. It is the time over which the TASE.2 server has to send the Data Set Transfer Report to the TASE.2
client. If the TASE.2 server anticipates that it cannot send the Data Set Transfer Report to the TASE.2 client within
the TLE time, then it shall not generate the report, and shall discard the data. The default is 60.
RIGHT CLICK CLIENT DATASET TRANSFER SETS OPTION

Delete All - Deletes all the Remote Control Center’s DataSet Transfer Sets.
103
DATA VALUE DISCOVERY

AX-S4 ICCP provides the ability to discover Data Values present in a Remote Control Center (Client). The primary
features implemented are the ability to:
1. Validate Existing Configuration

a. Detect Data Values that are missing or mistyped in the Remote Control Center.
b. Remove misconfigured Data Values from DataSets.
c. Mark misconfigured Data Values in the configuration database for review by the user.
2. Detect New Data Values
a. Detect Data Values in the Remote Control Center that are currently not configured.
b. Add newly detected Data Values to the AX-S4 ICCP configuration database for acceptance by user.
c. Add newly detected Data Values to the runtime configuration, making them immendiately available.
This highly configurable feature provides significant assistance in the area of Client Data Values (Data Values
present in a Remote Control Center). By enabling Discovery, it eliminates all the manual configuration of the
Remote Control Center’s data values. Please note however that some remote system do not support client data
value reads and as a result this feature will cause the connection to be dropped.
Figure 87: ICCP Configuration Utility RCC Client Data Value Discovery form
ENABLE CLIENT DATA VALUE DISCOVERY

This check box is used to enable/disable the overall Discovery functionality, regardless of other
Discovery configuration settings. This means that this box must be checked in order to use any of
the Discovery features.
Note: Most systems will benefit from enabling at least some of the Discovery features unless
Discovery is not supported by the Remote Control Center.
104
GENERAL
Association - Indicates the Association on which the Data Value Discovery is to be performed. There is at most one
single association per Remote Control Center that is used for Discovery. The selected association mode must be
either Client or Client/Server.
Execute - This option tells AX-S4 ICCP when it is to perform Discovery. Note that regardless of this option setting,
the user can always initiate the Discovery process manually by writing an OPC item. Each Remote Control Center
gains a Discover attribute through the OPC interface when the check box Enable Client Value Discovery is checked.
For example, if the current Local Control Center had a Remote Control Center named UtilitySiteB and the Discovery
attribute for this RCC was enabled, the OPC application could write a 1 to the following OPC item string to discover
new Data Values – UtilitySiteB:Discover.
Options are:
User Initiated - Discovery takes place only when the user initiates it using an OPC control item.
First Connection - Discovery is performed the first time a connection is established to the Remote Control
Center after AX-S4 ICCP starts, or after a configuration reload. Subsequent stops and restarts of the link will
not cause Discovery to take place.
Every Connection - Discovery is performed every time a connection is established. This option will always keep
the Local Control Center up-to-date with the server Bilateral Table changes being made and loaded into the
Remote Control Center. Please note that selecting this setting can add to association startup time and CPU
Utilization and should be selected carefully.
Automatically Accept Database Changes - Discovery can optionally change the configuration database – it can
write new Data Values to the configuration database, and mark misconfigured Data Values. By default, all database
changes are made available for user review, but do not become a part of the active configuration until accepted by
the user.
If this option is checked, the database changes will be accepted automatically and will become part of the active
configuration without user intervention. Please note that a fully automated system is recommended but this
feature has the effect of removing the user from the process – please consider the implication carefully before
enabling this option.
Create XML File for Remote Data Values - If this option is checked, AX-S4 ICCP will create an importable XML file
for the Data Values. When the Discovery has completed, a message will appear in the standard log of AX-S4 ICCP
(axs4iccp.log) stated where the XML file was written to:
Example:
XML Update for Remote 'TGMPI1_1 complete. (See C:\ProgramData\SISCO\AX-S4 ICCP \rem_UtilitySiteB.xml)
CONFIGURED CLIENT DATA VALUES

Validate Configured Data Values - AX-S4 ICCP can validate the presence (and optionally) the type of all configured
Data Values. This check box is used to enable/disable this feature, regardless of other settings for Configured Data
Value Validation.
105
Remove Mismatches from Data Sets - If this option is checked, AX-S4 ICCP will remove misconfigured (missing or
mistyped) Data Values from DataSets. In general, ICCP servers will not allow creation of a DataSet containing an
invalid Data Value. This option can be used to help ensure that DataSets can be created and data transfer can take
place. It is recommended to check this feature.
Correct Mismatches in Databases - If this option is checked, AX-S4 ICCP will mark missing and mistyped Data
Values in the ICCP configuration database. The user can then use the ICCP Configuration Utility to examine the
configuration mismatches and accept or reject the proposed changes. It is recommended to check this feature.
Data Type Validation - The following options are available in a drop down box:
None - No validation is done.
Normal - With this recommended setting, AX-S4 ICCP will use the MMS Read service to validate the types.
This option is fast but cannot distinguish between Data Value types of StateQualityTimestamp and
DiscreteQuality.
Detailed - With this alternate setting, AX-S4 ICCP will use the GetVariableAccessAttributes service to validate
the types. This option can take much longer to execute, but can always accurately determine the types as
configured in the server.
NEW CLIENT DATA VALUES

Discover New Data Values - AX-S4 ICCP can detect Data Values in the Remote Control Center that are not
configured, and add these new Data Values to the configuration database and/or the active configuration. This
check box is used to enable/disable this feature regardless of other settings for New Client Data Values. If checked,
AX-S4 ICCP will use the MMS GetNameList service to look for new Data Values.
Add to Active Configuration - If this option is checked, the newly discovered Client Data Values (and their
associated OPC items) will be added to the runtime configuration of AX-S4 ICCP. An OPC Client will be able to
browse newly discovered Data Values after the discovery process is complete. If this option is checked, the Add to
Database option must also be checked.
Add to Database - If this option is checked, the newly discovered Client Data Values will be added to the AX-S4
ICCP configuration database. The user can then use the ICCP Configuration Utility to examine the new Data Values
and accept or reject the proposed changes.
Set Read Only Attribute - If this option is checked, all newly discovered Client Data Values will be Read Only
instead of Read/Write.
Derived Types Using - The following options are available in a drop down box:
Detailed - With this recommended setting, AX-S4 ICCP will use the MMS GetVariableAccessAttributes service
to determine types for newly discovered variables.
Quick - With this alternate setting, AX-S4 ICCP will use the MMS Read service to determine types for newly
discovered variables. This setting has the advantage of being very fast and is more tolerant of non-conformant
implementations. However it is not possible to distinguish between Data Value types StateQualityTimestamp
and DiscreteQuality based on data, so AX-S4 ICCP will assume DiscreteQuality. This means that the user must
review all newly discovered Data Values and verify that the types are correct.
106
AUTO DSTS PARAMETERS

This option allows the user to configure the AX-S4 ICCP Auto-DSTS feature. This feature allows AX-S4 ICCP to
automatically assign remote Data Values into DataSets and create DataSetTransferSets. all at runtime and without
additional configuration. The configuration is the same as creating Data Set Transfer Sets with the static method
without having to recreate these every time a data value is added or removed from the system.
Note that using this recommended feature gives up some control, but does ensure that all Data Values are present
in DataSets. This is especially useful in systems where the Data Value set is not static.
107
CHAPTER 6: BUILDING APPLICATIONS USING OPC
OPC GENERAL CONCEPTS
AX-S4 ICCP, with its OPC interface, can provide applications with easy access to real-time data using a standard
interface. OPC, a standard developed by the OPC Foundation for interfacing Windows-based applications to device
networks, is based upon Microsoft’s COM/DCOM technology for Windows.
Configuring DCOM can be difficult. SISCO is not responsible for DCOM configuration of your system. Please consult
Microsoft support.
With AX-S4 ICCP supporting OPC and ICCP, connectivity can be provided to any OPC enabled application without
custom programming. With OPC, AX-S4 ICCP is the only interface needed to retrieve data from any number of
remote control centers. It will make possible communication between Windows applications and ICCP control
centers as well as other applications over ICCP-based Ethernet networks.
OPC SERVERS
When AX-S4 ICCP is installed, it registers the following OPC Server:
SISCO.AXS4ICCP.3 (SISCO.AXS4ICCP is the non version specific prog id.)
This provides the OPC Custom Interface (the preferred interface for use by HMI packages). The OPCDAAuto.dll is
installed to allow Visual Basic applications to access registered OPC Servers.
OPC ITEM STRINGS
The AX-S4 ICCP OPC interface supports browsing by OPC clients. Using the browsing features is the simplest way to
create OPC Groups and Items. If the OPC Client software does not support browsing, the item strings must be
constructed manually. The following discussion should help in determining the syntax and required content of the
OPC item strings.
OPC GROUP UPDATE RATE
The AX-S4 ICCP OPC Server now supports a group update rate of 0 (event based updates.
108
GENERAL OPC ITEM STRINGS
Figure 88: OPC Test Client
AddRemoteVCC - AddRemoteVCC is a VT_BSTR (string). Write the name of a new remote control center to load
the configuration data from the data base.
DisableAllAssociations - DisableAssociations is a VT_BOOL. Write VARIANT_TRUE to disable all associations for a

given Local Control Center.
LocalControlCenterName - Allows displaying the name of the current local control center.
OpcClientCount - Allows displaying the current number of OPC Clients attached to AX-S4 ICCP. The ICCP
Configuration Utility and the ICCP Monitor are OPC clients.
SaveCurrentSettings - SaveCurrentSettings is a VT_BOOL. Write VARIANT_TRUE to save all window sizes and
locations to the registry.
LOCAL AND REMOTE ITEM STRINGS
All AX-S4 ICCP objects are either a Local Server object or a Remote object. The Local Server objects are further
classified as Data Values, Local Status Information, Information Messages, or Devices. The Remote objects are
Links, Data Values, Transfer Sets, Information Messages, or Devices.
The general form of an OPC Item String for a Local Server object is:
LocalCCName:ObjectType~ObjectName.Attribute
The general form of an OPC Item String for a Remote object is:
RemoteCCName:ObjectType~ObjectName.Attribute
The LocalCCName component is the name of the local control center. The RemoteCCName component is the name
of the remote control center providing the data.
109
The ObjectType can be DataValue, InfoMsg, DeviceSelect, DeviceOperate, DeviceTag, DeviceGetTag, or

DeviceSetTag. The Local Control Center has an additional ObjectType (LocalStatus). The Remote Control Center has
additional ObjectTypes (Link and TransferSet).
The Object name is the configured name of the object in the case of data values, links, and devices. For
information messages the object name is “Ref#” followed by the configured reference number. For Transfer Sets,
the object name is the Data Set name associated with the transfer set. LocalStatus object names are predefined
and listed below.
Many different Attributes are possible depending on the ObjectType and the type of the object. Data Values that
are of type RealQ have different attributes than Data Values of type RealExtended. Remote Data Values that are
part of an active Data Set Transfer Set have additional attributes pertaining to the transfer set. Device attributes
vary depending on the device operation. Different attributes are required to select a device than to operate one.
For Information Messages and Devices, the attributes for the ICCP Server are different than the attributes available
to the ICCP Client. That is, the attributes differ for local objects and remote objects.
The following sample item strings define the available attributes.
Item String Type Value R/W

“Active”
“Inactive”
lccName:LocalStatus~DataSyncStatus VT_BSTR Read Only
“Mismatch”
“Not Enabled”
lccName:LocalStatus~GetIccpConfiguration VT_BOOL True/False Read Write
“Active”
“Inactive”
rccName:DataSyncStatus VT_BSTR Read Only
“Mismatch”
“Not Enabled”
rccName:GetIccpConfiguration VT_BOOL True/False Read Write
Table 6: OPC Sample Items Strings for Available Attributes
QUALITY FLAGS
If enabled, the AX-S4 ICCP server will automatically handle the quality flags associated with a local data value each
time the value is written by an OPC Client. At startup the quality flags are set to:
Validity = INVALID
CurrentSource = Configured Normal Source
NormalValue = NORMAL
TimeStampQuality = VALID if Auto-TimeStamp is enabled
110
When an OPC Client writes the Value attribute of a data value, the quality flags are set:
Validity = VALID
NormalValue = NORMAL If the Value written is within configured range, else ABNORMAL.
ICCP TO OPC QUALITY MAPPING

The OPC Quality of remote data values can optionally be based on ICCP Client Data Value quality flags.
The following registry value HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SISCO\AX-S4

ICCP\CurrentVersion\AXS4ICCP\UseLegacyQualityMappings
This must be set to 1 in order to use the mappings described in the table below. The UseLegacyQualityMappings
default is 1.
Use the ICCP Configuration Utility OPC parameters form to set the ICCP to OPC Quality Mapping. This value is
logically ANDed with the DataFlag item to create a mapping value that is used to determine the OPC quality for the
item as follows:
ICCP ICCP
Quali Old
New ICCP ICCP Norm Timesta
ty OPC
OPC Quality Validity Current Source al mp
Mask Quality
Value Quality
0x00 BAD BAD Any Any Any Any
Normal
0xc0 GOOD no reason GOOD VALID = 0 Any Valid = 0
=0
UNCERTAIN eng. Abnor

0x54 GOOD VALID = 0 Any Valid = 0
units exceeded mal = 1
GOOD with local Not Normal

0xd8 GOOD VALID = 0 Valid = 0
override (TELEMETERED=0) =0
UNCERTAIN No Invalid =
0x40 GOOD VALID = 0 Any Any
reason 1
GOOD with
0xd8 GOOD HELD = 1 Any Any Valid = 0
LocalOverride
UNCERTAIN No Invalid =
0x40 GOOD HELD = 1 Any Any
reason 1
UNCERTAIN No SUSPECT
0x40 GOOD Any Any Any
Reason =2
NOT
0x08 BAD not connected GOOD Any Any Any
VALID = 3
Table 7: ICCP to OPC Quality Mapping
111
ICCP STATE POLARITY

ICCP State bits are mapped to OPC Boolean where 1 is OFF and 2 is ON per tables in clause 8.1 of IEC 60870-6-802.
There is a registry parameter called ICCPStatePolaritySwitch controls the polarity of the mapping globally within
AX-S4 ICCP as follows. The default is 0.
ICCPStatePolarity = 0
When the OPC clients writes a the State value of a Local Data Value as an OPC Boolean, the Boolean value will be
transformed as follows:
OPC Value ICCP State Value

FALSE 1
TRUE 2
An OPC Client reading a State value of a Remote Data Value as an OPC Boolean will see the following OPC values
depending on the value of the ICCP state variable:
ICCP State Value OPC Value OPC Quality

0 Last Known Uncertain
OPC_QUALITY_EGU_EXCEEDED
OPC_LIMIT_LOW
1 FALSE Good
2 TRUE Good
OPC_LIMIT_HIGH
ICCPStatePolarity = 1
When the OPC clients writes a the State value of a Local Data Value as an OPC Boolean the Boolean value will be
transformed as follows:
OPC Value ICCP State Value

FALSE 2
TRUE 1
An OPC Client reading a State value of a Remote Data Value as an OPC Boolean will see the following OPC values
depending on the value of the ICCP state variable:
ICCP State Value OPC Value OPC Quality

OPC_LIMIT_LOW
2 FALSE Good
1 TRUE Good
OPC_LIMIT_HIGH
112
OPC TIMESTAMP FORMAT
For OPC Items with canonical data type of VT_DATE:
If the data is requested as a VT_BSTR (string) the date string passed to the OPC Client will have the format:
YYYY-MM-DDThh:mm:ss.mScZ.
The time is GMT not local.
The 'T' in the date string indicates the text that follows is the time.
The 'Z' in the date string indicates Zulu time (GMT).
The mSc is 3 characters of millisecond resolution.
AX-S4 ICCP REDUNDANCY
The following item strings are available only when redundancy support is enabled. See AX-S4 ICCP Redundancy
System.
Current Mode
Item String: Redundancy:CurrentMode
The current mode of the redundant node. Possible Values:
Active - Performs ICCP communciations.
Standby - Waiting and monitoring Active node communications.
ActiveLocked - Performs ICCP communciations. Automatic failover is locked out. Only manual failover is
allowed.
StandbyLocked - Waiting and monitoring Active node communications. Automatic failover is locked out. Only
manual failover is allowed.
Startup
Redundant communications are starting up.
Data Type: VT_BSTR
Access: Read Only
RPL Status
Item String: Redundancy:RPLStatus
The status of the RPL connection. The RPL is a connection between the active and standby nodes. It allows the
standby node to monitor the active node communications, provides for data and configuration transfer and
failover alerts. Possible Values:
Disabled - The RPL connection is disabled.
Connected - The RPL connection is enabled and connected.
Not Connected - The RPL connection is enabled but not connected.
113
Configuration Sync Status
Item String: Redundancy:ConfigSyncStatus
Data Type: VT_BSTR
Access: Read Only
The RPL connection will keep the configuration of the active and standby nodes synchronized. The item shows the
status of the configuration synchronization. Possible Values:
None - Configuration synchronization is disabled.
Active - Configuration synchronization is enabled.
Primary - The configuration on the Secondary node is synced to the Primary node.
Secondary - The configuration on the Primary node is synced to the Secondary node.
Data Sync Rate
Item String: Redundancy:DataSyncRate
The number of data items sent to the redundant partner per second.
Data Type: VT_I4
Access: Read Only
Heartbeat High Water Rx
Item String: Redundancy:HeartbeatHighWaterRx
The longest time between heartbeats from redundant partner in milliseconds.
Data Type: VT_I4
Access: Read/Write
Heartbeat Transmit Period
Item String: Redundancy:HeartbeatTransmitPeriod

The frequency for sending a heartbeat to the redundant partner in milliseconds.
Data Type: VT_I4
Access: Read/Write
Total ICCP Links
Item String: Redundancy:TotalICCPLinks

The number of ICCP links for all configured remote control centers.
Data Type: VT_I4
Access: Read Only
114
Active ICCP Links
Item String: Redundancy:ActiveICCPLinks

The number of ICCP links with an active state.
Data Type: VT_I4
Access: Read Only
Association Connection Timeout Enabled
Item String: Redundancy:AssociationConnectionTimeoutEnable

True if the Association Connection Timeout feature is enabled.
Data Type: VT_BOOL
Access: Read/Write
AssociationConnectionTimeout
Redundancy:LinkConnectTimeout The number of milliseconds that the active node is given to establish at least
one ICCP Link.
Data Type: VT_I4
Access: Read/Write
ModeSelect
Item String: Redundancy:ModeSelect
Allows manual mode selection. The ‘Default’ option will set the ‘Redundant Primary’ node as the active node and
the ‘Redundant Secondary’ node as the standby node. The ‘Forced’ options will perform the switchover and issue a
ModeLock request.
Possible Values: Active, Standby, Force Active, Force Standby, and Default
Data Type: VT_BSTR
Access: Read/Write
ModeLock
Redundancy:ModeLock Enable/Disable automatic mode switches.
Possible Values: Lock and Unlock
Data Type: VT_BSTR
Access: Read/Write
115
LocalConfigurationMatchStatus
Item String: Redundancy:LocalConfigurationMatchStatus
Indicates the status of data synchronization for local data values. Possible Values:
Not Enabled - Data sync is not enabled for local data values
Active - Data sync is enabled and active.
Mismatch - Data sync is enabled but the configurations do not match between the active and standby nodes.
RemoteConfigurationMatchStatus
Item String: Redundancy:RemoteConfigurationMatchStatus
Indicates the status of data synchronization for remote data values. Possible Values:
Not Enabled - Data sync is not enabled for remote data values.
Active - Data sync is enabled and active.
Mismatch - Data sync is enabled but the configurations do not match between the active and standby nodes.
LOCAL SERVER DATA VALUES
TestLocal:DataValue~DVName.Value
TestLocal:DataValue~DVName.TimeStamp
TestLocal:DataValue~DVName.COV
TestLocal:DataValue~DVName.State
TestLocal:DataValue~DVName.Quality.CurrentSource
TestLocal:DataValue~DVName.Quality.NormalValue
TestLocal:DataValue~DVName.Quality.Validity
TestLocal:DataValue~DVName.Quality.TimeStamp
The quality components can be passed to OPC Clients as short integers or strings. They are defined as follows:
Attribute Value String

CurrentSource 0 TELEMETERED
1 CALCULATED
2 ENTERED
3 ESTIMATED
NormalValue 0 NORMAL
1 ABNORMAL
Validity 0 VALID
1 HELD
2 SUSPECT
3 NOTVALID
Table 8: OPC Client Quality Components
116
LOCAL SERVER MESSAGES
TestLocal:InfoMsg~Ref#1.LocalRef
TestLocal:InfoMsg~Ref#1.Message
TestLocal:InfoMsg~Ref#1.MessageID
TestLocal:InfoMsg~Ref#1.RemoveVCC
TestLocal:InfoMsg~Ref#1.SendMessage
LOCAL SERVER DEVICES
TestLocal:DeviceSelect~DevName.Indication
TestLocal:DeviceSelect~DevName.RemoteVCC
TestLocal:DeviceSelect~DevName. CheckBackID
TestLocal:DeviceSelect~DevName.Status
TestLocal:DeviceSelect~DevName.SendResponse
TestLocal:DeviceOperate~DevName.Indication
TestLocal:DeviceOperate~DevName.RemoteVCC
TestLocal:DeviceOperate~DevName.Value
TestLocal:DeviceOperate~DevName.Status
TestLocal:DeviceOperate~DevName.SendResponse
TestLocal:DeviceTag~DevName.Reason
TestLocal:DeviceTag~DevName.TagVaue
TestLocal:DeviceTag~DevName.RemoteVCC
LOCAL SERVER STATUS INFORMATION
TestLocal:LocalStatus~AXS4DataSetTranRptRecd
TestLocal:LocalStatus~AXS4DataSetTranRptSent
TestLocal:LocalStatus~AXS4DeviceGetTagInd
TestLocal:LocalStatus~AXS4DeviceGetTagReq
TestLocal:LocalStatus~AXS4DeviceOperateInd
TestLocal:LocalStatus~AXS4DeviceOperateReq
TestLocal:LocalStatus~AXS4DeviceSelectInd
TestLocal:LocalStatus~AXS4DeviceSelectReq
TestLocal:LocalStatus~AXS4DeviceSetTagInd
TestLocal:LocalStatus~AXS4DeviceSetTagReq
TestLocal:LocalStatus~AXS4InfoMessagesRecd
TestLocal:LocalStatus~AXS4InfoMessagesSent
TestLocal:LocalStatus~AXS4NumErrors
TestLocal:LocalStatus~AXS4ReadDataValueInd
TestLocal:LocalStatus~AXS4ReadDataValueReq
TestLocal:LocalStatus~AXS4WriteDataValueInd
TestLocal:LocalStatus~AXS4WriteDataValueReq
TestLocal:LocalStatus~CfgFileName
TestLocal:LocalStatus~CfgVCCNames
TestLocal:LocalStatus~Error
TestLocal:LocalStatus~NumActiveLinks
TestLocal:LocalStatus~NumActiveVCC
TestLocal:LocalStatus~NumCfgLinks
TestLocal:LocalStatus~NumCfgVCC
117
REMOTE SERVER GENERAL INFORMATION
TestRemote:AXS4DataSetTranRptRecd
TestRemote:AXS4DataSetTranRptSent
TestRemote:AXS4DeviceGetTagInd
TestRemote:AXS4DeviceGetTagReq
TestRemote:AXS4DeviceOperateInd
TestRemote:AXS4DeviceOperateReq
TestRemote:AXS4DeviceSelectInd
TestRemote:AXS4DeviceSelectReq
TestRemote:AXS4DeviceSetTagInd
TestRemote:AXS4DeviceSetTagReq
TestRemote:AXS4InfoMessagesRecd
TestRemote:AXS4InfoMessagesSent
TestRemote:AXS4NumErrors
TestRemote:AXS4ReadDataValueInd
TestRemote:AXS4ReadDataValueReq
TestRemote:AXS4WriteDataValueInd
TestRemote:AXS4WriteDataValueReq
TestRemote:Bilateral_TableID
TestRemote:ReloadBLT
TestRemote:Supported_Features
TestRemote:TASE2_Version
REMOTE SERVER LINK INFORMATION
TestRemote:Link~LinkName.AXS4DataSetTranRptRecd
TestRemote:Link~LinkName.AXS4DataSetTranRptSent
TestRemote:Link~LinkName.AXS4DeviceGetTagInd
TestRemote:Link~LinkName.AXS4DeviceGetTagReq
TestRemote:Link~LinkName.AXS4DeviceOperateInd
TestRemote:Link~LinkName.AXS4DeviceOperateReq
TestRemote:Link~LinkName.AXS4DeviceSelectInd
TestRemote:Link~LinkName.AXS4DeviceSelectReq
TestRemote:Link~LinkName.AXS4DeviceSetTagInd
TestRemote:Link~LinkName.AXS4DeviceSetTagReq
TestRemote:Link~LinkName.AXS4InfoMessagesRecd
TestRemote:Link~LinkName.AXS4InfoMessagesSent
TestRemote:Link~LinkName.AXS4NumErrors
TestRemote:Link~LinkName.AXS4ReadDataValueInd
TestRemote:Link~LinkName.AXS4ReadDataValueReq
TestRemote:Link~LinkName.AXS4WriteDataValueInd
TestRemote:Link~LinkName.AXS4WriteDataValueReq
TestRemote:Link~LinkName.Enabled
TestRemote:Link~LinkName.State
118
REMOTE SERVER DATA VALUES
TestRemote:DataValue~DVName.Value
TestRemote:DataValue~DVName.TimeStamp
TestRemote:DataValue~DVName.COV
TestRemote:DataValue~DVName.State
TestRemote:DataValue~DVName.Quality.CurrentSource
TestRemote:DataValue~DVName.Quality.NormalValue
TestRemote:DataValue~DVName.Quality.Validity
TestRemote:DataValue~DVName.Quality.TimeStamp
TestRemote:DataValue~DVName.DSConditions_Detected*
TestRemote:DataValue~DVName.Transfer_Set_Time_Stamp*
TestRemote:DataValue~DVName.DataFlags**
Data Type: VT_I4
Data Format: Bit 0 = Quality.TimeStamp

Bit 1 = Quality.NormalValue
Bit 2 = Quality.CurrentSource Lo
Bit 3 = Quality.CurrentSource Hi
Bit 4 = Quality.Validity Lo
Bit 5 = Quality.Validity Hi
Bit 6 through Bit 25 = Unused
Bit 26 = DSConditions.OtherExternalEvent***
Bit 27 = DSConditions.IntegrityTimeOut***
Bit 28 = DSConditions.OperatorRequest***
Bit 29 = DSConditions.ObjectChange***
Bit 30 = DSConditions.IntervalTimeOut***
Bit 31 = unused
*Attribute only available for Data Values involved in active transfer sets.
**Contains the ICCP Quality data and optionally the DSConditions Detected from the Data Set Transfer Report.
***If DSConditions are present.
Integer Values of DSConditions:
IntervalTimout 128
IntegrityTimeout 64
ObjectChange 32
OperatorRequest 16
OtherExternalEvent 8
REMOTE SERVER TRANSFER SETS
TestRemote:TransferSet~DataSetName.Enabled
119
REMOTE SERVER INFORMATION MESSAGES
TestRemote:InfoMsg~Ref#1001.LocalRef
TestRemote:InfoMsg~Ref#1001.Message
TestRemote:InfoMsg~Ref#1001.MessageID
REMOTE SERVER DEVICES
TestRemote:DeviceSelect~DevName.SendRequest
TestRemote:DeviceSelect~DevName.CheckBackID
TestRemote:DeviceSelect~DevName.Status
TestRemote:DeviceOperate~DevName.Value
TestRemote:DeviceOperate~DevName.SendRequest
TestRemote:DeviceOperate~DevName.Status
TestRemote:DeviceGetTag~DevName.SendRequest
TestRemote:DeviceGetTag~DevName.Reason
TestRemote:DeviceGetTag~DevName.TagValue
TestRemote:DeviceGetTag~DevName.Status
TestRemote:DeviceSetTag~DevName.Reason
TestRemote:DeviceSetTag~DevName.TagValue
TestRemote:DeviceSetTag~DevName.SendRequest
TestRemote:DeviceSetTag~DevName.Status
ADD A REMOTE CONTROL CENTER CONFIGURATION
This item string is not associated with a Local or Remote control center. It is used to add a Remote Control Center
configuration. The syntax is as follows:
AddRemoteVCC
Writing this item string with the name of the new Remote Control Center causes the default configuration file
(XML file or DataBase) to be reread and parsed. The new Remote Control Center and its objects are added to AX-S4
ICCP. Any errors associated with this operation appear in the item string LocalName:LocalStatus~Error.
RELOADING A REMOTE CONTROL CENTER BILATERAL TABLE
Each Remote Control Center can have its object set reloaded while AX-S4 ICCP is running by writing the item string
RemoteName:ReloadBLT to the boolean value (such as the number 1). Writing this item string with the value of
TRUE causes the default configuration file (XML file or DataBase) to be reread and parsed. Any change to the
object set associated with the Remote Control Center is reflected in AX-S4 ICCP.
INFORMATION MESSAGE HANDLING
To send a message to a remote ICCP client the OPC client must include:
The LocalRef, Message, MessageID, RemoteVCC, and SendMessage attributes of a Local Server Message in the OPC
Group. The OPC Client must write values to all the attributes, writing the SendMessage attribute last. The
RemoteVCC field is the name of the Remote Control Center to which to send the message. Set the SendMessage
attribute to 1 to send the message.
120
LocalRef
Item String: UtilitySiteA:InfoMsg~Ref#1.LocalRef
This value is agreed upon between the sender and receiver of the message.
Data Type: VT_I4
Access: Read/Write
Message
Item String: UtilitySiteA:InfoMsg~Ref#1.Message
Displays the actual message to send to the Remote Control Center.
Data Type: VT_BSTR
Access: Read/Write
MessageID
Item String: UtilitySiteA:InfoMsg~Ref#1.MessageID
Used to identify different instances of an Information Message object.
Data Type: VT_I4
Access: Read
Remote VCC
Item String: UtilitySiteA:InfoMsg~Ref#1.RemoteVCC
Indicates the Remote Control Center to which to send the message.
Data Type: VT_BSTR
Access: Read
Send Message
Item String: UtilitySiteA:InfoMsg~Ref#1.SendMessage
This attribute must be set to 1 to send an Information Message to the Remote Control Center.
Data Type: VT_BOOL
Access: Read/Write
121
To receive an information message from a remote ICCP server, the OPC client application must monitor the
LocalRef, Message, and MessageID attributes of a Remote Control Center Info Message. The attributes are
updated as data is received from the remote server.
Please refer to the KB article AX-S4 ICCP Sending a Block 4 Message Object for an example of how to use Messages
with AX-S4 ICCP and an OPC Client.
DEVICE HANDLING
To handle incoming Select Device requests the OPC Client application must monitor the Indication, RemoteVCC,
CheckBackID, Status, and SendResponse attributes of a LocalControlCenter device. When a Select Device Request is
received from a remote client, the Indication attribute is changed to 1 and the RemoteVCC attribute is updated
with the name of the remote control center requesting to select the device. The OPC Client application must
respond by writing the CheckBackID, Status, and SendResponse attributes.
Valid Status values are:
0 = Success
1 = Device Does Not Exist
2 = Access Denied
3 = Device Inoperable
4 = Device Temporarily Unavailable
Set the SendResponse attribute to 1 to send the response.
The AX-S4 ICCP server will automatically respond to a Select request in certain situations.
• If the device is already selected, the AX-S4 ICCP server will automatically respond with “Device Temporarily
Unavailable”.
• If no OPC Client is monitoring the SelectDevice and a CheckBackID has been configured the AX-S4 ICCP Server
will automatically respond to the Select Device request.
• If no OPC Client is monitoring the SelectDevice and no CheckBackID is configured, the AX-S4 ICCP server will
respond with “Device Temporarily Unavailable”.
• If an Operate Device request is not received from the remote client who selected the device within the time
specified in the configuration file for select device timeout, the AX-S4 ICCP server will clear the device and
enable selecting.
To handle incoming Operate Device requests the OPC Client application must monitor the Indication, RemoteVCC,
Value, Status, and SendResponse attributes of a LocalControlCenter device. When an Operate Device request is
received from a remote client, the Indication attribute is set to 1, the Value is set to the value received from the
remote client and the RemoteVCC attribute is set to the name of the remote control center requesting to operate
the device. It is the responsibility of the OPC Client application to set the Status, as defined above, and write a 1 to
the SendResponse attribute. The AX-S4 ICCP server will return a Device Temporarily Unavailable status if the
DeviceOperate is not actively monitored by an OPC Client.
The SetTag and GetTag operations for LocalControlCenter devices are handled automatically by the AX-S4 ICCP
server. To monitor tagging activity for a local control center device, include the Reason, TagValue, and RemoteVCC
attribute of a DeviceTag object.
Please refer to the KB article How to Operate a Device Using Sample for an example of how to use Devices with
AX-S4 ICCP.
122
SELECTING A REMOTE DEVICE
The OPC Client application must monitor the SendRequest, CheckBackID, and Status attributes of a
RemoteControlCenter DeviceSelect object. Write a 1 to the SendRequest attribute. The Status and CheckBackID
returned from the remote server will be updated upon receipt.
OPERATING A REMOTE DEVICE
To operate a remote device, the OPC Client application must monitor the SendRequest, Value and Status attributes
of a RemoteControlCenter DeviceOperate object. Write the Value attribute and set the SendRequest attribute to
1. The Status returned from the remote server will be updated upon receipt.
GETTING TAG INFORMATION FROM A REMOTE DEVICE
To get the tag information from remote device, the OPC client application must monitor the SendRequest, Reason,
TagValue, and Status attributes of a RemoteControlCenter DeviceGetTag object. Set the SendRequest attribute to
1. The remaining attributes will be updated upon receipt from the remote server.
SETTING TAG INFORMATION OF A REMOTE DEVICE
To set the tag information of a remote device, the OPC Client application must monitor the SendRequest, Reason,
TagValue, and Status attributes of a RemoteControlCenter DeviceSetTag object. Set the Reason, TagValue, and
SendRequest attributes. The Status will be updated with the server response upon receipt.
AX-S4 ICCP STATISTICS
AX-S4 ICCP tracks certain ICCP events for the entire local ICCP server, for each remote and for each link. All
statistics are made available to an OPC Client as Read Only fields. The item strings used to monitor these statistics
are noted above.
To monitor the local server statistics use item strings similar to the following:
TestLocal:LocalStatus~AXS4DataSetTranRptRecd
To monitor the statistics for a specific Remote Control Center use item strings similar to the following:
TestRemote:AXS4DataSetTranRptRecd
To monitor the statistics for a specific Link, use item strings similar to:
TestRemote:Link~LinkName.AXS4DataSetTranRptRecd
123
The statistic items are defined as:
AXS4DataSetTranRptRecd: Number of Data Set Transfer Reports received.

AXS4DataSetTranRptSent: Number of Data Set Transfer Reports sent.
AXS4DeviceGetTagInd: Number of Get Tag requests received.
AXS4DeviceGetTagReq: Number of Get Tag requests sent.
AXS4DeviceOperateInd: Number of Operate requests received.
AXS4DeviceOperateReq: Number of Operate requests sent.
AXS4DeviceSelectInd: Number of Select requests received.
AXS4DeviceSelectReq: Number of Select requests sent.
AXS4DeviceSetTagInd: Number of Set Tag requests received.
AXS4DeviceSetTagReq: Number of Set Tag requests sent.
AXS4InfoMessagesRecd: Number of Information Messages received.
AXS4InfoMessagesSent: Number of Information Messages sent.
AXS4NumErrors: Number of ICCP errors
AXS4ReadDataValueInd: Number of Read Data Value requests received.
AXS4ReadDataValueReq: Number of Read Data Value requests sent.
AXS4WriteDataValueInd: Number of Write Data Value requests received.
AXS4WriteDataValueReq: Number of Write Data Value requests sent.
The statistics can also be viewed on the AX-S4 ICCP Connection State window.
LOCAL STATUS INFORMATION
AX-S4 ICCP Local Status Information consists of the statistics as mentioned above and some other items that
summarize the state of the local server. All fields are Read Only. The CfgVCCNames item returns an array of strings
containing the names of all the configured Remote Control Centers. The Error item returns a string explaining the
error that occurred.
LOG MASKS
AX-S4 ICCP allows selecting log masks from the OPC Client. Please refer to the Log Control Screen for an
explanation of the individual masks.
Logging.ACSE.Decode
Logging.ACSE.Encode
Logging.ASN1.Decode
Logging.ASN1.Encode
Logging.AX-S4.Flow
Logging.AX-S4.ICCP
Logging.AX-S4.OPC
Logging.AX-S4.OPCData
Logging.MI.Addressing
Logging.MI.Config
Logging.MI.Discovery
Logging.MI.Flow
Logging.MMS.Client
Logging.MMS.Server
Logging.MVL.Flow
Logging.MVL.ACSE
Logging.MVL.ACSEData
124
Logging.Redundancy.IrControl
Logging.Redundancy.IrData
Logging.Redundancy.IrFlow
Logging.Redundancy.RplFlow
LoggingSocket.Flow
LoggingSocket.Receive
LoggingSocket.Transmit
Logging.Sx.Decode
Logging.Sx.Flow
Logging.Security.SecFlow
Logging.Security.SecData
Logging.Security.SSleFlow
Logging.Security.SsleData
Logging.Security.Decode
Logging.Security.Encode
Logging.Ssc.Flow
ERROR HANDLING
Some errors can occur which are not fatal to the ICCP Client or the ICCP Server. These errors are stored and passed
to an OPC Client that is monitoring the “TestLocal:LocalStatus~Error” item string.
Due to the nature of OPC and the requirement that an OPC Server only supply updates to an OPC Client at
predefined intervals, the ICCP errors that occur are queued up and passed to the OPC Client one at a time when
the OPC group timer expires. The OPC time stamp indicates when the error occurred. No intervention is required
by the OPC Client. However, in some cases, configuration changes may correct the error condition.
The error string passed to the OPC Client has the following form:
remoteName:linkName~domainName/objectName.errorText
The “domainName/” is optional.
The following “errorText” strings may be reported:
• CreatingDataSetError – Unknown variable

• CreatingDataSetError – No READ permission
• CreatingDataSetError – Read variable failed
• ReadRequestError – FAIL
• ReadRequestError – Bilateral Table mismatch on ASN.1 value and type
• Critical NACK Received
• Critical Data not arrived
• Critical Data Time Out
• Unable to STOP Remote*
• Unable to Reload configuration*
• Unable to ReDefine Remote*
125
• Unable to load configuration**

• Supported Features Read Failure – Association Denied***
• Supported Features Mismatch – Association Denied***
• ICCP Version Read Failure – Association Denied***
• Bilateral Table Id Mismatch – Association Denied***
* Errors that occur when reloading configuration for a remote. No link name is present and the object
name = ReloadBLT.
**Errors that occur when adding a remote configuration. No link name is present and the object name =
AddRemote.
***Error string does not contain an object name.
TEST APPLICATIONS
The AX-S4 ICCP product CD contains two test applications that will assist in both learning AX-S4 ICCP and testing
your OPC Client application. OPCTestClient.exe is a sample OPC Client application that will allow you to connect to
AX-S4 ICCP, create groups, and add and remove items. IccpLiteTest.exe is a sample ICCP Client/Server. This
application is located in \<ApplicationData>\SISCO\AX-S4 ICCP\ICCPLiteTestApplication. The details for using
this executable are in ICCP LiteTest Sample Program.PDF in the \<ApplicationData>\AXS4ICCP\Documentation
directory.
126
CHAPTER 7: REMOTE CONTROL CENTER IDENTIFICATION AND ASSOCIATION

MATCHING
The AX-S4 ICCP configuration process includes defining Associations. These are used to enable ICCP connections to
be established with RCCs (Remote Control Centers). The Association configuration includes the local network
address (using a local AR Name) and one or more remote network addresses (using a remote AR Name).
Associations can be Calling (AX-S4 ICCP sends the initiate request) or Called (the Remote Control Center sends the
initiate request). The following applies to Called associations only.
When an initiate indication is received, AX-S4 ICCP uses the received addressing information to determine with
which configured Association the connection should be matched.
The addressing information available for use in this matching is as follows:
AP Title (optional)
AE Qualifier (optional)
AP Invoke ID (optional)
AE Invoke ID (optional)
Presentation Selector (PSEL)
Session Selector (SSEL)
Transport Selector (TSEL)
Network Address (IP Address)
The ICCP protocol specification (IEC 870-6-503) is not definitive regarding the addressing elements to be used in
identifying a Remote Control Center, but does indicate that the AE Title is the preferred identifier. However, the
specification also notes that an AE Title is bound to a single Presentation Address (which includes the Selectors),
and so either the Presentation Address or the AE Title can be used for Remote Control Center identification. This
means that it is within the letter of the specification to not support the use of AE Titles in addressing.
AX-S4 ICCP MATCHING ALGORITHM
Some ICCP implementations and systems make use of Selector based address differentiation and do not use the AE
Title addressing elements. Because of this, AX-S4 ICCP is designed to recognize this addressing approach and work
correctly in this environment. Meaning that the default settings for AX-S4 ICCP will allow recognition of Remote
Control Centers by a combination of AE Title and the Selectors.
127
Note that both the local (called) and remote (calling) addresses are used in the matching algorithm, as described as
follows:
For Each Configured Remote

{
For Each Configured Association
{
If the Association is: Called, Idle, and Enabled
{
If the Called address matches the Local AR Name address
{
For Each configured Remote AR Name for the Association
{
If the Calling address matches the Remote AR Name
{
If best match so far, the Initiate Indication is matched to the configured Association
}
}
}
}
}
}
MATCHING CRITERIA
The criteria for declaring that an address matches the configured address (AR Name) for an Association is specified
by a set of control parameters. These parameters provide support for a variety of address resolution schemes, and
will help ensure accurate and reliable mapping of incoming connections to configured Associations. Note that
these control parameters apply to all Associations and addresses, and so the requirements for all remotes must be
considered.
The default mapping control parameter values will be appropriate for most installations, where the set remotes
make use of both AE Title (an AE Title is a combination of both the AP Title and AE Qualifier) and Selector based
addressing. With this configuration, we can summarize the address mapping as follows:
Local Address/AR Name
• AE Titles are ignored.

• Selectors (PSEL, SSEL, TSEL) must match.
• Network Address is ignored.
Remote Address/AR Name
• AE Title must match

• AP Title and AE Qualifier only (Invoke IDs ignored)
• All AE Title elements configured at AX-S4 ICCP must be received.
• AE elements received but not configured at AX-S4 ICCP are ignored.
• Selectors (PSEL, SSEL, TSEL) must match.
• Network Address is ignored.
128
CHAPTER 8: AX-S4 ICCP REDUNDANCY SYSTEM
The following chapter will describe the functionality and architecture of the AX-S4 ICCP redundancy system. This
system allows two AX-S4 ICCP nodes to be deployed in redundant configurations, improving system availability.
REDUNDANCY SYSTEM FEATURES

• When an AX-S4 ICCP node is configured as a redundant node, a number of OPC Items are made visible. These
items can be used to monitor and control the redundancy subsystem. See AX-S4 ICCP OPC Item Availability for
item paths and descriptions.
• Automatic switchovers can take place due to heartbeat timeout when the Active node terminates normally, or
optionally when the Active node is unable to establish any active ICCP Links in a configurable period of time.
• Either node can initiate a manual Active/Standby mode switch. This can be done using the OPC server
interface. The ICCP Monitor or any OPC client application can be used for this purpose.
• There is no automatic return to the default mode. If the Primary fails and the Secondary becomes active, the
Secondary will then remain Active regardless of whether the Primary becomes available again. Of course theI
CCP Monitor or another OPC client application can manually cause the transition back to secondary using the
OPC interface.
• Both nodes send heartbeat messages to the partner node. These heartbeat messages contain node state
information, which is used as input information in the switchover control algorithm.
• The Active node will optionally send Data Value sync information to the Standby node. This can consist of local
data values or both local and remote data values, and serves to keep the Standby’s data in sync with the
Active.
• The redundancy control subsystem supports the AX-S4 ICCP on-line reconfiguration features. The procedures
for performing on-line reconfiguration are discussed further on in this chapter.
• The mode can be locked so that mode switches are disabled. This can be done using the OPC interface. The
ICCP Monitor or any OPC client application can be used for this purpose.
• The AX-S4 ICCP redundancy system is designed to integrate smoothly with commercially available OPC
redundancy brokers.
REDUNDANCY DEFINITIONS
PRIMARY NODE
One of two nodes in a redundant pair. This role is selected using the Redundancy form of the ICCP Configuration
Utility. The Primary node is responsible for initiating the Redundancy Port Link (RPL) connection. Otherwise, it is
functionally the same as the Secondary. A Primary can be in Active or Standby mode.
SECONDARY NODE
One of two nodes in a redundant pair; the role is selected using the Redundancy form of the ICCP Configuration
Utility. The Secondary node listens for RPL connections. Otherwise, it is functionally the same as the Primary. A
Secondary can be in Active or Standby mode.
129
ACTIVE MODE
A node in the Active mode has all ICCP associations enabled. The Active node can establish ICCP associations with
remote ICCP nodes and perform ICCP client and server activities.
STANDBY MODE
A node in the Standby mode has all ICCP associations disabled. The Standby node does not communicate with ICCP
remotes, but rather monitors the state of the Active node. In the case of Active node failure (or other conditions),
the Standby node will become Active.
REDUNDANCY PORT LINK (RPL)

The Redundancy Port Link (RPL) is the communications channel between the Primary and Secondary. Heartbeat,
Data Synchronization, Configuration Synchronization, and other redundancy control messages are exchanged using
RPL. This link makes use of a dedicated TCP port.
ICCP CONFIGURATION UTILITY (ICCPCFG)

This is the AX-S4 ICCP Configuration Utility. This application is used to configure the redundancy features of AX-S4
ICCP. Note that AX-S4 ICCP must be restarted for redundancy control changes to take effect.
130
REDUNDANT SYSTEM BLOCK DIAGRAM
OPC Client OPC Client

Application Application
ICCP ICCP Monitor

Monitor
AX-S4 ICCP: Primary Node AX-S4 ICCP: Secondary Node
ICCP Links
ICCP Links Enabled when
Enabled when Secondary is
Primary is RPL Protocol: Heartbeat/Control/Data
Active
Active
ICCP Remote ICCP Remote ICCP Remote
Figure 89: Elements of a redundant AX-S4 ICCP system
AX-S4 ICCP OPC ITEM AVAILABILITY
REDUNDANCY ITEMS
The set of OPC items related to Redundancy are available only when the node is configured to be either a
“Redundant Primary” or “Redundant Secondary”. If the node is “Not Redundant”, these items will not be available.
ACTIVE NODE
When a node is in the Active node, all OPC items can be accessed normally and will have values and qualities as
though the node is not part of a redundant pair.
131
STANDBY NODE
When a node is in the Standby mode, all OPC items for ICCP Remotes will have a “Bad” quality because the node is
not receiving the values from the Remote.
Local OPC items are available and a OPC client can continue to update the values regardless of the mode. This can
be useful in a deployment configuration with redundant OPC clients, but not for deployment configurations using
an OPC redundancy broker. Deployment configuration options are discussed further in this chapter.
LOCAL ICCP DATA VALUE QUALITY DURING SWITCHOVER
When a node first switches from Standby to Active, the quality and value of the ICCP Data Values being sourced
may “bump”as the newly Active node acquires new values from the OPC Client. That is, if the Standby’s copy of the
local data values is not kept up to date, remote nodes may receive data that is either old or invalid.
This sourced data “bump” can be minimized by using one of the following techniques:
1. Make use of the AX-S4 ICCP redundancy system Data Synchronization facilities for keeping the Standby
data values warm. Select the Local and Remote or Local mode.
2. Ensure that the OPC Client will attach to the appropriate DataSource and update the local data values in
the Standby node. Note that this option may not be possible in some redundant system deployment
scenarios, such as when an OPC redundancy broker is used. See the Deployment Options below for more
information.
REMOTE OPC ITEM VALUE QUALITY DURING SWITCHOVER
When a node first switches from Standby to Active, the quality of remotely sourced OPC Item values will be BAD.
As the newly Active node establishes associations with remote ICCP nodes and acquires values the quality of these
items will transition to GOOD.
DEPLOYMENT OPTIONS
AX-S4 ICCP can be deployed in a variety of redundant configurations, each with it benefits and shortcomings. Two
common deployment options are discussed below.
132
DEPLOYMENT OPTION 1: INTEGRATE WITH REDUNDANCY BROKER

The figure on the following page shows an AX-S4 ICCP redundant system integrated with an OPC redundancy
broker. This configuration allows a single OPC client application to make use of an enhanced availability ICCP
interface with no additional programming in the OPC client application. The OPC client is unaware that it is making
use of a redundant OPC server.
OPC Client
Application
OPC Server Interface
OPC Redundancy
Broker(ORB)
OPC Client Interface
OPC
OPC Server Interface OPC Server Interface
ICCPClient/Server RPL Interface RPL Interface ICCP Client/Server
RPL Protocol: Heartbeat/Control/Data
Figure 90: AX-S4 ICCP redundant system integrated with an OPC redundancy broker
133
DEPLOYMENT OPTION 2: REDUNDANT OPC CLIENT APPLICATIONS

Figure below shows an AX-S4 ICCP redundant system deployed with redundant OPC Client applications. This
configuration enables deployment of two independent OPC Clients using a single set of ICCP associations. Note
that the OPC client applications will need to be aware of redundant system issues and will likely require additional
application logic in order to interact with an OPC Server that may be in Standby mode. Data synchronization may
or may not be appropriate for these types of deployments depending on design details.
Local ICCP Value Source
Remote Values Local Values Local Values Remote Values

Received Updated Updated Received
Internal Interface Internal Interface

OPC Client Control OPC Client
Application A Application B
OPC Interface
OPC Interface
OPC Server Interface OPC Server Interface
ICCP Client/Server RPL Interface RPL Interface ICCP Client/Server
RPL Protocol: Heartbeat/Control/Data
Figure 91: AX-S4 ICCP redundant system deployed with redundant OPC Client applications
134
REDUNDANT AX-S4 ICCP CONFIGURATION ISSUES
The Primary and Secondary nodes need to be configured to use identical ICCP configurations (such as Local
objects, Bilateral tables). This is particularly important when using an OPC redundancy broker configuration, so
that the available OPC item set remains consistent. That is, the OPC items that are in use by the OPC Client should
be available in both nodes. If the available OPC item set is not the same for the Primary and Secondary nodes,
failover situations can result in undesirable OPC client behavior.
AX-S4 ICCP makes use of the ICCP Configuration Utility for ICCP object configuration as well as network addressing.
The ICCP configuration information is stored in a Microsoft Access Database on each AX-S4 ICCP node
(IccpCfg.mdb). Network addressing information is always read from the SISCO stack configuration file
(siscostackcfg.xml). ICCP configuration and Network addressing are loosely coupled using AR Names. This means
that the ICCP references AR Names (for ICCP associations) that must be present in the SISCO stack configuration
database. Thus, both nodes can use the same IccpCfg database.
AX-S4 ICCP can be configured to read the configuration directly from the database or from an XML encoded
configuration file. These can exported from the database using the ICCP Configuration Utility.
BASIC AX-S4 ICCP REDUNDANT CONFIGURATION PROCESS

1. Work with Primary Node (for example UtilitySiteA) using the ICCP Configuration Utility to perform all required
configuration including ICCP objects and network addressing.
2. Test the configuration on the Primary Node to ensure that the information is correct. Make sure the ICCP
association is working.
3. When ready to bring the Secondary Node on-line (or up to date), transfer the ICCP configuration from node A
to node B.
a. If the direct database load option is selected, this will typically mean transferring (copying) the ICCP
configuration database (IccpCfg.mdb) from the Primary Node to the Secondary Node.
b. If the XML load option is selected, this will mean transferring the XML configuration file from node A
to node B, then importing it.
Both cases entail file transfers from node A to node B. The tools to be used for accomplishing the required
configuration file transfers is outside the scope of the AX-S4 ICCP Redundancy System.
4. Working at the Secondary Node with the updated configuration, verify that all referenced Local and Remote
AR Names are present and correct. The ICCP Configuration Utility Association Summary feature will be helpful
in identifying problem areas.
5. Test the configuration on the Secondary Node using the manual switchover features as appropriate
(transitioning from Active to Standby and back again).
If these procedures are used, both the Primary and Secondary node will then have complete and correct copies of
all configuration information. Note that it is not necessary that the Network configurations match (addresses), but
that the AR Names are present. This flexibility can be useful in configuring network redundancy, but care must be
taken to ensure that both nodes address the correct Remotes.
135
ON-LINE AX-S4 ICCP RECONFIGURATION
The basic configuration procedures apply to on-line configuration. The redundancy subsystem provides the tools
for updating both nodes smoothly. When a node has a configuration change, the partner is notified of the change
and the configurations are compared and the data sync system is updated as appropriate.
Of course, the issue of OPC Item availability must be considered during the update process, especially when the
OPC redundancy deployment configuration is being used. In this case, only OPC items that are present in both
node configurations can be relied on in case of a failover. For this reason, it is advisable to update both nodes to
the same ICCP configuration in a timely manner.
DATA SYNCHRONIZATION ISSUES
The data synchronization feature can be used to keep the values of the Local and Remote ICCP objects up to date
in the Standby node. All data changes in the Active node are sent to the Standby node when the appropriate data
synchronization mode is selected.
The AX-S4 ICCP redundancy subsystem makes use of CRCs over the ICCP configuration to ensure that data
synchronization can take place correctly and safely. These configuration CRCs are calculated at AX-S4 ICCP startup
and when the configuration is changed on either node. The Local objects and each Remote have independent
configuration CRCs.
When the configuration CRCs are received, data synchronization can take place only within scopes with matching
configuration CRCs. Local and each Remote are managed separately. This means that local configurations must
match for local data sync and each remote configuration must match for that remote to be able to perform data
synchronization. Within the matching scopes, the Standby will request initial data from the Active node, and the
Active node will send all changed data to the Standby.
CONFIGURATION SYNCHRONIZATION
Installations making use of the AX-S4 ICCP redundancy features typically needed to have both systems running
identical configurations, so that switchovers are relatively transparent and Data Value synchronization can take
place. The table below describes the configuration elements that AX-S4 ICCP uses, where they are stored, and
whether they will be handled by the initial implementation of the sync system.
Configuration Element Location CRC? Sync’d?

AX-S4 ICCP
General (such as Configuration source, Auto param) IccpCfg Database No No
Remote Identification parameters IccpCfg Database No No
OPC Parameters (Timestamp, quality handling) IccpCfg Database No No
Redundancy (Role, IP addresses, options) Registry No No
Logging Registry No No
Network Addressing
Local AR Names siscostackcfg.xml No No
Remote AR Names siscostackcfg.xml No No
Security – General
Enable Security siscostackcfg.xml No No
Certificate ID’s siscostackcfg.xml No No
SSL Options (Ciphers, rekey control, etc.) siscostackcfg.xml No No
136
Configuration Element Location CRC? Sync’d?

Local AR Security siscostackcfg.xml No No
Remote AR Security siscostackcfg.xml No No
SNAP parameters siscostackcfg.xml No No
Security – System
Local Certificates Windows Certificate Store No No
Certificate Revocation Lists Windows Certificate Store No No
LocalControlCenter – General
MaxDsTs IccpCfg Database No Yes
MaxDataSets IccpCfg Database No Yes
MaxMmsMsgSize IccpCfg Database No Yes
Local Control Center - ICCP Objects
Local Data Values: Names IccpCfg Database Yes Yes
Local Data Values: Type, Normal Source IccpCfg Database No Yes
Local Devices: Names, SBO, Check back ID, Taggable, Tag IccpCfg Database Yes Yes
Enabled, Tag Value, Tag Reason
Local Devices: Type IccpCfg Database No Yes
Local Devices: Timeout IccpCfg Database No Yes
Local Messages IccpCfg Database No Yes
Remote Control Centers – General
TASE.2 Version IccpCfg Database No Yes
Bilateral Table Name IccpCfg Database No Yes
Bilateral Table Id IccpCfg Database No Yes
Local/Remote Domain Names IccpCfg Database No Yes
Shortest Interval IccpCfg Database No Yes
Supported Blocks IccpCfg Database No Yes
Remote Control Center – Associations
Local, Remote AR Names IccpCfg Database No Yes
Association parameters: Role, Retry, Heartbeat, Timeouts IccpCfg Database No Yes
Service Role IccpCfg Database No Yes
MMS Parameters: Message Size, Req.Ind Pending IccpCfg Database No Yes
Remote Control Center – ICCP Objects
Server Data Values: Name, Scope, Type IccpCfg Database Yes Yes
Server Data Values: Read Only IccpCfg Database No Yes
Server Devices: Name, Scope, Type, Tag Enable, Tag Value, IccpCfg Database Yes Yes
Tag Reason
Server Messages IccpCfg Database No Yes
Client Data Values: Name, Scope, Type IccpCfg Database Yes Yes
Client Data Values: Read Only IccpCfg Database No Yes
Client Data Sets IccpCfg Database No Yes
Client DSTS IccpCfg Database No Yes
Discovery/Validation Options IccpCfg Database No Yes
Auto-DSTS Options IccpCfg Database No Yes
Client Devices: Name, Scope, Type, SBO, CheckBack, Tag IccpCfg Database Yes Yes
Client Messages IccpCfg Database No Yes
Table 9: Configuration Elements Used in Synchronization
137
Making synchronizing more difficult is the availability of the Discovery feature in AX-S4 ICCP. When a redundant
pair is setup to use automatic discovery of new data values, it is possible to have the configurations go out of sync
without user action. This prevents remote Data Value data synchronization from taking place. This can occur with
the new discovery system when the Update Runtime Configuration == Add New Data Values or when Update ICCP
Configuration Database == Automatically Accept Updates
In order to keep configurations in sync, administrators currently have to manually transfer the configuration files
from one node to the other using some external means then manually apply the new configuration to the second
system. This typically involves using the ICCP Configuration tool to export the configuration from one node and
import at the other.
The AX-S4 ICCP Configuration Synchronization subsystem is designed to assist in keeping the redundant pair
configurations in sync.
Note: Configuration synchronization requires use of a single bilateral table in both systems.
SISCO recommends two approaches (Policies) for Configuration Synchronization. While other approaches are
possible, the potential for problems is much greater. SISCO does not support any approaches other than the two
recommended Policies.
POLICY 1: ADMINISTER APPROVED CONFIGURATION CHANGES

1. Client Data Value Configuration
Differences between the current set of configured Client Data Values and that which is exposed by the
remote control center will be discovered by AX-S4 ICCP and written into the configuration database for
review. This will include new, deleted, and changed data values.
No changes will be put into effect until the administrator uses the ICCP Configuration Utility to review and
either accept or reject them, then the remote configuration can be reloaded .
2. Configuration Synchronization
Primary/Secondary node configuration synchronization may be initiated manually in order to pull
(manually force) the configuration from one node to the other over the RPL connection.
Automatic configuration synchronization is disabled, so that no changes to configuration are made

without administrator action.
3. The following settings should be used on the forms indicated in the table:
Discovery Options Setting Notes
Enable Discovery On Discovery should almost always be enabled, because it is the

mechanism used to perform configured Data Value validation.
Execute (User Initiated, First Every This setting should be used assuming there is a single Client Association
Connection, Every Connection) Connection to the remote; otherwise, it should be set to User Initiated. Note that
there is some startup overhead for performing Discovery on every
connection, but this setting provides the best configuration
maintenance results.
Automatically Accept Database Off This setting ensures that the administrator reviews all changes before
Changes they are put into effect.
138
Configured Data Values
Validate Configured Data Values On These settings allow configuration mismatches to be tolerated, so that
mis-configured Client Data Values will not prevent a DataSet from being
Remove Mismatches from On created.
DataSets
Correct Mismatches in Database On This setting allows AX-S4 ICCP to markup the configuration database to
show what configuration mismatches are found. These markups do not
affect operation until the user accepts or rejects the changes.
Data Type Validation (Normal, Normal This setting verifies that the Client Data Values are accessible and
Detailed) provides reasonable confidence on data types. Detailed validation
provides more positive type validation but is much slower.
New Data Values
Discover New Data Values On This setting allows AX-S4 ICCP to markup the configuration database to
Add to Active Configuration Off This setting ensures that the administrator reviews all changes before
they are put into effect.
Add to Database On This setting allows AX-S4 ICCP to markup the configuration database to
Set Read Only Attribute On Depends on the remote implementation, but writing data values is
somewhat unusual.
Derive Type Using (Quick, Normal) Normal This setting is appropriate when the remote is a well behaved ICCP
Server. Only Data Value names should be returned by the server in the
Get Data Value Names operation. The Remote ICCP Server must return
ICCP responses for the Get Data Value Type operations that comply
with the IEC 60870-6-802 specification on IndicationPoint Type
descriptions.
AUTO DSTS Options Setting Notes
Enable On Under this policy the administrator can make use of either configured or
AUTO DSTS. In general, AUTO DSTS should be used so that all Client
Data Values are certain to be included in DSTS.
Redundancy Options
Association Connect Timeout
Enabled On System and application dependent.
Timeout 60000
139
Backup OPC
Local Data Quality Flag (Bad, Good OPC Client and application dependent.
Good, Uncertain)
Remote Data Quality Flag (Bad, Good
Good, Uncertain)
Server State Suspended Off
RPL Timers
Retry Time 2000 System and application dependent.
Startup Time 10000
Heartbeat TX Period 5000
Switch to Active Delay 1000
Data Synchronization
Mode (None, Local, Local & Local & OPC Client and application dependent.
Remote) Remote
Automatic Configuration Synchronization
Mode (None, Active, Primary, None This setting requires that configuration synchronization be initiated
Secondary) manually.
Table 10: Configuration Elements for Policy 1
140
POLICY 2: AUTOMATIC CONFIGURATION CHANGES

1. Client Data Value Configuration
Differences between the current set of configured Client Data Values and that which is exposed by the remote
control center will be discovered by AX-S4 ICCP and written into the configuration database without
administrator approval. This will include new, deleted, and changed data values.
All changes will be put into effect immediately, so that newly added Client Data Values will be available using
new OPC items.
2. Configuration Synchronization
Active to Standby node configuration synchronization will be initiated automatically by AX-S4 ICCP when
differences are detected. This means that the node in the Standby node (configuration synchronization Slave)
will pull the configuration from the Active node (configuration synchronization Master) using the RPL
connection.
3. Considerations
Note that when using this policy, configuration changes happen automatically and without visibility based
entirely on the behavior of the remote ICCP node. This is only advisable when the nature of the remote ICCP
node and its administrator policies are well known.
a. AX-S4 ICCP must be using a single client association.
b. The remote ICCP implementation must be well behaved with respect to the MMS GetNameList and
GetVariableAccessAttributes services as specified by the TASE.2 services (Get Data Value Names, Get
Data Value Types):
i. Data Values only are to be returned in the GetNameList response.
ii. Data Values must be exposed via the GetNameList in either VCC or ICC scope (not both).
iii. The correct ASN.1 type definitions (including element names) must be returned for data values.
c. The administrator of the remote ICCP node must make use of acceptable
configuration management policies.
d. Local configuration changes to Client Data Values are not persistent. That is, if the
administrator manually changes Client Data Values in either node, they will be
overwritten by AX-S4 ICCP during the discovery or configuration synchronization
processes.
4. The following settings should be used on the forms indicated in the table:
Discovery Options Setting Note
Enable Discovery On Discovery should almost always be enabled, because it is the mechanism used to
perform configured Data Value validation.
Execute (User Initiated, Every This setting should be used assuming there is a single Client Association to the
First Connection, Every Connection remote; otherwise, it should be set to User Initiated. Note that there is some
Connection) startup overhead for performing Discovery on every connection, but this setting
provides the best configuration maintenance results.
Automatically Accept On This setting keeps changes from being easily visible to the system administrator.
Database Changes
141
Configured Data Values
Validate Configured Data On This setting allows configuration mismatches to be tolerated, so that mis-
Values configured Client Data Values will not prevent a DataSet from being created.
Remove Mismatches from On
DataSets
Correct Mismatches in On This setting allows AX-S4 ICCP to markup the configuration database to show
Database what configuration mismatches are found. These markups do not affect
operation until the user accepts or rejects the changes.
Data Type Validation Normal This setting verifies that the Client Data Values are accessible and provides
(Normal, Detailed) reasonable confidence on data types. Detailed validation provides more positive
type validation but is much slower.
New Data Values
Discover New Data Values On This setting allows AX-S4 ICCP to markup the configuration database to show
what configuration mismatches are found. These markups do not affect
Add to Active On This setting exposes new Client Data Values as OPC items when they are
Configuration discovered.
Add to Database On This setting allows AX-S4 ICCP to markup the configuration database to show
what configuration mismatches are found. These markups do not affect
Set Read Only Attribute On Depends on the remote implementation, but writing data values is somewhat
unusual.
Derive Type Using (Quick, Normal This setting is appropriate when the remote is a well behaved ICCP Server. Only
Normal) Data Value names should be returned by the server in the Get Data Value Names
operation. The Remote ICCP Server must return ICCP responses for the Get Data
Value Type operations that comply with the IEC 60870-6-802 specification on
IndicationPoint Type descriptions.
AUTO DSTS Options Setting Note
Enable On Under this policy configured DSTS are not effective, and so the AUTO DSTS
features should be enabled so that all Client Data Values are included in DSTS.
Redundancy Options
Association Connect Timeout
Enabled On System and application dependent.
Timeout 60000
Backup OPC
Local Data Quality Flag Good OPC Client and application dependent.
(Bad, Good, Uncertain)
Remote Data Quality Flag Good
(Bad, Good, Uncertain)
Server State Suspended Off
142
RPL Timers
Retry Time 2000 System and application dependent.
Startup Time 10000
Heartbeat TX Period 5000
Switch to Active Delay 1000
Data Synchronization
Mode (None, Local, Local Local & Remote OPC Client and application dependent.
& Remote)
Automatic Configuration Synchronization

Mode (None, Active, Active This setting instructs the Standby node to obtain its configuration from the Active
Primary, Secondary) node whenever changes are detected.
Table 11: Configuration Elements for Policy 2
DATA SYNCHRONIZATION SAMPLE STARTUP SCENARIOS

The table below demonstrates a set of typical data synchronization scenarios. Configuration CRC mismatches are
marked with a *.
Node A Node B
Scenario Local Rem 1 Rem 2 Local Rem 1 Rem 2 Remarks
CRC CRC CRC CRC CRC CRC
Identical A B A B Local data sync OK
Configurations. Remote 1 data sync OK
Data A,B sent
Identical A B C A B C Local data sync OK
Configurations. Remote 1 data sync OK
Data A,B,C sent Remote 2 data sync OK
Local match, A *B A *C Local data sync OK
Remote Remote 1 data sync NOT OK
mismatch.
Data A sent
Local *A B *C B Local data sync NOT OK
mismatch, Remote 1 data sync OK
Remote match.
Data B sent
Local match, 1 A B *C A B *D Local data sync OK
Remote Remote 1 data sync OK
mismatch. Remote 2 data sync NOT OK
Data A,B sent
Table 12: Data Sync Sample Startup
143
DATA SYNCHRONIZATION SCENARIO: ADD REMOTE

This scenario illustrates the sequence of events for adding a Remote node to a redundant AX-S4 ICCP system.
Configuration CRC mismatches are marked with a *.
Node A Node B
Step Local Rem 1 Rem 2 Local Rem 1 Rem 2 Remarks
CRC CRC CRC CRC CRC CRC
Startup A B A B Local data sync OK
w/Identical Remote 1 data sync OK
Configurations.
Data A,B sent
Active Node (A) A B *C A B n/a Local data sync OK
adds Remote 2 Remote 1 data sync OK
on-line. CRCs Remote 2 data sync NOT OK
exchanged.
No Data sent
Standby Node (B) A B C A B C Local data sync OK
adds Remote 2 Remote 1 data sync OK
on-line. CRCs Remote 2 data sync OK
exchanged.
Data C sent
Table 13: Data Sync Sample Add Remote
144
CHAPTER 9: ICCP MONITOR
The AX-S4 ICCP Monitor is an OPC client application designed for monitoring and controlling AX-S4 ICCP. It allows a
user to examine the state of internal AX-S4 ICCP elements such as associations, Data Values, DSTS, Devices,
Messages, statistics, etc. The AX-S4 ICCP Monitor also allows control of associations and the discovery,
redundancy, and logging subsystems.
The ICCP Monitor can be invoked either by All ProgramsSISCOICCP Monitor AXS4ICCP Monitor or by
selecting the application from the Tools Menu of the ICCP Configuration Utility.
Figure 92: AX-S4 ICCP Monitor Main Screen
The following are configuration definitions available from the drop down menu selections on the top:
145
DROP-DOWN MENUS
EDIT - PREFERENCES
Figure 93: AX-S4 ICCP Monitor Preferences
This feature displays the following configurable parameters:
Group Update Rate - Indicates the default update rate for all OPC groups shown in the AX-S4 ICCP Monitor shown
in Milliseconds.
Double Click - This preference allows selecting whether the mouse selection is a double click or a single click (box is
unchecked).
Display OPC Quality Column - This preference allows selecting whether OPC Quality is displayed in the ICCP
Monitor.
Local Data Value Fields - These preferences allow selecting which fields to display for the Selected tab of any Local
Data Values. If all boxes are checked, the following is displayed for local data values.
146
Figure 94: AX-S4 ICCP Monitor Local Data Value Fields
Remote Data Value Fields - These preferences allow selecting which fields to display for the Selected tab of any
Remote Data Values. If all boxes are checked, the following is displayed for remote data values. The scrollbar will
need to be used to examine all fields.
Figure 95: AX-S4 ICCP Monitor Remote Data Value Fields
147
TOOLS - CLEAR STATUS

This feature clears the status pane at the bottom of the monitor.
START LOG VIEWER

This feature starts the SISCO Log Viewer. The SISCO Log Viewer allows users to view logging generated from one or
more logging sources. It makes use of TCP/IP for log data transfer, and so can be used to view diagnostic logging
from both local and remote sources. The SISCO Log Viewer is compatible with Microsoft Client Terminal Services.
LOCAL CONTROL CENTER OVERVIEW FORM
The following screen is displayed when the Local Control Center Name is selected in the tree in the left pane. It
displays overview information on the Local Control Center.
Figure 96: ICCP Monitor Local Control Center Overview screen
The following information is displayed:
AX-S4 ICCP
Version - Displays the release version of the software.
Status - Displays the Status of AX-S4 ICCP. Options are: Running, Standby, or Suspended.
OPC
Number of OPC Clients - Displays the number of OPC Clients attached to AX-S4 ICCP
Remotes – Number of Remotes - Indicates the number of configured Remote Control Centers.
148
Number of Active Remotes - Indicates the number of Remote Control Centers actively connected to AX-S4 ICCP.
Associations
Number of Associations - Indicates the number of configured associations. A remote can have more than one
association such as one for client activity and one for server activity. It is generally recommended to have one
association that performs both client and server functions.
Number of Active Associations - Indicates the number of associations actively connected to AX-S4 ICCP.
STATISTICS FORM
This screen displays general statistics on the local control center.
Figure 97: ICCP Monitor Statistics Screen
In all cases, the time stamp of the last item update is shown in the third column. If OPC Quality is checked in the
Preferences form, then the last OPC Quality is displayed.
SERVER SERVICES
Data Value Services
DSTS Reports Sent - Indicates the number of DataSetTransferSet Reports sent by AX-S4 ICCP.
Data Value Read Indications - Indicates the number of Reads received by AX-S4 ICCP.
Data Value Write Indications - Indicates the number of Writes received by AX-S4 ICCP.
149
DEVICE SERVICES
Device Get Tag Indications - Indicates the number of Get Tags received by AX-S4 ICCP.
Device Operate Indications - Indicates the number of Device Operates received by AX-S4 ICCP.
Device Select Indications - Indicates the number of Device Selects received by AX-S4 ICCP.
Device Set Tag Indications - Indicates the number of Set Tags received by AX-S4 ICCP.
INFORMATION MESSAGES
Information Messages Sent - Indicates the number of Information Messages sent by AX-S4 ICCP.
CLIENT SERVICES
DATA VALUE SERVICES

DSTS Reports Received - Indicates the number of DataSetTransferSet Reports received by AX-S4 ICCP.
Data Value Read Requests - Indicates the number of Read Requests sent by AX-S4 ICCP.
Data Value Write Requests - Indicates the number of Write Requests sent by AX-S4 ICCP.
DEVICE SERVICES
Device Get Tag Requests - Indicates the number of Get Tag Requests sent by AX-S4 ICCP.
Device Operate Requests - Indicates the number of Device Operate Requests sent by AX-S4 ICCP.
Device Select Requests - Indicates the number of Device Select Requests sent by AX-S4 ICCP.
Device Set Tag Requests - Indicates the number of Set Tag Requests sent by AX-S4 ICCP.
INFORMATION MESSAGES
Information Messages Received - Indicates the number of Information Messages received by AX-S4 ICCP.
150
REDUNDANCY SCREEN
If Redundancy is enabled, this screen displays parameters related to redundancy between the Active and Standby
Nodes.
Figure 98: AX-S4 ICCP Monitor Redundancy Screen
REDUNDANCY STATUS
See AX-S4 OPC Redundancy for information on these fields. A new redundancy mode can be set by clicking on the
CurrentMode field. This brings up a box to select an alternative redundancy mode.
Figure 99: ICCP Monitor Redundancy Screen Right-Click Set Mode
151
LOGGING SCREEN
This screen allows enabling/disabling of filtered logging for AX-S4 ICCP. General AX-S4 ICCP Logging (as selected on
the AX-S4 ICCP main screen) is global to all associations. Filtered logging of MMS Client/Server primitive
transactions and PDUs (Protocol Data Units) is available on an association basis. As soon as you enable logging on
an association, it turns off association specific logging on all the other associations.
Please refer to the KB article AX-S4 ICCP logging samples for examples of log masks turned on.
The Log Masks on the following screen can be enabled by setting the mask to True.
Important Note: Turning on anything but standard default logging can cause a noticeable performance hit on
a system. The standard log file will also wrap quickly and often needs to be extended in size
from the default. Only turn specific logging on when indicated by SISCO Technical Support
and turn it off when problem is resolved.
Figure 100: ICCP Monitor Log Masks
AX-S4
Flow - This logging enables flow and audit information from the AX-S4 ICCP implementation.
ICCP - This enables a high level audit of DataSet and DSTransferSet creation. This logging is useful when
troubleshooting DataSet and DataSetTransferSet creation problems.
OPC - This enables an audit trail of the OPC methods used in the DA server such as updating groups. Generally this
is not useful unless diagnosing specific OPC problems and requested by SISCO technical support.
152
MI
Flow - This logging enables flow and audit information from the SISCO’s ICCP-Lite implementation which is the
underlying code base.
Config - This logging is useful when troubleshooting issues related to configuration changes not showing up in the
TASE.2 provider at runtime (It shows what is configured vs. what is thought to be configured).
Adressing - This logging is useful when troubleshooting issue related to making an association between AX-S4 ICCP
and a Remote Control Center.
Discovery - Logs client data value information retrieved from the server during discovery.
MMS
Client - This logging is useful to watch DataSets be created on the Client and DSTransferSets received.
Server - This logging is useful to watch DataSets be created and DSTransferSets sent.
Note: Enabling Client and Server logging is useful when troubleshooting why an association goes active but later
disconnects.
MVL
ACSE - This shows Layer 7 (ACSE) stack information related to IP Addresses and selector values. This is useful for
double-checking addressing information used to troubleshoot problems seen when establishing associations.
REDUNDANCY
RplFlow - This log mask is used to troubleshoot RPL problems. It is useful in diagnosing issues between the actual
link between AX-S4 ICCP Active and Standby nodes.
IrFlow - This log mask provides additional redundancy logging involving switch over, data sync and configuration
sync.
SECURITY
This logging is used for the SISCO add-on Security Extensions only.
SecFlow - Shows detailed information about connection security elements such as certificates and processing
steps.
SSLeFlow - Shows detailed information on TLS/SSL connection, encrypting/decrypting, and MACE authentication.
RIGHT CLICK LOGGING OPTION
START LOG VIEWER

Right clicking on the Logging name in the tree starts the Log Viewer program.
153
DATA VALUES SCREEN
If all display columns are selected in the ICCP Monitor Preferences form, then the following data is shown for all
locally configured data values. The following key is used in the display of values in the form. Red means the quality
was bad, so 'bad value' is displayed for the value. Magenta means the quality is uncertain, so the value is
displayed in magenta with a (?) behind it.
Figure 101: ICCP Monitor Data Values screen
Right Clicking on any field brings up the following form:
Figure 102: ICCP Monitor Write Local Data Value
Name - This is a unique text string used to identify the data value.
Value - Indicates the current value of the DataValue.
TimeStamp - Indicates the timestamp for a data value each time the value is written by an OPC Client.
154
In addition to Name, the following quality flags can be displayed:
Quality Validity - Possible values are VALID, HELD, SUSPECT, NOTVALID.
Quality TimeStamp - Possible values are VALID, INVALID.
Quality Normal Value - Possible values are NORMAL, ABNORMAL.
Quality Current Source - Possible values are TELEMETERED, CALCULATED, ENTERED, ESTIMATED.
Note: The TimeStamp and COV fields are only updated when AX-S4 ICCP is configured to do so; else the OPC
client is required to update these two fields.
PROTECTION EVENTS SCREEN
This screen displays all locally configured protection events.
Figure 103: ICCP Monitor Protection Events Form
Right Clicking on any field brings up the following form:
Figure 104: ICCP Monitor Write Local Protection Event
Name - This is a unique text string used to identify the protection event object.
155
Event Flags - Indicates the bit strings for Protection Equipment events.
Operating Time (ms) - This is the time in milliseconds from the start of the operation until the first command was
issued.
Event Time - Indicates the time of the start of the operation.
LOCAL DEVICES
locally configured devices. The following key is used in the display of values in the form. Red means the quality was
bad, so 'bad value' is displayed for the value. Magenta means the quality is uncertain, so the value is displayed in
magenta with a (?) behind it. The ICCP Monitor does not allow writing to Devices. The information shown is
display only. See Device Handling in the OPC Chapter for more information on the displayed fields.
Information on Local Devices can only be viewed with the ICCP Monitor. An OPC client must be used to operate a
device.
Figure 105: ICCP Monitor Local Devices Screen
156
LOCAL MESSAGES
locally configured Messages. The following key is used in the display of values in the form. Red means the quality
was bad, so 'bad value' is displayed for the value. Magenta means the quality is uncertain, so the value is displayed
in magenta with a (?) behind it. The ICCP Monitor does not allow writing to Messages. The information shown is
display only. See Information Message Handling in the OPC Chapter for more information on the displayed fields.
The ICCP Monitor allows writing Local Information Messages. Right Clicking on any field brings up the following
form:
Figure 106: ICCP Monitor Write a Local Message Screen
Info Reference - This unique integer is used to identify the information message. This field cannot be edited.
Remote VCC - Displays a drop down to select the Remote Control Center name to send the message.
Local Ref - This is an OPC Native Type = VT_I4 (4 byte integer). The LocalReference attribute specifies a value
agreed upon between the sender and receiver of the message that further identifies the message (such as file
name, application identification).
Message ID - This is an OPC Native Type = VT_I4 (4 byte integer). This identifies the particular instance of a
message.
Message - This contains the byte stream of information being passed.
Important Notice: In order to send the message, an OPC client is needed. The Monitor cannot “Send” the
message; you must use the OPC Client for that.
157
Using an OPC Client, right right click on SendMessage, select WriteVQT...., select AsyncIO3, and Write a “Value” of
1. 1 = Send Message. You can also write the entire message from the OPC Client and not use the Monitor.
However, it is faster to use the Monitor to fill in the message, id, and local ref, then just enable the send bit with
the OPC Client.
Figure 107: ICCP Monitor Local Messages Screen
REMOTE CONTROL CENTERS OVERVIEW
The following screen is displayed when the Remote Control Center Name is selected in the tree in the left pane. It
displays overview information on the Remote Control Center.
Figure 108: ICCP Monitor Remote Control Centers Overview
Right clicking on any field in this form allows enabling/disabling the association.
Remote - Indicates the previously configured name of the Remote Control Center.
158
Association - Indicates the name assigned to the association.
Enabled - Indicate whether this association is enabled. Enabled means the status of the Link will transition towards
an ACTIVE status. Right click on this option allows disabling the association to disabled/enabled.
Status - Indicate the status of the association – options are:
IDLE - Means the association has not been started.
INIT_REQ - Means that AX-S4 ICCP has started to make a connection but the connection is not completely
established.
BACKOFF - Means that the association is not successful. Based on timers configured in the association form, it
will make another connection attempt.
ACTIVE - Means the connection is successfully established.
LISTEN - Means that AX-S4 ICCP is waiting for the Remote Control Center to make an association.
CONCLUDING - Means that the association is being dropped.
DISCOVERY - Means that AX-S4 ICCP is in discovery mode with the Remote Control Center.
Authentication - This indicates the type of authentication used for this connection. Default is none. This is only
used for AX-S4 ICCP Secure.
Encryption - This indicates the type of encryption used for this connection. Default is none. This is only used for
AX-S4 ICCP Secure.
159
INDIVIDUAL REMOTE CONTROL CENTER OVERVIEW
In addition, the following screen is displayed when a Remote Control Center Name is selected in the tree in the left
pane. It displays overview information on the selected Remote Control Center name.
Figure 109: ICCP Monitor Remote Control Centers Individual RCC Overview
Most of these fields are defined in the Remote Control Center Overview. The following are not.
Bilateral Table ID - Indicate the symbolic name (up to 32 characters) of the bilateral table version, which is
matched to the remote systems bilateral table version during the start of an association. If the two do not match,
the association is not allowed.
TASE.2 Version - Indicate the supported version of TASE.2 (ICCP).
Supported Features - Indicate the value of the features supported between AX-S4 ICCP and the remote control
center.
Remote AR - Indicate the AR Name of the Remote Control Center.
RIGHT CLICK ON NAME OF REMOTE CONTROL CENTER

The following menu is displayed:
160
Load into AX-S4 ICCP - This allows reloading the Bilateral Table information according to the settings in the ICCP
Configuration utility. If any fields have been changed in this utility, then the new changes need to be loaded into
AX-S4 ICCP in order to be sent to the Remote Control Center.
Execute Data Value Discovery - This feature executes the discovery algorithm according to the parameters known
when:
1. AXS4ICCP was started, or

2. the last time the Load into AX-S4 ICCP feature was executed.
Note: If some parameters have been changed on the Discovery form of the ICCP Configuration Utility and they
are needed to discover Client Data Values, use the Load into AX-S4 ICCP feature not the Execute Data
Value Discovery feature.
Refresh - The option refreshes all the forms used in the ICCP Monitor.
REMOTE CONTROL CENTER STATISTICS

This screen displays general statistics on the Remote Control Center. The fields displayed on this form are the same
of those of Local Control Center Statistics. In all cases, the time stamp of the last message received is shown in the
third column.
Figure 110: ICCP Monitor RCC Statistics
161
REMOTE CONTROL CENTER ASSOCIATION OVERVIEW

This screen displays association information on a specified Remote Control Center.
Figure 111: ICCP Monitor RCC Associations Overview
Association - Indicates the name assigned to the association.
Enabled - Indicates whether this association is enabled. Enabled means the status of the Link will transition
towards an ACTIVE status. Right click on this option allows disabling the association to disabled.
Status - Indicates the status of the association.
Authentication - This indicates the type of authentication used for this connection. Default is None. This is used if
AX-S4 ICCP Secure is installed.
Encryption - This indicates the type of encryption used for this connection. Default is none. This is used if AX-S4
ICCP Secure is installed.
REMOTE CONTROL CENTER ASSOCIATION STATISTICS

This screen displays general statistics on the Remote Control Center specific link. The fields displayed on this form
are the same of those of Local Control Center Statistics. In all cases, the time stamp of the last message received is
shown in the third column.
162
Figure 112: ICCP Monitor RCC Association Statistics
163
REMOTE CONTROL CENTER DATA VALUES

This screen displays information on data values configured for this selected Remote Control Center. Red means the
quality was bad, so 'bad value' is displayed for the value. Magenta means the quality is uncertain, so the value is
Figure 113: ICCP Monitor RCC Data Values
This screen displays some fields similar to those on the Local Control Center Data Values screen.
In addition, the following items are displayed:
Name - This is a unique text string used to identify the data value.
Value - Indicates the value of the DataValue.
TimeStamp - Indicate the timestamp attribute for the Data Value as assigned by the Remote Control Center.
Quality - In addition to Name, the following quality flags are displayed:
Quality Validity
Quality TimeStamp
Quality Normal Value
Quality Current Source
COV - Indicate the Change of Value counter for a data value each time the value is changed in the Remote Control
Center. If this value increments more than a value of 1 between changes, it has changed value more than once.
164
DS Conditions Detected - The conditions that triggered the DSTransferSet report to be sent. Possible values are:
OtherExternalEvent
IntegrityTimeOut
OperatorRequest
ObjectChange
IntervalTimeOut
Transfer Set Time Stamp - Indicate the time the Transfer Report was generated by the server.
REMOTE CONTROL CENTER PROTECTION EVENTS

The fields displayed are defined in the Local Control Center Protection Events.
Figure 114: ICCP Monitor RCC Protection Events
165
REMOTE CONTROL CENTER DEVICES

This screen displays all configured devices for a selected Remote Control Center. Red means the quality was bad,
so 'bad value' is displayed for the value. Magenta means the quality is uncertain, so the value is displayed in
magenta with a (?) behind it.
Figure 115: ICCP Monitor RCC Devices
SBO - Indicate if the device is Select Before Operate Device.
Check Back ID - This is used for SBO Devices only. The data is received from the Remote Control Center in the
Select response. The Check Back ID is a 16-bit integer.
Tag - If set to Yes, this indicates tag permission granted to the client.
Tag Value - Displays the value of the Tag, Options are:
NO-TAG=0
OPEN- AND-CLOSE-INHIBIT=1
CLOSE-ONLY-INHIBIT=2
Tag Reason - Indicate the reason for the tag. This is a user-defined string.
166
REMOTE CONTROL CENTER MESSAGES

This screen displays all configured messages on a selected Remote Control Center. Red means the quality was bad,
so 'bad value' is displayed for the value. Magenta means the quality is uncertain, so the value is displayed in
magenta with a (?) behind it. See Information Message Handling in the Building Applications Using OPC chapter.
Figure 116: ICCP Monitor RCC Messages
REMOTE CONTROL CENTER DSTS OVERVIEW
This screen displays overview information on all previously configured DSTransferSets on a selected Remote
Control Center.
Figure 117: ICCP Monitor RCC DSTS Overview
167
Name - Indicates the name of the DSTransferSet.
Enabled - Indicates whether the DSTransferSet is enabled.
Last Report Time - Indicates the last time the DSTransferSet was sent.
REMOTE CONTROL CENTER INDIVIDUAL DSTS OVERVIEW

This screen displays overview information on selcected DSTS associated with a Remote Control Center.
Figure 118: ICCP Monitor RCC DSTS Status and Parameters
STATUS
Enabled - Indicate if this DSTransferSet is enabled.
Association - Indicate the name of the association.
Data Set Name - Indicate the name of the Data Set.
Name - Indicate the name of the DSTransferSet.
Report Count - Indicate the number of DSTransferSets sent.
Last Time of Report - Indicate the last time the DSTransferSet was sent.
168
PARAMETERS
Start Time - Indicate the time value for the TASE.2 server to begin Condition Monitoring.
RBE - Indicate whether RBE is enabled. Report By Exception implies that the changed objects are reported.
Critical - Indicate whether critical is enabled. This controls the type of Transfer Report acknowledgement. A setting
of True means that the Transfer Report is critical and an acknowledgement from the TASE.2 client back to the
TASE.2 server is expected.
DSConditions.Interval - Indicate whether or not the TASE.2 server should send a report when the Interval time
arrives.
DSConditions.Integrity - Indicate whether or not the TASE.2 server should send a report of the entire Data Set
when the Integrity Check time interval expires. This only applies when RBE is TRUE.
DSConditions.Change - Indicate whether or not the TASE.2 server should send a report when any object in the
Data Set changes. Possible changes include a change of value, status, or the quality flag
DSConditions.Operator - Indicate whether or not the TASE.2 server should send a report when an operator at the
TASE.2 server control center requests it.
DSConditions.External - Indicate whether or not the TASE.2 server should send a report when any other external
event condition that is not described in the other conditions becomes true.
Interval - Indicate the time interval between TASE.2 server reports. The Interval starts when the Start Time occurs.
If RBE is set to No, then the current state of all objects in the data set are reported when the Interval expires. If
RBE is set to Yes, then the current state of only the changed objects in the data set are reported when the Interval
expires. If multiple changes occur to the same object during the Interval, then only the final value is reported. .
Integrity Check - Indicate the time value for integrity check when IntegrityTimeOut and RBE conditions are used.
Buffer Time - Indicate the time interval for buffering the ObjectChange condition before reporting to the TASE.2
client. The Buffer Time starts when the first ObjectChange condition occurs. If RBE is false, then the current states
of all objects in the Data Set are reported when the Buffer Time expires. If RBE is true, then the current state of
only the changed objects in the Data Set are reported when the Buffer Time expires. If the Buffer Time is zero, then
a report is generated for each change. If multiple changes occur to the same object during the Buffer Time, then
only the final value is reported.
TLE - Indicate the time value for Time Limit for Execution. This is a time that is primarily relevant to the TASE.2
server. It is the time over which the TASE.2 server has to send the Data Set Transfer Report to the TASE.2 client. If
the TASE.2 server anticipates that it cannot send the Data Set Transfer Report to the TASE.2 client within the TLE
time, then it shall not generate the report, and shall discard the data.
169
REMOTE CONTROL CENTER SELECTED DSTS DATA VALUES

This screen displays information on the data values associated with a selected DSTransferSet. Red means the
quality was bad, so 'bad value' is displayed for the value. Magenta means the quality is uncertain, so the value is
Figure 119: ICCP Monitor RCC Selected DSTS Data Values
Fields shown on this form are the same as described for Remote Control Center Data Values. Details on Data
Values, Protection Events, and Devices can be displayed by clicking on the individual branches of the DataSet
Transfer Sets.
170
LOCAL DATA SET TRANSFER SETS OVERVIEW
This screen displays all locally created DSTransferSets. These are the DataSetTransferSets created and started by
the remote control center and serviced by AX-S4 ICCP.
Figure 120: ICCP Monitor Local DSTS Overview
Name - Indicates the name of the DSTransferSet.
Enabled - Indicates whether the DSTransferSet is enabled.
Last Time Of Report - Indicates the last time the DSTransferSet was sent.
171
LOCAL DSTS STATUS AND PARAMETERS

See Remote Control Center Individual DSTS Overview for a description of these fields.
Figure 121: AX-S4 ICCP Monitor Local DSTS Status & Parameters
Details on Data Values, Protection Events, and Devices can be displayed by clicking on the individual branches of
the Local DataSet Transfer Sets.
172
CHAPTER 10: AX-S4 ICCP OPC CLIENT
AX-S4 ICCP now includes an OPC client gateway called the AX-S4 ICCP OPC Client that can transfer data from any
OPC server to/from the AX-S4 ICCP OPC Server. The AX-S4 ICCP OPC Client is essentially a general purpose gateway
that can transfer data between any OPC servers that has been enhanced with several key features to optimize
applications using the AX-S4 ICCP OPC Server as one of the OPC servers. The functionality included in the AX-S4
OPC Client Configuration includes:
• Allows multiple OPC servers to be selected. OPC items in each server can be used as either the source or
destination for data transfers.
• For each OPC server you can select OPC Items via OPC browsing to select which items will act as sources
(read from) and which items will be destinations (written to). Items can also be configured bi-directionally
enabling the same OPC Item to be used as a source and destination for different mappings.
• A special AX-S4 ICCP OPC Server item browser is provided to optimize handling of OPC items related to
remote and local data values with multiple OPC items for each ICCP data value.
• Ability to select items from the AX-S4 ICCP OPC Server in a generic way for mapping transfers of non-data
value items related to Information Messages and Devices for ICCP blocks 4 and 5 respectively.
• Ability to organize all OPC items into OPC Groups using configurable tuning parameters including Update
Rates, Deadband, and Keep Alive timer.
• The AX-S4 ICCP OPC Client can automatically generate ICCP timestamps using the OPC item timestamps
for destination items that are local data values.
• The AX-S4 ICCP OPC Client can automatically generate ICCP quality flags using the OPC item quality for
destination items that are local data values .
• Any OPC item for ICCP attributes like quality flags, change of value (COV) counters, extended data set
conditions, etc. is available for mapping as separate items if needed.
• A graphical user interface (GUI) is provided that enables configuration of source to destination mapping
using “drag & drop” of source items onto destination items.
• The AX-S4 ICCP OPC Client is integrated with the Excel file import/export capability of the ICCP
Configuration Utility enabling the OPC item mappings to be maintained using spreadsheets.
Once configured the AX-S4 ICCP OPC Client runs as a service and performs the data transfers in the background
enabling many different applications including:
1. As an OPC Client that can populate the Local Data Values (LDV) in the AX-S4 ICCP OPC Server form an
external OPC server.
2. As an ICCP Data Mirror where Remote Data Values (RDV) received by AX-S4 ICCP can be transferred to
Local Data Values and used in other bilateral tables to enable data from a single ICCP remote to be shared
with other remotes via separate links and Bilateral Tables.
3. As an ICCP-TASE.2 gateway where data from Remote Terminal Units (RTUs), Distributed Control Systems
(DCS), Progammable Logic Controllers (PLC), etc. can be used as sources of data for local data values as
well destinations where the values of remote data values can be written.
Descriptions of how to use the AX-S4 ICCP OPC Client for these applications will be described below. Many other
configurations, including combinations of these configurations, can be implemented using AX-S4 ICCP with the AX-
S4 ICCP OPC Client.
173
Figure 122: AX-S4 OPC Client Configuration Block Diagram
The diagram above illustrates how the AX-S4 ICCP OPC Client can be used to source data for local data values from
other external OPC servers. This is useful when you need to interface with an OPC application that does not
support an OPC client function. Some systems like DCS and SCADA packages may not include OPC client capabilities
by default and might include only OPC server functions. In that case, the AX-S4 ICCP OPC Client can be used to
transfer data to/from the OPC server and AX-S4 ICCP.
Although, the diagram illustrates application to local data values, the AX-S4 ICCP OPC Client can also be used to
transfer data from Remote Data Values to external OPC servers as a destination (instead of a source) enabling you
to send data to these external OPC servers.
To build this configuration, following configuration actions will need to be performed. Explanations of the various
screens and dialogs encountered are provided in a later section of this chapter titled Using the AX-S4 ICCP OPC
Client Configuration Utility:
1. Install and configure all the external OPC servers using the instructions provided by the suppliers of those
OPC servers. Please note that only OPC Data Access (DA) servers are supported by the AX-S4 ICCP OPC
Client. It is best to verify that the OPC servers are properly installed, configured and operational before
attempting to configure the AX-S4 ICCP OPC Client.
174
2. Configure the local data values in the AX-S4 ICCP OPC Server using the ICCP Configuration Utility as
described earlier in this manual.
3. Once the local data values and the external OPC server are configured, the AX-S4 ICCP OPC Client
Configuration Utility needs to be run in order to configure the data transfer between this OPC server and
AX-S4 ICCP local data values.
4. Use AX-S4 ICCP OPC Client Configuration Utility add the external OPC server to the list of OPC servers
displayed. By default the AX-S4 ICCP OPC Server is pre-configured.
Figure 123: Add an OPC Server
5. When making configuration changes a screen will pop up notifying that the configuration has changed
and warning that if the AX-S4 ICCP OPC Client service is running you will need to stop and then restart
that service once the configuration is complete. The double green arrow symbol is also shown on the top
right portion of the AX-S4 ICCP OPC Client Configuration Utility window as a reminder. When
configuration changes are done and you wish to deploy them, stop and start both the AX-S4 ICCP OPC
Client Configuration Utility and the AX-S4 ICCP OPC Client service.
6. Navigate to each added OPC server and use the item browser to select all the data points in that server
that will be used as data sources to AX-S4 ICCP local data values. Make sure only the “Read” check box in
the item browser is checked to indicate that you intend the selected points to be used as a source of data
only.
7. Next you will navigate to the AX-S4 ICCP OPC server and select “Add AX-S4 ICCP Data Values” via the righ-
click menu on OPC Group 1 to bring up the special AX-S4 ICCP Data Value Browser. Use this screen to
select all the local data values that need to be used while setting the Data Flow to “To AX-S4 ICCP”. If you
need to map items for local data messages or local devices right-click on the OPC Group 1 again and select
“Add OPC Group Items” instead. This brings up the generic item browser rather than the AX-S4 ICCP Data
Value Item browser.
8. Now that the source OPC items from the external OPC server have been configured and the local data
values in the AX-S4 ICCP OPC Server have been configured you will map the source OPC data items to the
destination local data values by clicking on the on the “Mapping” branch. This will display a dual paned list
of OPC Items. On the left side are all the OPC Items that can be used as source (where the “Read”
checkbox was checked when selecting the items) and on the right side are all the OPC Items that be used
as destinations for the mapping (in this case the AX-S4 ICCP local data values or any OPC Items you
selected that had the “Write” check box checked). If you have a long list of items you can use the filter
boxes on the top part of the screen to restrict what of items get displayed.
9. To create a mapping click on the desired source OPC item and then drag it over to the desired destination
item and then release the mouse button. This creates a mapping between the two items. You will see the
mappings appear on the bottom pane underneath the 2 OPC item lists as they are created. Repeat this
process until all the desired unmapped items have been mapped.
175
10. Once all the mapping have been done, exit the AX-S4 ICCP OPC Client Configuration Utility and Stop/Start
the AX-S4 ICCP OPC Client service if it is running.
Once the service comes back up the AX-S4 ICCP OPC Client will transfer all the data from the source OPC items to
the destination items at the group update rate that was set or upon a data change notification from the OPC
server. This results in the the AX-S4 ICCP local data values being updated from the data in the external OPC server
when the data in the OPC server changes. You can bring up the OPC Test Client and monitor the local data values
by connecting to the AX-S4 ICCP OPC Sever or by connecting to the external OPC server and monitoring the source
items.
USING AX-S4 ICCP OPC CLIENT FOR ICCP DATA MIRROR APPLICATION
Many times it is desired to share data that is received from one ICCP-TASE.2 remote with other remote ICCP nodes.
This is called an ICCP Data Mirror application. This is sometimes desirable because on some very large systems,
such as an ISO/RTO Energy Management System (EMS), the configuration of additional links for just a few data
points becomes difficult to implement for a several reasons. On these systems the ISO/RTO would prefer that if
ICCP data needs to be shared with another ICCP node that you do that without configuring a direct link to the
ISO/RTO system.
With the AX-S4 ICCP OPC Client, an ICCP Data Mirror application can easily be implemented as shown in the figure
below.
Figure 124: Using AX-S4 ICCP OPC Client for ICCP Data Mirror
176
The AX-S4 ICCP OPC Client Configuration Utility is used to select both Remote Data Values and Local Data Values.
When using the AX-S4 ICCP Data Value Item browser, elect both local and remote data values and set the Data
Flow To AX-S4 ICCP for the local data values and From AX-S4 ICCP for the remote data values.
The use of Excel spreadsheet files for configuration can be very helpful for data mirror applications. By exporting a
live configuration to an Excel spreadsheet you end up with a list of all the remote data values that are available.
You can then use spreadsheet functions and cut/paste techniques to quickly build up a list of local data values
corresponding to each remote data value. There are other shortcuts that can be used in the Excel file to create
single cell mappings for AX-S4 ICCP to AX-S4 ICCP item mappings. If you have a large number of points to map this
can save a lot of time compared to using the AX-S4 ICCP OPC Client Configuration Utility to drag and drop all the
individual mappings. See Chapter 11 for the Excel file functions.
EXAMPLE ICCP DATA MIRROR USING DEFAULT CONFIGURATION

By default, AX-S4 ICCP includes two utility control center configurations. UtilitySiteA is a default configuration for a
local control center that is preconfigured in the AX-S4 ICCP OPC Server when it is first installed. UtilitySiteB is a
preconfigure control center that the ICCP Test Application will execute by default. This is documented in an earlier
chapter.
AX-S4 ICCP also includes a default ICCP Data Mirror configuration. This is kept in an Excel file named
UtilitySiteADataMirroring.xlsx and is stored in \Program Data\SISCO\ICCP Configuration\Config directory during
installation. Starting with the default configuration of AX-S4 ICCP, the ICCP configuration Utility can then be used
to import the UtilitySiteADataMirroring.xlsx file to create a data mirror of all UtilitySiteB data values in
UtilitySiteA. Be sure to stop and then restart the AX-S4 ICCP OPC Client and the AX-S4 ICCP OPC Client
Configuration Utility if they are running when the spreadsheet import occurs.
177
USING AX-S4 ICCP OPC CLIENT FOR GATEWAY APPLICATIONS
Many times the data needed for local data values is available in a device like a Remote Terminal Units (RTUs),
Distributed Control Systems (DCS), Progammable Logic Controllers (PLC) or protection relay. By combining the AX-
S4 ICCP OPC Client with an external OPC server that can communicate with these devices you can build a
“gateway” that converts the data in the devices to ICCP local data values that can then be sent to remote ICCP
clients and will convert the data received from remote ICCP servers as AX-S4 ICCP remote data values to data in
these same devices.
The example below illustrates this application.
Figure 125: Using AX-S4 ICCP OPC Client as a Device Gateway
In this configuration, after the remote data values are updated as new data is received from remote ICCP servers,
the AX-S4 ICCP OPC Client will write that new data to the OPC server using the configured mappings after which
the OPC server will update the device data. Plus, when the OPC server updates the data items mapped to AX-S4
ICCP local data values, the AX-S4 ICCP OPC Client will update the local data values in the AX-S4 ICCP OPC Server.
Any ICCP clients with active links and data set transfer sets will be updated with the new data.
178
To build this configuration,l you need to pay attention to which items in the external OPC servers are selected with
the Read or Write attributes set using the OPC Group Item browser. In some cases, you may want a particular OPC
item to be both Read and Write where the value can not only be monitored via a mapping to a local data value
(OPC item = Read) but where a remote data value can change that item in the device (OPC item – Write). Likewise
you would generally use the local data values as the destinations for the OPC items selected with Read enabled
(Data Flow = To AX-S4 ICCP) but bidirectional data flow could be used for those local data values if updating a
device item with the local data value when it changes.
TIME STAMPS AND QUALITY FLAGS
Timestamps and quality flags are critical aspects of ICCP data. All AX-S4 ICCP components, including the AX-S4 ICCP
OPC Client, are designed specifically to ensure the integrity of the timestamps and quality flags that are sent and
received on the ICCP links when that value data is passed over the OPC interfaces.
The AX-S4 ICCP OPC Client is based on the OPC Foundation V3.00 Data Access (DA) specifications. The V3.00 DA
specification enables OPC clients and servers to read and write value, quality and timestamp information for all
OPC items. All AX-S4 ICCP components (including the AX-S4 ICCP OPC Client and AX-S4 ICCP OPC Server) are
capable of supporting the WriteVQT service where the value, quality and timestamp are all written together in a
single service call. This means that if you are using OPC servers that support the OPC V3.00 DA specification and
can support receiving a Write VQT service that accepts the value, quality and timestamp together in a single
transaction then the data transfers between those OPC servers and the AX-S4 ICCP OPC Server using the AX-S4
ICCP OPC Client will maintain the integrity of the value, quality and timestamps across the OPC boundaries. In that
case there is no need to perform any special processing of quality and timestamp data separate from the value
item. In this case, the AX-S4 ICCP OPC Client will automatically update the quality and timestamp data for all
destination items with a single mapping of the source value to the destination value when the value, quality and
timestamp data is received from the source item.
However, all OPC servers are not created equal. OPC servers based on OPC V2.05 or earlier do not support the
processing of WriteVQT in a single transaction. Also be aware that the processing of the quality and timestamp
data during the WriteVQT service by the OPC server is optional even with V3.00 servers. Sometimes there is a very
good reason for not supporting this service (e.g. where the device needs to generate the timestamp when it
receives the data from the OPC server and not when an OPC client writes the data to the OPC server). In other
cases there might be an OPC server that simply does not process quality and timestamp data. SISCO recommends
that you only use external OPC servers that are V3.00 and process the value, quality and timestamp in such a
manner as to ensure the integrity of those attributes.
Sometimes an non-SISCO OPC server must be used that does not properly process quality and timestamp data. In
those cases, you will need to handle the OPC Items related to the ICCP item validity/quality and timestamp
attributes separately. The AX-S4 ICCP OPC Client supports individual mapping of all ICCP attributes, including the
quality/validity and timestamp attributes, independent of the value items. This must be done very carefully
because ICCP attributes must be in a very specific format and the AX-S4 ICCP OPC Client does not support value
transformations that would enable complex operations on OPC item values to change them to conform to ICCP
requirements.
The AX-S4 ICCP OPC Client will perform some type transformations as described in the following section.
179
OPC TYPE MAPPING CONSIDERATIONS
The ICCP-TASE.2 standards specify the use of specific data types for ICCP attributes. All the OPC Items in the AX-S4
ICCP OPC Server representing ICCP data use the OPC type that mostly closely matches the ICCP types defined in
the standard. For instance, the item associated to the value of an ICCP REAL data value uses the OPC type of
“VT_R4” natively (or “Float32” in SISCO type notation). An OPC item representing an ICCP time stamp would be
represented by an OPC type of VT_DATE. An OPC item representing the value of an ICCP Information Message (a
String) uses an OPC type of VT_BSTR and so on.
When using the AX-S4 ICCP OPC Client to transfer data between OPC servers, it is highly recommended that this
transfer between OPC items of the same OPC type be done for both the source and destination. When the transfer
is done between matching OPC types. there is no loss of precision. However, this situation is not always possible.
External OPC servers may represent data using OPC types that are different from the native ICCP type definitions.
It is important to understand that when transferring data values between OPC items of different data types
problems can occur.
For instance, consider the following two data tpes:
a) An ICCP Discrete data value is a 32-bit Integer (Integer32) corresponding to an OPC type of VT_I4.
b) An OPC Item represented as a 16-bit Integer (Integer16) corresponding to an OPC Type of VT_I2.
If you use the AX-S4 ICCP OPC Client to transfer values between these 2 items the results will depend on the
direction of data flow and the value of the data being transferred as follows:
1. Transferring an Integer16 (VT_I2) OPC item to an Integer32 (VT_I4) OPC item:

a. Result is that the transfer is successful without data loss. All the possible values of the Integer16
will be converted to the correctly formatted Integer32.
2. Transferring an Integer32 (VT_I4) OPC item to an Integer16 (VT_I2) OPC item:
a. If the value of the Integer32 is between -32,768 and +32,767 then the transfer is successful
without data loss. In this case the Integer16 item is capable of representing the value of the
Integer32 item.
b. If the value of the Integer32 is less than -32,768 or more than +32,767 then the transfer cannot
be done. The result will be an error condition that will be logged in the AX-S4 ICCP OPC Client log
file and the OPC quality of that item will be set to BAD.
The following table defines how the AX-S4 ICCP OPC Client handles data transfers between different items of
differing types. The table defines the source item type on the vertical axis shown on the left and the destination
item on the horizontal axis at the top of the table. The key for the values in the table is shown below the table.
Any transfer that is attempted by the AX-S4 ICCP OPC Client where the condition specified in the table below is not
met will result in a log entry in the AX-S4 ICCP OPC Client log file identifying the error and the OPC quality of that
item will be set to BAD.
180
Source Types Destination Types
2
8
3
r16
r32
ed
ed
ed
r8
SISCO Types
n
2
l ea
n
n
ege
ege
ege
at3
at6
i ng
si g
si g
si g
e
o
Ti m
Flo
Flo
Un
Un
Un
Str
I nt
I nt
I nt
Bo
OPC Types VT_I1 VT_I2 VT_I4 VT_U1 VT_U2 VT_U4 VT_R4 VT_R8 VT_BSTR VT_BOOL VT_DATE
Integer8 VT_I1    1 1 1   X 3 X
Integer16 VT_I2 2   4 1 1   X 3 X
Integer32 VT_I4 2 5  4 6 7   X 3 X
Unsigned8 VT_U1 8        X 3 X
Unsigned16 VT_U2 8 6  4     X 3 X
Unsigned32 VT_U4 8 6 7 4 9    X 3 X
Float32 VT_R4 13 14 10 15 16 17   X 3 X
Float64 VT_R8 13 14 10 15 16 17 12  X 3 X
String VT_BSTR X X X X X X X X  X 11
Boolean VT_BOOL         X  X
Time VT_DATE X X X X X X X X 11 X 
Table 14: AX-S4 ICCP OPC Client Data Type Mappings
Key Meaning
 Mapping is allowed with no loss of precision
X Mapping is not allowed. Result is BAD quality for destination item.
1 Positive values only.
2 Allowed for values [-128..127] only.
3 0 = False !0 = True
4 Allowed for values [0..128] only.
5 Allowed for values [-32,768..32,767] only.
6 Allowed for values [0...32,767] only.
7 Allowed for values [0.. 2,147,483,647] only.
8 Allowed for values [0..127] only.
9 Allowed for values [0..65,535] only.
Allowed for [–2,147,483,648 to 2,147,483,647] only. Fractional component
10
truncated.
String must be in UTC format.
11
Example: “2012-11-12T16:14:15.0730000”
± 38
Allowed for ± 3.4 x 10
12
Fractional components more than 7 places truncated.
13 Allowed for values [-128..127] only. Fractional component truncated.
14 Allowed for values [-32,768..32,767] only. Fractional component truncated.
15 Allowed for values [0..128] only. Fractional component truncated.
16 Allowed for values [0..65,535] only. Fractional component truncated.
17 Allowed for values [0.. 2,147,483,647] only. Fractional component truncated.
Table 15: AX-S4 ICCP OPC Client Data Type Mapping Table Key
181
USING THE AX-S4 ICCP OPC CLIENT CONFIGURATION UTILITY
Configuration for the AX-S4 ICCP OPC Client can be invoked either by StartAll ProgramsSISCOAX-S4
ICCPConfiguration Tools AX-S4 ICCP OPC Client Configuration or by selecting the application from the Tools
Menu of the ICCP Configuration Utility.
Note: When Configuration Changes are made to the OPC Client Configuration, the OPC Client Configuration
Utility must be restarted. A dialog box is displayed to that effect. If multiple changes must be made, it is
recommended to make all necessary changes and then select OK on this dialog. The OPC Client
Configuration must be restarted.
This brings up the AX-S4 ICCP OPC Client Configuration Utility:
Figure 126: AX-S4 OPC Client Configuration
182
File – Exit - Exits the AX-S4 ICCP OPC Client Control.
View – Refresh - Refreshes information in the OPC Client Control displays.
TOOLS
Figure 127: AX-S4 OPC Client Configuration Tools Menu
Export Environment - Exports all the Items, Groups, Types into an XML file. By default, this file is saved to My
Documents.
Import Environment - Imports items, groups, types to the OPC Client from a previously exported XML file. It is not
recommended to modify these XML files in any way. All modifications should be done via the AX-S4 ICCP OPC
Client Configuration Utility or using the Excel file import functions (see Chapter 11).
Open Log File - Opens the AX-S4 ICCP OPC Client log file, UAPControl.log in the default program configured to
open *.log files.
Log Viewer - Opens the Log Viewer program.
Configure AX-S4 ICCP OPC Client Control Logging - Opens the AX-S4 ICCP OPC Client log confiruation file
(UapControlLogCfg.xml ) file using the default XML viewer (Internet Explorer) configured in Windows. This file is
used to configure log masks to diagnose issues. You may have to change your default XML editor in Windows to
cause this menu selection to use a program that can edit XML files (such as Notepad, WordPad, Notpad++, etc.).
DEFAULT OPC TUNING PARAMETERS

Clicking on the AX-S4 ICCP OPC Client branch in tree brings up the following form that allows setting default OPC
Group parameters that will be used when new OPC groups are created. These settings can always be edited for the
individual OPC groups after they are created.
183
Figure 128: AX-S4 OPC Client Configuration OPC Tuning Parameters
Default Update Rate - Displays the default OPC Group Update Rate in ms. Each group can be configured with a
different update rate. This rate should not be set to anything faster than the maximum rate of change for items in
that group. It is also recommended that you separate items into different groups that change at dramatically
different rates in order to avoid unnecessary processing for data that does not change.
Default Deadband - Displays the default Deadband as a percentage.
Note: Deadband is not supported for AX-S4 ICCP OPC Server Other OPC servers may support this functionality.
Default KeepAlive - Displays the default OPC KeepAlive timer in milliseconds. Each group can be configured with
an KeepAlive timer. The KeepAlive mechanism confirms the OPC Client callback connection is active.
RIGHT CLICK OPTIONS AX-S4 ICCP OPC CLIENT

Right-Clicking on the AX-S4 ICCP OPC Client branch gives access to the following options:
Start Client - Starts the AX-S4 ICCP OPC Client by bringing up a command prompt to execute the OPC client. Press
X within the prompt to exit the OPC clientCannot be selected. Use the Window Service Control Panel to start and
stop the AX-S4 ICCP OPC Client.
Configure AX-S4 ICCP OPC Client Logging - Opens the OPC Client Logging file in notepad. This used to select log
masks to diagnose issues.
Add OPC Server - Brings up a dialog to select another Add another OPC Server to the list of OPC servers.
184
ADD OPC SERVER DIALOG
Figure 129: AX-S4 ICCP OPC Client Configuration – Add OPC Server
The dialog displays a list of OPC DA servers that have been installed on the computer. The file at the top allows
filtering on OPC V2.XX or OPC V3.00 servers. It allows browsing the local machine or the local network for an OPC
Server. Click on a server to select it. Then press OK to accept or Cancel to exit.
OPC GROUP DISPLAY

Selecting the OPC Branch under the SISCO AX-ICCP branch brings up the OPC Groups form for the AX-S4 ICCP OPC
Server. The AX-S4 ICCP OPC Server comes pre-configured for the AX-S4 ICCP OPC Client.
Figure 130: AX-S4 ICCP OPC Client Configuration – OPC Group Dialog
185
OPC Server - Displays the OPC Server name. This cannot be modified.
Name - Displays the OPC Group Name. This field can be edited.
Update Rate - Displays the OPC Update Rate in milliseconds. This field can be edited.
Deadband - Displays the deadband. This is not supported for the AX-S4 ICCP server.
Note: Deadband is not supported for AX-S4 ICCP OPC Server. Other OPC servers may support this functionality.
KeepAlive - Displays the OPC Keep Alive Timer rate in milliseconds. The AX-S4 ICCP OPC Client will ensure that
there is some activity with the OPC server at least during this period. This field can be edited.
If any of these setting are changed, click the OK button to accept the changes or Cancel to Discard.
ADDCREATE/EDIT OPC GROUP DISPLAY

Pressing the Add button, or right-clicking on the OPC Group branch, brings up the Add OPC Group.
Figure 131: AX-S4 ICCP OPC Client Configuration – Create or Edit OPC Group Dialog
Allows adding a new OPC Group or editing an existing OPC Group for the selected OPC server. Must click on
Add/Update in order for the changes to occur. Click Close to exit.
Delete - Hightlight the OPC Group to delete, right-click and select Delete. It will prompt to verify that the deletion
should occur.
OPC GROUP ITEM SELECTION

Under the branch OPC Groups is listed all of the configured OPC Groups. Click on an OPC Group Name. The form
allows adding items to an OPC Group. Pressing Add on this screen will allow you to bring up the item selection
dialogs for that server.
If AX-S4 ICCP is the OPC server clicking Add will bring up a special AX-S4 ICCP OPC Item dialog that is optimized for
handling ICCP data values.
186
If you want to select OPC items from the AX-S4 ICCP OPC Sever that are not local or remote data values, such as
Information Messages or Devices, right-click on the OPC group and select Add OPC Group Items to bring up the
generic OPC Group Item Selection dialog.
If the OPC server selected is not the AX-S4 ICCP OPC Server then clicking Add will bring up the generic OPC Item
Selection dialog.
AX-S4 ICCP ITEM SELECTION FORM

When the selected group is in the AX-S4 ICCP OPC Server, clicking on Add brings up the AX-S4 ICCP OPC Item
Selection dialog:
Figure 132: AX-S4 ICCP OPC Client Configuration – Select AX-S4 ICCP OPC Item DIalog
Local - Data Values - Checking the Data Values box under local allows selecting local data values from the AX-S4
ICCP OPC Server’s namespace. A filter can be applied to reduce the number of queried local data values, for
example *Gas* will display local data values GasOn and GasTurbineStatus when using UtilitySiteA for the AX-S4
ICCP local control center. Clicking on the green arrow or the Query button displays the local data values.
Data Flow - Options are:
To AX-S4 ICCP Write

From AX-S4 ICCP Read
Bidirectional Read and Write
Remote - Data Values - Checking the Data Values box under Remote allows selecting remote data values from AX-
S4 ICCP’s OPC namespace. A filter can be applied to reduce the number of items. Clicking on the green arrow or
Query button displays the remote data values.
187
Data Flow - Options are:
To AX-S4 ICCP Write

From AX-S4 ICCP Read
Bidirectional Read and Write
Once the Local or Remote Data values are select as well as filters and Data Flow Options, press the Query button
to display the list of AX-S4 ICCP data values matching that criteria. You must click on Query in order to display
items for selection.
Data Value Attributes - Check the data value attributes for the selected items that will be included in the OPC Item
selection. The Attributes check boxes determines which attributes will have their corresponding OPC items
available for mapping after Add is pressed. If the check box is not selected for a given attribute, that attribute will
not appear as an item available for mapping.
In order to select a data value, hightlight the desired data values and click add. You can use the Ctrl and Shift keys
to select multiple items. Click Close to exit.
GENERIC OPC GROUP ITEM SELECTION FORM

If the OPC Server is not the AX-S4 ICCP Server, a generic OPC Group Item Selection form is displayed on which OPC
Items can be selected from ANY OPC server. Use this same form to select non-data value ICCP Items for AX-S4 ICCP
such as those for Information Messages or Devices.
Figure 133: AX-S4 ICCP OPC Client Configuration - Generic OPC Group Item Selection Form Tree View
View Options - This controls how the OPC items are displayed. Selecting Node displays a tree view that can be
used to browse of OPC items of interest. Selecting Flat displays all available OPC items in a single flat list (See
below).
On the left, a tree view of the OPC name space is presented that allows browsing for the items of interest. In this
example, a KepWare KepServerEx OPC server is shown. Expand the branches and then click on Node to display the
OPC items available at that level.
188
Item Options - Checking the Read or Write check boxes determines if these settings will be set for the selected
items when the Add button is pressed. To select source items only, check the Read box and uncheck the Write
box. To select destination items only, check the Write box and uncheck the Read box. Then select the items, and
then press Add to add those items to the OPC using those read/write settings.
After all items have been selected, press the Close button.
Figure 134: AX-S4 ICCP OPC Client Configuration - Generic OPC Item Selection - Flat View
OPC GROUP ITEM LIST DISPLAY

After adding items to the designated group, the OPC Group Item list is displayed:
Figure 135: AX-S4 ICCP OPC Client Configuration – OPC Group Item List Display
Add - Additional items can be selected by pressing Add to bring up the appropriate Select OPC Items dialog.
189
Delete - Deletes the highlighted items.
Read All - Changes all items in the group to read (source items).
Write All - Changes all items in the group to write (destination items).
If both checkboxes are selected, then the items are both read (From AX-S4 ICCP) and write (To AX-S4 ICCP).
OPC ITEM LIST

Selecting the OPC Items list under a given OPC server will display all the OPC Items that have been selected from
all the Groups defined for this OPC Server.
Figure 136: AX-S4 ICCP OPC Client Configuration – Group OPC Item List
190
OPC ITEM MAPPING

By selecting the Mapping branch, the Mapping display is shown. The Mapping display shows which OPC items
items have already been mapped and allows creating new mappings or to delete existing mappings.
Figure 137: AX-S4 ICCP OPC Client Configuration – OPC Mapping Display
The Mapping display consists of three elements:
1. The Source Item Pane – is on the top left side of the Mapping Display and shows a list of all the OPC Items
from all the OPC Groups in all the OPC servers that are configured where the Read checkbox is set. Any
OPC item where the Read box was checked can be used as a source item.
2. Destination Item Pane – is on the top right side of the Mapping Display and shows a list of all the OPC
Items from all the OPC Groups in all the OPC servers that are configured where the Write checkbox is set.
Any OPC item where the Write box was checked can be used as a destination item.
3. Mapped Item Pane – is on the bottom of the Mapping Display and shows a list of all the source and
destination items that have already been mapped together.
The Source and Destination Item Panes have settings at the top of them to control what items will be displayed:
<Filter> – putting text in the field with or without wildcard characters (‘*’) allows you to specify which items of all
the available items to display. For instance, entering “*AXS4ICCP*” into the Filter field and clicking on the green
arrow will result in a list containing items from the AX-S4 ICCP OPC Server only.
This symbol at the top of the Source and Destination Panes is the “Unmapped Item” filter. Clicking on this
item will highlight items (as shown in the figure above) and enables the Unmapped Item filter. This will
result in only displaying OPC Items that are not already in at least one mapping. By leaving this selection
on as you create mappings, the list of available OPC items will shrink until all items have been mapped.
191
CHAPTER 11: EXCEL FILE IMPORT AND EXPORT
AX-S4 ICCP provides the capability to import and export to an Excel Spreadsheet.
Modifying AX-S4 ICCP using the ICCP Configuration utility is relatively simple when making small changes.
However, with larger changes modifying the configuration can be burdensome and may take a while. Using the
Excel import export feature making large modifications becomes much more convenient. The Excel format allows
for the transfer of data from other sources much easier than with XML. The Excel format also allows for
customization before importing the data into the system. Look up tables provide current data structures to be
labeled without having to use ICCP nomenclature. OPC mappings to the OPC client can be added to the
configuration. Excel also allows the user to customize their systems imports and exports to meet their needs.
Reports and other excel related services can be added easily by the user. There are even batch commands that
allow the user to import and export the configuration to and from the system.
FUNCTIONALITY
Once the ICCP Configuration has been imported into an Excel Spreadsheet, the ability to add, modify, or delete
ICCP objects is possible.
The Local Control Center Name, Remote Control Center Name and Bilateral Table information MUST all exist in
order to use the Excel capabilities.
The Excel workbook consists of worksheets and columns dealing with the following information:
• RemoteControlCenterBLTs
• LocalDataValues
• LocalDevices
• LocalMessages
• ClientDataValues
• ClientDevices
• ClientMessages
• DataTypeMappings – Optional
For Local Objects:
• All Local Objects can be assigned as Server Objects for any Remote Control Center.
• LCC Data Values
o Action,Name,Type,NormalSource,NormalMin,NormalMax,MapInfo,Description
• LCC Devices
o Action,Name,Type,SBO,CheckBackId,SelectTimeout,TagEnabled,
MapInfo,Description
• LCC Messages
o Action,InfoReference,Size,MapInfo,Description
For Remote Objects:
• RCC Remote Data Values

o Action,Name,Scope,Type,ReadOnly,MapInfo,Description
192
• RCC Remote Devices

o Action,Name,Scope,Type,SBO,CheckBackId,TagEnabled,MapInfo,Description
• RCC Remote Messages
o Action,InfoReference,Scope,Size,MapInfo,Description
Note: MapInfo is limited to 4000 byte character size. If MapInfo field is created larger than 4000 and imported
back into the ICCP Configuration Utility, the following error is logged:
2014-08-29 15:24:17.963 SLOGALWAYS (Axiccb.c 124 ThreadId=0xBE8 (3048))

Product: AXS4ICCP-142-095, Version: 6.0000.0
2014-08-29 15:24:18.010 ICFG_LOG_ERR (IcfgDb.cpp 295 ThreadId=0xBE8 (3048))

ERROR: Invalid MapInfo size: 4163 for Local Data Value ActualVoltage
2014-08-29 15:24:18.057 ICFG_LOG_NERR (IcfgDb.cpp 135 ThreadId=0xBE8 (3048))

Configuration Read Error
2014-08-29 15:24:18.057 AXIC_LOG_ERR (Axicmain.c 217 ThreadId=0xBE8 (3048))

Error Reading Configuration.
2014-08-29 15:24:18.057 AXIC_LOG_ERR (axs4iccp.cpp 758 ThreadId=0xBE8 (3048))

AX-S4 ICCP Failed to start, error = 0x1
USING THE EXCEL OPTION FROM THE ICCP CONFIGURATION UTILITY
The ICCP Configuration Utility allows importing and exporting Local Control Center configuration to a Microsoft
Excel format. This can be performed in two ways:
• File menu option.

• Right-click on Local Control Centers branch in the tree.
EXPORT FROM EXCEL

The Export File indicates the name of the Microsoft Excel file (xlsx) and the path where it will reside. Selecting …
saves the file to another location. In addition to exporting all information to an Excel file, there are options to
select only one type of object to export such as LocalDataValues, LocalDevices, LocalMessages, RemoteDataValues,
Note: It is recommended that if importing only one type of object, the file name is meaningful such as
UtilitySiteALocalDataValues.xlsx.
193
Figure 138: ICCP Configuration Utility Export LCC to Excel
SAMPLE EXCEL FILES

Sample Excel files will be installed in \ProgramData\SISCO\ICCP Configuration\Config folder.
The ImportOptionsDescription.xlsx file contains one of every option available for the import options of Excel.
The IccpExcelTemplate.xltx template file should be used to create an Excel file. This can be opened in Excel and
objects can be added. So that the template file is not overwritten, this file is only ReadOnly.
A sample Excel file called UtilitySiteADataMirroring.xlsx is included to illustrate the mapping of all UtilitySiteB
measurements to local datavalues in UtilitySiteA. Local datavalues prefixed with B_ are the mirrored data.
ALL LOCAL CONTROL CENTER OBJECTS

If all Objects are exported, AX-S4 ICCP creates a sheet for each object type.
Below is shown an example of the LocalDataValues sheet.
Figure 139: Sample Excel LocalDataValues sheet
IMPORT FROM EXCEL

Brings up a form used to import a Microsoft Excel file (xlsx) for a Local Control Center from a list of all configured
Local Control Centers. Importing the file will save it to the ICCP Configuration Database. In addition to importing all
information from an Excel file, there are options to select only one type of object to import such as
LocalDataValues, LocalDevices, LocalMessages, RemoteDataValues, RemoteDevices, and RemoteMessages.
194
ICCPEXCEL WORKBOOK COLUMNS AND VALIDATION
The IccpExcel workbook contains seven worksheets. The contents of each are described briefly below.
LocalDataValues
Column Name Validation
A Action Add or Delete
B Name Identifier <= 32 characters
C Type Valid ICCP Type or User Type Mapped to a valid ICCP Type
D NormalSource Calculated, Entered, Estimated or Telemetered
E NormalMin Discrete: valid Int32, Real: valid Single, State: valid if 0 <= Byte <= 3
F NormalMax Discrete: valid Int32, Real: valid Single, State: valid if 0 <= Byte <= 3
G MapInfo If present, Length <= 4000
H Description If present, Length <= 255
++ See below 14 OPC Mapping columns : See below
Table 16: AX-S4 ICCP Excel Worksheet - LocalDataValues
LocalDevices
B Name Identifier <= 28
C Type Real, Discrete, Command
D SBO True or False
E CheckBackId A whole number between 0 and 32767, inclusive
F SelectTimeout A whole number between 1 and 2147483647, inclusive
G TagEnabled True or False
H MapInfo If present, Length <= 4000
I Description If present, Length <= 255
Table 17: AX-S4 ICCP Excel Worksheet - LocalDevices
LocalMessages
B InfoReference A whole number between 0 and 2147483647, inclusive
C Size A whole number between 0 and 2147483647, inclusive
D MapInfo If present, Length <= 4000
E Description If present, Length <= 255
Table 18: AX-S4 ICCP Excel Worksheet - LocalMessages
195
ClientDataValues
B RemoteControlCenterName Identifier <= 32 characters, and is in the database
C BilateralTableName Identifier <= 32 characters, and is in the database
D Name Identifier <= 32 characters
E Scope ICC, VCC or null (defaults to ICC)
F Type Valid ICCP Type or User Type Mapped to a valid ICCP Type
G ReadOnly True or False
H MapInfo If present, Length <= 4000
I Description If present, Length <= 255
Table 19: AX-S4 ICCP Excel Worksheet - ClientDataValues
ClientDevices
D Name Identifier <= 28 characters
F Type Valid ICCP Type or User Type Mapped to a valid ICCP Type
G SBO True or False
H CheckBackId A whole number between 0 and 32767, inclusive
I TagEnabled True or False
J MapInfo If present, Length <= 4000
K Description If present, Length <= 255
Table 20: AX-S4 ICCP Excel Worksheet - ClientDevices
ClientMessages
D InfoReference A whole number between 0 and 2147483647, inclusive
F Size A whole number between 0 and 2147483647, inclusive
G MapInfo If present, Length <= 4000
H Description If present, Length <= 255
Table 21: AX-S4 ICCP Excel Worksheet - ClientMessages
196
DATA TYPE MAPPINGS
DataTypeMappings
A UserType
B IccpType Must be one of:
Discrete
DiscreteQ
DiscreteQTimeTag
DiscreteExtended
DiscreteQTimeTagExtended
Real
RealQ
RealQTimeTag
RealExtended
RealQTimeTagExtended
State
StateQ
StateQTimeTag
StateExtended
StateQTimeTagExtended
SingleProtectionEvent
PackedProtectionEvent
Table 22: AX-S4 ICCP Excel DataTypeMappings
MAP INFO FIELDS

Below is a list of abbreviations used for MapInfo:
S = State
ES = ExpectedState
T = Timestamp
QS = Quality.CurrentSource
QN = Quality.NormalValue
QT = Quality.TimeStamp
QV = Qualty.Validity
TA = Tag
CV = ChangeOfValue
SF = SingleEventFlags
PF = PackedEventFlags
PE = PackedEvent
ET = EventTime
OT = OperatingTime
197
MAP INFO FORMATS
SPECIFYING JUST THE ITEM PATH
It will map only to the State or Value (whichever is the main type).
Item String:
<OpcMap>UtilitySiteA:DataValue~B_MEASUREMENT_RQ_03.Value</OpcMap>
This allows specifying the partial attributes and allows mapping to specific attributes within the Data Value.
Example:
<OpcMap>V==UtilitySiteA:DataValue~B_MEASUREMENT_RQ_01.Value</OpcMap>
<OpcMap>QC==UtilitySiteA:DataValue~B_MEASUREMENT_RQ_01.Quality.CurrentSource</OpcMap>
<OpcMap>QN==UtilitySiteA:DataValue~B_MEASUREMENT_RQ_01.Quality.NormalValue</OpcMap>
<OpcMap>QT==UtilitySiteA:DataValue~B_MEASUREMENT_RQ_01.Quality.TimeStamp</OpcMap>
<OpcMap>QV==UtilitySiteA:DataValue~B_MEASUREMENT_RQ_01.Quality.Validity</OpcMap>
SPECIFYING ALL ATTRIBUTES
Allows mapping of all attributes of the specified data value to the target data value. Attributes that exist in one
data value but not the other will be ignored. Only works when mapping to another AX-S4 data value and intended
for mirroring within AX-S4 ICCP.
Item String:
<OpcMap>*==UtilitySiteA:DataValue~B_MEASUREMENT_RQ_03</OpcMap>
USING THE COMMAND LINE UTILITY
A new utility that can be run from a command line can also be used to perform Excel Import and Export capability
without invoking the ICCP Configuration Utility.
To run the application, open a command prompt C:\Program Files (x86)\SISCO\ICCP Configuration\IccpExcel.exe.
This must be run with administrator privileges.
IccpExcel takes the following command line parameters, without quotes unless noted:
Mode={Import / Export} - Mandatory
Excel="ImportValuesA.xlsx" – Mandatory. Must be in quotes if the file name contains spaces
IccpCfg="iccpcfg.mdb" - Used for both modes. If not present, IccpExcel will get it from the registry. Must be in
quotes if the file name contains spaces
LCC=LccName – Mandatory
198
RCC=RccName - Optional
Import - Used when AddLocalToServer is specified. Use * or % for wildcards. If not specified, will add to all
Remotes
Export - Specifies RCC to be included in export. Use * or % for wildcards. Default is all Remotes
Objects={All / LDV / LDEV / LMSG / CDV /CDEV / CMSG} – Optional. Default is All
AddLocalToServer - Optional for Import, otherwise ignored. Instructs IccpExcel to add local objects as server
objects for one or more RCC.
ServerScope={ICC / VCC} - Optional for Import, only when AddLocalToServer, otherwise ignored. Specifies Server
scope. Default is ICC
ServerReadOnly={Yes / No} - Optional for Import when AddLocalToServer, otherwise ignored. Specifies whether
Server scope Data Values are Read Only. Default is Yes.
Quiet - Minimal screen output. Results are always written to ProgramData\SISCO\ICCP

Configuration\IccpExcelResults.txt
Return values from running the utility are:
Success : 0
Failure : 1
Partial Success : 2
This utility will have standard SISCO diagnostic logging. Logging is always written to ProgramData\SISCO\ICCP
Configuration\IccpExcel.log
For example:
Mode=Import LCC=LccName Excel="ExcelFileName" Objects=ObjectSelect AddLocalToServer

ServerScope=ServerScopeSelect RCC=RccName Quiet
199
APPENDIX A: LOG VIEWER AND LOGGING
The Log Viewer is an application that looks at logging from multiple applications in one file. Also, it can be setup on
a remote machine to capture logging from multiple applications. Current log parameter settings can be modified
without bringing applications down. This allows modifying log parameters while the application is running.
To capture logging for applications running on the same computer as the Log Viewer, no additional configuration
has to be done. The Log Viewer will automatically detect the applications and start capturing their logging.
To capture logging for applications running on a different computer, the Log Viewer will have to be configured to
look for the application. The SISCO Log Viewer runs on the Windows platform but can remotely access logging on
non-Windows machines.
Please refer to the LogViewer User’s Guide for general information on how to use this application.
StartProgramsSISCOLog ViewerSISCO Log Viewer User’s Guide.
Figure 140: Log Viewer Screen
200
LOG FILE LOCATIONS
Log files will be located in the following directories:
• <Common Application Data>\SISCO\LogViewer

• <Common Application Data>\SISCO\AX-S4 ICCP
o AXS4ICCP.log
To access these directories, folder options need to be set to Show hidden files and folders.
Within the file directory window – select Alt-F. This will bring up an alternate menu – select Tools – Folder
Options. Make sure that show hidden files, folders, and drives is selected.
Figure 141: How to Display Hidden Folders
For example:
\Documents and Settings\All Users\Application Data\SISCO\AX-S4 ICCP\axs4iccp.log
AX-S4 ICCP provides several useful diagnostic tools for troubleshooting problems in addressing, configuration, and
application development. Samples of different log masks are available in a KB article.
Important Note: Turning on anything but standard default logging can cause a noticeable performance hit on
a system. The standard log file will also wrap quickly and often needs to be extended in size
from the default. Only turn specific logging on when indicated by SISCO Technical Support
and turn it off when problem is resolved.
201
LOG CONFIGURATION EDITOR
The log configuration file for AX-S4 ICCP is called Axs4IccpLogCfg.xml.
Figure 142: Select Log Configuration File
STANDARD LOGGING
No additional log masks turned on results in default errors and normal errors logging. This is the recommended
default logging since it will capture errors without comprising the system usage. Any additional logging turned on
for any extensive time period will result in increases in CPU usage and a decrease in performance. This is not
recommended without recommendation from SISCO Technical Support. Once troubleshooting is finished, please
turn off all log masks to default to standard logging.
LOG CONTROL SCREEN

This form displays logging preferences. Please refer to the LogViewer User’s Guide for general information for
descriptions.
202
Figure 143: Log Configuration Editor Log Masks screen
AXS4ICCPLOGMASKS
Flow - This logging displays the flow and audit information for AX-S4 ICCP. It basically displays activity within the
AX-S4 ICCP interface. Recommended setting: Disabled.
ICCP - This enables a high level audit of DataSet and DSTransferSet creation. This logging is useful when
troubleshooting DataSet and DSTransferSet creation problems. Recommended setting: Disabled.
OPC - OPC logging shows OPC transaction activity such as browsing and the OPC method used. This logging is not
particularly useful unless troubleshooting specific AX-S4 ICCP to OPC Client problems. Recommended setting:
Disabled.
OPCData - OPCData logs all variant data when an OPC client issues a Write or WriteVQT request.Recommended
setting: Disabled.
MILOGMASKS
Flow - This logging enables flow and audit information from the SISCO MMS-EASE Lite ICCP implementation. This
code is used in AX-S4 ICCP for ICCP and lower layer processing. Recommended setting: Disabled
Addressing - This logging displays how parameters configured in the Identification tree affect the addressing
configuration found for Remote Control Centers. This log mask is useful when determining why associations are
not established. It will show which remotes are considered for incoming connect indications and which remotes
are ignored. Recommended setting: Disabled
203
Discovery - Logs client data value information retrieved from the server during discovery. It is useful when
diagnosing problems using Discovery. Recommended setting: Disabled
Configuration - This logging is useful when troubleshooting issues related to configuration changes not showing up
in the ICCP provider at runtime (It shows what you have configured versus what you think you have configured).
Recommended setting: Disabled.
MMSLOGMASKS
Client - This logging displays information on AX-S4 ICCP to Remote Control Center activity from the client side such
as connection issues as well as read and write requests. Recommended setting: Disabled.
Server - This logging displays information on AX-S4 ICCP to Remote Control Center from the server side such as
connection issues as well as read and write requests. Normally Client and Server logging are turned on in
conjunction to troubleshoot problems concerning associations and address configuration. Recommended setting:
Disabled.
MVLLOGMASKS
Flow - This logging displays the flow control logging for MMS-Lite Virtual Machine interface. These are internal
MVL calls from within AX-S4 ICCP. This is used Recommended setting: disabled.
ACSE - This logging audits MMS events passed up through the ACSE layer mostly connection related logging. It
displays AP Title, AE Qualifier and Selector information used to diagnose connection problems. Recommended
setting: disabled unless specified by SISCO Technical Support.
ACSEData - ACSEData displays the raw ACSE message (as hex bytes). This is normally only useful for diagnosing
ACSE encoding or decoding problems. Recommended setting: Disabled unless specified by SISCO Technical
Support.
REDUNDANCYLOGMASKS
RplFlow - This log mask is used to show redundancy link flow and audit tracing in AX-S4 ICCP. Recommended
setting: disabled.
IrControl - This log mask will track redundancy mode changes, CRC match information and RPL/heartbeat
timeouts. Recommended setting: disabled.
IrFlow - This log mask will track redundancy transactions. Recommended setting: disabled.
IrData - This log mask will track redundancy data synchronization. This is useful to troubleshoot problems in Data
Synchronization. Recommended setting: disabled.
ACSELOGMASKS
AcseEncode
This is used to diagnose ACSE layer problems in encoding. It is generally not used by customers. Recommended
setting: Disabled unless specified by SISCO Technical Support.
204
AcseDecode - This is used to diagnose ACSE layer problems in decoding. It is generally not used by customers.
Recommended setting: Disabled unless specified by SISCO Technical Support.
SOCKETLOGMASKS
Flow - This is used to diagnose flow control in the socket layer. Recommended setting: Disabled unless specified by
SISCO Technical Support.
Transmit - This logging shows Redundancy data being transmitted at the TCP socket layer. Normally when its
enabled and nothing is logged, Redundancy is misconfigured or the Windows Firewall is on without an exception
configured for the Redundancy port. This is used to diagnose transmit messages in the socket layer. Recommended
setting: Disabled unless specified by SISCO Technical Support.
Receive - This logging shows Redundancy data being received at the TCP socket layer. Normally when its enabled
and nothing is logged, Redundancy is misconfigured or the Windows Firewall is on without an exception configured
for the Redundancy port. This is used to diagnose receive messages in the socket layer. Recommended setting:
Disabled unless specified by SISCO Technical Support.
SXLOGMASKS
Decode - This is used to diagnose something decode problems when parsing xml data. Recommended setting:
Disabled unless specified by SISCO Technical Support.
ASN.1LOGMASKS
Encode - This logging displays encoding of a PDU at the ASN.1 level. The SISCO ASN.1 encoder builds from back to
front. Recommended setting: Disabled unless specified by SISCO Technical Support.
Decode - This logging displays ASN.1 decode information such as parsing class, form, tag, length, and contents.
Recommended setting: Disabled unless specified by SISCO Technical Support.
SECURITYLOGMASKS
This logging is used for the SISCO add-on toolkit only and is provided in separate documentation. If the Security
Extensions is not installed, no logging is generated.
AX-S4 ICCP LOG CONFIGURATION XML FILE

Below is the sample default file. This file can be edited without using the Log Configuration Editor.
<?xml version="1.0" encoding="UTF-8"?>

<LOG_CFG>
<LogControl>
<LogCommon>
<LogElapsedTime>Off</LogElapsedTime>
</LogCommon>
205
<LogFileAttributes>
<LogFileEnable>On</LogFileEnable>
<LogFileName>Axs4Iccp.log</LogFileName>
<LogFileSize>10000000</LogFileSize>
<DestroyOldFile>Off</DestroyOldFile>
<HardFlush>Off</HardFlush>
</LogFileAttributes>
<LogIpcAttributes>
<LogIpcAppId>AX-S4 ICCP</LogIpcAppId>
<LogIpcMaxQueCount>10</LogIpcMaxQueCount>
<LogIpcListenEnable>Off</LogIpcListenEnable>
<LogIpcListenPort>21016</LogIpcListenPort>
<LogIpcNumListenPorts>1</LogIpcNumListenPorts>
<LogIpcMaxListenConn>1</LogIpcMaxListenConn>
<LogIpcCallEnable>On</LogIpcCallEnable>
<LogIpcCallingPort>21001</LogIpcCallingPort>
<LogIpcCallingIp>127.0.0.1</LogIpcCallingIp>
<LogIpcCallingBackoff>500</LogIpcCallingBackoff>
<LogIpcSmartMode>On</LogIpcSmartMode>
<LogIpcEditLogCfg>On</LogIpcEditLogCfg>
<LogIpcSealMode>2</LogIpcSealMode>
<LogIpcSealTimeWindow>30</LogIpcSealTimeWindow>
</LogIpcAttributes>
</LogControl>
<LogMasks>
<Axs4IccpLogMasks>
<Flow>Off</Flow>
<ICCP>Off</ICCP>
<OPC>Off</OPC>
<OPCData>Off</OPCData>
</Axs4IccpLogMasks>
<MiLogMasks>
<Flow>Off</Flow>
<Addressing>Off</Addressing>
<Discovery>Off</Discovery>
<Configuration>Off</Configuration>
</MiLogMasks>
<MmsLogMasks>
<Client>Off</Client>
<Server>Off</Server>
</MmsLogMasks>
<MvlLogMasks>
<Flow>Off</Flow>
<ACSE>Off</ACSE>
<ACSEData>Off</ACSEData>
</MvlLogMasks>
206
<RedundancyLogMasks>
<RplFlow>Off</RplFlow>
<IrControl>Off</IrControl>
<IrFlow>Off</IrFlow>
<IrData>Off</IrData>
</RedundancyLogMasks>
<AcseLogMasks>
<AcseEncode>Off</AcseEncode>
<AcseDecode>Off</AcseDecode>
</AcseLogMasks>
<SocketLogMasks>
<Flow>Off</Flow>
<Transmit>Off</Transmit>
<Receive>Off</Receive>
</SocketLogMasks>
<SxLogMasks>
<Flow>Off</Flow>
<Decode>Off</Decode>
</SxLogMasks>
<Asn1LogMasks>
<Encode>Off</Encode>
</Asn1LogMasks>
<SecurityLogMasks>
<SecFlow>Off</SecFlow>
<SecData>Off</SecData>
<SSleFlow>Off</SSleFlow>
<SSleData>Off</SSleData>
<Encode>Off</Encode>
</SecurityLogMasks>
<SscLogMasks>
<Flow>Off</Flow>
</SscLogMasks>
</LogMasks>
</LOG_CFG>
207
APPENDIX B: TROUBLESHOOTING
This appendix lists some common problem with AX-S4 ICCP and recommendations to solve these issues.
PROBLEMS IN INSTALLATION
Any time there is a problem during the installation process of AX-S4 ICCP, please enter a ticket and submit the
following log file: C:\ProgramData\SISCO\Installation Log\SISCO_Installer_Log.log. Please include the Operating
System and Service Pack.
PROBLEMS ESTABLISHING AN ASSOCIATION
If AX-S4 ICCP cannot establish an association with a remote control center that has been configured, the following
steps should be taken in this order:
1. Ping the IP address of the remote control center.

2. Telnet to port 102 to verify that the port is open.
3. Check the configured values for AP Title, AE Qualifier, PSEL, SSEL, and TSEL parameters in the addressing
form. These parameters must be consistent with data at the remote control center in order to establish an
association.
4. Check the configured values for Bilateral Table ID, Local Domain, and Remote Domain parameters in the
association form. These fields must be consistent with data at the remote control center in order to establish
an association. A common problem is reversing the Local and Remote Domain names.
RPL CONFIGURATION ISSUES
If RPL log masks are turned on using either the Log Configuration Editor or the ICCP Monitor, RPL Configuration
Seal errors are listed in the axs4iccp.log file with a numeric number. Below is a description of possible RPL error
codes:
#define S_SEAL_KEYSEL 1
#define S_SEAL_BUFSIZE_REMAINDER 2
#define S_SEAL_ECRC_MISMATCH 3
#define S_SEAL_CRC_MISMATCH 4
#define S_SEAL_DATA_CRC_MISMATCH 5
#define S_SEAL_TIME_WINDOW 6
A common error is shown in the log file below. It indicates that there is a time discrepancy between the Primary
and Secondary AX-S4 ICCPs. This indicates that the PC clocks on both machines are out of time sync by more than
the 30 second default RPL heartbeat rate:
2009-11-03 09:14:05.734 RPL_LOG_ERR (rpl.c 1246)

RPL Authentication Failure, Seal: 6, Disabling
2009-11-03 09:14:05.734 RPL_LOG_ERR (rpl.c 828)
Message integrity checks failed
This is the most common RPL error.
208
HOW TO DETERMINE CURRENT VERSION
The AX-S4 ICCP version is important in diagnosing any technical issue. The AX-S4 ICCP product has many
components. Versions of these different components may not be the same. We do not track software by the ICCP
Configuration Utility, ICCP Monitor, SNAP-Lite, or the OPC Client versions. SISCO needs the current version of AX-
S4 ICCP (not the components). There are two ways to determine current version.
If the AX-S4 ICCP GUI can be invoked. If using rdp, this option is not possible. Select Help – About. The following
screen is displayed:
The other option is the registry settings. Open regedit. Go to

HKLM\Software\WOW6432Node\SISCO\AX-S4 ICCP \CurrentVersion
209
ERROR – UNABLE TO CREATE DATASET
When encountering the following error in the axs4iccp.log file:
Unable to create Data Set 'DataSet1' on Link 'PrimaryLinkA'

MMS Error: Definition, Object Undefined
This caused when creating manual data sets that do not match either the names, scopes, or data types on the
server. The result is the process of removing all of the data values from a data set causing the data set to be
invalid. AX-S4 ICCP does not tolerate empty data sets. Unfortunately the logging message does not completely
point in the right direction to resolve the issues except to start kicking out the bad points from the data set until
nothing is left at which point the connection is dropped. So the recommendation is as follows:
1. Check for valid DataValue name. Make sure of spellings and case sensitivity.
2. Check for valid DataType. Make sure that the DataType is the same for both the local and remote control
centers.
210
APPENDIX C: REGISTRY PARAMETERS
AX-S4 ICCP REGISTRY PARAMETERS.
Under the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SISCO\AX-S4 ICCP\CurrentVersion\AXS4ICCP:
AutoAckOperate This feature automatically responds to device Operate Indications. This means that AX-S4 ICCP
will automatically respond to incoming device operate requests for local devices when an OPC Client is not
monitoring the OPC Operate items associated with the device. This feature is enabled/disabled using a registry
parameter. Values are:
None: user must send response.

Subscribed: automatically send a success response if an OPC Client subscribes to the device
operate attributes.
Always: always send a success response to device operate indications.
Note: This only applies to local device operate requests. Select, GetTag, and SetTag requests are not affected.
IccpStateNativeConversion - Allow values (int16 or bool) to convert properly in AX-S4 ICCP. Currently boolean
(true/false) values are auto converted to ensure that values such as 0 and 1 are converted to 1 and 2 in AX-S4 ICCP.
It also allows 1 and 2 values to be converted to 0 and 1 values for some systems. Values are:
autoconvert = 0 (no conversion) Default
autoconvert = 1 (converts 0 and 1 to 1 and 2)
autoconvert = 2 (converts 1 and 2 to 0 and 1)
The following tables describe the modes and how they are used with Booleans (Bool) or Integers (Int16).
OPC as Boolean OPC Value OPC Quality ICCP Value ICCP Quality Comment
OPC to ICCP
0 Good 1 Good
1 Good 2 Good
ICCP to OPC
0 Good N/A Invalid Can’t map this
1 Good 0 Good
2 Good 1 Good
OPC as Integer OPC Value OPC Quality ICCP Value ICCP Quality Comment
OPC to ICCP
0 Good N/A N/A OPC Write Fails
1 Good 0 Good
2 Good 1 Good
Other Good N/A N/A OPC Write Fails
ICCP to OPC
0 Good 1 Good
1 Good 2 Good
2 Good N/A Invalid
3 Good N/A Invalid
Table 23: Autoconvert = 1
211
OPC as Boolean OPC Value OPC Quality ICCP Value ICCP Quality Comment
OPC to ICCP
0 Good 1 Good
1 Good 2 Good
ICCP to OPC
1 Good 0 Good
2 Good 1 Good
OPC as Integer OPC Value OPC Quality ICCP Value ICCP Quality Comment
OPC to ICCP
0 Good 1 Good
1 Good 2 Good
Other Good N/A N/A OPC Write Fails
ICCP to OPC
0 Good N/A Invalid
1 Good 0 Good
2 Good 1 Good
3 Good N/A Invalid
Table 24: Autoconvert = 2
ICCPStatePolarity Switch - ICCP State bits are mapped to OPC Boolean where 1 is OFF and 2 is ON per tables in
clause 8.1 of IEC 60870-6-802. This flag controls the polarity of the mapping globally within AX-S4 ICCP.
MinGroupUpdateRate - Default minimum OPC group update rate. Default is 100 ms. OPC Groups will a group
update rate of 0 will pass on all reported data immediately. All other data in the group wil be updated at the
MinGroupUpdate.
MinKeepAlive - Default minimum keep alive. Default is 100 ms. SetKeepAlive is part of the OPC 3.0 interface.
When called it forces a call to the clients OnDataChange every keepAlive msec even if the data does not change.
This allows the client to verify the health of their callback connection. If the OPC client calls SetKeepAlive with
keepAlive les than MinKeepAlive the call will fail and an error is logged.
SetDataValueValueOnly - If this is set to 1 any remote data value writes will only send the write request to the
remote control center after the value is written. Changes to the timestamp or quality will not trigger a write.
UseLegacyQualityMappings - A flag used to indicate whether to use legacy quality mappings. If set to 1, ICCP
quality will be converted to OPC quality based on the parameters on the OPC Parameters page of the ICCP
Configuration Utility. If set to 0, the quality will be converted based on the Axs4IccpQualityMap.csv file.
212
Under the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SISCO\AX-S4 ICCP\CurrentVersion\Tuning:
DataThreadPriority - The thread priority for the AX-S4 ICCP database thread. A Data Thread has been added to
handle remote data validation data base activity. The ‘Data Thread’ has a lower priority that allows ICCP and OPC
activity to be unaffected by the data base resource requirements.The default is
THREAD_PRIORITY_BELOW_NORMAL (-1).
MinWaitService - Default Value 200. This is the number o msec the ICCP thread will wait before servicing the
outgoing DSTS. This should only be modified if the DSTS are not going out in a timely manner.
SISCO STACK REGISTRY PARAMETERS
This section describes SISCO Stack Registry parameters.
Under the HKEY_LOCAL_MACHINE\SOFTWARE\SISCO\

Network\ CurrentVersion\Parameters
and
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SISCO\
Network\ CurrentVersion\Parameters:
SharedMemMode - parameter is used in run-time reconfiguration. It can have following values:
21 User Mode
42 Global Mode (the name of shared memory file is pre-pended with “Global\\”).
This is the default setting after SNAP-Lite installation.
UseCfgFile - Indicates if the siscostackcfg.xml file is being used to configure SISCO Stack parameters. The default is
1. All other values are invalid at this time.
213
APPENDIX D: SISCO STACK CONFIGURATION
ALL NECESSARY ADDRESSING INFORMATION IS HANDLED THROUGH THE ICCP CONFIGURATION UTILITY AND
AUTOMATICALLY SYNCHRONIZED WITH ADDRESSING FOUND IN THE SISCOSTACKCFG.XML. It is recommended
to not modify the xml file directly.
The Security Configuration Utility option is only available with AX-S4 ICCP Secure.
SAMPLE SISCO STACK CONFIGURATION FILE

This example shows the default configuration supplied for the product. It includes communication parameters as
well as sample AR Names used in the sample programs for non-secure communication. Secure version of this
configuration is described in the Installation and Configuration Guide – SISCO Security Extensions for AX-S4 ICCP.
<?xml version="1.0" encoding="UTF-8" ?>


<STACK_CFG>



<LeanT_Profile_List>
<LeanT_Profile>

<Name>SNAP</Name>
<Session_Disconnect_Timeout>60</Session_Disconnect_Timeout>
<Tcp_Max_Tpdu_Len>65531</Tcp_Max_Tpdu_Len>
<Tcp_Max_Spdu_Outstanding>50</Tcp_Max_Spdu_Outstanding>
<Tcp_Listen_Port>102</Tcp_Listen_Port>
<Tcp_Max_Idle_Time>0</Tcp_Max_Idle_Time>
<Gensock_Wakeup_Port_Base>20300</Gensock_Wakeup_Port_Base>
<Gensock_Wakeup_Port_Range>100</Gensock_Wakeup_Port_Range>
</LeanT_Profile>
<LeanT_Profile>

<Name>default</Name>
<Session_Disconnect_Timeout>60</Session_Disconnect_Timeout>
<Tcp_Max_Tpdu_Len>65531</Tcp_Max_Tpdu_Len>
<Tcp_Max_Spdu_Outstanding>50</Tcp_Max_Spdu_Outstanding>
<Tcp_Max_Idle_Time>0</Tcp_Max_Idle_Time>
<Tcp_Event_Wakeup_Port_Base>56000</Tcp_Event_Wakeup_Port_Base>
<Tcp_Event_Wakeup_Port_Range>100</Tcp_Event_Wakeup_Port_Range>
<Gensock_Wakeup_Port_Base>20300</Gensock_Wakeup_Port_Base>
<Gensock_Wakeup_Port_Range>100</Gensock_Wakeup_Port_Range>
</LeanT_Profile>
</LeanT_Profile_List>



<Security_Profile_List>
<Security_Profile>
<Secure>No</Secure>
</Security_Profile>
214
<Security_Profile>
<Name>No Security</Name>
<Secure>No</Secure>
</Security_Profile>
<Security_Profile>
<Name>SNAP</Name>
<Secure>No</Secure>
<Encrypt_Req_Called>No</Encrypt_Req_Called>
</Security_Profile>
</Security_Profile_List>



<AR_Matching_Profile_List>
<AR_Matching_Profile>
<Allow_Missing_AE>No</Allow_Missing_AE>
<Allow_Extra_AE>Yes</Allow_Extra_AE>
<Match_AP_Title>Yes</Match_AP_Title>
<Match_AE_Qualifier>Yes</Match_AE_Qualifier>
<Match_AP_Invoke>No</Match_AP_Invoke>
<Match_AE_Invoke>No</Match_AE_Invoke>
<Match_PSEL>Yes</Match_PSEL>
<Match_TSEL>Yes</Match_TSEL>
<Match_SSEL>Yes</Match_SSEL>
<Match_IP_Address>No</Match_IP_Address>
<Host_Name_Support>No</Host_Name_Support>
</AR_Matching_Profile>
</AR_Matching_Profile_List>



<App_SNAP>
<Max_Users>5</Max_Users>
<Max_Binds_Per_User>32</Max_Binds_Per_User>
<IPC_Port>10044</IPC_Port>

<IPC_Domain_Socket_Path>/tmp</IPC_Domain_Socket_Path>
<IPC_Timeout>25000</IPC_Timeout>
<CPU_Affinity>0x00000003</CPU_Affinity>
</App_SNAP>



<AR_Name_List>
<AR_Name>
<Name>SiteA</Name>
<Description>for compatability with older DIBS</Description>
<AP_Title>1 3 9999 2</AP_Title>
<AE_Qualifier>2</AE_Qualifier>
<PSEL>00 00 00 05</PSEL>
<SSEL>00 01</SSEL>
<TSEL>00 01</TSEL>
<IP_Address>127.0.0.1</IP_Address>
<Authentication_Mode>AE Title</Authentication_Mode>
</AR_Name>
<AR_Name>
215
<Name>SiteB</Name>
<Description>for compatability with older DIBS</Description>
<AP_Title>1 3 9999 1</AP_Title>
<AE_Qualifier>1</AE_Qualifier>
<PSEL>00 00 00 06</PSEL>
<SSEL>00 01</SSEL>
<TSEL>00 01</TSEL>
<IP_Address>127.0.0.1</IP_Address>
<Authentication_Mode>AE Title</Authentication_Mode>
</AR_Name>
</AR_Name_List>




<App_Network_List>
<App_Network>
<App_Name>Common Application Settings</App_Name>
<LeanT_Profile>default</LeanT_Profile>
<Security_Profile>default</Security_Profile>
<AR_Matching_Profile>default</AR_Matching_Profile>
</App_Network>
<App_Network>
<App_Name>MMS-DEMO Instance1</App_Name>
<App_AR_Name_List>
<App_AR_Name Role="Local">SiteA</App_AR_Name>
<App_AR_Name Role="Remote">SiteB</App_AR_Name>
</App_AR_Name_List>
</App_Network>
<App_Network>
<App_Name>MMS-DEMO Instance2</App_Name>
<App_AR_Name_List>
<App_AR_Name Role="Local">SiteB</App_AR_Name>
<App_AR_Name Role="Remote">SiteA</App_AR_Name>
</App_AR_Name_List>
</App_Network>
<App_Network>
<App_Name>SNAP-Lite</App_Name>
<LeanT_Profile>SNAP</LeanT_Profile>
<Security_Profile>SNAP</Security_Profile>
</App_Network>
<App_Network>
<App_Name>UtilitySiteA</App_Name>
<App_AR_Name_List>
<App_AR_Name Role="Local">SiteA</App_AR_Name>
<App_AR_Name Role="Remote">SiteB</App_AR_Name>
</App_AR_Name_List>
216
<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>
<App_Network>
<App_Name>UtilitySiteB</App_Name>
<App_AR_Name_List>
<App_AR_Name Role="Local">SiteB</App_AR_Name>
<App_AR_Name Role="Remote">SiteA</App_AR_Name>
</App_AR_Name_List>
<Max_Mms_Pdu_Length>32000</Max_Mms_Pdu_Length>
<Max_Calling_Connections>2</Max_Calling_Connections>
<Max_Called_Connections>0</Max_Called_Connections>
</App_Network>
</App_Network_List>
</STACK_CFG>
DESCRIPTION OF SISCO STACK CONFIGURATION XML FILE
This section describes the parameters of the configuration file siscostackcfg.xml. This explanation is subset of all
possible parameters, the Security Extensions for AXS4-ICCP documentation describes additional security
parameters. Please see Addressing Issues for a description of the various layers in the stack.
Note: Most of the required configuration, like AR Names in the AR_Name_List and App_Network_List is done
through the ICCP Configuration Utility interface and saved in the siscostackcfg.xml file. There is no other
GUI interface for non-secure AX-S4 ICCP parameters in the siscostackcfg.xml. If any changes in
LeanT_Profile or App_SNAP sections are required from assumed defaults they can be made manually by
editing the XML file.
LEANT_PROFILE SECTION
This section describes subsets of Transport parameters needed for a user application and the SNAP-Lite. Multiple
LeanT_Profile sections may be present within the LeanT_Profile_List. The SNAP-Lite LeanT_Profile parameters
should encompass the highest values of all LeanT_Profiles. At least one LeanT_Profile needs to be configured for
user applications. The “default” profile can be used by any application unless custom parameters are required.
Name - This is the LeanT_Profile user defined name. Maximum Name length is 255 characters. This parameter is
mandatory.
Session_Disconnect_Timeout - Session disconnect timeout is the maximum time interval that the Transport
Protocol will wait for a T-Disconnect Indication (Transport layer) from remote node before all connection resources
are released. If this optional parameter is not configured, then the default value is 60 seconds.
Tcp_Max_Tpdu_Len - Maximum length of a Transport PDU. Valid values are: 128, 256, 512, 1024, 2048, 4096,
8192 and 65531. Some applications could benefit from higher TPDU size, preventing segmentation of MMS PDUs.
On the other side, retransmission of big TPDUs may substantially degrade throughput. This Transport parameter is
negotiated during connection establishment phase.
217
SNAP-Lite accepts a transport connection and waits for a P-CONNECT PDU (Presentation layer) before the
connection can be passed to an application. For this reason, the most flexible max TDPU size for SNAP-Lite is
65531. If both sides negotiate this TPDU size, then the MMS PDUs will be segmented only by the TCP/IP protocol. If
the remote node proposes different transport PDU size then SNAP-Lite will accept this new max TPDU size. The
provided sample SISCO Stack Configuration file (siscostackcfg.xml) uses 65531 for the max TPDU size. If this
optional parameter is not configured, then the default value is 1024.
Tcp_Max_Spdu_Outstanding - Maximum number of Session PDUs queued at a lower level before they can be
transmitted on the socket. This parameter is used for sending flow control, thus preventing the application from
potentially creating unbounded send queues on active connections. The receiving flow control is done internally
using arbitrary parameters. If this optional parameter is not configured, then the default value is 50.
Tcp_Listen_Port - This parameter is used only by the SNAP-Lite to open a TCP listening port. During testing this
port could be configured to any desirable values, and any remote nodes would need to provide this port along with
the IP Address. If this optional parameter is not configured, then the default value is 102 (port designated for
RFC1006).
Tcp_Max_Idle_Time - Maximum time, in seconds, a TCP connection can be idle before it is disconnected.
All TCP connections are set with the SO_KEEPALIVE option. It means that the socket will be kept alive for extended
period of time even if an application does not transfer any data. The default value of the idle time is operating
system dependent and usually is set to a default of 120 minutes (on Windows it is the KeepAliveTime system
registry parameter). If a system-wide change of this parameter to a lower value is not advised since all applications
must use this timer, a user application can be configured to abort inactive TCP connections by using the
Tcp_Max_Idle_Time parameter. To prevent too much program overhead doing “unproductive” work, the socket
activity will be checked about every 30 seconds. If this optional parameter is not configured, then the default value
is 0 (no checking for idle time is performed).
Tcp_Event_Wakeup_Port_Base (not available for AX-S4 ICCP) - This parameter designates base port for a pool of
ports reserved for applications for internal events notification from SISCO Stack lower layer thread. The SISCO
Stack uses multithreaded processing to interface with sockets. This requires signaling between SISCO Stack thread
and an application main thread to indicate communication events. An internal socket connection is used for this
purpose. Every application will use one port for a wakeup socket for events notification on all TCP/IP connections.
This is the mms_event_fd that application will add to its select statement. If this optional parameter is not
configured, then the default value is 56000.
Tcp_Event_Wakeup_Port_Range (not available for AX-S4 ICCP) - This parameter designates a range of ports,
starting at the base port, used by applications for internal events notification from the SISCO Stack lower layer
thread. The port range should be set to the maximum number of applications and application instances planned to
run on a system. If this optional parameter is not configured, then the default value is 100.
Gensock_Wakeup_Port_Base - This parameter designates a base port for a pool of ports reserved by applications
for internal events notification from the application to SISCO Stack lower layer thread. The SISCO Stack utilizes
multithreaded processing to interface with sockets. This requires signaling between an application main thread
and the SISCO Stack thread to indicate communication events. An internal socket connection is used for this
purpose. The SISCO Stack thread will use one wakeup port for the events notification from application on all TCP/IP
connections. If this optional parameter is not configured, then the default value is 20300.
Gensock_Wakeup_Port_Range - This parameter designates a range of ports, starting at the base port, used by
applications for internal events notification from application to the SISCO Stack lower layer thread. The port range
should be set to the maximum number of applications and application instances planned to run on a system. If this
optional parameter is not configured, then the default value is 100.
218
SECURITY_PROFILE SECTION
This section allows configuring a list of Security profiles restricting the application connectivity. Multiple
Security_Profile configurations may be present within the Security_Profile_List section. At least one
Security_Profile needs to be configured. For a non-secure application, the “default” Security_Profile provided in
the sample configuration file is sufficient.
Name - This is a name given to the Security_Profile. The maximum length of the Name is 255 characters. This
parameter is required.
Secure - For non-secured connections, the only valid value is No. This parameter is required.
AR_MATCHING_PROFILE SECTION
This section allows to list criteria for matching connecting remote node with configured AR Names. Multiple
AR_Matching_Profile configurations may be present within the AR_Matching_Profile_List section. This section
may be empty since AX-S4 ICCP is ignoring these parameters. Matching parameters for AX-S4 ICCP Local/Remote
Control Centers are configured through the ICCP Configuration Utility (see AX-S4 ICCP Identification Parameters).
Name - This is a name given to the AR_Matching_Profile. The maximum length of the Name is 255 characters.
This parameter is required.
AE Allow Missing - When this parameter is set to No, all AE Title elements that are configured (locally) for the AR
Name must be present in the Calling and Called AE Titles. When set to Yes, any AE elements not sent by the
Remote are treated as present and matched, regardless of whether they are configured for the AR Name. If this
optional parameter is not present, the default is No. This is available in the ICCP configuration Utility under the
Identification form.
AE Allow Extra - When this parameter is set to Yes, it is acceptable for the Remote Control Center to send AE
elements that are not configured for the AR Name. When set to No, all AE Title elements that are NOT configured
(locally) for the AR Name must NOT be present in the Calling and Called AE Titles. If this optional parameter is not
present, the default is Yes.
Remote Address Matching - Following parameters may be used in remote node address matching: AP Title, AE
Qualifier, AP Invoke, AE Invoke, PSEL, SSEL, TSEL, and IP Address. If a matching parameter is set to Yes, then the
value received in the Associate Indication must match the configured (locally) value of that parameter.
If some optional parameters are not configured in the AR_Matching_Profile, they default to values shown below:
Remote Address Matching Parameters Default
Match_AP_Title YES
Match_AE_Qualifier YES
Match_AP_Invoke NO
Match_AE_Invoke NO
Match_PSEL YES
Match_SSEL YES
Match_TSEL YES
Match_IP_Address NO
Host_Name_Support NO
Table 25: Remote Address Matching Parameters
219
APP_SNAP SECTION
This section describes parameters that are used by SNAP-Lite. Although this section is optional in the parser, the
startup of SNAP-Lite will fail if this section is not present.
Max_Users - This parameter is used to set the maximum number of user applications that will be communicating
with SNAP-Lite. Each application instance counts as a new user. If this optional parameter is not configured, then
the default value is 64 user applications.
Max_Binds_Per_User - This parameter is used to configure the maximum number of binds that an application may
issue. The bind operation is known as an “activation of a Local AR Name” in an application. If this optional
parameter is not configured, then the default is 64 binds per each user application.
IPC_Port (Windows only) - The IPC port is used by SNAP-Lite to listen for internal TCP connections from
applications. The purpose is to perform an Inter Process Communication (IPC) between an application and SNAP-
Lite. See Wiki Inter-process communication - http://en.wikipedia.org/wiki/Inter-process_communication If this
optional parameter is not configured, then the default IPC port is 10044.
IPC_Domain_Socket_Path (not applicable for AX-S4 ICCP) - This is the path to the SNAP-Lite IPC directory. This
path is used to create an Inter Process Communication (IPC) file for communication between SNAP-Lite and an
application. If this optional parameter is not configured, then the default IPC directory is /tmp.
IPC_Timeout - The IPC timeout parameter specifies the wait time for an IPC message. Normally, the IPC processing
is very fast. However, there may be times when IPC operation would need to be aborted due to the IPC timeout in
order to make resources available for other operations. If this optional parameter is not configured, then the
default timeout is 1000 ms.
AR_NAME SECTION
This section allows configuring local and remote nodes addresses. AR Names configured in this section may be
used as a Local or Remote AR Names. The choice is being made in the App_Network Section. Multiple AR_Name
configurations may be present within the AR_Name_List section. Although this section is optional in the parser
there should be some AR Names configured for an application.
Selector sets in Local AR Names must be unique across all applications registering with SNAP-Lite. SNAP-Lite keeps
table of all registered selector sets. When selectors are decoded in an incoming connection, SNAP-Lite performs
look up in the table and passes the connection to an application that registered decoded selectors.
Name - This is a name given to an aggregate of attributes describing communication parameters for a local or
remote node on a network. The maximum length of AR Name is 64 characters. This parameter is required.
Description - This is a description for the AR Name. This parameter is ignored. This is an optional parameter.
AP_Title - This is the AP Title, in the form of an MMS Object Identifier, assigned by the network naming authority,
representing the Application Process Title for a particular application process. An Object Identifier is a sequence of
up to sixteen 16-bit integer values representing an application in the OSI Model. The first value in the AP Title
should be 1 (ISO) (the valid range is 0 to 2). The second value should be 1, 2, or 3 (the valid range is 0 to 39). The
third value is open for international assignment. If addressing is local, then this value should be 9999. The rest of
the values are arbitrary. For example, values could be assigned to represent type and location of the application.
This parameter is optional.
220
AE_Qualifier - This is the AE Qualifier. This is a 32-bit integer value used to qualify the Application Entity. This
parameter is optional.
PSEL - This is the Presentation Selector. The maximum PSEL size is 16 octets (32 ASCII encoded hex digits). This
selector can be empty (<PSEL></PSEL>). If this parameter is not present then it is assumed to be an empty selector.
There can be only one AR Name with all empty selectors. This parameter is optional.
SSEL - This is the Session Selector. The maximum SSEL size is 16 octets (32 ASCII encoded hex digits). This selector
can be empty (<SSEL></SSEL>). If this parameter is not present then it is assumed to be an empty selector. There can
be only one AR Name with all empty selectors. This parameter is optional.
TSEL - This is the Transport Selector. The maximum TSEL size is 32 octets (64 ASCII encoded hex digits). This
selector can be empty (<TSEL></TSEL>). If this parameter is not present then it is assumed to be an empty selector.
There can be only one AR Name with all empty selectors. This parameter is optional.
IP_Address - This is the node’s IP Address given as a dotted decimal or as a host name. If a host name is used, an
internal gethostbyname function call is used to resolve the IP address. This function may not return for a long time
if directory services are not available. If this optional parameter is not present, the local system default IP Address
of 127.0.0.1 is assumed.
TCP_Port - This is the TCP port to which to connect. For testing purposes, the TCP port may be set to a non-default
value, but in a real system it should be set to the default RFC1006 port. If this optional parameter is not present,
then the default RFC1006 port (102) is used.
Authentication_Mode - For non-secured connections, the only valid value is AE_Title. If this optional parameter is
not present, then AE_Title value is assumed.
APP_NETWORK SECTION
This section configures network parameters for user applications. Multiple App_Network configurations may be
present within the App_Network_List section. For every application, one App_Network needs to be configured. If
multiple instances of the same application are possible they may need individual App_Network configuration for
each instance. In addition, the configuration should include the “SNAP-Lite” App_Network.
App_Name - This is a user name given to the application. This name is referenced in an internal
sscConfigAppNetwork function during program initialization. The maximum length of the App_Name is 255
characters. This parameter is required.
LeanT_Profile - This is Name of the LeanT_Profile to be used with the App_Name application. This parameter is
required.
Security_Profile - This is Name of the Security_Profile to be used with the App_Name application. This parameter
is required.
AR_Matching_Profile - This is Name of the AR_Matching_Profile to be used with the App_Name application. This
parameter is optional. This parameter is not needed for the “SNAP-Lite” or AX-S4 ICCP Local Control Centers
App_Network configuration.
App_AR_Name - This is Name of the AR_Name configured in the AR_Name_List to be used with the App_Name
application. The same AR_Name can be used by different applications or their instances, with limitation specified
below. The App_AR_Name specifies Local or Remote role for the AR_Name. There should be at least one Local
App_AR_Name configured for each application. If the same Local AR_Name is used in configuration of multiple
applications then only one application can register (bind) this Local AR_Name with SNAP-Lite at the same time.
221
Registration of an AR Name is necessary only if an application will receive connections. This parameter is not
needed for the “SNAP-Lite” App_Network configuration.
Max_Mms_Pdu_Length (ICCP-LITE product only) - This is the max MMS PDU size.
Max_Calling_Connections (ICCP-LITE product only) - This is the maximum number of calling connection that
application will be allowed to make.
Max_Called_Connections (ICCP-LITE product only) - This is the maximum number of called connections that
application will be allowed to receive.
222
APPENDIX E: RUNNING SNAP-LITE
It is assumed that the SNAP-Lite and configuration files are installed on a target Windows system as described in
the above section. The configuration directory is specified by the Registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\SISCO\Network\CurrentVersion\ConfigPath. If you move the configuration
files from their installed directory, you must change this registry entry to specify the new path.
By default the SNAP-Lite is installed as a Windows Service. The SNAP-Lite Service can be deleted/added from/to
the Windows Services from the Start\All Programs\SISCO\SNAP Lite menu (use “Run As Administrator”). The
service can be started manually or automatically by rebooting the computer. The default SISCO Stack Configuration
(siscostackcfg.xml) file is simple enough to allow the SNAP-Lite to start in a non-secure mode after installation.
After changing the SISCO Stack Configuration file the SNAP-Lite and user applications must be restarted for the
configuration changes to take effect unless reconfiguration feature is available for given parameter.
The SNAP-Lite can be also started from Start menu or a command window although it needs to be first removed
from the Windows Services by running following SNAP Lite Start menu command “Unregister SNAP Lite Service”
with “Run As Administrator” option.
To start the SNAP-Lite process manually use the SNAP-Lite shortcut provided on the Windows Start menu or in a
command window type:
cd <Program Files>\SISCO\Network
snap_l
When SNAP-Lite is started from a command window it detaches itself from the command window and runs in the
background. To stop SNAP-Lite open the Windows Task Manager, find the snap_l.exe in the list of Processes and
select End Process.
To add SNAP-Lite to Windows Services run the SNAP Lite Start menu command “Register SNAP Lite Service” using
“Run As Administrator” option.
To confirm that the SNAP-Lite is running as a service enter Windows Task Manager and find the snap_l.exe name
in the list of Services.
223
The following execution cases of SNAP-Lite and Client/Server applications are supported. One configuration is
excluded due to Windows limitation on passing a TCP handle from SNAP-Lite to a Server application.
Server Application Accepting Connections Client Application Requesting Connections

Service or Service or
Non-Privileged Non-Privileged
Administrator Administrator
SNAP-Lite Service
Yes Yes Yes Yes
or Administrator
SNAP-Lite
No Yes Yes Yes
Non-Priviledged
Table 26: SNAP-Lite Windows Adminstration
SNAP-LITE PARAMETERS
The syntax for the SNAP-Lite on Windows is as follows:
snap_l [parameter=value][parameter]
Multiple parameters should be separated by spaces. Do not use spaces when entering the parameter=value
before or after the ‘=’ character.
On Windows the SNAP-Lite can be started with all default values. This is the recommended way unless there is
need to use some of the optional parameters below.
MAX_TCP_CONS= This limits the number of incoming TCP connections that will be simultaneously handled by
SNAP-Lite. This processing normally is very quick and the default number of 100 simultaneous TCP connections
should be sufficient for most uses.
MAX_PIPELINE= Max number of TCP connections that can be queued to user application in SNAP-Lite.
Default value is 10.
MAX_CON_TIME= Max number of milliseconds that SNAP-Lite will allow for processing of an incoming TCP
connection (reception of TPDU-CR, P-CONNECT SPDU and passing connection info to user application). Default is
60000 ms.
MEM_DEBUG This sets the m_mem_debug flag to SD_TRUE in the SNAP-Lite. A list of allocated memory pointers will be
maintained to detect memory overwrites and invalid calls to the chk_free function. There will be slight overhead
in program execution and memory usage, but this setting will help to detect memory problems before they cause
serious problems. This is the default setting compiled into SNAP-Lite.
If there is a need to troubleshoot memory, then this parameter along with additional memory debugging options
added to the snaplogcfg.xml can help to diagnose problems.
MEM_DEBUG_OFF This allows for disabling the m_mem_debug flag in the extreme case that the SNAP-Lite needs
extra performance.
SSLE_MEM_DEBUG Set flag used to allow track the SSL Engine memory in SNAP-Lite. This is the default setting
compiled into the SSL Engine.
SSLE_MEM_DEBUG_OFF This allows for disabling the m_mem_debug flag in the extreme case that the SSL Engine
needs extra performance.
224
RUN-TIME RECONFIGURATION
Some of the configuration parameters can be updated while SNAP-Lite and AX-S4 ICCP are running. The ICCP
Configuration provides the ability to Reload Stack Configuration from the Tools menu.
This allows a run-time reload of any changes into the SNAP-Lite and AX-S4 ICCP. The changes will replace or be
merged with existing parameters in memory.
The state of the configuration notification event is stored in shared memory created by SNAP-Lite during
initialization. Depending on how SNAP-Lite is started with or without elevated privilages the shared memory needs
to be created in a global context or in logged user context respectively. To coordinate access to the shared
memory by SNAP-Lite and by AX-S4 ICCP, a registry parameter SharedMemMode” was created under the
following path:
On Windows 2003 (32-bit)

\HKEY_LOCAL_MACHINE\ SOFTWARE\SISCO\Network\CurrentVersion\Preferences\
The Stack Configuration Utility is provided with AX-S4 ICCP Secure only.
On Windows 2008 R2 or Windows 7

\HKEY_LOCAL_MACHINE\ SOFTWARE\SISCO\Network\CurrentVersion\Preferences\
if 64-bit version of SNAP-Lite was installed on 64-bit Windows OS (the default case)
or
\HKEY_LOCAL_MACHINE\ SOFTWARE\Wow6432Node\SISCO\Network\CurrentVersion\Preferences\
if 32-bit version of SNAP-Lite was installed on 64-bit Windows OS
The SharedMemMode parameter can have following values:

21 User Mode
42 Global Mode (the name of shared memory file is pre-pended with “Global\\”). This is the default setting
after SNAP-Lite installation.
Here are guidelines on what stack configuration parameters can be updated during run-time.
Configuration Parameters Update Existing Add New
AR Names Yes (partial) See Note 1 Yes
Application Network Parameters Yes (partial) See Note 2 N/A

Table 27: Stack Configuration Parameters Modifiable During Runtime
Note 1: Local AR Names that are used by an application will not be updated.
Remote AR Names will be updated.
New Local/Remote AR Names can be added.
Note 2: Following App_Network parameters can be updated:

Local or Remote App_AR_Name can be added.
Security related parameters are described in the documentation accompanying Security product.
225
APPENDIX F: ADDRESSING TERMINOLOGY
This section explains the addressing scheme from the network and programmatic points of view. This appendix is
technical and may not be necessary for most users to understand.
PRESENTATION ADDRESS
In order for one ICCP application to establish a connection to another ICCP application, the initiating node must
know the address of the node with which it intends to communicate. This address is called the Presentation
Address and is comprised of the Presentation Selector, Session Selector, Transport Selector, and the IP Address.
Selectors are octet strings that can be assigned arbitrarily. IP Address is configured for a TCP/IP network. The
sequence of selectors and IP Addresses defines a branch through the Stack address tree. Please consult the
Wikipedia article http://en.wikipedia.org/wiki/OSI_protocols for information on the seven layer model.
To be able to use the SISCO Stack, the application must first bind to it. This is done by activating a Presentation
Address. This creates a new branch (path) in the address tree. Once the presentation address is successfully
registered (bound), the application is ready to receive connect requests using the newly activated path.
When an ICCP application attempts to establish a connection, it issues a connect request that contains the
presentation address of the application intended to receive the request. Upon receipt of the connect request, the
remote stack examines the selectors present in the request. If it finds a branch in its address tree with matching
selectors, the connect request is passed to the application that registered the branch. Otherwise, the connection is
rejected.
ACSE PARAMETERS
ACSE (Association Control Service Element) is used to establish an association between two ICCP programs. In
some situations, as in the case of secure systems, it may be necessary for the called application to know the
identity of the caller. In others, as in the case of ICCP-based gateways, the identity of the destination must be
known.
To provide and/or examine such information, ACSE offers a set of parameters that the application can send and
receive. These parameters are Application Process Title (AP Title), Application Entity Qualifier (AE Qualifier),
Application Process Invocation Identifier (AP Invoke ID), and Application Entity Invocation Identifier (AE Invoke ID).
These parameters are optional and their use is strictly application-specific. See the Application Level Addressing
section for more information on the format of the ACSE parameters.
AR NAMES
SISCO’s ICCP/MMS applications define the term “Application Reference Name”, or “AR Name”. An AR Name is an
ASCII string of up to 64 characters used to collectively identify Application Entity information (AP Title and AE
Qualifier) and the Presentation Address associated with an application. In other words, an AR Name is not
something that is exchanged between two applications over the network, but rather a human-readable shorthand
for the ACSE and addressing information that it represents.
226
ADDRESSING CONCEPTS
This section is intended to give insight into how Application Level addressing works.
The Seven Layer Stack is shown below. Oval accesses are shown between the adjacent layers represent the Service
Access Points (or SAPs). A SAP can be viewed as a channel through which one layer provides a set of services (such
as connection management and data transfer) to the layer immediately above it. A SAP is similar to a TCP/IP socket
as defined by BSD (Berkeley Software Distribution).
Psel AX-S4 ICCP Psel

MMS
ACSE
PSAP PSAP
Ssel Ssel
Presentation
Layer
SSAP SSAP
Tsel Tsel
Session Layer
TSAP TSAP
Transport Layer
IP Addr
Network Layer
LSAP
Data Link Layer

MAC
Address
Physical Layer
Figure 144: Seven Layer Stack
Additionally, the diagram shows Selectors. These are represented by arrows. A Selector is an octet string used to
identify a specific SAP at a specific layer for all upper layers (Transport and above). Since in most implementations
all SAPs at any layer provide the same set of services to their users, all such SAPs are equivalent. Although
theoretically, there may be several selectors that identify a single SAP, for the sake of simplicity, we will assume
that each unique selector identifies a unique SAP. Also, since selectors are simply identifiers, their values can be
chosen arbitrarily. From this discussion, it is easy to see that a selector is functionally equivalent to a TCP/IP Port
number, with the exception that the TCP/IP Port number usually defines an application protocol.
At the Network layer, no selectors are used because the IP Address itself is used to identify a node on a TCP/IP
network.
The Application Level address at any specific layer is constructed by combining all the selectors up to that layer.
ICCP uses presentation addresses to set up communication channels between two ICCP applications. A
presentation address is composed of the Presentation Selector, Session Selector, Transport Selector, and an IP
Address.
To summarize, the Presentation Address represents a conduit through a Seven Layer Stack that an application uses
to communicate with other ICCP applications on the network.
227
When communicating with another application process on a network using ICCP, an AR Name is configured in the
local configuration to represent the remote application. SISCO’s ICCP extracts the presentation address and ACSE
parameters from the configuration and passes this information to the stack.
Once the remote address is known, it becomes the job of the Network layer to find the proper subnetwork and the
best path to reach the destination.
NAMING AUTHORITY
In most applications where the network is local, the assignment of SAPs and selectors can be rather arbitrary, and
is usually done on an adhoc basis. However, the assignment of names and addresses can be an important issue
when designing a large open network. This is where the naming authority comes into the picture. The term
“Naming Authority” represents a person or an organization responsible for the assignment of network addresses
and ACSE parameters across the network or networks. In North America the “Naming Authority” is NERC (North
American Reliablity Corporation). Most SAPs can be modified to emulate the structure as if it were assigned by
NERC.
APPLICATION LEVEL ADDRESSING
A summary of the addressing elements is shown below.
AP TITLE
The AP Title is an Object Identifier, assigned by the network naming authority, representing the Application
Process Title for a particular application process. An Object Identifier is a sequence of integer values representing
an application in the Seven Layer Stack Model. The first value in the AP Title should be 1 (ISO) (the valid range is 0
to 2). The second value should be 1, 2, or 3 (the valid range is 0 to 39). The third value is open for international
assignment. If addressing is local, then this value should be 9999. The rest of the values are arbitrary. For example,
values could be assigned to represent type and location of the application.
AE QUALIFIER
This is an optional integer value used to qualify the Application Entity.
AE TITLE
Although an AR Name may be configured to use any or all of the ACSE parameters defined above, the
recommended approach is that if ACSE information is required it should be in the form of an AE (Application
Entity) Title. The AE Title is comprised of an AP Title and an AE Qualifier. If used, the AE Title should be registered
with the appropriate naming authorities for your network.
PRESENTATION SELECTOR
This octet string represents the Presentation Selector used to identify a Presentation SAP. The maximum PSEL size
is 16 octets (32 ASCII encoded hex digits).
228
SESSION SELECTOR
This octet string represents the Session Selector used to identify a Session SAP. The maximum SSEL size is 16 octets
(32 ASCII encoded hex digits).
TRANSPORT SELECTOR
This octet string represents the Transport Selector used to identify a Transport SAP. The maximum TSEL size is 32
octets (64 ASCII encoded hex digits).
229

UserGd Axs4iccp 142095 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

UserGd Axs4iccp 142095 PDF

Caricato da

Copyright:

Formati disponibili

AX-S4 ICCP

Systems Integration Specialists Company, Inc.

© SISCO, Inc. 1999-2015

Figure 1: AX-S4 ICCP Overview Diagram

• Chapter 3: Getting Started outlines AX-S4 features and setup options.

ICCP Inter-Control Centre Communications Protocol

THE AX-S4 ICCP MODEL

Figure 2: AX-S4 ICCP Model

AX-S4 ICCP includes the following primary components:

Figure 3: AX-S4 ICCP OPC Server Model

AX-S4 ICCP OPC Server – AX-S4 ICCP

ICCP Configuration Utility

AX-S4 ICCP OPC Client (new component)

AX-S4 ICCP OPC Client Configuration Utility (new component)

OPC Test Client

SISCO Stack (new component)

Log Configuration Editor

AX-S4 ICCP supports the following client side interface:

The following system requirements are required:

• AXS4-ICCP-142-095-DEV or AXS4-ICCP-142-095-PAK. A Development license is required before purchasing

• An 802.3 network with TCP/IP (RFC1006).

The following assumptions are made about pre-existing knowledge:

Important Notes on Upgrading from V5.0000 to V6.0000:

You also need to backup the registry settings in the

SETUP TASK LIST

1. Install a network adapter per the instructions that accompany it.

Carefully follow the steps shown below to install AX-S4 ICCP:

1. AX-S4 ICCP installation requires a user to have Adminstrator Privileges.

{d}:setup where {d} designates the letter of your CD-ROM drive.

or click on Setup.exe in the zip file.

3. Serial number tracking program has been added to the installation.

Figure 4: AX-S4 ICCP Installation – Enter Serial Number

4. Setup indicates three installation types:

Figure 5: AX-S4 ICCP Installation Features

8. The installation sequence is as follows:

MANUALLY MIGRATING THE DATABASE TO THE NEW XML FORMAT

1. Start a command prompt in Administrative mode [elevated].

2014-09-16 13:33:22.626 MigrateStack/Always (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.044 MigrateStack/Always (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.044 MigrateStack/Always (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.059 MigrateStack/Always (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.215 MigrateStack/Flow (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.215 MigrateStack/Flow (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.231 MigrateStack/Flow (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.231 MigrateStack/Flow (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.231 MigrateStack/Flow (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.605 MigrateStack/Always (Unknown -1 ThreadId=0x490 (1168))

2014-09-16 13:33:25.605 MigrateStack/Always (Unknown -1 ThreadId=0x490 (1168))

The directory structure shown is for Windows7/Server 2008/Server 2012:

Figure 6: AX-S4 ICCP Directory Stucture

Directory Path Description

\Program Files\SISCO\AX-S4 ICCP AX-S4 ICCP Program

<Common Application Data>\SISCO\AX-S4 ICCP\Config AX-S4 ICCP Client Configuration files

<Common Application Data>\SISCO\AX-S4

\Program Files\SISCO\Common SISCO OPCDAAuto.dll

C:\Windows\System32 or C:\Windows\SysWOW64 <WINSYSDIR>

Directory Path Description

\Program Files\SISCO\License SISCO License files

Sisco Software Configuration, Documentation and Log

Windows 2003 Application Data Common directory is:

Windows 7/Server 2008/Server 2012 Application Data Common directory is:

MULTIPLE ETHERNET ADAPTERS AND TCP/IP

TCP/IP (USING RFC1006) SUPPORT