ERCOT Nodal ICCP Communication Handbook

1
ERCOT Nodal ICCP Communication Handbook

• Bill Blevins
• Frank Kendall

2
Handbook Activities

• Feb 28th TPTF approved SCADA requirements
  document.
• ERCOT discussed ICCP codes with AREVA, ERCOT
  Operations, NMMS, MMS, ICCP beta testing group
  (EDS), EIP(Texas Nodal Enterprise Integration
  External Interfaces Specification), EMS groups,
  and the Network Data Support Working Group.
• ERCOT discussed ICCP codes with TPTF March 22nd.
• April 18th posted for TPTF comments thru May
  2nd.
• May 2nd thru May 7th ERCOT staff modify based on
  comments.
• May 7th-8th review with TPTF.
• May 14th post for Nodal Market Participants.
• June 1st EDS phase delivery 2 starts point to
  point check out with TSP Market Participants.

3
Audience of the handbook is

• Market Participants ICCP Vendor.
• ERCOT ICCP Vendor.
• ERCOT technical staff.
• ERCOT Market Participant technical staff.
• ERCOT Market Participant business
  representatives.
• ERCOT business staff.

4
Goal of the ICCP handbook

• Inform ERCOT and Market participant ICCP vendors
  and technical staff on methods and processes to
  uniformly configure and implement a high
  availability ICCP data transfer.
• Ultimately to enable the ERCOT EMS SCADA system
  to provide Market and Reliability functions
  required by the Texas Nodal Protocols.

5
ICCP handbook organization

• Section 1, Introduction describes the purpose and
  scope of the ERCOT Nodal ICCP Communication
  Handbook
• Section 2, Connecting to the ERCOT Wide Area
  Network.
• Section 3, ICCP Conventions provides details on
  the ICCP client/server architecture and describes
  parameters necessary for all Market Participants
  to successfully establish communication with
  ERCOT using ICCP.
• Section 4, QSE Connection requirements.
• Section 5, TSP Connection requirements.
• Section 6, Data Available to All Market
  Participants describes data produced by ERCOT
  available to all Market Participants with ICCP
  nodes.
• Section 7, Data Calculated Locally by ERCOT
  describes values that ERCOT calculates from TSP
  telemtered information.

6
New Information

• Document.
• Title changed
• Added in reference to EIP (Texas Nodal Enterprise
  Integration External Interfaces Specification.
• ERCOT Equipment diagram.
• New equipment delivered by ERCOT (Fig-2).
• ERCOT architecture for high availability.
• New ERCOT architecture will support both Taylor
  and Austin communication nodes live.
• SCADA will receive information from first primary
  and will shift to second primary Node on a loss
  of first primary.(Fig-3).
• Section 3.4 Quality Code and Source details
• ICCP domain convention
• Table 4-6 to describe code translations.
• Section 3.4.1 illustrated examples of ICCP code
  handling for MP and ERCOT.
• TSP information
• Table 39 naming convention examples.
• QSE information
• Table 22-24 naming convention and examples.
• SCED and Nodal LFC information.
• Data available to all market participants
• ICCP point naming convention.

7
Unresolved

• Sign Convention.
• Some comments from MPs are that the current sign
  convention is confusing.
• ERCOT Block 4 messages.
• Free form text reasons for operation beyond HSL,
  LSL and Ramp Rates.