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

What If DCAA Only Did Audits?

E-mail Print PDF

Say what you will about the Defense Contract Audit Agency – and boy howdy have we said a lot over the past eight years – it is an inescapable fact that the audit agency has a backlog of unperformed audits and that backlog has hobbled the ability of both government and contractor to timely close-out contracts. As a result of the backlog of unperformed audits, unliquidated obligations are held open unnecessarily long, final payments (which would include payments of final fees) are unnecessarily delayed, and past performance information (in terms of how much unallowable costs contractors claim) doesn’t get reported (and/or used) as the FAR intends.

That backlog of unperformed audits is a problem. It’s been a problem for years. DoD Leadership has spoken publicly about it. Congress has held hearings about it. GAO and various Inspectors General have expressed their concerns. Everybody has been waiting for DCAA to fix its problem, and the wait has gone on through the tenure of one Director and into the tenure of another.

As we reported, DCAA figured-out a “risk-based” way of closing out certain audit assignments without, you know, actually performing those audits. DCAA also figured-out a way of closing out other audit assignments by declaring the submissions to be irredeemably inadequate (in the short timeframe DCAA gave certain contractors to fix the alleged inadequacies)—and then kicked the proverbial can over to DCMA and made it DCMA’s problem to fix. The DCAA files say “assignment closed” and the unaudited submission no longer counts as backlog, as far as DCAA is concerned.

DCAA has figured-out several innovative ways to reduce its backlog of unperformed audits and, indeed, the reported backlog has dropped over time. DCAA claims this is a significant milestone and is indicative of performance improvement at the audit agency. Nonetheless, the backlog is still in excess of what the prior Director promised Congress and DoD Leadership and the taxpayers. It is still (at last report) about 170% of what the audit agency considers “normal backlog” (which is defined as 18 months’ worth of work—meaning DCAA would only be a little behind instead of being embarrassingly behind).

DCAA’s backlog reduction came too little, too late. DCAA failed to meet its commitment and now the audit agency is being held accountable for its failure. Congress, growing impatient with hollow promises and lack of progress, has acted to “help” DCAA out of its mess.

Congress acted in the form of statutory language in the FY 2016 National Defense Authorization Act (NDAA) that flat-out prohibited DCAA from performing audit work for any non-DoD agencies until it had reduced its backlog to “normal” levels.

In other words, Congress told DCAA that, given the audit agency’s inability to properly manage its workload, Congress would set the priorities for the audit agency. Congress would help DCAA focus on its audit backlog by prohibiting DCAA from wasting its scarce audit resources on activities that were not related to the backlog of unperformed audits. The Congressional action was similar to a teacher telling a distracted student to stop daydreaming and focus on the assignment. It was similar to a parent telling a teenager to stop playing video games until the homework assignment has been completed.

It was a desperation play, because (obviously) we shouldn't need a public law to tell DCAA what to audit. But apparently some people in Congress thought we did. So now we do.

And DCAA has figured-out how to get around it.

On January 7, 2016, DCAA issued MRD 16-PPD-001 (R), entitled “Audit Guidance on the Impact of the National Defense Authorization Act on DCAA’s Audit Support to Non-Defense Agencies.” The apparent purpose of the MRD is to tell auditors how to keep supporting non-DoD agencies. The apparent purpose of the MRD is to explain how DCAA will be ignoring Congressional intent. The apparent purpose of the MRD is to demonstrate (once again) how DCAA will keep doing what it wants to do, regardless of what outsiders may think.

The MRD states: “The NDAA prohibits DCAA from providing audit support to non-Defense Agencies/ reimbursable customers. Our legal team has advised that we can continue to provide services that fall outside audit support.”

In other words, DCAA has received a legal opinion that splits the hair and ignores the spirit of the law in favor of the letter. Sure, the NDAA says DCAA cannot perform audits for non-DoD agencies; but nobody ever said DCAA can’t perform other services for those same agencies.

DCAA is clearly ignoring Congressional intent here. Congress told DCAA to quit messing around with non-DoD stuff and focus all resources on getting its backlog of unaudited DoD submissions handled. The DCAA MRD ignores that, and permits resources to be squandered on matters other than the task that Congress wants DCAA to address.

So what kind of non-audit services can DCAA auditors perform for non-DoD agencies, according to the MRD? It states—

