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

The Ability to Accurately Input IR&D Information

E-mail Print PDF

Recently DCAA issued audit guidance designed to assist its auditors with the requirement that certain "major" DOD contractors must input IR&D information into the Defense Technical Information Center (DTIC).

Readers may remember we addressed the new requirement when it was promulgated. We wrote: "In sum, the new rule establishes two requirements: (1) reporting to DTIC, and (2) review of the information reporting by DCAA and the cognizant DOD ACO to determine which IR&D projects are 'of potential interest' to the Pentagon. Failure to meet the first requirement will lead to disallowed IR&D associated with specific, individual, IR&D projects."

The new DCAA audit guidance adds some detail to our summary. It states-

Contractors subject to the regulation must:

  • input project information to the DTIC database no later than three months after the end of the contractor fiscal year (CFY) in which the contractor initially incurs the associated IR&D;
  • annually update information in the database for ongoing projects (no later than three months after the end of the CFY in which the associated IR&D cost is incurred); and
  • update the database when the contractor considers the project completed.

Importantly, the DCAA audit guidance does not focus on the absolute accuracy of the data being input into DTIC; instead, it emphasizes the impact associated with the simple failure to input any information. With respect to audits of Forward Pricing Rates, the audit team may reduce or eliminate forecasted IR&D expenditures "based on the contractor's ability to appropriately complete the requirements to input data into the DTIC system." With respect to adequacy reviews of a contractor's Accounting System, "Audit teams should consider whether the contractor's failure to have adequate internal controls to ensure compliance with the regulation results in an accounting system deficiency."

Based on the foregoing, an inability to timely input the required information could have far-reaching and unpleasant ramifications. Accordingly, defense contractors subject to the DTIC reporting requirement should assign responsibility for the input and also design a compliance check to ensure the information was submitted on time.

Of course, the DCAA audit guidance reminded auditors that a failure to comply with the DTIC reporting requirements could and should lead to questioned (and ultimately disallowed costs). The audit guidance stated-

If the contractor fails to input the IR&D information into the DTIC database, the costs are expressly unallowable; audit teams should question the costs and recommend application of penalties. If the team identifies significant expressly unallowable costs, consider reporting a noncompliance with CAS 405, Accounting for unallowable costs.

We have already seen both DCAA and DCMA probing the DTIC input. Frankly, it should not be a big deal to support an audit RFI for those contractors subject to the rule. This is only going to be a big deal if somebody doesn't input the information when required to do so. But contractors required to input IR&D information, who do not or cannot timely fulfill their responsibility, may be in for a very rough ride indeed.

 

Counterfeit Parts: Turning the Dial to Eleven

E-mail Print PDF

Nigel Tufnel : The numbers all go to eleven. Look, right across the board, eleven, eleven, eleven and...

Marty DiBergi : Oh, I see. And most amps go up to ten?

Nigel Tufnel : Exactly.

Marty DiBergi : Does that mean it's louder? Is it any louder?

Nigel Tufnel : Well, it's one louder, isn't it? It's not ten. You see, most blokes, you know, will be playing at ten. You're on ten here, all the way up, all the way up, all the way up, you're on ten on your guitar. Where can you go from there? Where?

Marty DiBergi : I don't know.

Nigel Tufnel : Nowhere. Exactly. What we do is, if we need that extra push over the cliff, you know what we do?

Marty DiBergi : Put it up to eleven.

Nigel Tufnel : Eleven. Exactly. One louder.

Marty DiBergi : Why don't you make ten a little louder, make that the top number and make that a little louder?

Nigel Tufnel : [pauses] These go to eleven.

The Government Contracts Attorneys at McKenna, Long & Aldridge summarized the situation with simple elegance. They wrote: "Contractors still assessing compliance with the DOD counterfeit electronic parts rule could soon be faced with another counterfeit parts obligation."

You remember the DOD Counterfeit Electronic Parts rule, don't you?

It was issued after the DOD Interim Rule covering "supply chain risk." You know: that rule where contractors with secure supply chain systems would be subject to a statute-approved competitive advantage over those who did not. From our perspective, that rule was the carrot designed to entice contractors into moving into secure supply chains and product pedigree analysis.

