search

ConsumerDataStandardsAustralia / standards-maintenance

This repository houses the interactions, consultations and work management to support the maintenance of baselined components of the Consumer Data Right API Standards and Information Security profile.
41 stars 9 forks source link

Get Energy Account Detail API - Proposed Changes #517

Closed agl-cdrprogram closed 2 years ago

agl-cdrprogram commented 2 years ago

Description

In the Get Energy API we have identified some areas of concerns that should be addressed and have proposed to the following solutions to enable this to be better suited for Energy Retailers across the board.

Area Affected

We have noticed that there can be enhancements added to the fields:

  1. timeOfUseRates and demandCharges stored within the tariffPeriod section.
  2. Updates to the EnergyPlanSolarFeedInTariff for SingleTariff SolarFeedInTariff
  3. EnergyPlanControlledLoad / controlledLoad changes.
  4. New enum for 'public holiday' in the timeofuse 'days' field (EnergyPlanTariffPeriod).

Change Proposed

We are proposing to enhance these segments by adding additional fields/provisions to allow further detail to be provided, which allows for further context and complete tariff information.

GET ENERGY ACCOUNT DETAIL api.docx

agl-cdrprogram commented 2 years ago

Please reference this update version of the word doc.

CR#517_GET ENERGY ACCOUNT DETAIL api.docx

perlboy commented 2 years ago

It'd be good if requests can be placed in native format. It helps readers go through things faster and also means GitHub search works better.

TOU Tariff: Request to add provisions for surfacing below information in the ‘timeOfUse’ segment (of tariffPeriod section in Get energy account detail):

  • ‘MONTH’ (Start month – End month)’ (e.g., 1 November and 31 March) and/or
  • ‘SEASON’ (e.g., summer/winter)

Demand Tariff: Request to add provisions for surfacing below information in the ‘demandCharges’ segment (of tariffPeriod section in Get energy account detail):

  • ‘MONTH’ (Start month – End month)’ (e.g., 1 April to 31 May) and/or
    • ‘SEASON’ (e.g., summer/winter)

This looks like an overlap with https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/519 but for a different endpoint. MONTH makes sense (although start/finish date would be better imo) but I'm dubious about SEASON.

There are specific demand tariffs defined calculated as below: Peak demand applies 4pm -9pm weekdays and weekends all year. A minimum demand of 1.0 KW applies and off peak demand applies all other time. Therefore, request to consider above scenario and add/provide provisions for passing multiple start time and end time sections in the ‘demandCharges’ segment (of tariffPeriod segment of Get energy account detail api): In the current payload we can only provide one timestamp

This is incorrect. Many timestamps can be provided by providing many tuples in the array. Will this not work?

Can we request the current structure of 'EnergyPlanSolarFeedInTariff' (within GET ENERGY ACCOUNT DETAIL) to be updated to support representation of solarFeedInTariff with block rates/stepped rates applicable?

This looks like a duplicate of https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/520 ?

  1. The current ‘controlledLoad’ (EnergyPlanControlledLoad) segment within Get Energy Account Detail API, is an object and not an array structure and in this instance only one set of controlled load detail can be passed to the structure. However, there can be few instances where a customer has two controlledLoad tariffs applicable say e.g., both Tariff 31 and 33 rates applicable to customer’s account Is it possible to update same or provide feasibility for passing multiple ‘controlledLoad’ tariff details within this segment (as applicable)?

Making this an array will break other components of the payload. What about moving the period into the rates array within this object instead?

Request to add enum – ‘Public Holiday’ within the list timeOfUse – ‘days’ field

This looks like a duplicate of https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/502

I'm dubious about Public Holiday being introduced. Public Holiday where?

agl-cdrprogram commented 2 years ago

It'd be good if requests can be placed in native format. It helps readers go through things faster and also means GitHub search works better.