The following are the types of effort that we have determined are permissible to support reimbursable customers:

  • Negotiation support,

  • Litigation support,

  • Investigative support (performed by OIS), and

  • Non-audit services (e.g., requests for specific cost/rate information).

There you go. DCAA will continue to provide those services to non-DoD agencies.

But it got us wondering … what if DCAA only performed audits? What if DCAA only performed audits for DoD agencies? What if DCAA didn’t provide negotiation support or litigation support or non-audit services … for anybody?

If DCAA concentrated its resources solely on performing audits, and on performing those audits solely for the Department of Defense—then how quickly could that backlog of unperformed audits be reduced?

If DCAA focused its efforts, it might find it has sufficient resources to, you know, actually audit all incurred cost submissions, just as it used to do!

Wouldn’t that be nice?

 

2015 Recap—Top 5

E-mail Print PDF

Apogee Consulting, Inc. published 112 blog articles in 2015. That’s about one every three days (more or less). Some were more popular than others, as measured by the number of recorded “hits”—which are the number of times the article was clicked on. (That metric ignores the number of times the article was read from the site’s “main page” but it’s the closest thing we have to a popularity meter.)

Based on that metric, the most popular article was “DCAA Resources” followed closely by “Expressly Unallowable Costs”. But as we’ve noted before, the metric is somewhat misleading, in that older articles have had more time to garner hits.

Last year, we listed our personal “Top 5” favorite articles. But in looking over this year’s crop, what we see are themes rather than articles. We see a series of related articles that, when read together, provide analysis and (if you’ll permit us) insight. Thus, this year we will list our Top 5 themes—themes that we believe captured the trends of the year and provided solid assessments of those trends.

They are, in no particular order—

  1. “Goodbye DCAA” – in which we reported on the lack of DCAA audit coverage being provided to non-DoD agencies (such as the Dept. of Energy and NASA). The articles started with noting that changes in the DCAA “risk-based” audit approach meant that a significant portion of contractors’ annual proposals to establish final billing rates (also known as “incurred cost submissions”) were no longer being audited by DCAA, and the non-DoD agencies didn’t have a plan to address that shortfall. Later in the year, we addressed the FY 2016 National Defense Authorization Act (NDAA) and its prohibition on DCAA performing any audits for non-DoD agencies until the backlog of unaudited final billing rate proposals was reduced to a more manageable size. At this point, the non-DoD agencies are, essentially (though not completely), on their own with respect to audits of proposals, invoices, and the like. As far as we know, nobody has a plan covering how to replace the services DCAA formerly provided.

  1. “No Innovation Here” – in which we discussed the Pentagon’s expressed desire to regain its lead in technological innovation, and why we were so pessimistic that the kind of innovation that DoD leadership said it wanted was ever going to happen. We spoke publicly on the topic in April (at the BDO/PCI DCAA Executive Seminar in Tyson’s Corner) and we wrote many articles about it—culminating with our proposal for “achievable innovation” that laid-out several strategies that we thought might be feasible.

  1. “Contractor B.S.” – in which we discussed our thoughts on DoD’s management and oversight of contractor business systems. Some of the articles dealt with the DoD Inspector General’s criticism of DCMA; others dealt with the sheer unworkableness of the oversight regime. We spoke on the topic in November in front of government and private sector attorneys. At that forum, we called for a regime change, and we suggested that the American Bar Association sponsor a joint government/industry working group to design the “next generation” approach to contractor business system compliance. As of this date, we haven’t heard that anybody accepted our call to action….

  1. “Double-Secret Audit Guidance” – in which we discussed the startling lack of recently published DCAA audit guidance, and what that gap might mean. Readers responded and subsequently we learned that DCAA was issuing new audit guidance (via Memorandum for Regional Directors or MRDs). DCAA simply wasn’t choosing to publish the new audit guidance on its website anymore. Later in the series, we discovered that certain folks were able to access that secret audit guidance and were using it to drive a competitive advantage in the marketplace for consulting services. Thanks DCAA, for creating an unbalanced marketplace.

  1. “CAS” – in which we discussed the seemingly missing-in-action CAS Board, and how the CAS Board’s failure to make decisions and interpret its regulations actually affected multi-million dollar CAS-related litigation. This series of articles included a two-part discussion of the Raytheon Space and Airborne Systems business unit’s litigation at the ASBCA, and how the resulting decision clarified (for better or worse) how cost impacts related to changes in cost accounting practice were to be calculated.