Then DOD took the next step. It added requirements for a system to identify counterfeit electronic parts. DOD baked the new CEP requirements into the Purchasing System adequacy criteria and threatened to disapprove a contractor's purchasing system that failed to adequately address the new requirements. As we all know, a system disapproval in the DOD (or DOE) environment would lead to payment withholds that would impact cash flow. And DOD also said that the cost of rework or remedying inclusion of counterfeit electronic parts was likely to be unallowable, except in very specific circumstances. Those actions seemed like the sticks to us, designed to beat contractors who were not motivated by the carrot described above.

We figured that if the carrot didn't work, then sticks certainly would.

We figured the rulemakers had done their job and contractors would be moving in the desired direction.

And now the FAR Council has turned the dial to eleven.

We're talking about FAR Case 2013-002, "Expanded Reporting of Nonconforming Items." Here's a link to the proposed rule, which would revise the FAR (not just the DFARS) to require all government contractors to report not only counterfeit electronic parts, but also counterfeit parts of all types.

If adopted as proposed, the FAR rule will impose two fundamental requirements on government contactors:

  1. Ensure that vendors or suppliers of raw or processed materials, parts, components, subassemblies, and finished assemblies have an acceptable quality control system and that quality escapes from these vendors and suppliers are not incorporated into the contractor's final product; and

  1. Screen reports in the Government-Industry Data Exchange Program (GIDEP) to avoid the use and delivery of items that are counterfeit or suspect counterfeit items or that contain a major or critical nonconformance.

Contractors will be responsible for submitting a written report (a) to the Contracting Officer within 30 days, and (b) to the GIDEP within 60 days, when the contractor becomes aware of a counterfeit (or potentially counterfeit) part or if a quality escape deemed to be a critical or major nonconformance impacted a common item or more than one customer.

Clear?

Let's quote some proposed FAR definitions:

Common item means an item that has multiple applications versus a single or peculiar application. Common items include, for example, raw or processed materials, parts, components, subassemblies, and finished assemblies that are commonly available products (such as nondevelopmental items, off-the-shelf items, National Stock Number items, or commercial catalog items).

Counterfeit item means an unlawful or unauthorized reproduction, substitution, or alteration that has been knowingly mismarked, misidentified, or otherwise misrepresented to be an authentic, unmodified item from the original manufacturer, or a source with the express written authority of the original manufacturer or design activity, including an authorized aftermarket manufacturer. Unlawful or unauthorized substitution includes used items represented as new, or the false identification of grade, serial number, lot number, date code, or performance characteristics.

Critical nonconformance means a nonconformance that is likely to result in hazardous or unsafe conditions for individuals using, maintaining, or depending upon the supplies or services; or is likely to prevent performance of a vital agency mission.

Design activity means an organization, Government or contractor, that has responsibility for the design and configuration of an item, including the preparation or maintenance of design documents. Design activity could be the original organization, or an organization to which design responsibility has been transferred.

Major nonconformance means a nonconformance, other than critical, that is likely to result in failure of the supplies or services, or to materially reduce the usability of the supplies or services for their intended purpose.

Quality escape means a situation in which a supplier's internal quality control system fails to identify and contain a nonconforming condition.

Suspect counterfeit item means an item for which credible evidence (including but not limited to, visual inspection or testing) provides reasonable doubt that the item is authentic.

The proposed rule would apply to primes and to subcontractors, to simplified acquisitions and to negotiated acquisitions, and to acquisitions of commercial items.

Interestingly, the new requirements are not being driven by Congress. That is to say, Congress did not direct the FAR Council to take the far-reaching rule-making actions that have been proposed.

Readers may recall our analysis of the FY 2012 NDAA, in which we noted Section 818, which required DOD to enhance its processes for detecting and avoiding counterfeit electronic parts. Let's let the FAR Council describe how they implemented that piece of statutory direction, courtesy of the Background section of the proposed rule. They wrote-

