Transcript Output Tools Demo

C2 Modeling in JWARS
Lt Col Greg McIntyre
1
Agenda
 JWARS Background
 C4ISR Overview
 C2 Implementation
» JTF
» Air Component
» Land Component
» Maritime Component
» Logistics
» TBM
 Summary
2
Mission
Mission: Develop a state-of-the-art, constructive simulation that will:
 Provide a multi-sided and balanced representation of joint theater warfare
 Be able to assess current and future operational concepts to include Joint
Vision 2010’s:
» Dominant Maneuver, Precision Engagement, Focused Logistics, and Full-
Dimension Protection
 Use C4 and ISR as the foundation for how entities perceive and interact
with one another
Users
• Joint Staff
• Services
• CINCs
• OSD
• Joint Task Forces
• Other DoD org's
• Industry
Applications
1. Force assessment
2. Planning and execution
– Deliberate planning
– Crisis action planning
3. System effectiveness and trade off analysis
4. Concept and doctrine development and
assessment
Requirements - Warfare Functionality
(slide 1 of 2)
 Release 1 (Limited IOC)
» Include C4, ISR, logistics, and essential functionality in legacy simulations
TACWAR and MIDAS.
» Be capable of replacing TACWAR for force assessment application.
 Release 2 (Full IOC)
» Provide balanced warfare representation, including C4, ISR, logistics.
» Be capable of supporting the applications-1. Force assessment.
2. Planning and execution.
» Be capable of replacing TACWAR and MIDAS.
 Release 3 (FOC)
» Provide balanced warfare representation, including C4, ISR, logistics.
» Be capable of supporting the applications-1. Force assessment.
2. Planning and execution.
3. System effectiveness and trade-off analysis.
4. Concept and doctrine development and assessment.
» Be capable of replacing legacy simulations CEM, Thunder, ITEM, and
SUMMITS.
Requirements - Warfare Functionality
(slide 2 of 2)
JWARS
- Destruction of strategic / theater deployment assets
- Disruption of strategic / theater deployment network
Resupply requirements
Strategic
Logistics
Resupply requirements
Theater
Logistics
(Strategic movement of units (Within theater movement of
and supplies from POE to
units and supplies)
POD)
- Intended to replace
- Intended to replace MIDAS
SUMMITS simulation
simulation
Perception
Joint
Warfighting
(Combat, maneuver, C3)
- Intended to replace
TACWAR, CEM, Thunder,
and ITEM simulations
Release 1 Warfare Functionality
Summary
Limited IOC Functionality
C4ISR
Communications
Intelligence
Sensing
Reconnaissance
Perceived Truth
Indications & Warning
JTF Command and Control
Collection Plan
Release 1.3
Implemented
Functional; work
continues
Land
Maneuver
Direct Fire
Limited IOC Functionality
Maritime
Surface to Surface
Sub on Ship
Naval Blockade
ASW (Sub on Sub)
MW (Mine Deployment)
NSFS
Forcible Entry (Amphib)
C2
ASW (Ship on Sub)
ASW (Air on Sub)
Implemented
Indirect Fire
Forcible Entry (Airborne)
Maneuver Planning
Attack Helos
C2
Resupply
Implemented
Functional; work
continues
In Development
Functional; work
continues
In Development
Implemented
Functional; work
continues
In Development
Chem Offense
Chem Defense (MOPP)
Implemented
Unit Effects (Land)
Partially
Implemented
Unit Effects (Air)
Unit Effects (Installations)
In Development
Data Entry / Retrieval
Import/Export to Oracle Database
Add/Modify Orders
Data Modification
Data Dictionary (On-Line View)
Comparison of Scenario Data
Export Data (Instruments)
Limited IOC Functionality
Air
Operational C2
CAS C2 & Execution
Cruise Missiles
Dyanamic ATO Planning
Counter Air (A2A)
Attack / Interdiction (A2G)
Air Defense (S2A)
Air Base Ops
JTCB Planning
Air to Surface (ship)
SEAD
Release 1.3
Implemented
Functional; work
continues
In Development
TBM / TBMD
Combatant Logistics Force
WMD
Transportation and Logistics
Intertheater Lift Scheduling
Intertheater Lift Reschedule
Intertheater Lift Movement
Intratheater Lift
Intratheater Lift Reschedule
Intratheater Transportation
Installations
Sustainment
Release 1.3
Threat Missile
ABL
DSP Cueing
BMC3
HE Effects
Lower Tier (Patriot)
Lower Tier (AEGIS))
Upper Tier (THAAD)
Upper Tier (AEGIS)
Implemented
Functional; work
continues
Environmental Effects
Capable
Terrain
Networks (Land)
Weather
Ocenographics
Notes: - Functional areas displayed are Release 1 (Limited IOC) requirements.
- By Release 1.4, all areas will be Implemented.
Implemented
Mostly
Implemented
Guidelines for Model Development
UK/NATO Code of Best Practice in C2 Assessment
Models must represent
 Information as a commodity
 Realistic flow of information around the battlespace
 Collection of information from multiple sources and
tasking of collection assets
 Processing of information
 Represent C2 [C4ISR] systems as entities on the
battlespace
 Unit perceptions built, updated, and validated from
information available through its information systems
 Commander’s decision based on the unit’s perception
of the battlespace
 Information operations
7
Agenda
 JWARS Background
 C4ISR Overview
 C2 Implementation
» JTF
» Air Component
» Land Component
» Maritime Component
» Logistics
» TBM
 Summary
8
Fundamental Warfare Functionality Component -Battle Space Entity (BSE)
 BSE -- a friendly unit, enemy unit, or major system operating in the battle space. Examples:
-

Operational Headquarters
Strategic aircraft and ships
Airbases and seaports
-
Land: Maneuver Battalion
Air: Air Mission Element
Space: Sensor Satellite
Maritime: Ship, Submarine
Represented as a “composite software object.” Top-level decomposition:
Battle Space Entity (BSE)
Owns or
Controls
Command
& Control
“Thinking,”
Planning,
Decision Making
Sensor
Resource
Manager
Accountability of
Resources
Detecting,
recognizing,
identifying
Platform
Communications
Manager
Communicationsbased interface to
other BSEs
BSE
Location,
speed,
direction
9
ISR System Representation
Air
Cobra Ball
Space
F-14 TARPS
JSTARS
Global Hawk
Predator
Guardrail
Rivet Joint
U-2
ISR Sensor categories represented in JWARS:
– Electro-Optical (EO)
Surface
– Infra Red (IR)
– Synthetic Aperture Radar (SAR)
– Moving Target Indicator (MTI)
– Communications Intelligence (COMINT)
– Electronic Intelligence (ELINT)
– Human Intelligence (HUMINT)
– Measurements &Signatures Intelligence (MASINT)
NOTE: In order to represent any possible future, JWARS provides a generic capability to represent any kind of
platform and associate with it any kind of sensor with any intelligence discipline. The fact that such a modeling
capability exists does not imply that any such system exists, is planned, or is even feasible.
10
Logical Structure (Based on C4ISR)
Processing
(Correlation,
Association,
Fusion)
Situation Map
(Perceived Truth)
Decision
(Command and
Control)
Intelligence Preparation
of the Battle Space (User Input)
Collection Plan
(User Input)
Data
Collection
(Sensors)
Database of
Forces, Assets,
etc.
(Ground Truth)
Action
(Movement,
Combat)
All decisions (C2) are based on the current perception fed by the ISR
process over communications networks.
11
Intelligence Preparation of
the Battle Space
 User specified at initialization
 OPFOR information
» Order of Battle (unit strength, garrison location, org type)
» Doctrine (Templates)
 Environmental Information
» Terrain (Go/No Go)
» Day / Night
» Terrain Trafficability
12
Collection Plan
 Intelligence requirements
» Description
» Search Location
» Search Timing (if applicable)
» Processing - Immediate or Periodic Fusion
» Satisfaction Criteria - Absence, presence, strength,
condition, activity, etc.
» Priority
» Intelligence Disciplines (leads to sensor allocation)
» Quality (NIIRS equivalent)
» Report Requirements (when, to whom)
 Platform / Sensor Tasking
13
Data Collection - Asset Counting
Resulting Sensor Report
Search Area
Sensor
Sensor
Field of
View
x
5
Ground Truth
Asset
T-72 Tank
BMP 2
Zil 90 Truck
Total
1
4
3
1
3
1
13
Classification Results
Count
6
6
4
16
1
4
0.8
0.7
0.5
Actual / Perceived
T-72 Tank
BMP 2
Zil 90 Truck
2
Detected
T-72 Tank
BMP 2
Zil 90 Truck
T-72
1
0
0
Tank
3
1
0
IFV
0
3
0
Track
1
0
0
Truck Vehicle
0
0
0
1
3
0
Classification Matrix
3
Detection Probabilities
T-72 Tank
BMP 2
Zil 90 Truck
T-72 Tanks
Tank
IFV
Perceived Track Vehicle
Truck
Vehicle
Total
T-72
.20
.02
.00
Tank
.60
.08
.02
IFV
.10
.84
.03
Track
.05
.04
.05
Truck Vehicle
.03
.02
.02
.04
.85
.05
Total
1.0
1.0
1.0
5
5
3
Probabilities of detection, classification and identification can be affected by target’s
activity, local visibility, countermeasures (future), and local terrain/vegetation (future)
14
Communications
Important messages are simulated explicitly; others are “background” traffic.
144 message types sent explicitly, e.g.:
– Sensor Reports (multiple types)
– Battle Damage Assessments
- Resupply Requests
- Undersea Warfare Orders
Multiple networks with individually defined capabilities.
Each unit can be
on multiple
networks.
Network
performance and
connection
defined in data,
which can be
modified by user.
Delay (sec)
Network load and delay are a function of the network, phase of the war, and time of day.
No constraint on
# of networks,
Demand for
providers, and
Communications
subscribers.
Message Load
3.5Mbs
1Mbs
Initial Communications
Capacity for Network A
3.5Mbs
Major Node On-Line
1.5
2.6
Minor Node On-Line
Existing Infrastructure
Major Node Damaged
Major-Node Arrival
(2Mbs provider for Network A)
Minor-Node Arrival
(0.5Mbs provider for Network A)
1
5
10
15
Day
20
25
30
15
Processing
Bde HQ
Bde HQ
JTF
C2
Comm
Manager
C2
Comm
Mgr
Perception through
remote sensors and
communication of
“sensor” messages
SITMAP
Collection
Flight BSE
Comm
Mgr
C2
C2
Sensor
SITMAP
Units can query
simulated SITMAP
concerning OPFOR
in given area
II
II
II
?
SITMAP maintains status
of installations and
feature (e.g., bridges)
?
Perception through short range
organic sensors and
communication of “in contact”
messages and MISREPs 16
Processing Components
 Correlation
» Determine whether multiple sensor reports refer to a common
entity
 Delay
» Add Processing, Exploitation, and Dissemination (PED) delay
 Association
» Match sensor report (or set of reports merged per correlation)
with a particular perceived entity; if not, create a new
perceived entity
 Fusion
» Update perceived attributes of perceived entity based on all
available information, present and past
 Purge
» Delete mobile entities that are “too old.”
17
Situation Map
 Referred to as the JEF (JWARS Equipment & Forces)
or as the COP (Common Operational Picture)
 Maintained at the JTF-level
 Accessible by any BSE
 Information Variability
» Timeliness
 PED Delay, Age of Information
» Accuracy
 Unit Identification (multiple classification levels)
 Strength Estimate - Mean & Variance
 Geo-Spatial - Location & Velocity (subject to collection error)
» Subject to Negative Information
18
Decisions and Actions
Indication & Warning
Blue JTF Phase 1 (Deter/Deploy)
Maneuver Planning
NAI
16
NAI
14
NAI
NAI
NAI
NAI
12
STATE
S1
S2
S3
S4
STATE NAME
#PREAMBIGUOUS
#AMBIGUOUS
#UNAMBIGUOUS
#SURPRISED
Major Enemy
Movement
Perceived
False
True
True
False
Major Enemy
Movement
Perceived Below
Designated Phase
Line
False
False
True
True
Targeting
Joint Target Coordination
Board (JTCB) assess available
targets and assigns missions
JTF Actions
NAI
10
8
6
NAI
4
NAI
NAI
NAI
NAI
2
0
No action Rqd
I-Day Declared
W-Day Declared
C-Day Declared at
W+24 Hrs
I-Day and W-Day
Declared
C-Day Declared
NAI
NAI
16
14
NAI
NAI
NAI
NAI
12
10
8
6
4
2
0
• Maneuver and Fire Support
decisions are based on relative
density of friendly & enemy
forces
• Opposing force information
derived from perception
• Own force information based
on situation reports
19
Agenda
 JWARS Background
 C4ISR Overview
 C2 Implementation
» JTF
» Air Component
» Land Component
» Maritime Component
» Logistics
» TBM
 Summary
20
Command & Control Considerations
 Operational Structure
» Command and Control Hierarchy
» Orders
 Awareness - situation relative to mission
accomplishment
» Information from its own organic sensors
» Information through communications with other BSEs
» Query the JWARS Equipment and Forces (JEF)
 Commanders
» Decisions - based on available information not ground truth
21
JTF C2
Knowledge Base
Notifications
Component C2
• Air & Space
• Land
• Maritime
JTF C2
Status
Input
Enemy &
Environment
Status
C4ISR (J2)
Decisions
Status
Reports
Current
Phase &
State
Queries
JTF Decisions
• Phase & State
• ROE
• Allocations (future)
Friendly
Current
Phase &
State
Queries
Queries
Sensor
Reports
Environment
Enemy
22
JTF C2 Decisions
 User specifies overall campaign objectives
 JTF C2 decisions made dynamically
» Indications and Warning
» Joint Targeting
» Planning
» Battle Damage Assessment (BDA)
 Satisfies information needs in areas such as
» Air Superiority achieved/not achieved
» SLOC Open/Closed
» Ground Forces in Contact
» Ground Units Off-Plan
23
JTF C2 Decision Events (Criteria)
 Phase and State Rules
 Rules of Engagement (ROE)
 Enemy situation
 Changes in the Arc-Node Network
 General planning guidance
 Changes in the environment (future)
 Changes in political boundaries / coalition
membership* (future)
 Delay in execution of operational plans (e.g.,
amphibious assault with multi-Service support)
24
Collection Plan
 Intelligence gathering based on operational situation
assessment (changes reflected in the Collection Plan)
» Change collection priority
» Reprioritize platform / sensor collection
» Change area collected against
» Execute Component Commander requests for information
 ISR support to the amphibious assault
 ISR support of SEAD
 ISR support of joint targeting, pre-strike target confirmation and
post-strike BDA
25
Collection Plan Prioritization
 Search priorities are set by the JWARS user for:
» Each phase (e.g., pre-hostilities, defense, and counter-offense)
» Assignment of a search area by platform / sensor pair
 NAI, UAI, Cued, MSN, and JEF
» Multiple area deconfliction
 Uses revisit time, priority, and last time searched to
allocate Satellite-EO each period
26
Rule-Based Sensor Report
Preprocessing
Land
Sensor
Report
Mobile
Combatant
Maneuver or
HQ
SP Arty, Mech,
or Tank
Asset Items
Med. Unit
Mech or Tank
# Vehicles
Maneuver
% Tracked
Combat
Tank Bn
% Tracked
% Tanks*
* NOTE: The presence of T-72 tanks might lead to the identification of a specific org type or at least signify an elite unit
27
Air Component C2
 Structure
JTF
JFACC
Air Facilities
 Awareness
» JEF (via queries)
 Target Location
 BDA
» Component Commanders Plan
 JFLCC CAS & Attack Helo
 JFMCC
» Other Plans
 JTF Collection Plan
 Air Defense
Aircraft
28
Air Capable
Units
ALLOREQ
ALLOREQ
Allocation
(linear program)
A/C Type
A/C Type
Air Warfare Planning
Sorties by Launch Block
Launch
Inventory
Mission Category
User Specified
Apportionment
Mission Percentages
Sortie
Demand
JFACC
JTF C2

ATO Cycle
Control
ATO
Creation
Sortie
Supply
Launch Block
User Specified
Airspace
Control Order
Air Routes
Orbit Points
JTCB
Collection
Target Plan
Target/Asset Pairing
User Specified
Joint Air
Operations Plan
Plan
JFLCC
Land Spt Plan
Orbit Points
FSC ID
ATO
Collection Missions
ADP Missions
CAS/HCAS Missions
Target Mission
Air Defense
Plan
29
Integrated Air Planning
High Level View
Intelligence Processes
• Collection Plan
• IPB
• JTF JEF
• Enemy OB
• Electronic OB*
• Air OB**
Air Defense Planning
• Air Defense Plan
• TBMD Plan
Airspace Control Planning
• Create Air Routes
• Create Orbit/AR Points
• No Fly Zones**
SEAD Planning*
• JSEAD SO Plan
• LSEAD SO Plan
• LSEAD Strike Plan
JTCB Target Planning
• Target List
• Weapons List
• Weaponeering
• Route Risk Assessment*
• Packaging*
Maritime Support Planning
• SW Plan
• USW Plan
• Mine Plan
• Countermine Plan
• Assault Plan
Land Support Planning
• HCAS Plan
• CAS Plan
SOF Planning**
ATO Processes
• Allocation LP
• Launch Inventory
• Publish ATO/MTO
• Air Defense Plan
• Collection Plan
• Target Plan
• Land Support Plan
• Maritime Support Plan*
• SEAD Plan*
• SOF Plan**
* = Rel 1.4
** = Beyond Rel 1.4
30
Land Component C2
 Structure - Very hierarchical
 Awareness
» JEF via queries
JTF
» Own ground composite sensor
» From superior/subordinate
JFLCC
units
Corps
Division
Headquarters
Combat Service Support
Brigade
Battalion
Combat BSEs
31
Land Warfare CONOPS Implementation
User Specified
Units
Land
Units
Task Organization
Inventory
(Force Flow)
Order of Battle
Resources
& Assets
TPFDD
Forces in
Theater
User Specified
JTF C2
JTCB
Campaign Plan
Operational
Phase/State
Control
JFLCC
Joint
Target Plan
Target Nominations
Requests
Fire Support
Requests
JFACC
CAS/Helo Requests
Weapon Allocations
FSCL
High Level Orders
ROE/Guidance
Schedules
Allocations
Fire Support
Transport
Supplies
JFMCC
NSFS Plan
Tasks
Dynamic
Orders
Land Maneuver
Fire Support
Dynamic
Responses
Support Requests
Sensor Reports
SITREPs
Tech Parameters
Soft Factors
Routes, etc.
32
Land Commander
Assesses
Situation
Selects COA
Considers METT-T:
• Friendly mission
• Enemy capability
• Friendly capability
• Environment
• Schedule
CM Plays “chess” with a Game
Tree made of Outcomes of Game Boards
Evaluates the
Likelihood of
Success of Plan
Blue
Objective
Red
Objective
A Game Board:
Supply
Rate
Perceived
Strength
85.3
Ensures COA:
Periodically:
• Accomplishes mission • Checks thresholds
• Meets schedule
• Evaluates “off plan”
• Provides best value
• Decides if time to
A Game Tree:
• Offers acceptable risk
replan
Perceived
Strength
37.1
Advanc ing
Supply
Rate
Holding
(Simulation of the
Land Simulation)
(Alt ernative
Game Boards)
The Land Commander performs a Commander’s Wargame
of the likely Courses of Action (a simulation of the simulation)
Perceived Supply
Strength Rate
37.1
Advanc ing Holding
* Includes doctrine,
TTP, local customs,
history, etc. for this unit
Sch
ior’
so
Tro
ops
Ow
n
e (s
upe
r
ord
ObjectiveObjective
Unit-Level
Knowledge
Base*
edu
l
Rear
Area
Time-stepped simulation of the
simulation provides the underlying
parameters for COABlue
selection
Red
SupplyPerceived
Rate Strength
85.3
upe
r
ior’
s
Long range strike
Reserves & supplies
Force movement
Force maneuver
Force Intel capability
Combat
Strength
n (s
Combat
Strength
Mi s
sio
Rear
Area
rde
r s)
(
Ene
sub
or d
my
i nat
(per
e s)
c
e
ive d
Env
)
iron
men
t (p
erc e
ive d
)
JWARS C2 Design with CBM
er s)
The Improved Game Board
Individual Perceptions
Commander Model
NGIC Country
Behavior Data
DIA Unit
Behavior Data
Commander
Personality Data
Commander
Behavior
Model (CBM)
Individual Decision Criteria
Selected Course of Action
33
Combat Operations
Defend with Reserve
LEGEND
Unit Movement Vector
Weapon Orientation
Unit Formation
Orientation
No Reserve or Reserve Committed
Advance to
Contact
• Attack activity seeks combat, but not on any
terms (unless so ordered).
• Plans are simplistic, but will be more maneuver
oriented under the Maneuver Planner.
• Boundaries will constrain units, and unit
formations will automatically adjust to local
conditions.
Maritime Component C2
 Structure - Dynamic
 Awareness
» JEF via queries
JTF
» Own tactical sensor(s)
» From superior/subordinate
units
» Mission orders and status
JFMCC
 Pending, In Process,
TOG
TOG
Ships
Ships
Canceled, On Hold, Complete
Aircraft
 Warfare Area Commander controls one
or more TOGs
 A TOG can be subordinate to several
Warfare Area Commanders
* TOG - Task Oriented Group
35
Ship Type
Maritime CONOPS Implementation
User Specified
Maritime
Units
Task Organization
Inventory
(Force Flow)
Deploy Block
Mission Allocation
Resources
& Assets
Tasks
User Specified
JTF C2
JTCB
Operational
Phase/State
Control
Tomahawk
Target Plan
JFMCC
SUW, MIW,
STW, etc.
Demand
Target/Asset Pairing
Warfare
Operating Areas
JFLCC
ATO
NSFS Plan
Fire Support PIM
FSC ID
Composite
Warfare
Commander
Collection Missions
ADP Missions
CAS Missions
Target Mission
Dynamic Daily
Operational Tasking
SUW Daily Oper Task
USW Daily Oper Task
CV Oper Area
ASW Stations.
Ship Routing
Trunk
Specific
36
Maritime Order
 Specific action to take { What not How }
 An order is issued
» By Issuer (may be itself)
Issuer
 Sets Priority
 Issues all guidance needed for that order
• times
• locations
 Tracks Order
 Cancels order
» To Receiver
Order
Receiver
 Determines how to accomplish the order
• Course of Action selected on constraints and perceive situation
 Tells issuer when an order is
• Accomplished
• Off schedule
37
Where Orders come from
 From Superior or Self
» As part of a CONOP
 From scripted order
» Theater level only
 From self
» in response to events
 a task is invoked with a given priority
 When entering the theater { INCHOP orders }
38
Strategic Logistics C2
•Deployment Mode Selection
-Assign ULNs to carriers
•Air Route Selection
•Sea Route Selection
-Assign Carriers to Routes
Structure: JTF
Transcom
Awareness: Installation Status,
Prohibited Airspace, Asset Availability
•Airlift Scheduling
•Sealift Scheduling
-Schedule Carrier Loading,
-Departure and Arrival
39
Intra-Theater Logistics C2
Structure: JTF
Unit, sustainment and
transportation asset
locations
J4
 Theater
» Unit Equipment Moves From
PODs
AWARENESS
Infrastructure: Arc Capacities
(Environment), Attrition, Node
Ownership (Perception)
 From strategic lift operations
Scheduler
24 Hour Schedule
Requirements: Re-supply
Requests
Shortest Path
Algorithm
» Resupply Moves from PODs to
Depots
 From strategic lift operations
» Unit Moves Within Theater
(BSEs)
Prioritization rules: User
Defined
Unfulfilled requirements
 Administrative relocation
» Resupply Moves from Depots to
BSEs
40
TBM C2
 Structure
 Awareness
» Launch Detections
JTF
» Asset availability/status
AADC
JFMCC
JFLCC
JFACC
41
TBMD Illustration
DSP
ABL
Simplistic
Command
and Control
Aegis
(NADS/NTW)
Patriot/THAAD
42
Agenda
 JWARS Background
 C4ISR Overview
 C2 Implementation
» JTF
» Air Component
» Land Component
» Maritime Component
» Logistics
» TBM
 Summary
43
C2 Decision Algorithms Summary
 Air
» Command Hierarchy - JFACC, AME
» Linear Program - ATO planning for aircraft/weapon allocation
» Boolean Rules - CAS, SEAD, and Air-to-air weapons control
SEAD planning
 Land
» Command Hierarchy - JFLCC, Armys, …, BN
» Commander’s Model - Course of Action assessment
 Fuzzy Rule Sets and Game Theory
 Maritime
» Command Hierarchy - JFMCC, Task Forces, …, Ship
» Boolean Rule Sets - Course of Action assessment
 Moving towards CBM & Fuzzy Rule Sets used by Land
44
C2 Decision Algorithms Summary
(cont)
 Amphibious Operations
» Boolean Rule Sets - Go/No Go decisions
 Transportation & Logistics
» Routing & scheduling - Strategic and Theater lift
» Shortest path - Ground movement network
 TBMD
» Boolean Rule Sets - weapon system tasking
 Collection Planning
» Greedy Algorithm for IR prioritization
 Joint Targeting
» Greedy Algorithm for target weaponeering
45
Guidelines for Model Development
UK/NATO Code of Best Practice in C2 Assessment
Models must represent
 Information as a commodity
 Realistic flow of information around the battlespace
 Collection of information from multiple sources and
tasking of collection assets
 Processing of information
 Represent C2 [C4ISR] systems as entities on the
battlespace
 Unit perceptions built, updated, and validated from
information available through its information systems
 Commander’s decision based on the unit’s perception
of the battlespace
 Information operations (post Release 1)
46
Questions?
47