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

Proposed FAR Revision Hides Huge Impact Behind Innocuous Name

E-mail Print PDF


It's got a bland title, one that says "pay no attention to this technical change." But hidden inside is a huge problem for the majority of Government contractors.

On August 20, 2009 a proposed revision to the Federal Acquisition Regulation (FAR) was published with the innocuous title of "FAR Case 2008-020, Contract Closeout." Although some aspects of the proposed rule change did, in fact, address contract close-out activities, the majority of the language turned out to be a "wolf in sheep's clothing" that, if implemented as drafted, will significantly expand the powers of DCAA, and will force contractors to comply with arbitrary DCAA demands or risk monetary penalties.

The Good

Nearly five years ago (in 2005) the Federal government was concerned with the seeming inability of the contracting parties to close-out contracts after physical completion of the work. The administrative issues involved in the contract close-out process, including those related to finalization of indirect cost rates, seemed to defeat the best efforts of both contractor and Government employees. As a result, hundreds and even thousands of physically completed contracts were lingering on the Government's books like guests who wouldn't leave a party. Since the majority of those lingering contracts were "flexibly priced" types, that situation meant the Federal government didn't have a good handle on how much it might still owe its contractors--or whether those contractors owed it a refund based on their "final costs incurred." The financial situation was unclear and that prevented the agencies of the Executive Branch (DOD in particular) from generating accurate financial statements.

