ICCP Quality Codes

1
ICCP Quality Codes

• Bill Blevins/Frank Kendall

2
History

• In the Zonal Market, there were four key
  documents providing important communication
  information to market participants. They were
• Network Interface Control Document (NICD)
• Communicating with ERCOT
• TAC Approved Telemetry Standards
• ERCOT Operating Guide Section 8
• The information contained in the above documents
  is equally important to market participants under
  the Nodal Market.

3
History

• Nodal Documents
• A review of the four Zonal documents shows a
  considerable amount of information duplication.
  An example is the data exchange tables they
  appear in both Communicating with ERCOT and the
  ERCOT Operating Guide Section 8.
• Under consideration is the creation of the
  following documents
• ERCOT Communication Handbook ERCOT Operating
  Guide Section 8
• The ERCOT Communication Handbook will generally
  combine the information in the following
  documents
• Network Interface Control Document (NICD)
  Communicating with ERCOT
• The ERCOT Operating Guide Section 8 revision for
  Nodal will incorporate the TAC Approved Telemetry
  Standards.
• Revising these documents for Nodal presents the
  opportunity to reduce the number of documents and
  also eliminate duplication of information across
  them.

4
Issues

• The quality and availability of telemetry
  provided to ERCOT are important to the
  performance of the ERCOT State Estimator.
• The TAC approved Telemetry Standards do not
  provide quality code mapping.
• During Business Requirements phase in developing
  SCADA TPTF requested that ERCOT include quality
  code mapping as part of the SCADA requirements
  document.
• Additionally TPTF requested ERCOT discuss
  internally and externally means to provide
  mapping standards as part of the Telemetry
  Standard.

5
TAC approved Nodal Telemetry Standard
requirements

• ICCP Links
• Data Quality Codes
• Market Participants shall provide documentation
  to ERCOT describing their native system quality
  codes and defining the conversion of their
  quality codes into the ERCOT defined quality
  codes.
• Status analogs telemetered to ERCOT will be
  identified with the following quality codes
•     Valid represents analog or status the TSP
  considers valid
•     Manual represents a analog or status
  entered manually at the market participant (not
  received from the field electronically)
•     Suspect - Represents a analog or status in
  which the TSP is unsure of the validity
•     Invalid Represents a analog or status
  which the market participant has identified as
  out of reasonability limits.
• Com_fail informs ERCOT that due to
  communications failure, the analog or status
  provided ERCOT is not current

6
Problems with the Current TAC approved Telemetry
Standard

• ICCP supports a richer set of quality codes than
  the current standard reflects.
• Extended ICCP attributes (Current Source, Normal
  Value) convey important information to ERCOT.
  These extended attributes are not addressed in
  the Telemetry Standards.
• Com_fail is not supported by ICCP.

7
TPTF request

• TPTF requested that the EMS team work to
  incorporate the SCADA requirements Quality Codes
  as part of the telemetry standards.
• Actions
• Met with IRT-John Webb to discuss Quality Codes.
• Informed Operations of the effort we are
  undertaking to revise the TAC approved Telemetry
  Standards.
• Confirmed with NMMS the Quality Codes do not
  impact them.
• Confirmed with MMS the codes that ABB require.

8
Operating Guides Revision Task Force (OGRTF)

• OGRTF Posted the Operating Guide Section 8 for
  comments
• ERCOT submitted comments proposing the Quality
  code mapping as proposed in the ERCOT
  requirements document be incorporated as part of
  the Operating Guides Section 8.
• This should allow for Market participants to
  submit their feedback on the proposed Quality
  Code mapping.

9
Proposed ERCOT ICCP Quality Code Requirements

• ICCP Quality Codes from Market Participants to
  ERCOT
• The following table describes the ICCP quality
  codes to be provided to ERCOT by the Market
  Participant, the conditions under which each ICCP
  quality code is to be set, and the translation
  from the Market Participants ICCP quality code
  to the related local ERCOT real-time database
  quality code.

10
Table 1 ICCP Quality Codes from Market
Participants to ERCOT
11
Table 1 ICCP Quality Codes from Market
Participants to ERCOT
12
Proposed ERCOT ICCP Quality Code Requirements

• ICCP Quality Codes from ERCOT to Market
  Participants
• The following table describes the ICCP quality
  codes to be provided to the Market Participant by
  the ERCOT, the conditions under which each ICCP
  quality code is set, and the translation from the
  local ERCOT real-time database quality codes to
  the related ICCP quality code.

13
Table 2 ICCP Quality Codes from ERCOT to Market
Participants
14
Table 2 ICCP Quality Codes from ERCOT to Market
Participants
15
RTU and ICCP Cutover

• Can ERCOT cut over ICCP under Zonal?
• ERCOT is evaluating the scope of any Zonal cut
  over of QSEs.
• It looks like the work would involve about ½ a
  man year.
• Vendor has provided input that Database changes
  would be required and the scope would be more
  than just mapping RTU points to ICCP.
• ERCOT is going to work with a volunteer QSE to
  performed a more detailed evaluation before
  proposing any Zonal changes.