Should DynCorp have been warned its pricing was killing its bid?

Find opportunities — and win them.

The GAO and the Army say "No" because the decision wasn't about price, but when you read the GAO bid protest decision, it seems everything comes back to DynCorp's high price.

Several things stand out to me in a recent Government Accountability Office decision denying a protest by DynCorp.

First, there is the huge gap in the prices proposed by DynCorp, the incumbent, and KBR, the winner of a task order under the Logistics Civil Augmentation Program IV or LOGCAP contract. The Army was competing a following task to support military installations in the Arabian Peninsula.

DynCorp bid a price of $148.1 million, a whopping $111 million higher than KBR’s bid of $37 million. Yes, $37 million.

The second thing was that GAO said that the significant price difference didn’t matter, because this was going to be a cost-plus contract. “Regardless of the costs proposed, the government is bound to pay the contractor its actual and allowable costs,” GAO wrote.

Instead, the Army has to conduct a cost realism analysis to determine if the costs bid are realistic for the work to be done. GAO looks at the methodology used and determines whether it is reasonable.

And here is where the third thing stands out to me: GAO found several mistakes that the Army made in evaluating the bids, but none of the mistakes were egregious enough to show that DynCorp’s chances of winning were hurt.

Here again, the prices bid came into play. GAO wrote that “even if the protester was correct that KBR’s proposal should have been adjusted … it does not appear that the adjustments establish that, but for the alleged errors, the protester would have had a substantial chance for award.”

In other words, the Army’s mistakes couldn’t overcome the huge gap in the prices bid.

And a final issue: It appears that DynCorp may have been a victim of its own attempts to stand out from its competitors.

DynCorp argued that the Army had to have engaged in unequal discussions with KBR and Fluor, a third bidder, regarding the true nature of the requirements. Otherwise, there wouldn’t have been such a wide disparity between DynCorp’s proposed costs and the costs proposed by KBR and Fluor. (Fluor’s bid was $40.1 million.)

But the Army told GAO that DynCorp’s proposed hours and costs were not seen as a significant weakness. They found that DynCorp’s proposal was “realistic and reasonable” because it proposed a unique technical/management approach. In fact, the Army saw that part of DynCorp’s proposal as a unique strength.

But the uniqueness wasn’t enough to overcome a price that was some 300 percent higher than its competitors. GAO said it doubts that any discussions would have significantly closed the pricing gap.

GAO said just because the price gap was so significant, the Army still didn’t need to enter into discussions with DynCorp because its price and staffing proposals were not seen as weaknesses.

My conclusion is that I don’t quite buy the Army and GAO’s reasoning here because it seems obvious to me that gap is why DynCorp lost.

To use the car analogy: The Army wanted to buy a car and DynCorp bid a Lamborghini while KBR bid a Chevy.

It seems to me that while the Army might love the capabilities of the Lamborghini, it’s never going to buy the Lamborghini over the Chevy.

Don’t you think it is reasonable for the Army to tell DynCorp, Hey, we love your proposal but we can’t afford to buy it, especially when we have other bids that we reasonably expect will get the job done.

It seems to me that the Army should have had the conversation with DynCorp.

The Army and GAO might argue that the pricing wasn’t a weakness for DynCorp but in reading GAO’s decision, it’s obvious that the pricing was DynCorp’s fatal flaw, and they should have been warned.

NEXT STORY: Veritas closes Alion deal