Difference between revisions of "Digital Platform Pilot"

From RFF Wiki
Jump to: navigation, search
(Use Cases)
(Use Cases)
Line 14: Line 14:
 
** UC_01 [[DS_05_UC_01|Send Wagonposition]]
 
** UC_01 [[DS_05_UC_01|Send Wagonposition]]
 
** UC_03 [[DS_05_UC_03|Forward Wagonposition]]
 
** UC_03 [[DS_05_UC_03|Forward Wagonposition]]
{{Strikethrough}} * DS_06 [[Digital Train Operations]]
+
{{Strike * DS_06 [[Digital Train Operations]] }}
{{Strikethrough}} ** UC_01 [[DS_06_UC_01|Collect all train related information (TRF, TRI)]]
+
{{Strike ** UC_01 [[DS_06_UC_01|Collect all train related information (TRF, TRI)]] }}
{{Strikethrough}} ** UC_02 [[DS_06_UC_02|Apply plausibility check (data quality)]]
+
{{Strike ** UC_02 [[DS_06_UC_02|Apply plausibility check (data quality)]] }}
{{Strikethrough}} ** UC_03 [[DS_06_UC_03|Inform registered users about train status]]
+
{{Strike ** UC_03 [[DS_06_UC_03|Inform registered users about train status]] }}
{{Strikethrough}} * DS_03 [[Digital Train Composition]]
+
{{Strike * DS_03 [[Digital Train Composition]] }}
{{Strikethrough}} ** UC_02 [[DS_03_UC_02|Convert from RU train composition to IM train composition]]
+
{{Strike ** UC_02 [[DS_03_UC_02|Convert from RU train composition to IM train composition]] }}
  
 
= Proof of Platform =
 
= Proof of Platform =

Revision as of 13:33, 26 September 2021

Introduction

In this pilot RFF DP proofs the concept (POC) of the digital services developed and hosted with Microsoft and its new developed OSCP framework.

To test the platform a list of use cases have been selcted based on an evaluation schema found on Sharepoint.

Use Cases

{{Strike * DS_06 Digital Train Operations }} {{Strike ** UC_01 Collect all train related information (TRF, TRI) }} {{Strike ** UC_02 Apply plausibility check (data quality) }} {{Strike ** UC_03 Inform registered users about train status }} {{Strike * DS_03 Digital Train Composition }} {{Strike ** UC_02 Convert from RU train composition to IM train composition }}

Proof of Platform

Four areas of interest have been proposed to test the MS framework

  • Data Highway

In this test area the ability of the framework is tested:

  1. to route messages securely, independent and reliable
  2. to convert messages for delivery
  3. to convert messages at reception
  4. to orchestrate and operate the message passing (rules, auth, monitor, error handling, access/delivery patterns)
  • Railway functionality

This area focuses on the functionalities of the platform for railway business

  1. commercial
  2. planning
  3. operation
  4. controlling
  5. safety related

What functions are available, which are on the MS roadmap, what is open?

  • Data model

MS announced that the framework is based on the standardized data model. The tests aim to learn how

  1. to use the data model for railway business
  2. to convert from existing railway (industry) standards
  3. to shape the data model and
  4. to learn the roadmap of the model
  • Clients/GUI

In this area the tests concentrate on GUI technologies for

  1. webbased clients
  2. mobile based clients (native, PWA, hybrid, ...) and
  3. the development stack (code base, cross over, lifecycle, supported platforms, ...)