Why Mark VIe Needs Vibration Data
GE Mark VIe controls gas and steam turbines. It manages speed, load, temperature, and protection logic. However, shaft vibration and thrust position are often monitored by Bently Nevada 3500 racks. Bringing this data into Mark VIe improves trip analysis and operator visibility.
First, OPC UA provides a secure, standardized data path. Second, both systems support Ethernet and OPC UA natively. Therefore, integration avoids proprietary hardware gateways and simplifies long-term support.
Step 1: Configure the Bently Nevada 3500 OPC UA Server
Access the 3500 rack through the 3500/92 communication gateway. Enable the OPC UA server and assign a static IP address. Set the endpoint URL, for example:
opc.tcp://bently3500-turbine01:4840
Configure the security policy. Use Basic256Sha256 and certificate authentication for production systems. Create a read-only service account for the Mark VIe OPC UA client. Disable anonymous access.
- Enable OPC UA on the 3500/92 gateway.
- Import the Mark VIe client certificate.
- Set session timeout and subscription limits.
- Expose only turbine-relevant variables.
Step 2: Select Critical Vibration Tags
Bently Nevada 3500 racks expose many variables. For Mark VIe integration, focus on these critical tags:
- Shaft vibration amplitude in mils or micrometers
- Shaft relative position and thrust position
- 1X and 2X vibration vectors
- Probe gap voltage for sensor health
- Alert and Danger alarm status bits
- Channel OK status bits
However, avoid subscribing to raw waveform data unless Mark VIe needs it for advanced protection. Waveform streams consume significant bandwidth. Therefore, limit OPC UA subscriptions to slow-speed monitoring and status variables.
Step 3: Configure the Mark VIe OPC UA Client
In the Mark VIe ToolboxST application, add an OPC UA client connection. Enter the Bently Nevada endpoint URL and credentials. Browse the server namespace and import the selected tags.
Map each OPC UA variable to a Mark VIe signal name. Use a clear naming convention such as BN_TURBINE01_VIB_X. Set subscription rates based on criticality. Use 100 ms for alarm status bits and 1,000 ms for trend values. Finally, add a communication fault bit to detect OPC UA session loss.
Step 4: Build Alarms and Trip Logic
Create Mark VIe alarms for Bently Nevada Alert and Danger status bits. Add operator guidance describing the required response. For example, a Danger alarm on the turbine drive-end bearing should prompt an immediate trip review.
Moreover, log vibration values into the Mark VIe historian. Trend direct vibration and thrust position together with speed and load. This helps engineers diagnose machinery problems after an event. However, do not use OPC UA data for safety-critical protection functions unless the data path is certified for safety.
Step 5: Secure the Communication Path
Place the Bently Nevada and Mark VIe networks on a dedicated control system VLAN. Restrict OPC UA port 4840 access to the Mark VIe application server only. Monitor firewall logs for unauthorized connection attempts.
- Use certificate-based authentication.
- Rotate certificates before expiration.
- Disable unused protocols on the 3500/92 gateway.
- Audit user accounts quarterly.
Finally, test failover behavior. If the Bently Nevada OPC UA server restarts, Mark VIe should reconnect automatically and recover subscriptions without manual steps.
Conclusion & Action Advice
Integrating Bently Nevada 3500 vibration data into GE Mark VIe through OPC UA gives turbine operators better machinery visibility. Configure the 3500 server securely, subscribe to critical tags at appropriate rates, and build clear alarms and trends. Secure the network path and test reconnection behavior to ensure reliable long-term operation.