1. Jump to first page Title V Reporting at Wasatch Energy Systems Bart Baker - System Manager at Wasatch Energy Systems Mike Fishman – EXELE Information Systems, Inc.

2. Jump to first page Introduction n The use of PI to meet our environmental reporting requirements n Things to keep in mind when using PI for environmental reporting

3. Jump to first page About Wasatch n Special Service District n Burns municipal solid waste n Generates steam and electricity n Reduces landfill needs

6. Our “Fuel”

8. Jump to first page Reporting Requirements n CFR 40 part 60 n State Title V permit n NOX, SO2, CO, opacity u O2 u Steam n At least two “good” 15 minute averages required to create an hourly average

9. Jump to first page Inops and Exceedances n Inop Is a Loss of Valid Data Due to a Monitoring Equipment Problem n Exceedance Is the Violation of Permitted Concentration, Opacity, or Emission Rate n Each Inop or Exceedance Must Be Recorded and Assigned a Reason and Action

10. Jump to first page Reporting Requirements n Monthly,Quarterly, Semi-annual and Annual Reports n Quarterly EDR – Electronic Data Record u Comma Separated Values u Very Precise and Specific Format u Documents RATAs, CGAs, Exceedances and Inops

11. Jump to first page Our Hardware and Software …

13. Jump to first page CEMS Cabinets n Mirror Imaged n Contain AB PLCs u RSLinx u PI OPC Interface n Provide Backup Via “Timeshare” Mode

15. Jump to first page Software…. n PI – Application Platform n PI ProcessBook n MS Excel/DataLink n VB Based Calculation Package n Manual Entry Package n TopView Alarm Annunciator

16. Jump to first page n Averages and Emissions n Detection of Inops and Exceedances n Approx. 30 VB Equation Modules n Several Hundred PI Tags Receiving Calculation Results Calculations

18. Jump to first page Calculations… n Can stop and restart without loss of context. n Ability to “recalc” for past time periods. n Produces “reminders” to enter reasons and actions.

19. TopView

24. Jump to first page Project Execution n Searched, Interviewed and Selected PI System Integrator. n Installed VPN Capability. n Used Simulators at Start. n Ten Days of Meetings With Integrator. n Were Able to Run New System in Parallel With Old.

25. Jump to first page Summary n A Complex System That Came Together Smoothly u Open Architecture. u Standard, Configurable Tools. n We Have All the Application Code Available to Us. n PI Has Proven to Be an Ideal Platform

26. Jump to first page Things to Keep in Mind….. n PI Server n Averaging n Time Stamping n Data Types n Tag Naming n Tracing n Recalc n Overrides

27. Jump to first page n Use a dedicated PI server if possible. u Avoids interference from other plant activities. u Data custody. u Data retention. n Averaging – u Can’t just average raw values. u Each value needs to be validated. u Store results without compression.

28. Jump to first page n Time stamping – typically at beginning of time period. n Data types – u use full precision for manual input values and calculations. u Use integers to hold “state” data n Tag naming – use structured tag names.

30. Jump to first page n Tracing – aids in development, testing and auditing. n Recalculation – allows Manual Inputs to be re-processed, BAF’s to be reapplied, logic errors to be corrected. n Overrides – provide ability to correct for operations or maintenance errors.

31. Jump to first page Thank You! Q&A