Skip to main content
Version: v3.6 (Not Supported)

User Management

the content of an associated tag. This functionality allows Alert to be informed by the supervised application that the alarm has been masked. In addition, an option allows the masking condition to be reciprocally transmitted to the supervised application when the alarm is masked from Alert. Each time a tag declared as event or alarm changes of s tate (goes to event or return to normal), this change of state is time stamped and recorded in the event log (with possible copy on a line printer). If it is a change to event state, the local operator can be warned by two audio consecutive messages:

  • For alarms, a specific sound is played depending on the associated on call group (if the alarm option "play group tone" is validated and if a sound file is attached to the group).
  • A vocal message identifying the event (if the option "talk voice message" is va lidated and if a vocal message is attached to the event). On option, that message can be repeated in a continuous loop until the alarm acknowledgment. If the tag was declared as alarm, the following operations are done:
  • Updating of the alarm table and alarm history.
  • Updating of indicators (ALARM and ACK) on the alarm status bar.

The list of operators who will be called to intervene (either locally or at a distance) is defined in the user file.

Every operator is defined by:

  • His name and first name.
  • His usual language.
  • A real or virtual type.
  • A numerical operator identifier (ID), 1 to 4 digits.
  • A numerical access code (password), 0 to 4 digits.
  • His user class.
  • An off-duty option with or without substitute.
  • A list of call numbers.
  • Optionally,, a weekly program defining the automatic assignment of his call numbers.
  • An option to be called on event reset.
  • An option to be called on alarm acknowledgment. The name and first name are used to identify the operator during a local access on t he station (login). There are also used for recording in the event log events concerning him (calls, acknowledgments) and for intervention reports. When an operator has to identify himself he can enter his name, his name and his first name, or his name fol lowed by the first letters of his first name. The language of the operator specifies the language to use to transmit him the messages. If a message to transmit is not defined in the user language, it will be searched in the following priority order:

 in the language of the user interface, if it is defined in this language,  in US English, if it is defined in this language,  in the first available language for the message. A real operator corresponds to a physical operator that can intervene locally or at a distance on the installation. A virtual operator corresponds to a communication media, used by several operators: shared pager or cellular phone, telephone set in a common local, etc. When a virtual operator is called in vocal, any real operator who belongs t o the same on call group can identify himself instead of the virtual operator. On the same way, when the virtual operator is a pager, the real operator having received the message can call back in order to acknowledge the call. This functionality allows th e identification of who really took in charge the call transmitted. The operator code (ID), 1 to 4 digits , allows the operator to identify himself during telephonic communications by using the telephonic keyboard (DTMF codes). The access code allows the operator to authenticate himself when he locally logs on to Alert or during the telephonic communications. The user class (or user profile) defines the work environment of the operator. It can be easily configured and defines the menu and toolbar to displa y, the accessible screens and the authorized commands on each of these screens. Three basic classes are defined, each class being associated with an access level between 0 and 2, characterized by the following features:

  • Operation (level 0) The operator does not have access to the configuration of the application and cannot close the application.
  • Control (level 1) The operator has access to the configuration of most parameters (alarms, schedules,), except the configuration of user parameters (user profi les and user database) and environment parameters.
  • System (level 2) Maximal level, the operator has access to all functions of the application. The off-duty option allows an operator to be temporarily removed from the calling procedure without having to modify the schedule tables. An operator can be set on/off duty selectively for each of the on call groups he is belonging to. That option can be set or reset from an external application.. When an operator is set off -duty, another operator can substitute him in each group he his belonging to. The substitute has in charge his duty and those concerning the off -duty operator. A list of call numbers can be configured. Each call number is defined by the type of media to be used (beep, telephone, pager, fax, ema il...) and by the operator's address, in reference to the selected media (dial number, user identifier in paging system, email address...). A call number belonging to the call number list can be designated as an active number. It is the first number that wil l be used. A second number can be designated as relief number. This second number will only be used if the call to the active number did not succeed, after a configurable number of attempts.