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

Truth is Stranger than Fiction, or: A Conversation with a DCAA Auditor

E-mail Print PDF

Truth

Warning: The following conversation did not take place as written. Instead, what follows is a “reality-based” conversation that mashes-up several conversations and e-mail discussions that really, really, really did take place in real life. Details have been changed to protect client confidentiality. But seriously, this is as accurate as we could make it.

DCAA Auditor: Hi there! We are performing an audit of your client’s FY 2002 incurred cost proposal, submitted in June, 2003. We have a few questions; please see the attached Request for Information (RFI) which contains our initial data request. In addition, we would like to have an entrance conference with your client’s accounting management in order to discuss the go-forward plan.

Apogee Consulting, Inc.: Wait, what? Is this a typo? Do you really mean FY 2002 and not some other year? That was a decade ago! Plus, our client says that DCAA already performed the FY 2002 incurred cost audit several years ago. In fact, our client says that the work was performed and a draft audit report was generated (see attached draft audit report). There was an exit conference! In addition, our client provided comments, disagreeing with several of the findings (see attached client response to draft audit report). Our client has been waiting for six years for the final audit report to be issued and for negotiations with the Administrative Contracting Officer (ACO) to begin. Further, my client sent the Supervisory Auditor several emails over the past six years, inquiring as to the status of the final report. Each reply said the audit report was in “management review”. The last email from DCAA was dated two years ago (see attached email). What’s going on?

DCAA: Yes, well. DCAA discontinued working on incurred cost audits a few years ago, due to other priority assignments. We are now starting the process again for certain incurred cost audits, and your client’s FY 2002 assignment has been selected for audit (or, in this case, continuation of the audit). Though the audit was essentially completed by another auditor in 2006, it was never officially completed. So now I have to go back through the working papers and determine if additional work needs to be performed, based on our current Agency guidance.

Apogee: So you are going to evaluate the work done six or more years ago in light of your current HQ guidance regarding working paper documentation, sampling size, and other matters? Really? You do realize that a decade has passed, right? Most of the people who prepared the submission, or processed the accounting transactions, retired a while ago. What is the likelihood we are going to have the supporting documentation you now consider to be required, with a decade of hindsight? This makes no sense! Is this really what you are being told to do? Really?

DCAA: Yes, really. And my first question is: Where is your client located? I can’t find that in the working papers. And once I know where your client is located, we’ll schedule the entrance conference.

Apogee: Oh, this is so not going to go well.

*****

[Entrance Conference]

DCAA Audit Supervisor: So, as you can see, we have classified your client as “high risk” because this will be the first in-depth incurred cost audit performed by the Agency. As such, we will sample the maximum amount of transactions.

Apogee: What about the prior year’s costs? You audited those, didn’t you?

DCAA: Yes, but that was a desk audit. It doesn’t count.

Apogee: So you are saying that you will re-perform the work you’ve already performed, only more so?

DCAA: Yes, well. Not every account will be retested. We are only going to look at the accounts where we previously had findings.

Apogee: So if you didn’t have any findings, you will not re-perform the testing on those accounts?

DCAA: Yes, that’s correct.

Apogee (thinks to self, does NOT say out loud): Well, that’s just stupid. If the past procedures were inadequate, you should look where you didn’t find anything. Looking where you already had findings—and projected to the universe from those findings—shouldn’t generate very much more in questioned costs. This approach is flawed, but it makes us very happy.

Apogee (says out loud): We understand.

*****

[Field Work Commences]

DCAA Auditor: Hi, here is an RFI that requests all your policies and procedures related to accounting, billing, timekeeping, purchasing, estimating, and property control. In addition, please provide detailed information regarding the compensation of your top 5 most highly compensated executives, including a break-out of corporate revenue showing how much revenue each executive was responsible for. Plus, tell me if you had a Defined-Benefit pension plan.

