When integrating WIN-911 into an existing InTouch system, there are four recommended architectures to use:
- One InTouch Application with one WIN-911 system
- Redundant InTouch Applications with WIN-911 and a Hot Backup system
- One InTouch RD Server with one WIN-911 system
- Two Standalone InTouch Applications with one WIN-911 system
Each of these architectures requires the use of different combinations of WIN-911 licenses and add-ons. Review the InTouch Network Diagrams for examples of these options.
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.
If you are using InTouch across your network or onTerminal Services server, it is recommended that you review the Remote InTouch Configuration article.
C. Accessing WIN-911
There are two ways to open WIN-911 Workspace for editing:
- Clicking the shortcut that was created in the WIN-911 host's start menu,
- Opening a browser anywhere on the WIN-911 network and entering the WIN-911 Configuration URL.
The WIN-911 Configuration website can be accessed from any computer that is on the WIN-911 network if you have the proper credentials. Simply open a browser and enter the following URL: http://'WIN911 computer name'/WIN911.
Open the WIN-911 configurator and select Alarming > InTouch > Applications.
Select the Application tab.
Application: Enter the name of your InTouch Application
Node 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. The IP address should be static; if using a dynamic address, the user will have to update the address each time the IP changes.
Click the ellipse button to browse to your Node
SuiteLink Node Name: In the event that your InTouch Application network is configured such that the SuiteLink node is separate from the WindowViewer node, you will have to provide WIN-911 with the location of the SuiteLink node. Enter the node in the provided text box after selecting the Specify SuitLink Node Name checkbox.
There are two formats to choose from:
- RDShostname: clientIPaddress.
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 associated with a Strategy for alarm escalation. Configuring strategies are discussed later in this document.
- Name: the friendly name for this Watchdog configuration. Provide a user-friendly name here, as this is the name that will be most prominently displayed in alarm notifications.
- Description: a description of this configuration.
- Tagname: InTouch Tag that WIN-911 will monitor for a changing alarm state (or changing tag value). This field must match the name of the tag as it is configured in InTouch.
- Timeout: the elapsed time (seconds) when WIN-911 will periodically check the tag for activity.
- Strategy: the strategy to execute for the Watchdog alarm.
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.
F.1 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.
F.2 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.
The connection between WIN-911 and InTouch
- Optional: Watchdogs and Heartbeats
- Notifier Gateways
- Notifier Connections (people)
- Tactics and Strategies
- Alarms have been brought Into WIN-911
The next step is to trigger a test alarm and verify it was sent to the proper user. If the alarm does not appear use the WIN-911 Log Viewer to troubleshoot the alarm.
1. Open windows explorer and find the Log Viewer tool.
2. Verify the alarm was sent to the appropriate strategy:
3. Double click the alarm for more information about the dispatch process:
Once you review each tab and verify that the alarm behaved according to your Tactic and Strategy, you have finalized the steps to test and troubleshoot your alarms.