Inter-Control Center Communications Protocol (ICCP)

ICCP operates on a strict client-server architecture where one control center acts as the client requesting data and the other functions as the server providing it. This bilateral arrangement is established over a TCP/IP network connection using port 102. Each association is negotiated through a bilateral table that explicitly defines which data objects each party is authorized to access, ensuring strict access control between balancing authorities. The protocol supports concurrent associations, allowing a single control center to maintain simultaneous connections with multiple neighboring entities for comprehensive wide-area visibility.

ICCP supports multiple data transfer modes optimized for grid operations. Periodic polling retrieves data at configurable intervals, while report-by-exception (RBE) transmits values only when they change beyond a defined deadband threshold, dramatically reducing network bandwidth. The protocol also enables integrity polls that request a complete snapshot of all data points to resynchronize state after a communication failure. For critical control actions, immediate send operations bypass normal queuing to deliver time-sensitive commands such as AGC setpoint changes with minimal latency.

The Telecontrol Application Service Element 2 (TASE.2) defines the standardized object models that ICCP uses to represent power system data. Key objects include:

• Data Value Objects: Represent analog measurements like MW, MVAR, and kV
• Data Set Objects: Group related points for efficient bulk transfers
• Transfer Set Objects: Define conditions triggering report-by-exception
• Information Message Objects: Carry operator notes and textual alarms This object-oriented approach ensures semantic interoperability between control centers using different SCADA vendors, eliminating the need for custom protocol translation.

ICCP's block transfer capability is essential for Automatic Generation Control coordination between balancing authorities. Rather than transmitting individual data points, ICCP can transfer entire data blocks containing multiple values in a single protocol message. This mechanism efficiently exchanges:

• Area Control Error (ACE) values between neighbors
• Net interchange schedules for tie-line bias calculations
• Frequency bias coefficients for coordinated frequency response
• Dynamic schedule telemetered values for pseudo-tie resources Block transfers minimize protocol overhead and ensure that all related AGC inputs arrive simultaneously for consistent control calculations.

To guarantee multi-vendor interoperability, ICCP implementations must pass rigorous conformance testing defined in IEC 60870-6-702. Testing verifies:

• Protocol Implementation Conformance Statement (PICS): Documents which services and objects are supported
• Protocol Implementation eXtra Information for Testing (PIXIT): Specifies parameter values and operational constraints
• Interoperability tests: Validate bilateral table negotiation, data transfer, and error recovery between different vendor systems This standardized testing regime ensures that a control center using one SCADA platform can reliably exchange real-time data with neighbors running entirely different systems.

ICCP incorporates multiple security layers to protect critical grid data exchanges. The bilateral table serves as the primary access control mechanism, explicitly enumerating which data objects each connected entity can read or write. Modern implementations wrap ICCP traffic within Transport Layer Security (TLS) encryption to prevent eavesdropping and man-in-the-middle attacks on wide-area network links. Additional security measures include:

• IP address filtering to restrict connection sources
• Application-level authentication during association establishment
• Audit logging of all data access and control operations These protections align with NERC CIP requirements for securing electronic security perimeters around critical cyber assets.