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

Employee Qualifications

E-mail Print PDF

Some Federal government contracts contain requirements and directives regarding who can, and who cannot, charge reimbursable labor hours/dollars to them.

Did we say some? We meant to say all.

All of them do.

Whether you know it or not, every single Federal government contract that will be reimbursing your company for direct labor dollars (or direct labor hours) contains a statement or two (or more) delineating what labor will be reimbursed. If you don’t meet the contractual qualifications, your labor is not reimbursable.

(To be clear: you can always charge the labor to the contract; and in many circumstances you must charge the labor to the contract. However, the contract terms and conditions determine whether or not that labor will be reimbursed by the government customer.)

What happens if you bill labor to the customer that doesn’t meet the contractual definitions of reimbursable labor? Well, sometimes you might get away with it, but it’s likely that—sooner or later—you are going to get caught and then you may end up with an allegation of overbilling. That allegation may well be connected with an allegation that you violated the False Claims Act.

Some contract qualifications are very clear and expressly stated. Perhaps the most obvious example is a contract statement that all employees working on the project must hold the requisite security clearances. If they do not hold those clearances, then their labor is not reimbursable. This situation, of course, often leads to the question about where employees should charge time while awaiting their clearances. The answer to that question often depends on company policy or established practice. However, regardless of what that policy or practice is, that time cannot be billed as reimbursable labor—because it is non-compliant with contract terms and conditions.

The issue of employee labor qualifications is obvious when dealing with Time & Materials (T&M) contract types. In such contracts, each hourly billing rate is essentially a fixed price per labor hour, and a separate hourly billing rate is established for various categories of labor, as defined by the contract. Thus, the contract defines the qualifications associated with each hourly billing rate. For example, there may be separate hourly billing rates for senior engineers, mid-level engineers, and junior engineers. The differences between those three engineering levels will be defined by the contract, typically by parameters such as years of experience, education, and/or responsibility. Often, the contractor proposes its hourly billing rates in accordance with qualifying parameters defined by the Request for Proposals (RFP), and then has to “map” its employees to each hourly billing rate it is proposing.

That’s well and good—but what happens if, during contract performance, an individual employee gains sufficient experience or responsibility (or education) to then map to a higher labor category and associated higher hourly billing rate? The answer is (again) going to depend on what the contract says. Sometimes the contractor can simply remap that employee and bill at the higher rate without notification and without customer permission; but other times the contractor will need to notify the customer (at a minimum) and may even need a formal contract modification.

In other instances, the contractor will miss the opportunity to bill its employee at the higher rate, because nobody is monitoring the employees for such changes. Nobody is looking for the impact of promotions or additional years of experience. Oops! Opportunity missed.

Why are opportunities missed? Because nobody is looking. Nobody is looking because nobody has that responsibility. Is it the Program Manager’s job? Probably not, because most PMs have too many other things to worry about. Is it Accounting’s job? Probably not. If you work at a savvy contractor, you probably set forth the employee qualifications one time, at the beginning of performance, and document the qualifications and/or mapping in the Contract Brief. But many contractors don’t even do that. So how would Accounting know to change the employee mapping? You’re right; they wouldn’t know unless somebody tells them.

Maybe it’s Contracts’ job. Maybe the Contract Administrator or Contract Manager or whatever you call those folks have a responsibility to monitor employees to ensure that they are meeting contractual requirements. But I bet if you asked them, they would say “Not my job. That’s HR’s job.” And indeed, that may be the case—but if that is the case then HR needs to know what the contract qualifications are, and they need to know who’s working on that contract, and they need to know whom to inform when things change. In our experience, HR is busy doing other things (such overseeing the annual performance review process) and they are not likely to be thinking about how to partner with operations in the required area.

So we are left with the thought that it may be the job of Compliance to ensure that employee labor for which government reimbursement is being sought meets the contractual qualifications for doing so. It would seem that any robust compliance program ought to be testing to see whether billed labor meets contractual requirements. You test for cost allowability, why wouldn’t you test for labor allowability?

And if you did robust labor allowability testing you might identify opportunities to bill employees’ time at a higher hourly billing rate! Hopefully, though, you would (at a minimum) catch employees who didn’t meet contractual labor qualifications. You could then recommend that any non-compliant labor dollars be credited from customer billings and recorded as being unallowable direct labor.

That would be nice, wouldn’t it?

In order to accomplish that task, you would probably need some additional Compliance resources. Often, adding Compliance resources is a difficult conversation to have with your management team, because Compliance is seen as a necessary evil whose cost must be minimized to the lowest level possible.

