Slide 1
WW HMI SCADA-02 Discover the new Alarm improvements delivered in Wonderware System Platform 2014 social.invensys.com Rob Kambach Product Manager Platform and AppServer @InvensysOpsMgmt / #SoftwareRevolution /WonderwareHMI /Wonderware /Group - HMI/Scada/AppServer 2013 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of Invensys or its subsidiaries. All third party trademarks and service marks are the proprietary marks of their respective owners.
Current state around alarming Configured alarms per operator Number of Alarms an operator can theoretically respond to 10 per minute per operator Slide 3
Why did the number of alarms increase? Automation evolution (including fieldbus) brought more accessible information per sensor/actuator Alarms are easily configurable now (no more wired) -> no real cost at engineering or operating time to add alarms People (SI/EPC) tend to believe more is better: nothing can happen without noticing if everything has an attached alarm Slide 4
Typical observed behavior Operator overload leads to : Over-acknowledgement to keep management happy and control room quieter Inhibiting noisy alarms Missing important alarms Texaco Pembroke 1994 Not being able to mitigate in proper time Piper Alpha North sea 1988 Slide 5
Operators have too many alarms to manage What can we do? Slide 6
A set of standards and guidelines EEMUA 191, Alarm systems a guide to design Namur NA 102 Worksheet, Alarm Management NPD YA 711, Principles for alarm design (Norwegian petroleum doctorate slowly adopted throughout Europe as the standard) VDI/VDE Guideline 3699 (process control using monitors) ISA S18.02, Management of alarm systems for the process industry ANSI/ISA 18.2 Management of Alarm Systems for the Process Industries API RP-1167 Alarm Management For Pipeline Systems Slide 7
Our Vision To build a best of class Alarm System that is flexible, robust and complies to all regulations. Slide 8
What did we address so far 2014 release.. - Robustness, we developed a new storage mechanism that is redundant. - Severity, we introduced severities as a new indication 1-4 - Aggregation, we aggregate all active alarms throughout our object model so @ any level you can see the current state. - Introduced a new Animation called alarm border. - Have pre configured alarm controls that go with the default cab files. - Simplified workflow to store alarms from 21 steps to 1 to 2. - Have new alarm widgets to use in graphics and navigation. Slide 9
What is still to come after 2014 - Global Alarm Shelving based on time and operational permissions. - State based suppression. - Flexible messaging - Navigate from alarms to graphics - Extend alarm primitive to the field - Simple KPI index based on EEMUA Slide 10
Storage robustness. Support for - Redundant Engines - Store forward - Redundant Historians - Simplicity, no configuration required. Slide 11
Architecture Historical Configured for Hist_01 Auto_Failover Configured for Hist_02 Double redundant Historical A&E logging, Application Engines and Historians Slide 12
Architecture RT Alarm Hot Backup Manager supports Alarm platforms as providers Alarm Manager increased memory, modifiable through registry Fixed the Microsoft session 0 issue that got introduced in Vista, So now multiple Alarm Managers can run as a service. Slide 13
Simplicity of logging Checkboxes in the Alarm Severity list of the IDE determine if Alarms get logged. If Historian is defined, no further action is needed. The Old Process had 17 21 error prone steps. Changes in Functionality: If an alarm is silenced it will still log state changes to the A2ALMDB New DB A2ALMD to allow easy upgrades DB gets auto created, schema unchanged Supports domain security and OS based security Granular, event messages can be turned off Slide 14
Migration When moving from new to old typical the alarm DB logger logs alarms to the WWALMDB, the new DB is called A2ALMDB. So systems can co exist and alarm logging for new systems is for migrated systems by default turned off. Although the name A2ALMDB is fixed and gets installed by the Historian configurator, the file name is chosen in a way so the node name is part of the DB name. DB Schema did not get changed in this release. Slide 15
Global Priority to Severity mapping One location to change and customizable image Default Alarm Border Icons Slide 16
Global defined styles for alarm colors and borders. One place to change all apps how they represent Alarms Slide 17
Alarm Border animation. Runtime Global Icons Global Styles Auto Configuration for Field_Attributes or objects Slide 18
Simplicity and IT compliance clients Windows integrated security can be used Windows account security (domain based) Slide 19
Updated Clients- Historical Defined with the standard Themes and Styles colors Fonts best Practices HMI Standards Dynamic Filter tabs Group By functionality Slide 20
Update Clients - Runtime Tabbed filtering Actual alarm indicators on Tabs Ack buttons And styles and themes setup as default Slide 21
Severity Indication in Runtime and History mode within the ALM Grids Slide 22
Widgets for Alarming Area Indicator Object or Device Indicator Nav Button Indicator Field Attribute or reference details Slide 23
Platform Alarms customizable. Ability to switch of or change the priority of a Platform comm. alarm Slide 24
Thank you! Open for Questions Slide 25
Slide 26