• Increase font size
  • Default font size
  • Decrease font size
Apogee Consulting Inc

Aviation Week Editorial Calls for “More Rigor” in Defense Audits

E-mail Print PDF

The October 18, 2010, edition of Aviation Week & Space Technology magazine carried an unsigned editorial entitled, “Put More Rigor Into Defense Audits”. Look, it’s one thing when POGO or a similar gadfly watchdog organization complains about lack of contract oversight. It’s an entirely different thing when the leading aerospace/defense industry magazine calls for the same thing. It means that things are getting serious.

The AW&ST editorial started out with a bang, saying “Lost in the debate about U.S. defense spending … is the glaring fact that no one knows precisely where the money is being spent or even how much is being spent.” The editorial explains the root cause for this lack of knowledge: “One reason such calculations involve so much guesswork is because defense audits—whether for the whole department or one program—are often incomplete, error-laden or biased.” [Emphasis added.] Amen brother!

The editorial explores the well-known (to our readership, at least) criticisms of DCAA by “congressional auditors” and Senator Claire McCaskill. The editorial explains—

Congressional aides and auditors say changes are being made, but … doubts remain about the government’s own agencies that monitor program management. Just recently, the Congressional Research Service renewed a warning about Navy accounting in pursuing its 30-year, 313-ship plan. The Navy estimates the plan will require an average of $15.9 billion per year in today’s dollars to implement, but the Congressional Budget Office—which has a better track record—says it is more like $19 billion per year. How can two sets of professionals using accepted accounting principles be off by a whopping 19%?

But DCAA and the Navy are not the only targets of AW&ST’s wrath. The magazine also had some choice words for Lockheed Martin and its EVM System. Readers may recall our previous article, which discussed the Government’s disapproval of LockMart’s EVM System. The AW&ST editorial asserted that the decertification of LockMart’s EVM System is “the latest example of insufficient discipline” and rigor. The editorial asked, “When contractors cannot even implement the tool correctly, is it any wonder that so many lawmakers, lobbyists and others believe they can challenge the Pentagon’s programmatic decisions?”

As the editorial noted, by decertifying the F-35’s EVM System, “In a nutshell, the Pentagon is publicly questioning the internal cost and schedule management at its largest contractor in managing its largest program … as well as its own seriousness in responding to government oversight.”

The AW&ST editorial concluded—

It would be easy to chide the Defense Department and its contractors to get their numbers straight. Such calls have been issued for years. The Lockheed EVM rebuke, however, is concrete evidence of officials holding contractors accountable for shared work. Lockheed should take it seriously and get its house in order. Moreover, the Pentagon should not hesitate to call other contractors into question publicly when it finds hazy or lax management controls elsewhere.

One recurring theme on this website is the call for corporate leadership to invest in appropriate internal controls and internal oversight, to get its own house in order before DCAA and/or DCMA level criticisms, and before the Department of Justice demands serious cash for criminal wrongdoing by “rogue” employees. It’s one thing to read rants at this site. It’s one thing to read rants at POGO. But it’s quite another thing entirely to read near-rants from Aviation Week & Space Technology, calling-out one of its largest advertisers, and demanding enhanced oversight and public branding of miscreants.

We’ve been warning you for years. Here’s another warning, courtesy of Aviation Week & Space Technology magazine. How many times do you have to read the same rants from different sources before you start to take them seriously?

 

Russia Gains New Satellite Launch Capability from Boeing

E-mail Print PDF

Sea Launch

In 1995, Sea Launch was created. According to this Wikipedia article, Sea Launch “is a spacecraft launch service that uses a mobile sea platform for equatorial launches of commercial payloads on specialized Zenit 3SL rockets.” The article explains, “The sea-based launch system means the rockets can be fired from the optimum position on Earth's surface, considerably increasing payload capacity and reducing launch costs compared to land-based systems.”

