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

DOD Office of Inspector General Criticizes Contracting Officers (Again)

E-mail Print PDF

This blog has been active for more than ten years. That’s a decade of reporting observations and opinions about what we have seen in the Federal acquisition environment.

For much of that time, we’ve observed the Department of Defense Office of Inspector General (DOD OIG) criticize the contracting officers of the Defense Contract Management Agency (DCMA). Some of that criticism has been warranted, to be sure.i However, in our view (as expressed time and time again on this blog) much of the criticism has not been fair, or has been the result of sloppy (or even misleading) audit procedures that seemed designed to generate headlines and Congressional support rather than report an independent and objective conclusion. Much of that OIG criticism has been directed at contracting officers who deviate from Defense Contract Audit Agency (DCAA) audit findings without an adequately documented rationale.

For us, the bottom-line has been that DCMA contracting officers are charged with using independent business judgment to resolve administrative disagreements before they ripen into disputes. This is the policy of the United States Federal government, as expressed in Federal Acquisition Regulation 33.204. The policy is clear: “The Government’s policy is to try to resolve all contractual issues in controversy by mutual agreement at the contracting officer’s level. Reasonable efforts should be made to resolve controversies prior to the submission of a claim.”

The rationale for that policy position should also be clear: litigation wastes time and resources of both sides. The government simply does not have sufficient attorneys to litigate every disagreement, nor do contracting officers have sufficient time available to support those attorneys. Discovery efforts are lengthy and painful. Depositions are lengthy and painful. Going to court is often a crapshoot, and often bad precedents are set based on bad fact patterns. This is true for both sides, and thus both sides have a vested interest in avoiding litigation wherever possible.

Yet it seems that the auditors from the DOD OIG don’t see it that way. Based on the various audit reports we’ve seen (and discussed here), the OIG auditors seem to think that the use of independent business judgment should be curtailed unless the contracting officer has (1) reviewed all positions with legal support, and (2) documented all deviations from the initial DCAA audit positions.

Lost in this kerfuffle is the fact that DCAA audit positions are not always correct. Just before this blog started, you would have to go a long way to find anybody who thought DCAA’s audit conclusions were accurate or well-supported. It was the DOD OIG itself that leveled quite a bit of criticism at the DCAA audit procedures. Not to mention all the Congressional hearings. There was a real (and valid) belief at the time that DCAA as an audit agency had overstayed its welcome within DOD, and that DCMA contracting officers had better find alternate means of getting field pricing assistance or incurred cost audit assistance. That DCAA has come back from the brink is laudable—but its reputation was tainted and, for many, remains tainted to this day.

Thus, there is a tacit or even overt understanding that DCMA contracting officers will not always agree with DCAA audit findings—nor do they need to. As then-DCMA Director Charlie Williams expressed it to his contracting officers in 2011, with respect to forward pricing rates—

Working closely with DCAA auditors is a critical factor in your ability to be successful in the final outcomes that result from your rate decisions. … it is our policy that when you receive an audit report from DCAA, you should use the audited rates as the single government forward pricing rate recommendation. While this is policy, you will not find anything that states, ACOs should ignore common sense or relinquish their discretion in promulgating FPRRs. So simply put, it is my expectation that ACOs should always apply judgment and well informed thought prior to making any decision. I fully expect that there will be times when the contracting officer determines, in his or her judgment, that the rates contained in the audit may not be the best representation of future projections. When that judgment is well informed by fact and data, you must not be reticent or feel constrained in communicating your views with the auditors and if necessary requesting a Board of Review to elevate real differences.

But that was then and this is now.

Today, the DOD OIG criticizes DCMA contracting officers for using “common sense” and “discretion” to resolve differences in opinion between contractor and DCAA. And that is the relationship: DCAA has expressed a conclusion, the contractor disagrees, and it is up to the contracting officer to try to resolve that disagreement before it leads to litigation. Or, as the Claims Court stated: “[T]he contracting officer must act impartially in settling disputes. He must not act as a representative of one of the contracting parties, but as an impartial, unbiased judge.”ii

