DASH 2 MEF AMA Briefing.pdf

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Decision Advantage Sprint for Human-machine-teaming

DASH 2 – Match Effectors (MEF) Information Briefing and “Ask Me Anything”

Advanced Battle Management System Cross-Functional Team

711th Human Performance Wing

805th Combat Training Squadron

This briefing is

UNCLASSIFIED

Department of the Air Force

UNCLASSIFIED

◼ DASH 2 Basics

◼ Milestones and Schedule

◼ Location

◼ Deliverables and Desired Outcomes

◼ Transformational Model for Decision Advantage Introduction

◼ Ask Me Anything

Topics

UNCLASSIFIED

30 mins

45 mins

45 mins

DASH 2 Basics

Enriching C2 Decision Advantage Software Requirements

◼ Problem: Our C2 systems will not deliver decision advantage. All decision-making is still left to the humans without any help from the machines

◼ 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/enrich functional and technical requirements for implementing decision advantage via microservices

◼ Develop or improve microservice human-machine interfaces

◼ Produce prototype/MVP-like microservices

◼ Validate TM decision function decomposition for microservice development

◼ Week 1: TM deep dive, battle management scenario, software coding, operator feedback, software smoke tests

◼ Week 2: Software smoke tests, more software coding, final battle management scenario

◼ Post-event: Push DASH insights to C2 requirement developers for software acquisitions

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

UNCLASSIFIED

"...the C2 enterprise generates resilient decision advantage…by exploiting advances in digital engineering and human-machine teaming through the

Transformational Model for Decision

Advantage."

DASH 2 Milestones and Draft Schedule

◼ 30 May: AMA

◼ 13 June: RFP abstracts due; DTS cross-org information pushed to participating warfighters

◼ 27 June: Government invites selected software development teams

◼ 3 July: Software development team RSVPs due

◼ 11 July: Deep dive briefing with selected teams

◼ 20 July – 1 August: DASH 2 event

You are here

UNCLASSIFIED

20 Jul PDT 21 Jul 22 Jul 23 Jul 24 Jul 25 Jul 26/27 Jul PDT 28 Jul 29 Jul 30 Jul 31 Jul 1 Aug

0800 Check In 0800

0830 0830

0900 0900

0930 0930

1000 1000 Break/Software Config Change Break/Software Config Change

1030 1030

1100 1100

1130 1130

1200 1200

1230 1230 Software Config Change

1300 1300

1330 1330

1400 1400 Break

1430 1430

1500 1500

1530 1530 Break

1600 1600

1630 1630

1700 EOD EOD EOD Week 1 Wrap-Up 1700 EOD EOD

Tr av el D ay

DASH Brief

PAE Deep Dive

Lunch

PAE Deep Dive

Sim Execute Final Sim (1030-1130)

Sim Setup & Practice

Final Sim

Final Sim

Tr av el D ay

W ee ke nd

T im e O ff

Post-Sim Q&A

Sim Setup & Practice

Sim Setup & Practice

Final Sim (0900-1000)

Lunch/Outbrief Prep

Final Sim (1300-1400)

Outbrief (1430-1515)

Lunch/Outbrief Prep

Outbrief (1530-1615)

Outbrief (1230-1315)

Outbrief (1330-1415)

Outbrief (1430-1515)

DASH Wrap Up

Si m

R eh ea rs al (B

M T a nd W hi te

Fo rc e)

M

AC

E Tr ai ni ng (W hi te

Fo rc e)

So ft w ar e D ev

Vendor Prog Check

Se tu p

In iti al

So ft w ar e D ev

Working Lunch - PAE Seminar and

Software Dev Feedback

So ft w ar e D ev

C ol la bo ra tio n

Working Lunch - PAE Seminar and

Software Dev Feedback

So ft w ar e D ev

C ol la bo ra tio n

Working Lunch - PAE Seminar and

Software Dev Feedback

So ft w ar e D ev

C ol la bo ra tio n

So ft w ar e D ev

C ol la bo ra tio n

Working Lunch - PAE Seminar and

Software Dev Feedback

Working Lunch - PAE Seminar and Software

Dev Feedback

So ft w ar e D ev

C ol la bo ra tio n

Debrief

Vendor Prog Check

Debrief Vendor Prog Check

Debrief

Vendor Prog Check

Debrief

Vendor Prog Check

Debrief

Vendor Prog Check

Debrief

Vendor Prog Check

Debrief

Location: Howard Hughes Operations Center (H2O) 3773 Howard Hughes Parkway Suite 300, Las Vegas, NV 89169

H2O

N

◼ Logistics

◼ No visit access request req’d

◼ Names of participants needed

◼ Ample lodging, food, parking

◼ H2O Facility

◼ Unclassified environment

◼ Commercial Wi-Fi available

◼ No classified discussions

◼ H2O Software Dev Environment

◼ Hardware will be for scenario and software testing only

◼ Exploring routes of software transfer (External hard drive/GitHub)

◼ Expect further details after participation selection

Deliverables and Outcomes

◼ Proposal/abstracts (not to exceed 5 pages)

◼ Reflect an understanding of the MEF decision function

◼ Describe proposed microservice solution

◼ Address coverage of requirements as described by the MEF function

◼ Unclassified military use case/vignette demonstrating decision function understanding

◼ DASH

◼ Produce a prototype MEF microservice that outputs a stream of effects (BattleEffects) that map a change state onto an entity and includes applicable operational limits (e.g., rules of engagement) and the time window associated with the state change

◼ Demonstrate microservice performance when used by humans in a battle management scenario

◼ Furnish software performance and technical integration insights for government consumption

◼ Number of decision opportunities recognized/missed; decision speed; decision accuracy; human confidence in decision

Deliverables and Outcomes

◼ The MEF DASH aims to answer the following core questions:

◼ How many decision opportunities are recognized/missed?

◼ How fast can the HMT make its decision?

◼ How accurate or error free are the HMT’s decisions?

◼ How confident is the human operator in the HMT’s solution?

◼ What are some technical software attributes/requirements that must be considered along with the functional requirements?

◼ Reporting and presentations must include the following results:

◼ Number of tasks responded to (per Link 16 Track, Chat, and Speech-to-text)

◼ Response time per task (sec)

◼ Effector ranking per task

◼ Number of valid responses

◼ Number of invalid responses

◼ Summary of what was accomplished, issues, lessons learned

Additional Information

◼ COST PROPOSAL.

◼ The offeror shall submit the information outlined below, together with supporting breakdowns. All direct costs

(travel) should be provided by contractor fiscal year (CFY).

◼ a) Travel: Travel costs must be justified and related to the needs of the project. Identify the method of travel, number of travelers, airfare, per diem, lodging, etc.

◼ b) CLIN Structure:

◼ CLIN 0001 Travel Firm Fixed Price (not-to-exceed value of $10,000 per team)

◼ CLIN 0002 Data Not Separately Priced

◼ The submitted documentation and content thereof becomes the property of the U.S. Government and will not be returned. It does not commit the Government to reply to information received.

◼ PROPRIETARY INFORMATION.

◼ This notice is part of Government market research. Information received from this request will be considered as sensitive and will be protected as such. Any company or industry proprietary information contained in responses should be clearly marked by paragraph, so that publicly releasable and proprietary information are clearly distinguished. Any proprietary information received in response to this request will be properly protected from unauthorized disclosure. The Government will not use proprietary information submitted from any one source to establish the capability and requirements for any future acquisition, so as to inadvertently restrict competition.

Transformational Model for Decision Advantage

Introduction (see file: Transformational Model for Decision Advantage working slides v01c cao 20250331 for DASH MEF AMA v5 pdf)

Ask Me Anything