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

SBIR Phase II Contractor Must Comply with CDA

E-mail Print PDF

Follow_the_Rules
We have often provided counsel to contractors who have Small Business Innovation Research (SBIR) programs, as they transition from the firm fixed-price contract type of Phase I into the cost-reimbursement contract type of Phase II. That transition requires planning and, almost always, a significant change in the way in which the business is managed. Too many small business contractors cannot make the necessary changes and, as a result, end up in a dispute with their government customers.

For one example of the foregoing, see the hard-to-believe case of PHI Applied Physical Sciences, Inc., which we discussed right here. For another example, take a look at our article on Inframat. For a third example, consider the hard lesson learned by Thomas Associates, Inc.

As we considered the challenges for a small business faced with the transition into cost-type contracting we found the entire topic to be depressing, so depressing that we wrote about the sad situation and noted that the House Armed Services Committee (HASC) had similar concerns about the environment in which small business defense contractors operated.

Now we have another example to add to the stack of sad stories: the appeal by Sperient Corporation of “DCAA’s failure to reimburse Sperient for direct and indirect costs,” which Sperient characterized as being breaches of contract. According to Judge Braden, “Sperient seeks $632,765 in damages of for indirect costs incurred in fiscal years 2007 through 2011 and $168,750 for direct costs related to the leased radar range incurred in fiscal years 2007 through 2010, for a total of $801,515.”

The issues first arose in September, 2012, when DCAA “disallowed indirect costs incurred.” Even though Sperient provided DCAA with “additional details supporting the direct costs incurred,” DCAA “took no action” and in March, 2013, Sperient filed its complaint at the U.S. Court of Federal Claims (CoFC).

“Now wait a second,” we hear you saying, “since when does DCAA get to make the final decisions in cost disallowances, and since when does a contractor get to file a complaint without going through the contracting officer?”

Indeed, the record seems to be murky, because Judge Braden did not see fit to explain DCAA’s role in the direct and indirect cost disallowances. All we know is that “The Military Departments … refused to reimburse various costs incurred by Sperient…” presumably based on the DCAA audit report or reports.

With respect to your second question, Judge Braden pondered the same issue. He concluded the CoFC lacked jurisdiction to hear Sperient’s case, because “the court has determined that the SBIR Phase II contracts in dispute are best construed as procurement contracts that require Sperient to obtain a final decision by the responsible CO, pursuant to the Contract Disputes Act.”

The thing of it is, Judge Braden acknowledged that Sperient’s arguments and precedents were “persuasive” even if ultimately not sufficient to win the argument. Sperient’s counsel, who was very knowledgeable about government contract matters, provided a strong showing that, in other (distinguishable) circumstances, a SBIR award had been found to be other than a procurement contract, and thus the procedural requirements of the Contract Disputes Act would not be applicable. Unfortunately for Sperient, however, its strong arguments did not prevail and the case was dismissed (without prejudice).

Now Sperient needs to go back to its contracting officer and get a final decision, which it must then appeal (again) before a court. Seems like a painful re-do, but if you’ve been reading our blog articles, then you know that the courts strictly construe the CDA’s requirements.

The lesson to be learned here is that it’s really not going to be possible to short-circuit the procedural requirements when you decide to take on the U.S. Government in a contracting dispute. As painfully long and expensive as the process is going to be, if you want to have your day in court, then you need to be prepared for it.

 

DCMA Moves Forward Without DCAA

E-mail Print PDF

Riding_Into_the_Sunset
In another one of those “we told you this was happening and now it has come to pass” sort of things, we report today that—in the words of DCAA leadership—“DCMA policy will now encourage completion of Forward Pricing Rate Recommendations (FPRR) within 30 days of Forward Pricing Rate Proposal (FPRP) receipt and to start Forward Pricing Rate Agreement (FPRA) negotiations within 60 days.”

What does that mean?

Well, we think it means that DCMA is tired of waiting for DCAA to complete its audits before entering into negotiations with the contractors.

That’s not to say that DCAA is solely to blame for the inability of the government to enter into FPRAs. DCMA has to bear some of the blame as well, since its process for approving FPRA negotiations is bureaucratic in the extreme. But the fact of the matter is that DCAA’s insistence on “GAGAS-compliant audits,” coupled with a new focus on accomplishing MAAR testing during routine audits (such as FPRA audits), has led to a situation where DCAA is simply unable to complete its audits in time to support DCMA’s negotiations.

Consequently, DCMA has issued new policy guidance that “emphasizes that the input of all technical specialists (including DCAA) is not required to complete the process unless it is necessary to close a critical gap of information. “ Let’s repeat that for emphasis: input from DCAA is not required anymore.

