Difference between revisions of "TelematicData of Wagon"
From RFF Wiki
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | == Summary == | |
| − | + | Wagon Keepers are currently equipping their fleets with telematics and sensors to ease internal use cases (i.e. mileage, customer service, internal processes). No common solution exist on how to exchange telematics data. | |
| − | + | Creating a broker using the existing interfaces of the RFF DP ecosystem to transmit telematics data between partners to create transparency and a fully digitalized journey. Central mapping and geofencing capabilities would drive future standardizations and intelligently provide more context to the data captured. | |
| − | |||
== Description == | == Description == | ||
| − | * A broker using the | + | * A broker using the existing interfaces of the RFF DP ecosystem to transmit data from A to B |
* Workflow / data exchange derived from the underlying data governance concept that governs the data access and usage permissions in the ecosystem and form the backbone of automated data exchange between the stakeholders IT systems | * Workflow / data exchange derived from the underlying data governance concept that governs the data access and usage permissions in the ecosystem and form the backbone of automated data exchange between the stakeholders IT systems | ||
| − | * Central mapping and geofencing capabilities that would drive future standardizations (CRD) in this domain and | + | * Central mapping and geofencing capabilities that would drive future standardizations (CRD) in this domain and intelligently give more context to the data captured. |
| − | |||
| − | |||
* Wagon Keepers (Railway Undertakings and leasing companies) are equipping their cars with telematics and sensors and follow internal use cases (i.e. mileage, customer service, internal processes) | * Wagon Keepers (Railway Undertakings and leasing companies) are equipping their cars with telematics and sensors and follow internal use cases (i.e. mileage, customer service, internal processes) | ||
* Within rail freight wagons are exchanged and used through via several agreements (GCU, bilateral agreements, leasing, ….) and trains usually consist of cars from multiple keepers | * Within rail freight wagons are exchanged and used through via several agreements (GCU, bilateral agreements, leasing, ….) and trains usually consist of cars from multiple keepers | ||
* To achieve full visibility and create a fully digitized journey Data Sharing becomes inevitable (Track&Trace services, internal process optimization) | * To achieve full visibility and create a fully digitized journey Data Sharing becomes inevitable (Track&Trace services, internal process optimization) | ||
* With regards to digitized operations (i.e. digital freight train, automatic brake test) the need for shared telematic data will become a crucial success factor in near future | * With regards to digitized operations (i.e. digital freight train, automatic brake test) the need for shared telematic data will become a crucial success factor in near future | ||
| + | |||
| + | == Use Case == | ||
| + | * RU receives wagon telematic data | ||
| + | RU receiving telematics data of wagons which it is using (independent of being the wagon keeper) | ||
| + | Trigger: A wagon generates a telematics data set and sends it to the wagon keeper’s telematics application. | ||
| + | Description: The wagon keeper’s telematics application forwards the data to a centra broker which determines all RUs that are entitled to receive the data (current users of the wagon). The broker forwards the telematics data to those RUs. This may be restricted to a subset of the telematics data generated by the wagon (e.g. comprising the position data but not certain sensor data). | ||
== Preconditions == | == Preconditions == | ||
=== Basic Services === | === Basic Services === | ||
| + | Wagon usage determination: system’s capability to determine which RUs are entitled to receive current telematics data, for this | ||
| + | * Connection to order data and Consignment Note (CN) information/exchange: RUs named in a CN which is currently valid for the wagon (connection wagon to CN) | ||
| + | * Geofencing (detection of start and end time of validity of the connection of wagon to CN) | ||
== Dependencies == | == Dependencies == | ||
| Line 25: | Line 31: | ||
== Evaluation == | == Evaluation == | ||
| + | * Frank Kschonsak on 25 June | ||
| + | Focus should be on the load / freight, not the wagon. What is the main aim of our customers: transport in quality and time. | ||
Latest revision as of 12:47, 6 July 2021
Contents
Summary
Wagon Keepers are currently equipping their fleets with telematics and sensors to ease internal use cases (i.e. mileage, customer service, internal processes). No common solution exist on how to exchange telematics data. Creating a broker using the existing interfaces of the RFF DP ecosystem to transmit telematics data between partners to create transparency and a fully digitalized journey. Central mapping and geofencing capabilities would drive future standardizations and intelligently provide more context to the data captured.
Description
- A broker using the existing interfaces of the RFF DP ecosystem to transmit data from A to B
- Workflow / data exchange derived from the underlying data governance concept that governs the data access and usage permissions in the ecosystem and form the backbone of automated data exchange between the stakeholders IT systems
- Central mapping and geofencing capabilities that would drive future standardizations (CRD) in this domain and intelligently give more context to the data captured.
- Wagon Keepers (Railway Undertakings and leasing companies) are equipping their cars with telematics and sensors and follow internal use cases (i.e. mileage, customer service, internal processes)
- Within rail freight wagons are exchanged and used through via several agreements (GCU, bilateral agreements, leasing, ….) and trains usually consist of cars from multiple keepers
- To achieve full visibility and create a fully digitized journey Data Sharing becomes inevitable (Track&Trace services, internal process optimization)
- With regards to digitized operations (i.e. digital freight train, automatic brake test) the need for shared telematic data will become a crucial success factor in near future
Use Case
- RU receives wagon telematic data
RU receiving telematics data of wagons which it is using (independent of being the wagon keeper) Trigger: A wagon generates a telematics data set and sends it to the wagon keeper’s telematics application. Description: The wagon keeper’s telematics application forwards the data to a centra broker which determines all RUs that are entitled to receive the data (current users of the wagon). The broker forwards the telematics data to those RUs. This may be restricted to a subset of the telematics data generated by the wagon (e.g. comprising the position data but not certain sensor data).
Preconditions
Basic Services
Wagon usage determination: system’s capability to determine which RUs are entitled to receive current telematics data, for this
- Connection to order data and Consignment Note (CN) information/exchange: RUs named in a CN which is currently valid for the wagon (connection wagon to CN)
- Geofencing (detection of start and end time of validity of the connection of wagon to CN)
Dependencies
Planned Steps
Evaluation
- Frank Kschonsak on 25 June
Focus should be on the load / freight, not the wagon. What is the main aim of our customers: transport in quality and time.
