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

Proposed DFARS Allowability Rules Give and Take Away

E-mail Print PDF

Takers
The Defense Federal Regulation Supplement (DFARS) contains rules that apply primarily to DOD contractors. These rules are in addition to the requirements of the Federal Acquisition Regulation (FAR). The DFARS requirements supplement the FAR requirements. Thus: the “S” in the DFARS.

Recently, the Defense Acquisition Regulation (DAR) Council issued two proposed rules for public comment. We want to bring them to your attention in the (perhaps vain) hope that you will be inspired to submit comments to the DAR Council.

The first proposed DFARS rule implements Section 862 of the 2012 National Defense Authorization Act (NDAA), which required the DOD “to encourage contractors to develop science, technology, engineering, and mathematics (STEM) programs. STEM programs are, programs or initiatives, either formal or informal, which encourage the pursuit of education and experience in the Science, Technology, Engineering, and Mathematics disciplines.” Accordingly, the DAR Council proposed to add a new Subpart to the DFARS—226.72—appropriately entitled “Encouragement of Science, Technology, Engineering, and Mathematics (STEM) Programs.”

As the DAR Council noted, “There are no reporting, recordkeeping or other compliance requirements associated with this rule. This rule only encourages contractors, to the maximum extent practicable, to develop science, technology, engineering, and mathematics (STEM) programs. The contractor is not required to develop STEM programs or to report on this activity.” Instead, the proposed new DFARS Subpart establishes the policy position directed by the FY 2012 NDAA, and also creates a new solicitation provision/contract clause to be inserted in all RFPs and in all contracts. The proposed clause encourages the activities that Congress directed DOD to encourage. There’s a catch, however.

The catch is that the proposed clause states that “The Contractor shall assume the responsibility for all the costs and investments in support of the STEM disciplines.” It also states that “The Contractor will not be reimbursed for any costs incurred or associated with the support of the STEM disciplines. Any costs incurred for supporting the STEM disciplines are unallowable under this contract.”

We have two immediate thoughts on this proposed rule, which we hope will find their way into public comments submitted to the DAR Council.

Our first thought is that it is disingenuous and perhaps even contrary to Congressional intent, to both “encourage” contractors to engage in STEM-related activities, while at the same time declaring that if the contractor does engage in such activities, the costs are not allowable contract costs. One is tempted to assert that the two policy positions are contrary to one another. Declaring that STEM-related costs are unallowable seems to be faint encouragement, indeed.

Our second thought is that, if the DAR Council truly intends to make such costs unallowable, the place to do so is in DFARS Subpart 231 (“Contract Cost Principles and Procedures”) and not in Subpart 226. Putting the cost disallowance in Subpart 226 strikes us as an attempt to hide the policy position taken by the Defense Department. If the rule-makers want to declare such encouraged costs to be unallowable, then they should do so in the proper regulatory location.

Public comments must be submitted before April 29, 2013, via one of the methods listed in the proposed rule (link above).

The second proposed DFARS rule implements the wishes of the Honorable Shay Assad to penalize contractors for the healthcare costs of ineligible dependents. We’ve ranted about this particular issue before, most recently right here. We said—

We have two or three members of the Senior Executive Service (SES) who have embarked on a course of action that wastes the time, money, and resources of all involved. They have created a problem that exists only in their own minds, and refuse to let it go.

Our opinion on this entire issue remains unchanged.

The proposed rule will revise the DFARS Cost Principle at 231.205-6—

…to implement the Director of Defense Pricing policy memo ‘Unallowable Costs for Ineligible Dependent Health Care Benefits,’ dated February 17, 2012. The rule adds paragraph 231.205-6(m)(1) to explicitly state that fringe benefit costs incurred or estimated that are contrary to law, employer-employee agreement, or an established policy of the contractor are unallowable.

What a shame.

As with the first proposed rule, public comments must be submitted before April 29, 2013, via one of the methods listed in the proposed rule (link above).

 

 

Another CDA Statute of Limitations Case, Another Contractor Victory

E-mail Print PDF

Victory_Is_Mine
In the recent past, we have written less-than-flattering analyses of certain decisions issued by Judges of the Armed Services Board of Contract Appeals (ASBCA)—decisions that involved the Statute of Limitations (SoL) associated with the Contract Disputes Act (CDA). We’re sure that nobody over at the ASBCA cares a whit about our opinion of their decisions. After all, we are not attorneys and it should be crystal clear that we don’t understand all the intricacies and nuances of The Law.

But still. We can read and we can reason and we have opinions that at least some people take the trouble to read. So when we were somewhat critical about Judge Delman’s decision in the matter of Lockheed Martin’s alleged CAS noncompliance regarding its accounting for Independent Research and Development (IR&D) costs, we thought we were raising some reasonable points (for a layperson, anyway). And when we called Judge Delman’s subsequent decision in the matter of the allowability Raytheon’s executive incentive compensation plans a “half-a-loaf, not a full loaf” of a victory for contractors, we thought we were discussing relevant and on-point issues that few other sources were discussing.

And now we are back with another ASBCA decision by another Judge (Judge Melnick) on another CDA SoL case filed by the Raytheon Company, in which Raytheon cleaned the government’s clock. (Pending appeal, of course.)

Oh yeah, we don’t have too many strident layperson-type criticisms to level at this case. You all really, really need to go read it right now. The decision was issued January 28, 2013 but was held for 30 days to give the parties an opportunity to review and redact; consequently, it was published at the end of February.

In case you’re too lazy to go find and read it (even though we gave you a link to click on), we’ll recap it for you. We take the trouble to do this because we know our readership. Here goes:

Raytheon Missile Systems (RMS), one of the operating businesses of The Raytheon Company, disclosed to the Government its cost accounting practice of excluding certain subcontract costs (called “Major Subcontracts”) from the application of full indirect rate burdens. The disclosure was made at the end of 1998, to be effective January 1, 1999. Subsequently, on June 18, 1999, RMS submitted an amended CAS Disclosure Statement in which it disclosed that the group of Major Subcontracts would be expanded, so that more subcontracts would qualify for that special reduced indirect rate burdening. Even though RMS disclosed the revised cost accounting practice in mid-June, the practice was to be retroactively effective as of January 1, 1999.

On May 14, 1999, NAVAIR awarded RMS a letter contract to remanufacture Tomahawk missiles. RMS submitted a cost proposal to definitize that letter contract on July 20, 1999. That definitization proposal was submitted about one month after submission of the revised Disclosure Statement; consequently, RMS should have applied the revised Major Subcontract burdening practice in its cost proposal to NAVAIR. Allegedly, RMS failed to apply its reduced indirect rate burdens to the Lockheed Martin subcontract costs included in its proposal. The contract price was negotiated and agreed-upon on August 4, 1999, and nothing was said of the potential noncompliance with disclosed cost accounting practices at the time—even though a DOD pricing analyst reviewed the proposal in detail (including the application of indirect rates to proposed subcontract costs).

About six years later (in 2005), “the same DCMA price analyst performed a second review” of RMS’ 1999 pricing data. This time around, the price analyst noted that RMS failed to burden its proposed Lockheed Martin subcontract costs with its reduced Major Subcontract indirect rates. In April, 2006, DCAA issued a “draft condition statement” alleging that RMS’ proposal deviated from RMS’ disclosed cost accounting practices, and that the deviation led to “a significant increase in contract price.” RMS replied in July, 2006, “stating that it did not concur and that the alleged noncompliance [with disclosed cost accounting practices] had no cost impact.” DCAA issued its final audit report on September 22, 2006—seven years and one month after the contract price had been agreed-upon.

RMS’ Divisional Administrative Contracting Officer (DACO) issued an Initial Determination of CAS noncompliance on October 13, 2006. Discussions ensued. Eventually, on May 14, 2009, RMS communicated its final calculations regarding the cost impact of the alleged noncompliance. DCAA “evaluated” RMS’ analysis “and declared it to be inadequate” in a report issued June 28, 2011.

Yes, you read that correctly: DCAA took more than two years to determine that RMS’ cost impact analysis was “inadequate”. Unfortunately for contractors everywhere, that audit duration (and ultimate result) is far from unusual in the current audit environment.

The alleged inadequacy of RMS’ analysis did not prevent the DACO from issuing a Contracting Officer’s Final Decision on November 29, 2011, demanding $10,157,000 plus $6,885,884 in accrued interest. RMS appealed to the ASBCA.

To recap, in 2011 the government demanded that RMS pay $17 million, based on an alleged failure to follow disclosed cost accounting practices that took place in 1999. That’s a duration of 12 years between events giving rise to the alleged liability and the assertion of a claim for damages. As we’ve discussed many times before, the CDA SoL contemplates a duration of not more than six years.

