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

Court of Federal Claims Clarifies CAS 418

E-mail Print PDF

If you’ve been in this government contract cost accounting and compliance business long enough, you have come to realize that the regulations and the agency guidance aren’t the end of the matter.  Usually, it takes litigation to clarify what the regulations mean, and to determine if the agency guidance is (or is not) correct.  Which is why we here at Apogee Consulting, Inc. spend a lot of time on the internet, looking at Court and Board decisions to see the judicial interpretations of the Federal Acquisition Regulation (FAR) and the Cost Accounting Standards (CAS).  We routinely check out decisions at the Court of Appeals (Federal Circuit), the Court of Federal Claims, and the Boards of Contract Appeal, to see how they might impact our clients.  And we post our (layperson’s) thoughts about those decisions here in our blog.

This is one of those times.

Motions for summary judgment that are dismissed are not the final decisions of the judicial body.  Normally that means there are issues of fact that need to be tried, and thus a final decision will be forthcoming in the future.  But recently, the Judge Lettow of the Court of Federal Claims (CoFC) dismissed governmental motions for summary judgment and, in doing so, gave us a thorough discussion of the application of CAS 418.

Let’s look at that decision, shall we?

Sikorsky Aircraft Corporation, long-time maker of helicopters, filed an appeal of an Administrative Contracting Officer’s final decision alleging the company was in noncompliance with CAS 418.  According to the DCAA and the ACO, Sikorsky owed about $80 million because it had improperly allocated the indirect costs of its “materiel overhead” pool in violation of the requirements of that Standard.  The government filed several motions for summary judgment and, in the Court’s words—

In essence, by the pending motions, the parties have asked the court to provide a general interpretative framework for the most relevant Cost Accounting Standard, 48 C.F.R. § 9904.418, and in particular Section 9904.418-50, to guide their preparation of the consolidated cases for trial and final disposition.

In crafting his decision, Judge Lettow needed to be mindful of several Federal Circuit Appellate Court decisions.  The first decision was the infamous travesty of a judicial ruling (in our opinion, naturally) found in Rumsfeld v. United Techs. Corp., 315 F.3d 1361, 1369 (Fed. Cir. 2003).  The second decision was a more recent Federal Circuit decision in M. Maropakis Carpentry, Inc. v. United States, 609 F.3d 1323 (Fed. Cir. 2010).  As we’ll point out, Judge Lettow took great pains to address those issues and to position his decision to survive appeal at that level of the judiciary.

The Judge’s decision started with a review of the CAS Board history and put CAS 418 in that historical context.  As Judge Lettow wrote—

Of particular interest to the pending motions in this case is CAS 418, which sets out how contractors may distribute indirect costs, such as overhead, among their contracts. Specifically, CAS 418 specifies accounting practices for ‘the consistent determination of direct and indirect costs,’ ‘the accumulation of indirect costs . . . in indirect cost pools,’ and ‘the selection of allocation measures based on the beneficial or causal relationship between an indirect cost pool and cost objectives.’

Next, the Judge listed several “basic accounting concepts.”  These included the definitions of direct and indirect costs, as well as the definition of “cost allocation”.  For example, he wrote—

Indirect costs are apportioned according to an allocation method (also termed an allocation base, allocation basis, or cost driver), the selection of which is subject to detailed criteria. See id. § 9904.418-50. An allocation method, essentially, guides how an indirect cost is to be distributed among multiple cost objectives. For an indirect cost, an allocation method should be chosen based on the “causal or beneficial relationship,” id. § 9904.418-40(c), between the indirect cost pool and the final cost objectives, i.e., the allocation base should distribute the indirect cost to final cost objectives in a manner accurately reflecting each cost objective’s fair share of the indirect cost.

It what seems to us to be the Judge’s great pains to give the Federal Circuit some clue as to the concept of cost allocation, the paragraph quoted above included a footnote, which read as follows—

A relatively straightforward example would arise if two families, one of two adults and a child, the other of just two adults, shared a $60 meal. The $60 could be allocated between the families by several allocation measures. If the child eats little, it would be sensible to select the number of adults as the allocation measure: $60 divided among four adults is $15 per adult, and there are two adults per family, so each family would bear $30 of the cost. If the child eats as much as the adults, then a suitable allocation measure would be the number of persons: $60 divided among five persons is $12 per person, so the three-person family would bear $36 and the two-person family $24. See Ramji Balakrishnan et al., Managerial Accounting 88-90 (2009). If the child is a teenager who eats an extraordinary amount, a pounds-eaten allocation measure would be more appropriate. Assuming six pounds of food is eaten at the dinner, the food cost of $60 would be allocated at a rate of $10 per pound. If the four adults eat one pound each, and the child eats two pounds, the two-adult family, together eating 2 pounds, would bear $20 in costs, while the family with the child, together eating 4 pounds, would bear $40 in costs. For a more sophisticated example, see 48 C.F.R. § 9904.418-60(e).

Now that a context had been established, Judge Lettow turned to the merits of the case.  The dispute concerned the proper cost allocation base to be used for Sikorsky’s materiel overhead.  The materiel overhead pool collected “costs of the purchasing department, of receiving and inspecting the materi[e]l, and of its storage and transportation.”  The Judge continued—

Prior to 1999, Sikorsky allocated its materiel overhead cost pool to contracts by a materiel cost base. ‘In other words, Sikorsky allocated a portion of the materi[e]l overhead costs to each [g]overnment and commercial contract based on the cost of materi[el] associated with the contract.’ ...  According to Sikorsky, however, a materiel cost base distorted the relative costs of Sikorsky’s contracts because it did not account for the indirect costs of government-furnished materiel (‘GFM’) — items like engines that the government purchases elsewhere and provides to Sikorsky at no cost for further assembly. ...  ‘As a result, under Sikorsky’s pre-1999 accounting practice the value of GFM was not included in the materi[e]l cost base used to allocate the cost of materi[e]l overhead. Because GFM was excluded from the materi[e]l cost base, costs Sikorsky incurred when it received, handled, or inspected . . . GFM were under-allocated to [g]overnment contracts for which that work was performed.’  Consequently, on January 1, 1999, Sikorsky began allocating its materiel overhead cost pool on a direct-labor-cost basis.

