Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

The purpose of the Alarm Dashboard is to give an overview of recent alarms at a glance, without having to utilise the Playback Query function: https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/202670101/Playback#Running-a-Query. Clear, interactive graphs present alarm data ordered by Rule, Section and Time, as well as displaying System Alarms, Queues and Stopped Vehicles.

Contents 


Table of Contents
maxLevel3
indent16px
excludeIntroduction|Contents

Querying

To make an alarm query, three simple options need to be input in the Alarm Query Bar:

Image RemovedImage Added

Carriageway: Select the carriageway that you want to view alarms for. Note that when you filter to a selected carriageway, you will get alarm per section data.

Rule Type: Select the rule type you wish to filter for. You can select more than one rule type. Leaving this filter blank will select all.

Time Period: The fixed time period you want to review the alarm data for. These time periods run from midnight to midnight.

The results are automatically calculated and will be presented in the four graphs below; a Rules bar graph, an Alarm Count (per Sections) line graph, a Top Alarm Sections pie chart and an Alarms by Time line graph. In the example below, the alarm query has been for multiple alarms in Carriageway B over the last 24 hours:

The example illustrated here tells us:

  • There have been 82 Slow alarms in the past 24 hours.

  • Of those alarms, Sections 323 to 326 and 328 had the most with 3 each.

  • There was a spike of alarms around 14:16 on the 2nd November.

Export

You can select the Export button in order to export and save alarm query data:

Image RemovedImage Added

Alarms

It is possible to adjust the alarm results displayed in the Sections and Alarms by Time line graphs by 'deselecting' rules, through clicking on their bars. This will remove that rule's alarm data from the accumulated data displayed in the two line graphs and could be useful if a scale is skewed by a particular rule's alarm count being far higher than any other. A 'deselected' rule is removed from the graph.

Sections

There are two Sections graphs;an alarm count by sectionand Top Alarm Sections.

The alarm count line graph depicts the accumulated alarms per section of the selectedRule Types. The exact number of alarms in each section can be identified by hovering the cursor over the points of the line graph:

The Top Alarm Sections pie chart breaks down the Alarm Count in each section into their comparative proportional values. It also lists the sections into descending order of Alarm Count. Hovering the cursor over individual sectors in the pie chart will highlight which section they represent in the list below:

Alarms by Time

There are three Alarms by Time line graphs: Section Alarms, System Alarms and Queues. Each represents the spread of alarm frequency over time. The default time period will be 24 hours, but a period of up to 72 hours can be selected to be represented in an alarm query. The numbering alarms per specific hour can be identified by hovering the cursor over the points of the line graph:

System Alarms represents the alarms caused by any system fault or failure over the time period selected (the default will be 24 hours). In the example below, a perfect Witness ClearWay™ system has no errors and therefore no alarms:

Queues represent queueing traffic based on the settings of your carriageway, and any stopped vehicle alarms over the time period selected (the default will be 24 hours). The orange lines represent queues and red spots represent stopped vehicle alarms:

Note

If there are unusually few alarms on first glance at the Rules graph, then it may be useful to go straight to the System Alarms graph to see if there have been any errors in the system that have prevented usual rule and alarm generation.


Related Information

Filter by label (Content by label)
showLabelsfalse
cqllabel in ( "alarms" , "dashboard" , "query" , "rules" ) AND label != "advanceguard" and ancestor = "64159770"