DSB Maintenance Iteration 11: Agenda & Meeting Notes (14 June 2022) - ConsumerDataStandardsAustralia/standards GitHub Wiki

Date and time: 14/06/2022, 2:00pm – 4:00pm AEST

Location: WebEx

Dial-in details:

Chair: Hemang Rathod, DSB

Maintenance overview: Further information

Maintenance project board: See here

Decision Proposal: This maintenance iteration is being consulted on under Decision Proposal 249

Recording

The Maintenance Iteration Calls are recorded for note taking purposes only. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material will be provided without the participant's consent. Participants may email [email protected] should they have any further questions or wish to have any material redacted from the record.

Acknowledgement of Country

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.

Agenda

  • Introductions
  • Energy CRs under consultation
  • Any other business
  • Next Steps

Meeting notes

Introductions

This week is the fifth and an additional call in the 11th maintenance iteration series.

The purpose of the meeting is to consult on additional Energy candidates that we anticipate completing in the 11th maintenance iteration.

For full details on the Decision Proposal, Future Plan and Backlog please refer to the 8/06/2022 MI Agenda

  • Housekeeping
  • Discuss Energy CRs

Iteration 11 Issues

All open change requests can be found here: Standards Maintenance Issues.

Iteration 11 Progress

The following change requests are proposed for this iteration.

Energy CRs under consultation

Issue # Sector Change Request Proposed Outcome Change Type Future DatedObligation (FD) Affected Schema(if applicable) Affected Endpoint(if applicable)
Issue 472 Energy Modify Energy Plans structure to allow Time of Use based Controlled Load rates Under consultation Non-Breaking 15 Nov 2022 EnergyPlanControlledLoad
Issue 495 Energy GetAgreedPaymentSchedule API - manualPayment section should have paymentFrequency instead of billFrequency field Under consultation Non-Breaking 15 Nov 2022
Issue 502 Energy Review ENUM values for representation of days in Energy Standards Under consultation Non-Breaking 15 Nov 2022
Issue 515 Energy Clarity around GET Metrics for AER, DELWP and AEMO Under consultation Non-Breaking 15 Nov 2022
Issue 514 Energy Get Usage For ... Shared Responsibility APIs Payload size Under consultation Non-Breaking 15 Nov 2022
Issue 512 Energy Distributor needed for EnergyPlan.geography object Under consultation Non-Breaking 15 Nov 2022
Issue 505 Energy Representation of time within EnergyPlanDetail Schema Under consultation Non-Breaking 15 Nov 2022
Issue 499 Energy Unknown field in Energy Secondary Data Holder OpenAPI spec Documentation fix Non-Breaking 15 Nov 2022
Issue 493 Energy Get Transaction Detail - Client Error documentation Documentation fix Non-Breaking 15 Nov 2022
Issue 461 Energy Documentation Improvement: EnergyPlanContract.variation Documentation fix Non-Breaking 15 Nov 2022

Other CRs for discussion

MI11 Holistic Feedback (Energy specific items)

#511 Iteration 11 Holistic Feedback

  • Update on contributions to date

Any Other Business

Meeting Minutes

Notes

Energy CRs under consultation

  • #472 Modify Energy Plans structure to allow Time of Use based Controlled Load rates

    • Question was asked about making the controlled load structure into an array. It was clarified this was done in response to feedback highlighting scenarios where multiple controlled loads structures can exist for a single plan.
    • AGL noted they would review the proposal and provide any feedback on GitHub if necessary.
    • No other significant issues were raised.

  • #495 GetAgreedPaymentSchedule API - manualPayment section should have paymentFrequency instead of billFrequency field

    • The intent of the API was clarified - "It is not to describe payment plans details, it is to describe how a consumer has elected to pay for a given account or connection points within a given account."
    • Question was raised about the inclusion of servicePointId. The DSB clarified it was included as part of addressing the feedback to cater for scenarios where multiple payment agreements, one per specific service/connection point, within a single account can exist. Feedback is welcome on alternative options of mapping a payment agreement to a connection point.
      • It was noted that the servicepointid should be made optional. The DSB will make this change and update the proposal
    • The proposed digitalWallet structure to cater for pay pal based payments was discussed.
      • It was clarified that paymentMethod and calculationType were kept within the digitalWallter structure as manualPayment does not include them
    • The update to isTokenised description was discussed. The DSB agreed to remove the statement "If true then bsb and accountNumber should not be expected to be included" from the description

  • #502 Review ENUM values for representation of days in Energy Standards

    • It was mentioned that definition of BUSINESS_DAYS within EME includes public holidays. The DSB has taken action to clarify and adjust the proposal based on response.
    • DSB to clarify definition of BUSINESS_DAYS with EME and update proposal based on response

  • #515 Clarity around GET Metrics for AER, DELWP and AEMO

    • It was clarified that this is a rules/regulation driven which the DSB needs to accommodate
    • AEMO noted that they will be producing their own CDR dashboard with metrics information. They are already doing this for a number of other products and will continue to roll this out for CDR.

  • #514 Get Usage For ... Shared Responsibility APIs Payload size

    • Following are the agreed outcomes:
      • Incorporate the two recommendations from Stuart's (Biza) comment listed below:
        1. Optimise intervalReads by making it an array of actual reads. Reads of other quality will be represented separately.
        2. Introduce a query parameter to specifically request raw/full interval reads. By default aggregate reads would be returned
      • Introduce a query parameter to request for interval reads aggregated to 30 minutes as recommended by Opal (AEMO). This and the above query parameter could be defined as an ENUM.
      • The above changes will be incorporated for Nov 15 Energy go-live as AEMO has indicated they can adopt the changes in time.

  • #512 Distributor needed for EnergyPlan.geography object

    • Feedback during the call suggested that whilst including the distributors array would be ok, it should be optional.
    • It was clarified that if a DH holds value for an optional field they are required to provide it as per CDR standards (i.e. they are not optionally implementable by the DH). The DH will have to share the value of distributors if they have it even if it is optional.

  • #505 Representation of time within EnergyPlanDetail Schema

    • The proposed change was agreed by participants.
    • Question was raised about scenarios where timezone is not known and if TimeString type could be updated to cater for unknown timezones. The DSB considered this and has decided not to do it as part of this CR as:
      • Participants on the call indicated there would be no such scenario and time zone would always be known and pricing is not based across multiple states.
      • It can have unintended consequences on existing implementations.

  • #499 Unknown field in Energy Secondary Data Holder OpenAPI spec

    • Not discussed

  • #493 Get Transaction Detail - Client Error documentation

    • Not discussed

  • #461 Documentation Improvement: EnergyPlanContract.variation

    • Not discussed

MI11 Holistic Feedback (Energy specific items)

#511 Iteration 11 Holistic Feedback

  • Not discussed

Any other business

  • N/A

Next Steps

Discuss remaining open CRs where feasible and finalise proposals for presentation on 22 June 2022.