While section 818 applied only to DoD, only to electronic products, and only to contractors covered by the Cost Accounting Standards (CAS), the FAR Council concluded that the principles expressed in section 818 should be applied beyond DoD, should not be limited to electronic products, and should not be limited to CAS-covered contractors. Similarly, although OFPP Policy Letter 91-3 requires agencies to report to the Government-Industry Data Exchange Program (GIDEP), the FAR Council determined that reporting would be much more timely and effective if contractors were to make the reports directly to GIDEP.

So there you have it. A new, potentially far-reaching, proposed rule driven not by statute but, instead, by the FAR Council's view of the seriousness of the threat.

But we're not done yet.

Perhaps the FAR Council is not wrong in its assessment of the situation.

On June 13, 2014, the Department of Justice announced that-

The former president of a Burlington, N.J.,-based defense contracting business was arrested and charged today … Richard Melton, 44, of Moorestown, N.J., was charged by complaint with one count of conspiracy to commit wire fraud for receiving $3 million from 2008 to 2009 as a result of allegedly fraudulent contracts with the U.S. Department of Defense (DoD).

Melton owned and operated Partz Network from April 2003 to December 2009. Partz Network contracted with the government to supply the DoD with parts on small-dollar contracts. The majority of the contracts were for replacement parts for military rolling stock: trucks, trailers, and engineering equipment. The majority of Partz Network's DoD contracts required that the items provided be manufactured by DoD-recognized qualified manufacturers. Melton and his conspirators allegedly lied on Partz Network's bids for DoD contracts, stating that they would be providing the "exact product" sought by the DoD, meaning that the product was manufactured by a DoD-recognized qualified manufacturer. In fact, Partz Network was allegedly providing parts made by unapproved, and oftentimes unknown, sources.

In 2007, the Defense Logistics Agency (DLA), a DoD contracting agency, became aware of reports of nonconforming parts being received from Partz Network. As a result, DLA required Partz Network to provide "traceability documents" to confirm that the items it was supplying were actually being manufactured by DoD recognized qualified manufacturers. Partz Network provided traceability documents and invoices to DLA regarding items provided under the DoD contracts. When DLA researched the traceability documents supplied by Partz Network, DLA learned that the documents were either altered or completely fictitious. …

The items ultimately provided by Partz Network were not the exact products required under the contract because the items were not manufactured by a qualified manufacturer. In fact, on Nov. 10, 2007, five days prior to Partz Network submitting its bid for the contract, Melton sent an e-mail to a Partz Network employee with a link to the DoD RFQ that stated the following: "Bid these (1400) HMMWW oil pans at $53.85 and I will have them made overseas by [a company located in the People's Republic of China] or another overseas firm, 200-day lead time." Based on Partz Network documents related to that contract, Partz Network purchased the oil pans that were provided to the DoD from a company located in India in January 2008. …

The wire fraud conspiracy count with which Melton is charged carries a maximum potential penalty of 20 years in prison and a fine of $250,000, or twice the gain or loss from the offense.

So as long as the U.S. Government perceives the threat of non-conforming and/or counterfeit parts to be a serious threat, they would seem to be justified in requiring contractors to take measures to detect and deter their occurrence. The fact that it's going to impose new requirements (with additional costs) on contractors probably did not weigh heavily in the FAR Council deliberations. Perhaps with final implementation of this rule, there will be sufficient carrots and sticks available to reign in this practice.

