INT-003-3: Interchange Transaction Implementation

Purpose
To ensure Balancing Authorities confirm Interchange Schedules with Adjacent Balancing Authorities prior to implementing the schedules in their Area Control Error (ACE) equations.

Applicability
Balancing Authorities

Effective Date
First day of first calendar quarter after applicable regulatory approval, or in those jurisdictions where no regulatory approval is required, the first day of the first calendar quarter after Board of Trustees adoption.

Requirements
R1. Each Receiving Balancing Authority shall confirm Interchange Schedules with the Sending Balancing Authority prior to implementation in the Balancing Authority’s ACE equation. (Violation Risk Factor: Medium)

R1.1. The Sending Balancing Authority and Receiving Balancing Authority shall agree on Interchange as received from the Interchange Authority, including: (Violation Risk Factor: Lower)

R1.1.1. Interchange Schedule start and end time. (Violation Risk Factor: Lower)

R1.1.2. Energy profile. (Violation Risk Factor: Lower)

R1.2. If a high voltage direct current (HVDC) tie is on the Scheduling Path, then the Sending Balancing Authorities and Receiving Balancing Authorities shall coordinate the Interchange Schedule with the Transmission Operator of the HVDC tie. (Violation Risk Factor: Medium)

Measures
M1. Each Receiving and Sending Balancing Authority shall have and provide upon request evidence that could include, but is not limited to, interchange transaction tags, operator logs, voice recordings or transcripts of voice recordings, electronic communications, computer printouts, or other equivalent evidence that will be used to confirm that each Interchange Schedule’s start and end time, and energy profile were confirmed prior to implementation in the Balancing Authority’s ACE equation. (Requirement R1, R1.1, R1.1.1 & R1.1.2)

M2. Each Receiving and Sending Balancing Authority shall have and provide upon request evidence that could include, but is not limited to, interchange transaction tags, operator logs, voice recordings or transcripts of voice recordings, electronic communications, computer printouts, or other equivalent evidence that will be used to confirm that it coordinated the Interchange Schedule with the Transmission Operator of the HVDC tie as specified in Requirement 1.2.

Compliance
1. Compliance Monitoring Process

1.1. Compliance Monitoring Responsibility

1.2. Compliance Monitoring and Reset Time Frame

One or more of the following methods will be used to assess compliance:

– Self-certification (Conducted annually with submission according to schedule.)
– Spot Check Audits (Conducted anytime with up to 30 days notice given to prepare.)
– Periodic Audit (Conducted once every three years according to schedule.)
– Triggered Investigations (Notification of an investigation must be made within 60 days of an event or complaint of noncompliance. The entity will have up to 30 days to prepare for the investigation. An entity may request an extension of the preparation period and the extension will be considered by the Compliance Monitor on a case-by-case basis.)

The Performance-Reset Period shall be 12 months from the last finding of noncompliance.

1.3. Data Retention

Each Balancing Authority shall keep 90 days of historical data (evidence).

If an entity is found non-compliant the entity shall keep information related to the noncompliance until found compliant or for two years plus the current year, whichever is longer.

Evidence used as part of a triggered investigation shall be retained by the entity being investigated for one year from the date that the investigation is closed, as determined by the Compliance Monitor,

The Compliance Monitor shall keep the last periodic audit report and all requested and submitted subsequent compliance records.

1.4. Additional Compliance Information

None.

2. Violation Severity Levels:

R# Lower VSL Moderate VSL High VSL Severe VSL
R1 There shall be a separate Lower VSL, if either of the following conditions exists: One instance of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. One instance of not coordinating the Interchange Schedule with the Transmission Operator of the HVDC tie as specified in R1.2 There shall be a separate Moderate VSL, if either of the following conditions exists: Two instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. Two instances of not coordinating the Interchange Schedule with the Transmission Operator of the HVDC tie as specified in R1.2 There shall be a separate High VSL, if either of the following conditions exists: Three instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. Three instances of not coordinating the Interchange Schedule with the Transmission Operator of the HVDC tie as specified in R1.2 There shall be a separate Severe VSL, if either of the following conditions exists: Four or more instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. Four or more instances of not coordinating the Interchange Schedule with the Transmission Operator of the HVDC tie as specified in R1.2
R1.1 The Balancing Authority experienced one instance of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. The Balancing Authority experienced two instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2 The Balancing Authority experienced three instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. The Balancing Authority experienced four instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2.
R1.1.1 The Balancing Authority experienced one instance of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. The Balancing Authority experienced two instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2 The Balancing Authority experienced three instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. The Balancing Authority experienced four instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2.
R1.1.2 The Balancing Authority experienced one instance of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. The Balancing Authority experienced two instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. The Balancing Authority experienced three instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2. The Balancing Authority experienced four instances of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1.1 and R1.1.2.
R1.2 The sending or receiving Balancing Authority experienced one instance of not coordinating the Interchange Schedule with the Transmission Operator of the HVDC tie as specified in R1.2 The sending or receiving Balancing Authority experienced two instances of not coordinating the Interchange Schedule with the Transmission Operator of the HVDC tie as specified in R1.2 The sending or receiving Balancing Authority experienced three instances of not coordinating the Interchange Schedule with the Transmission Operator of the HVDC tie as specified in R1.2 The sending or receiving Balancing Authority experienced four instances of not coordinating the Interchange Schedule with the Transmission Operator of the HVDC tie as specified in R1.2

Regional Differences
MISO Energy Flow Information Waiver dated July 16, 2003.


Top