Open agl-cdrprogram opened 2 years ago
To be honest the Time of Use Type really doesn't look like a time of use if it also spans long ranges of dates too. I'm dubious about adding more ambiguous values into things as it will only be confused by implementers. What's wrong with specifying start/finish date information that just so happens to line up with Winter and Summer?
Description
We have a request for a CR to enhance the Billing API
Area Affected
This request is for a change to the Billing Energy API in segment DEMAND (Energy Billing Demand Transaction)
Change Proposed
Can we request to add enums: 'WINTER" & 'SUMMER" to the below list for supporting seasonal demand tariffs? Current 'timeOfUseType' for days containing following enums that we wish to add to: • PEAK • OFF_PEAK • OFF_PEAK_DEMAND_CHARGE • SHOULDER • SHOULDER1 • SHOULDER2 • CONTROLLED_LOAD • SOLAR • AGGREGATE