GSA Schedule Foul-Up Leads to $87.5 Million False Claims Act Settlement
Oops!
We’re quite sure that
Massachusetts-based EMC Corporation uttered
that word (or worse) when the Department of Justice intervened in a
whistleblower “qui tam” suit alleging, among other things, violations of
the False Claims Act. Here’s the DOJ announcement, reporting that EMC agreed to pay $87.5 million to settle
various allegations stemming from its GSA Schedule.
EMC Corporation, a Fortune 500 company
traded on the NYSE, is a multi-billion dollar
global provider of IT services. The company describes itself thusly:
EMC’s
Information Infrastructure business provides a foundation for customers
to manage and secure their vast and ever-increasing quantities of
information, automate their data center operations, reduce power and
cooling costs, and leverage critical information for business agility
and competitive advantage. EMC’s Information Infrastructure business
comprises three segments – Information Storage, Content Management and
Archiving and RSA Information Security.
EMC’s VMware Virtual Infrastructure
business, which is represented by EMC’s majority equity stake in VMware, Inc.
(“VMware”), is the leading provider of virtual infrastructure software
solutions from the desktop to the data center and to the cloud. VMware’s
virtual infrastructure software solutions run on industry-standard
desktop computers and servers and support a wide range of operating
system and application environments, as well as networking and storage
infrastructures.
We found an EMC brochure discussing its Federal government services.
Members of this website have access to our knowledge
resources. Among those resources one might find a couple of discussion
papers covering risk areas associated with GSA Schedules. Commonly
thought to be “low risk” contracts with the Federal government, the
reality is that GSA Schedule contracts are fraught with risk for unwary
contractors. Contractors whose only government contract is their GSA
Schedule contract, or
contractors who consider themselves to be “commercial companies” are at
the most risk—because such companies typically fail to invest in control
systems that would help to reduce the risk of a contract compliance
failure.
One of our discussion papers has
this to say:
- Risk Area: Pre-award disclosure of commercial sales practices
and discounts
- Contractor provides data on
commercial sales practices and discounting policies.
- Commercial Sales Practices (CSP) Format needs to be current,
accurate and complete at submission. If there is
any doubt about category of customers, discounts or concessions, err on
the side of disclosure.
- Risk Area:
Identification of Price Reduction Clause “Basis of Award” customers and
pricing relationship
- Contractor negotiates “Basis of
Award” (BOA) category of customers and BOA/GSA pricing relationship.
- Designate a category of customers that is realistic and
manageable, not too broad such as all commercial customers or all
national accounts. Make sure the category of customers price is accurate.
- Ensure that underlying terms and conditions of the most favored
customer pricing are clearly disclosed and understood.
- Be clear on pricing relationship between MAS contract price and
BOA category of customers price (i.e., proportional vs. absolute
relationship).
The DOJ had this to say about its
allegations regarding EMC’s Schedule contract:
… by misrepresenting its commercial pricing
practices, EMC fraudulently induced the General Services Administration
(GSA) to enter into a contract with prices that were higher than they
would have been had the information technology company not made false
misrepresentations. Specifically, the United States alleged that the … company represented during contract
negotiations that, for each government order under the contract, EMC
would conduct a price comparison to ensure that the government received
the lowest price provided to any of the company’s commercial customers
making a comparable purchase. According to the government’s complaint,
EMC knew that it was not capable of conducting such a comparison, and so
EMC’s representations during the negotiations – as well as its
subsequent representations to GSA that it was conducting the comparisons
– were false or fraudulent.
Oops—EMC should have read our discussion
paper! But that’s not all the DOJ has to say about this particular contractor—
The United States also alleged that EMC engaged in
an illegal kickback scheme designed to influence the government to
purchase the company’s products. EMC maintained agreements whereby it
paid consulting companies fees each time the companies recommended that a
government agency purchase an EMC product. These kickback allegations
are part of a larger investigation of government technology vendors that
has resulted in settlements to date with three other companies, with
several other investigations and actions still pending. The kickback
investigation was initiated by a lawsuit filed under the qui tam, or whistleblower, provisions of the False Claims Act, which
allow private citizens to sue for fraud on behalf of the United States
and share in any recovery.
EMC’s latest
quarterly 10Q report (May 7, 2010) had this to say in a footnote:
United
States ex rel. Rille and Roberts v. EMC Corporation.
Effective as of May 4, 2010, EMC entered into a settlement agreement
(the “Agreement”) with the United States of America, acting through the
Civil Division of the United States Department of Justice (the “DoJ”). The Agreement relates to a previously disclosed “qui tam”
action that followed an investigation conducted by the DoJ regarding (i) EMC’s fee arrangements with systems
integrators and other partners in federal government transactions, and
(ii) EMC’s compliance with the terms and
conditions of certain agreements pursuant to which we sold products and
services to the federal government, primarily a schedule agreement we
entered into with the General Services Administration in November 1999.
Pursuant to the Agreement, EMC will pay the United States $87.5 million.
In consideration of this payment, the United States has agreed to
release EMC with respect to the matters investigated and the claims
alleged by the DoJ in the civil action. As set forth in the
Agreement, EMC expressly denies any liability or wrongdoing in
connection with such matters and claims, and the settlement represents a compromise to avoid the
costs, distraction, and uncertainty of continued litigation. As
previously disclosed, EMC recorded an $87.5 million accrual for this
contingency as of December 31, 2009.
Well there you go. Readers might
recall our recent article on kick-backs.
We told you they are a “no-no”—especially in the government contracting
environment.
Saying “we told you so” somehow
seems to lack the air of professionalism for which we generally try to
achieve. But we will say this:
Sorry, EMC Corporation, but you should have checked this site before you decided to get into the GSA Schedule
contracting business.
DOD Makes it Tougher to Issue Award-Fee Contracts
We have previously
reported on the Obama Administration’s
efforts to restrict the use of “high-risk” contract types such as
award-fee contracts. And we previously posted an
article focused on award-fee contract types here, noting an April 2010 DOD Class Deviation that provided
contracting officers with a contract clause that would permit any award
fee to be “reduced or denied” if the prime contractor – or subcontractor
– was determined to be liable for serious bodily injury or death to any
civilian or military personnel of the Government through gross
negligence or with reckless disregard for their safety.
Recently DOD issued (on May 21,
2010) a new Class Deviation that made it much tougher to issue award-fee
contracts to DOD contractors. The Class Deviation increased the
approval level over the contracting officer “determination and finding”
required by FAR 16.401(d), from one level above the C.O. to “the head of
the contracting activity (HCA) or designee no lower than one level below
the HCA.” The approval authority cannot be further delegated. Obviously, the higher approval level makes it that much more difficult to issue this type of contract.
Without any further information, it’s difficult to speculate
what circumstances drove the need for this Class Deviation. One might
wonder whether DOD has 100 percent confidence in its cadre of
acquisition professionals. …
In the
meantime, GAO recently testified that “the
past two years have seen DOD and the Congress take meaningful steps
towards addressing long-standing weapon
acquisition issues” and that “DOD’s acquisition policies and processes
may [finally] be headed in the right direction.” GAO testified that it
expect these recent steps to “serve to improve acquisition outcomes” for
DOD—in terms of cost, schedule, and technical objectives. We note that
there was no mention of problems linking program outcomes to use of
incentives.
So GAO has told Congress that DOD
is headed in the right direction, but DOD leadership seems to believe
that its acquisition workforce needs more stringent controls, at least
in the area of award-fee contracting. What are they not telling us?
(That last part needs to be whispered in a conspiratorial tone.)
|
Cost-Reimbursement Contracting Class
Nick Sanders, Principal Consultant, has been invited to instruct a 3-day class in Cost-Reimbursement Contracting. The class, sponsored by Federal Publication Seminars, will be held in Las Vegas June 15-17, 2010. The course material is based on the famous Nash & Cibinic book, Cost-Reimbursement Contracting.
DOD Implements Franken Amendment (Again)

