The Comparison Report - Concurrencies report provides a comparison of the concurrencies in the system as it was just prior to running the interface compared to the contents of the buffer tables loaded by the interface run. It is primarily used with Test Mode interface runs so that the changes that would be made by a Full Mode interface run can be evaluated.

Each changed Dominant/Subordinate route combination that contains concurrencies is displayed in its own row containing the following information:

• Dominant Route Name – This is the name of the dominant route referred to by this row
• Subordinate Route Name – This is the name of the subordinate route referred to by this row
• Current: Concurrencies – This field shows the ranges of measures on the dominant route that corresponds to a range of measures of the subordinate route as it was just prior to running the interface. If the measures in the dominant range go from a greater measure to a lower measure, this means that the subordinate route increases measures in the opposite direction compared to the dominant route.
• Buffer: Concurrencies – This field shows the ranges of measures on the dominant route that corresponds to a range of measures of the subordinate route as it exists in the buffer table that was loaded by the interface. If the measures in the dominant range go from a greater measure to a lower measure, this means the subordinate route increases measures in the opposite direction compared to the dominant route.
• Error Text – This displays any errors that were detected when locating the changed version of the concurrency against the changed version of the LRS. The possible values for this field and their meanings are:
  • This concurrency (Dom side) does not occur on a route – Concurrencies must occur on a route
  • The start of this concurrency (Dom side) (<concurrency start>) occurs before the start of the route (<route start>) – Concurrencies must occur on a route
  • The end of this concurrency (Dom side) (<concurrency end>) occurs after the end of the route (<route end>) – Concurrencies must occur on a route
  • The concurrency (Dom side) (<concurrency start>/<concurrency end>) overlaps a gap (<gap start>/<gap end>) – Concurrencies must occur on a route
  • The start and end measures of this concurrency (Dom side) are the same – this indicates a point concurrency which is meaningless
  • The Dom start measure of this concurrency is null – Start measure is a key field that should never be null
  • The Dom end measure of this concurrency is null – End measure is a key field that should never be null
  • The Dom route name of this concurrency is null – Route name is a key field that should never be null
  • This concurrency (Sub side) does not occur on a route – Concurrencies must occur on a route
  • The start of this concurrency (Sub side) (<concurrency start>) occurs before the start of the route (<route start>) – Concurrencies must occur on a route
  • The end of this concurrency (Sub side) (<concurrency end>) occurs after the end of the route (<route end>) – Concurrencies must occur on a route
  • The concurrency (Sub side) (<concurrency start>/<concurrency end>) overlaps a gap (<gap start>/<gap end>) – Concurrencies must occur on a route
  • The start and end measures of this concurrency (Sub side) are the same – this indicates a point concurrency which is meaningless
  • The Sub start measure of this concurrency is null – Start measure is a key field that should never be null
  • The Sub end measure of this concurrency is null – End measure is a key field that should never be null
  • The Sub route name of this concurrency is null – Route name is a key field that should never be null
  • The start measure of this concurrency (Sub side) is greater than the end measure – Measures for the subordinate side should always go from lower values to higher values; on the Dom side when measures go from higher to lower it indicates that the 2 sides of the concurrency have opposite directions of increasing measures
  • This concurrency (Sub side) overlaps another concurrency (<route name>|<concurrency start>/<concurrency end>) – Subordinate concurrency sections should never overlap as this would indicate that more than one route is dominant for a given section
  • The measure ranges differ by <measure difference> – As both sides of a concurrency record represent the same section of road, it is expected that both sides will have the same length; this indicates an issue with calibration
• Status – This field shows the word Change if the values on the Current LRS fields differ from the values of the LRS Buffer fields. This field shows the word Error if the route did not change but exhibits an error. Otherwise this field is blank. By default, a filter is applied based on this field to show only rows where this field is not null.