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

Revise the Availability Requirements NFRs #660

Open jimbasiq opened 3 weeks ago

jimbasiq commented 3 weeks ago

Description

Some recent planned outages from data holders have been days in duration. This is damaging to the success of the CDR, it is eroding trust and driving data recipients to alternative data sources such as screen scraping.

Intention and Value of Change

We need data recipients and consumers to be able to trust in the stability of the CDR framework. We need data holders to carefully consider the impact to their customers when planning outages to CDR services.

Area Affected

Availability Requirements

Change Proposed

The proposal is to make the Availability Requirements NFRs binding and applicable for planned and unplanned outages - https://consumerdatastandardsaustralia.github.io/standards/?diff#availability-requirements

The proposed change is to make the 99.5% up time target a MUST for planned and unplanned outages so that there is a clear definition of what is expected of Data Holders.

Any planned outage that will exceet this parameter should be discussed with the ACCC as an exception.

JamesMBligh commented 1 week ago

I would like to voice support for this change. Since this issue was raised two weeks ago an energy retailer has published a 14 day planned outage. Clearly the current language is being taken advantage of.

It would be better to have the exclusion for planned outages to be removed from the definition of availability and then, if there is a real, justifiable, need for a prolonged outage a holder can discuss the need with the ACCC ahead of time to avoid any regulatory action.