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

Application of Hazardous Duty and Danger Pay Uplifts

E-mail Print PDF

In the fall of 2009, DCAA Director April Stephenson told the Commission on Wartime Contracting that “Through FY 2009, DCAA has reported total exceptions of $16.3 billion consisting of recommended reductions in proposed and billed contract costs of $8.8 billion and $7.5 billion of estimated costs where the contractor has not provided sufficient rationale for the estimate.” In addition, she told the Commission that “DCAA has issued over 140 Forms 1 under the Logistics Civil Augmentation Program (LOGCAP) III program that suspended or disapproved over $655 million.” (Stephenson Testimony, 11/02/2009) Based on Ms. Stephenson’s testimony, the Commission officially reported that it estimated “waste and fraud together range from $31 billion to $60 billion,” which was footnoted as being an estimate that 10 to 20 percent of every dollar spent in Iraq and Afghanistan was wasted, and that 5 to 9 percent of every dollar spent was fraudulently billed by contractors. As the Commission reported, “The Commission’s estimate of a 5 percent to 9 percent fraud rate would indicate that between $10.3 billion and $18.5 billion of the $206 billion in funds spent for contingency contracts and grants has been lost to fraud.” (Transforming Wartime Contracting: Controlling Costs, Reducing Risks, 8/31/2011)

Of course we all know today that the majority of DCAA’s questioned and suspended costs was not sustained, and that millions of dollars of such cost that were sustained were subsequently overturned on appeal. We know now – seven years later – that Ms. Stephenson’s testimony was self-serving at best and misleading at worst. In 2009 we linked the claims in Ms. Stephenson’s testimony (particularly those related to allegedly inadequate contractor business systems) to then-contemporaneous GAO and DOD IG reports blasting the audit agency’s audit quality. We wrote: “so long as the spotlight is turned on the contractors, DCAA can hide in the darkness.” It is unfortunate that the country’s perception of contingency contractors has been tainted by that testimony, just as it is unfortunate that we now have an expensive, nearly unworkable, and essentially valueless “contractor business system” administration and oversight regime as a direct result of that testimony.

Even before 2009, DCAA had issued audit guidance (04-PPD-023) that addressed the pay differentials contractors provided to their employees for working in combat areas such as Iraq and Afghanistan. The audit guidance was based on questionable statistics (e.g., a survey of the practices 37 contractors) rather than on an actual policy position based on contract terms and conditions. Some (unknown) amount of the questioned and suspended costs that were reported to the Commission on Wartime Contracting came from application of that audit guidance to contingency contractors. Importantly, the audit guidance focused on the Department of State Standardized Regulations (DSSR) as establishing allowability criteria, regardless of what the contract might have actually said. The audit guidance stated:

Most contractors justified providing the deployed employees with hardship pay differential due to the known difficult living conditions they would be working under. … However, the statistics that follow demonstrate that contractors did not adopt the DSSR specific percentage allowance or the salary base to which the percentage allowance was applied. The DSSR hardship pay differential for Iraq is 25 percent of an employee’s base pay, calculated on a 40 hour work week. … Since the predominant industry practice for the deployed contractor employees working on non-USAID contracts is to cite the DSSR as the basis for the hardship pay differential, auditors should evaluate contractors offering a hardship pay differential in excess of the DSSR hardship pay differential of 25 percent of base pay, calculated on a 40 hour work week. Review the contractor’s hardship pay policy and practices, the basis to calculate hardship pay, the deployed employees’ compensation agreements, and consider factors determined to be relevant by the contracting officer. In cases where there is inadequate contractor support to justify hardship payments beyond the DSSR allowances, challenges to these costs should be made in accordance with FAR 31.205-6(b) because the costs exceed compensation practices of other firms in the same geographic area (i.e., Iraq). In accordance with FAR 31.201-3(a), the burden of proof is then upon the contractor to establish that such a cost is reasonable. … The DSSR danger pay allowance for Iraq is 25 percent of an employee’s base pay, calculated on a 40 hour work week. … For those non-USAID contracts, auditors should perform an evaluation of contractors offering their deployed employees a danger pay allowance in excess of the DSSR danger pay allowance of 25 percent of base pay, calculated on a 40 hour work week. Review the contractor’s danger pay policy and practices, the basis to calculate the danger pay, the deployed employees’ compensation agreements, and consider factors determined to be relevant by the contracting officer. In cases where there is inadequate contractor support to justify danger pay allowances beyond the DSSR allowances, challenges to these costs should be made in accordance with FAR 31.205-6(b) because the costs exceed compensation practices of other firms in the same geographic area (i.e., Iraq). In accordance with FAR 31.201-3(a), the burden of proof is then upon the contractor to establish that such a cost is reasonable.

