Difference between revisions of "Phase2 Iteration2"
m (→C76 Monitor Consignment Note KPI) |
|||
| Line 23: | Line 23: | ||
=== Results === | === Results === | ||
| − | + | ==== C66 Monitor H30 quality ==== | |
| + | In this iteration we worked out three steps to monitor the H30 data quality and its coverage. | ||
| + | * Identified Hermes 30 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 [https://teams.microsoft.com/l/file/30592592-110B-48B7-98B0-F967B56896EC?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xls&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%202%2FRU%20architecture%20meetings%20-%20full%20round%2FIterations%2FIteration1%2F2021-02-12%20KPIs_V1.xls&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f H30 KPIs] | ||
| + | * Roadmap in Powerpoint | ||
| + | * Maintenance process in Powerpoint | ||
| + | |||
| + | The overview of the KPIs, grouped in work packages, can be seen here. | ||
| + | [[File:H30_KPI_210225.png|border|center|800px|WSM KPI]] | ||
| + | |||
===== C76 Monitor Consignment Note KPI ===== | ===== C76 Monitor Consignment Note KPI ===== | ||
| + | In this iteration we worked out three steps to monitor the CN data quality and its coverage. | ||
| + | * Identified CN KPIs | ||
| + | * Defined measurement points | ||
| + | * Prioritized KPIs | ||
| + | * Roadmap KPIs | ||
| + | |||
| + | The first step focus on identification and description of the KPIs to be measured. | ||
| + | |||
| + | * [https://teams.microsoft.com/l/file/30592592-110B-48B7-98B0-F967B56896EC?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xls&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%202%2FRU%20architecture%20meetings%20-%20full%20round%2FIterations%2FIteration1%2F2021-02-12%20KPIs_V1.xls&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f CN KPIs] | ||
| + | * Roadmap in Powerpoint | ||
| + | * Maintenance process in Powerpoint | ||
| + | |||
| + | The overview of the KPIs, grouped in work packages, can be seen here. | ||
| + | [[File:H30_KPI_210225.png|border|center|800px|WSM KPI]] | ||
| + | |||
===== C19 TrainOperation Requirements ===== | ===== C19 TrainOperation Requirements ===== | ||
| + | In this task we had to enlarge the scope beyond TrainOperation and Consignment Note information. | ||
| + | We have created a structure to learn about the "small" RUs situation and their needs. | ||
| + | For that we will organize sessions where we work out the (IT and process) surrounding in which those RUs operate. | ||
| + | The actual planning foresees to have discovery sessions regularly in the next months. | ||
Revision as of 09:19, 26 February 2021
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 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.
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.
Results
C66 Monitor H30 quality
In this iteration we worked out three steps to monitor the H30 data quality and its coverage.
- Identified Hermes 30 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 H30 KPIs
- Roadmap in Powerpoint
- Maintenance process in Powerpoint
The overview of the KPIs, grouped in work packages, can be seen here.
C76 Monitor Consignment Note KPI
In this iteration we worked out three steps to monitor the CN data quality and its coverage.
- Identified CN KPIs
- Defined measurement points
- Prioritized KPIs
- Roadmap KPIs
The first step focus on identification and description of the KPIs to be measured.
- CN KPIs
- Roadmap in Powerpoint
- Maintenance process in Powerpoint
The overview of the KPIs, grouped in work packages, can be seen here.
C19 TrainOperation Requirements
In this task we had to enlarge the scope beyond TrainOperation and Consignment Note information. We have created a structure to learn about the "small" RUs situation and their needs. For that we will organize sessions where we work out the (IT and process) surrounding in which those RUs operate. The actual planning foresees to have discovery sessions regularly in the next months.
