Aravolta
Book a demo

Monitoring from the day it lands.
Power on. Scan. Match. Live.

A module can be on site in weeks. The monitoring usually is not. Aravolta ships pre-configured, so the monitoring is live when the module is.

Request DemoRead the Flexnode case study
Live demo
Sample data. Sped up. At onboarding we build the template from your module drawings and equipment list.
MOD-07 / 40 ft module, first power-on
T+00:00
Node logaravolta-node
10.40.0.0/24waiting for link · 0 hosts
  1. 00:00bootpower on, config staged for MOD-07
Module plan
40 FT · 12.2 M8 FTBATBATR01R02R03R04R05R06R07R08POWER ROOMHOT AISLECOLD AISLE048 FTNET-1NODEUPS-AUPS-BMSB-1IRC-1IRC-2IRC-3IRC-4CRAC-1ENV-1GEN-1GENERATOR · OUTSIDE
Devices found
0
Library matches
0
Points mapped
0
Queued
0

Library: 46,000+ make, model, and firmware versions

Template · 40 ft module
Staged
  1. Devices placed37 of 38 on the plan
  2. DashboardsPower, cooling, environment, network
  3. Alert rules52 applied
  4. TwinMOD-07 plan, 37 assets
  5. BaselineRecorded for commissioning
MOD-07 not reporting yet
Sped up

Click a device in the log or on the plan for its matched profile and points. Jump to a step, drag the bar, or replay.

Time to monitoring

2 to 4 weeks, not 6 to 12 months

Traditional DCIM takes 6 to 12 months to implement. Aravolta deploys on a modular site in 2 to 4 weeks, with automatic discovery and pre-built templates.

One year, drawn to scale
  • Shortest
  • Longest
Traditional DCIM
6 to 12 months
Aravolta on a modular site
2 to 4 weeks
Before it ships

Pre-configured for modular sites

Containerized halls repeat the same layouts, so most of the setup is done before the Aravolta node ships.

On the network
Uplink
Outbound only. The node accepts no inbound connections.
Firewall
No inbound ports to open and no rules to change.
Probes
SNMP 161/udpModbus 502/tcpBACnet 47808/udpRedfish 443/tcp
How the node connects
Node configurationPer module type
Discovery
  • The node scans the subnet on power-up and finds every device
  • Network topology mapped automatically
  • Pre-mapped layouts for common module designs
  • Standard deployments configure themselves
Templates
  • Dashboards built for containerized halls
  • Monitoring profiles for common module types
  • Adjustable for a non-standard layout
Integration
  • SNMP, Modbus, and BACnet out of the box
  • Connector kits for common equipment
  • Integrations for Schneider, Vertiv, Huawei, and other module vendors
  • Pre-integrated with common modular BMS platforms
  • Cloud-hosted option for immediate access

The library holds more than 46,000 make, model, and firmware versions. A device we have not seen before is onboarded within 48 hours, at no cost.

Day one

Day-one visibility

What you see the first day, what you need to accept the module, and what carries on as the next ones arrive.

  1. Day one

    Monitoring

    • Power, cooling, and environmental readings from day one
    • IT equipment found and monitored
    • Capacity tracked as workloads land
    • Alerts on critical faults
  2. Acceptance

    Commissioning

    • Check delivered performance against manufacturer specs
    • Verify cooling and power distribution
    • Record the baseline
    • Acceptance test dashboards and reports
  3. Each new module

    Phased rollout

    • Add each module as it arrives
    • One view across all modules
    • Deployment progress against the schedule
    • Faults caught early in the rollout
Scenarios

Deployment scenarios

Three cases where a module has to be monitored from the day it arrives.

  • Emergency and disaster recovery

    • Fast deployment for disaster recovery
    • Configurations staged ahead of time
    • Remote monitoring from day one
    • Quick capacity check and tuning

  • Temporary and seasonal capacity

    • Fast deployment for peak periods
    • Monitoring tied into the existing site
    • A short decommissioning process
    • Cost tracking for the temporary unit

  • Remote sites

    • Fast deployment at remote locations
    • Little technical skill needed on site
    • Monitoring from headquarters
    • Automated maintenance and alerting
Scale

One module or hundreds

One unit or a full campus, same setup.

  • One dashboard for every module
  • The same monitoring across module types
  • Site-wide capacity and utilization
  • Workload balancing across modules
  • One set of operating procedures
MOD-01MOD-02MOD-03MOD-04MOD-05MOD-06MOD-07MOD-08MOD-09MOD-10MOD-11MOD-12MOD-13MOD-14MOD-15MOD-16MOD-17MOD-18MOD-19MOD-20MOD-21MOD-22MOD-23NEXTMOD-24NEXTSITE 14SITE PLANSAMPLE
22 of 24modules reportingMOD-07 is the module from the demo
Case study · Flexnode

Fully operational in weeks, including support for liquid cooled systems.

Read the case study
Modular and edge

More on modular and edge

OverviewThe twin, the template, and the fleet view.Remote monitoringReadings, alerts, and controls from anywhere.BMS integrationCooling and environment inside each module.EPMS integrationThe power chain from intake to rack.Edge computingSmall sites with little or no staff.Scalable infrastructureAdd modules without redoing the monitoring.Portable data centersUnits that move and keep reporting.Customer portalYour brand on your customers' view.

See it on your next module

Send the module vendor and the asset list. We will walk you through day one.

Request Demo