Difference between revisions of "Operational Train PreCheck"

From RFF Wiki
Jump to: navigation, search
(Basic Services)
 
Line 44: Line 44:
  
 
== Evaluation ==
 
== Evaluation ==
 +
* Frank Kschonsak on 25 June
 +
This functionality comes close to services, the RFF platform should provide on a wide scale: plausibility-/quality checks for all message types.
 +
The error-handling (-> re-sending 1-n times) has to be standardized as well.

Latest revision as of 12:48, 6 July 2021

Description

The service checks based on a given train characteristics and composition, sent by via H30 or TCM message,

  • the completeness
  • the alignment and
  • the appliances of the involved resources of the train.

The resources are

  • the locomotives
  • the wagons
  • the load
  • the path
  • the driver

Use Case

The use cases include:

Train PreCheck

The RU sends in the H30/TCM for the pre check. The service checks

  • the train route (locations, legs)
  • the train capacity (train-path)
  • the train characteristic (load)

Train Composition split

The RU sends in the H30/TCM for the full stretch. The service

  • splits it up into the different network sections.
  • It applies a check per section based on the national rules.
  • It transforms and adds the necessary national parameters to the individual TCM.
  • It sends out the new TCMs to the IMs.

Preconditions

Basic Services

This service depends on other services:

Dependencies

Planned Steps

Evaluation

  • Frank Kschonsak on 25 June

This functionality comes close to services, the RFF platform should provide on a wide scale: plausibility-/quality checks for all message types. The error-handling (-> re-sending 1-n times) has to be standardized as well.