Advanced Battlespace Information System (ABIS) Task force Report, Volume 4: Sensor-to-Shooter Working Group Results.
Abstract
This nested loop flow model of the Sensor-to-Shooter (STS) Operational Concept will be used in subsequent discussions of STS operations. The outer loop, which represents the longer cycle of battle management operations, splits into two branches, one branch containing the inner loop of sensor-to-shooter operations as a special case. Key observations about the nature of the STS operations follow: Sensor-to-shooter operations include many of the same functions in battle management operations (e.g., sensor tasking and information acquisition). This is so because the sensor-to-shooter operations begin when the mission is assigned to the mission leader. At this point, the sensor-to-shooter execution team must perform the same functions in planning how the mission is to be executed that the battle managers performed in planning what will be executed. Therefore, the sensor-to-shooter team requires the same functional capability as the battle manager, but for an increased depth of detail spanning a narrower area of interest. Although it has a different emphasis on timeliness and level of detail, this functional commonality with battle management is the essence of the sensor-to-shooter challenge. Sensor-to-shooter operations are basically of two types, those that are executing the preplanned ATO (that is, the outer loop including the lower branch) and those that are providing assets for highly responsive and autonomous operations against fleeting targets (that is, the fast, seconds to minutes, inner loop). These are discussed in detail in subsequent sections in subsequent sections. Although it is not obvious from the figure, a key element of integrated sensor-to-shooter operations is the fact that there are multiple cases of these executing elements operating simultaneously.
Document Details
- Document Type
- Technical Report
- Publication Date
- May 01, 1996
- Accession Number
- ADA313956