So that was the year that was.

We did not link to the various articles discussed above. The website has a News Archive button over there on the left, and it takes you to a list of articles shown in chronological order by date of publication. You can configure the list to display anywhere from 5 to 100 articles at a time. You can even tell the archive to display all articles in one (very long) list—assuming you want to scroll through the more-than-900 articles we’ve published to date.

 

DCAA Audit Support to Government Cost/Price Analysis

E-mail Print PDF

The ability to evaluate bidders’ proposed prices in order to determine the lowest probable price—the low bidder—is an art and a skill, and it requires the ability to engage in critical thinking.

Price analysis is always required. And when award will be made on a “best value” basis using FAR Part 15 procedures, the ability to perform cost/price analysis is critical. Part 15 states—

An agency can obtain best value in negotiated acquisitions by using any one or a combination of source selection approaches. In different types of acquisitions, the relative importance of cost or price may vary. For example, in acquisitions where the requirement is clearly definable and the risk of unsuccessful contract performance is minimal, cost or price may play a dominant role in source selection. The less definitive the requirement, the more development work required, or the greater the performance risk, the more technical or past performance considerations may play a dominant role in source selection. … When using a tradeoff process, the following apply:

(1) All evaluation factors and significant subfactors that will affect contract award and their relative importance shall be clearly stated in the solicitation; and

(2) The solicitation shall state whether all evaluation factors other than cost or price, when combined, are significantly more important than, approximately equal to, or significantly less important than cost or price.

This process permits tradeoffs among cost or price and non-cost factors and allows the Government to accept other than the lowest priced proposal.

The above points were emphasized in a recent GAO bid protest decision, as noted by Bob Antonio at WIFCON.

Although we’ve written before about concerns with DCMA’s skills in this area, the bid protest involved the General Services Administration (GSA) and not DCMA. But the lessons to be learned do not depend on the agency involved; they are universal. Let’s dig in, shall we?

GSA issued a small business set-aside RFP seeking up to 20 contractors to perform “repair and alteration” construction services. ID/IQ contracts were to be awarded. Under each ID/IQ contract, multiple task orders would be awarded, each valued at between $150,000 and $500,000. The ID/IQ contracts were to have ceilings of $50 million. In other words, the stakes were quite high for a small business; a winning award might well transform the small business into a successful large government contractor.

According to the GAO decision, the RFP provided that award would be made on a best-value basis, considering the following evaluation factors: prior experience on similar projects, past performance, evidence of local office, socio-economic status, and total evaluated price or cost. The RFP provided that the first two non-price factors were equal in weight and were more important than the remaining two non-price factors, which were equal to each other in weight. The RFP stated that all non-price factors, when combined, were significantly more important than cost or price; however, where the technical merit of competing proposals became more equal, price/cost would increase in importance in the award decision. Offerors were to submit separate technical and price proposals.

So far, so good. That’s all fairly standard stuff. If you have trouble following it, then you probably haven’t dealt with many government RFPs.

The kicker came when the RFP discussed the content of the bidders’ “price proposals.” According to GAO, “the solicitation required offerors to submit G&A rates, and stated that these rates alone would be used to evaluate price. Specifically, the solicitation stated that the offerors’ G&A rates would be evaluated using cost analysis to determine reasonableness, based upon verification of the offerors’ cost submissions for their G&A rates and confirming that the submissions are in accordance with the contract cost principles and procedures described in FAR part 31.” Obviously G&A rates are not costs nor do they correspond to an offeror’s proposed price. Moreover, a simple comparison of G&A rates is utterly meaningless.

The reason you can’t simply compare G&A rates is that G&A rates are calculated in different ways, using different allocation bases. CAS 410 permits three different G&A bases: Total Cost Input (TCI), Value-Added Base (VAB), and Single Element Base (SEB). Even if the G&A expense pool is exactly the same, you get an entirely different G&A rate with each allocation base. When we teach Cost/Price Analysis, calculating the G&A rate under each compliant G&A allocation base is one of the exercises—and it’s almost always an eye-opener for those analysts who think a higher G&A rate is “worse” than a lower one.