On the other hand, when the U.S. Government keeps awarding contracts to the low-price bidder without regard to how those low prices were derived ( e.g., outsourcing manufacturing to the People's Republic of China), it creates an incentive for contractors to keep breaking the rules. Note that the proposed rule would apply to both simplified acquisitions (Part 13) and commercial acquisitions (Part 12) as well as to negotiated acquisitions (Part 15). Price analysis is a significant aspect of Part 12 and Part 13 source selection decisions. It would not be uncommon for price to be the sole deciding factor between what seems to be otherwise responsible competing sources.

Moreover, it seems unrealistic to expect contractors to be motivated by regulatory carrots and sticks, when a threat of 20 years in Federal prison doesn't seem to affect behavior. The same people who would seek to defraud the Federal government prior to the implementation of this proposed rule would seem to still seek to defraud the Federal government, though of course there would be more certifications to falsify and more required reports to ignore. The same people who would ignore the Buy American Act and the Trade Agreements Act and the False Statements Act would not seem to be deterred by this new set of contractual requirements.

Consequently, one possible outcome of this proposed rule would be to increase the costs associated with the "good guys"-the compliant contractors who will do their best to meet their obligations … while having no cost impact on the "bad guys" (those who intend to provide counterfeit or nonconforming parts regardless of the consequences). If this is the outcome, then the price disparity between the good guys and the bad guys is going to increase, leading to more awards to the bad guys.

Will this be the outcome? Only time will tell.

 

Innovation: Not Invented Here Anymore

E-mail Print PDF

Google_Barge_Data_Center
In the 5/18/2014 edition of the National Defense Industrial Association magazine, Sandra Erwin wrote-

Cuts to federal spending have wreaked havoc on Defense Department research and technological pursuits, officials insist. Potential adversaries are modernizing while the next generation of U.S. weaponry remains bogged down in budget quagmires. … But the Pentagon also has itself to blame for losing the cutting edge, current and former defense officials contend. While budget cuts and sequestration have disrupted the Defense Department's research-and-development flow, they argue, a major impediment to innovation is a hidebound military establishment that cannot stay apace with advances in technology.

Another obstacle to innovation is the Pentagon's propensity to build 'big, robust, work-forever' systems with closed architectures that are incompatible with other software or computers … How the Pentagon connects with the private sector also hinders progress …

We've noted this challenge before. Others are noticing the same thing.

Bill Greenwalt, writing in Wired magazine, stated-

Despite some initially promising reforms in the early 1990s, the IT acquisition problem has gotten worse and the government continues to trail the private sector in its effective use of new technologies and approaches. Nor is the $500 billion annual federal acquisition problem limited to IT; it transcends major defense systems, research and development, construction, services contracting and commodities. A one-size fits all, rules based, Rube-Goldberg machine ensures that procurement failures are magnified and not left to chance.

The great mystery in all of this is why the federal government is failing in its IT programs when some of the best IT talent resides in U.S. The answer is that Silicon Valley is not involved in government contracting. … many of the most dynamic, innovative, successful, commercial firms will not bid on a standard government contract because of the costs of complying with federal acquisition rules and the limited returns associated with federal procurement. Limited? Think under ten percent for government contractors, versus returns of 20 percent and above in the commercial world.

Reforms made in the Federal Acquisition Streamlining Act of 1994 and the Clinger Cohen Act of 1996 made it easier to sell to the federal government, and for a while, commercial firms tiptoed into the federal market. However these reforms did not go far enough for many commercial companies. For example, the changes failed to remove the requirements to comply with unique government accounting standards, they failed to protect commercial intellectual property rights, and failed to stop arbitrary government audits. With the passage of time and without senior leadership support, bureaucratic inertia set in and resulted in the re-imposition of old requirements, in the creation of new barriers to doing business with the government, and in a de facto preference for government-unique rather than commercial solutions. So Silicon Valley did what it does best: ignore the government and make a lot of money elsewhere.

The current strained fiscal environment demands that the federal government move away from a process-driven acquisition system if it is ever going to access the cost saving opportunities and innovative solutions that have arisen in the commercial market. A system that only works by going around it is not a workable system and should be dismantled.

Not to be outdone, the Center for a New American Security issued a report (with significant input from former Deputy Defense Secretary William Lynn) that "the U.S. weapons industry moves too slowly to adjust to current trends." According to the Reuters story (link above), the report "said industry and government need to invest more in new technologies and remove regulatory and acquisition barriers that hinder U.S. firms. … The report called for reforms to allow more U.S. and foreign firms to participate in the U.S. weapons market, greater communication about the Pentagon's technology needs and measures to safeguard private intellectual property."

Whether you call it a triumph of bureaucracy or an innovation shortfall, the fact of the matter is that the Pentagon finds itself falling behind the private sector in terms of development speed and effectiveness. We don't have any brilliant answers to help DOD solve its innovation challenges, but we do have one observation to make.

When you keep buying based on the lowest priced solution, when you keep awarding contracts based on lowest perceived risk, when you insist on high Technology Readiness Levels … you are not going to get much innovation.

There was a time when basic research was seen as a public good, even when that research resulted in a dead end. The government was pleased to fund scientific inquiry, secure in the notion that knowledge was good and that progress would sooner or later result from that knowledge. Those days seem to have largely faded away. Nowadays we have Apple and Google and Facebook (which are the end product of government-funded research) and they seem to have plenty of money to splash around in the name of research and innovation.

You want to spearhead defense innovation? Then you had better ask one of those big players to help you out.

 

T&M Contracts Get Riskier

E-mail Print PDF

RisksTime and Material (T&M) contracts have always been the least preferred contract type, whether you are a Government customer or contractor.

From a Governmental viewpoint, a T&M contract does not require performance; it requires delivery of hours. The contractor delivers the hours and it gets paid at the specified contractual rates, regardless of whether or not those hours actually lead to the desired program outcome. In addition, there are cost-reimbursement aspects (on the "M" side) which means audits and negotiated final rates … which means it's going to take quite some time to actually close-out that contract after performance.

From a Government contractor perspective, a T&M contract requires juggling a number of variables to ensure a profit is generated. Employee salaries need to be estimated in advance, as do indirect rates. If somebody gets an unexpected raise, or if the indirect rates unexpectedly jump, then there is going to be immediate profit degradation. In addition, the T&M Payment clause (52.232-7) imposes a number of relatively onerous compliance requirements and the Allowable Cost & Payment clause (52.216-7) also imposes a number of definitely onerous compliance requirements. And the fact that actual allowable indirect cost rates are allocated to the "M" side means audits and auditors and protracted final rate negotiations … which means it's going to take quite some time to actually final-bill and close-out that contract after performance.

The profit negotiations on T&M contracts are difficult. Officially the contractor should not bill profit/fee on the "M" side of its contract. Officially subcontractor hourly billing rates (which include billing rates for other affiliated divisions of the contractor) do not bear any prime contractor profit. But of course the contractor expects to be paid a reasonable profit, not only on its own contract hours, but also on the hours billed by its subcontractors. Given that the only way to bill profit on those other hours (and materials and travel and Other Direct Costs) is to bake them into the contractor's hourly billing rates, what seems like a reasonable bottom-line profit percentage to the contractor seems egregiously rapacious to the Government Contracting Officer trying to negotiate a price.

For the foregoing (and other) reasons, neither contractors nor their Government customers should desire to enter into a T&M contract.

That warning doesn't keep far too many T&M contracts from being awarded each day. The Government keeps issuing 'em and contractors keep signing up for 'em, even though both parties know going in that there are going to be difficulties and risks, and at the end of the period of performance somebody is likely to be upset.

And the risk/reward equation of T&M contracts just skewed once again, as DCAA issued new audit guidance on May 22, 2014. The audit guidance reminds auditors of old 2007 guidance (issued in conjunction with the revision of the 52.232.7 T&M Payment clause) that said-

Labor hours incurred to perform tasks for which labor qualifications were specified in the contract will not be paid to the extent the work is performed by employees that do not meet the qualifications specified in the contract, unless specifically authorized by the Contracting Officer.

The audit guidance recognizes that each hourly labor category not only has a fixed billing rate, but also has a definition as to which contractor (or subcontractor) employees are allowed to bill at that particular rate. (We should note that is yet another variable the contractor needs to manage: making sure that its mapping of employees to labor categories/hourly billing rates complies with contractual definitions.)

The DCAA audit guidance tells auditors that a contractor's failure to properly map its employees to the contract-defined labor categories/hourly billing rates is not just an opportunity to question costs. It is also an opportunity to question the adequacy of a contractor's accounting system. The audit guidance states-

If the audit team determines that the contractor has a material amount of T&M billings that include hours that do not meet the labor qualifications specified in the contract, a significant deficiency related to DFARS 252.242-7006(c)(12) should be reported. The contractor has failed to establish adequate internal controls to exclude from costs charged to Government contracts, amounts that are not allowable in terms of contract provisions in the FAR 52.232-7 T&M Payment Clause. An adequate accounting system would include procedures for a contractor to ensure that they get the Contracting Officer's specific authorization prior to the delivery and billing of hours that do not meet the qualifications specified in the contract.

Consequently, a T&M contract not only includes most of the "normal" risks associated with government contracting plus unique profit risks plus unique personnel risks, it now also includes the risk that if you get anything wrong and DCAA notices your mistake, you may have to deal with a "deficiency report" and a recommendation that your accounting system be deemed to be inadequate for cost-reimbursement and/or T&M contracting.

But readers may notice something in the new DCAA audit guidance: it isn't new. It's essentially a rehash of the 2007 audit guidance plus a bolt-on paragraph related to the DFARS Business Systems administration/compliance regime. So why did DCAA issue it?

Well, we don't know the answer to that question. But we did notice a May 19, 2014 article in the Washington Post that reported on the findings of a DOD Inspector General audit report. The DOD IG report was FOIA'd by POGO (the Project on Government Oversight) and would not otherwise have been published had POGO not FOIA'd the DOD IG.

The not-for-publication DOD IG audit report found that from October 2007 through March 2013 Northrop Grumman "did not properly charge labor rates" for a counter-narcoterrorism contract. WaPo reported that "the Army agency in charge of the contract did not ensure that the people performing the work had the necessary qualifications. The agency also did not review invoices for millions of dollars of overtime."

Moreover (according to WaPo)-

… the IG found $21.7 million in 'potentially excessive payments' for overtime, including one employee who billed $176,900 for 1,208 hours in a 12-day period. That caught investigators' attention, since the employee was billing for more than 100 hours a day. The IG found that out of the charges submitted over nearly six years for 460 DynCorp employees working for Northrop Grumman, 360 did not meet the specified labor requirements, leading to $91.4 million in questionable costs. In one case, a program manager who billed 5,729 hours over a year and a half, totaling $1.2 million, did not have a bachelor's degree, which was a requirement of the position. Another employee billed 16,270 hours' worth $2 million over five years but was qualified for only 161 hours of the work.

Is there a connection between the May 19, 2014 Washington Post story about mismatches between contractor employee qualifications and contract-defined labor categories with individually specified hourly billing rates, and the May 22, 2014 reminder to DCAA auditors to check for matches between contractor employee qualifications and contract-defined labor categories with individually specified hourly billing rates?

We don't know but, if there is no official connection, then it's surely a strange coincidence, is it not?

 

Choice of Contract Type

E-mail Print PDF

Back in the day we were somewhere in the Northeast, consulting on a new thing called "Program Management Effectiveness" or PME. PME was the result of applying a CMMI approach to Defense Program Management. It evaluated the maturity of numerous attributes and (hopefully) identified "pain points" experienced by the Program (or Project) Management team, so that the organization could eliminate them. It was a fairly successful service offering but, like so many things in the consulting biz, the ultimate success or failure was largely in the hands of the client. We could identify immature processes, capability gaps and pain points, but if the client took our output and then stuck it on the bookshelf to gather dust, then it was all just an expensive waste of time.

Our team deployed at a designer and manufacturer of aircraft. We were invited to evaluate a couple of in-process major design initiatives that, if successful, were going to be franchise programs for that contractor. The problem was that they were not going very well, and senior management wanted a fresh, independent, perspective on what the contributing problems might be.

We interviewed several IPT leads and various levels of program management. We interviewed Contracts folks and Subcontract Management folks and Procurement folks. We interviewed HR and IT and a host of other functions. We delivered on our end. We never really learned what the client did with our recommendations, but I still read about those programs today; and they seem to be relatively successful as new aircraft programs go.

Out of the many issues we identified, one is relevant to today's article. It concerns contract type.

One of the more important metrics used by senior program management was "time to contract," which essentially measured the time it took to get a suppler an executed contract, once the requirements had been identified. Obviously, the quicker the better, right?

Maybe not.

When we interviewed the Subcontract Management and Procurement folks, they were quite pleased at their "time to contract" metrics. So many of the suppliers had been put under contract early in the program, and the personnel involved were proud of their efforts. They were also proud that they had placed 100% firm, fixed-price (FFP) contracts with their suppliers. FPP subcontracts were seen as lower-risk, since they put the risk of cost overrun on the subcontractor instead of the prime contractor. The folks saw it as a huge feather in their caps that they had negotiated and placed FPP subcontracts so early in the program life cycle.

They had never considered the ramifications of putting FFP subcontracts in place before the overall design had been finalized. They had never considered the implications of putting their suppliers on contract without having a final detailed design in place.

One thing we all know for sure is that no design is fixed until it's completely fixed. Until the design is fixed, expect changes. Perhaps lots of them. And even after the design is fixed, complete, done - expect more changes. Because just like no plan of war survives contact with the enemy, no aircraft design survives contact with a design review team, or a systems engineering team, or a manufacturability team, or an "as-built" review team. Changes are a given in any defense contract, let alone one for an aircraft that had never been built before.

Thus, the SCM and Procurement folks had never considered that their early FFP subcontracts were going to be subject to a multitude of changes. Changes initiated by the IPTs, changes initiated by the subcontractor, changes initiated by the customer that impacted the subcontractor, etc. There were going to be lots and lots of changes as the design went through reviews, and each of those changes had the potential to generate Requests for Equitable Adjustment (REAs) that could impact that tidy FFP subcontract price the folks had so quickly negotiated.

Processing REAs takes time and money. Time and money which nobody had budgeted for. We pointed that out to the contractor's senior management team; but I don't believe they ever really understood the fundamental point. The fundamental point was that the requirements needed to be close to final before a FFP subcontract was negotiated. The fundamental point was that establishing a metric that incented people to move quickly might, in this set of circumstances, be counter-productive to smart program management. If they were going to award FFP subcontracts then those should come later in the program life cycle, not earlier. Awarding them too early was going to lead to downstream cost and schedule impacts.

The Under Secretary of Defense (Acquisition, Technology and Logistics), Honorable Frank Kendall, recently discussed when it would be appropriate to issue FFP contracts and when it would not be as appropriate to do so. As many readers know, the Obama Administration has been hell-bent-for-leather on issuing as many FFP contracts as possible, while avoiding as many cost-type contracts as possible-judging cost-type contracts to be higher risk than FFP contract types.

As we just illustrated, that is not always the case. And apparently Mr. Kendall agrees with us on that, especially when a development contract is being contemplated.

He wrote (link above)-

FFP development tends to create situations where neither the government nor the contractor has the flexibility needed to make adjustments as they learn more about what is feasible and affordable as well as what needs to be done to achieve a design that meets requirements during a product's design and testing phases. … Most sophisticated weapons systems development programs deal with maturing designs and challenging integration problems. As a result, the government often will and should provide technical guidance and make tradeoff decisions during development. … While it certainly is possible to negotiate changes in a fixed-price contract environment, the nature of development is such that informed decisions need to be made quickly and in close cooperation with our industry partners. The focus in a fixed-price environment is squarely on the financial aspects of the contract structure and not on flexibly balancing financial and technical outcomes.

Risk is inherent in development, particularly for systems that push the state of the art. Even with strong risk reduction measures in Technology Demonstration phases and with competitive risk reduction prototypes, there still is often a good deal of risk in EMD [Engineering, Manufacturing, and Development]. Here are the considerations I look for before I will approve a fixed-price or FPI [Fixed-Price Incentive] EMD program:

  • Firm Requirements
  • Low Technical Risk
  • Qualified Suppliers
  • Financial Capability to Absorb Overruns
  • Motivation to Continue [in the event of overrun]


There was more but that a good summary. Mr. Kendall emphasized that FFP or FPI contract types are preferred, but that the contract type must be right for the circumstances. We agree.

 


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