Despite the foregoing, DOD OIG auditors don’t see it that way. The latest manifestation of their concerns is Report No. DODIG-2020-049, a redacted version of which was issued January 10, 2020. In that report, the OIG auditors criticized 18 (of 28) contracting officers for failing to “adequately explain why they disagreed with DCAA’s recommendations to assess penalties on $43 million in unallowable indirect costs.” More specifically—

  • For $32 million, the contracting officers determined that the costs were not subject to penalties. However, the DCMA contracting officers did not document adequate rationale for disagreeing with DCAA that the costs were unallowable and subject to penalties.

  • For $11 million, the contracting officers determined that the costs met the FAR criteria for waiving penalties. However, the DCMA contracting officers did not document adequate rationale to show that the DoD contractor met the FAR criteria for waiving penalties.

Thus, according to the OIG auditors, “the contracting officers did not comply with the FAR requirement that contracting officers document adequate rationale when they disagree with DCAA recommendations.”

Because of the alleged violations of FAR requirements, “DCMA will review the 18 DCAA audit reports in which contracting officers did not document adequate rationale and attempt to recoup any unallowable costs and assess penalties and interest.” So if you are one of those 18 contractors who thought you had settled your final rates, you may want to think again.

We would say more but we think we made our point. It very much seems to us that any attempt by DCMA contracting officers to use their judgment and discretion to resolve controversies before they become full-fledged disputes will be met with criticism from the DOD Office of Inspector General.

 

i Pun fully intended.

ii Penner Installation Corp. v. United States, 89 F. Supp. 545, 547 (Ct. Cl. 1950); aff’d by an equally divided court, 340 U.S. 898 (1950). Cited in Atkins North America & Mactech Engineering and Consulting v. US, No. 09-112 C (Ct. Cl. Aug 30, 2012); motion for interlocutory appeal denied.

 

Researching DFARS

E-mail Print PDF

Most of us would agree that the FAR is hard enough. But sometimes you have to go into the DFARS; and it turns out that is harder than it needs to be.

Recently I team-taught a class in England that was, essentially, an introduction to the FAR and the DFARS. A company had received multiple subcontracts from various US prime contractors, each of which contained a lengthy list of FAR and DFARS clauses—most of which had been incorporated by reference. Meaning that there was a clause number and a clause title and a date. And that was it.

An important exercise was looking up the clauses and their prescriptions. (For those who don’t know, the prescription tells the contracting officer when the clause is to be incorporated into a contract.) We also looked at the clauses themselves in order to identify whether the clause was a mandatory flow-down and, if so, then under what circumstances.

We taught the class that some DFARS clauses implemented a FAR clause while other DFARS clauses supplemented a FAR clause. (For your information, an implementation augments the FAR rule while a supplementation adds additional stuff not found in the FAR.) There are specific conventions that identify implementing clauses versus supplementing clauses, but you’re already bored so we’re moving on now.

In short, there was a lot of moving back and forth between the FAR and the DFARS, so as to see whether the FAR clause controlled, or if it had been modified somehow by the DFARS.

How did we do that? We did it electronically, using various websites.

Now, you might think that only one website would be necessary. Effective 30 September 2019, “Acquisition professionals and vendors will … have a single website to access and search the Federal Acquisition Regulation (FAR) and supplemental regulations.” And that website is www.acquisition.gov.

If you go to that site, on the very top of the page is a button marked “Regulations,” and clicking that button brings up all the various government acquisition regulations, from the FAR to the DFARS and even the military service supplements. The list of acronyms is amazing! Do you know what the DOLARS is? What about the LIFAR? Or the NRCAR? You get the picture.

Thus, if the site is to be believed, it’s a one-stop shop and one need go nowhere else. Yet we hardly used it.

Sure, as far as FAR research went, it was fine. But when navigating the DFARS, the site was lacking. It just didn’t work. The links between the DFARS clauses and their prescriptions didn’t. Or at least, they didn’t (link) consistently. The lack of effectiveness of the DFARS section of www.acquisition.com made me long for the days of farsite at hill.afb.org. That website worked and it was easy to navigate. But sadly, it’s no longer in existence.

So what did we do instead? We used the electronic Code of Federal Regulations website at www.ecfr.gov. Once you know that the FAR is Title 48 of the CFR and that the DFARS is Chapter 2 of Title 48, then you’re good to go. And the eCFR has really cool search features that turned out to be really useful.