At the time Sikorsky made its allocation base change, the DCMA Corporate Administrative Contracting Officer (CACO) found that it created no material cost impact to CAS-covered contracts.  However, “more than five years later,” DCAA issued an audit report finding that Sikorsky’s allocation base was in “potential noncompliance with CAS 418,” which required Sikorsky to negotiate with a new CACO.  According to Sikorsky, the matter was resolved by agreeing to a prospective change in allocation base.  (The new allocation base was not specified in the decision.)  But according to the government, that did not end the matter.  As the Judge wrote—

Two years later, on April 5, 2007, Sikorsky’s new CACO, Frank J. Colandro, relied on the same DCAA audit report issued in 2004 to submit a fresh notice to Sikorsky stating that its pre-2006 accounting practice potentially violated CAS 418. … Sikorsky protested that CACO Sherwood had approved its earlier practice and CACO Weisman had resolved the issues arising from the 2004 audit report. … Nevertheless, Mr. Colandro, on behalf of the Defense Contract Management Agency (‘DCMA’), issued a contracting officer’s final decision against Sikorsky. … The decision found that Sikorsky’s pre-2006 accounting practice violated CAS 418, that the practice became material in 2003, and as a result Sikorsky had overcharged the government respecting its contracts. Id. The decision ordered Sikorsky to pay the government $64 million in principal and $15 million in interest.

But before the Court could rule on the CAS matters before it, it first had to rule on the government’s motion to dismiss Sikorsky’s “protective, defensive claim” it had filed under a reasonable fear that its defenses wouldn’t be allowed under the Maropakis Doctrine.  The Maropakis Doctrine is another one of those WTF? decisions out of the Federal Circuit. Here’s a good summary from McKenna Long & Aldridge.

In its Maropakis decision, as the attorneys at McKenna Long wrote, “the Federal Circuit held that a contractor’s failure to present a certified claim for time extensions under its contract barred it from presenting any factual defenses to the government’s liquidated damages claim.”  In other words, the contractor was prevented from asserting factual defenses against the government’s claim, because it had failed to first submit a certified claim in accordance with the Contracts Disputes Act.  Though Judge Newman emphatically dissented from the opinion, writing that it was “contrary to the purposes of the CDA, contrary to precedent, and an affront to the principles upon which these courts were founded,” it stands as current precedent.  The MLA attorneys summed-up the situation thusly—

Now, when challenging a Contracting Officer’s final decision assessing liquidated damages, contractors must consider submitting a formal claim for recovery per the CDA prior to appealing the liquidated damages assessment, especially where the government sets-off the assessment against contract balance. Based upon the Federal Circuit’s far-reaching decision, a contractor could be held to have waived its ability to present a factual defense to a liquidated damages assessment if, prior to its appeal, it fails to embed such a defense in a corresponding claim to modify/adjust the contract and/or recover the assessed amounts.

Consequently, Sikorsky filed a claim with the ACO that presented its affirmative defenses in its CAS 418 dispute, in order to preserve its right to raise them at trial.  The ACO declined to issue any decision, because the matter was in litigation.  Sikorsky appealed that deemed denial of its claim.  So now the Court had two, related, appeals to adjudicate.  Naturally, the government moved to dismiss Sikorsky’s claim.

The whole course of action was ridiculous, but it was also the logical outcome of the Federal Circuit’s Maropakis decision.  Nice job there, Feds.  Way to promote judicial economy.In any case, Judge Lettow was able to deal with the matter succinctly.  First, he was able to distinguish between the current CAS 418 case and the Maropakis case.  Second, he dismissed the matter based on simple logic.  The Judge wrote—

Sikorsky need not be put to the Hobson’s choice of preserving its affirmative defenses only through its original complaint or not at all. … On the assumption that Maropakis does not apply to Sikorsky’s affirmative defenses, the court would continue to entertain Sikorsky’s affirmative defenses as pled in Sikorsky’s first complaint. Alternatively, if Maropakis’ filing requirement does apply to Sikorsky’s affirmative defenses, then this court manifestly has jurisdiction over Sikorsky’s second complaint (and, again, also over Sikorsky’s affirmative defenses). … If Maropakis applies to Sikorsky’s affirmative defenses, the contracting officer’s choice to decline issuing a final decision on Sikorsky’s second set of claims would be incorrect: the claims would not have been already in litigation, so the contracting officer should have issued a final decision within 60 days or a reasonable time. … The officer’s inaction thus would be deemed a denial, and appeal of that denial via the complaint in No. 10-741C would be jurisdictionally proper. … If Maropakis does not apply, then Sikorsky’s second complaint would be merely redundant.  Consequently, on these grounds, the court denies the government’s motion to dismiss Sikorsky’s complaint in No. 10-741C.

Having disposed of the pesky Maropakis decision, the Court next turned to the heart of the matter: compliance with CAS 418.

Judge Lettow wrote that “the central issue in this case is whether Sikorsky’s allocation of its materiel overhead pool contravened the requirements of” CAS 418-50.  The Judge wrote that there were two “mutually exclusive sets of requirements” in that section of the Standard.  One set of requirements, found at 418-50(d), pertains to “indirect cost pools containing ‘a material amount of the costs of management or supervision,’” whereas the second set of requirements (found at 418-50(e)) pertains to “such pools that ‘do not include material amounts of the costs of management or supervision.’”  (Emphasis added by the Judge.)  Sikorsky and the government disagreed about which set of requirements should be applied to the evaluation of Sikorsky’s materiel overhead pool.  Resolution of that disagreement would go a long way towards resolving the appeal.

The Judge summarized the parties’ positions thusly—

Sikorsky contends that the key to whether Subsection 418-50(d) or 418-50(e) applies to a pool is whether that pool includes ‘a material amount of the costs of management or supervision.’ … Thus, in Sikorsky’s view, pools containing significant management or supervision costs, as a quantitative measure, are governed by Subsection 418-50(d), and those that do not are governed by Subsection 418-50(e). … In contrast, the government argues that the key to determining whether Subsection 418-50(d) or 418-50(e) applies to a pool turns on the phrase that follows ‘material amounts of the costs of management or supervision,’ i.e., ‘activities involving direct labor or direct materi[e]l costs.’ … (emphasis added)…. The government avers that the CASB was not concerned with whether indirect pools contained management costs, but whether they collected costs of activities ‘hav[ing] a direct and definitive relationship . . . [to] benefiting cost objectives.’

