Page Tree
Other Releases
Alarms are fundamental elements of a SCADA system because they signal when events occur, allowing the system or the human monitor to take appropriate action. Events may occur, for example, when devices encounter abnormal conditions or when parameters fall outside normal ranges. In some cases, the system may be able to automatically provide the desired response, such as sending a corrective signal to a device. In other cases, human monitors need to be informed, by a visual display, an audio signal, or a remote message.Easy Heading Macro headingIndent 40 navigationTitle On this page selector h2,h3 wrapNavigationText true navigationExpandOption disable-expand-collapse
In FactoryStudio, alarms are associated with tags. An alarm may be triggered when a tag reaches a certain value, or when it falls outside a certain rangeWhen tags reach certain values or fall outside certain ranges, alarms maybe be triggered. Alarms may be linked to standard responses such as visual displays or sounds. Alternately, custom code may be provided to create almost any desired response.
Alarms are assigned priorities, so that which allows the most urgent can alarms to be handled if there are multiple alarms ones at the same time. Also, for convenience, alarms are organized in into groups, and each group shares some common properties. In particular, an alarm's group determines if and how the alarm must be acknowledged , and as well as if and for how long it should be recorded in the system log.
To minimize spurious alarmsFor when a system is set up, a time interval may can be established before each alarm may be triggered after system startupthat will give the system a time buffer for any possible spurious alarms, and a minimum time may can be set before the same alarm can be triggered again.
| Table of Contents | ||||
|---|---|---|---|---|
|
Configuring Alarms and Events
Alarm Groups
Every alarm and system event belongs to an alarm group. Alarm groups allow you to configure common settings for a collection of alarms. The A group's settings determine such things as whether or not an acknowledgment is required, whether or not a sound plays, what information is logged, and/or how alarms display.
FactoryStudio comes with several predefined alarm groups that you can usebe used, and/or you can create your own groups as well.
The predefined groups are:
- Warning (Warning messages that do not require acknowledgment)
- Critical (Critical Messages that require acknowledgment)
- AuditTrail (System Events log)
To configure alarm groups:
- Go to Edit > Alarms > Groups.
Enter or select information, as needed.
Column | Description |
Name | Enter a name for the alarm group. The system lets you know if the name is not valid. |
AckRequired | If required, the alarm stays in the alarm list until someone acknowledges the alarm by double-clicking it in the application. |
| ActiveTimeDeadband | Enter a time dead banddeadband that will create a delay from when the alarm happens plus the dead band configured, and will only trigger the alarm after thisafter an alarm occurs. The alarm will trigger again only after the deadband. |
AckTimeout | Defines a timeout to ack for acknowledging the alarm. If the alarm is not acknowledged after the specified time, the alarm becomes active again. |
AutoAckTime | If the alarm is not acknowledged after the specified time, the system acknowledges the alarm. |
Sound | Select the sound that will play when the alarm occurs. |
Show | Select List the list for the alarm to display in the alarm window in the application. |
LogEvents | Select when you want the alarm to be logged to the alarm historian:
|
Colors | Select the colors you want to use for each state:
|
| NotificationMethod | Calls a Script > Class method that trigger triggers a code when the alarm happens. |
Description | Enter a description of this for the alarm group. |
| [Other columns] | For definitions of other columns that are available in many tables, see "see Common Column Definitions". |
Alarms and Events
To configure The first step in configuring an individual alarm , the first step is to identify the tag on which the alarm will be based. It is okay to have multiple alarms associated with the same tag value.
Next, you must define the condition that will trigger the alarm. Possible conditions are based on comparing the value of the tag to two the Limit and the Setpoint, which aretwo specific values that you define called the Limit and the Setpoint. The available conditions are described in the table below.
Additional parameters to that can be configured for each alarm include the group for the alarm, the priority, and the message that will be displayed in the alarm list.
To configure Alarms:
- Go to Edit > Alarms > Items.
Enter or select information, as needed.
Column | Description | ||
TagName | Enter a tag name or click ... to select a tag. | ||
Condition | Select the condition you want to use for this alarm event (see the table below). | ||
Limit | Enter a value for the alarm limit to be used for the condition you selected. | ||
Deadband | Set the deadband, which represents the time that must pass after an alarm before a second alarm can be generated | Sets the deadband value. E.g.: for a Hi alarm item with limit as 100 and deadband as 10, the limit value is now 110; for a Lo alarm item, setting the deadband as 10 means the limit value is 90. | |
Setpoint | Sets | Setpoint | Set a value or a tag to compare for conditions that are based on that you want to compare other values against to determine if there is a deviation. |
SetpointDeadband | Set Sets the deadband for the setpoint when compared with the deviation. | ||
Group | Select the alarm group that should control what happens when this alarm occurs. | ||
| Area | Once created under Alarms > Areas, the areas will be displayed here and will be able to be chosen. | ||
Priority | Enter a priority value that controls where the alarm displays in the list. The higher the number, the higher the priority. You can use the same priority for more than one alarm event. Enter 0 (zero) for alarms to be at the end of the list. | ||
Message | Enter the text that displays in the alarm list. | ||
| [Other columns] | For definitions of other columns that are available in many tables, see "see Common Column Definitions".. |
| Info | ||
|---|---|---|
| ||
It is also possible to set the priority using the PriorityOrder property in CodeBehind or in PropertyWatch. In this case, the LOWER the number, the HIGHER the priority. Default is 0 (highest priority). |
The conditions that can be set are described in the following table:
Hi | Tag >= limit |
HiHi | Tag >= limit (when acknowledged, a Hi alarm is automatically acknowledged to for the same Tag) |
Lo | Tag <= limit |
LoLo | Tag <= limit (when acknowledged, a Lo alarm is automatically acknowledged to for the same Tag) |
RateOfChange | Tag rate of change >= limit |
DeviationMinor | Absolute value (tag - Setpoint) > limit |
DeviationMajor | Absolute value (tag - Setpoint) > limit |
Equal | Tag = limit |
GreaterThan | Tag > limit |
GreaterEqual | Tag >= limit |
LessThan | Tag < limit |
LessEqual | Tag <= limit |
Changed | Tag value changed |
ChangedUp | Tag value increased |
ChangedDown | Tag value decreased |
NotEqual | Tag different from limit |
| Note |
|---|
The limit is a specific value on which the condition is based. The setpoint, if used, may be either a value or another tag. |
General Alarm Options
Two There are two general options that apply to all alarms and should be set that apply to for all alarms. These determine how the system handles alarms during startup and how long alarms and events remain in the alarm historian.
To configure general alarm options:
- Go to Edit > Alarms > Groups.
- In the Initial Disable Time field
, enter a time for how long the system should wait during startup before considering an alarm state to be an alarm. This provides a short time for gives the system time to stabilize before any alarms may can be triggered.Anchor _GoBack _GoBack - In the Life Time field, enter the number of days for how long the alarm historian retains the alarm data, in days.
The Audit Trail
The audit trail provides a log of any selected system events for a specified length of time.
To configure the Audit Trail:
- Go to Edit >Alarms> Groups.
- Click Settings.
- The AuditTrail window displays.
- To enable event logging, select the Enable enable option.
- After selecting Enableenable, select the events you want to log.
- Click OK.
The Alarm Database
The database used to store the Alarms alarms is defined in Edit-Datasets-DBs and is defined by the AlarmHistorian, which is a database connection object with the name AlarmHistorian. By default, when a new project is created, the AlarmHistorian is defined to use the Tatsoft built-in embedded SQL database, TatsoftDB.
The TatsoftDB database should be used for databases up to 10GB. If it is expected you expect to create more than 10GB of data, you should define another SQL database for another Tag Historian Database. In order to define another Database to database that will store the Alarm Historian database, you need to create a new database connection, as explained on in "Configuring Database Connections" on page 105, and and name it AlarmHistorian.
The system does not allow duplicate names, so to create a DB connection with the name AlarmHistorian you must you will need to rename or delete the existing row using that the name.
The When you use the default TatsoftDB as the alarm logging database, the Alarm Module will automatically creates create the required tables in the database. An example of table schema is available opening any file with extension .TAlarm, created when running application using the default TatsoftDB as the alarm logging databaseTo see the table schema for these tables, you can look at any of the database table files, which have the extension TAlarm.
Alarm Visualization
To visualize alarms and events, you can use the built-in object on the in your displays or reports. See section "section Configuring an Alarm Window" for for more information.
Acknowledgments and Subscriptions
Acknowledging Alarms
There are several methods for acknowledging alarms:
- Using Alarm the alarm visualization object in the displays.
- Tag properties.
- Alarm group or Alarm the alarm item's runtime properties.
Acknowledge All Alarms
You can use the <Alarm.AckAll> property that acknowledges all active Alarms alarms.
Acknowledge a Single Alarm or the Highest Priority Alarm
The <Alarm.PriorityItem.UnAck> property allows for the acknowledgment of the highest priority Alarm alarm configured in <Edit.Alarms.Items> the "Priority" column if there is a pending ack alarm.
Acknowledge a Specific Alarm
To acknowledge a specific alarm, use the <Alarm.Items.IDxx.Unack> property. To verify the contents of the IDxx Alarm alarm columns, go to Alarm the alarm item and add the ID column (right-click in the table and select "ID").
Subscriptions to Notifications
In order to a apply custom actions action using .NET scripts, you can subscribe to notifications of alarms and events.
These notifications are typically used to send SMS or email warnings, execute custom calculations, add custom notification messages or audio alarms, text-to-speech audio alarms, and to perform any kind of action defined by custom programming.
To subscribe to alarm events, create a method in any Script Class of type Server, with the following prototype:
| No Format |
|---|
void Notification(AlarmEventInfo[] info) |
Finally, select that method on the method in the NotificationMethod column on Edit > Alarms >Groups at the NotificationMethod Column.
The name of the method can vary. What is important is the expected parameters. The AlarmEventInfo structure is defined in the namespace Alarm alarm on the runtime classes reference, http://www.tatsoft.com/help/fs-2014/runtime/index.html.
The Alarm Namespace
The Alarm namespace has the properties of the Alarm alarm server.
The Alarm.Group object has the list of all defined groups and their properties.
The Alarm.Item object has all alarm items and their properties.
The following tag properties are connected with the Alarm alarm module: For example: tag.tagname.Hi: configuration and runtime status of the HI alarm
, similar names for the other alarm types.. The naming of all tag properties follow this same method.
See NamespacesSee "Namespaces" for the complete programming reference on runtime objects.
Overview
Content Tools
Tasks