|
|
| (52 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | {| style="float:right;border:2px solid black;background-color:#FFFF00;width: 30%;text-align:center"
| + | ==Introduction== |
| − | | '''under construction'''
| + | The Architecture is developed based on |
| − | |-
| + | * the existing platforms and services |
| − | | this page is still under construction''
| + | * according to the needs and roadmap of the initiative -> [[Targets]] |
| − | |}
| + | * in compliance with the defined [[Values]] |
| | | | |
| − | = Current Architecture = | + | ==Development== |
| | + | The development of the Architecture was carried out with those steps |
| | + | * starting with the as is situation, |
| | + | * over the analysis of the gaps, |
| | + | * following the definition of the capabilities, |
| | + | * structuring the capabilities to topics, |
| | + | * their evaluation and |
| | + | * the basic platform services |
| | | | |
| − | In a first step existing systems and tools are analysed.
| + | ==Future Architecture== |
| | | | |
| − | The topology shows the various systems and its current owners. | + | === Principles === |
| | + | The basis for the future architecture are described under [[Architecture Principles]]. |
| | | | |
| − | For those systems the business objects were determined and in a second step the workflows between the business objects.
| + | === Build Blocks === |
| | + | The Building Blocks of the future platform are described |
| | + | === Roadmap === |
| | + | The roadmap to establish the RFF Digital platform ecosystem is worked out under [[Architecture Roadmap]] |
| | | | |
| − | All information is stored in Enterprise Architect in a common UML Model. A HTML copy of the model can be found here: [https://rff.models.interconnective.ch/model/latest/ UML Model]
| + | === Services === |
| | + | The [[Services]] that are offered on the RFF Digital Platform are grouped in |
| | + | * [[Business Services]] and |
| | + | * [[Facility Services]] |
| | | | |
| − | == Topology == | + | == Evolution == |
| − | | + | The architecture is developed in iterations. |
| − | The topology shows currently existing systems and tools that are analysed in details. The following links guide you to the corresponding architecture models
| + | * [[Architecture Development|ARCH 2020]] |
| − | | + | * [[ARCH 2021]] |
| − | The main systems are:
| + | * [[ARCH 2022]] |
| − | | |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=C74DDC6B-B33F-4b53-90CC-C51370B05152 GCU Broker]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=9B8A5B35-FF7F-4ae8-92AA-F9FB3AA2E1E1 RailData ORFEUS and ISR]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=8DFF41BF-7346-4e21-A631-D2FEA6E113F6 xRail Broker]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=C42D445B-8177-41b6-B0A0-F1D04CEE2CF9 RNE PCS, TIS and CRD]
| |
| − | | |
| − | [[File:UML_Model.png|border|600px|UML model]]
| |
| − | | |
| − | The topology can be found here: [https://rff.models.interconnective.ch/model/latest/index.htm?guid=C2517A10-E2E1-4079-9A71-380A0DB5A334 UML Model - Topology]
| |
| − | | |
| − | The following picture shows the platform coverage
| |
| − | | |
| − | [[File:Platform_coverage.png|border|800px]]
| |
| − | | |
| − | == 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
| |
| − | | |
| − | [[File:Business_obejcts.png|border]]
| |
| − | | |
| − | | |
| − | The topology can be found here: [https://rff.models.interconnective.ch/model/latest/index.htm?guid=8D39FDD0-C34E-4200-B1AB-3A9D7DD6AA29 UML Model - Business Objects]
| |
| − | | |
| − | Detailed Business Objects are available for
| |
| − | | |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=66C69BDD-81D8-428f-9F62-2A0AA2340BA8 GCU Broker]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=83936096-163F-493f-AA47-67EE97925351 RailData]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=20C2DAE5-FF43-4b93-9F41-E2EF7D64AF9D RNE]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=CF6450D5-2932-4720-842D-9487E13F7229 xRail]
| |
| − | | |
| − | == Workflows ==
| |
| − | | |
| − | The workflows describe the interaction of the business objects of todays systems
| |
| − | | |
| − | [[File:Workflows.png|border]]
| |
| − | | |
| − | Each workflow is described with a swimlane diagram in details
| |
| − | | |
| − | [[File:Swimlane.png|border]]
| |
| − | | |
| − | 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 [https://rff.models.interconnective.ch/model/latest/index.htm?guid=4BE8AF90-5F80-445f-A373-C9171711C79B 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 in Teams: [[https://teams.microsoft.com/l/file/155B0089-7919-496C-9775-0DC99CA378D1?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xlsx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FList_of_Limitations_Capabilities_NFR_SAFE.xlsx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f| Messages and Objects]]
| |
| − | | |
| − | Refer to the sheet '''Messages'''.
| |
| − | | |
| − | = Perspectives =
| |
| − | | |
| − | Based on the [[Architecture#Business Objects|business objects]] and [[Architecture#Workflows|workflows]] of [[Architecture#Current Architecture|todays systems]] the services are extracted into abstract layers combining services from various systems.
| |
| − | | |
| − | [[File:perspectives.png|border|center]]
| |
| − | | |
| − | == Steps ==
| |
| − | | |
| − | The steps (see bullet points) for doing that are:
| |
| − | | |
| − | # Describe the processes and platforms (done in the [[Architecture#Current Architecture|current architecture]])
| |
| − | # Remove platform borders keeping processes and objects
| |
| − | # Analysis of the services based on vision, governance and principles
| |
| − | # Aggregation of the found limitations
| |
| − | # Description of gaps (based on found limitations)
| |
| − | # Align services towards future architecture
| |
| − | | |
| − | == Perspectives and links to Processes, Objects, Limitations and Capabilities ==
| |
| − | | |
| − | Each perspective is assigned to a process and contains the process steps taken out of one of the systems currently covering this perspective. In the UML model the perspectives are described in detail. The following picture shows what can be found for each perspective.
| |
| − | | |
| − | [[File:Perspective_process_object.png|border|center]]
| |
| − | | |
| − | In the upper area of the perspective you find the <span style="color:#ff0000; font-weight:bold">Processes</span> that are covered with this perspective. Below the <span style="color:#ff0000; font-weight:bold">Workflows</span> for RUs and Partners as well as additional <span style="color:#ff0000; font-weight:bold">Digital Platform Workflows</span> are described using swimlanes.
| |
| − | | |
| − | <span style="color:#ff0000; font-weight:bold">Use cases</span> are described in the form of bubbles, showing involved actors.
| |
| − | | |
| − | <span style="color:#ff0000; font-weight:bold">Business Objects</span> (blue) and <span style="color:#ff0000; font-weight:bold">Masterdata</span> (grey) covered by this perspective are described in the lower area of the perspective.
| |
| − | | |
| − | <span style="color:#ff0000; font-weight:bold">Limitations</span> found in the current perspective are positioned where they occur (activity, business object or below the processes for general limitations) and described with boxes (orange/brown).
| |
| − | | |
| − | <span style="color:#ff0000; font-weight:bold">Sector Initiatives</span> belonging to this perspective that are not yet covered by a system or not yet described in the UML model are described with arrow-boxes (green).
| |
| − | | |
| − | Limitations are described in detail in a separate document. This document can be found here: [[https://teams.microsoft.com/l/file/155B0089-7919-496C-9775-0DC99CA378D1?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xlsx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FList_of_Limitations_Capabilities_NFR_SAFE.xlsx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f| List of Limitations]]
| |
| − | | |
| − | == Todays Perspectives ==
| |
| − | | |
| − | The following perspectives were identified. The ones that contain a link are already defined and described in the UML Model.
| |
| − | | |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=102D0A88-53AE-44ec-951A-2438EB954F4B Train Service Planning]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=C1EF6837-8470-4b8b-90E4-B790F913D1F3 Train Preparation]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=C3D069F0-FBCC-4cb8-B815-D2D19EB44FBE Train Operation]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=B854291A-E09D-4d56-B920-11ACBF6B14FC Wagon Status]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=FDDD87B2-32AA-4693-AFA1-6F5DD53E34A3 Wagon Performance]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=7B38AC84-329F-49f1-9CCD-DCED78A85AEF Wagon Damage]
| |
| − | * Wagon Check
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=78CCA4EF-8188-4e15-9DD4-2CC2BDCD8878 Order Consignment]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=07DBC82A-88EE-401a-97B2-ED3904530BBE Braking Rules]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=215C665F-7BF6-47a1-A1C1-B9816B7476D3 Rolling Stock Dataset]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=1B7C860B-2460-4654-8521-A42D20B38AB6 Shipment Booking]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=5C17FC43-EAB1-4b6e-864E-C68DC216CB38 Shipment Status]
| |
| − | | |
| − | == Further possible Perspectives ==
| |
| − | | |
| − | Addtionally the following possible perspectives were identified. These perspectives may be analyzed in a later step.
| |
| − | | |
| − | * Transport Planning and Preparation
| |
| − | * Driver Service Book
| |
| − | * Driver Route Knowledge
| |
| − | * Locomotive Service Book
| |
| − | * Locomotive Master Data
| |
| − | | |
| − | The perspectives can be found in the [https://rff.models.interconnective.ch/model/latest/index.htm?guid=F5E37690-5FBF-4803-84A5-F7BF41F09A7B UML Model]
| |
| − | | |
| − | The list of limitations can be found here: [[https://teams.microsoft.com/l/file/155B0089-7919-496C-9775-0DC99CA378D1?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xlsx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FList_of_Limitations_Capabilities_NFR_SAFE.xlsx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f| List of Limitations]]
| |
| − | | |
| − | = Non-Functional Requirements =
| |
| − | | |
| − | Non-functional requirements describe additional requirements besides those derived from business objects and workflows
| |
| − | | |
| − | == Basic Principles ==
| |
| − | | |
| − | The following basic principles can help to find non-functional requirements:
| |
| − | | |
| − | * Authentication and Security
| |
| − | * Small-Player Access to Services
| |
| − | * Traceability
| |
| − | * API Management
| |
| − | * Testing and Integration
| |
| − | * Service Behaviour
| |
| − | * Security and Redundancy
| |
| − | | |
| − | Non functional requirements were analysed together with the limitations and capabilities were defined, that on the one hand solve existing limitations but on the other hand also cover non-functional requirements.
| |
| − | | |
| − | [[File:Nfr.png|border|center]]
| |
| − | | |
| − | A detailed description of the basic principles can be found here: [[https://teams.microsoft.com/l/file/81511ADC-8280-497E-897F-7012AF953F3E?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=pptx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FBasic_Principles_for_NFReq.pptx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f| Basic Principles]]
| |
| − | | |
| − | The list of non-functional requirements can be found here: [[https://teams.microsoft.com/l/file/155B0089-7919-496C-9775-0DC99CA378D1?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xlsx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FList_of_Limitations_Capabilities_NFR_SAFE.xlsx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f| Non-functional Requirements]]
| |
| − | | |
| − | <span id="_Limitations" class="anchor"></span>
| |
| − | | |
| − | = Limitations =
| |
| − | | |
| − | When talking about limitations, we are in the '''World of Problems'''.
| |
| − | | |
| − | Based on the description of the current systems with its [[Architecture#Business Objects|business objects]] and [[Architecture#Workflows|workflows]] the limitations of todays systems can be analysed by making use of the [[Architecture#Perspectives|perspectives]].
| |
| − | | |
| − | == Methodology ==
| |
| − | | |
| − | # Limitations are identified in workshops based on the perspectives
| |
| − | # Limitations found are documented in a spreadsheet and in the UML model
| |
| − | # in order to cluster the limitations
| |
| − | ## duplicates are eliminated (in the spreadsheet)
| |
| − | ## dependencies between limitations are documented in the UML model
| |
| − | # then the limitations are grouped into limitation groups in the UML model
| |
| − | # for each of the groups the benefits and impacts are defined
| |
| − | # all the groups are categorized in low, medium and high priorities
| |
| − | | |
| − | == Criteria ==
| |
| − | | |
| − | The criteria to select potential limitations are:
| |
| − | | |
| − | * Constitutional Governance
| |
| − | * Data Governance
| |
| − | * Service Shaping
| |
| − | * Accessibility
| |
| − | * Integration
| |
| − | * Master Data
| |
| − | * Identifiers
| |
| − | | |
| − | == Priorities ==
| |
| − | | |
| − | All limitations are analysed and priority for each limitation is set according the following criteria and scores
| |
| − | | |
| − | === Priority Criteria ===
| |
| − | | |
| − | ==== Problem Area (PA) ====
| |
| − | | |
| − | {| class="wikitable"
| |
| − | ! '''If the limitation belongs to problem area'''
| |
| − | ! '''then the score is'''
| |
| − | |-
| |
| − | | Data Quality
| |
| − | | 3
| |
| − | |-
| |
| − | | Coverage (Governance)
| |
| − | | 2
| |
| − | |-
| |
| − | | Functionality / Business Processes
| |
| − | | 1
| |
| − | |}
| |
| − | | |
| − | ==== Level (L) ====
| |
| − | | |
| − | {| class="wikitable"
| |
| − | ! '''If the limitation belongs to level'''
| |
| − | ! '''then the score is'''
| |
| − | |-
| |
| − | | L1
| |
| − | | 3
| |
| − | |-
| |
| − | | L2
| |
| − | | 2
| |
| − | |-
| |
| − | | L3
| |
| − | | 1
| |
| − | |}
| |
| − | | |
| − | ==== Dependencies (D) ====
| |
| − | | |
| − | {| class="wikitable"
| |
| − | ! '''If the limitation has the following dependencies'''
| |
| − | ! '''then the score is'''
| |
| − | |-
| |
| − | | other limitations are dependent on this (predecessor)
| |
| − | | 3
| |
| − | |-
| |
| − | | this limitation has no dependencies
| |
| − | | 2
| |
| − | |-
| |
| − | | this limitations depends on other limitations
| |
| − | | 1
| |
| − | |}
| |
| − | | |
| − | ==== Value Added (V) ====
| |
| − | | |
| − | {| class="wikitable"
| |
| − | ! '''If impact of the limitation is'''
| |
| − | ! '''then the score is'''
| |
| − | |-
| |
| − | | big
| |
| − | | 3
| |
| − | |-
| |
| − | | medium
| |
| − | | 2
| |
| − | |-
| |
| − | | small
| |
| − | | 1
| |
| − | |}
| |
| − | | |
| − | ==== Effort (E) ====
| |
| − | | |
| − | {| class="wikitable"
| |
| − | ! '''If the implementation effort of the limitation is'''
| |
| − | ! '''then the score is'''
| |
| − | |-
| |
| − | | small
| |
| − | | 3
| |
| − | |-
| |
| − | | medium
| |
| − | | 2
| |
| − | |-
| |
| − | | huge
| |
| − | | 1
| |
| − | |}
| |
| − | | |
| − | === Weighting ===
| |
| − | | |
| − | For each of the above mentioned criteria a relative weight is defined
| |
| − | | |
| − | {| class="wikitable"
| |
| − | ! '''Criteria'''
| |
| − | ! '''Weight'''
| |
| − | |-
| |
| − | | Problem Area (PA)
| |
| − | | 3
| |
| − | |-
| |
| − | | Level (L)
| |
| − | | 1
| |
| − | |-
| |
| − | | Dependencies (D)
| |
| − | | 2
| |
| − | |-
| |
| − | | Value Added (V)
| |
| − | | 3
| |
| − | |-
| |
| − | | Effort (E)
| |
| − | | 2
| |
| − | |}
| |
| − | | |
| − | === Ranking ===
| |
| − | | |
| − | Based on sum of the scores of each criteria, multiplied with the weighting of the criteria an individual priority of each limitation results
| |
| − | | |
| − | <nowiki>Priority = (Score PA * Weight PA) + (Score L * Weight L) + (Score D * Weight D) + (Score V * Weight V) + (Score E * Weight E)</nowiki>
| |
| − | | |
| − | The priority of each limitation varies within the range of 1 and 10.
| |
| − | | |
| − | The higher the priority value the higher the ranking of a limitation.
| |
| − | | |
| − | === SAFe Ranking ===
| |
| − | | |
| − | The limitations were ranked additionally according to the SAFe Methodology (Scaled Agile Framework) in order to analyse the limitations in a longer planning horizon and set priorities accordingly.
| |
| − | | |
| − | The lower the SAFe for a limitation, the higher is the priority to act.
| |
| − | | |
| − | <nowiki>SAFe = Score E / Score VA / Score PA</nowiki>
| |
| − | | |
| − | * the higher the effort, the higer the SAFe, meaning, the lower is the priority to act.
| |
| − | * the higher the value added and/or the problem are, the lower is the SAFe, meaning, the higher is the priority to act.
| |
| − | | |
| − | == Conclusion ==
| |
| − | | |
| − | Based on the above described methodology the following 26 highly ranked limitations were found
| |
| − | | |
| − | [[File:Ranked_limitations.png|border|center|Ranked Limitations]]
| |
| − | | |
| − | When looking at the coverage of the various clusters, the following picture shows up:
| |
| − | | |
| − | [[File:Cluster_coverage.png|center|border]]
| |
| − | | |
| − | [[File:Prinicple_coverage.png|border|center]]
| |
| − | | |
| − | The first 19 of the top 26 limitations are related to Data Quality (out of 21 limitations), 4 limitations are related to governance and 1 limitation is related to functionality. Within the first 26 top ranked limitations business related limitations cannot be found.
| |
| − | | |
| − | == Documents ==
| |
| − | | |
| − | A detailed description of the weighting criteria can be found here: [[https://teams.microsoft.com/l/file/14097509-0FCF-4F43-99B7-F97196A1E290?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=pptx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FEvaluation_Criteria_Limitations.pptx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f| Criteria for Limitations]]
| |
| − | | |
| − | The list of limitations can be found in the following spreadsheet: [[https://teams.microsoft.com/l/file/155B0089-7919-496C-9775-0DC99CA378D1?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xlsx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FList_of_Limitations_Capabilities_NFR_SAFE.xlsx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f| List of Limitations]]
| |
| − | | |
| − | An overview of all limitations can also be found in the [[https://rff.models.interconnective.ch/model/latest/index.htm?guid=176A4576-5CFF-46cb-81E7-0F0E0F89812B | UML Model]]
| |
| − | | |
| − | Additionally you find the dependencies of limitations in the [[https://rff.models.interconnective.ch/model/latest/index.htm?guid=4BF3722E-615C-4740-BC93-E7C62AA64412 | UML Model]]
| |
| − | | |
| − | = Capabilities =
| |
| − | | |
| − | When talking about capabilities and gaps, we are in the '''World of Solutions'''.
| |
| − | | |
| − | Capabilities are derived from the [[Architecture#Limitations|limitations]] by taking into consideration the vision, governance and principles layed down by the CIOs.
| |
| − | | |
| − | Gaps result when future capabilities cannot be fulfilled with [[Architecture#Current Architecture|existing systems]] due to [[Architecture#Limitations|limitations]] of the existing systems.
| |
| − | | |
| − | They are the basis for the planning of development initiatives.
| |
| − | | |
| − | == Methodology ==
| |
| − | | |
| − | Based of the priorised groups of limitations the capabilities are elaborated:
| |
| − | | |
| − | # Definition of the capabilitity targets (what do we want)
| |
| − | ## out of the limitations
| |
| − | ## from platform requirements
| |
| − | ## from the vision
| |
| − | # Link the capabilities with the groups of limitations
| |
| − | # Elaborate the gaps between the groups of limitations and the expected capabilities
| |
| − | # Work out solution variants for the gaps, clearly describing
| |
| − | ## functionality
| |
| − | ## implementation effort (T-Shirt size, XS-S-M-L-XL)
| |
| − | ## implementation duration
| |
| − | ## affected stakeholders
| |
| − | # Assess the solution variants
| |
| − | # Decide about the final solution variants to be implemented
| |
| − | | |
| − | The result of this work is a backlog of solutions, that can be implemented in the '''World of Implementation'''.
| |
| − | | |
| − |
| |
| − | | |
| − | The capabilities can be found in the UML Model.
| |
| − | | |
| − | [[File:Limitations.png|center|border]]
| |
| − | | |
| − | They are linked with the limitations and non functional requirements.
| |
| − | | |
| − | Details can either be found directly in the Capability object or in the capabilities sheet [[https://teams.microsoft.com/l/file/155B0089-7919-496C-9775-0DC99CA378D1?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xlsx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FList_of_Limitations_Capabilities_NFR_SAFE.xlsx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f| here]].
| |
| − | | |
| − | == Capabilities Overview ==
| |
| − | | |
| − | The following areas were considered when looking for future capabilities. The links refer to the UML model, where you find the details for the capabilities of the corresponding area.
| |
| − | | |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=FE95617F-DD32-4c5e-AE8A-3F4C23F65FE1 Location Identification]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=FA4A9698-4110-4461-A9FC-13D6B2C8F9A8 Train Identification]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=F1FF5686-5643-43f7-BA22-81C200527969 Train Operations]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=3CF4BEB8-7513-4c1b-9E35-20484D49B5EB Wagon Status]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=B4492CAE-BF01-4567-8BA8-E51357BEE7DB Wagon Damage]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=A045F24B-1ABE-43c8-AC01-3846373AAFE7 Wagon Performance]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=9C889264-BD33-42fd-8848-E2954B8455A7 Rolling Stock]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=E54FD396-21A5-4655-ABC4-C4A97A4E7753 Train Preparation]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=9FAB6655-3100-40ae-A035-681AA86471ED Braking Rules]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=C7074BD9-0C71-4d99-83F1-5E2913A0E90E Shipment Booking]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=A26F6D4A-D3C9-45ff-A886-D2B8B7315C30 Shipment Order]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=9137A319-4855-475e-8C9B-752137542249 Train Service Planning]
| |
| − | * [https://rff.models.interconnective.ch/model/latest/index.htm?guid=B2F38FEF-4AEA-4e1d-A1E5-941B5DA960A5 Intermodal Traffic]
| |
| − | | |
| − | == Weighting and Ranking ==
| |
| − | | |
| − | All capabilities found were evaluated and a weighting added to each of the capabilities. The following approach was used to rank the capabilities:
| |
| − | | |
| − | === Select Capabilities Along Limitation Ranking ===
| |
| − | | |
| − | # All limitations with a priority higher than 8 were selected, which results in 26 limitations
| |
| − | # All capabilities that solve these limitations were selected and the priority of the capability was set to the priority of the limitation with the highest priority
| |
| − | | |
| − | This results in '''22 capabilities'''
| |
| − | | |
| − | === Independent Evaluation of all Capabilities ===
| |
| − | | |
| − | All capabilities were evaluated independently as follows
| |
| − | | |
| − | <ol style="list-style-type: decimal;">
| |
| − | <li><blockquote><p>estimated the cost of each capability<br />
| |
| − | (3=low/<200k€, 2=medium/200k€-1M€, 1=high/>1M€)</p></blockquote></li>
| |
| − | <li><blockquote><p>estimated the benefit of each capability<br />
| |
| − | (3=high, 2=medium, 1=low)</p></blockquote></li>
| |
| − | <li><blockquote><p>calculated the SAFE-factor for each capability<br />
| |
| − | SAFE = 1/cost/benefit (SAFE varies between 0.11 and 1)</p></blockquote></li>
| |
| − | <li><blockquote><p>excluded the capabilities already ranked along limitation ranking</p></blockquote></li>
| |
| − | <li><blockquote><p>sorted remaining capabilities according to ascending SAFE</p></blockquote></li>
| |
| − | <li><blockquote><p>selected capabilities with a SAFE-factor = 0.11</p></blockquote></li></ol>
| |
| − | | |
| − | This results in '''14 capabilites'''
| |
| − | | |
| − | === Additional Capabilities ===
| |
| − | | |
| − | At the end additional capabilities were selected that have a link to one of the above selected capabilities, since these capabilities have to realized together with the already selected capabilities in order to achieve the expected result.
| |
| − | | |
| − | This results in '''18 additional capabilities'''.
| |
| − | | |
| − | The 54 selected capabilities (of 105, 51%) solve at least 75 limitations (of 201, 37%)
| |
| − | | |
| − | == Conclusion ==
| |
| − | | |
| − | The 54 capabilities found cover almost all clusters
| |
| − | | |
| − | [[File:Capa_conclusion1.png|border|center]]
| |
| − | | |
| − | Within these 54 capabilites, only capabilites for Braking Rules do not appear. Their ranking is too low to appear in the list of ranked capabilities.
| |
| − | | |
| − | When clustering the 36 main capabilities (without the related ones), the following situation shows up
| |
| − | | |
| − | [[File:Capa_conclusion2.png|border|center]]
| |
| − | | |
| − | In the overview document of all capabilities (here), an even more detailed view of the capabilities and the covered limitations can be found.
| |
| − | | |
| − | [[File:Capa_conclusion3.png|border|center]]
| |
| − | | |
| − | The list of capabilities can be found here: [[https://teams.microsoft.com/l/file/155B0089-7919-496C-9775-0DC99CA378D1?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xlsx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FList_of_Limitations_Capabilities_NFR_SAFE.xlsx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f | List of Capabilities]] (as part of the List of Limitations). Each limitation described in this document has a link into the UML model.
| |
| − | | |
| − | Capabilities can also be found in the UML Model directly: [[https://rff.models.interconnective.ch/model/latest/index.htm?guid=733271D6-62C1-434d-90F8-3F7FD04C2FBB | here]]
| |
| − | | |
| − | = Data Objects =
| |
| − | | |
| − | == Objects of Existing Platforms ==
| |
| − | | |
| − | Based on [[Architecutre#Current Architecture|existing platforms]], objects were identified that will also be the basis for the future platform.
| |
| − | | |
| − | [[File:Objects_overview.png|center|border]]
| |
| − | | |
| − | see [https://rff.models.interconnective.ch/model/latest/index.htm?guid=AAB1D8C4-CEB2-4967-8F0A-DD160301A9CC |UML-Model]
| |
| − | | |
| − | Considered Platforms and Objects are:
| |
| − | | |
| − | * Xrail (yellow)
| |
| − | ** Shipment
| |
| − | ** Transport Plan
| |
| − | ** Booking
| |
| − | ** Trip Plan
| |
| − | ** ETA Deviation
| |
| − | * RNE (red)
| |
| − | ** Train Running Information
| |
| − | ** Path Coordination
| |
| − | ** Path Details
| |
| − | ** Train Route
| |
| − | ** Case Reference
| |
| − | ** Train Service
| |
| − | * RailData (green)
| |
| − | ** Wagon Status
| |
| − | ** Consignment Note
| |
| − | ** Train Composition
| |
| − | * GCU (blue)
| |
| − | ** Wagon Performance
| |
| − | ** Wagon Damage
| |
| − | ** Wagon Technical Data
| |
| − | ** Rolling Stock Data Set | |
| − | | |
| − | == Access Rights ==
| |
| − | | |
| − | For each of the above mentioned objects and all their attributes the accessibility on the future platform was defined. The following levels of accessibility were defined:
| |
| − | | |
| − | {| class="wikitable"
| |
| − | ! Closed
| |
| − | ! no data exchange is allowed
| |
| − | |-
| |
| − | | Restricted
| |
| − | | object is visible and accessible within the future platform if there is a contract or license to use the information
| |
| − | |-
| |
| − | | Internal
| |
| − | | object is visible and accessible within the future platform if role using the object is involved in the corresponding traffic or transaction
| |
| − | |-
| |
| − | | External
| |
| − | | object is visible and accessible by everybody
| |
| − | |}
| |
| − | | |
| − | per default, the access right to an object in the future platform, the level is Internal.
| |
| − | | |
| − | == Stakeholders and Roles ==
| |
| − | | |
| − | === Roles ===
| |
| − | | |
| − | Stakeholders accessing the objects on the future platform can have different roles. For each of these roles, the access rights to the objects can be different.
| |
| − | | |
| − | The following roles were identified:
| |
| − | | |
| − | {| class="wikitable"
| |
| − | ! Roles
| |
| − | |-
| |
| − | | Lead RU
| |
| − | |-
| |
| − | | Participating RU
| |
| − | |-
| |
| − | | Wagon Keeper
| |
| − | |-
| |
| − | | Infrastructure Manager
| |
| − | |-
| |
| − | | Yard Manager
| |
| − | |-
| |
| − | | Customer
| |
| − | |-
| |
| − | | Freight Forwarder
| |
| − | |-
| |
| − | | Port Authority
| |
| − | |-
| |
| − | | Terminal Operator
| |
| − | |-
| |
| − | | Intermodal Operator
| |
| − | |-
| |
| − | | Customs Handler
| |
| − | |-
| |
| − | | Third Party
| |
| − | |-
| |
| − | | Wagon Maintenance Workshop
| |
| − | |}
| |
| − | | |
| − | === Primary and Secondary Receivers ===
| |
| − | | |
| − | For the stakeholders primary and secondary receivers were differentiated:
| |
| − | | |
| − | {| class="wikitable"
| |
| − | ! Role
| |
| − | ! Colour
| |
| − | ! Description
| |
| − | |-
| |
| − | | Primary Receiver
| |
| − | | green
| |
| − | | a primary receiver needs the object/information in order to properly handle its business
| |
| − | |-
| |
| − | | Secondary Receiver
| |
| − | | yellow
| |
| − | | secondary receivers are interested in the information helping them to handle their business but the information is not mandatory to manage the business.
| |
| − | |}
| |
| − | | |
| − | == Object - Stakeholder Matrix ==
| |
| − | | |
| − | For each combination of object/attribute and stakeholder/role the access right of that stakeholder/role to the object/attribute was defined according to the defined access right levels.
| |
| − | | |
| − | [[File:Object_stakeholder_matrix.png|center|border]]
| |
| − | | |
| − | Example: access rights of Train Composition object and its attributes (grey fields: not of interest, green fields: primary receiver)
| |
| − | | |
| − | The full matrix can be found here: [[https://teams.microsoft.com/l/file/E7EE7A71-3944-4DDE-AD73-BCDF5AB60DBB?tenantId=ef588fbf-8705-4200-a1a6-3be9fc3bb45b&fileType=xlsx&objectUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms%2FShared%20Documents%2FEU%20data%20platforms%2FPhase%201%2FShare-2%2F01_Architecture%2FDocuments%2FObject_Receiver_Mapping.xlsx&baseUrl=https%3A%2F%2Fxrail.sharepoint.com%2Fsites%2FRFFDigitalplatforms&serviceName=teams&threadId=19:2ae0c3a808134862b280a79d6edb3cc4@thread.tacv2&groupId=e8f92e7a-8d91-4214-9fe7-28b21e040c7f| Object - Stakeholder Matrix]]
| |
| − | | |
| − | == Analysis and Conclusions ==
| |
| − | | |
| − | === Distribution of Stakeholder ===
| |
| − | | |
| − | [[File:Stakebholder_distribution.png|border|center]]
| |
| − | | |
| − | 63.3% of new stakeholders making use of the objects provided on the future platform are RUs. So RUs profit most from the addtional information provided on the platform.
| |
| − | | |
| − | On the other hand a third of the new stakeholders are none-RU stakeholders. This is an opportunity to sell the services of the new future platform to interested parties.
| |
| − | | |
| − | === Primary Receivers ===
| |
| − | | |
| − | [[File:Primary_receivers.png|border|center]]
| |
| − | | |
| − | 97.5% of the objects necessary for a primary receiver to do the job have an access level of internal, meaning that the receiver can access the object for the corresponding transaction or traffic.
| |
| − | | |
| − | === Secondary Receivers ===
| |
| − | | |
| − | [[File:Secondary_receivers.png|center|border]]
| |
| − | | |
| − | More than half of the objects can be accessed by the secondary receivers on an internal level. For a third of the objects/information the secondary receiver needs a contract or license to access the information.
| |
| − | | |
| − | Only 8 % of the objects/information is not accessible by secondary receivers.
| |
| − | | |
| − | === Consumption of Objects ===
| |
| − | | |
| − | [[File:Consumption.png|center|border]] | |
| − | | |
| − | When looking at who is consuming information it is interesting, that customers, freight forwarders, intermodal operators, customs handlers and third parties profit as secondary receivers from the objects/information provided by the future platform
| |
| − | | |
| − | Existing receivers like RUs, wagon keepers and IMs only profit limited from the additional objects provided, but several new receivers like yard managers, port authorities and terminal operators can profit massively from the new platform.
| |
| − | | |
| − | = Smart Services =
| |
| − | | |
| − | = Target Architecture =
| |
| − | | |
| − | This chapter describes the methodology to find the target architecture as well as the overview of the future target architecture with its basic framework concept.
| |
| − | | |
| − | The architecture is based on the [[\l|capabilities ]]and [[\l|smart services ]]and has the aim to close the identified [[\l|limitations]].
| |
| − | | |
| − | It takes into account [[\l|non-functional requirements]].
| |
| − | | |
| − | == The role of the RU community ==
| |
| − | | |
| − | In order to build up a future architecture, the RU community takes an important role.
| |
| − | | |
| − | It
| |
| − | | |
| − | * coordinates all RU interests
| |
| − | * represents small and large RUs
| |
| − | * acts as a cooperation body between RUs, Wagon Keepers, IMs (RNE) and other interested third parties.
| |
| − | * has the force to harmonize strategically and tactically
| |
| − | * can provide lobbying and marketing
| |
| − | * can participate as strong partner in standardization efforts
| |
| − | | |
| − | [[File:media/image26.png|410x234px]]
| |
| − | | |
| − | <span id="_Toc56062996" class="anchor"></span>Figure 23 - RU Community
| |
| − | | |
| − | == Platform Approaches ==
| |
| − | | |
| − | === Todays Situation ===
| |
| − | | |
| − | Today, each participant in the railway business has to connect itself to a variety of tools and platforms in order to exchange information with other participants.
| |
| − | | |
| − | [[File:media/image27.png|405x261px]]
| |
| − | | |
| − | <span id="_Toc56062997" class="anchor"></span>Figure 24 - Platforms Today
| |
| − | | |
| − | === Pilot for new Digital Platforms ===
| |
| − | | |
| − | Instead of decomposing and rebuilding todays available and proven platforms and tools a hub could be built up that hides todays platforms and tools and provides unique access in one place. The functionality of the hub can be reduced for small RUs and can provide various interaction possibilities for large RUs.
| |
| − | | |
| − | [[File:media/image28.png|405x266px|Ein Bild, das Monitor, Screenshot, Bildschirm, Anzeige enthält. Automatisch generierte Beschreibung]]
| |
| − | | |
| − | <span id="_Toc56062998" class="anchor"></span>Figure 25 - Pilot for New Platform
| |
| − | | |
| − | The advantage of this pilot are:
| |
| − | | |
| − | * Fast integration of available platforms and tools
| |
| − | * One single "Point of Contact" for RUs to exchange information
| |
| − | * Independence of the participants from changes in the underlying platforms and tools
| |
| − | | |
| − | === Evolution into Smart Services ===
| |
| − | | |
| − | Once these hubs are established, the underlying platforms and tools can be decomposed into smart services and new services can be added easily.
| |
| − | | |
| − | [[File:media/image29.png|435x282px]]
| |
| − | | |
| − | <span id="_Toc56062999" class="anchor"></span>Figure 26 - Evolution into Smart Services
| |
| − | | |
| − | In order to take the best out of the existing platforms, tools and systems, the best of all of todays applications can be selected and new smart services be built around this best breed.
| |
| − | | |
| − |
| |
| − | | |
| − | The RU community has a lot of opportunities and unique selling propositions to build up such an integrated platform:
| |
| − | | |
| − | * Best Governance
| |
| − | * CEO Integration
| |
| − | * EU Lobbying
| |
| − | * 450 Members
| |
| − | * Long Term Experience (25 years +)
| |
| − | * All major use cases covered
| |
| − | * agile and flexible approach
| |
| − | * modern IT platform
| |
| − | | |
| − | == Organization ==
| |
| − | | |
| − | === Todays Situation ===
| |
| − | | |
| − | Each existing platform today has a management organization, a business team and an IT design and service team.
| |
| − | | |
| − | [[File:media/image30.png|428x205px|Ein Bild, das Haufen, verschieden, viele, Anzeige enthält. Automatisch generierte Beschreibung]]
| |
| − | | |
| − | <span id="_Toc56063000" class="anchor"></span>Figure 27 - Organization Today
| |
| − | | |
| − | === Future Platform Organization ===
| |
| − | | |
| − | When moving towards an integrated RU platform a new organization has to be established, consisting of a new management organization, a new business experts group and one or more IT design and service teams. Participants of the new platform organisation have to take seat in the management and business experts teams of existing platforms that are not incorporated into the RU platform but interact with this new platform
| |
| − | | |
| − | [[File:media/image31.png|428x217px|Ein Bild, das Haufen, Foto, viele, verschieden enthält. Automatisch generierte Beschreibung]]
| |
| − | | |
| − | <span id="_Toc56063001" class="anchor"></span>Figure 28 - Future Platform Organization
| |
| − | | |
| − | <span id="_Platform_Framework_Concept" class="anchor"></span>
| |
| − | | |
| − | == Platform Framework Concept ==
| |
| − | | |
| − | When building up an integrated RU platform, this platform has to provide, some important basic services in a framework besides the provisioning and distribution of data. These basic services are described in this platform framework concept.
| |
| − | | |
| − | === Overview ===
| |
| − | | |
| − | [[File:media/image32.png|486x340px]]
| |
| − | | |
| − | <span id="_Toc56063002" class="anchor"></span>Figure 29 - Platform Framework Concept
| |
| − | | |
| − | === The Services ===
| |
| − | | |
| − | ==== Quality Service ====
| |
| − | | |
| − | [[File:media/image33.png|97x106px]]
| |
| − | | |
| − | The quality Service provides a centralized monitoring of the quality of the data delivered to the platform.
| |
| − | | |
| − | It monitors
| |
| − | | |
| − | * the quality of each data item delivered to the platform | |
| − | * the availability of data
| |
| − | * the volume of data
| |
| − | | |
| − | It provides
| |
| − | | |
| − | * KPIs, thresholds and semaphores to the RFF board
| |
| − | * reports to RFF board and participating parties about the quality levels
| |
| − | | |
| − | ==== Content Service ====
| |
| − | | |
| − | [[File:media/image34.png|93x88px]] | |
| − | | |
| − | The Content Service provides means to interact with the data provided by the producers of data.
| |
| − | | |
| − | It allows to
| |
| − | | |
| − | * filter | |
| − | * aggregate
| |
| − | * anonymise
| |
| − | * generate information
| |
| − | * store data intermediately
| |
| − | | |
| − | It checks if access to data is allowed, based on the Identity Service.
| |
| − | | |
| − | It provides access to the data through the Channel Service.
| |
| − | | |
| − | ==== Identity Service ====
| |
| − | | |
| − | [[File:media/image35.png|79x87px]] | |
| − | | |
| − | The Identity Service provides information about rights and duties of human and system users.
| |
| − | | |
| − | It provides
| |
| − | | |
| − | * User Management
| |
| − | * rights and duties of human users
| |
| − | * rights and duties of systems
| |
| − | * information about rights and duties to other services within the RU platform
| |
| − | * protocol information to the Quality Service regarding access violations
| |
| − | * security checks based on given tokens and access protocols
| |
| − | | |
| − | ==== License Service ====
| |
| − | | |
| − | [[File:media/image36.png|94x77px]]
| |
| − | | |
| − | The License Service manages contracts and licenses
| |
| − | | |
| − | It allows
| |
| − | | |
| − | * to manage contracts and licenses
| |
| − | * to notify about timed-out licenses or contracts
| |
| − | * to notify about billing and invoicing
| |
| − | | |
| − | It informs the Identity Service about new, changed or expired access rights of a license or contract
| |
| − | | |
| − | ==== Channel Service ====
| |
| − | | |
| − | [[File:media/image37.png|84x93px]]
| |
| − | | |
| − | The Channel Service provides a clear definition of offered active communication protocols
| |
| − | | |
| − | It
| |
| − | | |
| − | * is a decentralized service offered by each platform system.
| |
| − | * provides a channel management (who is providing what in which format with which technology)
| |
| − | * ensures that offered channels are available and operating
| |
| − | * regularely checks the availability of end-to-end communication chains
| |
| − | * provides integration blueprints and basic functional test capabilities
| |
| − | * provides specifications for format conversions
| |
| − | | |
| − | = Migration Path =
| |
The architecture is developed in iterations.
