***Important notes before configuring WIN-911***
Please review the System Requirements page for supported SCADA versions and other helpful information.
*** Important InTouch Notes ***
Please review the InTouch Network Diagrams for recommended architecture examples.
In all cases, a copy of InTouch will need to be installed on the WIN-911 computer (though an InTouch license is not required).
InTouch must be installed as it places dependencies on the PC in order for WIN-911 to connect through Wonderware's Distributed Alarm System (Alarm Manager and SuiteLink).
Be sure to install the same version of InTouch as the InTouch server you will be connecting to. A mismatch in versions may cause connectivity issues.
You can read additional information about nodes and licensing in the Nodes and Licensing Document.
Running WIN-911 on a Remote System or Terminal Services Server
If you are using InTouch across your network or on a Terminal Services server, it is recommended that you review the Remote InTouch Configuration article.
*** WIN-911 Configuration ***
In the WIN-911 Workspace, expand Alarm Sources > InTouch > Add New Application to create one.
Fill out the corresponding fields in WIN-911, to connect to the InTouch application.
Name: Enter any name for your InTouch application.
Node's Computer Name: WIN-911 will connect to the single running Application on this specified Node. If your application is running on the local machine, use localhost. Otherwise, enter its hostname or IP address.
Specify SuiteLink Computer Name: If your SuiteLink node is separate from your WindowViewer node, you will have to provide WIN-911 with the location of the SuiteLink node. Enter the computer name after selecting Yes in the dropdown.
There are two formats to choose from:
- RDShostname: clientIPaddress.
The InTouch data source supports two different methods to bring alarms into WIN-911. Choose one method to manage alarms processed by WIN-911.
1. Subscription Filters
▪ Allows filtering on Tagname, Group or Priority
▪ Subscriptions are less taxing on the processor
▪ Dynamically brings alarms into WIN-911 (Add a new alarm that fits an existing Subscription criteria, that alarm will already be filtered into WIN-911)
2. Import Alarms Tags
▪ Similar import process to Version 7 of WIN-911
▪ Group alarms and point to a specific Notification Policy
It is recommended to use Subscriptions to bring your InTouch alarms into WIN-911, as it is a dynamic process and does not require as much memory.
*** Option 1 ***
Configure Subscriptions - Expand Subscription section and click +Add Subscription
Type in a Name and select which Notification Policy the alarms will be sent to.
Clicking "Add Filter" and using the built-in "AND / OR" options with "Add Criterion" adds another layer of customization to each filter, allowing subscriptions to be as simple or complex as needed.
In this example, the filter will catch any Tag Name that contains the word Tank OR any Tag Name that contains the word Pump.
Click "Save Application" when finished. Alarms will be sent to the configured Notification Policy for the first matching subscription.
NOTE: Only 1 subscription can be matched, and no further processing against other subscriptions will occur.
Create as many subscriptions as needed. Reorder by dragging a line item up or down the list.
NOTE: A "catch all" for all alarms sent to a "Do Not Notify" Policy can be added as the last line item to verify alarms are being sent to WIN-911, you will see them in the Log Viewer. This Subscription filter can be deleted upon confirmation that alarms are being seen in WIN-911.
*** Option 2 ***
Tags - Expand Tags section and click Add Tag (to manually create an alarm) or Import Tags (to import alarms from InTouch).
+Add Tag - Enter a Name of your choice, and the TagName that matches the EXACT syntax of the alarm configured in InTouch. Select the correct Tag Type from the drop down.
Check the box for the correct type of Tag being defined (level alarm, rate of change alarm, or deviation alarm). Enter custom descriptions in desired, assign the alarm Tag to the desired Notification Policy.
Import alarm Tags - After clicking Import Tags, the following message will appear:
Alarm Tags must be exported to a CSV file by performing a DBDump in InTouch - Click Select File and the tags will be imported and stored in the current configuration.
And always... Save your changes!
WIN-911’s InTouch Source supports Watchdog alarms which is an optional part of the configuration. Watchdogs monitor a changing alarm state (or changing tag value) within your Application. If an update is not received within the specified timeout period, the watchdog will become an active alarm. Watchdogs can thus be used to monitor the operation and connectivity of critical devices.
Watchdogs have a configurable Severity from 0 – 1000 inclusively and may also have Labels attached. Watchdogs are configured to go to a specified Notification Policy.
WIN-911 can indicate its operational status by writing a periodically changing value to a tag in your InTouch Tagname Dictionary. We call this function a Heartbeat because it provides a vital-sign to your Application, allowing for corrective action to be taken.
The Heartbeat takes the form of an Integer value that ramps from 0 to 9 on a period of your choosing. After the value reaches 9 it resets to one, and the process is repeated ad infinitum. If the tag fails to update within the specified time, you can assume that WIN-911 is in an impaired state and no longer able to receive alarm event information.
To set up a heartbeat:
Create a tag in your InTouch - Windowmaker > Tools > Tagname Dictionary that is a type of Integer which allows input (i.e. Memory Integer).
Create InTouch QuickScript that monitors the Tag value and triggers recovery procedures/methods when the heartbeat fails.
WIN-911 Workspace > Alarming > InTouch > Applications > Heartbeat > Enable Heartbeat.
Enter the tag name of the InTouch Tag you created in step 1.
Set the heartbeat update rate (in Minutes) with the Write Interval combo-box.
Save your edits in the WIN-911 Workspace.
The Heartbeat Suspension feature is provided as a means of forcing a heartbeat failure in the event of a partial communications failure between your InTouch Application and WIN-911. WIN-911's InTouch Data Source leverages two Wonderware Toolkits. The SuiteLink toolkit provides InTouch with data from WIN-911, like alarm acknowledgment requests and heartbeat data. The Alarm Toolkit provides InTouch alarm information to WIN-911. If the Alarm Toolkit stops responding while SuiteLink remains, your InTouch Application will still be receiving a healthy heartbeat from WIN-911 even while WIN-911 is not receiving alarm events.
To setup heartbeat suspension:
Create a separate tag in your InTouch - Windowmaker > Tools > Tagname Dictionary that allows input. You can use a Memory Discrete, for example.
Set that tag with an alarm condition that cycles in and out of alarm on a periodic basis. In our Memory Discrete example, you can set the alarm state for On.
You will need to determine what amount of time you wish to check WIN-911 for alarm coverage. Let's say every 5 minutes in this scenario.
You will need to provide a way to write data to the tag you created in step 1. You can use InTouch QuickScript or another source of data like OPC. In this example, the data will need to be toggled at a rate that is less than the desired timeout, say every four minutes.
WIN-911 Workspace > Alarming > InTouch > Applications > Heartbeat >Enable Heartbeat Suspension.
Enter the tag name you created in step 1.
Set the suspension timeout (in Minutes) with the Timeout combo box.
Save your edits in the WIN-911 Workspace.
This will result in a dummy-alarm that WIN-911 will be advised of every four minutes. As long as this cycle continues, the heartbeat will continue to update and you can assume that WIN-911 is alive and capable of carrying out its duties. If the suspension timeout elapses without a new alarm being detected, WIN-911 will stop the heartbeat.
In certain instances you need to be able to auto start the WIN-911 InTouch App executable. Simply dropping a copy of the exe into the startup should allow this. If you do have issues with this however you can drop the batch file at the end of this document into your startup folder. This was an issue cause by file execution in newer operating systems, i.e, Windows 10, Server 2016.
Back to Quick Start Homepage >
To create a support case, you will need either your Customer Care Code or your Serial number. You can create a Case online or contact the product support line: (512) 326-1011.