Standardise control across every building - without replacing every BMS.
Connect existing BMS and SCADA, add portfolio-level schedules and controlled actions, and make ownership explicit before two systems try to command the same point.
Please enter a valid email address.
No rip-and-replace
Keep local control. Gain one portfolio operating model.
Let each BMS continue doing what it does well on site. Volts connects supported systems above it, standardises the portfolio view and fills only the missing measurement and control gaps.
- Connect through the interfaces the building already exposes - BMS, Modbus or API.
- Present mixed BMS brands and retrofit controls through one role-based workflow.
- Define whether each point is monitored, advised or directly controlled.
- Assign one authoritative owner to every writable point to prevent fighting loops.
Schedules & actions
Make the building follow the operating plan.
Apply approved schedules and triggers by site, zone and season. When conditions drift, Volts connects the exception to the right action without hiding who authorised the change.
- Align lighting, HVAC and selected plant with actual operating periods.
- Trigger tasks, approvals or commands from supported sensor and tariff conditions.
- Check safety limits and point ownership before every writable action.
- Record the previous state, new state, reason, approver and timestamp.
Know what connects before the project is priced.
The site survey maps every BMS, controller, gateway, meter and writable point. The resulting integration matrix states what Volts can read, what it can command and what must remain local.
What this means in practice
- Existing system and protocol inventory.
- Read-only, advisory and write-enabled point classification.
- Safety interlocks, fallback state and manual-override responsibility.
FAQ
Building automation without hidden control assumptions
Does Volts replace our BMS?
No. A supported BMS remains the local control system. Volts adds portfolio context, cross-site workflows and financial evidence above it, while missing points can be retrofitted selectively.
What can Volts actually control?
Writable points are confirmed per site during scoping, and each one states whether it is read-only, advisory or write-enabled.
Which industrial protocols are supported?
Volts connects through the interfaces a site already exposes, BMS, Modbus and API among them. Compatibility still depends on the device map, gateway and exposed points at each site.
How do you prevent an unsafe command?
Writable actions run through permissions, approvals and interlocks. Native equipment protections remain authoritative.
What if we need a workflow the BMS does not provide?
Volts can configure supported schedules, triggers, tasks, approvals and cross-site reports without altering the BMS logic itself.
What happens if Volts or the network goes offline?
Local systems keep running on their own logic. Behaviour on loss of connection is confirmed per controller at commissioning.
Can two systems command the same point?
Not safely. One authoritative owner is assigned to every writable point, and where shared control is unavoidable the priority, interlocks and safe fallback are documented before commissioning.
How is a control change audited?
Each supported action records the point, previous state, new state, trigger, approver and execution result.
Map every control point before replacing anything.
Bring the BMS list, a schematic and one workflow that is too slow or costly today. We will show what Volts can read, what it can control and where ownership must stay local.