🎓
TEL & SCORM Designer
JSP 822 V7.0 Vol 6 · Technology Enhanced Learning · Individual & Collective
JSP 822 V7 Vol 6 SCORM 1.2 / xAPI DLE · TAFMIS · STANAG 2591
📋

JSP 822 V7.0 Vol 6 — Technology Enhanced Learning Policy is fully integrated into this designer. All TEL content developed here must comply with the 12-Principle TEL Ruleset (Ch.5), be governed under DSAT (Ch.3.3), and follow DLE naming conventions (Ch.3.9). SCORM 1.2 packages are mandated for NATO sharing under STANAG 2591. TAFMIS must be used for all Phase 1/2/3 training management. DLE must be used for all VLE-hosted content. This tool applies to both Individual Training (DSAT Element 2/3) and Collective Training (CT Phase).

Step 1
TEL Requirement
Define needs & type
Step 2
Standards Check
TEL Ruleset compliance
Step 3
Content Design
Structure & objectives
Step 4
Package Generation
SCORM · Classroom · DLE
Step 5
LMS Registration
DLE · TAFMIS · NATO

Step 1 — TEL Requirement Definition

JSP 822 V7 Ch.2 Rule 1
📝

Learning Requirement

DSAT-Governed
DLE requires long and short name. Format: [Code] [Title] [Service] — JSP 822 V7 Vol 6 §3.9
JSP 794 naming conventions apply. JPA holds master competence list.
⚙️

TEL System Selection

MANDATED
DLE MUST be used for all learning requiring a VLE. TAFMIS MUST be used for P1/2/3. JSP 822 V7 Vol 6 §2.2
Rule 6: All systems and data must be within GCS policy. JSP 440 applies.
🔗 NATO Content Sharing
Where content is to be made available to NATO Allies, a SCORM version must be created to enable sharing under STANAG 2591. This applies to both Individual and Collective Training outputs. The UK MOD ADL WG co-ordinates NATO TEL interoperability. All NATO-shared packages must comply with IEEE P1484 open standards.

Step 2 — TEL Ruleset Compliance (12 Principles)

JSP 822 V7 Ch.5 — MUST

All 12 principles of the TEL Ruleset must be addressed in any TEL business case or development. Each principle requires articulation on either how it will be met, or the limitations that prevent it. The Ruleset does NOT apply to Simulation — see JSP 939 for M&S.

Rule 1
Define User Needs
Applied
TEL development follows a flexible method with regular stakeholder review. Separate from DSAT learning content development. User needs analysis documented in TNA/CTNA.
Rule 2
Make Things Accessible
Must
New TEL must be accessible for users and training designers. Consider Specific Learning Differences, disabilities, and digital literacy. WCAG 2.1 AA minimum.
Rule 3
Be Open / Use Open Source
Should
If reuse of extant TEL is not possible, analysis of available licence-free TEL must be evident. Open Source and Freeware options considered first.
Rule 4
Use Open Standards
Must
Defence TEL must use open standards to ensure interoperability. IEEE P1484 series, SCORM 1.2, xAPI (P9274), LTI. Systems integrating with TAFMIS must comply.
Rule 5
Use Cloud First
Should
Under JSP 440 and GDPR, public cloud considered first. DLE and TAFMIS are cloud-hosted. New bespoke TEL should justify non-cloud deployment.
Rule 6
Make Things Secure
Must
Systems and data within GCS policy and Defence Security requirements (JSP 440). Local ITSO and SCIDA POCs must assist with TEL security analysis.
Rule 7
Make Privacy Integral
Must
GDPR adherence integral. Privacy Impact Assessments recommended as part of TEL procurement. Learner data minimisation applied.
Rule 8
Share and Reuse Technology
Must
Existing TEL to be used where previously procured. DLE, VLE instances, enterprise authoring tool licences. DTEL Taxonomy tagging required for content reuse.
Rule 9
Integrate and Adapt
Should
New TEL interoperable with existing technologies and infrastructure. Good integration enables legacy compatibility without limiting future adaptation.
Rule 10
Make Better Use of Data
Should
Minimise data collection. Reuse data to avoid duplication. TAFMIS Business Intelligence and EMIS for management information. One version of training truth.
Rule 11
Define Purchasing Strategy
Must
Business Case required with approved in-year funding and future sustainment. Existing enabling agreements for approved suppliers. No lock-in to single supplier.
Rule 12
Meet Digital Service Standard
Should
GDS Digital Service Standard if creating a service. Agile procurement methods. Intellectual property rights retained by MOD where applicable.

DSAT Application to TEL Content

JSP 822 V7 Vol 6 §3.3 — MUST
DSAT Governance — Must All learning instances and content hosted on / delivered via the DLE must be governed and managed as part of an MTS in accordance with DSAT Direction & Guidance in JSP 822.
DLE Quality Rubric — Should Quality Rubric used as part of the DSAT 1st and 2nd party audit process for any course using online learning. Red scores form part of non-compliance task list.
TAFMIS TAD Integration — Must (P1/2/3) TAD supports the DSAT analysis & design process. CDCs not using TAD must liaise with TRAs to prioritise migration. TAD auto-populates fields throughout course folders.
InVal and ExVal — Must TAFMIS Course Validation module supports InVal and ExVal. ExVal determines impact on performance after training. Findings used during TNA in review of RolePS/OPS.
Collective Training — Additional CT learning content on DLE must use DLE code CT. CTNA products (FEPS, CTOs) inform CT content design. MIMIR PI integration required for CT assessment.

Step 3 — Content Design & Learning Architecture

DSAT Element 2 — Design
🏗️

Learning Architecture

Objectives must align to KSA/B from the Training Needs Analysis or CTNA FEPS. Each objective must be measurable.
SCORM cmi.score.min and cmi.score.max will be set accordingly. Recommend 80% for mandatory competence.
📦

SCORM Package Structure

SCORM 1.2
SCORM 1.2 is the DLE and NATO ADL standard. Use for all NATO-shareable content per STANAG 2591.
Each SCO is tracked independently in the LMS. Define one SCO per learning objective cluster.
DLE content must be tagged using DTEL Taxonomy stored in Alfresco to enable reuse across Defence. §3.8
Adapt Framework is open source (Rule 3) and natively generates SCORM 1.2. NOVA uses Adapt for all SCORM output.
🎖️ Collective Training TEL Requirements
For Collective Training content, NOVA generates additional CT-specific packages:

CT Phase  Exercise design documents, EXSPEC/EXPLAN
CT Phase  Observer/Controller packs with MIMIR PI checklist
CT Phase  After-Action Review slide decks with event replay guide
CT Phase  SCORM-packaged CT briefing modules for DLE

CT content must use DLE code CT in the DLE naming convention.

Step 4 — Package Generation

DSAT Element 3 — Delivery
📦
SCORM 1.2 Package
Full SCORM 1.2-compliant ZIP for DLE upload. Includes imsmanifest.xml, IEEE LOM metadata, DTEL Taxonomy tags, cmi.score tracking, and mastery threshold. NATO-shareable under STANAG 2591.
SCORM 1.2 · DLE · NATO
Build progressReady
📖
Classroom Package
Instructor delivery pack: lesson plans, PowerPoint slides, handouts, assessment papers, facilitator guide. Aligned to Training Objectives and DSAT standards. A4 portrait, MOD house style.
Instructor Pack · PDF · PPTX
Build progressReady
🎯
AI-Amplified KLP Modules
NOVA AI generates 200–300 words per Key Learning Point, role-specific and not generic boilerplate. Integrated into SCORM SCOs. Phase 5c pipeline: Adapt JSON → GitHub Actions → SCORM 1.2 build.
AI · SCORM · Adapt
AI generationReady
🌐
xAPI Package
Experience API (IEEE P9274) package for advanced learner analytics. Compatible with Learning Locker (DLE component). Tracks detailed learner interactions beyond SCORM completion/score.
xAPI · Learning Locker · P9274
Build progressReady
🪖
CT Exercise Package
Collective Training supplementary pack: EXSPEC, EXPLAN, O/C guide, MIMIR PI observation checklist, AAR slide deck. For CT DLE-hosted briefing content and observer/controller use.
CT · EXSPEC · MIMIR
Build progressReady
🏛️
NATO STANAG 2591 Package
NATO-ready SCORM package for sharing with Allied nations via the ADL Programme. Includes NATO metadata schema, STANAG 2591 compliance declaration, and UK ADL WG registration.
STANAG 2591 · NATO ADL
Build progressReady

Step 5 — LMS Registration & Governance

JSP 822 V7 Vol 6 §3–4

🖥️ Defence Learning Environment (DLE)

MANDATED VLE

The DLE MUST be used for all learning requiring a VLE. All courses must be designed by a DLE-authorised Course Designer who has completed DLERFT training.

DLE Course Designer authorisedDLERFT Role Functionality Training completed by designer.
Category Manager approvalSub-Category Manager must grant course-level permissions.
DLE Quality Rubric completedMust be stored in additional Topic within course. Red scores actioned.
DTEL Taxonomy tags appliedContent tagged in Alfresco for cross-Defence reuse.
DLE naming convention appliedLong name and short name per JSP 822 V7 Vol 6 §3.9.

📊 TAFMIS

MANDATED P1/2/3

TAFMIS MUST be used for all Phase 1/2/3 training management. All other organisations use JPA OLM for course bookings and competence recording.

TAFMIS Manager appointedSingle POC for training site. ToRs followed for TAFMIS Manager role.
TAD course folder createdTraining Analysis Developer populated. TNA data migrated.
Course Assessment module configuredQuestion banks, exams, questionnaires built. Scanning enabled.
InVal / ExVal configuredCourse Validation module set up. TRA ExVal access confirmed.
JSP 794 naming conventions appliedJPA master competence list cross-referenced. JPA number populated.

CEB Governance & TEL Assurance

JSP 822 V7 Vol 6 §2.6
Customer Executive Board (CEB) TEL Review
As a key enabler (methods and media) to learning design and delivery, the use of TEL is to be considered by CEB training governance and assurance functions. This module requires CEB sign-off before deployment.
📋
TEL Ruleset Sign-Off
12 principles documented
🔒
ITHC / Security
JSP 440 clearance
Accessibility
WCAG 2.1 AA confirmed
DLE Quality Rubric
No Red scores outstanding
🚀

Deployment Summary

JSP 822 V7 Compliant
TEL Ruleset (12 principles)75%
DSAT Governance100%
DLE Registration60%
TAFMIS Registration40%

Policy References:
JSP 822 V7.0 Vol 6 — Technology Enhanced Learning
JSP 822 Ch.5 — TEL Ruleset (12 principles)
JSP 822 §3.3 — DSAT application to DLE content
JSP 822 §3.9 — DLE Naming Conventions
JSP 794 — TAFMIS Course Naming
JSP 440 — Defence Security
STANAG 2591 — NATO Content Sharing
IEEE P1484 / P9274 — Open Standards