earth_america
user_standard Log on
action_search_stroke
earth_america
Log on to rate and give feedback 1 2 3 4 5 Log on to rate
0
How to

How to


Products: AS-B, Enterprise Central, Enterprise Server, AS-P, Project Configuration Tool
Functionalities: Alarms
Product version: 3.2, 3.3, 2022
8/15/2022

Configuring Forced User Actions

You force the user to perform certain actions when working with alarms to ​meet the unique needs of your site.

Show More
action_close

​You can add information when handling a trigger alarm. For example, you can add a comment to the alarm or open an action note that is connected to the alarm. When configuring an alarm, you can force the user to perform different actions when handling a triggered alarm.

You can add several comments and connect cause notes, action notes, and checklist items to a single alarm.

Note:

When an Enterprise Central is connected to an Enterprise Server, all existing checklists, action notes, cause notes, and categories on the Enterprise Server are preserved until you chose to manually synchronize with the parent server.

When an Enterprise Server is connected to a automation server, all existing checklists, action notes, cause notes, and categories on the automation server are removed and replaced with the objects from the Enterprise Server.

Comments

​Use comments to save written information about an alarm. Comments can be added and viewed at any time. A comment is automatically tagged with the user name and a time and date stamp. Useful comments could be the cause of the alarm and how it was taken care of. Information like this can be of great help the next time the same alarm is triggered.

For more information, see Comments .

Cause Notes

A cause note specifies the problem that caused the alarm. Cause notes are grouped by category, with possible alarm causes listed in each group. When an alarm is triggered, you can easily report the causes that triggered the alarm by selecting the predefined choices.

For more information, see Cause Notes .

Action Notes

​Action notes are grouped by category, with possible actions that may correct the problem listed in each category. An action note specifies the actions that you used to correct the problem that caused the alarm.

For more information, see Action Notes .

Checklists

A checklist is a set of steps that guides the user to which action to take when an alarm is triggered. If an alarm goes to normal state, the corresponding checklist is also reset and each step has to be checked again.

For more information, see Checklists .

Summary of User Actions

Table: User Actions

User Action

Description

Use

Comments

User added written information to a triggered alarm.

​Use comments to save written information to an alarm. For example, what triggered the alarm or how was the alarm solved.

Cause Notes

A predefined list of the problems that can have caused the alarm.

Use the cause notes to easily report the cause that triggered the alarm.

Action Notes

A predefined list of possible actions that can correct the problem.

Use the action notes to easily report the actions that were taken to correct the problem that triggered the alarm.

Checklists

A predefined list of steps that guides the user to solve the problem that can have triggered the alarm.

Use the checklist to navigate the user step-by-step to solve the problem.

To configure forced user actions

  1. In WorkStation, in the System Tree pane, select the alarm you want to configure.

  2. In the properties pane, click the User Action tab.

  3. Under Required user action , select the check boxes for Comment , Cause note , and Action note to force the user to act on the listed actions.

  4. In the Changes have been made dialog box, click Yes to save the changes.

See Also

  • User Actions
  • Create Alarm Wizard – User Action Page