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

Extend Get Generic Plan Detail to include a new field: `tariffCode` #662

Open RichardFoxworthy opened 2 months ago

RichardFoxworthy commented 2 months ago

Description An electricity meter will be assigned to a tariff type by the relevant DNSP. The tariff type defines the time periods for various tariff types, such as peak, off-peak, and shoulder, and also defines the network charges that the responsible retailer must bear for the consumption recorded by that meter. There is a single tariff-type assignment for each meter.

In general, retailers will align the tariff period definitions in their retail plans with the tariff types defined by DNSPs, but they are not obliged to.

Retailers are free to define their own tariff periods in the plans they offer to consumers, so they may offer ToU plans with time periods that do not align with the time periods for a DNSP-defined tariff code, or they may offer single-rate plans to consumers who are on a ToU tariff assignment.

This makes it impossible to know with certainty which plans are relevant and available to individual consumers.

Intention and Value of Change If the Generic Plan Detail data in CDR were to include a reference to the DNSP-defined tariff type/code(s) to which the retailer will make each plan available, it would be possible for users of the CDR Get Generic Plan Detail data to know with much greater certainty which plans are relevant and available to an individual consumer, based on the network tariff assignment for that consumer's meter.

Area Affected Get Generic Plan Detail

Change Proposed The Get Generic Plan Detail endpoint should be extended to include a new field: tariffCode

This field will contain the DNSP-defined tariff code(s) to which the retailer makes this plan available.

mattyp commented 6 days ago

+1

Without the tariffCode(s) that the plan is available to, there is a real chance of consumers being recommended plans that aren't available to them. This is because retailers make the plan available only to service points with meters registered with given tariffCodes but that requirement is not known outside the retailer. While CDR consumer data includes the tariff code that each meter is registered with, PRD of plan details does not include which tariff codes are required.

Currently, we see some retailers embedding a hint of the required tariff codes in the name of the plan (e.g. plan RED758437MRE5@EME has name of Living Energy Saver (SunSoak: BLNRSS2) where BLNRSS2 is the TOU tariff code that the plan is made available to. But mostly, there is no indication of the tariff code requirements for each plan.

It would make sense for such a property to be under electricityContract, alongside meterType and pricingModel.