[The government’s] interpretation of Subsections 418-50(d) and (e) serves as the textual touchstone for the government’s chief argument: the government posits that Subsection 418-50(d) sets out the allocation rules for indirect cost pools collecting overhead costs, which costs have a tenuous relationship to cost objectives, while Subsection 418-50(e) sets out the allocation rules for indirect cost pools collecting costs of service centers, which are more directly attributable to cost objectives. … As the government would have it, pools containing management costs are entirely governed by another Cost Accounting Standard, viz., 48 C.F.R. § 9904.410 (‘CAS 410’). … Therefore, reasons the government, because overhead pools fall strictly under Subsection 418-50(d), and because Sikorsky’s materiel overhead pool is an overhead pool, the factual inquiries at trial should be limited to whether Sikorsky’s pool complied with Subsection 418-50(d).

The Judge’s reasoning, which we will quote extensively below, is clearly written to address concerns raised by the Federal Circuit in reversals of prior CAS decisions of the lower Court.  For example, much is made of the “plain meaning” and use of “standard dictionary definitions” and significant effort is made to point out that no special accounting definitions are being applied. Keep in mind that the Federal Circuit has expressed suspicion regarding use of complex accounting terms and has clearly shown favor for such “Joe the Plumber” dictionary definitions.  It seems to us that Judge Lettow was trying very hard to forestall those potential Appellate-level objections to his CAS analysis while he was setting-forth his interpretation of how CAS 418-50 operates.  He wrote—

The plain language of Subsections 418-50(d) and 418-50(e) demarcates indirect cost pools based on two criteria: first, whether the pools contain significant management or supervision costs, and second, whether the activity being managed or supervised involves direct labor or direct materiel costs. Thus, Subsection 418-50(d) applies only to ‘an indirect cost pool which includes [1] a material amount of the costs of management or supervision [2] of activities involving direct labor or direct materi[e]l costs.’ … (bracketed numbers added). Conversely, Subsection 418-50(e) applies to ‘indirect cost pools [1] that do not include material amounts of the costs of management or supervision [2] of activities involving direct labor or direct materi[e]l costs.’ … (bracketed numbers added) (emphasis added). In short, both types of indirect cost pools use the words ‘activities involving direct labor or direct materi[e]l costs.’ … Nonetheless, not all of the costs in an indirect cost pool may involve direct labor or direct materiel costs, and this circumstance may vary somewhat depending upon which Subsection is involved. Rather, the Subsections are primarily differentiated based upon whether the indirect cost pools involved contain significant amounts of management and supervision costs.

The regulation defines neither ‘management’ nor ‘supervision.’ Consequently, they ‘will be interpreted as taking their ordinary, contemporary, common meaning.’ Perrin v. United States, 444 U.S. 37, 42 (1979) …; see Rumsfeld, 315 F.3d at 1370 (applying ‘standard dictionary definitions and other pertinent regulations’ to determine the meaning of undefined CAS terms); ATK Thiokol, Inc. v. United States, 68 Fed. Cl. 612, 630-31 (2005). The word ‘management’ is a nominal of the verb ‘manage,’ which means ‘[t]o direct or control the use of; . . . [t]o exert control over; . . . [t]o direct or administer (the affairs of an organization, estate, household, or business).’ American Heritage Dictionary of the English Language 792 (New Coll. ed. 1976). Correlatively, the noun ‘supervision’ stems from the verb ‘supervise,’ which means ‘[t]o direct and inspect the performance of (workers or work); oversee; superintend.’ Id. at 1292; see also Random House College Dictionary 811, 1320 (rev. 1st ed. 1975); Webster’s Third New International Dictionary 1372, 2296 (16th ed. 1971). The words have no special meaning for accountants or auditors. See Erik Banks, Palgrave Macmillan Dictionary of Finance, Investment and Banking 317-19 (2010) (no entry for ‘management’); id. at 496-97 (no entry for ‘supervision’); David O’Regan, Auditor’s Dictionary 176-78, 250 (2004) (‘management’ defined as ‘[t]he process of directing, controlling, and planning in an organization’ and ‘supervision’ defined as ‘[t]he oversight, review, and correction of a matter,’ id. at 250); Oxford Dictionary of Accounting 272-73, 404 (4th ed. 2010) (no entry for ‘management’ or ‘supervision’); Joel G. Siegel & Jae K. Shim, Dictionary of Accounting Terms 269-72, 429 (3d ed. 2000) (same). …

This plain language refutes the government’s contention that the phrase ‘management or supervision of activities involving direct labor or direct materi[e]l costs’ denotes the concept of an overhead cost pool for Subsection 418-50(d) and the same language refers specifically to service-center pools for Subsection 418-50(e). Had the CASB ‘intended for [these subsections] to carry a specialized — and indeed, unusual — meaning . . . , [the CASB] would have said so expressly.’ … (‘Reluctance to working with the basic meaning of words in a normal manner undermines the legal process.’); cf. Perry, 47 F.3d at 1138 (There is ‘no reason to believe the CASB would publish incomplete, and possibly misleading, illustrations.’). Section 418-50 does not mention overhead, service center, or other particular kinds of indirect cost pools. Instead, the language only refers to indirect cost pools generally, differentiating them insofar as they encompass ‘management or supervision of activities involving direct labor or direct materi[e]l costs.’

[Emphasis added by us.]But the Judge wasn’t finished (and so neither are we).  

He continued—

The plain language of the triggering portions of Subsections 418-50(d) and (e) admit only one interpretation. Even so, the court must ensure that the interpretation is not manifestly mistaken in light of the regulatory context. See … (dismissing plain language arguments that ‘would frustrate the undeniable purpose of [a CAS] provision,’ id. at 1374). The stated purpose of this portion of the CAS is ‘to provide for consistent determination of direct and indirect costs; to provide criteria for the accumulation of indirect costs, including service center and overhead costs, in indirect cost pools; and, to provide guidance relating to the selection of allocation measures based on the beneficial or causal relationship between an indirect cost pool and cost objectives.’ … (emphasis added). The second clause of the statement refers to both service center and overhead costs, but it does so in a way that suggests they should be grouped together, not separately. In this respect, the third clause states that all indirect cost pools should be allocated ‘based on [their] beneficial or causal relationship [to] . . . cost objectives.’