Originally, Sea Launch was a consortium comprised of Energia Overseas Ltd., a subsidiary of the Russian aerospace “giant” Energia (25% ownership), a Boeing subsidiary (40% ownership), Norwegian company Aker ASA (20% stake) and Ukraine’s SDO Yuzhnoye/PO Yuzhmash (15% ownership). Boeing managed the consortium. Since 1999, Sea Launch has had 27 of 30 successful satellite launches. But the financial seas of the commercial satellite launch business were rough and the consortium ran into problems. As one report explained—

One of the chief uncertainties before Sea Launch's mid-2009 filing for Chapter 11 bankruptcy protection was the Ukrainian Zenit rocket supply chain. According to court filings, the global financial crisis, a catastrophic launch mishap in 2007, and late equipment deliveries and cash payments triggered several serious delays.

In June, 2009, the company announced it was filing for Chapter 11 bankruptcy protection. In July 2010, Energia subsidiary Energia Overseas Limited (EOL) acquired a controlling 85% ownership stake in Sea Launch by a bankruptcy court ruling. The Committee on Foreign Investment in the United States (CFIUS) cleared the new ownership on September 8, 2010.

Effective October 27, 2010, Sea Launch emerged from Chapter 11 reorganization “debt-free” and “under majority Russian ownership”—according to this article at SpaceFlightNow.com. The company plans to resume satellite launches in 2011. The reorganized company will have more Russian involvement. For example, “an Energia affiliate in Moscow will oversee the supply chain in Russia and Ukraine,” and “Energia Logistics Ltd., a U.S. corporation, is taking over management of rocket and satellite operations in Long Beach.” Moreover, land launches “are managed by Space International Services Ltd. of Moscow.”

In prior articles, we noted that Russia was “resurgent” and playing a larger role on the world’s aerospace and defense stage. Although its bid to build the next generation USAF aerial tanker was lost through a series of missteps, Russian management of Sea Launch indicates that it is a player, and should be taken seriously.

 

Micro-Stories: Small Biz Fraud and FCPA Follow-up

E-mail Print PDF

We’re on TDY so were going to have to make this quick. Here are a couple of stories that our readers might find to be of interest.

Small Business Fraud

Our steady fountain of news stories, the Department of Justice, comes through again for us, with the announcement that “Maryland contractors and their president to pay United States for falsely obtaining Hubzone and SBA 8(a) contracts.” What’s the beef? According to the DOJ—

The United States alleged that Platinum One and Anthony Wright falsely represented to the SBA, the Navy and the Army that Platinum was controlled by a socially and economically disadvantaged individual. The government’s investigation found that Platinum One was actually controlled by Vernon J. Smith III, who is not socially or economically disadvantaged. The government alleged that Smith used Platinum’s 8(a) status to continue Capitol Contractor’s business operations after Capitol’s own 8(a) status expired in 2002. As a result of these false representations, Platinum obtained contracts from the Navy and the Army.

The United States also alleged that Platinum One and Anthony Wright falsely represented to the SBA and other government agencies that Platinum maintained its principal office in a designated HUBZone location. In fact, Platinum actually operated out of offices owned by Capitol that were not located in a HUBZone. Platinum One did not qualify for the HUBZone program, yet because of its false statements to the SBA and the Air Force, it obtained contracts that had been set aside by the Air Force for qualified HUBZone companies.

That little faux pas cost the companies and their President $200,000 “to settle claims that they used false statements to obtain contracts from the Department of Defense.”

BAE Systems Auditor is Audited

We previously reported about BAE Systems’ settlement(s) with UK and USA government entities for, among other things, false statements related to internal control adequacy and management’s commitment to ethical business conduct. At the time, we noted the statement of the BAE Systems CEO that the wrongdoing all took place “nearly a decade ago.” So that’s all water under the bridge, right?

Nope. The other shoe has dropped, and it’s dropped right on the head(s) of BAE Systems’ external auditors, KPMG. As one of our favorite sites, GoingConcern.com reported—

