TopView® version 6.26.1 Release

TopView® version 6.26.1 Release

February 25, 2017

TopView OPC/SCADA ● TopView OPC A&E ● 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

TopView for OSIsoft PI AF (Asset Framework) release

TopView PIAF is a new TopView data source that enables TopView users to efficiently monitor both PI tags and AF asset/element attributes.

TopView PI, an existing TopView data source based on the PI-SDK, allows users to monitor PI tags from one or more PI Servers.
TopView PIAF, the new data source based on the AF-SDK, allows users to monitor both PI tags and AF element attributes.

TopView PI AF includes

  • Efficient and configurable AF attribute and PI tag data monitoring through point lists, data pipes, or snapshot retrieval
  • Monitoring of AF Expression results through a new AFEXP operation. Expressions can contain both PI tags and element attributes.
  • Asset/element-based placeholders for asset-relative message content
    • %elementpath%: returns full element path for current attribute
    • <%attvalue||attname%> returns the value of attribute “attname” for the same element as the current attribute
    • <%attvalue||attname||formatstring%> returns the value of attribute “attname” for the same element as the current attribute and formatted according to the passed string
  • Data pipe activity monitoring (new events)
    • Admin Tools: displays data pipe activity on Performance screen
    • piaf_dp_count: status tag and performance counter contains the number of arriving events since last update

TopView PIAF requires the AF-SDK v (PI AF Client 2016-R2-SP1) or later

Alarm Time Zone

Alarm message and notification message content can include date/time information through the use of placeholders. For example, %toa% returns the “time of alarm”.
In previous versions of TopView the date/time placeholders only returned a date/time value in the time zone of the TopView machine.

Alarm Time Zone placeholders address the issue informing users of alarm-related time information (e.g. time of alarm) when the alarm exists in a time zone that is different than the time zone of the TopView machine.

Additional placeholders have been added to return date/time information based on the time zone of the alarm.

Notifications Settings API : Programmatic management of Contacts, Schedules, Global Notification Groups

The Global Contacts, Schedules, and Notification Groups can be managed through the (1) TopView Configurator application and (2) Contacts, Schedules, and Global Settings application.
This release includes a new .Net API that can be used to programmatically manage these items without use of the UI tools.

With this Notifications API, you can, programmatically:

  • List contacts, schedules, and groups
  • Add and remove notification settings
  • Edit and adjust contact information, schedules, and notification groups

Configuration change history (tags and alarm limits)

TopView maintains a change log and backup of all changes to the monitored tags and alarm settings (.tags file per TopView configuration).

A new change history screen is available in the Configurator and Admin Tools that allows the user to query and display the details of all changes to the monitored tags, alarms limits, and related settings.

To access the change history screen:

  • TopView Configurator: click [Tag & Limit changes] above the monitored tag list on the Tags and Limits screen
  • Admin tools: Left menu under “Reports and Audits”, select “Audit Change Log & Backup” then click the “Tag and alarm limit changes” tab

TopView Engine: Performance and Memory improvements

This release includes some significant TopView Engine improvements for alarm processing time and memory usage.

  • TopView Engine process memory: larger configurations (1000 points or more) will see memory usage reduction of around 25%-35% achieved through more efficient alarm condition and state caching.
  • Alarm processing time: the time it takes to determine current alarm state has been reduced by around 40%. The realized improvement will be based on the number of alarms but could be 10’s of milliseconds.


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