Document name
After-the-Fact Tagging Guideline
Category
( ) Regional Reliability Standard
( ) Regional Criteria
( ) Policy
(X) Guideline
( ) Report or other
( ) Charter
Document date
April 23, 2015
Adopted/approved by
Interchange Scheduling and Accounting
Subcommittee Committee
Date adopted/approved
Custodian (entity
responsible for
maintenance and
upkeep)
Stored/filed
Physical location:
Web URL:
Previous name/number
Reclassified from WECC Criterion (INT-019WECC-1) to the current WECC Guideline
Status
(
(
(
(
(
(
Developed as W ECC-0075
) in effect
) usable, minor formatting/editing required
) modification needed
)
superseded
by
)
other
) obsolete/archived)
June 13, 2011
WECC Guideline
After-the-Fact Tagging Guideline
Introduction
On October 27, 2010, the Standards Request Routing Committee assigned W ECC0075/INT-019-W ECC-CRT-2 to the Operating Committee (OC) for development. The primary
task of the project was to modify the purpose statement of INT-019-WECC- CRT1. After three postings for comment on the proposed modifications, the WECC-0075
drafting team concluded by unanimous vote that INT-019-WECC-CRT-1 was more
accurately a W ECC Guideline as opposed to a W ECC Criterion.
On July 14, 2011, the WECC-0075 drafting team recommended to the OC that the substance
of INT-019-WECC-CRT-1, along with the work product of the W ECC-0075 drafting team, be
combined into a single document and approved by the OC as a W ECC Guideline. This
document is that W ECC Guideline.
Purpose
The purpose of this WECC Guideline is to establish the process for the creation and use of
After-the-Fact (ATF) e-Tags or ATF tags. This Guideline applies only to the creation of new
ATF tags used for correction purposes. It does not apply to e-Tags created after the fact for
reserve sharing programs unless approving entities deem otherwise. See Appendix 1 for
further details including common reason when ATF tags are created.
Background
ATF tags are used to allow Balancing Authorities (BAs or CAs), Transmission Service Providers
(TSPs), and Scheduling Entities (SEs) to accurately reflect a schedule which was coordinated
and controlled to by a BA’s Energy Management System (EMS) and Automatic Generation
Control (AGC) system during real time system operations, but was not properly tagged.
Guideline
This WECC Guideline applies to BAs, TSPs, SEs entering into ATF tag arrangements.
The source or sink will take the lead in coordinating and processing the ATF tag and if necessary the
WIT Schedule Change Request Form. All CAs, TPs and SEs involved, from Source to Sink, must
agree to proceed with the processing of an ATF tag. The following common process flow is a useful
guide for creating ATF tags. These steps can be done in any order, as agreed to by those involved;
however, it is usually helpful to follow the process in the order as noted below.
Common Process Flow for ATF tags and/or WIT Schedule Change Request Form:
1. Call and/or email all parties involved on the tag when an ATF tag is needed and gain agreement to
proceed.
2. Coordinate changes needed within the timeframe for processing/submitting the ATF tag.
3. Route WIT Schedule Change Request Form to all parties for signatures.
4. Submit the WIT Schedule Change Request Form to the WIT Administrator and copy all parties
involved.
5. After WIT Administrator responds that the changes have been completed, all parties should verify
that the changes were made properly in the WECC Interchange Tool (WIT).
6. Submit the ATF tag by 2:00 p.m. (MST) on the same day that the WIT Administrator makes the
changes to WIT, inform all involved parties that the tag is out for approval and reference the new tag
number.
7. The lead BA will follow up that ATF tag was approved.
8. Each entity will update its in-house scheduling software to reflect the changes (adjust or zero MW
on the original tag schedule) and if necessary verify that the resultant Net Schedule Interchange
matches with WIT for that particular hour.
ATF Tags
ATF tags can be created up to 168 hours (one week) after the start time and are processed per
NAESB e-Tag Specifications.
Prior to submitting an ATF tag, all involved parties need to agree upon the requested changes. It is
important to note that changes can only be made to correct the tag to properly reflect the coordinated
and controlled to system operations at the time.




