...
Service onboarding within EOSC-hub is the process whereby a new service joins the EOSC-hub service catalogue and EOSC Marketplace. This provides services with all the benefits offered by the catalogue and marketplace - promotion of the service to users outside their local community domain a single gateway for users to discover and use services, regardless of their nature and the scientific discipline of the user, and potential integration with other services in the catalogue. The operational requirements for joining the catalogue from the Service Management System (SMS) are defined in deliverable D4.1 Operational requirements for the services in the catalogue, structured around different operational parts of the SMS covering the service delivery. However, the onboarding process itself is not covered in D4.1. This document aims at outlining this basic workflow, for the benefit of prospective service providers and EOSC-hub project staff.
2. Service Catalogues
...
Within EOSC-hub there are two service catalogues:
1) the internal catalogue containing access enabling supporting services developed as part of the project and necessary for the operation of the EOSC-hub (e.g. helpdesk and AAI). These services may not be ordered.
2) the external catalogue containing the common services on which many services depend (data, compute, orchestrators) and research-enabling services offering services to the end user, typically building on the common services.Alongside these two services catalogues, services may attain three levels of service integration. EOSC-hub has effort to assist Service Providers moving from a lower level to a higher level. The levels are:
1) LOW level has the minimum set of SMS requirements. Nevertheless, along with all other services in the external catalogue, services entering at this level benefit from the advantages of the EOSC-hub as listed in the Introduction above. Services which enter the catalogue at this level may either have a less mature SMS which they plan to develop, or a mature SMS but would like to join the EOSC-hub initially without committing additional resources for integration until a later stage.
2) MEDIUM level is aimed at services in the external catalogue that are being delivered as part of an existing and mature SMS complying with the majority of requirements of FitSM or other recognised Service Management Framework. Services achieving a Medium level of integration are encouraged to participate closely with the EOSC-hub by being represented at the Service Management Board meetings.
3) HIGH level is for services in the internal catalogue delivered as part of the EOSC-hub SMS. Services from the external catalogue may also achieve this highest level of integration. Services with a High level of integration are expected to participate closely with the EOSC-hub and expected to be represented at the Service Management Board meetings.
It is anticipated that new services wishing to join the EOSC-hub service catalogue will be joining the External Catalogue at either Low or Medium levels of integration. The onboarding process for each case is similar and is described in the next section below.
...
This catalogue consists of all other services apart from the supporting services developed by EOSC-hub project in addition to externally onboarded services.
3. Onboarding Process
...
3.1 Initial contact with EOSC-hub (Prospective service provider)
...
EOSC-hub staff working with Operations Coordination (EOSC-hub Task 4.1) review the operations validation checklist to evaluate the maturity of the service (i.e. TRL level of at least 8) and the maturity of the SMS of the Service Provider. (This may be done as an online meeting with the service provider, and the checklist may be sent in advance to aid preparation for the meeting). The initial level of integration is agreed with the Service Provider.
3.4 EOSC-hub SMS Process Integration
...