Yesterday, the Accountancy and Actuarial Discipline Board (AADB) in the UK announced that they would be reviewing a decade’s worth of audits performed by KPMG for BAE Systems, the British Defense Contractor. … So now, presumably because they thought it would be fun, the AADB is curious about what KPMG knew about these ‘commissions’ and ‘third parties’ … Well! The prospect for unlimited fine is interesting, to say the least. For their part, KPMG is cooperating with the investigation because, well, what else are they going to do? A spokesman told Reuters, ‘[T]he firm does not believe there has been any act of misconduct [and that] it will be cooperating fully with the AADB to ensure that the matter is brought to a swift conclusion,’ which, as we all know, runs on an audio loop on the firm’s automated press inquiries line. … The thing is, KPMG’s (or any accounting firm) involvement with BAE (or any defense contractor) has to be one of mixed feelings.

On the one hand, you’ve got extremely profitable international businesses that build all these cool toys that fly, blow things up and go into space. On the other, a lot of their customers are the shifty type, they probably keep lots of secrets and – OH YEAHtheir products are designed to kill people. But once you get passed all that, you realize it’s simply a business needing professional services and who better to provide it than a Big 4 firm, amiright?

Taking what many might consider a less casual approach to reporting the story, Reuters had this to say—

Audits covering the 10 years between 1997 and 2007 will be investigated, as well as ‘commission payments paid by BAE’, Britain's Accountancy and Actuarial Discipline Board (AADB) said in a statement posted on its website on Monday.

The AADB has begun an investigation under its accountancy scheme into the conduct of KPMG Audit plc as auditors to BAE Systems plc,’ the regulator said. …

AADB said it would investigate KPMG's advice to BAE on the operations of three of its offshore companies, Red Diamond Trading, Poseidon Trading Investments and Novelmight. ‘The regulator is looking specifically at the audit of commissions paid by BAE to outside agents, any tax advice given by KPMG on commission payments and the status of three offshore companies linked to BAE ... penalties could include an unlimited fine for KPMG,’ said Credit Agricole analyst Thomas Mesmin.

And as you ponder the idea of the auditor being audited, we wish you good day.


 

Text Messaging is a Contract Compliance Issue

E-mail Print PDF


 

We recently spent six enlightening hours listening to Washington, D.C., attorney Stephen Knight, of the firm Smith/Pachter/McWhorter PLC, discuss recent regulatory changes that might affect government contractors. Some of what he discussed was already familiar to us, and we’ve published articles on those topics on this website. But there were new things to learn as well (as one might expect from such an accomplished legal practitioner), and we want to share one of them with you today. It’s about the contract compliance issue(s) associated with text messaging while driving.

Now, we confess that when this interim rule was issued in late September 2010, we didn’t take much notice. After all, California and other states already prohibit such unsafe practices. So what’s the big deal? Well, Stephen explained the big deal and we’re going to try to explain it to you.

Federal Acquisition Circular 2005-46, published September 29, 2010, contained several proposed and final FAR revisions. Amongst those revisions was FAR Case 2009-028, issued as an interim rule. As the FAR Councils explained, “This interim rule [implements] Executive Order 13513, issued on October 1, 2009 … entitled “Federal Leadership on Reducing Text Messaging While Driving.” The interim rule revised FAR Part 23 and implemented a new subpart at 23.11 (“Encouraging Contractor Policies to Ban Text Messaging While Driving”).

Helpfully, the new rule provides definitions for challenging concepts, such as the term “driving” and the term “text messaging”. You may be relieved to note that the definition of “text messaging” “does not include glancing at or listening to a navigational device that is secured in a commercially designed holder affixed to the vehicle”. However, that exception only covers the situation when “the destination and route are programmed into the device either before driving or while stopped in a location off the roadway where it is safe and legal to park”. Otherwise, you are (apparently) not permitted to listen to your navigation device—nor are you (apparently) permitted to use your smart phone as such a device, unless it is “secured in a commercially designed holder affixed to the vehicle”. Okay, we could go on but you get the point—this is a bit of a bureaucratic joke.

What’s not funny is the new contract clause (52.223-18) that came along with the new rule. It states—

(c) The Contractor should--

(1) Adopt and enforce policies that ban text messaging while driving--

(i) Company-owned or -rented vehicles or Government-owned vehicles; or

(ii) Privately-owned vehicles when on official Government business or when performing any work for or on behalf of the Government.

(2) Conduct initiatives in a manner commensurate with the size of the business, such as--

