Skip to main content

Auto eLogger Entries

Contributors:
Tyler EngelhardtTyler Engelhardt

Auto eLogger Entries Overview

Overview​

Auto eLogger Entries is an integration solution that automates the logging of plant events into eLogger by leveraging AVEVA PI System’s Asset Framework (AF), Asset Analytics, and PI Notifications. The integration is designed to trigger log entries in eLogger based on real-time equipment and process events detected in AF, using standard PI tools and the eLogger API. This approach eliminates manual data entry, reduces operator workload, and ensures accurate, timely event logs for compliance and operational analysis.

The integration is deployed and managed using PI Builder and Asset Framework templates, making it repeatable and efficient for both simple and complex sites. No PI Web API or custom JSON configuration is required.

Goals​

  • Automate Manual Logging: Replace manual entry of common plant events (e.g., breaker status changes, pump starts/stops, turbine signals) with automated, real-time logging to eLogger.
  • Improve Operator Focus: Free operators to focus on plant operations, especially during critical periods like startups, shutdowns, and trips, by reducing up to 90% of manual logging tasks.
  • Enhance Data Quality: Ensure logs are accurate, consistent, and timely, supporting compliance and operational analysis.
  • Streamline Integration: Provide a repeatable, efficient deployment process using PI Builder and Asset Framework templates, minimizing setup time for both simple and complex sites.
  • Support Recovery: Leverage PI Notifications’ retry and backfill capabilities to minimize data loss during outages or service disruptions.

Challenges​

  • Exception Deviation & Stepped Values: For low-frequency or stepped PI Points, exception deviation can delay data delivery, resulting in inaccurate timestamps. Disabling exception deviation for certain points may be necessary for real-time accuracy.
  • Digital Set Handling: Digital (enumerated) PI Points require special handling to map PI states to eLogger values.
  • Authentication & Permissions: Integration requires correct permissions for PI Data Archive and Asset Framework. eLogger may not support modern authentication methods like gMSA, complicating secure deployments.
  • Service Disruption Recovery: While PI Notifications can retry and backfill, improper configuration or extended outages can still result in lost or duplicate events. Backfilling must be used carefully to avoid duplicates.
  • Backfill Duplicates: Backfilling notifications after a service disruption will duplicate events within a 72-hour window, due to the way analytics and notifications are configured by AVEVA. Careful planning and manual review may be required to prevent or clean up duplicate log entries.