Real deployments · evidence labelled

The problem. The intervention. What changed in the building.

Nine completed, active or pilot deployments across offices, retail, logistics, hospitality, gas and water—each separated by evidence status so a live rollout is never presented as a finished result.

Find a Case Like Mine Scope a First Site

Clients remain anonymous unless written permission covers the company name, logo, project detail and any quantified result.

Office tenant

Completed result

Independent readings made the monthly charge defensible.

A tenant in a Sofia office building could not reproduce the electricity allocation behind its monthly bill. A defined circuit-level measurement boundary created an evidence set both sides could inspect.

Before, action, outcome
  • Before: electricity charges moved month to month with no calculation either side could inspect.
  • Action: circuit-level meters on the tenant boundary, reported automatically into Volts.
  • Outcome: the charge was rebuilt from readings both sides could check, and the method agreed for future periods.

Completed result · Client anonymous pending written permission

Read the office billing case

Retail park portfolio

Active deployment

Common-area charges tenants can trace back to readings.

A multi-site retail operator needed one allocation method across parks instead of separate checks and spreadsheet explanations. The deployment connects shared-area consumption to the rule behind each charge.

Before, action, outcome
  • Before: common-area costs were allocated by hand, and tenants had no way to check their share.
  • Action: energy, water, footfall and property workflows are being brought into one portfolio view.
  • Outcome to date: cost and exceptions are compared across locations from the same records. The rollout is still in progress.

Active deployment · Interim results only

See retail-park operations

Logistics campus

Completed deployment

Every major load traced to its system and zone.

A Bulgarian logistics campus needed to separate energy and water use by operational area. The deployment built a measurement map that makes idle load, peak events and zone cost visible.

Before, action, outcome
  • Before: energy and water use across the campus could not be separated by area or shift.
  • Action: metering across the selected zones and utilities, feeding automated reports and anomaly alerts.
  • Outcome: energy and water visibility by area, with anomalies raised as they appear rather than found on the invoice.

Completed deployment · Client anonymous unless written permission is on file

See logistics and warehousing

Regional water network

Rollout in progress

Direct crews to the loss before another meter round.

A regional water operator is moving from manual collection toward remote readings and exception-led investigation. Loss and billing results are not yet measured, so this is reported as rollout progress.

Before, action, outcome
  • Before: readings were collected on foot, so a loss was only found on the next visit.
  • Action: remote metering feeds readings into one operating view, with a customer portal and billing integration behind it.
  • Outcome to date: losses surface between visits instead of after them. The rollout is still in progress.

Rollout in progress · Outcome measurement pending

See water and leak detection

Multi-site logistics

Completed deployment

One weekly exception view across every base.

A logistics operator needed portfolio visibility without rebuilding a report for each site. Meter data is consolidated into one review that shows cost, variance and the sites needing action.

Before, action, outcome
  • Before: each site reported separately, and the portfolio picture was rebuilt by hand every week.
  • Action: multi-site energy metering feeding one automated weekly report.
  • Outcome: the weekly view arrives built, and sites are compared on the same basis.

Completed deployment · Anonymous deployment

See dashboards and reports

Hospitality

Completed deployment

Zone charges built on readings - not last year’s estimate.

A hospitality property needed to connect consumption by zone to budgeting and tenant allocation. The deployment replaced an estimated split with a repeatable reading-to-charge workflow.

Before, action, outcome
  • Before: tenants with very different usage profiles were charged from estimates.
  • Action: single- and three-phase metering with communication modules mapped consumption by tenant and zone.
  • Outcome: allocation and reporting run from readings, and budgeting works from real consumption.

Completed deployment · Anonymous deployment

See tenant billing

Hotel heat-pump plant

Completed deployment

See which unit delivers the heat you are paying for.

A Sofia hotel needed more than one plant total. Unit-level input and thermal output make faults visible earlier and allow comparable COP analysis by mode and period.

Before, action, outcome
  • Before: heat-pump efficiency could not be tracked, so a degrading unit went unnoticed.
  • Action: energy and thermal measurement across the plant, with COP calculated per unit.
  • Outcome: thermal flows and unit efficiency are visible, and deviations can be acted on.

Completed deployment · Client anonymous unless written permission is on file

See hotels and hospitality

Gas distribution

Completed pilot

Reconcile supply and consumption point by point.

A gas distribution operator needed a shared history for supply and consumption points. The pilot tested whether each point could be read, compared and investigated without interrupting operations.

Before, action, outcome
  • Before: supply and consumption could not be balanced without manual collection.
  • Action: remote gas measurement over an NB-Fi network planned for the route.
  • Outcome: supply and consumption can be balanced from remote readings.

Completed pilot · Client anonymous unless written permission is on file

See smart metering

Underground water network

Pilot validated

Prove the signal where ordinary coverage fails.

An underground network pilot tested remote readings in metal shafts with high humidity. Communications and measurement performance were assessed separately, against acceptance criteria agreed before installation.

Before, action, outcome
  • Before: meters sat in metal shafts and humid enclosures where signal did not reliably escape.
  • Action: a radio architecture chosen and tested for exactly those conditions.
  • Outcome: readings came through reliably enough to validate the approach for wider rollout.

Pilot validated · Wider rollout not implied

See Volts hardware

Find the closest proof. Then test it on your site.

Bring the building type, the operational problem and the systems already installed. We will show the most relevant evidence, separate proven results from open assumptions and scope one measurable first site.

Scope a Pilot Find a Case Like Mine