Bently Nevada AnomAlert: Motor Anomaly Detection Without Sensors

TL;DR: The Bently Nevada AnomAlert is a motor anomaly detector that watches a three-phase motor through its voltage and current at the motor control centre instead of mounting sensors on the machine. The current published datasheet is 286754 Rev. N (copyright 2021). The hardware and the 390100-… ordering codes are still published, but AnomAlert is no longer one of the systems listed on Baker Hughes’ current English online condition-monitoring pages, so treat it as a mature product and confirm availability by quotation before designing it into a new project. On a line-driven motor it needs three CTs and three PTs; on a vector-controlled drive it needs a voltage divider and three Hall-effect current sensors. Inverter chopping frequency must be above 2 kHz, load and speed must stay within 15% over any 6-second window, and soft-starter operation is excluded unless the starter is automatically bypassed. AnomAlert reports anomalies against a learned baseline — not a frequency spectrum — and it is not a protection system. The OPC server sits in AnomAlert Enterprise Software (AES), not in the panel device, so System 1 integration requires AES plus the licensed System 1 AnomAlert Extender, with tags refreshed every 90 seconds.
Spare-parts listings frequently merge three different Bently Nevada products into one description: the AnomAlert motor anomaly detector, the 1900/27 vibration monitor, and the 1900/65A general-purpose monitor. The part numbers overlap at “1900”, the descriptions overlap at “monitor”, and the result is a quotation for the wrong device. This guide checks the claims against the AnomAlert Motor Anomaly Detector datasheet (286754 Rev. N), the System 1 Classic datasheet that covers the AnomAlert extender (174590), and Bently Nevada’s own diagnostics material — and separates what the product actually does from what resellers say it does.
What is the Bently Nevada AnomAlert?
AnomAlert is a permanently mounted, panel-format anomaly detector for three-phase AC induction or synchronous motors, fixed-speed or inverter-driven. It measures the three motor voltages and three motor currents, builds a model of the motor and its load, and raises an alarm when measured behaviour departs from that model. It requires no sensor installation on the motor, coupling or driven equipment.
Each unit is a 96 × 96 mm panel instrument, 140 mm deep, with a six-key keypad, a small LCD and six LEDs. It is mounted indoors, typically in the motor control centre, and configured entirely from the front panel. One AnomAlert covers one motor. The device is ordered as 390100-AA-BB-CC-DD, where the letters encode motor voltage class, fixed or variable speed, current range and language.
There is a separate generator variant, 390150, documented in datasheet 288496. It is a different product with a different ordering code and should not be quoted as an AnomAlert motor unit.
The architecture matters more than the box. AnomAlert is a data source. Configuration, trend storage, real-time display and the OPC interface live in AnomAlert Enterprise Software, which runs on a plant computer. Without AES the device can still alarm locally and close its relay, but the data does not reach a historian or System 1.
Is the AnomAlert still in the Bently Nevada product line?
AnomAlert is still documented and still carries published ordering numbers, but it is not presented as a current product on Baker Hughes’ English online condition-monitoring pages. Datasheet 286754 Rev. N, dated 2021, is the newest revision we could locate, and the AES software is specified for Windows XP, Server 2003, Server 2008, Vista and Windows 7 — all out of support. Buy it as a supported legacy product, not as a new-platform launch.
The evidence is mixed and worth stating plainly. On the positive side, the datasheet is hosted on the current Baker Hughes document server, the ordering table is complete and unchanged, the user guide (286869-01) is still referenced, and AnomAlert still appears on some regional Bently Nevada condition-monitoring pages. On the negative side, the English online condition-monitoring page now lists only Trendmaster and Orbit DCM as systems, and no 2024–2026 successor datasheet or product launch for AnomAlert exists.
The practical conclusion for a plant engineer is that AnomAlert should be treated the way you treat any mature monitoring platform: confirm the current lead time, the current software build and the support status in writing before you commit a project to it. If the answer is “limited supply”, that changes the spares strategy, not the measurement principle. The same discipline applies to any legacy automation purchase, as set out in our guide to managing industrial automation obsolescence.
| Item | What the documentation says | What it means for a project |
|---|---|---|
| Datasheet revision | 286754 Rev. N, copyright 2021 | Newest revision found; no later issue located |
| Ordering code | 390100-AA-BB-CC-DD (motor), 390150 (generator) | Codes still published and decodable |
| Software | AnomAlert Enterprise Software, order 390125-01 | Separate line item; one per enterprise computer |
| Host operating system | Windows XP / 2003 / 2008 / Vista / 7 | Requires an isolated host or a VM; IT policy review needed |
| Product visibility | Absent from current English online CM page | Confirm availability and support by quotation |
What does AnomAlert measure, and what hardware has to be installed?
AnomAlert measures three phase-to-phase voltages and three phase currents. The voltage input is rated 480 Vrms line-to-line (277 Vrms line-to-neutral) maximum, CAT II, with 3.5 MΩ phase-to-phase impedance. Current is measured through customer-supplied CTs with 1 A or 5 A secondaries, or through Hall-effect current sensors on inverter-driven models. Nothing is mounted on the motor.
That is the whole point of the architecture. Because the measurement point is the electrical supply, the detector works on motors where a vibration sensor cannot practically be fitted: hermetic pumps, submersible units, sealed compressors, and driven equipment inside a process envelope. The datasheet states it is applicable to most pumps, compressors and similar loads for exactly this reason.
The input hardware is not included. CTs, PTs and current sensors are customer supplied, and the accuracy requirement is explicit: 1% or better. That single line causes more commissioning problems than any other part of the specification, because a protection-grade CT selected for relaying may not hold 1% accuracy at the low current end where anomaly detection actually works.
| Motor / drive type | Voltage sensing | Current sensing | Notes from the datasheet |
|---|---|---|---|
| Low voltage (≤480 Vac), line driven | Tap directly off the voltage lines to the motor | 3 CTs, 1% accuracy, 1 A or 5 A secondary | Simplest installation; one unit per motor |
| Low voltage, scalar-controlled VFD | 3 PTs, 1% accuracy, 100/110/120 V secondary | 3 Hall-effect sensors, 50–400 mA secondary | Sensor power supply required in the MCC |
| Vector-controlled VFD (medium/high voltage models) | Voltage divider giving 100–120 V nominal into AnomAlert | 3 Hall-effect sensors, 50–400 mA secondary | Divider, not a PT, because of the PWM waveform |
| Medium/high voltage (>480 Vac), line driven | 3 PTs, 1% accuracy, 100/110/120 V secondary | 3 CTs, 1% accuracy, 1 A or 5 A secondary | Voltage class chosen in the model code |
Note the asymmetry in the current path. A conventional CT works on a sinusoidal line current, which is what a line-driven motor draws. A drive output is a chopped waveform with a high common-mode component, so the variable-speed models use Hall-effect sensors with a 50–400 mA output and an external power source instead. That is a real installation constraint, not a detail: the sensor supply has to be designed into the panel, and the sensors have to be selected against the motor current range coded in the model number.
Power input is 100–240 Vac at 47–64 Hz, 19 VA, or 120–300 Vdc. Field wiring enters through the rear; the front face is IP40 and the complete unit is IP20, so the device belongs inside an enclosure, not on a wall in a washdown area.
Does AnomAlert work on VFD-driven motors?
Yes, with three published conditions. The inverter chopping frequency must be greater than 2 kHz. Motor current load and speed must not vary by more than 15% during any 6-second interval. And soft-starter systems are excluded unless the starter is automatically bypassed immediately after motor start-up and during subsequent use. Scalar and vector control are both supported, but they require different voltage-sensing hardware.
The chopping-frequency limit is the one that disqualifies older drives. Below 2 kHz, the switching ripple dominates the current waveform and the model cannot separate motor behaviour from drive behaviour. Most modern drives default to 4–8 kHz, so the check is straightforward, but it must be done per drive, not per plant.
The 15%-in-6-seconds limit is the more subtle constraint, and it is the one that rules out many real applications. AnomAlert compares measured behaviour against a learned model at an operating point. If the load swings continuously — a ramping extruder, a batch mixer, a wind-varying fan — the model is chasing a moving target and the anomaly index becomes noise. The device is designed for steady process duty, which is exactly what most pumps and compressors provide.
The soft-starter exclusion is a safety-of-measurement rule. During start, a soft starter chops the voltage and the motor is neither at speed nor at load; the model has no valid reference. Automatic bypass removes that window, but it has to be verified at commissioning, not assumed from the single-line diagram.
Vector control needs the divider because a PT is a 50/60 Hz magnetic device. Feeding a PWM output through a PT gives a distorted secondary that varies with the drive’s modulation index, not with the fundamental voltage the motor actually sees. A resistive or capacitive divider tracks the fundamental, and the datasheet specifies the result as 100–120 V nominal into the device. This is the same reason a drive output should never be measured with a standard panel meter selected for sinusoidal service.
Which motor faults can AnomAlert actually detect?
The datasheet claims mechanical anomaly detection (unbalance, misalignment, roller bearings and similar), electrical anomaly detection (loose windings, short circuits and similar), electrical parameters (voltage and current imbalance, power factor) and load changes caused by the driven equipment, such as cavitation or plugged filters and screens. It does not publish a fault-frequency table, and it does not name individual rotor or stator failure modes in the motor datasheet.
That distinction is important because vendor summaries often go further than the document. The AnomAlert datasheet is deliberately functional: it says the device detects the presence of an anomaly in a category, not that it identifies a specific defect with a specific severity. Bently Nevada’s machinery diagnostics material goes one step further and lists non-uniform air gap, rotor bar cracks, brush faults, insulation deterioration and loss of an output phase among the motor and generator malfunctions that electrical measurements can reveal. Those are credible detection targets for model-based current and voltage analysis, but they are not enumerated in 286754, and no accuracy or detection-probability figure is published for them.
| Fault or condition | Category | Where it is documented | What you get |
|---|---|---|---|
| Unbalance | Mechanical | 286754 Rev. N description | Anomaly alarm against baseline |
| Misalignment | Mechanical | 286754 Rev. N description | Anomaly alarm against baseline |
| Roller bearing degradation | Mechanical | 286754 Rev. N description | Anomaly alarm against baseline |
| Loose windings, short circuits | Electrical | 286754 Rev. N description | Anomaly alarm against baseline |
| Voltage and current imbalance, power factor | Electrical parameter | 286754 Rev. N description | Trended measured value |
| Cavitation, plugged filters and screens | Driven equipment / process | 286754 Rev. N description | Load-change alarm |
| Non-uniform air gap, rotor bar cracks | Electrical | Bently Nevada diagnostics literature | Detection target, not itemised in 286754 |
| Brush faults, insulation deterioration, lost phase | Electrical | Bently Nevada diagnostics literature | Detection target, not itemised in 286754 |
What the device does not do is equally clear. It does not output a spectrum, it does not calculate bearing defect frequencies, and it does not give a remaining-life estimate. The alarm structure is two-level and directional: Line Change for an unexpected change in incoming power, Load Change for an unexpected change in process, four configurable alarm parameters, and a two-stage response labelled “Examine 1: plan maintenance” and “Examine 2: perform maintenance”. There is one assignable relay output with NO/NC contacts.
That structure is an operational workflow, not a diagnostic report. The output tells a reliability team that something changed and how urgently to look; it does not tell them which bearing or which stator slot. A technician still needs a portable analyser, a thermographic survey or an insulation test to localise the fault. AnomAlert narrows the search — that is its value, and it is a real one on inaccessible machines.
How does AnomAlert connect to System 1?
The OPC server is built into AnomAlert Enterprise Software, not into the panel device. AES collects from the units, stores the data in a SQL database and publishes OPC DA 2.0. System 1 reads that OPC data through the AnomAlert System Extender, which is ordered separately under datasheet 174590 and requires its own licence. Tag update rate is 90 seconds.
This is the single most common error in reseller descriptions, and it is worth correcting explicitly: a panel-mounted AnomAlert does not talk to System 1 on its own. The chain is device → RS-422/485 or Ethernet → AES → OPC → System 1 extender. Each hop is a separate order line and, in the Ethernet case, a separate converter.
The capacity figures are published. One AES computer supports up to 200 AnomAlert units across serial and TCP/IP channels, with a maximum of 10 units per channel. One System 1 OPC server instance handles 100 units, and there is one OPC server instance per system, hosted on the master AES. Each AnomAlert exposes over 180 tags. If you plan more than 20 units on the bundled SQL Express database, the full SQL Server licence is required and must be purchased separately.
The communication hardware is equally specific. Converter kit 287127-01 converts RS-232 to RS-422/485, and kit 287128-AA is a Moxa NPort DE-311 that converts RS-422 to TCP/IP Ethernet. RS-232 on the device itself needs an additional converter. None of this is exotic, but all of it has to appear in the bill of materials, because a quotation that lists only the monitors will not produce data.
Two integration risks deserve a place in the project risk register. First, the AES host operating system list stops at Windows 7, so the software normally runs on a segregated VM or an isolated engineering station. Second, a 90-second tag refresh makes AnomAlert unsuitable as a control or protection input — it is a condition-monitoring data source, and System 1 treats it as one.
| Integration item | Published specification | Practical consequence |
|---|---|---|
| OPC interface | OPC DA 2.0, built into AES | Not available from the panel device directly |
| System 1 connection | AnomAlert System Extender, datasheet 174590 | Separate licence and configuration step |
| Tags per unit | Over 180 | Point-count and licence sizing |
| Tag update rate | 90 seconds | Trending and advisory use only |
| Units per AES computer | Up to 200; 10 per channel | Channel and converter planning |
| Units per System 1 OPC instance | 100 | Second OPC instance above 100 motors |
| Database | SQL Express included, up to 20 units | Full SQL licence above 20 units |
How does electrical monitoring compare with vibration monitoring?
Vibration monitoring measures the machine; AnomAlert measures the motor’s electrical response. Vibration wins on localisation and on anything mechanical outside the motor — bearings, gears, couplings, looseness, rotor dynamics. AnomAlert wins on access and on electrical faults that never produce a strong vibration signature. The two are complementary, and neither replaces the other.
The blind spots are structural, not commercial. A vibration sensor on a bearing housing sees the bearing. It does not see a stator winding that is loosening, a rotor bar that is cracking, or a supply imbalance that is heating the motor from the inside. Those conditions show up in current and voltage long before they show up in an accelerometer, which is why motor current signature analysis exists as a discipline at all.
The reverse is also true. AnomAlert does not resolve a gear mesh frequency, it does not detect a coupling rub in its early stage, and it cannot separate two bearings on the same shaft. For a critical train, the conventional architecture — proximity probes or accelerometers into a Bently Nevada 3500 machinery protection system with a 3500/42M Proximitor/Seismic monitor and a 3500/50M tachometer module for speed reference — remains the right choice. AnomAlert adds a second, independent view of the same asset from the electrical side.
Where AnomAlert is genuinely hard to replace is the machine you cannot instrument. A hermetic canned-motor pump has no accessible bearing housing. A submersible sewage pump has no place to bond an accelerometer. A compressor inside a sealed package may have no spare penetration. In those cases, three CTs in the MCC bucket are the only condition-monitoring route that does not require a shutdown and a modification to the machine.
| Question | Vibration monitoring | AnomAlert electrical monitoring |
|---|---|---|
| Where is the sensor? | On the machine, bearing housing or casing | In the MCC, on CTs and PTs |
| Access to the machine required? | Yes, for installation and route access | No |
| Bearing and gear localisation | Yes, with spectrum and defect frequencies | No |
| Stator, rotor and supply faults | Indirect at best | Primary detection target |
| Output for diagnosis | Waveform and spectrum | Anomaly alarms and trended parameters |
| Update rate | Continuous or fast scan | 90-second OPC tag refresh |
| Protection / trip function | Yes, in a 3500 or similar rack | No; one assignable relay for advisory use |
| Best-fit asset | Critical trains, gearboxes, turbomachinery | Pumps, compressors, inaccessible motors |
If the plant already runs 3300 XL proximity probes and a 3500 rack, AnomAlert is an add-on data source, not a replacement. If the plant runs Orbit 60 conneX with a DCS interface, AES data can sit alongside it in the same enterprise hierarchy, which is the argument for keeping the System 1 extender in scope even when the initial project is small.
What does installation involve on the electrical side?
Installation is electrical work inside a live-capable motor control centre: CTs and PTs have to be fitted or tapped, secondary wiring run to the panel, and the device mounted in a 96 × 96 mm cut-out with 140 mm behind the door. That work requires lock-out/tag-out, arc-flash PPE appropriate to the panel’s incident energy, and a qualified electrician working to the site’s electrical safety programme. AnomAlert itself is a CAT II 480 V measuring device; it does not make the panel safe to work in.
The specific hazards are the familiar ones. An open-circuited CT secondary develops a dangerous voltage, so CT wiring must be shorted before any secondary circuit is opened and the short removed only after the circuit is restored. PT circuits need fuse or MCB protection on the primary side and must be isolated before the device terminals are touched. Phase rotation and CT polarity have to be verified, because a reversed CT produces a plausible but wrong current vector and the model will learn the error.
Panel design details from the datasheet: the unit is 96 × 96 × 140 mm, weighs 1.17 kg in the line version and 0.98 kg in the inverter version, and requires 0–40 °C ambient with up to 90% relative humidity, non-condensing. That temperature window is narrower than most MCC rooms are designed for. In a hot climate, the panel cooling calculation has to include the 19 VA device load and the converter, or the unit will sit above its rating in summer.
On the network side, plan the daisy chain before pulling cable. RS-422/485 supports up to 10 units per channel and needs a converter at the computer end; Ethernet needs the Moxa NPort converter at the panel end. Whichever route is chosen, the AES computer needs a fixed address, a database backup policy and a patching approach that respects its legacy operating system.
Commissioning sequence that avoids the usual rework: confirm motor nameplate data against the ordered model code, verify CT ratio and class against the 1% accuracy requirement, check drive chopping frequency and confirm the 15%-in-6-seconds load stability assumption over a full production cycle, then let the model learn across the full operating envelope before setting Examine 1 and Examine 2 thresholds. Setting thresholds during a learning period is the fastest way to produce an alarm that everyone learns to ignore.
What should buyers verify before ordering a 390100 AnomAlert?
Verify five things: the voltage class (low ≤480 Vac versus medium/high >480 Vac), the speed type (fixed line-driven versus variable inverter-driven), the current range and CT secondary, the language option, and the software and System 1 extender licences. The model code encodes all of them, and a wrong digit produces a unit that cannot be commissioned on the motor it was bought for.
The current range is where most errors happen. Fixed-speed models offer only 1 A or 1–5 A CT secondaries. Variable-speed models offer six ranges from up to 1 A through 1000–2000 A, and the Hall-effect sensor must match the chosen range. Buying a 1–5 A unit for a motor whose CTs are 1 A is not a configuration detail; it is the wrong product.
Then confirm the surrounding bill of materials. The CTs, PTs and current sensors are customer supplied. At least one software version must be ordered, and the AES is one licence per enterprise computer. System 1 integration needs the extender from datasheet 174590 plus a licensed System 1 installation. Converter kits are separate. None of these items appear automatically on a monitor-only quotation, and each one is a reason a project stalls at commissioning.
Finally, verify identity before price. AnomAlert shares a number family with the 1900-series monitors and is routinely mis-described in secondary-market listings. Our guide to verifying an automation part number before you order sets out the cross-check sequence, and the Bently Nevada spare-parts buying guide covers the wider family. If the application is a standard IE3 machine such as the SEW Eurodrive DRN90L4 1.5 kW IE3 motor on a Lenze 8200 vector frequency inverter, the drive type decides whether you order a PT-based or divider-based voltage input — check that before the model code is fixed.
Where do these AnomAlert facts come from?
- AnomAlert Motor Anomaly Detector datasheet, 286754 Rev. N, Baker Hughes / Bently Nevada. Primary source for inputs, limits, ordering codes, AES capacity and alarms.
- AnomAlert Generator Anomaly Detector datasheet, 288496, Baker Hughes / Bently Nevada. Confirms the generator variant is a separate 390150 product.
- Bently Nevada Machine Diagnostics Services, Baker Hughes. Lists non-uniform air gap, rotor bar cracks, brush faults and insulation deterioration under electrical measurements.
- Online Condition Monitoring Systems, Baker Hughes. Current English product page listing Trendmaster and Orbit DCM; AnomAlert is not listed.
- Plantwide condition monitoring solutions brochure, Baker Hughes. Describes AnomAlert as a model-based motor anomaly detection system with an OPC interface.
Frequently asked questions
Is the Bently Nevada AnomAlert still available?
It is still documented with live ordering codes, and the 2021 datasheet (286754 Rev. N) remains the current published revision. However, AnomAlert no longer appears among the systems listed on Baker Hughes’ current English online condition-monitoring page, which lists Trendmaster and Orbit DCM. Treat it as a mature product in support rather than a current-platform launch, and confirm lead time, software build and support status in writing with Baker Hughes before committing a project.
Does AnomAlert need sensors installed on the motor?
No. AnomAlert measures the three motor voltages and three motor currents at the motor control centre, so nothing is mounted on the motor, coupling or driven equipment. The CTs, PTs and Hall-effect current sensors are customer supplied and installed in the electrical panel. This is why the product suits hermetic pumps, submersible motors and packaged equipment where a vibration sensor cannot be fitted.
Does AnomAlert work on VFD-driven motors?
Yes, for both scalar and vector control, subject to three published conditions. The inverter chopping frequency must be greater than 2 kHz, motor current load and speed must not vary by more than 15% over any 6-second interval, and the motor must not run on a soft starter unless it is automatically bypassed immediately after start-up and during use. Scalar-controlled drives use three PTs; vector-controlled drives use a voltage divider giving 100–120 V nominal into the device.
What current transformers does AnomAlert need?
Line-driven models use three customer-supplied CTs with 1% or better accuracy and either a 1 A or 5 A secondary, selected by the model code. Inverter-driven models use three Hall-effect current sensors with 50–400 mA secondary outputs and an external power source, generally installed in the motor control panel. Protection-grade CTs chosen only for relaying may not meet the 1% accuracy requirement across the low-current range that anomaly detection depends on.
Can AnomAlert detect rotor bar and stator winding faults?
The motor datasheet claims electrical anomaly detection for loose windings, short circuits and similar conditions, plus voltage and current imbalance and power factor. It does not itemise rotor bar cracks, air gap eccentricity or insulation degradation. Bently Nevada’s machinery diagnostics literature does list non-uniform air gap, rotor bar cracks, brush faults and insulation deterioration among the motor and generator faults that electrical measurements can reveal, but no detection probability or accuracy figure is published.
Is AnomAlert a protection system?
No. It is a condition-monitoring anomaly detector. It has one assignable relay output with NO/NC contacts and a two-stage advisory structure (“Examine 1: plan maintenance” and “Examine 2: perform maintenance”), and its System 1 data refreshes every 90 seconds. It is not SIL-rated, it does not trip the motor, and it should not be used as a substitute for motor protection relays or a Bently Nevada 3500 machinery protection rack on critical assets.
Is the OPC server inside the AnomAlert device or in the software?
The OPC server is built into AnomAlert Enterprise Software (AES), not into the panel-mounted device. AES collects data from the units, stores it in a SQL database and publishes OPC DA 2.0 to System 1 through the AnomAlert System Extender. A quotation that includes monitors but not AES, the extender and the communication converters will not deliver data to System 1.
Which System 1 versions support AnomAlert?
AnomAlert data enters System 1 through the AnomAlert System Extender described in System 1 datasheet 174590, and the integration is documented in System 1 Classic 6.x material. Because the AES host operating system list stops at Windows 7 and the product is mature, confirm the exact System 1 version and extender compatibility with Baker Hughes before purchase rather than assuming support for the newest release.
How many motors can one AnomAlert Enterprise Server handle?
One AES computer supports up to 200 AnomAlert units across serial and TCP/IP channels, with a maximum of 10 units per channel. One System 1 OPC server instance handles 100 units, and there is one OPC server instance per system, hosted on the master AES. The bundled SQL Express database covers up to 20 units; beyond that the full SQL Server licence must be purchased separately.
What can AnomAlert see that vibration monitoring cannot?
It can see electrical and supply-side conditions that produce little or no casing vibration: loose stator windings, short circuits, voltage and current imbalance, power factor changes, and loss of an output phase. It also monitors the driven load, so cavitation and plugged filters or screens appear as load changes. It cannot resolve bearing defect frequencies, gear mesh, coupling rubs or rotor dynamics, which remain the domain of vibration measurement.
