INT-016-WECC-CRT-32.1 Data SubmittalPage 1 of 5

A.Introduction

  1. Title: Data Submittal[SB1]
  2. Number:INT-016-WECC-CRT-32.1
  3. Purpose:To ensure all Requests- For- Interchange (RFI), less than 60-minutes in duration, are submitted to the iInterchange software tool Coordinator[SB2] (AKA: WECC Interchange Tool (WIT)) to support accurate[SB3] correct Net Scheduled Interchange data for NERC reporting[SB4].
  4. Applicability:
  5. Functional Entities:
  6. Balancing Authority
  7. Purchasing-Selling Entity
  8. Effective Date:July 1, 2012

B.Requirements and Measures

WR1.Each Purchasing-Selling Entity and each Balancing Authority meeting one or more of the following[SB5] criteria shall identify either the designate either the Purchasing-Selling Entity or the Balancing Authority as the entity or Purchasing-Selling Entity responsible for electronically submitting the RFI:Request-For-Interchange:

  • Purchasing-Selling Entity or Balancing Authority submitting a RFI Request-For-Interchangenot otherwise required under a NERC Standard; (or),
  • Purchasing-Selling Entity or Balancing Authority that has experienced a loss of resources affecting Net Scheduled Interchange.

WM1. Each Balancing Authority meeting one or more of the criteria listed in WR1 will have evidence that it made the designations as required in WR1.

Evidence may include, but is not limited to, Evidence of compliance with WR1 may include, but is not limited to, production of the e-Tag identifying the parties.

WR2.Each Balancing Authority designated in WR1 that submits an RFI shall submit its RFI using the same interchange tool used by its Reliability Coordinator.Each Purchasing-Selling Entity and each Balancing Authority designated in WR1 to submit a Request-For-Interchange affecting Net Scheduled Interchange shall submit that transaction electronically to the WECC Interchange Tool (WIT).

WM2.Each Balancing Authority designated in WR1 that submits an RFI per WR2 will have evidence that it electronically submitted that transaction using the same interchange tool used by its Reliability Coordinator.

Evidence may include, but is not limited to, vidence of compliance with WR2 may include, but is not limited to, production of the e-Tag identifying the parties.

Version History

Version / Date / Action / Change Tracking
0 / April 10, 2007 / Initial Tracking / INT-BPS-016-0
0 / May 1, 2007 / Operating Committee Approved / Initial version
1 / August 31, 2009 / Converting current approved Business Practice into a new regional Criterion format – no other changes are being submitted / Designation change
2 / June 25, 2012 / WECC Board of Directors Approved / Developed as WECC-0082. Updated as part of INT Rewrite Project
2 / July 1, 2012 / Effective Date
INT-016-WECC-CRT-1 was retired by the WECC Board of Directors as of the Effective Date of INT-016-WECC-CRT-2. / Designation change
The substance of INT-016 and 017 were combined into this document. WR2 of INT-017-WECC-CRT-1 has been removed and is under development in INT-008-WECC-CRT-2 as of July 1, 2012.
2 / September 5, 2013 / WECC Board of Directors changed designation from “CRT” to “RBP” / Designation change
2 / June 25, 2014 / WECC Board of Directors changed designation from “RBP” to “CRT”. / Designation change
2.1 / January 28, 2016 / Errata / Numbered items in WR1 were changed to bulleted items. Numbered items indicate an all-inclusive set; bullets indicate either/or.
2.1 / April 1, 2016 / No Change / Converted to new template

Disclaimer

WECC receives data used in its analyses from a wide variety of sources. WECC strives to source its data from reliable entities and undertakes reasonable efforts to validate the accuracy of the data used. WECC believes the data contained herein and used in its analyses is accurate and reliable. However, WECC disclaims any and all representations, guarantees, warranties, and liability for the information contained herein and any use thereof. Persons who use and rely on the information contained herein do so at their own risk.

Attachments

Attachment A

Not Used

Rationale

A Rationale section is optional. If Rationale Boxes were used during the development of this project, the content of those boxes appears below.

The Generic use of Interchange Software

Throughout the Western Interconnection, the interchange software used is colloquially known as the WECC Interchange Tool (WIT), even though WECC neither owns, controls, nor contracts for the software package. The interchange software currently falls under the purview of Peak Reliability. Further, there is an expanded spectrum of the services offered under the contract that are not specifically contemplated in this document.

This document recognizes that the name and attributes of the interchange software, its origin, and its vendor will change from time-to-time. To ensure the viability of this document, the generic term “interchange software” has been used instead of the specific name (proper noun) of the interchange software package.

It is this interchange software package that is used to authorize the implementation of valid and balanced Interchange Schedules between Balancing Authority Areas, and ensures communication of Interchange information for reliability assessment purposes.

WR1 and WR2

WR1 and WR2 establish the which entity is responsible for submitting a RFI.Request-For-Interchange when either the Purchasing-Selling Entity or the Balancing Authority can do so. Thereafter, it ensures the designated entity submits the transaction electronically thereby allowing the interchange software tool WECC Interchange Tool to perform its tasks in an automated fashion. This supports compliance with NERC Standards INT-003-3, INT-007-1, and BAL-006-2[SB6] .

WR2 also allows the interchange software tool WECC Interchange Tool to be the sole source for Net Scheduled Interchange in compliance with BAL-006-2, Inadvertent Interchange. To accomplish this, it requires transactions be submitted that are otherwise excluded by NERC INT-010-2.1, Interchange Initiation and Modification for Reliability. 1[SB7].

Western Electricity Coordinating Council

[SB1]The CRT has only two Requirements. Can they be consolidated into another document?

[SB2]WECC-0118, use of the term WIT or WECC Interchange Tool or Western Interchange Tool has been discontinued in favor of a generic.

See proposed Guidance Section. That section has already been included in WECC-0118, INT-020-WECC-CRT-2, Interchange Schedule Backup Process.

No minority comments were received in opposition of its inclusion.

[SB3]Optional: Use accurate instead of correct. Correct can be either a noun or a verb. “He was correct in that he used the tool to correct the data.”

[SB4]Not needed unless the CRT is specifically for the sole purpose. .

[SB5]Consider deleting the PSE altogether. This says the PSE will designate the EITHER the PSE or BA responsible. As the PSE is no longer in the NERC Compliance registry, simply shift these duties to the BA.

Each BA meeting [the criteria] shall designate a different BA as the responsible party.

[SB6]INT-003-3 is retired.

INT-007-1 is retired.

BAL-006-2, Inadvertent Interchange has a US Enforcement date of 4/1/2011.

[SB7]Do we need this paragraph at all? BAL is in flux and the doc will become outdates as soon as a new version is created.

Rule: Do not incorporate by reference. .