And in this case, the situation is even more dynamic because all bidders were small businesses and small businesses are exempt from CAS. Thus, while CAS would permit a choice of any of three compliant allocation bases, in this case the bidders were unconstrained and could literally choose any G&A allocation base that had a logical relationship to the expense pool.

All the above didn’t stop the GSA cost/price analysts from using bidders’ G&A rates as a (really poor) surrogate for total cost or total price being offered. Moreover, just to make matters worse, the RFP instructed offerors to submit “certified financial statements or DCAA report substantiating the offeror’s G&A rate.” The problem there is that you really can’t calculate a FAR Part 31 compliant G&A rate from financial statements—certified or otherwise—because the GAAP definition of G&A doesn’t necessarily match the FAR definition of G&A. For example, for financial statement purposes it’s called “S, G&A” (meaning selling, general & administrative) but it’s just G&A for government accounting purposes. Selling can be part of the G&A expense pool, or not. But that wasn’t the end of the problems GSA was creating for itself and its bidders.

A competitive range was established based on perceived technical risk, and then the G&A rates came into play. Per GAO—

The agency further determined that two of the T1 [Tier 1] technically-ranked proposals with G&A rates of 12% and 20.10%, and three of the T2 technically-ranked proposals with G&A rates of 11%, 11.40%, and 19.58%, did not have ‘the most favorable G&A rates when compared to the others.’ As a result, these proposals, including the protester’s proposal--which received a T2 technical ranking and proposed a G&A rate of [deleted]--were not further considered for award. With respect to the 12 remaining proposals, the agency contacted eight of the offerors and requested that they verify or confirm their G&A rates because of concerns about the rates. … The offerors generally responded by confirming their G&A rates. In these cases, the agency did not request any further substantiation, nor did the agency conduct any analysis of the ‘verified’ rates. The agency, nonetheless, accepted the rates provided in the responses as the offeror’s ‘verified’ rate.

(Internal citations and footnotes omitted.)

Needless to say, disappointed bidders had problems with the foregoing approach to cost/price analysis and the source selection decision. West Coast General Corporation was one such disappointed bidder, and decided to protest the award decision. “Specifically, the protester argues that the agency accepted G&A rates from some offerors that were unsubstantiated, and were not explained by the submitted financial data, as expressly required by the RFP.” Unsurprisingly, GAO sustained the protest.

Among the reasons cited by the GAO for sustaining the bid protest—

… the agency’s evaluation of price proposals was inconsistent with the RFP requirement that offerors’ proposed G&A rates be verified and substantiated using certified financial statements or DCAA reports, as described above. The protester asserts that instead, the agency accepted from eight of the 12 awardees ‘post-bid commitments’ of G&A rates that were either unsubstantiated or unexplained by financial data (and in some instances, directly contradicted by the financial data).

A fundamental lesson to be learned here is that past financial statements—certified or not—or DCAA audit reports confirming the accuracy of past G&A rates is really no basis for evaluating offerors. The G&A rates that were relevant to the source evaluation were future G&A rates to be incurred during task order performance. Past G&A rates were not good indicators of future G&A rates, especially given the fact that these were going to be relatively large task orders awarded to small businesses. One or more task order awards in a single year could result in a significant decrease to the historical G&A rate. The GSA evaluation scheme missed this point entirely.

This points to a larger problem: the notion that DCAA (or any government analyst) can “audit” a contractor’s estimate of future costs to be incurred. That’s not correct. A DCAA admission that such “forward priced proposal” reviews are not audits, and not really subject to the full GAGAS treatment, would go a long way to alleviating the audit agency’s well-known problems regarding quality, timeliness, and usefulness.

As colleague Darrell Oyer recently wrote in his newsletter, “One cannot audit something that has not yet happened. … Audit standards are not applicable to proposal audits. However, the audit attitude is evident by a statement of a DCAA auditor in a deposition: ‘Estimating does not require judgment—you just look at the books and records to see what it cost previously.”

So what value does DCAA provide to those charged with cost/price analysis and in making an informed source selection decision that will survive a bid protest? In theory, DCAA is capable of auditing historical cost data and the reasonableness of contractors’ projections that use that historical cost data as a starting point. DCAA can also audit vendor and subcontractor quotes and can verify the bidder used those quotes properly. DCAA’s audits of proposals don’t ever save the taxpayers any money, but they can certainly help the contracting officer better negotiate the price, which of course does save taxpayers money.

