Difference between revisions of "Phase2 Iteration4"

From RFF Wiki
Jump to: navigation, search
(Created page with "The Phase 2 works in iterations. See setup of the Architecture stream. == Iteration 4 == The fourth iteration lasts from 25.March to 15.April. === Topics === ==== Capabiliti...")
 
(→‎SM: SmartService Profile)
 
(6 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
=== Topics ===
 
=== Topics ===
 
==== Capabilities ====
 
==== Capabilities ====
−
The top most ranked capabilities from the [[Shopping List 2021| shopping list]] are treated in this third iteration.  
+
The top most ranked capabilities from the [[Shopping List 2021| shopping list]] are treated in this fourth iteration.  
−
Also tasks created during the work in the previous iterations are continued here.
+
Also tasks created during the work in the previous iterations are continued in this iteration.
  
 
==== A&B RU's requirements ====  
 
==== A&B RU's requirements ====  
 
We plan one or two introduction sessions for the interested type A&B RU partners.
 
We plan one or two introduction sessions for the interested type A&B RU partners.
 
Additionally the first Discovery Session will take place in this iteration.
 
Additionally the first Discovery Session will take place in this iteration.
−
So at the end of this iteration we can give a first insight of the new workshop format.
+
So at the end of this iteration we can give a first insight of the new workshop format: [[Discovery Session]]
  
 
==== SM: SmartService Profile ====
 
==== SM: SmartService Profile ====
−
Based on the [http://www.example.com Smart Services list] we will describe  
+
Based on the [[Smart Services]] we will describe  
 
* what the smart service is about
 
* what the smart service is about
 
* what is the aim
 
* what is the aim
Line 22: Line 22:
 
We have begun to create the first profiles and will continue in this iteration.
 
We have begun to create the first profiles and will continue in this iteration.
  
−
==== Legal and process related capa for TAF/P ====
+
==== C01: Managed CRD Location Masterdata ====
 +
The target of this task is to enhance the CRD masterdata to a level where it can be used as new GEO masterdata reference. We will start this task in this iteration 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
 +
We know that this task will accompany us for several iterations.
  
−
==== C43: Pilot WSM quality ====
+
==== C34: WPM KPI Web Monitor ====
 +
This task forsees to visualize the defined WPM KPI to support the WPM data quality maintenance.
 +
Each partner can access directly its dashboard to get an overview if and where its WPM data quality is below the expected level.
 +
 
 +
----
 +
 
 +
=== Reviews ===
 +
==== Smart Service profiles ====
 +
* SM_01 [[Optimize Asset Utilization]]
 +
* SM_13 [[Share Free Capacity]]
 +
* SM_21 [[GPC Triggered TRI]]
 +
* SM_22 [[WDI Enhancement for Last Mile]]
 +
* SM_23 [[TelematicData of Wagon]]
  
 
----
 
----
 +
 
=== Results ===
 
=== Results ===
−
==== A&B RU requirements ====
+
==== A&B RU's requirements ====  
−
In this task we had to enlarge the scope beyond TrainOperation and Consignment Note information.
+
We have planned to conduct an introduction sessions for the interested type A&B RU partners.
−
We have created a structure to learn about the "small" RUs situation and their needs.
+
and the first Discovery Session in this iteration.
−
For that we will organize sessions where we work out the (IT and process) surrounding in which those RUs operate.
+
* We have created 4 sessions with four seats available each.  
−
The actual planning foresees to have discovery sessions regularly every two weeks in the next months:
+
* We have sent out 30 invitations to RUs.
−
[[File:210225_DiscoverySessions_Structure.png|border|center|800px|Discovery Structure]]
+
In ten days we got one reservation. The interest is too low to start the sessions. Therefor we  reschedule the sessions. The topic will be discussed in the SteerCo and then we relaunch this task. [[Discovery Session]]
−
The content discussed in those sessions encompasses the topics a smaller RU is faced with:
 
−
[[File:210225_DiscoverySesions_Content.png|border|center|800px|Discovery Content]]
 
−
With this structure in place we will plan the discovery sessions for the next weeks.
 
−
Please help us and publish these sesssions internally in your company to attract many interested parties. The target group are type "A" and "B" RU (see below).
 
−
The preparation consists of three steps:
 
−
* Send a mail to RFF ARCH group
 
−
* Read the RFF introduciton slides and the entry questions in the questionnaire to acquaint yourself to the topics
 
−
* Register at MIRO to access the board used in the sessions
 
−
The material is available on [https://teams.microsoft.com/_#/files/Architecture?threadId=19%3A2ae0c3a808134862b280a79d6edb3cc4%40thread.tacv2&ctx=channel&context=BasicMaterial&rootfolder=%252Fsites%252FRFFDigitalplatforms%252FShared%2520Documents%252FEU%2520data%2520platforms%252FPhase%25202%252FRU%2520architecture%2520meetings%2520-%2520full%2520round%252FDiscoverySessions%252FBasicMaterial Basic Material for Discovery Sessions].
 
−
===== Small RU =====
 
−
The term Small RU is for our purpose too vage and may lead to different interpretations. Our distinction is focused on what type of IT the RU is using:
 
−
* Office and webbbased IT: The RU requires both external webbased and mobile clients and he needs a Office based integration. Some steps in the use cases are covered by manual interactions. He requires webbased or mobile Apps to enable him to participate in the common data transfer.
 
−
* Lean, off-the-shelf IT: The RU runs off-the-shelf software with "standard" apdapters for different services. Some advanced use cases are not supported by his systems and are (semi)- manually. He is looking for suitable interfaces to conntect to the off-the-shelf adapters.  
 
−
* Extensive, tailor made IT: The RU runs tailor made software adpated to his specific needs. This can be based on off-the-shelf software too which was tailored to an importent degree according to his needs. He wants to evolve his IT landscape frictionless and secure the return on his investments. The volume of transactions don't allow (semi)- manual processes. He looks for external services that helps him to streamline his processes internally and to innovate the next service types.
 
−
This leads to different requirements for digital platforms.
 
−
Therefor we differentiate in our context between the three RU types:
 
−
* '''A'''pp based RU (web, mobile, office)
 
−
* '''B'''asic API oriented RU (based on sector standards)
 
−
* '''C'''omprehensive service oriented RU (full service context)
 
−
This is a model to distinct between the different needs of such a schematic sketched RU.
 
−
In real life a RU may combine several of those types. He may run a tailor made, extensive commercial system (so type C RU). In production he plans with webbased tools (type A RU) and he operates his transports with an off-the-shelf product (type B RU).
 
  
 
==== SM: SmartService Profile ====
 
==== SM: SmartService Profile ====
 
Based on the Smart Services list we have described the following Smart Services.
 
Based on the Smart Services list we have described the following Smart Services.
−
* SM_01 [[Optimize Asset Utilization]]
+
* SM_08 [[Siding Everywhere]]
−
* SM_13 [[Share Free Capacity]]  
+
* SM_17 [[Facilities on location]]
−
* SM_21 [[GPS triggered TRI]]
+
* SM_24 [[Authority Communication]]
−
* SM_22 [[WDI Enhancement for Last Mile]]
 
−
* SM_23 [[TelematicData of Wagon]]
 
 
We will continue to describe the next [[Smart Services]].
 
We will continue to describe the next [[Smart Services]].
 
With these profiles we can then start the discussion with the CIO/steering committee on prioritization.
 
With these profiles we can then start the discussion with the CIO/steering committee on prioritization.
  
−
==== Legal and process related capa for TAF/P ====
+
==== Coverage Map ====
−
We have collected all capabilities with legal issues for the usage in sessions with ERA/EU to discuss the development of European standards.
+
As announced we have created the first [[Coverage Map]]s to make
−
The list of gaps and capabilities is available here.
+
* the usage and  
−
 
+
* data quality efforts
−
==== C14: Pilot WSM quality ====
+
on the digital platforms transparent.
−
We have finished the work on the WSM KPI pilot to learn and prove the RFF KPI maintenance process. With this we are able to propose the appropriate data quality maintenance process and necessary reports. We reached the aim to close the pilot at the end of iteration 3 and proceed now with the normal data quality maintenance process.
+
Please check your company "colours" and indicate wrong values.
  
−
==== C34: Implement WPM quality ====
+
==== C34: RSDS Office Integration ====
−
The implementation of the measurement of the defined KPIs is ongoing and needs to finish before we can start the WPM pilot in Iteration 5.
 

Latest revision as of 15:43, 13 April 2021

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

Iteration 4

The fourth iteration lasts from 25.March to 15.April.

Topics

Capabilities

The top most ranked capabilities from the shopping list are treated in this fourth iteration. Also tasks created during the work in the previous iterations are continued in this iteration.

A&B RU's requirements

We plan one or two introduction sessions for the interested type A&B RU partners. Additionally the first Discovery Session will take place in this iteration. So at the end of this iteration we can give a first insight of the new workshop format: Discovery Session

SM: SmartService Profile

Based on the Smart Services we will describe

  • what the smart service is about
  • what is the aim
  • which needs does it cover and
  • what is the potential benefit of it.

We have begun to create the first profiles and will continue in this iteration.

C01: Managed CRD Location Masterdata

The target of this task is to enhance the CRD masterdata to a level where it can be used as new GEO masterdata reference. We will start this task in this iteration 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

We know that this task will accompany us for several iterations.

C34: WPM KPI Web Monitor

This task forsees to visualize the defined WPM KPI to support the WPM data quality maintenance. Each partner can access directly its dashboard to get an overview if and where its WPM data quality is below the expected level.

Reviews

Smart Service profiles

Results

A&B RU's requirements

We have planned to conduct an introduction sessions for the interested type A&B RU partners. and the first Discovery Session in this iteration.

  • We have created 4 sessions with four seats available each.
  • We have sent out 30 invitations to RUs.

In ten days we got one reservation. The interest is too low to start the sessions. Therefor we reschedule the sessions. The topic will be discussed in the SteerCo and then we relaunch this task. Discovery Session

SM: SmartService Profile

Based on the Smart Services list we have described the following Smart Services.

We will continue to describe the next Smart Services. With these profiles we can then start the discussion with the CIO/steering committee on prioritization.

==== Coverage Map ==== As announced we have created the first Coverage Maps to make

  • the usage and
  • data quality efforts

on the digital platforms transparent. Please check your company "colours" and indicate wrong values.

C34: RSDS Office Integration

Retrieved from "https://rff.wiki.interconnective.ch/index.php?title=Phase2_Iteration4&oldid=1270"