Other portions of CAS 418 elaborate on these relationships. Section 418-40 explains that pools with significant management costs have a more attenuated causal relationship to cost objectives than do pools without significant management costs. ‘If a material amount of the costs included in a cost pool are costs of management or supervision of activities involving direct labor or direct materi[e]l costs, resource consumption cannot be specifically identified with cost objectives.’ … This is because, as Sikorsky observes, ‘[t]he costs of managing or supervising activities of employees whose own work involves various contracts are further removed from the benefiting contracts. As a result, indirect cost pools that include significant management or supervision costs ‘cannot be allocated on measures of a specific beneficial or causal relationship.’’ … Therefore, ‘in that circumstance, a base [is] used which is representative of the activity being managed or supervised,” i.e., a base among the alternatives provided by Subsection 418-50(d).

Conversely, if a ‘cost pool does not contain a material amount of the costs of management or supervision of activities involving direct labor or direct materi[e]l costs, resource consumption can be specifically identified with cost objectives.’ … This is because the pool’s activities are more directly associated with cost objectives. Consequently, the pool’s costs can be allocated more precisely, i.e., ‘[t]he pooled cost [can] be allocated based on the specific identifiability of resource consumption with cost objectives . . . in accordance with the criteria set out in 9904.418-50(e).’ Id. The regulation’s illustrations bear out this analysis. See id. § 9904.418-60(e) (commenting that a weighted-square-foot basis for allocating occupancy costs ‘adequately reflect[s] the proportional consumption of resources,’ as required by Subsection 418-50(e)); id. § 9904.418-60(f) (noting that a dollars-of-materiel-issued basis for allocating the costs of a materiel-related overhead pool ‘varies in proportion to the services rendered,’ as required by Subsection 418-50(e)).

The Judge continued, reciting the history of the Standard’s development and discussing both published and unpublished comments.  We’ll spare you that recital, though it’s an excellent resource for those who may want to read it.  The Judge summed-up as follows—

The plain language of 48 C.F.R. §§ 9904.418-50(d) and (e) divides indirect cost pools by inclusion, or not, of significant costs of management or supervision of activities related to direct labor or materiel costs. Pools containing such significant costs are governed by Subsection 418-50(d); pools without such costs are governed by Subsection 418-50(e). This interpretation is supported by the regulation’s overall operation and purpose, and by the relevant regulatory history. Consequently, whether Sikorsky’s materiel overhead pool falls under Subsection 418-50(d) or under Subsection 418-50(e) turns on whether the pool contained significant costs of management or supervision of direct-cost activities.

The government’s motions were denied and the case will proceed to trial, where it will be determined whether or not Sikorsky’s materiel overhead pool contained a “material” amount of the costs of management or supervision of the activities related to direct labor or materiel costs.  Meanwhile, we practitioners of CAS and other related matters of government contract cost accounting compliance have an important resource to use, in order to better understand the operation of CAS 418.
 

Supply Chain Transparency

E-mail Print PDF

Our long-time readers know that we have a “special place” in our hearts for supply chain management. Our efforts advising program teams have convinced us that effective management of the program supply chain is the single most important key to program success. We’ve also ranted and raved about supply chain security and making sure counterfeit parts are excluded from qualified parts.

But we’ve never linked supply chain management with human trafficking.

Like many compliance professionals, we know about the FAR’s prohibition on engaging in such abhorrent activities.  We’ve opined before that the FAR prohibition goes too far, actually making engagement in legal commercial sex transactions a contract violation that could lead to contract termination.

But did you know that on January 1, 2012, the California Transparency in Supply Chains Act becomes effective?  The attorneys at Venable LLP knew it, and they wrote up a summary right here. According to Venable, the new California law applies to retailers and manufactures doing business in California, if they have total annual sales of at least $100 million.

The Venable summary reports that the law requires covered companies to report on five areas, as follows—

1. Disclose the extent to which the company engages in verification of product supply chains to evaluate and address risks of human trafficking and slavery. The disclosure shall specify if the verification was not conducted by a third party.

2. Disclose the extent to which the company conducts audits of suppliers to evaluate supplier compliance with company standards for trafficking and slavery in supply chains. The disclosure shall specify if the verification was not an independent, unannounced audit.

3. Disclose the extent to which the company requires direct suppliers to certify that materials incorporated into the product comply with the laws regarding slavery and human trafficking of the country or countries in which they are doing business.

4. Disclose the extent to which the company maintains internal accountability standards and procedures for employees or contractors failing to meet company standards regarding slavery and trafficking.

5. Disclose the extent to which the company provides company employees and management, who have direct responsibility for supply chain management, training on human trafficking and slavery, particularly with respect to mitigating risks within the supply chains of products.

Whew! That’s quite a lot of disclosing to do. As Venable notes, “while compliance with the new law is simple insofar as all that is technically required is disclosure of what a company is doing to combat slavery in its distribution chain, the type of meaningful compliance necessary to enable a company to certify that it has met, and continues to meet, each of the five requirements noted above may require substantial effort.”

We continue to believe that effective management of suppliers/subcontractors is the key to program execution success. That being said, we recognize that, in this era of budget pressures and cost-consciousness, it’s perhaps unpleasant to have to contemplate adding staff and increasing the scope of activities in the realm of “supply chain management.” But with DCAA being “under-resourced” and hence unwilling and/or unable to perform its historical role in auditing subcontractors, the burden now falls more heavily on the primes and upper-tier subcontractors to “get their hands dirty” by auditing their lower-tier subcontractors’ pricing, business systems, CAS compliance, compliance with the Foreign Corrupt Practices Act, and other matters.

And now, we can all add compliance with California SB 657 to the list of things with which to be concerned.

What are you doing about adequately managing compliance risk in your supply chain?  We bet it’s not enough.

 

ASBCA Demonstrates Knowledge of FAR Cost Allowability Rules, Not So Much on FAR Contract Administration Processes

E-mail Print PDF

An old legal adage says that “bad cases make bad law”.  By this we take it that bad rulings make hard compliance.  A recent ASBCA ruling on a motion for reconsideration in the appeal of SRI International (ASBCA No. 56353, issued October 5, 2011) is a good exemplar of what we mean.

SRI International’s original appeal to the Board under the Contract Disputes Act concerned the allowability of Letter of Credit (LOC) fees over a two-year period.  The Board found that the costs were allowable.  As the Board decided—

