Migrating from Bailey SEMAPI to ABB OPC Server: Setting Up the PI OPC DA Interface

For PI System administrators planning to upgrade their ABB DCS data integration, transitioning from a Bailey SEMAPI node to an ABB OPC server is a significant, but manageable, step. This blog outlines the process and key considerations for configuring the PI OPC DA interface to collect real-time data from an ABB OPC server.

Understanding the Transition

The Bailey SEMAPI node is traditionally used for integrating legacy ABB DCS systems with PI via a specific protocol interface. With the evolution of DCS systems and connectivity standards, many ABB DCS implementations now support OPC DA, offering a more flexible and widely-supported integration path.

Are ABB OPC Servers Special?

The good news is that from the PI System perspective, there are no ABB-specific adjustments required for connecting to an ABB OPC DA server. The PI Interface for OPC DA is designed to interact with standards-compliant OPC DA servers, regardless of vendor. This means the configuration process remains fundamentally the same, whether your OPC server comes from ABB or another supplier.

Step-by-Step Guide to Setting Up the PI OPC DA Interface

1. Prerequisites

• Ensure the OPC DA server is installed, licensed, and running on your ABB DCS host or an accessible server.
• The PI Interface node must have network access to the OPC server.
• Install the PI Interface for OPC DA on your desired interface node (refer to the official OSIsoft documentation for supported versions).

2. Configure DCOM Settings

OPC DA connectivity relies on Microsoft DCOM for communication. Security and connectivity often depend on correct DCOM configuration between the PI Interface node and the ABB OPC server node. This involves:

• Setting appropriate permissions for the account running the PI OPC DA interface
• Configuring firewall rules to permit DCOM traffic
• Ensuring the system clocks are in sync to prevent authentication errors

3. Adding the OPC Server Reference

During interface configuration:

• Specify the OPC server's ProgID or CLSID using the /OPCServer parameter, e.g., ABB.OPCServer.1 (consult ABB documentation for the exact identifier).
• Provide the network node name if the OPC server is running remotely.

4. Create and Map PI Points

• Use PI Builder or PI SMT to create PI tags that correspond to DCS process variables exposed by the OPC server.
• Set the attribute InstrumentTag or Location4 with the exact OPC ItemID (Tag name) as defined in the ABB OPC server.

5. Test the Data Flow

• Start the PI OPC DA interface service.
• Use PI SMT and the OPC Server Browser to verify successful data updates.
• Check logs for interface errors or connection issues.

Documentation and Resources

For a comprehensive step-by-step walkthrough and troubleshooting guidance, utilize these authoritative resources:

• PI Interface for OPC DA Documentation
• PI Interface for OPC DA - YouTube Playlist

Final Thoughts

Migrating from a legacy Bailey SEMAPI interface to ABB OPC DA is a future-focused decision that streamlines both configuration and ongoing support. By following standard PI System procedures for OPC DA integration, you can confidently connect to ABB OPC servers and ensure seamless, reliable PI data collection.

If you have unique requirements or encounter ABB-specific OPC configurations, reach out to ABB support or your PI System integrator. Otherwise, leverage the wealth of community and official OSIsoft resources for additional help.