DOD Clarifies Implementation of the New CAS Threshold
We reported on the new CAS applicability threshold of $700,000 right here. One issue with the implementation of the higher threshold was how to deal with FAR solicitation provisions and contract clauses, which continued to use the old, superseded, threshold of $650,000. In our previous article (link above) we wrote—
One issue with this rule change is how to apply it to subcontracts under existing prime contracts. Although the CAS regulations have been revised, no similar revision has been made (yet) to the CAS Administration rules in FAR Part 30, nor have any revisions been made to the 52.230 series of CAS-related contact clauses. At the moment, the FAR language continues to use the now outdated $650,000 CAS applicability threshold.
We were not the only ones to figure out the problem. In fact (as we reported) one commenter raised the issue to the CAS Board itself, only to be told that addressing the issue was “beyond the authority of the CAS Board” and needed to be addressed by the FAR Councils. Given the FAR Council’s rule-making process, it will take some time—perhaps measured in months—to revised the FAR to conform to the CAS regulations.
Richard Ginman, current Director, Defense Procurement and Acquisition Policy (DPAP) decided that the DOD couldn’t wait for the FAR Councils to act. On January 31, 2012, DPAP issued a Class Deviation to DCMA Contracting Officers, providing them with revised solicitation provisions and contract clauses. The Class Deviation is linked here. The new provisions and clauses are to be used by Contracting Officers in “new solicitations and resultant contracts,” effective immediately.
The CAS-related provisions and clauses include the series 52.230-1 through 52.230-5. The provisions/clauses are to be used as directed by FAR 30.201-3 and 30.201-4—except the prescriptions in those FAR regulations “shall” be modified to read with the new CAS threshold of $700,000, instead of the current language, which contains the old, superseded, threshold.
For DOD Contracting Officers (and, presumably, for DOD Prime Contractors), problem solved.
DCAA/DCMA Discuss Run Rules for New Business Systems Rule
Apogee Consulting, Inc. has been focused on the new DFARS Business Systems rule since its ill-begotten conception back in early 2010. We submitted our comments and concerns to the DAR Council, and were disappointed that that interim rule (issued May 2011) addressed so few of our comments. Nonetheless, our anxiety was ameliorated somewhat by DCMA’s policy addressing implementation of the rule, which created a Contractor Business Systems Review Panel for the purpose of performing “a higher-level review of the COs final determination to disapprove a Contractor’s Business System, prior to notifying the Contractor in writing that the system is disapproved.”
We also reported on early implementation efforts, noting that it seemed that enterprise-wide systems (e.g., Accounting or EVM) might carry more financial risk than segment-specific systems, since significant deficiencies at one segment might trigger payment withholds across the enterprise if those deficiencies led to the entire system being disapproved.
Since that time, we’ve gathered up a few more tidbits of information for sharing with our readership.
First, DCMA has issued a process flowchart, updated its OneBook guidance, and created training for its contracting officers. You can find the Agency’s process flowchart and training slides on our site under “Knowledge Resources”—but only if you are a member. (Remember, membership has privileges!)
Second, DCMA held an “Industry Day” to discuss the new Business Systems rule on December 15, 2011. We weren’t invited (and couldn’t have attended even if invited), but we lucked into some good, detailed, notes from somebody who did attend that meeting. We’re going to cut-n-paste (with a little editing) from those notes for you.
A representative of DCAA told the audience the following–
-
DCAA’s system audits will be attestation compliance audits and will state whether the contractor is compliant or noncompliant with each of the system criteria listed in the applicable DFARS clause. The DCAA report will connect the [alleged] deficiency to the purpose statements in the DFARS Clause – i.e., what does the system ‘provide for’.
-
Any material weaknesses will be considered a system deficiency. However, DCAA is still determining whether any noncompliance with an individual system criterion will be considered a ‘significant deficiency’ within the meeting of the regulation. [Ed. Note: This was a concern that we raised to the DAR Council in our comments to the initial proposed rule.]
-
Regardless of the foregoing, DCAA does not intend to be prescriptive or to dictate a contractor’s system policy and procedures. DCAA acknowledges that the business system criteria are broad and there is more than one effective way to achieve the desired internal control objective.
-
DCAA will no longer issue Flash Reports as a means of identifying potential system deficiencies - they will issue a complete noncompliance report with adequate supporting detail. [Ed. Note: Finally! Good riddance to a terrible practice.]
Representatives from DCMA told the audience the following—
-
DCMA’s view is that the new Business Systems rule is not to be applied as a punitive rule. Audit reports and related withhold determinations need to address the government’s risk.
-
To ensure consistency in administration, Contracting Officers have been instructed to escalate and coordinate at the CACO level to ensure CACO/DACO agreement on proposed actions.
-
The contractor will receive a ‘substantial’ out-brief from the auditor (or DCMA functional specialist) before the audit report is issued. The out-brief may be written and/or verbal; the focus will be on ‘meaningful’ engagement and/or discussion, not just an exchange of paper.
-
If there is no reasonable expectation of harm to the Government then the deficiency would not be considered significant and the system would be approved.
-
While it is true that ‘a corporate wide system or Shared Service disapproval could impact an entire corporation,’ the focus will be on identifying where the risk is to the government. [Note: In other words, the contractor may be able to argue that a significant deficiency at one segment should not lead to payment withholds across the enterprise.]
-
While it is true that DCMA has established a Contractor Business System Review Panel, only ‘disagreements between the DCAA recommendation and the Contracting Officer determination’ will go to a DCMA Headquarters-level Board of Review.
-
A Contracting Officer may not make an Initial Determination regarding the adequacy of a specific business system until the contractor receives a contract containing both the DFARS Clause 252.242-7005 and the specific clause related to the system at issue.
-
If the contractor submits an effective Corrective Action Plan (CAP) as part of the contractor’s response to the CO Initial Determination, then the payment withhold could start at 2%.
-
Contracting Officers ‘will – not may’ – reduce withhold upon submission of an adequate CAP with milestones.
-
An adequate CAP must include discrete and measurable actions with realistic due dates and an explanation of how the corrective action plan will be monitored. The DCMA CO, in consultation with auditor or functional specialist, will monitor the contractor’s progress on the CAP. If the CO determines that the contractor is not making adequate progress, then the payment withhold will be increased. The Contractor should notify CO when the entity believes that the identified deficiencies have been corrected. The CO, with input from auditor/functional specialist, will determine whether all corrective actions have been completed, or whether there is a reasonable expectation (based on the evidence presented) to believe that the deficiencies have been corrected. If so, then the CO will approve the system and release the payment withholds.
-
DCMA’s Business System Instruction [in the OneBook] provides that a payment withhold is only applicable to CAS covered contracts valued at $50M or more, that contain the DFARS Clause 252.242-7005;. However, the CO can apply a payment withhold on one or more contracts valued at less than $50M with CMO Contracts Director approval. The DCMA letter notifying the contractor of implementation of payment withholds will include a listing of the contracts for which it is to be applied.
-
The Business System payment withhold is in addition to any fixed fee withholds because those withholds exist for different reasons
-
If a system is not already “Approved”, “Adequate”, “Accepted” or “Disapproved”, then it is considered “not evaluated”.
Apparently, some disagreement emerged between DCAA and DCMA regarding the responsibilities of a prime contractor when its subcontractor has had a system disapproved and payment withholds initiated. According to the meeting participant—
-
DCAA opined that subcontractors should withhold costs on cost-type invoices before submitting to prime contractor
-
DCMA stated that there is no provision in the rule to flow-down the withhold requirement from prime to subcontractor. In any case, there is no ‘privity of contract’ between the prime contractor’s CO and the subcontractor. According to the clause, the DCMA CO has the responsibility to implement payment withholds on Progress Payments and Performance Based Payments. Thus, the prime contractor can’t really step into the role of the CO to implement payment withholds. If this were even possible, how would it work in practice—would the prime contractor hold the money in its own bank account or somehow forward to the DCMA CO?
-
DCMA noted that subcontractors who have disapproved systems will have withholds implemented on their prime contracts, so they are incentivized to correct their systems in any case.
-
DCMA also noted that they still need to work out the implementation of payment withholds on Interorganizational Transfers.
From our perspective, it’s good to see that DCMA is figuring-out (and letting contractors know) how it will be implementing the new rule. We recommend that our readers carefully review the bullet points above and consider “socializing” the new run rules with employees. It would also seem desirable to review the “run rules” with government oversight officials in order to make sure everybody has the same understanding of how the payment withholds—should they be deemed necessary—will be implemented.
We note that DCAA has taken a hardline stance (as has become all too typical of the audit agency), asserting that the new rule applies to subcontractor invoices to prime contractors. While we are pleased to see DCMA (quite correctly) disagree with that position, we worry that DCAA will apply its flawed logic to its system reviews. DCAA might well assert that a prime contractor’s accounting system has a significant deficiency because subcontractors are not directed (by the prime) to implement payment withholds when the subcontractor’s business systems have been disapproved.
Despite potential problems we continue to be encouraged that DCMA is thinking through its process, and that the process appears reasonable (given the inherent problems in the rule itself). Obviously, the reasonableness of the process turns on the subjective nature of the definition of “significant deficiency” and how the DCMA COs will link the alleged significant deficiencies to the government’s risk of making overpayments to contractors.
The proof, as they say, will be in the pudding.
In the meantime, we’ll stay focused on DOD’s implementation of this new rule.
|
Some Labor Relations Costs Now Unallowable
We post this with the objective of completeness; we don’t expect that this will be news to many readers nor that it will impact many contractors to a significant degree. But here it is:
On November 2, 2011, the Cost Principle at 31.205-21 was revised. Here’s a link to the Federal Register announcement. But before we look at the revised Cost Principle, let’s recap the history that led to the revision.
On January 30, 2009—literally within days of taking office—President Obama issued an Executive Order entitled Economy in Government Contracting. The Executive Order stated—
It is the policy of the executive branch in procuring goods and services that, to ensure the economical and efficient administration of Government contracts, contracting departments and agencies, when they enter into, receive proposals for, or make disbursements pursuant to a contract as to which certain costs are treated as unallowable, shall treat as unallowable the costs of any activities undertaken to persuade employees -- whether employees of the recipient of the Federal disbursements or of any other entity -- to exercise or not to exercise, or concerning the manner of exercising, the right to organize and bargain collectively through representatives of the employees' own choosing. Such unallowable costs shall be excluded from any billing, claim, proposal, or disbursement applicable to any such Federal Government contract.
On October 30, 2009, the Executive Order was amended to read (in part) as follows—
Contracting departments and agencies shall treat as allowable costs incurred in maintaining satisfactory relations between the contractor and its employees (other than the costs of any activities undertaken to persuade employees to exercise or not to exercise, or concerning the manner of exercising, the right to organize and bargain collectively), including costs of labor management committees, employee publications, and other related activities. See 48 C.F.R. 31.205-21.
So it was only a matter of time before the FAR Councils started rule-making to implement the Executive Order(s). On June 14, 2010, a Notice of Proposed Rule-Making was issued for collection of public comments. The comments were reviewed and, essentially, completely ignored in drafting the final rule—as the FAR Councils made “just one minor editorial change” in response to public comments.
The Cost Principle was revised to add a new paragraph covering “persuader activities”—that is, “activities undertaken to persuade employees … to exercise or not to exercise, or concerning the manner of exercising, the right to organize and bargain collectively through representatives of the employees' own choosing.” Such persuader activities are unallowable.
Consistent with the amended Executive Order (and also consistent with the history of the Cost Principle and with the history of the Federal government’s policy towards contractors’ relationships with their workforce), costs incurred in “maintaining satisfactory labor relations” remain allowable.
As we stated at the beginning of this article, we don’t expect this revision to affect many contractors to a significant degree. Those that are affected by the revision likely already know about it. But we like to be complete about these things.
Moments of Transition
In late January, 2012, our “friends” at the Project on Government Oversight (POGO) noted that General James Cartwright (USMC, Retired), former Vice Chair of the Joint Chiefs of Staff, had joined the Board of Directors of Raytheon Company. Despite POGO’s somewhat mean-spirited insinuations to the contrary, the transition from military service to defense contractor is not at all unusual. There is no reason at all to believe that General Cartwright will do anything but add value as a senior advisor and leader of the Top 5 defense company.
POGO also reported that former Under Secretary of Defense Bill Lynn had accepted the position of CEO at DRS Technologies, a subsidiary of Finmeccanica.
We also want to report that Michael Thibault, former executive at DCAA and former co-chair of the Commission on Wartime Contracting, has found a new position after the sun-setting of the CWC—as Vice President of Government Finance and Compliance at DynCorp International. According to this report at FederalTimes.com, Thibault was expected to help DynCorp fight fraud, waste and abuse. Readers may remember that the CWC raked DynCorp, and other “contingency contractors” supporting operations in Iraq and Afghanistan, over the proverbial coals during several years of hearings.
The same FederalTimes.com report noted that former Department of Defense Inspector General, Gordon Heddell, had found a position with Booz Allen Hamilton, as a “senior executive advisor.”
Though POGO had some nasty comments regarding Lynn and Cartwright, they were noticeably kinder to Thibault and Heddell. In this blog post, POGO wrote—
Unlike some revolving door situations, the hiring of Michael Thibault and Gordon Heddell seems based more on higher principle than on purely political or economic gain. We can only hope that the skills they developed as watchdogs and fighters of fraud, waste, and abuse will continue to serve the public interest.
We think POGO treated the transitions of the “former watchdogs” differently than it treated the transitions of the former DOD leaders. At best, POGO displayed an interesting level of naiveté if it attributed the hiring of Thibault and Heddell to a “higher principle than … purely political or economic gain.” We see the transitions of Lynn, Cartwright, Thibault, and Heddell as essentially being equivalent in both form and substance.
One transition that is a bit different from those we’ve discussed heretofore—and also a bit sadder—is the rather abrupt retirement of (Admiral) Jim Maslowski (US Navy, Retired) from his position as President of Hawker Beechcraft Defense Company (HBDC). Readers may remember our article on the travails of HBDC as it pursued award of the Light Air Support (LAS) contract, and its subsequent bid protests. In our article we focused on questions regarding the HBDC Contracts Manager, who apparently left a critical piece of correspondence in his in-box for two weeks before reading and acting on it. We wrote—
Was the HBDC contracts manager sick or on vacation? Was he or she busy with other pressing matters? The GAO didn’t say and we may never know. But still, it says something (to us, anyway) that correspondence from a customer regarding a competition for what was potentially more than a billion dollars’ worth of business just sat in an in-box for two weeks. … HBDC … has to explain (to its Board of Directors and shareholders, if to nobody else) why a critically important piece of correspondence lay unopened for two weeks, letting regulatory deadlines lapse in the meantime. (We would not want to be in that contracts manager’s seat right now….)
Not to mention, of course, why its proposal for such a ‘must-win’ competition was so flawed that the Air Force threw it out as being (essentially) uncorrectable. Did HBDC have the right skill sets? Did they put the company’s varsity team on the proposal? What went wrong?
We focused on the poor HBDC Contracts Manager, but apparently we should have aimed higher. The HBDC Board of Directors apparently held Admiral Maslowski responsible for the fiasco we described in our article. His departure was abrupt and unplanned-for, as the company has appointed an interim President while they search for a suitable successor. In the meantime, though, Admiral Maslowski isn’t disappearing entirely. The company’s press release stated, “Upon retirement, Maslowski will continue as a consultant to HBDC and its business development efforts with the title of Vice Chairman, HBDC.”
We have no doubt Admiral Maslowski will continue to be paid as a consultant. We assume that was a part of his negotiated exit deal. As to whether he will actually perform any “business development” efforts in return for those transitional consulting fees … well, let’s just say that experience has made us a bit cynical in that area.
J. Michael Straczynski has written—
The future is all around us, waiting, in moments of transition, to be born in moments of revelation. No one knows the shape of that future or where it will take us. We know only that it is always born in pain.
As we look at these five men moving through their moments of transition, we wonder what the shape and direction of their future will be.
|