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

The Incumbent Contractor

E-mail Print PDF

Debates swirl regarding whether the incumbent contractor is in the best position in a recompete situation. Certainly, the incumbent knows the current situation better than any other competitor, and it knows exactly what it will take to perform on the new contract. The incumbent has built relationships with the government program office, and with the Contracting Officer’s Representative (COR). The incumbent has recent experience and, if the CPARS are good, that experience is going to look good to evaluators. So, yes. The incumbent contractor has a lot of advantages—assuming it’s done a good job on the current contract.

On the other hand, the incumbent contractor is locked-in to what it knows to be true. It has a workforce and it is pretty much locked-in to paying the wages it currently pays, and offering the benefits it currently offers. Competing contractors have freedom to propose lower wages and to offer lower benefits (if they can convince source selection folks that doing so won’t pose too much risk). Competing contractors have freedom to offer innovative—perhaps lower-cost—solutions, and that often works to their advantage.

We saw this effect most clearly when Stewart & Stevenson (which was then a subsidiary of BAE Systems located in Sealy, Texas) lost the $3 billion recompete for the Army’s FMTV trucks to Oshkosh in 2009. The BAE Systems subsidiary had participated in the original designs, and had been making those trucks for nearly a decade when the recompete happened. The workforce was well-trained. The supply chain was mature. Presumably, they were the world’s experts in those trucks. Yet they lost and the plant was shuttered, resulting in hundreds (if not thousands) of lay-offs.

Of course, the selection of Oshkosh was protested. We reviewed the protest in this article. (Sorry for the format problems. It was early days.) Of note was the “unrealistic” Oshkosh pricing—at least in the words of BAE Systems officials at the time. In fact, they called it “unbelievable.” And perhaps it was; there is no prohibition on offering prices that create a loss (see FAR 3.501). One source asserted that Oshkosh’s pricing was 30% below BAE Systems’ pricing, and relied on “financial aid from state and local governments” in order to make a profit. In addition, while BAE Systems had the necessary tooling to build the trucks, that tooling was actually owned by the Army and could be provided to Oshkosh. Consequently, the tooling issue was not as much of an impediment as it might seem at first.

Oshkosh’s low-ball pricing overcame perceived risks and the protests were not sustained. In fact, Oshkosh is still making FMTV trucks nearly a decade later.

Thus, sometimes the incumbent is at a disadvantage. It knows too much. Innovative approaches are discarded in favor of “the way it’s always been done.” Supplier prices are firm; workforce costs are firm. None of which apply to the competing contractors, who have a blank slate to propose anything—and any pricing—that they think will be attractive to evaluators.

And sometimes DCAA knows too much about the incumbent contractor.

The Defense Threat Reduction Agency (DTRA) issued an RFP to award a cost-type contract for support to the agency’s “Balanced Survivability Assessment” (BSA) teams. The RFP told bidders the evaluators would conduct a “best-value tradeoff” to select the winning bidder. Six proposals were received and CENTRA Technology was declared to be the winner. ENSCO, Inc., the incumbent contractor, protested, claiming that the agency “conducted an unreasonable cost realism evaluation.”

The GAO opinion reported –

Cost was not to be rated or scored, but each offeror’s cost proposal was to be evaluated for realism, reasonableness, and completeness. Realism was to assess whether proposed cost elements are realistic for the work to be performed, reflect a clear understanding of the requirements; and are consistent with the unique methods of performance and materials described in the offeror’s technical approach. Reasonableness was to be evaluated using one or more of the cost/price analysis techniques defined in Federal Acquisition Regulation (FAR) section 15.404. According to the RFP, ‘[i]n evaluating reasonableness, the Government will determine if the Offeror’s proposed costs and fee, in nature and amount, do not exceed those which would be incurred by a prudent company in the conduct of competitive business.’ The solicitation notified offerors that the agency will determine the most probable cost (MPC) by adjusting the offeror’s proposed cost and fee, when appropriate, to reflect any additions or reductions in cost elements to realistic levels based on the results of the cost realism analysis. The MPC was to be used to determine best value to the government, and was to represent the agency’s ‘best estimate of the cost of any contract that is most likely to result from the Offeror’s proposal.’

