L4 - Operational service

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 workflow components and workflows 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: Coordinates the further development of the virtual lab with a scientific vision.
User supporter: Is the primary point of contact in case any problems arise with the virtual lab.
Community supporter: Identifies any potential new golden users from the community using the virtual lab.
Virtual lab developer: Development of the main virtual lab is kept in the hands of virtual lab developers or taken over by the user community.
Virtual lab coordinator: Ensures the VRE keeps supporting the virtual lab.
Infrastructure supporter: Monitors, provides, and adjusts infrastructure for the virtual lab.