Apogee Consulting, Inc.: Hi! No problem! Here are all the policies and procedures you requested. Here is the compensation information you requested. Our client did not have a Defined-Benefit pension plan.

DCAA: No, this won’t do. It won’t do at all. You provided current policies and procedures. We need to see policies and procedures from FY 2002. Plus you didn’t provide the revenue break-out we requested.

Apogee: We are trying to find the policies and procedures that were in effect a decade ago. Our client didn’t retain them. Plus nobody here knows or remembers how to apportion the revenue amongst the top 5 executives. That wasn’t how the company was managed at the time.

DCAA: What do you mean you don’t have FY 2002 policies and procedures? Doesn’t your client understand the FAR record retention requirements? What do you mean you can’t break-out the revenue the way we requested?

Apogee: Yes, our client understands the requirements of FAR 4.7. But you have to understand that our client thought the audit work on that year had already been completed. Our client thought that was the case because there was a draft audit report and an exit conference. So nobody thought there was any reason to keep the old policies and procedures. We are trying to see if somebody kept a set by accident. If we find them, we’ll provide them to you.

DCAA: This is going to be a problem. I need those policies and procedures to complete my risk assessment.

Apogee: Risk assessment? Didn’t your Supervisory Auditor say our client had been assessed as “high risk”? Doesn’t that mean you’ve already completed the risk assessment? Are you saying you are still working on the risk assessment even after you’ve concluded on the risk level?

DCAA: Well, our new audit procedures now include a new working paper entitled “Gain an Understanding of the Contractor’s Internal Controls.” We need to document our understanding so that we can show compliance with GAGAS 6.10. If you don’t have the policies and procedures, how am I supposed to document that I understand the applicable internal controls?

Apogee: Well, didn’t DCAA perform a full-scope post-award accounting system review in FY 2003, and found the client’s overall control environment and the accounting system to be “adequate”? Can’t you rely on that audit to document compliance with GAGAS 6.10?

DCAA: No, we can’t do that. The audit was in the wrong year. We are auditing FY 2002 and not FY 2003.

Apogee: You’re kidding us, right? You can’t rely on your own Agency’s work?

DCAA: No. I thought that if your client could document that there were no changes to the internal control systems between FY 2002 and FY 2003 that might work. But then I reviewed the working papers of the accounting system review and, unfortunately, they are not compliant with current working paper standards. So we can’t rely on that audit work, not even for the FY 2003 incurred cost audit—which we will be starting as soon as we wrap-up the details for FY 2002. In fact, our FAO told the Region that we would have both FY 2002 and FY 2003 finished by the end of September.

Apogee (thinks to self): Yeah, good luck with that. We’re not even sure we can find the transaction support once you identify what you want to see. Everything’s in storage. Everything, that is, that wasn’t purged years ago.

Apogee (says out loud): Well, our client will do the best it can.

DCAA: Let me discuss this with my Supervisor. We’re supposed to wrap-up 2002 and 2003 by September, and then start on FY 2004 and FY 2005.

Apogee: FY 2005?

DCAA: Yes. That’s the plan.

Apogee: There is no FY 2005. Our client was acquired by Mega-Defense Corp. in late 2004 and was consolidated into Mega’s accounting system effective FY 2005. There’s nothing to audit.

DCAA (quietly): Oh.

Apogee: In fact, Mega-Defense Corp. has already negotiated final costs on the majority of the flexibly priced contracts you are auditing.

DCAA: How could that have happened? Your client doesn’t have final indirect rates for those years!

Apogee: True. But the customers got tired of waiting and they didn’t like having obligations open … something about expiring funds. So they simply negotiated and closed the contracts. We think they may have used your draft audit report from FY 2002, but we’re not really sure. It was a long time ago and most of the negotiators retired last year.

DCAA (quietly): Oh. I need to let my Supervisor know this. It will definitely affect our risk assessment.

