SAIC, AES and Navy Computing Officials: An Alleged Head Start Before the Bids

The 2011 SAIC Navy computing settlement called for $22,676,000 to resolve allegations of procurement steering, including advance information and a solicitation shaped to favor SAIC’s contractor team. The alleged advantage reached into the competition before the government chose a contractor. Someone who worked on the proposal or saw the solicitation take shape could recognize the central issue: what one team knew, when it knew it, and who helped write the terms it would bid on.

The Justice Department’s September 29, 2011 announcement covered SAIC, its subcontractor Applied Enterprise Solutions LLC, AES’s chief executive and two former government employees. Lockheed Martin, another member of the SAIC team, had reached a separate settlement earlier that year.

What Was the SAIC Navy Computing Settlement?

SAIC agreed to pay $20,400,000 after receiving $116 million under the contract, according to the September announcement. AES and its chief executive agreed to pay $2,166,000 together. The two former government employees, the Navy computing center’s former director and deputy director, agreed to pay $110,000 together.

A former employee of the Naval Oceanographic Major Shared Resource Center brought the case. The government joined the claims against the September settling parties.

The Navy Computing Contract at Stennis

The General Services Administration awarded SAIC the task order in April 2004 to provide support services for the National Center for Critical Information Processing and Storage. That center was at the Naval Oceanographic Major Shared Resource Center at Stennis Space Center in Hancock County, Mississippi. The purchase was computing support for the Navy, with GSA handling the award.

SAIC teamed with Lockheed Martin and AES to perform the work. The prime contractor contracts directly with the government, while a subcontractor supplies the prime. Here, SAIC held the government award, and the September release specifically identified AES as its subcontractor. That structure matters because the allegations reached both the company receiving the task order and people working with its team.

What Are the Red Flags in Procurement Fraud?

In this case, the alleged red flags were unequal access to procurement information and a solicitation shaped to favor the team receiving it. The Justice Department described conduct both before the solicitation came out and after it became public. The allegation concerned who controlled the competition’s information and terms.

First, the suit alleged that the officials shared nonpublic, advance procurement information with the SAIC team that other potential bidders did not receive. For someone preparing a proposal, information about the purchase can shape the work long before submission. The comparison is between what the favored team allegedly had and what the other potential bidders could see.

The next allegation concerned timing: the SAIC team allegedly received solicitation information before other bidders. One team can begin working from information that the others are still waiting for.

The final allegation reached the solicitation itself. According to the suit, the officials and supplier participants chose a type of contract and put language into the solicitation to bias selection toward SAIC’s team. Contract type determines who bears cost risk, so influence over that choice can favor a team’s approach to the work. The alleged favor was built into the terms on which the government would choose a winner.

On the suit’s account, an honest competitor preparing its best proposal still faced a selection process shaped for someone else. Some competition. Taxpayers were paying for a Navy support contract, and the alleged manipulation concerned who got that business in the first place.

The Officials and the Supplier Team

The two government participants held the director and deputy director roles at the Navy computing center, according to the Justice Department’s January account. The suit alleged that they conspired with SAIC, AES, AES’s chief executive and Lockheed Martin to secure the task order for the team. Their alleged contribution was access to procurement information and influence over the solicitation. The investigation involved the Justice Department’s Civil Division, the Defense Criminal Investigative Service, the Naval Criminal Investigative Service and the GSA Office of Inspector General.

Lockheed Martin’s Earlier Settlement

Lockheed Martin reached its own $2 million settlement, announced on January 24, 2011. The January release also described Lockheed’s role as a subcontractor paid under its agreement with SAIC. That puts Lockheed in the contract’s performance and payment chain as well as in the allegations about obtaining the award.

What Proof Do You Need as a Whistleblower?

For an allegation about a favored solicitation, we assess how the information you saw connects to the competition, the award and government payments. The useful evidence connects what the government presented to bidders with what happened inside the procurement. You may know when information reached a proposal team, who helped shape a requirement or how a change favored the eventual winner.

The SAIC allegations give those observations a concrete focus. We would compare the information available to potential bidders with the information allegedly shared privately, then examine the timing and the solicitation terms. The team arrangement and contract payments connect that account to the government business at stake. These are the connections we would assess with you, starting with the part you know firsthand.

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. Our work on defense contractor whistleblower claims begins with the connection between your knowledge of the procurement and the money the government paid. We help you develop that account into a case with whistleblower lawyers who understand defense procurement.

What Inside Bid Information Can Buy

A separate whistleblower complaint against ADS Tactical alleged that a payment to a contracting officer bought access to competitors’ exact bid amounts. The complaint explained the alleged commercial use of that information:

The alleged advantage in that complaint was knowing the numbers to beat. In the SAIC matter, the allegations concerned early procurement information and influence over the solicitation. Both accounts make an insider’s view of the competition valuable: what looks like a successful proposal from outside can depend on information or influence available only to one team.

Why Access Before Award Matters

Third Way’s 2026 policy memo, Pentagon Procurement: Big Spending, Bigger Vulnerabilities, describes a procurement system that buys routine support services as well as weapons. It argues that uncovered fraud cases reveal only part of the system’s exposure. It calls for fixing the weaknesses that make fraud possible, alongside pursuing fraud after it happens.

The SAIC allegations put that concern at the beginning of a purchase: access to information and influence over the terms before award. For a proposal employee or someone inside the buying organization, the important knowledge may be how the competition took shape. We connect that account to the award and payments it helped produce.

You Saw the Competition Take Shape

If you saw procurement information reach a favored team or watched solicitation language change to help it win, speak with our whistleblower experts about what happened before award. We shape your strongest defense procurement whistleblower case, bring in whistleblower lawyers who know bid-steering cases and stay beside you through the pursuit of a recovery.