Software and Data Solution

RailEyes Dynamics

RailEyes Dynamics blends onboard inertial signals, visual corridor proof, and rail-specific map matching so abnormal motion patterns can be reviewed at the correct track location.

Documented basis

The hardware report states that onboard IMU data collection was validated for detecting train motion during the pilot, creating a foundation for route-linked motion review.

PK: --
Smooth motion
High Speed Train

Route dynamics timeline

Yellow and red segments indicate stronger vibration or abnormal motion windows.

Smooth Elevated Abnormal

Infrastructure-quality signals

Beyond Journey Quality Index: Signals for Infrastructure Excellence

Journey quality metrics are useful, but RailEyes Dynamics is designed to add infrastructure context. When elevated or red abnormal motion records appear at a map-matched track location, they become review signals that can be checked beside visual corridor evidence.

These signals are not automatic fault diagnoses. They help operators flag repeated inconsistencies, identify locations that deserve closer inspection, and investigate conditions that may be difficult to understand from a single image, journey, or field visit.

Over repeated passes, the same PK or track segment can accumulate sensory context across time, temperature, speed, season, and maintenance state. That history can support predictive-maintenance workflows by showing where motion patterns are stable, worsening, or linked to specific operating conditions.

Visual + inertial

A clearer inspection record.

Motion signals gain meaning when reviewers can compare them with the camera view from the same corridor context.

Map-matched

Signals tied to rail location.

Rail-specific matching helps teams review abnormal records against the correct track segment, station area, or PK reference.

Repeated passes

A path toward trend analysis.

Repeated observations at the same location can reveal whether a motion pattern is isolated, recurring, or changing over time.

Operator value

Why railway teams care.

Infrastructure teams can review motion signals beside visual observations and rail location context, helping them distinguish isolated journey events from repeated infrastructure-quality signals.

Investor value

Why this can compound.

Repeated measurements at the same map-matched location can compound into a defensible railway dataset for trend analysis, predictive-maintenance enablement, and future analytical products.

Workflow

How RailEyes Dynamics fits into the RailEyes platform.

Collect IMU measurements alongside camera, time, and GPS data.
Map-match motion records to railway references instead of nearby road geometry.
Correlate abnormal motion signals with visual corridor context.
Track repeated signals across journeys, seasons, speeds, and environmental conditions.

Outputs

What the module produces.

Map-matched motion signalsVisual proof contextRepeated-location trendsPredictive maintenance inputs

Supporting technical context

Vibration-level patterns remain available for deeper review.

The vibration view supports the same story at a more technical level: motion readings can be examined as route-linked records rather than detached journey statistics.

RailEyes vibration level and train dynamics context.

Connected products

Combine Dynamics with visual inspection and RailEdge capture.

Dynamics becomes more useful when motion signals can be compared with corridor imagery and captured repeatedly through the same edge hardware foundation.