Documentations of Service Portfolio Reviews¶
| Review No. | Review Category | Review Type | Starting in | Completed in | Summary of Results | Documentation |
|---|---|---|---|---|---|---|
| 1 | Regular Review | Services in Portfolio Service selection criteria Portfolio processes |
01/2022 | 03/2022 | - Remove 7 services from Service Portfolio since they were withdrawn by the Service Provider - Adapt service type wording for former “HIFIS Basis Services” to “Helmholtz Cloud core services” - Adapt criteria descriptions/requirements - Adapt field descriptions in Application form as a result of collected experiences during review - Adapt Service Canvas as a result of collected experiences and for better structure |
Link to Documentation |
| 2 | Regular Review | Services in Portfolio Service selection criteria Portfolio processes |
11/2022 | 02/2023 | - Remove 3 services from Service Portfolio since they were withdrawn by the Service Provider - Update Service Information as indicated by Service Owners - Adapt Service Selection criteria: Ease requirements regarding degree of automation in user provisioning and deprovisioning – rather ask for commitments - Adapt Service Portfolio processes: Service Onboarding Process, Service Recruiting (former Request for Service) Process, Service Integration Process, Simplify rights matrix for Operation of Services, Add Service type for “guest services” (tbd) - Adapt fields in Plony (modification of explanation texts and field names, deactivation of unnecessary fields, addition of new fields) |
Link to Documentation |
| 3 | Regular Review | Services in Portfolio Service selection criteria Portfolio processes |
09/2023 | 12/2023 | - Update Service Information as indicated by Service Providers - For Services in Service Pipeline: - Ask service provider for integration timeline and suggest to withdraw and later reactivate service if integration can’t be completed in a reasonable time - For nubes (HZB) & LimeSurvey (HMGU): - Services are not available since Cyber attacks. Regularly get in touch with service provider to plan service comeback Adapt fields in Plony (Increase usability by restructuring Responsibilities, indenting field input in all forms, organizing “My Services” overview in tabs) Service Selection criteria + Service Portfolio Processes do not require adaptation |
Link to Documentation |
| 4 | Regular Review | Services in Portfolio Service selection criteria Portfolio processes |
10/2024 | 03/2025 | - Update Service Information as indicated by Service Providers - Points regarding specific services: - REMS (DKFZ) & Container Runtime (FZJ) will be offboarded as requested by Service Provider - B2Share (FZJ) becomes a pilot service since no connection to Helmholtz AAI is yet established - Helmholtz KG & unHIDE (FZJ) becomes a Fully integrated service - HAICORE services (FZJ) need to be discussed due to no connection to Helmholtz AAI and lacking characteristic of Cloud services - OpenStack (FZJ) switches resources from HDF Cloud to JSC-Cloud, thus resulting in a bunch of service information changes. Service Card Review will be repeated. - WebODV (AWI) is back online after a longer period of not being available due to restructuring/update - Adapt Process Framework (condense Exclusion criteria regarding legal aspects, simplify criterion regarding connection to Helmholtz AAI, drop Weighting & Information criteria since they are not used) - Adapt fields in Plony (restructure Application form & Service Canvas, reduce number of fields) |
Link to Documentation |