Q1. What is Dynamic Load Harmonisation (DLH)?
DLH is a cloud-hosted optimisation layer that sits on top of your existing refrigeration and cooling controls. It continuously monitors how your plant is running — compressors, fans, evaporators, expansion valves — and fine-tunes the control parameters in real time so you deliver the same cooling with less electricity and less mechanical stress. It does not replace your equipment or your existing controls; it works with them. Sites typically see cooling energy reductions of 13–40%, along with improved diagnostics, longer asset life and lower maintenance costs, all without any capital expenditure on new hardware.
Q2. How is DLH different from voltage optimisation?
Voltage optimisation installs a device on the incoming mains supply that reduces and stabilises site voltage. It is passive: it responds to whatever voltage the grid delivers and applies a static correction. It does not monitor individual assets, detect anomalies or adapt to changes in how your cooling plant behaves. If a compressor is short-cycling, a door seal is failing or a refrigerant charge is dropping, voltage optimisation will not see it.
DLH is proactive and asset-level. It analyses the real-time behaviour of each cooling unit, learns normal operating patterns, and intervenes when a setpoint or variable drifts — adjusting setpoints, flagging emerging faults, and pointing engineers to the likely cause before a failure occurs. The savings come from genuinely smarter operation, not a passive voltage reduction.
Q3. Does DLH require new hardware, sensors or sub-meters?
No. DLH works with operational data that already exists in your refrigeration / HVAC control system — compressor duty cycles, setpoints, temperatures, run times and manufacturer performance data. It does not need new meters, sensors, probes or on-site hardware installations. Deployment is handled remotely, with secure access to existing controllers. This is why it can be implemented without capital expenditure and without disrupting trading operations.
Q4. How are energy savings measured and verified?
DLH uses a standards-aligned Measurement and Verification (M&V) methodology. It builds a statistical digital twin of each cooling system — a model of how the plant would behave without DLH — using existing operational data and physics-informed performance curves. It then compares that expected operation with actual operation under DLH, and converts the difference into verified energy savings. This approach does not rely on monthly utility bill comparisons, which are slow and imprecise. Savings are visible in near real time, with a full audit trail that supports ESG reporting, Green Plans and net zero commitments.
Q5. How long does implementation take and will it disrupt operations?
Implementation is carried out remotely using secure access to existing site controllers. There is no on-site installation, no new cabling and no disruption to trading or operations. From connection to live optimisation, deployment is typically completed in weeks rather than months. DLH is designed to be operational without requiring estates teams, engineers or facilities staff to change what they do.
Q6. What energy savings can we realistically expect?
Across deployments, sites typically see cooling energy reductions of between 13% and 40%. The range depends on plant age, configuration and how the system has been set up historically — older plant running on conservative fixed setpoints tends to show the largest improvements. DLH does not project savings speculatively; it produces a verified saving figure continuously once live, so performance is transparent from day one. We can provide a desktop assessment based on your energy bills and site list before any commitment is made.
Q7. How does DLH protect stock and service, not just energy?
Most refrigeration failures do not arrive without warning — they drift. Temperatures creep up, compressors begin short-cycling, superheat patterns change. Traditional monitoring waits for an alarm to fire, by which point damage may already have occurred. DLH detects these deviations hours before a threshold is breached, allowing issues to be addressed remotely or flagging them for a targeted engineer visit before stock is at risk or service is affected. For multi-site operators, this early warning extends across the whole estate — so problems at individual sites become visible centrally, not just locally.
Q8. What is Estate Management and how does it work across multiple sites?
Estate Management is DLH's live dashboard view of every cooling asset across every site in an operator's portfolio. Instead of waiting for individual sites to report problems, estate managers see a continuously updated picture of how every cabinet, pack, chiller or cellar cooler is performing — with alerts flagged for assets showing early signs of stress. When attendance is required, engineers are sent with the likely fault and likely part already identified, reducing diagnostic visits and repeat call-outs. Evidence across deployments points to 15–30% reductions in maintenance costs and up to 20% extension of critical asset life through reduced cycling and mechanical wear. Beyond visibility, the application operates as a full management system — spanning monitoring, work order triggers, preventative maintenance scheduling and ongoing optimisation.
Q9. Which sectors does DLH work in?
DLH is deployed in any environment where refrigeration and cooling is a significant operational cost and risk. Current sectors include food retail and supermarkets, pubs, bars and hospitality, data centres, hospitals and NHS Trusts, hotels, cold stores, and food manufacturing. The underlying technology is the same across sectors; the optimisation strategies and early warning thresholds are configured to the specific plant type and operational requirements of each environment. In practice, if there is a system controller on site, DLH can be deployed.
Q10. How is DLH funded — what does it actually cost?
DLH operates on a no-capex model. There is no hardware to purchase and no upfront investment. There is an implementation fee, which is determined in advance based on the estate and agreed before rollout. The ongoing service is then funded from the verified savings it generates — energy savings, reduced maintenance spend and avoided emergency call-outs. This means the business case is effectively self-funding, with ongoing costs coming out of savings rather than new capital or operational budgets. For organisations with capital constraints or approval processes that make new investment difficult, this is a significant practical advantage.