We recently noted a DoD Inspector General report that essentially found that DCMA Cost Monitors were less effective at evaluating contractor proposals than DCAA had been. We didn’t buy the DoD OIG conclusions. In retrospect, we could have and should have made our point better than we did in that article.

Our viewpoint is that nobody should expect DCMA Cost Monitors to perform audits of contractor proposals. Cost Monitors don’t actually, you know, perform audits. They are not trained to do so. (Well, except for all those ex-DCAA auditors who are now DCMA Cost Monitors.) Cost Monitors are supposed to comply with DCMA Instruction 120 (“Pricing and Negotiation”) and not with GAGAS. So it should absolutely not be surprising that Cost Monitors don’t perform audits as well as DCAA does.

On the other hand, it should also be clear that DCAA doesn’t perform audits well—especially when asked to perform “audits” of contractor cost proposals related to future work to be performed. Those cost proposals are essentially estimates. Estimates are not really subject to audit, for the reasons Darrell Oyer stated (which we quoted above). That being said, to the extent those estimates are based on cost information that can be audited, a DCAA auditor should be able to provide valuable assistance to those personnel performing cost realism analyses and who are negotiating contract prices.

Which leaves us right back where we started.

The ability to evaluate bidders’ proposed prices in order to determine the lowest probable price—the low bidder—is an art and a skill, and it requires the ability to engage in critical thinking.

It is not the exclusive province of DCAA, nor is it the exclusive province of a Cost Monitor or Contracting Officer. It is not a function of agency or position. To do a good evaluation—one that will survive a bid protest—is the province of a very few people who have the right skills, the right training, the right disposition, and the right attitude.

When done well, it saves the taxpayers money and results in a defensible contract award. When done poorly (as was the case with the GSA bid protest we summarized here), it hurts both government and contractor. The government ends up with delayed contract performance and possibly with the less-than-best contractor doing the work. The protestor ends up with wasted B&P dollars and possibly with unallowable legal bills. The lawyers, however, are quite happy.

 

 

Meet the Apogee Consulting, Inc. Team

E-mail Print PDF

2015 is over and, as we look back over another exciting year, I thought I might indulge in a rare shout-out to the people who make Apogee Consulting, Inc. happen.

First let me introduce Mark Sewall, who is the guy who keeps this website running and who makes sure the articles get published. Mark has two jobs that keep him busy. He spends most of his time working on projects for Event Special Effects, a group of talented (and crazy) people who develop special effects to support marketing efforts by various entities. Think Mythbusters but without the TV cameras and Kari Byron. On the side he runs Practical Brilliance, a boutique consultancy focused on helping small businesses with their IT, A/V, and related technology challenges.

Next meet Tom Schmitz. Tom is a 30+ year veteran of the aerospace/defense industry. Most of that time was spent at Hughes Aircraft/Raytheon in Finance, Estimating and Pricing functions. Toward the end of his successful career, Tom managed the Pricing/Estimating function for Raytheon’s Space and Airborne Systems business segment—a $6 billion dollar entity that spit out literally hundreds of proposals each year. Tom is our SME in the areas of Estimating Systems, proposal preparation, and cost/price analysis. He recently completed an assignment supporting a mid-size defense contractor who was having trouble getting its government customer to accept the cost/price analyses it had performed. The problem was holding-up award of a major contract. Tom showed up on site with literally one day advance notice and, within a couple of weeks, the government customer was satisfied. Just as importantly, the contract was awarded. Tom has also worked Accounting System and organizational structure issues in past assignments.

A more recent addition to the ranks of Apogee Consulting, Inc. support staff is Ed Kasaba. Ed is another 30+ year veteran, but he split his time between the aerospace/defense industry (at companies such as Rockwell, Boeing, and Pratt & Whitney Rocketdyne) and the bio-pharmaceutical industry (at Amgen). Ed is our Purchasing System and Socioeconomic Reporting System SME. He also handles contract compliance and supply chain management issues. Ed has worked with companies—both large and small—in establishing their first Master Small Business plans. He also recently helped a start-up company prepare to start bidding on its first Federal contract, including working through registration issues for the various government databases and identifying key business practices changes necessary to comply with contract requirements.