We needed strong search features because of this little ditty buried in the DFARS clause 252.244-7000 (“Subcontracts for Commercial Items,” June 2013). That clause states:

  1. The Contractor is not required to flow down the terms of any Defense Federal Acquisition Regulation Supplement (DFARS) clause in subcontracts for commercial items at any tier under this contract, unless so specified in the particular clause.

What does that mean? It means that the only DFARS clauses that are mandatory flow-downs for subcontracts for commercial items are those clauses that expressly require flow-downs to subcontracts for commercial items. Let me give you an example. Suppose a clause states “Contractor must flow this clause down to all subcontracts.” That clause would not be a mandatory flow-down to a subcontract for commercial items because it does not expressly say “… all subcontracts, including those for commercial items.”

That’s right. “All” does not mean “all.”

Right. That blew my mind as well. But there you go.

I know, you’re thinking I’m crazy. Here’s an example of what I’m talking about. If you look at the DFARS clause 252.229-7014 “(Taxes-Foreign Contracts in Afghanistan,” December 2015) you see this clear direction to contractors that have received contracts that incorporate that particular clause: “(e) The Contractor shall include the substance of this clause, including this paragraph (e), in all subcontracts, including subcontracts for commercial items.” (Emphasis added.) If you see that direction, then you know the clause is a mandatory flow-down for subcontracts for commercial items. If you don’t see that, then the clause is not a mandatory flow-down.

If you think this is crazy hard (and you should), you should have seen the faces of the British folks we were training. (It took a couple of days, but they all got it in the end.)

Fortunately, we had the eCFR site so we could search for the clauses that needed to be flowed-down. Because if we had relied on the www.acquisition.gov site for the training, it would have been impossible.

 

DCAA Statistics

E-mail Print PDF

As we come to the end of 2019, I first wanted to thank readers for their patience. This has not been the most productive year as far as blog posts are concerned. In fact, it’s been the least productive in the 10 years the blog has been active. That’s not to say that we haven’t been productive in other areas, but focus on those other areas has meant that blog output has suffered. So thank you for hanging in there.

Now: to the blog post.

Over the past 10 years, the most popular articles have always been about the Defense Contract Audit Agency. Many people seem to be interested in what we have to say about DCAA. Contractors, contracting officers, and even DCAA auditors themselves seem to want to learn more about our thoughts on what DCAA is up to and how the audit agency is doing.

From time to time, we publish DCAA statistics. You can see the statistics manifested in the previous two blog posts. Where do those statistics come from? They come from official government publications—primarily the Department of Defense Office of Inspector General’s Semi-Annual Report to Congress, and from DCAA’s own Annual Report to Congress. We have been tracking audit-related statistics for many years and now have 13 years’ worth, which makes for interesting trend analysis.

Let’s look at those trends.

First, audit reports. Audit reports mean that contractors have to respond. Audit reports mean that contracting officers have to disposition and decide whether or not to sustain. Audit reports can lead to disputes and litigation. The following chart shows audit reports by type by year.

dcaa_audit_reports_type

An interesting thing happened circa 2010. DCAA started tracking a metric called “assignment completed”—which meant that a certain number of assignments were completed without issuing an audit report. Typically, those assignments were closed via a Memorandum (either to the contracting officer or to the DCAA’s files). A completed assignment is what you get when DCAA chooses not to audit your proposal to establish final billing rates (aka incurred cost submission). A completed assignment is what you get when there are no findings and the exit conference is via telephone. As a rule, contractors like completed assignments with no audit report. So do DCAA auditors, as it means it’s harder to find GAGAS violations. We’re sure it was a coincidence that DCAA starting moving to the “completed assignment” metric at about the same time the audit agency was coming under heavy criticism for GAGAS violations.

The following chart shows the percentage of assignments completed without an audit report since DCAA started tracking that metric.

assignment_no_report

As you can see from the chart above, in GFY 2019 nearly three-quarters (74%) of all DCAA assignments were completed without issuance of a formal audit report.

Another interesting metric is the value of dollars examined by DCAA auditors each year. The following chart compares dollars examined against staff years. We don’t have GFY 2019 staffing yet (it’s typically published in March of the following year) so the chart tracks only through 2018.

dollars_examined_staffing_levels

