Get documents about "WECC Criterion: WECC-0041, After-the-Fact Tagging Guidelines
Document Sample
Management of Adjacent Data Points Criterion
INT-015-WECC-CRT-2
Version 5
Open: September 24, 2012 Closed: October 24, 2012
Document name Management of Adjacent Data Points
Category ( ) Regional Reliability Standard
(X) Regional Criterion
( ) Policy
( ) Guideline
( ) Report or Other
Document Publication
Date
Approved By Operating Committee
Date Approved
Custodian (entity
responsible for
maintenance and upkeep)
Stored/Filed Physical Location:
Web URL:
Previous Name/Number (If any)
Status ( ) In Effect
( ) Usable, Minor Formatting/Editing
Required
( ) Modification Needed
( ) Superseded By
_____________________
( ) Other
_____________________________
( ) Obsolete/Archived)
Version Control
Version Date Action Change
1 04/10/07 Initial version
1 5/1/07 Approved by the Operating
Committee
1 8/31/09 Converting current approved Format Change
Business Practice (INT-BPS-016-0)
into new Regional Criterion format
– no other changes are being
submitted.
Developed as WECC-0081 1
Management of Adjacent Data Points Criterion
INT-015-WECC-CRT-2
Version 5
Open: September 24, 2012 Closed: October 24, 2012
Criterion Development Roadmap
This section is maintained by the drafting team during the development of the criterion
and will be removed when the criterion becomes effective.
Development Steps Completed:
Completed Actions Completion
Date
1. Converting current approved Business Practice (INT-BPS- 8-31-2009
003-0) into new Regional Criterion format – no other
changes are being submitted.
2. Posting 1 posted for 45-Day Comment 4-25-2011
3. Posting 1 Comment period closed 6-9-2011
4. Responses due back on the WECC Web 7-11-2011
5. Posting 2 posted for 30-Day Comment 11-3-2011
6. Posting 2 Comment period closed 12-5-2011
7. Responses due back on the WECC Web 1-4-2012
8. Posting 3 posted for 30-Day Comment 2-9-2012
9. Posting 3 Comment period closed 3-12-2012
10. Responses due back on the WECC Web 4-11-2012
11. Posting 4 posted for 30-Day Comment 7-27-2012
12. Posting 4 Comment period closed 8-27-2012
13. Responses due back on the WECC Web 9-26-2012
Developed as WECC-0081 2
Management of Adjacent Data Points Criterion
INT-015-WECC-CRT-2
Version 5
Open: September 24, 2012 Closed: October 24, 2012
Description of Project, Process and Current Draft:
INT Rewrite Project
As part of this Operating Committee “INT Rewrite Project”, spearheaded by the Interchange
Scheduling and Accounting Subcommittee (ISAS), a drafting team was solicited and
convened from nominations submitted for the purpose of reviewing INT criteria 1-17 to bring
those criteria into conformance with current drafting conventions. This team did not address
INTs 1, 2, 5, 6, 7, 8, (12 and 13 do not exist) as they have been assigned to other teams.
(See matrix below.)
The Drafting Team has reviewed the associated criterion to identify and correct, among other
things: 1) ambiguities in the existing language, 2) superfluous language and Requirements,
3) missing Requirements, 4) accuracy of assigned Applicable Entities, 5) capitalizations / use
of defined terms, 5) application of existing drafting conventions, 6) potential retirement of the
document, 7) errata, and 8) consideration of updated criterion formatting.
A Cross-Reference Table to each criterion in the INT Rewrite Project and its associated
Request is offered below.
A Mapping Table comparing the existing criterion and its Requirements to the proposed
criterion and its Requirements is offered below.
Developed as WECC-0081 3
Management of Adjacent Data Points Criterion
INT-015-WECC-CRT-2
Version 5
Open: September 24, 2012 Closed: October 24, 2012
Cross Reference Table
Old Number New Number Title WECC Tracking Number
INT-BPS-001 INT-001-WECC-CRT-2 Request to Modify INT-BPS-001-2 53
INT-BPS-002 INT-002-WECC-CRT-2 WECC Net Actual Interchange 85
Reconciliation Process
INT-BPS-003 INT-003-WECC-CRT-1 Interchange Preschedule Calendar 76
INT-BPS-004 INT-004-WECC-CRT-4 Tag Curtailment / Reload 77
Responsibilities for Transmission (INT-4 and 10 to be combined)
Emergencies
INT-BPS-005 INT-005-WECC-CRT-1 Real-Time Interchange Schedule / 86
Manual Emergency Curtailment
Procedures
INT-BPS-006 INT-006-WECC-CRT-1 Real-Time Net Interchange 73
Reconciliation
INT-BPS-007 INT-007-WECC-CRT-7 Real-Time Processing of Late 56
Electronic Tags
INT-BPS-008 INT-008-WECC-CRT-8 Dynamic Schedule e-Tagging 87
Requirements
INT-BPS-009 INT-009-WECC-CRT-1 Capacity Tag Functionality
INT-BPS-010 INT-010-WECC-CRT-1 Reliability Curtailment 77
(INT-4 and 10 to be combined)
INT-BPS-011 INT-011-WECC-CRT-1 Ten Minute Recallable e-Tag 79
Functionality for Reserves
INT-BPS-014 INT-014-WECC-CRT-1 Identification of Contingency 80
Responsibilities in the e-Tag
INT-BPS-015 INT-015-WECC-CRT-1 WECC Interchange Tool e-Tag 81
Validation Prior to Distribution of a (15-16-17 to be combined)
Request for Interchange Approval
IINT-BPS-016 INT-016-WECC-CRT-1 Require Electronic Submittal of Request 82
for Interchange to the WECC (15-16-17 to be combined)
Interchange Tool (WIT)
INT-BPS-017 INT-017-WECC-CRT-1 Requirement to e-Tag Every (15-16-17 to be combined)
Transactions that Impacts Net
Scheduled Interchange with Correct
Value
Mapping Table: INT-015-WECC-2
The origins of Requirements can be found in the following locations:
Current WECC Requirement New WECC Requirement
INT-015-WECC-CRT-1 WR1 and WR2 were removed as they refer to a
WR1 and WR2, task performed by software and not a responsible
entity. The substance of these Requirements will
be communicated to WECC staff for software
development discussions with the appropriate
software vendor.
WR3 Was removed. The team concluded that having
any multiple of lists was not the best approach;
rather, reliance on the adjacency records contained
in the Western Interchange Tool (WIT) would be
the best approach.
Developed as WECC-0081 4
Management of Adjacent Data Points Criterion
INT-015-WECC-CRT-2
Version 5
Open: September 24, 2012 Closed: October 24, 2012
Overview
The team concluded that although the Applicable Entity designated as the “Interchange
Authority” was likely the best choice for the Requirement(s) under this criterion, under the
Reliability Standards Development Procedures (Procedures) the use of Interchange Authority
is no longer allowed. As a second alternative, the team discussed using “Interchange
Coordinator”; however, there are no responsible entities registered under that category and
no known mechanism to force an entity to so register. As a result, the team reviewed the
criterion, eliminated those tasks otherwise performed solely by software, and then assigned
the remaining task to the Balancing Authority.
As for those tasks otherwise applicable to software, the team has taken two approaches. In
the first, the team has drafted a technical document containing what the team has identified
as “software tasks” to be performed by a piece of software as opposed to a human entity.
This listing and its functionality will be sent to WECC Staff for communication to the
appropriate software vendor. Any remaining information has been moved to the guidance
section of the document so as not to lose that information.
After making the above changes, the team opted to change the name and the Purpose
statement to more closely reflect the substance of the remaining Requirement.
Finally, the proposed definition for WECC Registry was removed as that capitalized term
refers to a proper noun and does not reflect a term of art within the industry.
If you have questions as to the Process, please contact W. Shannon Black at
sblack@wecc.biz, (503) 301-5782.
Implementation Plan
No implementation plan is proposed.
Definitions of Terms Used in Criterion
This section includes all newly defined or revised terms used in the proposed criterion.
Terms already defined in the Reliability Standards Glossary of Terms are not repeated
here. New or revised definitions listed below become approved when the proposed
criterion is approved. When the criterion becomes effective, these definitions will be
removed from the criterion and added to the WECC Glossary.
Developed as WECC-0081 5
Management of Adjacent Data Points Criterion
INT-015-WECC-CRT-2
Version 5
Open: September 24, 2012 Closed: October 24, 2012
A. Introduction
1. Title: Management of Adjacent Data Points
2. Number: INT-015-WECC-CRT-2
3. Purpose: To define the process by which physical segment
adjacencies are included in the WECC Registry for
validation by the Western Interchange Tool (WIT)
4. Applicability
4.1. Balancing Authority
4.2 Transmission Service Provider
5. Effective Date: The first day of the first quarter following approval by
the WECC Board of Directors.
B. Requirements:
WR1. Each Balancing Authority and each Transmission Service Provider
entering an adjacency record(s) into the WECC Registry shall enter such
request no later than 12:00 p.m. (Central Prevailing Time) two days prior
to the desired activation time of that requested record, excluding
weekends and NERC holidays.
WM1. Each Balancing Authority and each Transmission Service Provider
entering an adjacency record(s) into the WECC Registry will have
evidence that it submitted adjacent data points in accordance with
WR1 above. Evidence may include, but is not limited to, time-
stamped records from the WIT reflecting the criteria required in
WR1.
WR2. Each Balancing Authority and each Transmission Service Provider listed
in the adjacency record(s) of the WECC Registry shall approve or deny
any request to activate an adjacency record, by no later than 12:00 p.m.
(Central Prevailing Time) of the day prior to the activation time of that
requested adjacency record, excluding weekends and NERC holidays.
WM2. Each Balancing Authority and each Transmission Service Provider
listed in the adjacency record(s) of the WECC Registry will have
evidence that it approved or denied adjacent data points in
accordance with WR1 above. Evidence may include, but is not
limited to, time-stamped records from the WIT reflecting the criteria
required in WR1.
Developed as WECC-0081 6
Management of Adjacent Data Points Criterion
INT-015-WECC-CRT-2
Version 5
Open: September 24, 2012 Closed: October 24, 2012
Guideline and Technical Basis
Overview
In order to facilitate efficient scheduling, an accurate list of adjacency records needs to
be maintained. There is no stated limitation in this criterion as to what entity may submit
an adjacency record for inclusion in the master list. The following recommendations are
made as to the most appropriate entity to perform the stated tasks.
It is recommended, though not required, that the Source Balancing Authority is the most
appropriate entity to register the adjacent Point-of-Receipt for the first physical
transmission segment listed on an e-Tag.
It is also recommended, though not required, that the Sink Balancing Authority is the
most appropriate entity to register the adjacent Point of Delivery for the last physical
transmission path segment on a given e-Tag.
Finally, it is recommended, though not required, that the Transmission Service Provider
should be the entity to register each path adjacency between each physical path
transmission segment and the prior and succeeding Scheduling Entity for a given e-
Tag.
As to WR1, for purposes of this criterion, the types of adjacency records addressed
include only the following types of records as listed in the WECC Registry, as used by
the Western Interchange Tool:
Path Definition
Source/Point-of-Receipt Adjacency
Point-of-Delivery/Sink Adjacency
Balancing Authority Adjacency
Developed as WECC-0081 7