(Internal footnotes omitted.)

Readers will note that, when a cost-type contract is to be awarded, the proposed costs are not dispositive because actual allowable costs will be incurred and invoiced. Thus, the FAR requires a cost realism analysis and, if necessary, adjustment of proposed costs to reflect expected costs.

CENTRA’s adjusted costs were found to be $61.85 million, less than $100,000 higher than its proposed costs. ENSCO’s adjusted costs were found to $79.9 million, about $850,000 higher than its proposed costs. ENSO argued that the cost realism analysis was flawed. You’d think that any flaws wouldn’t add up to $18 million, but the GAO didn’t see it that way. The protest was sustained because the agency evaluators only adjusted costs (specifically labor costs) for which the DCAA provided audit findings. If DCAA didn’t provide any findings with respect to labor (or other costs), then they were not adjusted. In GAO’s view, that was not much of a cost realism analysis.

Further, which contractor do you think DCAA had the most information on? On which contractor’s audit report did DCAA have the most findings? If you said “the incumbent contractor” then you should step up and accept your prize.

The GAO decision stated—

The error, in our view, is the agency’s exclusive use of DCAA-verified rates, without any meaningful analysis of the direct labor rates that were not verified by DCAA. Since ENSCO was the incumbent contractor, many of its rates were adjusted to conform to the rates paid under its incumbent contract, which negated the firm’s proposed cost reduction. In contrast, only two of CENTRA’s proposed rates were adjusted, while the remainder of the firm’s proposed direct labor rates were apparently not scrutinized. The record does not reflect any analysis of non-DCAA verified rates, even though the agency had available to it rates proposed by other offerors, including the incumbent, for comparison. The agency also had available an IGCE, which provided the government’s own estimates of the cost for each position required under the solicitation. In this regard, a review of the IGCE shows that the government’s own estimates of direct labor costs were generally much higher than those proposed by CENTRA, yet the agency conducted no comparison, and made no MPC adjustments, even though the agency will bear the cost of these employees during performance of this cost reimbursement contract. Consequently, we cannot conclude that the agency’s exclusive use of DCAA-verified rates, without further explanation--and generally only for ENSCO--was reasonable. We also agree with ENSCO that the impact of the agency’s evaluation methodology resulted in disparate treatment of these offerors. Therefore, we sustain the protest on this basis.

(Internal footnotes omitted.)

In addition, GAO took issue with the evaluation of CENTRA’s labor rates. Apparently, CENTRA had bid labor rates 30 percent below ENSCO’s incumbent workforce rates—even though CENTRA’s proposal assumed that several of its key personnel would be recruited from ENSCO. “… the record shows that in evaluating CENTRA’s proposal, the agency attributed greater confidence to CENTRA’s proposal for its approach to attempt to recruit additional incumbent employees [DELETED] without analyzing the impact of CENTRA’s significantly lower direct rates on its ability to recruit incumbent personnel. … Without such an analysis, we cannot conclude that the agency’s finding was reasonable.”

In summary, the agency evaluators relied on DCAA audit findings rather than making a thorough cost realism analysis, as the RFP had promised. Because DCAA was more familiar with ENSCO, the incumbent contractor, it received more audit findings than did CENTRA. Those audit findings resulted in more adjustments to its proposed labor rates. Further, because the evaluators relied on DCAA audit findings, they missed a significant risk in CENTRA’s proposal. It’s proposal relied on recruiting incumbent personnel at rates significantly lower than they were currently being paid.

Thus our conclusion: sometimes the incumbent is in the best position; other times not so much.

 

Time

E-mail Print PDF

Readers: It’s not that we have nothing to say; it’s that we have no time for saying it.

Very busy time of year. Much travel.

Would love to chat but gotta go.

Talk to you later.

 

Capitalization and Expensing Part 3

E-mail Print PDF

In the two previous articles we discussed basic GAAP requirements and some of the fundamental FAR and CAS requirements that may supersede GAAP requirements, especially for government contractors that are subject to Full CAS coverage.

Link to Part 1

Link to Part 2

This article will explore some of the compliance challenges in a government contracting environment. As we hope to demonstrate, sometimes you have to throw out everything you thought you knew in order to comply with the requirements. It can be tough to try to explain what’s going on to people who thought they had it all down.

