Facility Services

From RFF Wiki
Revision as of 17:06, 23 June 2021 by Sfr (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Quality Management

Framework quality.png

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 Provisioning

Framework content.png

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 Management

Framework identity.png

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

Framework license.png

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 Management

Framework channel.png

The Channel Service provides a clear definition of offered active communication protocols

  • It offers two separated service types
    • Decentralized Agent: one is the management of the decentralized services offered for each platform system. It creates a stable facade for the customer.
    • Centralized Note: the other is the central component that defines and enforces the defined formats and their services
  • in general it provides a channel management (who is providing what in which format with which technology)
  • provides integration blueprints and basic functional test capabilities
  • provides specifications for format conversions
  • passes on the information to the monitoring facility as basis.

Platform Monitoring

Icon Monitor.png

To ensure a decent platform operation and steering a dedicated monitoring service is needed.

  • It ensures that offered channels are available and operating
  • reports the load on the channels
  • any misuse or attacks.
  • It regularly checks the availability of end-to-end communication chains
  • informs about service fall outs and recovery
  • it reports the usage of provides services

Platform Operation

Icon Operation.png

  • operation
  • routing
  • load balancing
  • fail over scenarios
  • service migration

Marketplace

Icon Marketplace.png

  • Business service catalog
  • App Shop
  • API Offerings

Hub Connection

Icon Hub.png

Hub services for interconnection with other ecosystems provide a bridge mechanism to

  • translate
  • transform
  • convert and
  • provide information

of the two connected ecosystem.

Such hubs include bridges to:

  • RNE for IM
  • GCU for WagonKeeper
  • VDV for "Small" national RUs
  • **tbd** for Authorities
  • **tbd** for IntermodalOperator
  • **tbd** for Shunter

Service Incubator

Icon Incubator.png

In the incubation environment new services are focus to

  • develop
  • shape
  • harden and
  • train

These future smart business services are prepared for the productive usage on the platform. For that purpose the incubator provides the necessary

  • sources
  • data streams and
  • loads

to emulate the productive environment.