Phase2 Iteration1

The Phase 2 works in iterations. See setup of the Architecture stream.

Iteration 1

The first iteration lasts from 21.January to 11.February.

Topics

1. Capabilities

In this iteration four of the top most ranked capabilites from the shopping list are treated in this first iteration.

1. 1. C14 Monitor WSM data quality

The aim is to define the KPIs for the Wagon Status Message flow. For details of the Wagon Status domain please read Domain Wagon Status. The task includes the definition and description of the KPI. It also encompasses the grouping of the found KPIs into work packages and the setup of a roadmap for implementation. In the next step the exact formula for the its calculation, the targeted level for the data quality and the report frequency are tackled and aligned with the participating RUs in the ARCH stream.

1. 1. C34 Monitor WPM data quality

The aim is to define the KPIs for the Wagon Performance Message flow. For details of the Wagon Performance domain please read Domain Wagon Performance. The task includes the definition and description of the KPI. It also encompasses the grouping of the found KPIs into work packages and the setup of a roadmap for implementation. Beside that the target WPM routing is described. In the next step the exact formula for the its calculation, the targeted level for the data quality and the report frequency are tackled and aligned with the participating RUs in the ARCH stream.

1. 1. C19 Train operation for small RU

To simplify the access for small RU's to participate in a train run the operation of a train should be backed up by providing information before and during the train run, assist in the preparation and operation of the train and include the small RU in the information and management loop together with the (bigger) partner. In this first step we invite RNE to present the TIS service in this flow, with the special focus on small RU integration (Coverage).

1. 1. C77 Consignment note for small RU

To simplify the access for small RU's to participate in a train run the preparation of a train should be backed up by providing information before hand and assist in the preparation of the train and include the small RU in the information and management loop together with the (bigger) partner. In this first step we analyse the WDI initiative of RailData to find out what is on their roadmap and planned for this year.

1. Plan iterations 2 to 4

During the first iteration the next three iterations for the first quarter are sketched out to enable the other RFF streams to align and to include the ARCH steps into their planning. The tasks in those iterations are taken from the shopping list.

1. Prepare ticket system

To support the ARCH stream in planning and managing the different tasks UTrack as ticketing system, the installation is operatd by Xrail, is prepared and configured.

Results

C14 Monitor WSM

In this iteration we worked out four steps to monitor the WSM data quality and its coverage.

• Identified WSM KPIs
• Defined measurement points
• Prioritized KPIs
• Roadmap KPIs

The first step focus on identification and description of the KPIs to be measured.

• list in Excel WSM KPIs
• Roadmap in Powerpoint
• Maintenance process in Powerpoint

The overview of the KPIs, grouped in work packages, can be seen here.

C34 Monitor WPM

• list in Excel WPM KPIs

• measurement points

Three measurement points were identified.

1. RailData input queue of WSMm messages

For a data quality information of all received wagon performance messages at RailData.

1. RailData output queue for WPM messages

For a data quality information of all processed/calculated wagon performance message inside of RailData.

1. 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.

An overview can be seen here.

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