Apogee (thinks to self): Yeah, you mean the risk assessment that you already concluded was “high risk” because you didn’t have an audit history. An audit history that you couldn’t rely on in any case, because the working papers didn’t meet your current standards. That risk assessment?

Apogee (says out loud): Well, let us know if you need any more information.

*****

THE STORY CONTINUES

 

DCAA Director Defends Derelict Defense Audit Agency

E-mail Print PDF

On June 10, 2012, Sarah Chacko wrote an editorial in Federal Times regarding DCAA’s problematic backlog of unperformed and uncompleted audits. Entitled “DCAA Must Balance Quality and Quantity—And Soon,” Ms. Chacko’s editorial took DCAA to task for the lack of audit productivity. She wrote—

Four years ago, lawmakers ordered Pentagon officials to overhaul how their auditors review contracts to make sure costs are reasonable. Their chief complaint: Auditors were more concerned with being speedy than thorough. … Now the problem is that DCAA auditors are being thorough to a fault. They are devoting more attention to each audit, but performing dramatically fewer audits. And that is even after the agency hired 615 additional staff members since 2008 for a total of 4,876 as of last year. … In short, a far smaller portion of transactions conducted between the Pentagon and its contractors is getting any scrutiny, despite a huge DCAA staffing increase and skyrocketing costs. …

DCAA must find a better balance between quantity and quality in its auditing operation. Quality is great, but a quest for perfection is impractical, slows the process and costs the taxpayers large sums. … And DCAA must act fast: As the backlog swells even more, billions of dollars of improper payments will be lost and unrecoverable.

Readers will recognize the issues at the heart of Ms. Chacko’s concerns. After all, we’ve devoted several articles to the topic and spent at least three articles exploring DCAA’s audit productivity metrics, as expressed in its FY 2011 Annual Report to Congress. Suffice to say that we find little in Ms. Chacko’s editorial with which to disagree.

That said, the Director of DCAA, the Honorable Patrick Fitzgerald, wrote a letter to the Federal Times editor to express his disagreement with Ms. Chacko’s concerns about current DCAA policy—a policy that seems to favor audit file working paper documentation over performance of actual audits.

Director Fitzgerald wrote—

In defense of DCAA … you neglected to consider important points that would give a more accurate picture of the Defense Contract Audit Agency’s effectiveness and productivity.

To use the number of audits completed as your basis for evaluation isn’t valid for two reasons. First, you imply that our performance standard should be the number of audits DCAA was completing at the time it was criticized by the Government Accountability Office. This just isn’t where our agency needs to be. Second, doing more audits does not automatically result in more savings. In reality, the amount of net savings is one of the most tangible benefits of our audit work. … Although we issued about 75 percent fewer audit reports and examined fewer dollars, we questioned more costs on a percentage basis. …

We know there is a sizable incurred-cost workload ahead of us, and we are executing a plan to eliminate the backlog as quickly as possible while still addressing the taxpayer’s interest. We are making good progress. …

Well, we could take issue with just about every one of Director Fitzgerald’s points. But instead, let’s approach this from a slightly different vector.

If one were to go back to the 2008/2009 GAO and DOD IG reports that formed the basis of the criticism to which DCAA (over) reacted, one would not find much (if any) criticism regarding the quantity of audits being performed. Instead, one would find two primary criticisms—(1) audit conclusions and opinions that lacked sufficient supporting evidence, and (2) supervisory changes to auditor conclusions and opinions that lacked sufficient supporting evidence. Sure, there were ancillary issues such as allegations of workforce intimidation and attempts to impede the GAO audit. There were unsupported allegations that DOD buying command and contractors improperly influenced the scope of certain audits. But the main thrust of the criticism was that DCAA was not complying with Generally Accepted Government Auditing Standards (GAGAS) because its audits lacked evidentiary support for the conclusions reached. The focus was on poor audit quality, and did not speak to whether the audits were or were not performed too quickly.

