Wireless condition monitoring

Know which machine fails next — and why

Not a spectrum to interpret — the machine, the component, how urgent, how sure, and enough warning to schedule the fix instead of reacting to it.

No line shutdown to install · On-premise available

Motor and pump with two TrackBeat wireless sensors — each capturing vibration and temperature — mounted on the motor drive end and the pump bearing Motor · Drive end Pump · Bearing
Reliability engineer checking machine health on a tablet beside a row of pumps

Your machines talk.
TrackBeat listens.

  • 320%Return on investment
  • 214 hDowntime avoided
  • $2.4MTotal net benefits

ROI, downtime avoided and net benefits are illustrative figures for a model plant over 3 years, not customer results.

Downtime avoided

46 h

Unplanned downtime avoided on the main line in the first 90 days.

Sap Swiss · Production line · 32 assets · Illustrative figure, pending confirmation

3 senses
Vibration, temperature and shaft speed in one sealed unit
ISO 20816
Severity anchored to published velocity zones, not a private score
11 faults
Fault modes diagnosed by name, with the affected component identified
48 h
Raw waveform buffered on every sensor for forensic pull

Who it’s for

Three jobs. One heartbeat.

The plant manager, the reliability engineer and the maintenance crew all depend on the same machines. Now they all hear them, too.

Sensor online · readings illustrative

Stop guessing which
machine is next.

TrackBeat listens to every monitored asset on every shift. When something changes, it names the fault, grades it, and puts the job in front of the right person.

  • Vibrationmm/s RMS
  • Temperature°C
  • Shaft speedrpm
The business case

What is unplanned downtime costing you?

Your numbers. Your arithmetic. Not someone else's ROI study.

Unplanned failures a year6
Average downtime per failure8 h
Cost of downtime per hourCA$12,000
Share caught early enough to act on60%

That last one is the honest variable. Not every failure gives warning — a seized bearing from a lubrication error can go in hours. Rotating-equipment faults that develop over days are what this platform is for, and you should set that share yourself rather than let us set it for you.

Addressable with early warning
CA$345,600
a year, on your numbers
Unplanned downtime hours48 h
Total cost of unplanned failureCA$576,000
Share you expect to catch early60%
This is arithmetic, not a promise. It multiplies four numbers you supplied and claims nothing about what we will detect on your equipment. The only figure worth trusting is the one measured against your own criteria at day 90 — which is exactly what the pilot is for.
Alarms

Alarms your team can act on.

Graded against ISO 20816, checked against each machine’s own baseline, and closed with a record of the work.

  • Severity and anomaly

    Four ISO 20816 levels, from A Good to D Unacceptable, plus an anomaly alarm when a machine departs from its own baseline.

  • Quiet when stopped

    Severity alarms are held while a machine is stopped, so an idle machine does not raise one.

  • Acknowledge to close

    Acknowledge, assign, comment, log the work done, and export the history to CSV.

How alarms work

Diagnostic coverage

Exactly what we detect — and what we don’t.

Eleven fault modes. Two honest gaps.

  • How detectedVibration — band energy at BPFO + harmonics

    EquipmentMotors, pumps, fans, gearboxes

  • How detectedVibration — BPFI + shaft-rate sidebands

    EquipmentMotors, pumps, fans, gearboxes

  • How detectedVibration — BSF + cage-rate modulation

    EquipmentMotors, pumps, fans, gearboxes

  • How detectedVibration — FTF, sub-synchronous energy

    EquipmentMotors, pumps, fans, gearboxes

  • How detectedVibration — dominant 1× radial, stable phase

    EquipmentAll rotating equipment

  • How detectedVibration — elevated 2× with axial component

    EquipmentCoupled drives

  • How detectedVibration — harmonic series, raised noise floor

    EquipmentAll rotating equipment

TrackBeat sensorVibration · Temperature · Magnetometer
  • How detectedTemperature — absolute trend and rate of change

    EquipmentAll rotating equipment

  • How detectedVibration — broadband high-frequency energy

    EquipmentPumps

  • How detectedVibration — GMF + shaft-rate sidebands

    EquipmentGearboxes

  • How detectedMagnetometer — running state and shaft speed

    EquipmentAll rotating equipment

  • How detectedRequires stray-flux ESA — out of scope for the current magnetometer

    EquipmentMotors

  • How detectedCurrently surfaces as a bearing-mode escalation, not its own class

    EquipmentAll rotating equipment

Detected 11 Not yet 2 Hover or select a fault to see how it is detected and on which equipment.Tap a fault to see how it is detected and on which equipment.

Full technical specifications

Rollout

From purchase order to a diagnosis you trust, in about 90 days.

Week zero to day ninety.

Week 0

Scope one line

We pick a line together, list its assets by criticality, and agree in writing what success looks like — faults caught, at what lead time, at what false-alarm rate.

Week 1

Install

Sensors mount externally on bearing housings; the receiver goes on a wall. No shutdown, no wiring, no controls work. Your technician commissions each sensor in the app.

Weeks 2–4

Learn baseline

The platform observes each asset across its real duty cycle — every shift, load state and changeover — to learn what normal looks like on your floor, not on a test rig.

Weeks 4–8

Diagnose & tune

Insights start firing. Technicians log what they found when they opened the machine, and each label feeds retraining. This is where the false-alarm rate drops.

Weeks 8–12

Review honestly

We measure against the week-zero document: what we caught, how early, what we missed, what we called wrong. That evidence drives the plant-wide rollout decision.

From purchase order to a diagnosis you have personally verified.