Automating Interface Configuration Changes in PI System

Automating Interface Configuration Changes in PI System to Resolve Redundant Data Issues

Managing industrial data efficiently is a challenge, especially when faced with infrastructure configurations that don't align with optimal practices. For example, dealing with redundant servers that aren’t properly configured at the OPC UA server level can lead to duplicate data across multiple tags. This blog post discusses a proactive approach to managing such a situation using PI System's capabilities, especially focusing on automated interface configuration changes.

The Problem Scenario

Imagine a scenario where you receive data from two redundant servers, but they aren't configured to recognize each other as redundant at the SCADA level. Therefore, your PI System receives duplicated information across two different sets of tags. This situation is not ideal, as it can lead to inconsistencies and redundancy issues, especially during server maintenance periods.

In our example, it's assumed the plant is a solar farm, allowing a window of downtime (approximately 10 hours) to perform adjustments without impacting operations significantly.

Considering the PI-to-PI Interface

One potential solution to address this is to use a PI-to-PI interface configured in HRONLY (historical recovery) mode to synchronize data from one set of tags to another. However, real-time synchronization may burden the buffer subsystem unnecessarily. By automating the change of the Historical Recovery period and restarting the interface nightly, you can manage duplicate data without real-time synchronization.

Steps to Automate PI Interface Configuration:

• Configuration of PI-to-PI Interface: Set the PI-to-PI interface to HRONLY initially to ensure data isn't duplicated real-time.
• Automating HR Period Adjustments: Write a script to adjust the HR period as needed based on the status of the servers.
• Service Restart Automation: Automate the start and stop of services through Windows Task Scheduler or similar tools to apply changes seamlessly without manual intervention.

An Alternative Approach: Custom Scripting

If you prefer to avoid using PI-to-PI interfaces due to complexity or resource constraints, another approach involves writing custom scripts employing the PI API functions piar_getarcvaluesx and piar_putarcvaluesx. This option may offer greater control and potentially lower overhead, but it requires robust error handling mechanisms to match the PI-to-PI interface's reliability.

Advantages of Using a Third Set of Tags

Another viable method could be using PI Analytics or tag-based analytics (Performance Equations) to populate a third set of tags from the "live" data set. While this approach requires more storage, it allows running operations in real-time, ensuring data consistency and quality over time.

Conclusion

Redundancy in data interfaces, if not handled properly, can lead to significant inefficiencies in data management. Automating the process of managing such configurations in the PI System using scripts and PI tools can ensure data integrity without excessive manual adjustments. While each approach has its pros and cons, choosing the right one depends on your system’s specific needs, available resources, and the criticality of the data involved. By leveraging automation and advanced PI System features, organizations can maintain seamless operations and accurate data reporting, even in complex redundant configurations.

These insights not only resolve data redundancy issues but also enhance your PI System’s operational efficiency, allowing for robust data management strategies tailored to unique industrial needs.