Train Signal Sighting

Overview 

This Civil Validation and Analysis tool allows for interactive Rail Equipment Sighting Validation from a train drivers perspective based on specific train characteristics against a federated iModel. The analysis is performed against static trackside equipment against a moving driver's eye camera.

 {Figure: Civil Design Validation and Analysis - Train Signal Sighting }

Finding the command

 

In the Civil Frontstage, open the left widget panel and select the Civil Design Validation and Analysis tab.

 

{Figure: Civil Design Validation and Analysis tab within Bentley Infrastructure Cloud}

 

The Summary page presents any existing analysis runs for review. To create a new Analysis, select from the dropdown the desired tool.

 

{Figure: Add New Civil Design Validation}

Adding new will open an associated form allowing entry of required inputs -Run Name, Alignment Selection, Train Characteristics and Sighting Requirements, that all need to be completed prior to analysis.

 

{Figure: Signal Sighting Setup}

 

 

Run Name

The name entered will be visible in the ‘Summary page’

 

Alignment Name

Selection of the Alignment can either be from the graphics or from the drop down list of available Alignments

 

Train Characteristics (Metric or Imperial depending on project settings)

Predefined starting values are provided that will need adjusting based on the train characteristics for

• • Bogie-Driver Distance –the train specific distance the driver sits in front of the forward bogie.
  • Bogie Distance – the train specific distance between the train bogies
  • Eye Height – the assumed required drivers eye height in the cab
  • Left and Right Viewing angles – these will be train cab specific
  • Speed – Allows selection of typical run speeds for the analysis.

 

Sighting Requirements

Provides the run specific list of equipment to be analyzed. An empty template file is provided that creates analysis per row based on the parameters defined in the Sighting Locations file.

 

Sighting Class – the tool supports 3 primary sighting assessments that are specified in the Sighting Locations file for

• • Signal Sighting
  • Speed Signal Sighting
  • Level Crossing

Or All can be run in a single analysis.

 

[Note: a given setup can be duplicated from the add new summary page and edited to adjust values provided to give a comparison between two runs at say different speeds or to check for different train equipment.]

 

Sighting Locations – .CVS file upload

Provides the user defined point list with classifications and sighting requirements for each point being assessed Please note the formatting outlined in the template file

 

• • Object ID - Unique identifier for each object. IDs are based on user specifications and should be unique / not repeated across objects
  • Coordinates (x;y;z) - Target point coordinates (x;y;z) of the object on the viewport ie centre of the stop signal. To obtain the required value use tools like Point Analysis to obtain the Coordinates. Ensure x; y; z are all separated by ";",
  • Time (seconds) - Time in seconds from the start to when the object is reached. Used to determine the total distance for this object.
  • Min. Sighting (%) - Minimum percentage of the distance at which the object must remain visible from the start to the minimum sighting point,
  • Standard Sighting (%) Standard sighting percentage of the object over the defined distance. Represents typical sighting conditions,
  • Close Sighting Distance – is the distance (m or ft) in front of the driver after which the object is no longer visible.
  • Sighting Class – requires definition of sighting class object as ‘signal’; ‘speed’; ‘levelcrossing’ (case sensitive)

 

Analysis Results

The results are presented in tabulated view indicating the status for each point Analysis based on the sighting requirements.

 

{Figure: Analysis Results}

 

The results table presents each object id summary indicating success / failure status and also provides a way of navigating the table and model since it synchronizes the model view to fit the selected objects run results. For the selected object id in the table the sight line will be colour coded for any deficiencies, the details for these deficiencies can be reviewed in the Object Visibility Results table detail by expanding the run results

 

{Figure: Expanded Object Visibility Results

 

To aid understanding of analysis the sight line and any failure can be zoomed to in its own window and the slider used to travel along the sight line for an understanding of any failure.

 

Figure: Object Visibility Results - Zoom to point

 

• Additional Object Visibility options
  • For any given object results the main view can have
• Emphasize - highlight the object locations
• Route Line Mode – adds highlighting to the sight line

 

Figure: Object Visibility Results – View Options

 

Enter Drive Mode – Sets the main view into ‘drive mode’ along the current Object id’s sight line.  

 

Figure: Object Visibility Results – Drive Mode

 

[Note: To aid understanding of analysis the sight line and any failure can be zoomed to in its own window and the slider used to travel along the sight line for an understanding of any failure.]