Commercial model
Hardware once. Software per monitored asset. Users are free.
Quoted against your asset list, not your headcount.
We do not charge per seat, because a monitoring platform only works when the whole plant is looking at the same screen. Pricing is quoted against your asset list.
Step one
Pilot
One production line, fixed scope, fixed price, and a written success definition agreed before we start.
- Sensors and one receiver included
- Installation and commissioning support
- 90-day review against agreed criteria
- Credited against a plant rollout
Most plants start here
Plant
A full site under monitoring, with the receiver tier sized to your asset density and layout.
- Annual subscription per monitored asset
- Unlimited users across all four roles
- Full API, streams and CSV access
- Model improvements included, no site visit
Multi-site & regulated
Enterprise
Several plants under one organisation, or a deployment that has to live inside your own perimeter.
- Multi-site tenancy and site-level access
- On-premise deployment option
- Security review and questionnaire support
- Direct support contact
Before you ask
The questions that decide it.
How long before it tells us something useful?
Live readings and running-state data are available from day one. Diagnosis needs a baseline, which takes roughly two to four weeks of real duty cycle. Any vendor promising a trustworthy fault call on day one is showing you a generic model that has never seen your machines.
What about false alarms? We’ve been burned before.
This is the failure mode that kills condition-monitoring programmes. Severity and confidence are separate fields, so a low-confidence call is never dressed up as certainty. Every outcome your technician logs is kept, so alerts get sharper over the first few months rather than staying noisy.
Do we need a reliability engineer on staff to use it?
No. The output is a plain-language diagnosis — failure type, affected component, severity, confidence, recommended action — aimed at a maintenance technician, not a vibration analyst. If you do have an analyst, the full spectrum, fault-frequency overlays and contributing features are there for them to audit every call we make.
Will this replace our CMMS?
No, and it shouldn’t. TrackBeat is the condition-monitoring layer that tells your CMMS which work order deserves to exist. Turnkey connectors are on the roadmap; today the documented API supports that integration, and we will help build it during onboarding.
What about hazardous areas, and battery life?
Tell us your area classification during scoping and we will tell you honestly whether we can serve it today — we would rather lose a zone than sell you hardware that shouldn’t be there. On battery: life is 5–6 years on the battery-powered sensors, and each sensor carries on-board fuel gauging that reports its state of charge to the platform.