The mission planning environment for the strategic bomber is characterized by numerous man-to-machine relationships, data flows and organizational interactions. Currently, these activities are accomplished by several mechanisms using a variety of data formats. Several tools have been developed to address the complexity of not only bomber mission planning, but tactical (unit) level mission planning as a whole. Unfortunately, many of these initiatives have fallen short of seamlessly connecting the tactical level mission planning processes with the operational level or providing the unit- level mission planner with the right information, in the correct format, at the right time. One of the major reasons these initiatives fail is the developers of tactical mission planning systems do not completely understand the business rules, data exchanges and activities that compromise the bomber mission planning process. Through structured architecture, this paper discovered a general set of bomber mission planning environment requirements, common to all bomber Major Weapon Systems (MWS), at the tactical level. During the analysis process, several observations were made which require more consideration during future requirements development and/or mission planning system acquisition.
Requirements for Common Bomber Mission Planning Environment
2006
106 pages
Report
No indication
English
Aircraft , Military Operations, Strategy, & Tactics , Mission profiles , Air force planning , Bomber aircraft , Data management , Tactical bombing , Strategic bombing , Man machine systems , Information exchange , Jmps(Joint mission planning system) , Common mission planning environment , Air force mission support system
Crew-centered bomber mission model (CCBM)
Tema Archive | 1989
|Globale Mission: Bomber der USAF üben 24-Stunden-Einsätze
Online Contents | 1995
Engineering Index Backfile | 1935
Air Force secretary sheds more definition on mission for new bomber
Online Contents | 2007