This article, Data, Dialogue and Doing it Properly, is part of a series of technical insights from our in-house expert and Technical Project Consultant, Daniel Davies.
No fluff. No jargon. Just what you need to know to stay compliant, stay in control and keep residents informed.
If you strip heat networks back to their fundamentals, they are actually very simple.
- Generate heat efficiently.
- Distribute it reliably.
- Measure it accurately.
- Bill it fairly.
Yet most of the issues we see across existing residential schemes don’t come from catastrophic plant failure. They come from weaker links further downstream, usually around data visibility, billing transparency and resident confidence.
Franklin House in Grimsby is a strong example of that. The generation side of the scheme, delivered alongside Worcester Bosch, was robust. The plant was professionally specified and installed.
From a mechanical perspective, the backbone of the network was solid. But as is often the case on retrofit and legacy schemes, the data layer hadn’t evolved at the same pace as the plant.
And in 2026, that matters.
Why Data Is the Real Backbone
There’s a misconception in parts of the industry that once the boilers are commissioned and the flow temperatures are stable, the hard work is done. It isn’t.
Without structured, resilient consumption data, a heat network operator is effectively operating with partial sight. You might know what’s leaving the plant room, but you don’t necessarily know how it’s being distributed, consumed or reconciled at dwelling level with confidence. That creates risk.
Risk in billing. Risk in compliance. Risk in resident trust.
At Franklin House, the requirement wasn’t simply “collect meter readings”. It was to design a data collection architecture that was reliable, scalable and capable of supporting a seamless billing environment, without creating unnecessary disruption in an occupied residential building.
That last point is crucial.
The Practical Constraints of Retrofitting
When you look at traditional hard-wired M-Bus systems, they absolutely have their place. In new-build schemes where cable routes are planned from day one, they can be effective and robust But in existing multi-storey residential blocks, retrofitting structured cabling can be invasive, expensive and inflexible.
Running new containment through communal risers, navigating fire-stopping, dealing with legacy infrastructure all while residents are living in the building, introduces complexity very quickly.
You can solve the data problem and create a disruption problem at the same time.
That’s why, at Franklin House, we took a different approach.
Designing the LoRaWAN Infrastructure
We implemented a LoRaWAN data collection protocol across the building.
From a purely technical perspective, this allowed us to create a decentralised, wireless communication layer between the heat meters and a central gateway. Each meter transmits consumption data over long-range, low-power radio frequency, which is then securely aggregated and transferred into the billing environment.
Why LoRaWAN?
Because it offered the right balance between coverage, resilience and practicality for this specific building. The reinforced concrete structure required strong signal penetration. The network needed to operate across multiple floors without reliance on continuous cable routes.
The solution had to be scalable, allowing additional meters or assets to be integrated in the future without ripping infrastructure apart.
LoRaWAN delivered that. Signal testing confirmed reliable coverage throughout the building envelope. Gateway positioning was optimised to minimise blind spots and maximise redundancy.
The architecture reduced single points of failure compared to centralised wired systems. From an engineering standpoint, the result was a stable, resilient data layer underpinning the entire scheme. But technology alone doesn’t define success.
Building a Seamless Billing Platform
Data collection is only valuable if it feeds into something meaningful. Once structured consumption data was being reliably transmitted, it was integrated into the billing platform to create a seamless, transparent charging structure.
Residents would be billed based on actual recorded usage rather than estimates or inferred distribution models. This has several advantages.
Firstly, it improves fairness. Each dwelling is charged based on its own consumption profile.
Secondly, it improves reconciliation. Operators can compare generation figures against aggregated dwelling consumption to identify anomalies, losses or system inefficiencies.
Thirdly, it improves compliance readiness. As regulatory oversight increases across the UK heat network sector, schemes with structured, auditable data are better positioned to adapt.
From my perspective, accurate data is not just about billing. It is about control. When you can see what is happening across your network in near real time, you move from reactive management to proactive optimisation.
The Real Challenge: Perception
Technically, Franklin House progressed exactly as planned. The greater challenge came from something far less tangible: perception.
When residents were informed that billing would be supported by remote data collection, there was understandable hesitation. The phrase “remote monitoring” can trigger concerns around privacy and cost escalation. Without context, it sounds intrusive. And if we are honest, the heat network sector has not always done a good job of explaining itself.
Residents often inherit systems they did not choose. They receive terminology HIUs, primary circuits, standing charges that feels technical and inaccessible.
If communication is limited, uncertainty fills the space. At Franklin House, we made a conscious decision not to let that happen.
The Residents’ Meeting
Rather than commissioning the system quietly and relying on post-installation documentation, we held a structured residents’ meeting.
We explained, in plain language, what a heat meter actually measures: thermal energy consumption in kilowatt-hours. No behavioural tracking. No personal data extraction. No hidden surveillance.
We broke down how tariffs are formed, separating standing charges from variable consumption charges. We clarified how accurate data protects residents from cross-subsidy and estimated billing.
We also addressed the wider context.
Heat networks are becoming more regulated. Transparency is increasing. Structured data is not about increasing costs; it is about ensuring costs are distributed correctly.
The tone of the room changed as the mechanics became clear. Once residents understood that the system ensured they were only paying for what they used nothing more, nothing less… scepticism softened.
This is the part of the project that doesn’t sit on a schematic diagram but arguably matters most.
Collaboration Done Properly
Franklin House worked because roles were aligned. Worcester Bosch ensured that the plant solution was technically robust, efficient and professionally delivered.
Our responsibility was to ensure the data infrastructure supporting that plant was equally resilient and future-ready.
Too often in our industry, plant, metering and billing are treated as separate conversations.
Mechanical engineers focus on generation. Metering contractors focus on devices. Billing providers focus on statements.
But residents don’t see those silos.
They see one system.
At Franklin House, generation and data were treated as two parts of the same ecosystem. That alignment is what allowed the scheme to move from “operational” to “optimised”.
Lessons from Franklin House
There are a few clear takeaways from this project.
Firstly, data architecture should be considered as seriously as plant specification. If you design generation without designing visibility, you are embedding risk from day one.
Secondly, wireless protocols such as LoRaWAN are not shortcuts. When designed correctly, they can provide resilient, scalable infrastructure particularly suited to retrofit environments.
Thirdly, resident engagement is not optional. You can install the most advanced metering system available, but if residents do not understand it, confidence will always lag behind capability.
And finally, collaboration across disciplines matters.
Manufacturers, data specialists and billing providers need to operate as a coordinated unit rather than isolated contractors.
Final Thoughts
Franklin House in Grimsby is not just a story about installing a LoRaWAN network. It is a case study in aligning engineering, data and communication.
Reliable generation provided the foundation. Structured data collection provided visibility. Clear engagement provided trust.
When those three elements come together, heat networks stop feeling complex or opaque. They start feeling controlled and fair.
As the regulatory landscape tightens and scrutiny increases across the sector, schemes that prioritise accurate data and transparent communication will be the ones that stand up to inspection, both technically and socially.
Franklin House reinforced something I have said many times: Heat networks are not inherently problematic. Poor visibility and poor communication are.
Fix those, and the rest becomes manageable.
Got a Heat Network Challenge? Ask Daniel.
Stay up-to-date
If you found this useful, we’re just getting started.
Subscribe for future insights from our Technical Project Consultant, Daniel Davies – tackling the real-world challenges of compliance, performance and fair billing.