Process
The Niteworks delivery framework identifies activity, deliverables and milestones, and is governed by Gates, which are formal points in the process that afford decision-makers the opportunity to decide whether development of a Theme has matured enough to enable it to move to the next phase of the process. Each Gate meeting is attended by both MOD and Industry.
Problem
A Niteworks Theme begins with a MOD-proposed problem selected by the Niteworks Programme Board. The Programme Board has representation from Niteworks management and MOD.
Once a problem is selected it is held on Gate 0 until resource is available to prosecute the problem. The problem is transformed to a “bounded question” for Gate 1, which requires wide stakeholder engagement and context gathering across MOD and industry.
Solution
Once sufficient work has been conducted to identify potential solutions to answer the question and it is concluded that an experiment is applicable, an internal review takes place mid-way between Gate 1 and 2, where the solution is ratified.
Design
The experiment is designed and costed for Gate 2, identifying the experimental components, such as players, environment and measures. At Gate 2 the experiment is approved in terms of technical and financial quality.
Experiment
The experiment is conducted post Gate 2 at the selected facility.
Report
Two reports are created post experiment, one for the customer community detailing the benefits of the Theme to MOD, and another for the scrutiny and scientific community supporting the benefits described in the customer report.
Exploitation
The agreed benefits for the Theme are formally handed over to MOD from Niteworks for exploitation.