We learned of this change from DCAA itself, via issuance of a new MRD.

What else did we learn from the new DCAA MRD? We also learned that DCMA thinks it can move forward without DCAA because “DCMA is growing their cost monitoring function” and “DCMA believes that the FPRP audit should confirm information acquired during the cost monitoring process.”

Interestingly, the MRD tells DCAA auditors to keep on performing those FPRA audits, even though DCMA won’t be relying on them anymore. First of all, the MRD tells DCAA auditors to support DCMA audits by communicating “known audit issues” during DCMA negotiations. (This despite those known issues not being supported by any type of GAGAS-compliant conclusions.)

Second, the MRD tells DCAA auditors to issue their report despite the fact that an FPRA has been executed, so that the DCMA contracting officer can use the report’s findings to enter into a new (we assume more favorable to the government) FPRA. We can’t speak for all contractors, but we suspect that if the government wants to rescind the just-executed FPRA and implement lower billing rates, the contractor is not going to feel as if the government negotiated in good faith.

Furthermore, by the time DCAA issues its GAGAS-compliant audit report, we bet the contractor will have already submitted a new Forward Pricing Rate Proposal (FPRP), mooting DCAA’s findings to a very large extent.

This DCAA MRD may be the beginning of the end for the entity that once was inarguably the Federal government’s premier audit agency. If DCMA will no longer be relying on DCAA for Forward Pricing Rate input, where else can they do without the auditors?

One answer to that question comes from Redstone Consulting. In the firm’s recent blog article, it reported that—

… DCMA has started hiring auditors away from DCAA to perform, among other things, CAS disclosure statement reviews.  DCMA says they don't need a GAGAS compliant audit to make a determination of adequacy.  They only need enough information to make an assessment.  …  Of course one of our other former DCAA Managers is right with his assessment after I informed him of this latest blow to DCAA’s credibility.   DCAA Management probably wouldn't object.  With the agency’s apparent single-minded goal of increased dollars audited with corresponding savings   as evidenced in emphasized remarks in reports to Congress and other statements (i.e. $6.5 to $1 ‘ROI’), DCAA wouldn't mind getting rid of this apparent ‘non-value added’ effort.  Since they don't count towards dollars audited and they don’t contribute to cost questioned or ROI, why do them?

Is this the beginning of the end for DCAA? Lord knows we’ve predicted it before. So let’s not rush into any conclusions.

But it’s tough to argue that DCMA has not made a profound change to its FPRA negotiation approach by deciding to move ahead without input from DCAA. It’s a message to DCAA leadership from its single largest customer. One wonders where DCMA found the courage to make such a fundamental change.

In completely unrelated news, we heard through sources that Mr. Charlie Williams, Jr., Director of DCMA, has announced his impending retirement effective December, 2013.

 

Pratt & Whitney Joins 5% Withhold Club

E-mail Print PDF

This week Aviation Week & Space Technology reported that DCMA has decided to start withholding 5% of its payments to United Technology’s Pratt & Whitney subsidiary because of significant deficiencies in the company’s Earned Value Management System (EVMS). AWST reported—

EVMS decertification is not an indictment of a company’s technology or ability to deliver quality equipment. It does, however, indicate an inability of the Pentagon to certify the data on a company’s progress in executing programs. This means that the data could be flawed. ‘The EVM requirement is meant to protect taxpayers from overbilling and focuses on the business systems defense companies use to estimate costs for bids; purchase goods from subcontractors; manage government property and materials; and track for costs and schedule progress,’ said [the spokesperson for the F-35 Joint Program Office].

Yeah. That last part confused us as well. We’ll just assume he meant to describe the Business System DFARS clause, and move on.

That same AWST article also reported—

Pratt is working on four areas to improve its EVMS compliance: updating documentation to better align with process, improving how scheduling tools are managed and integrated, better cost estimating and forecasting, and improving planning for work packages. The company has submitted corrective action plans for each to DCMA for approval.

So there you go.

In that same article, AWST updated the status on Lockheed Martin’s EVMS-related payment withholds. We last reported on LockMart’s problems right here. That was about a year ago. Since then, DCMA has decided to drop its payment withhold back to 2 percent. AWST reported—

In late August, DCMA reduced the withholding on Lockheed Martin to 2% when it decided the company was ‘making significant progress on the approved corrective action plan,’ says Kenneth Ross, a Lockheed Martin spokesman. However, getting recertified is a painstaking process, as demonstrated by the long time that Lockheed Martin has been decertified.

