Every system. Every site.
One command center.
Generators, chillers, switchgear, UPS, and the cooling plant, monitored and controlled from one screen. The Aravolta node can act as your PLC or DDC, running control logic on site without depending on the network, or sit above the controllers you keep and handle the high-level communication.
“Quick and efficient to bring online... unified building, electrical, and network management... flexible and customizable.”
All points nominal. No active events.
Where SCADA sits
SCADA is the supervisory layer. It reads the BMS, EPMS, fire, security, and generator controllers and puts them in one operator interface. Every mechanical, electrical, and environmental system on site: read it, alarm on it, and write to it without switching tools.
HMI in the browser
Floor plans and system schematics with live values overlaid, from any browser. Build views by drag and drop or start from a template. There is no SCADA workstation to maintain and no VPN to set up.
Alarms across systems
One rule can span systems: 'UPS load above 80% and chiller output falling' is a single condition. Cooldown and dedup logic stop alarm storms. Alarms route to Slack, email, SMS, or PagerDuty.
Control and write-back
Start and stop generators, write cooling setpoints, switch power paths, open and close breakers. Roles decide who can write to what. Every control action goes in the audit log with the time, the value written, the user, and its status.
Historian and trends
Every point is stored at the resolution you set. Overlay trends from different systems on one chart, cooling output against power draw against server load. Export the history for audits.
Cooling, HVAC, environmental, fire
Power distribution, metering, UPS
Sensors, PLCs, RTUs, meters, IoT endpoints, CT clamps, analog inputs
Keep your PLCs and DDCs, and Aravolta sends them supervisory setpoints and runs the cross-asset logic a single controller cannot see. Or let the Aravolta node be the controller: it runs the sequences on site with its own I/O, without depending on the network.
Alarms that mean something
A humidity sensor drifting 2% is not a UPS on battery. Severity, cooldown, and routing are set per rule. Alarms correlate across systems, so the operator sees the cause instead of the noise.
Cooldown logic keeps one chiller failure from turning into 500 alerts. A single rule can span several assets and zones. The NOC gets the root cause instead of a page for every symptom.
Modify the alert rule configuration.
Alert Summary
Triggers when:
Output Load on UPS-A is at least 80 %
Capacity on CH-2 falls below 40 %
Fires only after condition holds for 5 minutes
Checked every minute · 15 minutes cooldown
Sample data. One rule across a UPS and a chiller.
Write-back with an audit trail
Most DCIM tools are read-only. Aravolta SCADA writes to the plant: start a generator, change a cooling setpoint, switch a power path, open or close a breaker, from the browser.
Roles decide who can write what. Facility ops can move setpoints while generator control stays with the people you name. Every write is logged with the time, the device, the value written, the user, and its status. Where your PLCs stay in place, they keep their interlocks and staging.
Issue commands to devices and review recent activity for this datacenter.
| Time | Device | Control | Value | By | Status |
|---|---|---|---|---|---|
| less than a minute ago | CH-2 chiller controller | CHW Supply Setpoint | 6.50 °C | l.park@example.com | processing |
| 6 minutes ago | CT-2 fan VFD | Fan Speed Limit | 90.00% | Automation | completed |
| 42 minutes ago | GEN-1 controller | Test Run | Start | d.okafor@example.com | completed |
| about 1 hour ago | ATS-2 | Preferred Source | Utility 2 | d.okafor@example.com | completed |
| about 2 hours ago | AHU-3 controller | Supply Air Setpoint | 19.00 °C | m.chen@example.com | completed |
| about 3 hours ago | SWGR-2 BKR-4 | Breaker Command | Close | d.okafor@example.com | completed |
Sample data. Each write keeps the device, the control, the value, who sent it, and whether it landed.
Live in about two weeks
A traditional SCADA deployment means proprietary hardware, a specialist integrator, and months of point mapping. Aravolta does it with one node, discovery, and about two weeks.
Node · in your facilityDrivers for Modbus TCP/RTU, BACnet IP/MS-TP, OPC-UA, MQTT, SNMP, and REST APIs, the protocols already on your plant network. Custom drivers available. For equipment that is not on the network, the node takes CT clamps, RS-485 and RS-232 serial, Form C dry contacts, and 4-20mA / 0-10V analog inputs.
- 01
Install the node
One node per site, on the management network. It reaches your BMS, EPMS, and field devices over BACnet, Modbus, OPC-UA, and SNMP, so there is no rack-by-rack wiring.
- 02
Auto-discovery
The node scans the subnet and imports every device it finds: generators, chillers, switchgear, meters, sensors. Each one is matched against 46,000+ device profiles and gets its point map applied. You send credentials. We do the rest.
- 03
Live in ~2 weeks
Dashboards, alarms, control sequences, and the historian are configured, and operators are on it. Equipment added later is picked up by discovery, or onboarded within 48 hours if it is a device type we have not seen.
SCADA for data centers: common questions
For how SCADA relates to the rest of the stack, read BMS vs EPMS vs SCADA vs DCIM, or see how Aravolta covers BMS and EPMS on the same platform.
- What is SCADA in a data center?
- SCADA (Supervisory Control and Data Acquisition) is the supervisory layer above the plant controllers. It polls the field equipment and controllers (generators, chillers, switchgear, UPS, cooling plant) and gives operators one interface to watch conditions, work alarms, look back through history, and send control commands.
- What is the difference between SCADA and a BMS?
- A BMS is a packaged building automation product scoped to cooling, air handling, fire, and security. SCADA is the more general supervisory layer built on field controllers, and in data centers it has usually covered the electrical and mechanical plant. Many facilities run both. Aravolta puts SCADA-style supervision, BMS, EPMS, and DCIM on one platform.
- Does Aravolta SCADA replace my PLCs and DDCs?
- It can, or it can run alongside them. The Aravolta node can be the PLC or DDC itself: it runs your programmed control logic on site through its own I/O, so control does not depend on the network. Or keep the PLCs and DDCs you have, and Aravolta handles the high-level communication above them: it reads every point, writes supervisory setpoints with an audit trail, and runs the cross-asset logic a single controller cannot see, such as a cooling setpoint that depends on rack power and outside air together.
- Can I control equipment remotely with Aravolta SCADA?
- Yes. Operators start and stop generators, write cooling setpoints, switch power paths, and open or close breakers from a browser. Role-based access gates every write, and each one is logged with the time, the device, the value written, the user, and its status.
- What protocols does Aravolta SCADA support?
- Modbus TCP and RTU, BACnet IP and MS/TP, OPC-UA, MQTT, SNMP, and REST APIs. Custom drivers are available. For equipment that is not on the network, the node accepts CT clamps, RS-485 and RS-232 serial, Form C dry contacts, and 4-20mA / 0-10V analog inputs.
- How long does a SCADA deployment take?
- About two weeks for a typical facility. One node goes in per site, discovery matches what it finds against 46,000+ device profiles, and we configure the dashboards, alarms, and historian. A device type we have not seen before is onboarded within 48 hours at no cost.
- Do I need dedicated SCADA workstations or per-point licenses?
- No. Aravolta SCADA runs in the browser, so any browser is a workstation. Pricing is per asset, not per point, so every metric your equipment reports is included.
See it on your plant
Every controller on site, monitored and controlled from one screen. No proprietary hardware and no specialist integrator.
- One-second data refresh
- Vendor-agnostic
- Live in ~2 weeks