Difference between revisions of "Phase2 Iteration1"
m (→C34 Monitor WPM) |
m (→C14 Monitor WSM) |
||
| Line 23: | Line 23: | ||
* list in Excel | * list in Excel | ||
| − | |||
| − | |||
| − | |||
* (formula) | * (formula) | ||
* (target level) | * (target level) | ||
* Roadmap in Powerpoint | * Roadmap in Powerpoint | ||
* Maintenance process in Powerpoint | * Maintenance process in Powerpoint | ||
| + | |||
| + | An overview of the KPIs can be seen here. | ||
| + | [[File:WSM_KPI_210204.png|200px|thumb|left|WSM KPI]] | ||
==== C34 Monitor WPM ==== | ==== C34 Monitor WPM ==== | ||
Revision as of 14:08, 4 February 2021
The Phase2 works in iterations.
Contents
Iteration 1
The first iteration lasts from 21.January to 11.February.
Topics
- Capabilities
- C14 Monitor WSM data quality
- C34 Monitor WPM data quality
- C19 Train operation for small RU
- C77 Consignment note for small RU
- Plan iterations 2 to 4
- Prepare ticket system
Results
C14 Monitor WSM
In this iteration we worked out four steps to monitor the WSM data quality and coverage.
- Identified WSM KPIs
- Defined measurement points
- Prioritized KPIs
- Roadmap KPIs
The first step focus on identification of the KPIs to be measured.
- list in Excel
- (formula)
- (target level)
- Roadmap in Powerpoint
- Maintenance process in Powerpoint
An overview of the KPIs can be seen here.
C34 Monitor WPM
- list in Excel WPM KPIs
An overview can be seen here.
- measurement points
Three measurement points were identified.
- RailData input queue of WSMm messages
For a data quality information of all received wagon performance messages at RailData.
- RailData output queue for WPM messages
For a data quality information of all processed/calculated wagon performance message inside of RailData.
- GCU Broker input queue for WPM messages
This must be discussed and agrred on qith the GCU community.
- (formula)
The formula applied to calculate the specific KPI is described in detail. WPM KPIs
- (target level)
The targeted data quality level is defined and agreed on. WPM KPIs
- Targeted Routing for WPM messages
The Domain Wagon Performance encompasses the communication flows between the sending RU and the receiving WagonKeeper. The RU is obliged to deliver the wagon performance in those transports he his responsible for. At the arrival of the last station, final destination or delivered to the customer the RU sends the Wagon Performance to the WagonKeeper follwing the workflow described below. If he is not in the position to calculate the distances for those wagons he can profit from the special service of Mileage Calculation. This service will calculate in the name of the RU the necessary wagon performance data sets based on the sent in Wagon Status messages. If the receiving WagonKeeper would like to fill the remaining gaps in the Wagon Performance he can opt for the special service of Filling Gaps. This service will estimate for each remaining gap a replacement to complete the Wagon Performance "chain".
This routing shows the target situation. Today not all wagon performance messages are routed via the GCU Broker. Instead they are exchanged bilaterally between RU and WagonKeeper or routed by RailData directly to the WagonKeeper as RailData member.
C19 Train Operation
Roadmap in Powerpoint next task in Powerpoint
C77 Consignment Note in WDI
Slideset of Josef Stahl Open questions: coverage, role and license
