CDR-API-Stream
commented
2 years ago Summary of issue:
- Solar tariffs can be stepped, see example - https://www.energymadeeasy.gov.au/plan?id=RED207686MRE7&postcode=2500
- The current standards allow providing multiple solar tariffs but don't allow explicit specification of stepped volumes that a rate may apply to.
Option 1 - Do Nothing
Use the description field in EnergyPlanSolarFeedInTariff structure to described the stepped rates. Multiple entries can be provided (one per stepped rate) as EnergyPlanSolarFeedInTariff structure is an array.
Option 2 - Update EnergyPlanSolarFeedInTariff with rates object
The EnergyPlanSolarFeedInTariff schema can be updated with the rates object used in other parts of energy standards such as EnergyPlanTariffPeriod. The volume field in the rates object could then be used to specify the volume of usage a particular rate applies to.
03/03/2023 Update The option is updated with optional startDate and endDate fields to accommodate seasonal rates as per the feedback in this comment.
The change would like as below:
"solarFeedInTariff": [
{
"displayName": "string",
"description": "string",
"startDate": "DateString", // Optional start date of the application of the feed in tariff
"endDate": "DateString", // Optional end date of the application of the feed in tariff
"scheme": "PREMIUM",
"payerType": "GOVERNMENT",
"tariffUType": "singleTariff",
"singleTariff": {
"rates": [ // mandatory - Array of rates
{
"unitPrice": "string", // mandatory- Unit price of usage per measure unit (exclusive of GST)
"measureUnit": [ "KWH", "KVA", "KVAR", "KVARH", "KW", "DAYS", "METER", "MONTH" ], // optional - The measurement unit of rate. Assumed to be KWH if absent
"volume": 0 // optional - Volume that this rate applies to. Only applicable for ‘stepped’ rates where different rates apply for different volumes in a period
}
],
},
"timeVaryingTariffs": {
"type": "PEAK",
"rates": [ // mandatory - Array of rates
{
"unitPrice": "string", // mandatory- Unit price of usage per measure unit (exclusive of GST)
"measureUnit": [ "KWH", "KVA", "KVAR", "KVARH", "KW", "DAYS", "METER", "MONTH" ], // optional - The measurement unit of rate. Assumed to be KWH if absent
"volume": 0 // optional - Volume that this rate applies to. Only applicable for ‘stepped’ rates where different rates apply for different volumes in a period
}
],
"timeVariations": [
{
"days": [
"SUN"
],
"startTime": "string",
"endTime": "string"
}
]
}
}
]FDO
- Any material change approved as part of this CR will not be implemented for November 15th 2022 energy go live and will have a future dated obligation date (FDO).
~- The DSB proposes a FDO date of 07/04/2023 from the obligation date schedule~ ~- Based on feedback, the proposed FDO date is now 15th May 2023 in alignment to tranche 2 release of energy sector.~ - Based on feedback during MI call on 8th March, the proposed FDO date is now 1st November 2023 in alignment to tranche 3 release of energy sector
Feedback on the solution options and FDO date is welcome.
perlboy
garychapman
rob-hale
DannyDuong
AGL-CDR
Description
During consultation on issue https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/472, the question of representation of stepped solar feed in tariffs in Energy APIs was raised.
This issue is raised to consult on if/how stepped solar feed in tariffs should be represented in EnergyPlanSolarFeedInTariff.
Area Affected
Change Proposed
This decision proposal is currently a placeholder. The DSB will publish recommended changes to be consulted on within the Maintenance Iteration it gets prioritised for.
DSB Proposed Solution
The current DSB proposal for this issue is in this comment. Note The comment was updated on 14th October 2022 with a "Do Nothing" option