The Bilateral Hub shouldn't have to feel like another system

At Cloudwater, we've started development of a new Bilateral Hub module for Edge, designed to integrate bilateral processes directly into the retailer's normal operational workflow.

The objective is straightforward: when somebody needs to raise a bilateral request, Edge already knows the customer, SPID, premises, meter and relevant market data. Why make the user leave the system and find it all again?

Our aim is to connect Edge directly with the Bilateral Hub so requests, responses, status changes and audit history become part of the same operational picture.

Retailer → Edge → Bilateral Hub → Wholesaler

It's the same philosophy we've applied to HVI integration: market processes work best when they're embedded into the platform people already use.

Bob explores the wider thinking behind this in this week's Edge Insights: “The Bilateral Hub: Why Integration Matters.”

The best integration may be the one nobody notices.