Alarm Manager - Alarm Status view

The Alarm Status view lets you manage Alarm jobs and provides information about them. For a detailed description of the columns of its two tables see below.

The Alarm Manager module organizes its tasks in "jobs". Each job defines

• the alarm condition: selectable from all conditions or module-dependent,
• the alarm action: you can select group-dependent actions,
• the condition status (did the condition occur or disappear?),
• an action delay (optional).

Additionally, the following applies:

• If the Alarm module is loaded, its jobs are enabled; if the module is unloaded, the jobs stop executing their tasks.
• You can pause any job by selecting the None action.
• You can define several action settings depending on Alarm groups.
  

  To define a module group, you select specific modules from all modules currently added to the system.

  Tip - If you add new modules to the system later, they are by default members of the All group. For all other groups, make sure to add new modules to the matching group(s).

  Many Trimble products allow one to make use of module groups, when setting up alarm jobs. For all alarm jobs, the same module groups are available. When defining an alarm job, you define for each module group the specific action settings.

The Alarm Manager module can run multiple jobs. For example, to invoke two different actions for the same alarm condition, set up two jobs.

Adding jobs

To add a new job to the list, do one of the following:

• Right-click into the list to open the shortcut menu, and select Add Job,
• Click the module-view button.

Edit the job properties.

Modifying jobs

If you double-click onto a job entry, its Properties dialog lets you edit and customize the settings of the activated job.

Deleting jobs

To delete one or several jobs from the list of jobs, use the standard Windows selection methods to activate the respective jobs, and do one of the following:

• Right-click to open the shortcut menu, and select Delete Job(s).
• Click the module-view button.

Acknowledging alarms

If the Alarm Manager setting Enable alarm acknowledgment is set to Yes, some alarms require being acknowledged, depending on the alarm type and alarm condition. If these alarms are not acknowledged, they will not disappear from the current alarm status table (the lower table), even if their status has changed. Acknowledging alarms does not depend on whether other alarm actions as sending an e-mail have been defined or not.

• The Enable alarm acknowledgment setting only applies to specific alarms. If an alarm type and condition does not allow alarm acknowledgment, or if Enable alarm acknowledgment is set to No, the Acknowledged by field displays Not required.
• Alarms of the Information type must always be acknowledged, if Enable alarm acknowledgment is set to Yes.
• Some alarm conditions require entering a comment.
• If entering a comment is required, the Acknowledgment Requires Comment dialog appears, when you acknowledge the alarm.

To acknowledge alarms do one of the following:

• To acknowledge a specific alarm, double-click its entry in the current alarm status table (the lower table).
• To acknowledge several alarms in one step, which do not require a comment, use the default selecting tools and then select the shortcut menu command Acknowledge all selected non-comment required alarms.

Job settings (upper table)

The upper table displays the job settings. It lets you define and remove any number of alarm jobs.

Current alarm status (lower table)

The lower table displays the current status of alarms. It is empty as long as no alarm is currently raised. If an alarm is raised, you can easily move to the module that has issued the alarm: Select the list item's shortcut menu command Go to module. This opens the module view of the respective module in the main view area.

Tip - If the alarm status that triggers an alarm is linked to the status "Condition disappears", the alarm event will stay at the lower spreadsheet until the "Condition occurs" status occurs. It might be advisable to minimize the use of alarm jobs with the "Condition disappears" setting.