Difference between revisions of "Phase2 Iteration1"
m (→C34 Monitor WPM) |
(→Plan iterations 2 to 4) |
||
| (37 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | The | + | The Phase 2 works in iterations. See setup of the Architecture stream. |
| − | |||
== Iteration 1 == | == Iteration 1 == | ||
The first iteration lasts from 21.January to 11.February. | The first iteration lasts from 21.January to 11.February. | ||
| + | |||
=== Topics === | === Topics === | ||
| − | + | ==== Capabilities ==== | |
| − | # | + | In this iteration four of the top most ranked capabilites from the [[Architecture#Shopping List| shopping list]] are treated in this first iteration. |
| − | + | ||
| − | + | ===== 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. | |
| − | # Prepare ticket system | + | |
| + | ===== 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. | ||
| + | |||
| + | ===== 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). | ||
| + | |||
| + | ===== 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. | ||
| + | |||
| + | ==== 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 [[Architecture#Shopping List| shopping list]]. | ||
| + | |||
| + | ==== Prepare ticket system ==== | ||
| + | To support the ARCH stream in planning and managing the different tasks UTrack as ticketing system, the installation is operated by Xrail, is prepared and configured. | ||
| + | |||
| + | ---- | ||
| + | |||
=== Results === | === Results === | ||
==== C14 Monitor WSM ==== | ==== C14 Monitor WSM ==== | ||
| − | In this iteration we worked out four steps to monitor the WSM data quality and coverage. | + | In this iteration we worked out four steps to monitor the WSM data quality and its coverage. |
* Identified WSM KPIs | * Identified WSM KPIs | ||
* Defined measurement points | * Defined measurement points | ||
| Line 20: | Line 38: | ||
* Roadmap KPIs | * Roadmap KPIs | ||
| − | The first step focus on identification of the KPIs to be measured. | + | The first step focus on identification and description of the KPIs to be measured. |
| + | |||
| + | * list in Excel [https://teams.microsoft.com/l/file/2C3AB67B-9E93-4433-9320-4FFB9C9CF031?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xls&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%202%2FCore%20group%20meetings%2F210128_CoreTeam%2F210128_WPM_KPIs_V1.xls&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f WSM KPIs] | ||
| + | * Roadmap in Powerpoint | ||
| + | * Maintenance process in Powerpoint | ||
| − | + | The overview of the KPIs, grouped in work packages, can be seen here. | |
| − | + | [[File:WSM_KPI_210204.png|border|center|800px|WSM KPI]] | |
| − | |||
| − | |||
| − | |||
==== C34 Monitor WPM ==== | ==== C34 Monitor WPM ==== | ||
| + | To setup the monitoring of WPM KPIs the following documents were prepared: | ||
* list in Excel [https://teams.microsoft.com/l/file/2C3AB67B-9E93-4433-9320-4FFB9C9CF031?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xls&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%202%2FCore%20group%20meetings%2F210128_CoreTeam%2F210128_WPM_KPIs_V1.xls&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f WPM KPIs] | * list in Excel [https://teams.microsoft.com/l/file/2C3AB67B-9E93-4433-9320-4FFB9C9CF031?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xls&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%202%2FCore%20group%20meetings%2F210128_CoreTeam%2F210128_WPM_KPIs_V1.xls&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f WPM KPIs] | ||
| − | |||
| − | |||
| − | * (formula) | + | * measurement points: Three measurement points were identified. |
| − | The formula applied to calculate the specific KPI | + | # 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 agreed on with the GCU community. | ||
| + | |||
| + | * (formula) The formula applied to calculate the specific KPI will be described in detail in the next iteration. [https://teams.microsoft.com/l/file/2C3AB67B-9E93-4433-9320-4FFB9C9CF031?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xls&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%202%2FCore%20group%20meetings%2F210128_CoreTeam%2F210128_WPM_KPIs_V1.xls&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f WPM KPIs] | ||
* (target level) | * (target level) | ||
| − | The targeted data quality level | + | The targeted data quality level will be defined and agreed on in the next iteration. [https://teams.microsoft.com/l/file/2C3AB67B-9E93-4433-9320-4FFB9C9CF031?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xls&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%202%2FCore%20group%20meetings%2F210128_CoreTeam%2F210128_WPM_KPIs_V1.xls&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f WPM KPIs] |
* Targeted Routing for WPM messages | * 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". | 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. | 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. | ||
| − | [[File:Wagon_Performance_message_routing.png| | + | [[File:Wagon_Performance_message_routing.png|border|center|800px|WPM Routing]] |
| + | |||
| + | An overview can be seen here. | ||
| + | |||
| + | [[File:WPM_KPI_210204.png|border|center|800px|WPM KPI|left]] | ||
==== C19 Train Operation ==== | ==== C19 Train Operation ==== | ||
| − | + | Presentation of the TIS service at RNE in the WalIn session of 2.February 2021. | |
| − | + | [https://teams.microsoft.com/l/file/8501FADD-690C-4787-B987-E499D5F0A7AC?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=pdf&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%202%2FRU%20architecture%20meetings%20-%20full%20round%2F20210202_WalkIn_TIS_Presentation%2FTIS-2020%20Master%20Report.pdf&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f|Slideset of Josef Stahl/RNE] | |
| + | Questions: | ||
| + | * coverage | ||
| + | * role | ||
| + | * license | ||
| + | ===== Coverage ===== | ||
| + | Train Running Information (TRI) | ||
| + | At the moment nearly 100% of the international and 70% of the national train runs are reported to TIS. Be the end of 2022 all IM's have promised to send 100% national train running information. | ||
| + | Train Running Forecast (TRF) | ||
| + | This depends widely on the national legacy systems of the IMs. The bandwidth is between no TRF at all over one TRf at the border to for each reporting point a TRF. Approximately 50% of the IMs delivers TRF messages. As a figure TIS calcultes a median ETA based on statistical data to inform the user about the truthworthiness. | ||
| + | |||
| + | ===== Role ===== | ||
| + | The RU can access the web client in different roles. It has to provide the SafetyCertificate. He either participates in the train run, in the shunting, on the first/last mile and the terminal. | ||
| + | ===== License ===== | ||
| + | There exists two licenses. The one mentioned in the presentation is for the system interface (via CI) to TIS. The customer gets all Train Running information for those trains he participates. This interface costs 900EUR/month. The other smaller license is free of charge and allows the user to access the web client, shown in the presentation. | ||
==== C77 Consignment Note in WDI ==== | ==== C77 Consignment Note in WDI ==== | ||
| − | + | ===== Roadmap in Powerpoint ===== | |
| − | + | After a session with RD we have summerized the issues in the [https://teams.microsoft.com/l/file/DE48C837-DFD5-4EDA-A34E-207398178874?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=pptx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%202%2FCore%20group%20meetings%2F210211_Full%20team%20meeting%20-%20preparation%2FRFF_architecture%20full%20team_210211.pptx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f|Iteration meeting slides] | |
| + | Together with RailData we have discussed the development plan for the WDI application. The existing roadmap will be prolonged to add the necessary functionality to WDI iteratively. | ||
| + | The defined roadmap can be found here. | ||
| + | |||
| + | ===== Next Task ===== | ||
| + | During the discussions it became obvious that we don't know precise enough the demands of the small RU's. | ||
| + | * What are their concerns, | ||
| + | * what hinders them to complete/adapt/access the CN data, | ||
| + | * in what process step are they, | ||
| + | * what IT services do they need, ... | ||
| + | All of these questions should be discussed with some representatives from small RUs. We combine those questions with those questions collected from the other tasks (C19 Train Operation, C100 Train Service, ...) | ||
Latest revision as of 17:50, 15 February 2021
The Phase 2 works in iterations. See setup of the Architecture stream.
Contents
Iteration 1
The first iteration lasts from 21.January to 11.February.
Topics
Capabilities
In this iteration four of the top most ranked capabilites from the shopping list are treated in this first iteration.
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.
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.
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).
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.
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.
Prepare ticket system
To support the ARCH stream in planning and managing the different tasks UTrack as ticketing system, the installation is operated 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
To setup the monitoring of WPM KPIs the following documents were prepared:
- list in Excel WPM KPIs
- 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 agreed on with the GCU community.
- (formula) The formula applied to calculate the specific KPI will be described in detail in the next iteration. WPM KPIs
- (target level)
The targeted data quality level will be defined and agreed on in the next iteration. 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
Presentation of the TIS service at RNE in the WalIn session of 2.February 2021. of Josef Stahl/RNE Questions:
- coverage
- role
- license
Coverage
Train Running Information (TRI) At the moment nearly 100% of the international and 70% of the national train runs are reported to TIS. Be the end of 2022 all IM's have promised to send 100% national train running information. Train Running Forecast (TRF) This depends widely on the national legacy systems of the IMs. The bandwidth is between no TRF at all over one TRf at the border to for each reporting point a TRF. Approximately 50% of the IMs delivers TRF messages. As a figure TIS calcultes a median ETA based on statistical data to inform the user about the truthworthiness.
Role
The RU can access the web client in different roles. It has to provide the SafetyCertificate. He either participates in the train run, in the shunting, on the first/last mile and the terminal.
License
There exists two licenses. The one mentioned in the presentation is for the system interface (via CI) to TIS. The customer gets all Train Running information for those trains he participates. This interface costs 900EUR/month. The other smaller license is free of charge and allows the user to access the web client, shown in the presentation.
C77 Consignment Note in WDI
Roadmap in Powerpoint
After a session with RD we have summerized the issues in the meeting slides Together with RailData we have discussed the development plan for the WDI application. The existing roadmap will be prolonged to add the necessary functionality to WDI iteratively. The defined roadmap can be found here.
Next Task
During the discussions it became obvious that we don't know precise enough the demands of the small RU's.
- What are their concerns,
- what hinders them to complete/adapt/access the CN data,
- in what process step are they,
- what IT services do they need, ...
All of these questions should be discussed with some representatives from small RUs. We combine those questions with those questions collected from the other tasks (C19 Train Operation, C100 Train Service, ...)
