Bently Nevada has not discontinued the 3500 — and that is the point. Baker Hughes' condition-monitoring brand says the 3500 line remains in full product support, with more than 80,000 systems deployed and roughly 5,000 new systems installed each year, while Orbit 60 is the platform it recommends for new installations “wherever suited.” The real decision for a plant is therefore not “3500 or Orbit 60?” but “which assets should move to the newer architecture, and what does the 3500 fleet need to keep running?” The short answer: Orbit 60 wins on distributed layout, cyber segregation and channel density; the 3500 remains a defensible choice where the rack works, the spares are healthy and no new cyber requirement forces a change.

Key facts at a glance

What Bently Nevada actually said — and what it left open

The current Orbit 60 product page is explicit: “Our flagship monitoring system, 3500, will continue to be supported in coming years and well into the future; the 3500 is currently in full product support.” A separate Bently blog, “Our commitment to the 3500 monitoring system,” answers the question customers keep asking — whether the 3500 is obsolete — with a direct no. The company describes Orbit 60 as the recommendation for new installations after 2020 where it fits, and says there is “no compelling reason to upgrade” existing 3500 systems immediately unless Orbit 60 functionality is required or desired.

That is a support statement, not a product roadmap. Bently has not published an end-of-life date, a last-order date or a spare-parts window for the 3500, and it has not promised that every future capability will be back-ported to the older platform. The commitment is about keeping installed systems serviceable: modules, repair, documentation, firmware and configuration tooling. Anyone who reads “fully supported” as “feature-identical to Orbit 60” will be disappointed.

The scale explains the position. Bently says more than 80,000 3500 systems are deployed worldwide, with around 5,000 new systems still going in each year. A 2019 launch release for Orbit 60 cited 85,000 racks installed. Those numbers make a forced migration programme commercially and operationally implausible; they also mean the secondary market for 3500 modules will stay liquid for years.

Why the 3500 is still in the catalogue

The 3500 is a rack-based protection system that has been in service since the late 1990s. It is API 670-aligned and available as a SIL 2-rated system, with hazardous-area approvals and a wide catalogue of application-specific monitors: vibration, displacement, temperature, pressure, speed, overspeed, relay and communication modules. For fluid-film-bearing turbomachinery, that application depth is the reason the platform persists.

Bently's commitment blog points to concrete investment rather than sentiment. The 3500 is manufactured, tested and assembled in Minden, Nevada. The company spent 2016 and 2017 refreshing the electronics and board layout of its 3500 modules to meet RoHS requirements, replacing green boards with blue ones, and it says it has negotiated lifecycle contracts with suppliers to manage component and tool obsolescence. Firmware documentation and libraries were completed, and the rack configuration software was being refreshed. That is the unglamorous work that keeps a 25-year-old platform orderable.

What it does not mean is that the 3500 is the right choice for every new project. A greenfield plant with a cyber budget, a distributed machine train and a preference for fewer spare-part families will usually be better served by Orbit 60. The 3500 earns its place in existing cabinets, in applications where its specific cards are proven, and in plants that value a stable, well-understood protection layer over platform novelty.

What Orbit 60 changes: three architecture ideas

Orbit 60 is not simply a faster 3500. Bently markets three architectural concepts, and each has a practical consequence for a plant.

Orbit aXess is the cyber story. Protection and condition monitoring coexist in the same rack and can share the same I/O, but Bently says they function independently, with data moving in one direction only — from the protection side out to the monitoring network — with no digital handshaking. The company describes it as “like a diode, only better,” and says the design is patented. In practice, a compromised business network has no return path into the protection functions through that interface.

Orbit conneX is the process-data story. It provides a bidirectional interface to the control system: protection and condition data go out to the DCS or historian, and process data comes back into the monitoring environment. That is how a monitoring system becomes part of plant-wide asset health rather than a standalone rack.

Orbit Xtend is the layout story. Bridge modules create a virtual digital backplane across chassis over copper or fibre, so I/O can sit near the machine while the rest of the system sits elsewhere. Bently claims more than 50% lower field wiring for a new project, fewer analogue ground loops and less need to send maintenance staff into hazardous areas. This is the single biggest engineering difference from a centralized 3500 rack.

Chassis options and what fits where

The 6U detail matters for retrofits: Bently says it holds more channels than the 3500 but fits in the same size cutout. That removes one of the biggest civil and panel-modification costs of a migration. It does not make the systems electrically interchangeable — wiring, terminations, module positions and configuration all change.