(i) Establishment of new rules and programs or re-evaluation of existing programs to prohibit text messaging while driving; and

(ii) Education, awareness, and other outreach to employees about the safety risks associated with texting while driving.

Moreover, the contract clause is a mandatory flow-down for “all subcontracts that exceed the micro-purchase threshold”.

Need we point out that, in order to comply with the new contract clause, your company may well have to develop new policies and procedures to “prohibit” the undesirable behavior, and will need to educate employees about the new policies and procedures? And you are going to have to perform some level of due diligence on your subcontractors to make sure they are complying with the new rules.

The foregoing really is no laughing matter. In this environment of cost-consciousness, you’re going to have to modify existing HR or ES&H policies and conduct even more employee training.

So now you know.


 



 



 

Backlash from Changes to Proposal Audit Thresholds

E-mail Print PDF

We first told you about changes to the DFARS PGI—changes that limited DCAA’s audits of contractor cost proposals—in this article. We are proud to claim to be one of the early reporters of the story, breaking it two weeks before other outlets reported it. To recap, we reported (with approval)—

What we see in the foregoing is a movement towards limiting DCAA’s role in DCMA proposal analysis. Fixed-price proposals valued at less than $10 million normally should not be reviewed by DCAA. Similarly, cost-type proposals valued at less than $100 million normally should not be reviewed by DCAA.

Well, other outlets finally caught up with the story, and they did not exhibit the same approval as we did.

First, the Project on Government Oversight (POGO) published an “alert”—or what might also be termed a “rant”—with the inflammatory title, “Pentagon Radically Reducing Oversight of Contracts Worth Tens of Billions”. The POGO rant linked to an October 18, 2010 MRD from DCAA (MRD 10-PSP-030(R)) that transmitted news of the PGI revisions to the agency’s auditors. There was nothing new in the DCAA audit guidance, but POGO made it sound like an insidious conspiracy was at work. POGO rhetorically asked its readers—

POGO has long feared contractors and their government allies would block DCAA from exposing contractor ripoffs,’ said Nick Schwellenbach, POGO’s director of investigations.  ‘Why are billions of dollars being put at risk when Secretary Gates is demanding cost savings?’

In addition, POGO reported—

The reason for this new restriction is DCAA’s attempt to perfectly comply with Generally Accepted Government Auditing Standards (GAGAS). With this standard, which requires meticulous documentation of findings, DCAA is unable to cover as much ground as they used to, thus the need to restrict ‘audits’ as defined by GAGAS.  The number of DCAA reports produced annually has plunged: 33,801 in FY 2007 to 30,352 in FY 2008 to 21,276 reports in FY 2009.

Rather than subjecting reviews of cost or pricing data to GAGAS, DCAA should consider these reviews as financial advisory services, which are not subject to all GAGAS requirements.  This would better protect taxpayers and warfighters by allowing DCAA to review cost data and deliver advice to contracting officers in a timely fashion.

We have a couple of thoughts on POGO’s rant. First, it is absolutely misleading to assert that oversight over DOD contracts is being reduced. That is not the case. In fact, what is being reduced is DCAA’s review of bids submitted to DOD. Some of those bids might become future contracts, in which case they will be subject to the full panoply of the Pentagon oversight regime. Until that time, DCAA’s review is simply to assist the DCMA Contracting Officer is preparing for negotiations. DCMA is the customer and it can request (or not request) DCAA review. In this case, the two DOD agencies are mutually agreeing that certain proposals will not be subject to DCAA review—which frees up audit resources to focus on larger and/or higher risk proposals. This is a good thing, though POGO makes it sound as if the criminals are being freed from jail.

Second, we actually agree with POGO that DCAA should exempt certain of its activities from GAGAS. In fact, we recommended that nearly a year ago, in this open letter to DCAA Director Pat Fitzgerald. So (to reword a bit) we are pleased to see that POGO agrees with our recommendation.

Robert Brodsky at GovExec.com was more restrained in his reporting (as we have come to expect from him). He reported—