Seems like an easy call for the Judge to make. And indeed, such seemed to be the case. Judge Melnick dismissed the Government’s claim as being “untimely and … therefore invalid.” The appeal was dismissed for lack of jurisdiction, meaning that Raytheon Missile Systems owed the Government nothing.

Yay, RMS. (Pending appeal.)

Judge Melnick made the following points in his decision that we want to bring to your attention.

  • The Government contended that RMS had the burden of proving that the Government’s claim was untimely. Judge Melnick disagreed, writing “By advocating in response to Raytheon’s motion that its decision is valid the government is effectively the proponent of our jurisdiction and therefore bears the burden of proving it under these circumstances.”

  • Judge Melnick discussed when the CDA SoL timeclock began to run in this case, writing “The events fixing liability should have been known when they occurred unless then can be reasonably found to have been either concealed or ‘inherently unknowable’ at that time.

  • The CDA SoL timeclock began to run in this dispute in 1999. Judge Melnick wrote, “Raytheon … disclosed sufficient facts to the government in 1999 to conclude it [the Government] should have known about the claim at that time. Accordingly, to the extent the government now claims the expanded special burden was effective on 1 January 1999, and that the Lockheed Martin subcontract should have received special burden under that expanded definition, Raytheon gave it all the information necessary to know of that claim in 1999.”

  • Judge Melnick wrote, “claim accrual does not turn upon what a party subjectively understood; it objectively turns on what facts are reasonably knowable.

The Government argued that what the price analyst knew was irrelevant, and that only the DACO’s personal knowledge mattered with respect to starting the SoL timeclock. (Echoing the position taken by Judge Delman in his Lockheed Martin decision.) Judge Melnick rejected that argument, writing—

The government fails to cite any authority supporting the proposition that claim accrual is based only upon the knowledge of the individual clothed by a contracting party with authority to assert the claim. If that were the case, then both contractors and the government could suspend accrual by internally compartmentalizing relevant information and insulating senior decision makers from it for as long as they choose. Nothing in FAR 33.201, which commences accrual of a claim when the events fixing alleged liability ‘were known or should have been known’ by a party, contemplates permitting such gamesmanship. Claim accrual is not suspended simply because the government may have been delayed appreciating the implications of what Raytheon had disclosed, or in funneling to the individual authorized to act upon the claim all of the information relevant to it.

As if he realized that he was disagreeing with another sitting ASBCA Judge, Judge Melnick wrote—

Accrual of a contracting party's claim is not suspended until it performs an audit or other financial analysis to determine the amount of its damages. … Damages need not have actually been calculated for a claim to accrue. … The fact of an injury must simply be knowable. … The fact the government waited until 2006 to declare in an audit report that these earlier materials provided that notice is irrelevant. Delay by a contracting party assessing the information available to it does not suspend the accrual of its claim. … These facts distinguish this appeal from Lockheed Martin Corp., where we held the government was not notified of overbillings until a DCAA draft audit discovered them. … Additionally, in the absence of misconduct by Raytheon rising to the level of trickery, once the claim accrued and the limitations period began to run, subsequent communications between Raytheon and the government about the claim's merits and magnitude did nothing to toll it. … There is no evidence of trickery here.

To sum this up, Judge Melnick’s decision—with its concise refutation of all government arguments as to why their claim for damages should be heard 12 years after the events that fixed the alleged liability took place—seemed to signal a return to a more “bright line” test of CDA SoL claim accrual. Assuming that other ASBCA Judges find Judge Melnick’s reasoning more persuasive that Judge Delman’s reasoning, the two major Contracts Disputes Act fora (the ASBCA and the U.S. Court of Federal Claims) may be narrowing their interpretative differences regarding SoL claim accrual.

Which is good news for contractors everywhere.

 

The SB Subcontractor Payment Rollercoaster

E-mail Print PDF

Roller_Coaster
In July, 2012, we told our readers about an OMB Memo that directed Federal agencies to pay their prime contractors more quickly, so that the primes could, in turn, pay their small business subcontractors more quickly. The Memo established a “one year, temporary, transitional” policy goal of paying the primes within 15 days of receipt of an invoice, so that the primes could pay their small business subcontractors within 15 days. The agencies were directed to “encourage” their prime contractors to modify their existing subcontracts with small business “without consideration or fees” to include “a clause providing that the prime contractor will pay the small business subcontractor along an accelerated timetable to the maximum extent practicable; and insert a similar clause in their future contracts with small businesses subcontractors.” The Memo also requested that the FAR Councils create a new contract clause that would require prime contractors to implement that policy, thus moving the policy from a matter of “encouragement” to a matter of regulatory compliance.

We opined at the time that the OMB Memo—

… would mean significant work on the part of the Primes. It might also impact the ‘accepted’ way that cash flow has been managed for many years. In particular, it puts in peril the disreputable ‘pay when paid’” contract term that leads to subcontractors financing the Prime Contractors’ cash flow.

Indeed, the FAR Councils heard OMB’s request, and opened FAR Case 2012-031 to make the appropriate regulatory changes. The public comment period ended February 19, 2013. Currently, the public comments are being consolidated by the FAR Secretariat.

Subsequently, we told our readers in August, 2012, that the Defense Procurement and Acquisition Policy (DPAP) Directorate had decided to jumpstart the matter by issuing a Class Deviation that included a new, mandatory flow-down, contract clause (52.232-99) that required—

Upon receipt of accelerated payments from the Government, the contractor is required to make accelerated payments to small business subcontractors to the maximum extent practicable after receipt of a proper invoice and all proper documentation from the small business subcontractor.

And there things have stood.

Until this week.

The thing that changed was that DOD ended its practice of providing accelerated payments to its prime contractors, about six months early. It documented its policy about-face in this DFARS Notice. According to the Notice, DOD now plans a “phased implementation” of the policy (whatever that means). The Notice also reminded us that “This action does not affect DoD's policy to assist small business prime contractors by paying them as quickly as possible after receipt of an invoice and all proper documentation, while also maintaining necessary DoD internal controls.”

Why did the DOD do a 180 degree turn on this matter?

Well, according to an article at the Federal Times,

Pentagon officials said changing these payment processes combined with other initiatives will add about $1 billion, or a few days [sic] worth, of available cash within working capital spending accounts. … The Pentagon is facing a $46 billion reduction to its 2013 budget between March and September should across-the-board defense spending cuts, known as sequestration, go into effect. Also complicating matters is that DoD is operating under a continuing resolution, which freezes spending at 2012 budget levels, creating an $11 billion shortfall from planned 2013 spending. The continuing resolution also keeps funds aligned in the same accounts as 2012, meaning new programs cannot start and ones that have been terminated are still receiving money. … The working capital fund pays for business-like activities, such as fuel, spare parts and office supplies. By law, the DoD must keep money in these coffers at all times; however, the amount of funds in these accounts is shrinking.

The Federal Times article reports that one of the causes of DOD’s shrinking working capital is the accelerated payments to its contractors—which we suppose is another example of the effect of unintended consequences.

Note: we are not saying that we don’t understand the drivers behind DOD’s policy change. We do. We just find the change to be both ironic and amusing.

Meanwhile, those prime contractors that heeded DOD’s “encouragement” and modified their subcontracts with small businesses are now stuck with the accelerated payment terms. Those prime contractors that modified their procurement systems to make the accelerated payment terms a part of their standard set of subcontract terms and conditions are stuck with the language.

Of course, it is certainly possible for the primes to do their own 180 degree turns, but reversing the previous changes will cost money and take time, and will take resources away from other matters. At a time when contractors are being driven to do more with less, this is (in our view) a great example of how government decisions impact contractors’ overheads … and why the Defense Department enjoys such a well-deserved reputation for driving up the costs of its goods and services.

 

 

Former DCAA Auditor in Hot Water Over Conflicts of Interest

E-mail Print PDF

A quick Friday note to get you all ready for the weekend. It’s a cautionary tale of how government ethics rules can entangle folks even with the best of intentions. It comes to us courtesy of the Alaskan Native News.

The Alaskan Native News reported that Jodi Ann Andres, a former DCAA auditor, had been indicted by a federal grand jury for (allegedly) violating federal conflict of interest laws. According to the news story, Ms. Andres worked for the DCAA from 2003 to 2006. During that period, “she was the primary auditor of cost proposals, labor rates and claims for the Missile Defense Agency.” The story reported—

