Laserfiche WebLink
10. It shall be possible to automatically activate any graphic display when an alarm <br />occurs. <br />11. The software shall have built-in support for sending messages automatically and <br />manually to email, alphanumeric and numeric -only pagers. Use of an external <br />program or DDE to communicate alarms to a pager is not allowed. <br />12. Alarm/Event Summary <br />i. The software shall have a standard Alarm/Event Summary display page. The <br />Summary shall have the facility for scrolling up and down the page. <br />ii. The software shall be configurable to enable continuous viewing of a <br />configurable number of the latest alarm and/or event records at the top or <br />bottom of the display screen; or to pop-up the summary via pushbutton, <br />keyboard, mouse selection, or window pull -down menu either automatically or <br />manually. <br />iii. The software shall support automatic retrieval of the summary based on user - <br />defined logic and manual retrieval through a single key -stroke. <br />iv. The Alarm/Event Summary shall allow users to filter alarms such that viewing <br />can be based on alarms only, events only, or both; host server computer <br />assignment, alarm group and/or subgroup assignment; alarm priority ranges; <br />user names; user comments; object name; description; etc. <br />v. It shall be possible to distinguish the current condition of an alarm based on <br />color dependent on whether the alarm is Active Unacknowledged, Active <br />Acknowledged, Acknowledged Normal, or Unacknowledged Normal. <br />vi. The software shall allow for operator comments to be added to the <br />Alarm/Event Summary and permanent alarm log for each record <br />acknowledged. <br />13. Alarm Acknowledgment <br />i. Users shall be able to acknowledge individual alarms, groups of alarms, a <br />filtered list of alarms, and/or all alarms through a single key -stroke. <br />ii. The software shall allow users to filter alarms such that acknowledgment can <br />be based on host server computer(s), alarm group assignment/area, alarm <br />priority ranges, user names, user comments, object name, and description. <br />14. Alarm/Event Printing and Reports <br />i. The software shall support logging of alarms directly to a designated alarm <br />printer as they occur. <br />ii. The software shall include a preconfigured alarm/event report capable of <br />including all alarm and event records stored on disk. <br />iii. The alarm/event report shall also be able to filter records that meet certain <br />criteria such as alarm group and/or subgroup assignment(s), alarm priority <br />ranges, user names, user comments, object name, who acknowledged the <br />alarm, description, and time range. <br />iv. The alarm/event report shall also be configurable to include only a snapshot of <br />current alarms/events, a history of alarms and events for a give time period, or <br />both. <br />v. The alarm/event report shall be able to be printed, or saved into a .CSV file for <br />on -screen evaluation and sorting in third -party packages such as Microsoft <br />Excel or Microsoft Access. <br />3.6 UNATTENDED OPERATION <br />City of Santa Ana Security Management System Specific Requirements <br />Security Management System Project Page 17100-17 <br />SantaAna_SMS_17100 <br />