20111117 WAM reporting for end customers


Published on

WAM - Web-enabled Alarm Management for Invensys System Platform, Archestra, Intouch, Infusion, Foxboro Control Software users.

For more information visit: http://www.ureason.com or http://www.wonderware.com/solution_providers/isv/PartnerProductSpec.asp?ProductID=7730

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • ISA S18 de standaard 17 meri 2011 © UReason
  • ISA S18 de standaard 17 meri 2011 © UReason
  • ISA S18 de standaard 17 meri 2011 © UReason The long term average workload W , that an alarm system imposes on the operator may be calculated as W = R * T With R the average rate at which alarms are presented to an operator And T the average time taken by the operator to respond to an alarm
  • UReason has automated the entire workflow from alarm capture to generating Powerpoint Presentations and Word Documents with standard reports included which are e-mailed on a regular basis (weekly, monthly) to all stakeholders Every stakeholder receives the same figures, which he cannot manipulate to his personal insights OASYS-AM has been chosen over cpmpetitive products for its completeness and data integrity
  • 20111117 WAM reporting for end customers

    1. 1. Introduction
    2. 2. Overview <ul><li>OASYS-AM = WAM (restricted to be used in conjunction with IOM software) </li></ul><ul><li>WAM = Web enabled Alarm Management </li></ul><ul><li>All analysis and reports are available in web browser </li></ul><ul><li>Configuration from web browser </li></ul>Slide
    3. 3. WAM Reporting <ul><li>EEMUA Publication 191 compliant reporting + advanced analysis </li></ul><ul><li>Installs easily and connects to Wonderware’s alarm and event database </li></ul><ul><li>Runs on top of Wonderware SCADA system (WWALMDB) </li></ul><ul><li>Thin client (web browser) access to reports and/or report templates </li></ul><ul><li>Up to 10 concurrent clients </li></ul><ul><li>User administration: two types of users: </li></ul><ul><li>Those who can only access existing (pre-configured) reports (e.g. Alarm Top 10 of past week) </li></ul><ul><li>Those who can access templates and can configure reports </li></ul>Slide Product info Reporting: measure the past behavior of the alarm system and improvements made over time
    4. 4. WAM Reporting <ul><li>Typically on a server in the business network </li></ul><ul><li>Can connect up to n SCADA systems </li></ul><ul><li>Performance depends on the server </li></ul>Slide Product info
    5. 5. WAM Reporting Slide 20 Pre-configured Report types (EEMUA 191 Compliant Reports + advanced
    6. 6. WAM Reporting Slide Built in KPI Setup and Reporting
    7. 7. EEMUA Publication 191 proposed reports <ul><li>Event Totals and Distribution by Priority example </li></ul><ul><li>10 Most Frequent Alarms </li></ul><ul><li>The count of Fleeting alarms </li></ul><ul><li>The Top 10 fleeting alarms </li></ul><ul><li>The Average Alarm Rate report </li></ul><ul><li>Top 10 Average Alarm Rates </li></ul><ul><li>The count of standing alarms </li></ul><ul><li>Top 10 standing alarms </li></ul>
    8. 8. UReason additional reports <ul><li>Top N Bad Actors </li></ul><ul><li>Alarm Improvement Report </li></ul><ul><li>Alarm Summary Report </li></ul><ul><li>Events Totals for Filter </li></ul><ul><li>KPI Reports </li></ul><ul><li>Total and Acknowledged Events report </li></ul><ul><li>Total and Cleared-( Un)acknowledged Events </li></ul><ul><li>Distinct Alarm Summary report </li></ul><ul><li>Top N Consequential Alarm Analysis </li></ul><ul><li>More reports can be included on customer specification, e.g. cause or effect analytics </li></ul>
    9. 9. Event Totals and Distribution by Priority <ul><li>EEMUA 191 A12.9 and A12.4 </li></ul><ul><li>Black line left axis: </li></ul><ul><li>Total alarms per time unit </li></ul><ul><li>Bars and colour scheme (right axis): </li></ul><ul><li>High: target of 5% and no more than 10% </li></ul><ul><li>Medium: target of 15% and no more than 20% </li></ul><ul><li>Low priority alarms: target of 80% and no less than 70% </li></ul>
    10. 10. Top ‘N’ alarms <ul><li>EEMUA 191 A12.6 </li></ul><ul><li>Bad actor analysis </li></ul><ul><li>20% of alarms form  80% frequency </li></ul><ul><li>Used for weekly or bi-weekly bad actor mitigation </li></ul>
    11. 11. The count of Fleeting Alarms <ul><li>Fleeting alarms are alarms which are raised and cleared repeatedly over a period of time and are the cause of nuisance to the operator </li></ul><ul><li>The report provides in the count of alarms fleeting < T and issued to detect specific occurrences where the operator had to deal with fleeting alarms </li></ul>
    12. 12. Top ‘N’ Fleeting Alarms <ul><li>EEMUA 191 4.2.1 </li></ul><ul><li>This report is used to determine which alarm causes most nuisance alarms to the operator. The purpose is to remove these alarms </li></ul>
    13. 13. Average Alarm Rate per ‘T’ <ul><li>EEMUA 191 A12.5 </li></ul><ul><li>Used to determine the alarm system load and compare with the goals and objectives set in the alarm philosophy </li></ul>
    14. 14. Top ‘N’ average alarm rates <ul><li>EEMUA 191 A12.7 </li></ul><ul><li>This report serves to detect situations where the operator had to deal with alarms storms, sometime referred to as alarm flooding. </li></ul>The green line represents the EEMUA Publication 191 target, but can be set to your own (the customer’s) alarm philosophy
    15. 15. The count of standing alarms <ul><li>EEMUA 191 A12.8 </li></ul><ul><li>The report shows the number of Standing Alarms. A high number of standing alarms indicates either that the plant is being badly operated or maintained, or that there are a lot of alarms generated from things that do not require operator attention and which possibly need elimination, suppression, re-prioritization or re-routing) </li></ul>
    16. 16. Top ‘N’ Standing alarms <ul><li>EEMUA 191 A12.8 </li></ul><ul><li>A long-standing alarm means that a process condition, which needs to be alarmed, is valid for a longer period. It is questionable in such cases whether the alarm settings are correct or if the operator was able to do something about the alarm. The purpose of this report is to locate unnecessary information </li></ul>
    17. 17. Total and Acknowledged Events by time-period <ul><li>This report shows whether or not the operator is managing to acknowledge the alarms being generated. It does not reflect that fact that alarms may have been cleared without first being acknowledged. </li></ul><ul><li>This report is also referred to as Event Balance Trends (EBT’s). The EBT can have five values: </li></ul><ul><li>in balance </li></ul><ul><li>excessive notification </li></ul><ul><li>excessive operation </li></ul><ul><li>work overflow </li></ul><ul><li>inadequate operation </li></ul>
    18. 18. Total and Cleared-(Un)acknowledged Events <ul><li>This report shows whether or not the operator is managing to deal with the alarms being generated. Unlike the Total and Acknowledged Events report, this report does reflect the fact that alarms may be cleared without first being acknowledged. </li></ul><ul><li>It can also be used to obtain an idea of Operator Response Time (EEMUA 191 A12.10) </li></ul>
    19. 19. Distinct Alarms Summary Report <ul><li>A Distinct Alarms Summary Report is a list of alarm groups in the system, where a group consists of events with common values for Tag (all alarms for one Tag), Type (all alarms for one Type), Summary Message (all alarms with the same Summary Message) or Severity (all alarms with the same severity) </li></ul>
    20. 20. Alarm Improvement Report <ul><li>Compares different criteria and generates a list of improvement values at the bottom of the report </li></ul>
    21. 21. Alarm Summary Report <ul><li>Gives an overview of the alarms for a given period: </li></ul><ul><ul><li>Total number of alarms (A12.4) </li></ul></ul><ul><ul><li>Distribution by priority (A12.9) </li></ul></ul><ul><ul><li>Average alarm rates (A12.5) </li></ul></ul><ul><ul><li>Acknowledgement times (A12.10) </li></ul></ul><ul><ul><li>Clear times </li></ul></ul>
    22. 22. Event Totals for Filter <ul><li>Shows in a bar graph the same values as the black line in the Event Totals and Distribution By Priority report (EEMUA 191 A12.4) </li></ul><ul><li>Each column is clickable: </li></ul>
    23. 23. KPI Reports <ul><li>Compares different criteria and generates a list of improvement values at the bottom of the report </li></ul><ul><li>Note: KPI report is not to be confused with real-time KPIs per Event Browser </li></ul>
    24. 24. Top N Consequential Alarm Analysis <ul><li>Consequential alarm analysis with automated pattern detection and recommendations </li></ul><ul><li>Discovers alarm patterns and list the top 10 ones sorted by number of occurrences </li></ul><ul><li>Includes load percentage </li></ul><ul><li>Suggests actions </li></ul>
    25. 25. Top N Bad Actors <ul><li>This weekly report identifies bad actors and compares them with previous three months. It also generates recommendations </li></ul>Lists the top 15 bad actors of the week sorted by number of occurrences Includes load percentage Shows how many of the bad actors are fleeting Compares with last 3 months Suggests actions
    26. 26. Configuration <ul><li>Configuration has been made easy and from within the web client </li></ul>
    27. 27. User configuration <ul><li>User management is now available from thin client </li></ul>
    28. 28. WAM Reporting benefits <ul><li>Objective of an alarm improvement program: </li></ul><ul><li>Optimise production, reduction of process upsets & disturbances </li></ul><ul><li>ROI: Complying with state laws/regulations </li></ul><ul><ul><li>Safety/security  potential reduction of insurance premiums </li></ul></ul><ul><ul><li>Preventing upsets  emission reductions, avoiding production losses </li></ul></ul><ul><ul><li>Reducing information overload  less operator stress, avoiding burn out of most valuable resources </li></ul></ul><ul><ul><li>Maintaining licence to operate  avoid destruction of capital, avoid equipment damage </li></ul></ul><ul><li>ROI: Lower cost of ownership </li></ul><ul><ul><li>Good integration with existing IT </li></ul></ul><ul><ul><li>Ties into preventive maintenance </li></ul></ul><ul><ul><li>Ties into asset management & condition monitoring </li></ul></ul><ul><li>Unique selling point: while other tools provide graphs and diagrams, WAM Reporting helps – out of the box - with analysis and improvement </li></ul>
    29. 29. No extra hands needed … <ul><li>UReason has automated the entire workflow from alarm capture to generating PowerPoint Presentations and Word Documents with standard reports included which are e-mailed on a regular basis (weekly, monthly) to all stakeholders </li></ul><ul><li>In this mode, stakeholders come to an improvement meeting to discuss content not the data or the graphs </li></ul><ul><li>It provides consistency in reports over years </li></ul><ul><li>It reduces the burden Alarm Management often imposes on an organization </li></ul>