When the government disallows costs on the basis of a FAR cost principle, the burden is on the government to prove that the costs are unallowable. … In disallowing SRI's LOC costs … the government relies solely on FAR 31.205-20. In pertinent part, this cost principle disallows ‘costs of financing...capital.’ ’Capital’ is defined to mean ‘net worth plus long-term liabilities.’ … SRI has treated all of the $25 million worth of bond debt… as a part of its ‘Current liabilities.’ ... Thus, even though the … Bonds have a maturity date of 2028, from an accounting standpoint, SRI's financing of its renovation project has actually been, and is, raising capital in the short-term, not long-term.

The government has not challenged as inappropriate SRI's treatment of the full amount of its long-term bond debt as a part of its ‘Current liabilities.’ It has not explained why FAR 31.205-20 disallowing the cost of financing—which specifically defines capital as ‘long-term liabilities’—is applicable in view of that treatment. We conclude that FAR 31.205-20 is inapplicable to disallow the fees SRI paid for the LOC required to secure its long-term bond debt in the short-term (one year).

So that would be the end of the matter, with the Board finding that SRI’s Letter of Credit fees to be an allowable indirect expense, but for the government’s motion for reconsideration.

In its motion, the government did not challenge the Board’s ruling that SRI’s LOC costs were allowable; instead, the government asked the Board “to clarify the portion of the decision that could be interpreted as making a lump sum monetary award plus interest.”

In its original ruling, the Board stated, “…this appeal is sustained in the amount of $609,621 with interest pursuant to 41 U.S.C. § 611 running from the putative receipt date of 21 September 2007.”  The Board’s direction contradicted an agreement struck between SRI and the government while the decision was pending.  That agreement called for the following –

The parties agree that the overhead rates established by this Agreement include disputed costs.  In order to expedite the settlement of these rates and factors, these costs have been provisionally allowed.  If ASBCA concurs with the Contracting Officer’s Final Decision (COFD) finding the costs unallowable, the Contractor agrees to make separate payment to the Government of the amount of G&A expenses overpaid by the Government, plus interest, under the contracts subject to this Agreement by reason of the cited noncompliance.  If the contractor prevails in the aforementioned ASBCA case, it is agreed that no adjustments to the rates established by the Final Overhead Agreement for SRI International’s FY 2005 shall be made.

The government’s concern was that the Board’s direction “could be interpreted as awarding SRI ‘a lump sum payment … with interest …’ as opposed to allowing SRI to ‘recover the LOC costs as part of the final overhead rate settlement process …’.”  According to the Board, the government contended that, “the exact amount SRI will recover under all the affected contracts may not necessarily be $609,621” and, as a result, SRI might “recover more money than it is entitled to recover under the affected contracts.”

For its part, SRI told the Board that it agreed that it was not entitled to a lump-sum payment with respect to the previously disallowed LOC fees.  However, SRI contended that it was entitled to a lump-sum payment for interest as computed by the Contract Disputes Act.

The Board explained that—

To be clear, what our decision holds is that the LOC costs SRI incurred in FYs 05 and 06 are allowable indirect costs, and SRI is therefore entitled to include the LOC costs in its indirect G&A cost pool for those years.  This, however, is not the end of the process.  As envisioned in the Allowable Cost and Payment clause and FAR 42.705-1, the allowable LOC costs for FYs 05 and 06 still have to be allocated to the affected contracts and be scrutinized against the terms of those contracts before the actual amount of allowable LOC costs under each affected contract may be determined.  Thus, the final indirect cost rate establishment process must run its course.

The Board quoted its decision in ATK Launch Systems and the Court of Federal Claims’ 2007 decision in ATK Thiokol v. US, stating—

The consequence of an award of monetary damages in this case is only that the award will be included in the G&A pool applicable to the affected contracts. … To the extent that the court’s award implicates cost ceilings, incentive provisions or other clauses of particular contracts, the DACO, not the court, will make any necessary interim adjustments. … Ultimately, a final indirect cost rate and the final amount due under each contract will be established by the DACO, reconciling any payments that have been paid out on an interim basis, including any damages awarded by the court.

The Board rejected the government’s argument that CDA interest cannot be awarded in this case because “until such time as SRI submits its completion vouchers for FY 2005 and FY 2006, the Government’s contractual obligation to make final payments for the allowable indirect costs does not arise.”  Instead, the Board decided that “the amount found due is the total amount of LOC costs … and paid pursuant to FAR 52.216-7(h) as a consequence of our decision.”  Moreover, “the CDA interest on the FYs 05 and 06 LOC costs due SRI will be computed from [the date SRI filed its CDA claim] and run until paid under each affected contract….”

The Board’s ruling makes good legal sense.  It is also ridiculous.

Under the Board’s logic, SRI is entitled to interest on its CDA claim, but that interest needs to be computed as follows:

  1. Determine how much LOC costs for FYs 2005 and 2006 were allocated to individual contracts.

  2. Determine which contracts can recover those costs.  For example, firm fixed-price contracts do not permit recovery of any increased contractor costs.

  3. For contracts that do permit cost recovery, determine how much can be recovered, contract by contract.  For example, if recovery of the additional costs puts the price above the amount of funding available, then the contractor cannot recover.

  4. For contracts that permit recovery, prepare and submit final vouchers.

  5. Determine the date on which the government pays the final vouchers.

  6. CDA interest is the amount determined to be recoverable in Step 3, applied to the period between the date the claim was submitted and the date the final voucher was paid.

The Board’s decision is impractical and, hopefully, the parties will figure out a way around it.

First of all, the very definition of G&A assumes that there is no individual beneficial or causal relationship between an element of the G&A expense pool and an individual final cost objective (contract).  See FAR 31.201-4(c).  It is literally impossible, from a government contract cost accounting viewpoint, to determine how much of the LOC costs (as individual cost items) would be allocated to any particular contract.  If such a relationship could be determined, then the LOC costs should not have been included in SRI’s G&A expense pool.

Second, to have to calculate interest due on a contract-by-contract basis is infeasible and borders on the absurd.  SRI will have to wait until its FY 2006 indirect costs are audited and negotiated. As we all know, that could take years.  Then it will have to submit final completion invoices and determine when the government pays those vouchers.  Then it will have to submit another request for payment (to the DOD Judgment Fund, we assume) and wait for that payment to be made.

