Bently Nevada, a Baker Hughes business, publishes a global installed base of more than 8 million sensors and more than 100,000 rack monitoring systems, built on more than 60 years of machine protection and condition monitoring experience. The 6 million sensor figure that circulates alongside those numbers comes from an Infragistics customer case study created in December 2020, while the Orbit 60 Series was moving from announcement to first shipments; it is a date-stamped snapshot, not a current total. Both figures count cumulative sensors deployed or installed, not monitoring channels or monitored points, and neither source publishes a channel-level breakdown.
That distinction is not academic. Maintenance and procurement teams size spares pools, plan retrofits and justify monitoring upgrades from installed-base numbers, and a figure quoted without its date or unit can be wrong in either direction. The two Bently Nevada sources below are both official or vendor-published, and they disagree by roughly two million sensors. The disagreement is explained by time, not by a contradiction.
The Three Numbers, and What Each One Actually Counts
| Figure |
Value |
Unit and what it counts |
Source and date |
| Sensors deployed (older snapshot) |
Over 6 million |
Cumulative sensors installed globally; the source says sensors, not channels or measurement points |
Infragistics customer case study, PDF created 18 December 2020 |
| Sensors deployed (latest published) |
Over 8 million |
Cumulative sensors deployed to date across the globe; same unit, no channel split published |
Bently Nevada blog "Why Orbit 60? Why Now?", English page last modified 27 September 2024 |
| Rack monitoring systems |
Over 100,000 |
Installed rack-based monitoring systems across all product generations |
Both sources, 2020 and 2024 |
| Years of experience |
Over 60 |
Company experience in machine protection and condition monitoring |
Both sources |
| 3500 Series units |
Over 100,000 |
Units of the 3500 Monitoring Series installed since its 1996 launch |
Bently Nevada blog, 2024 revision |
The unit matters because a sensor count and a channel count diverge quickly in a real plant. Proximity probes, accelerometers, velocity transducers and Keyphasor references are different devices, and a single rack can terminate many of them across several cards. Bently Nevada states the figures as sensors. They should not be quoted as channels, measurement points or "data streams" unless a source explicitly says so.
The rack total is the most stable of the three numbers: it is over 100,000 in both the 2020 case study and the 2024 revision of the blog. The sensor total rose by roughly two million over the same period. The sources do not break down where those additional sensors were deployed, so any explanation beyond the published numbers would be inference rather than fact.
Translated copies are a separate trap. The Korean-language version of the same Bently Nevada article still shows 6 million sensors and 85,000 installed 3500 units, even though the English page carries the revised 8 million and 100,000 figures. When a number is quoted in a tender document or an internal business case, the language and the revision date belong next to it.
Why the 6 Million Figure Is a 2020 Snapshot
The Infragistics case study is a genuine Bently Nevada source, but it is a point-in-time document. Its PDF was created on 18 December 2020, and its opening paragraph describes the company as leveraging "over 60 years of expertise with over 6 million sensors and 100,000 rack monitoring systems installed globally." That sentence has been reproduced widely, usually without the date.
The Orbit 60 timeline explains why the document reads the way it does. Bently Nevada announced the platform on 10 September 2019, opened fixed-price quoting in April 2020 and began shipping in April 2021. The case study therefore sits between quote availability and volume shipment: the installed base it describes is the pre-Orbit 60 fleet, dominated by the 3500 Series.
| Milestone |
Date |
What it means for the installed base |
| Public announcement of the Orbit 60 Series |
10 September 2019 |
New platform disclosed; existing fleet remains 3500-dominated |
| Available to quote |
April 2020 |
Customers can specify Orbit 60, but shipments have not started |
| Infragistics case study PDF created |
18 December 2020 |
6 million sensors and 100,000 racks recorded as the fleet of that moment |
| Available to ship |
April 2021 |
Orbit 60 begins entering the installed base |
| English blog last modified |
27 September 2024 |
8 million sensors and 100,000 racks in the current version |
Read together, the two documents describe the same fleet at two different moments. The case study is the better source for what the installed base looked like when Orbit 60 was being introduced. The current Bently Nevada page is the better source for a present-day total. Quoting the 2020 figure as "today" understates the fleet by about two million sensors.
What Infragistics Actually Built for Orbit 60
The Infragistics work is also frequently misread. Bently Nevada did not partner with Infragistics on sensors, rack hardware or the protection path. The case study describes a software interface problem: Orbit 60 is a data-driven platform that has to handle high volumes of streaming IIoT data from hundreds or thousands of devices, and the team needed visualisations that made that data usable rather than overwhelming.
Bently Nevada selected Infragistics Ultimate UI for WPF and used its data grid, property grid, dock manager, charting and custom editor controls in Orbit Studio and in decision-support screens. The controls handle column grouping, row nesting, per-cell custom editing and filtering across complex domain data models.
"Instead of overwhelming our end users with a seemingly infinite list of columns in a data grid, we wanted to make it easier to see the important information, at a high level, and then let them decide if they wanted to dig deeper into the data," said Craig Campbell, Senior Staff Software Architect at Bently Nevada, in the case study.
Cody Worsnop, Lead Developer at Bently Nevada, described the same requirement from the implementation side: custom editors per grid cell let developers work with complex Bently domain data models "seamlessly and with almost no turnaround time." Vikas Desai, Global Technology Executive at Baker Hughes, framed the outcome as speed: "Infragistics helps us to move faster and accelerate our building of applications."
The boundary is worth stating plainly. Infragistics supplies a presentation layer inside the configuration and visualisation software. The protection function still runs from sensor to I/O module to monitoring card to relay output inside the rack. A WPF data grid can make a trend easier to read; it does not sit in the trip path, and it does not change the measurement chain.
Orbit 60, 3500 and System 1: Where Each Fits
| Platform |
Role |
Status and notes |
| 3500 Monitoring Series |
Rack-based machinery protection and condition monitoring |
Launched 1996; more than 100,000 units installed; Bently Nevada says it remains in full product support with new features in development |
| Orbit 60 Series |
Next-generation rack-based and distributed protection and condition monitoring |
Announced September 2019; shipping from 2021; API 670 protection with SIL certification; designed to IEC 62443-4-2 |
| System 1 |
Condition monitoring software for diagnostics, trending and reporting |
Now delivered as Cordant Asset Health, powered by System 1 |
| Orbit Studio |
Configuration and visualisation application for Orbit 60 |
Uses Infragistics WPF controls for grids, charts and property editing |
The naming is often flattened into "Orbit 60 is the new 3500," which loses the software layer entirely. The 3500 and Orbit 60 are hardware platforms that acquire and protect. System 1 is the software that stores, trends and diagnoses. Orbit Studio is the engineering tool used to configure and view Orbit 60 systems. Infragistics appears only in the last of those four rows.
Inside the Orbit 60 Architecture
Orbit 60 was designed around three ideas that the 3500 architecture could not accommodate: data isolation between the protection and condition-monitoring networks, a distributable chassis topology, and much higher channel density per system.
-
Channel density. A single System Interface Module defines a system of up to 80 dynamic channels. Bently Nevada describes deployments with up to 65 dynamic vibration inputs and 100 static inputs, such as temperature, in one system.
-
Distributed topology. Bridge modules connect multiple chassis in daisy-chain or star configurations, replicating data at full resolution between bridged bases. I/O can sit next to the machine to cut field wiring, or remain in a central control room.
-
Cyber segregation. The architecture separates the protection function from the condition monitoring and business network, so a user on the monitoring side cannot reach the protection network. Bently Nevada states the platform is designed to meet IEC 62443-4-2.
-
Keyphasor scalability. The 3500 supports up to four Keyphasor inputs; Bently Nevada states that Orbit 60 has no inherent limit, which matters for multi-shaft trains and for monitoring many smaller machines on one system.
-
Chassis options. 3U 10-slot and 19-slot, and 6U 28-slot chassis are listed, with 7-slot and 11-slot compact chassis listed for availability in early 2027.
For a plant with an existing 3500 fleet, the practical question is not which platform is newer. It is which assets justify a distributed, cyber-segregated platform and which are still best served by the 3500 racks already installed, wired and validated.
What 100,000 Racks Means for Spares and Retrofits
An installed base of more than 100,000 rack monitoring systems is also a spares market. Bently Nevada states that the 3500 remains in full product support, and the company documents a retrofit path from 3500 to Orbit 60 that is intended to minimise risk, cost and downtime. Both statements point in the same direction: the 3500 fleet is not being abandoned, and module-level demand will persist for years alongside new Orbit 60 deployments.
That is why suffix-level part numbers still matter more than family names. A 3500/42-01-02, a 3500/42M-09-00 and a 3500/45-05-00 are not interchangeable because they share a series number; channel count, I/O type, firmware compatibility and rack slot assignment all change with the suffix. The same rule applies to probes and transducers, where cable length, connector type, armor and temperature rating are encoded in the model string.
PLC Source PRO lists more than 3,500 Bently Nevada part numbers across 3500 modules, 3300 XL probes, Proximitor sensors, accelerometers, Velomitor transducers and probe housings. Availability changes continuously, so confirm the exact suffix before ordering.
Products and Spares for Bently Nevada Monitoring Systems
The table below maps commonly requested part numbers to their function in the measurement and protection chain. Every link points to a live product page on this site.
Need a cross-reference from a 3500 module to an Orbit 60 equivalent, or a probe assembly matched to an existing extension cable? Contact PLC Source PRO with the full model string and rack slot details.
Key Takeaways
- Bently Nevada, a Baker Hughes business, publishes more than 8 million sensors and more than 100,000 rack monitoring systems in its current English material, with more than 60 years of experience.
- The 6 million sensor figure comes from an Infragistics case study created in December 2020; it describes the pre-Orbit 60 installed base and should always be date-stamped.
- Both figures count sensors deployed, not channels or monitored points; no channel-level breakdown is published.
- Infragistics supplied WPF UI controls for Orbit Studio, the configuration and visualisation software, not sensors, rack hardware or the protection path.
- Orbit 60 is the next-generation hardware platform; System 1 is the software; the 3500 remains in full product support with more than 100,000 units installed.
- Orbit 60 adds distributed chassis, up to 80 dynamic channels per SIM, IEC 62443-4-2 design and protection-to-monitoring network segregation.
Frequently Asked Questions
Is Bently Nevada owned by Baker Hughes?
Yes. Bently Nevada operates as "Bently Nevada, a Baker Hughes business," and that is the attribution used in both the Infragistics case study and Baker Hughes' own product and blog pages. For procurement and brand consistency, the full attribution is the accurate form rather than "Bently Nevada" alone.
Does Bently Nevada have 6 million or 8 million sensors installed?
Both numbers have been published, at different times. The Infragistics case study, created in December 2020, states over 6 million sensors and 100,000 rack monitoring systems installed globally. The current English version of Bently Nevada's "Why Orbit 60? Why Now?" article, last modified on 27 September 2024, states over 8 million sensors deployed to date with the same 100,000 rack total. For present-day use, 8 million is the newer official figure. Both are stated as sensors, not channels or measurement points.
Did Infragistics build the Orbit 60 sensors or rack hardware?
No. Infragistics supplied user-interface controls, specifically Ultimate UI for WPF, used in Orbit Studio and decision-support screens. The case study describes a data-visualisation problem: Orbit 60 generates high-volume streaming IIoT data, and Bently Nevada needed grids, charts and property editors that could present it clearly. The sensors, I/O modules, rack hardware and protection logic are Bently Nevada's own, and the protection path does not depend on the Infragistics controls.
Is the 3500 Series discontinued now that Orbit 60 exists?
No. Bently Nevada states that the 3500 remains in full product support, with new features and functionality in development, and that more than 100,000 units have been installed since the series launched in 1996. Orbit 60 is positioned as the next-generation platform for new deployments and for retrofits, with a documented migration path from 3500. Both platforms therefore coexist in the installed base, which is why 3500 module-level spares remain in demand.
Sources: Infragistics — Bently Nevada Makes Streaming IIoT Data More Accessible (customer story) · Infragistics — Bently Nevada customer story PDF (created 18 December 2020) · Baker Hughes — Why Orbit 60? Why Now? (English, last modified 27 September 2024) · Baker Hughes — Why Orbit 60? Why Now? (Korean version, still showing the earlier figures) · Baker Hughes — Orbit 60 Series product page · Baker Hughes — Bently Nevada launches the Orbit 60 Series (10 September 2019) · Baker Hughes — Orbit 60 Series milestones (ATD, ATQ, ATS) · Baker Hughes — Bently Nevada monitoring systems (3500 and Orbit 60)
Related reading on PLC Source PRO: Rockwell Automation SecureOT and IEC 62443 obligations for OEMs · Mitsubishi Electric's OT security approach for industrial equipment.