Difference between revisions of "Phase2 Iteration10"

From RFF Wiki
Jump to: navigation, search
(Created page with "The Phase 2 works in iterations. See setup of the Architecture stream. == Iteration 10 == The tenth iteration lasts from 2.September to 23.September. === Topics === ==== Ca...")
 
Line 15: Line 15:
 
* defining the maintenance process
 
* defining the maintenance process
 
* Bilateral location quality meetings will be planned to discuss the national specialties and the maintenance process.
 
* Bilateral location quality meetings will be planned to discuss the national specialties and the maintenance process.
* Beside that we will continue on the GEO model – location link.
+
==== Smart Services ====
 +
===== SM17 Facilities on Location =====
 +
We have continued our work on the GEOmodel.
 +
The description is [[GEO Model|here]].
  
 
==== User Validation ====
 
==== User Validation ====
  
The User validation stream consists of three different topics:
+
===== DISCO: Discovery Session =====
# RFF member validation
+
Two sessions were held in this iteration.
# Discovery sessions
+
# [[https://rff.wiki.interconnective.ch/index.php/DS_DE1_SOL|SOL Discovery Session DE1 in German]]
# Ecosystem alignment
+
# [[https://rff.wiki.interconnective.ch/index.php/DS_DE2_GAP|GAP Discovery Session DE2 in German]]
 
+
The documentation and English summary is available under the above links.
===== RFF member validation =====
 
In the RFF member validation each member can lay out
 
* his preferences for realization of the RFF topics and
 
* his contribution in this selection
 
With this voting the Peer groups and sponsors are identified to support the chosen services to build up.
 
  
===== DISCO: Discovery Session =====
+
===== POC DigitalPlatform =====
We will in this iteration  
+
In this iteration we conducted an evaluation of the potential use cases for the DigitalPlatform POC.
* sketch the second solutions for the Gap Discovery session (in German) and  
+
We processed the following steps:
* to support and follow up with the contact persons of the RFF partners.
+
# 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 [[https://rff.wiki.interconnective.ch/index.php/Digital_Platform_Pilot|here]].
 +
The selection was proposed to the SteerCo on the 10th of September.
  
==== Ecosystem alignment ====
+
The next step is to gain an overview of the individual RU interest in those uses cases.
In the next step we will tackle the integration of the RFF DP ecosystem in the existing context.
+
Therefor we will present them in short to the FullTeam ARCH member and ask their evaluation.
  
===== WDI/MARS service =====
+
===== POC MARS MVP =====
 
Work on the publication of the MARS functionality and project planning for version 3.
 
Work on the publication of the MARS functionality and project planning for version 3.
 
  
 
----
 
----

Revision as of 18:00, 16 September 2021

The Phase 2 works in iterations. See setup of the Architecture stream.

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 description is here.

User Validation

DISCO: Discovery Session

Two sessions were held in this iteration.

  1. [Discovery Session DE1 in German]
  2. [Discovery Session DE2 in German]

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:

  1. Selection on Digital Themes and topics from the UserValidation:
    • Digital Train Composition
    • Digital Train Handover
    • Digital Consignment Notes and
    • GEOmodel (see above)
  2. Evaluation of the described uses cases in those selectd topics. We included time2market, feasibility, attractiveness, MARS independency and testability of the platform as criteria.
  3. The 8 top ranked uses cases were chosen as short list
  4. We grouped them according their abbility to test the platform in terms of
    • Data highway including access
    • Railway functionality
    • Data model
    • Client technology
  5. 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
  1. 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.


Reviews


Results