Such an approach, we believe, eviscerates the intent of the Contract Disputes Act.  Instead of acknowledging the time value of funds lost through an erroneous Contracting Officer’s Final Decision, the methodology outlined above might actually end up costing SRI more to implement than it obtains in CDA interest payments.

It seems to us that a much more workable solution would have been to allow SRI to include the LOC costs in its G&A expense pool but have the government issue a lump-sum payment for CDA interest, based on the ratio of cost input in the cost-reimbursement (and perhaps T&M) contract types to the total G&A allocation base, times an agreed-upon duration.  Have the government cut SRI a single check for interest only, and let that be the end of it.

The ASBCA did a good job with respect to the determination of cost allowability.  But it did a poor job with respect to understanding how government contract administration works.  This decision, if followed literally, will result in a burdensome and expensive solution to what was an easily negotiated solution.

As we said in the beginning, “bad cases make bad law”.  And bad rulings make hard compliance.

 

GAO Says DCMA Has Been Mismanaged, Is Overly Reliant on DCAA

E-mail Print PDF

Changed_PrioritiesWe have called them the “DOD Oversight Wars” and there have been episodic outbreaks of bureaucratic and political attacks for almost four years.  GAO attacks DCAA; DCAA attacks DCMA; the DOD IG attacks both DCAA and DCMA; etc.  You get the picture.  Add-in the proxy attack dog, The Commission on Wartime Contracting, and various House and Senate hearings—with associated politician-generated soundbites, of course—and an observer might easily get the idea that the Federal government was distracted by defense-related internecine warfare.  The DOD Oversight Wars are not only a symptom of the petty squabbling and lack of policy leadership to be found within today’s defense acquisition and oversight satrapies, they are also a primary driver of increased contractor overhead costs and program execution inefficiencies.

And so here we are again, with another kneecapper fired by GAO at the Department of Defense’s acquisition management team within the Defense Contract Management Agency (DCMA).  We’re talking about the November 4, 2011 report (GAO-12-83), in which the Government Accountability Office told Congress, “A shift to a substantially decentralized, customer-oriented approach in the mid-2000s, intended to mitigate the impact of this workforce imbalance, resulted in unintended consequences such as inefficiencies in how work was done at the CMOs [Contract Management Offices].”  Which is kind of a nice way of saying that DCMA was mismanaged, isn’t it?

And remember—the mid-2000s were a time when this nation was boots-on-the-ground in Afghanistan and Iraq, as well as pursuing vigorously what was called at the time the “global war on terror”.  In other words, when the warfighters (and, indeed, the nation) needed effective and efficient management of the defense industrial base, DCMA was busy managing itself into the “unintended consequences” of “inefficiencies in how work was done”.  Why nobody was fired or perhaps prosecuted for sabotage in the time of war, remains a mystery.

If you think we are overreacting just a tad, check out this definition of “sabotage”—

Sabotage is a deliberate action aimed at weakening another entity through subversion, obstruction, disruption, or destruction. In a workplace setting, sabotage is the conscious withdrawal of efficiency generally directed at causing some change in workplace conditions.

(Emphasis added.)

Anyway, the GAO report, entitled, “DEFENSE CONTRACT MANAGEMENT AGENCY: Amid Ongoing Efforts to Rebuild Capacity, Several Factors Present Challenges in Meeting Its Missions,” engaged in less hyperbole, but was just about as damning in its criticism of DCMA management.  GAO reported that DCMA staffing declined during the 2000s, from a high of nearly 20,000 (1993) to a low of 9.300 (2008).  You read that correctly.  For the first seven years of the global war on terror, DCMA continued to shed staff, even while its contract administration duties and unliquidated obligations under management continued to increase.

While the agency has focused on adding staff since 2008, GAO also reported that 52 percent of the DCMA workforce is currently eligible for either full or early retirement.  That’s called the “human capital crisis” and the DOD has been warned about the phenomenon for more than a decade. Not that they ever did anything to mitigate the easily foreseeable problem, mind you ….

In addition, DCMA has mismanaged away “key skill sets,” according to GAO.  The report says—

In addition to its precipitous drop in workforce numbers, DCMA had experienced an atrophying of some key skill sets. At the CMO level, one way DCMA is looking to build expertise of its new employees is by changing the workforce structure. Specifically, CMO staff are organized in one of three functional areas: contracting, engineering, or quality assurance. Previously, CMOs were organized in multifunctional teams, with employees from different disciplines (e.g., an ACO, a quality assurance representative, an engineer, etc.) on one team and responsible for overseeing a certain number of contracts.

The GAO report identified specific examples of how DCMA mismanagement had led to a degradation in functional efficiency.  For example—

… by the late 1990s DCMA was routinely combining the duties of its contract cost/price analyst positions with the duties of its contracting specialists; and at that time, the agency had lost the majority of its contract cost/price analysts. Loss of this skill set, according to DCMA, meant that many of its pricing-related contract administration responsibilities, such as negotiating forward pricing rate agreements and establishing final indirect cost rates and billing rates, were no longer performed to the same level of discipline and consistency as in prior years. As a result, DCMA reported that DOD’s acquisitions were subjected to unacceptable levels of cost risks. In one recent example, a DCMA official told us about a case where an ACO, lacking support from contract cost/price analysts had, for simplicity, incorrectly blended a contractor’s overhead rates rather than deriving separate rates for different areas (e.g., general and administrative, and manufacturing).

(Emphasis added.)

Well, while DCMA points to the loss of its contract cost/price analysis skill set as one of the causes of “unacceptable levels of cost risks,” the rest of the defense industrial base points to it as one of the causes of contract management ineptitude.  What we’re saying is that you can look at this from (at least) two points of view.  One point of view says DCMA mismanagement created a lack of necessary skill sets (including knowledge and experience) which led to “cost risks” in the pricing of DOD contracts.  The other point of view says DCMA mismanagement created a lack of necessary skill sets that made effective management and administration of those contracts nearly impossible.  While GAO worried about the pre-award negotiation and pricing, we’re worried about the post-award contract execution phase of things.

And, you know, while one can wail and moan about how contracts were priced in an inconsistent manner that lacked discipline, the sad truth of the matter is that it’s the post-award stuff that leads to ridiculous levels of cost growth and quality escapes that keep the warfighters from getting what they need, when they need it, at a reasonable price.  Which is supposed to be DMCA’s raison d'être—or so we’re told from its website.

The GAO informed readers that, realizing its management approach of the 2000s was sub-optimal, DCMA was in the process of reorganizing in a more centralized approach.  As we quoted in the beginning of this article, GAO reported that DCMA’s “customer-oriented, decentralized approach” led to “unintended consequences”—such as stovepiped silos and “confusion” amongst the CMO workforce.  GAO reported—

... DCMA rescinded its compliance and procedures manual for the agency’s required contract management functions—known as the ‘DCMA One Book.’ … The intent of the change was to allow more flexibility for the CMOs to modify existing processes and explore new ones to better support their own customers’ expected outcomes and objectives. However, officials from some CMOs we visited said the loss of the ‘DCMA One Book’ resulted in loss of consistent agency guidance and procedures, with one official characterizing this situation as a ‘free for all.’

Ironically, this focus on providing CMOs the flexibility to meet their customers’ needs as well as the absence of specific guidance and procedures resulted, according to DCMA officials, in a level of confusion among their program office customers. … Relatedly, the decentralized nature of DCMA guidance led each product division to develop and execute its own policies and provided CMOs the leeway to develop additional policies and procedures to respond to their own customers’ needs. This led to inconsistent oversight and surveillance activities among CMOs. Another unintended consequence was inefficiencies in how CMOs operated. For example, CMOs in close proximity but under different product divisions sometimes did not share resources or expertise and thus did not leverage their workforces to help meet workload surge requirements.

In addition—and as promised by this article’s title—GAO reported that DCMA has become too reliant on use of DCAA audits.  In particular, GAO noted that DCAA’s lack of timely audits of contractor business systems had a significant impact on the ability of DCMA Administrative Contracting Officers (ACOs) to assess contractor risk.  GAO reported—

A key external risk to DCMA’s ability to effectively carry out its responsibility to determine the adequacy of defense contractor business systems comes from delays in obtaining audits from DCAA. We also found that DCMA contracting officers maintained their determination of many contractor business systems as adequate despite the fact that the systems had not been audited by DCAA in a number of years—in many cases well beyond the time frames outlined in DCAA guidance. Another potential risk for DCMA is a recent DOD policy change that increased the dollar threshold at which DCAA will conduct certain audits; as a result, DCMA’s own pricing workload will increase. In addition … the agency faces a potential increased workload in oversight and surveillance of key suppliers as defense subcontracting grows. …

We examined the status of [ ] three business systems for the 17 defense contractors responsible for programs included in this review. ... We found a substantial number of systems that had not been audited within the DCAA time frames; 12 of the contractors had at least one system without a current and timely audit. For example, as of May 31, 2011, 10 contractors had not had an overall accounting system audit within the last 4 years, and 9 had not had an estimating system audit within the last 3 years. In one case, a contractor which has increased its government business more than sevenfold since 2000 has not had an overall accounting system audit since 1998, despite the ACO requesting that DCAA perform such an audit. Further, one estimating system audit and two MMAS audits have never been conducted because, according to DCAA and DCMA officials, DCAA has not had the resources available to perform them. …

That’s not all.  GAO reported the same thing we’ve been noting for several years:  DCMA contracting officers are not pleased with DCAA’s level of performance.  GAO reported—

Some ACOs expressed concern that they did not have more up-to-date information with which to determine the status of the business systems… Many expressed frustration at the lack of timely DCAA audit support and identified it as a significant impediment to their ability to assess the status of contractor business systems, particularly accounting and estimating systems. Further, most noted that their DCAA counterparts were unable to provide clear and firm time frames for when the next audits would take place. In some cases, ACOs reported that expected audits planned by DCAA for a given fiscal year were not completed, so were moved back to the next year or canceled. When business systems are not audited in a timely manner, the government is at increased risk of paying for unallowable and unreasonable costs, as a contractor’s cost structure or accounting procedures may change over time.

Some may remember our comments to the DAR Council on the proposed rules regarding contractor business systems.  We opined that DCAA lacked the resources to fulfill its end of the bargain.  We are pleased, in a bitter-sweet way, that GAO agreed with us.  GAO reported—

However, because we found consistent delays in the audit time frames for the business systems that require support from DCAA, higher-level attention is needed to mitigate the risk to the government of outdated business system audits. DCAA, because of workforce challenges of its own, is not at present able to fulfill its business system audit responsibilities and is not likely to be in a position to do so in the near term given its other priorities. Thus, the department needs to consider alternative methods to accomplish these critical audits in a timelier manner.

(Emphasis added.)

To sum this up, GAO has reported, for all who have eyes to read it, that DCMA has been mismanaged for the past decade, that the mismanagement has put the agency in an untenable position, and that DCMA’s position is further undercut by reliance on a contract audit agency (DCAA) that is not able to fulfill its regulatory oversight function.

Other than that, we’re sure things are fine at the Department of Defense.

 

Proposed Rule on Proposal Adequacy

E-mail Print PDF

You have to give us some credit on this one.  Sure, our lead time was measured in hours and not days or weeks, but at least we were in front of the curve .  Our readers did get some measure of “heads-up”.  And it would have been more, too, but the SoCal windstorm took out the power at our webmaster’s lair, and so publication was delayed for a couple of days until the electricity was restored.  But we were on this like a drug-sniffing K-9 canine prowling an opium den.

(The foregoing is a long-winded and clearly defensive introduction to the very recently published proposed DFARS rule on proposal adequacy, found right here.)

As we mentioned in our previous article (link found in the long-winded and clearly defensive introductory paragraph, above), we start off with the proposition that this rule is unnecessary, overly bureaucratic, and possibly un-American.  DCAA already has such a checklist and has been using it to avoid auditing contractor proposals for some time.  Moreover (and as we noted in our previous article), though the DCAA proposal adequacy checklist expressly applies only to contractor proposals for which certified cost or pricing data are being submitted, DCAA has told its auditors that the checklist is may be good “guidance” to help an auditor “reach an opinion on the adequacy of the [contractor’s] proposal.”  And so we’ve seen proposal after proposal rejected for audit as being inadequate, even though TINA, the requirements of FAR Table 15-2, and the proposal adequacy checklist itself are clearly and expressly Not Applicable.

But try as we might, we can’t get away from the fact that it is the Contracting Officer’s responsibility to determine whether the contractor’s proposal is adequate to negotiate a fair and reasonable price—before requesting the “field pricing assistance” of DCAA auditors.  (See FAR 15.404-2.)  So while DCAA may need a checklist to determine whether a proposal is adequate for audit, we have to reluctantly agree that it may be reasonable for DOD to issue to its Contracting Officers a checklist to assist them in determining whether a proposal is adequate for negotiation.

(You’d think that any warranted CO would be able to make that determination on his or her own, and that any CO who couldn’t make the right call in that particular area might be relatively unfit to have received the warrant in the first place, but perhaps we digress.)

So let’s now turn to the substance of the proposed DFARS rule and see if it is focused on assisting Contracting Officers in determining whether a contractor proposal is adequate for negotiating a fair and reasonable price.

The substance of the proposed rule is to create a solicitation clause (252.215-70XX) that imposes a “proposal adequacy checklist” for contractors to submit, along with their proposals, when solicitations “require the submission of certified cost or pricing data, if the contracting officer chooses to use the provision.”  We note that the proposed DFARS language states, “When the solicitation requires the submission of certified cost and pricing data, the contracting officer should include 252.215–70XX, Proposal Adequacy Checklist, in the solicitation.”  So inclusion of the provision clearly is not mandatory; nonetheless, you should expect to see it frequently, since Contracting Officers who opt not to include it may have to justify their decision.

Though the Regulatory Flexibility Act analysis that accompanies the proposed rule states that only 905 contract actions per year will qualify for the new proposal adequacy checklist, we are more than a little skeptical of that number.  If the entire defense industrial base were only submitting 905 TINA-compliant proposals each year, then DCAA could kick back and read the newspaper.  Instead, DCAA reports that it is so bogged-down in auditing “forward priced proposals” that it needs to limit its audits only to those that exceed certain dollar thresholds.  In fact, in its most recent Semi-Annual report to Congress, the DOD Inspector General reported that DCAA had issued 1,143 audit reports on contractor forward pricing proposals.  (See Appendix D.)  And that was over a 6-month period (not a full year), and after the dollar thresholds noted above had already been implemented!  So while not all of those proposals would be subject to TINA, we believe the majority of them would be.  So quite clearly, we think that the proposed proposal adequacy will be applied to far more than the 905 instances DOD has stated would be the case.

The proposal adequacy checklist itself is not very novel.  It you look at the DCAA’s proposal adequacy checklist you’ll find the source of the majority of the 47 proposed points of proposal adequacy.  Other items include stuff pulled from FAR 2.101 (e.g., definition of commercial item) or from other FAR Parts.  It’s quite a bit redundant with the requirements of FAR Table 15-2 in that (by our count) 30 of the 47 points of adequacy simply reiterate requirements from that Table.  It would be much simpler, and provide Contracting Officers with exactly the same information, if those 30 points were collapsed into one single point that said, “Contractor certifies that it complies with all applicable requirements of FAR Table 15-2.”

Contractors subject to TINA, and wishing to successfully negotiate a contract award with DOD, should already be prepared to comply with the requirements of FAR Table 15-2.  We don’t see this proposed checklist as adding very much (if any) value to such contractors.  So why does DOD think it’s even necessary?

Well, according to the comments accompanying the proposed rule—

This rule will implement one of DoD’s Better Buying Power initiatives. The objective of the rule is to ensure that offerors submit thorough, accurate, and complete proposals. By completing the checklist, offerors will be able to self validate the adequacy of their proposals.

So there you are.  DOD is implementing this proposed rule to help its contractors check, on their own, that their proposals are “adequate”.  We should all say “thanks” to the DAR Council and just go about our business.

Hold it! Not so fast.

We told you about DOD’s “better buying power” initiative in a series of blog posts, including (for example) this article.  As we told you, DOD has been pursuing two distinct lines of attack:  (1) the drive to reduce waste, bureaucracy, and inefficiency within the Pentagon (AKA the “efficiency” attack), and (2) the drive to reduce the costs of goods and services by focusing on reducing contract prices (AKA the “affordability” attack).  We reviewed (once again), the September 2010 Memo and its 23 “principal actions”.  The funny thing was that we couldn’t find anything in that Memo about the adequacy of contractors’ proposals.  Sure, you could say this effort falls under the general rubric of “reduce non-productive processes and bureaucracy”—and maybe it does.  But we didn’t see anything under that heading that caused us to think this proposed rule was contemplated by the Better Buying Power initiative.

To the contrary—under the heading “reduce non-productive processes and bureaucracy” we found this objective:

Reduce non-value-added overhead imposed on industry. Industry has its own internal unproductive processes which add to project costs, but these are in some part a reflection of the requirements which the government imposes. A great number of the inputs I received from industry were directed at what was viewed as excessive overhead expenses based solely on non-value-added mandates and reporting requirements which may have been relevant at some point in time, but have little relevance in the world in which we now find ourselves. In order to identify and reduce these costly requirements, I am directing the Director of Industrial Policy, with support from DPAP, to more fully survey our industrial base to identify, prioritize, and recommend a path forward to unwind duplicative and overly rigorous requirements that add to costs, but do not add to quality of product or timeliness of delivery. As we remove these requirements, I will expect a decline in the overhead charged to the Department by our industrial base that reflects these reduced costs.

(Italics in original.)

So, rather than impose an additional solicitation provision and checklist on contractors, the Better Buying Power initiative actually directed the exact opposite take place.

Contractors already know—or should know—how to submit adequate proposals.  If they can’t submit adequate proposals, then they shouldn’t expect to win any work from DOD.  Instead of this ill-begotten piece of bureaucratic misadventure, what is needed is a checklist for DOD Contracting Officers to use in determining whether a proposal meets the Section L pricing instructions of the solicitation, whether it is adequate as submitted to commence negotiations leading to a fair and reasonable price, and/or whether field pricing assistance (including DCAA audit) is necessary.

Contractors don’t need this kind of assistance from the DAR Council.  Instead, DOD needs to be assisting its Contracting Officers in being more efficient.  That will be the theme of the comments that Apogee Consulting, Inc. intends to submit to the DAR Council.

What will you be saying?

 


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