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...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring Incident Groups for TrackingConfiguring Incident Groups for TrackingIncident OverviewC•CURE <strong>800</strong>/<strong>800</strong>0 journal reports track the history of all monitored activitiesand activity messages for inputs (alarm points) and/or events labeled with anIncident ID, if this functionality has been enabled for your system.NOTEBy default, Incident ID functionality is not enabled.To enable Incident ID1. Select the UseIncidentId Entry in the Driver section of the Ccure.inifile, accessed through the Diag Systems utility2. Set the Entry Value to 1 (one).3. Restart the driver if it is running.For more information, see the Diag Systems help.The Incident tab in the Journal Replay dialog box allows you to replay eventmessages and log messages for either of two types of Incident IDs:• A particular incident group• A particular event incidentAn Incident ID is a unique number generated by C•CURE <strong>800</strong>/<strong>800</strong>0. Itconsists of two parts separated by an underscore and is guaranteed to beunique:Example:499796920_2821• The first digits before the underscore are the number of seconds sinceJanuary 1, 1990 (GMT).• The four digits after the underscore are:• For an incident group, the incident group object ID•For an event not in an incident group, the event object ID.C•CURE <strong>800</strong>/<strong>800</strong>0 <strong>Software</strong> <strong>Configuration</strong> <strong>Guide</strong> 25–9

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

Saved successfully!

Ooh no, something went wrong!