The View and manage alarm definitions page displays the alarm definitions located in the Platform for the search criteria specified, and only for those models to which you have privileges. If you accessed this page from the View and manage models page, the list of alarm definitions includes only the definitions for the model whose Manage Alarms link you selected.
The table shows the following information for each alarm definition:
o Alarm Name -- the name associated with the alarm definition in the Platform
Note: If you see the icon next to the alarm name, it means that the Alarm Disposition has been changed at the asset level.
o Model -- the model associated with the alarm definition
o Description - If entered when the
alarm definition was created using the Axeda Configuration application,
this field shows that text. If the alarm definition was created automatically
when a new instance of the alarm was detected by th Platform and if the
information was provided with the alarm instance, this field typically
shows user-defined information about this alarm.
For an Axeda Gateway or Axeda Connector Agent, the information shown in
this field depends on the main category of alarm (analog, digital, custom,
or dynamic):
§ Analog alarms -- If the alarm is a Value alarm, this field shows the Description entered for the Value Level (LoLo, Low, HiHi, or High) in Axeda® Builder. If this alarm is a Deviation alarm, this field shows the Description entered for the Minor Deviation or Major Deviation in Builder.
§ Digital alarms -- This field shows the text entered for the Message in the configuration of the Digital Alarm Style in Builder.
§ Custom alarms -- This field shows the text entered for the Message in the configuration of the Custom Alarm Style in Builder.
§ Dynamic alarms -- This field shows whatever the driver sent for a message.
For an Axeda® IDM Agent, this field shows the four components of an IDM Agent fault (alarm): code, abstract, description, and detail. The following example shows how they would appear here:
ErrorCode=<fault error code>
Abstract=<fault abstract>
Description=<fault description>
Detail=<fault detail>
If expression rules have been written for the IDM Agents to take this alarm information and generate new alarms, using the information, then this field will show only the information provided in the Description component of the fault.
o Attributes -- indicates whether or not the attributes of the alarm will be stored in the Platform
o Alarm Disposition
-- the disposition of an alarm refers to how the alarm is handled when
it is first detected by the Platform. This column shows the current disposition
setting for an alarm definition for a model. This column displays the
current initial disposition for the model
Empty column - When the Alarm Disposition column is empty, the alarm definition
is Enabled and Unsuppressed. New instances of this alarm are processed
normally - their state is set to "Started", they are stored
in the Platform, and they are available for evaluation by Expression Rules.
Disabled means that all new instances of this alarm are discarded. These
alarm instances are not stored in the Platform nor are they visible in
the Axeda® Service
application. Since they never enter the Platform, rules that are configured
to run when these alarms are detected do not run.
Suppressed means that all new instances of this alarm are set to "Closed"
upon receipt and they are visible only in the Historical Alarms page.
These alarm instances do not appear in the Alarms module on the Asset
dashboards nor do they appear in the Current Alarms page. Like Disabled
alarms, Suppressed alarms are not available for evaluation in Expression
Rules.
Note: With the proper privileges, a Service Technician can suppress alarms for an asset from the Alarms module of the Asset dashboard or from the Alarm Definitions page for the asset in the Axeda Service application. If an alarm that was enabled and unsuppressed at the model level has been suppressed at the asset level. the icon appears next to the alarm name. Changing the disposition at the model level while the override is still on does NOT affect the disposition at the asset level. You must remove the override to change the disposition at the asset level. Refer to View and manage asset alarm definition overrides for information about removing overrides.
o Actions -- The available actions depend on the current disposition. The actions are links that you can click to enable or disable and suppress or un-suppress each alarm for a model. Note that you must have the appropriate privileges to be able to see and use these actions.
From this page, you can select to filter the list of alarm definitions based on search criteria, view more information for an alarm definition, edit an alarm definition and remove alarm definitions.