Stop heating and lighting space nobody is using.
Turn schedules, occupancy, thresholds and approved recommendations into controlled actions - with safety limits, one owner per point and a local manual override.
Please enter a valid email address.
Relays & schedules
Make every controlled circuit follow the operating plan.
Remote switching is useful; predictable operation is the outcome. Set approved schedules by circuit, zone and season, then keep every manual or scheduled change visible across the portfolio.
- Control only circuits and points confirmed in the site integration matrix.
- Apply schedules by approved operating hours, season and building use.
- Record the point, previous state, new state, user or rule and timestamp.
Alarms that act
Give every threshold a defined, reversible response.
Decide in advance whether a condition should notify, create a task, request approval or trigger a safe command. The same rule states the limits, owner, fallback and evidence required afterward.
- Separate notification, advisory, approval-required and automatic modes.
- Check interlocks before a command leaves the platform.
Beyond rules
Let agents propose the pattern. Let people grant the action.
Agents can identify repeated after-hours load or a peak forming across several circuits. They prepare the evidence and next step; execution remains inside the permission and approval boundary chosen for that site.
- Detect patterns that a single fixed threshold would miss.
- Show the readings, cost signal and proposed schedule or task.
- Roll out a proven rule only after site-specific review and approval.
Keep one owner for every writable point.
Volts works alongside supported BMS, controllers and relays. Before write access is enabled, the deployment assigns point ownership, native protection, fallback state and local override.
What this means in practice
- Supported controllers and protocols are confirmed per site during scoping.
- Every control point states whether it is read-only, advisory or write-enabled.
FAQ
Smart control with the safe state defined
Does this replace our building-management system?
No. Volts can work above supported existing systems and add selected retrofit controls where none exist. The integration matrix defines which system owns each writable point.
Could something switch off by accident?
Any control system carries risk. Volts uses permissions, approvals and interlocks, while native equipment protections and local overrides remain in force.
What can Volts actually switch or adjust?
Circuits, relays, setpoints and the commands your controller exposes. Availability depends on the controller, wiring and site safety design.
Does this work across a portfolio?
Yes. Approved schedules and rule templates can be managed across sites, but each rollout should preserve the local operating hours, equipment limits, owner and commissioning check.
Do we have to automate anything?
No. A site can remain monitoring-only, use manual remote control, run schedules, require approval or allow selected automatic actions.
What happens when the network connection fails?
Behaviour on loss of connection is confirmed per controller at commissioning.
Can someone override Volts locally?
A local override stays in force. The system records the resulting state rather than fighting the authorised local command.
How do we prove a control action produced the saving?
Connect the command and time window to the relevant meter data, then compare performance before and after.
Choose one controllable waste. Define the safe response.
Bring the circuit, schedule or threshold causing cost today. We will map the controlling system, owner, limits, fallback and evidence required before any command is enabled.