The chat responses are generated using Generative AI technology for intuitive search and may not be entirely accurate. They are not intended as professional advice. For full details, including our use rights, privacy practices and potential export control restrictions, please refer to our Generative AI Service Privacy Information. As this is a test version, please let us know if something irritating comes up. Like you get recommended a chocolate fudge ice cream instead of an energy managing application. If that occurs, please use the feedback button in our contact form!
Skip to content

One key to advancing sustainable transportation is to digitally increase the capacity of rail systems - with less resources.

Streaming Data REST API

The API provides direct, programmatic access to live data streams from assets in the Railigent X data lake.

This REST API is as a straightforward and powerful tool for building real-time monitoring and data analysis applications. It enables the integration of live asset data directly into existing systems or the creation of responsive solutions.

Railway operators, owners, and lessors receive real-time data from critical onboard systems, enabling continuous tracking and analytics of their rail vehicle operations.

Data Flow

Why real-time streaming via an API?

Following the Data as a Service (DaaS) paradigm, this API gives you a convenient way to receive live information and raw data from your assets in near real-time. This machine-to-machine interface allows you to process continuous data streams directly within your own business applications, tailored to your specific needs.

Pre-processed operational data can be easily integrated into customer systems, empowering you to develop insights and optimize vehicle utilization and maintenance strategies.

We provide a robust, standardized streaming service for developers building real-time monitoring and data analysis solutions.

Your Benefits:

  • Enables real-time monitoring of key vehicle data in customer systems
  • Choose your own tools. Full flexibility in processing and displaying vehicle data
  • Monitor operational behavior, detect outliers, fill data gaps

Available Data Services Packages

The availability and scope of data service packages are determined by contractual agreements and are specific to vehicle types.

Generally, the following data service packages are available:

Note: As a Vectron customer, all your agreed-upon data is accessible independently of specific service data packages.

Live Vehicle Information

The Live Vehicle Information package provides railway operators and leasing companies with a seamless way to integrate real-time data on the position, speed, and mileage of their rail vehicles directly into their IT systems. Unlike manual data collection or third-party hardware solutions, this API-based service delivers reliable, up-to-date information across all the vehicles in a customer’s fleet, with no additional effort required in workshops or on the vehicles. By easily incorporating critical vehicle data points, users can gain a continuous, near real-time overview of their fleet, enabling more informed decisions and quicker responses to changing conditions.

Key benefits of the Live Vehicle Information API include streamlined data integration, improved visibility and responsiveness, and hassle-free implementation. The standard package provides access to key asset data points: position, speed, mileage, vehicle ID, and trip ID, in near real-time. Customers can rely on consistent, accurate information across their entire fleet, regardless of hardware or software version, thanks to the platform's enterprise-grade reliability and security.

Occupancy Information

Occupancy Information is an optional service package for passenger vehicles. It provides the degree of occupancy per saloon, in percent.

This package is an optional add-on to Basic Vehicle Information.

Vehicle Status

The Vehicle Status package provides railway operators, owners, and lessors with real-time data from critical onboard systems, enabling continuous tracking and analytics of their rail vehicle operations. Delivered via the Railigent X Train API, this service offers visibility into how assets are being utilized, allowing users to optimize vehicle deployment and inform data-driven maintenance planning. Unlike installing third-party hardware, the API-based solution simplifies data access by providing pre-processed operational data that can be easily integrated into existing systems.

Key benefits of the Vehicle Status package include enhanced operational efficiency, improved vehicle utilization, and streamlined data integration. Railway operators and vehicle owners can analyze usage patterns to plan maintenance and circulation, while dispatchers and rental companies can leverage historical data to optimize fleet deployment. The flexible, scalable, and secure platform allows customers to seamlessly incorporate vehicle status information into their own analytics and reporting tools.

Subset of available data:

  • Train Mode: Current operational mode of the train.
  • Line Current: Electrical current in the train's power line.
  • Line Voltage: Voltage in the train's power line.
  • Tractive Effort: Force exerted by the train for movement.
  • Cab: Status of the train's cab.
  • Number of Locomotives: Count of locomotives in the train.
  • Pantograph: Status of the train's pantograph.
  • Wheel: Status of the train's wheels.
  • Brake Effort: Force applied by the train's braking system.
  • Train Length: Total length of the train.
  • Train Shutdown: Indicates if the train is shut down.
  • Train Weight: Total weight of the train.
  • CCU1 Software Version: Software version of the first control unit.
  • CCU2 Software Version: Software version of the second control unit.
  • RDA Software Version: Software version of the remote data acquisition unit.
  • Diesel Tank Liquid Level: Liquid level in the diesel tank.
  • Main Air Pressure: Pressure in the main air system.
  • Energy: Energy consumption or generation status.
  • Pressure Brake Pipe: Pressure in the brake pipe.
Vehicle Counters

The Vehicle Counters package provides railway operators and leasing companies with a data service that delivers the current values of maintenance-relevant counters from their rail vehicles. This information allows users to plan data-driven maintenance by gaining visibility into the operation hours and switching cycles of critical components, rather than relying on time-based schedules. For dispatchers and rental companies, the historical counter data can also be leveraged to inform the efficient allocation and circulation of the vehicle fleet.

Key benefits of the Vehicle Counters package include optimized maintenance planning, enhanced fleet utilization. Unlike manual data collection or the installation of third-party hardware, the API-based solution provides accurate and up-to-date counter information with minimal effort required on the customer's part.

Subset of available data:

  • Time in DC Mode 1500V On: Duration the vehicle operates in 1500V DC mode.
  • Time in DC Mode 3000V On: Duration the vehicle operates in 3000V DC mode.
  • Time in AC Mode 25KV On: Duration the vehicle operates in 25kV AC mode.
  • Time in AC Mode 15KV On: Duration the vehicle operates in 15kV AC mode.
  • Time Main Switch DC On: Duration the main switch is on in DC mode.
  • Time Main Switch AC On: Duration the main switch is on in AC mode.
  • Switch Cycles Main Switch DC: Number of cycles the main switch operates in DC mode.
  • Switch Cycles Main Switch AC: Number of cycles the main switch operates in AC mode.
  • Operating Time Vehicle: Total operating time of the vehicle.
  • Time Speed Greater Than 2KMH: Duration the vehicle speed is greater than 2 km/h.
  • Switch Cycles Main Air Compressor: Number of cycles the main air compressor operates.
Vehicle Config Data

The Vehicle Config Data Package provides rail operators with a centralized source of comprehensive vehicle data to support informed decision-making and efficient fleet management. The package documents the vehicle's key technical specifications, including maximum speed, starting traction, and braking force, which can be valuable for optimizing operations and maintenance.

The package covers essential vehicle master data, such as the UIC number, vehicle variant, and the latest software release available for that specific model. At the core of the package is a detailed list of the hardware and software versions currently installed on the vehicle's RDA (Remote Diagnostic Access) box. This information is complemented by a "Target/Current Analysis" (TCA) report, which identifies any deviations between the target software release and the versions currently running on the vehicle. This analysis helps pinpoint vehicles that may require software updates. For vehicles where Siemens is responsible for service, the package includes the target software release, enabling a direct comparison to the actual installed version.

Subset of available data:

  • Vehicle master data: UIC number, vehicle variant. Latest software release available for this vehicle. For vehicles where SMO is responsible for service, we also provide the target release for each vehicle.
  • Keeper, as known by Siemens. (Customers can request an update via help desk ticket.)
  • Vehicle capabilities:
    • max speed
    • max starting traction
    • max braking force
  • List of reported hard- and software versions from the RDA box: Actual vehicle configuration, as maintained
  • Target / Current Analysis: actual software versions on vehicle vs current software versions on vehicle, indicating which device should receive which software, in which version.

Deprecation Policy

In the course of product and feature development at SMO, the API may evolve. We want to ensure that customers receive the information they need to take advantage of these features, and to update their systems in time. Features from previous releases may become deprecated with a new feature release (“breaking change”). SMO will notify API customers ahead of the release date, and ensure six months of backward compatibility. Examples of breaking changes are:

  • Changes to endpoint URIs
  • Changes in the API´s request / response structure
  • Changes in HTTP methods used

Important Considerations

To ensure a stable and reliable experience for all users, please be aware of the following policies.

  • Data Retention: Data within a stream is retained for a specific period. Be sure to retrieve the data you need within this retention window, as older data may not be available through the streaming interface.
  • Service Usage Limits: The API is subject to usage limits to ensure fair use and system stability. These limits may apply to the number of consumers, subscriptions, or the frequency of data retrieval requests.