Technical Specifications

FAQ

1. What is the primary function of the 60R/CMM01 Condition Monitoring Module?

The 60R/CMM01 is the dedicated condition monitoring and data acquisition module for the Bently Nevada Orbit 60 system. It collects information generated throughout the Orbit 60 architecture and makes that information available to condition monitoring software such as System 1. The module can process and manage measurements, waveforms, digital transducer information, system status, configuration information, process data, alarms, and event records. Unlike a protection processing module, the CMM is intended primarily for condition monitoring and data management rather than directly performing the primary machinery protection function. Its read-only information architecture also helps keep condition monitoring communications separated from critical protection functions, making it suitable for industrial machinery where monitoring data must be accessed without compromising the protection system.

2. How does the 60R/CMM01 communicate with System 1 software?

The 60R/CMM01 provides an Ethernet-based interface for transferring condition monitoring information to System 1 software. It receives information from the Orbit 60 system through a one-way data stream and then makes the available data accessible to the host condition monitoring environment. Under normal communication conditions, data can be transferred continuously so that System 1 can receive current measurements, waveforms, alarms, events, and other relevant machinery information. The module includes two configurable RJ-45 Ethernet ports, which provide flexibility for network architecture and communication arrangements. Network configuration should take into account the plant’s Ethernet structure, System 1 requirements, cybersecurity policies, IP addressing, and communication redundancy requirements.

3. What type of data can the 60R/CMM01 monitor and store?

The 60R/CMM01 can handle a broad range of information generated by the Orbit 60 system. This includes measurement values, waveform information, digital transducer signals, system control information, system status, configuration data, process variables from external systems, alarms, and event logs. The module is designed to support condition monitoring rather than simply passing a single type of sensor measurement. This allows engineers to analyze machinery operating conditions using multiple sources of information. Historical information can also be buffered in non-volatile storage when communication with the host software is interrupted. Once communication is restored, the stored information can be transferred to the host system, helping reduce the possibility of losing important historical monitoring data during temporary network interruptions.

4. How does the 60R/CMM01 protect machinery protection functions from external network access?

The 60R/CMM01 uses a one-way information architecture in which it listens to information available within the Orbit 60 system without having the ability to write commands back into the protection system through that data path. This separation is important because condition monitoring systems frequently need to communicate with business networks, remote monitoring platforms, or host software, while machinery protection functions must remain isolated from unnecessary external access. The CMM can therefore provide measurement and condition monitoring information to System 1 without becoming a control path for critical protection functions. This architecture helps reduce the potential cybersecurity exposure of the protection system while still allowing engineers and maintenance personnel to access useful machinery data for diagnostics, trending, and predictive maintenance.

5. How many chassis slots does the 60R/CMM01 occupy?

The 60R/CMM01 is a two-slot condition monitoring module in the Orbit 60 system. Its two-slot configuration should be considered when planning the overall chassis layout because the available module capacity must accommodate the CMM together with the required system interface, power, protection, input, output, and communication modules. Multiple CMM modules can also be installed within a suitable Orbit 60 system when additional processing capability, independent System 1 access, or communication redundancy is required. When replacing an existing two-slot CMM01 with a newer single-slot CMM02, the unused slot may require an appropriate blank module depending on the system configuration. Therefore, chassis slot planning should always be completed before selecting or replacing CMM modules.

6. What happens if communication between the 60R/CMM01 and System 1 is interrupted?

If communication with the host System 1 environment is temporarily lost, the 60R/CMM01 can use its non-volatile storage to buffer historical condition monitoring information. This is important because network interruptions do not necessarily mean that all monitoring information generated during the interruption must be discarded. Once communication is restored, buffered information can be transferred to the host software. The exact amount of information that can be retained depends on the available storage and the nature and volume of the data being collected. During troubleshooting, engineers should check Ethernet cabling, connectors, network configuration, IP addressing, communication equipment, and System 1 connectivity. If the network is operating normally but the CMM remains unavailable, the module status and Orbit 60 system configuration should also be investigated.

7. Can multiple 60R/CMM01 modules be installed in one Orbit 60 system?

Yes. Multiple CMM modules can be used when the system requires additional processing capability, independent connections to System 1 clients, or redundant communication arrangements. This can be particularly useful for large machinery monitoring installations where a single condition monitoring interface may not provide the desired communication architecture. Each CMM operates as part of the Orbit 60 system and receives the information made available through the chassis architecture. When multiple CMM modules are planned, engineers should consider chassis slot availability, network architecture, System 1 configuration, Ethernet addressing, data distribution, and maintenance requirements. The number of CMM modules should be selected according to the actual monitoring and communication requirements rather than simply maximizing the available slots.

8. What should be checked when the 60R/CMM01 is not communicating correctly?

Troubleshooting should begin with the physical Ethernet connection and module status. Check the RJ-45 Ethernet cables, connectors, network switches, and link indicators for abnormal conditions. Verify that the configured network parameters, IP address, subnet information, and other communication settings correspond to the plant network and System 1 configuration. The CMM’s connection to the Orbit 60 chassis should also be checked to ensure that the module is correctly seated and receiving the required system power. If communication has been interrupted for an extended period, review whether historical data has been buffered in the module. System 1 configuration should then be checked to confirm that the correct CMM and associated data sources are recognized. If the physical network is healthy but communication remains unavailable, review module status information, system configuration, firmware compatibility, and network security settings before considering replacement of the CMM01.