Why Combine Bently Nevada with DeltaV?
Bently Nevada 3500 systems protect large rotating machinery such as compressors, pumps, and turbines. They monitor shaft vibration, thrust position, and temperature. However, operators often prefer to see all process and machinery data on one HMI.
Emerson DeltaV supports OPC UA natively. First, the 3500 rack exposes data through its OPC server. Second, DeltaV subscribes to that server. Therefore, vibration data appears alongside process variables without expensive custom gateways.
Step 1: Prepare the Bently Nevada 3500 Rack
Verify the rack contains the correct monitor modules. For shaft vibration, use the 3500/42M proximity monitor. For thrust position, use the 3500/45 position monitor. Ensure firmware supports the OPC interface.
- Connect the rack to the plant Ethernet through the 3500/92 communication gateway.
- Assign a static IP address to the gateway.
- Confirm each probe is calibrated and tagged in the rack configuration software.
- Verify that Alert and Danger setpoints match API 670 recommendations.
Moreover, document the channel-to-probe mapping. Future troubleshooting depends on accurate records.
Step 2: Configure the Bently Nevada OPC UA Server
Open the 3500 Rack Configuration Software. Enable the OPC UA server on the 3500/92 gateway. Define the endpoint URL, such as:
opc.tcp://bently3500-gw01:4840
Configure security policy and certificates. For plant internal networks, Basic256Sha256 is typical. Create a read-only user account for DeltaV to limit exposure. Finally, expose only the required variables to reduce server load and attack surface.
Step 3: Map Tags in DeltaV OPC UA Client
In DeltaV Explorer, add an OPC UA client interface. Enter the Bently Nevada endpoint and credentials. Browse the namespace and subscribe to these essential tags:
- Direct vibration amplitude in mils or µm
- Gap voltage for probe integrity
- Alert and Danger alarm status bits
- Channel OK status bit
- Shaft rotational speed in RPM
However, avoid subscribing to every available variable. A large compressor train may have hundreds of points, but the operator HMI only needs the key ones. Therefore, prioritize visibility over completeness.
Step 4: Build DeltaV Alarms and Trends
Create alarm conditions in DeltaV for Alert and Danger booleans. Add priority levels and operator guidance. For example, a Danger alarm on a compressor drive-end bearing should trigger an automatic load reduction workflow.
Use DeltaV trends to plot direct vibration and gap voltage over time. Add a baseline trend captured after commissioning. Finally, configure an asset health display that shows all Bently Nevada points for a given machine train on one screen.
Common Pitfalls to Avoid
- OPC UA certificate expiry breaks the connection after one year.
- Duplicate tag names between DeltaV and Bently Nevada cause import errors.
- Firewall rules block port 4840 between the DeltaV application station and the 3500 gateway.
- Overly fast subscription rates saturate the gateway CPU.
Finally, schedule an annual review of certificates, tag lists, and firewall rules. Machinery protection integration is only reliable if the data path stays healthy.
Conclusion & Action Advice
Integrating Bently Nevada 3500 data into Emerson DeltaV via OPC UA unifies machinery protection and process control. Prepare the 3500 rack carefully, configure the OPC server securely, subscribe only to essential tags, and build meaningful alarms and trends. Keep certificates and tag lists maintained for long-term reliability.