Difference between revisions of "Facility Services"
From RFF Wiki
| (One intermediate revision by the same user not shown) | |||
| Line 36: | Line 36: | ||
== Identity Management == | == Identity Management == | ||
| − | [[File:Framework_identity.png|border]] | + | [[File:Framework_identity.png|border|upright=2]] |
The Identity Service provides information about rights and duties of human and system users. | The Identity Service provides information about rights and duties of human and system users. | ||
| Line 51: | Line 51: | ||
== License Service == | == License Service == | ||
| − | [[File:Framework_license.png|border]] | + | [[File:Framework_license.png|border|upright=2]] |
The License Service manages contracts and licenses | The License Service manages contracts and licenses | ||
| Line 65: | Line 65: | ||
== Channel Management == | == Channel Management == | ||
| − | [[File:Framework_channel.png|border]] | + | [[File:Framework_channel.png|border|upright=2]] |
The Channel Service provides a clear definition of offered active communication protocols | The Channel Service provides a clear definition of offered active communication protocols | ||
| − | It | + | * 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 | |
| − | ** one is the management of the decentralized services offered for each platform system. It creates a stable facade for the customer. | ||
| − | ** 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) | * 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 integration blueprints and basic functional test capabilities | ||
| Line 83: | Line 81: | ||
[[File:Icon_Monitor.png|border]] | [[File:Icon_Monitor.png|border]] | ||
| − | * ensures that offered channels are available and operating | + | 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 | * informs about service fall outs and recovery | ||
| + | * it reports the usage of provides services | ||
== Platform Operation == | == Platform Operation == | ||
| Line 91: | Line 93: | ||
[[File:Icon_Operation.png|border]] | [[File:Icon_Operation.png|border]] | ||
| + | * operation | ||
| + | * routing | ||
* load balancing | * load balancing | ||
| − | * | + | * fail over scenarios |
| + | * service migration | ||
== Marketplace == | == Marketplace == | ||
| Line 106: | Line 111: | ||
[[File:Icon_Hub.png|border]] | [[File:Icon_Hub.png|border]] | ||
| − | Hub services for interconnection with other ecosystems | + | 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 | * RNE for IM | ||
* GCU for WagonKeeper | * GCU for WagonKeeper | ||
| Line 118: | Line 130: | ||
[[File:Icon_Incubator.png|border]] | [[File:Icon_Incubator.png|border]] | ||
| − | + | In the incubation environment new services are focus to | |
* develop | * develop | ||
| − | * shape and | + | * shape |
| + | * harden and | ||
* train | * train | ||
| − | future smart business services | + | 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. | ||
Latest revision as of 17:06, 23 June 2021
Contents
Quality Management
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
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
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
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
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
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
- operation
- routing
- load balancing
- fail over scenarios
- service migration
Marketplace
- Business service catalog
- App Shop
- API Offerings
Hub Connection
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
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.