One important differentiator between Apogee Consulting, Inc. and other boutique providers of contract compliance services is that our consultants are here because they want to be—and not because they have to be. Both Tom and Ed are retired and they enjoy their retirement. But they also enjoy helping other people and companies with the expertise they gained over their long and successful careers. They are consultants because they want to help, not because they need a paycheck.

Another point to consider: Because their Apogee Consulting work is a part-time thing, being fit in between home remodeling and leisurely vacations, our clients can be assured we are not looking for a long-term assignment. We are not looking to “milk” a project for maximum billable hours. Indeed, our policy is that we only bill clients for value-added hours; which means (for example) we don’t bill clients for travel time. We show up, we get the job done, and we leave. And that’s the way we like it.

In addition to the foregoing, our people are committed to transferring their knowledge and experience to our clients. We pride ourselves on making sure our clients know why and how, as well as what. We never have a problem explaining the regulatory drivers associated with what needs to be done.

So that’s the Apogee Consulting, Inc., team. Without them, all we would be is a website and a blog. 

 

The Importance of Incurred Cost Adequacy

E-mail Print PDF

One of the biggest irritants we encounter at the ASBCA website is that decisions are posted in chronological order based on the date the decision was issued. The problem with that approach is that some decisions are delayed after issuance to permit the parties to identify proprietary information and redact that information from the decision. Thus, there may be a 30 day (or longer) delay before a decision gets published, and the decision is slipped into the list without any identifier that it is a delayed publication. If you follow the ASBCA decisions each week (as we do) and you assume that what’s past is past, you’ll tend to miss a couple of decisions.

That was the case with the November 10, 2015 decision in the matter of Alion Science and Technology Corporation. The decision continued an unfortunate trend regarding application of the Contract Disputes Act Statue of Limitations (CDA SoL) to disputes between the government and its contractors. We missed the decision and, if were not for a somewhat critical article penned by the government contracts attorneys at Dentons, we might still be unaware of its existence. The Dentons article asserted—

After years of establishing precedent that a government claim begins to accrue when the government should have known about the facts underlying a claim, the ASBCA continues to disregard its previous holdings by incorrectly applying what appears to be approaching an actual knowledge standard. … The ASBCA held that disputed material facts precluded summary judgment essentially because the contractor could not establish that the government possessed actual knowledge of the specific facts supporting its penalties claim. The ASBCA based its decision on the contractor's inability to demonstrate that the government received from the contractor specific cost transaction data relating to the costs that were the subject of the government's penalties claim more than six years prior to the date that the government issued the final decision.

(Emphasis in original.)

We have noted this troubling trend in other articles on prior ASBCA decisions. Essentially, it seems that the ASBCA Judges are permitting the government to unilaterally toll the statute of limitations by the tactic of delaying the audit of contractors’ costs. The delays are often based on thinly veiled pretexts such as a DCAA determination of “submission inadequacy” that, quite frankly, the ASBCA Judges ought not to condone. Alion continues this troubling trend where the government is permitted to claim that it did not know of disputed costs until the contractor provides detailed cost data—a line of argument that blithely ignores the fact that the submission of the final billing rate proposal (also known as “incurred cost submission”) triggers an affirmative duty to investigate and actually, you know, conduct an audit to determine whether or not disputed costs were submitted. Alion continues the troubling trend at the ASBCA where the DCAA is permitted to avoid indefinitely its affirmative duty through claiming that the contractor’s proposal was inadequate—a charade that is in direct contravention of applicable FAR requirements. Alion continues the troubling trend of ASBCA permitting the government to claim it was unaware of any asserted harm even though it waited more than six years to look to see if it was harmed.

We are not fans of this line of decisions at the ASBCA.

That said, what did Alion do wrong, such that DCAA claimed it was unaware of allegedly expressly unallowable costs in the final billing rate proposal?

