Alcatel-Lucent and Lucent Technologies World Services: The Tests Behind Iraq’s Emergency Network

In the Alcatel-Lucent and Lucent Technologies World Services settlement, the company agreed to pay $4.2 million to resolve allegations of misleading radio-network testing certifications. The underlying Army contract was worth $250 million. The government alleged that inaccurate assurances about testing Iraq’s emergency communications system supported claims for equipment, services and performance award fees. If you know what happened during testing and what the customer was told afterward, the gap between those accounts is what these allegations were about.

What the Iraq Radio-Testing Settlement Covered

Lucent Technologies World Services was the Alcatel-Lucent subsidiary responsible for the Army contract. The Justice Department announced the settlement on September 21, 2012, describing allegations about the design, construction and modernization of Iraq’s emergency communications system.

The Army awarded the company the contract in March 2004 to build the Advanced First Responder Network. The network was intended to let Iraqis summon police, fire and medical assistance through a 911 emergency-response and first-responder communications system.

The challenged certifications concerned testing between January and July 2005. The government alleged that the company inaccurately certified that it had performed and successfully completed certain tests of radio transmission sites, along with validation of the network as a whole. The testing was meant to establish proper operation before acceptance by the United States and transfer to the Iraqi government.

Why Radio-Site Tests and Network Validation Mattered

The alleged misleading testing certifications connected technical work to government money. The settlement announcement identifies claims for equipment and services as well as contract performance award fees. The allegedly inaccurate assurances helped support both the bill for the work and claims for a performance award.

We see the absurdity: a performance award supported by allegedly misleading assurances about performance. The certification was supposed to give the Army confidence in the network it was accepting.

The distinction between a radio-site test and validation of the whole network also matters to someone who knows the project. The government’s allegation addressed both, so the comparison has to reach the site-level testing and the account of how the network operated as a whole.

The 2007 Brookings paper Can’t Win With ‘Em, Can’t Go to War Without ‘Em: Private Military Contractors and Counterinsurgency describes contractors handling logistics, operating facilities and maintaining sophisticated weapons systems. That account of contractors keeping military operations running helps explain the stakes of the Lucent allegations: the Army needed assurance that Iraq’s emergency network would work when someone called for help.

What Evidence Is Needed to Prove Fraud?

For a testing-certification case, useful evidence connects the required tests, the underlying results, the company’s assurances and the government claim. We examine what the government was told alongside what the work actually showed, including how the certification reached acceptance and payment decisions.

Payment terms and individual contract line items identify the work required and the basis for the money requested. The executed contract and its modifications matter because the testing requirement, the acceptance decision and the fee can each depend on what the parties agreed the company would deliver.

For an insider who knows the tests or the contract records, the useful comparisons are concrete:

• The requirement and the work. The contract, modifications and testing requirements identify what had to be demonstrated.
• The results and the certification. Original results can be compared with the certification that described testing as completed and successful.
• The certification and acceptance. Acceptance and transfer records connect the technical assurance to the government’s decision to take the work.
• The assurance and the money. Equipment and service claims identify what the contractor asked the government to pay for. Performance-award records connect the claimed achievement to the fee requested for it.

A contract manager and a testing employee may see different parts of that sequence. One may understand the requirement and the submission, while the other knows what was tested and what the result meant. We bring those perspectives together around the government’s bill, so the technical discrepancy has its financial context.

Who Investigated the Allegations?

The Defense Criminal Investigative Service’s Seattle Resident Agency, the Defense Contract Audit Agency and Army Criminal Investigation Command provided investigative support. The U.S. Attorney’s Office for the Western District of Washington and the Justice Department Civil Division’s Commercial Litigation Branch jointly handled the case.

The audit role in a defense fraud investigation includes examining a contractor’s accounting and pricing. That financial work matters to a testing case because the technical assurance has to connect to the money the contractor requested.

A Radio Upgrade That Allegedly Could Not Be Done

A separate whistleblower complaint against Airbus Defense and Space shows how technical knowledge can matter before the government awards a radio contract. The complaint alleged that the Army awarded a contract without competing bids to upgrade a communications system because only the vendor could perform the work on its proprietary network. The whistleblower alleged that Airbus, called ADSI in the complaint, already knew the radios would need complete replacement:

The alleged radio capability protected the company’s access to a contract without competition. In the Lucent case, the alleged misrepresentation concerned testing already described as completed. Each account puts the technical representation next to a government spending decision. An insider who knows the technology can explain why that representation mattered.

The Contract Manager’s Whistleblower Case

A former Lucent Technologies World Services contract manager for the project brought the whistleblower suit resolved by the settlement. The False Claims Act allows a private party to bring a qui tam case on the government’s behalf and share in a recovery.

A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. For someone considering a defense contractor whistleblower case, knowing how a testing assurance became a bill can help turn a suspicion into a case. We work with you to connect what you saw to the government’s payment and the company decisions behind it.

You Know What the Tests Showed

If you saw testing described as successful when the results told a different story, talk with our whistleblower experts about the contract and the claim. We build the case with you and bring in defense contractor fraud whistleblower lawyers who understand testing requirements, acceptance and performance payments. Your technical knowledge belongs at the center of that work, and we stay beside you through the case.