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

The Map is Not the Territory

E-mail Print PDF

I’m working on this theory about compliance. I’m not saying it’s fully baked yet, but I thought I’d share some thoughts. Your feedback is welcome.

First, the title of this article. It comes from “General Semantics”—an early-to-mid-century philosophical movement. Although General Semantics aimed at changing human thoughts and behaviors, what interests me about it was how it later impacted research into human perceptions and communication. The Institute of General Semantics continues to probe these areas. Although I’m in no way any kind of expert in the area, my layperson’s understanding is that a foundational precept was the notion of abstraction. The title is based on a General Semantics axiom that the description of a thing is not the thing itself. You can describe an object or a feeling, but that description is limited by your language and my internal language (how I process what you are describing). Neither of us is actually sensing the true object (or feeling). Another General Semantics saying is “the word is not the thing.” You get the idea.

Anybody who has ever relied solely on GPS directions and, as a result, has made a wrong turn or gotten lost, understands this concept. The GPS model on which the directions are based may not, in fact, be an accurate representation of the environment in which you are driving.

How does this all relate to compliance?

It seems to me that a compliance plan is like a map. It is the abstraction of compliance. It is not compliance. It’s useful—as maps are useful—as a guide or limited description; but it is subject to limitations (like our GPS directions) and thus should not be relied upon as being the entire compliance universe.

Compliance is the thing. Compliance is people—individual people—complying with rules and guidelines. Those people are making decisions in the moment. Those decisions lead to actions that are (or are not) compliant with the rules and guidance the organization has determined it wants to follow.

Right away it becomes apparent that there are abstract rules and regulations and laws. The “organization” (another abstraction) reviews those abstract things and decides, based on the review, what behaviors and actions constitute “compliance.” The first step (and the most abstract step) is having knowledgeable people within the organization review the various rules, regulations, and laws in order to determine which ones are applicable to the organization and then what compliant behavior and actions look like. The result of this review is a set of parameters that guide individual behavior.

Another complication is that the laws, regulations, and rules change—so the review must be performed fairly frequently.

The review output is a set of parameters. Individual actions and behaviors that fall within the parameters are “compliant;” whereas those that fall outside the parameters are non-compliant and require correction.

The next step is to translate the parameters into written guidance. Policies, procedures, practices. Command media, each piece of which has a topic and an associated behavioral parameter. This is compliant behavior, this is not compliant behavior. The documents are another abstraction. Somebody has to decide what to communicate and how to communicate. The end goal is to effectively communicate in such a way that an individual faced with a decision—a choice—can use the document as an aid. The better the document, the more likely the individual will be to make a decision that leads to behavior within the desired parameters—compliant behavior and compliant actions.

When complete, the command media must be explained. Individuals must be trained. People need to understand (1) where to find the guidance, and (2) where to find within the guidance the decision aid they are seeking. Many times, organizations opt to create Computer Based Training (CBT) for such interaction; but note that the creation of CBT itself involves choices and decisions about what content to teach and want content not to teach. Even if the training is instructor-led, the communication is almost wholly dependent on the instructor’s competence—not only in the subject matter but also in effectively communicating the subject matter. Finally, regardless of the training modality, the student’s mindset is critical. Students on the phone listening (on mute) to a conference call while simultaneously watching a CBT are likely not paying sufficient attention to either task. (As we’ve asserted before, multi-tasking is a detrimental myth.) Accordingly, effective communication is not being achieved, regardless of the effort put into the training by those who created the CBT or the instructor.

At this point, to create a decision that leads to compliant behavior or action, we have had to navigate multiple levels of abstraction. Each level has required choices, and those choices have reduced the full and complete “reality” of the thing. We don’t use the full text of an applicable statute; we abstract it and summarize. We don’t publish the full summary; we piece it into parts and create documents that explain it and apply it to organizational functions and activities. That step involves many choices. Finally, we train individuals; but we don’t train them in the entire command media document(s); we pick and choose the parts we think are important for the individuals to know.

It’s conventional wisdom that when you have communicated expectations to employees and trained them in those expectations, you are now positioned to enforce discipline. You may in fairness reward compliant behavior and penalize noncompliant behavior. But in order to get here you have had to make so many abstractions, so many choices, so many compromises! Can you truly be said to have effectively communicated both the parameter and the consequences?

I’m not sure you have. But the conundrum is that communicating the actual thing--the compliance driver--is literally impossible. The map is not the territory. If you made a map that was 100 percent in fidelity with the territory, then you would be recreating the territory. You would have a map that had a 1:1 scale: one mile would equal one mile. It would be accurate; but it would also be unusable. If you drafted a a policy or procedure that was 100 percent the law or regulation or rule itself, then you would be simply recreating the statute or regulation or rule, instead of creating a useful aid for individual decision-making.

Some thoughts for you to consider as you create your compliance plans.

 

Generating Profits Through Foreign Military Sales

E-mail Print PDF
Historically defense contractors have had two primary customers for their goods and services: the U.S. Department of Defense and the rest of the world. As U.S. defense budgets wax and wane (which is dependent on various factors including the global security situation, Congressional mood, and Presidential intent), contractors either focus on their domestic customer or else look for international sales channels. (Many do both!) For example, take a look at this Raytheon “global presence” webpage. In recent years, nearly one-third of Raytheon’s revenue has been from international sales.

Contractors have two avenues for international sales of defense products. They can contract directly with the buying government (commonly called “direct commercial sales” or DCS) or they can use the U.S. DoD as an intermediary (commonly called “Foreign Military Sales” or FMS). Choosing one avenue over the other is not an easy decision; there are pros and cons with both approaches. Often, the decision is made for the contractor. For example, if a foreign government wants U.S. financial assistance with paying for the weapons it wants, the U.S. Government may insist that FMS be used. (See our article on security assistance here. Further, we have uploaded a 2013 DoD presentation on the topic, intended for DCMA contracting officers, on this site’s knowledge resources page.) Even when the choice is available, the decision can be a tough one to make.

As the Government Accountability Office (GAO) recently wrote: “According to DOD and State officials, FMS provides multiple benefits to foreign governments and the U.S. government. Foreign governments that choose to use FMS rather than direct commercial sales receive greater assurances of a reliable product, benefit from DOD’s economies of scale, improve interoperability with the U.S. military, and build a stronger relationship with the U.S. government … although using FMS is generally not the quickest or least expensive option for foreign governments.”

We want to unpack that last point a bit. Why should FMS transactions be any more expensive than DCS transactions?

One answer to that question is that the Defense Security Cooperation Agency (DSCA)—the DoD component that administers FMS transactions---charges governments a transaction fee for their services. As GAO recently noted, “DSCA charges purchasers certain overhead fees to cover the U.S. government’s costs for operating the FMS program. These fees include the administrative fee, which covers costs such as civilian employee salaries, facilities, and information systems, and the contract administration services (CAS) fee, which covers the costs of quality assurance and inspection, contract management, and contract audits. These fees are collected in separate accounts in the FMS trust fund, which is used for payments received from purchasers and disbursements made to implement FMS.”

In other words, foreign governments that directly contract with U.S. defense contractors are responsible for administrating and managing their contracts; whereas governments that contract through DSCA via the FMS program have those services provided by DoD entities—for a price. That price covers the listed services, and within those listed services one finds contract administration and quality assurance (DCMA) and contract audit (DCAA). Presumably, CAS provides assurance that the foreign customers are getting what they are paying for, and that the price they are paying is considered to be fair and reasonable. GAO reported that “The base CAS fee has three subcomponents, which are currently set at (1) 0.5 percent for quality assurance and inspection, (2) 0.5 percent for contract management, and (3) 0.2 percent for contract audits.”

The U.S. government intends that its FMS administration fee—currently 3.5% of the FMS agreement (or case) value—is a break-even fee. It is not intending to profit from the fee. In fact, GAO reports that the Standard FMS Terms and Conditions “indicates that the U.S. government will not profit from the FMS program.”

The problem is that the U.S. Government is profiting to the tune of billions of dollars.

GAO report GAO-18-401, published May 10, 2018, told Congress and the public that “The FMS administrative account balance grew by over 950 percent from fiscal years 2007 to 2017—from $391 million to $4.1 billion—due in part to insufficient management controls, including the lack of timely rate reviews.” (Emphasis added.) Further, GAO reported that “The FMS CAS account grew from fiscal years 2007 to 2015 from $69 million to $981 million, due in part to insufficient management controls …”

So when DSCA and other DoD officials blithely note that FMS transactions are neither the quickest nor the least expensive option for foreign customers, what they are really saying is that FMS sales do not represent good value for money. FMS transactions take longer than they should and they cost more than they should. FMS transactions do not represent the optimum sales channel, nor do they lead to fair and reasonable prices. It’s not the contractors’ fault: it’s the DoD’s fault. When using the FMS program, DoD expects its foreign partners to pay for the privilege of slowing down weapon system delivery. And DoD is profiting from the situation.

DSCA describes this situation as “building a stronger relationship with the U.S. Government.”

How much profit is DoD making on these transactions? GAO reported “Our analysis indicates that even if the administrative fee rate were reduced to as low as 2.9 percent and administrative expenditures were to increase 15 percent above expected growth, the administrative account balance would likely remain sufficient to pay for projected expenditures while maintaining a reserve balance through at least fiscal year 2024.”

GAO says the excess balance (profit) generated by the excessively high administrative fees could be used to pay for additional expenditures. Sure. That is certainly one possibility.

Or perhaps the U.S. Government could build stronger relationships with its international partners by refunding the excess costs—costs that it was prohibited by contract terms and conditions from collecting—back to the entities that overpaid in the first place.

You think that might generate some goodwill? We certainly do.

Meanwhile, DSCA and DoD continue to charge international customers the excessively high transaction fees that add costs while admittedly slowing down the entire process.

 

TINA Threshold Can Be Raised Across All Agencies

E-mail Print PDF
The story continues.

It started with the 2018 National Defense Authorization Act (NDAA), a piece of legislation focused on the Department of Defense and NASA. The 2018 NDAA directed DoD (and NASA) to make a number of changes to the acquisition regulations. We told you about many of those changes. Notably, the 2018 NDAA changed the threshold at which contracting officers (and contractors) must obtain certified cost or pricing data—commonly known as “the TINA threshold” (referring to the Truth-in-Negotiations Act). The 2018 NDAA raised the TINA threshold from $750,000 to $2 million.

Again, the NDAA language was focused on DoD and NASA, but that focus created a problem. The problem is that the TINA language—e.g., FAR 15.403-4(a)(1)—applies to all Federal agencies, not just to DoD and NASA. Essentially, then, Congress was telling the DAR Council (one of the two FAR Councils who writes the acquisition regulations) to make special language in the Defense Federal Acquisition Regulation Supplement (DFARS). That would be an enormous undertaking, since the DAR Council would not only have to create regulatory language that paralleled the existing FAR language, but would also have to create new solicitation provisions and contract clauses that paralleled existing FAR provisions and clauses. That would be hard and take a long time, a duration perhaps measured in years. In the meantime, DCMA contracting officers would be stuck, forced to choose between complying with statute and complying with the existing FAR regulatory language. We wrote about that challenge in this article.

We followed-up that article with another one, one that discussed how the Civilian Agency Acquisition Council (CAAC)—the sister entity to the DAR Council—had issued a Class Deviation that authorized civilian agencies to adopt some of the 2018 NDAA acquisition thresholds. This was a significant step because it was a strong indication that the 2018 NDAA changes were going to be adopted across the entire FAR, and not just adopted within the DFARS. However, we noted that the CAAC Class Deviation was silent with respect to the TINA threshold. We speculated that it might be the subject of a future CAAC communication.

In yet another article on the topic, we discussed in some detail the quandary faced by both DCMA contracting officers and contractors, because the existing FAR language and associated solicitation provisions and contract clauses all referenced a specific dollar value ($750,000) as the TINA threshold, rather than the value in the statute. Thus, if the statute changed but the regulatory language did not, then there was going to be a conflict between the two. Further, the CAS threshold (which is the contract value at which CAS is applied, unless an exemption is available) is tied to the TINA statute rather than to the regulation. That created yet another compliance quandary for people. We wrote—

By ‘slow-rolling’ the implementation of the 2018 NDAA threshold changes into the acquisition regulations, the FAR Councils have created a problem for contractors. If the contractors wait for the regulatory implementation, then they must disconnect CAS coverage from TINA coverage. They will end up requesting certified cost or pricing data from subcontractors that are, by statute, exempt from CAS. This helps nobody and may well lead to increased procurement costs.

In our view, the only rational approach is to apply the statutory threshold changes now. The FAR Councils should immediately issue a Class Deviation to FAR 15.403-4(a)(1) to implement the new TINA threshold, even if formal rule-making takes a bit longer. If you are a contractor, you should discuss this quandary with your cognizant contracting officer and try to get some relief.

Then, in two other (brief) articles, we noted that the DoD had issued Class Deviations to implement the 2018 NDAA acquisition threshold changes in advance of formal rulemaking. (See here.)

Just to recap, by this point the CAAC had issued a Class Deviation to permit civilian agencies to implement some of the 2018 NDAA threshold changes—in particular, those associated with the Simplified Acquisition Threshold (SAT) and the Micro-Purchase threshold—but they had not addressed changes to the TINA threshold. The Department of Energy (DOE) had jumped on that permission and had issued its own Class Deviation. But of course DOE could not address the TINA threshold, because the CAAC had not addressed it in its Class Deviation. The DoD had issued two Class Deviations addressing the SAT, the Micro-Purchase threshold, and the TINA threshold.

Now we are all up to date.

And you should not be surprised to learn that on May 3, 2018, the CAAC issued a Class Deviation via CAAC Letter 18-003, that addressed the TINA threshold. The CAAC Class Deviation authorizes civilian agencies to “raise[ ] the threshold for requiring Certified Cost or Pricing Data from $750,000 to $2,000,000.” So there you go.

Importantly, the CAAC Letter also addressed how the threshold increase is to be implemented on existing contracts. The CAAC Letter stated “contracts entered into on or before June 30, 2018 are excluded from this threshold increase.” That sounds like another problem, doesn’t it? Contractors are supposed to have one Purchasing System, with a single set of requirements and thresholds, and not two separate ones (one for old contracts and another for new contracts).

Fortunately, the CAAC Letter also offered a way out of the problem. It stated “contractors for those [old] contracts can request to modify such contracts, without consideration, to use the new threshold.” Note the key phrase – “without consideration.”

At this point, contractors should be moving briskly to revise their Purchasing/Subcontracting procedures to implement the new 2018 NDAA thresholds. They should also be preparing letters to their procuring contracting officers to have their existing contracts modified to adopt the new acquisition thresholds. Contractors with DoD and/or NASA contracts should have already sent those requests, and contractors with civilian agency contracts should be looking to do the same.

 

Long-Term Travel

E-mail Print PDF
We’ve noticed that, for a while now, the Department of Energy (DOE) has been moving forward on clarifying and streamlining existing acquisition rules and regulations. Good for them! We believe that DoD might learn a thing or two from following the lead of DOE.

Thus, we were interested to see DOE issue Acquisition Letter 2018-08 on May 3, 2018. The Acquisition Letter addresses a topic in which we have long been interested – “long-term travel” (or, as DOE terms it “domestic extended personnel assignments").

Most contractors’ travel policies address the costs of normal business travel, which is sometimes called “TDY travel.” The policies tell employees what costs will be reimbursable and at what amounts. The policies are (usually) aligned somewhat with the FAR cost principle at 31.205-46. Most contractors understand that there are also government travel rules, which apply to government travelers—and some (but not all!) of those government travel rules are incorporated into the FAR travel cost principle. As the DOE Acquisition Letter explains, “the travel cost principle does not incorporate the entirety of the FTR, JTR or SR. Absent specific contract language to the contrary, only the maximum per diem rates, the definitions of lodging, meals, and incidental expenses, and the regulatory coverage dealing with special or unusual situations are incorporated.”

Even though most contractors understand the interplay between the FAR travel cost principle, the Federal Travel Regulations, the Joint Travel Regulations, and the Standardized Regulations, many of those same contractors have not extended their travel policies to address long-term travel. Long-term travel is the situation where an employee is assigned to a single location for an extended period of time. The employee’s permanent work location has not changed, but they are going to be somewhere else for 60 or 90 days, or perhaps as much as a year. (You don’t want to go over a year in duration unless you want to deal with some complicated tax issues.)

When an employee is on long-term travel (or, as DOE calls it “a domestic extended personnel assignment”), it’s not reasonable to have them keep incurring the same amounts of travel costs they would incur on normal business travel. For example, if they are going to be at a single location for six months, why can’t they lease an apartment, or (at least) start renting their hotel room by the month instead of by the day? Why can’t they buy food and cook it in their own kitchen, instead of going out to eat three meals a day?

In other words, reasonable people would expect the employee’s daily travel costs to drop significantly while on long-term travel. Lodging costs should drop. The Meals & Incidentals allowance should drop. Too many contractors’ travel policies don’t take this into account.

The DOE Acquisition Letter addresses this issue and establishes DOE policy on cost allowability associated with long-term assignments. The AL starts with a clear, concise definition: “Contractor domestic extended personnel assignments are defined as any assignment of contractor personnel to a domestic location different than (and more than 50 miles from) their normal duty station for a period expected to exceed 30 consecutive calendar days.” In other words, you can be on TDY travel for the first 30 days, but on day 31 the employee’s travel costs are supposed to come down. That sounds very reasonable to us.

The DOE AL lists a number of allowability rules. We won’t recap them all here (we provided a link to the AL in the 2nd paragraph). Here are some significant policy positions:

  • For the first 60 days and last 30 days of the assignment, DOE/NNSA will reimburse costs associated with lodging at the lesser of actual cost or 100% of the Federal per diem rate at the assignment location. The intervening days will be reimbursed at the lesser of actual cost or 55% of Federal per diem.

  • For the first 30 days and last 30 days of the assignment, DOE/NNSA will reimburse costs associated with meals and incidental expenses (M&IE) at a rate not to exceed 100% of the Federal per diem rate at the assignment location. The intervening days will be reimbursed at a reduced rate, not to exceed 55% of Federal per diem.

Contractors whose travel policies do not currently address long-term travel would do well to review this DOE Acquisition Letter in some detail and consider adopting the DOE cost allowability standards as the company’s reimbursement policy positions when their employees are on an extended assignment that does not involve a permanent change in work location. In particular, we advise paying attention to the portion of the AL that discusses the cost analysis that should be performed when considering putting an employee into a long-term travel situation. The AL recommends that a full-up relocation be considered and costed. If the relocation is less expensive than the costs of the extended assignment, it would seem reasonable and prudent to relocate the employee—and that’s what the DOE AL suggests.

In other words, there is more to this particular topic than simply complying with applicable regulations. There is a certain level of analysis expected. We agree. And we recommend that contractors structure their travel policies accordingly.

 

Defective Pricing: So This Happened

E-mail Print PDF
On May 4, 2018 the Defense Federal Regulation Supplement (DFARS) was revised via issuance of a final rule “to state that, in the interest of promoting voluntary contractor disclosures of defective pricing identified by the contractor after contract award, DoD contracting officers have discretion to request a limited-scope or full-scope audit, as appropriate for the circumstances.”

According to the background section of the final rule, this regulatory revision came about because contractors requested it. Contractors requested it because DoD asked about opportunities to reduce or eliminate regulatory burdens “where costs [of compliance\ outweigh benefits [to the government.” DoD asked contractors for input as part of “Better Buying Power 3.0,” which we discussed here. We offered opinions regarding BBP 3.0 in this article. In our typically understated, diplomatic style, we concluded that “BBP 3.0 is much the same as its predecessors: More bureaucratic management and more bureaucratic processes. Processes designed and implemented by bureaucrats for bureaucrats in order to achieve bureaucratic ends.”

But this article isn’t about BBP 3.0. Nor is it about BBP 2.0 (which is where the notion of regulatory roll-backs started). Nope. This article is about the regulatory revision that allegedly spawned from BBP 3.0, a claimed regulatory roll-back intended to reduce a burden on contractors so that the associated reduced costs could be passed back to taxpayers.

Yeah, that’s a lie.

We documented the true story on this blog site.

As we documented, after five years of intensive study, after five years of focusing on reducing regulatory burdens where the costs to contractors outweighed the benefits to the government, after admittedly spending $600,000 of taxpayer funds, the DoD issued this report entitled “Eliminating Requirements Imposed on Industry Where Costs Exceed Benefits.” (Catchy title, right?) We documented how almost every single input received from contractors was dismissed by the study’s authors. We documented how the authors promised to continue to study regulatory roll-back in “Phase II,” and we opined that we would expect much of the same, in terms of results. I.e., nothing.

One of the few contractor recommendations that was accepted by the authors was to reduce the number of certified cost or pricing (CoP) data submissions. We discussed that recommendation, in some detail, in this article. We quoted from the DoD report and we repeat that same quote here so that readers can see the exact language of the recommended regulatory roll-back:

We concur with contractors’ recommendation in the first category: DoD should clarify policy guidance to reduce repeated submissions of CoP data. Multiple submissions are an unintended, and generally unsought, consequence of the FAR requirement that certified CoP data be ‘current.’ Frequent resubmissions appear to be the result of contractors’ fears that out of date CoP data that becomes inaccurate will lead to defective pricing claims by DoD post-award. However, lack of clarity on what is considered ‘current’ motivates some contractors to provide excessively frequent CoP data updates during negotiations (weekly or monthly), which creates unnecessary work not only for contractors, but also for the Procuring Contracting Officer (PCO). We recommend amending DFARS (and/or the FAR) to remove uncertainty about the appropriate frequency of providing certifiable CoP data to ensure it remains ‘current’ and/or to clarify pricing changes that warrant resubmission of CoP data. … Reducing unnecessary resubmissions of certifiable CoP data would lower contractor proposal costs and reduce procurement administrative lead time. Making this change also weakens the argument for making additional changes to the TINA statute, such as increasing thresholds or relaxing waiver criteria.

(Emphasis added to show exactly what the authors were recommending.)

So then this happened.

As we documented in the article (link above), the report’s recommendation was changed. The recommendation provided to the Director of Defense Pricing became ““Consider revising the FAR to eliminate the requirement that a defective pricing claim and associated audit must be initiated if a contractor voluntarily discloses defective pricing post-award …”

You see the disconnect, don’t you?

Further (and as we documented), even though the recommendation was to revise FAR 15.407-1(c), the Director of Defense Pricing initiated a DFARS Case (215-D030) that would only revise DFARS 215.407-1. Because the FAR was not being revised (as recommended), there would be no associated cost reductions with the regulatory revision.

So here we are today, more than two years after the DFARS Case was opened, with a final rule that does nothing. It reduces no regulatory burden and it reduces no contractor costs. What it does do is clarify the rights of the parties.

  • “Voluntary disclosure of defective pricing is not a voluntary refund as defined in 242.7100 and does not waive the Government entitlement to the recovery of any overpayment plus interest on the overpayments in accordance with FAR 15.407-1(b)(7).”

  • “Voluntary disclosure of defective pricing does not waive the Government's rights to pursue defective pricing claims on the affected contract or any other Government contract.”

Thus, if you determine that you may have defectively priced your cost proposal, in that you failed to disclose accurate, complete, and current certified cost or pricing information (as that term is defined at FAR 2.101), then you may make a voluntary disclosure to your contracting officer. Who will discuss the situation with DCAA. The contracting officer and DCAA will determine how best to proceed in evaluating the contractor disclosure. Regardless of the voluntary nature of the contractor’s disclosure, that disclosure may lead to further demands for repayment, as the solicitation provisions and contract clauses provide. In some extreme cases, the government (or qui tam relator) may pursue a lawsuit under the civil False Claims Act, based on the theory that any invoice submitted under a defectively priced contract is a false claim.

The only silver lining in this situation is that Congress recently raised the threshold at which contractors must certify their cost or pricing data from $750,000 to $2 million. DoD recently issued a Class Deviation to implement that statutory change ahead of formal rule-making. Consequently, the number of proposals subject to this rule—especially at smaller contractors—should decrease significantly.

Otherwise, this story is the poster child for how the DoD “fourth estate” sabotages attempts to improve the defense acquisition environment. As we have documented here for our readership to consider.

 


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