Difference between revisions of "Phase2 Iteration5"
(→Iteration 5) |
(→Results) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
== Iteration 5 == | == Iteration 5 == | ||
| − | The fifth iteration lasts from | + | The fifth iteration lasts from 15.April to 6.May. |
=== Topics === | === Topics === | ||
| Line 13: | Line 13: | ||
===== C14: Define report tool for RFF ===== | ===== C14: Define report tool for RFF ===== | ||
| + | The target is to define the centrally operated reporting tool for the RFF digital platform. | ||
| + | |||
| + | And two existing to continue: | ||
| − | |||
===== C01: Managed CRD Location Masterdata ===== | ===== C01: Managed CRD Location Masterdata ===== | ||
| Line 40: | Line 42: | ||
---- | ---- | ||
=== Results === | === Results === | ||
| + | |||
| + | ===== C43: Office Integration of RSDS requests ===== | ||
| + | The task foresees to lower the hurdles for A type RUs to access RollingStock datasets. | ||
| + | This should be achieved by utilizing Office technology. | ||
| + | |||
| + | ===== C14: Define report tool for RFF ===== | ||
| + | We settled the basis to define the centrally operated reporting tool for the RFF digital platform. | ||
| + | |||
| + | The analysis of the RFF reporting tool revealed the six layers: | ||
| + | * Report phases: In what phases the report tool will be used? | ||
| + | * Use Cases: What use cases need to be supported? | ||
| + | * Enablers: What are the enablers for the reporting tool service? E.g. Drill down to message, to time slot … | ||
| + | * Report Objects: What objects are the result of those reports? | ||
| + | * Existing Systems: What systems are used on the existing platforms? | ||
| + | * Basic Principles: What basic principles are set up for the future reporting tool? | ||
| + | |||
| + | [[Reporting Tool]] | ||
| + | |||
| + | ===== C01: Managed CRD Location Masterdata ===== | ||
| + | |||
| + | The target of this task is to enhance the CRD masterdata to a level where it can be used as new GEO masterdata reference. We will start this task in this iteration by | ||
| + | * collect the experience and gaps with the CRD data quality so far | ||
| + | * sketch a analysis method to determine the actual state of the master data | ||
| + | * evaluate whether a data quality assurance is needed (CRD KPI) | ||
| + | * defining the maintenance process | ||
| + | |||
| + | The findings can be found at [[Master Data]]. | ||
Latest revision as of 15:41, 3 May 2021
The Phase 2 works in iterations. See setup of the Architecture stream.
Contents
Iteration 5
The fifth iteration lasts from 15.April to 6.May.
Topics
Capabilities
There are two new topics to handle:
C43: Office Integration of RSDS requests
The task foresees to lower the hurdles for A type RUs to access RollingStock datasets. This should be achieved by utilizing Office technology.
C14: Define report tool for RFF
The target is to define the centrally operated reporting tool for the RFF digital platform.
And two existing to continue:
C01: Managed CRD Location Masterdata
The target of this task is to enhance the CRD masterdata to a level where it can be used as new GEO masterdata reference. We will start this task in this iteration by
- collect the experience and gaps with the CRD data quality so far
- sketch a analysis method to determine the actual state of the master data
- evaluate whether a data quality assurance is needed (CRD KPI)
- defining the maintenance process
We know that this task will accompany us for several iterations.
SM: SmartService Profile
Based on the Smart Services list we continue to describe the Smart Services. With these profiles we can then start the discussion with the CIO/steering committee on prioritization.
Reviews
Smart Service profiles
- SM_08 Siding Everywhere
- SM_17 Facilities on location
- SM_24 Authority Communication
Results
C43: Office Integration of RSDS requests
The task foresees to lower the hurdles for A type RUs to access RollingStock datasets. This should be achieved by utilizing Office technology.
C14: Define report tool for RFF
We settled the basis to define the centrally operated reporting tool for the RFF digital platform.
The analysis of the RFF reporting tool revealed the six layers:
- Report phases: In what phases the report tool will be used?
- Use Cases: What use cases need to be supported?
- Enablers: What are the enablers for the reporting tool service? E.g. Drill down to message, to time slot …
- Report Objects: What objects are the result of those reports?
- Existing Systems: What systems are used on the existing platforms?
- Basic Principles: What basic principles are set up for the future reporting tool?
C01: Managed CRD Location Masterdata
The target of this task is to enhance the CRD masterdata to a level where it can be used as new GEO masterdata reference. We will start this task in this iteration by
- collect the experience and gaps with the CRD data quality so far
- sketch a analysis method to determine the actual state of the master data
- evaluate whether a data quality assurance is needed (CRD KPI)
- defining the maintenance process
The findings can be found at Master Data.
