7 years, 4 months ago
Captain Tim Hsia, U.S. Army, has written a thoughtful and provocative article at the Small Wars Journal Blog entitled Intelligence Collection and Sharing. Captain Hsia begins by cataloging the sundy reasons for the paucity of good local and regional intelligence and other information.
When a unit assumes battle space within Iraq the first thing that a commander receives from his higher headquarters is a plethora of maps detailing major avenues of approach, religious divides, key figures, demographics, key infrastructure, etc. However, much of the intelligence is outdated or watered down, and the source of this data is often unattributed. The source of this intelligence is necessary in order to winnow the chaff from the wheat. The intelligence received from higher headquarters can come from multiple sources, which oftentimes can be suspect and unverifiable. For example, is this intelligence derived from an Iraqi Army soldier, Iraqi policeman, neighborhood councils, street vendor, coalition signal assets, or from the previous military units who have operated within the current Area of Operations? Additionally, this initial trove of intelligence oftentimes provides just the basics and does not delve into more important issues that commanders need to know, such as the amount of money U.S. forces have spent developing the local infrastructure, the number of discontinued projects and reasons for their discontinuance, the quality of local leaders, and the attitudes of those leaders toward the U.S. military.Counterinsurgencies are not won by more soldiers, cutting edge technology, or more lethal weapon systems. Rather insurgents are defeated when the pacifying force fully understands the local citizenry, when the people identify with the pacifying force, and when there is an abundance of timely information which allows the pacifying force to apply their intelligence to operations that result in overturning and disrupting insurgent activity. Despite the great advances in the U.S. military’s ability to leverage technology to gain intelligence, it has been less successful in storing and synchronizing the historical data compiled during the past several years in its campaigns in the Middle East.
When a unit redeploys to the states they usually dump all of their electronic files to their counterparts in no systematic or coherent manner. This is the ideal situation, though if they are on a more limited timeline they might just pass off the most essential information. With units being continually shifted around Iraq with little or no notice to respond to increased violence in different areas, it has been almost impossible for units to properly pass off their intelligence to the next battle space owner or more importantly to future units that will operate in their sector. At best the problem a commander faces is an abundance of information that is improperly cataloged. Oftentimes however it is the worse case scenario in which commanders and diplomats encounter, a difficult situation where they have little to no information regarding a region or locale
As a sidebar note, if Captain Hsia is arguing for a small footprint model of counterinsurgency, he has history with which to contend (the problems in Operation Iraqi Freedom II and III caused by inadequate force size and force projection, as well as the problems in Afghanistan from the same). But continuing with the point of his article, he advocates a rather remarkable solution to this problem.
A way to remedy the chaotic state of intelligence management is to create a central intelligence collection platform that will allow any unit to upload operation summaries, economic analysis, tribal networks, environmental analysis, and graphical overlays into a central site that future commanders can access when they assume an assigned battle space. Currently all military units in Iraq and Afghanistan have access to a worldwide SIPR (secure Internet protocol router) network which allows them to access, view, and transmit secret information. Expanding this network to encompass a more centralized program of data sharing would not require any additional hardware. A fusion of geography and intelligence within a centralized network can ensure that commanders arrive at any location with the necessary intelligence derived from years of work by previous agencies and military units that have already provided a framework for understanding the enemy and the people in his assigned area. Commanders could then be spared the countless man hours recollecting data that has already been captured thru blood, sweat, and tears. A solution to the current intelligence blackhole would be to collect, store, and sift this data into a intel site organized in a manner replicating stock market data.
The appeal for such a system is strong. I started the category The Anbar Narrative in order to begin to capture snippets of perspectives and information regarding the campaign in Anbar in its various manifestations. I have exchanged perspectives with Lt. Col. Gian Gentile at the Small Wars Journal in which I have taken the position that the campaign in Iraq can be at least partially categorized as a counterinsurgency, while he has clearly said multiple times that it is only a civil war. Gentile’s perspective doesn’t affect the Anbar narrative, but it does go to show that the region and locale within Iraq can deeply affect the way a participant sees the situation. In Anbar and to the East around Ramadi, the Anbar narrative became all about tribes “flipping.” In Fallujah, tribal sheikhs were irrelevant and kinetic operations, gated communities and biometrics were the order of the day, and the muktars were much more important than the sheikhs. To the West in Haditha, fighters from Syria were problematic and earthern berms were necessary to isolate the area from outside influences. In Basra, the story is one of competing Shi’a gangs and thugs in a struggle for power. In Kirkuk there is a mixed Sunni, Shi’a and Kurdish population, and like Baghdad, civil war might be a better description of the circumstances. No single narrative fully explains the complexity of the Iraq experience. Combined with personalities, monies spent successfully and wasted, and other exigencies of the battle space, one can easily be overwhelmed by the data and information. And if we cannot even get our history right while the campaign is ongoing, how can we expect to pass on more particular and detailed information with precision?But the solution Captain Hsia profers is overwhelming as well. Note well what is being advocated. Graphical overlays, potential enemy information, (probably) census information, operational summaries, and on the list goes. All of this would have to be in a database, searchable on name (enemy), operational details (e.g., what were the locations and patrol sizes when IEDs were encountered, were distributed operations successful against enemy snipers, etc.). This means that such a database would have to be a relational database. This means that those who enter the information and access the information would have to be trained in this relational database (search query criteria, required entry information and formatting, etc.). This means that in order to deploy such a system across the armed forces in a consistent manner, a defense contractor will be at work for years to develop such a system and training for its operation would be implemented only over subsequent years in order to put it to use.We have noted with lament that the U.S. armed forces is at war, and the public has not yet mobilized for this war. Defense Secretary Gates is having trouble deciding to wean the Army off of a fifty year old cold war by re-deploying from the European theater, and the Afghanistan campaign suffers from a lack of force projection. And yet we are discussing millions and years more to deploy an integrated relational database for battle space intelligence!We like the idea, but we are realistic about it. It pays to profer the idea when its need is seen, but it also pays to point out the scope of the project. This scope is likely to kill the project before it ever gets off the ground.