Milestone Central 3.7 - Manual (Page 53)

Milestone XProtect 3.7; Administrator’s Manual
Editing Alarm Settings
Alarm settings are general for all alarms on your XProtect Central system; they determine how
long alarms are kept for before they are deleted.
To edit alarm settings, do the following:
1. Right-click Alarms in the Client’s Navigation section, then select Edit Alarm Settings... This
will open the Alarm Settings dialog.
2. You are now able to edit two settings:
• The number of days for which to keep closed alarms, i.e. alarms in the states
Closed, Auto-closed, Ignore, and Reject.
This is normally set to a low number, such as 3 days, but you can define any
number up to 99.999 days, server space permitting. The value 0 can be used to
indicate keep closed alarms indefinitely, server space permitting.
• The number of days for which to keep all other alarms, i.e. alarms not in the states
Closed, Auto-closed, Ignore, and Reject.
This is normally set to a somewhat higher number, such as 30 days, but you can
define any number up to 99.999 days, server space permitting. The value 0 can be
used to indicate keep all other alarms indefinitely, server space permitting.
3. When ready, click OK to save the alarm settings.
IMPORTANT: Alarms often contain video recordings. While the alarm information itself is stored
on the XProtect Central Server, the associated video recordings are fetched from the relevant
surveillance system server when XProtect Central users wish to view them. Therefore, if it is vital
for your organization to have access to video recordings from all your alarms, make sure that video
recordings from relevant cameras are stored on relevant surveillance system servers for at least as
long as you intend to keep alarms on the XProtect Central Server.
Cleaning Up Unwanted Alarms
Occasionally you may find that one of your alarm definitions has generated too many irrelevant
alarms, and that you want to quickly get rid of all these alarms.
When this is the case, the alarm cleanup feature lets quickly you do the following with all alarms
generated on the basis of a selected alarm definition:
• Change their state
• Delete them
Example: An alarm definition based on motion detection has generated too many irrelevant alarms.
First, you edit the alarm definition so it will lead to fewer alarms in the future. Then, what do you
do with the irrelevantly generated alarms? With alarm cleanup, you can delete all alarms generated
by the alarm definition in question. Alternatively, you may decide to keep the irrelevant alarms, but
use alarm cleanup to change their states.
To use alarm cleanup, do the following:
1. In the Client’s Navigation section, right-click the required alarm definition, and select Alarm
Cleanup from the menu that appears:
www.milestonesys.com Page 53 Client: Alarms