History

Site History can be opened from Alarm Dispatch, Site Data Entry, Quick Call, and Site Lookup. History displays Event Codes and Operator Actions that have occurred on the site.

Parameters can be entered to filter the history. By default, the history displays activity on all Devices on the Site. An Xmit# can be entered to limit the results to one device. An End Date can be entered to go back into history to a specific date. T he results can be filtered to only include Event Codes and not Operator Actions. The results can be filtered by Report Codes. The results can be filtered for a specific area.

History rows are alternate between white and gray (previous days) or light blue (today). The first signal of a new day is indicated with a black line, the first signal of a new alarm is indicated with a red line. If the signal is a new day and a new alarm, the red line will display. A signal that changes the priority of an existing alarm is indicated with an orange line.

The number of history rows returned at one time is defined in Operator Preferences for the user, or stages® Option globally (default to 25). History can be advanced to the next page, or previous page of history results. If a row is highlighted in history, the next page will start with the highlighted row and the previous page will end with the highlighted row. The refresh button will go to the most recent history.

If a history row is linked to an SMS, Email, GPS location, URL, Video, or Audio file, a button will be available to open the related information.

History Purge

Servers can be identified to be purged or to be the database of record for history transactions. Specific report codes can be configured to be purged at a shorter time period than the global rate for history.

History Purge is managed in Utilities > stages™ > History Purge Control.

In History Purge Control – Servers, servers are configured with a purge option and the history server is identified. Servers that are configured with a purge option of ‘Purge’ will be set up to purge history. If a server is identified as the History Server, it will be called when the full History window is viewed (from the History button in Site Data Entry or Alarm Dispatch or the Site Lookup, or in the tab in Quick Call). Recent History in the Alarm Dispatch window will still use the local server data. If the History Server is unreachable, the local server data will be used.

In History Purge – All Events and Operator Actions, the global # Days History is defined. All Events and Operator Actions older than this number of Days will be purged on all servers with the Purge Option of ‘Purge’.

In History Purge – Report Codes, the report codes are listed with an option to enter # Days History. The Number entered here will override the global value for the event codes and operator actions belonging to the report code. For example, Timer Test events can be purged every 90 days, while history is purged every 365 days.