Expensing and Capitalization Revisited

In Parts 1 and 2, we explained that the 205-11 cost principle required contractors subject to Full CAS coverage to comply with the requirements of CAS 404 (to determine the value of the capital asset) and CAS 409 (to determine the estimated service life and the amount of annual depreciation associated with the capital asset). We told you that assets valued at $5,000 or more, which had an estimated service life of two years or more, were required to be capitalized. If the asset was valued at less than $5,000 or had a service life of less than two years, the contractor had some discretion in the expensing/capitalization decision (so long as it consistently followed its written practices). Seems pretty straightforward.

But hold on there.

What about direct contract costs?

Suppose you have a contract that requires a test station to be constructed. The value of the test station is $100,000. It is expected to have a useful life of 5 years. According to what we thought we knew, we are required to capitalize that test station.

But not always. If the test station is a contract requirement, the contractor can charge the entire $100,000 to the contract. The $100,000 will be expensed as costs are incurred.

The same is true for direct material costs. A part that costs $50,000 might well be directly charged to the requiring contract as an expense.

Really.

Don’t believe us? Check out CAS 411, which states “The cost of units of a category of material may be allocated directly to a cost objective provided the cost objective was specifically identified at the time of purchase or production of the units.”

Check out the cost principle at 31.205-40 (Special Tooling and Special Test Equipment Costs), which states “The cost of special tooling and special test equipment used in performing one or more Government contracts is allowable and shall be allocated to the specific Government contract or contracts for which acquired …”

Thus, it seems apparent that certain transactions are exempted from the standard capitalization criteria. The primary distinguishing characteristic of such transactions is that they are direct contract costs. A contractor may choose to treat those direct contract costs as current period expenses, even if they would otherwise be required to be capitalized.

This is not as much of a free pass as one might think. There are rules regarding when a transaction may be treated as a direct contract cost. For example, see 31.201-4(a) and the definition of “direct cost” at FAR 2.101. In addition, we devoted an article to the notion of “authority to acquire,” which we broadly defined as “the terms of the prime contract (or higher tier subcontract) gives the entity performing the contract the authority to procure the stuff necessary to execute the contract’s (or subcontract’s) Statement of Work (SOW).” We noted in that article that contractors who charge goods and services directly to their government contracts without that authority run some risks. We summarized the situation thusly: “… goods and services obtained and direct-charged without the requisite authority to acquire can impact every one of the six DFARS business systems. They can impact financial results. They can impact tax reporting. They can, in extreme cases, lead to disputes and litigation.”

So yeah, not really a free pass. But still, valid direct charges will supersede the GAAP and FAR and CAS requirements that we thought we knew.

Direct vs. Indirect Revisited

One of the more interesting questions we encounter, from time to time, is whether a contract requirement must be directly charged to the requiring contract. Can you sometimes take a contract requirement and, instead of treating it as a direct contract cost, treat it instead as a capital asset on your balance and recognize the cost ratably over time through depreciation?

Sure you can.

We mean, not always. If you are building a contract deliverable then we’re fairly sure that the costs of that deliverable must be charged to the contract, regardless of contract type. But take the example from a couple of paragraphs above, where you have a $50,000 test station you need to build. Assume it’s not a deliverable, you simply need it to test widgets and you expect it to last for five years. You are going to test widgets and you may have multiple contracts during that five-year period. As we know, the cost principle at 31.205-40 permits you to direct charge that piece of special test equipment directly to the contract. You can do that. But must you do that? The answer—perhaps surprisingly—is no. You can, but you don’t have to.

First, you and your customer can agree to exclude certain items from contract costs. Looking again at 31.205-40, there’s a limitation that states, “Items which the contract schedule specifically excludes, shall be allowable only as depreciation or amortization.” Thus, it seems quite clear that the FAR contemplates a contractual agreement that certain items—special test equipment for example—may be excluded from a contract even if otherwise required by that contract; and if that’s the case, then the contractor must capitalize and depreciate those items over time, in accordance with its accounting policies and procedures.

And as we noted in the previous article, while depreciation is normally an indirect expense, it does not have to be. CAS 409 expressly permits treatment of depreciation as a direct contract cost, if done consistently and on the basis of usage.

Therefore, it is certainly possible to reduce your estimated (and actual) contract costs on a CLIN or annual basis by proposing to your customer to remove certain items from the contract schedule, such that you will capitalize the costs of those items and amortize the cost over a period of time. You can, if you want, charge the depreciation/amortization as a direct contract expense.

It can be done. Larger contractors do this all the time. (Well, maybe not the direct charge part, but certainly the exclusion part.)

It’s not a particularly great financial strategy. If you treat the cost of the item(s) as direct costs of the contract, then you are recovering your costs within a month (assuming a cost-type contract). Even in a fixed-price contract scenario, if you have contract financing payments you are still recovering the vast majority of your costs within a month or two. In contrast, if you capitalize the item(s) and recover them through depreciation/amortization, then your cash flow will be negatively impacted. The costs you would have recovered in roughly 30 days will now be recovered over a period of years. Still, if that’s the win strategy then oftentimes a contractor will trade cash flow for the revenue.

A government contractor has some flexibility in its direct versus indirect decision-making, just as it has with respect to its expensing versus capitalization decision-making. Some people (usually auditors) like to argue that if a cost can be identified with a final cost objective, then it must be allocated to that final cost objective as a direct cost. That is absolutely not the case. The definition of “direct cost” at FAR 2.101 has a subtle nuance that many people miss. Let’s quote it—

‘Direct cost’ means any cost that is identified specifically with a particular final cost objective. Direct costs are not limited to items that are incorporated in the end product as material or labor. Costs identified specifically with a contract are direct costs of that contract.

See that? A direct cost is one that is identified specifically with a particular final cost objective—not one that can be so identified. If the contractor records a cost as a direct contract cost, then it is one; but if the contractor records the cost as an indirect cost—or as a capital asset—then that cost is not a direct contract cost. Again, consistency is important here, as is transparency and reaching an agreement with a customer regarding contract cost exclusions. We don’t at all mean to say the discretion afforded a contractor with respect to its accounting treatment is a free pass to bid costs one way and account for them in another way.

However, we are confident that the discretion discussed in this article exists, and that it may be used when it makes good business sense to do so.

Expensing versus capitalization. Seems fairly straightforward on first glance. Many contractors can simply follow GAAP and IRS rules, and they’ll be fine. But other contractors have to content with rather complex and nuanced FAR and CAS requirements. Savvy contractors can use those nuances to their competitive advantage.

We trust that you’ve enjoyed the deep dive into the business challenges presented by what seems at first to be a relatively trivial issue.

 

Tell Us About It

E-mail Print PDF

This is the worst RFP I’ve ever seen in my career!

This contracting officer doesn’t know what they’re doing!

Doesn’t anybody care that we are spending $100 to deal with $5 in costs?

We’ve all heard such comments. Businesses don’t like doing business with the government, primarily because the government doesn’t do business very well. It does government, not business. (H/T Brent C.)

RFPs are poorly drafted—ambiguous at best, literally insane at worst. CO’s won’t listen; or if they do listen, they listen to DCAA and not the contractor. DCAA auditors don’t even understand their own audit programs. We could go on, listing complaints so common that we don't pay attention to them anymore.

We get it. According to many, the government workforce is poorly prepared, poorly trained and, as a result, poorly executes. And then the finger gets pointed at the poor contractors, who were trying to do their best and were only following direction.

We’ve all heard it. We have all heard the foregoing complaints, and many others as well. More than likely we’ve all heard those complaints many many times.

Complaining. Grousing. Kvetching. Bitching.

Whatever you want to call it.

But it’s almost never said directly to the people who most need to hear it. You complain about the situation around the watercooler with your colleagues, or you complain late at night when you are trying to complete that stupid schedule. You complain to us via email.

But you don’t actually complain to the contracting officers, or to the ACOs, or to the audit supervisors. You don't complain to the people you think are responsible for the problems, and thus nobody is ever held accountable. You don't officially complain, do you?

Now’s your chance.

On July 23, 2018, the FAR Councils published a proposed rule to allow contractors to offer “feedback … on Government contracts and solicitations.”

Remember, this is a proposed rule. The Councils are looking for feedback as to whether or not contractors would actually provide the feedback, if there were a mechanism in place to receive and disseminate it.

An example of the kind of feedback they would be looking for can be found here.

The proposed rule discussed ten things for which the FAR Councils are seeking industry comment. Why don’t you follow the link above, and see whether or not you might have some responses you’d like to submit for consideration?

Remember, if you don’t provide your feedback to the proposed rule, you may not like the final rule and the final survey questions. And if you don’t use the future state feedback portal because you don’t like the survey questions or you don’t like the portal—or you think you will be the object of retaliation if you really tell the truth—then you will have nothing.

You will be right back where you are now, grousing about the situation with no means of communicating what’s wrong, let alone changing it.

So tell them about it now, so that you can tell them about it later.

 

CAS Board Makes More Changes to Rules

E-mail Print PDF

Roughly four months ago, we noted that the CAS Board had jumped back into action by adding a single word (“certified”) to the 48 CFR 9903-201-1(b)(15) list of CAS exemptions. It took the CAS Board a full seven years to make that one-word change.

Seven years.

Still, we were happy to see evidence—any evidence—that the CAS Board was moving forward. Even if the speed at which the Board was moving resembled molasses flowing over ice at the North Pole.

Now comes additional evidence that the CAS Board is continuing to move forward. Forgive us if you’ve already seen this, but we don’t think many people have.

On July 17, 2018, the CAS Board published a Federal Register notice announcing a final rule that revised the CAS exemption for contracts and subcontracts for the acquisition of commercial items. Previously, the exemption at 48 CFR 9903-201(b)(6) exempted “firm fixed-price contracts and subcontractors for the acquisition of commercial items.” The problem with that language was that government acquisition folks were awarding commercial item contracts that were other than firm fixed-price. Read literally, it was only a subset of commercial item contracts (and subcontracts) that were exempt from CAS; however, as the Board explained, that was never the intent. The Board stated—

An inconsistency has developed between the list of contract types recognized for use in acquiring commercial items set forth in paragraph (b)(6) and that commercial item exemption and contract types reflected in FAR 12.207. For example, FAR 12.207 allows the use of firmed fixed price contracts in conjunction with award fee incentives or performance or delivery incentives, known as fixed-price incentive (FPI) contracts, when the award fee or incentive is based solely on factors other than cost. However, the (b)(6) exemption does not expressly recognize FPI contracts on the enumerated list of exempt contracts. Because of this discrepancy, some commenters on a prior CAS Board rulemaking expressed concern that these types of FPI contracts might be excluded under a literal reading of the (b)(6) exemption. See 72 FR 36367.

The Board went on to state that, when read in proper context—i.e., by reading the CAS Board’s “authorizing statute at 41 U.S.C. 1502(b)(1)(C)(i) as well as the language in section 4205 of the Clinger-Cohen Act”—a reasonable person wouldn’t reach the conclusion that only a subset of commercial item awards were exempt from CAS. But some people might not be reasonable, and therefore the Board acted to clarify the (b)(6) CAS exemption.

To keep things simple, the Board decided to stop listing contract types and just refer to FAR Part 12 (Acquisition of Commercial Items). In the Board’s words: “… this final rule amends the language at 9903.201–1(b)(6) to exempt contracts and subcontracts authorized in 48 CFR 12.207 for the acquisition of commercial items.”

In other words, if the contract or subcontract is a commercial item contract as authorized by FAR 12.207, then it is exempt from CAS.

Period.

Seems pretty simple, right?

It took the CAS Board nearly six years to go from proposed rule to final rule.

Six years.

Still, it was faster than the prior regulatory action.

Perhaps that molasses is flowing a bit more quickly these days.

 


Page 45 of 278

Newsflash

Effective January 1, 2019, Nick Sanders has been named as Editor of two reference books published by LexisNexis. The first book is Matthew Bender’s Accounting for Government Contracts: The Federal Acquisition Regulation. The second book is Matthew Bender’s Accounting for Government Contracts: The Cost Accounting Standards. Nick replaces Darrell Oyer, who has edited those books for many years.