Abstract: This paper is based on the experience gained by personnel in the Information Directorate of the U.S. Air Force Research Laboratory's Rome, NY, Research Site, during the development, validation, testing, and fielding of the Joint Defensive Planner (JDP) in the USAF Theater Battle Management Core Systems (TBMCS). JDP has been used for the past 3 years in its successive developmental spirals by the US/NE/GE Extended Air Defense Task Force during the Joint Project Optic Windmill (JPOW) exercises in NATO. JDP is currently being evaluated by personnel in the United Kingdom (UK) Joint Force Air Command HQ and the UK Air Warfare Centre for potential use in UK Systems. This paper addresses the theme of this symposium: "Commanders at all levels and types of military organizations require timely and accurate awareness of the situation in their respective areas of responsibility as well as prediction of likely intentions of participants." Of equal, or greater, importance is that Commanders at all levels have a consistent situational awareness, although the level of detail may vary, depending upon his/her position in the Chain of Command or organizational functions to be performed. The overall goal is to provide a single, joint software planning tool to assist Theater Air and Missile Defense (TAMD) staffs of the Combatant Commander (COCOM), Joint Force Commander (JFC), Area Air Defense Commander (AADC), Regional Air Defense Commander(s) (RADC), and Service Component Commanders to collaboratively develop the operational level joint TAMD plan to counter air and missile threats. The resultant Area Air Defense Plan (AADP) documents the AADC's plan for integrating and coordinating joint air and missile defense. This paper reflects on JDP Lessons Learned and incorporates them as general guidelines to describe a process to develop defensive planning tools for combined forces. Twelve briefing charts summarize the presentation. (11 figures)
| Limitations: |
 APPROVED FOR PUBLIC RELEASE NATO FURNISHED |
| Description: |
Conference paper |
| Pages: |
23 |
| Report Date: |
MAR 2004 |
| Report Number: |
A506824 |
|
|
|
|
Keywords relating to this report:
