I found this article very interesting because it talked about the U.S. Governments inability or unwillingness to have an operable searchable database.  Working for the state of California I found the same issues to be true in that the state acted as if it could not develop an ease running database that would allow its employees to readily do their jobs.  We’ve already learnt that data is so exponential that we must have Information Technology to helps us make sense of the data. 
The article which I found on Wired.com is interesting because it relates to what I have read in chapter six about t he need for a data warehouse having a logical collection of information. A data mart contains a subset of data warehouse information.  If the government warehouse for which I worked would have had such a model my job as a Material Distribution Manager would have been a dream.  It’s so unfair for employees, managers and any outside customer’s to have to deal with poorly designed and piecemeal electronic warehouses. 
My main problem was that the state failed to use an accurate ease-to-use system and it caused the backorders to increase and money to be spent elsewhere. When you deal with a large warehouse databases it important to know what merchandise is needed for internal customers, employees such as gloves needed to work on the hot asphalt. Your budget must be accurate so that you know what you can afford to purchase and how you must prioritize in spending.  Another point is that you must know what outdated items that are left in your warehouse that you must write-off at the end of the fiscal year.  Finally if a database is an accurate and clean database in regards to customer names, addresses and billing invoices it saves the finance department money.
(http://www.wired.com/threatlevel/2007/03/government_spen/)