Phase2 Iteration10
The Phase 2 works in iterations. See setup of the Architecture stream.
Contents
Iteration 10
The tenth iteration lasts from 2.September to 23.September.
Topics
Capabilities
C01: Managed CRD Location Masterdata
The target of this task is to enhance the CRD master data to a level where it can be used as new GEO master data reference. We will continue this task 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
- Bilateral location quality meetings will be planned to discuss the national specialties and the maintenance process.
Smart Services
SM17 Facilities on Location
We have continued our work on the GEOmodel. The initial use case definition is available here.
In the next step we align with RNE (CRD) and ERA (RINF) about linking the data sets.
Three of the use cases are potential candidates for the POC DP.
User Validation
DISCO: Discovery Session
Two sessions were held in this iteration.
The documentation and English summary is available under the above links.
POC DigitalPlatform
In this iteration we conducted an evaluation of the potential use cases for the DigitalPlatform POC. We processed the following steps:
- Selection on Digital Themes and topics from the UserValidation:
- Digital Train Composition
- Digital Train Handover
- Digital Consignment Notes and
- GEOmodel (see above)
- Evaluation of the described uses cases in those selectd topics. We included time2market, feasibility, attractiveness, MARS independency and testability of the platform as criteria.
- The 8 top ranked uses cases were chosen as short list
- We grouped them according their abbility to test the platform in terms of
- Data highway including access
- Railway functionality
- Data model
- Client technology
- We ended up with a selection of 5 use cases out of the topics Digital Train Operation and GEOmodel to enter the discussion with Microsoft.
We have chosen a set of (smaller) use cases because
- we retain the management ability during the project phase (blocker, delays, dependencies, access, feasibility)
- we can implement them independently from each other
- we can enlarge or reduce the scope according to the project progress
The five use cases are described [[1]]. The selection was proposed to the SteerCo on the 10th of September.
The next step is to gain an overview of the individual RU interest in those uses cases. Therefor we will present them in short to the FullTeam ARCH member and ask their evaluation.
POC MARS MVP
Work on the publication of the MARS functionality and project planning for version 3.