The issues regarding an alleged undue focus on audit productivity metrics were raised during testimony before Congress. Then-Director April Stephenson and her Executive leadership team decided—on their own—that a management focus on productivity metrics were a cause of poor audit quality. Then-Director Stephenson and her Executive leadership team decided—on their own—that they would stop measuring audit completion cycle times. Then-Director Stephenson and her Executive leadership team decided—on their own—that they would comply with GAGAS (as they interpreted the Standards) by focusing on working paper documentation. Then-Director Stephenson and her Executive leadership team decided—on their own—to focus on reviews of contractor interim vouchers and contractor internal control “business systems.” This was a course initially charted by Then-Director Stephenson and her Executive leadership team, and subsequently continued by Director Fitzgerald and his Executive leadership team (which is essentially the same Executive leadership team he inherited from Stephenson).

Director Fitzgerald’s letter to the editor noted that “contracting officers are continuing to uphold a majority of [DCAA’s] questioned costs.” Readers should take that statement with a grain of salt, remembering that in March, 2009, DCAA HQ issued policy guidance to its auditors directing them to report uncooperative DCMA contracting officers to the DOD Inspector General. This audit guidance was characterized by one respected government contracting attorney as introducing “a new level of formality in DCAA’s unceasing quest to intimidate and control contracting officers in the exercise of their discretion.”

In addition to the foregoing, it is DOD policy that significant disagreements between DCMA contracting officers and DCAA auditors will be elevated for review and adjudication. No employee wants that level of management scrutiny. So it should be unsurprising that DCMA contracting officers are very, very reluctant to disagree with anything DCAA may have to say, regardless of their personal feelings and regardless of the FAR mandate that they exercise independent business judgment and discretion.

In sum, Director Fitzgerald may think he has the audit agency on the right path. But if so, he may be alone in that regard. We think that most observers are more closely aligned with Ms. Chacko’s concerns about a growing backlog and a seemingly fanatical focus on administrative minutiae at the expense of audit performance. Most observers we know think that DCAA is on the wrong path, has misinterpreted GAGAS, and has focused on the wrong things, at the expense of its fundamental mission.

 

 

DOD Implements Limits on Prices Paid for Contracted Services

E-mail Print PDF

We have devoted several blog articles to the question as to whether or not the Federal government’s use of contracted (“outsourced”) services results in any cost savings. As we reported, opinions vary. The Project on Government Oversight (POGO) had an opinion; so did the Government Accountability Office (GAO); so did the Congressional Budget Office (CBO). Opinions varied and we suggested that our readers should look at the various studies and reach their own conclusions.

In the meantime, Congress has spoken. In a little-known section of the FY 2012 National Defense Authorization Act, Congress imposed “a temporary limitation” on the amount of funds available for contracted services by Department of Defense. The Public Law reads—

Except as provided in subsection (b), the total amount obligated by the Department of Defense for contract services in fiscal year 2012 or 2013 may not exceed the total amount requested for the Department for contract services in the budget of the President for fiscal year 2010 (as submitted to Congress …) adjusted for net transfers from funding for overseas contingency operations.

In addition, Congress directed the Secretary of Defense as follows—

Not later than 60 days after the date of the enactment of this Act, the Secretary shall issue guidance to the military departments and the Defense Agencies on implementation of this section during fiscal years 2012 and 2013. The guidance shall, at a minimum—
(1) establish a negotiation objective that labor rates and overhead rates in any contract or task order for contract services with an estimated value in excess of $10,000,000 awarded to a contractor in fiscal year 2012 or 2013 shall not exceed labor rates and overhead rates paid to the contractor for contract services in fiscal year 2010;

(2) require the Secretaries of the military departments and the heads of the Defense Agencies to approve in writing any contract or task order for contract services with an estimated value in excess of $10,000,000 awarded to a contractor in fiscal year 2012 or 2013 that provides for continuing services at an annual cost that exceeds the annual cost paid by the military department or Defense Agency concerned for the same or similar services in fiscal year 2010;