In a statement, a Defense Department spokeswoman said the change will allow DCAA to focus on the highest-risk areas, and ‘actually increase savings to the department and warfighter.’ … The redistribution of audit assistance work came as no surprise to observers who have tracked DCAA's response to a stinging 2008 Government Accountability Office report. The watchdog found DCAA auditors often failed to comply with generally accepted government auditing standards, documented their audit opinions improperly and submitted sloppy working papers.

But, some auditors suggested DCAA managers overreacted to the report, and they now have embraced the time-consuming GAGAS process for all audits and reviews of cost data in contractor proposals. The result has been that reports take longer and require a field office manager's approval. Often contracts are issued before the DCAA reviews are complete.

Once again, we are pleased to see our position(s) agreed-with. In this article, we asserted, “So perhaps it’s not really the workload that’s causing ‘lingering audit problems,’ but might be instead the process by which audits are being executed?“

As always, comments on the GovExec.com site, from purported DCAA auditors, are brutal but illustrative. Here are a few of them for your edification:

  • Every audit takes longer to complete and then do over after the rules on what the agency expects change every other week. We don't audit really, we access risk for weeks, document sampling plans that are crazy and document work papers to a level of insanity. Once an audit is actually complete, the rules on how to do an audit change again. Then after four levels of review, no one wants to issue it anyway. But don't worry, by this point the contract has been awarded and we can cancel the assignment so no one gets Gigged. I have to believe that the people writing the audit guidance for proposal audits have never actually done one of these audits. Forward pricing proposals, should not be audited to GAGAS!!!!! Does anyone know how insane it is to tell a contractor that your unsupporting all their out year indirect rates for lack of budgetary data but by the way I want to test your pool and base amounts anyway for the current year? It will take me two weeks to document that sample plan and then you can pull the 750 transactions I need to look at. But don't worry by the time I'm done the contract will be awarded and most likely the assignment canceled. The report will never leave the DCAA family. Has anyone requested a basic assist audit from another DCAA office in the past nine months? Am I the only one who has noticed that basic requests for audit assistance, do not even get acknowledged anymore? How can they be acknowledged when the agency is in melt down mode? People are too busy documenting work papers to ever acknowledge a basic request for an audit. Why acknowledge it, when you know you never will issue it anyway?

  • All I can say to this is...What the #$%^? I don't even have a clue when I will get an audit back from DCAA...now they tell me that they will not look at a cost proposal under $100M.. We might as well terminate DCAA's charter and desolve their workforce because I'm lost on their utility for the majority of DOD actions.

In response to the foregoing (unwarranted and uneducated) criticism, DOD is trying to explain itself. This article at WashingtonTechnology.com reported—

The Project on Government Oversight watchdog group called it a “radical” reduction in the contracts to be reviewed, saying about $92 billion a year in contracts would be affected.

But defense officials believe the change will focus resources on high-risk areas and increase savings to the department.

Defense Procurement Acquisition Policy, in coordination with the acquisition community and DCAA, made the change to the Defense Federal Acquisition Regulation Supplement,’ reads a statement distributed by a DOD spokeswoman on Nov. 1.

DCAA is working with the acquisition community to align our resources with the highest risk areas. DCAA believes this change will allow them to focus on audit areas with the greatest payback to the taxpayer and will actually increase savings to the Department and warfighter. Finally, DCAA has coordinated this change with DCMA, and are confident that they will be able to provide the necessary pricing coverage for the procurements below the threshold,’ the DOD statement said.

To sum up, the inflammatory and highly misleading tack taken by POGO is being picked up by other media outlets, and generating utterly unwarranted criticism aimed at the DOD. While there are some good points being made (i.e., those that agree with our previously published positions and recommendations), there is much nonsense being spouted as well.

As educated and experienced readers of this site, you know better.


 


Page 218 of 278

Newsflash

Effective January 1, 2019, Nick Sanders has been named as Editor of two reference books published by LexisNexis. The first book is Matthew Bender’s Accounting for Government Contracts: The Federal Acquisition Regulation. The second book is Matthew Bender’s Accounting for Government Contracts: The Cost Accounting Standards. Nick replaces Darrell Oyer, who has edited those books for many years.