...
Within EOSC-hub there are two service catalogues portfolios:
1) the internal catalogueHUB Portfolio containing supporting services developed as part of the project and enabling services necessary for the operation of the EOSC-hub (e.g. helpdesk and AAI) and for integration with external services. These services may not be directly ordered by end users.
2) the external catalogueEOSC Service Portfolio containing the common services on which many services depend (data, compute, orchestrators) and in addition to research-enabling services offering services to the end user, typically building on the common services. This catalogue consists of all other services apart from the supporting services developed by EOSC-hub project in addition to externally onboarded servicesThese services may be integrated with the enabling services within the HUB Portfolio. External services may be added (or onboarded) to this portfolio by following the process described below.
3. Onboarding Process for new services joining the EOSC Service Portfolio
3.1 Initial contact with EOSC-hub (Prospective service provider)
The prospective Service Provider completes the Join as a provider form on the EOSC-hub website, providing high-level information about the service and motivation for joining. The submitted information becomes a ticket in Jira to track an internal ticket which is used for tracking the request.
3.2 Initial evaluation of request
EOSC-hub staff working with Service Portfolio Management (EOSC-hub Task 2.2) evaluate the request, contacting the submitter for supplementary information to initially gauge the high-level validity of the request and to confirm that the service is appropriate for inclusion into the service catalogueportfolio. If so, the prospective service provider fills in the Service Portfolio Entry Template (at least all mandatory fields) and Service Options are discussed.
...
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 Providerincluding the TRL level which ideally should be level 8) as well as other essential information relating to the delivery of the service. (This may be done by email or as an online meeting with the service provider, and the checklist may be sent in advance to aid preparation for the meeting).
3.4 EOSC-hub SMS Process Integration
At this point where all requirements are fulfilled at the agreed level of integration, the following steps are required. In all cases, the step is tracked in Jira.
3.4.1 Adding the new service to the
...
portfolio
Information required by SPM about the service is added to the catalogueportfolio
3.4.2 Preparation for SLA creation
...
If appropriate, an SLA template is populated for the new service in readiness for SLAs with end users, and the service contact is made familiar with its format
3.4.3 Security
...
The nominated contact from the Service Provider (or another nominated security contact) is added to the appropriate database (e.g. GOCDB) for security-related issues.
3.4.4 Support
...
An appropriate contact for providing support is added to the EOSC-hub catalogueportfolio. In the case of services who have requested the Helpdesk service bundle, a new support unit is created in XGUS and associated with the appropriate contact for providing support.
3.4.5 Marketplace integration
...
The prospective Service Provider completes the Service Description Template providing information relevant to the Marketplace. Other existing services on the marketplace are introduced that may be relevant and of interest for potential future integration.
3.4.5 Operational integration
...
A nominated contact from the Service Provider is invited to engage with the Service Provider Forum by joining its mailing list and attending quarterly meetings. The Service Provider Forum is designed to facilitate communication between Service Providers and the EOSC-hub project, in addition to requirements gathering.For the highest level of partnership, the nominated contact from the Service Provider is additionally invited to attend Service Management Board meetings.