Defining the Role of Airpower in Joint Missions

Kent, Glenn A.; Ochmanek, David

doi:10.21236/ada342423

Cited by 6 publications

(3 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…13 The Joint Operational Architecture was envisioned to describe the totality of tasks and activities, operational elements, and information flows required to accomplish the missions of DoD. 14 The chairman of the Joint Chiefs of Staff, viewing the Joint Operational Architecture as a key mechanism to foster interoperability, issued direction to organize it around "Joint Mission Areas" and identified about a dozen "as-is" and "to-be" Joint Mission Areas. 15 Later, DoD Instruction 4630.8 codified these ideas and others more formally; the key concepts are summarized in Appendix A.…”

Section: Pressure To Implement Effects-based Operationsmentioning

confidence: 99%

See 1 more Smart Citation

Beyond the Task Force Conops: The Path to a Capabilities-Based Modernization Framework for the Air Force

Planeaux¹

2003

View full text Add to dashboard Cite

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

show abstract

Section: Pressure To Implement Effects-based Operationsmentioning

confidence: 99%

“…14 The hierarchy and similar definitions were "accepted" by the Air Force and written into AFPD 10-28, but never implemented to a great degree; it is not known whether the expected revision to AFPD 10-28 will continue to endorse the RAND hierarchy.…”

Section: Kent and Ochmanek "Framework For Modernization"mentioning

confidence: 99%

Beyond the Task Force Conops: The Path to a Capabilities-Based Modernization Framework for the Air Force

Planeaux¹

2003

View full text Add to dashboard Cite

show abstract

“…73 "The planner must therefore be permitted to sustain a focus on future needs and opportunities if he or she is to perform the critical responsibilities of setting demand, developing innovative operational concepts, evaluating alternative investment plans, and developing and advocating the Plan." 74 One of the major reasons for the reorganization was Air Force leadership felt that the longrange planning and MPP functions were too stovepiped, and that options developed did not represent an integrated viewpoint and was too narrowly focused. As a result, many experts asserted that the decisions made concerning tomorrow's Air Force were being made on current issues, which increased the risk of acquiring the wrong capabilities for tomorrow's threat.…”

Section: Focus/divisionmentioning

confidence: 99%