NOVA™ — M&S Designer

🏛️

JSP 939 V3.1 (January 2025) — Defence Policy for Modelling & Simulation governs all M&S used in UK MOD training and experimentation. Every M&S system starts as non-compliant; compliance must be earned against the eight Coherence Principles and declared by the relevant SCTA. NOVA generates the doctrinal evidence base for SCTA review. This tool applies to both Individual Training (DSAT Elements 1–3) and Collective Training (CT Cycle). All simulation standards must comply with the Defence M&S Standards Profile (DMSP V13, Def Stan 03-050). For Gladiator (Air), Spartan (Maritime), and CTTP (Land) enterprise architectures, domain SCTA engagement is mandatory at Coherence Principle 5.

Step 1

M&S Requirement

Define need & type

Step 2

JSP 939 Compliance

Eight coherence principles

Step 3

Standards & Design

DMSP · HLA · Fidelity

Step 4

Output Generation

FSR · TSS · CTAR · LSB

Step 5

SCTA Governance

DSC · Gladiator · Spartan

Step 1 — M&S Requirement Definition

JSP 939 CP1 & CP2

📋

Training M&S Requirement

DSAT-Governed

Programme / Exercise Title *

Training Type *

Domain Architecture * JSP 939 CP5 — MUST align

CP5: New capability must align with existing domain architecture. SCTA must be engaged at programme concept stage, not after requirements are fixed.

Training Category (Fidelity) * JSP 822 Table 8 — DIF-derived

Training Category is derived from DIF Analysis (27-permutation algorithm, JSP 822 Table 8). Higher TC = higher fidelity requirement. Instructional features are more important than fidelity per se — do not gold-plate.

Exercise Type (CT only)

🔍

DSC Catalogue Check

CP1 — MUST

JSP 939 CP1 MUST: Before procuring or building any M&S capability, check whether something already exists in the DSC Catalogue. Contact: UKStratCom-DSCEnquiries@mod.gov.uk

DSC Catalogue Check Status *

Record the DSC Catalogue check outcome here. This constitutes CP1 evidence for the CTAR submission.

DSC Reference / Existing Asset Details

New Asset for DSC Catalogue? CP2 — Procure for Reuse

CP2: Any new M&S asset must be made available to the rest of Defence in open, interoperable formats via the DSC Catalogue.

⚖️ Live-Synthetic Blend (LSB) — QinetiQ Framework

JSP 939 Section 7 / JSP 822 Vol 2 Ch 3. Six factors determine the right LSB:

Availability Platform available? Trainees co-located?
Legal Noise regs, working time, certification constraints
Environmental Carbon footprint, ecological secondary costs
Safety Unacceptable risk of injury in live training?
Security Classified tactics or sensor data at risk?
Cost-Effectiveness Through-life simulator vs live costs

NOVA generates the LSB Decision Record in Step 4.

Step 2 — JSP 939 Coherence Principles Assessment

JSP 939 V3.1 CP1–8

⚠️ Every M&S system starts as non-compliant

Compliance is not assumed. It must be earned and formally declared by the relevant SCTA and endorsed by the DMSO TA Head. Work through each of the eight Coherence Principles below. NOVA's evidence will be assembled into CTAR format in Step 4.

MUST

CP 1

Reuse Existing

Check DSC Catalogue before building or buying. Recorded in Step 1.

MUST

CP 2

Procure for Reuse

New assets go into DSC Catalogue in open, interoperable formats.

MUST

CP 3

M&S Standards

All standards must comply with DMSP (Def Stan 03-050 V13). Assessed in Step 3.

MUST

CP 4

Enumerations

All entities must have SISO enumeration registered with DSC. Captured in TSS (Step 4).

MUST

CP 5

Enterprise Architecture

Align to Gladiator / CTTP / Spartan. SCTA engagement mandatory. Selected in Step 1.

MUST

CP 6

Technical Documentation

ICDs, 3D model metadata, Interface Control Documents. Captured in TSS (Step 4).

MUST

CP 7

SE Data

Terrain, 3D models, geospatial data from DSC. JSP 465 SDMP if DSC unavailable.

SHOULD

CP 8

Research Exploitation

Detailed Evidence — CP3, CP4, CP6, CP7

CTAR Evidence

📐

CP3 — M&S Standards Proposed

Primary Federation Architecture *

HLA is mandated for any exercise connecting multiple simulation systems. DIS requires justification. DMSP V13.

Additional Standards Required

NETN FAFD
NATO AMSP-04

UCATT
SISO-STD-016

DDCA
SISO-STD-015

C2Sim
SISO-STD-019

