Difference between revisions of "Phase 1"

From RFF Wiki
Jump to: navigation, search
(Workshops)
 
(4 intermediate revisions by the same user not shown)
Line 119: Line 119:
 
In order to define the architecture of the future RU platform, the following Roadmap was worked out.
 
In order to define the architecture of the future RU platform, the following Roadmap was worked out.
  
[[File:Roadmap_Phase1.png|border|center|Roadmap]]
+
[[File:Roadmap_Phase1.png|border|Roadmap]]
  
 
In the following document, you will find results to all aspects covered by the blue architecture team.
 
In the following document, you will find results to all aspects covered by the blue architecture team.
  
Based on the [[Vision|Vision]] and [[Values#Basic Principles|Basic Principles]] defined by the CIOs and based on the [[Architecture_Limitations|Limitations]] of todays systems (defined in the [[Architecture#Current Architecture|Current Architecture]]), Target [[Architecture#Capabilities|Capabilities ]]were worked out. Gaps between existing limitations and future capabilities were identified and process requirements were worked out.
+
Based on the [[Vision|Vision]] and [[Values#Basic Principles|Basic Principles]] defined by the CIOs and based on the [[Architecture#Limitations|Limitations]] of todays systems (defined in the [[Architecture#Current Architecture|Current Architecture]]), Target [[Architecture#Capabilities|Capabilities]] were worked out. Gaps between existing limitations and future capabilities were identified and process requirements were worked out.
  
 
Based on these results the necessary [[Architecture#Data Objects|data objects]] and their visibility was worked out.
 
Based on these results the necessary [[Architecture#Data Objects|data objects]] and their visibility was worked out.
Line 129: Line 129:
 
The [[Architecture#Target Architecture|target architecture]] is based on the choosen data objects and capabilities and defines a basic framework with basic services, a future RU platform has to provide.
 
The [[Architecture#Target Architecture|target architecture]] is based on the choosen data objects and capabilities and defines a basic framework with basic services, a future RU platform has to provide.
  
Based on the choosen Basic Principles a [[Architecture#Migration Path|migration path ]]was worked out for the first iteration phase.
+
Based on the choosen Basic Principles a [[Architecture#Migration Path|migration path]] was worked out for the first iteration phase.
  
 
Results from Vision, Governance and Value Proposition were always considered and incorporated into the analysis of the architecture team.
 
Results from Vision, Governance and Value Proposition were always considered and incorporated into the analysis of the architecture team.
Line 171: Line 171:
 
* [[Phase1 Workshop17|Migration Path Scenarios (October 22 2020)]]
 
* [[Phase1 Workshop17|Migration Path Scenarios (October 22 2020)]]
 
* [[Phase1 Workshop18|Document Approval (December 12 2020)]]
 
* [[Phase1 Workshop18|Document Approval (December 12 2020)]]
 
[[Pandoc]]
 

Latest revision as of 18:47, 15 February 2021

under construction
this page is still under construction

Architecture Team

The following persons were part of the architecture team

Name Company Email
Mahesh Bhatter DB Cargo mahesh.bhatter@deutschebahn.com
Cecilia Dagerholm xRail cecilia.dagerholm@xrail.eu
Erik Evtimov Citrail erik.evtimov@cit-rail.org
Vanessa Langhammer RCA vanessa.langhammer@railcargo.com
Markus Lund xrail markus.lund@xrail.eu
John Lutz UIC (RPC) john.lutz@orange.fr
Lori Paquet CFL lori.paquet@cfl-mm.lu
Stefan Schaefer UIC (interconnective) sfr@interconnective.at
Dani Schwander UIC (interconnective) dsc@interconnective.at
Christian Strauss DB Cargo christian.c.strauss@deutschebahn.com
Tom Thijs Lineas tom.thijs@lineas.net
Michel Thüring SBB Cargo michel.thuering@sbbcargo.com
Wassilios Tsolakidis UIC (Oaktree) wtsolakidis@oaktree-partners.com
Mark Verhulst Lineas /RailData mark.verhulst@lineas.net
Petr Červinka  CD CARGO petr.cervinka@cdcargo.cz
Thomas Heydenreich GCU mail@th-heydenreich.de
Josef Stahl RNE josef.stahl@ren.eu
Hannes Luts Xrail hannes.lutz@xrail.eu
Conor Feighan Erfa Rail conor.feighan@erfarail.eu
Mike Gürntke Xrail mike.guerntke@xrail.eu
Helge Stuhr Xrail helge.stuhr@xrail.eu
Bertrand Minary SNCF Fret bertrand.minary@sncf.fr
Michel van Dijk Xrail michel.vandijk@xrail.eu
Marc Valette CFL marc.valette@cfl-mm.lu
Christian Kühnast DB christian.kuehnast@deutschebahn.com

RoadMap

In order to define the architecture of the future RU platform, the following Roadmap was worked out.

Roadmap

In the following document, you will find results to all aspects covered by the blue architecture team.

Based on the Vision and Basic Principles defined by the CIOs and based on the Limitations of todays systems (defined in the Current Architecture), Target Capabilities were worked out. Gaps between existing limitations and future capabilities were identified and process requirements were worked out.

Based on these results the necessary data objects and their visibility was worked out.

The target architecture is based on the choosen data objects and capabilities and defines a basic framework with basic services, a future RU platform has to provide.

Based on the choosen Basic Principles a migration path was worked out for the first iteration phase.

Results from Vision, Governance and Value Proposition were always considered and incorporated into the analysis of the architecture team.

Iterations

aus UIC_RFF_Meeting_Minutes.pdf

Workshops