Just to recap:

  • DCMA “decertified” LockMart’s EVMS (at its Fort Worth, TX plant) in October, 2010

  • In March, 2012, payment withholds of 2 percent were imposed

  • Payment withholds were increased to 5 percent in June, 2012 and the follow-up audit to evaluate LockMart’s corrective action plan was delayed for a year

  • In August, 2013, the follow-up audit found that LockMart had made significant progress on its corrective action plan, and payment withholds were reduced back to 2 percent.

So that’s the kind of experience that Pratt & Whitney can look forward to, now that it’s joined the 5 percent withholding club.

 

 

Concurrent Changes to Cost Accounting Practice

E-mail Print PDF

Examining_Legal_Decisions
This is one of those times when several different threads weave together into a story that demands to be written, even though distractions threaten to derail us from this task. Let us begin.

If you’ve been reading many of the roughly 700 articles on this site, you know several themes have emerged over the course of the past four or so years. One of those themes has been the increase in litigation between the government and its contractors—fueled by adversarial relationships, a general unwillingness to engage in negotiations leading to a compromise, and audit methodologies infused with built-in bias toward generating as much questioned cost dollars as possible. As a result of those factors contractors are too often put into a position where they must choose between acceding to what amounts to government-imposed extortion, or else lawyering-up and litigating the issues before a tribunal.

Another long-running theme has been the failure of the FAR Councils to understand the Cost Accounting Standards (CAS), particularly with respect to quantification of cost impacts related to voluntary (“unilateral”) changes in cost accounting practice. When FAR 30.6 and associated CAS contract clauses were revised in 2005, the FAR Councils essentially adopted the DCAA positions over loud objections from affected government contractors. Unfortunately for all concerned, since then those objections have proven to have been well-founded while the DCAA positions have proven to have been ill-founded.

One of the things that the rule-makers got wrong was the treatment of concurrent changes to cost accounting practice—where the contractor makes multiple changes at the same time, whose individual impacts offset each other. This plays into the interpretation of the phrase “in the aggregate” as it is used in CAS regulations. It also plays into the failure of the FAR Councils, DCMA, and DCAA to understand the difference between the statutory goal of “protect[ing] the Government from payment, in the aggregate, of increased costs” stemming from voluntary changes to cost accounting practice, and the current policy goal of recovering increased costs stemming from such changes.

With that background in mind, consider the following guidance from the CAS regulations–

A contract price adjustment undertaken under section 1502(f)(2) of this title shall be made, where applicable, on relevant contracts between the Federal Government and the contractor that are subject to the cost accounting standards so as to protect the Federal Government from payment, in the aggregate, of increased costs, as defined by the Cost Accounting Standards Board. The Federal Government may not recover costs greater than the aggregate increased cost to the Federal Government, as defined by the Board, on the relevant contracts subject to the price adjustment unless the contractor made a change in its cost accounting practices of which it was aware or should have been aware at the time of the price negotiation and which it failed to disclose to the Federal Government.

Which brings us to a recent decision by the Armed Services Board of Contract Appeals (ASBCA) regarding voluntary changes to cost accounting practice made at two segments of The Boeing Company. The decision came close to being a landmark decision, but missed because it only addressed a part of the controversy. Let’s discuss.

On January 1, 2005, Boeing initiated three voluntary (“unilateral”) changes in cost accounting practice, moving from one CAS-compliance practice to another at its Philadelphia segment. According to Judge Freeman, the impacts associated with each of those changes were as follows—

Change No. 1 $ (790.000) Decreased costs to the Government

Change No. 2 $ (289,000) Decreased costs to the Government

Change No. 3 $1,477,000 Increased costs to the Government

Net impact all changes $ 398,000 Increased costs to the Government

On the same date, Boeing initiated six voluntary (“unilateral”) changes in cost accounting practice at its El Segundo segment. The impacts associated with each of those changes were as follows—

Change No. 1 $(3,724.000) Decreased costs to the Government

Change No. 2 $(1,916,000) Decreased costs to the Government

Change No. 3 $(1,293,000) Decreased costs to the Government

Change No. 4 $ (260,000) Decreased costs to the Government

Change No. 5 $ 1,136,000 Increased costs to the Government

    Change No. 6 $ 206,000 Increased costs to the Government

Net impact all changes $(5,851,000) Decreased costs to the Government

A key tactic in the government’s (flawed) approach to analyzing cost impacts from concurrent changes is to ignore decreased costs to the government and focus only on changes that lead to increased costs—thus accepting the lower costs that will be passed on to it, while concurrently demanding repayment of the increased costs. (Apparently government policy makers do not regard this approach as generating a windfall. LOL.)

