What your team opens every morning.
The fleet, the machine, the alarm. In that order.
Live screens. Plant name changed. Numbers unchanged.
- Site and area rollup
Six locations, 42 areas and 100 machines on one map. Each site card shows its worst state.
- Alarm, warning, advisory
Fleet-wide counts by severity, so the day starts with the sites that need attention.
- Sensors online
96 of 100 sensors reporting. Stale and offline sensors are counted and filterable.
- ISO 20816 zones
Velocity RMS is plotted against the ISO 20816-3 A to D bands for that machine class.
- Anomaly score
Mahalanobis d² measures distance from learned normal, shown against its χ² threshold.
- Baseline learning
The baseline locks after enough readings. Health then blends ISO severity with the anomaly score.
- Filter what matters
Warn or alarm, ISO or anomaly, by asset, site, owner and time window.
- Alarm ACK
Acknowledge from the inbox. Open and acknowledged alarms stay in separate lists.
- CSV export
Export the filtered list for a shift report or your CMMS.
Three screens, read in order.
Each screen answers one question and hands you to the next. Nobody starts the day by reading a spectrum.
- 01 · FleetWhich site needs me?
Every site, area, and machine is on one map, and each site card shows its worst state. The fleet-wide counts of alarms, warnings, and advisories tell you where to look first. Sensors that have gone stale or offline are counted too, so a quiet machine is not mistaken for a healthy one.
- 02 · AssetWhat is wrong with this machine?
The machine opens on its health, its ISO zone, and the axis that is worst. Behind that sit the trends: velocity on the ISO bands, the anomaly score against the learned baseline, temperature, and kurtosis. The spectrum is marked against the bearing frequencies for the engineer who wants the evidence.
- 03 · AlertsWho is dealing with it?
Warnings and alarms land in one inbox. Filter by severity, source, asset, site, owner, and time window, then acknowledge from the row. Open and acknowledged alarms stay in separate lists, and the filtered list exports to CSV for the shift report or your CMMS.
How the platform decides.
The numbers on screen are not a private score. Each one traces back to a published standard or to what your own machines have done before.
- Severity on a published standard
- Velocity RMS is plotted against the ISO 20816-3 zones, A to D, for that machine class.
- A baseline learned on your floor
- The platform watches each asset across its real duty cycle, every shift and load state. The baseline locks after enough readings, and the anomaly score measures distance from it.
- One health figure
- Health blends the ISO severity with the anomaly score, so a machine that is inside its zone but drifting still shows up.
- The same screen for everyone
- Users are free and unlimited across all four roles, because monitoring only works when the whole plant is looking at the same screen.
- Your data stays yours to use
- REST API, live WebSocket streams, and CSV export. It is the same API the app itself uses.
- Cloud or on-premise
- The platform runs in the cloud, or inside your own network on the Enterprise plan.