There is a documentation wrinkle worth knowing. The Cordant Orbit 60 page (2026) describes the 7-slot compact as available and the 11-slot compact as “upcoming … (2027).” The older Orbit 60 series page still labels both compact chassis “Available early 2027,” while the current system datasheet already describes both. If an 11-slot chassis is on your critical path, treat 2027 as a planning assumption and get written availability from the factory rather than relying on a web page.

One more constraint: the Integrated System Module, which combines system interface, protection processing and communications in one module, is supported only in the compact 7-slot and 11-slot chassis. It cannot be configured as part of a redundant processor pair and is not currently supported in bridged architectures. Compact does not mean fully equivalent.

Channel capacity: read the fine print

Bently's current marketing says Orbit 60 supports up to 65 dynamic data channels per rack, against an industry average of about 50. That is a meaningful density advantage: fewer racks, less cabinet space and fewer duplicated components.

The system-level number is less settled. The current datasheet says one System Interface Module defines a system of “up to 68 dynamic channels” on its opening page and “up to 64 dynamic channels” four pages later; the older Orbit 60 series page still says “up to 80 dynamic channels.” These are not interchangeable figures, and the difference matters when you are sizing a machine train. Ask Bently or your representative to confirm the channel count for the exact chassis, module mix and datasheet revision you are designing against. A conservative design margin of 15–20% is cheaper than discovering the limit during commissioning.

Cybersecurity: what a data diode proves — and what it doesn't

Orbit 60's strongest differentiator is architectural, not a feature list. The Condition Monitoring Module connects to the business network through a cyber-secure access port, while protection processing stays separate. Bently says the design is “aligned to the IEC 62443-4-2 standard,” with encrypted communications using current TLS standards, PKI-signed firmware images for secure boot and trusted updates, and certificate-based device identity.

That is a credible component-level story, and IEC 62443-4-2 is the right reference for embedded device requirements. But “designed to meet” and “aligned to” are not the same as a certificate for every variant, and a secure component does not make a plant compliant. The remaining work sits with the asset owner: network segmentation, account and patch management, remote-access control, logging, incident response and a software bill of materials.

The data diode is also narrower than it sounds. It protects the inbound path from the monitoring network to the protection functions. It does not stop someone with physical access, a misconfigured engineering laptop, a compromised System 1 server or a supply-chain issue in a module. Those risks are managed by process, not by architecture alone.

Useful questions for any vendor in this category: Which IEC 62443-4-2 certificate exists, for which product variants and firmware versions? How long are security updates provided? Is firmware signed and is secure boot enforced? Are default credentials forced to change? Which TLS versions and cipher suites are supported? Is there a published vulnerability-disclosure process? Bently's answer may be strong; the point is to get it in writing.

3500 vs Orbit 60, side by side

The comparison is Bently's own, published as a 2025 factsheet. Read it as a statement of design intent, not a guarantee of project savings. The 50% wiring and spares numbers depend on machine count, distance, cabinet layout and how much of the existing infrastructure you reuse.

Migrate, hybrid or stay: a decision table

If you migrate: the practical checklist

1. Confirm the cutout and cabinet. The 6U chassis fits the 3500 cutout, but check depth, ventilation, power and cable entry before ordering.
2. Audit the sensor layer. Bently's 3300 XL probe systems are used across its monitoring platforms, but confirm the input module type — negative-powered PAV or positive-voltage PVT — and connector compatibility for each channel.
3. Map the wiring. Distributed I/O changes cable routes and lengths. Reusing home runs may erase the wiring saving that justified the project.
4. Re-validate safety. Orbit 60 is SIL 1 certified and SIL 2 capable; the 3500 is SIL 2-rated. The system rating does not automatically preserve the existing safety function, proof-test interval or stop category.
5. Plan the data path. Decide what goes to System 1, what goes to the DCS or historian, and which side of the data diode each flow uses.
6. Check the channel maths. Size against the confirmed figure for your chassis and module mix, with margin for spare channels and future machines.
7. Pilot one machine train. Run a full production cycle before standardizing. Measure commissioning effort, alarm quality and spares availability, not just installation cost.

Spares planning for a mixed fleet

A mixed 3500 and Orbit 60 estate is the likely end state for most plants, and it changes the spares question. The 3500 is a combination of modules rather than a single article, so record the exact part numbers for power supplies, processors, monitors, relays and communication gateways separately. Firmware versions, configuration backups and option modules belong in the same register.

For the 3500 fleet, the highest-consequence items tend to be the modules that stop a machine train when they fail. Our 3500 monitoring-system category covers the common building blocks: 3500/15 power supplies, the 3500/22M transient data interface, 3500/25 Keyphasor modules, 3500/33 relay modules, 3500/42M proximity and seismic monitors, 3500/50M tachometers, 3500/53 overspeed detection, 3500/60 temperature monitors, 3500/77M pressure monitors and 3500/92 communication gateways.