This was back in the day when the contracting parties still aimed for "partnering" with each other to overcome the mutual challenges of performing the contracted work. (In today's environment, such alignment is called an "independence violation" and "lack of oversight.") The Defense Acquisition Regulation (DAR) Council (aka DARC) asked contractors to meet with them and identify opportunities to better the contract close-out process so that more contracts could be closed-out faster. Input into that forum can be found here.

The DAR Council and others in the DOD mulled over the input for two years and, in 2007, came up with some recommendations to improve the process. In the words of the FAR Council, "The assessment resulted in recommendations for revisions to policy, guidance, and training related to contract closeout responsibilities in both the FAR and DFARS. The DARC opened DFARS Case 2007-D015 and recommended changes to the DFARS text and PGI documents." Government rule-making being what it is, it took an additional two years to get to the point where, on August 20, 2009 a proposed rule was published for public comment.

The foregoing is the background to why the proposed rule has the title it does, and why it contains some language that will be helpful to contractors. Some of the helpful language includes:

Revises FAR Part 4 to require clearing of final patent reports within 60 days of receipt. If a required patent report is not received, permits the Contracting Officer to proceed with contract close-out actions "upon consultation with the agency legal counsel responsible for patent matters."

  • Revises FAR 42.708 (Quick-closeout Procedure) to increase the dollar value limit of "unsettled indirect and direct costs" that qualify a contract action for quick close-out, from $1 million to $4 million.
  • Provides more detailed guidance to Contracting Officers regarding the "risk assessment" to be performed when evaluating whether to utilize quick close-out procedures.

The above revisions are helpful but, in a seeming , quid pro quo, the FAR Council asks contractors to accept extremely unhelpful regulatory changes along with the helpful one.


The Bad

Currently, the FAR permits Contracting Officers to withhold some portion of the fixed fee owed a contractor, "in an amount necessary to protect the Government's interest [but the amount] shall not exceed 15 percent of the total fixed fee or $100,000, whichever is less." (See the clauses 52.216-8, 51.216-9, and 52.216-10.) Importantly the clauses directs the Contracting Officer to release "75 percent of all fee withholds under this contract after receipt of the certified final indirect cost rate proposal covering the year of physical completion of this contract."

This new rule proposes to revise those three contract clauses so as to "encourage the timely submission of an adequate indirect cost rate proposal." The revised language does that, and more.

For example, the revised clause language at 52.216-8 (Fixed Fee) now reads (in part):

"The Contracting Officer shall release 75 percent of all fee withholds under this contract after receipt of an adequate certified final indirect cost rate proposal covering the year of physical completion of this contract, provided the Contractor has satisfied all other contract terms and conditions, including the submission of the final patent and royalty reports, and is not delinquent in submitting final vouchers on prior years’ settlements. The Contracting Officer may release up to 90 percent of the fee withholds under this contract based on the Contractor’s past performance related to the submission and settlement of final indirect cost rate proposals."

Accordingly, if the proposed rule is finalized as drafted, contractors, fees will become hostage to the DCAA's determination that their final indirect cost proposals are, in the subjective judgment of the auditor, "adequate" for audit. What constitutes an "adequate" submission, one might wonder?

The Ugly

What constitutes an "adequate" final indirect cost proposal is discussed at FAR 42.705-1.

The FAR says "The required content of the proposal and supporting data will vary depending on such factors as business type, size, and accounting system capabilities. The contractor, contracting officer, and auditor must work together to make the proposal, audit, and negotiation process as efficient as possible. ... A contractor shall support its proposal with adequate supporting data. For guidance on what generally constitutes an adequate final indirect cost rate proposal and supporting data, contractors should refer to the Model Incurred Cost Proposal in Chapter 6 of the Defense Contract Audit Agency Pamphlet No. 7641.90, Information for Contractors, available via the Internet at DCAA.

It is clear in the current FAR language that the DCAA "model incurred cost proposal" is "guidance" and absolute conformity is not mandatory for a determination of "adequacy." Indeed, the FAR acknowledges that "the required content ... will vary" by contractor.

The proposed rule will change all that, if finalized as drafted. The proposed rule defines an "adequate" proposal is great detail and, not coincidentally, the definition of adequacy is taken, word for word, directly from the DCAA's model incurred cost proposal. No more will contractors be able to adjust their proposals to match their business systems and cost accounting practices; they will be forced to comply in all respects with the DCAA's idea of an "adequate" submission, without regard to what makes sense for the contractor given its business type, size, and accounting system capabilities. This will undoubtedly impact many contractors and will disrupt their operations. To the extent that they will need to revise business systems and processes, or add resources, to meet these new requirements, it will increase the costs of doing business with the Federal government.

Although the Federal Register notice claims this proposed rule revision is "not a significant regulatory action," nothing could be further from the truth.

The other problem with this rule making effort is that it continues the recent trend of DCAA inserting itself into the procurement process, establishing a situation where DCAA's decisions affect the ability of the contracting parties to comply with contract terms. Whereas a decision by the Contracting Officer is subject to appeal under the Contract Disputes Act, there is no such appeal from a DCAA auditor's decision. Regardless of how arbitrary or capricious the DCAA decision regarding "adequacy" may be, it cannot be reviewed by any judicial entity -- which upsets the careful system of checks and balances established by the three branches of Federal government through the Contract Disputes Act and similar statutes.

Find the proposed rule here.

Comment on the proposed rule at regulations.gov.

or via mail following the detailed instructions in the proposed rule.

 

Northrop Grumman to Sell TASC Consulting Business

E-mail Print PDF
On August 20, 2009 the Wall Street Journal reported that Northrop Grumman had announced it was seeking a buyer for its TASC consulting business.  TASC is based in Herndon, Virginia, and employs roughly 5,000 people.  Insiders say Northrop Grumman is hoping to sell the unit for $1 billion, and has retained Goldman Sachs and Credit Suisse Group AG as advisers.  The Wall Street Journal article says that a deal for TASC could emerge by the end of September, and "private-equity firms are among the interested parties."

Why sell now?  There are clearly several meta-trends that could impact TASC's business model.

1.  Conflict of interest rules.  In May, Congress moved to close conflict-of-interest (COI) loopholes by tightening the standards to be applied to contractor employee who act as augmented staff to the Federal workforce.  Cutbacks in Federal acquisition and program management staff over the past 15 years have resulted in a need to hire contractors to do what had formerly been "inherently governmental" functions such as designing specifications, determining technical needs, and developing solicitations.  Clearly, companies (such as Northrop Grumman) that both supplied staff and submitted bids faced potential COI issues (which can be mitigated); but the tougher rules would tend to make it harder to keep from straying over the line.  Significantly, TASC's competition includes Booz-Allen Hamilton, who does not offer military hardware.  TASC is in the unenviable position of being denied advisory opportunities in order to protect Northrop Grumman's competitive position, while simultaneously denying Northrop Grumman bid opportunities because of TASC's existing advisory role.  Splitting the entities is in the best interest of both.

2.  Insourcing.  Recognizing that the Pentagon may have relied too much on contractors to fill its staffing shortages, SecDef Gates recently announced an intention to beef-up his acquisition corps, in order to return thousands of jobs back to the Federal government.  Thus, the need for TASC's services might diminish in the future.

3.  The Obama administration's budget balancing act is just getting started.  Recent reports indicate that the Pentagon has to trim $60 billion, for starters. It is likely that future demand for TASC's services will flatten or decline in the near future.

Given the foregoing, it is no surprise that Northrop Grumman wants to divest TASC.  The question is, given the cloudy future facing defense companies, will NGC get the premium it is hoping for?

When contemplating the acquisition of any business that sells goods and/or services to the Federal government, it is important to evaluate the probability of contingent liabilities, and factor them into the deal.  Government contracts, by their very nature, have long tails.  It can take literally years after completion of the work for "contract close-out" to take place.  Even after contract close-out and receipt of final payment, contract clauses give the Government the right to assert claims for an additional three years.  Thus, after an acquisition an allegation of wrongdoing can surface that relates to actions that took place literally years before.  Records can be missing, personnel may have departed, but the acquiring company still has to deal with the issue(s).  It is critical to structure the deal so as to protect the acquiring entity from such contingent liabilities.  Typically this is done either through purchase price adjustment, establishment of an escrow fund, or both.

During the due diligence phase of the acquisition, it is critical to evaluate existing internal and operational controls, administrative attention to detail, and to try to assess the probability that a contingent liability will surface after acquisition.  Some areas to evaluate include:  compliance with Truth-in-Negotiation Act (TINA), accuracy of timekeeping, accuracy of invoicing preparation, and integrity of the accounting system and related controls.  Note that these areas have limited overlap with Sarbanes-Oxley Section 404 internal controls, and require some degree of expertise in order to properly evaluate.

In addition to the foregoing, considerable thought must be given to the post-acquisition control environment--particularly even two Government contractors are merging.  Many operational control systems (e.g., estimating, accounting, billing, EVMS) have existing system descriptions that will need to be revised and resubmitted to Government oversight officials.  The post-acquisition entity will need to allocate indirect costs and to calculate indirect cost rates; the cost impact(s) of the new rates on existing contracts cannot be ignored.  Moreover, should one or both of the entities be subject to Cost Accounting Standards (CAS), then any changes to cost accounting practice must be carefully coordinated with Government customers, and may require revision of CASB Disclosure Statements and calculation of contract cost impacts in accordance with complex and very detailed process rules.  In sum, there is quite a bit to think about and the traditional business-to-business M&A due diligence does not really address the necessary issues.

Northrop Grumman is putting its TASC unit up for sale.  They want to receive top-dollar (reportedly, $1 billion) for the business.  Interested suitors will need to carefully weigh a myriad of detailed issues, as well as the impact of several mega-trends, when creating an offer.  It will be interesting to see whether a deal that satisfies--and protects--both parties will be struck.
 

AEHF … WTF?

E-mail Print PDF

On August 17, 2009 DefenseNews.com published an article (authored by William Matthews) that had such an eye-catching lead-in, we had to see for ourselves whether or not it was for real.  The article started as follows:

 

In April, U.S. Defense Secretary Robert Gates terminated TSAT, an ambitious communications satellite program that was over budget, behind schedule and plagued by technical problems.  In its place, he substituted AEHF - the Advanced Extremely High Frequency satellite - a less ambitious communications satellite program that also is over budget, behind schedule and plagued by technical problems. … TSAT, the Transformational Satellite communications system, cost U.S. taxpayers $2.5 billion before Gates pulled its plug. AEHF was expected to cost $5.6 billion in 2001 when the program was getting under way, but today the price tag is more than $10 billion for fewer satellites, according to the Government Accountability Office (GAO).  TSAT was at least four years behind schedule. Launch of the first satellite had been pushed back to 2019.  The first AEHF was supposed to be launched in 2008, then 2009, and now Lockheed is aiming for late 2010.

 

Now that’s how to write a story!  So what’s the story behind the story?  Let’s look.SPAC Satellite AEHF Concept

 

The Advanced Extremely High Frequency (AEHF) satellite is designed to replace the 20 year-old MILSTAR military satellite communication system by providing “near-worldwide, secure, survivable satellite communications to support strategic and tactical forces of the United States and its international partners during all levels of conflict,” according to globalsecurity.org.  The website notes that the AEHF system will provide 12 times the data throughput of the MILSTAR system, so that “for every one link of the old Milstar, the Air Force now has 12 operating at four times the speed.”

 

After the loss of MILSTAR Flight 3 in April, 1999, the Department of Defense (DOD) created the AEHF program consisting of a consortium of Lockheed Martin, Hughes Aircraft Co., and TRW (now Northrop Grumman).  GlobalSecurity.org reports that –

 

On 16 November 2001 the U.S. Air Force awarded a $2.698 billion System Development and Demonstration [SDD] contract for the Advanced Extremely High Frequency satellite program to a team comprised of Lockheed Martin Corp., Lockheed Martin Missiles and Space, Sunnyvale, Calif. and TRW Inc., Space and Electronics, Redondo Beach, Calif. The contractor team is led by Lockheed Martin as the prime integrator and provider of the Spacecraft Bus and ground command and control segments with TRW providing the satellite payload. The contract will culminate in the delivery of two AEHF satellites and the ground command and control system. The first of two satellites under this contract was scheduled for launch in 2006.

 

Since early system definition studies in 1999, the AEHF program has gone through a series of design changes.  For example, GlobalSecurity.org reports that on May 18, 2004 Lockheed Martin Corp., Space Systems Co. and Northrop Grumman Space Technology, were (together) awarded a $149 million contract modification which incorporated within-scope changes resulting from a revision to the AEHF KI-54 Cryptographic Interface Control Document (ICD). The KI-54 ICD modification required to AEHF team to redesign the Host Accessory Logic Application Specific Integrated Circuit (HAL ASIC) in the AEHF communication payload. This effort also led to a four months program extension.  In December 2004, the U.S. Air Force reported that the AEHF program had experienced unavoidable delays and cost growth because of delayed delivery of signal-encryption products, which had resulted in a delay of command and control terminals. As a result of these schedule impacts, the AEHF program was delayed by 12 months.  Additional reports noted that the program incurred cost growth from unplanned payload component testing and replacement of existing critical electronic components that were disqualified for space flight. The cost and schedule impacts were expected to increase the overall cost of the AEHF program by roughly 20 percent.

 

The number of planned AEHF satellites has fluctuated over time as well.  The original SDD contract called for a “pathfinder” satellite followed by four, higher-capability, satellites, for a total constellation of five.  In reality, the number of AEHF satellites would depend on the progress of another satellite program, the “transformational” communication satellite, or TSAT, program.  In 2002 the Air Force decided not to acquire two AEHF satellites.  In October 2004 the Air Force decided not to acquire the fourth AEHF satellite in order to proceed more quickly with the TSAT program.  The TSAT program was terminated by Secretary of Defense Gates in October 2008, after incurring approximately $2.5 billion in costs.  (DefenseNews.com reported that the TSAT program was “at least four years behind schedule” and that “launch of the first satellite had been pushed back to 2019” at the time of program termination.)  In 2005 a third satellite was added back to the program, at a reported cost of $491 million.  After the TSAT program termination a fourth AEHF satellite was added back to the program resulting in additional cost and schedule impacts that triggered a “Nunn-McCurdy” breach and mandatory Pentagon program review.  According to a September 2008 article in Aviation Week & Space Technology, “The fourth satellite accounts for four-fifths of the FY '09 cost increase in the program. The spacecraft's high price is due to the expense associated with restarting Lockheed Martin's production line.”

 

Impacts to the program’s cost and schedule, as well as the impacts from the fluctuating number of satellites, compelled the contractors to initiate a program “rebaseline” or “replan” that resulted, in April 2006, in an $454.9 million contract modification to compensate the contractors for the changes as well as the delay of the first AEHF launch date from 2006 to April 2008.  Current reports indicate a planned launch date of 2010 with a total program cost of $9.2 billion.

 

So to sum up, the DefenseNews.com article had its facts correct, but seems to have taken them out of context.  Like many high-tech developmental programs, the AEHF program has been the victim of Pentagon budget wars.  While the program undoubtedly suffered from many of the pains associated with trying put a highly secure, classified payload into space, it also suffered from a lack of firm strategic leadership from the Pentagon.  The fluctuations in the number of satellites and budgetary uncertainty clearly impacted the contractors at least as much (if not more) than the technical challenges.  While it might serve as a good example of out-of-control defense programs, it might also serve as a good example of the impacts of failed leadership.  It seems that the DefenseNews.com article missed the mark, choosing to take cheap shots rather than dig for the truth.

 

Is the Vulcan Hypersonic Engine a Game-Changer?

E-mail Print PDF

DARPAIn May 2009 the Defense Advanced Projects Research Agency (DARPA) announced the kick-off of its Vulcan program by awarding eight-month system requirements development contracts to four contractors:  Alliant TechSystems (ATK), General Electric (GE), Rolls Royce, and United Technologies Corporation (UTC).  The Vulcan program aims to develop a “constant volume combustion” (CVC) engine that will accelerate a vehicle from rest to Mach 4+.  (Some reports say the program aims to achieve Mach 6, which would be equal to a true airspeed of about 3,700 at a flight level of 50,000 feet, or a true airspeed of about 4,600 MPH at sea level.  In other words, Vulcan aircraft will be very fast.)  According to DARPA, the Vulcan engine will integrate an existing production turbine engine (such as a F100-229, F110-129, F119 or F414 engine) with a CVC engine.  DARPA says that the Vulcan engine will “enable full scale hypersonic cruise vehicles for intelligence, surveillance, reconnaissance, strike, or other critical national missions.”  A DARPA briefing calls the Vulcan engine “a game changer.”Vulcan Engine Logo

 

This concept has been described as the integrated combination of a turbo jet and a scramjet.  Current engines, including advance turbine engines, operate on the principle of constant pressure combustion (CPC).  According to DARPA, CVC engines “offer potentially very significant performance improvements over conventional cycles, have the ability to operate statically through high Mach numbers and offer significant design flexibility.”  In particular, CVC engines should be able to achieve a 35% improvement in thermal efficiency when compared to traditional CPC engines.  However, an aircraft needs to attain Mach 2+ before the CVC engine can begin to operate.  Thus, the need to combine a traditional turbine engine with the CVC engine in order to provide continuous thrust from take-off through the higher Mach velocities.  DARPA states that a key objective of the program will be ”to integrate the turbine engine into the Vulcan engine system with minimal modification to the turbine engine, operate the turbine engine from rest to its upper Mach limit and cocoon the turbine engine when it is not in use during flight.”  DARPA’s vision is that the turbine and CVC engines will share a common inlet and nozzle.

 

There are, of course, technical challenges that will need to be overcome.  As DARPA itself notes, the challenges include “efficient detonation initiation, low total pressure loss detonation initiation devices, low total pressure loss air valves, thermal management systems, efficient nozzles, and control systems.” Among the other challenges is deciding on the appropriate configuration for the CVC engine, which could consist of pulsed detonation engines (PDEs), Continuous Detonation Engines (CDEs), or another “unsteady CVC” method.

 

Flight International magazine (FlightGlobal.com) reports that the Vulcan configuration decision will be made in December 2009.  According to a FlightGlobal.com report,

 

The Vulcan's configuration will be selected from a number of different options, some of which were presented at the American Institute of Aeronautics and Astronautics' 45th Joint Propulsion Conference held in Denver, Colorado. What is decided is that the engine will use a turbojet and a constant volume combustion engine (CVC) in combination. Examples of CVC are Continuous Detonation Engines (CDE) and Pulse Detonation Engines (PDE). The basic operation for a CDE or PDE is a propellant injected into a tube, open at one end and the fuel is ignited. The detonation wave travelling down the tube generates the thrust.

 

After selection of the configuration, the program will begin an eighteen-month Phase 2 to include preliminary design, trade studies, and a demonstration of the CVC components.  Phase 3 is forecasted to last another eighteen months and will include detailed designs, simulations, and tests of the CVC engine components.  Phase 4 (another 18-month phase) will include fabrication, assembly and test/demonstration of the integrated Vulcan engine.  If all goes according to plan, by 2014 the Vulcan engine should be proven and demonstrated technology.Vulcan Engine Timeline

 

At that point, we should know whether the Vulcan engine is truly the “game changer” that DARPA believes it can be.

 

Recipients of Recovery Act Funds -- Time to Register!

E-mail Print PDF
Effective August 17, 2009 recipients (and sub-recipients) of American Recovery and Reinvestment (ARRA) funds are required to begin to register at FederalReporting.gov
.  This is the Federal government's website that acts as a central government-wide data collection system for both Federal agencies and recipients of Federal awards under Section 1512 of ARRA.  Recipients (and sub-recipients) are required to register on the site, and then to enter required data on a quarterly basis for Recovery Act grants, loans, and contracts they have received.  The first reporting period will begin October 1 and end October 10, 2009.  Effective October 11, 2009 the public will be able to view information via the Recovery.gov website. But prior to registering at the FederalReporting.gov website, recipients must first jump through a few hoops.  Prime recipients (those that receive funds directly from the Federal government) must first do the following steps prior to registering:

  1.  Have a valid email address.
  2.  Obtain a 9-digit DUNS number from the Dun & Bradstreet website here.
  3.  Register in the Federal government's Central Contractor Registration (CCR) database here.

For sub-recipients (those that receive funds from a prime recipient) the pre-registration steps are identical to those for prime recipients.  For reporting, the subs will need to also know their prime's DUNS number and Award number.

This is a bold experiment in Federal contract transparency, and it is likely there will be some initial "bumps" as the process is implemented.  To help ease the strain, the Recovery Accountability and Transparency Board has created a "Recipient Reporting Data Model" to standardize reporting data.  The Recipient Reporting Data Model can be downloaded from the "Downloads" tab of FederalReporting.gov and is also accessible via Recovery.gov.

There are other interesting challenges involved in entering and reporting use of Recovery Act funds.  For example, GovExec.com reports that "The 28 federal agencies that have distributed the stimulus funds also must sign up at FederalReporting.gov to review information submitted by recipients and discuss with them any errors or corrections. While agencies can view the information, only recipients will be able to change the data once it is submitted, and only for a short period of time after the Oct. 10 reporting dead-line.".  The same article also notes that "The [Recovery Accountability and Transparency] board expects 150,000 to 200,000 recipients to file reports by the Oct. 10 deadline."

Recipients and sub-recipients should begin the registration process now and get familiar with the Recipient Reporting Data Model, in order to ensure that they are reporting accurate information on time, and in the right format, beginning October 1st.  Although it is not clear whether the Federal government will be able to identify those recipients who fail to report, it is a near certainty that those recalcitrant recipients that are identified may be accused of breaching the terms and conditions of their Recovery fund award, and that may lead to a "rough ride" that is otherwise completely avoidable.  Just as importantly, recipients and sub-recipients must ensure that they have implemented internal accounting and other operational control systems to track how their Recovery Act funds are used.
 


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