INT-006-5 – Evaluation of Interchange Transactions

Purpose
To ensure that responsible entities conduct a reliability assessment of each Arranged Interchange before it is implemented.

Applicability

Effective Date
See Implementation Plan.

Requirements and Measures
R1.
Each Balancing Authority shall approve or deny each on-time Arranged Interchange or emergency Arranged Interchange that it receives and shall do so prior to the expiration of the time period defined in Attachment 1, Column B. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations, Real-time Operations]

1.1. Each Source and Sink Balancing Authority shall deny the Arranged Interchange or curtail Confirmed Interchange if it does not expect to be capable of supporting the magnitude of the Interchange, including ramping, throughout the duration of the Arranged Interchange.
1.2. Each Balancing Authority shall deny the Arranged Interchange or curtail Confirmed Interchange if the Scheduling Path (proper connectivity of Adjacent Balancing Authorities) between it and its Adjacent Balancing Authorities is invalid.

M1. Each Balancing Authority shall have evidence (such as dated and time stamped electronic logs, or other evidence) that it responded to each request for its approval to transition an Arranged Interchange to a Confirmed Interchange within the time defined in Attachment 1, Column B. (R1)

R2. Each Transmission Service Provider shall approve or deny each on-time Arranged Interchange or emergency Arranged Interchange that it receives and shall do so prior to the expiration of the time period defined in Attachment 1, Column B. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations, Real-time Operations]

2.1. Each Transmission Service Provider shall deny the Arranged Interchange or curtail Confirmed Interchange if the transmission path (proper connectivity of adjacent Transmission Service Providers) between it and its adjacent Transmission Service Providers is invalid.

M2. Each Transmission Service Provider shall have evidence (such as dated and time stamped electronic logs, studies, or other evidence) that it responded to each Arranged Interchange or emergency Arranged Interchange within the time defined in Attachment 1, Column B. If the transmission path between the Transmission Service Provider and its adjacent Transmission Service Providers is invalid, each Transmission Service Provider shall have evidence (such as dated and time stamped electronic logs, studies, or other evidence) that it denied the Arranged Interchange or curtailed confirmed Interchange. (R2)

R3. The Source Balancing Authority and the Sink Balancing Authority receiving a Reliability Adjustment Arranged Interchange shall approve or deny it prior to the expiration of the time period defined in Attachment 1, Column B. [Violation Risk Factor: Lower] [Time Horizon: Operations Planning, Same-day Operations, Real-time Operations]

M3. Each Balancing Authority shall have evidence (such as dated and time stamped electronic logs, studies, or other evidence) that when responding to a Reliability Adjustment Arranged Interchange, it either approved the request or denied the request.

R4. Reserved.

M4. Reserved.

R5. Reserved.

M5. Reserved.

Compliance
1. Compliance Monitoring Process

1.1. Compliance Enforcement Authority: “Compliance Enforcement Authority” means NERC or the Regional Entity, or any entity as otherwise designated by an Applicable Governmental Authority, in their respective roles of monitoring and/or enforcing compliance with mandatory and enforceable Reliability Standards in their respective jurisdictions.
1.2. Evidence Retention: The following evidence retention period(s) identify the period of time an entity is required to retain specific evidence to demonstrate compliance. For instances where the evidence retention period specified below is shorter than the time since the last audit, the Compliance Enforcement Authority may ask an entity to provide other evidence to show that it was compliant for the full-time period since the last audit.

The applicable entity shall keep data or evidence to show compliance as identified below unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of time as part of an investigation.

• The Balancing Authority shall maintain evidence to show compliance with R1 and R3 for the most recent three calendar months plus the current month.
• The Transmission Service Provider shall maintain evidence to show compliance with R2 for the most recent three calendar months plus the current month.
• If a Balancing Authority or Transmission Service Provider is found noncompliant, it shall keep information related to the non-compliance until found compliant.

The Compliance Enforcement Authority shall keep the last audit records and all requested and submitted subsequent audit records.

1.3. Compliance Monitoring and Enforcement Program: As defined in the NERC Rules of Procedure, “Compliance Monitoring and Enforcement Program” refers to the identification of the processes that will be used to evaluate data or information for the purpose of assessing performance or outcomes with the associated Reliability Standard.
• Compliance Audits
• Self-Certifications
• Spot Checking
• Compliance Investigations
• Self-Reporting
• Complaint