On May 19, 2010, the DAR Council published an interim Defense Federal Acquisition
Regulation (DFARS) rule implementing the Franken
Amendment. “Wait!” we hear you saying. “Didn’t Apogee Consulting, Inc.
already publish an article entitled “DOD
Implements the Franken Amendment”? What’s going on here?
Well, it’s like this: Previously, we reported that DOD has
issued a “Class Deviation” implementing the Franken Amendment on various
DOD contract actions, as discussed below.
- An order valued at more than $1
million that uses FY 2010 funds, placed against an ID/IQ contract, is
covered by the Franken restriction “regardless of whether the basic
ID/IQ contract was covered.”
- An order valued at more
than $1 million that uses FY 2010 funds, placed against a GSA Schedule,
is covered.
- A contract modification adding more
than $1 million in FY 2010 funds to a contract awarded before February
17, 2010, is not covered by the
restriction. However, a
“bilateral modification adding new [contract] work after February 17,
2010 to such a contract is covered” by the restriction.
But a Class Deviation does not a regulatory action make, so
the DAR Council was required to publish a proposed rule for public
comment. Interestingly, the DAR Council chose not to publish a proposed
rule, but instead to publish an interim
rule. What’s the difference? A proposed rule is not binding on
anybody. Nothing happens until public comments are received and a final
rule issue is issued in the Federal Register. The final rule may or
may not look like the proposed rule, depending on what public comments
are received and how they are viewed by the rule-makers. On the other
hand, an interim rule goes into effect immediately, even while public
comments are being received and reviewed. If the comments have any
influence, then a final rule may be issued that differs from the interim
rule; otherwise, the interim rule is declared to be a final rule and
that’s that.
We’ll assume you already know what
the Franken Amendment is. If not, click the second link above and you
can review its origin and some of its history. The interim rule adds a new
subpart 222.74 (Restrictions on the Use of Mandatory Arbitration
Agreements) to the DFARS. It does not apply to
the acquisition of commercial items, but it does apply to “covered
subcontractors”. It also applies to any contract, bilateral contract
modification, or task/delivery order valued at more than $1 million that
used FY 2010 appropriated funds.
Helpfully,
the DAR Council provided some examples to help determine what contract
actions are (and are not covered) by the new rules.
- A new
order that exceeds $1 million using funds appropriated or otherwise
made available by the FY 10 DoD Appropriations Act, placed against an
indefinite-delivery/indefinite-quantity contract for an applicable item
or service, is covered by this restriction, regardless of whether the
basic indefinite-delivery/indefinite-quantity contract was covered.
- A funding modification adding more than $1 million of funds
appropriated or otherwise made available by the FY 10 DoD Appropriations Act to a contract that
does not contain the clause at 252.222-7006 or 252.222-7999
(Deviation), is not covered.
- A bilateral
modification adding new work that uses funds appropriated or otherwise
made available by the FY 10 DoD Appropriations Act in excess of $1 million is covered.
- The award of a new order using funds appropriated or otherwise
made available by the FY 10 DoD Appropriations Act with a value of $700,000 is not covered,
since the value is under $1 million.
- A
contract valued at $1.5 million awarded today, and only $10,000 in funds appropriated or otherwise made available by
the FY 10 DoD Appropriations Act will
be obligated, with the remaining balance being FY 11 funding, is not
covered, because the total value of funds appropriated or otherwise made
available by the FY 10 DoD
Appropriations Act is less than $1 million.
- An
entity or firm that does not have a contract in excess of $1 million
appropriated or otherwise made available by the FY 10 DoD Appropriations Act is not affected by
the clause. The term ‘contractor’ is narrowly applied only to the
entity that has the contract. Unless a parent or subsidiary corporation
is a party to the contract, it is not affected.
The restrictions mandated by the Franken Amendment are being
implemented via solicitation and contract clause 252.222-706
(“Restrictions on the Use of Mandatory Arbitration Agreements”). Readers can review the exact clause language in the first link, above.
As always, the public may submit comments at www.regulations.gov. Details regarding how to address and submit a comment are
found in the interim rule itself.
|