1. GETTING ACCESS — DO THIS FIRST
- Find your unit data steward (data stewards may be embedded in your unit, assigned at battalion, brigade, or division level, or positioned within a directorate at the ASCC — ask your chain of command if you’re unsure who to contact).
- Ask them to submit an MSS account request with your name, unit, MOS, and required access level.
- MSS admin team provisions your account and assigns markings (markings = the data categories and classification levels you’re authorized to see).
- You receive notification when account is active — typically 3–5 business days.
- Receive the MSS portal URL from your unit data steward. This is your login link.
2. WHAT IS MSS?
MSS is the mission command information system (MCIS) program of record, directed by the USAREUR-AF CG to enable rapid and accurate decision-making. It is a secure, web-based platform where your unit’s data lives and can be analyzed and acted upon. Think of it as a shared operations center for data: information from logistics, personnel, readiness, and other systems is collected, organized, and made accessible through applications your unit uses every day.
MSS is built on the Palantir Foundry platform, authorized for Army use under the Maven Smart System program.
Stores data from Army systems in a single, organized location; makes data visible through applications and dashboards; enables units to update records, report status, and track readiness; provides analysis tools for authorized personnel; supports AI-assisted analysis through AIP tools embedded in applications; includes Gaia — a map-based geospatial application for situational awareness and operational overlays; and provides command-level applications (e.g., CUB/CUA in USAREUR-AF) for operational briefing and C2.
Not a replacement for official systems of record (DCPDS, GCSS-A, MEDPROS, etc.); not classified by default — classification depends on data markings; not a public system — access is controlled and audited.
- Personnel Readiness — Soldier readiness status
- Logistics — equipment availability & maintenance
- Operational Reporting — SITREPs and updates
- Planning — orders, unit positions, task org
- C2 — unit status across the AOR
3. SECURITY RESPONSIBILITIES
- Use only your own credentials. Do not share your CAC, PIN, or access tokens.
- Access only data you are authorized to view.
- Report misrouted data immediately. If you see data at a higher classification than your clearance — STOP and report it.
- Do not export data without authorization. Exports are logged.
- Log out when done. Do not leave an MSS session unattended on an unlocked workstation.
- Report security incidents immediately to your supervisor and unit security officer.
4. TASKS
- Insert your CAC into the CAC reader.
- Open an approved web browser (Chrome or Firefox recommended).
- Navigate to the MSS portal URL provided by your unit data steward.
- When prompted, select your authentication certificate (not email certificate).
- Enter your CAC PIN when prompted.
- MSS home screen loads — you are now logged in.
| Element | Location | Purpose |
|---|---|---|
| Search bar | Top center | Find datasets, applications, and projects |
| Notification bell | Top right | System alerts, workflow updates |
| User profile icon | Top right | Account settings, markings (your authorized data categories), logout |
| Compass (file explorer) | Left sidebar | Browse all MSS resources; pin resources to top of Files page for quick access |
| Home button (logo) | Top left | Return to home screen from anywhere |
| Pinned items | Home main area | Shortcuts to frequently used resources |
| Recent activity | Home main area | Recently visited datasets and apps |
| Notepad | Left sidebar / search | Draft documents with AIP-assisted editing — use custom prompts and recently-used functions to accelerate writing |
5. Q1 2026 PLATFORM UPDATES
- AIP Analyst sessions persist when you switch tabs or change sections — no more losing your chat context
- Custom background colors on Workshop sections and pages for better visual organization
- Markdown editing now available in text input widgets
- Microsoft Word export — export Workshop content directly to .docx (in addition to CSV)
- Usage metrics — track how Workshop applications are being used across your organization
- Custom widgets on mobile — Workshop mobile now supports custom widget rendering
- Notepad is a document editor integrated into MSS for drafting reports, SOPs, and notes
- AIP-assisted editing — enter custom prompts to have AIP help draft, revise, or restructure your text
- Recently-used functions appear in the AIP Assist menu for quick reuse
- AI FDE integration — Notepad connects to the AI forward deployed engineer for deeper analysis
- Gaia default styles — interfaces with geometry properties now have configurable default map styles in Ontology Manager
- Gaia → Workflow Lineage — new shortcut to jump from a Gaia map directly to Workflow Lineage for tracing data sources
- Compass pinning — pin resources to the top of the Files page for quick access to frequently-used items
- Project selection now available during installation configuration
6. REPORTING PROBLEMS
| Problem Type | Who to Contact |
|---|---|
| Cannot log in | MSS Help Desk |
| Cannot access a project | Unit data steward |
| Data appears incorrect | Unit data steward (do not correct it yourself) |
| System error or crash | MSS Help Desk (provide error code and screenshot) |
| Security incident | Supervisor and unit security officer — IMMEDIATELY |
| Application not working | MSS Help Desk |
UPCOMING TRAINING — SL 1
| Dates | Location | Format | POC | Seats | Status |
|---|---|---|---|---|---|
| 14 APR 2026 | Wiesbaden, Clay Kaserne, Bldg 3312, Rm 104 | In-Person | SSG Johnson | 20 / 20 | OPEN |
| 05 MAY 2026 | Grafenwöhr, Bldg 244, Conf Rm B | In-Person | SFC Davis | 8 / 20 | 8 SEATS REMAINING |
| 18 JUN 2026 | Stuttgart, Kelley Bks, Bldg 3357 | In-Person | SSG Martinez | 20 / 20 | OPEN |
| 09 JUL 2026 | Virtual (MS Teams) | Virtual | SSG Johnson | 30 / 30 | OPEN |
Duration: 1 day (8 hours). Course runs 0800–1700. All dates subject to change — confirm with POC 5 days prior.
COMPETENCIES UPON COMPLETION
- Use Solution Designer to visually map data flows and application architecture before building
- Build project roadmaps using forward and backward planning from the commander’s requirement
- Create and organize Foundry projects via the UI
- Set up folder structure: raw / staging / curated layers
- Manage project access and permissions via UI
- Follow USAREUR-AF naming conventions and builder standards
- Ingest data using Pipeline Builder — visual, no code
- Configure connectors and file sources via UI
- Schedule pipeline runs via UI
- Understand raw / staging / curated dataset layers
- Create Object Types and set primary keys via Ontology Manager UI
- Define Interfaces and apply them to Object Types for consistent property contracts
- Configure Object Views to control how properties display to operators
- Create Link Types between objects via UI
- Understand Action types (write-back, form, webhook, conditional) and configure basic Actions
- Validate Object data in Object Explorer before building apps
- Build and publish Workshop applications with dashboards, forms, and filters
- Select and configure appropriate widgets for each use case
- Apply access controls and publish to users
- Use Foundry branching to build and promote via UI
- Distinguish development from production environments
- Apply USAREUR-AF builder standards
Branching = making a test copy of your work before going live. You build in the dev branch (your sandbox), test it, then publish to production (what users see).
THE FOUNDRY DATA STACK
Data flows through layers. As a SL 2 builder, you work in the middle layers using visual tools. Never modify raw data — report data errors to your data steward instead.
WORKSHOP WIDGET SELECTION
| You Need To… | Use This Widget |
|---|---|
| Display many objects or records | Object Table |
| Show details for one selected object | Object Detail |
| Let users filter the data they see | Filter Panel / Dropdown |
| Show a chart (bar, line, pie) | Chart Widget |
| Show geographic data on a map | Map Widget |
| Let users write or update data | Button + Action or Action Form |
| Show a single key metric prominently | Metric Tile |
| Navigate between app sections | Navigation / Tab Widget |
ONTOLOGY SETUP ORDER (UI STEPS)
- Confirm curated dataset exists and is populated (Pipeline Builder pipeline passing)
- Open Ontology Manager in the left sidebar
- Create Object Type → set primary key property → map properties from curated dataset
- Create Link Types between related Object Types (if needed)
- Publish ontology branch and test in Object Explorer
- Build Workshop app only after Object Explorer confirms objects are visible
NAMING CONVENTIONS
| Object Type | Convention | Example |
|---|---|---|
| Datasets (path) | /Project/AOR/source/raw|staging|curated | /USAREUR/EUR/personnel/curated/soldier_status |
| Object Types | PascalCase | UnitStatus |
| Properties (API name) | camelCase | unitName |
| Properties (display name) | Title Case | Unit Name |
| Link Types | PascalCase verb form | HasEquipment |
| Workshop app names | Unit + function + version | EUR-Personnel-Readiness-v2 |
Q1 2026 PLATFORM UPDATES
- Core Object Views are now generally available (Feb 2026) — standard, configurable views for browsing and exploring object data
- Foundry Branching support — develop and test Object Views safely in branches before promoting to production
- Updated Object Explorer with redesigned landing page for improved ontology discoverability
- Incremental execution enforcement — configure Pipeline Builder to require incremental execution for efficiency
- Preview behavior controls — enforce manual confirmation before running previews to prevent accidental full runs
- LLM data generation — generate notional/test data with LLMs directly in Pipeline Builder
- Approximate nearest neighbor join for vector similarity and geospatial matching
- File/file set output — output files and file sets directly from Pipeline Builder
- Role-based branch security — assign users roles to control who can manage and merge branches
- Upgraded branch security now enabled for all users by default
- Ontology SQL in Quiver for querying object sets directly
- Quiver time series — dedicated workspace for time series analysis
UPCOMING TRAINING — SL 2
| Dates | Location | Format | POC | Seats | Status |
|---|---|---|---|---|---|
| 21–25 APR 2026 | Wiesbaden, Clay Kaserne, Bldg 3312, Rm 104 | In-Person | SFC Chen | 7 / 15 | 7 SEATS REMAINING |
| 11–15 MAY 2026 | Grafenwöhr, Bldg 244, Conf Rm B | In-Person | SSG Williams | 3 / 15 | 3 SEATS REMAINING |
| 22–26 JUN 2026 | Stuttgart, Kelley Bks, Bldg 3357 | In-Person | SFC Chen | 15 / 15 | OPEN |
| 13–17 JUL 2026 | Virtual (MS Teams) | Virtual | SSG Williams | 20 / 20 | OPEN |
Duration: 5 days (40 hours). Course runs 0800–1700 each day. Prerequisite: SL 1 complete. All dates subject to change — confirm with POC 5 days prior.
WHO ATTENDS
- SL 2 Go on file — hard requirement, no exceptions
- Command-approved Project Brief — submitted to C2DAO ≥14 days before Day 1
- Supervisor signature on enrollment request
- Specific output: named dashboard, pipeline, Ontology type, or Quiver/Contour product
- Named consumer — a real person or role who will use the product
- All data sources accessible before Day 1
- No code required — Python / TypeScript / OSDK = SL 4 track, not FBC
- 5-day feasibility: functional prototype reachable within sprint
SPRINT WEEK STRUCTURE
| Day | Activity |
|---|---|
| Day 1 | In-brief: scope review, environment check, kickoff (0800–0900). Build (0900–1700). |
| Days 2–4 | Daily standup (0800, 15 min). Build (0815–1700). SME available throughout. |
| Day 5 | Product demo / peer review (0800–1000). Go/No-Go determination (1000–1200). Out-brief and handoff (1300–1500). |
GO STANDARD
| Standard | Criterion |
|---|---|
| Functional product | The product does what your Project Brief says it will do — your named consumer can use it |
| Documentation | Naming conventions followed; product description explains purpose and data sources |
| Handoff package | Complete by end of Day 5 — product description, data sources, limitations, maintenance guidance, promotion status, POC |
| Governance | Product in a branch; promotion plan documented or production promotion initiated |
ENROLLMENT
- T-21 days: Enrollment request submitted
- T-14 days: Project Brief approved by C2DAO
- T-10 days: Sprint workspace provisioned
- T-5 days: Candidate confirms access
- Day 1: Sprint begins
- 4 sprint events per fiscal year (quarterly)
- 4–16 participants per sprint
- 1 SME per ≤8 participants
- Annual schedule published each October
WHAT THIS COURSE COVERS
What MSS does for your formation and why it matters; how to evaluate data products — operationally, not technically; how to guide your formation’s data posture through resourcing, prioritization, and governance; what questions to ask about data freshness, source integrity, and product quality; and the training pipeline that qualifies your data workforce (SL 1 through SL 5).
Not a platform navigation course — you will see MSS, not operate it; not a data literacy primer — you already understand why data matters; not a substitute for SL 1 in the standard pipeline; not a qualification to build, modify, or administer anything on the platform.
DAILY SCHEDULE
| Time | Block | Content |
|---|---|---|
| 0800–0830 | 1 | Course introduction; senior leader role in the data environment |
| 0830–0930 | 2 | Why MSS exists — strategic context, CG guidance (Ch 1) |
| 0930–1030 | 3 | The platform and what it produces — five-layer architecture, data product types, live walkthrough (Ch 2) |
| 1030–1045 | — | Break |
| 1045–1200 | 4 | How data products impact your formation — data as command function, failure patterns, Commander’s Data PIRs (Ch 3) |
| 1200–1300 | — | Lunch |
| 1300–1345 | 5 | The training pipeline — SL 1 through SL 5, FBC, resourcing decisions (Ch 4) |
| 1345–1430 | 6 | Governance — the governance chain, VAUTI framework, red flags (Ch 5) |
| 1430–1445 | — | Break |
| 1445–1530 | 7 | How data projects work — agile overview, roadmap vs POAM (Ch 6) |
| 1530–1615 | 8 | Working with data professionals — engagement practices, terminology (Ch 7) |
| 1615–1700 | 9 | Asking the right questions — diagnostic questions for products, workforce, and AI (Ch 8–9) |
DOCUMENTS
COMPETENCIES UPON COMPLETION
- Design multi-page Workshop applications with conditional logic and variable passing
- Build dynamic layouts: show/hide panels based on user selections
- Design navigation flows and inter-page parameter handoff
- Publish and manage application versions
- Build multi-source join pipelines with complex aggregations (visual)
- Design scheduled and triggered pipeline runs
- Review and interpret data lineage graphs
- Escalate to SL 4 when code transforms are required
- Design Object Type and Link Type models via Ontology Manager UI
- Architecture thinking: model for downstream app requirements, not just source data
- Design Action workflows with validation and approval logic via UI
- Coordinate ontology changes with all downstream application owners
- Conduct advanced Contour analysis: complex aggregations, pivots, calculated columns, saved views
- Build advanced Quiver dashboards with multi-object analysis and linked views
- Create reusable analysis templates for unit use
- Configure AIP Logic workflow parameters and natural language query on Object Types
- Build basic AIP agents in Agent Studio — connect Object Types, write output instructions, test and validate responses
- Orient to AIP Analyst and AI FDE — awareness of the full AIP toolset
- Advanced agent development (custom tools, action logic, production deployment) is SL 4H scope
- Configure Kairos timeline widgets — Ontology-driven, real-time planning visualization (distinct from static Gantt charts)
- Orient to Target Workbench — targeting workflow integration; operational use is SL 4A/SL 4B scope
- Ensure Object Types are structured to support both tools
- Configure Automations on Object Types — schedule or condition-triggered property updates, pipeline runs, and notifications
- Model basic business processes in Machinery — multi-step workflows with roles, transitions, and object linkage
- Monitor automation execution history and active process instances
- Manage branching and production promotion via UI
- Apply USAREUR-AF C2DAO governance standards and naming conventions
- Manage governance workflows with data stewards
- Ensure coalition-facing products have C2DAO coordination and NAFv4 compliance review
SL 3 vs SL 4 — WHAT YOU OWN VS WHAT YOU ESCALATE
| You Own At SL 3 (UI) | Escalate to SL 4 When… |
|---|---|
| Application design and UX | Custom Python/PySpark transforms needed |
| Ontology model design (via UI) | Functions on Objects (TypeScript) required |
| Advanced Pipeline Builder (visual) | Incremental watermark or code logic needed |
| AIP Logic configuration + basic agent building | Custom tool development, agentic action logic, or production agent deployment needed |
| Governance coordination | External application (OSDK) needed |
| Production promotion via UI | CI/CD pipeline automation needed |
C2DAO GOVERNANCE GATES — HARD STOPS
| Requirement | SL 3 Action | Hard Gate? |
|---|---|---|
| New shared Object Type or dataset | Coordinate with C2DAO before publishing to production | Yes |
| Coalition / MPE-facing data product | C2DAO coordination + NAFv4 compliance review | Yes — do not skip |
| Schema change to existing shared resource | Notify all downstream owners; coordinate with steward | Yes |
| New AIP Logic workflow on operational data | Authorization review before deployment | Yes |
| Access permission changes | Submit through formal request to unit data steward | Yes |
UPCOMING TRAINING — SL 3
| Dates | Location | Format | POC | Seats | Status |
|---|---|---|---|---|---|
| 28 APR – 02 MAY 2026 | Wiesbaden, Clay Kaserne, Bldg 3312, Rm 104 | In-Person | CW3 Thompson | 4 / 10 | 4 SEATS REMAINING |
| 15–19 JUN 2026 | Virtual (MS Teams) | Virtual | CW2 Rodriguez | 15 / 15 | OPEN |
| 17–21 AUG 2026 | Wiesbaden, Clay Kaserne, Bldg 3312, Rm 104 | In-Person | CW3 Thompson | 10 / 10 | OPEN |
Duration: 5 days (40 hours). Course runs 0800–1700 each day. Prerequisites: SL 1 and SL 2 complete. All dates subject to change — confirm with POC 5 days prior.
Q1 2026 PLATFORM UPDATES
- AIP Logic branch selection for evals — run evals against specific branches to test changes before promotion
- Autopilot (new, Mar 2026) — visualize, monitor, and debug automation workflows in a dedicated UI
- Interface parameters now supported in Automate actions
- Function effects supported in Automate — actions can now trigger function side effects
- Streaming time series conditions — create conditions on streaming time series data in Automate
- Presentation mode — create and present lineage visualizations with frames
- Multi-ontology support — view lineage across multiple ontologies in one graph
- Log search — search logs directly from Workflow Lineage nodes
- Monitoring status colors — color lineage nodes by monitoring status for quick health assessment
- Expanded access — Workflow Lineage is now accessible from more locations across the platform (Gaia, Quiver, Notepad, Automate)
- Role-based branch security — assign users specific roles (manage, merge) for fine-grained branch access control
- Upgraded branch security enabled for all users — all new branches use the enhanced security model
- Object Views + Branching — develop and test Object Views safely in branches before production
- Materializations now supported for object types with row-level policies
TRACK SELECTION BY MOS / ROLE
| Role / MOS | Recommended Track | Advanced |
|---|---|---|
| Warfighting Function Tracks (SL 4A–F) | ||
| G2/S2 — MI units, ISR analysts | SL 4A (Intelligence) | — |
| FA officers/NCOs — Fire support | SL 4B (Fires) | — |
| Maneuver units — G3/S3 data roles | SL 4C (Movement & Maneuver) | — |
| G4/S4 — Logistics, GCSS-A | SL 4D (Sustainment) | — |
| Air defense, CBRN, force protection | SL 4E (Protection) | — |
| G6/S6 — C2 systems, networks | SL 4F (Mission Command) | — |
| Technical Specialist Tracks (SL 4G–O) | ||
| FA49 — Operations Research Analyst | SL 4G (ORSA) | SL 5G |
| G2/S2 quantitative analyst | SL 4G (ORSA) or SL 4K (KM) | SL 5G / SL 5K |
| 17A/17C — Cyber officer/NCO | SL 4L (SWE) or SL 4H (AI Eng) | SL 5L / SL 5H |
| 25D — IT specialist | SL 4L (SWE) | SL 5L |
| AI/ML engineer (GS/contractor) | SL 4H (AI Eng) or SL 4M (MLE) | SL 5H / SL 5M |
| Data scientist (GS/contractor) | SL 4G (ORSA) or SL 4M (MLE) | SL 5G / SL 5M |
| G8/S8 — Resource manager | SL 4J (PM) | SL 5J |
| Program Manager (PM / GS) | SL 4J (PM) | SL 5J |
| KMO / Knowledge Officer / 37F | SL 4K (KM) | SL 5K |
| Civil Affairs | SL 4J (PM) or SL 4K (KM) | SL 5J / SL 5K |
| UI/UX designer (GS/contractor) | SL 4N (UX Designer) | SL 5N |
| Platform engineer / DevOps / SysAdmin | SL 4O (Platform Eng) | SL 5O |
- Configure Code Workspaces (Python/R) within Foundry
- Statistical modeling: regression, classification, validation for readiness/logistics
- Time series forecasting with ARIMA/SARIMA patterns
- Monte Carlo simulation for COA comparison and risk quantification
- Linear programming for resource allocation and scheduling optimization
- Wargame/exercise data collection architecture and aggregation pipelines
- Analytical decision support products (Quiver/Contour) to commander standard
- Communicate uncertainty: confidence intervals, sensitivity analysis, briefing standards
- Author AIP Logic workflows: prompt engineering, chain design, output handling
- Build and configure AIP Agent Studio agents with tools, memory, and orchestration
- Implement LLM integration patterns: ontology data grounding, RAG, context construction
- Apply AI safety requirements: human-in-the-loop gates, output validation, OPSEC
- Write Python transforms that prepare data for AI consumption
- Connect AIP Logic workflows to Object Types and Actions
- Test and red-team AI outputs; evaluate quality against defined standards
- Deploy and monitor AIP Logic workflows in production
- Configure Code Workspaces for model development (GPU, packages, environment management)
- Build and evaluate ML models within the Foundry environment
- Manage model versioning, experiment tracking, and reproducibility
- Deploy models to production and integrate with Ontology Objects and Actions
- Implement MLOps patterns: monitoring, drift detection, retraining triggers
- Apply responsible AI practices and model documentation standards for operational use
- Stand up Agile project structures (backlog, sprint cadence, ceremonies) for data and AI builds
- Write user stories and acceptance criteria that SL 4G–O developers can execute without ambiguity
- Manage the ML/AI project lifecycle: six phases from Problem Definition through Sustainment
- Translate commander requirements into prioritized, sprint-ready backlogs
- Specify project tracking systems (sprint boards, status dashboards) for SL 4L implementation
- Build and maintain risk registers; manage dependency blockers across specialist tracks
- Conduct production readiness reviews against the Definition of Done before release
- Execute change management plans for new MSS capability rollout to operational units
- Design knowledge architecture for AAR, lessons learned, doctrine, and SOP repositories
- Build AAR capture systems using Workshop forms and Object Type pipelines
- Design and operate lessons-learned ingestion and tagging pipelines
- Use AIP Logic for knowledge summarization, search augmentation, and theme extraction
- Build full-text and semantic search systems over knowledge repositories
- Manage doctrine and SOP version control within Foundry
- Build personnel expertise mapping (skills/experience registries)
- Design knowledge transfer and unit continuity processes using MSS
- NEW: Leverage Document Intelligence (GA) for automated document parsing and extraction
- NEW: Use Object Views (GA) for curated knowledge browsing interfaces
- Authenticate and query the Foundry Ontology via OSDK (TypeScript/Python)
- Execute Actions, subscribe to Object changes, handle pagination and filtering via OSDK
- Use Foundry Platform SDK for dataset operations, file management, and branch management
- Build TypeScript Functions on Objects (computed properties, bulk query patterns)
- Write and test complex Action validators with TypeScript
- Build Slate applications integrated with the Foundry API
- Apply USAREUR-AF code review and deployment standards for MSS applications
- NEW: Use Pilot for AI-assisted code generation within Code Repositories
- NEW: Monitor OSDK client health via the Health Dialog dashboard
- NEW: Integrate external tools via Model Context Protocol (MCP) connectors
- Conduct user research in operational and classified environments (interview, contextual inquiry, usability testing)
- Design information architectures for data-dense operational displays
- Build interactive prototypes from low-fidelity sketches through high-fidelity mockups
- Design Workshop layouts: widget selection, dashboard hierarchy, responsive patterns
- Apply visual design standards for tactical displays: classification marking, contrast, field conditions
- Ensure Section 508 / WCAG 2.1 AA accessibility compliance
- Architect and operate Kubernetes clusters for MSS workloads
- Implement Infrastructure as Code with GitOps workflows and continuous reconciliation
- Design CI/CD pipelines: automated build, test, scan, and deploy for MSS applications
- Harden containers using DoD Iron Bank images, vulnerability scanning, and SHA256 digest pinning
- Deploy across classification boundaries and DDIL environments (air-gapped, edge clusters)
- Manage RMF/ATO lifecycle from the infrastructure perspective, STIG compliance
- NEW: Configure and optimize Compute Modules (GA) for scalable pipeline execution
- NEW: Manage Data Connection source types and third-party integration patterns
▾ Warfighting Function Tracks (SL 4A–F)
| Designation | Track | Publication |
|---|---|---|
| SL 4A | Intelligence | TM_40A_INTELLIGENCE.pdf |
| SL 4B | Fires | TM_40B_FIRES.pdf |
| SL 4C | Movement & Maneuver | TM_40C_MOVEMENT_MANEUVER.pdf |
| SL 4D | Sustainment | TM_40D_SUSTAINMENT.pdf |
| SL 4E | Protection | TM_40E_PROTECTION.pdf |
| SL 4F | Mission Command | TM_40F_MISSION_COMMAND.pdf |
SL 5 SERIES — PUBLICATIONS
- Nonlinear programming, stochastic models
- Agent-based modeling (ABMS)
- Campaign wargame data architecture
- Multi-agent orchestration & shared state
- Advanced RAG, domain-adapted LLMs
- AI red-team assessment & observability
- Automated retraining pipelines
- Transformer fine-tuning, GNNs
- Federated retraining, adversarial robustness
- PI planning, cross-team governance
- GO/SES briefing, Palantir partnership
- Technical debt at program scale
- Federated KM architecture, NATO integration
- STANAG 4778 conformance
- Knowledge graphs at scale
- Scale, multi-tenancy, event streaming
- OWASP, SAST, authorized pen testing
- Architecture review, platform governance
- Design systems at scale, component libraries
- DDIL-aware and cross-domain UI design
- DesignOps, ResearchOps, accessibility at enterprise scale
- Multi-cluster fleet management, SRE practices
- RMF/ATO automation, continuous compliance
- Cross-domain infrastructure, developer experience engineering
Written for commanders, senior NCOs, and senior Civilians. Covers command responsibilities, evaluating data products, directing a data-capable formation, and decision frameworks.
Format: Short (~20–30pp). Principles, not procedures. Chapter/paragraph numbered.
Key topics: Commander’s data responsibilities • Evaluating analytical products • Standing up MSS capability • Data governance and stewardship
Comprehensive platform-agnostic data literacy reference. Recommended prior reading before SL 1.
Format: Long (~50–100pp). Examples, vignettes, detailed explanations, annexes.
Key topics: Data types and structures • Pipeline concepts • Data quality • Analysis fundamentals • Security and classification • Operational data integration • Governance
FULL PUBLICATIONS INDEX
| Publication | Audience | Purpose | When to Read |
|---|---|---|---|
| Foundation — All Personnel | |||
| Data Literacy (SL) | O-5+ / SGM+, Sr Civilians | Principles, command responsibilities | Before directing MSS use |
| Data Literacy | All personnel | Comprehensive data literacy reference | Before SL 1 (recommended) |
| SL 1 | All personnel | Operate MSS as end user | Before first MSS access |
| SL 2 | All staff | Build pipelines, Ontology, Workshop via UI — no code | After SL 1 |
| SL 3 | Data-adjacent specialists | Design complex apps; governance; C2DAO standards | After SL 1 + SL 2 |
| SL 4 — Warfighting Function Tracks (by WFF assignment) | |||
| SL 4A | G2/S2, MI, ISR | Intelligence WFF MSS integration | After SL 3 |
| SL 4B | FA, fire support | Fires WFF MSS integration | After SL 3 |
| SL 4C | Maneuver, G3/S3 | Movement & Maneuver WFF MSS integration | After SL 3 |
| SL 4D | G4/S4, logistics | Sustainment WFF MSS integration | After SL 3 |
| SL 4E | Air defense, CBRN, force protection | Protection WFF MSS integration | After SL 3 |
| SL 4F | G6/S6, C2, networks | Mission Command WFF MSS integration | After SL 3 |
| SL 4 — Technical Specialist Tracks (by role/MOS) | |||
| SL 4G | ORSA / FA49 | Statistical modeling, simulation, wargame analytics | After SL 3 |
| SL 4H | AI Engineers | AIP Logic authoring, Agent Studio, LLM integration | After SL 3 |
| SL 4M | ML Engineers | Code Workspaces, model training, MLOps | After SL 3 |
| SL 4J | PMs / G8 | PM dashboards, milestone tracking, portfolio analysis | After SL 3 |
| SL 4K | KMs / KMOs | Knowledge repositories, AIP summarization, lessons learned | After SL 3 |
| SL 4L | SWEs | OSDK, full-stack Foundry apps, TypeScript Functions | After SL 3 |
| SL 4N | UI/UX Designers | Soldier Centered Design, Workshop & Slate UI, accessibility | After SL 3 |
| SL 4O | Platform Engineers | Kubernetes, CI/CD, DevSecOps, Infrastructure as Code | After SL 3 |
| SL 5 — Advanced Technical Tracks (by role/MOS) | |||
| SL 5G–O | Senior developers (all tracks) | Advanced versions of each SL 4 specialist track | After SL 4 (by track) |
| CDA Reference — SL 3 and Specialist Tracks (SL 4G–O) | |||
| EA Series (00–05) | SL 3+, SL 4K, SL 4L | Enterprise Architecture — foundation, schools of thought, artifacts, governance, military application | With or after SL 3 |
| CDA Doctrine Overview | SL 4G–O | Doctrine-driven development; JRTC lessons; Foundry Ontology blueprint | At start of SL 4G–O |
| Identity vs. Classification | SL 3, SL 4K, SL 4L | Identity resolution and classification governance at scale | With SL 3 |
| Enterprise Data Compass | SL 4J, SL 4K | Authoritative data architecture, ontology, and semantic governance standard | With SL 4J/K |
| CDA Slide Library | All tracks (prereq reading) | 29 decks — Intro To Data (SL 1 prereq), Data 101 (SL 2 prereq), Data 201 (SL 3/40G–O prereq) | Before each TM level |
CDA REFERENCE MATERIAL
Six-module reference series covering EA foundations, schools of thought, artifacts and views, governance, and military application. Supports SL 3, SL 4K, and SL 4L.
Key topics: EA vs DA • TOGAF, Zachman, DODAF frameworks • Capability mapping • NAF/ArchiMate • Army EA governance
Doctrine-aligned data product design using JRTC lessons learned. Covers doctrine-first Ontology design, the Three-Generation Dilemma, and AVT25 assessment case study.
Key topics: MDMP data support • COA analysis modeling • Doctrinal object types • AVT25 tools case study
XVIII ABC’s corps-level ODT pilot. Their organizational journey, manning structure (PM + UX + SWE + DE + DS), problem-solution development process, Program Increment cycles, and BDA visualization case study (prototype → MVP → POR in 9 months). Military Review, Feb 2026.
Key topics: ODT organization • TIO governance • ASWF methodology • Exercise integration • Echeloned ODT employment • Decision optimization
Required reading: SL 4J, SL 4F • Recommended: All SL 4 tracks
How five tools in the same enclave multiplied work exponentially by failing to share doctrinal primitives. The case for doctrine-first shared data architecture.
Key topics: Shared primitives • DBO architecture • Exponential work multiplication • Time cost analysis
One officer’s thought piece proposing terminology for decision optimization at echelon. Introduces useful shorthand: operationalized data, Automated Fighting Products (AFP), and Decision Optimization Teams. Names the Maven Smart System as an ASCC-level COP platform. Military Review, Jan–Feb 2025.
Key topics: Operationalized data • AFP evolution • DOT at echelon • FA 26B/49/57 workforce • Training pipeline
Supplementary reading: SL 4F, SL 4G, SL 4J • Recommended: All SL 4 tracks, Senior Leaders
EXTERNAL DOCTRINE & INSTITUTIONAL SOURCES
MCCoE’s conceptual framework for integrating data-centric capabilities into mission command. Defines decision optimization at echelon and the role of Operational Data Teams in the command post.
Relevance: SL 4F (Mission Command), SL 4J (Program Manager), EXEC (Senior Leader)
CTC observer trends on data-centric operations, common gaps in unit-level data readiness, and recommendations for training programs. Published Feb 2025.
Relevance: SL 1 (all personnel), SL 4A–F (WFF tracks), instructor development
TRADOC’s institutional approach to data literacy across the force. Defines competency levels, assessment criteria, and integration with PME. Informs the MSS SL 1/20 foundation sequence.
Relevance: Data Literacy publications, SL 1, SL 2, instructor certification (T3-I)
Public announcement of Maven C2 integration into training and education at the Combined Arms Center. Establishes institutional backing for MSS-based training programs. Published Feb 2026.
Relevance: All tracks — institutional context for the MSS training program
CORE DATA LITERACY CONCEPTS
TRAINING PATH
CONTACT ROUTING
| Issue | Route To | Priority |
|---|---|---|
| Cannot log in / CAC issues | MSS Help Desk | Normal |
| No access to a project or dataset | Unit data steward | Normal |
| Data appears incorrect | Unit data steward (do not self-correct) | Normal |
| System error, crash, or outage | MSS Help Desk + screenshot + error code | Normal |
| Application broken or not loading | MSS Help Desk | Normal |
| Building question / how-to | Unit data lead or USAREUR-AF data team | Normal |
| Governance / C2DAO question | USAREUR-AF C2DAO | Normal |
| Security incident | Supervisor + unit security officer | IMMEDIATE |
COMMON DAILY TASKS
| Task | How |
|---|---|
| Find a record | Search bar or Filter Panel |
| Filter the view | Select values in the Filter Panel |
| Export data | Export / Download button → CSV or Excel |
| Submit or update a record | Click record → Action button → fill in → Submit |
WHEN IT BREAKS
SECURITY — DO NOT
- Do not export data to a personal device or unapproved storage
- Do not share your MSS credentials with anyone — URLs and screenshots are fine unless data is sensitive
- Do not enter classified information into MSS unless your instance is approved for that classification level
- Do not screenshot or share MSS screens containing data above your network’s approved classification
- Do not use MSS on public or unsecured Wi-Fi
- If you see data you should not have access to — stop and report to your data steward immediately
BEFORE CALLING FOR HELP — COLLECT THIS INFORMATION
- Your username and unit
- Name of the application, dataset, or pipeline you were using
- Exact error message (screenshot preferred)
- Time the error occurred (local or Zulu — state which)
- Steps that led to the error in order
- Browser and workstation you are using
PREREQUISITES BEFORE FIRST LOGIN
- Annual Cyber Awareness Training — required for all DoD personnel; must be current
- MSS User Onboarding Brief — provided by unit data steward
- Account request approved — submit at mss.data.mil or through your unit data steward; provisioning generally completes within 24 hours. If access is not active after 24 hours, contact your data steward directly.
IMPORTANT: If you work on multiple enclaves (NIPR, SIPR, MPE, etc.), you must complete account setup and first login on each enclave separately. Your account on one enclave does not carry over to another.
USAREUR-AF DATA TEAM
USAREUR-AF Operational Data Team
Army AI/Data Accelerator (C2DAO)
Reference Documents
Technical Manuals — Foundation (All Staff)
TM-40 Warfighting Function Tracks (6 — click to expand)
TM-40 Technical Specialist Tracks (8 — click to expand)
- Regression, classification, forecasting
- Monte Carlo COA analysis
- Optimization and sensitivity analysis
- AIP Logic workflow design
- Agent configuration
- LLM integration patterns
- NEW: AIP Document Intelligence (GA) — chunking & embedding
- NEW: AI FDE (GA Mar 2026)
- Feature engineering, experiment tracking
- Batch inference, model versioning
- Drift detection, retraining pipelines
- NEW: Model Studio (GA Feb 2026) — no-code model training
- Scrum / Kanban for data projects
- ML/AI project lifecycle
- Risk register, release planning
- Knowledge ontology design
- Lessons-learned intake pipeline
- SOP review workflows
- NEW: Document Intelligence, Object Views
- OSDK & Platform SDK
- Functions on Objects, Actions
- CI/CD, security, Slate
- NEW: Pilot, OSDK Health, MCP
- Workshop UI patterns & design systems
- User research in military contexts
- Accessibility & DDIL-aware design
- Foundry infrastructure management
- SRE practices & observability
- RMF/ATO compliance automation
- NEW: Compute Modules, Data Connection
TM-50 Advanced Technical Tracks (8 — click to expand)
Train the Trainer — T3 (2 courses + SOPs — click to expand)
Concepts Guides (23 — click to expand)
Practical Exercises (13 — click to expand)
Pre-Assessment Tests (27 — click to expand)
Post-Assessment Tests (26 — click to expand)
Course Syllabi (26 — click to expand)
Self-Study Guides (17 — click to expand)
Lesson Plans (5 — click to expand)
Administrative & Institutional (12 — click to expand)
Enterprise Architecture Series (6 — click to expand)
Architecture & Design References (28 — click to expand)
CDA — Common Data Architecture (15)
GDAP — Governance Data Access Platform (5)
MIM — NATO MIP Information Model (7)
Ontology Design (1)
External Doctrinal & Strategic References
ARMY DOCTRINE & REGULATION
| Publication | Title | Type | Tracks |
|---|---|---|---|
| ADP 3-0 | Operations | Doctrine | WFF (A–F) |
| ADP 3-19 | Fires | Doctrine | SL 4B |
| ADP 3-37 | Protection of the Force (Jul 2019) | Doctrine | SL 4E |
| ADP 3-90 | Offense and Defense | Doctrine | SL 4C |
| ADP 5-0 | The Operations Process | Doctrine | SL 4F, SL 4G |
| ADP 6-0 | Mission Command (Jul 2019) | Doctrine | SL 4F |
| ADP 7-0 | Training | Doctrine | Training Mgmt |
| AR 25-1 | Army Information Technology (Jul 2019) | Regulation | All |
| AR 25-2 | Army Cybersecurity (Apr 2019) | Regulation | SL 4H, SL 4M, SL 4L |
| AR 25-30 | Army Publishing Program | Regulation | SL 5H |
| AR 25-400-2 | Army Records Management | Regulation | SL 4K |
| AR 5-11 | Management of Army Models and Simulations | Regulation | SL 4G |
| AR 71-9 | Warfighting Analysis | Regulation | SL 4G |
| AR 350-1 | Army Training and Leader Development | Regulation | Training Mgmt |
| AR 525-2 | Force Protection | Regulation | SL 4E |
| AR 530-1 | Operations Security | Regulation | SL 4E |
| FM 2-0 | Intelligence (Oct 2023) | Doctrine | SL 4A |
| FM 3-0 | Operations (Mar 2025) | Doctrine | WFF (A–F) |
| FM 3-01 | U.S. Army Air and Missile Defense | Doctrine | SL 4B |
| FM 3-09 | Fire Support and Field Artillery Operations (Aug 2024) | Doctrine | SL 4B, SL 4C |
| FM 3-12 | Cyberspace and EW Operations | Doctrine | SL 4E, SL 4H, SL 4M, SL 4L |
| FM 3-27 | Army Global Ballistic Missile Defense | Doctrine | SL 4B |
| FM 3-55 | Information Collection | Doctrine | SL 4A |
| FM 3-60 | Targeting (Aug 2023) | Doctrine | SL 4B |
| FM 3-81 | Maneuver Enhancement Brigade | Doctrine | SL 4C |
| FM 3-90 | Offense and Defense (May 2023) | Doctrine | SL 4C |
| FM 4-0 | Sustainment (Aug 2024) | Doctrine | SL 4D |
| FM 1-0 | Human Resources Support | Doctrine | SL 4D |
| FM 5-0 | Planning and Orders Production (Nov 2024) | Doctrine | SL 4F, SL 4C |
| FM 6-0 | Commander’s Activities (May 2022) | Doctrine | SL 4F, SL 4C |
| FM 7-0 | Training (Jun 2021) | Doctrine | Training Mgmt |
| ATP 2-01 | Collection Management (May 2023) | Doctrine | SL 4A |
| ATP 2-33.4 | Intelligence Analysis | Doctrine | SL 4A |
| ATP 2-22.9-1 | PAI/OSINT (Oct 2023) | Doctrine | SL 4A |
| ATP 3-01.81 | Counter-UAS | Doctrine | SL 4B |
| ATP 3-09.42 | Fire Support for M&M | Doctrine | SL 4B |
| ATP 3-13.3 | Army Operations Security | Doctrine | SL 4E |
| ATP 3-90.4 | Combined Arms Mobility | Doctrine | SL 4C |
| ATP 5-0.1 | Army Design Methodology | Doctrine | SL 4F |
| ATP 5-0.3 | Multi-Service Tactics for Ops Assessment | Doctrine | SL 4G |
| ATP 6-01.1 | Techniques for Effective Knowledge Management | Doctrine | SL 4K, SL 5K |
| TC 6-0.2 | Battle Staff Operations | Doctrine | SL 4F |
| DA PAM 5-11 | Verification, Validation & Accreditation | Doctrine | SL 4G |
| DA PAM 25-1-1 | IT Implementation Instructions | Doctrine | SL 4K, SL 4L |
| DA PAM 25-2-5 | Cybersecurity Technical Reference | Doctrine | SL 4H, SL 4M, SL 4L |
| DA PAM 25-40 | Army Publishing Program Procedures | Doctrine | Standards |
| DA PAM 25-403 | Army Records Information Management | Doctrine | SL 4K |
| DA PAM 600-3 | Officer Professional Development | Doctrine | SL 4G |
DoD DIRECTIVES & INSTRUCTIONS
| Publication | Title | Type | Tracks |
|---|---|---|---|
| DoDD 3000.09 | Autonomy in Weapon Systems (Jan 2023) | Directive | WFF (A–F) |
| DoDI 5000.87 | Software Acquisition Pathway (Oct 2020) | Instruction | SL 4L, SL 5L, SL 4J, SL 5J |
| Army Directive 2024-02 | Agile Software Dev & Acquisition (Dec 2024) | Directive | SL 4L, SL 5L, SL 4J, SL 5J |
| Army Directive 2024-03 | Army Digital Engineering | Directive | SL 4H, SL 4M, SL 4L |
TRADOC PUBLICATIONS
Published at adminpubs.tradoc.army.mil, not armypubs.army.mil
| Publication | Title | Type | Tracks |
|---|---|---|---|
| TR 350-70 | Army Learning Policy and Systems | Regulation | Training Mgmt |
| TP 350-70-3 | Faculty and Staff Development Program | Pamphlet | Training Mgmt |
| TP 350-70-7 | Army Educational Processes | Pamphlet | Training Mgmt |
| TP 350-70-14 | Training Development in Institutional Domain | Pamphlet | Training Mgmt |
NATO STANDARDS & AGREEMENTS
| Publication | Title | Type | Tracks |
|---|---|---|---|
| ADatP-34 / NISP | C3 Interoperability Standards and Profiles | Standard | SL 4K, SL 4L |
| STANAG 5636 / NCMS | Core Metadata Specification | STANAG | SL 4K, SL 5K |
| STANAG 5643 (proposed) | MIM Governance Standard | STANAG | SL 4K, SL 4L, SL 5K, SL 5L |
| ADatP-5644 | Web Service Messaging Profile (WSMP) | Standard | SL 4L, SL 5L |
| ADatP-36 | Friendly Force Information (FFI) | Standard | SL 4A, SL 4C |
| STANAG 5527 | FFT Systems Interoperability | STANAG | SL 4A |
DoD & ARMY STRATEGIC GUIDANCE (not doctrine)
| Document | Authority | Date | Tracks |
|---|---|---|---|
| DoD Data Strategy | OSD | Oct 2020 | All |
| DoD Data, Analytics & AI Adoption Strategy | CDAO | Nov 2023 | All |
| DoD Responsible AI Strategy | CDAO | Jun 2024 | SL 4H/M, SL 5H/M |
| DoD Zero Trust Reference Architecture v2.0 | DISA/NSA | Jul 2022 | SL 3 |
| DoD AI Cybersecurity Risk Mgmt Guide | DoD CIO | 2024 | SL 4H/M, SL 5H/M |
| DoD Software Modernization Strategy | OSD CIO | Feb 2022 | SL 4L, SL 5L |
| JADC2 Strategy Summary | Joint Staff | Mar 2022 | WFF (A–F), SL 4G |
| JCOIE | Joint Staff J-7 | Current | SL 4F |
| Army Data Plan | Army CIO | Oct 2022 | All |
| Army Cloud Plan | Army CIO | Oct 2022 | SL 1, SL 2, SL 3 |
| UDRA v1.1 | DASA(DES) | Feb 2025 | SL 3, Specialist (G–O) |
| Army CIO Data Stewardship Memo | Army CIO | Apr 2024 | SL 1, SL 2, SL 3, SL 4K |
NATO STRATEGIC GUIDANCE (not doctrine)
| Document | Date | Tracks |
|---|---|---|
| NATO Data Strategy for the Alliance | Feb 2025 | SL 3, SL 4K, SL 5K |
| NATO Data Centric Reference Architecture v2 | 2025 | SL 3 |
| NATO Data Quality Framework for the Alliance | Aug 2025 | SL 3 |
| NATO Digital Transformation Implementation Strategy | Oct 2024 | WFF (A–F) |
| NATO Warfighting Capstone Concept | 2021 | SL 4F |
Professional Reading & Lessons Learned (65+ articles)
MILITARY REVIEW — Army University Press (14)
| Title | Date | Tracks |
|---|---|---|
| Data-Centric at the Division: 3ID’s One-Year Journey to Transform and Modernize | Jan 2025 | All |
| Modernizing Military Decision-Making: Integrating AI into Army Planning | Aug 2025 | SL 4F, SL 4H, SL 4G |
| The Military Needs Frontier Models | Aug 2025 | SL 4H, SL 4M, SL 4L |
| Exploring AI-Enhanced Cyber and Information Operations Integration | Mar-Apr 2025 | SL 4E, SL 4A, SL 4H |
| Authorities and the Multidomain Task Force | Mar-Apr 2025 | SL 4A, SL 4B, SL 4F |
| Taking a Data-Centric Approach to Unit Readiness | 2024 | All, esp. SL 4G |
| Attaining Readiness by Developing a Data-Centric Culture | 2024 | All, esp. SL 4J |
| Sustaining Our People Advantage in Data-Centric Warfare | 2024 | All |
| AI as a Combat Multiplier: Using AI to Unburden Army Staffs | Sep 2024 | SL 4H, SL 4F, SL 4G |
| Transforming the Multidomain Battlefield with AI | 2024 | SL 4H, SL 4M, SL 4A |
| The Coming Military AI Revolution | May-Jun 2024 | SL 4H, SL 4M |
| AI in Modern Warfare: Strategic Innovation and Emerging Risks | Sep-Oct 2024 | All |
| Advancing Counter-UAS Mission Command Systems | May-Jun 2024 | SL 4E, SL 4F |
| The True Test of Mission Command | Sep-Oct 2024 | SL 4F |
PARAMETERS — Army War College Quarterly (3)
| Title | Date | Tracks |
|---|---|---|
| Responsibly Pursuing Generative AI for the War Fighter | Winter 2025-26 | SL 4H, SL 4M, All |
| Integrating AI and ML into COP and COA Development | 2024-25 | SL 4G, SL 4H, SL 4F |
| Trusting AI: Integrating AI into the Army’s Professional Ethic | 2024 | All |
MIPB — Military Intelligence Professional Bulletin (6)
| Title | Date | Tracks |
|---|---|---|
| FRIDAY: Unlocking OSINT for a Data-Driven Army | 2025 | SL 4A, SL 4H, SL 4L |
| Intelligence Support to Information Advantage | Jan-Jun 2026 | SL 4A, SL 4K |
| Using AI to Create Digital Enemy Commanders | Jul-Dec 2025 | SL 4H, SL 4M, SL 4A |
| The Market Knows Best: Prediction Markets for National Security | Jul-Dec 2025 | SL 4A, SL 4G |
| Army Transitioning to Support Deep Sensing in MDO | Jul-Dec 2025 | SL 4A, SL 4B, SL 4C |
| Open-Source Intelligence Support to Targeting | 2024 | SL 4A, SL 4B |
FIELD ARTILLERY BULLETIN — Line of Departure (6)
| Title | Date | Tracks |
|---|---|---|
| The New Digital Kill Chain | 2025 | SL 4B, SL 4L |
| AI’s New Frontier in War Planning | 2025 | SL 4B, SL 4H |
| Project Convergence: Revolutionizing Targeting in LSCO | 2025 | SL 4B, SL 4A, SL 4G |
| Enhancing Tactical Level Targeting With AI | 2024 | SL 4B, SL 4H, SL 4M |
| The Future of Strategic Fires Target Acquisition | 2024 | SL 4B, SL 4A |
| The Combat Aviation Brigade and Digital Call for Fire | 2024 | SL 4B, SL 4C |
NCO JOURNAL — Army University Press (3)
| Title | Date | Tracks |
|---|---|---|
| Knowledge Management and The Old Guard | Aug 2025 | SL 4K, SL 4F |
| From Data to Wisdom | Feb 2025 | All |
| Artificial Intelligence and Future Warfare | Sep 2025 | SL 4H, SL 4M, All |
ARMY SUSTAINMENT — Army Logistics University (4)
| Title | Date | Tracks |
|---|---|---|
| Army Sustainment Enterprise’s Delayed Approach to Data Modernization | Winter 2025 | SL 4D, SL 4K |
| Predictive Logistics: Reimagining Sustainment on the 2040 Battlefield | Winter 2025 | SL 4D, SL 4H, SL 4M, SL 4G |
| Enabling Logistics in Contested Environments | Spring 2025 | SL 4D, SL 4G |
| Advancing to Data-Driven Logistics Operations | 2024 | SL 4D, SL 4K |
ARMY AL&T MAGAZINE (7)
| Title | Date | Tracks |
|---|---|---|
| Accelerating the Army’s AI Strategy | 2024-25 | SL 4H, SL 4J, All |
| Commoditizing AI/ML Models | 2024-25 | SL 4H, SL 4M, SL 4L |
| The Army’s Data (Ad)Vantage | 2024 | All |
| The Software Advantage | 2024-25 | SL 4L, SL 4J |
| Army Intelligence | 2025 | SL 4A, SL 4H |
| Emerging Technology and Modernizing the Army | 2024-25 | All |
| Reality Check (AI/ML implementation) | 2024-25 | SL 4H, SL 4M, SL 4J |
ARMY COMMUNICATOR — Cyber CoE (3)
| Title | Date | Tracks |
|---|---|---|
| Leading in Data Centricity, C2 Fix Best Practices | Spring 2025 | SL 4E, SL 4F, SL 4L |
| Army Communicator Spring 2024 | Spring 2024 | SL 4E, SL 4L |
| Army Communicator January 2024 — ITN Suite | Jan 2024 | SL 4E, SL 4C |
FROM THE GREEN NOTEBOOK (3)
| Title | Date | Tracks |
|---|---|---|
| How To Be a Data Literate Leader — And Why It Matters | Mar 2024 | All, SL 4K |
| Harnessing the Power of Knowledge Management | Apr 2024 | SL 4K, SL 4F |
| Understanding Weapons of Math Destruction | Jul 2024 | SL 4G, SL 4H, SL 4M |
INFANTRY MAGAZINE — Maneuver CoE (1)
| Title | Date | Tracks |
|---|---|---|
| Moneyball for Gunnery — 1/4 ID BCT data analytics | 2024 | SL 4C, SL 4G |
SMALL WARS JOURNAL (4)
| Title | Date | Tracks |
|---|---|---|
| Data as Firepower: Data Superiority as a Warfighting Concept | Aug 2025 | All |
| Elevating Information: Why the Army Should Establish Information as a Core WfF | Apr 2025 | SL 4A, SL 4F, SL 4K |
| Accelerating Decision-Making: Integrating AI into the Modern Wargame | Feb 2026 | SL 4G, SL 4H, SL 4F |
| AI-Enabled Wargaming at CGSC | Jan 2026 | SL 4G, SL 4H, SL 4F |
WAR ON THE ROCKS (1)
| Title | Date | Tracks |
|---|---|---|
| The U.S. Army, AI, and Mission Command | Mar 2025 | SL 4F, SL 4H |
MODERN WAR INSTITUTE — West Point (1)
| Title | Date | Tracks |
|---|---|---|
| Leadership, Lethality, and Data Literacy | 2024 | All |
CALL — Center for Army Lessons Learned (1)
| Title | Date | Tracks |
|---|---|---|
| FY24 MCTP Key Observations | Feb 2025 | All |
CDA Slide Decks — Conceptual Prereqs
SL 1 — Orientation (2 decks — click to expand)
SL 2 — Intro To Data (10 decks — click to expand)
SL 2 / SL 3 — Data 101 (4 decks — click to expand)
SL 3 — Advanced (8 decks — click to expand)
SL 3 / SL 4 — Data 201 (6 decks — click to expand)
SL 4 — Specialist Track Decks (4 decks — click to expand)
SL 5 — Advanced Track Decks (6 decks — click to expand)
Program & Briefing Decks (3 decks — click to expand)
http://<host>:<port>. Contact your ODT representative for the current host address.