-
Notifications
You must be signed in to change notification settings - Fork 56
ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 4th of August 2022
When: Weekly every Thursday at 3pm-4.30pm AEST
Location: WebEx, quick dial +61-2-9338-2221,,1650705270##
Meeting Details:
Desktop or Mobile Devices
https://treasuryau.webex.com/treasuryau/j.php?MTID=m9614a7c6166155d3d950a8999e437f9f
Once connected to your meeting remember to start your audio and video
Please mute when you are not speaking.
Video Conferencing (VC) Rooms
Use the remote control or touch panel and dial the number indicated below:
External VC Room: [email protected]
Phones - AUDIO ONLY
- Primary Australia: +61-2-9338-2221
- Quick Dial: +61-2-9338-2221,,1650705270##
- Other Global Numbers: https://treasuryau.webex.com/cmp3300/webcomponents/widget/globalcallin/globalcallin.do?MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&MTID=m311f46c87a3ab9ae5335a6c0ea431da4&serviceType=MC&serviceType=MC&serviceType=MC&siteurl=treasuryau&siteurl=treasuryau&siteurl=treasuryau&apiname=globalcallin.php&apiname=globalcallin.php&apiname=globalcallin.php&rnd=6124483603&rnd=6124483603&rnd=6124483603&tollFree=0&tollFree=0&tollFree=0&ED=1403111402&ED=1403111402&ED=1403111402&needFilter=false&needFilter=false&needFilter=false&actappname=cmp3300&actappname=cmp3300&actname=/webcomponents/widget/globalcallin/gcnredirector.do&actname=/webcomponents/widget/globalcallin/gcnredirector.do&renewticket=0
- Meeting Number/Access Code: 165 070 5270
- Introductions
- Actions
- CDR Stream updates
- Presentation
- Q&A
- Any other business
- 5 min will be allowed 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.
Type | Topic | Update |
---|---|---|
Standards | Version 1.17.0 Published | Link to change log here |
Standards | Version 1.18.0 to incorporate changes from Maintenance Iteration 11 | Timing to be confirmed |
Maintenance | Maintenance Iteration 12 | First meet on the 20th of July 2022 |
Maintenance | Maintenance Iteration 12 | Next week on the 3rd of August 2022 the Working Group will meet |
TSY Newsletter | To subscribe to TSY Newsletter | Link here |
DSB Newsletter | To subscribe to DSB Newsletter | Link here |
TSY Newsletter | 1st of July 2022 | View in browser here |
DSB Newsletter | 29th of July 2022 | View in browser here |
Consultation | Normative Standards Review (2021) | No Close Date Link to consultation |
Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
Noting Paper | Noting Paper 255 - Approach to Telco Sector Standards | Link to consultation |
Consultation | Decision Proposal 256 - Telco Endpoints Feedback closes: 12th of August 2022 |
Link to consultation |
Consultation | Decision Proposal 257 - Customer Data Payloads for Telco Feedback closes: 12th of August 2022 |
Link to consultation |
Noting Paper | Noting Paper 258 - Independent Information Security Review | Link to consultation |
Guidance | Update: Links correct on Power of Attorney and Nominated Representative | CDR.gov.au Link |
Provides a weekly update on the activities of each of the CDR streams and their stream of work
Organisation | Stream | Member |
---|---|---|
ACCC | CDR Register | Emma Harvey |
ACCC | CTS | Andrea Gibney |
DSB | CX Standards | Amy Nussbaumer |
DSB | Technical Standards - Energy | Hemang Rathod |
DSB | Technical Standards - Banking | Mark Verstege |
DSB | Technical Standards - Telecommunications | Brian Kirkpatrick |
DSB | Technical Standards - Engineering & Register | James Bligh |
None this week.
Questions will be received by the community via WebEx 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 |
---|---|---|
1423 | Can DSB confirm the Data Holder is required to return the following API’s on closed accounts (where the customer is eligible) as per Schedule 4, 3.2(7): • Get Service Points • Get Service Point Detail • Get Usage For Service Point • Get Bulk Usage • Get Usage For Specific Service Point • Get Balance For Energy Account • Get Bulk Balances for Energy • Get Balances For Specific Energy Accounts • Get Invoices For Account • Get Bulk Invoices • Get Invoices For Specific Accounts • Get Billing For Account • Get Bulk Billing • Get Billing For Specific Account In relation to the above we are unclear if Service Point API's are required for closed accounts. For example, Service Point APIs would not be relevant as these would relate to today's details - e.g. today the NMI could be extinct, whereas last year it was active. |
Please note we have raised a decision proposal which recommends changes to the energy standards for sharing of closed account information. The proposal should help answer the question raised in this ticket. It would be really helpful if you could review the proposal and provide any feedback as it relates to the question asked. |
1384 | I will rephrase my question to clarify our understanding after reading rules: Schedule 4, 3.2, subclause 7 Despite subclause (2), for an account that is closed at a particular time, each of the following is not required consumer data: (a) CDR data held by AEMO, other than metering data; (b) CDR data held by a retailer, other than billing data; and (c) CDR data that is not excluded by paragraph (a) or (b), but relates to a transaction or event that occurred more than 2 years before that time. 1) Get Accounts API: We agree that as long as the CDR consumer is eligible, the Get Account API will list all accounts open or closed within the last 2 years as eligible accounts. 2) Get Account Details API if the account is closed Based on the above rule, our interpretation is that we do not need to provide any data other than billing data. Is out understanding correct. 3) Get Account Details API if the account is open A customer could be on a plan A last year, and could be on a plan B this year. And for a customer who could have been with a retailer for many years, there could be many plans. We were of the opinion, that we were to only supply the current plan. However, your response suggests that we need to provide historical plans as well. Questions: A) If we need to send historical plans, we need to understand how far do we have to go back. Is it 24 months? We are not obliged to provide data for more than 2 years. B) If we need to include historical data, why has this API not been designed to include the following in parameter query - newest-date & oldest date as we have done for Get Invoices for account and Get Billing for Account. |
Please note we have raised a decision proposal which recommends changes to the energy standards for sharing of closed account information. The proposal should help answer the question raised in this ticket. It would be really helpful if you could review the proposal and provide any feedback as it relates to the question asked. |
View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.