A subcontractor for a subcontractor for a subcontractor to the Army's Logistics Civil Augmentation Program, or LOGCAP, contract turns out to be a private military contractor (PMC). The "news" is that this company used armed guards to protect the transportation of cash used to pay vendors and employees and were part of a contract that does not allow contracting for armed security.
Since the prime contractor is a Halliburton subsidiary (KBR) and the security firm is Blackwater, Inc, from Moyock, NC, it makes headlines and a congressional hearing.
What is interesting to me is that the KBR contract administrator recognized the problem with this and understood his firm's role in flowing the proper clauses down to the subcontracts. He recommended not following the direction that the eventual sub-sub-subcontract went.
Of course, he wrote all this in an email and for some reason "top officials" at KBR were unaware of it. It seems logical that all email traffic is not forwarded to the senior officials at this company that has 57,000 employees.
That happens to me all the time. No one at the Pentagon ever reads these important postings nor my emails and nor takes my opinion seriously. I can't understand why KBR doesn't do a better job with far fewer employees.
I am not sure what the true issue is here. Is it the numbers of contractor personnel in Iraq? Is it the number of contractors that are needed to protect other contractors? Or is this something not contract-related at all- perhaps an issue of rules of "behavior" in-theater- or maybe it is just politics.
Tuesday, February 13, 2007
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment