And doubtless the majority are, man. I know this to be true, as well. Like the Army, a "few bad apples", etc.

Where a problem seems to exist with regards to support contractors is out-of-scope violations by entities other than the Contracting Officer.

Case in point: I know of a contractor performing work ordered within scope by the KO to pour sidewalks at a FOB. The sidewalk-making was going well and within cost, schedule and performance parameters. Then a senior soldier (we'll keep the rank out of this on principle) decided he needed a sidewalk to his quarters, along with one for his boss. He directed the contractor to perform this. The contractor's on-site supervisor, not having a full command of the language, and doing what DCUs tell him to, begins pouring the extra sidewalks.

Needless to say, confusion, frustration and anger reigned with both the KO and the contractor when the project busted the parameters. Evil, greedy contractor? Not hardly. Government conspiracy? Nope. Apparent authority mis-utilized? Yep.

While a relatively-harmless (I say "relatively", as no loss of life, limb or eyesight occurred, but your tax dollars bought some turd the luxury of not getting his feet dusty enroute to the latrine), it's a good case in point that the Government/Contractor team can get befuddled or just plain mutually injured. The situation on the ground often aggravates this.



Quote Originally Posted by Schmedlap View Post
Seemed like hard-working, honest, decent folks to me.