Onboarding new customers

For new customers a new instance of RailDB will be configured consisting of the following components:

  • Datawarehouse storage
  • Import/Export service
  • Algorithm service
  • API service
  • Mapservices

RailDB offers an integrated SAAS solution.

Updating railway models

When a new railway model version is available a new mapping must be implemented in RailDB. This process is organized as follows:

  • A customer sends new railway model version.
  • The new railway model is checked by RailDB using data checkers. Minor issues with the model are solved by RailDB.
  • If the model is ok, then RailDB generates a new segment mapping for the datawarehouse.
  • The new mapping is loaded into the datawarehouse.
  • The customer is informed that the new model is implemented in RailDB. Imports, exports and algorithms can be run using all versions of the track model including the newest one.

Configuring data collections

When the new IT instance of RailDB for the customer is implemented it can be configured. This comprises of the following steps:

  • A data delivery protocol is agreed upon between RailDB and customer that define the required data collections and corresponding data formats in the datawarehouse. RailDB has standard data delivery protocols available that cover 95% of the needs for most customers including geometry data, NDT-data, platform measurements, inspection data etc. It is off course possible to define custom imports.
  • RailDB will setup the defined imports for these collections corresponding to the data delivery protocol.
  • When the imports are configured the customer can upload data and create a task in RailDB to import the data into the datawarehouse. If required, RailDB also provides imports with additional data checks.

Configuring algorithms

The standard algorithms in RailDB provide out of the box analyses and reporting functionalities and can be configured by the customer to a certain extent. Initial setup of the required algorithms is executed by RailDB. The exact configuration can be done by the customer through the API, for example:

  • Set the measurement data datetime interval to include by the algorithm.
  • Set the spatial extent for the analysis by the algorithm.
  • Set the norm exceedance limits depending on local standards.
  • Set the algorithm specific parameters like sensitivity.

Routing measurement data

In order to import measurement data into RailDB the data needs to be coupled to the railway model. This proces is called routing and can be done based on GPS or ODO metadata. We offer this as a service since we have a lot of experience with this.

Other Gridware services

With our company Gridware we also provide more general data consultancy in the rail sector. We are specialized in:

  • Creating and maintaining track models
  • Writing measurement tenders
  • Data driven assetmanagement
  • Managing track data
  • Data science for rail
  • PowerApps for rail inspections

For more information on these services check out our Gridware website.