Volts Deployment | From Site Survey to Proven Pilot

From one building problem to a measurable first result.

We map what is installed, agree the data and control boundary, connect or retrofit the gaps, and commission the workflows your team will use—before you decide on a portfolio rollout.

1. Define the outcome and map the estate

Start with the cost, billing, response or reporting problem. The survey then records meters, panels, BMS, SCADA, network access, ownership and gaps across the first site.

You receive: an asset list, a connection map, the exclusions and dependencies we found, and a scoped quote.

2. Agree the boundary and commission the workflow

Define what Volts may read, what it may control, who approves sensitive actions and how failures are handled. Connect serviceable assets, retrofit missing signals, then configure sites, tariffs, roles and workflows.

You receive: a tested connection map, permissions model, configured workflows and a commissioning record.

3. Measure the first site and decide whether to scale

Train the team on its own building, operate for the agreed measurement period and compare the result against the approved baseline. Roll out only when data quality, workflow adoption and value meet the acceptance criteria.

You receive: the measured result, the open risks, the ongoing scope and a rollout recommendation based on your own data.

Prove the operating model before multiplying it.

The first site should answer the expensive questions once: whether the data is reliable, whether the team will use the workflow and whether the measured outcome justifies the next building.

Data gate: agreed meters and systems report with the required completeness, units, timestamps and quality.

Workflow gate: alerts, approvals, billing or reporting steps reach the named users and close with a traceable record.

Value gate: the agreed outcome is measured over the period set at scoping, against the baseline agreed with it.

Start with One Site

Eight deployment questions answered before the survey.

How long until we see the first data?

A representative connection can be tested after access and compatible equipment are confirmed. Full commissioning is a separate milestone.

How long until the first site is fully commissioned?

It depends on access, documentation, protocol availability, retrofit work, network approval and acceptance testing.

How much time do our IT and facilities teams need?

They provide site access, system contacts, network and security decisions, tariff or allocation rules, and acceptance sign-off.

What if a meter cannot be read?

We test whether a reader, gateway or supported interface can expose the signal. If not, the proposal identifies the replacement or new meter as a separate option, with the reason and cost.

Will installation disrupt the building?

Any shutdown, panel access, permit or out-of-hours work is identified in the method statement before installation.

What happens to our existing BMS or SCADA?

It remains the building system where it is fit for purpose. We agree read and write ownership point by point, integrate supported data and avoid parallel control without an approved authority model.

What if the vendor will not open the system?

We document the blocked interface, test safe alternatives and price any gateway or independent sensing required. We do not promise access to a closed system before the vendor and rights position are confirmed.

What do we receive at handover?

The final pack contains the connection map, the commissioned points, the permissions model, the acceptance results and your support contacts.

From one building problem to a measurable first result.

Three phases. A decision at each gate.

Prove the operating model before multiplying it.

Eight deployment questions answered before the survey.

Scope the first site. Know every dependency up front.