As contractors have been discovering this little landmine buried in the Public Law, they have become concerned that overzealous contracting officers might use the foregoing to limit any contractor increases to direct labor rates and/or to indirect cost rates. A careful reading of the language should clarify that the statute does not impose any such limits; instead, it requires that such limits be used to establish the government’s negotiation objectives.

That is not at all the same thing. The government may establish for itself any negotiation objective it wishes; that does not mean government negotiators will achieve those goals.

In order to comply with the statutory requirement, the DOD could not wait for the usual rule-making bodies to act. Instead, the Defense Procurement and Acquisition Policy (DPAP) Directorate issued a Class Deviation in June, 2012. The Class Deviation essentially reiterates the statutory language quoted above, and notes that the Class Deviation will “remain in effect until incorporated in the FAR or DFARS, or rescinded.”

The thing is, why would this ever need to be in the FAR or DFARS? The statute required that “guidance” be issued, and so it was issued. Nothing more need be done. In fact, we would assert that “guidance” doesn’t belong in the FAR or DFARS. If DPAP thinks it’s necessary to codify the guidance, then the proper place for it would be in the DOD PGI (Procedures, Guidance, and Information). That may sound like a bit of a nitpick (and perhaps it is). But the folks at DPAP are supposed to be the top regulatory policy and rule-makers at DOD, and they are not supposed to make mistakes like that. (If it wasn’t a mistake and they really do think that the proper place for “guidance” is in the FAR or DFARS, then Heaven help us all.)

One might wonder why Congress felt it was necessary to implement such funding controls over outsourced DOD services. According to the Senate Conference Report (helpfully provided at the WIFCON website)—

The efficiencies initiatives announced by the Secretary of Defense on August 9, 2010, included a 3-year, 10 percent per year reduction in support contractors performing `staff augmentation services' and a 3-year freeze on DOD civilian personnel. The committee notes that `staff augmentation services' has a subjective definition, and this category of contractors is not tracked in any of the Department's business systems. Moreover, many comparable functions are performed both by civilian employees of the Department and pursuant to contracts for services. Expected savings from the reduction in staff augmentation services and the civilian workforce freeze could easily be lost if other categories of services contracts are permitted to grow without limitation so that spending can shift to these contracts.

Over the last decade, DOD spending for contract services has more than doubled, from $72.0 billion in fiscal year 2000 to more than $150.0 billion (not including spending for overseas contingency operations), while the size of the Department's civilian employee workforce has remained essentially unchanged. The Under Secretary of Defense for Acquisition, Technology, and Logistics testified in September 2010:

