Motors & vibration
See motor changes before the next inspection round.
External vibration and temperature sensors on bearing housings and frames, a current clamp at the supply, and a hub that sends readings to the cloud platform. Changes show against the motor's own history.
- 1Drive-end bearingRising · review
- 2Frame tempWithin normal
- 3MaintenanceChange flagged · review
Motors change in ways you cannot see on a walk-round.
Bearing changes between inspections
A bearing housing that is vibrating or running warmer than its own recent range is worth a look before the next scheduled round.
Load that creeps
Current patterns can show a motor working differently than it used to, before anything is audible.
Knowledge that walks out at shift change
Recording what was found and what was done keeps the history with the motor.
Start with a small pilot
A few drives that matter most first; expand once the value is clear.
How it works
Three steps: pilot, review, expand.
Mount external sensors
Vibration on the bearing housing, temperature on the frame, clear of rotating and hot parts.
Connect the hub
Each hub: 8 sensor leads of any mix + 3 CT clamps for three-phase current + internal sensors. CT clamps go on the supply, fitted by qualified personnel.
Review trends
Against the motor's own history, with notifications for configured conditions.
What you get
An asset that knows itself — and a team that hears about it first.
Readings, trends and history your team can review; a notice when something needs a look; one record per machine.
Vibration trends
Changes in how the motor runs, compared with its own recent range.
Surface temperature
Bearing and frame temperatures across operating conditions.
Current and runtime
Operating pattern and load changes where the installation supports them.
What this is worth to you
Run efficiently. Plan the work. Stop paying for surprises.
The value is the stop that did not happen, the part that was not replaced for nothing, and the energy that stopped leaking. The full story — hub, platform, installation and the pilot plan — is on the IoT Octopus page.
Start with a small pilot
A few critical assets, installed by our team, reviewed with yours. When the value is clear: the first site, then the rest.
Start a pilotBuilt for industrial reliability
Proprietary hardware and software, developed in Kitchener, Ontario.
Built on Google Cloud with per-customer data isolation. In commercial industrial use. Invented, designed and made in Canada.
Applications and resultsExternal sensors
Vibration and temperature sensors mount on accessible surfaces; current clamps need electrical access by qualified personnel.
Review together
Readings, trends and notifications reviewed with your team on an agreed cadence.
Questions
Answered plainly.
Which motors are suitable?
Motors with accessible bearing housings and frames, from older units with no instrumentation to modern drives. Suitability, sensor access and electrical access are confirmed per application.
How do we start?
With a small pilot on a few critical assets. We agree the configuration, review the readings with your team on an agreed cadence, and expand to the next assets and sites once the value is clear.
How is our data secured, and where is it stored?
Equipment data is encrypted in transit and at rest with per-customer isolation, on a platform built on Google Cloud using the most modern data-security protocols. Data residency is agreed with each customer. See the security page.
Does it predict when a failure will happen?
No. Monitoring helps people review changes over time against the asset's own history. A trend may support investigation; it does not establish a diagnosis or guarantee when a failure will occur.
Next step
Book a motor demo.
Tell us the equipment and the question. We reply within one business day to find a time for a 20-minute demo on your kind of assets.
Prefer the full form? Go to Contact. Existing customer? Customer Login.