INT-004-2: Dynamic Interchange Transaction Modifications
Purpose
To ensure Dynamic Transfers are adequately tagged to be able to determine their reliability impacts.
Applicability
- Balancing Authorities
- Reliability Coordinators
- Transmission Operators
- Purchasing-Selling Entities
Effective Date
August 27, 2008 (U.S.) – NERC Board Approval: October 9, 2007
Requirements
R1. At such time as the reliability event allows for the reloading of the transaction, the entity that initiated the curtailment shall release the limit on the Interchange Transaction tag to allow reloading the transaction and shall communicate the release of the limit to the Sink Balancing Authority.
R2. The Purchasing-Selling Entity responsible for tagging a Dynamic Interchange Schedule shall ensure the tag is updated for the next available scheduling hour and future hours when any one of the following occurs:
R2.1. The average energy profile in an hour is greater than 250 MW and in that hour the actual hourly integrated energy deviates from the hourly average energy profile indicated on the tag by more than ±10%.
R2.2. The average energy profile in an hour is less than or equal to 250 MW and in that hour the actual hourly integrated energy deviates from the hourly average energy profile indicated on the tag by more than ±25 megawatt-hours.
R2.3. A Reliability Coordinator or Transmission Operator determines the deviation, regardless of magnitude, to be a reliability concern and notifies the PurchasingSelling Entity of that determination and the reasons.
Measures
M1. The Sink Balancing Authority shall provide evidence that the responsible PurchasingSelling Entity revised a tag when the deviation exceeded the criteria in INT-004 Requirement 2.
Compliance
1. Compliance Monitoring Process
Periodic tag audit as prescribed by NERC. For the requested time period, the Sink Balancing Authority shall provide the instances when Dynamic Schedule deviation exceeded the criteria in INT-004 R2 and shall provide evidence that the responsible Purchasing-Selling Entity submitted a revised tag.
1.1. Compliance Monitoring Responsibility
Regional Reliability Organization.
1.2. Compliance Monitoring Period and Reset Time Frame
One calendar year without a violation from the time of the violation.
1.3. Data Retention
Three months.
1.4. Additional Compliance Information
Not specified.
2. Levels of Non-Compliance
2.1. Level 1:
Not specified.
2.2. Level 2:
Not specified.
2.3. Level 3:
Not specified.
2.4. Level 4:
Not specified.
Regional Differences
1. None