Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

PI Interface for OPC Alarms and Events

TABLE OF CONTENTS

Configuration checklist

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedOct 20, 2026
  • 2 minute read

After the interface software is installed, use PI ICU to configure the interface instance. A standard configuration would include the following steps.

For more information about standard UniInt interface configurations, see the PI Universal Interface (UniInt) User Guide.

For more information on using PI ICU, see the PI Interface Configuation Utility (PI ICU) User Guide.

Procedure

  1. Create the interface instance on the interface node.

  2. Configure security.

    1. Configure the Windows service.

    2. Restrict access for service accounts.

    3. Create and configure a PI identity, PI trust, and mappings for the interface (application name: PI-OE), the buffering subsystem, and the PI ICU applications.

    4. Configure DCOM settings.

  3. Configure interface startup batch (.bat) file parameters with the minimal settings:

    • Point source

      Use OPCAE or an unused point source of your choice.

    • Scan Class

      Set as desired. Scan class 1 is reserved for advise points.

    • Interface ID

      Use 1 or any unused numeric ID.

  4. Configure the connection to an OPCAE server. From the General tab in the OPCAE tab in PI ICU, add the OPC AE Server name to the Server field. If the server is on another machine, specify that machine or IP address in the Node field.

  5. See Principles of operation on how to verify the interface startup and information about OPC AE server data collection.

  6. Build input points for the interface, and verify that data appears in PI Data Archive. For details on point attributes, see PI Point configuration.

  7. Configure buffering.

  8. Stop the interface, then configure and start buffering. Restart the interface and confirm that the service and buffering restart.

  9. Configure the following optional features:

    • Performance and Health Points

      Performance and health points are PI points that track the status and performance of the interface.

    • Disconnected startup

      Disconnected startup allows the interface to start even if PI Data Archive is not available.

    • UniInt failover

      UniInt failover minimizes data loss by enabling a backup interface instance to collect data if the primary interface instance fails.