Implementing Preemption ARef Tag Validation for Transmission Services
"Learn about implementing Preemption ARef Tag Validation for transmission services, following the NAESB WEQ standard. Find out how to handle flagged reservations and ensure compliance with the competition flag requirement. Get insights on the upcoming release of the Scheduling Transmission Service Business Practice." (268 characters)
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Preemption ARef Tag Validation CBPI October 16, 2024 Mike Anderson
B O N N E V I L L E P O W E R A D M I N I S T R A T I O N Summary Preemption Aref tag validation implements NAESB WEQ standard. WEQ-001-25.4.4.2.3 says: "While a reservation is flagged, the Transmission Provider may deny an RFI that references that reservation until the competition flag is cleared." Error message on eTag: AREF is involved in a Preemption This means that the AREF is involved in a Preemption as either a Defender or a Dependent. Note: An e-Tag that uses a Blanket contract in the OASIS field can still be approved against a conditional reservation even if the Competing Request Flag has already been set for that reservation. This tag validation will be included in the next release of the Scheduling Transmission Service Business Practice. Scheduled to be turned on in Production on 10/22/2024 at 11:00 am. 2
B O N N E V I L L E P O W E R A D M I N I S T R A T I O N Example (1 of 2) TSR 73136834 is Defender with Competing Request Flag = 3885. Tag MA10011 is then created with TSR 73136834 as its OASIS number. 3
B O N N E V I L L E P O W E R A D M I N I S T R A T I O N Example (2 of 2) Tag MA10011 fails the Preemption Aref tag validation for TSR 73136834. Error message appears in Reason/Comment field of Approval Status History for tag. 4
