Phase2 Iteration2
The Phase 2 works in iterations. See setup of the Architecture stream.
Contents
Iteration 2
The second iteration lasts from 11.February to 4.March.
Topics
Capabilities
In this iteration four of the top most ranked capabilites from the shopping list are treated in this second iteration. Also tasks created during the work in the first ieteration are tackled here.
C66 Monitor H30 quality
The aim is to define the KPIs for the Hermes 30 Message flow. For details of the Wagon Status domain please read Domain Train Preparation. 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.
C76 Monitor Consignment Note KPI
The aim is to define the KPIs for the Consignment Note Message flow. For details of the Consignment Note domain please read Domain Consignment Note. 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.
C19 TrainOperation Requirements
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.
