In October, we convened the Perseus Technical Advisory Group, chaired by Icebreaker One.

Date: 15th October 2024 10:00-11:30 BST

Location: online

Chair:

  • Frank Wales, IB1

Secretariat: IB1

Meeting Aims

  1. The endorsement of the Provenance and Exported Energy documents
  2. Provide updates on ongoing work
  3. Outline future work and what to expect for the remainder of the year
  4. A call for interest in the documentation Working Group and a co-chair for 2025

Summary:

  • The directory and registry were presented to members and it was noted that both have been deployed ahead of the pilot
  • An update to the specification for exported energy data was presented to members, with two changes noted:
    • The JSON API standard for error passing has now been implemented as there was not previously a definition for passing errors#
    • An endpoint data source has been added to account for the fact that exported energy requires two meters for import and export 
  • The provenance and assurance principles were proposed to members: 
    • Assurance: is the metadata which enables a member to decide how much trust to place in a dataset with machine-readable assurance signals 
    • Provenance: is a record of where data came from, the members who collected and processed it, and what processing was performed
  • It was noted that the provenance record is a container for the assurance signals, it is the use cases which define the assurance metadata with a view to building and adopting standards within the Trust Framework 
  • The provenance record is designed to be extensible and it was discussed that a scheme may want to add further checks: 
    • Additional traceability
    • Stronger technical safeguards 
    • Proof of processing
  • It was noted that, for the assurance signals, there is the need for a mechanism to flag when some data is missing
  • It was noted that there will be one master permission flow to cover an SME through their whole journey
  • It was noted that elements of the pilot are real financial products, which can themselves be prototypes or pilots; the banks will be using assurable emissions reports to inform lending decisions, and all participants will be maintaining logs and audit trail information as required by the Perseus Scheme 
  • To ensure that the Trust Framework is capturing all of the data during the pilot phase, it was discussed that there should be different scopes for logging, with five scopes proposed to members for feedback:
    • Audit logs
    • Operational logs
    • User activity logs 
    • Account logs
    • Permissions logs

Voting outcomes will be updated shortly.

Next meeting: 2025 date TBC

Formal records are maintained by the secretariat. These are confidential to the Advisory Group Members.