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

Group and Team Organization

The numbers are called sequentially in the order of the list, t he call cycle being ended with the first successful call of a final number. A final number is a number which requires a call acknowledgment, automatic or not. In case a call failure, the call is reiterated a number of times configurable (globally or at the level of a specific number), after a time also configurable. After the configured number of unsuccessful attempts, the call is resumed with the following number of the list. A call acknowledgment can be required (globally or at the level of a specific num ber). If the call acknowledgment is not automatic, a timeout for waiting the call acknowledgment can be defined with a number of reiterations of the call if no call acknowledgement is performed in the defined time. The list of the numbers to call at a gi ven time can be automatically established from a weekly program of the call numbers . This program defines the assignment of the call numbers for each day of the week and the public holidays, by time sections of 15 minutes. The program can be put in service (automatic change of the list of call numbers at each new period) or out of service (manual operation). Under automatic operation, it is possible to derogate temporarily from the current configuration by modifying it manually. This configuration will remain valid until the next period. Every operator owns his mail box that stores the last 10 service messages that have been transmitted to him. The operator can consult and erase them, either locally, or at a distance by telephone (audio messages) or from a remote terminal. An operator can be declared as console operator. This attribute allows a list of operators to be defined, these operators being able to receive specific messages via the DDE command " SendConsole" or the API function "AlertSendConsole". The messages transmitted by this way will be only sent if the operator is on -call. If the operator is not on - call, the messages will be stored and transmitted at the beginning of his on -call period, unless they have been acknowledged meanwhile (DDE command "A ckConsole" or function "AlertAckConsole"). In the case of a multi stations management, the operators can be attached to a specific station or to all the stations. Operators with the same name can be defined on different stations. Some operators can be dest ined to receive a full traceability of the alarms ( activations, acknowledgments, returns to normal state). In that case, the call options on event reset and alarm acknowledgment have to be validated for the operators in question.

Several on call groups can be defined, each one corresponding to a group of users having the same localization or competence (fire, security...).

A group is characterized by:

  • An identifier name for the group.
  • An operator list attached to the group.
  • A specific audio signal (local alarm). Operators belonging to a group must have been previously declared in the user file. An operator can simultaneously belong to several groups.

In a group, it is possible to create teams. A team is a set of operators w ho can be called to intervene simultaneously or by rotation (following option at the group level and at the team level) when an alarm concerning the group is detected. By default, a team is created for every operator belonging to the group.

A team is defined by:

  • The name of the team (by default it is the name of the first operator).
  • A color allowing the team to be visually identified in schedule table..
  • The list of operators making up the team. In a team, some operators can be declared as relief operators. By default, these operators are called only when the main operators cannot be reached. The call order of relief operators is the list order. On option, it is possible to call one relief operator for each main operator not reached, in order to guarantee t he intervention of a constant number of operators. A schedule is defined for each group. This one is defined over a year from the previous month of the current month. A team can be programmed by time sections of 15 minutes minimum. A time period can be q ualified as a period of reduced duty , i ndicating that during this time only the important alarms will be immediately treated. A group schedule can be configured very easily with the mouse by positioning teams on the schedule table (by drag and drop operation). The schedule of a group also can be automatically configured from its weekly program. This program defines the assignment of the teams for each day of the week and for the public holidays, by time section of 15 minutes. A team can be programmed in r educe duty or not. This program is applied automatically for every new month. It can be manually forced from the current day and the current hour and for the eleven next months. When a program has been applied in the schedule table, it is still possible to modify it manually. A group can be set in derogation state. In this state, calls concerning this group are redirected to a team of the group designated as a derogation team. If there is no designated team, calls are abandoned or suspended according to op tion. The derogation of a group can be temporized until a limit time or the next change of on-call team. The change of the on-call team can be done through a declared team changeover. When a team executes a team changeover, it immediately starts its on -call period. On option, the team changeover can be mandatory. In this mode, each change of on -call team must be explicitly declared. In case of no changeover in a given time from the scheduled hour, an alarm can be trigged. For a given group, it is possible to designate a relief group. This last will be called on alarm only if there is no active team in the schedule for the corresponding period or in case of failure of the call cycle of the main group. This possibility allows the definition of a secondary on c all process for the group, independent of the main on call process of the group. It is possible to cross the relief groups (a group can be designated as relief group of its own relief group). When calling a group, it is possible to transmit commands to sup ervised application, or any other external application, to signal the starting, the success, the failure or the acknowledgment of the group call.