You are here

Intelligence Requirements Management (IRM)


OBJECTIVE: The contractor shall design and develop the ability to generate, track, and maintain the intelligence requirements and provide the repository of the resulting intelligence products. This capability also needs to provide the capability to initiate intelligence collection, monitor the status, and notification of collected information by interoperating with existing and future ISR Synchronization tools. DESCRIPTION: An IRM provides the ability to trace each intelligence analysis task to the original intelligence requirements in the Commander's Critical Information Requirements (CCIRs), Priority Intelligence Requirements (PIRs), and Friendly Force Information Requirements (FFIRs) during the Military Decision Making Process (MDMP) as the basis for their analysis and conclusions. Also, data collection activities need to be traced to each intelligence analysis tasks in order to monitor and measure the effectiveness of each collection systems to satisfy the original intelligence requirements. PHASE I: Perform a design study to formulate innovative technical approaches to develop an IRM that offers an enterprise solution that works within the Army Command Post Computing Environment architecture, which is based on virtualization, rich web client (Ozone Widget Framework), and data analytic cloud. The design study should define the paradigm for customizable and evolving applications that interoperate with existing and future ISR Synchronization tools. Complete an IRM design concept and demonstrate through modeling, analysis or prototype that it meets the requirements. PHASE II: Use the results of the design concept generated in Phase I to develop a software prototype of the IRM for use with ISR applications and with existing and future ISR Synchronization tools. Use the software prototype of the IRM to perform a demonstration that validates that the approach improves traceability of Intelligence Requirements and operational effectiveness. PHASE III: Implement the IRM as part of the DCGS-A/JUMPS systems and deploy the system for test and evaluation using commercially available technologies. The implementation should ensure that the system is interoperable with existing and future Synchronization Tools. Potential applications include special operations forces missions, maritime domain awareness, and border security missions. REFERENCES: 1. Brigadier General John F. Stewart, Jr.,"Operation DESERT STORM, The Military Intelligence Story: A View from the G2, 3d U.S. Army,"April 1991. 2. For insight into synchronization planning from the collector's viewpoint, see Captain Timothy J. Moynihan's"MI Battalion Synchronization Matrix: Tactical Tool for the Commander and Staff,"Military Intelligence Professional Bulletin, Vol.19, No. 1, January-March 1993, 38-41. 3. General Gordon R. Sullivan,"Delivering Decisive Victory: Improving Synchronization."Military Review, Vol. LXXII, No. 9, September 1992, 8. 4. The G2 may employ intelligence synchronization to answer information requirements whenever those answers are required at particular times. I have emphasized PIR in this article by choice. 5. FM 34-130, Intelligence Preparation of the Battlefield, 8 July 1994, 1-11. 6. FM 34-1, Intelligence and Electronic Warfare Operations, 27 September 1994, 2-17. Ibid, 2-20. 7. FM 34-2, Collection Management and Intelligence Synchronization Planning, 8 March 1994, 3-26.
US Flag An Official Website of the United States Government