Because of the (flawed) approach, the parties could not resolve Boeing’s cost impacts and the dispute was still unresolved more than 5 years later. With literally days to go before the CDA Statute of Limitations was to expire, the cognizant contracting officers issued Final Decisions in which it was determined that Boeing owed the Government $1,477,000 for the single Philadelphia segment change and $1,341,840 for the two El Segundo changes (plus interest). As per policy, changes that led to decreased costs were ignored by the contracting officers. Need we say that Boeing appealed the COFDs?

Since Boeing disclosed and implemented its changes to cost accounting practice prior to the FAR Councils’ (flawed) CAS administration revisions, Judge Freeman decided the dispute based on the pre-2005 CAS and FAR language—which was silent on concurrent changes. For its part, Boeing argued that the phrase “in the aggregate” had to mean that all changes to cost accounting practices made at the same time had to be netted against each other. The Government argued that “FAR 30.606(a)(3) is to the contrary and dispositive of these appeals is without merit.” (Sic.) The Government argued that the 2005 FAR revisions merely clarified the previous statutory interpretation. The Judge rejected both parties’ interpretations.

Judge Freeman found a way to decide the dispute without interpreting the disputed language, which is why the decision falls short of being a landmark decision. In point of fact, many contractors have been subject to the Government’s “cherry picking” approach to quantifying cost impacts from concurrent changes to cost accounting practice and everybody desperately needed a bright line decision. Judge Freeman declined to provide that bright line.

Instead, Judge Freeman decided the dispute based on existing government guidance in effect at the time, which included DCMC (Defense Contract Management Command, now Defense Contract Management Agency) guidance to contracting officers and DCAA audit guidance. Judge Freeman wrote—

On this record of the ‘guidance’ and established practice of the government agencies primarily responsible for enforcing the cost accounting standards statute and regulations, we conclude that Boeing could properly combine the 1 January 2005 cost accounting practice changes at each segment for purposes of computing the aggregate cost impact to the government of the changes at that segment.

So that disposed of concurrent changes prior to the 2005 FAR revisions, but left unanswered the question of how to handle such changes after the revisions—i.e., did the FAR Councils have the authority to interpret CAS and, if they did have that authority, did they do so correctly?

(We note for the record that Judge Freeman declined to take judicial notice of the “interim” guidance of the DOD CAS Working Group. This was the body with authority to interpret CAS for the various entities within the Department of Defense, though the body was disbanded long ago. Looking at the guidance of WG 76-8, the Working Group wrote—

The combining, for offset purposes, of several accounting changes within a segment as long as they have the same effective date should also serve to reduce the number of necessary contract price changes. Although individual treatment of voluntary changes could maximize the potential for downward price adjustments, the government’s interests are adequately protected if no overall price increase is paid by the United States.

It’s too bad the FAR Councils ignored those words when, in 2005, it decided to adopt DCAA’s ill-founded positions without much in the way of critical thought. Now both parties are stuck with those ill-founded positions, which necessitate litigation and an appeal for a judicial interpretation based on equity and common sense.

The Boeing decision addresses and solves one facet of the problem, but other facets remain to be solved in future litigation. In the meantime, we expect the Government to file an appeal of Judge Freeman’s decision, because … well, because they can. 

 

Still Here

E-mail Print PDF

Yeah, it’s been a while since a blog article was published. As I told a concerned reader, I’ve had an article half-written for too long now. (Either an article gets written in one fell swoop, or it dies from lack of passion.) Every so often I pull it up and type a few more words … but so far it’s been a painful process akin to pulling teeth without anesthesia.

I’ve also been thinking about how the FAR Councils don’t understand what a final cost objective is, and how that lack of understanding negatively impacted the June 2011 revisions to the 52.216-7 Allowable Cost and Payment clause. But that article’s going to take quite a bit of work, and I can’t find the time or the energy.

I can find neither the time nor the energy to get articles written right now, because of both professional and personal issues. First, I’ve been up to my eyeballs with work at my primary employer. We’ve got a new incurred cost audit started and DCAA is playing hardball right now. (As is their right. No whining here.) And I’ve been having a time of it in the personal realm as well. Moving one’s family half-way across the country and putting the kids into new schools has a way of sapping a person’s attention, you know?

That’s not to say everything has been doom and gloom. It’s just that in the larger scheme of things, writing blog articles falls toward the bottom of the stack, somewhere between posting updates on Facebook and reading new headlines on Fark.com. Far below new Season 3 episodes of Person of Interest.

Which is to say: Please be patient.

I have not given up writing articles for this website. But as I told you, this is hiatus time.

I will return.

In the meantime, I am very pleased that the DOD has told DCMA and DCAA and DFAS folks to come back to work. Although I have professional differences with many civil service employees at the Department of Defense, nobody should be treated as a pawn in a game of power politics.

Welcome back to work, folks.

 


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