TOU Tariff: Request to add provisions for surfacing below information in the ‘timeOfUse’ segment (of tariffPeriod section in Get energy account detail):

  • ‘MONTH’ (Start month – End month)’ (e.g., 1 November and 31 March) and/or
  • ‘SEASON’ (e.g., summer/winter)

Demand Tariff: Request to add provisions for surfacing below information in the ‘demandCharges’ segment (of tariffPeriod section in Get energy account detail):

  • ‘MONTH’ (Start month – End month)’ (e.g., 1 April to 31 May) and/or
  • ‘SEASON’ (e.g., summer/winter)

This looks like an overlap with #519 but for a different endpoint. MONTH makes sense (although start/finish date would be better imo) but I'm dubious about SEASON.

Happy for SEASON to be a good to have, however we suggested it to provide a distinct representation of season for which tariff is being applied (i.e. WINTER/ SUMMER) as some demand/s are Season based (i.e. months may not be necessarily specified e.g Peak summer demand)

There are specific demand tariffs defined calculated as below: Peak demand applies 4pm -9pm weekdays and weekends all year. A minimum demand of 1.0 KW applies and off peak demand applies all other time. Therefore, request to consider above scenario and add/provide provisions for passing multiple start time and end time sections in the ‘demandCharges’ segment (of tariffPeriod segment of Get energy account detail api): In the current payload we can only provide one timestamp

This is incorrect. Many timestamps can be provided by providing many tuples in the array. Will this not work?

Sure, will look into this suggestion i.e. For representing two diff timestamps that are applicable for a single demandcharge - can repeat the demandCharges section (e.g.twice) for different timestamps.

Can we request the current structure of 'EnergyPlanSolarFeedInTariff' (within GET ENERGY ACCOUNT DETAIL) to be updated to support representation of solarFeedInTariff with block rates/stepped rates applicable?

This looks like a duplicate of #520 ?

Yes that's correct, consolidated all the Get Energy Account detail related proposals in CR517.

  1. The current ‘controlledLoad’ (EnergyPlanControlledLoad) segment within Get Energy Account Detail API, is an object and not an array structure and in this instance only one set of controlled load detail can be passed to the structure. However, there can be few instances where a customer has two controlledLoad tariffs applicable say e.g., both Tariff 31 and 33 rates applicable to customer’s account Is it possible to update same or provide feasibility for passing multiple ‘controlledLoad’ tariff details within this segment (as applicable)?

Making this an array will break other components of the payload. What about moving the period into the rates array within this object instead?

https://github.com/ConsumerDataStandardsAustralia/standards-maintenance/issues/472

Tariff31 & Tariff33 Controlled loads are two separate controlled loads registers/Rate type in a meter, each controlled load has its specific rate/ tariffs thus an array structure is required to pass multiple controlled load/s that are applicable during a particular time period Note: Also Tariff 31 & Tariff 33 controlled load are not a seasonal / stepped / blocked controlled loads tariffs, therefore, moving the period into the rates array within this object will not provide a correct representation of two separate Controlled Load/s

Hope this clarifies.

  1. Refer Link - https://www.ergon.com.au/retail/residential/tariffs-and-prices/economy-tariffs
  2. From EME refer:

image image

Request to add enum – ‘Public Holiday’ within the list timeOfUse – ‘days’ field

This looks like a duplicate of #502

I'm dubious about Public Holiday being introduced. Public Holiday where?

Happy to omit 'Public holiday' proposal request , however suggested it, as this may be utilised for commercial tariffs and might be a tranche 2 consideration. There are few tariffs (state / distributor specific) where • weekday rates gets applied for Public holiday or • weekend rates gets applied for Public holiday, and for better representation of for what day the tariff is applied, same was requested e.g refer links (pg – 29, 33, 37)- https://www.aer.gov.au/system/files/Powercor%20-%20APP05%20-%20Tariff%20structure%20statement%20reasons%20-%2031%20January%202020.pdf