Today we released some new functionality within the RailState User Interface.
You will notice a new menu item called Route Analysis. Within you will find the new location for Travel Times, as well as four new tabs. A summary of each is as follows:
- Travel times: Define a route (or route segment) and review the average time (in hours) it took trains to traverse between sensors.
- Travel times scatter plot: See the travel times in scatterplot form, brought to life by the various Group By options, such as Train Type, Train Operator, or Equipment List.
- Travel speeds: See the average speed, in miles per hour, in which trains travelled while they traversed the route.
- Train Order: Within a route, review the order in which we detected a train at the first sensor, compared to the order in which we detected the same train at subsequent sensors. Compare results to gain insight into how rail traffic is being handled in different gateways, relative to other trains or train types.
- Train summary: Quickly see all trains that completed a defined route in table form, with some key summary information and performance metrics, such as the travel time in hours, and average travel speed.
In the interest of reducing some mouse clicks, we have also enhanced our filters throughout the UI with a new 'Select All' filter functionality.
Further below you will find some more explanations and tips regarding the new functionality.
If you have any feedback or suggestions, or would like an overview of any existing features, reach out to support+UI@RailState.com or click this link: Schedule an Overview
Where to Find Route Analysis:
Route Analysis is a new menu item, located to the right of Charts, as pictured below:
Within Route Analysis, you will find tabs for each of the reports, as shown below:
Reminder: To see data within these new tabs, you need to first define a route, or route segment! (See the how-to refresher below)
How-To Refresher - Define a Train Route:
Within the Filters bar on Search and Charts you can specify direction of travel through a site, as well as a site sequence, or combination of both. To use the Route Analysis tabs, you need to define a route, or route segment.
To do so, add your first site via the filter bar, then select the Set Train Route Details option as indicated below:
How-To Refresher - Define a Train Route:
Within the Filters bar on Search and Charts you can specify direction of travel through a site, as well as a site sequence, or combination of both. To use the Route Analysis tabs, you need to define a route, or route segment.
To do so, add your first site via the filter bar, then select the Set Train Route Details option as indicated below:
Continue building the route (or route segment) by defining an end point by selecting Add Site as indicated below, and selecting your next sensor:
.png?width=1120&upscale=true&name=unnamed%20(1).png)
Combine both the sequence and direction (optional) to define a route (or route segment), then press Apply. Results returned will show records that meet each and every criterium defined, in the order they are listed.
Tip: It is best to go broad in these definitions and use filters and other parameters to drill in further.
Reminder: When a route is engaged, to be included in the results, the records must match the defined train route (or route segment) parameter, and have had the same RailState Train ID detected at each sensor. If the Train ID changed between locations then that train will not be included in the 'full route' results.
Route Analysis Overview:
The following is a description of each of the report tabs. In addition to the route (or route segment) filter token we reviewed above, you can further refine views with additional filters, date ranges, etc. Add further insight to your analysis by applying Group By parameters.
Travel Times: Define a route (or route segment) and review the average time (in hours) between sensors. Further modify by working with the aggregation period and chart types.
Travel Times Scatter Plot: Define a route (or route segment) and review the average time (in hours) between sensors in a scatter-plot form.
Important Note: For the two reports above, 'anchor' your Travel Times data by using Group By Sensor Site, and selecting one site along the way, such as the final site. Regardless of what site you choose, you will still see the travel time for the full route or segment transit plotted, but this will eliminate duplicate data points by framing the query to one place in time, such as the day it exited the route.
Travel Speeds: Define a route (or route segment) and review the average speed, in miles per hour, in which the train moved to traverse the route. This is a calculated value based on time and miles travelled.
Train Order: Likely one of the most impactful new tools, define a route (or route segment) and review the order in which we detected a train at the first sensor, compared to the order in which we detected the same train at subsequent sensors. This tool can help provide insight into how rail traffic is being handled in different gateways.
There are three modes, each with distinct differences:
Full route fully within time interval: Based on the route defined in the search token, the chart shows only train records that fully completed the route, and ALL site-sightings were recorded within the specified search timeframe - meaning trains were detected at each of the sensors, and all the detection events occurred within the specified search timeframe.
Full route: Based on the route defined in the search token, the chart shows only train records that fully completed the route, and at least one site-sighting was recorded within the specified search timeframe - meaning trains were detected at at least one of the sensors, and one of the detection events may have occurred outside of the specified search timeframe.
All sightings: Based on the route defined in the search token, the chart shows train records that were seen at any part of the route, and that site-sighting occurred within the specified search timeframe - meaning train records that may not have completed the full route are also shown.
Note: Search tokens apply to all the three views shown, so that you can easily toggle between the three modes.
An example of the Train Order is below, showing the change in train position at start and end of the defined route:
Tip: You can click on any hyperlinked value and go to the Train History. To navigate back, click the BROWSER back button and it will return you to the filtered Train Order tab.
Train Summary: Based on the route defined in the search token, the table shows all trains that completed that route with some key summary information, such as the travel time in hours, and average travel speed, in table form.
Note: Use the 'Customize' button to add, remove, or reorganize columns to get the perfect summary to fit your specific needs.
Tip: Watch for messages: There are some limitations as to the number of records displayed, which if exceeded may result in some missed data. If you receive on-screen warnings, you will want to apply additional filter parameters.
Select-All Filter Functionality:
As a small but surprisingly useful item, we have now added a 'Select All' button on various filters cards throughout the UI. You can now 'select all' then de-select, which may be fewer clicks than clicking on each item individually.
To use, click the 'Select all' button (as shown below) then de-select individual items by clicking on them and navigating away from individual selections (you will see them turn white as you navigate away).
