Phase 1
| under construction |
| this page is still under construction |
Contents
Architecture Team
The following persons were part of the architecture team
| Name | Company | |
|---|---|---|
| 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.
Figure 1 - 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.
Basic Principles
The following Basic Principles for a future RU platform were defined by the CIOs as part of their Vision considerations
Ein Bild, das Text enthält. Automatisch generierte Beschreibung
Figure 2 - Basic Principles
Data Quality
Raise the data quality on the digital platforms
Coverage
Early increase of the usage of existing services in the Ecosystem
Consolidate Ecosystem
Migrate the services to one future platform
One stable RU interface
Define one stable interface for the RUs with modern interface technology
Innovation
Develop innovative services based on the existing offered services.
Current Architecture
In a first step existing systems and tools are analysed.
The topology shows the various systems and its current owners.
For those systems the business objects were determined and in a second step the workflows between the business objects.
All information is stored in Enterprise Architect in a common UML Model. A HTML copy of the model can be found here: UML Model
Topology
The topology shows currently existing systems and tools that are analysed in details. The following links guide you to the corresponding architecture models
The main systems are:
Ein Bild, das Platz enthält. Automatisch generierte Beschreibung
Figure 3 - UML Model
The topology can be found here: UML Model - Topology
The following picture shows the platform coverage
Figure 4 – Platform Coverage
Business Objects
The business objects describe in an abstract way the basic objects of todays systems.
They are described in the UML Model for the above mentioned systems
Figure 5 - Business Objects
The topology can be found here: UML Model - Business Objects
Detailed Business Objects are available for
Workflows
The workflows describe the interaction of the business objects of todays systems
Figure 6 - Workflow
Each workflow is described with a swimlane diagram in details
Figure 7 - Swimlane
Workflow diagrams and swimlanes can be found in the UML model for each of todays systems.
Please refer to the detailed diagrams in the subdirectories of the UML Model - Business Workflows.
Messages and Data Objects
An overview of all messages exchanged with the related data objects in the current architecture landscape can be found as a list in the following document on the sheet Messages.
Iterations
aus UIC_RFF_Meeting_Minutes.pdf
- Iteration 1 (April 30 - May 13 2020)
- Iteration 2 (May 14 - May 27 2020)
- Iteration 3 (May 28 - June 9 2020)
- Iteration 4 (June 10 - June 24 2020)
- Iteration 5 (June 25 - July 8 2020)
- Iteration 6 (July 9 - August 19 2020)
- Iteration 7 (August 20 - September 2 2020)
- Iteration 8 (September 3 - September 16 2020)
- Iteration 9 (September 17 - October 14 2020)
- Iteration 10 (October 15 - October 28 2020)
- Iteration 11 (October 29 - November 10 2020)
- Iteration 12 (November 11 - December 4 2020)
- Document Approval (December 10)
Workshops
- Capabilities - Location and Train Identification (June 16 2020)
- Capabilities - Train Operations and Wagon Status (June 18 2020)
- Capabilities - Wagon Damage, Rolling Stock (June 22 2020)
- Capabilities - Train Preparation and Braking Rules (June 24 2020)
- Capabilities - Shipment Booking and Ordering (June 26 2020)
- Capabilities - Train Service Planning and Intermodal Traffic (June 29 2020)
- Capabilities - Non-Functional Requirements (June 30 2020)
- Capabilities - Rolling Stock (July 7 2020)
- Data Objects - Consignment Note, TrainPreparation, Wagon Status (August 24 2020)
- Data Objects - Path Management, Train Run (August 27 2020)
- Data Objects - Wagon Related Messages (August 28 2020)
- Data Objects - Single Wagon Load, Shipment, Booking, Operations (August 31 2020)
- Architecture - Platform Framework Concepts (September 10 2020)
- Architecture - Platform Framework Deep Dive (September 11 2020)
- Architecture - Architecture Meeting (September 17 2020)
- Small Player Integration (October 14 2020)
- Migration Path Scenarios (October 22 2020)
- Document Approval (December 12 2020)
