| sidebar_position | title |
|---|---|
1 |
L4 - Operational service |
import * as Responsibilities from './Responsibilities.js';
At the start of the operational service phase, the lab has been tested by multiple users and the documentation has matured.
In this phase the virtual lab has been industrialized and is provisioned on the research infrastructure.
The following should be done during operational service:
- Expand and adapt the virtual lab where useful.
- Keep up to date with new versions of dependencies.
- Make the containerized cells and workflow interoperable with other systems where use cases for the interoperability between NaaVRE and another system arise.
The following milestones can occur when a virtual lab runs as an operational service:
- Silver and ivory users successfully run their own scenarios in the virtual lab.
- Silver and ivory users make their own modifications to the virtual lab to facilitate their research.
- Users come up with ideas that spawn the creation of a new virtual lab: Whenever users of the virtual lab come up with a new idea that does not fit in the possibilities of existing virtual labs, they can contact the community supporter or virtual lab coordinator to discuss the possibilities of creating a new virtual lab.
The following responsibilities should be assigned when the virtual lab is an operational service:
- Scientific steering board: <Responsibilities.L4SteeringBoard/>
- User supporter: <Responsibilities.L4UserSupporter/>
- Community supporter: <Responsibilities.L4CommunitySupporter/>
- Core developer: <Responsibilities.L4CoreDeveloper/>
- Virtual lab coordinator: <Responsibilities.L4Coordinator/>
- Infrastructure supporter: <Responsibilities.L4InfrastructureSupporter/>