Difference between revisions of "Phase2 Iteration8"

Revision as of 14:19, 2 July 2021 (view source) Sfr (talk | contribs) (→‎Smart Services description) ← Older edit		Latest revision as of 10:18, 6 July 2021 (view source) Sfr (talk | contribs)
(One intermediate revision by the same user not shown)
Line 55:		Line 55:
	----		----
	=== Results ===		=== Results ===
		+
		+	==== Locations ====
		+	We are looking for a link
		+	between the existing railway infrastructure
		+	Databases, CRD and RINF, and the GEO model of
		+	OpenStreetmap (openstreetmap.org)
		+
		+	We have two possibilities to link them:
		+	* CRD and RINF locations carry the OSM key
		+	* OpenStreetmap has two railway tags (e.g. CRD-ID and RINF-ID)
		+
		+	==== Architecture for MVP MARS and PoC Platform ====
		+	The two topics of the next step are
		+	* MVP MARS and
		+	* PoC Platform
		+	The architecture for this step needs to address the aspects of boths tasks.
		+	The MVP MARS implement the MARS services for
		+	* TrainComposition and
		+	* WagonControl
		+
		+	The PoC with the potential platform partner focus on
		+	* Start to use future platform
		+	* Learn about the platform services in
		+	** Facility services
		+	** Mobile access services
		+	** Accounting and license management
		+
		+	Therefore the architecture needs to cover
		+	* Facility Services
		+	* Mobile Access Services
		+	* Accounting Services
		+	* Railway Business Services
		+
		+	* BackEnd Serices
		+	* FrontEnd Services
		+	* Access Layer
		+	* Encapsulation
	==== Smart Services description ====		==== Smart Services description ====

---

Latest revision as of 10:18, 6 July 2021

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

Iteration 8

The eight iteration lasts from 17.June to 8.July.

Topics

Capabilities

C01: Managed CRD Location Masterdata

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

User Validation

The User validation stream consists of three different topics:

1. RFF member validation
2. Discovery sessions
3. Ecosystem alignment

RFF member validation

In the RFF member validation each member can lay out

• his preferences for realization of the RFF topics and
• his contribution in this selection

With this voting the Peer groups and sponsors are identified to support the chosen services to build up.

DISCO: Discovery Session

We will in this iteration

• to conduct the first Gap Discovery session (in German) and
• to support and follow up with the contact persons of the RFF partners.

Ecosystem alignment

In the next step we will tackled the integration of the RFF DP ecosystem in the existing context.

SM: SmartService Profile Review

The last descriptions of the 26 SamrtServices are completed and can be reviewed. With these profiles we can then start the discussion with the CIO/steering committee on prioritization and validation.

---

Reviews

Reporting Tool

• Reporting Tool

Smart Service profiles

• SM_08 Siding Everywhere
• SM_17 Facilities on location
• SM_24 Authority Communication

---

Results

Locations

We are looking for a link between the existing railway infrastructure Databases, CRD and RINF, and the GEO model of OpenStreetmap (openstreetmap.org)

We have two possibilities to link them:

• CRD and RINF locations carry the OSM key
• OpenStreetmap has two railway tags (e.g. CRD-ID and RINF-ID)

Architecture for MVP MARS and PoC Platform

The two topics of the next step are

• MVP MARS and
• PoC Platform

The architecture for this step needs to address the aspects of boths tasks. The MVP MARS implement the MARS services for

• TrainComposition and
• WagonControl

The PoC with the potential platform partner focus on

• Start to use future platform
• Learn about the platform services in
  • Facility services
  • Mobile access services
  • Accounting and license management

Therefore the architecture needs to cover

• Facility Services
• Mobile Access Services
• Accounting Services
• Railway Business Services

• BackEnd Serices
• FrontEnd Services
• Access Layer
• Encapsulation

Smart Services description

• SM_06 End-To-End Transport Planning
• SM_07 Capacity Optimization
• SM_09 Low Entry Barrier for Transport Offerings
• SM_11 Automated Shunting
• SM_12 Intermodal Alignment
• SM_15 Intermodal Connectivity Package
• SM_25 Port Terminal Communication

User validation

lead by Tibo Noël Summarizes two important tasks

1. RFF member validation and cooperation
2. A&B type Discovery sessions

RFF Member validation and cooperation

Tibo plans with each partner a workshop to validate its interests and cooperation abilities

A&B type Discovery sessions

Goal: Identify needs of non-RFF members, non platform users (focus in first step on A&B type RU’s) Topics: Learn about the needs of “Small RU’s” and sketch possible services to cover them First session (in German language) held Tuesday 6.July with

• SBB Cargo International (RU)
• BLS Cargo (RU)
• WLE (RU)
• CN Consult (Railway IT supplier)