The lead entity shall coordinate with all parties involved to make sure all agree to the start time,
stop time, MWhs, integrated values if necessary, reservation numbers, etc.
One of the easiest ways to create an ATF tag is to make a copy of the original, incorrect tag
and make the necessary corrections.
If the ATF tag is replacing an original tag it should be noted in the comments that this is an ATF
tag replacing an original tag. It is helpful to name the tag with reference to ATF. This allows for
ease of locating the tag in the queue and helps preserve the relationship to the original tag.
o For example, in naming the ATF tag, original tag name ABC1234 would be replaced by
ATF tag ATF1234.
Once the ATF tag is submitted, all involved parties must be informed that the tag is ready for
approval and the new tag number should be referenced.
Each entity should notify the responsible tag approver within its company that an ATF tag is being
submitted so that it can promptly be approved. Many ATF tags fail automatically for tag timing or time
out because the operator or approver was not aware that either the tag was valid or that it was in the
queue waiting for approval.
WIT Schedule Change Request Form
A WIT Schedule Change Request Form is only necessary when the original tag is being zeroed out
and/or replaced by an ATF tag or when MW values require an adjustment down for reliability reasons.
The lead entity shall complete the WIT Schedule Change Request Form and route to all involved
parties for signatures. Once all signatures have been compiled, submit the WIT Schedule Change
Request Form to the WIT Administrator at disputereports@wecc.biz (or whatever email address the
WIT Administrator may use in the future) and copy all parties involved.
After the WIT Administrator responds via email that the changes have been completed, all parties
should verify that the changes were made properly in WIT.
A WIT Schedule Change Request Form is not necessary when MW values require an adjustment up.
In this case, an ATF tag should be processed for the MW difference only (for example: original tag is
for 5 MW and it should have been for 7 MW as it was controlled to at 7 MW, the ATF tag would be for
2 MW). Because a Tag is processed and it impacts WIT no manual adjustments are necessary.
Treatment of Original Tag and BA Adjacency Checkout
Once an ATF tag has been implemented it may be necessary for those involved to update in-house
scheduling systems to reflect the changes made. For example, if a tag has been replaced by an ATF
tag, the original schedule should be adjusted to show zero MWhs as the ATF tag schedule shall
replace the original tag schedule. The original tag will remain in the tagging and/or scheduling system;
however, its schedule will be manually adjusted to zero. If MW values are adjusted up and an ATF tag
is processed for the difference, no updates will be required to in-house scheduling systems. However,
if MW values are adjusted down, in-house scheduling system should be adjusted accordingly.
Affected BAs should also verify WIT adjacency checkout numbers due to any ATF change.
Appendix 1
Reason to Create ATF Tags



ATF tags are used by Balancing Authorities (BAs or CAs), Transmission Service Providers
(TSPs), and Scheduling Entities (SEs) to accurately reflect a schedule which was coordinated
and controlled by a BA’s Energy Management System (EMS) and Automatic Generation
Control (AGC) system during real time system operations, but was not properly tagged.
Inaccuracies or errors creating a hardship for the BA to accurately represent what actually was
controlled to during real time operations.
Shall not be used generation imbalance or for market driven situations.
Reserve Sharing Tags
Reserve Sharing tags are created after an event occurs to properly reflect those participants receiving
and delivering MWs in a particular hour(s). Tag templates are used to account for reserve sharing
events. The paths chosen for the tag templates may or may not be the actual path that the energy
takes during an event. These tags are created after an event occurs, and their creation does not fall
under this guideline. Only an error requiring a correction falls under this guideline. The following are
examples of such instances:
 System failed to create Reserve Sharing (RSH) tag
 System created duplicate RSH tag
 Entity incorrectly denies a RSH tag
 Tag hours were incorrectly identified