ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 4th of July 2024
When: Weekly every Thursday at 3pm-4:30pm AEDT
Location: Microsoft Teams
Meeting Details: Join on your computer, mobile app or room device Click here to join the meeting
Meeting ID: 446 019 435 001
Passcode: BU6uFg
Download Teams | Join on the web
Join with a video conferencing device
[email protected]
Video Conference ID: 133 133 341 4
Alternate VTC instructions
Or call in (audio only)
+61 2 9161 1229,,715805177# Australia, Sydney
Phone Conference ID: 715 805 177#
Find a local number | Reset PIN
Learn More | Meeting options
- 5 min will be al lowed for participants to join the call.
We acknowledge the Traditional Custodians of the various lands on which we work today and the Aboriginal and Torres Strait Islander people participating in this call.
We pay our respects to Elders past, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.
The Consumer Data Right Implementation Calls are recorded for note taking purposes. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material shall be provided without the participant's consent. Participants may [email protected] should they have any further questions or wish to have any material redacted from the record.
By participating in the Consumer Data Right Implementation Call you agree to the Community Guidelines. These guidelines intend to provide a safe and constructive space for members to discuss implementation topics with other participants and members of the ACCC and Data Standards Body.
⭐ indicates change from last week.
| Type | Updated | Links |
|---|---|---|
| Standards ⭐ | Version 1.31.0 | Published: 3rd of July 2024 Change log |
| Maintenance ⭐ | Iteration 20 Kick-off is 10th of July 2024 |
Sign-up and Register Data Standards Body Events |
| Maintenance ⭐ | Iteration 20 Schedule: 10/07/2024 Kick-off and backlog review 24/07/2024 Consultation 7/08/2024 Consultation and new issue checkpoint 21/08/2024 Proposal Checkpoint 4/09/2024 Approvals and Documentation |
Agenda page to come |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| DSB Newsletter ⭐ | 28th of June 2024 | View in browser here |
| Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
| Consultation | Noting Paper 279 - Accessibility Improvement Plan | No Close Date Link to consultation |
| Consultation | Noting Paper 323 - NFR Workshops | Link to consultation |
| Consultation | Noting Paper 348 - Use Case Enablement Experiment: Account Origination |
Open for comment: 12th July 2024 Link to Noting Paper |
| Consultation | Noting Paper 351 - LCCD Risk workshop summary | No feedback sought Link to Noting Paper |
| Action ⭐ |
Maintenance 20 Sign Up Sign Up on the DSB Events Calendar |
Please check your registration and calendar entry for MI 20 |
Provides a weekly update on the activities of each CDR stream and their work.
| Organisation | Stream | Member |
|---|---|---|
None this week.
Questions will be received by the community via Microsoft Teams chat before the questions are opened to the floor. Participants can submit questions outside of the CDR Implementation Call to the CDR Support Portal.
In regards to topics for questions, we ask the participants on the call to consider the Community Guidelines when posing questions to the subject matter experts.
| Ticket # | Question | Answer |
|---|---|---|
| 2378 | We wanted to seek clarification on the following - Is it mandatory for a Data Holder to support the Amend Authorisation/Consent flows? With reference to the CDR Rule 1.14 (2A) “The consumer dashboard may also include a functionality that allows a CDR consumer to amend a current consent." The support for Amending Consents is optional for the ADRs, is this also optional for Data holders? We do currently support Amending Consents but are considering turning off if not mandatory to do so. |
We note that an accredited person may invite a CDR consumer to amend a consent in accordance with the criteria set out in rule 4.12B of the CDR Rules. As you have noted, an accredited person may but is also not required to include a functionality on the consumer dashboard that allows a CDR consumer to amend a current consent (see rule 1.14(2A)). However, a data holder must invite the CDR consumer to amend a relevant authorisation, in accordance with Division 4.4 of the CDR Rules, if it receives a notification from an accredited person or CDR representative principal that a CDR consumer has amended their consent (see rule 4.22A). This means while it is optional for an accredited person to invite a CDR consumer to amend a consent, a data holder is required to invite a CDR consumer to amend an authorisation if the data holder has received a relevant notice under rules 4.18C or 4.20S. We note that this is a civil penalty provision (see rule 9.8). We also note that data holders are also required to display details of each amendment (if any) that has been made to an authorisation on the consumer’s dashboard (see rule 1.15(3)(h)). This is also a civil penalty provision (see rule 9.8). |
| 2373 | We've observed that the usage data available covers only the past year. From my understanding of the rules snippet attached, transactions within the last two years are deemed required data. Would usage data fall under this category of transactions? | Schedule 4, clause 3.2(7)(c) (from your snippet) of the CDR rules specifies that for a closed account, any CDR data not excluded by 3.2(7)(a) or (b) that “relates to a transaction or event that occurred more than 2 years before” is not required consumer data. This means that for an eligible CDR consumer, metering data held by AEMO (referred to as usage data in your query) for the period of less than 2 years before the date of a consumer data request is required consumer data for closed accounts. For open accounts, the same period of 2 years applies – see rule 3.2(2)(b)(iii)(B) of schedule 4. However, we note that there may be valid reasons that metering data for the entire period is not disclosed by AEMO. For example – the consumer may have switched energy retailers 12 months ago. To resolve individual instances of this issue we encourage you to raise an incident in the CDR Service Management Portal. Additionally, if you have further queries or wish to provide additional information on the issue, please contact us via [email protected]. |
Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.
View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |