National Academy of Sciences | 150 Year Anniversary

Questions? Call 800-624-6242

| Items in cart [0]

The National Academies Press

PAPERBACK
price:$108.00
add to cart

Rights & Permissions

topleft topright

Modeling Human and Organizational Behavior: Application to Military Simulations (1998)
Board on Human-Systems Integration (BOHSI)

Citation Manager

. "8 Planning." Modeling Human and Organizational Behavior: Application to Military Simulations. Washington, DC: The National Academies Press, 1998.

Please select a format:

BibTeX EndNote RefMan


Page
218
bottomleft bottomright

The following HTML text is provided to enhance online readability. Many aspects of typography translate only awkwardly to HTML. Please use the page image as the authoritative form to ensure accuracy.


Modeling Human and Organizational Behavior: Application to Military Simulations

TABLE 8.4 Models for Planning in Military Human Behavior Representations (HBR)

Name

Sponsor

Service (Domain)

Level

Functions/Activities Modeled

Implementation/Architecture

Comments

Adaptive Combat Model

Marine Corps Modeling and Simulation Office

Infantry/Marines (HBR models)

Individual and unit

Route planning

• Genetic algorithm optimization

• Currently an exploratory study

Commander's Visual Reasoning Tool (CoVRT)

Army Research Laboratory (ARL)

Army (decision support)

Brigade

Course-of-action generation

• Decision-aiding workstation with graphic depiction of military entities

• Underlying command/staff dependency matrix provides over-all framework for information flow among HBR agents

Marine Computer-Generated Force (CGF)

Defense Advanced Research Projects Agency (DARPA), Hughes Research

Marine (HBR models)

Individual and unit

Route planning

• Production rule system driven by external state variables

• Multiple rulesets for different decision alternatives;

• Generation of single plan frame for ModSAF execution

Computer-Controlled Hostiles for Team Target Engagement Simulator (TTES)

Institute for Simulation and Training/University of Central Florida (IST/UCE)

Marine (HBR models)

Individual

Short-term planning for individual military operations in urban terrain activities

• Hierarchical goal decomposition;

• Decision-theoretic goal selection;

• Situation-driven rules

Appears to be single-step planner, but could be expanded to multiple steps for individual course-of-action generation

Fixed-wing Attack (FWA)-Soar and Soar-Intelligent Force Agents (IFOR)

DARPA, Air Force, University of Michigan (UMich), University of California/Los Angeles (UCLA), Carnegie Mellon University

Air Force (HBR models)

Individual and unit

Full activities of tactical pilots across a wide range of aircraft and missions

• Soar architecture with hierarchical goal decomposition;

• Efficient production rule system to deal with large rulebase;

• Situation-driven rules

• Planning not explicitly represented, as Soar supports only single-step planning;

• Could be expanded to support an explicit planning module

Rotary-Wing Attack (RWA)-Soar

DARPA, Army, UMich, UCLA

Army Aviation (HBR models)

Individual and unit (company)

Full activities of rotorcraft pilots and company commander for RWA mission

• Live battalion commander;

• Soar-CFOR company commander that:;—Generates mission plan;—Monitors progress;—Replans as necessary;

• Soar-IFOR RWA pilots;

• ModSAF vehicle entities

• Plan generation and elaboration done through tactical templates and standard operating procedures;

• Plan refinement done through checks on task interdependencies, timing

Man-Machine Integration Design and Analysis System (MIDAS)

National Aeronautics and Space Administration, Army

Army Aviation (HBR models)

Individual and unit

Full activities of tactical rotorcraft pilots

• Symbolic operator model architecture with hierarchical mission activity decomposition;

• Production rule system to implement procedures;

• Situation-driven productions

• Similar to Soar in its top-down decomposition from mission phases to low-level activities;

• Single-step planning, but could be expanded to support an explicit planning module

Page
218