`I just tell you, the low-hanging fruit really is [in contract services]. There's a lot of money. There has been a very, very high rate of growth over the last decade, in services. They have grown faster than everything else. . . . So, there's a lot we can do. … I think great savings can be had there, across the Services' spend. It's essential that we look there, because that's half the money.' …

The committee concludes that an across-the-board freeze on DOD spending for contract services comparable to the freeze that the Secretary of Defense has imposed on the civilian workforce is warranted to ensure that the Department maintains an appropriate balance between its civilian and contractor workforces and achieves expected savings from planned reductions to both workforces.

In other words, DOD promised to cut its support contractors as well as its civilian workforce as part of its “Better Buying Power Initiative.” Congress didn’t want those promised cost savings offset by increases in other areas of service contracting. Moreover, DOD officials testified that they could find lots of cost savings in that area; Congress was simply taking them at their words.

In other words, DOD did this to itself. Now they—and defense contractors—need to live with the results.

 

 

DCAA Implements Major Changes to Incurred Cost Audit Program

E-mail Print PDF

DCAA
On May 2, 2012, the Defense Contract Audit Agency issued MRD 12-PPD-014(R), announcing that the audit agency had eliminated the standard audit program for auditing the “incurred costs” of “non-major” contractors. Instead of having two audit programs—one focused on the larger “major” contractors and the other focused on the smaller, less risky, “non-major” contractors—the audit agency will henceforth have only one audit program for performing “incurred cost” audits.

The agency offered no substantive explanation for the change, reporting only that—

As part of Policy’s ongoing assessment of current audit programs supported by the Strategic Plan Ad Hoc on Incurred Cost, an in-depth review of the major and non-major incurred cost audit programs was performed. Based on this assessment, a decision was made to eliminate the non-major incurred cost audit program.

As readers know, we (and others) have opined that DCAA’s policy choices regarding GAGAS compliance and audit prioritization (as well as other choices we could list) have led the audit agency to an untenable place where its backlog of unperformed/uncompleted audits is too large to reduce in any meaningful way. A recent Federal Times editorial suggested that the Contract Disputes Act’s Statute of Limitations would soon render much of the backlog unauditable. That’s not necessarily true, but it’s very possible that the CDA SoL would make any Government action to collect money (allegedly) owed from DCAA audit findings unenforceable in court, should a contractor choose to contest them. So there would be little point to performing the audits.

Some might suggest that DCAA is undertaking this significant reform in order to speed the audits. We don’t know. We did notice that the MRD emphasized (for the first time in recent memory) the use of auditor “professional judgment” in order to “tailor the audit program to efficiently and effectively accomplish the audit objectives.” In fact, the MRD states—

In tailoring the audit program steps, the auditor, in consultation with his or her supervisor, should apply professional judgment, considering the significance of the claimed amounts and known risk factors. Auditors are reminded that the standard audit program provides the overall framework for performing the audit in compliance with GAGAS and it is expected that the program will be tailored for the specific contract audit based on the risk assessment.

So now there is one approach to performing “incurred cost” audits, and it is based on every contractor being as risky as the larger contractors. The funny thing is, DCAA did not extend the logic into other areas. For example, the 10310 audit program, entitled “Audit Program for Non-Major Contractors Labor Floorchecks,” still maintains the distinction between major and non-major contractors. Hmmm….

We have seen it suggested, by self-identified current and former DCAA employees, that the agency intends to reduce its enormous backlog by “risking-away” the smaller dollar value audits. As we told you, one commenter wrote—

Concerning the incurred cost workload, the plan for getting current is to sample the submissions that are less than $250M. Those that are less than $1M will likely never be audited because HQ views those audits as cost losers, which is no wonder given the amount of prepatory work (the risk assessment, increased transaction testing, and the greater number of reviews) now required. HQ is talking about more and more sampling (leaving more submissions completely unaudited), which will certainly incentivize some contractors to push the envelope when it comes to questioned costs. …

Another commenter asserted—

… DCAA wants to waive all possible incurred cost audits under $1 million too. And the metrics will show that we actually completed these audits. Waiving 1 low dollar incurred cost = completing 1 (only in DCAA does 0 = 1). Then there's our audit guidance - all of our audit guidance is being written for the largest contractors. Does our upper management get the risks at the nonmajors especially at a time when there is less spending and companies are going out of business or being bought out? … We can get plenty of these audits done if we had the prior audit programs that were geared towards non-major contractors. The new B2 is overkill and redundant. It's confusing. It's too much for a small contractor where an audit is performed by 1 person. Who really understands it? It's not user-friendly for auditors. Then it appears HQs wants to staff up the largest contractors with more people because that's the only places where risk exists to them. …

Well, we certainly don’t know what’s in the minds of DCAA leadership. Quite possibly the intention is to re-emphasize auditor judgment—a move that we would heartily endorse. Or perhaps, as the commenters quoted above implied, there is an ulterior motive behind the elimination of the “non-major” contractor category with respect to incurred cost audits. Again, we do not know.

But we know that the smaller, formerly “non-major” contractors should prepare themselves for a rough ride.

 

 

Has USAF (Re)Learned How to Evaluate Proposals?

E-mail Print PDF

reaper-targeting
Readers know that we’ve taken the US Air Force to task—more than once—for botched source evaluation and award decisions. The debacle of the KC-X aerial tanker competition was not the only screw-up. More recently, legal maneuvering with regard to the Light Air Support (LAS) competition, evaluation, and award to the team of Sierra Nevada Corporation (SNC) and Embraer has generated several articles on this site—the most recent here.

The LAS story involves a USAF award decision that was “inadequately documented,” a refusal to provide the losing bidder with a debrief (because of an untimely request), a denied protest at GAO, litigation at the Court of Federal Claims, a “Commander Directed Investigation” into the source selection decision, an early termination of the inadequately documented contract award, and a decision to recompete the matter. As we reported, the USAF decided not to conduct a fly-off in the recompete, a decision that Under Secretary for Defense (AT&L) Kendall termed “acquisition malpractice” when it was made with respect to the F-35 JSF program.

It is that decision not to perform flight tests that sparked SNC to file an action of its own at the Court of Federal Claims, seeking to have its terminated contract reinstated. The various stories on SNC’s action all of appear to be strangely similar in wording, almost as if they were all recapping the same SNC press release. Here’s a quote from the story linked-to above—

According to SNC the cancellation of the contract was an extreme response to what appears to be paperwork errors on the part of the USAF. Moreover, the revised Request for Proposal (RFP) issued by the USAF is tilted in favor of the competition. … SNC’s filing also raises specific concerns with the source selection process and revisions to Amendment 8 of the RFP. The new source selection process eliminates any flight demonstration/evaluation and moves the completion of First Article Test (FAT) of production aircraft out until delivery in July 2014.  … The original source selection process included flight demonstrations of training and combat mission profiles and austere field operations. The competition sought non-developmental aircraft, which by definition should be available for evaluation.

Using language that was quite reminiscent of Hawker Beechcraft’s complaints regarding the original source selection decision, SNC Vice President Taco Gilbert was quoted as saying—

‘Despite repeated written and verbal attempts, we have not received adequate explanation – much less justification – for the termination of our contract, the reopening of the LAS competition or the readmission to the LAS competition of our competitor whose submission was previously found to be technically deficient and carry unacceptable mission capability risk.’

Gilbert added—

‘What we seek is a fair and open competition – one where there is a level playing field, one that provides transparency into the decision making process, and one that selects the best value as required by the Request for Proposal. Unfortunately, based on the information we have, we are concerned that this competition will not conform to these goals.’

But while the LAS debacle continues (depriving the warfighters in Southwest Asia with needed ISR capability), the USAF seems to have figured out how to evaluate complex proposals and make protest-proof source selection decisions in other areas. We are referring to the Dismount Detection Radar (DDR) contract award to Raytheon, a decision that was protested by the losing bidder (Northrop Grumman). Northrop’s protest was denied, and the lengthy GAO decision gives us enough details so that we think the USAF evaluators may have (re)learned how to do their job.

According to the GAO decision—

The DDR system is intended to provide a ground moving target indicator capability to detect and track vehicles and dismounts. The system, operating as a pod on the MQ-9 Block 5 Reaper, will allow combatant commanders and their forces to identify and eliminate threats before adversaries engage in harmful activities against the United States and Coalition Forces. … According to the agency, the DDR system is an urgent and compelling need of the warfighter.

The Air Force sought bids from only two companies, Raytheon and Northrop. The decision to limit competition was properly justified, according to the GAO. RFP evaluation factors were clearly articulated, as follows—

Award was to be made to the offeror whose proposal represented the best value to the government based on an integrated assessment of three evaluation factors: (1) schedule; (2) technical capability (comprised of two subfactors, technical performance, and engineering and management integrated processes--technical performance was considered more important); and (3) cost/price. … The schedule factor was more important than the technical capability factor; when combined, these factors were approximately equal to the cost/price factor. Each offeror’s technical solution would be assessed both technical and risk ratings for the schedule factor and for each technical capability subfactor. … For the technical ratings, the Air Force was to evaluate the quality of the technical solutions as outstanding, good, acceptable, and so on. In assessing the risk associated with each approach, which was to be evaluated as low, moderate, or high, the Air Force was to consider such things as the potential for disruption of schedule and the need for increased government oversight.

The bidders submitted proposals and made an oral presentation. The Source Selection Evaluation Team (SSET) made an initial evaluation and briefed the Source Selection Authority (SSA). Written and oral discussions were held with both bidders, and both bidders submitted final proposal revisions in response to those discussions. The final proposal revisions were evaluated by the Source Selection Evaluation Board (SSEB), briefed the Source Selection Advisory Council (SSAC) on its findings, and prepared a Proposal Analysis Report (PAR). The SSAC prepared a Comparative Analysis Report (CAR) and briefed the SSA on its award recommendation. The GAO decision stated—

In making his source selection decision, the SSA conducted an integrated assessment and found that Raytheon’s proposal presented a lower evaluated cost, less risk in the schedule factor, and a higher performing and more capable DDR system in the technical performance factor. He considered Raytheon’s proposal to be the best value for the government.

The GAO decision also reported that—

… the SSA first found that Raytheon had the stronger proposal under the schedule factor based on differences in the maturity of the offerors’ antenna array design/built/test efforts. … Second, under the technical performance subfactor, the SSA explained that Raytheon’s one weakness was based on its proposal of [DELETED] flight tests, an insufficient number. The SSA concurred with the technical team’s conclusion that four additional flight tests would be required; given Raytheon’s approach, [DELETED] flight tests would be adequate. Raytheon’s GEMPC [Government Estimate of Most Probable Cost] was adjusted upward to account for the additional flight tests. Overall, the SSA concluded that Raytheon’s proposal, and its combined performance in the areas of radar performance, non-developmental items reuse, scalability and upgradeability, and information assurance, offered significantly more benefit to the government than did Northrop Grumman’s proposal…. Although Northrop Grumman distinguished itself in certain areas, it was not enough to overcome Raytheon’s overall superior DDR system performance and capabilities. … The SSA also noted that Raytheon’s proposal had the lowest evaluated cost.

We won’t go into all the issues raised by Northrop. We’ll simply summarize the issues as the GAO did. To wit—

Northrop Grumman primarily challenges numerous aspects of the Air Force’s evaluation of the proposals and alleges that they were disparately evaluated.

The evaluation of technical proposals is a matter within the agency’s discretion, since the agency is responsible for defining its needs and for identifying the best methods of accommodating those needs. … Our Office will not reevaluate technical proposals; rather, we will review a challenge to an agency’s evaluation only to determine whether it was reasonable and consistent with the terms of the solicitation and applicable statutes and regulations. … A protester's mere disagreement with the agency's judgment regarding the relative merits of competing proposals does not establish that the evaluation was unreasonable. … Our decision does not specifically address all of Northrop Grumman’s arguments, but we have fully considered each of them and conclude that they do not provide a basis to sustain the protests.

Readers unfamiliar with the intricacies of government source selection and evaluation requirements may be put-off by the number of acronyms and the obviously bureaucratic processes involved. (We could have described even more bureaucratic processes and used even more acronyms, had we wished. They are certainly present in the GAO protest decision.) But readers need to understand that such seemingly bureaucratic processes are designed to (1) provide documentation, (2) support transparency, (3) facilitate oversight (including judicial review, if necessary), and (4) provide assurance that taxpayer funds are being wisely spent.

Contrast the robust documentation trail in the DDR source evaluation and selection decision with the “inadequate” documentation trail in the LAS competition. In the former case, a protest was denied and the winner could get back to performing the contract. In the latter case, a contract was terminated, an investigation was launched, and the parties are flailing about in court. In the former case, the warfighters will get their technical support on time; in the latter case, they will not.

Which do you think is the better outcome?

 

 


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