<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Icebreaker One</title>
	<atom:link href="https://ib1.org/feed/" rel="self" type="application/rss+xml" />
	<link>https://ib1.org</link>
	<description>Making data work harder to deliver net-zero</description>
	<lastBuildDate>Thu, 14 May 2026 13:41:27 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.1.10</generator>

<image>
	<url>https://ib1.org/wp-content/uploads/2020/11/cropped-00-IB1-Roundel-Yellow-X-Small-128px-rgb-32x32.png</url>
	<title>Icebreaker One</title>
	<link>https://ib1.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Open Energy Webinar: Defining the data infrastructure for I&#038;C flexibility</title>
		<link>https://ib1.org/2026/05/12/open-energy-webinar-defining-the-data-infrastructure-for-ic-flexibility/</link>
		
		<dc:creator><![CDATA[Ross Crear]]></dc:creator>
		<pubDate>Tue, 12 May 2026 09:03:44 +0000</pubDate>
				<category><![CDATA[Energy]]></category>
		<category><![CDATA[Open Energy]]></category>
		<category><![CDATA[Webinars]]></category>
		<category><![CDATA[energydata]]></category>
		<category><![CDATA[energysector]]></category>
		<category><![CDATA[open energy]]></category>
		<category><![CDATA[opendata]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19998</guid>

					<description><![CDATA[Join Open Energy today “There are 300,000 assets on the platform, but only 300 are I&#38;C (Industrial &#38; Commercial)… that’s [&#8230;]]]></description>
										<content:encoded><![CDATA[
<h2 class="has-text-align-center has-ib-1-grey-4-background-color has-background"><a href="https://ib1.org/join/">Join Open Energy today</a></h2>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="Open Energy webinar: Defining the data infrastructure for I&amp;C flexibility" width="1170" height="658" src="https://www.youtube.com/embed/E-GAei-ajx8?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<div class="wp-block-media-text alignwide is-stacked-on-mobile has-ib-1-grey-2-background-color has-background" style="grid-template-columns:24% auto"><figure class="wp-block-media-text__media"><img decoding="async" loading="lazy" width="400" height="400" src="https://ib1.org/wp-content/uploads/2026/05/1528547961418.jpeg" alt="" class="wp-image-20009 size-full" srcset="https://ib1.org/wp-content/uploads/2026/05/1528547961418.jpeg 400w, https://ib1.org/wp-content/uploads/2026/05/1528547961418-150x150.jpeg 150w, https://ib1.org/wp-content/uploads/2026/05/1528547961418-230x230.jpeg 230w, https://ib1.org/wp-content/uploads/2026/05/1528547961418-350x350.jpeg 350w, https://ib1.org/wp-content/uploads/2026/05/1528547961418-45x45.jpeg 45w" sizes="(max-width: 400px) 100vw, 400px" /></figure><div class="wp-block-media-text__content">
<h3>“There are 300,000 assets on the platform, but only 300 are I&amp;C (Industrial &amp; Commercial)… that’s 0.1% of assets delivering around 60% of capacity.” <strong><em>Yingyi Wang, Flexibility Commercial Manager at National Grid Electricity Distribution</em></strong></h3>
</div></div>



<p></p>



<p>Early on in our Open Energy webinar, panelist Yinghi Wang highlighted the outsized role I&amp;C flexibility is already playing in the energy system. Despite representing a tiny fraction of total assets, I&amp;C providers are delivering a significant share of flexibility capacity. Yet participation remains surprisingly low.</p>



<p>In fact, I&amp;C flexibility fell from around 1.7GW in 2021 to just 0.8GW in 2023. At a time when the energy system needs greater flexibility to support electrification and renewable generation, participation appears to be moving in the wrong direction.</p>



<p>Part of the challenge lies in how businesses capture value from flexibility. In the move towards maximising implicit flexibility(where organisations adjust energy use in response to price signals) participation can be complex, requiring upfront investment in control systems and automation, internal resources, and operational change. For many organisations, uncertainty around long-term returns only adds to the perceived risk of participation.</p>



<h2>Not one-size-fits-all</h2>



<p>Another reason participation remains low is that flexibility cannot be approached in the same way across every organisation. When it comes to energy use, every organisation has a flexibility profile that’s shaped by its operations. A manufacturing site, a commercial building, and a data centre each have very different capabilities and constraints.</p>



<p>For industrial processes in particular, flexibility is not simply a matter of switching off or shifting demand. Doing so can have significant operational and commercial impacts. Add in changes to decarbonise a business &#8211; such as process electrification or installation of low carbon technologies &#8211; and the picture can become even more complex.</p>



<h2>Data, the great enabler</h2>



<p>Across the regulators, networks, suppliers, and trade bodies that joined our OE webinar, one view shared throughout was that data is the critical enabler of flexibility.</p>



<p>The energy sector is operating in an environment with limited visibility of available assets, inconsistent standards for data sharing and fragmented systems that do not easily interoperate. As a result, even where flexibility exists, it is difficult to identify, access, and integrate into markets. </p>



<p>This lack of visibility also impacts network planning, as discussed by Open Energy Co-chair, Sara Vaughan: “<strong>It is vitally important to have visibility of what assets are out there to support network planning. In order to achieve this, we need trusted data sharing.”</strong></p>



<p>Without trusted and interoperable data sharing, scaling I&amp;C flexibility will remain a challenge and Clean Power targets will suffer as a result.</p>



<h2>Join Open energy</h2>



<p>Open Energy plays a critical role in addressing these barriers by tackling one of the root causes behind slow flexibility adoption: fragmented and inconsistent data sharing. It also tackles the participation challenge by bringing together industry, networks, and market participants to co-design the rules and harmonise the standards needed to unlock I&amp;C flexibility at scale.</p>



<div class="wp-block-media-text alignwide is-stacked-on-mobile has-ib-1-grey-2-background-color has-background" style="grid-template-columns:30% auto"><figure class="wp-block-media-text__media"><img decoding="async" loading="lazy" width="400" height="400" src="https://ib1.org/wp-content/uploads/2026/05/1620152775524-1.jpeg" alt="" class="wp-image-20003 size-full" srcset="https://ib1.org/wp-content/uploads/2026/05/1620152775524-1.jpeg 400w, https://ib1.org/wp-content/uploads/2026/05/1620152775524-1-150x150.jpeg 150w, https://ib1.org/wp-content/uploads/2026/05/1620152775524-1-230x230.jpeg 230w, https://ib1.org/wp-content/uploads/2026/05/1620152775524-1-350x350.jpeg 350w, https://ib1.org/wp-content/uploads/2026/05/1620152775524-1-45x45.jpeg 45w" sizes="(max-width: 400px) 100vw, 400px" /></figure><div class="wp-block-media-text__content">
<h3 id="block-d2837090-235f-4138-a14b-84590170e38e">&#8216;What is absolutely key to enabling more I&amp;C participation in flexibility markets is data. We need to ensure trusted data sharing that benefits the energy system and the customers who are participating… Open Energy has been working in this area for a number of years and, through the Perseus Scheme, Icebreaker One has already demonstrated proof of concept.&#8217; Sara Vaughan, Co-chair of Open Energy</h3>
</div></div>



<h3>To find out more about the Industrial &amp; Commercial Flexibility use case, or to join Open Energy, please get in touch with us at openenergy@ib1.org</h3>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Perseus Advisory Group 2 (Technical Infrastructure) Summary Minutes April 2026</title>
		<link>https://ib1.org/2026/04/30/perseus-advisory-group-2-technical-infrastructure-summary-minutes-april-2026/</link>
		
		<dc:creator><![CDATA[Janice Holloway]]></dc:creator>
		<pubDate>Thu, 30 Apr 2026 10:56:35 +0000</pubDate>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[Minutes]]></category>
		<category><![CDATA[Perseus]]></category>
		<category><![CDATA[Programmes]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19988</guid>

					<description><![CDATA[We reconvened the Perseus Technical Infrastructure Advisory Group, chaired by Icebreaker One. Date: 28 April 2026 10:00-10:45 BST Location: online [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>We reconvened the Perseus Technical Infrastructure Advisory Group, chaired by <a href="https://icebreakerone.org/">Icebreaker One</a>.</p>



<p>Date: 28 April 2026 10:00-10:45 BST</p>



<p>Location: online</p>



<p>Chair: Frank Wales</p>



<p>Secretariat: IB1</p>



<p><strong>Meeting Aims</strong>:</p>



<ol>
<li>Update on onboarding flows</li>



<li>Discuss coding agents in relation to onboarding</li>



<li>Discuss automated compliance monitoring</li>
</ol>



<p><strong>Summary</strong>:</p>



<p>It was <strong>agreed</strong> that:</p>



<ul>
<li>Participants to send example queries and desired time ranges so the sandbox can be configured to return realistic test data.</li>



<li>IB1 technical team to investigate synthetic data resembling real consumption patterns, alongside a deterministic dataset for automated emissions testing.</li>



<li>Coding agent practitioners within participant organisations to be identified for further input on tooling and workflow.</li>
</ul>



<p>It was <strong>noted</strong> that:</p>



<ul>
<li>Complete demo CAP flow is now available in the example app, with step-by-step guides for both CAP and EDP implementations.</li>



<li>Single-step directory enrollment in progress; full API access to the directory planned.</li>



<li>The sandbox EDP currently returns only ~3 days of February data, insufficient for monthly, quarterly, and annual reporting cycles and pure random synthetic data triggers anomaly detection and is not viable for testing.</li>



<li>A heartbeat service is already included in the Perseus spec to check endpoint liveness and certificate validity.</li>



<li>No SLA is currently in place for the sandbox; this is expected to change in production.</li>
</ul>



<p>It was <strong>discussed</strong> that:</p>



<ul>
<li>Publishing skills alongside Perseus APIs is likely to significantly lower the barrier to integration when using AI coding tools.</li>



<li>Agent authentication is an open design question; current thinking favours re-authenticating agents at each workflow stage rather than carrying a persistent token.</li>



<li>Machine-parseable error messages and a separate agent sandbox were identified as priorities for AI-assisted integration.</li>



<li>Compliance monitoring and operational/performance monitoring should be treated as distinct activities.</li>



<li>In a federated peer-to-peer architecture, misbehaviour may only be apparent at points of interaction between peers; consideration needed on whether clients should be able to flag anomalies centrally.</li>



<li>SMEs are out of scope for the Consumer Consent Solution at launch but expected to be included shortly after; no significant technical blockers identified.</li>
</ul>



<p><strong>Next meeting:</strong> Tuesday 30 June 2026 10:00-11:00 BST</p>



<p>Formal records, including attendees, are maintained by the secretariat. </p>



<p>These are confidential to the Advisory Group Members.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Stream Steering Group April Meeting Summary</title>
		<link>https://ib1.org/2026/04/29/stream-steering-group-april-meeting-summary/</link>
		
		<dc:creator><![CDATA[Janice Holloway]]></dc:creator>
		<pubDate>Wed, 29 Apr 2026 16:00:16 +0000</pubDate>
				<category><![CDATA[Minutes]]></category>
		<category><![CDATA[Programmes]]></category>
		<category><![CDATA[Stream]]></category>
		<category><![CDATA[Water]]></category>
		<category><![CDATA[stream]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19980</guid>

					<description><![CDATA[A Stream Steering Group was convened on 2026-04-21. The Steering Group comprises experts that represent [Stream] water companies, regulators, research, [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>A Stream Steering Group was convened on 2026-04-21.  The Steering Group comprises experts that represent [Stream] water companies, regulators, research, innovation bodies and government. Co-chaired by <a href="https://icebreakerone.org/">Icebreaker One</a> and <a href="https://www.nwl.co.uk/">NWL</a>, the group’s primary function is to help provide leadership and market signalling. </p>



<p>Date: Tuesday 21 April 2026 10:00-12:00 BST</p>



<p>Location: online</p>



<p>Co-Chairs: Melissa Tallack (NWL); Gavin Starks (IB1)</p>



<p>Secretariat: IB1</p>



<p><strong>Meeting Aims</strong> </p>



<ol>
<li>Confirm confidence in the given ecosystem maps and agree priority outreach</li>



<li>Review member feedback on the Data Sharing Working Group documents and discuss next steps</li>



<li>Discuss and endorse collaboration with the energy sector</li>
</ol>



<p><strong>Summary:</strong></p>



<ul>
<li>It was <strong>agreed</strong> that:
<ul>
<li>If members endorse the proposal, Thames Water will formally join Stream as a member, achieving full national coverage across England, Wales and Scotland for the first time, which strengthens its position as it moves towards becoming an independent entity.</li>
</ul>
</li>



<li>It was <strong>noted</strong> that:
<ul>
<li>Six priority stakeholder groups have been identified for focused Q2 engagement, with environmental regulators receiving a clear consensus as the top priority.</li>



<li>An ecosystem stakeholder map has been developed to direct outreach activity, with a review cadence of at least every six months.</li>



<li>Success will be measured through a mix of quantitative metrics (newsletter sign-ups, LinkedIn followers, event attendance) and qualitative outcome indicators (advocacy behaviours, funding facilitation, adoption of Stream as the defacto data infrastructure).</li>



<li>Stream is looking to engage with the energy sector on data sharing interoperability, as part of existing cross-sector commitments within the current funding period.</li>
</ul>
</li>



<li>It was <strong>discussed </strong>that:
<ul>
<li>The qualitative success metrics for ecosystem engagement, while directionally correct, require further detail at the individual stakeholder level to avoid setting targets for their own sake or driving unintended behaviours.</li>



<li>Outreach responsibilities need to be distributed across the Stream membership rather than relying on a single voice.</li>



<li>The regulatory reform landscape presents a timely opportunity to establish Stream as the defacto data sharing infrastructure for the water sector.</li>



<li>Cross-sector interoperability with energy requires careful management to avoid constraining Stream&#8217;s pace of progress, with transparency and communication being key to maintaining alignment without creating dependencies.</li>
</ul>
</li>
</ul>



<p><strong>Next meeting:</strong> Tuesday 2 June 2026 10:00-12:00 BST</p>



<p>Formal records, including attendees, are maintained by the secretariat. </p>



<p>These are confidential to the Steering Group Members.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>IB1 response to DESNZ&#8217;s Data for AI in the energy system call for evidence</title>
		<link>https://ib1.org/2026/04/27/ib1-response-to-desnzs-data-for-ai-in-the-energy-system-call-for-evidence/</link>
		
		<dc:creator><![CDATA[Caroline Fraser]]></dc:creator>
		<pubDate>Mon, 27 Apr 2026 15:35:35 +0000</pubDate>
				<category><![CDATA[Consultations]]></category>
		<category><![CDATA[Energy]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19904</guid>

					<description><![CDATA[This is Icebreaker One’s response to the Department for Energy Security and Net Zero&#8217;s Data for AI in the energy [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>This is Icebreaker One’s response to <a href="https://www.gov.uk/government/calls-for-evidence/energy-datasets-for-artificial-intelligence-applications/data-for-ai-in-the-energy-system-call-for-evidence-accessible-webpage" data-type="URL" data-id="https://www.gov.uk/government/calls-for-evidence/energy-datasets-for-artificial-intelligence-applications/data-for-ai-in-the-energy-system-call-for-evidence-accessible-webpage">the Department for Energy Security and Net Zero&#8217;s Data for AI in the energy system: call for evidence</a>.</p>



<p>Please note that throughout this response, Icebreaker One uses the terms Open, Shared and Closed data as defined <a href="https://icebreakerone.org/open-shared-closed/">here</a>.</p>



<p>If you have any questions about our submission or require clarifications please do not hesitate to contact us via <a href="mailto:policy@ib1.org">policy@ib1.org</a>. We have omitted questions which we did not answer. </p>



<h4><strong>Call for evidence response:</strong></h4>



<h5>1. What energy problem do you want to solve?&nbsp;</h5>



<p><strong>There is a wide range of energy use cases identified and highlighted in </strong><a href="https://ib1.org/2025/03/26/ib1s-response-to-desnzs-developing-an-energy-smart-data-scheme-call-for-evidence/"><strong>IB1’s response to DESNZ’s Developing an energy smart data scheme: call for evidence</strong></a><strong> (question 14). </strong>There are core principles IB1 recommends embedding.&nbsp;</p>



<p><strong>Smart Data becomes effective for use in AI and in decision making when it is connected</strong></p>



<p>In terms of prioritisation of sector, use cases requiring cross-sector interoperability and cohesion offer the greatest immediate ability to create impact, with a manageable degree of complexity involved in rollout.&nbsp;</p>



<p><strong>Regardless of use case, codify a requirement to contribute to net zero</strong></p>



<p>As mentioned in IB1 response to <a href="https://ib1.org/2025/02/20/ib1s-response-to-ofgems-ai-in-the-energy-sector-guidance-consultation/">Ofgem’s AI in the energy sector guidance consultation</a>, we acknowledge and appreciate Ofgem’s commitment to encouraging innovation while helping the UK to meet its net zero target and other associated targets.&nbsp;As mentioned in the <a href="https://ib1.org/2024/05/20/ib1-response-to-ofgems-call-for-input-on-the-use-of-ai-in-the-energy-sector/">IB1’s May 2024 AI consultation response</a>, IB1 recommends that the developing AI governance landscape <strong>codifies a requirement</strong> for AI use in the energy sector to demonstrably contribute to the UK’s net zero targets and for this requirement to be open to monitoring and audit. Without codification of this principle there is a risk that AI systems are established to optimise non-environmental goals, while creating negative environmental impacts.&nbsp;</p>



<p>IB1 acknowledges the risk of AI systems generating increases in energy and water demand. Both the impacts and the demand profile of AI use should be subject to scrutiny and <strong>appropriately governed</strong> to ensure they contribute meaningfully to the UK’s net zero targets.</p>



<h5>2. What kind of data is needed?&nbsp;</h5>



<p>All identified IB1 use cases, detailing the value, kind, potential users, and scale of the required data, are outlined here: <a href="https://ib1.org/energy/reports/">https://ib1.org/energy/reports/</a>&nbsp;</p>



<h5>3. What work is needed to create or enable a useable dataset, including making sure it can be easily combined with other datasets?&nbsp;</h5>



<p>IB1 observes that this list concentrates on technical barriers to data use, but fails to highlight legal, licensing and commercial considerations. It is very possible that cost, usage and IP conditions will hamper otherwise technically possible uses of the data. We recommend early surfacing of this information to mitigate five risks:&nbsp;</p>



<ol>
<li><strong>Regulatory and compliance complexity:</strong> Data licensing must align with compliance rules around grid data, market data, and critical infrastructure. It is important to ensure data inputs to AI systems, and the outputs of the AI, remain compliant.</li>



<li><strong>Third-party data dependencies</strong> AI models in energy often rely on weather feeds, satellite imagery, market pricing, and sensor data from multiple vendors. Each source carries its own licensing terms around permitted use, commercial exploitation, and AI training rights. Identifying these dependencies early prevents data supply chain disruptions during development, or worse, after deployment.</li>



<li><strong>Intellectual property and model ownership:</strong> Who owns the AI model trained on licensed data? Many data providers now include clauses that restrict or claim rights over derivative works, including trained models.</li>



<li><strong>Onward data publishing and monetisation: </strong>Energy sector companies typically want to share or sell AI-derived insights. Licensing terms set upstream can block valuable downstream opportunities. </li>



<li><strong>Long-term data access and continuity risk:</strong> Many foreseeable AI systems in the energy sector (e.g. predictive maintenance, load forecasting) need consistent, long-term data access. Identifying long-term data rights is critical to operational resilience.</li>
</ol>



<p><strong>Governance to enable usable datasets which can be combined with other datasets&nbsp;</strong></p>



<p>As mentioned in <a href="https://ib1.org/2025/02/20/ib1s-response-to-ofgems-ai-in-the-energy-sector-guidance-consultation/">IB1 response to Ofgem’s AI in the energy sector guidance consultation </a>IB1 encourages cross-sector collaboration and learning wherever possible. We recommend engaging with cross sector (i.e. water, transportation, local authorities, etc) and working with citizen advocacy groups to learn from best practices, ensure guidance is consistent for cross sector use cases (hydrogen, electric vehicles, electrifying public transport, etc), and understands the impact of AI guidance on different socio-economic stakeholder groups.</p>



<p>As described in <a href="https://ib1.org/2025/02/05/our-positioning-on-artificial-intelligence-ai/">IB1’s AI positioning statement</a>, IB1 supports a <strong>hybrid governance model</strong>, combining robust oversight with decentralised data sharing, including smart contracts and digital identity solutions</p>



<p>AI must be designed to mitigate bias and discrimination, ensuring fair access to economic opportunities, financial services, and public resources. We support governance which is co-designed through processes which are adequately representative of different stakeholders or stakeholder groups, ensuring that the approach is collective rather than ‘done to’ from the top down.</p>



<p>To mitigate risks and enable data sharing at scale for AI use, the industry must consider more than just the dataset. For an identified use case, it needs to collectively determine:</p>



<ul>
<li><strong>User needs &amp; impact:</strong> commercial priorities, business cases, and prospective new products and services to be unlocked.</li>



<li><strong>Technical infrastructure:</strong> shared ontologies, APIs, schemas and standards to support data exchange.&nbsp;</li>



<li><strong>Licensing &amp; legal:</strong> data sharing agreements, modes of redress and liability frameworks.</li>



<li><strong>Engagement &amp; communications:</strong> common language, stakeholder engagement and recruitment.</li>



<li><strong>Policy</strong>: alignment with corporate policy and industry regulations.</li>
</ul>



<p>At IB1 we do this through a <a href="https://ib1.org/sops/governance-schemes/">robust governance process</a> and <a href="https://ib1.org/icebreaking/">Icebreaking</a> to drive groups of organisations to make the critical decisions required to exchange data with one another.</p>



<h5>4. Who would the users of the dataset be?&nbsp;</h5>



<p>All identified IB1 use cases, detailing the value, kind, potential users, and scale of the required data, are outlined here: <a href="https://ib1.org/energy/reports/">https://ib1.org/energy/reports/</a>&nbsp;</p>



<h5>5. What scale does the dataset need to be?&nbsp;</h5>



<p>All identified IB1 use cases, detailing the value, kind, potential users, and scale of the required data, are outlined here: <a href="https://ib1.org/energy/reports/">https://ib1.org/energy/reports/</a>&nbsp;</p>



<h5>6. What would enabling AI use of this dataset unlock?&nbsp;</h5>



<p>All identified IB1 use cases, detailing the value, kind, potential users, and scale of the required data, are outlined here: <a href="https://ib1.org/energy/reports/">https://ib1.org/energy/reports/</a>&nbsp;</p>



<h5>7. What would be the arrangements for ongoing maintenance, governance and curation of the dataset?&nbsp;</h5>



<p>As noted in <a href="https://ib1.org/2025/02/20/ib1s-response-to-ofgems-ai-in-the-energy-sector-guidance-consultation/">IB1’s response to Ofgem’s AI in the energy sector guidance consultation</a>:&nbsp;</p>



<p>IB1 encourages cross-sector collaboration and learning wherever possible. IB1 recommends engaging with cross sector (i.e. water, transportation, local authorities, etc) and working with citizen advocacy groups to learn from best practices, ensure guidance is consistent for cross sector use cases (hydrogen, electric vehicles, electrifying public transport, etc), and understands the impact of AI guidance on different socio-economic stakeholder groups.</p>



<p>AI must be designed to mitigate bias and discrimination, ensuring fair access to economic opportunities, financial services, and public resources. IB1 advocates strongly for AI governance to <strong>integrate with developments in data governance</strong>, both within the energy sector and in the cross-economic space (e.g. Smart Data Roadmap, approaches to consent or permission).&nbsp;</p>



<p>IB1 believes it is important for data governance to establish principles, structures, roles and responsibilities, agreed upon by market participants, that enable auditable, accurate and timely data sharing at a market-wide scale. As mentioned in the <a href="https://ib1.org/2024/05/20/ib1-response-to-ofgems-call-for-input-on-the-use-of-ai-in-the-energy-sector/">IB1’s May 2024 AI consultation response</a>, IB1 recommends that the data ecosystem, and integration with the data governance landscape be acknowledged.</p>



<p>IB1 notes that in training a model it is highly likely that training datasets will contain sensitive data (it is also possible to use only anonymised data within a training dataset to retain privacy in the model itself), but it is possible to implement techniques where sensitive data is significantly better protected in the training of the model such as aggregation, pseudo-anonymising personal data. A good example of this that has been accepted by Ofgem as appropriate for maintaining privacy is the creation of datasets in energy that aggregate data down to a few households based on which properties are on different Low Voltage Feeders. If there are clear controls on the training data which datasets can and cannot be used to train AI models, then we can expect the produced AI model to be privacy preserving. If you implement data protections after an AI model has already been trained, it is harder to control. If a model has used training datasets with potentially identifiable data within them, the model may provide outputs using this data and can end up linking datasets together to make it personally identifiable</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>IB1 response to Ofgem&#8217;s Connections end-to-end review consultation</title>
		<link>https://ib1.org/2026/04/27/ib1-response-to-ofgems-connections-end-to-end-review-consultation/</link>
		
		<dc:creator><![CDATA[Caroline Fraser]]></dc:creator>
		<pubDate>Mon, 27 Apr 2026 15:28:16 +0000</pubDate>
				<category><![CDATA[Consultations]]></category>
		<category><![CDATA[Energy]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19901</guid>

					<description><![CDATA[This is Icebreaker One’s response to Ofgem’s Connections End-to-end Review consultation. Please note that throughout this consultation, Icebreaker One uses [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>This is Icebreaker One’s response to <a href="https://www.ofgem.gov.uk/consultation/connections-end-end-review-updated-proposals-and-next-steps" data-type="URL" data-id="https://www.ofgem.gov.uk/consultation/connections-end-end-review-updated-proposals-and-next-steps">Ofgem’s Connections End-to-end Review consultation</a>. </p>



<p>Please note that throughout this consultation, Icebreaker One uses the terms Open, Shared and Closed data as defined <a href="https://icebreakerone.org/open-shared-closed/">here</a>.</p>



<p>If you have any questions about our submission or require clarifications please do not hesitate to contact us via <a href="mailto:policy@ib1.org">policy@ib1.org</a>. We have omitted questions which we did not answer. </p>



<h4><strong>Overall Position</strong></h4>



<p>We support the introduction of a new licence condition requiring improvement to connections data. However, the proposal would benefit from clearer definitions of sensitive data and a broader scope that includes both <a href="https://ib1.org/navigating-data-sharing/">open data and shared (sensitive) data</a>. It is important to note that capacity data is relational not static &#8211; interoperability between different data providers and datasets is essential.</p>



<p>A transparent user needs-led approach to data assurance would encourage data sharing, support higher data user confidence, and provide more flexibility than fixed requirements on accuracy, completeness and timeliness, for example regarding update schedules and interoperability. Data user needs must be explored and permitted to share improvement incentives to ensure design and use are aligned. It is important that shared data improvement is incentivised before the timeline for full DSI integration as there is demand for this data immediately.&nbsp;</p>



<h4><strong>Consultation question responses:</strong></h4>



<p><strong>Theme 1 &#8211; Improving visibility and accuracy of connections data&nbsp;</strong></p>



<h5>Q1.1. Do you agree with Proposal 1.1. to introduce a new licence condition for accurate, complete and timely data?&nbsp;</h5>



<p>Yes, we agree with Proposal 1.1 to introduce a new licence condition, however, it should not be limited to open data publication (see question 1.2 below for sensitive data response). All data sharing would benefit from a clear assurance framework, which may draw from established assurance approaches such as <a href="https://specification.trust.ib1.org/generic-dataset-assurance-levels/1.0/" data-type="URL" data-id="https://specification.trust.ib1.org/generic-dataset-assurance-levels/1.0/">Icebreaker One’s generic dataset assurance levels</a>. Data that is not 100% accurate, complete or timely can still be valuable as long as the limitations are made clear. Assurance encourages publication rather than waiting for “perfect” data, which can mean that key datasets are not published due to data quality concerns. Assurance can include accuracy, completeness and timeliness but it enables more nuanced or context-specific signals about data quality, for example interoperability or provenance.</p>



<p>We encourage licensees to engage widely with stakeholders, particularly those outside the energy sector, to develop data assurance signals that meet specific user needs. <a href="https://ib1.org/energy/uk" data-type="URL" data-id="https://ib1.org/energy/uk">Open Energy</a> can facilitate this through a structured approach to design, implementation and governance of such standards within the <a href="https://ib1.org/tf/estf" data-type="URL" data-id="https://ib1.org/tf/estf">Energy Sector Trust Framework</a>.  </p>



<p>We support the requirement for data to be as close to real time as feasible, subject to security considerations (e.g. more granular data may be subject to additional access controls). Monthly updates should be considered a minimum baseline, not an indicator of best practice. More frequent (e.g. daily) data updates would be helpful to accelerate policy ambitions to speed up the connection queue. In all cases, update schedules should be published transparently as part of the assurance process.</p>



<p>It is vital that this condition has a consistent&nbsp; approach across distribution and transmission networks to ensure data is as interoperable as possible. Increasing demand from new industrial plants and digital infrastructure reinforces the need for high-quality, frequently updated, relational connections data. Connections data requirements should apply consistently to both:</p>



<ul>
<li>Generation connections</li>



<li>Demand connections (including large industrial loads and data centres)</li>
</ul>



<h5>Q1.2. Do you agree with Proposal 1.2. to split data into open and sensitive categories, and to use the Data Sharing Infrastructure to share sensitive data?&nbsp;</h5>



<p>No. Sensitive data is not a monolithic category, there are existing approaches (e.g. <a href="https://ib1.org/data-sensitivity-classes/" data-type="URL" data-id="https://ib1.org/data-sensitivity-classes/">IB1 Data Sensitivity Classes</a>) to sub-categorise which should be used in order to assess data sensitivities and place appropriate access controls/licensing. This will provide DNOs greater guidance from regulators on what should be considered sensitive data. </p>



<p>DSI data sharing may not be (immediately) suitable for all use cases, it is currently unclear when and how non-regulated actors will be able to access data via the DSI and these actors constitute major customers for connections data (e.g. heavy industry, retail etc). While sensitive data may be exchanged via the DSI in future, improvements must not be put on hold until the solution is ready. Further, determining whether the DSI is used as the primary mechanism to share sensitive data should depend on the outcome of the MVP.&nbsp;&nbsp;</p>



<h5>Q1.3. Do you have any additional comments in relation to the decisions and proposals outlined in this theme? Do you have any additional comments related to any other aspects of this theme you think we should consider?&nbsp;</h5>



<p>Additional comments:</p>



<ul>
<li>Network headroom is not static at a single supply point (substation / GSP). Capacity availability is relational and influenced by:
<ul>
<li>Nearby supply points and how power is drawn/combined from different points</li>



<li>Connection queues and timelines</li>



<li>Reinforcement plans and timelines</li>



<li>Local and regional constraints (e.g. DNO/TNO or cross-DNO constraint interactions)</li>
</ul>
</li>



<li>The licence condition and associated data standards should better capture and communicate these relational dependencies.</li>



<li>Greater transparency regarding capacity that has been committed but is not yet utilised (and anticipated timescale for use) may support better planning.</li>
</ul>



<p>Lessons from relevant innovation projects (e.g. work examining relational network constraints) should inform the design of data publication and visualisation tools. In particular, lessons from the S<a href="https://ib1.org/energy/react/">trategic Innovation Fund REACT programme</a> which aimed to  address current planning and future planning for generation siting may be valuable. REACT’s Alpha Phase Data accessibility and interoperability report recommendations:</p>



<ul>
<li><strong>Reducing friction: </strong>To improve data assurance, reduce friction across data silos and provide forward compatibility with the Virtual Energy System, the REACT project must embrace a ‘Trust Framework’ methodology throughout its work.</li>



<li><strong>Improving data accessibility: </strong>To improve the discoverability of datasets and encourage process innovation, Transmission Owners should publish internal process diagrams that describe the workings of complicated internal processes &#8211; such as the Network Connection Request process.</li>



<li><strong>Improving prediction</strong>: To improve long-term planning for Transmission Owners and for other stakeholders, a statistical model of projects should be embraced that tracks a project’s estimated probability of success according to the best available data.</li>



<li><strong>Embracing innovation: </strong>To radically embrace innovation around processes, such as the Network Connection Request process, virtual ‘sandbox’ representations of these processes with representative data should be created. This will enable innovators to safely experiment with innovative solutions without affecting Business as Usual.</li>
</ul>



<p>As mentioned in <a href="https://ib1.org/2026/01/27/ib1-response-to-ofgems-modifications-to-the-riio-3-licenses-and-documents-consultation/">IB1’s Response to Ofgem Modifications to RIIO-3 consultation</a>, with the progress of the Data Sharing Infrastructure (DSI) programme, IB1 anticipates ‘<a href="https://ib1.org/open-shared-closed" data-type="URL" data-id="https://ib1.org/open-shared-closed">Shared Data</a>’ sharing will evolve and will inform the evolution of data best practice (DBP) guidance. In particular, as data sharing scales, the need to standardise and harmonise legal and technical approaches will become more pressing in order not to slow innovation and add unnecessary cost. IB1 recommends that DBP should include guidance around Shared Data within the triage processes and licensing decisions, highlighting the role of Shared Data Schemes to provide definitions that aid interoperability and maximise impact.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>IB1 response to Elexon&#8217;s P494 Assessment Procedure consultation</title>
		<link>https://ib1.org/2026/04/27/ib1-response-to-elexons-p494-assessment-procedure-consultation/</link>
		
		<dc:creator><![CDATA[Caroline Fraser]]></dc:creator>
		<pubDate>Mon, 27 Apr 2026 15:19:08 +0000</pubDate>
				<category><![CDATA[Consultations]]></category>
		<category><![CDATA[Energy]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19898</guid>

					<description><![CDATA[This is Icebreaker One’s response to Elexon’s P494 Assessment Procedure Consultation. Please note that throughout this consultation, Icebreaker One uses [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>This is Icebreaker One’s response to <a href="https://www.elexon.co.uk/bsc/consultation/p494-assessment-procedure-consultation-establishing-a-smart-data-repository-sdr/">Elexon’s P494 Assessment Procedure Consultation</a>. </p>



<p>Please note that throughout this consultation, Icebreaker One uses the terms Open, Shared and Closed data as defined <a href="https://icebreakerone.org/open-shared-closed/">here</a>.</p>



<p>If you have any questions about our submission or require clarifications please do not hesitate to contact us via <a href="mailto:policy@ib1.org">policy@ib1.org</a>. We have omitted questions which we did not answer. </p>



<h4><strong>Consultation response:</strong></h4>



<h5>1. Do you agree with the Workgroup’s initial view that P494 does better facilitate the Applicable BSC Objectives than the current baseline?* Please provide your rationale and, if ‘No’, please provide full details of your Alternative Modification(s) and your rationale as to why it / they better facilitate the Applicable BSC Objectives. </h5>



<ul>
<li><strong>Yes</strong></li>



<li>No </li>



<li>Neutral / No Comment </li>



<li>Other </li>
</ul>



<p>Rationale: Elexon is unable to fulfil the potential benefit of making the data available with its current position as Data Processor.</p>



<h5>2. Do you agree with the Workgroup that the draft legal text in Attachment B delivers the intention of P494?</h5>



<ul>
<li>Yes</li>



<li><strong>No</strong> </li>



<li>Neutral / No Comment&nbsp;</li>



<li>Other&nbsp;</li>
</ul>



<p>Rationale:&nbsp;</p>



<ul>
<li>Data Controller is limited to “<a href="https://bscdocs.elexon.co.uk/guidance-notes/data-protection-bsc-controllers-and-bsc-processors">Relevant BSC Personal Data</a>” which only applies to data about natural persons. This will exclude data protections for company data envisaged in the DUAA. It leaves a lot of heavy lifting to the SDR Rules for non-personal but commercially-sensitive company data.</li>



<li>SDR Rules not sufficiently developed at this time to assess whether, in combination with the code change, they are sufficient to ensure adequate data protection under the DUAA:
<ul>
<li>Identifying legitimate agents</li>



<li>Identifying meter owners not covered by CCS</li>



<li>Licensing and access arrangements for commercially-sensitive but non-personal data</li>
</ul>
</li>



<li>The consultation notes that “The means of determining whether a data set is commercially sensitive or personal data are being explored and are outside of P494”. This leaves a lot of work for the SDR Operations Manual to cover. The SDR is described on p27 of the consultation as containing “list of all APIs and reports published as well as technical details for how SDR users can interact with the SDR”. It will need to have much more detailed governance information. There is a risk that these considerations will “fall between the stools” of the BSC modification and the SDR Operations Manual.</li>
</ul>



<h5>3. Do you agree with the Workgroup’s recommended Implementation Date?</h5>



<ul>
<li>Yes</li>



<li>No&nbsp;</li>



<li><strong>Neutral / No</strong> <strong>Comment</strong> </li>



<li>Other </li>
</ul>



<h5>4. Do you agree with the Workgroup that there are no other potential Alternative Modifications within the scope of P494 which would better facilitate the Applicable BSC Objectives?</h5>



<ul>
<li>Yes</li>



<li>No&nbsp;</li>



<li><strong>Neutral / No Comment</strong> </li>



<li>Other&nbsp;</li>
</ul>



<h5>5. Do you agree with the Workgroup’s assessment of the impact on the BSC Settlement Risks?</h5>



<ul>
<li>Yes</li>



<li>No&nbsp;</li>



<li><strong>Neutral / No Comment </strong></li>



<li>Other&nbsp;</li>
</ul>



<h5>6. Will P494 impact your organisation?</h5>



<p>* If it will impact, please provide a description of the impact(s) and any activities which you will need to undertake between approval and implementation (including any necessary changes to your systems, documents and processes) and any on-going operational impacts. Where applicable, please state any difference in impacts between the Workgroup’s proposed solutions.&nbsp;</p>



<ul>
<li>High </li>



<li>Medium </li>



<li><strong>Low</strong></li>



<li>None </li>



<li>Other </li>
</ul>



<p>Rationale: There is potential for P494 to affect the Perseus smart meter scheme positively, opening up a wider array of the kind of meter points used by SMEs. </p>



<h5>7. How much will it cost your organisation to implement P494?</h5>



<p>* If any, please provide details of these costs, how they arise. Please also state whether it makes any difference to these costs whether implemented as part of or outside of a normal BSC Systems Release. Where applicable, please state any difference in costs between the Workgroup’s proposed solutions and if applicable, between the different roles.&nbsp;</p>



<ul>
<li>High </li>



<li>Medium </li>



<li>Low</li>



<li><strong>None</strong> </li>



<li>Other </li>
</ul>



<p>Rationale: P494 does not drive any direct costs</p>



<h5>8. What will the ongoing cost of P494 be to your organisation?</h5>



<p>* If any, please provide details of these costs, how they arise. Please also state whether it makes any difference to these costs whether P494 is implemented as part of or outside of a normal BSC Systems Release. Where applicable, please state any difference in costs between the Workgroup’s proposed solutions and if applicable, between the different roles.&nbsp;</p>



<ul>
<li>High </li>



<li>Medium </li>



<li>Low </li>



<li><strong>None</strong></li>



<li>Other </li>
</ul>



<h5>9. How long (from the point of approval) would you need to implement P494?</h5>



<p>* Please provide an explanation of your required lead time, and which activities are the key drivers behind the timescale. Please also state whether it makes any difference to this lead time whether implemented as part of or outside of a normal BSC Systems Release. Where applicable, please state any difference in lead times between the Workgroup’s proposed solutions.&nbsp;</p>



<ul>
<li>0-6 months </li>



<li>6-12 months </li>



<li>>12 months </li>



<li><strong>Other</strong></li>
</ul>



<p>Rationale: P494 does not require any action from us</p>



<h5>10. Do you agree with the Workgroup’s assessment of the consumer benefits?</h5>



<ul>
<li>Yes </li>



<li>No </li>



<li><strong>Neutral</strong>/<strong>No</strong> <strong>comment</strong></li>



<li>Other</li>
</ul>



<h5>11. Do you agree with the Workgroup’s assessment that P494 does impact the European Electricity Balancing Guideline (EBGL) Article 18 terms and conditions held within the BSC?</h5>



<ul>
<li>Yes&nbsp;</li>



<li>No&nbsp;</li>



<li><strong>Neutral</strong>/<strong>No</strong> <strong>comment</strong></li>



<li>Other</li>
</ul>



<h5>12. Do you have any comments on the impact of P494 on the EBGL objectives?</h5>



<p>No</p>



<h5>13. Which of the following funding options do you prefer for the recovery of SDR costs?</h5>



<ul>
<li>Costs recovered from Suppliers based on the number of MPANs supplied (option one)</li>



<li>Costs recovered from Suppliers based on their share of delivered energy volumes (option two)</li>



<li>Costs recovered from Suppliers using a hybrid approach combining MPAN-based and volume-based charging (option three) </li>



<li>Costs recovered through existing BSC arrangements and borne by all BSC Trading Parties (option four) </li>
</ul>



<p>Rationale: No comment</p>



<h5>14. Do you have any views on when the full review of the cost to SDR Users should occur?</h5>



<ul>
<li>Yes&nbsp;</li>



<li>No&nbsp;</li>



<li><strong>Neutral</strong>/<strong>No</strong> <strong>comment</strong></li>



<li>Other</li>
</ul>



<h5>15. Do you agree with the legal basis to establish and operate the SDR?</h5>



<ul>
<li>Yes </li>



<li>No&nbsp;</li>



<li>Neutral/No comment</li>



<li><strong>Other</strong></li>
</ul>



<p>Rationale: The underlying mechanism of creating the SDR Manager and giving it Processor rights seems sound, but it is lacking detail for non-domestic users as noted in our response to Question 2</p>



<h5>16. Do you have any views on what the de minimis aggregation level should be?</h5>



<ul>
<li><strong>Yes</strong> </li>



<li>No&nbsp;</li>



<li>Neutral/No comment</li>



<li>Other</li>
</ul>



<p>Rationale: The proposed choice of 10 MPANs is not presented with a clear evidence based rationale. If there is a more detailed rationale this should be put forward transparently. There is an opportunity to build a more nuanced context-specific decision on the appropriate level of aggregation based on factors such as geographic dispersal and existence of generation and storage capabilities that may provide a “signature” in the data. Also consider differentiating “highly aggregated” data (say 50+ MPANs) that may be widely licensed, and “minimally aggregated” data (5-10 MPANs) that may have more restrictive access and licensing to prevent abuse.</p>



<h5>17. Do you have any further comments on P494?&nbsp;</h5>



<p>There is a considerable amount of work to be done in the SDR Operations Manual in order to achieve the goals of the SDR Trust Framework. The following are some key elements left to be defined:</p>



<ol>
<li>ID &amp; Verification for non-CCS access is not defined (and even for CCS requires that to have been established). CCS should eventually cover business meters , and hopefully this will extend to smart and AMR meters. But that may not be until 2028. Businesses are key potential beneficiaries of SDR, for both cost reduction and net-zero impact. A number of the expected SDR Users focus on services intended for business. How will SDR support businesses in the interim? How will the SDR Users be verified, their data usage controlled, and how will they provide evidence for meter data access from businesses?</li>



<li>The data sensitivity classes need more definition and clear policies for application</li>



<li>The eligibility requirements and decision-making process for executing an Access Agreement and allowing access must be defined, as well as policies/processes for ensuring SDR Users remain eligible</li>



<li>Data licensing requirements are not mentioned in the consultation. How will purposes be categorised and policed? What is permitted/not permitted for the various levels of non-open data?</li>



<li>Liability and redress are not mentioned in the consultation. What policies and processes will enable data subjects harmed by the SDR to seek redress?</li>
</ol>



<p>Since SCR covers a wider range of legal bases and potential data users than CCS, we recommend early consideration of how governance elements such as those above may be harmonised with other data sharing initiatives. This may be achieved through identifying opportunities for common definitions around ID&amp;V, data sensitivity, purposes (or classes of purpose), and licences. Icebreaker One and Open Energy have research and experience, drawn from wide stakeholder engagement, that can inform this work.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>IB1 response to Ofgem&#8217;s Enhancing asset visibility: DNO options consultation</title>
		<link>https://ib1.org/2026/04/27/ib1-response-to-ofgems-enhancing-asset-visibility-distribution-network-operator-options-consultation/</link>
		
		<dc:creator><![CDATA[Caroline Fraser]]></dc:creator>
		<pubDate>Mon, 27 Apr 2026 14:36:21 +0000</pubDate>
				<category><![CDATA[Consultations]]></category>
		<category><![CDATA[Energy]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19889</guid>

					<description><![CDATA[This is Icebreaker One’s response to Ofgem’s Enhancing asset visibility: Distribution Network Operator options consultation. Please note that throughout this [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>This is Icebreaker One’s response to <a href="https://www.ofgem.gov.uk/consultation/enhancing-asset-visibility-distribution-network-operator-options" data-type="URL" data-id="https://www.ofgem.gov.uk/consultation/enhancing-asset-visibility-distribution-network-operator-options">Ofgem’s Enhancing asset visibility: Distribution Network Operator options consultation</a>. </p>



<p>Please note that throughout this consultation, Icebreaker One uses the terms Open, Shared and Closed data as defined <a href="https://icebreakerone.org/open-shared-closed/">here</a>.</p>



<p>If you have any questions about our submission or require clarifications please do not hesitate to contact us via <a href="mailto:policy@ib1.org">policy@ib1.org</a>. </p>



<h4><strong>Consultation response:</strong></h4>



<h5>Q1. Do you agree with our case for change and that policy intervention is needed for DNO asset registration?&nbsp;</h5>



<p>Icebreaker One (IB1) is a non-profit working on data sharing and sustainability, convening organisations and governments to design market-scale solutions to make data work harder to deliver Net Zero. IB1 creates and runs programmes to reduce barriers and costs to finding, accessing, using, and sharing data, which will ultimately reduce costs for consumers.</p>



<p>IB1 supports better data on assets, and data sharing between DNOs, suppliers, and other organisations who need to understand headroom capacity and demand. We note there is a need to distinguish clearly between asset type(s) and capacity at the initial phase. In future, better data on asset performance and behaviours would be helpful to ensure this initiative can be most useful &#8211; e.g. capacity is not static with flexibility assets in play.</p>



<h5>Q2. Do you agree with our priority use cases, and are there any other use cases we should consider?&nbsp;</h5>



<p>We agree with Ofgem’s identified use cases, however, we note that the data end user within the priority (regulated entities) and further use cases may have very different needs and data sharing instruments available. As mentioned in <a href="https://ib1.org/2026/02/04/ib1-response-to-ofgems-energy-digitalisation-governance-architectural-coordination-letter/">IB1’s response to Ofgem’s Energy digitalisation governance: architectural coordination letter</a>, we propose that an industry-independent coordination body helps coordinate a flexible energy system. Data sharing at scale requires the separation of ‘the data’ from its governance and the technology used to host and transfer it.</p>



<p>We encourage the inclusion of potential ‘further users’ as a part of a governance process from the outset to ensure a solution suits their needs and does not exclude the solution from expanding past the priority use cases. We advocate for starting with a use case with external (non-regulated / less digitally mature) players, then a B2B DNO focussed use case to make subsequent use cases easier and less likely to inadvertently produce blockers. Leaving local authority use cases for “later” risks local planning and investment being disconnected from the physical reality of supply. A key use case to consider is data centre energy demand, which reinforces the need to urgently prioritise local authority use cases.&nbsp;</p>



<p>IB1 has worked on a few other relevant collaborative use cases in this area, including:</p>



<ul>
<li>Getting small scale assets / flex services online (<a href="https://ib1.org/energy/reports/">Open Energy Future of heating &#8211;&nbsp; Residential Property Developer</a> use case).</li>



<li>How data sharing can be used to better understand how to maintain the assets already in place. IB1, SSEN-Transmission, IBM, and Palantir on a Strategic Innovation Fund programme, NIMBUS, which focussed on granular weather data and network innovation to build for sustainability. See the <a href="https://ib1.org/energy/nimbus/">Discovery Phase report</a> and the <a href="https://ib1.org/energy/nimbus/">Alpha Phase report</a>.</li>



<li>IB1 partnered with SSEN-Transmission, Olsights, Mapstand, SGN, and National Grid on a Strategic Innovation Fund programme REACT to address current planning and future planning for generation siting. See the <a href="https://ib1.org/energy/react/">Discovery Phase report</a>, and the <a href="https://ib1.org/energy/react/">Alpha Phase report</a>. This use case reinforces the need to know other assets on grid to aid grid capacity understanding and future planning.</li>
</ul>



<h5>Q3. Are there any other policy or industry initiatives that we should seek to align with?&nbsp;</h5>



<p>IB1 encourages seeking alignment with:</p>



<ul>
<li><a href="https://ib1.org/energy/uk/">Open Energy</a> &#8211; run by IB1, has expertise articulating use cases, and designing and quickly implementing shared data schemes with appropriate governance – includes legal agreements, assurance and technical specifications – in collaboration with stakeholders.</li>



<li><a href="https://www.ofgem.gov.uk/consultation/connections-end-end-review-updated-proposals-and-next-steps">Connections end-to-end review: updated proposals and next steps​ consultation</a>. To what extent are external entities interested in assets as opposed to capabilities?</li>



<li>Consumer Consent Solution, currently being developed, designed and delivered by RECCo Ltd, as small scale asset data is in scope (unless this programme is using another lawful basis for processing, this would need to be articulated clearly).</li>
</ul>



<h5>Q4. Do you agree with the scope proposed for assets, data, entities, and data stages, should anything else be considered?</h5>



<p>As mentioned above, there needs to be a defined governance process for considering and agreeing upon the proposed scope for assets, data, entities, and data stages.&nbsp;</p>



<p>IB1 would highlight there is a need to identify current data uses, and to be flexible enough to incorporate new ones as they emerge, to establish both the scope and the data quality and completeness requirements for asset information. For example, there is likely to be a difference between the DNOs&#8217; data quality requirements at the lowest end of the asset capacity scale and the data quality requirements for users like councils, planners, microgrid/heat network assessors etc. Additionally if this asset data feeds into the flex market, missing or incorrect installations could lead to financial consequences for asset owners.&nbsp;</p>



<p>While not in scope for the initial phase of development, our suggestion for future development would be the ability to transfer data on asset profiles/behaviours. This would be incredibly useful to better understand how flexible assets actually behave and their real-life impact, for example on network capacity.</p>



<h5>Q5. Do you agree with our enablers and dependencies, and are there any others we should consider?&nbsp;</h5>



<p>IB1 would add on the lawful basis for processing &#8211; if not using consent then clarify on what lawful basis the register operates under. It would also help to understand how any data protection risks potentially associated with the register will be managed and governed. It is not currently clear how the lawful basis distinguishes between household and business (including microbusiness/SME) assets. This will interact with the Data (Use and Access) Act for businesses and requires clarification.</p>



<h5>Q6. Do you have any suggestions for collecting legacy data, or for integration of other datasets into DNO registers?&nbsp;</h5>



<p>No comment.&nbsp;</p>



<h5>Q7. Do you agree with the advantages and disadvantages for the proposed options, are there others or any wider aspects we should consider?&nbsp;</h5>



<p>Wider aspects to consider on Option 2:</p>



<ul>
<li>May require upskilling/investment by DNOs, with an opportunity to subcontract if they are lacking skills in-house. This is a low risk if data standards are agreed through a governance process.</li>



<li>As mentioned in Question 2, this initiative must be mindful of restricting use cases to regulated entities first which may make it harder for other users in the future.&nbsp;</li>



<li>As there is demand by non-regulated users for asset data now, there may be a benefit to spinning up a <a href="https://ib1.org/definitions/scheme/">scheme</a> in the short frame which is ready to integrate with DSI but has governance to engage a wider range of end users at the start. </li>



<li>This option has the highest potential to scale as it does not bottleneck in a single database/register, and provide utility for a wide range of use cases.&nbsp;</li>
</ul>



<p>Wider aspects to consider on Option 3:</p>



<ul>
<li>New databases and portals struggle to scale for a wide array of use cases as infrastructure systems are being digitalised in a decentralised and distributed way</li>



<li>This option gives liability to a central entity versus distributed liability to DNOs</li>



<li>May conflict with current DNO autonomy in deciding what data to publish and how to publish it, guided by DBPG. In particular may lead to a lowest-common-denominator approach that disincentivises DNOs from publishing otherwise-useful data that isn’t needed by the central register</li>
</ul>



<p>Wider aspects to consider on Option 4:</p>



<ul>
<li>Operating a flexible market is a significantly different use case from the ones articulated above &#8211; expanding existing initiatives may result in a loss of focus on the original challenge it was solving</li>



<li>Suggest a focus on harmonisation rather than making FMAR even more complex.</li>
</ul>



<h5>Q8. Are there any changes you would make to any of the proposed options to enhance them?&nbsp;</h5>



<p>IB1 would emphasise the need for a determination on what body would govern the standards for Option 2, and how stakeholder engagement beyond the regulated entities will be managed. There is a need to convene stakeholders within and outside the industry to ensure it is fair and accessible as well as implementable by the data holders.&nbsp;</p>



<h5>Q9. Have we missed or discounted any options that you think are suitable? In particular, for option 4 is there a preferable alternative to FMAR for expansion, and why?&nbsp;</h5>



<p>No Comment.&nbsp;</p>



<h5>Q10. Which option is your preferred option, and why?</h5>



<p>IB1 would encourage Option 2, as it is the fastest to market and lowest cost, and can be decoupled from other initiatives, so can run in parallel and at pace. We would suggest this happens through a trial &#8216;scheme&#8217; developed as and will be DSI integration ready for when DSI is ready to support asset data sharing.&nbsp;</p>



<p>This option also has the opportunity to have the simplest governance (only DNO liabilities) &#8211; although this needs defining &#8211; as referenced in Question 8.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Connect Don&#8217;t Collect: The UK Smart Data Strategy &#038; Perseus</title>
		<link>https://ib1.org/2026/04/21/connect-dont-collect-the-uk-smart-data-strategy-perseus/</link>
		
		<dc:creator><![CDATA[Ross Crear]]></dc:creator>
		<pubDate>Tue, 21 Apr 2026 11:01:47 +0000</pubDate>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[Perseus]]></category>
		<category><![CDATA[Podcast]]></category>
		<category><![CDATA[netzero]]></category>
		<category><![CDATA[smartdata]]></category>
		<category><![CDATA[SME]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19812</guid>

					<description><![CDATA[The UK Government’s Smart Data Strategy sets a clear direction for the future of data sharing across the economy. In [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>The UK Government’s Smart Data Strategy sets a clear direction for the future of data sharing across the economy. In this episode, Siobhan Dennehy (Department for Business and Trade) and Gavin Starks unpack what it means in practice, from policy ambition to real-world delivery. They explore how schemes like Perseus are emerging as best practice, and what it takes to move from vision to implementation at scale.</p>



<div style="position:relative;padding-bottom:56.25%;height:0;overflow:hidden;">
  <iframe src="https://www.youtube.com/embed/P7P9zP7F88Q" style="position:absolute;top:0;left:0;width:100%;height:100%;" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="">
  </iframe>
</div>



<p></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Stream Advisory Group 2 April Meeting Summary</title>
		<link>https://ib1.org/2026/04/16/stream-advisory-group-2-april-meeting-summary/</link>
		
		<dc:creator><![CDATA[Janice Holloway]]></dc:creator>
		<pubDate>Thu, 16 Apr 2026 15:03:07 +0000</pubDate>
				<category><![CDATA[Minutes]]></category>
		<category><![CDATA[Programmes]]></category>
		<category><![CDATA[Stream]]></category>
		<category><![CDATA[Water]]></category>
		<category><![CDATA[stream]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19733</guid>

					<description><![CDATA[We reconvened the Stream Technical Advisory Group, Co-chaired by Icebreaker One and Pennon Group. Date: 7 April 2026 10:00-11:30 BST Location: Online Co-Chairs: [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>We reconvened the Stream Technical Advisory Group, Co-chaired by <a href="https://ib1.org/">Icebreaker One</a> and <a href="https://www.pennon-group.co.uk/">Pennon Group.</a></p>



<p>Date<strong>: </strong>7 April 2026 10:00-11:30 BST</p>



<p>Location: Online</p>



<p>Co-Chairs:<strong> </strong>Lucy Chambers (IB1); Dan Slidel (Southern Water)</p>



<p>Secretariat<strong>:</strong> Icebreaker One </p>



<p><strong>Meeting Aims</strong></p>



<ol>
<li>Create clarity on the framework, infrastructure and processes needed for sharing data.</li>



<li>Review use case process and confirm whether there is room for improvement.</li>
</ol>



<p><strong>Summary</strong>:</p>



<ul>
<li>It was <strong>noted</strong> that:
<ul>
<li>NESO is conducting similar work on templated Data Sharing Agreements, for interoperability purposes, Stream should endeavour to collaborate at some point.</li>



<li>The Working Group has developed early outputs to support data sharing, including a decision tree and an initial view of required templates and modules.</li>



<li>The work has been informed by a legal and risk‑based perspective, recognising varying sensitivity and risk across data sharing scenarios.</li>



<li>A revised use case process map was presented, intended to provide clearer expectations, support varied use case entry points, and remain adaptable as understanding matures.</li>
</ul>
</li>



<li>It was <strong>discussed</strong> that:
<ul>
<li>Widening participation in the Data Sharing Working Group is essential to diversify inputs.</li>



<li>A one‑size‑fits-all approach to data sharing agreements is not appropriate, and that a modular, templated approach may better accommodate different use cases.</li>



<li>Decision‑making tools should be usable by non‑legal stakeholders, while enabling appropriate escalation to legal, governance and compliance functions.</li>



<li>Reducing friction in data sharing requires attention beyond legal agreements, including identity management, audit and enforcement, data quality, infrastructure security, and organisational buy‑in.</li>



<li>Data ownership should sit with business leads, supported by legal oversight rather than led by legal teams alone.</li>



<li>There is a need to clarify what should be handled centrally versus individually by member organisations.</li>



<li>There’s a need for clearer decision rights and escalation, more effective prioritisation, and explicit consideration of funding, resourcing and capacity constraints within an agile use case process.</li>



<li>Members need better visibility of the pipeline and roadmap to understand what is coming, what is committed, and when.</li>



<li>The process should include a post‑delivery review to assess whether use cases delivered value and what was learned.</li>
</ul>
</li>
</ul>



<p><strong>Next meeting:</strong> Tuesday 19 May 2026 10:00-11:30 BST</p>



<p>Formal records, including attendees, are maintained by the secretariat. </p>



<p>These are confidential to the Advisory Group Members.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Stream Advisory Group 1 April Meeting Summary</title>
		<link>https://ib1.org/2026/04/15/stream-advisory-group-1-april-meeting-summary/</link>
		
		<dc:creator><![CDATA[Janice Holloway]]></dc:creator>
		<pubDate>Wed, 15 Apr 2026 16:04:15 +0000</pubDate>
				<category><![CDATA[Minutes]]></category>
		<category><![CDATA[Programmes]]></category>
		<category><![CDATA[Stream]]></category>
		<category><![CDATA[Water]]></category>
		<category><![CDATA[stream]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19724</guid>

					<description><![CDATA[We reconvened the Stream Market &#38; User Needs Advisory Group, Co-chaired by Icebreaker One and Northumbrian Water. Date: 2 April 2026 10:00-11:30 BST [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>We reconvened the Stream Market &amp; User Needs Advisory Group, Co-chaired by <a href="https://ib1.org/">Icebreaker One</a> and <a href="https://www.nwl.co.uk/">Northumbrian Water</a>.</p>



<p>Date<strong>: </strong>2 April 2026 10:00-11:30 BST</p>



<p>Location: Online</p>



<p>Co-Chairs:<strong> </strong>Charlotte Hillenbrand (IB1), Katy Woodward (United Utilities) and Josh Evans (Pennon Group) </p>



<p>Secretariat<strong>:</strong> Icebreaker One </p>



<p><strong>Meeting Aims</strong></p>



<ol>
<li>Reviewing the use case template plus endorsement&nbsp;</li>



<li>Review and discuss the ecosystem map&nbsp;</li>



<li>Update members on use case status</li>
</ol>



<p><strong>Summary</strong></p>



<ul>
<li>It was <strong>agreed</strong> that:
<ul>
<li>The WEC use case needed formal approval from members to take to the Steering Group.</li>
</ul>
</li>



<li>It was <strong>noted</strong> that:
<ul>
<li>All outcomes are now published on the Stream website. </li>



<li>The stakeholder map is intended to be a live tool, reviewed and refined over time rather than fixed.&nbsp;</li>



<li>Welsh, Scottish (and potentially Northern Ireland) regulators were identified as missing and should be added to the stakeholder map.&nbsp;</li>



<li>Both Stream team capacity and member capacity were recognised as constraints when sequencing activity (particularly use cases).&nbsp;</li>



<li>It is important that we measure the impact of what we’re doing, looking at outcomes and quantitative targets for the activity level. </li>



<li>Each stakeholder will be assigned to a desired outcome: high levels of advocacy, integration of Stream into their ways of working (such as with DEFRA), facilitate access to sources of funding, and recognise and adopt Stream as the de facto data sharing infrastructure.</li>



<li>Independent innovators should be considered in the wider ecosystem map.</li>
</ul>
</li>



<li>It was <strong>discussed</strong> that:
<ul>
<li>The priorities of the group might be skewed towards the government/regulatory group, rather than the representative of the wider water industry but this may be influenced by the Water Sector reform over the next two years.&nbsp;</li>



<li>Stream could look to the EU for research and data sharing opportunities.</li>



<li>Stream’s role may increasingly be one of coordination, rather than delivery alone.</li>
</ul>
</li>
</ul>



<p><strong>Next meeting:</strong> Thursday 14 May 2026 10:00-11:30 BST</p>



<p>Formal records, including attendees, are maintained by the secretariat. </p>



<p>These are confidential to the Advisory Group Members.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>From volatility to visibility: Perseus gas expansion helps SMEs manage risk</title>
		<link>https://ib1.org/2026/04/14/from-volatility-to-visibility-perseus-gas-expansion-helps-smes-manage-risk/</link>
		
		<dc:creator><![CDATA[Ross Crear]]></dc:creator>
		<pubDate>Tue, 14 Apr 2026 09:35:07 +0000</pubDate>
				<category><![CDATA[Energy]]></category>
		<category><![CDATA[Finance]]></category>
		<category><![CDATA[Media]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Perseus]]></category>
		<category><![CDATA[energy]]></category>
		<category><![CDATA[GAS]]></category>
		<category><![CDATA[netzero]]></category>
		<category><![CDATA[SME]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19712</guid>

					<description><![CDATA[Join Perseus today Since the end of February, energy price volatility has been seen across multiple fuels, including oil and [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="has-text-align-center has-ib-1-orange-color has-ib-1-dark-blue-background-color has-text-color has-background"><a href="/join/perseus">Join Perseus today</a></p>



<p>Since the end of February, energy price volatility has been seen across multiple fuels, including oil and gas. And, while this volatility is being felt across the board, SMEs &#8211; <a href="https://www.gov.uk/government/statistics/business-population-estimates-2025/business-population-estimates-for-the-uk-and-regions-2025-statistical-release#composition-of-the-2025-business-population" data-type="URL" data-id="https://www.gov.uk/government/statistics/business-population-estimates-2025/business-population-estimates-for-the-uk-and-regions-2025-statistical-release#composition-of-the-2025-business-population">which represent 99.85% of total business population and £2.8Tn in turnover</a> &#8211; are being disproportionately exposed, particularly to sharp rises in gas prices.</p>



<p>For many SMEs, energy costs represent a meaningful share of operating expenses, particularly in sectors such as accommodation, retail, and food production. This leaves them more exposed to sudden price volatility, especially when access to tools and finance might be limited.</p>



<p>As costs rise, margins tighten and cash flow becomes less predictable, leading to increased uncertainty for both SMEs and lenders. For financial service providers &#8211; <a href="https://www.british-business-bank.co.uk/about/research-and-publications/small-business-finance-markets-report-2026" data-type="URL" data-id="https://www.british-business-bank.co.uk/about/research-and-publications/small-business-finance-markets-report-2026">with over £68bn in SME lending portfolios</a> &#8211; this shapes how risk is assessed and how capital is allocated.</p>



<p>At the same time, SMEs remain difficult to assess due to limited and inconsistent data. Rising uncertainty could push banks to tighten credit conditions across their portfolios, resulting in a feedback loop where SMEs face higher costs and reduced access to finance, while lenders carry greater uncertainty and risk.</p>



<h2><strong>Perseus provides a more complete view of energy costs</strong></h2>



<p>By expanding to include gas data, Perseus directly addresses this problem. In March 2026, the Perseus scheme began incorporating gas data, supporting calculations of Greenhouse Gas Protocol Scope 1 (direct) emissions alongside the Scope 2 (indirect) electricity emissions.</p>



<p>Moving beyond electricity to provide a more complete view of SME energy consumption and emissions gives SMEs better control over their energy exposure, while enabling banks to assess risk, verify impact, and finance the transition with greater confidence.</p>



<p>With this expansion, Perseus is <strong>estimated to have potential reach of over 1 million UK SMEs and cover over 70% of use cases</strong>, reflecting the scale of energy data across organisations.</p>



<p>For more on Perseus gas emissions methodology: <a href="https://ib1.org/perseus/emissions-calculations/">https://ib1.org/perseus/emissions-calculations/</a>&nbsp;</p>



<p><strong>For SMEs, this means:</strong></p>



<ul>
<li>reduced time, cost, and complexity of reporting</li>



<li>a more complete and credible picture of energy use and emissions</li>



<li>better access to finance and incentives</li>



<li>potential for lower cost of borrowing</li>
</ul>



<p><strong>For banks and lenders, it enables:</strong></p>



<ul>
<li>more accurate assessment of SME energy exposure</li>



<li>improved risk pricing and credit decisions</li>



<li>comparable, standardised data across portfolios</li>



<li>the ability to develop targeted financing products linked to energy performance</li>
</ul>



<h2><strong>Renewables over reliance </strong></h2>



<p>Reliance on fossil fuels remains a key driver of energy market volatility. It’s not an imagined scenario either, with Reuters recently reporting that wind output in Q1 2026 increased significantly year-on-year, helping to drive a ~16% drop in gas-fired generation. This cushioned the UK from the impacts of the gas price spike and contributed to relatively lower wholesale power prices versus some European peers.&nbsp;</p>



<p>As more low-cost renewable electricity comes online, reliance on gas, and exposure to its volatility, can be reduced. This means the shift towards a cleaner renewable energy future is more than an environmental move but a financial one too, creating new opportunities for both SMEs and Financial Service Providers.&nbsp;</p>



<p>While renewables can reduce our reliance on gas, flexibility determines how much of that value can actually be captured. For more on the impact I&amp;C Flexibility can have on renewables take-up and the wider energy market, <a href="https://ib1.org/2026/03/26/ic-flexibility-is-ready-to-scale-is-the-data-infrastructure/" data-type="URL" data-id="https://ib1.org/2026/03/26/ic-flexibility-is-ready-to-scale-is-the-data-infrastructure/">read our latest blog.</a> </p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Perseus is infrastructure, not a product</title>
		<link>https://ib1.org/2026/04/01/perseus-is-infrastructure/</link>
		
		<dc:creator><![CDATA[Gavin Starks]]></dc:creator>
		<pubDate>Wed, 01 Apr 2026 10:00:00 +0000</pubDate>
				<category><![CDATA[Briefing]]></category>
		<category><![CDATA[Perseus]]></category>
		<category><![CDATA[Stories]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19644</guid>

					<description><![CDATA[[reading time: 5 mins] As Perseus co-chair, members, stakeholders, and the broader community tell me that it is seen as [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p><em>[reading time: 5 mins]</em></p>



<p>As Perseus co-chair, members, stakeholders, and the broader community tell me that it is seen as a pioneering initiative, with a significant scale of opportunity (at least £5B+ in embedded sustainable finance), but there are still challenges in communicating what it is, and isn&#8217;t, and &#8216;why <em>now</em>?&#8217;.</p>



<blockquote class="wp-block-quote">
<p>&#8220;Collaborate on the rules, compete in the game.&#8221;</p>
</blockquote>



<p><strong>The course is set, now it’s time to shape how value is realised</strong></p>



<p>Perseus is now recognised as a flagship exemplar under the UK Data (Use and Access) Act, supported by both the Smart Data Council (in its<a href="https://www.gov.uk/government/publications/smart-data-strategy"> Smart Data Strategy for 2035)</a> and the Net Zero Council. The regulatory current is moving in this direction, and the Perseus team is both in constructive conversations with regulators and code bodies, and at the table in creating the UK Smart Data guidebook.&nbsp;</p>



<p>Perseus Members are defining where the rules of <strong>embedded sustainable finance</strong> are being written. The question isn&#8217;t whether this infrastructure gets built, it&#8217;s who helps shape it, and who arrives late.</p>



<p>To help better position what Perseus is, here are some of my reflections, based on 300+ conversations.</p>



<figure class="wp-block-image size-full"><img decoding="async" loading="lazy" width="1600" height="575" src="https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026.jpg" alt="" class="wp-image-19678" srcset="https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026.jpg 1600w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-600x216.jpg 600w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-768x276.jpg 768w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-1536x552.jpg 1536w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-830x298.jpg 830w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-230x83.jpg 230w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-350x126.jpg 350w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-480x173.jpg 480w" sizes="(max-width: 1600px) 100vw, 1600px" /></figure>



<p><strong>Getting the data to do the work: SME impact at market scale</strong></p>



<p>SMEs are where the impact is needed (they are <a href="https://www.bath.ac.uk/publications/sme-decarbonisation-in-the-uk-emerging-market-trends-and-their-implications-for-government/">half of UK business emissions)</a>. For the vast majority, carbon reporting is a burden: manual, confusing, inconsistent, and disconnected from anything that actually helps them run their business better.&nbsp;</p>



<p>Perseus flips this: with the SME&#8217;s permission, their energy data flows automatically into their accounting platform and to their lender. No spreadsheets, no data entry, no consultants: they get a verified emissions baseline, access to sustainable finance products they can&#8217;t easily reach, and a credible sustainability story they can use with their own customers and suppliers.&nbsp;</p>



<p>Perseus <em><strong>meets them</strong> <strong>where they</strong> <strong>are</strong>,</em> through the tools and relationships they already have, and costs them almost nothing to participate. Reducing friction and cost is the point of good data infrastructure, getting smart data to do the work so the SME gets the benefits, and the market gets the scale.<strong>&nbsp;</strong></p>



<p><strong>Perseus is infrastructure, not a product</strong></p>



<p>Most responses to addressing SME carbon emissions follow a familiar playbook: build an app, sign up users, grow a dataset, and sell reporting services. Some go further and package insights as a commercial proposition. Both hit the same ceiling: they create value for their own customers, but they don&#8217;t change the market.</p>



<blockquote class="wp-block-quote">
<p>&#8220;Carbon reporting can often be seen as a random number generator linked to compliance, not value.&#8221;</p>
</blockquote>



<p><strong>Data silos are no longer business moats</strong></p>



<p>When data stays siloed and calculations stay inconsistent, every bank, accountant, lender, software provider keeps solving the same problem independently, at their own cost. Multiply that across the whole economy and you have a colossal, systemic waste of time and money: with no true comparability, little trust, and no efficiency of scale. As one senior expert put it, <em>&#8220;it&#8217;s a random number generator linked to compliance, not <strong>value</strong>&#8220;</em>.</p>



<blockquote class="wp-block-quote">
<p>&#8220;Perseus meets SMEs where they are, through the tools and relationships they already have, and costs them almost nothing to participate.&#8221;</p>
</blockquote>



<p>Perseus takes a structurally different route (the same route Open Banking took). The design of Open Banking wasn&#8217;t to &#8216;make a better banking app&#8217;, it was that if you agree the rules by which data flows between <em>any</em> bank and <em>any</em> third party, every player in the market benefits simultaneously, and the infrastructure becomes self-reinforcing as more join.</p>



<p>Perseus applies exactly that logic to SME emissions data: not a pipe, not a platform, a Scheme. A Scheme is a shared rulebook that defines how the data flows, it is legally permissioned, technically assured, and provenance-stamped between energy data sources, carbon accountants, and lenders, regardless of which specific providers are involved.</p>



<p>Schemes are designed to &#8216;do as little as possible&#8217; so that the heavy lifting that they do deliver, can deliver at scale. Perseus is not a database, or a calculator, or a portal. Instead it&#8217;s the trust layer that makes everyone else&#8217;s products work together, enables solutions to <strong>go to where the customer already is,</strong> and makes them credible due to the governance wrapped around its design.</p>



<blockquote class="wp-block-quote">
<p>&#8220;Perseus is not a database, or a calculator, or a portal. It&#8217;s the trust layer that makes everyone else&#8217;s products work together.&#8221;</p>
</blockquote>



<p><strong>No single organisation can build what Perseus builds collectively</strong></p>



<p>Any carbon accounting platform can reach its existing customers, any energy data business can find organisations already looking for a data feed, any bank can bring these things together, but none of them can, on their own, shift the behaviour of 5.5 million SMEs and the financial system that serves them.</p>



<p>Perseus can because its Steering Group and commercial membership collectively represent the whole system: the banks, accountants, energy companies, trade associations, and SME platforms that already have the customer relationships. The joint communications that can flow from this coalition don&#8217;t just amplify awareness, or make &#8216;business today&#8217; more efficient, it creates an addressable market that didn&#8217;t previously exist. By going far together, they can all reach SMEs who have never considered net zero was for them, through channels they already trust: their bank, their accountant, their software tools, and their trade association. Perseus is creating a route to market no individual organisation can replicate through its own sales effort, and this is estimated to be £5B-£10B by 2030 (<a href="https://ib1.org/perseus/2025-report/">see 2025 annual report</a>).</p>



<p>Its benefits can compound in both directions: automating data flows that currently require manual effort, reducing the cost of compliance, reducing friction at every point in the chain and building customer trust not for one product, but at market scale.</p>



<blockquote class="wp-block-quote">
<p>&#8220;Perseus Members are defining where the rules of embedded sustainable finance are being written. The question isn&#8217;t whether this infrastructure gets built, it&#8217;s who helps shape it, and who arrives late.&#8221;</p>
</blockquote>



<p><strong>The value case for a Financial Services Provider (e.g. bank, lender)</strong></p>



<p>There are reasonable objections a bank or lender might raise. Right now, Perseus is a UK SME Scheme, not where the biggest financed emissions numbers sit for most large institutions; they may have existing bilateral data arrangements they&#8217;re reluctant to revisit; and in a climate where public sustainability commitments are under scrutiny anything that looks &#8216;new&#8217; can face internal resistance.&nbsp;</p>



<p>These are valid questions, but they don&#8217;t change the underlying logic.</p>



<p>In <strong>impact</strong>, most initiatives measure engagement, they rarely measure or report on verifiable impact. Perseus enables continuous, assurable measurement, reporting and verification of impact. By harmonising the approach, the reporting is comparable across organisations.</p>



<p>On <strong>scale</strong>: the UK SME market is not a rounding error but <em>half of all UK business emissions</em>. Any lender with a material SME book has a financed emissions reporting problem that carries sufficient risk to increase their cost of capital. Perseus addresses this across the whole market at once. Perseus Members have indicated that &#8216;just&#8217; energy (electricity and gas) addresses over 70% of their use cases, and the programme is designed to expand beyond energy based on Member needs (e.g. water). If we go far together, our collective impact is material and meaningful.</p>



<p>On existing <strong>bilateral arrangements</strong>: Perseus doesn&#8217;t replace them, it improves them through harmonisation of approach, liability and technical provenance. Joining doesn&#8217;t unwind existing relationships, rather it gives them an additional trust layer, aligned with the Data Act and endorsed by the Net Zero Council.</p>



<p>On the <strong>commitment</strong>: Perseus is not a &#8216;climate pledge&#8217;, but an action to deliver the data infrastructure for embedded sustainable finance. Operationally, it&#8217;s equivalent to joining any financial data scheme &#8211; a technical and commercial decision, not a public statement about net zero ambition. It supports diverse go-to-market impact messaging across cost savings, energy efficiency, energy security, net zero and transition planning. It’s not a campaigning approach, but rather a way to deliver measurable value to the market.</p>



<blockquote class="wp-block-quote">
<p>&#8220;Any lender with a material SME book has a financed emissions reporting problem that carries sufficient risk to increase their cost of capital.&#8221;</p>
</blockquote>



<p>On <strong>governance</strong> and <strong>legal</strong> <strong>overhead</strong>: Perseus&#8217; architecture is deliberately modelled on Open Banking. Its legal agreements, certificate infrastructure and KYC processes are designed to align with what regulated financial institutions already do (the path through legal and compliance is not trivial, but it is well-trodden).</p>



<p>Ultimately, the financial providers already in Perseus are sitting in the room where the rules of sustainable finance data infrastructure are being written. It is a choice to be a late adopter of a model that Perseus members helped design, for a membership fee and some internal process. The cost of joining later is accepting the rules written by others.</p>



<p><strong>The value case for a Carbon Accounting Providers (whether financial or carbon management)</strong></p>



<p>A CAP might ask: why do we need Perseus? (we already have integrations with energy data providers, have bank and lender customers, and are building the product that does this).</p>



<p>These are fair points, but miss what Perseus is.</p>



<blockquote class="wp-block-quote">
<p>&#8220;Perseus is not a database, or a calculator, or a portal. It&#8217;s the trust layer that makes everyone else&#8217;s products work together.&#8221;</p>
</blockquote>



<p>Every CAP currently solving this problem is solving it alone: each has negotiated its own data access arrangements, built its own ingestion pipelines, made its own judgements about data quality, and written its own terms. The result is a market where every emissions calculation is done differently, every audit trail looks different, and no two outputs are directly comparable. That&#8217;s not a CAP problem to fix, it is a market structure problem, and no single CAP can fix market structure.</p>



<p>This has been the case for decades. Now the baseline calculation needs to become pre-competitive infrastructure (co-designed and delivered by the market) so that CAPs can compete on the value they build on top of it.</p>



<p><strong>Collaborate on the rules, compete in the game</strong></p>



<p>Perseus addresses this by establishing a common trust layer (common legal agreements, provenance standards, assurance levels, harmonised calculations) so that data flowing into any Perseus-connected CAP is verified, traceable, and comparable to data flowing into every other. This doesn&#8217;t commoditise the CAP&#8217;s product, but rather makes the CAP&#8217;s product something an SME or bank can actually rely on, report against, and put in front of an auditor with confidence.</p>



<p>On <strong>distribution</strong>: joining Perseus is not just a technical integration but access to a network of lenders, trade associations and SME platforms that <strong>collectively reach the entire UK</strong> <strong>SME market</strong>. This is a route to market no CAP can replicate through its own commercial efforts. Perseus-connected CAPs are not just selling software but access to a trusted, standards-aligned data flow that their competitors outside the scheme cannot match.</p>



<p>On the <strong>competitive</strong> question: the CAPs already building Perseus integrations reach hundreds of thousands of UK SMEs today. They are not waiting before positioning themselves within it. Waiting until Perseus is &#8216;already proven&#8217; before engaging will find the integrations, the relationships, and the market positioning is already occupied.</p>



<p>On<strong> effort</strong>: Perseus adds a compliance overhead, but this is inversely proportional to scale. The cost of integrating once (which can be done in under a month) with a common framework is substantially lower than maintaining multiple bespoke bilateral arrangements as the market grows. Perseus reduces long-run complexity, it doesn&#8217;t add to it.</p>



<p>Spend-based estimates or manually uploaded spreadsheets are no longer fit-for-purpose. Perseus provides the foundations that CAPs can build on top of, creates trust, defensibility, reduces long-term costs, increases market engagement and innovation.</p>



<p>To go far, we go together.</p>



<p class="has-text-align-center has-ib-1-orange-color has-ib-1-dark-blue-background-color has-text-color has-background"><a href="/join/perseus">Join Perseus today</a></p>



<figure class="wp-block-image size-full"><img decoding="async" loading="lazy" width="1600" height="575" src="https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026.jpg" alt="" class="wp-image-19678" srcset="https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026.jpg 1600w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-600x216.jpg 600w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-768x276.jpg 768w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-1536x552.jpg 1536w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-830x298.jpg 830w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-230x83.jpg 230w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-350x126.jpg 350w, https://ib1.org/wp-content/uploads/2026/04/IB1-PERSEUS-overview-2026-480x173.jpg 480w" sizes="(max-width: 1600px) 100vw, 1600px" /></figure>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>DRCF insights: Smart Data frameworks</title>
		<link>https://ib1.org/2026/03/31/drcf-insights-smart-data-frameworks/</link>
		
		<dc:creator><![CDATA[Gavin Starks]]></dc:creator>
		<pubDate>Tue, 31 Mar 2026 10:23:09 +0000</pubDate>
				<category><![CDATA[Briefing]]></category>
		<category><![CDATA[Opinion]]></category>
		<category><![CDATA[Reports]]></category>
		<category><![CDATA[Research]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19663</guid>

					<description><![CDATA[About&#160; Ref: https://drcf.org.uk/publications/papers/insightssmartdataframeworks&#160; Published on 26 March 2026, this report from the Digital Regulation Cooperation Forum (DRCF) provides an international [&#8230;]]]></description>
										<content:encoded><![CDATA[
<h3><strong>About&nbsp;</strong></h3>



<div class="wp-block-media-text alignwide is-stacked-on-mobile" style="grid-template-columns:18% auto"><figure class="wp-block-media-text__media"><img decoding="async" loading="lazy" width="800" height="1147" src="https://ib1.org/wp-content/uploads/2026/03/drcf.jpg" alt="" class="wp-image-19666 size-full" srcset="https://ib1.org/wp-content/uploads/2026/03/drcf.jpg 800w, https://ib1.org/wp-content/uploads/2026/03/drcf-418x600.jpg 418w, https://ib1.org/wp-content/uploads/2026/03/drcf-768x1101.jpg 768w, https://ib1.org/wp-content/uploads/2026/03/drcf-230x330.jpg 230w, https://ib1.org/wp-content/uploads/2026/03/drcf-350x502.jpg 350w, https://ib1.org/wp-content/uploads/2026/03/drcf-480x688.jpg 480w" sizes="(max-width: 800px) 100vw, 800px" /></figure><div class="wp-block-media-text__content">
<p>Ref: <a href="https://www.drcf.org.uk/publications/papers/insightssmartdataframeworks">https://drcf.org.uk/publications/papers/insightssmartdataframeworks</a>&nbsp;</p>



<p>Published on 26 March 2026, this report from the <strong>Digital Regulation Cooperation Forum</strong> (DRCF) provides an international comparative analysis of Smart Data implementation models to inform the UK&#8217;s strategic approach under the Data (Use and Access) Act (DUAA) 2025. </p>
</div></div>



<p><strong>Core focus</strong></p>



<p>The report reviews how jurisdictions worldwide have approached consumer data portability and Smart Data ecosystems, drawing lessons to help the UK implement its cross-sectoral Smart Data ambitions. The DUAA 2025 empowers the Secretary of State to create sector-specific Smart Data schemes via secondary legislation, building on the Open Banking precedent. As of May 2025, one in five UK consumers and small businesses were actively using Open Banking services, up from one in seventeen in March 2021.</p>



<h3><strong>Three implementation models</strong></h3>



<p>The report categorises global Smart Data approaches into three main models:</p>



<p><strong>1. Regulator-mandated</strong>&nbsp;</p>



<p>Government-led, prescriptive legislation (e.g. Australia&#8217;s Consumer Data Right, Brazil&#8217;s Open Finance). Provides legal certainty and mandated participation, but risks high compliance costs, regulatory rigidity, and potential for stifling innovation. Australia&#8217;s experience is cited as a cautionary tale of disproportionate costs relative to uptake.</p>



<p><strong>2. Market-facilitated</strong>&nbsp;&nbsp;</p>



<p>Industry-driven, with regulators in a facilitative role (e.g. US, Japan, Hong Kong). Fosters innovation and commercial flexibility but suffers from inconsistent standards, fragmentation, slower incumbent adoption, and uncertain liability frameworks. The US is experiencing particular instability following legal challenges to its framework, which has been seen as lacking unambiguous positioning.</p>



<p><strong>3. Public infrastructure-led</strong>&nbsp;</p>



<p>Built on foundational national Digital Public Infrastructure such as digital identity and data exchange layers (e.g. Estonia&#8217;s X-Road, Singapore&#8217;s SGFinDex via Singpass). These solve interoperability and trust-by-design but require major upfront investment and sustained political commitment. Estonia saves an estimated 820+ years of working time annually through X-Road.</p>



<p>A fourth category, Hybrid and Transitioning, covers jurisdictions like India (Account Aggregator / DEPA framework, with over 100 million consents by 2024) and the UAE (transitioning from market-led to a centrally mandated Open Finance framework).</p>



<h3><strong>Key themes from the analysis</strong></h3>



<p><strong>Governance</strong></p>



<p>A central coordinating body is consistently identified as critical. Without it, sector-by-sector schemes under the DUAA risk creating new data silos rather than eliminating them.</p>



<p><strong>Standards and interoperability</strong></p>



<p>Cross-sector fragmentation is a recurring failure mode. The risk that different UK government departments managing different Smart Data schemes could produce divergent technical standards is highlighted as a significant concern.</p>



<p><strong>Consumer consent journey</strong></p>



<p>Legal compliance alone is insufficient. The quality of the consent user experience is as important as the legal principle. Brazil&#8217;s experience shows how broadly drafted consent forms led to data misuse and loss of public trust. India&#8217;s AA framework shows high consent numbers but low conversion due to friction. Singapore&#8217;s integration with Singpass is held up as a model of frictionless, trustworthy consent.</p>



<p><strong>International alignment</strong></p>



<p>The report recommends aligning with Gaia-X (the EU&#8217;s federated data infrastructure framework) to protect the UK&#8217;s data adequacy status (renewed until 2031), maintain access to EU digital markets, and reduce compliance burdens for internationally active businesses.</p>



<p><strong>Anti-competitive risks</strong></p>



<p>The report flags the possibility that Smart Data schemes could inadvertently facilitate tacit collusion if they enable easy monitoring of competitor pricing — a novel risk that warrants safeguards by design.</p>



<h3><strong>Considerations for the UK</strong></h3>



<p>The report proposes five strategic pillars:</p>



<ol>
<li><strong>A central Smart Data governance body</strong> to coordinate all schemes, set baseline standards, and prevent fragmentation.</li>



<li><strong>Phased, use-case-driven rollout</strong> prioritising energy (for Net Zero), finance, and telecoms, learning iteratively before expanding.</li>



<li><strong>Sector-tailored implementation models</strong> — acknowledging that some sectors suit market-led approaches while others need regulatory mandates, within a unified strategic framework.</li>



<li><strong>Interoperability by design</strong>, integrating with the UK&#8217;s Digital Verification Services (DVS) trust framework (as envisioned in the DUAA) to create a trusted, unified consent architecture.</li>



<li><strong>Clear secondary legislation</strong> covering liability frameworks, security standards, transparent cost-benefit processes, and safeguards against anti-competitive conduct.</li>
</ol>



<h3><strong>Relevance to IB1</strong></h3>



<p>The DRCF report findings and recommendations are closely aligned with IB1&#8217;s existing work and strategic positioning.&nbsp;&nbsp;</p>



<p><strong>Central governance and Trust Frameworks</strong></p>



<p>The report&#8217;s core recommendation, a ‘central’ body setting common baseline standards and ensuring cross-sectoral interoperability, closely mirrors the architecture IB1 has developed through its Trust Framework and Scheme architecture. The DRCF&#8217;s concern about fragmented sectoral schemes producing new data silos is precisely the problem IB1&#8217;s governance approach is designed to solve, specifically the interoperability between them.</p>



<p><strong>Energy Smart Data and Perseus</strong>&nbsp;</p>



<p>The report explicitly names energy as a priority sector for Smart Data designation, citing its alignment with Net Zero policy objectives. IB1&#8217;s Perseus programme, enabling permissioned energy data access for SME carbon reporting and green finance, is an existing example of the kind of sector-specific, use-case-driven scheme the report advocates.</p>



<p><strong>Consent and liability frameworks</strong></p>



<p>IB1 has developed detailed consent and liability standards across energy, water, finance, supply chains, and other sectors. The DRCF&#8217;s finding that the quality of the consent journey is as critical as the legal principle, and that clear liability apportionment is essential for industry confidence, directly reinforces the value of this work.</p>



<p><strong>Interoperability across sectors</strong></p>



<p>The report warns that without strong central coordination, different government departments could develop incompatible standards across schemes. IB1&#8217;s cross-sector interoperability work, including its engagement between Open Energy, Perseus and Open Banking, addresses this risk directly.</p>



<p><strong>International standards alignment</strong></p>



<p>The report recommends aligning with international frameworks such as Gaia-X. IB1&#8217;s engagement with cross-border data governance and its work across multiple jurisdictions is consistent with this direction.</p>



<p>The DRCF report diagnosis and recommendations map closely with the approach IB1 has built, and provides independent external validation of the strategic importance of IB1’s work.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Perseus Advisory Group 4 (Communications &#038; Engagement) Summary Minutes March 2026</title>
		<link>https://ib1.org/2026/03/30/perseus-advisory-group-4-march-meeting-summary/</link>
		
		<dc:creator><![CDATA[Janice Holloway]]></dc:creator>
		<pubDate>Mon, 30 Mar 2026 14:58:11 +0000</pubDate>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[Minutes]]></category>
		<category><![CDATA[Perseus]]></category>
		<category><![CDATA[Programmes]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19660</guid>

					<description><![CDATA[We reconvened the Perseus Engagement &#38; Communications Advisory Group, co-chaired by Icebreaker One and Tide. Date: 26 March 2026 10:00-10:45 GMT [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>We reconvened the Perseus Engagement &amp; Communications Advisory Group, co-chaired by <a href="https://icebreakerone.org/">Icebreaker One</a> and <a href="https://www.tide.co/">Tide</a>.</p>



<p>Date: 26 March 2026 10:00-10:45 GMT</p>



<p>Location: online</p>



<p>Co-Chairs: Laura Townshend, (IB1); Zarina Banu, (Tide) </p>



<p>Secretariat: IB1</p>



<p><strong>Meeting Aims</strong>:</p>



<ol>
<li>Update on case studies</li>



<li>Discuss upcoming actions</li>



<li>Review Vision statement</li>
</ol>



<p>It was <strong>agreed </strong>that:</p>



<ul>
<li>British Chambers of Commerce, FSB and IOD should be prioritised as strategic targets to help amplify comms due to their credibility, authority and member reach</li>



<li>The updated Perseus’ vision and mission statement should be approved</li>
</ul>



<p>It was <strong>noted</strong> that:</p>



<ul>
<li>Innovate Finance&#8217;s Global Summit is in April and panel opportunities on sustainable energy featuring Perseus maybe available</li>



<li>London Climate Action Week takes place in June and IB1 has a cross-sector meetup planned</li>



<li>One of the members has two potential SME contacts who might be able to contribute, both PR-ready having presented at the Houses of Parliament</li>
</ul>



<p>It was <strong>discussed </strong>that:</p>



<ul>
<li>The geopolitical context presents a timely opportunity to amplify Perseus messaging, particularly around energy sovereignty, the government&#8217;s consideration of decoupling gas/electric price caps, and the cost of living crisis</li>



<li>Small businesses are being significantly impacted by energy costs, national insurance increases, minimum wage changes and inflation, making Perseus a relevant operational efficiency solution</li>



<li>In order to achieve amplification, there is a need to identify the right internal spokespeople within steering group member organisations, not just the steering group representatives themselves</li>
</ul>



<p><strong>Next meeting</strong>: Thursday 28 May 2026 10:00-10:45 BST</p>



<p>Formal records, including attendees, are maintained by the secretariat. </p>



<p>These are confidential to the Advisory Group Members.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>UK Smart Data Strategy &#8211; to 2035</title>
		<link>https://ib1.org/2026/03/27/uk-smart-data-strategy/</link>
		
		<dc:creator><![CDATA[Gavin Starks]]></dc:creator>
		<pubDate>Fri, 27 Mar 2026 13:35:53 +0000</pubDate>
				<category><![CDATA[Briefing]]></category>
		<category><![CDATA[Milestones]]></category>
		<category><![CDATA[open energy]]></category>
		<category><![CDATA[Perseus]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[stream]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19637</guid>

					<description><![CDATA[The UK Gov Smart Data Strategy is now live. https://www.gov.uk/government/publications/smart-data-strategy For IB1, this is core to our work &#8211; and [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>The UK Gov Smart Data Strategy is now live.</p>



<ul>
<li>twenty interoperable Smart Data schemes by 2035</li>



<li>£36m of Industrial Strategy investment</li>



<li>cross-sector Trust Frameworks and data sharing interoperability across the economy</li>
</ul>



<p><a href="https://www.gov.uk/government/publications/smart-data-strategy
">https://www.gov.uk/government/publications/smart-data-strategy</a></p>



<p>For IB1, this is core to our work &#8211; and features the <a href="/perseus">Perseus</a> programme. It underpins how we will help deliver our sustainable economy into a data-enabled digital-first era, building the load-bearing foundations for trust, protecting our data rights, and delivering impact. </p>



<p>Open Banking took a decade to get right: we can now move much, much faster.&nbsp;The opportunity isn&#8217;t just &#8216;switching&#8217;, it&#8217;s opening up new markets and connecting financial flows to real-world outcomes at scale. The time to engage is now: the schemes being shaped today will define the data infrastructure of the next decade.</p>



<p>The UK has a great team helping to lead this, with <a href="https://www.linkedin.com/in/samanthaseaton/">Samantha</a> as co-chair, the <a href="https://www.linkedin.com/company/department-for-business-and-trade/">Department for Business and Trade</a> (<a href="https://www.linkedin.com/in/siobhan-dennehy-1a954535/">Siobhan</a>, <a href="https://www.linkedin.com/in/agnieszkascott/">Agnieszka</a>, <a href="https://www.linkedin.com/in/pmr15/">Priya</a>, and a growing support team), and non-govt Smart Data Council members including <a href="https://www.linkedin.com/in/henkvanhulle/">Henk</a>, <a href="https://www.linkedin.com/in/adamjacksonuk/">Adam</a>, <a href="https://www.linkedin.com/in/liz-brandt-a5824b1/">Liz</a>, <a href="https://www.linkedin.com/in/charliemercer/">Charlie</a>, <a href="https://www.linkedin.com/in/mariewalker1/">Marie</a>, <a href="https://www.linkedin.com/in/csouthworth/">Chris</a>, <a href="https://www.linkedin.com/in/ezechi-britton-mbe-452a893/">Ezechi</a>, <a href="https://www.linkedin.com/in/ghelaboskovich/">Ghela</a>, <a href="https://www.linkedin.com/in/helen-margetts-1601bb34/">Helen</a>, <a href="https://www.linkedin.com/in/joe-cuddeford-2a441685/">Joe</a>, <a href="https://www.linkedin.com/in/jdaddario/">Josh</a> , <a href="https://www.linkedin.com/in/louisebeaumont/">Louise</a>, <a href="https://www.linkedin.com/in/mariaharrisdigitalcat/">Maria</a>, <a href="https://www.linkedin.com/in/nicola-anderson-227b3779/">Nicola</a>, <a href="https://www.linkedin.com/in/stephen-wright-50195/">Stephen</a>, <a href="https://www.linkedin.com/in/janelucy/">Jane</a>, <a href="https://www.linkedin.com/in/lucyyu1/">Lucy</a>, <a href="https://www.linkedin.com/in/sue-daley-obe-b13398b6/">Sue</a> and many others across industry and government now engaged.<br><br>At <a href="https://www.linkedin.com/company/icebreaker-one/">Icebreaker One</a> it&#8217;s what we&#8217;ve been building with <a href="/energy">IB1 Open Energy</a> <a href="/perseus">Perseus</a><a href="https://www.linkedin.com/search/results/all/?keywords=%23stream&amp;origin=HASH_TAG_FROM_FEED">,</a> <a href="https://www.linkedin.com/search/results/all/?keywords=%23stream&amp;origin=HASH_TAG_FROM_FEED">STREAM</a> and our <a href="https://ib1.org/?s=Data+infrastructure">Data Infrastructure</a> work and we will continue to lead on Open Sustainable Finance.</p>


<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><a href="https://assets.publishing.service.gov.uk/media/69c50b1e93cc6e8b87a6f708/smart-data-strategy-large-print.pdf"><img decoding="async" loading="lazy" src="https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data-1424x2048.jpg" alt="" class="wp-image-19642" width="393" height="565" srcset="https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data-1424x2048.jpg 1424w, https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data-417x600.jpg 417w, https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data-768x1105.jpg 768w, https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data-1068x1536.jpg 1068w, https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data-830x1194.jpg 830w, https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data-230x331.jpg 230w, https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data-350x504.jpg 350w, https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data-480x691.jpg 480w, https://ib1.org/wp-content/uploads/2026/03/UK-Smart-Data.jpg 1484w" sizes="(max-width: 393px) 100vw, 393px" /></a></figure></div>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>I&#038;C flex ready to scale. Is the data infrastructure?</title>
		<link>https://ib1.org/2026/03/26/ic-flexibility-is-ready-to-scale-is-the-data-infrastructure/</link>
		
		<dc:creator><![CDATA[Ross Crear]]></dc:creator>
		<pubDate>Thu, 26 Mar 2026 15:57:48 +0000</pubDate>
				<category><![CDATA[Energy]]></category>
		<category><![CDATA[Media]]></category>
		<category><![CDATA[Open Energy]]></category>
		<category><![CDATA[Webinars]]></category>
		<category><![CDATA[energydata]]></category>
		<category><![CDATA[energysector]]></category>
		<category><![CDATA[net-zero]]></category>
		<category><![CDATA[open energy]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19591</guid>

					<description><![CDATA[Consumer-led Industrial and Commercial (I&#38;C) flexibility allows large energy consumers (factories, retailers, office blocks, data centres, hospitals etc.) to adjust [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Consumer-led Industrial and Commercial (I&amp;C) flexibility allows large energy consumers (factories, retailers, office blocks, data centres, hospitals etc.) to adjust their net energy consumption for short periods in response to the needs of the grid, incentivised through flexibility markets. </p>



<p>In the electricity market, this enables demand to respond to supply, a crucial shift as sectors move towards electrification and as electricity production shifts to cheaper, cleaner, but more intermittent, renewable sources.</p>



<p>Flexibility forms up a core part of the government’s <a href="https://assets.publishing.service.gov.uk/media/677bc80399c93b7286a396d6/clean-power-2030-action-plan-main-report.pdf" data-type="URL" data-id="https://assets.publishing.service.gov.uk/media/677bc80399c93b7286a396d6/clean-power-2030-action-plan-main-report.pdf">Clean Power 2030 Action Plan</a> and is explored in depth in the <a href="https://assets.publishing.service.gov.uk/media/68874ddeb0e1dfe5b5f0e431/clean-flexibility-roadmap.pdf" data-type="URL" data-id="https://assets.publishing.service.gov.uk/media/68874ddeb0e1dfe5b5f0e431/clean-flexibility-roadmap.pdf">Clean Flexibility Roadmap</a>. It also delivers clear value, from reducing system costs for networks to unlocking new revenue streams and resilience for energy users. But, realising its full potential and accelerating the transition to Net Zero requires market-wide adoption.</p>



<h4>Benefits of I&amp;C flexibility</h4>



<p><strong>For grid operators, enabling flexibility can deliver:</strong></p>



<ul>
<li>Reduced generation curtailment</li>



<li>Reduced need for expensive grid-scale energy storage projects</li>



<li>Reduced costs for grid capacity upgrades</li>



<li>Alignment with Ofgem’s forthcoming RIIO-ED3 price control</li>
</ul>



<p><strong>For I&amp;C Consumers, benefits include</strong>:</p>



<ul>
<li>Lower energy costs</li>



<li>New revenue streams</li>



<li>Reduced expenditure on grid connection upgrades</li>



<li>Increased resilience for key consumers, such as hospitals, in times of grid stress</li>
</ul>



<p></p>



<h3>Data is the common thread</h3>



<p>And yet, I&amp;C flexibility isn&#8217;t one-size-fits-all. It encompasses a spectrum of approaches from direct demand response (where consumption is increased or decreased for a set period) to more sophisticated coordination of co-located technologies like solar, battery storage, heat pumps, and EV fleets.</p>



<p><strong>What connects these approaches is data.</strong> Granular, trusted data sharing enables I&amp;C sites to assess what options are feasible and maximise the benefits of participating in flexibility markets. Electricity networks also need real-time, high-quality data to plan and operate their networks, and to balance supply and demand. Without this, take-up of I&amp;C flexibility will not reach its full potential, or will be costly to implement.</p>



<h4 class="has-white-color has-ib-1-dark-blue-background-color has-text-color has-background">Sharing large amounts of data between diverse groups or organisations can lead to challenges including:</h4>



<ul class="has-white-color has-ib-1-dark-blue-background-color has-text-color has-background">
<li>Varying data formats, standards and semantics</li>



<li>Separate representations of network assets and constraints</li>



<li>Different data publication schedules</li>



<li>Non-interoperable licensing and permissioning frameworks</li>



<li>Issues with machine-readability</li>



<li>Commercial and security sensitivities</li>



<li>A lack of easy consumer data portability</li>



<li>Fragmented data on existing I&amp;C flexibility participation and performance</li>
</ul>



<p></p>



<p>For I&amp;C consumers, these barriers make it harder to identify viable flexibility opportunities and build robust business cases. This increases cost and complexity, often diverting time and investment elsewhere.</p>



<p><strong>Unlocking flexibility at the speed and scale required to decarbonise the grid will therefore require a fundamental shift in how data is shared.</strong></p>



<h4>A data sharing scheme to accelerate I&amp;C flexibility</h4>



<p>The market needs a way for I&amp;C actors to securely and easily share data with authorised parties to assess, plan and deliver flexibility at scale. Open Energy’s mission is to collaboratively define and develop a data sharing <a href="https://ib1.org/definitions/scheme/" data-type="URL" data-id="https://ib1.org/definitions/scheme/">Scheme </a>to support this, recognising that delivery is a co-ordination challenge, requiring collaboration to solve.</p>



<p>No single organisation can solve this alone, and implementing technical solutions without understanding the needs, constraints, and capabilities of others risks becoming an expensive exercise with unreliable outcomes.</p>



<p>The scheme will align with wider energy and cross sector initiatives such as NESO Data Sharing Infrastructure, RECCo Consumer Consent Solution, Elexon Flexibility Market Asset Register, Market-Wide Half-Hourly Settlement, and Smart Data policy), strengthening the overall data ecosystem and enabling interoperability.</p>



<p>Open Energy brings together energy system and I&amp;C participants to build the data foundations for accelerating flexibility. IB1 acts as a neutral facilitator and data governance expert supported by the <a href="https://ib1.org/tf/estf/" data-type="URL" data-id="https://ib1.org/tf/estf/">Energy Sector Trust Framework</a>, a ready-to-use mechanism for governing the exchange of data in a consistent, trusted, and scalable way, without the need for centralised infrastructure.</p>



<h4>How your organisation can benefit</h4>



<p>If flexibility impacts your organisation, whether as an opportunity, a challenge, or a dependency, being part of Open Energy gives you a seat at the table, where the future of data sharing is being built. You’ll also help shape how the Energy Sector Trust Framework evolves to meet the specific needs of the flexibility market.</p>



<p><strong>For networks:</strong></p>



<ul>
<li>Contribute to, and benefit from, sector-wide alignment on data classification, licensing, and access controls</li>



<li>Reduce the risk of costly inconsistencies emerging as flexibility markets mature.</li>
</ul>



<p><strong>For flexibility providers and aggregators:</strong></p>



<ul>
<li>Access cleaner, more consistent data pipelines</li>



<li>Access a governance framework that makes it easier to operate across multiple network areas.</li>
</ul>



<p><strong>For large energy consumers and trade bodies:</strong></p>



<ul>
<li>Gain faster visibility of viable flexibility opportunities and incentives</li>



<li>Access insights to support adoption and decision-making</li>
</ul>



<p></p>



<h4>Join us &amp; your peers</h4>



<p>To find out more about the Industrial &amp; Commercial Flexibility use case, or to join Open Energy, get in touch with us at openenergy@ib1.org  </p>



<p>And register for our upcoming webinar: <a href="https://events.humanitix.com/oe-i-and-cflex-webinar">https://events.humanitix.com/oe-i-and-cflex-webinar</a></p>



<p>The decisions being made now will shape the direction of the energy sector for years to come. Those helping to shape it will be best placed to benefit from the opportunities that follow.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Stream Steering Group March Meeting Summary</title>
		<link>https://ib1.org/2026/03/23/stream-steering-group-march-meeting-summary-2/</link>
		
		<dc:creator><![CDATA[Janice Holloway]]></dc:creator>
		<pubDate>Mon, 23 Mar 2026 12:46:31 +0000</pubDate>
				<category><![CDATA[Minutes]]></category>
		<category><![CDATA[Programmes]]></category>
		<category><![CDATA[Stream]]></category>
		<category><![CDATA[Water]]></category>
		<category><![CDATA[stream]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19557</guid>

					<description><![CDATA[A Stream Steering Group was convened on 2026-03-10. The Steering Group comprises experts that represent [Stream] water companies, regulators, research, [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>A Stream Steering Group was convened on 2026-03-10.  The Steering Group comprises experts that represent [Stream] water companies, regulators, research, innovation bodies and government. Co-chaired by <a href="https://icebreakerone.org/">Icebreaker One</a> and <a href="https://www.nwl.co.uk/">NWL</a>, the group’s primary function is to help provide leadership and market signalling. </p>



<p>Date: Tuesday 10 March 2026 10:00-12:00 GMT</p>



<p>Location: online</p>



<p>Co-Chairs: Melissa Tallack (NWL); Gavin Starks (IB1)</p>



<p>Secretariat: IB1</p>



<p><strong>Meeting Aims</strong> </p>



<ol>
<li>Sign off Q2 outcomes and priority use case</li>



<li>Align on bids process criteria for incoming bids</li>
</ol>



<p><strong>Summary:</strong></p>



<ul>
<li>It was <strong>agreed</strong> that:
<ul>
<li>Q2 strategic business priorities include: (endorsed by members after this meeting)
<ul>
<li>defining Stream’s 12‑month ambition and roadmap</li>



<li>continuing development of the Change Champion network</li>



<li>establishing a clearer process for supporting funding bids</li>



<li>progressing the Open Data maturity assessment plan.</li>
</ul>
</li>



<li>The first prioritised Water Efficiency use case for this year will be Water Situation Reports.</li>
</ul>
</li>



<li>It was <strong>noted</strong> that:
<ul>
<li>Co-ordination will be required with the Environment Agency for the water situation report (as the report is owned by the EA)</li>



<li>Growing demand for Stream support on shared data use cases highlights the need for a clearer triage and prioritisation approach.</li>



<li>Members and observers felt there were certain items that should be taken into consideration, such as scope clarification (open vs shared data), the importance of FOI/EIR alignment, and maintaining opt‑in/opt‑out flexibility.</li>



<li>Energy sector learnings highlight the importance of common pattern libraries and Trust Frameworks to minimise cost and legal complexity.</li>



<li>Cross‑sector use cases may present future opportunities and should be considered in long‑term design thinking.</li>
</ul>
</li>



<li>It was <strong>discussed</strong> that:
<ul>
<li>The bids process requires refinement, including criteria such as value, repeatability, resource impact, technology implications, and avoiding parallel infrastructures.</li>



<li>A scoring matrix for shared data use cases could include economic, social and environmental value, friction reduction, legal complexity, and organisational readiness.</li>



<li>A Trust Framework model separating identity assurance from Scheme rules could lower future cost and improve cross‑sector interoperability.</li>



<li>Sector legal engagement will be challenging but early use case examples could build confidence and reduce friction.</li>



<li>Further knowledge‑sharing and workshops are needed to deepen understanding of Trust Frameworks and scheme governance.</li>
</ul>
</li>
</ul>



<p><strong>Next meeting:</strong> Tuesday 21 April 2026 10:00-12:00 BST</p>



<p>Formal records, including attendees, are maintained by the secretariat. </p>



<p>These are confidential to the Steering Group Members.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Perseus Steering Group Summary Minutes February 2026</title>
		<link>https://ib1.org/2026/03/11/perseus-steering-group-february-summary-minutes/</link>
		
		<dc:creator><![CDATA[Janice Holloway]]></dc:creator>
		<pubDate>Wed, 11 Mar 2026 14:59:58 +0000</pubDate>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[Minutes]]></category>
		<category><![CDATA[Perseus]]></category>
		<category><![CDATA[Programmes]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19533</guid>

					<description><![CDATA[A Perseus Steering Group was convened on 2026-02-23. Co-chaired by the British Business Bank and Icebreaker One, the Perseus Steering Group [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>A Perseus Steering Group was convened on 2026-02-23. Co-chaired by the <a href="https://www.british-business-bank.co.uk/">British Business Bank </a>and <a href="https://ib1.org/">Icebreaker One</a>, the Perseus Steering Group includes major trade associations that represent stakeholders, UK Government and international observers. It plays a critical role in engagement, dissemination, and fostering trust in decision-making. </p>



<p>Date: Monday 23 February 2026 13:00-15:00 GMT</p>



<p>Location: online</p>



<p>Co-Chairs: Gavin Starks (IB1); Hannah Gilbert (British Business Bank)</p>



<p>Secretariat: IB1</p>



<p><strong>Meeting Aims</strong> </p>



<ol>
<li>Agree on updated vision and mission</li>



<li>Understand 2026 roadmap</li>



<li>Update on DOC and AG</li>



<li>Commit to amplifying case studies</li>



<li>Identify funding sources</li>
</ol>



<p><strong>Summary:</strong></p>



<ul>
<li>It was <strong>agreed</strong> that:
<ul>
<li>Case studies are the critical success metric for 2026. The ambition is to secure at least five examples that demonstrate real-world application.</li>



<li>Alignment with the Net Zero Council and the Smart Data Council agenda should continue, positioning Perseus as an exemplar of Smart Data implementation and Net Zero innovation.</li>
</ul>
</li>



<li>It was <strong>noted</strong> that:
<ul>
<li>The 2025 AGM reflected strong engagement from key stakeholders and financial service providers (including incumbents NatWest, Barclays and Lloyds and challenger banks).</li>



<li>Language has evolved to “embedded sustainable finance”, with continued emphasis on SME impact.</li>



<li>Sandbox learnings (AG2) identified and resolved integration challenges (e.g. with certificate authentication, improved documentation and clarity of roles, setup guides, tooling and specifications have been developed in response).</li>



<li>Legal updates (AG3) incorporate gas into permission text, clarify CAP-initiated (two-click) and FSP-initiated (single-click) consent journeys; Scheme agreement documentation has been consolidated; changes remain compliant with prior external legal advice.</li>



<li>Annual renewals remain the current funding model, with forecast renewals on track but cashflow risk recognised and multi-annual renewals should be considered.</li>



<li>The relationship with B4NZ (formerly ‘Bankers for Net Zero’) was recognised as having been supportive in the formation of the programme, and there is no ongoing relationship with that initiative.</li>



<li>Adam Jackson has accepted the role of DOC Chair.</li>
</ul>
</li>



<li>It was <strong>discussed</strong> that:
<ul>
<li>The proposed new vision, “Embedded sustainable finance for SMEs”, provides a clear and memorable direction of travel. Further refinement of mission language will be considered to ensure terminology resonates with SMEs.</li>



<li>The SME focus remains strategically valuable for maintaining clarity and discipline. Discussion included whether anchoring exclusively on SMEs may constrain broader use cases and it was noted that related initiatives (e.g. <a href="http://ib1.org/Orion">ib1.org/Orion</a> and <a href="http://ib1.org/carbon-commons">ib1.org/carbon-commons</a>) had been created as channels to help develop ideas without distracting from Perseus’ core mission.</li>



<li>Case study development faces practical barriers: delays often arise from internal processes and time constraints, rather than inherent SME reluctance. It was noted that the majority SMEs day-to-day concerns are focussed on cash, not sustainability, and that Perseus’ strategy to reduce both cost and friction for SMEs (including ‘taking solutions to where the SME already are’) was the correct approach.</li>
</ul>
</li>
</ul>



<p><strong>Next meeting:</strong> Monday 18 May 2026 13:00-15:00 BST</p>



<p>Formal records, including attendees, are maintained by the secretariat. </p>



<p>These are confidential to the Steering Group Members.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Stream Advisory Group 2 February Meeting Summary</title>
		<link>https://ib1.org/2026/03/05/stream-advisory-group-2-february-meeting-summary/</link>
		
		<dc:creator><![CDATA[Janice Holloway]]></dc:creator>
		<pubDate>Thu, 05 Mar 2026 13:12:27 +0000</pubDate>
				<category><![CDATA[Minutes]]></category>
		<category><![CDATA[Programmes]]></category>
		<category><![CDATA[Stream]]></category>
		<category><![CDATA[Water]]></category>
		<category><![CDATA[stream]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19499</guid>

					<description><![CDATA[We reconvened the Stream Technical Advisory Group, Co-chaired by Icebreaker One and Pennon Group. Date: 24 February 2026 10:00-11:30 GMT Location: Online Co-Chairs: [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>We reconvened the Stream Technical Advisory Group, Co-chaired by <a href="https://ib1.org/">Icebreaker One</a> and <a href="https://www.pennon-group.co.uk/">Pennon Group.</a></p>



<p>Date<strong>: </strong>24 February 2026 10:00-11:30 GMT</p>



<p>Location: Online</p>



<p>Co-Chairs:<strong> </strong>Lucy Chambers (IB1); Darren Anderson (NWL)</p>



<p>Secretariat<strong>:</strong> Icebreaker One </p>



<p><strong>Meeting Aims</strong></p>



<ol>
<li>Endorse the Q2 outcomes</li>



<li>Endorsement for CReDO data standardisation</li>



<li>Accelerating the decision towards sharing agreement templates</li>
</ol>



<p><strong>Summary</strong>:</p>



<ul>
<li>It was<strong> agreed</strong> that:
<ul>
<li>There were no significant concerns with the overall approach; however, the primary delivery risk identified was engagement with internal legal teams.</li>



<li>There’s value in the development of reusable artefacts and templates to avoid repeated drafting and to help colleagues engage legal teams more effectively.</li>
</ul>
</li>



<li>It was <strong>noted</strong> that:
<ul>
<li>A decision was made to continue with Esri on a reduced basis, with the cost totalling £27,000, down from £45,000 in year 1 and 2 of the project.</li>



<li>Q2 outcomes were presented for endorsement, including:
<ul>
<li>progressing data sharing agreements (created and signed) and sharing progress on shared data;&nbsp;</li>



<li>technology / data sharing infrastructure best practice to CaSTco extension funding project</li>
</ul>
</li>



<li>The next CReDO workshops are on hold, pending a further funding decision.</li>



<li>A case study on the Perseus data sharing scheme was presented as an example of how multilateral data-sharing arrangements and governance structures have been implemented elsewhere.</li>



<li>The working group outlined its approach to data-sharing agreements, including developing a decision framework and questionnaire to guide organisations on appropriate sharing mechanisms, categorising data by risk level, and creating a modular template agreement that could be adapted by participating organisations.</li>
</ul>
</li>



<li>It was <strong>discussed</strong> that:
<ul>
<li>There are risks associated with combining datasets and the need for legal and security considerations to be embedded within the framework.</li>



<li>It might be worth convening legal stakeholders together, potentially at the Innovation Festival, to help develop draft agreements and accelerate buy-in across water companies.</li>
</ul>
</li>
</ul>



<p><strong>Next meeting:</strong> Tuesday 7 April 2026 10:00-11:30 BST</p>



<p>Formal records, including attendees, are maintained by the secretariat. </p>



<p>These are confidential to the Advisory Group Members.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Open Energy Steering Group February Meeting Summary</title>
		<link>https://ib1.org/2026/03/04/open-energy-steering-group-february-meeting-summary/</link>
		
		<dc:creator><![CDATA[Janice Holloway]]></dc:creator>
		<pubDate>Wed, 04 Mar 2026 12:56:06 +0000</pubDate>
				<category><![CDATA[Energy]]></category>
		<category><![CDATA[Minutes]]></category>
		<category><![CDATA[Open Energy]]></category>
		<category><![CDATA[Programmes]]></category>
		<category><![CDATA[open energy]]></category>
		<guid isPermaLink="false">https://ib1.org/?p=19491</guid>

					<description><![CDATA[An Open Energy Steering Group was convened on Tuesday 17 February 2026. The Steering Group comprises a wide range of industry [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>An Open Energy <a href="https://ib1.org/open-energy-uk/">Steering Group</a> was convened on Tuesday 17 February 2026. The Steering Group comprises a wide range of industry leaders and subject matter experts spanning the commercial, regulatory and government landscapes. The Steering Group plays a critical role in Open Energy’s development, providing a sector perspective that ensures that Open Energy is designed for and with the energy industry.</p>



<p>Date: Tuesday 17 February 2026 11:00-12:30 GMT</p>



<p>Location: In person &amp; online</p>



<p>Co-Chairs: Sara Vaughan &amp; Gavin Starks</p>



<p>Secretariat: IB1</p>



<p><strong>Meeting Aims</strong> </p>



<ol>
<li>Support for the use case for 2026</li>



<li>Support the governance process</li>



<li>Connect us with new potential members</li>
</ol>



<p><strong>Summary:</strong></p>



<ul>
<li>It was <strong>agreed</strong> that:
<ul>
<li>The 2026 roadmap will move from engagement and prioritisation early in the year to implementation activity later in the year.</li>



<li>Remaining organisations will be asked to complete outstanding terms of reference signatures, where that is possible.</li>
</ul>
</li>



<li>It was <strong>noted</strong> that:
<ul>
<li>An update was given on activities since the last SG, including:
<ul>
<li>Government and Ofgem activity is increasingly focused on ensuring greater visibility of distributed and flexible energy assets.</li>



<li>Elexon has gone live with its flexibility market facilitator role, and the new Flexibility Commissioner has been announced.</li>



<li>NESO and XOSERVE have announced a strategic partnership on consolidation and sharing of gas data which will help facilitate and streamline whole-system planning.</li>



<li>Ofgem published its Forward Workplan for 2026/7.</li>



<li>RECCO published the design consultation on its Consumer Consent solution.</li>



<li>The intended publication of the DESNZ/Ofgem Digitalisation Vision in Q1 2026 was confirmed.</li>
</ul>
</li>
</ul>



<ul>
<li>The Smart Data Council has resumed and is developing UK guidance for smart data schemes.</li>



<li>The Perseus programme has broad participation and commercial offerings are expected from 2026, with a £5-10bn SME opportunity by 2030.</li>



<li>Feedback to the Open Data access controls paper has been positive across the sector.</li>



<li>The 2026 priority use cases will focus on UC04 &#8211; cross-sector storm response or UC05 &#8211; industrial and commercial flexibility.</li>
</ul>
</li>



<li>It was <strong>discussed</strong> that:
<ul>
<li>Practical implementation and real use cases may be more persuasive to policymakers than theoretical proposals.</li>



<li>A Community Interest Company (CIC) based SPV funding model could support multi-year funding and participation from multiple network operators but, given IB1’s non-profit, public benefit status, there was not a strong case to change to such a model.</li>
</ul>
</li>
</ul>



<p><strong>Next meeting:</strong> Thursday 7 May 2026 14:30-16:00 BST</p>



<p>Formal records, including attendees, are maintained by the secretariat. </p>



<p>These are confidential to the Steering Group Members.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