OpenXR
V1.0 — XR/VR

GM-VV
SISO-GUIDE-001

🗺️

CP7 — Synthetic Environment (SE) Data

SE Data Sourcing * JSP 465 applies if DSC unavailable

SE Data Requirements

CP7: All terrain, 3D model, and geospatial data must come through the DSC. Document any data sourced outside DSC and the SDMP reference.

📝

CP4 & CP6 — Enumeration Requirements & Technical Documentation

New Entity Types Requiring SISO Enumerations SISO-REF-010-2025

CP4: Every entity in a distributed simulation must have an official SISO enumeration registered with the DSC. New types must be submitted to DSC before federation testing.

Technical Documentation Plan CP6 — ICDs & metadata

CP6: Full technical documentation must be available so others can understand and connect to the system. ICDs are mandatory for any HLA/DIS federate.

Step 3 — M&S Standards & Training Design

DMSP V13 · JSP 939 Section 7

📊

DMSP V13 Standards Reference — Def Stan 03-050

Oct 2025

Standard	Status	Category	Use Case for This Programme
HLA (IEEE 1516)	MANDATED	Interoperability	Primary federation architecture for any distributed simulation. Mandatory unless DIS is specifically justified.
NETN FAFD (AMSP-04)	MANDATED	FOM	NATO exercises connecting allied simulators. Required for Gladiator interoperability with allies.
UCATT (SISO-STD-016)	MANDATED	Live Simulation	Live simulation systems in multinational training. Critical for live/synthetic exercises (UCATT enables live entity interop).
DIS (IEEE 1278.1)	CURRENT	Interoperability	Legacy / simple platform-level simulation. Use only where HLA is disproportionate.
DDCA (SISO-STD-015)	MANDATED	Debrief	Distributed After Action Review. Mandatory for any distributed exercise. NOVA Post-Exercise Report must reference DDCA.
GM-VV (SISO-GUIDE-001)	CURRENT	V&V	Verification and Validation methodology. Required for all M&S systems. Evidence captured in Evaluation Plan.
C2Sim (SISO-STD-019)	CURRENT	C2 Integration	CT exercises with real C2 systems. Enables simulation to receive orders from live C2. CPX/CAX with C2 integration.
OpenXR (V1.0)	CURRENT	XR	VR/AR training applications. Required for any XR-based training identified in the TOA.
Enumerations (SISO-REF-010)	MANDATED	Enumerations	All distributed simulation entities. New types must be registered with DSC before testing.

🎚️

Fidelity Design — Individual Training

Fidelity Rationale * Derived from DIF Analysis / TOA

Fidelity must be derived from the 27-permutation DIF algorithm (JSP 822 Table 8), not from preference or budget pressure. Do not gold-plate: specify the right fidelity, not the maximum fidelity.

Simulation Type

Instructional Features Planned

Clear learning objectives

Structured practice opportunities

Immediate feedback

Progress assessment

Varied scenarios

Stress induction

🎯

Threat Model — JSP 939 Section 11

Defence Intelligence (DI) is the sole authoritative source for threat models above Official Sensitive. Engage DI at the earliest opportunity — fidelity of threat determines fidelity of training.

Level	Definition	Use Case
Parametric	System-specific data into generic algorithms. Lowest fidelity.	Strategic/Theatre exercises.
Analytic	Sub-system behaviours modelled by system-specific algorithms.	Mission/Battle level. Required for Audacious Training.
Emulative	Model reflects actual system design. Highest fidelity.	Engagement/Component. Aircrew threat evasion (Gladiator).

Threat Fidelity Required

DI Engagement Status

🪖

Collective Training M&S Design

CT Phase

Exercise Lifecycle Stage

DExp Compatibility Check JSP 939 Section 9

JSP 939 S9: DExp and CT are incompatible when Treatment, Threat, or Scenario differs from current force capability. NOVA CT Scoping Study flags this automatically.

Performance Capture System

MIMIR
PI mapping

EXONAUT
Event recording

DDCA
Distributed debrief

O/C Manual
Observer collection

NATO CT&E Compliance Required Bi-SCD 075-003

Step 4 — M&S Output Generation

DSAT Elements 1–4

📄

Fidelity Statement Requirement (FSR)

Procurement-ready fidelity specification derived from DIF Analysis (TC 1–6). Maps training tasks to required simulation fidelity standard. References DMSP-compliant simulation standard for each task. Not a wish-list — doctrinal standard, not maximum fidelity.

JSP 822 Table 8 · DIF-derived

Build progressReady

📐

Training System Specification (TSS)

