“Affordability” and “Efficiency” Become New DOD Mantras
We’ve been following the Pentagon’s recent obsession
with moving “tail to tooth” by reducing its overhead expenditures—and
that of its contractors—by $100 billion in order to prepare for the new
fiscal realities. In fact, we’ve been rather critical
of the effort so far, calling it “exactly the opposite” of what
Secretary Gates called for, in that the early activity seemed to consist
of adding bureaucracy rather than cutting it. We may have been a bit
overhasty in our initial assessment.
In
our defense, very few of the news stories on these topics are getting
it right either. It this all about affordability or efficiency? Is it
about the Pentagon, or its contractors? It turns out it’s about both.
What we are seeing now is a bifurcation: it looks like two separate initiatives
are being pursued by the DOD. One effort is focused on delivering
Secretary Gates’ call for “efficiency” within the Defense Department,
while the other effort is focused on implementing the call for
contractor “affordability” (as championed by Deputy SECDEF Lynn and
Undersecretary (AT&L) Dr. Ash Carter).
According to this story
at DefenseNews.com, on July 29, 2010, Defense Secretary Gates planned
to meet “with more than a dozen U.S. defense industry executives to
discuss his efficiencies effort. Gates will be joined … by Deputy
Defense Secretary William Lynn and Pentagon acquisition executive Ashton
Carter … to hear their suggestions, thoughts and concerns about the
Pentagon's efforts to find efficiencies and get a better deal when it
buys weapons, services and other items from industry.”
Let’s review the status each of the efforts.
Affordability
The
July 26, 2010 edition of Aviation Week & Space Technology magazine
carried a story about Dr. Carter’s meeting with various industry
executives at the Farnborough air show, in order “to emphasize the need
to improve affordability and productivity in weapon system development
and procurement” and “to solicit input” into his initiative. But the
executives (who insisted on anonymity) were somewhat less than
supportive. AW&ST reported that “one executive says that because
companies already answer to shareholders, they are often leaner than the
government.” (We agree, and we pointed that out in our prior articles
on this topic.)
Regardless,
Dr. Carter intends to move forward to find savings in the defense
industrial base. He wrote an article for FederalTimes.com here, in which he stated—
To
sustain our force structure, modernize and develop future combat
capabilities, we must make every taxpayer dollar count. This initiative
is a first step toward restoring affordability to defense spending.
Those
who hesitate to embrace the need for change should consider the
alternative: broken and canceled programs, unpredictability and
uncertainty for industry, erosion of taxpayer confidence and, above all,
lost capability for our war fighters.
The
savings we seek will not be found overnight. It has taken years for
excessive costs to creep into our business practices, and it will take
years to root them out. But it is crucial that we begin this process
now. …the earlier we embark on this initiative, the easier it will be to
succeed.
Efficiency
The Wall Street Journal blog reported
that the Defense Business Board prepared a series of recommendations
for SECDEF Gates’ consideration. Although the recommendations are not
yet finalized, the blog stated—
In
a presentation issued today at the Pentagon, the Defense Business
Board, an independent federal advisory body that includes business
executives and corporate strategy types, offered a few proposals for
getting smarter about spending. The board’s observations would be
familiar to any corporate efficiency expert: The Department of Defense
often suffers from bloated staffs, redundant layers of management and
inadequate spending controls. …
This
report offers a number of concrete measures, including a hiring freeze
within the Office of the Secretary of Defense, and an effort to
streamline staff within the Pentagon’s geographic commands. It also
encourages the department to get a grip on contractor headcounts, and
find out how many contractors actually work for the DoD. And it
recommends elimination of Joint Forces Command, a contractor-heavy
headquarters organization based in Norfolk, Va.
Similarly, DefenseNews.com reported that the DBB would recommend that the Pentagon’s civilian workforce should be cut by 111,000 heads. The article stated—
The
study group will advise Gates to either shrink the DoD civilian work
force to 2003 levels or by 15 percent, whichever is greater. The greater
reduction would be a 15 percent cut, which would amount to 111,508
personnel, based on the 743,388 employees DoD had in March, according to
the Office of Personnel Management's online database, Fedscope. DoD had
654,287 civilian employees in September 2003.
(We
have sourced a copy of the actual Defense Business Board’s
“pre-decisional” presentation. Members will be able to find it in our
knowledge resources section very soon. UPDATE: The DBB presentation is available under Knowledge Resources as of 08/03/10.)
Notes from the July 27, 2010 meeting between Pentagon officials and industry executives revealed the following points:
- This initiative is “not a budget exercise.” The DOD is “not looking to take money from contractors or from existing programs.
- The
DOD is not looking to “enforce improvements in existing programs.”
Instead, reforms will be imposed on “all future programs.”
- Dr.
Carter will be issuing a memo in September that will kick-off sustained
follow-up effort. The memo will not be the end of the process; “it’s
just the beginning.”
- “Mr.
Lambert stressed a few times about the unintended consequences of our
actions and implement solutions that work without falling into the trap
in unintentionally making things worse.“
Notes
from a participant, distributed by Lt. General Larry Farrell (USAF,
Retired), to members of the National Defense Industrial Association
(NDIA), included the following points:
- Someone made a really good suggestion about cutting the requirements for proposals. I recently saw a proposal that cost a company $4 million and took two pallets to deliver. I can’t imagine that all of that paper was really necessary to make an intelligent procurement decision. By
limiting proposals to things that really contribute to lower risk and
greater value the B&P costs will be reduced and there will be more
money available for competing more, lowering G&A or doing IR&D,
not to mention hiring the people who must read and document their
assessments of all of that stuff.
- There have been many discussions about reducing cycle times for decades. Doing this not only saves money, but produces more timely results, and keeps pace with technology. We have an enemy who improvises - this is not the cold war. The ‘Lean Aerospace Initiative’ was an attempt to create metrics that would lower cycle times. Its findings should be re-examined, updated, and extended. Time is money, but it is also lost capability.
While
the foregoing activity was happening, another key stakeholder was warning
that cutting funding for weapon programs would be a mistake. This New York Times article reported that “a blue-ribbon board” warned that efforts to cut Pentagon waste “would not free
enough money to modernize aging ships and planes and close a ‘growing
gap’ between the size of the military and its missions.” According to
the article—
Its 155-page report
expressed mild criticism of the Pentagon’s planning process. And it
warned that ‘a train wreck’ was coming unless the Pentagon found more
money to modernize the Air Force and Navy and gained control of
skyrocketing health and benefits costs.
Conclusion
The
more we hear about these initiatives, the more we hope they will
succeed. The Pentagon’s bloated bureaucracy needs to be pruned, and
there’s absolutely nothing wrong with rewarding contractors that deliver
their programs on-time and on-budget—while penalizing those that do
not. Nonetheless, we maintain a detached air of pessimism, informed by
decades of watching similar efforts that went nowhere.
DCAA Director Fitzgerald Testifies Before CWC; Blasts LOGCAP Subcontractor Management
On July 26, 2010, the Commission on Wartime Contracting in Iraq and Afghanistan (CWC) held a hearing
entitled “Subcontracting: Who’s Minding the Store” to address concerns
about the subcontracting process in Southwest Asia. As the Commission
Co-Chairs noted, “Poorly conceived, poorly structured, poorly conducted,
and poorly monitored subcontracting can lead to poor choices in
security measures and damage to U.S. foreign-policy objectives, among
other problems.” Accordingly, the Commission explored “whether,
especially in a high-risk, contingency environment, the government needs
additional controls over, or more visibility into, subcontractor
performance and costs to ensure the prime contractor is adequately
managing its subcontractors.”
(We
have reported on several of the CWC hearings and reports before. To
find those stories, type “CWC” in the search window on the website.)
Before
we delve into DCAA’s testimony, we want to note a statement made by the
Commission Co-Chairs (Shays and Thibault). They said that the
Commission “will issue a major report with proposals for statutory and
administrative changes in December, followed by our final report to
Congress in July 2011.” So we are in our final year of CWC activity.
We look forward (with more than a little trepidation) to reading the
Commission’s recommendations for “statutory and administrative
changes.” Now on to the hearing….
The
hearing consisted of three panels, logically arranged into (1)
Government, (2) Prime Contractors, and (3) Subcontractors. Looking at
the first panel, we were less than impressed with the “motherhood and
apple pie” written statements from most of the participants. DCAA
Director Patrick Fitzgerald’s written statement,
however, piqued our interest. Lying amongst his platitudes and
smooth-talk were some gems of note. Let’s look at those, shall we?
Director
Fitzgerald told the Commission that DCAA has 34 full-time auditors
assigned to audit contingency contractors in Iraq, Kuwait, and
Afghanistan. 17 are assigned to the Afghanistan Branch Office (ABO) and
17 are assigned to the Iraqi Branch Office (IBO). By the end of GFY
2010 (September 30, 2010), DCAA expects to increase its workforce to 40
full-time auditors.
Director
Fitzgerald also testified that, “As noted in the Commission’s interim
report (June 2009), adequate contractor business systems are the first
line of defense against waste, fraud and abuse. In the realm of
subcontracting, we find this statement to be profoundly true.” What did
he mean by that statement?
As
Director Fitzgerald explained to the Commissioners, “With respect to
the three LOGCAP IV performance contractors, DCAA has reported all the
estimating systems as inadequate and cited their estimating practices as
being deficient for ensuring fair and reasonable subcontract prices.”
In addition, “DCAA has performed contractors’ purchasing system reviews
(CPSRs) for the Defense Contract Management Agency (DCMA) Administrative
Contracting Officer (ACO) at all of the three LOGCAP IV performance
contractors and has found each system to be inadequate.” Moreover,
Director Fitzgerald told the Commission, “During our review of prime
contractor billings and incurred cost audits, DCAA has identified
situations where the prime contractor has not awarded its fixed-price
subcontracts based on fair and reasonable prices leading to unreasonable
or unallowable costs being paid by the Government.”
Reasonableness of Subcontractor Costs
It
is one of the few unavoidable requirements placed on Government
contractors that, prior to making a subcontract award, the prime must
first make a written determination that the price it proposes to pay is
fair and reasonable. (See FAR 15.404-3(b), which requires a prime
contractor (or higher-tier subcontractor) to “conduct appropriate cost
or price analyses to establish the reasonableness of proposed
subcontract prices.”) So when Director Fitzgerald says the LOGCAP IV
prime contractors are failing in their duty to perform the requisite
analyses, that statement gets our attention.
Director Fitzgerald provided some details to support his assertion. He told the Commission—
In
March 2010, DCAA reported estimating system deficiencies at DynCorp
related to the inclusion of unsupported subcontract costs … for Corps
Logistics and Support Service, Theatre Transportation Mission and Postal
Operations in Iraq (commonly referred to as the CTP proposal). During
the audit of the CTP proposal, the auditors found the subcontract
proposal from DynCorp’s then “team member” subcontractor, Agility, to be
inadequate. An examination of the U.S.-based Agility business unit
disclosed that approximately 40 percent of the proposed direct costs
were unsupported. That is, the subcontractor, Agility, was unable to
support the reasonableness of the proposed direct labor costs proposed
as part of the CTP proposal. Further, in its proposal to the prime
contractor, Agility included lower-tier subcontractors to perform the
bulk of the subcontract effort. In fact, Agility proposed to use two
foreign-based Agility-affiliated subcontractors (sister business units).
… During the review of one affiliate’s proposal, the Iraq Branch found
the lower-tier subcontractor had only prepared a rough order magnitude
proposal without supporting detailed data. In the case of the other
lower-tier subcontractor, the Iraq Branch was initially denied access
supposedly on the basis that its prices were commercial prices and
exempt from any requirement for the submission of cost or pricing data.
As a result, the auditors determined that almost all of the proposed
Agility (and its affiliated subcontractor) costs were unsupported. … As a
result, the DCAA audit report classified over $800 million of the
proposed subcontract costs predominately related to Agility and its
affiliates as unsupported. It is important to point out that the prime
contractor had not performed adequate subcontract cost or price
analyses. The DCAA reported the contractor proposal was not adequate for
the basis of negotiating/awarding a fair and reasonable contract price.
But DynCorp wasn’t alone. As Director Fitzgerald told the Commissioners—
Our
audits of KBR proposals have disclosed similar significant unsupported
subcontract costs. In May 2010, DCAA issued its report on the LOGCAP III
Task Order (TO) 151 extension proposal. We identified over $48 million
of unsupported subcontract costs. KBR failed to obtain subcontract
proposals and conduct the required price or cost analyses. The
contractor’s failure to obtain adequate support from its prospective
subcontractors on this sole-source procurement increases the likelihood
of subcontract prices being unreasonable in amount. Similarly, earlier
this month, we completed an audit of Fluor’s “rebaseline” proposal under
LOGCAP IV TO 0002 that incorporated the impact of numerous change
orders on the total task order price. The change orders included
proposed subcontract costs of approximately $35 million. DCAA reported
over 40 percent of the proposed subcontract costs as unsupported because
the prime contractor’s proposal lacked sufficient supporting
documentation (e.g., cost or price analysis, competitive quotations).
The majority of the proposed subcontract costs that we reported as
unsupported were from foreign subcontractors of Fluor where, despite the
sole source nature of the contracting action, Fluor did not obtain cost
or pricing data from the related subcontractors.
DCAA’s
procedures did not stop at evaluating the adequacy and reasonableness
of proposed pricing. Indeed, DCAA proposed to disallow the cost of
paying already-awarded subcontracts when price reasonableness could not
be established. As Director Fitzgerald stated—
During
our review of prime contractor billings and incurred cost audits, DCAA
has identified situations where the prime contractor has not awarded its
fixed-price subcontracts
based on fair and reasonable prices leading to unreasonable or
unallowable costs being paid by the Government. For example, DCAA has
identified several cases where the prime contractor asserted the
subcontract price was based on adequate competition; however, our audit
disclosed that adequate competition did not exist. Although the prime
contractor is required to pay its fixed price subcontract amount, FAR
52.216-7 and the FAR 31.2 principles state the Government only makes
payments of amounts determined to be allowable and reasonable.
Therefore, where DCAA has determined that the subcontract price is not
fair and reasonable DCAA has attempted to calculate a reasonable amount
for reimbursement of the contractor’s billings attributed to
subcontractor costs. However, in those cases where the subcontract is
sole source, it is often difficult to obtain cost data to ascertain the
reasonable costs without access to the subcontractor’s books and
records. DCAA access to subcontractor books and records is generally
limited and dependent on the flow down by prime contractor to the
subcontractor of the appropriate FAR clauses, and in instances of fixed
price subcontracts, virtually nonexistent. For example, during DCAA’s
reviews of Fluor vouchers submitted for payment under a LOGCAP IV Task
Order, the prime contractor was unable to show the prices paid to its
subcontractor for DFAC and other services were fair and reasonable in
amount. Since DCAA does not have access to the subcontractor’s books and
records, we were unable to determine through other processes the
reasonableness of the prices being paid to the subcontractor and
subsequently passed on to the Government for reimbursement. As a result,
the DCAA auditors have suspended much of the subcontractor’s costs from
payment on vouchers (invoices) submitted for payment by Fluor. In
addition, the contractor has been withholding a portion of the
subcontractor billings, so that in total approximately $24.5 million is
being withheld from payment until the issue is settled. The FAR audit
access clause does not provide for Government access to the
subcontractor’s costs records when the subcontract is firm-fixed-price.
To
wrap up our review of Director Fitzgerald’s testimony, we want to recap
a couple of his concluding remarks. The following are direct quotes
from his written statement.
- Prime
contractors have the responsibility to manage their subcontracts (FAR
42.202(e)(2)) and also have a fiduciary responsibility to monitor
subcontractor performance and control costs to ensure the U.S. taxpayer
resources are used wisely and appropriately. … we have found that prime
contractors have not consistently monitored subcontractor performance
and subcontractor billings submitted to the prime contractor for
inclusion in the prime contractor’s billings to the Government. Although
the FAR requires the management of subcontracts by the prime contractor
and higher tier subcontractors, DCAA intends to recommend a review to
the Director, Defense Procurement and Acquisition Policy, of the
feasibility of specific contract clauses that would implement the basic
FAR provision on management of subcontracts. For example, prime
contractors should have systems or processes in place to review
subcontractor billing processes to ensure subcontract billings are in
accordance with subcontract terms and conditions.
- Based
on our audit results we question whether there was adequate/true
competition considering the limitations that the contractors have in a
contingency environment. In Iraq and Afghanistan, U.S. and coalition
military organizations most likely have consumed almost all of the
capacity of most or all subcontractors capable of performing in-theater.
Therefore, at best, competition within the area of a contingency is
limited because the Government-required goods and services generally
exceeded vendor capacities (that is, the Government is the sole or major
purchaser of goods and services from all vendors) and all vendors are
provided a portion of the requirements in order to satisfy the
Government’s needs. In such circumstance, we do not believe competition
and/or market forces provide better prices to the Government and believe
cost data should be provided to determine fair and reasonable
subcontract prices.
- DCAA
has taken exceptions to several subcontract pricing actions where the
prime contractor asserted a fair and reasonable subcontract price based
on “adequate competition” where in fact only one bid was received by the
prime contractor. DCAA is concerned about the risks created by current
regulations permitting awards to subcontractors using competitive
pricing procedures when only one bid is actually received. Again, in
these cases, we believe it would be beneficial for the prime contractor
and contracting officer to have access to subcontractor cost data to
determine fair and reasonable contract prices. The Adequate Pricing
Subcommittee under Mr. Assad’s Panel on Contracting Integrity is taking a
look into this area. They are ascertaining the need to revise this
“loophole” in the regulation that we believe leads to subcontract prices
being awarded at unreasonable prices. I will continue to work this
issue as the Chair of this Subcommittee.
We Take Issue with Some of Director Fitzgerald’s Statements
This
is much to think about in the written testimony of Director
Fitzgerald. We completely agree with him that adequate price or cost
analysis must be performed by contractors, in order to determine price
reasonableness, prior to awarding subcontracts valued in excess of
certain dollar thresholds. But we also note that, far too often,
government acquisition schedules fail to allow contractors sufficient
time to perform the required analyses. As a result, contractors often
sacrifice some of the administrative requirements. We’re not saying
they’re correct in doing so, but critics need to look at the driver(s)
of improper activities—and one of those drivers is the government’s
rushed RFP turn-around times.
We
also take issue with Director Fitzgerald’s statements that DCAA “has
performed” CPSRs for the DCMA and, as a result of its audit procedures,
“has found each system to be inadequate.” First of all, DCAA auditors don’t perform CPSRs.
At most, they perform some procedures to assist the DCMA functional
specialists with the purchasing system review, under the auspices of the
cognizant contract administration office. Don’t believe us? Check out
the DCAA Contract Audit Manual (CAM) at 5-603.
Even
when DCAA independently reviews a contractor’s purchasing system—and it
can only do so when the cognizant Administrative Contracting Officer
approves the audit activity—the auditors are not
performing a CPSR. As the CAM states, “Where the ACO agrees with DCAA
concerns, the auditor should perform a purchasing system internal
control audit (not CPSR) ….” We will not recite the control objectives
and control activities DCAA believes constitute an adequate set of
purchasing internal controls. Suffice to say that they are not
dissimilar from other DCAA internal control matrices, and are actually
worth reviewing when establishing a purchasing system.
But
the fact remains that DCAA lacks regulatory authority to determine that
any contractor’s purchasing system is inadequate. That authority is
vested in the cognizant ACO. (See FAR 44.305-1: “The cognizant ACO is
responsible for granting, withholding, or withdrawing approval of a
contractor’s purchasing system.”)
We
are also concerned with Director Fitzgerald’s unsupported assertion
that the current FAR Part 15.403-1 definition of “adequate competition”
somehow creates a “loophole” that permits contractors to award contracts
at other than fair and reasonable prices. There was no evidence
provided to support that assertion. Moreover, based on Director
Fitzgerald’s own testimony, the root cause was not a lack of
competition, but instead failure to perform adequate price or cost
analysis.
Look,
we don’t know all the facts and circumstances. All we have is the
testimony proffered to the Commission. But we get very concerned when
we hear somebody say that Contractors followed the regulatory
requirements to the letter, but somehow that the results were found to be improper by
the audit agency. If the so-called “loophole” is to be closed by new
statutory or revised regulatory language, then we need to see some solid
evidence that such a change is necessary. And we need to be convinced
that doing so will fix the alleged problem. Failing that, we suggest
DCAA get back to auditing and let the DCMA functional specialists handle
this area.
Conclusion
One
has only to search this site for the phrase “supply chain management”
to see the importance we place on the topic. Proper management of
subcontractors is absolutely crucial to assuring adequate program
execution. Part of that task is to put subcontractors under contract—to
identify sources, to evaluate bids, and to negotiate (and document) why
the resulting subcontract prices are fair and reasonable. In fact, in
November 2008, we told a small gathering at the local NCMA Chapter that,
“Acquisition professionals must own
all pre-award activities … Don’t be afraid of cost analysis. Dig deep
into supplier bids. Take whatever time is necessary to gain the proper
understanding.” So when DCAA tells the CWC that this is an area that
needs to be addressed, we have to agree.
Clearly,
subcontractor management—ranging from pre-award activities to
post-award performance management—is a topic of increasing interest to
DOD and other oversight officials. Look for recommended changes and
increased emphasis on this area from DCMA, DCAA, and others. If you
believe your procedures can be enhanced, then by all means we urge you
to get started right away. But we can’t help noting that, if you’ve
been reading this site, you would have been sensitized to this issue
long ago.
|
Government Contractor Fraud in the News

