Skip to main content
Data Management
PI System
Operational Technology

Strategies for Accurate Totaliser Calculations in PI System

Learn how to address common totaliser calculation challenges in PI System and ensure more accurate flow measurements with expert strategies.

Roshan Soni

4 min read

Strategies for Accurate Totaliser Calculations in PI System

When working with PI System, particularly in time-series data management for monitoring and control systems, users often encounter challenges with calculating accurate totals, especially in the context of flow meters. A common issue arises when totalisers trend inaccurately during periods of no flow, leading to misrepresentative cumulative totals.

Key Challenges in Totaliser Calculations

In the context of a user's PI System experience, we encounter two primary difficulties:

  1. Downward Trending Totalisers: Annual totals decrease erroneously during zero-flow periods.
  2. Unexpected Reset Times: Daily totalisers reset at unanticipated times (e.g., 1 AM instead of midnight).

These issues are often linked to the methodologies employed in calculating time-weighted totals and the nuances present in data interpolation processes.

Addressing Downward Totaliser Trends

The issue of downward trending totalisers is frequently a result of the underlying TagTot function, which calculates totals based on "good" data and scales it by the percentage of this data within the total time frame. This becomes problematic when discrete zero values—common in situations of no flow—affect the calculation.

Solutions for Accurate Totaliser Reporting

Several methods can mitigate inaccuracies in totaliser computations:

  1. Intermediate Attributes:

    • Implement an intermediate attribute that replaces bad data with zero values.
    • This approach ensures that all data considered by the totaliser reflects actual conditions, preventing incorrect downward trends.
  2. Use Alternative Functions:

    • Consider using the Total function in conjunction with RecordedValues, MapData, and FilterData to gain more explicit control over input data treatment.
    • This approach allows a more refined and accurate calculation of totals.
  3. Manual Total Calculation:

    • For more granular control, manually calculate the totals by iteratively reading from and writing to a PI Point.
    • This manual method can be complex but offers heightened precision and data integrity.
  4. PctGood Adjustments:

    • By incorporating the PctGood function, multiply the calculated total by PctGood/100, correcting for discrepancies due to bad data input.
  5. Optimized Triggering:

    • Trigger calculations based on flow meter values rather than on an hourly basis. Further, for syncing issues, set calculations a few seconds or minutes past the hour to include relevant data inputs.
    • Implement constraints like TagTot('att', 't', PrevEvent('att, '*')) to focus strictly on intervals with available data.

Resolving Reset Timing Issues

Totalisers sometimes inexplicably reset at non-standard timings due to differences in time zone settings between the user’s local machine and the PI System analysis server.

  • Ensure that time zone settings are correctly configured and synchronized across all relevant PI components to maintain alignment in system time references.

Conclusion

By addressing these common pitfalls in PI System totaliser calculations, users can achieve more accurate and reliable monitoring outputs, enhancing the effectiveness of data-driven decision-making. Implementing these strategies can significantly improve the precision of total flow measurements, ultimately leading to better operational outcomes within the PI environment.

Tags

#PI System
#Industrial Automation
#Totaliser Calculations
#Data Accuracy
#Flow Measurement

About Roshan Soni

Expert in PI System implementation, industrial automation, and data management. Passionate about helping organizations maximize the value of their process data through innovative solutions and best practices.

Sign in to comment

Join the conversation by signing in to your account.

Comments (0)

No comments yet

Be the first to share your thoughts on this article.

Related Articles

Enhancing PI ProcessBook Trends with Banding and Zones: User Needs, Workarounds, and the Road Ahead

A look at the user demand for trend banding/zoning in OSIsoft PI ProcessBook, current VBA workarounds, UI challenges, and how future PI Vision releases aim to address these visualization needs.

Roshan Soni

Migrating PIAdvCalcFilVal Uptime Calculations from PI DataLink to PI OLEDB

Learn how to translate PI DataLink's PIAdvCalcFilVal advanced calculations—like counting uptime based on conditions—into efficient PI OLEDB SQL queries. Explore three practical approaches using PIAVG, PIINTERP, and PICOunt tables, and get tips for validation and accuracy.

Roshan Soni

Understanding PI Web API WebID Encoding: Can You Generate WebIDs Client-Side?

Curious about how PI Web API generates WebIDs and whether you can encode them client-side using GUIDs or paths? This article explores the encoding mechanisms, current documentation, and best practices for handling WebIDs in your applications.

Roshan Soni