Request Summary
Add WRAP identifier to tagging requirement to BPM205
Co-sponsors
Description Of Issue
There currently is no programmatic way to identify etags used to deliver energy through the WRAP program during a sharing event.
This effects to areas.
- Program participants are required to submit an After The Fact Energy Deployment (ATFED) file within 168 hours of energy delivery. To ensure reliability and accuracy of the submittal of information Chelan County PUD would like to automate the process of aggregating the data that underlies this file, which would require the programmatic aggregation of etag information.
- Chelan County PUD would like to automate both the creation, approval and denial of etags related to WRAP activities through its automated services, but currently cannot programmatically identify WRAP etag with certainty.
Proposed Solution
Chelan County Proposes to use the (token:value) pair inside the MISC info area within the physical path definition to distinguish WRAP etags.
Possible Combinations (token:value):
WRAP:ENERGY
WRAP:DLVRY
WRAP:HOLDBACK
Specific Document And Language
Once the specific changes have been identified and approved, the BPM205 document section 3.1 should be updated with additional requirements.
Suggested Language Update
"Program participants are required to enter a MISC info (token:value) pair of the following information into the physical path section of the etag [WRAP:ENERGY]".
Benefits
Program participants will be able to programmatically identify WRAP related etags for approval/denial and after the fact aggregation into datasets required in the AFTED file.
Data Or Information