The chart above shows that DCAA was at its most productive in 2008, when about $113 million was examined per auditor (or per audit staff year, depending on what data was being reported). On the other hand, that focus on productivity was blamed for audit quality failures. (There was no evidence showing that was the case, mind you. But that’s what people said and that’s what Congress glommed on to.) Consequently, audit productivity fell as the agency focused on quality. (Which tended to manifest as a lot of management reviews.) According to DoD OIG reports, audit quality did not significantly increase as the result of the focus on process instead of productivity. Nonetheless, the data indicate a dramatic loss of productivity.

At about the same time, audit staff headcount (or staff years) started to vary. GFY 2018 audit headcount is about 10 percent below the highs reflect in 2010 and then again in 2014. (Again, the data is a bit fuzzy because sometimes it’s reported as headcount and other times as staff audit years, which we assume includes audit hours performed on overtime. But you get the picture.)

It is only recently – GFY 2018 – that auditor productivity has returned to 2008 levels. In GFY 2018, auditors were examining about $99 million per head. Since we don’t have GFY 2019 staffing levels, we can’t conclude anything, but we can state that total dollars examined in GFY 2019 was lower than in 2018 ($365M vs. $410M). Consequently, unless headcount dropped significantly, it seems likely that GFY 2019 productivity will be below GFY 2018 levels.

What does this all mean?

Well, it may mean nothing. Or it may mean that DCAA’s strategy of completing assignments without issuing an audit report (but counting those assignments as dollars examined) may lead to a perception of increased auditor productivity.

Thus, as Apogee Consulting, Inc., blog productivity has declined in recent years, it appears that DCAA’s audit productivity is on the increase. Maybe our strategy should change to align with DCAA’s strategy? If so, then we will start posting blogs with no content and then claiming a completed blog post.

Yeah, that’s the ticket.

 

Good-Bye 2019, We Hardly Knew Ye

E-mail Print PDF

Last blog post for the year, and what a year it’s been.

There were eight Federal Acquisition Circulars (FACs) published. They included both proposed and final rules. In addition, there were several proposed and/or final FAR revisions published outside of the official FACs. Looking back, not many of the rules—whether proposed or interim or final—seemed especially significant. The definition of “commercial item” was expanded. The prohibition on obtaining certified cost or pricing data was restricted (but not for all agencies). Procurement of telecommunications equipment from Huawei Technologies Company or ZTE Corporation was prohibited. In summary, not a particularly eventful year.

DCAA published three Memoranda for Regional Directors (MRDs), continuing its unfortunate trend of hiding a lot of its audit guidance behind agency firewalls. However, what was published contained potentially significant changes to how DCAA uses materiality in its audits of contractor final billing rate proposals (aka incurred cost submissions). In addition, DCAA continued to build its “Selected Areas of Cost Guidebook” (which replaced what used to be Chapter 7 of the Contract Audit Manual); and DCAA also revised quite a few of its audit programs—most notably the 11070 audit program for performing Accounting System audits. Thus, it’s not fair to judge DCAA solely on its output of MRDs; one should strive to look at the total output.

Speaking of DCAA output, we’ve devoted a few recent blog articles to discussing DCAA productivity. In Government Fiscal Year 2019 (which ended 30 September 2019), the audit agency examined $365.2 billion using procedures that resulted in a GAGAS-compliance audit report. If we subtract out audit reports related to audits of contractor proposals, that figure drops to $246.3 billion. (Since the audit agency only issued audit reports in 26 percent of the assignments it completed, we can infer that roughly $950 billion was examined in non-proposal audits, in total).

Of the $246.3 billion that was reported upon, about $1.94 billion was questioned in an audit report (a figure that excludes “funds put to better use,” which is how DCAA reports findings related to proposal audits). Thus, DCAA questioned less than one percent of all dollars examined.

How did Apogee Consulting, Inc. fare in 2019? Let’s recap.

  • 51 blog articles published (counting this one)

  • 2 textbooks edited for ThompsonWest/LexisNexis

  • 1 six-week adult education class created and taught

  • 1 presentation for the Society of Corporate Ethics and Compliance

  • 1 presentation for the Association of Government Accountants

  • 1 presentation for the National Contract Management Association

  • Participated in roundtable discussion at the Rocky Mountain Compliance Conference

  • Participated in roundtable discussion at the BDO/Deltek Government Contracting Seminar in San Diego

  • 1 article drafted for publication (will be submitted in January)

  • Testified in an arbitration proceeding

Thus, while blog article production fell precipitously, we made up for it in other areas.

Looking forward to 2020, we know we will be editing the two textbooks again. We have submitted a proposal to SCCE for another presentation. We expect to teach at SDSU once again. Our first 2020 engagement starts January 6th, and we hope to start another major project in late January/early February. We predict 2020 will be another busy year.

Here’s hoping your 2020 is as rewarding as we expect ours to be.

 

Business System Stuff

E-mail Print PDF

It seems that everybody is talking about business system audits/reviews these days. (For the record, DCAA performs audits and DCMA performs reviews.) Now that DCAA has “caught up” with its backlog of audits of proposed final billing rates, it has reportedly turned its attention back to the more traditional audit areas: Cost Accounting Standards, defective pricing, and business systems. Thus, many people will tell you that your risk in those areas has increased.

But it hasn’t. Not really.

DCAA has always performed some level of CAS, defective pricing, and business system reviews. And DCMA has never stopped performing those reviews. So your company’s risk has always been there, though of course DCAA’s recent strategic changes increase the likelihood that your company will be the recipient of one of those reviews.

What is DCAA doing differently?

Two main things: (1) creation of Headquarters “Truth in Negotiations” audit teams that do nothing but defective pricing audits, and (2) creation of Regional Business System teams that do nothing but audits of Accounting, MMAS, and Estimating Systems.

It’s too early to see the results of those changes but, anecdotally, we know that audits are on the increase. Further, as DCAA does not track its business systems audits separately from its other audits, the official statistics don’t tell the whole story. But we do have statistics on defective pricing and CAS audits:

cas_report_06_19

 

tina_reports_06_19

As the charts above illustrate, it won’t take much of an increase to (say) double or even triple the number of reports that DCAA will be issuing.

Back to Business Systems. While there are not statistics we can find regarding the number of audits/reviews performed, we did find some statistics about system status. What we came across was dated 01 November 2019 – about six weeks ago as this is being written.

As of that date:

  • There were 30 Accounting Systems that had been officially found to be inadequate out of 3,751 evaluated

  • There were 3 MMAS that had been officially found to be inadequate out of 313 evaluated

  • There were 38 Estimating Systems that had been found to be inadequate out of 709 evaluated

Looking just at those three Business Systems (which are the ones that DCAA takes the lead in auditing) we can see that the Estimating System audits are the riskiest. Obviously, the Accounting System audits are the most important; but you are more likely to suffer an Estimating System disapproval. The statistics indicate that you have less than a one percent chance of having your Accounting System found to be inadequate but you have a greater than five percent change of having your Estimating System found to be inadequate. All other things being equal, of course.

A similar analysis on the DCMA-led Business Systems indicates that Purchasing is the riskiest. Forty-six Purchasing Systems have been found to be inadequate out of 876 reviewed; meaning that you have about a five percent chance of having your system found to be inadequate when DCMA performs a review. Both EVMS and Property Systems have a less than one percent inadequate-to-evaluated ratio.

That doesn’t mean you can relax and focus only on your Estimating and Purchasing Systems; but it does tend to indicate that those systems fail reviews at a much higher rate than the others.

What should you be doing about the situation?

We recently spoke at a compliance conference and offered this advice

  1. Review your contracts and identify which contracts have which business system DFARS clauses

  2. If you have any contracts with both an individual business system clause AND the DFARS general Business System clause (525.242-7005) then your company is subject to payment withholds when a business system is found to be inadequate.

  3. For each business system you are required to maintain in an acceptable manner (as defined by the individual business system clause), you need to develop a compliance strategy. The compliance strategy should include:

    1. Clear delineation of roles and responsibilities. Who is the individual who is responsible and accountable for the adequacy of the business system?

    2. Ensuring that a system description exists and that is it current and complete

    3. Ensuring that system policies, procedures, and instructions are well-documented

    4. Development of a self-governance approach, including transaction testing to provide assurance that employees are complying with expectations

  4. Many companies perform mock audits in preparation for an official government audit/review. For companies that lack resources, an outside firm is often hired.

The above steps can be performed by companies of any size. The same approach can be taken with respect to CAS and defective pricing audits—i.e., first identify the contracts that have the clauses and then figure out how you will comply with the clauses’ requirements.

This approach won’t guarantee that you will pass a government audit/review, but it will increase your chances of doing so.

 


Page 28 of 279

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.