A motor health monitoring platform that measures only overall vibration misses rotor bar faults. One that measures only current misses bearing wear and misalignment. Complete motor health monitoring requires both electrical and mechanical signals, or two systems that share data.
What Motor Health Monitoring Covers
A motor health monitoring platform tracks the complete set of failure mechanisms that cause unplanned motor outages. These mechanisms split cleanly into two categories that require different sensor types and different analysis methods.
Electrical Faults
Electrical failure modes include rotor bar cracks or breaks, stator winding insulation degradation, phase current imbalance, voltage supply asymmetry, and ground faults. These are detected primarily through motor current signature analysis (MCSA) and, where voltage monitoring is included, electrical signature analysis (ESA). Key indicators: sideband amplitudes at rotor bar pass frequency and its harmonics, negative-sequence current component, and insulation resistance trends from periodic offline testing.
Mechanical Faults
Mechanical failure modes include bearing outer and inner race defects, rolling element defects, cage faults, shaft misalignment, mass imbalance, and mechanical looseness. These are detected through vibration analysis at the bearing fault frequencies specific to the bearing geometry. Temperature monitoring provides a secondary indicator: elevated bearing temperature often precedes detectable vibration in the early stages of lubrication failure.
Both categories are active in parallel on every operating motor. Rotor bar faults develop alongside bearing wear. Misalignment creates elevated mechanical vibration while also producing characteristic sidebands in the current spectrum from the resulting load oscillation. A platform that monitors only one category gives an incomplete health picture and will miss the failure mode outside its measurement scope.
Deployment Models Compared
Integrated Multimodal Sensor on Motor Housing
The most compact approach: a single wireless sensor mounted on the motor housing captures vibration, temperature, and motor current (via a current transformer on the supply cable). All data is associated with one asset record and processed by one platform. Installation involves one device per motor; data integration is built in rather than engineered.
Trade-off: current measured at the motor terminal has a shorter cable run than current measured at the MCC, which can reduce interference from other loads on the same feeder. However, the current transformer must be accessible at installation, and on motors where the supply enters through sealed conduit, this may require an additional installation step.
Separate Electrical Monitoring Plus Separate Mechanical Monitoring
Some plants install dedicated electrical monitoring hardware (permanent CTs at the MCC, connected to an electrical monitoring gateway) alongside separate vibration sensors on the motor housing. This can make sense where an existing vibration monitoring system is already in place and adding electrical coverage is the incremental step.
The integration challenge: data from two separate systems must be correlated at the software layer to achieve signal correlation across measurement types. If the two platforms do not share a common asset database or time-stamp synchronization, cross-signal analysis requires manual effort. Budget for integration time when evaluating this architecture.
Portable Electrical Monitoring
Portable MCSA instruments collect current signatures on-demand during a route-based inspection program. This provides electrical data without continuous monitoring infrastructure, which suits facilities with limited IT bandwidth or motors that are genuinely non-critical. The limitation: faults that develop between route intervals are not detected until the next visit. For motors where the mean time to failure from first detectable MCSA change is less than the inspection interval, portable monitoring misses the detection window.
Key Platform Capabilities
Fault Frequency Automation
The platform should calculate bearing fault frequencies (BPFO, BPFI, BSF, FTF) and electrical fault frequencies (rotor bar pass frequency, pole pass frequency, stator slot harmonics) automatically from motor nameplate data and bearing model numbers. Manual frequency entry at fleet scale is an ongoing maintenance burden that introduces errors when motor replacements change the bearing model.
Baseline Trending
Both vibration amplitude at bearing fault frequencies and current sideband amplitudes at electrical fault frequencies need to be trended against a motor-specific baseline, not a universal fixed threshold. A bearing fault frequency amplitude of 0.5 g/s may be normal for a large pump motor at full load and alarming for a small fan motor at the same operating point. Baseline-relative trending produces detection that is calibrated to each motor's normal operating behavior.
Alarm Workflow
An alarm that generates an email and requires a technician to log into a separate CMMS to create a work order introduces delay and manual steps. Evaluate whether the platform creates work orders natively, integrates with your existing CMMS via API, or requires a custom integration layer. The alarm-to-work-order path is where many platforms lose the value of their detection capability.
Multi-Parameter Correlation
Some fault conditions produce signatures in both electrical and mechanical data simultaneously. Bearing damage in the late stages often elevates both the BPFO vibration amplitude and the rotor bar pass frequency sideband, because the mechanical bearing load variation creates a corresponding load current oscillation. A platform that correlates elevated bearing fault frequency in vibration with elevated load-related sidebands in MCSA data provides higher-confidence fault classification and fewer false alarms than either signal evaluated independently.
Fleet-Level Reporting
Individual motor alarms are tactical. Fleet-level reporting is strategic: which asset classes are failing most frequently, which sites have disproportionate motor fault rates, which maintenance actions are reducing recurrence. A platform that surfaces fleet-level pattern data helps maintenance engineering teams prioritize capital investment in motor replacement or upgrade programs, not just respond to individual alarms.
Questions to Ask Any Vendor
- Does the platform monitor both electrical and mechanical signals from the same motor asset? If they are separate products or separate databases, ask specifically how data from both is correlated in the interface and in alarm logic.
- Does it correlate signals across measurement types to reduce false alarms? Ask for a specific example of how a multi-parameter alarm rule works, not a general claim about "holistic monitoring."
- What is the sensor's frequency range for bearing fault detection at your operating speeds? For motors below 1,500 RPM, bearing fault frequencies at the outer race (BPFO) fall below 200 Hz. For high-speed motors above 3,000 RPM, fault frequencies are higher but require sampling rates sufficient to resolve them. Confirm the sensor's effective frequency range against your actual motor speed distribution.
- Does it handle VFD-driven motors? Ask specifically whether the platform uses speed-normalized fault frequency calculation or fixed-frequency analysis. The answer reveals whether VFD compatibility is genuine or a checkbox claim.
- What does the alarm-to-work-order flow look like? Walk through the exact steps between a triggered alarm and a scheduled maintenance task in your CMMS. Count manual handoffs.
Deployment Model Comparison
| Deployment Model | Electrical Coverage | Mechanical Coverage | Integration Complexity | Best Suited For |
|---|---|---|---|---|
| Integrated multimodal sensor | Yes (current via onboard CT) | Yes (vibration + temperature) | Low, single platform | New deployments; fleets where motor health is the primary program goal |
| Separate electrical + separate mechanical | Yes (dedicated CT at MCC) | Yes (separate sensor) | Medium to high, two systems require data integration | Plants with existing vibration programs adding electrical coverage incrementally |
| Portable electrical monitoring only | Yes (route-based) | No | Low, no infrastructure | Non-critical motors; facilities with limited IT capacity; program bootstrapping |
| Permanent electrical at MCC only | Yes (continuous, all motors on feeder) | No | Low to medium | Motor fleets where electrical faults are the dominant failure mode; mechanical covered separately |
What Tractian Offers
Tractian's motor health monitoring platform captures vibration, temperature, and current from a single sensor unit mounted on the motor housing. The three measurement types share one asset record, one time base, and one alarm platform, no integration project required to correlate electrical and mechanical data on the same motor.
The platform's motor health capabilities include:
- Continuous MCSA alongside bearing fault frequency trending: Current is sampled continuously, not periodically. Bearing fault frequencies in vibration data are computed from bearing geometry entered at asset configuration. Both trend in parallel on the same asset view.
- Automated electrical fault frequency tracking: Rotor bar count and pole number entered at commissioning drive automatic computation of rotor bar pass frequency and its harmonics. The analyst sees which frequencies are fault-related and their trending amplitude, without manual frequency lookup.
- VFD-aware analysis: For inverter-driven motors, the platform applies algorithms that account for VFD carrier frequency components and compute fault frequencies relative to actual operating speed.
- Multi-parameter alarm correlation: Alert rules can combine vibration and electrical conditions. A motor showing both elevated bearing outer race frequency and elevated load-related current sidebands triggers a higher-severity alert than either condition alone, reducing alarm fatigue on motors with high but stable vibration baselines.
- Direct integration with Tractian's maintenance platform: An alarm on any monitored motor can generate a work order within the same platform, with asset context, fault description, and recommended action pre-populated. No manual handoff between monitoring and CMMS.
- Fleet-level dashboard: Asset health status across all monitored motors is visible in a single view, with filtering by site, criticality, alarm severity, and asset type. Fleet-level fault pattern reports surface recurring failure modes across motor classes or operating areas.
The sensor hardware is wireless, which simplifies installation on motors where running signal cable to a gateway is impractical. Data is transmitted to the cloud platform where processing occurs, with edge buffering to handle intermittent connectivity.
What to Evaluate in Other Platforms
Monitor Electrical and Mechanical Health on the Same Motor
Tractian's multimodal sensor captures vibration, temperature, and current continuously, on one device, one platform, one alarm workflow.
See Electrical Monitoring