According to the decision denying Alion’s motion for summary judgment, Judge Melnick found that Alion submitted its FY 2005 incurred cost proposal on March 31, 2006. Alion did not use the DCAA’s “Incurred Cost Electronically” (ICE) model of linked spreadsheets. (Indeed, at that point in time Alion was not required to do so. Today, Alion would be required to use the exact ICE model or an extremely similar series of linked spreadsheets that mimicked the ICE model, pursuant to FAR 52.216-7, Allowable Cost and Payment.) Instead, Alion used its own series of schedules, which generally followed the DCAA ICE model format, but also contained custom formulae and spreadsheet links. For example, “within Schedule 14, the entry for job number 90035003001000000 lists a recorded amount of $718,967 … The corresponding entry in the spreadsheet titled ‘Sch 14 Table’ lists a grand total amount of $718,967.05. Double-clicking this cell opens a new spreadsheet containing approximately 750 individual items of cost with accompanying information, including the amount of the cost, the date incurred, a general description of the cost, and various accounting data.”

To be clear, the then-current FAR did not require a certain exact format or set of schedules to be used. Instead, the FAR stated “The required content of the proposal and supporting data will vary depending on such factors as business type, size, and accounting system capabilities. The contractor, contracting officer, and auditor must work together to make the proposal, audit, and negotiation process as efficient as possible.” [FAR 42.705-1(b)(1)(i)] Regardless of the lack of any prescription to use specific schedules, and regardless of the clear and express permissiveness found in the FAR (as quoted above), DCAA found Alion’s submission to be “inadequate” because it lacked a Schedule H-1 (government participation in indirect expense pools) and a Schedule L (reconciliation of total payroll to total labor distribution).

Those two Schedules have nothing to do with auditing incurred costs. Instead, those two Schedules are simply former DCAA working papers that DCAA now wants contractors to complete for them, so as to make their audits more efficient. Nonetheless, DCAA found Alion’s proposal to be inadequate because it failed to include two minimally value-added Schedules.

Alion submitted the two additional Schedules on September 7, 2007—about ten months after DCAA rejected its proposal. DCAA rejected the revised proposal once again, finding it to be inadequate for additional reasons not originally specified. Once again, Alion resubmitted its FY 2005 proposal (on or about February 8, 2008 – approximately two years after its first submission). Along with the submission came a full data-dump from Alion’s JAMIS accounting system. As Judge Melnick stated, “The government asserts that it was not until the submission of the JAMIS database that the government was able to identify the Engineering Overhead and G&A costs (other than SRC costs) at issue as expressly unallowable.”

Essentially, then, the government’s position was that it was not the submission of the proposal to establish final billing rates that triggered the CDA SoL; instead, it was the submission of the contractor’s general ledger that started the CDA SoL clock. Judge Melnick agreed with the government and rejected Alion’s Motion for Summary Judgment. He wrote “Respecting Alion's other costs, Alion has failed to identify within its 31 March 2006 proposal the specific costs at issue in this appeal. Viewing the record in the light most favorable to the government as the nonmoving party, as we must on summary judgment … there is a genuine issue of material fact as to whether the 31 March 2006 final indirect cost rate proposal included the alleged expressly unallowable costs at issue in this appeal.”

We are not attorneys. We are not learned judges. Our opinion about this line of recent ASBCA decisions—and this decision in particular—means nothing.

But still.

The Contract Disputes Act has to mean something. The definition of “claim accrual” found FAR 33.201 has to mean something. The permissive language of FAR 42.705-1 has to mean something. Statutes and regulations don’t exist for the purpose of being ignored in judicial proceedings.

It seems that the ASBCA Judges are bound and determined to ignore the plain language of those citations (and others). It seems that the ASBCA Judges are bound and determined to let the government unilaterally toll the CDA SoL through a charade, perpetrated upon the Court by auditors of DCAA, who can seemingly indefinitely refuse to audit a contractor’s proposal to establish final billing rates upon the thinnest of rationales—to which the Judges grant great deference.

The lesson here is simple and we’ve posted it before. When contractors submit their final billing rate proposals they must include their general ledger. Forget the fact that the FAR doesn’t require it. Forget the fact that most modern general ledgers are so chock-filled with transaction data that it’s almost impossible to make an electronic copy and transmit it. Forget the fact that most DCAA auditors can’t access such a file if one manages to create and provide it to them.

Because according to the ASBCA, the only way to start the CDA Statute of Limitations is to provide that general ledger to DCAA.

It’s crazy, but that’s the lesson to be learned here.

 


Page 98 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.