Introduction

Slide 2

OverviewOASYS-AM = WAM (restricted to be used in conjunction with IOM

software)WAM = Web enabled Alarm ManagementAll analysis and reports are available in web browserConfiguration from web browser

Slide 3

WAM Reporting

EEMUA Publication 191 compliant reporting + advanced analysisInstalls easily and connects to Wonderware’s alarm and event databaseRuns on top of Wonderware SCADA system (WWALMDB)Thin client (web browser) access to reports and/or report templatesUp to 10 concurrent clientsUser administration: two types of users:1. Those who can only access existing (pre-configured) reports (e.g. Alarm Top 10 of past

week)2. Those who can access templates and can configure reports

Product info

Reporting: measure the past behavior of the alarm system and improvements made over time

Slide 4

WAM ReportingProduct info

Typically on a server in the business network

Can connect up to n SCADA systems

Performance depends on the server

WAM Reporting

Slide 5

20 Pre-configured Report types (EEMUA 191 Compliant Reports + advanced

WAM Reporting

Slide 6

Built in KPI Setup and Reporting

EEMUA Publication 191 proposed reports

Event Totals and Distribution by Priority example10 Most Frequent AlarmsThe count of Fleeting alarmsThe Top 10 fleeting alarmsThe Average Alarm Rate reportTop 10 Average Alarm RatesThe count of standing alarmsTop 10 standing alarms

UReason additional reportsTop N Bad ActorsAlarm Improvement ReportAlarm Summary ReportEvents Totals for FilterKPI ReportsTotal and Acknowledged Events

reportTotal and Cleared-

(Un)acknowledged EventsDistinct Alarm Summary report Top N Consequential Alarm

Analysis

More reports can be included on customer specification, e.g. cause or effect analytics

Event Totals and Distribution by Priority

EEMUA 191 A12.9 and A12.4Black line left axis:Total alarms per time unitBars and colour scheme (right axis):High: target of 5% and no more than 10%Medium: target of 15% and no more than 20%Low priority alarms: target of 80% and no less than 70%

Top ‘N’ alarms

EEMUA 191 A12.6

Bad actor analysis

20% of alarms form 80% frequency

Used for weekly or bi-weekly bad actor mitigation

The count of Fleeting Alarms

Fleeting alarms are alarms which are raised and cleared repeatedly over a period of time and are the cause of nuisance to the operator

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

Top ‘N’ Fleeting Alarms

EEMUA 191 4.2.1 This report is used to

determine which alarm causes most nuisance alarms to the operator. The purpose is to remove these alarms

Average Alarm Rate per ‘T’

EEMUA 191 A12.5

Used to determine the alarm system load and compare with the goals and objectives set in the alarm philosophy

Top ‘N’ average alarm rates

EEMUA 191 A12.7

This report serves to detect situations where the operator had to deal with alarms storms, sometime referred to as alarm flooding.

The green line represents the EEMUAPublication 191 target, but can be

set to your own (the customer’s) alarm philosophy

The count of standing alarms

EEMUA 191 A12.8

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)

Top ‘N’ Standing alarms

EEMUA 191 A12.8

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

Total and Acknowledged Events by time-period

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.

This report is also referred to as Event Balance Trends (EBT’s). The EBT can have five values:

in balanceexcessive notificationexcessive operationwork overflowinadequate operation

Total and Cleared-(Un)acknowledged Events

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.

It can also be used to obtain an idea of Operator Response Time (EEMUA 191 A12.10)

Distinct Alarms Summary Report

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)

Alarm Improvement Report

Compares different criteria and generates a list of improvement values at the bottom of the report

Alarm Summary ReportGives an overview of the alarms for a

given period:• Total number of alarms (A12.4)• Distribution by priority (A12.9)• Average alarm rates (A12.5)• Acknowledgement times (A12.10)• Clear times

Event Totals for FilterShows in a bar graph the same values as the black line in the Event Totals and Distribution By

Priority report (EEMUA 191 A12.4)

Each column is clickable:

KPI Reports

Compares different criteria and generates a list of improvement values at the bottom of the report

Note: KPI report is not to be confused with real-time KPIs per Event Browser

Top N Consequential Alarm AnalysisConsequential alarm

analysis with automated pattern detection and recommendations

Discovers alarm patterns and list the top 10 ones sorted by number of occurrences

Includes load percentage

Suggests actions

Top N Bad ActorsThis weekly report identifies bad actors and compares them with previous

three months. It also generates recommendations

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

Configuration

Configuration has been made easy and from within the web client

User configuration

User management is now available from thin client

WAM Reporting benefitsObjective of an alarm improvement program:Optimise production, reduction of process upsets & disturbances

ROI: Complying with state laws/regulations• Safety/security potential reduction of insurance premiums• Preventing upsets emission reductions, avoiding production losses• Reducing information overload less operator stress, avoiding burn out of most valuable resources• Maintaining licence to operate avoid destruction of capital, avoid equipment damage

ROI: Lower cost of ownership• Good integration with existing IT• Ties into preventive maintenance• Ties into asset management & condition monitoring

Unique selling point: while other tools provide graphs and diagrams, WAM Reporting helps – out of the box - with analysis and improvement

No extra hands needed …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

In this mode, stakeholders come to an improvement meeting to discuss content not the data or the graphs

It provides consistency in reportsover years

It reduces the burden Alarm Management often imposes on anorganization