Guidelines and Technical Basis
Many aspects of managing Interchange are supported by software applications. There are fundamental tasks that each entity should be able to perform in an electronic manner as listed below.

A Load-Serving Entity and Balancing Authority that submits Requests for Interchange should have the capability to electronically:
• Submit a Request for Interchange to a Sink Balancing Authority
• Submit a request to modify Interchange
• Receive distributions of Confirmed Interchange
• Receive distributions of Reliability Adjustment Arranged Interchanges

Each Sink Balancing Authority should have the capability to electronically:
• Receive a Request for Interchange
• Receive a request to modify Interchange
• Validate Requests for Interchange by verifying:

o Source Balancing Authority megawatts equal Sink Balancing Authority megawatts (adjusted for losses, if appropriate).
o All reliability entities involved in the Arranged Interchange are valid.
o Generation source and Load sink are defined.
o Megawatt profile is defined. o Interchange duration is defined.

• Validate request to modify Interchange by verifying:

o Source Balancing Authority megawatts equal Sink Balancing Authority megawatts (adjusted for losses, if appropriate).
o Megawatt profile is defined.
o Interchange duration is defined.

• Distribute the validated Request for Interchange as Arranged Interchange
• Distribute the validated Reliability Adjustment Arranged Interchanges
• Receive communication of approval or denial of Arranged Interchange

o Distribute notification as each entity approves or denies an Arranged Interchange.
o Transition Arranged Interchange to Confirmed Interchange if all approvals are received.
o Distribute notification of whether Arranged Interchange was transitioned to Confirmed Interchange or not.
o Submit a request to modify Interchange

• Each Load-Serving Entity that approves or denies Arranged Interchange, and each Balancing Authority and Transmission Service Provider should have the capability to electronically:

o Receive distribution of Arranged Interchange
o Communicate approval or denial of the Arranged Interchange to the Sink Balancing Authority
o Receive notification of whether Arranged Interchange was transitioned to Confirmed interchange or not.
o Submit a request to modify Interchange

• While Interchange is normally facilitated using electronic communication and software tools, there are occasions with those electronic capabilities are reduced or unavailable. It is recommended that all entities involved in aspects of Interchange should have, maintain and implement a plan describing the manner and timing in which all capabilities listed above will be provided when electronic capabilities are reduced or unavailable. Each plan should address the following topics:

o Alternate methods of communicating Interchange information between Purchasing Selling Entities, Balancing Authorities, and Transmission Service Providers.
o How to notify others that it is activating the plan
o How it will process requests for emergency Arranged Interchange and Reliability Adjustment Arranged Interchange.
o Restrictions and limitations that may apply during the period of reduced or unavailable capability (such as limits on volume, only accepting emergency transactions, etc.).
o Delegation of approval rights and proxy actions, if such approaches will be used.
o How known Confirmed Interchange will be scheduled following a reduction in or loss of capability.
o Personnel plans for short-term and extended periods.
o Training of personnel in the use of the plan.

Rationale
During development of this standard, text boxes were embedded within the standard to explain the rationale for various parts of the standard. Upon BOT approval, the text from the rationale text boxes was moved to this section.

Rationale for R1:
Balancing Authorities must take action on a received Arranged Interchange within a certain time frame. Requirement R1, Parts 1.1 and 1.2 provide reliability-related reasons that a Balancing Authority must deny an Arranged Interchange, but Balancing Authorities may deny for other reasons. If the conditions described in Requirement R1, Parts 1.1 or 1.2 are recognized after approval is granted, the Balancing Authority may curtail the Confirmed Interchange prior to implementation.

Rationale for R2:
TSPs must take action on a received Arranged Interchange within a certain time frame. Requirement R2, Part 2.1 provides reliability-related reasons that a TSP must deny an Arranged Interchange, but TSPs may deny for other reasons. If the conditions described in Requirement R1, Part 2.1 are recognized after approval is granted, the TSP may curtail the Confirmed Interchange prior to implementation.

 


Top