TopView® version 6.24.0 Release

TopView® version 6.24.0 Release

May 20, 2016

TopView OPC/SCADA ● TopView PI ● TopView for Canary Labs ● TopView SQL ● TopView PerfMon

Exele Information Systems, Inc.
Phone: +1 585-385-9740

See the release notes for a full list of changes included in this version

Persist run-time user disable actions to configuration file

Each TopView alarm has a “disabled” setting that is stored as part of the TopView configuration and controls the initial state of the alarm (enabled or disabled) when the TopView Engine starts.
While the TopView Engine is running, users can enable and disable alarms. In previous versions of TopView, the run-time disable state was not persisted to the configuration file. Therefore if the TopView Engine process was stopped and restarted, the last run-time user disable action was lost and the configuration setting was restored.

A new option allows the run-time disable actions by users to be written back to the configuration file. If enabled, the TopView Engine will update the “Disable alarms” setting of the tag/row in the configuration file based on the user actions. Enabling this setting will synchronize the configuration file “Disable alarms” setting with the run-user time disable actions allowing run-time disable actions of users to persist through a hard stop/start of the TopView Engine process.

Persist alarm, acknowledge, and disable state during internal restart

An internal restart of a TopView Engine occurs when the TopView Engine process remains running but reloads the configuration and resumes monitoring and alarming.
During an internal restart, the default behavior of TopView is to reset all alarm and acknowledged states and to “start over” as if the TopView Engine process restarting. This default behavior can result in re-alarming previous alarms and the loss of acknowledged alarms.

If “Persist alarm, acknowledge, and disable state during internal restart” is selected, TopView will attempt to preserve the current alarm, acknowledge, and disable state for all tag/rows that existed before and after the internal restart.

Persisted items include:

  • Alarm state (active/inactive) and alarm start time
  • Alarm “delay in” timers
  • Alarm message
  • Alarm comment/annotation
  • Alarm acknowledged state and time
  • Existing notification escalation steps
  • Alarm disabled and snooze/shelve state

Comment/annotation user and time

The comment time is now part of the stored alarm comment information in SQL Server.

Comment user and comment time are now visible in the following:

  • Alarms View in interactive TopView Engine Window and Remote Viewer
  • Scheduled alarm reports
  • Snapshot reports, alarms
  • Comment time added to details of selected alarm in alarm history details (interactive TopView Engine Window and Remote Viewer)
  • Comment time added to configurable columns in Remote Viewer ad-hoc alarm reports

See the release notes for a full list of changes included in this version