One argument you might advance in support of your request is that government auditors are being trained to look for billed labor that doesn’t meet contractual qualifications. Several DCAA audit programs now include this area; and it’s relatively easy for them to identify non-compliant labor once they obtain resumes and other HR information. Employee interviews are a quick way to have employees confirm whether they have what the resume says they have. So you might consider telling your management team that DCAA is going to be looking for this, sooner or later, and it would be beneficial to the company if it looked first. Plus—maybe identify opportunities to bill at higher rates! (Now Compliance is a profit center.)

Another argument you might advance in support of your request to add more Compliance resources to look at this area is “what happens if we have been mis-billing for years, and we didn’t know it?” To answer that question, you should produce this press release from the Department of Justice.

In that press release, DoJ announced that it had reached a $6.4 million settlement with CH2M Hill, a large engineering services firm, “to resolve allegations that CH2M Hill overbilled the U.S. Air Force for environmental consulting work.” What was the nature of the overbilling?

According to the announcement, “CH2M Hill admits that it billed under the government contract for employees who did not meet the educational and work experience qualifications in the contract.” The subheadline of the press release is very clear: “CH2M Hill overbilled U.S. Air Force for work done by unqualified staff.”

Yeah, that’s not a good headline. More to the point, how many new Compliance resources could CH2M Hill have deployed for $6.4 million? We’re guessing quite a few.

But what makes this announcement interesting (to us) is that the $6.4 million settlement resolved the False Claims Act exposure but the settlement came after CH2M Hill had already refunded to the Air Force $10.5 million. (We believe that prior invoice credit was made pursuant to the mandatory disclosure requirement found in the contract clause 52.203-13.) Thus, this was not a $6.4 million issue; it was actually a $16.9 million issue.

And that value excludes the undoubtedly millions of unallowable dollars paid to attorneys to negotiate the settlement.

Now how many new Compliance resources would you add to mitigate that risk?

One more point. The DoJ announcement went out of its way to allege that CH2M Hill delayed reporting the overbilling for several years. According to the announcement, “CH2M Hill knew of the overpayment as early as 2011, but attempted to keep the information secret by claiming that an audit of its labor practices was privileged information” before finally self-reporting the issue (and refunding the non-compliant labor dollars plus interest on the associated overpayments) in 2017.

Those of you who have to contend with Legal Departments that insist that all internal compliance investigations must be undertaken under Attorney-Client Privilege may want to keep this settlement in mind. We’re just saying….

Employee labor qualifications. Easy to detect problems during an external audit; harder to manage during ongoing contract performance. Thus, an area of high risk to which government contractors should devote resources.

If their management permits them to do so.

 

Rule-Making Like Molasses

E-mail Print PDF

Well, finally. On October 2, 2019, the FAR Councils finally published two proposed rules that would implement the statutory changes made by the 2017 and 2018 National Defense Authorization Acts (NDAAs). Hey, it’s good news!

It’s good news even though these mandated rule-making revisions should have sailed through like a hot knife through butter. Instead, like molasses, they moved slowly—leaving contracting officers and their contractors to rely on controversial theories (such as whether a statutory threshold trumped the regulatory threshold upon which it was based) and Class Deviations issued by individual Federal agencies.

Okay, what are we talking about?

  • FAR Case 2018-004 would increase the micro-purchase and simplified acquisition thresholds to $10,000 and $250,000 (respectively).

  • FAR Case 2018-005 would increase the threshold at which certified cost or pricing data is required to be provided to $2,000,000. In addition, the threshold at which Cost Accounting Standards is applicable is also raised to $2 million.

Right, good news.

But if you’ve read this blog before, you know it wasn’t easy getting these regulatory changes made. We devoted several articles (rants? pleas?) to this topic. Our last article was posted in June, 2018—about sixteen months ago. In that article, we discussed changes to the DOD Class Deviation implementing the statutory changes ahead of the regulatory changes. In the months leading up to that article, we posted article after article, documenting the situation faced by acquisition professionals when the statute changed but not the implementing regulations.

For example, see this one. In it, we wrote:

Do Contracting Officers need to follow the statute or the regulation? If they follow the statute and not the regulation, do they need an official FAR deviation? What about the sentence at FAR 1.602-1(b), which states “No contract shall be entered into unless the contracting officer ensures that all requirements of law, executive orders, regulations, and all other applicable procedures, including clearances and approvals, have been met.” How can a Contracting Officer comply with that requirement if a statute and its implementing regulation are in conflict?

The job of the two FAR Councils and the FAR Secretariat is to make sure those conflicts are few and far between.

So here we are, nearly two years later. And now—only now—have the two FAR Councils and FAR Secretariat published rules that would address the concerns noted above. And they weren’t even published as interim rules!

Like molasses, I tell you.

 

Reforming the Pentagon’s “Fourth Estate”

E-mail Print PDF

The story (which may be apocryphal) goes like this:

Alanis Morissette’s 1995 album, “Jagged Little Pill,” was a huge hit (selling more than 33 million copies); it won five Grammy awards (including album of the year). The album spawned six singles, including “You Oughta Know,” “All I Really Want,” and “Ironic”. The lyrics of “Ironic” are famous for generating a two-decade long debate about whether, in fact, the situations described in the song were ironic. The consensus is that they were not. They were not ironic. Isn’t that ironic?

UK Interviewer: Ms. Morissette, let’s talk about your song, “Ironic.” The lyrics are puzzling. “A black fly in your chardonnay?” “rain on your wedding day?” “good advice that you just didn’t take?” Et cetera. None of those are ironic. Most are just coincidence.

Morissette: Okay.

UK Interviewer: Isn’t this misuse of the word ‘irony’ just another example of the failed American educational system?

Morissette: Actually, I was born and raised in Canada. I’m not American by birth or education.

UK Interviewer: Uh ….

Morissette: Isn’t that ironic?

Whether you call it irony or coincidence, we couldn’t help but notice that the very day after we submitted our most recent blog post—the one that included criticism of the Pentagon regarding its failed efforts to reform its own backoffice bureaucracy (the so-called “Fourth Estate”)—a new report was released from the Pentagon’s Office of the Chief Management Officer (OCMO) that addressed progress to reduce costs in that very area.

Why the report? Well, Section 921 of the 2019 National Defense Authorization Act (NDAA) requires it. Specifically, it requires the OCMO to reduce costs in certain “covered areas” by 25 percent by GFY 2020, or to justify why doing so would create unacceptable inefficiencies. And that same Section of the public law requires the OCMO to issue a periodic report on progress being made. So here it is…

Let’s cut to the bottom-line. Quoting from the report:

In order to meet Congressional intent, this report focuses on reforms and financial savings in the four covered activities within the Fourth Estate, including Defense Agencies and DoD Field Activities (DAFA). While the OCMO projects that it will not meet the 25 percent savings targets in all of the four covered activities in FY 2020 against the FY 2019 baseline, the OCMO forecasts an average 5 percent cost reduction for each of the covered activities in the Fourth Estate.

So: Mission not accomplished.

One thing that we noticed—which should be no surprise to those who follow Pentagon business reform efforts—is that a new group was created to oversee the reductions to bureaucracy. The new group is called “Fourth Estate Management Office” (FEMO). As noted in the report, FEMO is supported by outside consultants.

That’s right. The first action taken in the effort to reduce bureaucracy was to create a new bureaucratic entity.

We further noticed that the ability to reduce Fourth Estate costs was tied to the definition of which entities comprise the Fourth Estate. Thus, adding the Washington Headquarters Services to the definition of the Fourth Estate—and then declaring a goal to reduce WHS costs by 30 percent—means that the other functional aspects of the Fourth Estate don’t need to be cut as much.

That strategy is consistent with a bureaucracy protecting itself.

Is this a big deal? Not really. It’s just interesting to observe how the Pentagon protects itself. Former SECDEF Gates called for cuts in this area. Congress called for cuts in this area via public law. You’d think there would be some accountability for failing to deliver. Not so far.

The Pentagon bureaucracy seems to be avoiding the hard decisions in an apparent effort to protect certain fiefdoms, despite being told to make those hard decisions by people who would seem to have authority in the chain of command.

Isn’t that ironic?

 

So Then This Happened … Regulatory Changes

E-mail Print PDF

I’m not a big fan of just linking to proposed and/or final rule changes, nor am I a big fan of simply recapping what they say. My thought is: You all can do that. You can read the rule and grasp what’s going on. Thus, I don’t normally just tell you what’s happening because you can all do that for yourselves.

Instead, I want to express a point of view about the regulatory change. I want to tell you what’s happening and then opine on why it matters—or should matter—to you. That’s the goal of this blog (even if it sometimes gets me into trouble.) I want to tell you what’s going on and why you should care.

With that being said, let’s discuss some recent regulatory rule changes.

  1. Effective 01 October 2019, the DFARS was changed via final rule to limit the use of Lowest-Price, Technically Acceptable (LPTA) source selection procedures. Going forward, the LPTA process can only be used when—

(i) Minimum requirements can be described clearly and comprehensively and expressed in terms of performance objectives, measures, and standards that will be used to determine the acceptability of offers;

(ii) No, or minimal, value will be realized from a proposal that exceeds the minimum technical or performance requirements;

(iii) The proposed technical approaches will require no, or minimal, subjective judgment by the source selection authority as to the desirability of one offeror's proposal versus a competing proposal;

(iv) The source selection authority has a high degree of confidence that reviewing the technical proposals of all offerors would not result in the identification of characteristics that could provide value or benefit;

(v) No, or minimal, additional innovation or future technological Start Printed Page 50789advantage will be realized by using a different source selection process;

(vi) Goods to be procured are predominantly expendable in nature, are nontechnical, or have a short life expectancy or short shelf life (See PGI 215.101-2-70(a)(1)(vi) for assistance with evaluating whether a requirement satisfies this limitation) ….

And the LPTA process must be avoided “to the extent practicable” in the following circumstances:

(i) Information technology services, cybersecurity services, systems engineering and technical assistance services, advanced electronic testing, or other knowledge-based professional services;

(ii) Items designated by the requiring activity as personal protective equipment (except see paragraph (b)(1) of this section); or

(iii) Services designated by the requiring activity as knowledge-based training or logistics services in contingency operations or other operations outside the United States, including in Afghanistan or Iraq.

And the LPTA process is “prohibited” in the following circumstances:

… items designated by the requiring activity as personal protective equipment or an aviation critical safety item, when the requiring activity advises the contracting officer that the level of quality or failure of the equipment or item could result in combat casualties. See 252.209-7010 for the definition and identification of critical safety items.

… to acquire engineering and manufacturing development for a major defense acquisition program for which budgetary authority is requested beginning in fiscal year 2019.

All of the above changes were driven by legislation—i.e., language found in the FY2017 and FY2018 National Defense Authorization Acts (NDAAs).

What was Congress thinking?

Well, we think Congress was reacting to the recent trend by the DOD in awarding major defense procurements to companies who are willing to “invest” in them by offering prices below estimated costs. See, for example, this article discussing Boeing’s ability to “invest” (in the words of its executives) “to create long-term valuable products and services franchises.” In that same article, we discussed news reports stating that Marilyn Hewson (Lockheed Martin’s CEO) had said that her company didn’t have the same cash resources as Boeing had, and that it could not compete if the competition is based on the size of the contractor investment. More explicitly, Lockheed Martin’s CFO was quoted as saying “Those [losses] were disappointing for a lot of reasons. But the fact they really decided, all three, on an LPTA (lowest price technically acceptable) basis, didn’t help the situation.”

Thus, we reckon that Congress heard those complaints (whether from reading them in the press, or via testimony at hearings, or via whispers of lobbyists into the right ears) and decided to tell DOD to knock it off.

And how is Boeing’s strategy working out for the company?

  • It’s winning orders for new aircraft.

So: a mixed bag. In the long run, Boeing’s strategy likely makes sense for the company and its shareholders (of which I am one). However, in the short-term Boeing has had to take literally billions of dollars in financial reserves to cover its cost growth on the program. As we have pointed out before, if the DOD’s penchant for awarding to the low-bidder were to continue, then only the very largest of contractors will end up with any future awards. Thus, we are pleased to see Congressional action in this area.

Speaking of Congressional action, as the result of a 2017 NDAA requirement, the FAR definition of commercial item was recently revised via final rule. The revised definition adds the following situation to the definition at FAR 2.101:

A nondevelopmental item, if the procuring agency determines the item was developed exclusively at private expense and sold in substantial quantities, on a competitive basis, to multiple State and local governments or to multiple foreign governments.

That should be helpful to a few folks out there.

There have been a number of proposed rules published recently. In the interest of brevity we won’t list them all. But one was “interesting” and we think worth bringing to your attention. See link here.

The proposed rule, if implemented as drafted, would provide notification to contractors doing business in Afghanistan that there are exemptions from liability for Afghanistan taxes, customs, duties, fees or similar charges. The rule does not add any new requirements for contractors; however, it is providing unified guidance for contractors performing in Afghanistan. The DFARS already has such language, but now it’s being proposed for inclusion in the FAR.

Regulatory changes continue to happen. For a long time, the rule-making process seemed paralyzed, but now it seems to be getting back on track.

 

Peering Into the Future

E-mail Print PDF
unnamed
Recently I had an opportunity to attend an industry briefing, given by a senior DOD acquisition policy official. (I need to be vague here because the briefing was on a “non-attribution” basis, meaning that no direct quotes are permitted.) In that briefing, the senior official cited to the 2018 U.S. National Defense Strategy.

The National Defense Strategy (NDS) is the successor to the Quadrennial Defense Review. As such, it is produced very four years. It provides broad guidance to the Pentagon in areas such as military planning, military strategy, force posturing, force constructs, force modernization, etc. The Pentagon takes that guidance and, through the Joint Chiefs of Staff, creates the National Military Strategy (NMS), which provides detailed guidance for theater campaign planning, modernization, force posturing, and force structure. The NMS is classified; while most of the NDS is not.

Thus, when this senior DOD acquisition policy official cited to the latest NDS, he was citing to the highest level of U.S. military strategic planning. It was interesting to see an acquisition official cite to military guidance, but it made sense—because the military objectives are intertwined with acquisition objectives.

The 2018 NDS includes eleven strategic objectives. We’re going to list just two of them, because they seem relevant to the topic. They are:

  • Continuously delivering performance with affordability and speed as we change Departmental mindset, culture, and management systems

  • Establishing an unmatched twenty-first century National Security Innovation Base that effectively supports Department operations and sustains security and solvency

The first bullet point listed above is an old topic, much repeated. We first noted it way back in 2009, when we reported to readers that the Defense Science Board had told SECDEF that the DOD acquisition process was too bureaucratic to meet the needs of the warfighters. In the intervening decade, not much has changed, though some Section 809 Panel recommendations, if adopted, might move the needle a bit.

The second bullet point is also interesting from a nomenclature perspective. Historically, the defense industrial base has been referred to as just that—“the defense industrial base.” In fact, the official Pentagon component that works in that space is the “Industrial Policy Office.” So to see the description change to “National Security Innovation Base” is interesting and speaks to what the Pentagon is hoping to get.

Importantly, the NDS devoted a significant amount of verbiage to acquisition reform. (Only it wasn’t called that.) The NDS stated—

The current bureaucratic approach, centered on exacting thoroughness and minimizing risk above all else, is proving to be increasingly unresponsive. We must transition to a culture of performance where results and accountability matter. … Current processes are not responsive to need; the Department is over-optimized for exceptional performance at the expense of providing timely decisions, policies, and capabilities to the warfighter. Our response will be to prioritize speed of delivery, continuous adaptation, and frequent modular upgrades. We must not accept cumbersome approval chains, wasteful applications of resources in uncompetitive space, or overly risk-averse thinking that impedes change. Delivering performance means we will shed outdated management practices and structures while integrating insights from business innovation. …

Better management begins with effective financial stewardship. … We will continue to leverage the scale of our operations to drive greater efficiency in procurement of materiel and services while pursuing opportunities to consolidate and streamline contracts in areas such as logistics, information technology, and support services. We will also continue efforts to reduce management overhead and the size of headquarters staff. We will reduce or eliminate duplicative organizations and systems for managing human resources, finance, health services, travel, and supplies.

Naturally, the above objectives are much more easily said than done. Still, most of us would agree they are important objectives that, if met, could make the defense acquisition environment a more efficient (and easier!) marketspace in which to operate.

But as history consistently has shown us, the Pentagon is not comfortable shining a light into its back-office workings. (See this blog article for one example.) As soon as Congress (or the Secretary of Defense) challenges the Pentagon to reduce bureaucracy (and/or costs), the next step is to focus on contractors. That diversion ignores the fact that contractor costs (largely) come out of a different color of money, and it ignores the fact that those who focus on contractors instead of the Pentagon’s “Fourth Estate” are missing the point of the exercise. Still, it’s the traditional approach when faced with a challenge to shrink Pentagon bureaucracy and to streamline business processes.

In what we are sure is an effort completely unrelated to the NDS objectives discussed above, that same senior Pentagon acquisition official noted that it is past time to perform another study of contractor financing and profit. The reported goal is to complete that study by the end of GFY 2020.

Many readers are largely ignorant of the give-and-take between Pentagon leadership, Congress, and the largest defense contractors. That give-and-take involves influencing annual National Defense Authorization Acts (NDAAs), establishing acquisition policy goals, and addressing proposed changes to acquisition regulations. It’s an ongoing process, involving lobbyists, staffers, Pentagon stakeholders, and industry associations (just to name a few). The give-and-take process is happening right now, and it will continue into the foreseeable future.

We trust you’ve enjoyed a glimpse into that process.

 


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