Explore Orbit 60 protection, condition-monitoring and distributed architecture, then prepare the evidence needed for a machinery-monitoring project.

Protection, condition data and plant context鈥攄esigned as one platform.
Orbit 60 is a scalable machinery-protection and condition-monitoring architecture. A project still begins with assets, sensors, channels and protection requirements.
Bently Nevada positions Orbit 60 as its next-generation platform for continuous online monitoring across critical and plant-wide machinery. Its architecture separates protection processing, condition-monitoring data and external communications into defined system functions.
Know the platform modules before counting channels
System Interface Module
Provides the system access point for configuration and maintenance and defines the connected Orbit 60 system.
Protection Processing Module
Acts as the protection computational engine, deriving machinery measurements and alarm determinations.
Condition Monitoring Module
Supports acquisition and storage of condition data and communication with condition-monitoring software.
Measurement modules
Selection depends on sensor types, machine measurements, channel density and project requirements.
Distributed chassis
Bridge modules can connect chassis so I/O is positioned around the plant architecture.
Process integration
Communication functions exchange defined data with plant systems through supported industrial protocols.
Cybersecurity is architectural, not decorative
Keep alarm decisions independent
Manufacturer information describes designed isolation between protection and condition-monitoring data paths. The project must preserve those trust boundaries.
Move useful data with control
System 1 integration and plant communications should be designed around required data, supported interfaces, access control, patching and lifecycle ownership.
Security also depends on system design, supported versions, configuration, network controls, credentials, monitoring and change management.
Start a project with the asset register
Machine
Turbine, compressor, pump, motor or gearbox criticality.
Measurement
Vibration, position, speed, temperature and process context.
Protection
Alarms, trips, voting, relays and required standards.
Lifecycle
Spares, support, backups, testing, cybersecurity and outages.
Compare the 3500 module guide and the installed-rack planning framework before deciding whether a new Orbit 60 project or continued 3500 support best matches the plant. Browse Moore Automated鈥檚 machinery-protection catalogue and parts enquiry guide for independent sourcing context.
Questions maintenance teams ask
01What is Orbit 60?
It is Bently Nevada鈥檚 machinery-protection and condition-monitoring platform for critical and plant-wide assets, using a modular and distributable architecture.
02Does Orbit 60 replace every 3500 system automatically?
No. Any transition requires an engineered comparison of channels, sensors, wiring, logic, communications, standards and outage constraints.
03What is the role of the CMM?
The Condition Monitoring Module supports condition-data acquisition, storage and communication with condition-monitoring software while the protection architecture remains separately governed.
04Can multiple chassis form one system?
Manufacturer information describes bridge modules for connecting multiple chassis. The topology and supported configuration must be designed from current documentation.
05Is Orbit 60 cybersecurity automatic?
No. Built-in isolation is one architectural control; secure operation also requires correct design, configuration, access control, updates and monitoring.
06What should a project enquiry contain?
Provide the asset list, required measurements, channel count, sensor types, protection and integration needs, project stage, destination and schedule.
Scoping Orbit 60 or supporting an existing 3500 system?
Share the machine, measurement and installed hardware evidence. We can separate parts sourcing from the engineering project decision.
Original article video
The video from the original published article is retained as supplementary company content. It is not a compatibility approval, product test record or lifecycle notice.










Leave Your Comment