We recently posted an article about fraud in the commercial and international marketplaces. (We could keep on posting similar articles, such as this one,
but we won’t.) Other past articles have focused on corrupt activity by
military or civilian government employees. Our point—which we’ve made
before—is that a myopic focus only on government contractors misses the
bigger picture. Fraud and corruption are endemic to the human
condition, and they flourish where weak people and their temptations
meet lax oversight and/or ineffective controls. Enhance the control
environment and you reduce the opportunity for miscreants to break the
rules.
But
today we are reporting on yet more government contractors who are in
the news because of alleged wrongdoing. Let’s start first with John
Feeney, of Woodbridge, Virginia—who at age 28 has pretty much ruined the
rest of his life. According to the Department of Justice, Mr. Feeney pleaded guilty
to one count of mail fraud on July 28, 2010. Interestingly, Mr. Feeney
thought he was defrauding only his employer, BAE Systems Training
Services, Inc. Unfortunately for him, BAE Systems was a government
contractor whose expenses were reimbursed by Uncle Sam’s Defense
Department—meaning Mr. Feeney was really defrauding the U.S. Government,
who frowns on that sort of thing.
According to the DOJ press release, Mr. Feeney was a logistics engineer who “used
his position to authorize the purchase of camera lenses and video
equipment, intending to keep the equipment for his personal use but to
bill BAE for the purchases.” Mr. Feeney made 15 such “illicit
purchases” between August 2005 and June 2006, which cumulatively were
worth $476,424. Let’s repeat that: Mr. Feeney purchased nearly half a
million dollars worth of camera lenses and video equipment in less than a
year, and sent the bills to his employer, who was apparently pleased to
pay them.
What
did he do with his ill-gotten treasure of photographic goodness? The
DOJ reported that “Feeney subsequently sold many of the purchases on
an Internet auction site for profit.” As
we mentioned, Mr. Feeney’s employer had a contract at that time with
the DOD, under which “BAE would purchase surveillance equipment and
subsequently bill the U.S. government for those purchases.” In
fact, Mr. Feeney’s job was to purchase the equipment for the contract.
BAE Systems billed the DOD for $464,819 of the equipment he
fraudulently acquired. We don’t know how Mr. Feeney was caught, but
caught he was.
According to the DOJ, “The mail fraud count carries a maximum penalty of 20 years in prison, a
$250,000 fine or twice the gross gain or loss, whichever is greater, as
well as three years of supervised release.“ That pretty much takes
care of the rest of Mr. Feeney’s career.
Next,
we report the settlement of a False Claims Act case against Quantum
Dynamics, of Macon, Georgia. On July 29, 2010, the DOJ announced
that it had reached a settlement with the company, who allegedly
received contracts from the U.S. Army by fraudulently claiming to be a
HUBZone contractor. As the DOJ noted—
Under
the HUBZone program, companies that maintain their principal office in a
designated HUBZone and employ 35 percent of their workforce from a
HUBZone, among other requirements, can apply to the Small Business
Administration (SBA) for certification as a HUBZone small business
company. HUBZone companies can then use this certification when bidding
on government contracts. In certain cases, government agencies will restrict competition for a contract to HUBZone-certified companies.
Because
Quantum Dynamics did not qualify as a HUBZone company, its
representations that it was one created a false statement (under the
False Statements Act). Because it billed the Government for the
fraudulently obtained contracts, its invoices were considered to be
“false claims” that subjected the company to considerable liability.
The reported settlement figure--$750,000—indicates to us that either the
prosecutors felt there was some question as to the company’s intent to
defraud, or else that the company was short on financial resources and
there was little use asking for more. (Actually it could be both, as
the HUBZone rules are complex and difficult to understand.) The DOJ
press release did not report which company would be completing the work
started by Quantum Dynamics.
Next, we report that on the same day (July 29, 2010) DOJ announced that it had intervened in a qui tam
False Claims Act suit against Oracle Corporation (and its subsidiary
Oracle America, Inc.) for allegedly failing to disclose its commercial
sales practices to the General Services Administration (GSA)—which then
would allegedly lead to the government paying higher prices than it
otherwise would have. The DOJ reported that Oracle billed GSA “hundreds
of millions of dollars in sales” under the contract, so we’re not
hopeful that Oracle can settle the suit for less than a million dollars,
as Quantum Dynamics did.
What did Oracle (allegedly) do wrong? According to the DOJ—
Under
the contract, GSA used Oracle’s disclosures about its commercial sales
practices to negotiate the minimum discounts for government agencies who
bought Oracle software. The contract required Oracle to update GSA when
commercial discounts improved and extend the same improved discounts to
government customers. The suit contends that Oracle misrepresented its
true commercial sales practices, ultimately leading to government
customers receiving deals far inferior to those Oracle gave commercial
customers.
The
DOJ noted that the suit was originally filed by Paul Frascella, who was
the Senior Director of Contract Services at Oracle, and who might be
expected to know Oracle’s sales practices. The suit, United States ex rel. Frascella v. Oracle Corp. et al., No. 1:07cv:529 (E.D.
Va.), may make Mr. Frascella a rich man, since as “relator” he will
share in any damages awarded by the Court to the United States.
Finally, we wanted to relate this sad tale of corruption in the executive ranks of a defense contractor. (Here’s the link,
but you need to be a member to access the story.) This is not so much a
story of defrauding the U.S. Government, as it is a story about
“sweeping accusations of fraud, insider trading, and company-financed
personal extravagance.” According to the New York Times story, David
Brooks (former CEO and Chairman of the Board at DHB, now called Point Blank Solutions)
received corporate reimbursement for “more than $6 million in personal
expenses”—including luxury cars as well as “university textbooks for his
daughter, pornographic videos for his son, plastic surgery for his
wife, a burial plot for his mother, prostitutes for his employees, and,
for him, a $100,000 American-flag belt buckle encrusted with rubies,
sapphires and diamonds.”
Hey, some of that stuff might be unallowable!
As
the article noted, what makes this story interesting is the
egregiousness of Mr. Brooks’ behavior and “how gross the abuses are.”
The article stated that—
Mr.
Brooks has not disputed that many of his personal expenses were paid
for by the company, but his lawyers have maintained that the practice
was authorized. His lawyers also defended the hiring of prostitutes for
employees and board members, arguing in court papers that it
represented a legitimate business expense ‘if Mr. Brooks thought such
services could motivate his employees and make them more productive.’
There’s
quite a bit more to the story, including allegations of forged
compensation agreements, inventory manipulation, insider trading, and
tax evasion. If convicted, Mr. Brooks may be spending a long time
behind bars. Apparently, Mr. Brooks is aware of his precarious future,
as the article reported that—
He
may also face additional charges stemming from an episode last week
when he was caught for a second time trying to smuggle into jail
prescription anti-anxiety pills, which were similar to medication he was
already taking at an unusually high dose. The pills had been hidden in
pens that a supporter of Mr. Brooks’s had placed near the defendant’s
seat in the courtroom.
So
as we bring this article to its conclusion, we agree that we have
presented litany of dissimilar stories that may not have much of a
common theme—other that they all happened at government contractors. On
the other hand, government contractors are supposed to have developed
robust internal controls to prevent such acts from occurring. We hope
readers will think carefully about how they might detect or prevent
similar incidents at their companies.
Former State Department Employee, IRMO Advisor, Charged with Wire Fraud and “Conversion”
Conversion—“An
authorized assumption and exercise of the right of ownership over goods
… belonging to another … Any unauthorized act which deprives an owner
of his property permanently or for an indefinite time. Unauthorized and
wrongful exercise of dominion and control over another’s personal
property … See also Embezzlement, … Fraudulent Conversion …”
-- Black’s Law Dictionary, 6th Edition
On July 22, 2010, the Department of Justice announced
that Robert Hearn, of Temple, Texas, had been arrested and indicted for
wire fraud and conversion, stemming from an alleged “orchestration” of
the transfer of “approximately 60
accommodations caravans and other equipment from the site of a
U.S.-funded power plant project in Khor Az Zubair, Iraq, to the port” of
Umm Qasr, in Basra, Iraq. Mr. Hearn was employed by the State
Department an assigned to the Iraq Reconstruction Management Office
(IRMO) from April 2005 through September 2006, where he “was responsible
for providing advice to the director of the port,” who was “an official
with the Iraqi Ministry of Transportation.”
The
indictment alleges that Mr. Hearn, who was allegedly reassigned for
“failure” to properly advise the port director, carried out a number of
unauthorized acts while assigned to port Umm Qasr. Among the allegedly
unauthorized acts were the following—
- (Allegedly)
in December 2005, Mr. Hearn accepted the transfer of the 60
“accomodations caravans” to IRMO, even though he lacked the authority to
do so and “U.S. officials notified Hearn that IRMO did not have the
necessary property-management structure and therefore could not take
control of the equipment.” Subsequently, Mr. Hearn (allegedly)
“directed an Iraqi employee of the Ministry of Transportation to sign
for and accept the equipment on behalf of the Iraqi government.”
- (Allegedly)
the individual who signed for the equipment also was employed by
Bawabet Al Amer Company (BAC), a private Iraqi company operating at the
port. BAC provided security, through subcontractors, as well as lodging,
office space and dining services for government and private personnel.
The indictment alleges that from the summer of 2005 to the fall of 2006,
Hearn controlled the day-to-day operations of BAC, and on behalf of BAC
and a silent investor, negotiated business contracts, provided input in
BAC’s hiring decisions and directed the work of BAC employees.
- (Allegedly)
Hearn signed a three-year lease agreement on Jan. 1, 2006, on behalf of
IRMO, permitting BAC to use a portion of the port, which during Hearn’s
tenure became known as "Bob’s Camp." Hearn … had no authority to enter
into this agreement in his official capacity with IRMO and did not
discuss it with his supervisors. A portion of the transferred
accommodations caravans was installed by BAC employees in "Bob’s Camp."
- (Allegedly)
on Sept. 14, 2006, the day before Hearn was scheduled to be reassigned
to IRMO’s Baghdad office, he … negotiated a rental agreement on behalf
of BAC involving several of the transferred accommodations caravans. …
Hearn directed that rental payments be wired to a bank account in
Conroe, Texas, which he controlled. In this manner, Hearn allegedly
received $147,000 from the lessee business, which he used for personal
and business expenses.
The
DOJ announced notes that, “if convicted, Hearn faces 20 years in prison
and a $250,000 fine on each of the four wire fraud counts. If convicted
on the conversion charge, he faces a maximum of 10 years in prison and a
$250,000 fine.” For those doing the math, Mr. Hearn is facing 30 years
in prison and $1,250,000 in fines. How come he gets the book thrown at
him when others, including Major Sublett, Sergeant Chase, and Captain Mike, get away comparatively scott-free? Are the notorious bleeding-hears of Foggy Bottom actually tougher on miscreants than the Department of Defense? One can only wonder ....
|