M-DASH Pre_submission AMA Briefing_15 Oct.pdf

Edit distribution statement in the slide master

MUTLI-DECISION ADVANTAGE SPRINT FOR

HUMAN-MACHINE-TEAMING

(M-DASH)

“ASK ME ANYTHING”

A F R L

A B M S C F T

8 0 5 T H C T S

Unclassified

Edit distribution statement in the slide master 2

M-DASH Intro

PM/Contracting Comments

Roll Call:

• AFRL

• 711th HPW/RR

• Contracting

• ABMS CFT

• 805th CTS (ShOC)

Important Dates:

• 15 Oct: Pre-submission AMA

• 21 Oct @ 1700 EDT: Submissions due

• ~04 Nov (approx.): selection notifications

• 25 Jan – 05 Feb: M-DASH event

You are here

Unclassified

Unclassified

• Once submitted, please ensure you receive a confirmation receipt email. If you do not, please reach out.

• Will add the AMA slides & an updated Q&A excel spreadsheet of any questions from the AMA session to

SAM.gov.

• If you already submitted a proposal, you will be able to amend and resubmit after this AMA up until the proposal deadline.

• Proposal received after the deadline will not be considered or evaluated.

Edit distribution statement in the slide master 3

M-DASH Overview

• Problem: Our C2 systems focus on information advantage. All decision-making is still left to humans

• Collaboration between AFRL, ABMS CFT, and 805 CTS

• Battle management warfighters and software developers collaborate over two-weeks to:

• Use the Transformational Model (TM) to define, derive, and enrich software requirements for decision advantage

• Produce prototype/MVP-like services

• Validate TM decision function decomposition for service development for PAE, MEF, and GBC

• Week 1: TM deep dive, baseline battle management scenario, software coding, warfighter feedback

• Week 2: Progress check, more software coding, HMT battle management scenarios

TM-framed DASH events will help us build machine teammates that arm our C2 enterprise with decision advantage capabilities.

Unclassified

Unclassified

BattleCOA Ensemble Multi-DASH (M-DASH) = Perceive Actionable Entity (PAE), Match Effectors (MEF), and Generate BattleCOAs (GBC)

Edit distribution statement in the slide master 4

M-DASH Deliverables

• Demonstrated Functional Relevance

• Contribute to the overarching goal of enabling the human operator to make better, faster decisions

• Software outputs

• Provide outputs to the Government Software System API (for PAE, MEF, and GBC) using

Government provided data schema.

• Traceability logs

• Government Outbriefing

• Presentation (PowerPoint format) covering event overview, tech approach, relevant findings, metrics, feedback

• Technology Survey

• May include, but not be limited to: AI models utilized, model licensing, model card information, hardware and runtime requirements, power consumption estimates, etc.

Edit distribution statement in the slide master 5

Software Dev Environment

• Unclassified – no classified materials or discussions

• Individual development space

• On-site hardware will be for scenario/ operator use

• BYOH for development and hosting

• Ability to access web-based services

Networking

• Commercial Wi-Fi available

• Local network for data connections

Unclassified

Unclassified

M-DASH Facilities

Example Information Sources

• Data (REST, SSE, etc.)

• IRC Server

• Text docs

Edit distribution statement in the slide master 6Edit distribution statement in the slide master

Academics