Kudos to Ray Locker and Ken Dilanian at USA Today who recently published a story on the rampant conflicts of interest within a study panel that evaluates the Department of Defense's (DOD) Quadrennial Defense Review (QDR) for Congress. Locker and Dilanian's analysis found that "more than half of the panel members appointed to review the Pentagon's latest four-year strategy blueprint have financial ties to defense contractors with a stake in the planning process."
According to the article, Congress created the 20-member review panel in 2006 "to provide an independent 'alternate view'" of the QDR, "which shapes future military policy and spending on weapons and other needs." Both DOD and Congress appoint the unpaid panelists, with the Secretary of Defense selecting 12 members and the top Republican and Democratic members of the House and Senate Armed Services Committee diving up the other eight.
The 11 members with ties to the defense contracting industry include:
Last year, according to Locker and Dilanian, Secretary of Defense Robert Gates mandated that his appointees conform to federal ethics rules, which, among other things, requires them to disclose their assets and sources of income to the Pentagon and recuse themselves from recommendations that could affect a company with which they are affiliated. The congressional appointees have been under no such requirement. Shortly after USA Today began inquiring about the connections that some members of this year's panel had to the defense contracting industry, however, the Pentagon and Congress decided that federal ethics rules would apply to all panelists.
My first question is why Congress didn't require all panelists to conform to federal ethics rules from the beginning. Like any congressional committee that deals with powerful special interests, I think most members of the Armed Services committees operate with a certain benign outlook toward defense contractors. If you truly want an independent, alternate view of the QDR, though, why not, at a minimum, institute the commonsense rules that are already available to help ensure that outcome.
As Locker and Dilanian point out in their article, there are two sides to this issue. Some, like John Lehman, a panelist who works for a private equity firm that owns several defense contractors, point out that "most defense experts have some financial affiliation with the defense industry" and that those "with defense ties are capable of offering unbiased advice." While others, like Jordan Tama, a professor at American University, claim it is possible to find experts who don't have defense industry ties. In addition, some, like Janine Wedel, a professor at George Mason University, maintain that federal ethics rules hardly provide a guarantee of impartiality in these instances.
While I don't doubt that it's possible for someone with ties to the defense industry to offer unbiased advice on a defense matter, the whole issue with a conflict of interest is that you can't be sure, no matter if the advice directly impacts a company the individual is connected to or not. I think that largely stems from the fact that, like a member of the Armed Services committees, a panelist with defense ties defaults towards a sympathetic viewpoint of the military-industrial complex. With that said, it's not as if this committee is going to weigh the option of spending $200 billion on defense versus $600 billion. Of course, if DOD and Congress wanted to alleviate fears of conflict of interest, they could just appoint panelists that don't have ties to the defense industry, like the other nine members of the panel.
Image by Flickr user Nick Sherman used under a Creative Commons license.
(Gary Therkildsen 03/04/10; 0 comments)All the pieces are in place for Senate passage of major food safety legislation that would give the Food and Drug Administration new powers to police both home grown and imported foods. “[I]t is urgent that that FDA food safety legislation, which could improve the safety of 80 percent of the food supply, not get pushed behind other pressing issues that are less likely to garner bipartisan support,” Caroline Smith DeWaal, food safety director for the Center for Science in the Public Interest, writes in an op-ed for The Hill.
The bill, the FDA Food Safety Modernization Act (S. 510), developed in a bipartisan environment, DeWaal writes:
Amid the rancorous partisanship that has marked the past year in the nation’s capital, a bipartisan effort to pass food safety legislation has been quietly taking shape. While the healthcare negotiations have broken down, restarted, and now seem to be in limbo, efforts quiet but sure to upgrade the Food and Drug Administration’s food safety mandate are progressing steadily. The last push for Senate action is near. And that effort is evidence that Washington can sometimes work, albeit slowly.
Seven of the bill’s 15 cosponsors are Republicans, DeWaal notes. A similar bill enjoyed bipartisan support in the House where it passed last July, 283 to 142.
I’m less than sanguine about quick passage in the Senate – a body that seems to revel in slackery and incompetence. The food safety bill has been good to go since November when it passed the Senate health committee. What’s a bipartisan bill have to do to get some floor action in this town?
Nonetheless, the bill should remain a high priority for two reasons, as DeWaal argues. First, the bill would improve the safety of the food supply by allowing the agency to order mandatory recalls of tainted food products (a power it does not currently possess) and implement a program to collect fees from certain food facilities to fund increased safety inspections, among other provisions. Second, it would serve as evidence that government works to protect the public (and that government works period).
The latter is no small achievement. According to a recent CNN poll, 83 percent of Americans think our government is broken. According to a different poll, a majority of Americans think government has grown so large that “it poses an immediate threat to the rights and freedoms of ordinary citizens.”
Ensuring the safety and integrity of the food supply is an example of government intervention that aids, not threatens. Considering voter frustration with government’s role in society – which I believe stems in large part from the political morass that has bogged down health care reform and economic stimulus – now is an opportune time to highlight what government can do well.
(Matthew Madia 02/26/10; 0 comments)Yesterday morning, Rep. Jan Schakowsky (D-IL) and Sen. Bernie Sanders (I-VT) held a press conference to announce the reintroduction of legislation to phase out the government's use of private security contractors in war zones. The Stop Outsourcing Security Act, which Schakowsky and Sanders originally introduced in 2007, seeks to prevent contractors in war zones from performing "mission critical or emergency essential functions," including security, military and police training, interrogation, and intelligence.
During the press conference, Sanders explained the rationale for the bill thusly:
I believe that it is wrong and extremely dangerous for private companies to perform mission critical functions in the field of war. Private contractors do not operate within the traditional military chain of command. They are not subject to the same rigorous standards of vetting and training as are members of our armed forces. Most importantly, ... the function of a private corporation is to make as much money as possible, not to serve the best interests of the people of the United States or our policies.
Sen. Sanders hits the nail on the head. Time after time after time, private security contractors in Iraq and Afghanistan have shown their inability to perform mission critical functions up to the military's standards by engaging in questionable conduct that severely damages the image of the United States abroad. Just as appalling, the offenders, more often than not, escape without sufficient reprimand, if they receive punishment at all. These events, both the abhorrent conduct and the lack of consequences, are even more harmful in the context of a counterinsurgency effort wherein the military is trying to protect and win over a foreign populous.
Phasing out security contractors, though, will likely prove a difficult task, both legislatively and logistically. Legislatively, the government contracting industry, especially the defense contracting industry – within which most security contractors reside – is an exceptionally powerful lobbying force. Faced with essentially the demise of their industry, the security contracting community, represented by influential groups such as the Professional Services Council and the Orwellian-named International Peace Operations Association, will fight tooth and nail against this bill.
Logistically, the government employed, at last count, roughly 22,000 security contractors in Iraq and Afghanistan. That's a lot of personnel, and while the legislation grants the federal government until the end of the year to replace all security contractors and permits the president a temporary waiver for agencies that can't make the transition deadline, it would be difficult for the government to ramp up hiring to fill those positions that fast. Indeed, the Defense and State departments have gradually transitioned to the use of contractors mainly because they didn't have an adequate number of personnel to carry out their missions to begin with and they view security contractors as a cost-effective substitute.
Reintroduction of the outsourcing bill comes at a propitious moment for Schakowsky and Sanders, as the Senate Armed Services Committee held a hearing this morning to investigate charges of corruption against Blackwater/Xe, an infamous security contractor. Whether the increased attention to this issue will help boost the bill's chances of passage is debatable, but one would think that security contractors could create only so many high profile foreign policy headaches for the United States before Congress stepped in to cut them off. With that said, the first time Schakowsky and Sanders introduced their bill in 2007 they had the Nisour Square massacre providing impetus, but the bill never progressed beyond the committee level in either the House or Senate.
The use of contractors in war zones is nothing new. The United States has used contractors even before the inception of the country in the days of the American Revolution, but the unprecedented expansion of security contractors, both in their numbers and the roles that they play, is dangerous for the U.S. Even if the government finds it impossible to move beyond the use of security contractors in the wars in Iraq and Afghanistan, I believe it's important for Congress to at least set down a set of policies for future contingency operations.
Image by Flickr user munir used under a Creative Commons license.
(Gary Therkildsen 02/24/10; 1 comment)On Friday, the White House met another Open Government Directive deadline by issuing a framework for federal spending data quality. The framework requires that agencies submit plans by April 14 for improving quality of their spending data, implementing internal controls and process changes.
Current challenges that need to be addressed such as missing data, duplicate data, and inaccurate data. The new policy is meant to meet some of these problems, but it doesn’t do so as completely or thoroughly as it might have. For instance, it doesn’t allow for independent data quality verification whether from inspectors general or by comparing the data to the Treasury Department’s disbursements.
According to the policy, OMB is to monitor progress through “potential” dashboards that will be publicly available. However, it doesn’t promise to make agency data quality plans public. How can we know how well the data verification process is if we don’t have the plan? Regardless, this is a positive step forward to ensuring consistency in data reporting.
Once the plans are received, OMB will provide initial feedback by April 30 and work with agencies to develop final plans which are due on May 14. Although the framework states that portions of the plans will be used to monitor agency implementation, they do not mention any mechanism to be provided to the public to report data and implementation problems.
(Roger Strother 02/15/10; 0 comments)
The office of the Special Inspector General for Iraq Reconstruction (SIGIR) released its 24th quarterly report on Saturday. If you haven't been paying attention to what's been going on in Iraq recently, it's worth a read. Besides providing observations on what's happening in the country and detailing the sources and uses of reconstruction funds, the inspector general's report also describes their recent oversight activities and successes in rooting out corruption within government contracting overseas.
Among SIGIR's investigations this past quarter, several are worth mentioning (details of each case are available in the report):
That's a pretty diverse group of people, which shows you how broad SIGIR's reach extends. In addition to these convictions, the inspector general's office has debarred a number of individuals and contractors, and has saved almost $82 million while redirecting another $230 million to better use because of their investigations.
The inspector general's office is currently operating with a $30 million budget in FY 2010, double what they had in FY 2009, and President Obama has asked Congress for $22 million in FY 2011. As the U.S. begins to withdraw troops from Iraq over the next two years – a period in which our resources will be particularly vulnerable to fraud and waste – SIGIR's presence will become vitally important and it makes sense to invest adequately in their mission.
Image by Flickr user The U.S. Army used under a Creative Commons license.
(Gary Therkildsen 02/03/10; 0 comments)The Office of Management and Budget unveiled President Obama’s FY 2011 budget request on Monday. Obama has decided to propose a spending freeze for discretionary, non-defense budget items. (See OMB Watch’s statement here.) Because Obama has proposed an overall freeze and not a line-item-by-line-item freeze, spending could be transferred to other areas to reflect administration priorities.
The FY 2011 budget is a mixed bag for regulatory agencies, many of which suffered from near-perennial raids on their coffers when President Bush was in power. In his first budget proposal submitted shortly after he took office, Obama tried to reverse some of the funding trends at regulatory agencies. His FY 2010 proposal was pretty good, but not great. As expected because of the spending freeze, the FY 2011 budget is a bit more subdued. Here is the run down.
Obama proposed almost $300 million in cuts to the Environmental Protection Agency’s budget for FY 2011 after an approximately $2.7 billion increase the year before. Interesting, however, is the “Clean Air and Global Climate Change” line item which gets a healthy boost to $540 million from $502 million. (Climate Science Watch also points out that Obama has proposed a hefty $439 million increase for the U.S. Global Change Research Program, which covers climate issues.)
Obama’s budget would raise the Food and Drug Administration’s budget by about $500 million, including industry-paid licensing and registration fees, a.k.a. user fees. That does not include an additional $289 million in new user fees currently under consideration in Congress, $220 million of which would go towards food safety. As for run-of-the-mill appropriations, Obama’s budget increases the food safety line item to $848 million, from $784 million. Reactions from food safety advocates are mixed.
As for the regulator of all things meat and poultry, the Food Safety and Inspection Service, the Obama budget calls for a modest $18 million, or 1.6 percent, increase, and only 31 additional employees.
The Occupational Safety and Health Administration would see a 2.5 percent increase under Obama’s proposal. But a look inside the numbers is more telling: The rulemaking division’s budget would rise to $24 million from $20 million – an important increase for an agency with an overwhelming rulemaking agenda. The budget takes away $3 million, or about 4 percent, from compliance assistance programs, which critics say are too lenient and did not deter bad behavior. Unfortunately, the Obama budget actually calls for a 51-person reduction in the OSHA workforce.
The Mine Safety and Health Administration’s budget would go from $356 million to $363 million. On the plus side, the Wage and Hour Division, which enforces minimum wage and child labor laws, among other worker rights issues – would see a $20 million, or 9 percent increase.
Last, but certainly not least, the Consumer Product Safety Commission. CPSC’s budget woes are probably the most well-chronicled of this lot. CPSC’s budget was halved (after adjusting for inflation) from the mid-1970’s to the 2000’s. Employment levels declined similarly.
But progress has been made in recent years, rising from about $63 million in FY 2007 to $118.2 million this year, plus about $4 million in industry fees. Last year, Obama proposed a minimal increase, which Congress improved upon. This year Obama is proposing a paltry $400,000 increase. For some obligatory perspective, the increase is about one half, of one millionth, of one percent, of the national defense budget. (Six zeros after the decimal, then a five.) The budget does call for an additional 46 employees, presumably because the agency can continue to absorb new hires because of the major funding increases in recent years.
The figures here are mostly taken from OMB budget documents, available here. The budget’s Appendix provides the most detail. Leave questions or discrepancies in the comments.
(Matthew Madia 02/03/10; 0 comments)
The folks over at Government Executive.com have the scoop on the Commission on Wartime Contracting's (CWC) recent move to open two field offices in Southwest Asia. The Iraq office, which is currently staffed by one expert and awaiting a second, is located in central Baghdad. Two experts staff the Afghanistan office, located at Bagram Air Field, which is roughly 25 miles outside the capital of Kabul.
The article quotes Robert Dickson, the commission's executive director, as stating that the staffers hired for these overseas posts "have decades of experience in construction management, military contracting, development projects, policy analysis, program management, and other work that ties directly to our research areas."
The piece also quotes Dickson as saying that these new offices will allow the commission to "maintain liaison with agencies and commands in theater, fill data requests from stateside staff, directly observe events on the ground, and assist with commissioners' research visits to the region."
It's hard to say to what degree these offices will affect the commission's future work, but my hope is that it will allow the CWC to dig a little deeper into the messes that are our contingency contracting environments in the two theaters of war.
Image by Flickr user The U.S. Army used under a Creative Commons license.
(Gary Therkildsen 01/29/10; 0 comments)
With the recent passage of President Obama's first anniversary in office, journalists, bloggers, and commentators have been sizing up the administration's accomplishments and failures thus far. In that spirit, Fox News, in an article examining a contract recently awarded under the Obama administration, concluded that the president has failed to keep his campaign promise of ending no-bid "sweetheart deals" in government contracting. To say that this verdict – which manipulated data from OMB Watch – is misleading and a bit premature is an understatement.
The contract in question is a $24 million award for "rule of law stabilization services" in Afghanistan. Fox News tells us that this contract warrants scrutiny because the recipient company is "owned by a Democratic campaign contributor," and the contracting agency, the United States Agency for International Development (USAID), awarded it without competition, which, according to Fox, proves that the president broke his campaign promise.
To start, let's separate the two issues that Fox News has conveniently tangled together here. The first issue is the "controversial" nature of the contract; that it is somehow a "sweetheart deal." Unless I missed something in the article, Fox has zero evidence that USAID awarded the contract based on the party affiliation or campaign contribution history of the top executive of the winning company. Indeed, a quick check of USASpending.gov reveals that the government has been contracting with the company for millions of dollars each year since 2002, not exactly a period of Democratic dominion in the executive branch.
Add to all this the fact that USAID made the award without competition because it was renewing a previous contract that the company had with the agency – a completely legitimate reason – and the controversy quickly falls away.
The second issue, which parts of the blogosphere have begun to regurgitate, is the president's campaign promise. President Obama never promised to end the use of no-bid contracts, he promised to end the abuse of them. Cynics might dismiss this distinction, but it's an important one that Fox News glosses over. No contracting analyst would honestly argue that the government could get rid of no-bid contracts; they perform an essential role in the government's repertoire of contracting vehicles. The president even said as much last March when he laid out his proposal to reform government contracting.
While I applaud Fox News for attempting to hold President Obama accountable and appreciate their use of the information we provide the public, they may want to do a little more research next time and make a better effort at getting their facts straight. And as far as campaign promises go, I would caution against concluding that the president has failed to end the abuse of no-bid contracts based on the non-competed renewal of a $24 million USAID award one year into his presidency.
Image by Flickr user Barack Obama used under a Creative Commons license.
(Gary Therkildsen 01/28/10; 1 comment)
On Tuesday, when the Federal Bureau of Investigation (FBI) arrested 22 executives from the military and police equipment industry on violations of the Foreign Corrupt Practices Act (FCPA), they nabbed a number of individuals that work for companies that contract with the government. Of the 16 companies represented, at least half received federal dollars for products or services during fiscal year 2009, and most of them have had a relationship with the government stretching back several years.
Below is a list of those arrested individuals that work for companies that contract with the government. Through the magic of USASpending.gov, I've included how many contracts the company has recently received and the dollar value associated with those contracts. Voila:
The contracts add up to over $200 million spent over the course of a decade for items like guns, ammunition, and body armor, from both large and small firms, some of which are quite well known.
As the Project on Government Oversight (POGO) notes on their blog, none of these companies has ever appeared in their Federal Contractor Misconduct Database, which POGO runs to keep track of transgressions by companies that contract with the government. And as of right now, the government has not implicated any of these companies in wrongdoing. But, the FBI investigation is ongoing and, as Professor Mike Koehler of Butler University states, "past FCPA enforcement actions demonstrate [that] corporate enforcement actions or investigations often, but not always, precede or follow individual enforcement actions."
The question is if these companies were somehow involved in a scheme to bribe a fictitious African minister of defense, should that have some bearing on whether they continue to receive taxpayer dollars through government contracts. I think most taxpayers would say yes. But, even if the government eventually charges these companies with some wrongdoing associated with this case, a federal contracting officer (CO) would likely never see this information in the future when attempting to make an award decision.
And that's because, along with being a fractured, siloed mess, the government's contractor performance databases don't reveal illicit behavior unless a company has admitted to it or accepted fault. This rarely happens, as most companies settle civil, criminal and administrative misconduct cases on the condition that they are absolved of any wrongdoing.
I'm not arguing that a company shouldn't receive a contract simply because it has broken the law in the past, but I believe a contracting officer should see all of a company's past so that the CO may make the most informed decision possible when awarding a contract. The wise spending of taxpayer dollars demands nothing less.
Image by Flickr user matthewbradley used under a Creative Commons license.
(Gary Therkildsen 01/22/10; 1 comment)FDA food safety officials want to increase the agency’s overseas inspection presence 20-fold, Congress Daily (subscription) reports today: “The Obama administration intends to increase the number of inspections of foreign food plants from 100 per year to 2,000 per year, a key FDA official said Wednesday.”
The official, Stephen Sundlof, said FDA wants to focus on listeria in imported dairy products. The initiative stems from fears that Chinese manufacturers do not safeguard against melamine contamination. In 2008, the chemical was added to baby formula, sickening, and even killing, infants in China. Melamine has been detected in other Chinese products, including pet food.
According to Congress Daily, “Sundlof also noted that there are 200,000 foreign plants that make food for the U.S. market and said FDA will also focus on the food safety systems in foreign countries.”
The FDA needs to be paying close attention to the food safety systems in other countries. In recent years, an increasing amount of foodstuffs has come from overseas – a trend that will surely continue. To date, FDA has not responded in kind, as is evidenced by the fact that the agency currently conducts only 100 inspections annually.
Since more inspections likely necessitates more inspectors and more resources, I’ll be anxious to see whether Sundlof’s comments are reflected in President Obama’s FY 2011 budget request scheduled to be released Feb. 1. Check back with the Fine Print for a rundown of FDA’s budget and the budgets of other regulatory agencies.
(Matthew Madia 01/21/10; 0 comments)