The Alaska Aerospace Corporation, formerly the Alaska Aerospace Development Corporation, was established in 1991 by the State of Alaska to develop a high technology aerospace industry in the state. Alaska Aerospace became a contractor for the Missile Defense Agency in 2003 and under a five year contract, provided support for launches from the Kodiak Launch Complex in Kodiak, Alaska.

In September 2006, Andres left employment with the DCAA and began employment with Alaska Aerospace as its Controller. The indictment alleges that in July 2008, Andres represented Alaska Aerospace during communications and negotiations with the DCAA about the same Missile Defense Agency contract she had previously audited, with the intent to influence the DCAA about that contract, in violation of a lifetime restriction which barred such communications.

Well.

We’re not experts on Federal ethics rules. We’re not attorneys. So we have a hard time understanding how representing a contractor—years after the fact—on matters in which the auditor was significantly involved represents a conflict of interest. If she had known she was going to take the job while performing the audit, we’d get it. But such an allegation was not reported. Accordingly, we’re left wondering where the conflict of interest was to be found.

In the meantime, we should all pause and reflect on how the onerous and complex federal ethics rules can have an impact, literally years after one’s federal employment took place.

 

Court of Appeals Schools Court of Federal Claims on Definition of a Claim

E-mail Print PDF

You_Got_Schooled
Quite some time ago, we wrote this article with the rather snarky title, “Northrop Grumman Gets Schooled on Anti-Assignments Act.” The article addressed an appeal, filed by Northrop Grumman Computing Systems against the Department of Homeland Security, Bureau of Immigration and Customs Enforcement. The Judge Allegra of the Court of Federal Claims dismissed Northrop’s appeal, ruling that Northrop’s failure to disclose the fact that it had assigned its interest in the contract’s payments to ESCgov (who had then assigned its interest to Citizens Leasing Corporation) hid an important fact that might have affected the Contracting Officer’s Final Decision. As part of his ruling, Judge Allegra found that Northrop’s initial assignment was null and void, because it violated 31 U.S.C. § 3727 (more commonly known as one of the two Anti-Assignments Acts).

Judge Allegra found that Northrop’s failure to disclose the fact of the assignment of its payments to the Contracting Officer rendered its claim defective—and therefore he dismissed Northrop’s appeal of the claim for lack of jurisdiction. And that’s were things stood, until the U.S. Court of Appeals, Federal Circuit, reversed Judge Allegra’s decision in this decision.

Judge Reyna, writing for the Court, found—

A prerequisite for jurisdiction of the Court of Federal Claims over a CDA claim is a final decision by a contracting officer on a valid claim. … The CDA establishes some prerequisites for a valid claim. … In addition to the statutory requirements of the CDA, we assess whether a claim is valid based on the Federal Acquisition Regulation(s), the language of the contract in dispute, and the facts of the case. … In Reflectone, we held that the FAR sets forth only three requirements of a non-routine ‘claim’ for money: that it be (1) a written demand, (2) seeking, as a matter of right, (3) the payment of money in a sum certain. … While a valid claim under the CDA must contain ‘a clear and unequivocal statement that gives the contracting officer adequate notice of the basis and amount of the claim,’ the claim need not take any particular form or use any particular wording. … Northrop submitted a written claim letter to the CO in Northrop I. The letter contained clear allegations of the Government’s breach of specific contractual provisions, and it demanded a specific amount in damages. The letter was accompanied by the required certification statement, and it stated a clear request for a final decision along with the relief sought. As required by the CDA and the FAR, Northrop’s claim letter was ‘a clear and unequivocal statement’ that gave the CO adequate notice of the basis for the alleged breach and specified an amount of the claim. … Northrop’s claim letter thus satisfied all the requirements listed for a CDA ‘claim’ according to the plain language of the FAR. … Because Northrop was the proper party to bring the claim, we disagree that by omitting financing information Northrop failed to give the contracting officer adequate notice for the basis of its claim.

[Emphasis in original.]

Thus, because Judge Allegra had properly found that Northrop’s assignment was null and void, its failure to disclose that assignment had no bearing on the Contracting Officer’s ability to render a valid Final Decision. Accordingly, the Appellate Court found that Northrop had submitted a valid claim and the Court of Federal Claims should have heard its arguments. The CoFC’s decision was reversed, and the matter was remanded back to the CoFC “for adjudication on the merits.”

And so it goes in the world of government contracting.

 

 


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