DSB Maintenance Iteration 18: Minutes (7 February 2024)

Meeting Minutes

Release Plan

• v1.29.0 was published on 21 December which incorporated the outcome MI17, see Change Log for full details.
• There is a known issue with v1.29.0 where the incorrect version for Energy Billing APIs was published. This will be resolved at the earliest convenience.
• The outcome of MI18 will likely be published in v1.30.0

Maintenance Iteration Review

• Attendees were invited to participate in a process improvement review for Maintenance Iterations.
• The raw input and synthesised feedback is available here: https://miro.com/app/board/uXjVNzxv1Pk=/
• Feedback was synthesised identifying several themes:
  • Consider improvements the communication of changes adopted for Maintenance Iterations
  • Consider improvements to the process by which changes become binding obligations
    • Avoid obligations for changes that coincide with any major go-live dates for industry
    • Consider grace periods and drafts of standards that aren't immediately enforceable
    • Consider having a minimum lead time for changes to come into effect even if they are non-breaking changes
  • Consider establishing separate domain-aligned maintenance iterations (feedback indicated a lack of banking changes and lots of energy changes in 2023 led to lack of engagement from the banking sector)

Requirements Analysis

CX

• #616 Consumer's Data Holder(s) not available in ADR consent flow (potentially list not up-to-date)
  • DSB consulting with stakeholders, propose moving it to the backlog.
• #563 Recognition of corrected data in DH Dashboard
  • DSB consulting with stakeholders.

Common

• #610 Addition of an (18 or over) Age Verification Flag
  • Hoping to publish position in near future.

Errors

• #412 Proposal to change specific error codes from MUSTs to SHOULDs
  • May be withdrawn, ANZ to advise.

NFR

• #604 Arrangements with large numbers (500+) of accounts
  • Will be covered off in NFR Working Group
• #618 Modification Request for Stages of Get Metrics v5 "abandonmentsByStage" Object
  • Guidance progressing.

Documentation

• #473 Add RFC8174 to list of normative references and update the use of Requirements Levels
  • Moved to backlog, requires substantial amount of work to realign terminology in the standards.

Backlog Grooming Maintenance Iteration 18 Candidates

The DSB started with a list of iterations candidates carried over from MI 17 as well as initial candidates considered a priority. These issues were discussed. The outcome was that several issues were removed from the candidates list for this iteration. Participants also raised additional candidates that were discussed and they have been included for consideration as candidates for this MI.

MI 18

• #629 Maintenance Iteration 18 Holistic Feedback
  • Candidate

CX

• #468 Secondary user approvals withdrawal standards
  • Agreed to include as an MI candidate
• #577 Withdrawal of a SUI by an Account Holder leaving an "Empty" Authorisation
  • Agreed to include as an MI candidate

Security

• #628 Addition of a DH-side endpoint for querying the status of a consent establishment flow
  • Agreed to include in the MI candidates.
  • Important that abandonment lifecycle aligns to NFR metrics changes.

Banking

• #630 Commercial Credit Card Structure under Get Account Details call
  • Given outstanding DP306 and DP338 along with NBL changes it was considered that this candidate will not be consulted on in this maintenance iteration.

Energy

• #624 Improved structure for Solar Time Varying Tariffs
  • Agreed to include as an MI candidate
• #625 Additional field to support Step Tariff calculations
  • Agreed to include as an MI candidate
• #623 Add new pricing models to EnergyPlanContractV2
  • Agreed to include as an MI candidate
• #627 EnergyPlanTariffPeriod - Change to daily supply charge
  • Agreed to include as an MI candidate

Admin

• #626 AuthorisationMetricsV2 abandonmentsByStage property descriptions and CDS Guide
  • Agreed to include as an MI candidate

NFR

• #602 NFR: Secondary Data Holder unable to determine Customer Present
  • Agreed to include as an MI candidate
• #603 NFR: Policing of Data Recipient Low Velocity Data Sets Thresholds
  • Agreed to include as an MI candidate

Documentation

• #615 Plan Obligation Milestones for 2025
  • Given the lack of clarity of industry go-live dates for NBL, it was decided that obligation windows that avoid clashing with significant go-live dates could not be consulted on effectively. As a result, it was agreed that this candidate would be put into the backlog until such time that NBL dates are known.

Other business

None

Next Steps

Call out to the community to comment on #DP340 to suggest iteration candidates over the next two weeks.