The sensor layer is shared. A 3300 XL 8 mm proximity probe or an 11 mm 3300 XL Proximitor can outlive the rack it was wired to, which is why probe and extension-cable stock should be planned separately from electronics. The 200350 accelerometer covers casing vibration where proximity probes are not practical. The full Bently Nevada range and the 3300 XL probe category are the fastest way to check availability.

Stock by criticality, not by platform. A redundant fan drive with a local spare is a different risk from a single monitor card on a bottleneck compressor. And do not wait for an EOL notice to capture data: the exact part numbers are stamped on the modules and are much easier to read during a planned outage than during a failure. If a module is not listed, our team can help with cross-reference and lead-time checks.

What to watch next

Four items will decide the pace of migration. First, the 11-slot compact chassis: Bently's page says 2027, and the date will determine whether space-constrained projects can standardize on Orbit 60 or need a 7-slot design. Second, any 3500 lifecycle notice: the trigger is a last-order or spare-parts window, not the launch of a new platform. Third, IEC 62443-4-2 certificate scope: which variants and firmware versions are covered matters more than the logo. Fourth, Orbit 60 firmware and retrofit kits: the 3500 retrofit path becomes cheaper each time Bently publishes a migration guide or adapter set.

For now, the defensible position is neither “replace all 3500s” nor “ignore Orbit 60.” Keep the 3500 fleet supported, fix the network exposure that can be fixed, and use Orbit 60 where its architecture solves a real problem — new machines, distributed layouts, cyber requirements or cabinet constraints. The 3500 earned its installed base; Orbit 60 has to earn each migration.

Frequently asked questions

Is the Bently Nevada 3500 discontinued?

No. Bently Nevada says the 3500 is currently in full product support, with more than 80,000 systems deployed and about 5,000 new systems installed each year. It has not published an end-of-life or last-order date, and it says there is no forced obsolescence programme.

What is the difference between the 3500 and Orbit 60?

The 3500 is a centralized 6U rack-based protection system with application-specific modules and a single TDI for configuration and condition data. Orbit 60 is a centralized or distributed platform with separate system interface and condition-monitoring modules, a one-way data path, higher channel density and configurable spectral resolution.

What chassis options does Orbit 60 offer?

Bently lists a 3U chassis with 19 general-purpose slots, a 6U chassis with 28 slots, a compact 7-slot chassis with 6 slots and a compact 11-slot chassis with 10 slots. The 11-slot compact is listed as upcoming in 2027; confirm availability in writing before it becomes a project dependency.

Does Orbit 60 fit a 3500 rack cutout?

The 6U Orbit 60 chassis is designed to fit the same panel cutout as a 3500 rack and holds more channels. It is not a drop-in replacement: wiring, terminations, module positions, configuration and safety validation all differ.

What is Orbit aXess?

It is Bently's data-isolation architecture. Protection and condition monitoring share a rack but run independently, and data moves one way only from the protection side to the monitoring network, with no digital handshaking. Bently describes it as a patented data-diode design.

Is Orbit 60 certified to IEC 62443?

Bently says the platform is designed to meet IEC 62443-4-2 and aligned to that standard, with TLS encryption, PKI-signed firmware, secure boot and certificate-based device identity. Ask for the certificate scope, product variants and firmware versions rather than assuming every configuration is certified.

Should I stock 3500 spares or migrate now?

Stock by criticality. Capture exact module part numbers, firmware and configuration backups, and hold spares for drives or machine trains whose failure would stop production. Migrate when a new installation, cyber requirement, space constraint or failing rack justifies it — not because a new platform exists.

Sources

• Bently Nevada: “Our commitment to the 3500 monitoring system” (installed base, Minden manufacturing, PCBA refresh, obsolescence management)
• Baker Hughes Cordant: Orbit 60 product page (chassis configurations, 65 channels per rack, aXess, conneX, Xtend)
• Bently Nevada: Orbit 60 Series overview (3500 support statement, chassis notes, SIL certification, 80-channel SIM reference)
• Bently Nevada: Orbit 60 Series System Overview Datasheet 137M5182 Rev. AB (slot counts, IEC 62443-4-2 alignment, SIL 1 certified / SIL 2 capable)
• Bently Nevada: “3500 or Orbit 60 — Which is right for you?” comparison factsheet, 2025
• Bently Nevada: 3500 Machinery Protection Systems (SIL 2-rated, API 670)
• Baker Hughes: Orbit 60 Series launch release, 10 September 2019 (85,000 3500 racks, long-term service commitment)
• Bently Nevada: Approtium hydrogen project in South Korea using Orbit 60, 150+ sensors and System 1