Bently Nevada Orbit 60 conneX: Bidirectional DCS Interface

Bently Nevada’s Orbit 60 condition monitoring platform connects to the rest of the plant through conneX—a bidirectional digital interface that links the machinery protection system directly to the DCS, the process historian, and other automation platforms over a single channel. Unlike earlier Bently Nevada protection systems that only published protection and alarm data one way—out to the process control system—conneX carries data in both directions at once: machine protection values and alarms go out to the control room, while process variables flow back into the condition monitoring environment. The practical result is one interface instead of two, eliminating the separate “collect process data” and “publish protection data” links that older architectures required.
This capability was detailed in Baker Hughes’ Plantwide Condition Monitoring Product Overview, which positions conneX as the integration layer that turns a standalone protection rack into a full participant in plantwide asset health.
What Orbit 60 conneX actually is
conneX is one of three enabling technologies inside Orbit 60 (the other two being aXess for cyber-secure isolation and Xtend for distributed chassis). Where aXess moves data in a single, diode-like direction from protection to monitoring, conneX is explicitly bidirectional.
In Baker Hughes’ own words from the Plantwide CM Product Overview, conneX is “one interface to get all data into the process control world while simultaneously getting thousands of points of process data out of the process control world and into the condition monitoring world.” One interface does both jobs.
The one-way limitation of earlier systems
Previous-generation Bently Nevada machinery protection platforms—most notably the 3500/22M Transient Data Interface (TDI) module in a 3500 rack—connected upward to System 1 for diagnostics, but their relationship with the process control system was effectively one-directional. Protection and alarm values were published out to the DCS or historian; process data did not flow back into the monitoring layer.
That created a structural gap. A plant that wanted both “protection data available in the control room” and “process context available to the protection engineers” typically had to deploy two separate interfaces: one to collect process data for the monitoring environment, and one to publish protection data to the DCS. Each interface was another gateway to license, secure, and maintain.
The classic 3500/System 1 network diagram tells the story: firewalls sat between the System 1 data-acquisition servers and the business network, and historian access was largely a one-way feed. Useful, but not integrated.
How conneX moves data in both directions
conneX collapses the two old links into a single bidirectional channel. The two flows are:
- Outbound (protection → control): alarms, events, overall and envelope values, and dynamic data are published to the DCS, historian, and OPC clients.
- Inbound (control → monitoring): thousands of points of process data—loads, temperatures, flows, setpoints—are retrieved into the condition monitoring environment where they add context to vibration and position signals.
That inbound flow is the part older systems could not do. When a protection engineer opens System 1 or Cordant Asset Health, the process context that explains a vibration trend is already there, because conneX brought it in.
conneX vs aXess vs Xtend: three distinct jobs
All three technologies are part of the same Orbit 60 rack, but they solve different problems. Confusing them is a common mistake, so here is the clean separation:
| Technology | Direction | Job it does | Standard / detail |
|---|---|---|---|
| conneX | Bidirectional | Links Orbit 60 to DCS, historian, and automation platforms | Modbus TCP, EGD, OPC UA, PROFINET |
| aXess | One-way (diode) | Isolates protection network from condition monitoring network | IEC 62443-4-2; no digital handshaking |
| Xtend | Internal | Virtual digital backplane linking chassis up to 2 km apart | Copper or fibre; cuts field wiring |
aXess keeps the protection layer safe; Xtend spreads I/O close to the machine; conneX is what makes Orbit 60 a peer of the control system rather than a silo.
Technical integration and supported protocols
The bidirectional link is implemented in the Orbit 60 Communications Gateway (CGW) module, which provides two Ethernet ports and supports Modbus TCP, EGD (Ethernet Global Data), and PROFINET for two-way interaction with DCS and PLC platforms, with reported update rates as fast as 20 ms. External data exchange is also available through OPC DA/UA.
In the plantwide architecture this stacks cleanly:
Process Control System / Historian ⇄ conneX ⇄ Orbit 60 rack ⇄ aXess ⇄ System 1 / Cordant Asset Health
The 3500/40M Proximitor Monitor and 3500/42M Proximitor/Seismic Monitor modules that older plants know are the spiritual predecessors of these signal paths, but they never carried conneX’s reverse data flow.
Why bidirectional data matters for plantwide condition monitoring
The value of conneX is not the protocol list—it is what the two-way flow unlocks:
- Better diagnostics: protection engineers see process context (load, temperature, flow) inside the same tool as vibration and position, so a developing fault can be correlated with what the machine was actually doing.
- One screen for operators: machinery health appears in the DCS without a separate monitoring workstation, shortening the path from alert to action.
- Lower cost and smaller attack surface: one interface means one gateway to license, secure, and maintain instead of two, which also tightens the cybersecurity scope.
- Fleet-level strategy: bidirectional context feeds System 1 and Cordant Asset Health, supporting proactive maintenance and enterprise-wide asset health programs.
Migrating from 3500 to Orbit 60 conneX
Bently Nevada continues to support the 3500 platform, and the 3500 system guide remains relevant for existing racks. Orbit 60 is the recommended path for new installations, distributed machine trains, and projects with a cybersecurity budget—precisely where conneX removes the integration gaps the 3500 left to the user.
Practically, the 6U Orbit 60 chassis fits the same panel cutout as a 3500 rack, and Bently Nevada offers adapters for a smoother upgrade. The signal chain still starts with proven sensors: 3300 XL proximity probes, 31000-series proximity probes, Proximitor I/O modules, and 32000 metric probe housings all feed the same measurement philosophy that Orbit 60 digitizes and shares through conneX.
Key takeaways
- Orbit 60 conneX is a single bidirectional interface to the DCS, historian, and automation platforms.
- Earlier systems (e.g. 3500/22M TDI) published protection data one way and needed a second interface to pull process data back.
- conneX carries both flows at once—outbound alarms/values and inbound process context.
- It speaks Modbus TCP, EGD, OPC UA, and PROFINET via the CGW module, updating in as little as 20 ms.
- The outcome is plantwide condition monitoring with one interface, lower cost, and a smaller cybersecurity footprint.
For sourcing the underlying hardware, see our Bently Nevada spare parts buying guide.
Frequently asked questions
What is the difference between Orbit conneX and Orbit aXess?
aXess is a one-way, diode-like isolation that keeps the protection network separate from the condition monitoring network (built to IEC 62443-4-2). conneX is bidirectional and links Orbit 60 to external control and historian systems. aXess protects; conneX integrates.
Does Orbit 60 replace the need for a separate historian gateway?
In most cases yes. Because conneX publishes alarms and values to the historian and retrieves process data back into monitoring through the same interface, the separate one-way gateways that 3500-era plants required are no longer needed.
What protocols does Orbit 60 conneX support?
The Communications Gateway (CGW) module supports Modbus TCP, EGD (Ethernet Global Data), and PROFINET for DCS/PLC interaction, with external data exchange also available through OPC DA/UA. Update rates can be as fast as 20 ms.
Can Orbit 60 connect directly to a DCS without System 1?
Yes. conneX provides the DCS/historian link directly from the Orbit 60 rack. System 1 or Cordant Asset Health is used for deeper diagnostics and fleet management, but it is not a prerequisite for the control-system connection.
Is the 3500 still supported if it only publishes one way?
Yes. Bently Nevada continues to support the 3500 platform. The one-way limitation is an architectural characteristic of the older design, not a reason for forced migration; Orbit 60 with conneX is simply the newer option for projects that need bidirectional integration.