And so the DCAA auditors followed that audit guidance and questioned contractor compensation costs because they did not strictly follow the DSSR guidance (as interpreted by Fort Belvoir) and the contractor could not provide sufficient justification to the auditor as to why its practices deviated from those directed by the DSSR. (Note that second criterion is an entirely subjective factor, one that many if not all contractors likely would be unable to meet.) We don’t know how many millions of dollars’ worth of hazardous duty post and danger pay uplifts were questioned, but we know it was a lot (because we have worked with some of those contractors). Some contractors accepted the audit findings, others negotiated a compromise, and still others fought them.

One contractor that fought the audit findings was CACI.

CACI won at the ASBCA, on a motion for summary judgment. The decision may be appealed, but we think Judge Prouty’s logic is sound. Writing for the Board, he summarized the issue at the heart of the dispute as follows—

This appeal comes down to the interpretation of a contract provision permitting [CACI] to be reimbursed by the government for hazardous duty pay made to its employees assigned to work overseas …. . The pay at issue was 35% of the ‘basic compensation’ made by CACI to its employees. In its pending motion for summary judgment, the government contends that this ‘basic compensation’ is what the CACI employees are paid for non-overtime hours. After the employees were paid for the first 40 hours that they worked per week, the government argues, any additional hours that they worked should be considered to be overtime and not subject to the 35% pay supplement.

CACI urges the Board to recognize that the ‘normal hours’ that its employees were expected to work by the government (depending on the government task order at issue), were either 84 or 72 hours per week, without such hours being considered overtime. Thus, as CACI would have it, since 84 or 72 hours per week were the employees' expected hours, pay for the entirety of those hours was the employees' basic compensation to which the 35% pay supplement should apply.

As Judge Prouty wrote in his decision: “CACI prevails.”

This is an important decision, because it overturns 12 years of DCAA audit guidance, audit guidance based on a flawed interpretation of the DSSR. The contracting parties had incorporated the DSSR rules into the contract, but the flawed interpretation by DCAA, the Special Inspector General for Iraqi Reconstruction (SIGIR), and the Contracting Officer required CACI to litigate in order to prevail. Judge Prouty quoted the DSSR at length and compared the requirements therein to requirements found elsewhere in the contract. We urge readers with similar audit findings to read his decision in detail. But for this blog article, we’ll summarize as follows.

Despite the fact that contractor employees were working far in excess of 40 hours per week on a routine basis, the contract refused to recognize those excess hours as being overtime. Because the hours worked in excess of 40 were not overtime hours, they were part of the employees’ “basic compensation.” (This makes sense because the employees were expected to work those excess hours on a routine basis and did not get any overtime premium pay for working them, to which they might otherwise have been entitled.) Because the excess hours were part of the employees’ basic compensation, CACI properly used the employees’ total work hours as the basis for applying danger pay uplifts.

Although the dollars involved were relatively small, the issue is large. This decision, unless overturned on appeal, will establish proper application of salary uplifts for contractor employees assigned to support overseas operations.

 

 

DOD Issues More Guidance on Commercial Items

E-mail Print PDF

On 02 September 2016 the Director, Defense Procurement and Acquisition Policy, issued new policy guidance on commercial item determinations.

As we understand it, the guidance implements the tenets of the proposed rule on the topic. To be clear: the guidance implements the proposed rule before public comments are received and before it becomes a final rule.

Now, we didn’t have very many problems with the proposed rule. We opined that the definition of “nontraditional defense contractor” was poorly worded and would lead to (perhaps) unintended consequences. And we snarked a bit at the news that DOD has a “cadre of experts” in commercial item determinations who would be available to offer “expert advice” to contracting officers on the topic. Other than those two cavils, we were generally in favor of the proposed rule. However, the fact that we liked the proposed rule is not at all the same thing as endorsing an early implementation via guidance memo of something that really needs to wait for the rule-making process to complete. If DOD felt so strongly about the topic, the rule could have been issued as an interim rule; but it wasn’t.

Anyway, back to the memo. It announces six Commercial Item Centers of Excellence “staffed with a cadre of engineers and price/cost analysts to advise” COs in how to make commercial item determinations. Again, nothing is provided regarding the qualifications of the cadre (times six) and we have to wonder where all those experts are coming from? Are they being decanted from storage? Because if they’ve been around, we’ve never encountered them.

As the memo notes, “the responsibility for commercial item determinations remains a PCO responsibility.” However, we strongly suspect that it will be a rare, courageous PCO who takes issue with the advice and assistance of the “experts” located in the Centers of Excellence.

Interestingly, the memo notes that DOD elements and “interested companies” are “working closely” to “define, through the use of advance agreements, the types of information necessary to support commercial item determinations and associated pricing determinations.” In other words, certain companies will be able to enter into Advance Agreements that will permit streamlined determinations. The Advance Agreements will be uploaded into the CBAR database. Companies that do not execute Advance Agreements in this area may not be able to avail themselves of streamlined determinations.

Selling commercial items to the DOD does not have to be difficult. However, certain elements within DOD historically have tried to impede the process. In addition, certain contractors have created difficulties by failing to provide information that a CO deemed necessary to their determination. This memo should go a long way toward helping in this area though, as noted, we still have some concerns with the process.

 

 

Pre and Post Contract Costs

E-mail Print PDF

DCAA incurred cost audit procedures often require auditors to examine claimed costs that are outside a contract’s period of performance. Many contracts specify a period of performance – i.e., a start date and a completion date. For example a firm, fixed-price (FFP) contract might specify that a contractor must provide a specific Level of Effort (LOE) for a certain duration. (See, for example, FAR 16.306(d)(2).) DCAA audit guidance (at 6-202.2, Feb. 2016) directs auditors to disallow claimed costs outside the specified contractual period of performance, stating: “The auditor shall not approve for reimbursement any costs incurred by the contractor subsequent to the expiration date stated in the contract, or in excess of contract limitations.”

Thus, according to DCAA, costs incurred after the expiration of the contract’s period of performance will be disallowed. But note the language carefully. It says “costs incurred by the contractor” not all costs. For example, costs incurred by a subcontractor before the expiration of the prime contract’s period of performance, but not recorded by the prime contractor until after the expiration date are clearly allowable costs.

Disagreements with DCAA auditors often center on contract close-out activities, such as efforts to obtain plant clearance for property, security and intellectual property certifications, and costs associated with preparing final invoices. If those efforts are charged as direct costs, and fall outside the contractual period of performance, they run the risk of disallowance. As we have posted before, our recommendation is to consistently treat the costs of contract close-out activities as being indirect costs, thus avoiding that risk.

Some contracts are called “completion-type” because they obligate the contractor to deliver the specified product. While costs incurred in excess of estimated costs may not be reimbursed, the contract’s period of performance may be waived. In other words, the contractor may deliver late, and any costs incurred in performance (even after the period of performance has expired) may be claimed as allowable costs, up to the contractually specified cost limit. (See DCAA CAM at 6-202.3.) With respect to completion type contracts, the DCAA CAM states: “… questioning costs based only on the fact that they were incurred after the performance period would be inappropriate.”

But what about costs incurred before the official contract start date?

Such costs are called precontract costs. They are discussed at the cost principle found at FAR 31.205-32. That cost principle states—

Precontract costs means costs incurred before the effective date of the contract directly pursuant to the negotiation and in anticipation of the contract award when such incurrence is necessary to comply with the proposed contract delivery schedule. These costs are allowable to the extent that they would have been allowable if incurred after the date of the contract (see 31.109).

Based on the cost principle, if a contractor starts work early, it may claim those costs only if certain conditions are met. To be allowable, the precontract costs must:

  1. Be incurred “directly pursuant to” contract negotiations. We interpret that to mean that the contractor must disclose its early start to government negotiators, and they must not prohibit the early start.

  2. In anticipation of the contract award. We interpret that to mean that both parties must believe that the contractor will receive an award. A contractor cannot simply start work based on submitting a proposal; there must be a clear indication that the contractor will be the winning offeror and the government anticipates giving that contractor a contract.

  3. Must be necessary to comply with the proposed delivery schedule. The costs must be shown to be related to the proposed delivery schedule, such that, without being incurred, the proposed delivery schedule cannot be met.

  4. The must be allowable. In other words, a contractor cannot make an unallowable cost allowable by calling it a precontract costs.

Finally, there is a reference to FAR 31.109, meaning that the FAR drafters recommend an Advance Agreement be executed to clearly show the parties’ intent to incur and reimburse precontract costs. Note that such an Advance Agreement is not required; it is simply recommended. Legitimate precontracts costs that meet the four tests noted above should not be disallowed by DCAA auditors because an Advance Agreement is lacking. (See DCAA CAM at 6-202.1.)

Given the scrutiny DCAA auditors often apply to contracts’ periods of performance, contractors should take care to ensure that all claimed costs fall within specified contract dates. Where costs fall outside the contractual periods of performance, see if one of the exceptions we’ve listed here may apply. Another good practice is to modify the contract (or subcontract) as necessary to adjust the official period of performance to match the parties’ expectations. In our experience, it’s easier to process an administrative (no-cost) mod than it is to try to convince the auditors that a claimed cost that falls outside the official contract period of performance should not be disallowed.

 

Thoughts on the Navy Gold Coast Small Business Conference

E-mail Print PDF

appogee_consulting_trade_showAs many of you know Apogee Consulting, Inc. attended its first trade show this past week. We exhibited at the Navy/NDIA Gold Coast Small Business conference, a 2-day affair. This article explores our impressions of the conference.

First, thanks to all those who sponsored the conference, who volunteered, who handled logistics, who coordinated the speakers and who made everything work for the participants and exhibitors. We very much appreciate your efforts.

Second, let’s talk about the presentations and the speeches.

Oh, wait. We can’t do that, because we didn’t hear any of them. We were over in the exhibitors’ space for the entire two days. To be fair, we could have – and were encouraged to – go have lunch with the participants and listen to the luncheon speakers. We chose not to accept that offer and, instead, to hang out in case anybody wanted to discuss Apogee Consulting, Inc. with us. (We were not the only exhibitors to make that decision.)

When we say above that we were “encouraged” to have lunch and listen to the luncheon speakers, that’s a bit of understatement. In fact, the exhibitors’ space was closed and the doors were locked and security actively kept people – including the exhibitors – from entering. The only flaw in that cunning plan was the bathrooms. Each bathroom had multiple entrances. For example, the men’s room had two doors facing the main hallway. In addition, the men’s room had a door that faced the exhibitors’ space. So while security had locked the entrance doors and was guarding them with two or sometimes three people, we just went in and out through the bathroom. It was no problem whatsoever. (Don’t tell them about the security hole.)

We were excited to be among the exhibitors, which included large primes (such as Lockheed Martin, Northrop Grumman, Raytheon, and AMEC Foster Wheeler) and other small businesses. Most of those small businesses seemed to be in search of primes that would buy their services/products. Some of the small businesses were looking to hook up with Navy folks and maybe grab a small business set-aside award. Some of the exhibitors (like us) were looking to hook up with the other exhibitors and make B2B deals.

Unlike most (if not all) of the other exhibitors, Apogee Consulting, Inc. wasn’t there solely to generate sales. We were there to expand brand awareness and to perhaps engage in some discussions about government contract compliance and related matters. And indeed, we had several good interactions. Those interactions may turn into projects or they may not, but they were fun!

We had several discussions with primes and several discussions with others (e.g., DCMA) and they encouraged us to submit Statements of Qualifications and to register in the appropriate databases so that we could get work. After some internal discussion, we don’t think that’s the right approach for us. We are a very small consultancy and we simply don’t have the bandwidth to support a large number of engagements. While it would be nice to be recommended by DCMA, contracting officers and/or primes to their various small business constituencies, we don’t have the appetite to support that work. Thus, we’ll continue to rely on this blog, word of mouth, and other channels to generate a small number of advisory projects with select clients—projects that we will enjoy performing.

Interestingly (as least to us) we overestimated the interest in government contract compliance by the attendees. We had anticipated about 150 – 200 interactions and we had about 10 – 15 over the course of two days. And in no case did anybody actually ask us any questions about compliance. The closest we got was a question about QuickBooks. In another instance we offered several sites for research purposes and we recommended one or two seminar providers. But that was it. The people who stopped to chat acknowledged the importance of compliance, and they acknowledged their general lack of knowledge in the area, but they couldn’t (or wouldn’t) engage in any in-depth discussions. There were no questions about cost allowability or direct versus indirect or compliance with Cost Accounting Standards. That surprised us. On the other hand, perhaps people were reluctant to air their dirty laundry in public, preferring rather to research us before engaging us. Which is fine … but nonetheless it took us by surprise.

All the other exhibitors had trinkets to give away in order to attract people to their booths. There were many with pens, some with candies, others with mousepads. There was one with branded mini-calculators. Everybody had something. Apogee Consulting, Inc. had knowledge. We were giving away advice and knowledge. That was all we had.

We were giving away knowledge but almost nobody at the conference seemed to want to receive it. Several participants acknowledged the importance of knowledge in this difficult area, and they acknowledged they lacked knowledge in this important area, but nobody – none of the people at the conference – tried to rectify their lack of knowledge by actually asking questions of the people who were the (relative) experts in the area.

 

SBA Opens Mentor-Protégé Program to All Small Businesses

E-mail Print PDF

Did you see this final rule, published in the Federal Register on July 25, 2016? It’s kind of awesome. It expands the Mentor-Protégé Program to all small businesses.

Before now, the Program was limited to 8(a) Program participants. If you were an 8(a) participant, then you could be a Protégé to a large business Mentor. There were several advantages to both parties from program participation. With respect to DoD participants under the “pilot” Mentor-Protégé Program (which was initially established in 1991), Protégé firms can receive significant assistance from their Mentor firms in terms of management systems, help with proposal preparation, and other important areas. With respect to the Mentor firms, they can receive direct reimbursement from DoD for the costs of assisting the Protégé firms, or if not direct reimbursement, they can apply their costs towards small business plan credit for categories in which they are lagging their goals. And (perhaps most importantly) a Mentor firm can award a subcontract to a Protégé firm without competition.

We did our time in the Mentor-Protégé Program trenches in the 1990’s. Indeed, our team was awarded one of the earliest Nunn-Perry Awards for achievement in that area. But that was a very long time ago, and the new SBA rules signal a new chapter in the Program.

The new rule opens the Program to all small businesses. If your firm qualifies as a small business under a NAICS code, then it can qualify as a Protégé firm – assuming you can find a Mentor firm willing to help you out. If you are a large business, then any small business supplier you have—or are considering using—can become a Protégé firm. The benefits from the arrangement are noted above.

And SBA expanded the benefits as well as opening the program to all small businesses. It loosened the affiliation standards, such that a Mentor and Protégé could create a Joint Venture and pursue work as a small business. The new rule provides –

A firm that has an SBA-approved mentor-protégé agreement authorized … is not affiliated with its mentor firm solely because the protégé firm receives assistance from the mentor under the agreement. Similarly, a protégé firm is not affiliated with its mentor solely because the protégé firm receives assistance from the mentor under a federal mentor-protégé program where an exception to affiliation is specifically authorized by statute or by SBA under the procedures set forth in § 121.903. …

Two firms approved by SBA to be a mentor and protégé under § 125.9 of this chapter may joint venture as a small business for any Federal government prime contract or subcontract, provided the protégé qualifies as small for the size standard corresponding to the NAICS code assigned to the procurement, and the joint venture meets the requirements of § 125.18(b)(2) and (3), § 126.616(c) and (d), or § 127.506(c) and (d) of this chapter, as appropriate.

For purposes of this provision and in order to facilitate tracking of the number of contract awards made to a joint venture, a joint venture: must be in writing and must do business under its own name; must be identified as a joint venture in the System for Award Management (SAM); may be in the form of a formal or informal partnership or exist as a separate limited liability company or other separate legal entity; and, if it exists as a formal separate legal entity, may not be populated with individuals intended to perform contracts awarded to the joint venture (i.e., the joint venture may have its own separate employees to perform administrative functions, but may not have its own separate employees to perform contracts awarded to the joint venture). SBA may also determine that the relationship between a prime contractor and its subcontractor is a joint venture, and that affiliation between the two exists, pursuant to paragraph (h)(5) of this section.

So the ability to joint venture is not without limits, and we strongly recommend that any Mentor and/or Protégé firms seeking to take advantage of this change read the SBA rules in Title 13 of the Code of Federal Regulations very carefully.

Another change is that the SBA will permit a Mentor to invest in and own as much as 40 percent of its Protégé firms without changing the Protégé firms’ status as a small business. This would seem to be of a significant advantage to those large firms seeking access to small business set-asides.

In summary, it looks like the SBA has opened the floodgates and we expect quite a number of government contractors to be thinking hard about how to take advantage of the new environment.

 

 


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