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

Statute of Limitations, Again

E-mail Print PDF

Acquaintances who are attorneys assure me that the current state of judicial interpretation of the Contract Disputes Act (CDA) Statute of Limitations (SoL) rules make sense and can be consistently enforced. Okay. We’re not attorneys so we’ll have to take their word for it, even though we can’t figure the logic out for ourselves.

Some things we think we know:

  1. Unallowable direct costs: The CDA SoL starts running when the customer pays the invoice. (See: Sparton de Leon Springs)

  2. CAS noncompliances: The CDA SoL starts running when the customer pays an invoice that included the noncompliant costs. (See: Fluor) Or when the customer knows it has been harmed through overbillings resulting from noncompliant costs. (See: Lockheed Martin)

But with respect to unallowable indirect costs, the judicial record seems a bit more muddied to us. (Again, perhaps that’s just us!)

There is a Raytheon decision that states the CDA SoL clock starts running when the contractor submits its final billing rate proposal, because (essentially) the government had the ability to start the audit at that time. However, there are other decisions that state that the CDA SoL clock starts running (with respect to indirect costs) when the audit starts (or perhaps concludes), because only then has the government looked at individual indirect cost transactions and had the ability to know whether claimed costs were allowable or unallowable.

Because of those latter decisions, we have recommended that contractors submit their general ledgers showing all indirect cost transactions along with their final billing rate proposals, when feasible to do so. (We get that it rarely is feasible to do so.)

In addition, we strongly suspect that the CDA SoL issue(s) are going to go away soon—at least with respect to unallowable costs—because DCAA is now operating under a public law that requires the auditors to complete their audit within one year of contractor submission. This means that contractor final billing rate proposals won’t lie fallow for years, as was the case up until the statute was amended by an Act of Congress.

Still, contractors who submitted their proposals (and/or who were audited) prior to the change are still dealing with CDA SoL issues, as we will now discuss.

In a recent decision on competing motions for summary judgment, Judge Hartman of the ASBCA gives some hope that the CDA SoL rules on unallowable indirect costs may be clarified in the near future. To be clear, Judge Hartman, writing for the Board, denied both motions. It was the reasoning used that we found to be of interest.

Advanced Technologies Group, Inc. (ATGI) appealed two Contracting Officer Final Decisions (COFDs) in which certain indirect costs questioned by DCAA during audit were found to be expressly unallowable and penalties were assessed. The years in question were ATGI’s FY 2007 and FY 2009. Apparently ATGI is one of those contractors where only some final billing rate proposals are audited in full. (The decision noted that “DCAA advised [ATGI that] full, detailed reviews would occur only every three to five years, with less-detailed reviews occurring the other years.”) This may have been because ATGI was a small business with only few cost-type contracts—primarily those issued under the Small Business Innovation Research (SBIR) program.

(Interestingly, DCAA had classified ATGI as “low risk” until it filed its appeals at the ASBCA, whereupon ATGI suddenly became a “high risk” contractor whose annual final billing rate proposals would receive very thorough audits. We note the only thing that seemed to have changed was ATGI’s willingness to challenge DCAA audit findings in court.)

Many small businesses stumble when they receive their cost-type SBIR contracts. We’ve written before about the challenges associated with making the transition from receiving grants or fixed-price contracts to receiving cost-type contracts. However, in this case, ATGI made efforts to do the right thing. The decision notes that “ATGI consulted with DCAA regarding its accounting practices, direct and indirect rates and the methods to establish those rates from the first cost-plus contract it performed. ATGI used the incurred costs electronically (ICE) Excel spreadsheet model furnished by DCAA to submit its incurred cost proposals.” (Citations omitted.) It took ATGI four tries to get an adequate final billing proposal with respect to its FY 2006 claimed costs; presumably, by FY 2007 and FY 2009 it had learned what DCAA needed to see and was able to submit adequate proposals the first time.

During its audits of FY 2007 and FY 2009, DCAA questioned two types of claimed indirect costs: marketing expenses and legal expenses associated with patents. (Travel costs were also questioned, but did not seem to be a part of the dispute.) The Judge stated that, with respect to FY 2006 costs, a final rate agreement was negotiated and executed; in that agreement “Legal and patent costs for FY 2006 were deemed acceptable as part of the G&A indirect rate.” That fact became part of ATGI’s motion for summary judgment.

The chronology of the audits is interesting and may shed some light on the eventual decision on the merits. Apparently, DCAA started and stopped and restarted its FY 2007 audit (as was common at the time). Further, DCAA apparently withdrew from the FY 2009 audit because it was “unable to complete the audit due to time constraints.” The FY 2009 audit thus was completed by the DCMA Contracting Officer, who subsequently claimed that he was unaware of the potentially unallowable nature of ATGI’s indirect costs before ATGI provided support for its claimed costs directly to him.

As noted above, Judge Hartman had competing motions for summary judgment.

ATGI argued that the government’s claims were time-barred by the CDA SoL. Its position was based on the theory that the SoL clock started to run when it submitted its final billing rate proposals to the government for audit.

The government argued that the SoL clock started to run when it learned of the nature of the transactions at issue. Judge Hartman wrote—

In submitting its FY 2007 and 2009 ICPs, ATGI did not provide DCAA any financial, accounting or other records or documents with specific information regarding the marketing, legal fees or travel expenses included in the G&A Schedules. For example, DCAA did not obtain data showing or from which it could have known of the unallowability of the patent costs identified as expressly unallowable in the FY 2007 COFD until after May 10, 2011.

(Citations omitted.)

Thus, according to the government, the COFDs (issued April 13, 2015 and January, 2018, respectively) were timely based on when it received information from ATGI showing the nature of the claimed indirect costs.

ATGI disputed the government’s position, arguing that “DCAA knew at the time it accepted the ICPs what types of costs were incurred ‘based on all previous incurred cost proposals submitted, accepted and audited by DCAA for the full history of ATGI’.” The following paragraph from Judge Hartman concisely summarizes ATGI’s and the government’s arguments—

ATGI essentially asserts here that, at time of receipt of its ICPs, the government had access to its accounting system and could verify it was billing the government for the costs billed. ATGI therefore concludes the government ‘should have known’ the material facts of the claims it asserts against ATGI. The government denies that it knew or should have known at time of its receipt of the ICPs information necessary for assertion of its ACO’s claims. The government presents affidavits of its officials testifying the ICPs did not identify the specific cost transactions forming the basis for its claims. According to the government, while it knew ATGI was billing costs to the government, it did not know facts sufficient to conclude that some of those costs were expressly unallowable and created a cause of action.

The Board was unable to grant either party’s motion for summary judgment. With respect to ATGI’s arguments, “ATGI … has not met its burden of establishing the requisite factual predicate for invoking the statute of limitations as a bar to the government’s claims.”

With respect to the government’s arguments, the Board found that the government had not met its burden of proving that ATGI’s claimed costs were, in fact, unallowable—let alone expressly unallowable. (We’ve written about the difference between the two types of unallowable costs on this blog.) In particular, Judge Hartman wrote—

The government also has not shown that the patent legal costs claimed are not required by the contracts at issue. SBIR contracts, such as the four here, generally contain a patent rights clause specifying the rights retained by the contractor and the rights granted the government in inventions developed under the SBIR contract. E.g., FAR 27.303(b), 52.227-11. …

The patent rights clause in ATGI’s SBIR contracts expressly requires it to protect the government’s interests. Specifically, the contractor is to have executed and delivered to the government all instruments necessary to establish or confirm the rights throughout the world that the government has in an SBIR funded invention for which ATGI possesses title, including notifying the CO of any decisions not to file a nonprovisional patent application, continue the prosecution of a patent application, pay maintenance fees, or defend in a reexamination or opposition proceeding upon the patent in any country before expiration of the response or filing period required by the relevant patent office. …

While we do not decide the issue today, it appears the requirements of FAR 52.227-11(c) place a contractual obligation upon a contactor to perform the effort described in FAR 31.205-30(a)(1), (a)(2), and (a)(3). If that is so, it appears that related patent legal costs would be allowable. See FAR 31.205-30(c).

Thus, the government had the burden of showing that ATGI’s legal expenses related to patents were not required by its SBIR contracts, a burden it could not meet in its motion for summary judgment. Judge Hartman concluded—

Because the record before us primarily contains terse legal bills specifying money due for patent legal work without a detailed description of the legal work actually performed and the government has not presented evidence regarding the disputed costs showing that they are expressly unallowable, we currently do not have a factual basis to grant summary judgment to the government that ATGI’s patent legal costs are ‘expressly unallowable.’ Because the government has not developed the facts sufficiently here, the issue of allowability of the disputed costs cannot now be resolved by summary judgment. Simply put, there are genuine issues of material fact that bar us from granting the government’s cross-motion.

(Citations omitted.)

While neither motion for summary judgment prevailed, this seems to be an interesting case with facts that may lead to a further clarification of the muddled rules on interpretation of the CDA SoL when the case goes to a trial on the merits. So stay tuned for more on this matter.

 

Accidental Diversity

E-mail Print PDF

[Editor’s Note: This article was first published on LinkedIn.]

Those who know me and/or read my blog know that I tend to go off on rants from time to time. I don’t really want to upset anybody, but sometimes things upset me; the blog is a vehicle to communicate with others about the situation. With whom am I communicating? I don’t ever really know that for sure, but I do know that I have a small following who thinks that my blog articles are of some interest.

Like me, they are interested in the arcana of government contracting and the myriad of issues that a government contractor must deal with on a daily basis. Proposals and pricing of goods/services. Cost accounting and compliance with Federal Acquisition Regulations and Cost Accounting Standards. Accurate billing. Program management and supply chain management. Changes and Requests for Equitable Adjustment. Budget management. Calculation of indirect rates. Terminations. Claims. Fun and interesting stuff—if only to a few people, like me.

Who could get upset about any of that stuff?

Hold on, because what follows is a rather long rant.

Recently I came across a Department of Justice press release that announced a legal settlement with a government contractor. The amount of the settlement--$19 million—indicated that the contractor had a fairly serious situation to resolve. No, I’m not going to identify that contractor here. That’s not the point of this article.

The point of this article is about making good hiring decisions.

Interested in how the contractor got to where it had a $19 million legal settlement (after receiving credit for making the initial disclosure and cooperating with investigating authorities, and after incurring no doubt quite a bit of unallowable legal costs along the way), I spent some time looking at the company’s website. In particular, I looked at the open positions to see if the company’s $19 million “lesson” had sparked the recognition of the need to hire some top-notch government contracting compliance folks to prevent a future recurrence of the same issue(s) that led to the settlement.

I was disappointed at what I found. In particular, what I found indicated that—based solely on the position descriptions—the company was unlikely to ever fill an open position with the right candidate. To say the position descriptions were vague would be to pay them a compliment.

It occurred to me that if you can’t describe what you are looking for in a prospective hire, you are unlikely to find the right candidate. At a minimum, you will waste a lot of time reviewing resumes of candidates who don’t meet your needs.

If you wonder why you get so many resumes that seem unrelated to the position you are trying to fill—or why you can’t seem to fill the position despite months of effort—perhaps it’s because you didn’t properly describe your requirements. If you can’t clearly define your requirements you are going to have challenges along the way.

We know this to be true in other areas, such as software development. The first thing one needs to get started is a detailed set of requirements. Generally, you don’t have a project until you have a set of requirements. (As one software development company states, the first milestone in software development is gathering requirements, and the second milestone is to validate those requirements.) Moreover, one of the bigger gripes in software development (or any project management discipline, really) is changing requirements. If you change the requirements, you are bound to get cost and schedule impacts. Changing requirements are the bane of effective project management, though I would assert that the ability to handle changing requirements is the mark of an effective project management team.

Let’s apply that viewpoint to talent acquisition, using as an example an actual job opportunity posted on that same company’s website. Let me show you what I saw on the company’s “career” website and let me share my thoughts about what I saw.

Among the positions the company is looking to fill, one is called a Project Finance Analyst. This is a common position in government contractors; typically, it is a business management person who handles the financial aspects of the project, allowing the Project Manager to focus on technical and customer management. In this case, the successful candidate will “will work under close supervision to support the management of numerous tasks and provide overall management of project financials.” Clearly, then, the company is looking for an individual contributor.

I’ll ignore the key responsibilities of the position, because they are essentially the customary responsibilities that one would expect to see. I’m going to focus on the position’s qualifications, both “required” and “preferred.” Quoting verbatim, here is what the position description states:

Required Qualifications

  • Requires a Bachelor's Degree in area of specialty or equivalent and at least 8+ years of experience in the field or in a related area

  • 5 or more years of experience in a government contracting environment. Working knowledge of indirect rate structures, a plus

  • Demonstrated proficiency in Microsoft Office, especially Excel

  • Work independently and in collaborative teams, and to adjust schedule to address workload demands and meet deadlines

  • Attention to detail and the ability to manage multiple duties simultaneously while meeting deadlines

  • Excellent organizational, analytical, and problem-solving skills

  • Strong interpersonal, verbal and written communication skills

  • Must be proactive and eager to tackle new challenges

Candidates that do not meet the required qualifications will not be considered.

Preferred Qualifications

  • Understanding of various contract types, e.g., cost plus fixed fee, award fee, fixed price contracts, and Government Wide Agency Contracts

  • Knowledge of Microsoft Excel including advanced formulas and their use in financial tracking, analysis, and reporting environments

  • Knowledge of monitoring compliance with general contract terms and conditions for government contracts and supporting multiple clients in a fast-paced environment Experience with financial modeling, including revenue projections

  • Experience with project or program management, including Federal Acquisition Regulation (FAR) and Joint Travel Regulation (JTR) requirements

  • Experience with accounting standards, such as General Accepted Accounting Principles (GAAP) and Sarbanes-Oxley (SOX)

  • Experience with financial management support in a government contracting environment

Let’s start with the required qualifications.

  • Bachelor’s degree “in an area of specialty” or no Bachelor’s degree and “at least 8+ years of experience in the field or in a related area”

I’m not a Talent Acquisition expert, but I really have very little idea as to what that even means. What, exactly, is “an area of specialty”? Does a degree in art history count? What about basket-weaving? Each of those is an area of specialty. If the company meant a degree in a field related to the job responsibilities, then why didn’t it say so? Remember, candidates that don’t meet the required qualifications will not be considered. If, for example, a candidate was not considered based on having a degree in art history versus a degree in finance, then that would seem to be grounds for some type of complaint about the fairness of the hiring process.

Also you don’t really even need a degree, so long as you have “at least 8+ years” (sic) of experience “in the field” or in “a related area.” What field? “Field,” as in farming? Or perhaps you are a veteran who has been deployed oversees “in the field.” Do those count? And what “area” is related to the field? Agriculture in general? Animal husbandry? Viniculture?

Oh, you mean a field related to finance. Is that what you meant? Then why didn’t you say so? Remember, you are going to be discarding candidates that don’t meet the required qualifications, so you had better be clear regarding exactly what those requirements are. Because you didn’t specify “the field or a related area,” you should expect to see a lot of candidates with widely disparate backgrounds.

Diversity is good! But diversity without purpose doesn’t help anybody, especially if most of the candidates with “diverse” backgrounds will not make the list of finalists for the position. In this case, let’s call it “accidental diversity.” It’s probably not a good thing, since it wastes the time of both the applicants and those vetting applications.

Diversity without purpose wastes times and keep you from finding the right candidate you are looking for.

(And do I even have to mention that if you fail to consider a candidate who does not have a Bachelor’s degree but who does have more than eight years of experience in a related area, then you aren’t following your own rules?)

But let’s move on.

  • 5 or more years of experience in a government contracting environment. Working knowledge of indirect rate structures, a plus

Okay, this seems clear. “5 or more years of experience in a government contracting environment.” But what kind of experience is required? I know some members of the janitorial staff who have more than 5 years of experience working in a government contracting environment. Do they meet the required qualifications? If not, why not? Since the company failed to specify the type of experience that candidates are required to possess, it should expect a wide range of applicants, very few of whom the company is really looking for. (See: “accidental diversity.”)

Let’s also discuss that last bit. “Working knowledge of indirect rate structures, a plus.” Why is that even listed here? How can “a plus” be part of the required qualifications? Aren’t required qualifications a pass/fail thing? If a candidate does not have working knowledge of indirect rate structures, has that candidate still met all the required qualifications? If the candidate does possess that working knowledge, is that a preferred candidate?

In other words, why is that particular statement found here and not under “preferred qualifications?”

And I’ve got to tell you, that sentence fragment is the poster child for vagueness. I do have a working knowledge of indirect rate structures, and I don’t know what in the world the company is actually looking for. It’s not clear whether “working knowledge of indirect rate structures” means knowledge of how to design a structure, or understanding the FAR and CAS rules of cost pooling and cost allocation, or perhaps merely how to take rates that one is given and apply them to program budgets. (Again: “accidental diversity.”)

As before, “working knowledge” is vague and the company probably means “experience with.” Similarly, the company’s requirement that a candidate must have “demonstrated proficiency in Microsoft Office, especially Excel,” is also poorly written, in my view. How, exactly, will candidates demonstrate their proficiency? Will there be a test? Should they bring a recently completed Excel workbook with them to the interview? What is the difference between “can use Excel” and “proficient in Excel”?

Honestly, to me “working knowledge” means somebody can use the basic functionality. It’s probably the next step up from entry level. In a Project Financial Analyst, you probably want a bit more than that, but whatever.

If the required qualifications are imposed to weed out unqualified candidates, the company should have a plan for executing the weeding. Putting in vague or poorly worded qualifications makes me think that the real weeding process will take place using qualifications other than those listed.

And it would be those unwritten qualifications that could lead to potential legal problems for that company, should somebody look at the pool of applicants versus those interviewed, and see that decisions were made based on unwritten qualifications.

Okay, done with the “required qualifications” and moving to the “preferred qualifications.” Presumably, the preferred qualifications are the means of deciding the list of final candidates, once they have been screened against the “required qualifications.”

  • Understanding of various contract types, e.g., cost plus fixed fee, award fee, fixed price contracts, and Government Wide Agency Contracts

This is another example of vagueness. What does “understanding” mean in this context? As in, “took a class” or “read a book” or “spent 15 minutes reading FAR Part 16 (‘Types of Contracts’)”? Does the company mean “experience working with various contract types,” and, if so, how many years of experience is preferred? Knowledge and experience are two different things. If you have both, that’s great. But don’t confuse one for the other.

  • Knowledge of Microsoft Excel including advanced formulas and their use in financial tracking, analysis, and reporting environments

Check. That would be an important skill to have for a Project Finance Analyst. But what, exactly, constitute knowledge of “advanced formulas” in Excel? Ability to set data filters? Ability to use Pivot tables or VLOOKUP? Ability to click the Autosum button? And who decides when a candidate possesses sufficient Excel skills? The hiring manager? How will the knowledge be tested? Will the results of the test be applied fairly to each candidate?

  • Knowledge of monitoring compliance with general contract terms and conditions for government contracts and supporting multiple clients in a fast-paced environment Experience with financial modeling, including revenue projections

This is the requirement that got me started on this rant. It sounds so good, and still lacks any meaning. How can you determine the right candidate based on this requirement?

Let’s unpack this a bit.

“Knowledge of monitoring compliance.” Note, no actual experience with monitoring compliance is required. Just knowledge. Theoretical knowledge of some unspecified amount. It’s a preferred job qualification. And remember, just “monitoring” compliance. No actual, you know, action is required. Just monitor compliance; and if you see anything noncompliant going on, continue to monitor until directed otherwise.

And what should you know how to monitor? “Compliance with general contract terms and conditions for government contracts.” You know what? Most government contracts (with perhaps the exception of construction contracts) don’t actually have any “general” terms and conditions. There are only terms and conditions of the contract. In an Indefinite Delivery/Indefinite Quantity (ID/IQ) type contract, there are overarching contract terms and conditions, and individual Task or Delivery Order terms and conditions, but there are no “general” terms and conditions. It’s a meaningless thing, written by a person who doesn’t understand what they are hiring for. Yet, it’s a preferred qualification, presumably intended to help identify finalists for the position.

Talk about “accidental diversity!”

I could continue this rant, poking at the preferred “experience with” qualifications that include such disparate subjects as the Federal Acquisition Regulations, the Joint Travel Regulations, Generally Accepted Accounting Principles/Procedures, the Sarbanes-Oxley Act, and “financial management support in a government contracting environment.”

(That latter may be the most important qualification of them all, even though it’s listed last. It’s probably what the company is actually looking for. I would have listed it under “required qualifications,” not “preferred qualifications.”)

I could continue to poke at “experience” because there is no amount of experience that is specified. One day of experience is, apparently, equal to five years of experience. And this is how you get “accidental diversity” with respect to experience, as well.

Certainly, some candidates—especially candidates with experience in CPA firms—are going to have a lot of what the company is looking for. But if the company wants somebody with everything it is looking for, then it should expect to pay top dollar. And the candidate with all that expertise is not going to want to be “closely” supervised; that person is going to expect to work independently and perhaps to supervise others.

Which brings me to: “Who wrote this?” Was it the HR function or Talent Acquisition function? Did they take a standard boilerplate set of qualifications and just post it to the website? That would make some sense to me, given what I saw.

But what if the Hiring Manager wrote all that gobbledygook? How scary would that be? Because it would tell us that the Hiring Manager doesn’t actually know enough about the job to write a meaningful set of required job qualifications. How is that person going to exert effective supervision over this position that (let’s remember) “will work under close supervision.”

At a bare minimum, I would expect that the Hiring Manager reviewed and approved the job opening. That’s really not any better, is it?

In my view this is as poorly worded a job opportunity as I have seen in a long time. The requirements are vague, poorly worded, and will tend to generate a lot of applicants who will not be what the company is really looking for (or what it really needs). I expect the company will generate quite a bit of “accidental diversity” that is going to waste a lot of time and impede the efficient hiring of the right candidate.

Let’s just say that, based on this one job description, I am not surprised the company just paid $19 million to the government in a legal settlement.

 

CAS Board Moves Forward

E-mail Print PDF

As readers know, we are not super satisfied with the recent pace of CAS Board activity. You can blame COVID-19, or you can blame the lack of an industry representative. You can even assert that the CAS Board Chair has other things to think about right now. Whatever the reason, it’s a rare day when we can post anything about CAS Board activity.

This is one of those days.

But before we discuss the CAS Board’s action, we need to put it into context. As part of that context, let’s look at the five stages of grief. They are:

  1. denial

  2. anger

  3. bargaining

  4. depression

  5. acceptance

In fairness, we understand that there is much to criticize in the above model. It’s not necessarily a series of discrete steps that one checks off along the way towards acceptance of loss. But we still think it provides context here: just as there are stages of grief, there are also stages of CAS Board rulemaking.

The difference between the stages of grief and the stages of CASB rulemaking are many; but one fundamental difference is that the CASB rulemaking process is defined by statute. According to the statute, the following summarize the steps of CAS Board rulemaking:

  1. Prepare and publish in the Federal Register a report on the issues associated with the proposed rulemaking (often called a Staff Discussion Paper or SDP)

  2. Publish an advanced notice of proposed rulemaking (ANPRM) in the Federal Register to solicit comments on the report

  3. Publish a notice of proposed rulemaking (NPRM) in the Federal Register and provide all parties affected at least 60 days after publication to submit their views and comments

  4. Publish the final rule

Recently we discussed a Staff Discussion Paper (SDP) regarding possible revisions to Standards 404 and 411. The interesting thing about the SDP was that it didn’t seem to fully embrace the statutory requirement to discuss the issues associated with the proposed rulemaking. Instead, it just asked a bunch of questions. Will the answers lead to publication of an ANPRM or another SDP? We couldn’t say.

The CAS Board moves in mysterious ways.

The CASB also recently published an ANPRM. It wasn’t published in the Federal Register, as statute requires, but there was a Federal Register notice and a link to the ANPRM. So—good enough for government work?

The latest ANPRM aims to conform CAS and GAAP with respect to the concepts of “operating revenue” and “lease accounting.” Most readers will understand that there has been a lot of relatively recent movement in GAAP with respect to those issues; and most readers will similarly understand that there has been zero movement in CAS for decades with respect to those issues. Thus, what was once similar has now diverged, and the CAS Board aims to bring them back together.

Maybe.

We’ll have to see.

With respect to the concept of “operating revenue,” the CAS Board—

… believes that the definition in GAAP is essentially equivalent to the CAS definition, except that the Board notes that, for purposes of management contracts under which the contractor essentially acts as an agent of the Government in the erection or operation of Government-owned facilities, the CAS definition of operating revenue includes only the fee earned for managing the contracts. GAAP provides no such limitation.

So: essentially equivalent but different with respect to GOCO and M&O contracts. The CAS Board proposed to adopt the GAAP definition but retain the exception for such contracts. “The Board solicits public comments to the proposed change to the CAS definition of operating revenue.”

The Board would also like to know “whether changes to cost accounting practices to conform Operating Revenue to ASC 606 should be considered to be a required change, a unilateral change, or desirable change.” In other words, if, by changing the CAS definition of “operating revenue,” there is a need for a corresponding change in a contractor’s cost accounting practice, how should that change be treated for purposes of determining whether there has been a cost increase in aggregate and how that cost increase (if any) should be treated. That’s kind of an important question and CAS-covered contractors should think long and hard about their answer.

With respect to the concept of “lease accounting,” the CAS Board is aware that adoption of ASC 842 means that contractors are putting more leases on their balance sheets, as well as creating a new type of asset called “right-of-use assets.” As the Board explained—

Right-of-use assets were formerly classified as operating leases. Right-of-use assets are recorded on the balance sheet by the lessee as assets and amortized on a systematic basis representative of the pattern in which the lessee expects to consume the right-of-use asset’s future economic benefits. A corresponding lease liability is also recorded by the lessee at the present value of the lease payments not yet paid. It is the recording of right-of-use assets on the balance sheet that may cause the potential confusion as to whether these “assets” are intangible capital assets or tangible capital assets for CAS purposes.

(Readers may recall that, in 2016, the ASBCA ruled that CAS 404 didn’t apply to leases (whether classified as operating or capital leases) because “by its terms” CAS 404 “applies only to ‘tangible capital assets’ and does not apply to a lease because a lease is an intangible asset.” We wrote about that decision here.)

With the wisdom of Solomon, the CAS Board found a solution to any confusion caused by right-of-use assets. It proposed to define them as being neither tangible nor intangible assets “at this time.” This is because “Before right-of-use assets are considered for inclusion on balance sheets, the Board would need to further analyze the impact of these changes [on various other Standards]. Thus, the proposed rulemaking would be to make no rules, pending further analysis.

And some readers wonder why we have issues with the CAS Board’s speed of activity….

In summary, this ANPRM, which represents one of the most significant actions taken by the CAS Board in several years, accomplishes the following:

  1. Makes minor changes that acknowledge GAAP treatment, while preserving the status quo.

  2. Asks more questions.

And … that’s about it.

Great job, CAS Board!

Now go get your rulemaking participation ribbons.

 

Cyber-Security and You

E-mail Print PDF

We don’t write much about cyber-security.

There are a couple of reasons for that.

First, everything is moving very quickly and it’s tough to hit a moving target. For the past several years, the US Government—especially DoD—has been struggling to adopt a cyber-security framework that provides assurance that contractors (and their supply chains) are reasonably secure from cyber-intrusions. There have been several iterations of that framework and we have been waiting until the framework seemed to reach a close-to-final state.

Second, there are lots and lots of articles that are already being published by law firms, consulting firms, and want-to-be CMMC audit firms. We don’t feel we have much to add to that pile of publications, so we have refrained.

Third, it’s not like we haven’t been ringing this bell for literally years. In 2019, we wrote this article about “cyber-security and subcontractors.” But our interest in this general topic goes back to 2013, when we wrote about supply chain risk, and noted that a final DFARS rule had just been published “that requires ‘defense contractors to incorporate established information security standards on their unclassified networks and to report cyber-intrusion incidents that result in the loss of unclassified controlled technical information from these networks.’” We concluded that 2013 article with a simple sentence: “You have been warned.” We were there seven years ago and we warned our readers that things were changing in this area, and that it was time to get very serious about securing the supply chain.

Thus, savvy contractors (or at least the ones that read this blog) have had seven years to prepare for this. When did your company start preparing?

Where do things stand today, seven years later?

There is the new CyberSecurity Maturity Model (CMMC), which establishes levels of maturity for contractors (and their suppliers) with respect to cyber-security practices. Oversight is provided by the CMMC Accreditation Body (CMMC-AB), The CMMC-AB determines who can be a Registered Practitioner and who can be a Provisional Assessor. In November, 2020, individuals started receiving official “badges” for those positions—and if you are a contractor in need of Certification, you can go to the “marketplace” and find somebody to evaluate you.

There is also something called a CMMC Third Party Assessment Organization (C3PAO) that hasn’t quite jelled yet. But we are quite sure that many consulting firms are ready and eager to get their C3PAO designation so that can help you in this area.

We should mention that the CMMC-AB has itself had an “evolution” over the past year, with Board Members being replaced and new operating philosophies being implemented. But insofar as we can tell, things are settling down there.

Effective 30 November 2020, a new interim DFARS rule dealing with assessments of contractor cyble-security maturity—and establishing required maturity levels in RFPs and contracts—came into effect. To help understand how to implement that new rule, John Tenaglia (the new Director of DoD’s Defense Pricing and Contracting group) issued a helpful guidance memo.

Without rehashing the entire memo, here are some bits we found interesting. Rather than relying on our excerpts, we suggest you go read the memo. But knowing our readers, most will not do so. For them:

  • On or after November 30, 2020, the contracting officer shall, prior to awarding a contract, task order, or delivery order to, or exercising an option period or period of performance with, an offeror or contractor that is required to implement NIST SP 800-171 in accordance with the clause at DFARS 252.204-7012, verify that the summary level score of a current NIST SP 800-171 DoD Assessment (i.e., not more than 3 years old, unless a lesser time is specified in the solicitation) is posted in Supplier Performance Risk System (SPRS) for each covered contractor information system that is relevant to an offer, contract, task order, or delivery order.

  • On or after November 30, 2020, when a requiring activity identifies a requirement for a contract, task order, or delivery order to include a specific CMMC level, the contracting officer shall not award to an offeror that does not have a CMMC certificate at the level required by the solicitation, or exercise an option or extend any period of performance on a contract, task order, or delivery order unless the contractor has a CMMC certificate at the level required by the contract Contracting officers shall use Supplier Performance Risk System (SPRS) to verify an offeror or contractor’s CMMC level.

  • On or after November 30, 2020, use the new provision at DFARS 252.204-7019 in all solicitations, including solicitations using FAR part 12 procedures for the acquisition of commercial items, except for solicitations solely for the acquisition of COTS items.

  • On or after November 30, 2020, use the new clause at DFARS 252.204-7020 in all solicitations and contracts, task orders, or delivery orders, including those using FAR part 12 procedures for the acquisition of commercial items, except for those that are solely for the acquisition of COTS items. This clause is required to be flowed down to subcontracts and other contractual instruments, including subcontracts for the acquisition of commercial items (excluding COTS items)

  • November 30, 2020, through September 30, 2025, use the new clause at DFARS 252.204-7021in solicitations and contracts or task orders or delivery orders, including those using FAR part 12procedures for the acquisition of commercial items, except for solicitations and contracts or orders solely for the acquisition of COTS items, if the requirement document or statement of work, as determined by the requiring activity and approved by OUSD(A&S), requires a contractor to have a specific CMMC level.

  • On or after October 01, 2025, CMMC requirements will apply to all solicitations and contracts or task orders or delivery orders, except for solicitations and contracts or orders solely for the acquisition of commercially available off-the-shelf (COTS) items. On or after October 1, 2025, use the clause at DFARS 252.204-7021 in all solicitations and contracts or task orders or delivery orders, including those using FAR part 12 procedures for the acquisition of commercial items, except for solicitations and contracts or orders solely for the acquisition of COTS items. This clause is required to be flowed down to all subcontracts and other contractual instruments, including subcontracts for the acquisition of commercial items, excluding COTS items.

  • The CMMC level to be required for subcontractors is the level that is appropriate for the information that is being flowed down to the subcontractor.

To conclude this article, DoD is now making your cyber-security practices—and those of your supply chain—a matter of responsibility for new competitions. If you don’t have what it takes, then don’t bother to submit a proposal. Further, if you do win a new contract award, be prepared to make cyber-security a matter of on-going contract compliance.

We told you this was coming seven years ago. Don’t say you weren’t warned.

 

Another GSA Contractor Settles Legal Problems

E-mail Print PDF

I do not know the company Cognosante LLC. It could be a great company, a top-notch government contractor. I don’t know. I visited the company website and I don’t feel as if I learned much more than I knew before I visited it.

The company’s mission statement includes the following: “We are a mission-driven technology company that delivers innovative and transformative solutions to government. Our missions inform our market focus, business strategy, investments, and culture.” Does that seem as vague to you as it does to me?

Cognosante is apparently in the healthcare space—which is a pretty good place to be these days. I know this because there is a fair bit about healthcare on the website. For example, on the website Cognosante talks about expanding access to healthcare for “200 million Americans with innovative technologies and expert support.” Cognosante also discusses “improving clinical performance with technology, systems integration and citizen engagement services.” In addition, the website discusses “health equity,” and states that the company is involved in “delivering solutions that address and positively impact the social determinants of health and wellness.” That’s all great stuff and I’m sure the company is thriving.

I’m just not sure what any of that means, in practical business terms.

From the website, I also learned that Cognosante has multiple ISO Certifications as well as a HITRUST Certification for “Data Security and Minimized Risk.” In addition, Cognosante has had a CMMI Level 3 Certification since 2019—which is interesting but it is not the same thing as a CMMC Level 3 Certification. It’s cool that the company has invested time and energy into making sure its Quality and other management processes comply with important standards.

But what’s missing is any hint that the company is focused on other aspects of compliance, such as complying with contract terms and conditions. Cognosante has many government contract vehicles, including Alliant 2 and OASIS GWACS, as well as GSA Schedules and a Seaport ID/IQ and several individual state contracts. But you wouldn’t really know that from the company’s website (well, except the part where they list those contract vehicles).

There are open positions and, if you’re in Contracts, they have openings for you. But if you are into cost accounting, CAS/FAR compliance, or related disciplines, then not so much. For example, there’s an opening for a Project Financial Analyst, and that opening states that required qualifications include “5 or more years of experience in a government contracting environment. Working knowledge of indirect rate structures, a plus.” Preferred (but not required) qualifications include “Understanding of various contract types, e.g., cost plus fixed fee, award fee, fixed price contracts, and Government Wide Agency Contracts; Knowledge of monitoring compliance with general contract terms and conditions for government contracts and supporting multiple clients in a fast-paced environment Experience with financial modeling, including revenue projections; Experience with project or program management, including Federal Acquisition Regulation (FAR) and Joint Travel Regulation (JTR) requirements; Experience with accounting standards, such as General Accepted Accounting Principles (GAAP) and Sarbanes-Oxley (SOX).” (Emphasis added.1)

But you’ll notice that there is not much actual expertise being required. It would be nice if the successful candidate had “experience” with the FAR and the JTR, but it’s not actually required. And generally, those two areas of expertise are not found within the “project or program management” disciplines. In a similar vein, it would be nice if the successful candidate had “experience” with GAAP and SOX, but it’s not really something the company is super concerned about. In fact, you can be the successful candidate and know nothing about those areas, so long as you have five or more years of experience in a government contracting environment (working knowledge of indirect rate structures, a plus2). I know many members of aerospace/defense company janitorial staff who have more than five years of experience in a government contracting environment. Presumably, they are just as qualified as anybody for the company’s job opening.

But it doesn’t just end there. Looking at Cognosante’s website again, there is a page devoted to the Leadership Team. The CFO has an impressive pedigree, including a Masters in Engineering and having served the company as both VP of Finance and the company’s Chief Contracting Officer. The Chief Administrative Officer (who oversees both HR and Quality) is similarly impressive. But what I don’t see is any MBA or CPA types in a leadership role. The closest thing I see is that the CEO has a master’s degree in public and private management from Yale School of Management—which is impressive, no doubt. But it’s not an MBA or a CPA. (Note for accuracy: I didn’t check every leadership bio, but I did check the ones I thought would have or should have a compliance role.)

The key role that’s missing on the Leadership Team page is a Chief Compliance Officer. You might argue that should be the role of the General Counsel. You’d be wrong to argue that, but it’s certainly not unheard-of. Yet there is nothing in the General Counsel’s job description that says he is focused on anything other than the law department. There’s no Chief Compliance Officer listed, just as there is no Chief Internal Auditor listed; and there is very little (if anything) that hints that compliance is taken seriously by the Cognosante Leadership Team.

Neither the bios and job descriptions for the Chief Administrative Officer (who is responsible for the Quality function) nor the Chief Financial Officer (who is responsible for financial reporting, billing accuracy, and other compliance matters) have any indication that compliance is something they care about, are focused on, or are responsible for.

The Cognosante website also has an aggregation of recent press releases and other news in which the company is mentioned. There’s something missing there, as well.

What’s missing is this Department of Justice press release announcing that Cognosante LLC “agreed to pay the United States $18,987,789 to resolve allegations that it violated the False Claims Act by using unqualified labor and overcharging the United States for services provided to government agencies under two General Services Administration (GSA) contracts.”

The settlement resolves allegations that Cognosante overcharged the United States for services performed under two GSA MAS contracts, including by providing false information concerning Cognosante’s commercial discounting practices during contract negotiations. It also resolves allegations that Cognosante charged the United States for labor that failed to meet the qualifications in one of the contracts.

In fairness, the press release notes that it was Cognosante, itself, that identified the issues and disclosed them to the US Government. The company “received credit for its disclosure and cooperation.” So apparently there is some type of internal audit/internal compliance function in operation, even if the company’s website ignores it.

But remember, the $19 million settlement was after Cognosante received credit for disclosure and cooperation. That sum is indicative of a fairly large billing problem; and it is likely that the problem went unnoticed for some time before being discovered and disclosed.

Look, I don’t know Cognosante. It could be a great company, a top-notch government contractor. I don’t know.

But I do see correlation between the gaps in the company’s leadership team and the necessity to pay the government $19 million to settle allegations of noncompliance with contract terms and conditions.

Perhaps that will change, now that the company has been burned. Perhaps if I revisit the company’s website in a few months, I’ll see a newfound focus on compliance. Perhaps there will be a Chief Compliance Officer and/or a Chief Internal Auditor.

I hope so.


1 Editorial note: Please explain what “general contract terms and conditions” means in a government contracting environment. Which terms and conditions are general, and which are specific? Show your work.

2 It’s not clear whether “working knowledge of indirect rate structures” means knowledge of how to design them, understanding of the rules of cost pooling and cost allocation, or simply how to take rates one is given and apply them to program budgets.

 


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