Alarm Handling

The system maintains a full log of any alarm report, including time and date stamping of all stages of the alarm processing.

Alarm reporting can be via the PC console in conjunction with graphical site layouts (including CCTV integration for alarm verification), telephony links, email, SMS messaging etc.

The system includes automatic alarm escalation which is freely user programmable, meaning that any incoming alarm can be reported to a variety of outputs in turn until the alarm is accepted.

Example

An incoming alarm would typically go though the following process (escalation):

1)  The alarm is reported to a PC workstation (or more than one) and a response is expected within say 30 seconds.

2)  The ‘workstation’ fails to respond within the time limit so the call is then routed to one or more DECT handsets using SMS messaging for 30 seconds.

3)  The DECT handsets do not respond, so the alarm is now routed to PSTN or mobile handsets, again using SMS messaging for 30 seconds.

4)  No response from any of the above so either call the public emergency services and/or send out some emails.

The above procedure is fully user programmable and can be unique for each alarm or group of alarms. Voice announcements can substituted for SMS messages. Various options are available including interfaces to pager systems, PA systems, alarm bells, etc.

Lone Worker

Lone Worker monitoring is an extension of the alarm handling and can operate in a variety of ways, but primary proactive or reactive.

For most Lone Worker applications the Lone Worker needs to log onto the system by calling the log in number and entering a PIN number or similar. The handset can be identified either by the PIN number, CLI (CLIP) information, or by DTMF CLI.

When a Lone Worker is logged into the system a check call is returned to the Lone Worker within 30 seconds confirming the ‘log-in’ either via SMS or voice.

Once a Lone Worker is logged in, then the system will ALWAYS make a check call to the lone worker at a pre-determined interval.

The Lone Worker can pre-empt this check call by ‘calling in’ within the system check call period. Normally a Lone Worker check-in call can be accepted by using CLI or similar without the need for a PIN number.

If a check call fails the system can be set to repeat the check call (normally after a short delay) and if that fails an escalation procedure as described for alarm handling will be initiated.

The software allows for any handset connected to the system to initiate an emergency call, normally by a pre-programmed number, which again will invoke an escalation procedure. (note: in many circumstances a 999 call might be more appropriate)

Customisation

Alarm handling systems need to be very flexible. In the brief outline given above each alarm or handset can have its own unique customisation and every significant event for every alarm is recorded in the system log.

On a large system many alarms will have common handling procedures, and the normal way of setting up a large system would be to group alarms into escalation group where a group of alarms all use the same reporting procedure.

The Grovedime Alarm Software is well field proven over a number years and is used by a number of large companies including chemical plants, breweries, and local authorities.

Features

The PC based software can operate unattended and all alarms report via various communication networks including PSTN, Mobile, Email, SMS messaging, LAN, WAN etc.

A Graphical (maps, diagrams etc) interface is available, along with interfacing to CCTV etc for alarm confirmation, location verification via GSM or local PABX.

Lone Worker support as standard.

Stable software and hardware field proven over a number years with large schemes.

Multiple workstations.

Full time and date stamped transaction logging, report generation and analysis.

Each alarm can have a unique configuration and escalation.

Automatic escalation of alarms by user defined procedures.