Losing the War Data For Iraq and Afghanistan

cervesaebraciator writes with an excerpt from an analysis of a kind we're likely to see more of as ubiquitous sensors and cheap storage continue to proliferate: "'The Iraq and Afghanistan campaigns are unique in that they were the first wars to be documented electronically. The use of computers to track stabilization efforts produced enormous datasets in which important indicators were tracked, including daily electricity-production rates, georeferenced insurgent attacks, factory employment numbers, military spending on locally sourced goods and services and public opinion. [...] Army Secretary John McHugh recently admitted to members of Congress that thousands of records from the Iraq and Afghanistan conflicts are missing. [...] The problem is that much of the existing data were collected in an ad hoc manner that reflects the lack of planning for stability operations following both invasions. While certain data types were methodically maintained, others were kept by single individuals in more arbitrary ways—in some cases, on a single computer's hard drive, in a personal computer or within an e-mail account. As flash drives are lost, computers reformatted, files erased, and human and magnetic memory degrades, various data types have been and will continue to be destroyed." With apologies to Santayana, those who do not backup data sets of the past are condemned to repeat them."

Comments

On the shoulders of giants

[Anonymous Coward]

The problem is that much of the existing data were collected in an ad hoc manner that reflects the lack of planning for stability operations following both invasions.

With each generation the prior generation of technology often looks ad hoc or patched together. Given that these operations happened over a decade ago it's no surprise that the data was handled poorly by today's standards.

Re:On the shoulders of giants

[clodney]

The problem is that much of the existing data were collected in an ad hoc manner that reflects the lack of planning for stability operations following both invasions.

With each generation the prior generation of technology often looks ad hoc or patched together. Given that these operations happened over a decade ago it's no surprise that the data was handled poorly by today's standards.

I find it hard to believe that anybody is the least surprised by this. Look around your organization. Surely there is some guy down the hall who has taken it upon himself to keep track of something that is not required but that makes his job easier or piques his interest. After awhile people start to realize that he has a list of which customer has been sent which update, something which for some reason is not tracked in the CRM, but is sometimes very useful to have. He faithfully maintains the list for several years, until he moves to a different job. Turns out his successor does not find the information as useful, so stops collecting it. 2 years later it is hopelessly out of date and it gets deleted.

There were *millions* of people involved in the Iraq and Afghanistan wars. That kind of semi-official record keeping had to have happened thousands of times. Suppose I work for a battalion of engineers doing electrical grid repairs. The CO has to make a report to Brigade every month on various metrics. Some staffer compiles the info every month for a Powerpoint. After the tour ends and the CO is no longer reporting to Brigade every month, why would I continue to maintain the data? Who is going to come asking for it? So I delete it. Now repeat that for thousands of records.

Don't panic

[ebonum]

We can start another war and re-build the data set.