12.07.2015 Views

C•CURE 800/8000 Software Configuration Guide - Tyco Security ...

C•CURE 800/8000 Software Configuration Guide - Tyco Security ...

C•CURE 800/8000 Software Configuration Guide - Tyco Security ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuring Incident Groups for TrackingAn Incident ID can have multiple causes. If the same event is activated bysome other causes during its activation period, a new Incident ID is notassigned. The event still keeps the Incident ID of the earliest active cause, aslong as the event is still active.Event activations get new Incident IDs when the driver is restarted.Example:If a manual action activates an event from 8 a.m. to 12 p.m and the driveris stopped and restarted at 10 a.m., the event activation at the restart of thedriver gets a new Incident ID. However, if a panel event is no longeractive, but still needs acknowledgement or clearing, it keeps the sameIncident ID after the driver is restarted.Configuring an Incident GroupTo Configure an Incident Group1. Select Configure>Group from the Administration application menu.2. From the sub-menu that appears, select Incident Group. The selectionbrowser for Incident Groups appears, similar to the example shown forInput Groups shown in Figure 25-1 on page 25-3.3. Click New to create a new Incident Group. The Incident Group dialogbox appears, as shown in Figure 25-6 on page 25-15.25–14 C•CURE <strong>800</strong>/<strong>800</strong>0 <strong>Software</strong> <strong>Configuration</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!