Defines what fidelity standard a simulator must meet. Lists applicable DMSP standards (HLA, NETN, UCATT, DDCA), enumeration requirements table, ICD outline, and CP3–CP6 evidence. Structured for SCTA review submission.

CP3 · CP4 · CP6 · DMSP

Build progressReady

⚖️

LSB Decision Record

Live-Synthetic Blend decision record capturing all six QinetiQ framework factors (Availability, Legal, Environmental, Safety, Security, Cost-effectiveness). Structured evidence for JSP 939 Section 7 compliance. Both Individual and Collective Training modes.

JSP 939 S7 · QinetiQ LSB

Build progressReady

🏛️

CTAR Evidence Pack

Capability Technical Assessment Report evidence pack. Assembles NOVA outputs into the evidence categories that a DMSO SCTA review requires. Cover sheet maps each NOVA document to the relevant Coherence Principle. Ready for RAF SCTA / Army SCTA / Navy SCTA submission.

CTAR · DMSO · SCTA

Build progressReady

🪖

CT Exercise M&S Pack

Collective Training supplementary pack: EXSPEC M&S annex, EXPLAN federation architecture diagram, O/C MIMIR PI checklist, AAR debrief pack with DDCA reference, SISO enumeration requirements table. CT Tier classification documented.

CT · EXSPEC · MIMIR · DDCA

Build progressReady

🌐

NATO CT&E Compliance Check

NATO CT&E Compliance Check document mapped to Bi-SCD 075-003. Verifies CTOs against NATO CT&E framework, confirms NETN FAFD compliance, cross-references MIMIR PIs against NATO metrics, and produces TQCC-V validation declaration. Dual UK/NATO doctrinal citations.

NATO · Bi-SCD 075-003 · NETN

Build progressReady

Step 5 — SCTA Governance & DSC Registration

JSP 939 V3.1 Part 2 Section 3

🖥️ Individual Training — SCTA Engagement

CP5 MANDATED

SCTA must be engaged at programme concept stage, not after requirements are fixed. Domain SCTAs are the technical authority for JSP 939 compliance within their domain.

Domain SCTA identifiedRAF SCTA (Air & Space Warfare Centre) / Army SCTA / Navy SCTA — confirm point of contact.

SCTA engagement initiatedProgramme brief and NOVA output pack shared with SCTA for initial assessment.

CTAR submittedCTAR Evidence Pack (Step 4) submitted to SCTA for formal review.

Domain architecture alignment confirmedCP5: Gladiator / CTTP / Spartan alignment documented and SCTA-endorsed.

SCTA compliance declaration receivedFormal compliance declaration from SCTA and DMSO TA Head endorsement.

🪖 Collective Training — SCTA & NATO CT&E

CT CYCLE

For CT exercises, both domain SCTA and NATO CT&E governance applies. NETN FAFD compliance requires ACT engagement for allied exercises.

CT Scoping Study M&S annex completeDSC Catalogue checked at scoping stage. DMSO engaged.

EXSPEC HLA/DIS federation design approvedFederation architecture diagram signed off by SCTA before EXPLAN.

SISO enumerations registeredNew entity types submitted to DSC. Reference numbers obtained before federation testing.

NATO NETN FAFD compliance confirmedAllied exercise: NETN FAFD compliance statement prepared. ACT notified.

TQCC-V validation declaration completePost-exercise: TQCC-V validation declaration generated from NOVA CT Assurance phase.

DSC Registration & CP8 Compliance

CP8 — Research Exploitation

📋 DSC Registration — NOVA as M&S Decision-Support Tool

CP8: Any M&S research or decision-support activity must be registered with the DSC so it can be found and reused, preventing duplication. NOVA itself constitutes a registered M&S research and decision-support activity. Registration contact: UKStratCom-DSCEnquiries@mod.gov.uk. Include NOVA programme reference, output document catalogue, and DSAT doctrinal basis in the registration submission.

🚀

M&S Programme Summary

JSP 939 V3.1 Compliant

JSP 939 CP1–8 Evidence75%

DMSP Standards Coverage100%

SCTA Engagement40%

DSC Registration20%

Policy References:
JSP 939 V3.1 Jan 2025 — Defence Policy for M&S
DMSP V13 Oct 2025 — Def Stan 03-050
JSP 822 V8.0 / DTSM 1–8 V2.0 — DSAT
JSP 465 — Geospatial Data (SE Data / SDMP)
SISO-REF-010-2025 — Enumerations V35
Bi-SCD 075-003 — NATO CT&E Exercise Directive
AMSP-04 (NETN FAFD) — NATO FOM Standard
IEEE 1516 (HLA) / IEEE 1278.1 (DIS)