multi-dimensional clustering analysis ex: cluster on information location(a/c)...

Multi-dimensional Clustering AnalysisEx: Cluster on Information

Location(A/C)

Conduct_DCA_Intercept_&_Escort

Issue_Level_1_Query

Clear_Aircraft_Departing_CV

ID(Track)

Range(Track,USN_Ship)IFF(A/C)

Engagement_solution

Engagement_order

IFF(Track)

Location(Track)

Review_ID_Indicators

Respond_to Air_ThreatConduct_Threat_Assessment

Issue_DMZ_Violation_ReportControl DCA

Conduct_Threat_ Assessment

Conduct_Engagement _with_Birds

Control_ DCA

Review_ID_ Indicators

Location(A/C) 0 0 1 0Location(Track) 1 1 1 1Range(Track,USN_ships) 1 1 0 0Engagement_solution 1 1 0 0Engagement_order 0 1 0 0IFF(A/C) 0 0 1 0IFF(Track) 0 0 0 1ID(Track) 1 0 0 1

Conduct_Engagement_with_Birds

Info

rmat

ion

feat

ures

• Goal: Maximize information within watchstanders; minimize info overlap when unnecessary• Conduct_DCA & Control_DCA use similar info; Review_ID & Conduct_engage-ment do not.

InfoTask

Phase D: Engineering Team Interactions

Uniquely assign tasks when possible to minimize routine communications between team members

May need to split tasks if individuals are overloaded

Detailed Modeling Tool:

Note: Splitting tasks introduces new communication workload

Information Variables

Decision Variables

Action Variables

Outcome Variables

Initiate/Confirm Engage Order

Engage_with_Birds

In-boundmissile msg

ROE

Track’s failure torespond to Level II Warning

Track’s failure torespond to Illumination

System Status

Track Verbal Report

Engagement Status

Weapons Away (Y/N?)

Engagement OrderKill Evaluation (Y/N?)

‘Initiate/ConfirmEngagement’Msg

‘Produce EngagementSolution’Msg

‘Weapons Ring’Msg

‘Issue Track Report’Msg

‘Kill Evaluation’Msg

Release Missiles

Track’s visualdisplay profile Track is covered (Y/N?)

System’s movingtwds releasing Weapons (Y/N?)

Firing Solutionstill a go (Y/N?)

In-boundMissile (Y/N?)

Track’s meetingROE (Y/N?)

Track’s approachingits weapons range (Y/N?)

Initiate Engage Orders (Y/N?)

Engagement Solution

WeaponsAway Yes

Kill Yes

Track is covered

System’s movingtwds releasing Weapons

Firing Solutionstill a go Yes

Engage OrdersInitiated

Firing Solutionno longer a go

System’s failed inmovingtwds releasingWeapons

Engage OrdersNOT Initiated

Track is NOT covered

WeaponsAway No

OUTCOME Variables

DECISION Variables

INFORMATION Variables

ACTION Variables

OUTCOME Variables

DECISION VariablesINFORMATION Variables

ACTION Variables

Respond_to_air_threat

Evaluate_threat

Intra- and inter-task analyses suggest opportunities to combine tasks into roles

3

2

Intra- and Inter-Task Analysis

Example Objective: Balancing Workload in the Team

Instant Workload

0

Threshold

)()(max0;

maxargmax tWtW iDMiDM

ttAEGISiDMMMWSiDM

Objective 1:

min)(

)(

max

max

0

0

minarg

maxarg

tt

iDM

tt

iDM

tW

tW

MMWSiDM

MMWSiDM

Workload AccumulationBalance

DM1 DM2 DM3 DM4 DM5

1 101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

Team Leader

101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

Air Coordinator-

101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

Watchdog

101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

Information Coordinator

101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

Battle Manager

Notional Workload Analysis

Outline of Presentation

Value of modeling C2 Organizations– Prescriptive vs. descriptive modeling– Model-Based Experimentation

TIDE modeling approach

C2 Design Example: AWACS

How to use TIDE products

AWACS Design Challenge

TIDE Design Approach Mission analysis

What needs to be done What information is available

Task analysis How is it done What information is used

Organizational analysis How is information shared Who does what

How do you design an optimal command & control teams for complex, variable AWACS missions to take advantage of advanced information fusion technology?

Example: AWACS Crew Optimization

Human-Centered Re-Engineering of AWACS Command and Control Teams (REAC2T)– Phase III SBIR Project funded by AWACS System Program

Office ESC, Hanscom AFB

Demonstrate proven, scientific approach to C2 team design in AWACS domain– Team Integrated Design Environment (TIDE)

Present ACC/Wing with proof-of-concept for crew optimization– Evaluate impact of information fusion on mission performance

and operator functions– Introduce optimized team structures to enhance mission

performance

AWACS Example: Inputs to Mission Model

Mission decomposition and evaluation– Work with operational community to define current approach to

mission completion• CONOPS, tactics, roles, and responsibilities

Red Flag Spin-Up Training– Tinker AFB

Live Fly Red Flag Exercises– Five flights, Nellis AFB

Cognitive Task Analysis– Wing Tactics Office, Tinker AFB– SD instructors Fighter Weapons School, Nellis AFB

TIDE Prototype Software

Mission & task graphs are converted into data tables to serve as input for optimization algorithms

Preliminary Results: Baseline 14 Operator Task Distribution

Colors represent unique operational tasks

Max Workload = 1400

Impact of Technology (MSI) Insertion:Non-Optimized 14 Operator Configuration


Max Workload = 950

Impact of Technology (MSI) Insertion:Optimized 14 Operator Configuration


Max Workload = 750

Impact of Technology (MSI) Insertion:Optimized 12 Operator Configuration


Max Workload = 800

Internal Communication: Outgoing Messages

MSS W1S W2 W3 W4 W5 W6 S1S S2 S3 S4 S5 0

20

40

60

80

100

120

140

DMs

Out

goin

g M

essa

ges

MCC SD STK OCA Chk_In HVAA STK_Ast OCA_Ast ASO ECO AAST AST_1 AST_2 AST_3 0

20

40

60

80

100

120

DMs

Out

goin

g M

essa

ges

Baseline


50

100

150

200

250

300

350

400

450

500

DMs

Out

goin

g M

essa

ges

MSI Non-Optimized 14

MSI Optimized 14 MSI Optimized 12


20

40

60

80

100

120

140

160

DMs

Out

goin

g M

essa

ges1. Technology1. Technology

InsertionInsertion

500 160

3. Manning 3. Manning OptimizationOptimization

2. Optim

al

2. Optim

al

TeamTeam

Summary: Model-based Re-Engineering of AWACS Command & Control Teams (REAC2T)

T91 -Recordkeep - Significant

events

T76 - Provide C2for workaroundsto appropriate

players

T75 - Coordinatewith senior C2

elements

T74 - Define/recommend

missionmodifications

T71 - Define whatis needed to

continue/complete mission

T62 - Send anarrow

T60 - Broadcastnew information

T57 - Requestsupport fromsupervisorT47 - Distribute

mission status

T46 - Providevector information(i.e. refueling, flight

join, airspace)

T43 - Respond torequests for

information (RFI)

T42 - Makepicture calls

T26 - Identify airthreats

T24 - Provide allavailable amplifyinginformation (tracks)

T20 - Utilizeorganic radar

data

T19 - Fuse datafrom multiple

sources to locateobjects (detect)

T7 - Reconfigureradar for

changing missionobjectives

T102 - Receiveinformation from

pilots

T45 - Monitorairborne assets

missionreadiness

T48 - Assessfighter fuel level

T103 - Pullinformation from

pilots

ANDOR

AND

OR

AND

AND

OR

AND

A17 - Fuse data frommultiple sources toensure tracks are

correct

A12 - Detectnew track

D28 - Determinewhere you shouldanticipate a threat

D16 - Decidewhat is a valid

air object (track)

I17 -Intelligence

dataI4 - ATO

I64 - RadarData

I65 - IFFData

I66 - ESMData

I67 - OtherSensor

A2 - InitiateTrack

SymbologySwitch Action

AND

O39 - Tracksymbology

I56 - Trackposition

Re-engineering based on AWACS mission task models Scientific C2 team design approach to AWACS domain: TIDE

-Team Integrated Design Environment Org. design for new technology insertion and optimized manning

0

2

4

6

8

10

12

Baseline New Tech Only

New Tech + Optimized 1

New Tech + Optimized 2

Crew Configuration

Ave

rag

e T

ask

Del

ay

(se

co

nd

s)

Task Model

Faster Teams

Outline of Presentation

Value of modeling C2 Organizations– Prescriptive vs. descriptive modeling– Model-Based Experimentation

TIDE modeling approach

C2 Design Example

How to use TIDE products

TIDE Model Products

Mapping of Tasks to Team Members

Task Cluster Output

DM1 DM2 DM3 DM4 DM5

Configure_Watchstation 1 1 1 1 1

Plan/Configure_for_Air_Defense_Mission 1 1 1 1 1

Review_Systems_Status 1 1 1 1 1

Issue_Level_1_Query 0 0 1 0 0

Respond_to_Air_Threat 1 0 1 1 0

Conduct_Engagement_with_Birds 1 0 0 1 0

Review_ID_Indicators 3 1 2 2 4

Issue_Update_Track_Verbal_Report 0 0 0 1 0

Conduct_DCA_Intercept_&_Escort 1 0 0 1 1

Issue_DMZ_Violation_Report 2 1 1 1 1

Clear_Aircraft_Departing_CV 0 0 0 0 1

Team Descriptions

4.0

4.1

4.2.1 4.2.2

4.3

CAS (8)

CV (1)

TARP (1)

Rifle Co (3)

Stinger (1)

4.2

Cobra (2)

Rifle Co (3)

Cobra (2)

Stinger (1)

Eng . (1)

MED (1)

MCM (1)

CG(1), DDG(2)

Eng . (1)

MED (1)

MCM (1)

VF(8), FFG(2)

Performance Predictions

1 101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

Team Leader

101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

AIC-REDCROWN

101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

Watchdog

101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

Information Coordinator

101 201 301 401 501 601 701 801 901 1001 1101 1201 1301 1401 1501 1601

Battle Manager

Detailed Specification of Team Roles:

When Tasks are performed

How Decision are made

What Resources are used

What Information is used

What Communications are required

Multiple Applications of TIDE Model

EVENTS

TEAM LEADER'S WORKSTATION

MULTI-CHANNEL COMMUNICATION LINK

"WORLD" EVENTS

Synthetic Task Environments

TIDE Organizational Design Process

Phase A:Mission

RepresentationPhase B:

Task-ResourceMapping

Phase E:Organizational

Structuring

Phase C:Clustering Tasks

into Roles

Event-Task Mapping

Optimized TaskScheduling

Operator Role Definition/Info Requirements

Team-LevelAssignments

Team Design(Structures

+ Processes)

Design Objectives,

Criteria,Constraints

Design Objectives,

Criteria,Constraints

Phase D:Decompositionof Role Overlap

Organizational Design

Intelligent Agents

Training Programs

Tide Input Model

IDAO Decomposition

A31 - Target thethreat

D4 - Decidehow to use

available airand groundresources

O14 - Commit pairfighters

I49 - Fighterweapons

status

I19 - Missionrequirementsand priorities

I41 - Fighterfuel status

I51 - Threat/target

location

ANDI17 -

Intelligencedata

A22 - Monitor theair picture

IDAO Decomposition

Event-Task Mapping

Time on Target (ToT)

T36 - Maintainaccurate track /

symbologycorrelation

T19 - Fuse datafrom multiple

sources to locateobjects (detect)

T22 - Interpret /Filter information

T20 - Utilizeorganic radar data

T95 - Monitorairspace

T42 - Make picturecalls

T86 - Providetarget location

T43 - Respond torequests for

information (RFI)

T24 - Provide allavailable amplifyinginformation (tracks)

OR

T102 - Receiveinformation from

pilots

T56 - Receivemission effectiveness

/ BDA

T47 - Distributemission status

AND

Event-Task Mapping

Task Decomposition

ID/track air objects

Respond to threats

Record keeping

ASK FOR INPUTto ATSO (self-preservation)

Identify Threat type

Identify ThreatLocations

Direct weaponsto target/threat

Analyze system resourcesto locate jammers whileMonitoring system for jamming

Execute electronic countermeasures while Monitoringsystem for jamming

Broadcast jammer locationwhile Monitoring systemfor jamming

TCTC Mission

Define Threats

Decide to engage or not

Operate MCS systems

Surveillance/detectair objects

Create/maintain recognizable& integrated air picturePass/receive information

Manage ATO execution

ATSO (self preservation)Airborne (C2 of airborne assets)

Respond to Threats Respond to pop-up targets

Monitor system for jamming


Respond to threats

Record keeping








TCTC Mission

Define Threats


Operate MCS systems







Mission Decomposition


Respond to threats

Record keeping








TCTC Mission

Define Threats


Operate MCS systems








Respond to threats

Record keeping








TCTC Mission

Define Threats


Operate MCS systems







0 200 400 600 800 1000

Line1

T18T68T28 T20 T66 T70 T67 T69 T71 T28 T83 T83 T83

Line2

T18T18T28 T20 T37 T67 T69 T71 T95 T44 T71 T83

Line3

T18T20 T20 T67 T69 T71 T83

Line4

T18T18T18T18T20 T66 T69 T71 T44 T98 T70

Line5

T28T18T20 T20 T90 T67

Line6

T28 T20 T20 T92 T28 T83 T1

Line7

T28T18T20 T92 T28 T9 T83 T44 T83 T87

Line8

T18T18T18T20 T20 T65 T64 T69

Line9

T4T18 T66 T77 T70 T81 T69

Line10

T28 T20 T97 T83 T83 T83

Line11

T18T18 T16 T9 T83

Line12

T18T18 T16 T27

Line13

T18T28 T20 T2 T83

Line14

T20 T20 T37

Line15

T18T18 T20

Line16

T18T18 T20

Line17

T18T18 T20

Line18

T28 T20

Line19

T89

Line20

T20 T20

Line21

T16

Line22

T20 T20

Line23

T20

Time

C2 Process Re-engineering

Interface Design

Model-driven Measurement ProcessModel-driven Measurement Process

Learning Objectivesin JTF Environment

Competencies:Knowledge, Skills,and Abilities

Tasks

Scenario

Stimulated or Trained by...

Improve by X%

Put together into vignettes...

IndividualTeam

Team-of-Teams

Theories ofPerformance LinkSkills to Behaviors toTasks

Stories andevents

MOPs &Measurement

Tools

MeasurementChallenges

Performance Measures by TaskHow well did learners perform?

KSA AssessmentWhat KSAs do learners have/lack?Diagnose individuals’ needs for additional training

Success in Meeting Training ObjectivesHow well are training objectives met?Success at JTF; Certification

Subject Matter Experts

TIDE Model

TIDE Integrated Toolset

Task Network SimulationOrganizational Structure

Task Hierarchy

Assess platformneeded

Receiveplatform

status

Assess need torequest

Task

Platform, DM Platform

Task, Platform

Task, Platform

Task, Platform, DM

Decision-Maker Model

DESIGN

SIMULATION-BASEDEVALUATION

ANALYSIS

Team Optimal Design

(TOD)(TOD)T

DMR

User/SME input and review

MissionAnalysis

S u b 3

S u b 1 S u b 2

L ead

Sub 2 Sub 3

Sub 1

Leader

Computational Organization Model

50 10060 70 80 90

85.1

79.7

76.2Mis

sio

n O

utc

om

e

Some Current Military Applications of the TIDE Modeling Methods and Tools

Joint Task Force Adaptive Architectures for Command and Control (A2C2)Next Generation Navy Surface Ships (SC-21/DD-21)Human-Centered Re-Engineering of AWACS Command and Control Teams (REAC2T)Uninhabited Combat Air Vehicle (UCAV) Control CenterKwajalein Radar/Missile Control Center (ATIDS)Air Operations for Time Critical Targets (JFACC)Time Critical Targeting Cell in Air operations (CAOC)Effects-Based Operations in Operations Center (EBO)Army Future Combat Systems (FCS)Global Wargame JTF Org. Design and Assessment….

Summary: Why Model C2?

TIDE is a method to optimize decision-making organizations to capitalize on advanced technology

Model-based organizational structures are “congruent” with mission needs

Modeling guides experimentation and performance assessment

Analysis and design tool for system designers– Cost and risk reduction

– New technology payoffs

Mission/organization model serves multiple purposes – Organizational design: Provide alternative, optimized organizations

– Team training: Highlight areas for team training

– Synthetic tasks: Develop environments to train and evaluate teams

– Interface design: Functional definition of GUI

multi-dimensional clustering analysis ex: cluster on information location(a/c)...

Documents

c2 team design

donewhat information

balancing workload

operator configurationcolors

information goal

awacs crew optimizationhuman

dca control

operational community