-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design Paper: a peer-to-peer data access model in the energy sector #177
Comments
The following feedback was sent via email to [email protected] in addition to be posted here on behalf of Momentum Energy:
The second half of this feedback referenced the Joint Account Opt Out model and is submitted there. |
Commonwealth Bank supports the peer-to-peer approach proposed in the design paper, which aligns to the model used in the application of the CDR to the banking sector. This will lead to a more consistent participant and consumer experience. It will also enable the ecosystem to leverage the experience gained to date in implementing Open Banking, thereby mitigating possible security and integration challenges. |
AGL appreciates the opportunity to provide feedback on the issues raised in the Peer-to-peer access model in the energy sector paper (P2P paper). We welcome and are supportive of Treasury’s decision to move to a P2P model from the gateway model as this aligns with the position AGL has advocated for since the outset of the CDR consultation. As previously discussed with Treasury, we consider the P2P model the best model for the energy sector and for cross sectional functionality, with further reasons considered in our position below. We look forward to working with Treasury on developing the rules and standards framework of the P2P model that results in the most cost-effective solutions and drives a simple and easy to access energy CDR regime for consumers. We offer the following comments in relation to some of the questions raised in the P2P paper: Question 1: Rules considerations
|
Further to AGL's response to the P2P paper set out above, AGL provides the following comments in relation to 1.3 Standards consideration:
We look forward to participating further in this discussion through the technical standards working groups. |
Further to AGL's response to the P2P paper set out above, AGL provides the following comments in relation to Section 2: Customer Accounts:
|
Origin Energy appreciates the opportunity to provide input into the development of a Peer-to-Peer (P2P) Data Access Model in the energy sector. In principle, we support the move to a P2P Model. We believe that it will allow for greater privacy and data security protections of consumer data and appears less complex than the manner in which the Gateway model which was being developed and consulted on in DP 140. Origin did not support AEMO (ie the Gateway) being the master of consumer consent. However, the effectiveness of this is dependent on the development of optimal and efficient rules and standards – this includes the development of standards for the exchange of data between retailers and AEMO. There are a number of outstanding questions and comments in relation to the operation of the P2P model. These include: • Whether AEMO or the DSB are responsible for developing data transfer standards for the exchange of data such as DER, NMI standing data and meter data if necessary. Given that retailers will be relying on AEMO to provide the data as a ‘secondary data holder’, there should be service level requirements on AEMO; • Scope of consumers to be included as an ‘eligible consumer’ for energy CDR. The size of the consumer will be critical to both the rules and standards development. Large consumer accounts are complex and solutions will vary depending on how consumers are defined. This has not been addressed in the Design Papers; • It is unclear whether retailers will have any role with regards to generic product data. Retailers will not be the data holder for this data, but it is unclear whether the ADR will go directly to Energy Made Easy or Victoria Compare or whether retailers will have any role with authentication. The Design Paper does not appear to address this issue; and • We agree that consumers should be able to select which accounts that they provide consent to share. Energy consumers could have multiple accounts (ie same consumer has a residential and a separate business account or the same consumer has a separate electricity and gas account). The term ‘account’ may be an appropriate term that could be applied across sectors, however, technically it may need to be defined differently for energy in standards. It will need to be determined whether account is defined by NMI/MIRN, account number, site ID, consumer ID or some other relevant means to the energy sector. Origin would be keen to have further discussions with the DSB on this issue. Further details with regards to the above issues, can be found in our detailed response to the Treasury Design Paper. It is noted that the DSB developed several wireframes to assist with the visualisation of how the rules and standards would appear in systems. We appreciate and thank the DSB for this assistance. Specific comments on the wireframes for the P2P Model are set out below. 1) Wireframe - 2.2 Energy | P2P Model • Step 2a - Can a consumer select more than one data holder? We understand that this is vanilla scenario example, however we are unclear how it will work for multiple properties or multiple Data Holder scenarios? OR is it always only one data holder at a time? • Step 3 – We request clarification of the term ‘sharing period’? Is it possible that the ADR will default the sharing period to 12 months as they are unsure how long the consumer has been active with the retailer? Or does it allow the ADR to request just 6 months of data (ie they include the dates which the consumer has supplied of being with the retailer)? Or does it mean going forward, ADR can request consumer’s data anytime within this period? • Step 6 – Is it the retailer (or the Data Holder) to determine which field of information that they will use to authenticate the consumer? That is, the retailer could use phone number, email address, date of birth or any other field? We also seek confirmation that authentication for energy will be online only. We do not support offline authentication. • Step 9 – Previous energy rules consultations suggested that there may be additional consent or authorisation requirements for sensitive data. Sensitive data referring to concessions, direct debt details or hardship information. Is sensitive data categories still being considered and it yes, how will they be added to the authorisation flow? • Step 10 - Between step 10 and 11, does there need to be additional steps where a data holder sends the confirmation email to the consumer notifying that they have authorized to share data from XX data cluster (including AEMO specific data clusters) for YY period with an ADR? • Step 13 - If a consumer has three properties with a data holder -
• Step 13 – Extending from previous comment, for cross-sector, is it assumed all the data clusters will be applicable for all accounts across all sectors? 2) Wireframe - Cross-sector | Electricity and Gas accounts with the same provider (hypothetical) • Step 3 – What if the authorisation field is different between electricity and gas? That is, the consumer has an electricity and gas account, but they have been entered into at separate times. One account may have one mobile number and the other account a different account number. What will happen if the authorisation for the 2 accounts do not match? Also, when different data holders use different portals to authorise – how will this operate? • Step 4 - Does it depend on the ADR sending the request as well? What happens if an ADR is accredited only for a specific sector and not both – will the Data Holder portal still shows cross- sector accounts for selection? • Step 5 - From a cross-sector perspective, is it an assumption that data clusters will be uniform and applicable across all sectors? Or will the data cluster selection be specific and unique for each account? • Step 8 – We seek confirmation of this step - Are the two portals supposed to be in sync and talking to each other every time a change is made on one side (ADR or DH)? How does it currently work for banking? For example, if a consumer updates (withdraws) CDR consent for a data set on an ADR’s portal, does this information flow to the DH on an instantaneous basis? or is there a delay in this information flowing to the DH or it depends on a consumer updating authorisation explicitly on DH portal as well? |
Good afternoon everyone, |
In response to the submissions from @SarahSilbertAGL: The rules specific feedback will be collated and passed to the Treasury rules team for consideration. There were, however, a number of comments specifically related to the need to separate responsibility for data between retailers and AEMO. These will also be taken into consideration when amending the non-functional requirements section of the standards to facilitate the introduction of the concept of a secondary data holder. In response to specific feedback:
This is helpful feedback and could be used as a general principle for the development of standards between primary and secondary data holders or between designated gateways and data holders. This will be incorporated into the consultations on the end points to be exposed by AEMO to support the P2P model.
This is helpful feedback for the standards as we adopt the second sector. The possibility of multi-sector data holders and the need to reduce implementation costs by limiting bespoke builds will need to be considered in subsequent technical consultations.
This is certainly the intent of the CX standards and aligns with the standards for the development of both technical and CX standards. |
In response to additional feedback from @SarahSilbertAGL:
Thank you for this feedback.
This is essentially driven by the designation instrument so can only be commented on by the policy teams within Treasury. From a standards perspective, the standards will be developed to align to the rules and the designation instrument. |
In response to the standards specific feedback from @PratibhaOrigin:
The DSB concurs with this statement. Feedback on what would be considered optimal and efficient by the existing participants of the energy sector would be welcome in upcoming consultations.
It is understood that this will be done by standard CDR standards development processes. The DSB will provide advice to the Data Standards Chair who has the authority to make binding standards.
The design paper does not address this as this is not an area of the designation that is impacted by the P2P model change. Generic product data will be delivered to ADRs by EME and VEC using data provided to them by retailers as per the current designation instrument for the energy sector.
This is helpful feedback and aligns with feedback from other contributors.
Thank you for this detailed feedback. It has been noted by the CX team. Questions that can be immediately addressed are responded to below.
The authorisation part of the consent flow can only be exercised per data holder as the data holder needs to authenticate the user and complete authorisation separately.
While the ADR can request a sharing duration of the consumer it is required that the consumer can elect how long they are comfortable sharing during.
Yes. The standards currently require that the authentication process will uniquely identify a consumer and the expectation of the rules is that all eligible consumers can be authenticated but, within constraints of this nature, there is latitude for the data holder how authentication is done due to the variation that exists with existing authentication processes.
The consideration for these has been to move them to a separate, dedicated scope, so the consumer has direct control of the sharing of these fields. This is currently addressed in the draft energy standards.
We will take this question on notice.
The scopes and sharing duration are common for a single authorised consent and apply to all associated accounts. If separate scopes are required for different accounts then this would be serviced by an ADR through the creation of multiple concurrent consents.
No. There will be no requirement for retailers to support banking data clusters or for banks to support energy sector data clusters. The requirements for specific data holders to support specific data clusters is driven by the designation instruments. If a specific organisation meets the data holder criteria for multiple designations (for instance, a bank that is also an energy retailer) then it is understood that data clusters for each of the applicable designations will need to be supported.
As we are at the consultation stage for the energy sector with regards to the concept of account (that is one of the subjects of this consultation) this hypothetical can not yet be definitively answered. Scenarios of this type, however, will be very helpful to test solutions as they emerge in future consultations.
There is currently no specific guidance on these questions. This will be worked out in subsequent consultations.
Data clusters will be consistent wherever applicable. Only the customer data cluster is currently designated for both energy and banking sectors.
The only change that is currently supported via dashboards is revocation. When a revocation occurs the other party must be notified. This is required by the rules and supported in a cross-sectoral manner in the current standards. |
Thanks for all of the feedback. This consultation is now labelled as feedback closed but we will leave this thread open in case there are any clarifications or responses to the feedback given by the DSB above. |
Having reviewed the design paper: a peer-to-peer data access model in the energy sector #177, I have the following comments: How will the peer-to-peer model support the simple authentication model for historical energy usage and export data? Accessing consumption and export data will likely be the highest volume usage of the CDR for energy but the peer-to peer data access model does not recognise the need for that feature to be implemented with a lower level of authentication as is supported through existing manual process (meter data requests through network operators and automated meter data acquisition used by Energy Made Easy and Victorian Energy compare). This requirement for low authentication was proposed by multiple submissions including:
There is no reference to how this will be supported in the peer-to-peer model so it appears that the request from the majority of comparators (who made submissions previously) and who are potential ADRs will not be supported. With all due respect if these features aren't supported this will directly impact the number of ADRs who will leverage the CDR due to the higher costs and consumer complexity inherent in the strong authentication approach. This will directly impact consumers who will have less choice in the service providers who offer comparisons using meter data from the CDR. As a more general comment, the CDR looks increasingly expensive and complex for potential ADRs like us (WATTever) to implement as time goes by. |
The following public consultation, for the peer-to-peer model for the energy sector, is open for feedback.
We invite all participants in the Consumer Data Right to submit their feedback below as part of this GitHub consultation.
The date of closure of consultation is: 26th of May 2021
Link to the consultation: https://treasury.gov.au/consultation/c2021-168954
Context
This consultation is opened in support of the recent announcement from the Treasury, which proposes design options around rules and standards to implement a peer-to-peer model for the energy sector and on an opt-out data sharing model for joint accounts.
This announcement also includes information relating to a change in the gateway model for the energy sector. The implications of this change in direction are the subject of this consultation.
Design Paper
A design paper is a new consultation approach being trialled that intends to provide an opportunity for simultaneous consultation on the rules, policy, standards and guidelines for a change to the Consumer Data Right. In the past we have worked together to solve implementation questions and challenges by first defining Rules and Standards and then requesting comment. A design paper lets participants comment on the implications of proposed Rules and Standards, before they are defined. Where applicable, a design paper will also include consumer experience mock-ups to demonstrate the implementation and how that may affect existing participant's systems.
Providing Feedback
A design paper will elicit feedback to be consumed by multiple teams. Feedback on the standards can be provided here and the DSB will respond directly as per usual. Rules and policy feedback can also be provided here and the DSB will seek to clarify this feedback and then provide it to the appropriate team for consideration.
To assist the feedback process. We ask that you use the numbered reference assigned to each of the paragraphs in the design paper.
Feedback can also be provided via email to [email protected] or to [email protected]. As per usual practice email submissions will be made public unless a request is included to keep the submission private. While we appreciate that some submissions may need to be private the fact that they will not be available for community discussion necessarily means we will not be able to give them the same consideration as public feedback.
The text was updated successfully, but these errors were encountered: