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

The Christian Doctrine

E-mail Print PDF

The Christian Doctrine has little to do with Christianity and much to do with lawyers, judges, and government contracting. You’ll need to be careful with your internet search terms, lest you wind up with very unexpected results! Here’s a link to a Wikipedia entry to get you started.

The Doctrine started with the case of G.L. Christian and Associates v. U.S. in 1963. The litigation originated when the Army terminated Christian’s contract, and attempted to apply the rules associated with then-standard Termination for Convenience clause to the termination settlement. For its part, Christian argued that the Army couldn’t take that approach because it had failed to include the T4C clause in Christian’s contract. The Army prevailed, with the court ruling that the contract should be read to include the T4C clause because it should have been part of the contract if the drafters had followed applicable regulations.

Though the concept has evolved over time, the Christian Doctrine basically states that a government contract will be interpreted to include certain clauses, even if those clauses have been (intentionally or unintentionally) omitted. As of 1993, the Doctrine was held to apply only to “mandatory contract clauses which express a significant or deeply-ingrained strand of public procurement policy,” and not to every clause.

The trick is to know which clauses will be read into your contract, and which ones will not. Courts have not always been consistent in their application of the Christian Doctrine to disputes between the Federal government and its contractors. Some cases have been decided via strict adherence to the Christian Doctrine and others apparently have been decided in spite of the Christian Doctrine. At this point, it’s difficult to assert with any degree of certainty whether any given FAR contract clause will be found to be read into a contract when it’s missing.

We want to discuss two recent cases involving the Christian Doctrine. One comes from the Armed Services Board of Contract Appeals (ASBCA) and the other from the U.S. Court of Federal Claims (CoFC).

Let’s start with the ASBCA case: Space Gateway Support LLC v. United States. The first thing you’ll notice, should you click the link, is that the decision is massive—weighing-in at more than 230 pages. “It must be a very complicated case,” you may well think … before you notice that almost all of the decision has very little to do with the actual case at hand. Instead, Judge Hartman provided a very detailed history lesson, with the apparent intention of supporting his finding that SGS was not entitled to profit or fee on its acquisition of equipment in its cost-reimbursement J-BOSC (“Joint Base Operations Support Services”) contract at Cape Canaveral Spaceport. Judge Hartman found that, though the contractor had been directed to acquire the equipment for the benefit of the government (and title in the equipment passed to the government), it should not be entitled to any fee/profit on the costs of the equipment.

SGS argued that it should be permitted a profit on items it acquired on behalf of the Government, because (a) the contract was not a facilities contract (which would have prohibited a profit), and (b) “it lacked notice it was being furnished ‘facilities’ by NASA because the CO did not include in its contract (which was ‘other than a facilities contract') unspecified portions of standard clauses for facilities contracts and therefore its contract should not include a prohibition against profit or fee on facilities acquired in order to conform with its belief it was not receiving ‘facilities.’”

After some 200-plus pages of the history of government contracts, Judge Hartman concluded that—

… even if we did not hold FAR 45.302-3 to be controlling on NASA's COs and the J-BOSC, we would conclude it applied to SGS's contract here because it presents a significant or deeply ingrained strand of public procurement policy. As we discussed above, we believe that well-established contract law doctrines permit us to conclude a party, such as SGS, who willingly, and without protest, enters into a government contract with imputed knowledge of the government's interpretation--as prohibiting the payment of profit or fee on cost of facilities acquired for the account of the government and use by the contractor--is bound by such interpretation and cannot subsequently claim that it thought something else was meant. … Alternatively, however, we conclude that the prohibition on profit or fee set forth in FAR 45.302-3(c) is incorporated in SGS's contract by the Christian doctrine set forth by the Court of Claims nearly 50 years ago. We recognize the so-called Christian doctrine is not tied to the intent of the contracting parties, is not invoked frequently by tribunals … and is thought by some to provide less certainty than standard contract doctrines because what comprises a ‘significant or deeply ingrained strand of public procurement policy’ may not be readily predictable. … We rely upon the doctrine here as an alternative ruling because the doctrine remains binding precedent … and this is one of those rare instances of a significant procurement policy spanning 95 years of our nation's history.

 

[Emphasis added.]

In a most unusual step, the two concurring Judges issued a separate opinion. It was once sentence long. In fact, the concurring opinion consisted of just four words. Perhaps the two Judges felt Judge Hartman had written more than sufficient verbiage in his opinion?

Looking at the next case, we turn to the matter of Bay County, Florida v. United States. This opinion by Judge Lettow at the CoFC was 11 pages long. Forget the facts of the case; here’s what Judge Lettow ruled—

The government argues that Bay County waived its potential status as an independent regulatory body by [inclusion of] FAR § 54.241-8 in the Sewage Contract — ignoring the limitation of Subsection (a) on application, viz., “[t]his clause applies to the extent that services furnished hereunder are not subject to regulation by a regulatory body.” … the government contends that the only way to give meaning to the Sewage Contract is to treat Bay County as a non-independent regulatory body. …

When a contract subject to the FAR incorporates improper terms of the FAR, the correct provisions of the FAR control. … ‘Under the so called Christian doctrine, a mandatory contract clause that expresses a significant or deeply ingrained strand of procurement policy is considered to be included in a contract by operation of law.’ … In S.J. Amoroso, as here, an improper clause was substituted for a proper clause. … As S.J. Amoroso held, ‘[a]pplication of the Christian doctrine turns not on whether the clause was intentionally or inadvertently omitted, but on whether procurement policies are being ‘avoided or evaded (deliberately or negligently) by lesser officials.’’ … (citing G.L. Christian & Assocs., 320 F.2d at 351). The proper clause was consequently given effect. …

In this instance, inclusion of the clause prescribed for unregulated utilities constitutes such an impermissible deviation. … The text of the FAR is unambiguous in its requirement for inclusion of the proper change of rate clause … The prescribed condition for inclusion of FAR § 52.241-7 is that the utility services ‘are subject to a regulatory body.’ … As established supra, Bay County qualifies as an independent regulatory body, and as such, FAR § 52.241-7 is a required term of the utility contract. Correspondingly, FAR § 52.241-8 is inappropriate. Although deviations may be authorized by the agency head for individual contract actions, such a deviation must be documented and justified in the contract file. … No such documentation or justification is present here.

Accordingly, the Christian doctrine applies and binds the contracting parties to the mandatory contractual term. … ‘Such regulations are law, binding on the contract parties’ when otherwise applicable to the contract, Dravo Corp. v. United States … and ‘need not be physically incorporated into the contract,’ First Nat’l Bank of Louisa, Ky. v. United States …. The court determines as a matter of law that the clause pertaining to independently regulated utilities, FAR § 52.241-7, is incorporated into the contract in place of the improper clause, FAR § 52.241-8, which is physically present.

[Emphasis added.]

So here are two recent cases that use the Christian Doctrine as support for their rulings. In one case, the Judge delved into the arcana of government contracting history to support the finding that the contractor was not entitled to make a profit on items it acquired on behalf of its customer, because the Christian Doctrine resolved any contract language ambiguities in favor of the historical approach to such acquisitions. In the other case, the Judge used the Christian Doctrine to substitute the correct contract clause for an inapposite clause, such that the contractor was entitled to recover its utility rates charged to an Air Force base.

The Christian Doctrine is frequently used in debates regarding what contracts “mean” and what they require of the parties. In point of fact, the Doctrine is inconsistently applied and we assert it’s unwise to rely on it when trying to parse contract language. A much better approach, we believe, is to take pains to fully understand what the contract language means—including discussing seeming ambiguities before execution—so that disputes are avoided.

As we’ve opined before, if you don’t understand your contract, you probably shouldn’t be contracting with the Federal government.

 

Dept. of Energy Embraces DFARS Business System Compliance Regime

E-mail Print PDF

Croggle—To astound, shock, or bewilder.

We found a new word recently that comes from Science Fiction fandom. (See above.) We think it appropriately captures our mood as we learned that the Department of Energy (DOE) has adopted, apparently on a completely voluntary basis, the DFARS Business System compliance regime.

We were croggled.

In a prior article, we reacted with a mixture of wonder, bewilderment, and shock to the notion that the Office of the Inspector General of the United States Postal Service would consider the DFARS Estimating System adequacy criteria to be a set of “best practices.” Apparently, the USPS operating deficit wasn’t large enough; the USPS OIG wanted to add to the deficit by requiring USPS contractors to embrace the same adequacy criteria used by DOD contractors—criteria that have been demonstrated to add a premium of 17 to 20 percent to contractors’ pricing.

Similarly, we were croggled when we read that the DOE published an Acquisition Letter (AL) that implemented “compliance enforcement mechanisms in the form of business systems clause and related clauses that requires the contractor to have acceptable business systems that comply with system criteria.”

And as is the case with DOD contractors, “When a contractor’s business system contains identified significant deficiencies, the contracting officer will be able to withhold a percentage of payments in accordance with the applicable system clause.”

The new compliance regime—which is the subject of a proposed rule to modify the Department of Energy Acquisition Regulations (DEAR)—will not apply to Management and Operating (M&O) contractors. As the notice stated, the rule applies to “applies to DOE and NNSA for non-M&O contracts in support of Capital Assets (as prescribed in DOE Order 413.3 B or latest version) or non-capital asset projects (other than M&O).” Moreover, the rule is to be applied retroactively to existing contracts. The Acquisition Letter stated—

When the threshold and contract type are met, the contracting officer will negotiate bilaterally with the contractor who hold affected contract to incorporate the clauses of this AL into the affected contract within 90 days. The contracting officers will also incorporate the clauses of this AL into affected contracts before extending them or exercising options under them by negotiating bilaterally with the contractors.

Here’s a link to the formal Acquisition Letter, containing all the details.

Readers will note that DOE is adopting only five of the six DOD business systems—MMAS will not be applicable to DOE contractors. We were also a bit croggled at the rationale for adopting the DOD business systems compliance regime. The AL stated—

Contractor business systems and its internal controls are the first line of defense against waste, fraud, and abuse. Weak control systems increase the risk of unallowable and unreasonable cost on Government contracts. … When the contractor has acceptable business systems that comply with the terms and conditions of the contract, this will improve contract performance.

Given the DOE’s rationale, quoted above, it seems puzzling that the M&O contractors would be exempted from the new business systems compliance regime. According to the DOE itself, M&O contracts are “central to the DOE’s business model.” That same DOE document also stated, “DOE relies upon the M&O contractors for the performance of the substantial part of the agency’s mission.” So we are at a loss as to exactly why those contractors would be exempt from the new compliance requirements.

Perhaps additional rule-making, focused on M&O contractors, is planned for the future? We don’t know. But we do know that the current additional compliance requirements focus on contractors that are less essential to the DOE mission, that handle less critical projects, and that spend the smaller fraction of the DOE budget.

If you are a DOE contractor, you had better review the AL and contract language, and be prepared to comply. Expect retroactive implementation on contracts already awarded—which of course will entitle you to an equitable adjustment.

Enjoy!

 

Breaking Down the Silos

E-mail Print PDF

We all know that the organizational “silos” undercut both efficiency and effectiveness. The silos—and the myopic self-interest such entities promote—act to sub-optimize decision-making time after time after time. It’s no longer about the larger organizational mission, and it becomes (at some level) about the mission of the smaller entity. Individuals in the smaller entity think primarily of their own interests, and not the interests of the larger organization. And so the larger strategic objectives suffer because poor decisions are made. Strategic objectives are not attained because the organization, as a whole, is not internally aligned. In at least some respects, the organization may actually be working at cross-purposes.

We all know this to be true. We’ve all experienced this situation. It’s likely the most common work environment in mid-size and larger organizations. Indeed, finding a large organization that was not divided into “silos” would be a rare and pleasant surprise.

Yet despite our best efforts to “smash the silos” (as one consultancy puts it), the “rice bowls” and “fiefdoms” and similar organizational entities seem to persist.

Perhaps it’s just human nature.

Perhaps we should expect ambitious folks to “build their empires” and defend their ‘turf’ from those who would seek to integrate (or annex, if you prefer) disparate organizational entities into one. Perhaps we should simply accept the fact that Type A individuals will put their own self-interest ahead of the interests of the entire organization.

Still ….

It’s tough to be an effective consultant when the hiring organization cannot operate effectively, because of competing organizational silos.

You hire PwC or KPMG or Deloitte or EY, or Accenture or FTI, and you are paying top-dollar for expertise and experience—both of which inform strategic and tactical recommendations. If you hire Apogee Consulting, Inc., you pay significantly less, but you are still paying for the same thing. The same concept holds true for any consultant or professional you may hire—including attorneys.

If you decide to hire outside advisors, you pretty much know you are going to be paying some significant dollars.

So why would you let your ability to implement those expensive recommendations be undercut by your own organization?

Of course you wouldn’t do that in a rational work environment; but, as we’ve already noted, irrational structures and self-dealing individuals persist, despite management’s efforts to eradicate them. (And that assumes management knows about them; they are often hidden from sight in backoffice eddies.)

Too often—far too often—we’ve experienced bizarre and irrational organizational behavior that undercut the strategy and tactics for dealing with Government compliance issues. Big companies, mid-size companies, even small companies: all exhibit a tendency to let competition between internal organizational entities stop effective implementation of the recommended courses of action. And this has been true even after top leadership has agreed to implement the recommendations.

In 1999, a multi-billion dollar corporation paid a consultancy about $500,000 for an in-depth analysis of its contracting and billing functions. The analysis took about six weeks and involved a joint effort with internal counsel and other employees, who were seconded to the analysis team to make sure the consultants got it right. The corporation needed to get it right, because the Department of Justice was already involved. For that $500,000 investment, plus the additional investment of internal time and resources, the corporation received 18 very detailed recommendations. The consultancy was thanked for its efforts; the bills were paid. And then … the corporation actually implemented only one of the 18 recommendations. The other 17 recommendations were ignored.

Why? Why would a corporation facing significant sanctions make those investments and then not make the necessary changes to create the “return on investment” that they had told themselves they wanted?

Many of those other 17 recommendations involved making changes to the ways in which aspects of the corporation operated. They threatened fiefdoms and rice bowls and turf. From one perspective, it was easier to ignore them than to think about work flow and reorganizations and employee transfers. From another perspective, it was easier to ignore them than to expend the political capital necessary to make the changes.

Regardless of the reason, the corporation’s shareholders spent half a million dollars, and received very little return on their investment.

And this is but one of the many examples we could write about.

We could write about the multi-billion defense contractor that paid $500,000 for a new approach to risk management, one that would be designed to reduce line stoppages that stemmed from vendor delivery delays. They got what they paid for, only to see the innovative approach killed by “sector management” because it was that entity who “owned” risk management, organizationally speaking. Innovation threatened their monopolistic position. And so the contractor paid its bills and got nothing in return.

We could write about the mid-size E&C contractor who let its corporate accounting function hold-off the hiring of external consultants to perform an independent analysis of its indirect cost allocation structure (since there was no reason to change what had been successfully working for so long). Yeah, that worked for them—right up to the time DCAA pulled the accounting system adequacy because the company couldn’t document, trace, or support its indirect cost allocations.

So here’s the thing: we consultants do not like to see our time and efforts wasted by your organizational inefficiencies. Despite the popular stereotype, most every consultant we know gets great satisfaction from seeing their recommendations successfully implemented and seeing your problems resolved. We do not simply want to take your money: we very much want to help you solve your problems and improve your operations. Our success is measured by your success, not by the bills you pay.

When you pay our bills but don’t take our recommendations, when your problems go unresolved because you don’t take our advice, then that disappoints us more than you can imagine.

And when you listen to us and agree to implement the actions that we both agree are the right actions to take, and then you don’t implement the actions because your internal organizational “silos” are not aligned and, indeed, engaged in active warfare with the goal of scuttling the organization’s strategic objectives because they threaten somebody’s little fiefdom … well, that upsets us more than you can possibly imagine.

***

Why did we write this blog article? Why did this topic come to the forefront of our consciousness today?

Oh, no particular reason.

Why do you ask?

 

Government Establishes Position on CAS 412 Requests for Equitable Adjustment

E-mail Print PDF

If you’ve been reading this blog for any length of time, you more than likely have read an article or two on CAS 412. CAS 412 is one of those Cost Accounting Standards that only a very few (possibly psychologically unwell) individuals enjoy delving into. And the truth is, you really don’t need to understand the intricacies of CAS 412 unless you have a defined benefit pension plan. Those many upon many contractors who have defined contribution pension plans instead of defined benefit plans really can afford to stay the heck away from CAS 412, and thus maintain lower blood pressure readings and perhaps a healthier psyche.

For those who enjoy staring into the abyss, we want to recap some of our articles on the topic, in order to establish a historical context.

In May, 2010, we wrote this article, in which we discussed the Pension Protection Act (PPA) and how that public law led to “CAS harmonization”—especially the revisions to CAS 412 and 413. Three years ago, we wrote—

The Standards dealing with defined-benefit pension plans are about to be revised, and contractors will have to change their cost accounting practices in order to comply with the revised CAS requirements.  The changes will lead to an increase in measured pension costs.  A ‘SWAG’ by a DCMA pension expert estimated a 60% increase in pension costs!  Because the cost accounting practice changes are required by the revised Standards, contractors are entitled to an equitable adjustment to contract prices.  They are going to be hitting up their customers for the increased costs.  … The DOD has known about this upcoming day of reckoning for quite some time, and has taken actions that would prevent contractors (and their government customers) from doing anything about it until the CAS Board finishes its rulemaking work.  Yes, you heard that correctly.  The Pentagon has actively prevented DOD programs from creating reserves that would cover the upcoming cost impacts.  … As a result of DOD’s willful blindness, someday soon there is going to be a reckoning, as CAS-covered contractors with defined benefit pension plans notify contracting officers of the contract price increases stemming from the new CAS rules.  DOD has no budget for the price increases and any attempt at proactive planning was effectively halted by the DPAP memo noted above.  Won’t Congress dearly love the upcoming surprises coming its way!

In March, 2012, we wrote an update article, in which we discussed reactions to the news about the costs of contractor pension plans, in which several ostensibly knowledgeable entities and individuals feigned surprise and shock over the additional pension costs stemming from the CAS 412 changes that “harmonized” CAS with the PPA.

About a month later, we discussed a Memo issued by the Honorable Shay Assad, DOD Director of Pricing. That was an important Memo for two classes of contractors: (1) those that had defined benefit pension plans whose cost measurement had been impacted by the CAS 412 and 413 revisions, and who would be submitting Requests for Equitable Adjustment (REAs) associated with their cost increases; and (2) those that had defined benefit plans whose cost measurement had been impacted by the CAS 412 and 413 revisions, but who would not be permitted to submit REAs associated with their cost increases.

Okay, with that background, you are now ready for the latest discussion point: a new Memo issued by Shay Assad, entitled “Guidance on the Cost Accounting Standards Board Equitable Adjustment Process Related to Cost Accounting Standards, December 27, 2011, ‘Final Rule to Harmonize CAS 412 and 413 with the Pension Protection Act of 2006.’”

Whew. With a title like that, you know it’s got to be good!

Notably, the latest Assad Memo states—

Contracting parties have been developing, submitting, reviewing, and negotiating cost impacts since the establishment of the CAS. For these reasons, this well-defined process will serve well in this instant case. However, it must be recognized that the actual impact of CAS Pension Harmonization on affected contracts can be significant even with relatively minor increases/decreases in the interest rate used to compute the minimum actuarial liability and minimum normal cost. Accordingly, included in the attachment [to the Memo] is guidance to ensure that the adjustment to affected contracts is equitable for both contracting parties. This would include an annual assessment and potential adjustment to the negotiated cost impact based upon looking back and comparing the impact between the forecasted and actual interest rates.

Also notably, the Memo states that the contractors who submit REAs will not be entitled to profit/fee on those REAs.

The second point is annoying but perhaps relatively minor. The first point, quoted at length above, is significant and, in our view, inapposite. So we’ll rail a bit on the first point.

The purpose of a cost impact analysis is to establish the cost impact on affected CAS-covered contracts, so that the contracting parties can negotiate a contract modification that acknowledges that cost impact. (Normally, the cost impact is supposed to be a price impact, but see the second point noted above.) The point is, it’s a single negotiation, informed by the cost impact analysis. That impact analysis is really a proposal and it’s audited, more often than not, by the DCAA—just as if it were a cost proposal for new contract work. The parties then sit down and negotiate how the price of one, or more than one, contract will be affected. (See FAR 30.6 and the CAS clause 52.230-6.)

Nowhere does the CAS or FAR anticipate that the negotiation will become an annual affair, with the contract cost impact and resulting modification being adjusted again and again, based on changes to forecasted interest rates. That’s just something created out of whole cloth in order to keep the cost impact to a minimum; it comes from the same place as the notion that a contractor shouldn’t get the profit it would have originally negotiated, had Mr. Assad not forbidden the contracting parties to consider the impact of PPA in their price negotiations.

So in our view it’s kind of an inappropriate approach to negotiating cost impacts. In fact, in our experience, it would take far longer than one year for DCAA to conduct an audit of the interest rates and for DCMA to negotiate contract modifications. Thus, in addition to our philosophical objections, we believe it’s simply unworkable in practice.

Now before you get all worked up, we also consulted other practitioners at affected contractors, at least one of whom attended in person an industry meeting with Mr. Assad to discuss this new guidance Memo. The other folks told us, “it could have been worse.” In other words, they think they can live with it.

And unless you, too, are a fully CAS-covered contractor with a defined benefit pension plan, then it’s their opinion that matters and not yours. And likely not ours, either.

 

Update on Apogee Consulting, Inc.

E-mail Print PDF

Flying on a plane between Texas and California, it seems an appropriate time to give a 38,000 foot perspective on where Apogee Consulting, Inc. is going.

The consulting continues, though at lower levels than we’ve previously experienced. We thank our clients for their continued use of our services, and for their referrals. We will continue to provide consulting services to those who request them, though we will do so from Texas instead of California.

The website continues, though quite honestly we’re a bit concerned about the lack of use of some of our features. For instance, though we get anywhere from 600 to 1,000 visits a week, almost nobody cares to leave comments or reactions to our blog articles. It was some of our regular visitors who requested those features, and we spent time and money to create the functionality. If they’re not going to be used, we’ll probably kill them come January.

The fate of the comments/reactions functionality is in your hands, gentle readers.

The other feature that’s not being used is that of our accumulated knowledge resources. You can find things there that are tough to find anywhere else. Yet, despite what we think is much value, almost nobody is using them. Thus: we probably won’t be adding many new resources to our repository. As we look to streamline the future site, we’ll evaluate such features based on usage/popularity.

We will be resuming blogging soon but, consistent with the state of flux involved in relocating halfway across the country, readers should not expect daily updates. Right now, once or twice a week seems to be the right level—unless something really frosts us and demands a screed of outrage.

So what will we be doing with all our free time?

Well, for starters we have a few eBooks to get written. We’ll start with something on Leadership that’s never been published anywhere, and then we’ll do at least one compilation of well-received blog articles from this site. The compilations will be for sale – for cheap! – on Amazon. We’ll announce them here. Look for them before too long.

We are also thinking about bigger fish, such as a book on the Cost Accounting Standards that does more than simply rehash the rules and regulations. It seems past time for such a book to be written, and we think we have the chops to see it through. Only time (and a willing publisher!) will tell.

So that’s the 38,000 foot perspective on 2013 and beyond.

Thanks for your support.

 


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