Summary

Navigation Updates

Links between Channels and Loggers

It is now possible to navigate from a channel to the logger which collected the data. This is provided on the channel page with the logger displayed at the bottom of the page:

Open

Assets now show links to manually created alarms

An alarm which is created on a specific channel, will be displayed against any related asset. For example, the following DIP change alarm can be This mapping is based on the channel selected and any associated asset. For example, a DIP change alarm can be created on any channel associated with the asset and it will be displayed in the alarms tab of that asset, under the “Alarms Associated by Channel” heading:

Open

Navigation from playback to loggers

The “Loggers” button on the playback map could erroneously list loggers which were associated with the wrong site.

This has been updated to navigate to the loggers list on the site page:

Old analogue and text data can be automatically highlighted on the replay map

It is possible to indicate data which has not been updated after a set period of time. This will be visible on the map, illustrated by the clock icon as follows:

It is configured by editing the indication and setting the “Warn if data older than” field:

The hover-over text has been updated to show how old the sample data is:

Data Processing

Virtual Channel Improvements

Virtual channels have been updated to better operate where multiple loggers are connected to a single site. Previously a race condition existed which would prevent correct operation. A virtual channel will correctly operate on the proviso that the input channels are all from the same data logger. They will not operate correctly where inputs are from different data loggers.

Track Occupation

All analogue track circuits (e.g. HVI, Reed etc.) have been updated to generate occupation data. The checkboxes which make this optional have been removed. This means that existing and new track circuit assets will generate occupation data. The user interface is updated to remove the following option:

From release date, occupation data will now be generated automatically, and can be seen from the “health | playback” tab as before (note: the alarms, and thus thresholds will not be automatically generated, these are generated from the link highlighted):

This change affects the following track circuit asset types:

• DC Track Circuit

• AF Track Circuit

• Ebi Track 400 Receiver

• HVI Track Circuit

• HXP-3 Track Circuit

• Reed Track Circuit

Assets & Alarms

Alarm raise page improvements and navigation changes

When navigating to an alarm raise any alarm with an asset selected will now navigate to the asset playback page at the time that the alarm was raised, all asset playback pages show alarm raises at the top of the page when there are alarm raises that were triggered at the selected time.

Alarm raises for all other alarms will continue to use the alarm raise page. The alarm raise page has been updated and includes a new navigation header similar to the asset playback page, allowing navigation by activating, unsuppressed or all raises.

Asset Health Score and Alarm

All track circuit assets that support track occupations and RCM tags (Ebitrack 400, HVI, HXP-3 and Reed Track Circuits) now produce an extra “Health Score” channel.
RCM tags are used to mark an occupation as having some negative behaviour, the asset health score is increased whenever a tagged occupation is observed and decreased whenever an untagged occupation is observed.

An Analogue Level Asset Health Alarm can be generated from the asset alarms page.

HXP-3 Alarms

Two new HXP-3 alarms, HXP-3 Poor Shunt and HXP-3 RX High Occupation Rx, have been added to Centrix.

Both alarms work by creating a score channel and listening for specific RCM Tags on the occupations for that asset, e.g. poor shunt tags for the poor shunt alarm.

When these alarms raise, the alarm raises are shown in the asset playback page along with the RCM Tags that triggered them

EBITrack 400 Data Quality RCM Tagging and Alarms

EBI Track 400 assets will now generate RCM tags that highlight poor quality data and potential logger misconfigurations. Alarms can be created which listen for these RCM tags.

The alarm works by creating a score channel and listening for the specific RCM Tags on the asset. The parameters are the same as for the HXP-3 alarms above.

Again, when these alarms raise, the alarm raises are shown in the asset playback page along with the RCM Tags.

Minor amendments and fixed issues

• Links to the Alarm Wizard from an Asset weren’t preselecting the Asset.

• The asset playback page is now used for any alarm raise on an alarm with an asset selected.

Addendum 102.3 Hotfix Release

• Prevented track occupations from being built for deleted assets.