.png)
Monnit Condition Monitoring for Rotating Equipment: Early Warning Alerts for Motors and Pumps
A motor rarely fails without warning. The warning may be a new vibration pattern, a bearing that runs hotter than usual, a pump that cycles too often, or a compressor drawing more current than it did last week. The hard part is catching those changes before they become downtime.
That is where Monnit condition monitoring fits well. By combining multiple wireless sensing technologies with centralised alarms in iMonnit, maintenance teams can watch motors, fans, compressors and pumps without relying only on manual rounds. Instead of waiting for a scheduled inspection, the system raises attention when the equipment starts behaving outside its normal range.
Rotating equipment needs more than one warning sign
Motors and pumps fail for many reasons. Bearings wear. Shafts fall out of alignment. Belts loosen. Filters block. Loads change. Moisture enters enclosures. Cooling airflow drops. A single measurement can help, but it will not tell the whole story.
A high motor temperature might point to a failing bearing, poor ventilation, overload, or a hot plant room. Higher current may suggest extra load, but it could also come from a pump working against a restriction. Vibration may show imbalance or misalignment, but it becomes far more useful when compared with runtime and temperature.
A stronger early-warning system uses several signals together. Monnit sensors can monitor the machine, the power feeding it, and the space around it. iMonnit then brings those readings into one place, where thresholds, notifications and history make the data useful.
For rotating equipment, the main monitoring layers are:
Monitoring layer | What it can reveal | Useful for |
Vibration | Imbalance, misalignment, looseness, bearing wear, abnormal movement | Motors, fans, pumps, compressors |
Temperature | Overheating, friction, cooling problems, rising bearing or casing heat | Motors, bearings, pump housings |
Electrical current | Load changes, abnormal draw, motor running status, short cycling | Pumps, compressors, blowers |
Runtime | Excessive operation, unexpected starts, duty cycle changes | Standby pumps, exhaust fans, compressors |
Environmental conditions | Heat, humidity, water leaks, ambient conditions affecting equipment | Plant rooms, pump stations, mechanical spaces |
Each layer supports the others. That matters because many failures show up as a pattern, not as one perfect alarm.
Vibration monitoring catches mechanical change early
Vibration is one of the most direct ways to monitor rotating equipment. When a motor, fan, compressor or pump is healthy, its vibration tends to stay within a known range. As components loosen, wear or fall out of balance, that pattern changes.
A Monnit vibration sensor mounted to the right part of the machine can help detect movement that sits outside the expected baseline. That does not replace detailed vibration analysis by a specialist, but it does give maintenance teams a practical way to know when a machine deserves attention.
Common vibration-related issues include:
Imbalance
A fan wheel, impeller or rotating assembly may vibrate more as debris builds up or parts wear unevenly.
Misalignment
A motor and pump coupling that shifts can create extra vibration and heat.
Looseness
Soft mounts, loose fasteners or weakened supports can let equipment move more than it should.
Bearing degradation
Bearings may produce rising vibration as surfaces wear and friction increases.
The value comes from trend and timing. If vibration rises steadily over several shifts, it suggests a developing fault. If it jumps suddenly, it may point to a new mechanical event, such as a loosened mount, impact, blockage or coupling issue.
Temperature monitoring shows stress, friction and cooling problems
Temperature is simple to understand, but powerful when used well. A motor that has always run warm may not be a problem. A motor that runs 10 °C hotter than its own normal pattern deserves attention.
Monnit temperature sensing can support condition monitoring in several ways. Sensors can track ambient temperature inside a plant room, temperature near a motor casing, or temperature around equipment that depends on airflow. The goal is not only to catch extreme heat. It is to see when heat starts trending away from normal.
Temperature alerts are useful when:
A pump bearing area warms while vibration also rises
A compressor room becomes hotter during summer operation
A motor enclosure runs hotter after a change in production load
Ventilation fans fail to keep a mechanical area within its normal range
A previously stable machine begins heating faster after startup
Temperature data also helps reduce false assumptions. If several motors run hot on the same day, the issue may be ambient room temperature or cooling, rather than individual motor faults. If one asset runs hot while nearby equipment stays stable, the cause is more likely local.
Electrical current reveals load and operating state
Current monitoring adds another view of machine behaviour. For many motors, current draw provides a useful signal for load, start events and run status.
A current sensor can help show whether a motor is running, how often it starts, and whether its electrical load has shifted. This is especially useful for assets where direct observation is difficult, such as remote pump stations, rooftop fans, packaged compressors or equipment inside restricted areas.
Electrical current monitoring can help detect:
Pumps running longer than expected
Compressors short cycling
Motors drawing more current under the same process conditions
Standby equipment starting unexpectedly
Fans running outside scheduled hours
Equipment failing to start when called
Current is also valuable because it links mechanical condition to actual operation. A vibration alert means more when the system also knows the motor was running at the time. A temperature rise means something different if the equipment was off, recently started, or under heavy duty.
This is where centralised data becomes useful. Instead of looking at current, vibration and temperature as isolated readings, iMonnit can help present them as part of the same asset story.
Runtime makes hidden duty cycle problems visible
Runtime is often overlooked until a failure prompts the question, “How long has that been running like that?”
For rotating equipment, runtime gives context. Two identical pumps may have very different wear profiles if one carries most of the duty and the other rarely runs. A fan may appear healthy, but if it starts running continuously because a controller has failed, it can wear faster than planned. A compressor may be operating, but excessive cycling may point to leaks, storage pressure issues or control problems.
Runtime monitoring helps answer practical questions:
Did the asset start when it should have?
Did it stop when expected?
How many hours has it accumulated since last service?
Is duty shared fairly between lead and lag equipment?
Has the operating pattern changed?
For maintenance planning, this can be more useful than calendar-based service alone. A pump with heavy runtime may need attention sooner. A standby motor with little runtime may still need testing, but not the same wear-based service as a hard-working duty unit.
Runtime alerts can also reduce site visits. If a remote exhaust fan is confirmed running through sensor data, a manual check may not be needed that day. If it fails to run during its expected window, the system can raise an alarm.
Environmental monitoring explains what the machine is living in
Rotating equipment does not operate in isolation. Plant rooms get hot. Pump pits become damp. Enclosures can collect condensation. Water leaks can reach electrical areas. Dust and poor ventilation can contribute to overheating.
Environmental Monnit sensors can monitor the space around the asset, adding context that machine-mounted sensors cannot provide by themselves.
Useful environmental readings include:
Ambient temperature
Humidity
Water presence or leaks
Door or access status
Airflow or ventilation-related conditions, where applicable
This matters because environmental stress can be the root cause of equipment problems. A motor may overheat because the room is too hot, not because the motor itself is failing. A pump controller may suffer because humidity or water ingress is affecting the area. A compressor may work harder because the intake air is warmer than usual or ventilation is poor.
When environmental readings sit beside asset readings in iMonnit, the team can see cause and effect more clearly.
iMonnit turns readings into centralised alarms
Sensors only help when the right people know what is happening. iMonnit provides the central point for sensor data, alerts and history, so condition monitoring does not depend on someone walking past at the right time.
A practical setup might send alarms by email, text message or app notification when a sensor crosses a set limit. More importantly, it can give different limits for different assets.
For example:
A large exhaust fan may have a higher normal vibration range than a small pump
A compressor room may need tighter temperature limits in summer
A standby pump may need an alarm if it runs at all outside a test window
A duty pump may need an alert only if runtime becomes excessive
A motor may need both warning and critical thresholds
This avoids treating every machine the same. It also helps reduce noise, which is vital. If alarms are too sensitive, people learn to ignore them. If they are too loose, the warning comes too late.
A useful alarm structure often has two levels:
Alarm level | Purpose | Typical action |
Warning | Flags a change from normal behaviour | Review trend, inspect at next suitable window |
Critical | Indicates a condition that may lead to failure or unsafe operation | Investigate promptly and decide whether to stop the asset |
This approach supports earlier action without creating panic for every small variation.
How the sensor layers work together in real conditions
The strongest use case for Monnit condition monitoring is not one sensor sending one alert. It is the way several measurements support a better decision.
Consider a chilled water pump. Over several days, the vibration reading starts to climb. At the same time, the motor casing temperature rises above its normal range. Current draw also increases during similar operating periods. That combined pattern may suggest mechanical drag, bearing wear, misalignment, or a process restriction.
Now consider a ventilation fan. Current monitoring confirms it runs on schedule, but runtime shows it has begun operating for longer periods. Ambient temperature in the plant room is also rising. This points maintenance towards ventilation load, controls or airflow, not only the fan motor.
For a compressor, frequent starts and short runtime periods may raise an alert. If current spikes also increase, the team may investigate controls, leaks, pressure settings or mechanical load before the compressor trips.
For a remote pump station, water leak detection and humidity monitoring may be just as valuable as machine data. An environmental alarm can prompt action before moisture damages electrical parts or creates unreliable operation.
These patterns are valuable because they reduce guesswork. A technician who attends site already has a timeline of what changed, when it changed, and which readings moved together.
Reducing manual inspections without losing visibility
Manual inspections still matter. People hear, smell and see things sensors cannot. A technician may notice a coupling guard rubbing, a belt shedding dust, or a valve position that explains a problem.
The goal is not to remove skilled inspection. The goal is to use manual checks where they add the most value.
Without remote monitoring, teams often inspect equipment on fixed rounds because there is no other way to know what is happening. That can mean long travel time, repeated checks on healthy assets, and delayed detection between visits.
Condition monitoring changes the rhythm:
Traditional inspection pattern | Sensor-supported pattern |
Check every asset on a fixed schedule | Check stable assets less often and focus on alerts |
Find issues during rounds | Receive warnings between rounds |
Rely on handwritten or scattered readings | Review centralised history in iMonnit |
React after shutdowns or complaints | Investigate abnormal trends earlier |
Spend time confirming equipment is running | Use current and runtime data to verify operation |
This is especially useful across multiple sites. For organisations with pump stations, plant rooms, warehouses, workshops, agricultural facilities or commercial buildings across Australia, reducing unnecessary site visits can save time and help small teams cover more assets.
Building a practical monitoring plan
A good condition monitoring setup starts with the asset, not the sensor. The question should be simple: what failure or abnormal condition would cause the most trouble, and which measurements would reveal it early?
Start with equipment where unexpected shutdown would create high cost, safety risk, product loss, service interruption or difficult after-hours callouts.
Good candidates include:
Main process motors
Duty and standby pumps
Exhaust and supply fans
Air compressors
Refrigeration or cooling-related motors
Remote pump stations
Sump and wastewater pumps
Critical ventilation assets
For each asset, define what “normal” means. This may need a baseline period where sensors collect readings during healthy operation. Once the normal range is understood, alarms can be set more intelligently.
A simple planning method is:
Choose the asset
Pick equipment where early warning would matter.
Identify likely failure modes
Think about overheating, vibration, overload, short cycling, leaks, humidity or failed starts.
Select matching sensors
Use vibration, temperature, current, runtime and environmental sensing where they add useful evidence.
Set warning and critical thresholds
Base them on normal operation, manufacturer guidance, site experience and maintenance judgement.
Assign alarm recipients
Send alerts to people who can act, not to everyone.
Review trends after real operation
Adjust thresholds if alarms are too frequent or too late.
This process does not need to be complicated. A pump may only need current, vibration and leak detection. A compressor may benefit from current, temperature, runtime and room conditions. A high-value motor may justify several sensing points.
What early warning looks like in practice
Early warning does not always mean a dramatic alarm. Often, it means a small change appears early enough to schedule work sensibly.
A useful alert might lead to:
Tightening a loose mount before vibration damages bearings
Cleaning a blocked filter before a motor overheats
Balancing a fan before it damages supports
Investigating a pump that runs too long before it burns out
Finding a leak that causes a compressor to cycle too often
Fixing ventilation before a whole plant room runs hot
Checking a standby pump that failed to start during a test
The benefit is not only avoiding failure. Planned work is easier to manage. Parts can be ordered. Production can be consulted. A shutdown can be scheduled. A technician can arrive with a clearer fault history and the right tools.
That is a very different position from receiving a call after a motor has tripped, a pump has stopped, or a compressor has shut down on a busy day.
A stronger way to watch critical equipment
Monnit condition monitoring for rotating equipment works best as a layered early-warning system. Vibration shows mechanical change. Temperature shows heat and stress. Current confirms load and operation. Runtime reveals duty cycle problems. Environmental sensing explains the conditions around the asset. iMonnit brings those signals together, so alerts are visible, centralised and easier to act on.
The practical outcome is clear: fewer unnecessary manual inspections, faster awareness of abnormal conditions, and better decisions before an unexpected shutdown.
Start with the assets that would hurt most if they stopped without warning. Add the sensors that match the likely failure modes. Set sensible alarms, watch the trends, and let the data guide the next inspection instead of waiting for the next breakdown.
