Electrical monitoring software is only as useful as the decisions it enables. A platform that stores raw current spectra without computing fault frequencies, trending amplitudes, or connecting alarms to maintenance actions generates data, not decisions.
What Electrical Monitoring Software Does
Electrical monitoring software processes raw current and voltage data from sensors mounted on motor circuits and converts it into actionable diagnostic information. The core functions separate useful platforms from data repositories:
- Spectrum analysis: The software applies FFT or similar transforms to raw current waveforms, producing a frequency spectrum where motor fault signatures appear as sidebands around the fundamental frequency and its harmonics.
- Fault frequency calculation: For each motor, fault frequencies (rotor bar pass frequency, bearing outer race frequency, stator slot harmonics) depend on motor nameplate data: number of rotor bars, bearing geometry, number of poles, and slip. The software must compute these frequencies automatically and overlay them on the spectrum.
- Amplitude trending: Knowing the fault frequency location is only the starting point. The software must track sideband amplitude over time and compare it to a baseline established when the motor was known to be healthy.
- Alarming and reporting: Threshold-based or baseline-relative alarms trigger notifications when a sideband exceeds a defined deviation from baseline. Reporting aggregates asset health status across a fleet.
Platforms that require manual fault frequency entry, that do not support trending, or that alarm only on fixed thresholds rather than baseline deviation create significant analyst workload and produce more false alarms on motors operating at variable load.
Key Evaluation Criteria
Automatic Fault Frequency Calculation
A platform should calculate all motor fault frequencies automatically when the user enters motor nameplate data: rotor bar count, bearing model numbers, pole count, and rated speed. Manual frequency entry is acceptable for initial commissioning of a few motors but does not scale to fleets of hundreds of assets.
Baseline-Relative Alarming
Fixed threshold alarms produce high false-alarm rates on motors that operate at variable loads, because fault sideband amplitudes scale with motor current. A motor running at 90% load produces higher sideband amplitudes than the same motor running at 40% load, regardless of fault condition. Baseline-relative alarming normalizes against the motor's own historical behavior and produces more accurate fault detection.
Electrical Signature Analysis (ESA) Support
ESA uses both voltage and current signals to separate motor-side faults from supply-side conditions. A platform that monitors only current cannot distinguish whether an elevated negative-sequence component comes from a supply voltage imbalance or from a motor winding asymmetry. Voltage input capability is therefore a differentiating feature for plants with known power quality variability.
VFD-Aware Algorithms
VFD output is not a fixed-frequency sinusoid. Platforms using standard line-frequency MCSA algorithms on VFD-driven motors will compute incorrect fault frequencies and produce unreliable results. VFD-aware platforms reconstruct the fundamental frequency from the drive output and apply speed-normalized fault frequency calculations.
CMMS and EAM Integration
A monitoring platform that cannot create a work order, or push to a system that does, adds a manual handoff step between alarm and action. Integration with common CMMS platforms (SAP PM, IBM Maximo, or the vendor's own maintenance module) closes this gap. Evaluate whether integration is native, API-based, or requires a separate middleware layer.
Cloud vs. On-Premise Deployment
Cloud deployment simplifies fleet-level access and software maintenance but requires reliable site connectivity and accepted data residency terms. On-premise deployment keeps data within plant boundaries, which matters in regulated industries or facilities with strict IT security policies. Some platforms offer hybrid architectures with local edge processing and selective cloud synchronization.
Sensor Compatibility
Some platforms are closed ecosystems requiring proprietary sensors. Others accept standard 4-20 mA or Modbus inputs from third-party CTs and power quality meters. Evaluate whether the platform's sensor requirements lock you into a single hardware vendor for future expansion.
Questions to Ask Any Vendor
- Does the software compute fault frequencies automatically from motor nameplate data? If the answer is "you enter the frequencies manually" or "we provide a table," assess the scalability implication for your fleet size.
- Does it trend sideband amplitude against a baseline rather than comparing to a fixed threshold? Ask for an example of a baseline-relative alarm and how it handles load variability on the same motor.
- Can it separate supply-side imbalance from motor-side imbalance? The answer requires voltage monitoring capability and negative-sequence analysis. If the platform is current-only, this distinction is not possible.
- Does it handle VFD-driven motors with specialized algorithms? Ask for documentation of how the platform handles inverter output waveforms specifically, not just "variable frequency" as a marketing term.
- What does the alarm workflow look like: does it create a work order? Walk through the alarm-to-work-order path. Count the manual steps between a triggered alarm and a scheduled maintenance task in the CMMS.
What Tractian Offers
Tractian's electrical monitoring capability is built into its condition monitoring platform alongside mechanical monitoring (vibration, temperature) on the same physical sensor and asset record.
For electrical monitoring specifically, the Tractian platform provides:
- Continuous MCSA: Current signals are sampled continuously, not on a scheduled periodic basis. Fault progression between periodic checks does not go undetected.
- Automated fault frequency tracking: Motor nameplate data entered at asset configuration drives automatic fault frequency calculation. Rotor bar count, bearing geometry, and pole count map directly to tracked sideband frequencies in the spectrum view.
- Baseline-relative trending: Sideband amplitude is trended against a motor-specific baseline established during a known-healthy operating period. Alarms trigger on statistically significant deviation from baseline, not on a fixed dB threshold shared across all motors.
- VFD-aware analysis: The platform includes algorithms designed for inverter-driven motors, accounting for the carrier frequency and its harmonics in the current spectrum to avoid false fault identification.
- Integration with Tractian's maintenance platform: Electrical monitoring alarms connect directly into Tractian's work order and maintenance planning module. An alarm on a compressor motor can trigger a work order with asset context, fault description, and recommended action, without leaving the platform.
- Fleet-level reporting: Asset health status across hundreds of motors is visible in a single dashboard, with filter capability by site, motor type, criticality classification, and alarm status.
The Tractian sensor captures vibration, temperature, and current from a single unit installed on the motor housing, which simplifies installation and keeps all motor health data on one asset record rather than spread across separate electrical and mechanical monitoring systems.
What to Evaluate in Other Platforms
See How Tractian's Platform Handles Electrical Monitoring
Continuous MCSA, automated fault frequency tracking, and direct integration with maintenance workflows, on the same sensor as vibration and temperature monitoring.
See Electrical Monitoring