win-911: enterprise edition strategic alarm notification discussion
TRANSCRIPT
Patent Pending. No Use or Disclosure Permitted Without the Written Authorization of Specter Instruments
The Enterprise Edition framework represents a total rethinking of WIN-911 designed for tomorrow’s technologies.
Enterprise is based on modular architecture that provides our customers with unprecedented reliability, security, flexibility, and performance.
The Enterprise system is self-organizing and distributable with no user configuration required.
Supports SQL data storage technologies
The Browser-based user interface can be made available on the local network or beyond and can adapt to different languages and cultures.
Enterprise is runtime all the time
Enterprise Edition
WIN-911 Rockwell Automation® Overview
Enterprise Edition
Rockwell Automation® FactoryTalk® Alarms and Events RSView®
Introducing Strategic Notification.
Strategic Notification: Logically follows your process Allows more efficient use of personnel Allows policies to be executed dynamically Changes with your organization Highly Customizable Easy to configure Scales well with complexity Script free
Escalation logic beyond a simple callout list.
Enterprise Edition
Strategic Notification Tools
Alarms trigger Strategies
Strategies utilize Tactics
Enterprise Edition
Tactics
Specify a Notification workflow A notification workflow
Email Adam
Wait 2 minutes
Contact Bob
Wait 2 minutes
Call Charles
…
Enterprise Edition
Strategies
Composed of Policies
Specify Actions to take at various points
during an alarm lifetime
Actions
Start, Stop, and Restart Tactics
And more…
Enterprise Edition
WIN-911 Enterprise Overview
HOW should notification be escalated
Navigation of Configuration Notification Gateways Connections Roles Labels Tactics Strategies Subscriptions Watchdogs
WHO should be contacted
WHAT alarms should be monitored
Enterprise Edition
Configuration objects are organized logically
The “Contacts” section allows
you to specify WHO will be
contacted by the system. The “Notification” section is
used to define the actions to
perform on an alarm or HOW
notification will take place.
The “Alarming” section defines
WHAT alarms are of interest to
the system
WHO
HOW
WHAT
Example Project
When an alarm occurs, we should alert
Operators & Technicians.
When the alarm changes state, we should notify
all previously notified connections.
When the alarm gets acknowledged, we can
stop notification (except as previously specified).
After 10 minutes, if the alarm is not yet
acknowledged, the Manager on duty.
Enterprise Edition
Open Contacts
Let’s get started!
Again, objects are logically organized
by Notification type.
Open Email
Notification Modules have two basic configurable items.
Gateways specify how to communicate with the outside world.
Connections specify the destination to contact.
Open Gateway
WIN-911 now knows how to send email, but not yet WHO to
send them to. We now need to define our Connections.
Go Back
The web browser’s Back and Forward buttons
allow a familiar method of navigation.
Open Connections
Create One!
Let’s create a Connection for a new
fictional character, Oscar the Operator.
Type “Oscar”
Type an address
In WIN-911, Roles provide a way to organize
Connections to make creation of notification
strategies easier.
Add
Select OK
Oscar is an operator. Let’s label him as such.
Select “HTML Long” The next tab is
used to change
what information
is included in
emails sent to
Oscar and how
those emails look.
Currently Oscar is not allowed to acknowledge
alarms through this Connection.
Let’s change that.
This option would require a specified
password to be included in reply emails.
Select
This option does not require a password.
Now Oscar can simply reply to an alarm
message to acknowledge all the way back into
SCADA software
SCADA will record the acknowledgement actor
as “WIN-911: Oscar” and will also record any
comment which Oscar provides if supported.
Save
Create
Oscar now appears in our
collection of Email Connections.
Let’s make another.
Type “Ted”
Now let’s create a Connection for another
fictional character, Ted the Technician. Like
Oscar, Ted is an operator as well.
Type address
Add Role
Go
Ted is also a Technician, a Role we don’t
currently have defined. We can use the
Forward Navigation Button to navigate to the
Roles workspace so we can define it.
Create
We’re now on the Roles workspace, ready to
create a new Role for Technicians.
Type “Technicians”
Save
We can optionally specify new colors
to help quickly identify this new Role.
Go Back
Our new Role appears as expected.
Add
We’ve returned right where we left off,
editing our new Connection for Ted! Let’s
add that new Role now.
Select OK
Time to tag Ted as a technician.
Save
Notice that Ted is wearing multiple
Roles now. Connections can be tagged
with as many Roles as needed.
We’re free to remove
assigned Roles as well.
Create
Ted now has
some company.
Let’s make one more connection for
Mary the Manager, Oscar and Ted’s boss.
Add Role
Mary doesn’t need to ack
via email. So, there’s no
need to change that default.
Type “Mary”
Type address
Mary is only interested in receiving notification
via email during typical work hours
Select “Standard Hours”
Example Project Overview
We’re ready to look at Labels. Let’s go there
now using the Top Navigation Pane.
Navigation of Configuration Notification Gateways Connections Roles Labels Tactics Strategies Subscriptions Watchdogs
WHO
HOW
WHAT
Enterprise Edition
Select “Alarming”
Then Select “Labels”
Much like Roles provided a way to
tag Connections, Labels provide a
way to categorize Alarms.
We’ll use this new Labels in
the creation of our objects for
Strategic Notification.
So what are these objects?
We’ll start by defining a new Tactic to
capture the action of our first specification:
contact either Technicians or Operators
depending on whether or not the alarm is a
tagged as “Technical”.
Select “Notification”
Then Select “Tactics”
Create
The Tactic workspace allows us to create
a notification workflow. Start by giving
the new Tactic a name. Then switch the
toolbox to the “Decisions” section.
Type “Example”
Switch
We’ll start by dragging and dropping
a new “Label Decision Block” onto the
visual workflow editor.
Drag This
Drop Here
Click or tap the new
block to bring up the
floating action menu.
Click
Click or tap the now
visible Edit button on the
floating action menu.
Click
Select
OK
We need to check if the alarm
is labeled as “Technical”
Now we’ll switch to
the “Notifications”
section of the toolbox.
Switch
We’ll now drag and drop a “Notify All”
block onto the right side of our
previous decision block.
Drag This
Drop Here
Click or tap the
new block to bring
up the floating
action menu.
Click
Now edit the block properties.
Click
Select
OK
Technical alarms should
be sent to Technicians.
Repeat this process on the left branch
to notify “Operators” in this case.
Drag This
Drop Here
By utilizing Roles, we’ve reduced maintenance.
Operators may come and go; this logic remains.
Save
Create
Now let’s create a simple Tactic to
notify Mary the Manager.
We’ll start by dragging and dropping
a new “Notify Block” onto the visual
workflow editor.
Drag This
Drop Here
Name this Tactic and edit the
previously added block.
Type “Mary”
Edit
Select
OK
Save
Example Project Strategy
When an alarm occurs, we should check if it’s a
“Technical” alarm and alert Operators (like
Oscar) or Technicians (like Ted) as appropriate.
When the alarm changes state, we should notify
all previously notified connections.
When the alarm gets acknowledged, we can
stop notification (except as previously specified).
After 10 minutes, if the alarm is not yet
acknowledged, we should notify Mary the
Manager if she is on duty.
Tactic “Example”
Tactic “Mary”
Enterprise Edition
Now that we’ve defined our actions
as Tactics, we’re ready to define our
Strategy for Strategic Notification.
Select “Notification”
Then Select “Strategies”
Create
Type “Station Alarms”
Change
On a New Alarm, we want to run the
logic defined in the “Example” Tactic.
Select
OK
Change
We want to stop upon
Acknowledgement.
Add
Let’s add a policy to notify previously
notified connections of a state change.
Change
We simply change the condition.
Add
Now we just need one more policy to
start the “Mary” Tactic after 10 minutes.
Change
Our condition is “Elapsed Time”.
Change
Our Action is “Start Tactic”.
Change
Select
OK
Change
Now we just need to change 1 hour to
10 minutes on the policy condition.
Modify
OK
Save
We now have the HOW.
Example Project Overview
Navigation of Configuration
Notification Gateways
Connections
Roles
Labels
Tactics
Strategies
Subscriptions
Watchdogs
Now we just have to apply our Strategic
Notification to some alarms from your
SCADA software
WHO
HOW
WHAT
Enterprise Edition
Let’s create a new Source for
Factory Talk Alarms & Events
Create
Enterprise Edition
Enterprise Edition
Enterprise Edition
Enterprise Edition
Enterprise Edition
Enterprise Edition
Enterprise Edition
Enterprise Edition
Reports Create reports in your WIN-911 Enterprise FactoryTalk project using OPC Data Tags
Use a FactoryTalk Alarm to trigger report
Reports can be sent to individuals or groups using Voice, Email or Smartphone Apps
Reports can be requested using Voice, Email or Smartphone Apps
Enterprise Edition
Enterprise Edition
Enterprise Edition
Enterprise Edition
Mobile-911 System Architecture