Labels and Tags

Accountability (71) Adequate documentation (7) ADR in procurement (4) Allocation of risks (6) Best interest of government (11) Best practices (19) Best value (15) Bidder prejudice (11) Blanket purchase agreement (1) Bridge contract (2) Bundling (6) Cancellation and rejection (2) Centralized procurement structure (12) Changes during bid process (14) Clarifications vs Discussions (1) Competence (9) Competition vs Efficiency (29) Competitive position (3) Compliance (35) Conflict of interest (32) Contract administration (26) Contract disputes (4) Contract extension or modification (9) Contract formation (1) Contract interpretation (1) Contract terms (3) Contract types (6) Contract vs solicitation dispute (2) Contractor responsibility (20) Conviction (4) Cooperative purchasing (3) Corrective action (1) Cost and pricing (13) Debarment (4) Determinations (8) Determining responsibility (37) Disclosure requirements (7) Discussions during solicitation (10) Disposal of surplus property (3) Effective enforcement requirement (35) Effective procurement management (5) Effective specifications (36) Emergency procurement (14) eProcurement (5) Equitable tolling (2) Evaluation of submissions (22) Fair and equitable treatment (14) Fair and reasonable value (23) Fiscal effect of procurement (14) Frivolous protest (1) Good governance (12) Governmental functions (27) Guam (14) Guam procurement law (12) Improper influence (11) Incumbency (13) Integrity of system (31) Interested party (7) Jurisdiction (1) Justification (1) Life-cycle cost (1) Limits of government contracting (5) Lore vs Law (4) market research (7) Materiality (3) Methods of source selection (33) Mistakes (4) Models of Procurement (1) Needs assessment (11) No harm no foul? (8) Offer & acceptance (1) Other procurement links (14) Outsourcing (34) Past performance (12) Planning policy (34) Politics of procurement (52) PPPs (6) Prequalification (1) Principle of competition (95) Principles of procurement (25) Private vs public contract (17) Procurement authority (5) Procurement controversies series (79) Procurement ethics (19) Procurement fraud (31) Procurement lifecycle (9) Procurement philosophy (17) Procurement procedures (30) Procurement reform (63) Procurement theory (11) Procurement workforce (2) Procurment philosophy (6) Professionalism (17) Protest - formality (2) Protest - timing (12) Protests - general (37) Purposes and policies of procurement (11) Recusal (1) Remedies (17) Requirement for new procurement (4) Resolution of protests (4) Responsiveness (14) Restrictive specifications (5) Review procedures (13) RFQ vs RFP (1) Scope of contract (16) Settlement (2) Social preference provisions (60) Sole source (48) Sovereign immunity (3) Staffing (8) Standard commercial products (3) Standards of review (2) Standing (6) Stays and injunctions (6) Structure of procurement (1) Substantiation (9) Surety (1) Suspension (6) The procurement record (1) The role of price (10) The subject matter of procurement (23) Trade agreements vs procurement (1) Training (33) Transparency (63) Uniformity (6) Unsolicited proposals (3)
Showing posts with label The role of price. Show all posts
Showing posts with label The role of price. Show all posts

Monday, December 25, 2017

Crikey! Wot a rort!

I remind my reader to click the links to the articles presented and read the originals, as I slice and dice the material for didactic purposes in order to try to present a "teachable moment". These posts are mostly to be considered as hypothetical procurement case studies, not news or other literary content, and omit, paraphrase and rearrange a lot of original material. You've been warned, again.

Allegations of systemic fraud sparked Defence Department internal audit
Confidential documents drafted by a senior defence department investigator reveal allegations of systemic fraud spanning several years inside the government's biggest spender. The 10-month investigation, which finished in February this year, was prompted by an anonymous disclosure about fraud and corruption made to the department in April 2016.

One of the most concerning aspects involved the department awarding companies contracts without a competitive tender process and only a flimsy justification they met "value for money" requirements. In other cases the department was unable to tell whether a contract breached procurement rules or not because important paper work could not be found.

In 2015-16 the Department of Defence reported the largest yearly contract spend of any agency within the public service. The department dialled-up a bill of $30.5 billion on contracts, amounting to 54 per cent of total government contractor spending.

The investigation raised serious questions about the department's use of "single source" tenders, where a single company is awarded a contract without having to compete against other providers. "It is questionable whether true value for money is achieved when [redacted] continually conduct single source limited tenders," Dr Clarke wrote. "Whilst there is less administration and quicker decision making with this approach, it provides limited opportunity for Defence to achieve the best possible outcome. "Single source limited tenders increase the risk of contractor underperformance and corruption."
Defence spending data unreliable, incomplete, national audit office says
Transparency and accountability for billions of dollars of annual defence spending remains suspect despite recent reforms, the Australian National Audit Office (ANAO) has found.

Last year, the Defence Department spent $8.3 billion on keeping its equipment in working order, known as "sustainment" in military jargon. Yet, the audit office found that despite small recent improvements, information about where that money went and whether it was being spent wisely was often unreliable or not available.

The report also questions a claim from Defence that reforms to its sustainment policies had saved $2 billion. "Defence has not been able to provide the ANAO with adequate evidence to support this claim, nor an account of how $360 million allocated as 'seed funding' for Smart Sustainment initiatives was used," it read.

Auditors were also critical of inconsistencies between figures given to the Government during the budget process and those provided in the department's annual report. "It's absolutely not good enough," Andrew Davies, director of defence and strategy at the Australian Strategic Policy Institute, told AM.
Oz military megahack
An Australian Signals Directorate (ASD) presentation to the Australian Information Security Association (AISA) conference yesterday detailed the hack. Suffice to say that a medium-sized defence contractor was breached and gigabytes of aerospace data and commercial arrangements for military aircraft and naval vessels were delivered into the hands of the attackers. The ASD used it as a case study for the AISA conference yesterday.

The government has since said the information was commercial-in-confidence, but not classified. This is not an isolated incident: in Australia, as elsewhere, attackers thwarted by a network's defences then seek out third-party contractors as an easier mark.

This suggests a problem in sub-contractor oversight – you can win a government contract without proving you have adequate network security.

Minister for Defence Industry Christopher Pyne seems to agree. This morning, he told Radio National's Breakfast programme that the government can't be held responsible for a contractor's lax security.
Fat and mismanaged public sector is eating us alive
In a Crikey article, carried by the Community and Public Services Union, Eric Beecher chronicles appalling mismanagement in service delivery.

Then there’s the $11 billion spent by the Defence Department managing 119 bases around Australia which the ANAO says is well in excess of the $9.3bn “expected value” of the 10 services contracts, signed in 2014, to do the work. The department has defended its performance, saying the vast project to renegotiate the contracts has delivered value for money, when considered against increased service demands and changing expectations of the ADF. Yet a new $120 million IT system, meant to manage contracts ­between Defence and the private companies servicing the bases, was $39m over budget and five years late.

There’s also the flawed tendering and contracting processes overseen by the Immigration ­Department, which resulted in the waste of “tens and possibly, hundreds of millions of dollars”. Given these practices were subject to a scathing ANAO report, they could hardly be ignored.

We’re reminded of last year’s Australian Bureau of Statistics census “stuff-up”, the Australian Taxation Office’s massive and damaging IT outage, the Department of Health’s decade-long mismanagement of e-health records, and the embarrassing release of identifiable Medicare information. There’s also the Department of Finance’s lax oversight of ministerial travel arrangements. But not raised is the $576m public service travel bill — a blowout of $75m in just four years.

While this shocking record is acknowledged, Beecher argues the blame lies mainly with outsourcing to powerful private contractors.
Outsourcing failures expose weaknesses in both government and business
The problems of dealing with private sector providers and contractors are a persistent theme in the analysis of government shortcomings. For example, recent Australian National Audit Office reports highlighted contracting problems in Air Services Australia, the Defence Department and the Immigration Department. Contract management issues were at the heart of last year's failed online census and have been a constant factor in the turbulent administration of Australia's controversial offshore detention centres. Over-reliance on contracted consultants was a major cause of the botched home insulation scheme.

Given the extent to which governments rely on private contractors for a large range of goods and services, it is unsurprising that contractors are often in the frame when things go wrong. But many of the recurring issues arise out of factors specific to the contracting process.

A common complaint is that the use of contractors has caused agencies to run down their in-house expertise and technical resources. As a result, it can be argued, agencies lack the capacity to assess whether the contracts they are agreeing to give the government and taxpayer adequate value for money. Without their own professional judgment, grounded in technical knowledge and practical experience of the area in question, public service managers are ill-equipped to decide matters of all-round quality. Instead, they tend to fall back on generic checklists of assessment criteria that emphasise easily specifiable factors, such as cost and timeliness.

Alternatively, if funds allow and time permits, they may contract in an external consultant or commissioner to give an expert opinion on a proposed contract. But such advice carries the risks of perverse incentives attached to all forms of external contracting and consulting. The consultants' objective is to gain future contracts, which encourages them to say what they think governments want to hear in preference to what they ought to hear. Once again, without the professional judgment to tell the difference and without their own in-house, trusted staff to advise them, public service managers are at the mercy of self-interested outsiders. This vulnerability is compounded by the lack of transparency that surrounds contracting. Overuse of commercial-in-confidence provisions has shielded public servants from the bracing effects of public scrutiny.

The lack of in-house capacity can affect not only the initial process of drawing up contracts but also the oversight of how contracts are implemented. However, as the constant stream of scandals illustrates, many commercial providers are more interested in profit than in good service and cannot be trusted to do the right thing. As a result, governments are being driven to impose tighter controls and regulations. Even then, in the face of determined rorting and corner-cutting, most government agencies lack the resources to prevent opportunistic contractors from wrongfully expropriating public funds.

After two decades of wholesale outsourcing, some general conclusions are clear. Contracting out is an efficient and effective alternative to in-house provision where the objectives are clear and easily monitored, and where there is a competitive market of alternative providers. It also works well for more complex services where providers can be trusted to pursue public-interest objectives for their own reasons. However, where these conditions of either simplicity or trust do not apply, the risks that governments will not receive value for money start to build. Moreover, extensive experience with outsourcing has itself compounded these risks by reducing governments' capacity to effectively draw up and monitor outsourcing contracts. Some complex service contracts that could have been safely contemplated a generation ago are now beyond the professional expertise of public servants to administer.

politicians need to recognise that outsourcing complex government services requires the development of trust between the parties, which means looking beyond the short-term bottom line and not always preferring the cheapest option. In addition, successful contracting depends on well-resourced government agencies with the skills and experience necessary to manage ongoing relationships with contractors. Running down government staffing levels while relying more on private contractors is a recipe for continuing policy failure.

Contractors, for their part, must earn the right to be treated as trusted partners. They must be prepared for the long haul and willing to learn from experience. They must also be ready to submit to the level of public scrutiny and accountability that public servants take for granted. Indeed, given that the commercial private sector is not imbued with the same commitment to serving the public interest, there is a case for subjecting private contractors to more scrutiny than the public service, not less.

Tuesday, November 28, 2017

The laborious SAGA of the US Navy's BOSS contract on Guam

This post is a follow-up to a prior post almost 3 years ago, Protest of Navy's BOSS contract on Guam upheld.

Note: As always, I take considerable liberties with the source documents when presenting them here. For instance, critical citations are often omitted, parts are re-arranged and/or paraphrased, etc. Read the source at the link if accuracy, completeness and fidelity is important to you. (If it is not important to you, reconsider wandering around the web without an escort.)

Before the GAO in re Matter of: Fluor Federal Solutions, LLC, File: B-410486.9, January 18, 2017
DIGEST: Fluor maintains that the agency misevaluated proposals and made an unreasonable source selection decision. Protest challenging agency’s evaluation of staffing and resources proposals is sustained where record shows that agency evaluated the protester’s and awardee’s proposals disparately in a manner that prejudiced the protester. We sustain the protest.

This is our third occasion to consider the propriety of the Navy’s actions in connection with this acquisition. In a prior decision, we sustained a protest filed by Fluor relating to the agency’s evaluation of proposals and conduct of discussions in connection with this acquisition. We recommended that the agency reopen discussions with the offerors, solicit, obtain and evaluate revised proposals, and make a new source selection decision.

The Navy implemented our recommended corrective action and again selected DZSP for contract award. Fluor filed a second protest challenging the agency’s selection of DZSP in the wake of the agency’s corrective action. After full development of the record in that case, we conducted an outcome prediction alternative dispute resolution (ADR) procedure at the request of the Navy. We advised the parties that the agency’s evaluation of DZSP’s proposed cost in the area of its exempt employee compensation (discussed in detail below) appeared to have overlooked certain significant features of DZSP’s proposed costs. As a result, the GAO attorney advised that our Office likely would sustain the protest. The agency advised our Office that it intended to take corrective action to address the concerns we identified, and on that basis we dismissed Fluor’s second protest as academic.

After dismissal of Fluor’s second protest, the agency engaged in limited discussions with the protester and DZSP and solicited, obtained and evaluated revised proposals. The agency again selected DZSP for award, and the current protest followed.

The RFP advised offerors that the agency would make award on a best-value basis, considering cost and several non-cost evaluation factors. The non-cost factors were as follows: past performance, occupational safety, staffing and resources, technical approach, and small business utilization. For cost evaluation purposes, the RFP advised offerors that the agency would evaluate proposals for completeness, reasonableness, balance, and realism. The RFP stated that the agency would assign past performance examples relevancy ratings of very relevant, relevant, somewhat relevant or not relevant, and would assign each offeror’s past performance a confidence rating of substantial confidence, satisfactory confidence, limited confidence, no confidence or unknown confidence. Finally, the RFP stated that past performance was approximately equal in importance to the other four non-cost evaluation factors combined, and that all five non-cost factors, when combined, were approximately equal in importance to cost.

DZSP had proposed 113 exempt labor categories, and claimed that it was escalating the direct rates of compensation for these employees by [deleted] percent for each year of contract performance. A careful examination of the record showed, however, that in addition to applying an escalation factor of [deleted] percent, DZSP also was applying what it termed a “decrement factor” of [deleted] percent to these same rates of compensation. The net result of these calculations was that, rather than escalating its direct labor by [deleted] percent per year, DZSP actually was reducing the rates of compensation for these employees by [deleted] percent during each year of contract performance. The contemporaneous record showed that the agency failed to recognize this decrease in DZSP’s proposed compensation, and that its cost realism evaluation failed to take it into account.

The record further showed that Fluor had been found technically superior to DZSP under the non-cost evaluation factors. While both firms received the highest ratings (substantial confidence and outstanding) under the past performance, occupational safety, staffing and resources, and small business utilization factors, Fluor’s proposal received an outstanding rating under the technical approach factor, while DZSP’s proposal was assigned a rating of good under that factor.

The agency’s selection of DZSP’s lower-rated proposal was based on its conclusion that it represented a savings of approximately $6.9 million over the life of the contract. However, we concluded, based on the error associated with the agency’s failure to recognize DZSP’s decrease in its exempt employee compensation, that this apparent cost savings was largely non-existent. We therefore concluded that the agency’s source selection decision was not reasonable.

Subsequently, the agency elected to allow Fluor and DZSP to make limited revisions to their proposals.
Both firms revised their proposals and the agency reevaluated them on the basis of those revisions. The agency made no changes to the adjectival ratings assigned to the offerors’ non-cost proposals (Fluor was again found superior under the technical approach factor). Both firms revised their proposed costs: Fluor proposed a total cost of $494,519,656, and DZSP proposed a total cost of $491,894,166. The agency made no adjustments to either firm’s proposed cost for purposes of evaluating realism. On the basis of these evaluation results, the agency again made award to DZSP, concluding that, although Fluor’s proposal was technically superior, it did not merit the approximately $2.6 million cost premium.

The focus of Fluor’s latest protest centers on a change in the proposed approach to managing and compensating its exempt personnel that DZSP introduced in response to the agency’s latest round of discussions. The agency had provided DZSP a discussion question relating to the fact that, in its earlier proposal, it had offered to reduce its exempt employees’ compensation by a net factor of [deleted] percent during each year of contract performance. The agency advised DZSP that such an approach was not considered by the government to be reasonable or realistic because it implied that every exempt position would be replaced with a new hire at a lower rate of compensation for each year of contract performance.

In response to the agency’s discussion question, DZSP essentially introduced an entirely new approach to how it would manage and compensate its exempt employees. In effect, DZSP’s new approach was that it would replace incumbent workers at a rate of [deleted] percent of its exempt workforce per year and hire new, lower paid, employees in their place. These new employees would be paid [deleted] percent of the hourly rates identified in DZSP’s proposal. The employees that were not replaced in a particular contract year would be given a [deleted] percent escalation to their hourly rates of compensation (until such time as they were replaced), and this would result in [deleted] hourly rates of compensation that would [deleted] over the life of the contract.

Fluor raises various challenges to the agency’s evaluation of DZSP’s proposed approach to maintaining [deleted] wage rates for its exempt employees. Among other arguments, Fluor alleges that the agency engaged in disparate treatment in connection with evaluating its proposal and DZSP’s proposal in the area of staff recruitment and retention.

For the reasons discussed below, we agree with the protester that the agency evaluated the two proposals disparately in connection with the question of recruitment and retention of staff. It is axiomatic that agencies are required to evaluate proposals on a common basis and in accordance with the terms of the RFP; agencies may not properly engage in disparate treatment of offerors in the evaluation of proposals.

Under the express terms of the RFP, the agency was required to evaluate the adequacy of the offerors’ staffing approach as it related to the recruitment and retention of staff.

The record shows that Fluor’s staffing approach for exempt employees involved recruitment of 95 percent of the incumbent staff. Fluor represented to the agency that it was confident in its ability to do this based on the wage rates it was proposing. Of significance, Fluor specifically represented that, in the event it was unable to attract the incumbent staff with the rates of compensation it was proposing, Fluor proposed to [deleted] for exempt employees. Notwithstanding this representation in the Fluor proposal, the record shows that the agency’s evaluators and source selection authority expressed a concern that Fluor would be unable to recruit the incumbent exempt employees at the wage rates it had proposed. The agency’s technical evaluators questioned Fluor’s ability to recruit the incumbent exempt staff based on the wage rates it had proposed, and suggested that Fluor’s approach could result in employee morale and retention issues. The agency’s cost evaluators echoed these same concerns.

In contrast, the evaluators did not give meaningful consideration to similar implications of DZSP’s proposed approach described above, or how it would impact the firm’s retention of employees, as required by the RFP. In this connection, the evaluators gave no consideration to the fact that DZSP expressly proposed to replace its incumbent staff at a rate of [deleted] percent per year for each year of the 8-year potential life of this contract. The agency technical evaluators confined their observations to consideration of whether or not it was realistic for DZSP to replace its existing, incumbent exempt employees, and concluded that it was “very realistic” for DZSP to do so because approximately [deleted] percent of DZSP’s overall workforce was comprised of an aging population. In addition, the technical evaluators observed only that DZSP’s claimed 95 percent retention rate for its exempt employees would “not be applicable” to future contract periods, but did not criticize the firm’s proposal for this reason. The cost evaluators, for their part, did not give consideration to DZSP’s proposed plan to replace its exempt workforce, and instead confined their observations to whether or not DZSP’s proposed rates of compensation were reasonable and realistic.

In addition to these inconsistencies, the agency’s source selection authority (SSA) specifically found the DZSP proposal superior to the Fluor proposal in the area of employee retention and used that as a discriminator for making her selection decision. In fact, she apparently was unaware of DZSPs’ proposed approach of essentially replacing its exempt workforce more than once over the life of the contract.

In sum, the record shows that the agency evaluated the offerors disparately under the staffing and resources factor, criticizing Fluor’s proposed approach as possibly involving a risk that it would not be able to recruit the incumbent workforce, while at the same time failing to meaningfully consider whether a similar risk was raised by DZSP’s proposed approach of repeatedly replacing its exempt employee workforce over the life of the contract. In light of these considerations, we sustain Fluor’s protest.

We recommend that the agency reevaluate proposals in a manner that is consistent with this decision and make a new source selection decision after performing that reevaluation. Should the agency conclude that DZSP is no longer in line for award, we further recommend that the agency terminate DZSP’s contract for the convenience of the government, and make award to Fluor, if otherwise proper.

Wednesday, April 19, 2017

The lowest what?

Bid awards are meant to go to the lowest responsive bid from a responsible bidder, right?

Lowest what?

Too often, the assumption, therefore the focus, is on price: the sticker price. Lowest price wins, right?

But from the phrase "sticker price", we also get the phrase "sticker shock".

Sticker shock is what County Officials are coming to terms with as they near completion of a new 22-story Superior Courts building in downtown San Diego, California. Here's the story from the San Diego Union Tribune:

COSTLY ADD-ON AT NEW COURTHOUSE
The new building downtown county courthouse, designed with 71 courtrooms, will consolidate operations at the 1960s-era downtown criminal courthouse on Broadway, Family Court on Cedar Street and the Madge Bradley Building on Ash Street. The 110 deputies and community services officers working at those three locations will be transferred to the new courthouse.

It will cost an extra $3.3 million a year in staffing to resolve security risks caused by the design of the $555 million downtown county courthouse set to open this summer, county officials say.

They point, in part, to a cost-cutting decision not to build a $25 million tunnel under Union Street that would have allowed deputies to escort inmates directly from the Central Jail to the new Superior Courts building.

“This design difference imposes a measurable and higher level of security costs,” said a 2016 report by Sheriff Bill Gore and Helen Robbins-Meyer, the county’s chief administrative officer.

The San Diego County Sheriff’s Department provides deputies and community services officers as security at the region’s courthouses. The department said it needed 33 more positions on top of the 110 originally planned in order to safely move prisoners in and out of the new 22-story building, and to respond to any courtroom emergencies.

The tunnel from Central Jail to the new courthouse was part of the original construction plan, and Keim said the sheriff continues working with state and local leaders to get it built.

Without the tunnel, the plan is to bus jail inmates two blocks to a controlled entryway at the courthouse called a sally-port. Gore says the buses require extra supervision, as do extra holding cells added to the courthouse design.

Gore’s report, submitted to the state Department of Finance, said the new courthouse’s high-rise configuration “significantly affects the ability of deputies to respond to security issues, dangerous incidents or emergencies.”

He noted that a 2015 study showed an average of 16 such incidents per week at the current courthouse.

There will be up to four criminal trial courtrooms on each of 11 floors in the new building. The sheriff wants roving deputies available to run up or down stairwells to assist courtroom bailiffs in any emergencies. Using an elevator might actually be slower if deputies on multiple floors stop it to get on board, the report says.

Other “rovers” would keep an eye on large public spaces, including the lobby and food court. More deputies also are needed to run the five weapons-screening stations at the entrance.

Two felony arraignment courtrooms pose added concerns: They are on the first floor near the exit doors. That proximity, the sheriff’s report says, “presents an increased security risk for a successful escape of in-custody prisoners charged with serious felony crimes.”

The sheriff has asked the state to cover the $3.3 million estimated annual cost of hiring 30 more deputies and community service officers, and three sergeants.

San Diego County spokesman Michael Workman said, “We need $3 million. If that doesn’t happen, we’ll have to determine what to do. It would probably have to come out of (the sheriff’s) budget.”
So, to save the upfront price to construct the tunnel by $25 million in fixed today's dollars, the taxpayers (of either the State of the County) will have to shell out over $3 million a year in servicing expenses, which tend to escalate over time -- for the lifetime of the complex.

Such a deal to get a lower bid price! In just eight years that $25 Million up front price will look a bargain, but the court will be doing 8 years to life (cycle).

This is an example of contemplating bid prices on sticker prices. That is not the model used, however, in the ABA Model Procurement Code, nor the Guam procurement law and regulations, which are founded on the ABA Model Code.

Whatever the colloquial use of "lowest price" may describe the Model law and regulation require a more holistic analysis. It requires "bids will be evaluated to determine which bidder offers the lowest cost". Moreover, "Only objectively measurable criteria which are set forth in the Invitation for Bids shall be applied in determining the lowest bidder. Examples of such criteria include, but are not limited to, transportation cost, and ownership or life cycle cost formulas." (See, Guam regulation 2 GAR 3109(n)(4))

Nobody likes sticker shock. In a $555 million procurement, that is a rookie mistake.

Sunday, October 30, 2016

It's sticking to "the letter and spirit of the evaluation procedures" that counts

These articles, which I've sliced and diced to my own ends, discuss the ramifications of looking at bid protests from a practical, not pendantic, view point. You can read the case discussed here; you should read the full stories at the links provided, lest my version taint your perspective.

OPINION: Contractors must recognise new US procurement rules
Nothing illuminates the essential characteristics of this new era better than the Government Accountability Office’s stinging and even humiliating rejection of Boeing’s protest at the US Air Force’s decision to award the long range strike-bomber (LRS-B) contract to Northrop Grumman a year ago; the GAO’s newly-released decision offers valuable instruction for competing in this new era.

The most surprising revelation in the report is how the USAF structured the LRS-B competition. It may be the first time it has acquired a combat aircraft based on a lowest-cost, technically compliant bid. Northrop heavily invested corporate funds in classified risk-reduction efforts, a fact the GAO says played a key role in reducing the USAF’s estimated price for its proposal. As bidders line up for a host of new USAF contracts, upfront investments by contractors are essential.

It is fair to say that Boeing did not like how the USAF evaluated both proposals on cost. Boeing quibbled over which historic programmes should be used as the baseline to forecast production costs on LRS-B. According to the GAO, Boeing submitted cost data based on derivative programmes, but the USAF preferred clean-sheet aircraft developments. Boeing sent the USAF a rebuttal, but apparently used inaccurate labour cost data, which, the GAO passive-aggressively notes, “did not enhance the credibility of Boeing’s estimate”.

Despite Boeing’s multiple objections, the GAO laid out a clear case that the USAF stuck to the letter and spirit of the evaluation procedures.
Game Over: GAO Protest Reveals Cost Was Deciding Factor in B-21 Contest
The Air Force in October 2015 awarded Northrop the contract to develop and produce its newest bomber, now designated the B-21 Raider. Northrop beat out a Boeing-Lockheed Martin team for the two-pronged contract that covers the engineering, manufacturing and development phase of the program as well as the first five low-rate initial production lots.

According to the GAO decision, Boeing argued that the Air Force did not effectively measure the risk of Northrop’s bomber. The company contended that if the service had followed definitions set in the request for proposals, Northrop would not have met four out of seven unnamed technical capability subfactors. Boeing also stated that Northrop’s proposal was “inherently high risk” with regard to certain requirements in a way that should have rendered its offering unacceptable.

GAO shot down those claims, saying its review found the Air Force evaluated Northrop’s bid in a way that was “reasonable and consistent” with the RFP.

Boeing also alleged that the service overestimated the price of its own offering and relied too heavily on independent government estimates. Again, the GAO disagreed.

“We see no error in the Air Force’s rejection of supporting cost data presented in Boeing’s proposal, or its upward adjustment to Boeing’s proposed EMD costs,” it wrote.

The office noted that both Northrop’s total weighted price and total estimated price were lower than Boeing’s. Although Boeing calculated that its proposal price had been overestimated, the decision noted, even if Boeing’s proposal was adjusted by that figure, it would have not been enough to topple Northrop, which would have nabbed the contract on the basis of its lower total weighted price. Thus, GAO said Boeing could not demonstrate that the Air Force had demonstrated competitive prejudice — a situation where the company would have won the contract if not for the government mismanagement or wrongdoing.

the decision sheds light on many interesting aspects of the competition. After the companies submitted their proposals to the Air Force in 2014, the service found both offerings technically unacceptable and held eight rounds of discussions where the competitors worked through deficiencies, although the GAO noted that some risk still remained with each proposal.

Those discussions failed to resolve questions about ​both Boeing and Northrop’s cost estimates for the EMD phase of the program, which Air Force found to be overly optimistic when compared with its own independent government estimates. Even after eight rounds of talks, neither company was able to put forward a proposal that could be considered realistic with respect to the majority of the cost categories.

But while Northrop increased its own estimates, Boeing kept its own cost data at the same level, the GAO said. And, partially because Northrop offered to pay for certain expenses internally on its own dime, the company was able to keep EMD costs below Boeing’s throughout the duration of the discussion process.
How the Air Force's $55B bomber contract became an LPTA competition
Information on the bomber program is apparently a touchy subject for the Air Force, which has steadfastly refused to release the value of Northrop Grumman’s bid. The $55 billion price is based on price estimates prior to the competition.

U.S. Sen. John McCain, chairman of the Senate Armed Services Committee, has been especially vocal with his criticism that the contract is a cost-plus contract and subject to overruns that the government will be on the hook for. He has threatened to withhold funding for the bomber.

To be fair to the Air Force, initial development of the first 21 planes is cost-plus, but once the craft moves into full production of up to 100 planes the contract switches to fixed price.

In a footnote, GAO describes how Northrop’s engineering and manufacturing development costs were significantly lower than the Boeing-Lockheed proposal because of investments Northrop had made but did not pass on to the government. What those investments were is redacted from the decision and Northrop declined to comment.

Northrop also had lower labor rates and labor escalation rates. Northrop also declined to comment on how they made their labor rates lower.

Because of Northrop’s investments and lower labor rates, the independent government estimates of costs for Northrop’s proposal was lower than the Boeing-Lockheed proposal.

This is significant because both teams were deemed to be technically acceptable.
The solicitation’s selection criteria stipulated that if the higher bid was greater than 103 percent of the lower bid than the lower bid would be deemed best value. The bid by the Boeing-Lockheed team was more than 103 percent so the Air Force picked Northrop.

The argument is that this is best value because why should the Air Force pay a higher price if both proposals were found technically acceptable?

As GAO said, Northrop’s price “created a near-insurmountable obstacle to Boeing’s proposal achieving best value.”

Saturday, January 24, 2015

You can't get just anything you want at the FSS restaurant

Apologies to Arlo Guthrie.

This is not an accurately complete rendition of the GAO's decision. Read that at the link.

Matter of: US Investigations Services, Professional Services Division, Inc.: B-410454.2, January 15, 2015
DIGEST: Protest against issuance of a task order to a vendor for support services pursuant to its General Services Administration Federal Supply Schedule contract is sustained where the record does not support contracting agency’s determination that the services called for under the task order were within the scope of the vendor’s contract.
US Investigations Services, Professional Services Division, Inc. (USIS) protests the issuance of a delivery order to FCi Federal, Inc. under request for quotations (RFQ) issued by the Department of Justice, Federal Bureau of Investigation (FBI), for services in connection with the agency’s Name Check and Freedom of Information Act (FOIA)/Declassification programs. The Delivery Order was issued under FCi’s Federal Supply Schedule (FSS) contract.

The RFQ contemplates the award of a fixed-price delivery order for a 12-month period of performance. The successful contractor will provide personnel to perform services in connection with the agency’s National Name Check Program. Under that program, the successful contractor will provide research, analytical, and reporting services for authorized federal agencies. Essentially, contractor personnel research FBI files to provide available and appropriate information within legal and policy constraints. The RFQ also contemplates services in connection with the agency’s FOIA/Declassification program. Under that program, the successful contractor will provide services to the agency in connection with responding to FOIA requests, and also in making determinations regarding the appropriate classification of national security related information.

The agency received three quotations in response to the solicitation. All three quotations were found technically acceptable, and all three firms also received past performance ratings of good. FCi submitted the lowest price of $13,298,366, followed by USIS and the third firm. The agency made award to FCi because it submitted the lowest price.

After being advised of the agency’s issuance of a task order to FCi, USIS filed this protest. USIS alleges that issuance of a task order to FCi was improper because the labor categories required to perform the task order are not on FCi’s FSS contract. The protester maintains that the agency erred in finding that the labor categories included on the awardee’s FSS contract encompass the types of employees required to perform the requirement. We agree with the protester that the labor categories included on FCi’s FSS contract do not encompass the solicited services.

As a general matter, FSS procedures provide agencies a simplified process for obtaining commonly used commercial supplies and services and, although streamlined, by regulation, satisfy the requirement for full and open competition. However, non-FSS products and services may not be purchased using FSS procedures; their purchase requires compliance with otherwise applicable procurement laws and regulations, including those requiring the use of full competitive procedures.

Where an agency announces its intention to order from an existing FSS, all items quoted and ordered are required to be on the vendor’s schedule contract as a precondition to its receiving the order. In the case of a services task order such as the one at issue here, all of the solicited labor categories must be on the successful vendor’s FSS contract.

The RFQ here essentially included four principal labor categories: research analysts, program managers, general consultants, and legal administrative specialists. For three of the four labor categories -- research analysts, general consultants, and legal administrative specialists -- FCi proposed a single labor category from its FSS contract, program management analyst. FCi’s FSS contract includes the following description of its program management analyst labor category:
Plans and provides analytical support for facilitation, methodology development and evaluation, business management techniques, and organizational development. Supports business process improvements and modernization projects. Key responsibilities include: Developing modern business methods, identifying best practices, and creating and assessing performance measurements.
An examination of the labor categories required under the RFQ, however, shows that the duties, responsibilities and qualifications of the types of employees solicited by the agency are not encompassed within FCi’s program management analyst labor category.

Comparing the above-quoted definitions found in FCi’s FSS contract and the RFQ, we conclude that FCi’s program management analyst labor category does not include many of the requirements for the labor categories identified in the RFQ. For example, FCi’s labor category description makes no mention of experience with paralegal, records management, declassification review or historical research career fields, and also makes no mention of in-depth knowledge of FBI policy, functions, and familiarity with other government agencies’ functions. FCi’s labor category description also makes no mention of applying knowledge of administrative principles, practices, and techniques; organizing and maintaining files and database record keeping systems; preparing, writing, editing, and creating graphs and charts; or drafting, reviewing, evaluating, and processing technical and administrative documents.

Instead of the disciplines and career fields identified in the RFQ, the principal disciplines and capabilities described in FCi’s program management analyst labor category are the development of business methods, the identification of best practices, and creating and assessing performance measurements. The focus of FCi’s labor category appears principally to be the development of business techniques and organizational development activities. Simply stated, none of the responsibilities or activities described in FCi’s labor category description -- identified as ‘key’ responsibilities in FCi’s labor category description -- is germane to the work required under the RFQ.

The contemporaneous evaluation record does not show that the agency gave any meaningful consideration to the question of whether or not FCi’s FSS contract included labor categories that encompassed the requirements of the task order. In this connection, the agency’s individual evaluators did not prepare any narrative materials when reviewing the proposals. The agency’s summary technical evaluation report and award determination similarly are devoid of any meaningful consideration of whether award could be made to FCi in light of the labor categories available under its FSS contract.

Finally, in responding to the protest, the agency states only generally that it gave consideration to whether or not FCi’s FSS contract included labor categories that encompassed the requirements of the RFQ. Even in responding to USIS’s specific allegations, the agency has not meaningfully or critically analyzed the question, or explained how it reasonably could reconcile the apparent divergence between FCi’s labor category description quoted above and the requirements of the RFQ.

[But here, the GAO ran into an obstacle preventing the usually implemented remedial recommendation, because the FBI pulled a quicky ("urgent and compelling") stay override.]

In light of our discussion above, we conclude that FCi is ineligible for award because the labor categories required to perform are not available under FCi’s FSS contract.

Ordinarily, our Office would recommend that the agency terminate the task order issued to FCi because FCi is ineligible for award. However, during the pendency of the protest, the agency elected to override the automatic stay of performance of the FCi task order based on urgent and compelling circumstances.

Accordingly, we recommend that the agency consider the feasibility of terminating the task order awarded to FCi. Should the agency conclude that it is not feasible to terminate FCi’s task order, we recommend that USIS be reimbursed the costs associated with preparing its quotation in response to the RFQ. In addition, and regardless of whether or not the agency decides to terminate FCi’s task order, we recommend that USIS be reimbursed the costs associated with filing and pursuing its protest, including reasonable attorneys’ fees. In the alternative, if the agency determines that it is feasible to terminate FCi’s task order, we recommend that the agency make award to the concern next in line for award, if otherwise proper.

It is perhaps worth reminding here that the GAO, which hears most protests in federal government contracting, has no enforcement power, thus "recommends" remedial actions it finds appropriate. The overwhelming majority of these recommendations are, however, adhered to by agencies.

Also, though not directly related to the focus of the decision, the GAO's decision included a very instructive footnote, as well as a "zingy":
[1] USIS alleges that the agency improperly found FCi’s prices reasonable. According to the protester, because FCi did not propose labor categories that were required by the RFQ, the firm’s proposed hourly rates were unreasonably low. There is no merit to this aspect of USIS’s protest. In a fixed-price contract setting, determinations of price reasonableness relate to whether a firm’s proposed prices are too high, not too low. An allegation that a firm’s prices are too low does not provide a basis for our Office to object to the agency’s price evaluation.

USIS also challenges the agency’s evaluation of its past performance. We have considered this aspect of its protest and conclude that USIS’s allegation amounts to no more than disagreement with the agency’s evaluation findings in the area of past performance. USIS’s disagreement with the agency’s evaluation, without more, does not provide a basis for our Office to find the agency’s evaluation unreasonable.

[4] It would appear that USIS is the next firm in line for award. In considering whether or not award to USIS is otherwise proper, the agency will be required to find the firm responsible. In a recent decision of our Office, we specifically questioned an affirmative determination of USIS’s responsibility made by the Department of Homeland Security, U.S. Citizenship and Immigration Services, because the record demonstrated that the contracting officer there failed to consider specific allegations of fraud advanced by the Department of Justice (DOJ) in a civil suit filed against USIS’s parent company, USIS LLC; failed to consider the relationship between USIS and its parent concern; and applied an incorrect legal standard in determining whether USIS was responsible. FCi Federal, Inc., B-408558.4, et al., Oct. 20, 2014, 2014 CPD ¶ 308 at 11. [See also, The responsibility to consider all factors to make a determination of responsibility]

Sunday, January 11, 2015

Best buy based on price or value?

When you are standing in that long isle looking at all the shampoos available to you on the five shelves of product (as I experienced this last weekend), what moves you to choose one of them? (In my case, I just moved on, overwhelmed, deferring to whatever my wife decides to buy.)

Presumably, if you are a rational, frugal, person, you would choose the one that you needed, at the lowest cost. That requires filtering all the brand and other marketing temptations, of course, and knowing if you have oily hair, itchy scalp, or other conditions you are trying to address (adding color, conditioning, or ego boosting marketing imagery). Thus, you really do need to know what you need if you are going to be a smart shopper, before you go to the store.

But when your requirements are novel, either because you are going where no man has gone before, or whether the vehicle by which you want to get there is in the flux of major technological changes, you need to do more homework, have an open mind about what you do in fact need, and be prepared to pay more than one particular product costs in order to get what you think will better suit your anticipated but unarticulated circumstances.

That is the main reason for a variety of government contracting procurement methods: one size does not fit all.

But, it is important to understand why one method is superior to another, and, critically, to understand the role price pays in each different method. The article below is about what the US federal contractors call the low-price/technically acceptable source selection technique, known as LP/TA. Those of us more closely aligned to the ABA Model Procurement Code refer to it as the "multi-step" bid process. 

Don't be confused by the terminology. Under an Invitation for Bid and under the LP/TA price is the ultimate determiner for award: low price wins. The difference is that in the plain vanilla IFB, the final specifications are in the bid package (subject to minor changes along the way), whereas under the multi-step bid process, the government first solicits "unpriced technical offers" and the means is established whereby both the technical offers and specifications can be fine-tuned (within the scope of the original solicitation) before a call for final prices.

This is why it is absolutely essential in every method of source selection, especially low-price bids, to carefully identify the absolute minimal needs requirements and clearly communicate that to vendors by translating that into specifications that can be understood by the lowest common denominator of experienced reader -- the judge.

The low price scheme differs from the negotiated contract/"best value" procurement method, where low price is not determinative, with price being only one of several factors in determination of award. To the extent that the non-price factors are more subjective than objective, fairness and accountability for award determinations are more problematic than with low-price bids.

The risk factor must also be considered in making the choice of procurement method. Under the low-price method, the government bears the risk of identifying its need and translating that into specifications. Under the "best value" method, the government bears the risk of paying too much for something it doesn't understand, ending up with something it may not need. 

(It's having that kind of risk that led me to walk out of the store and "let" my wife select the shampoo.)

With that backgound, read the following articles in point and counter-point; don't just take my rendition of it, though -- read the articles for stuff I leave out, rearrange and paraphrase, etc.

Finding a Bargain for Government Buyers Shouldn’t Be a Crime, by J. David Cox J. David Cox Sr. is national president of the American Federation of Government Employees.
Contractors, who bill taxpayers a whopping $500 billion annually for goods and services, hope to use the “acquisition reform” moniker to minimize the importance of cost-efficiency in the federal acquisition process.

The No. 1 objective of contractors is to demonize the low-price/technically acceptable source selection technique, known as LP/TA, so that its use is greatly limited if not proscribed.

Contractors would prefer that DOD use a more expensive process called “best value,” which allows them to charge more for features that warfighters usually don’t need. A contractor who believes DOD should be asking for more can suggest additional features to the contracting officer, who can then include them in a new or revised solicitation, if necessary, so the most cost-efficient qualified contractor can then be identified.

The Government Accountability Office reports that DOD is using LP/TA more frequently to generate savings. GAO, however, dismisses contractor allegations that such savings come at the expense of quality: “Best value processes continued to underlie the vast majority of DOD’s new, competitively awarded contracts. DOD has increased its use of the LP/TA process in recent years for higher value contracts, and its decision-making regarding which source selection process to use did not appear to be ill-advised.”

Solicitous lawmakers profess fear that LP/TA’s emphasis on costs will erode contractor confidence and undermine the industrial base. Think tanks produce paid-to-order research that purports to demonstrate a link between LP/TA and poor goods and services. Helpful trade publications breathlessly report every contractor complaint about LP/TA, however unfounded. The goal of this public relations campaign is to enact prohibitions on the use of LP/TA or to at least make the technique so controversial that acquisition personnel will use the best-value technique instead.

There is a consensus in the so-called “acquisition reform” debate that the Pentagon needs to issue better and more detailed solicitations, which is another argument for preserving the LP/TA technique because it requires discipline and knowledge to write quality specifications and/or statements of work. In contrast, “best value” is often used as a crutch by agencies to allow contractors to tell DOD what to buy.

The key to successful use of LP/TA is for contracting officers to specify the critical acceptability criteria, which can often be easily accomplished with military equipment and services. Best value may be the appropriate technique when DOD doesn’t know precisely what it is seeking to purchase, or when the work is inherently difficult to describe. Acquisition personnel represented by the American Federation of Government Employees believe that the LP/TA technique provides the necessary level of performance at a lower cost to the government.
Acquisition 101: When a Bargain Isn’t a Bargain by Eric S. Crusius, a partner with Fed Nexus Law, who focuses on government contracts, cybersecurity, employment law and complex litigation.
LPTA certainly has its admirers, but even the most ardent supporters in the contracting community recognize its severe limitations. Nevertheless, J. David Cox, national president of the American Federation of Government Employees, offered a full-throated endorsement of LPTA in a recent column in Government Executive. Mr. Cox stated the reasons why LPTA is preferred to the “best-value premium” approach to acquisition.

LPTA is simply a road leading to mediocrity.

Here are several reasons he is wrong:

“Best-value premium” is a misnomer because these procurements still allow agencies to choose the lowest cost option. With any best-value procurement, the agency always has the discretion to choose the lowest bid unless something compelling exists that is worth a premium. This approach allows agencies the flexibility to pick the option that best suits their needs.

LPTA is often used where it should not be used. “Lowest price/technically acceptable” can be an appropriate mechanism in highly regulated or commoditized industries, where there is little differentiation between minimally acceptable products [such as the vacuum cleaners he mentions in the article??]. The approach, however, is popping up in situations where marginal product quality is a differentiator (such as medical products used to care for soldiers) and in the outcome-based services industry. A long dissertation is not necessary to explain why that approach is highly problematic. Would you like it if your children’s school hired its teachers on an LPTA basis?

LPTA often ends up costing more. This contracting method frequently attracts contractors who are unable to fulfill the requirements or complete the work without great assistance from the government customer. (This can be the case especially when past performance is not evaluated.) Eventually, drives up costs. It has held true through time with products that are minimally acceptable—the example of the vacuum cleaner is illustrative. In addition, this contracting method is driving responsible contractors away from doing business with the federal government, resulting in less competition. In fact, the number of small businesses participating in the federal marketplace has declined over the past few years.

There are also social reasons to shy away from using LPTA, such as lower wages and benefits for contractor employees and the exclusion of small businesses from government contracting, all of which drives down the overall economy.

While LPTA certainly has its place in federal contracting, that place is a small defined box with highly commoditized requirements. Anything larger robs agencies of much needed discretion, drives valuable contractors away from the federal marketplace, and enriches lawyers like me with more potential clients seeking assistance in filing bid protests.

Sunday, December 21, 2014

Change in evaluation method or quantity requirements from specifications

You are reminded that cases and articles are typically sliced, diced, rearranged, paraphrased and otherwise edited to my own ends, plus I often leave out necessary or other interesting material, so you must read the whole piece at the link rather than rely on my rendition.

GAO Decision Matter of: CGI Federal Inc.. File: B-410330.2, Date: December 10, 2014
CGI Federal Inc., of Fairfax, Virginia, protests the award of contracts to five other offerors under request for proposals (RFP). The RFP here, which is a follow-on to previously awarded contracts for system design and development and the production of limited deployment units, contemplates the award of contracts pursuant to which production units for unit, force, and submarine platforms will be ordered on a build-to-print basis. The RFP provided for the award of up to three indefinite-delivery/indefinite-quantity (ID/IQ) contracts with firm-fixed-price (FFP) and cost-plus-fixed-fee (CPFF) contract line items (CLINs).

The SSAC recommended that despite the solicitation language indicating that the agency intended to award up to three contracts, award be made to the five top-ranked offerors. In conjunction with its decision to increase the number of awards, the agency decided to change its strategy for placing delivery orders with the selected contractors. Specifically, the agency decided that it would not place 3-4 orders of larger quantities of CANES units annually as originally planned, but rather it would issue more orders for smaller quantities of CANES units in order to achieve more competition on a per order basis.

CGI raises a number of challenges to the agency evaluation of proposals. As a threshold matter, the protester argues the agency used a flawed price evaluation methodology, which produced a misleading result. In this regard, CGI contends that the agency knew prior to award that the solicitation’s stated approach to evaluating offerors’ prices, based solely on the highest order level of 15 units, departed from how the agency actually intended to order the units, which was to place orders for much lower levels. Accordingly, CGI maintains that the agency should have amended the solicitation’s price evaluation scheme to comport with the agency’s actual ordering needs.

CGI contends that the agency’s price evaluation methodology, which provided for comparing offerors’ prices at the maximum order level of 15 units, did not match the agency’s planned ordering needs as determined by the agency prior to award. Given this disconnect, the protester argues that the agency was required to amend the solicitation’s evaluation scheme to provide a reasonable basis for comparing offerors’ prices, one which matched the agency’s ordering needs. CGI further maintains that if the price analysis had been based on offerors’ NTE unit prices for quantities of 5 per delivery order, which is far more in line with the agency’s revised acquisition strategy, decision. its evaluated price would have been [deleted], rather than highest, which would clearly have had an impact on the best value tradeoff.

This case turns on two fundamental principles. One is that, while it is up to the agency to decide on some appropriate and reasonable method for evaluating offerors’ prices, an agency may not use an evaluation method that produces a misleading result. Raymond Express Int’l, B-409872.2, Nov. 6, 2014, 2014 CPD ¶ 317 at 6; Air Trak Travel et al., B-292101 et al., June 30, 2003, 2003 CPD ¶ 117 at 22. That is, the method chosen must include some reasonable basis for evaluating or comparing the relative costs of proposals, so as to establish whether one offeror’s proposal would be more or less costly than another’s. Id.

The other is that where an agency’s requirements materially change after a solicitation has been issued, it must issue an amendment to notify offerors of the changed requirements and afford them an opportunity to respond. Federal Acquisition Regulation (FAR) § 15.206(a); Murray-Benjamin Elec. Co., L.P., B-400255, Aug. 7, 2008, 2008 CPD ¶ 155 at 3-4.

For example, where an agency’s estimate for the amount of work to be ordered under an ID/IQ contract changes significantly, prior to award, the agency must amend the solicitation and provide offerors an opportunity to submit revised proposals. See Symetrics Indus., Inc., B-274246.3 et al., Aug. 20, 1997, 97-2 CPD ¶ 59 at 6. In Symetrics, our Office concluded that the agency should have amended a solicitation for an ID/IQ contract because although the solicitation initially estimated the agency would require 3,755 sequencers, the agency subsequently learned--prior to award--that the agency no longer had a requirement for 3,219 of the sequencers. Id. Similarly, in Northrop Grumman Info. Tech., Inc., et al., B-295526 et al., Mar. 16, 2005, 2005 CPD ¶ 45 at 13, our Office sustained a protest where the Department of the Treasury, prior to award, negotiated a memorandum of understanding with OMB and the General Services Administration that significantly changed the approach set forth in the solicitation and the FAR for determining whether to exercise contract options, making it significantly less likely that the options, which were part of the evaluation, would be exercised.

The circumstances here are unusual in that the meaningfulness of the price evaluation scheme set forth in the RFP changed between the closing date for receipt of FPRs and the date of award. That is, the record reflects that it made perfect sense to evaluate on the basis of 15/each unit pricing when the agency intended to award three contracts and issue 3-4 delivery orders per year. Evaluating on the basis of 15/each unit pricing no longer provided a rational basis for comparison, however, when, during the source selection process, the agency decided to increase the number of awardees to five, and to alter its ordering strategy to significantly increase the number of delivery orders annually, thereby decreasing the number of units to be acquired per delivery order.

Given this fundamental shift in the agency’s anticipated ordering plans, it was unreasonable for the agency to proceed with a price evaluation methodology that was divorced from these plans. Rather, the appropriate course of action was for the agency to amend the solicitation in a manner that would enable it to evaluate, and make a tradeoff decision based on, the offerors’ relative relevant prices.

The agency defends its actions on the basis that it followed the terms of the solicitation and that all offerors competed on an equal basis because the solicitation did not establish that the agency would, in fact, place orders at the 15/unit level. Regarding the latter point, the agency notes that offerors were to submit prices at each level and should have understood that orders could be placed at any of the 15 price levels. The agency’s arguments, however, miss the point.

We agree that the agency followed the terms of the solicitation, and that the offerors submitted prices on an equal basis. The problem is that the price evaluation, and resulting selection decision under which CGI did not receive an award due to its high price, were based on comparing prices for quantities of units that the agency now knows it does not intend to order.
We recognize that price evaluation in the context of an ID/IQ contract may be representative, and therefore something of a fiction; nevertheless, the fiction employed must bear some rational relationship to the agency’s needs. See CW Govt Travel, Inc.--Recon.; CW Gov’t Travel, Inc., et al., B-295330.2 et al., July 25, 2005, 2005 CPD ¶ 139 at 4-5.
Where the agency’s intended ordering strategy does not anticipate placing orders at the 15 unit per order level, we fail to see how comparing prices at this level, and using such prices as the basis for a tradeoff decision, can be understood to be reasonable. As explained above, where the disconnect between the terms of the solicitation and the agency’s order needs became apparent prior to award, it was incumbent on the agency to instead amend the solicitation to correct the flaw in the solicitation.

CGI further contends that the agency failed to conduct a price realism analysis, as required by the terms of the solicitation, and that it failed to recognize that the prices of one of the awardees were unbalanced. CGI also argues that the agency engaged in unequal discussions, assigned its proposal too low a rating for past performance, and unreasonably assigned NG’s proposal a performance confidence rating of satisfactory. We deny the protester’s remaining arguments.

Wednesday, August 6, 2014

The pendulum swings along the price to quality spectrum

When it comes to objectively observable source selection criteria, price is somewhat certain; quality is less so. The less objectively certain a factor is, the more discretion comes into play, and the greater the wriggle room to wrangle an angle that masks favoritism. Couple that with the mood swings in the public and holders of the public purse as economies swell and shrink, and attitudes shift. And so, the meme du jour in procurement shifts to getter more "value" for money to getting more cost savings. 

All that said for context to the next article below from blogger and editor John Keller, an easy and instructive review of the procurement pendulum swing.

Pentagon's lowest price technically acceptable (LPTA) guideline is latest attempt to attack costs
The U.S. Department of Defense has a long history of trying to balance the quality and price of the nation's weapon systems. With tight budgets the rule these days -- and the threat of another round of sequestration as early as 2016 -- the scales may be tipping in favor of price over quality.

There was a day many of us remember thirty-some years ago when the goal of military program managers was to procure only the best; money was no object under most circumstances. While this approach secured for the United States the world's mightiest military force, it also bought for us thousand-dollar toilet seats, hundred-dollar hammers, and fifty-dollar electronic diodes.

Among the roots of the problem then was the custom-design nature of military systems. Buying the best required technologies and components tailored specifically for each application; rarely was the economy of scale of the commercial market brought to bear on military procurement challenges.

There also was a bias in those days of buying from the commercial market. There was a belief that buying commodity items at discount-store prices would result in poor quality unacceptable to critical military missions. Better to pay too much than compromise military capability was the prevailing attitude.

Then the Berlin Wall came down, and with it the end of the Cold War -- at least that particular iteration of the Cold War -- that lasted from about the end of World War II until 1990. With a perceived end of the Soviet threat, military planners during the Clinton Administration decided it was time to reap a "peace dividend," and reduce military spending.

One of the first results of the so-called peace dividend was the notion of COTS -- short for commercial off-the-shelf -- brought to us in 1993 by Bill Clinton's secretary of defense, William Perry.

COTS, often incorrectly criticized at the time as a conduit for bringing substandard equipment into the military, was a solid concept, especially as it remains today more than two decades later. COTS wasn't an attack on quality, but instead was an acknowledgement that the military could buy standard off-the-shelf components economically and without compromising quality.

With little doubt, COTS has saved the military millions of dollars -- perhaps a lot more -- and rather than compromising quality actually has enhanced quality in many cases by implementing industry standards and best practices, rather than custom-designing ordinary components. Continuing downward pressure on the Pentagon budget, however, is calling for additional new measures in military procurement.

One of the latest is "lowest price technically acceptable," which the military shortens to LPTA. Like COTS, LPTA is intended to prevent the Pentagon from paying too much for what it buys -- commendable in this day and age -- but also like COTS, the new term LPTA often comes under scrutiny for its perceived threat of compromising quality.

Essentially, LPTA calls on the Pentagon's procurement officers to determine a level of quality that is good enough for the job at hand. Any contractor bid that falls within this "good-enough" guideline becomes a competition finalist, and the one submitting the lowest bid wins the contract.

In theory, LPTA does not leave military buyers with the leeway to pay a little extra for superior quality; it's all about what's good enough at the lowest price. While this emphasis on price over quality does have the potential to compromise quality, there also may be some benefits.

It's not the way all procurements should be run, granted, but for a growing number of components ranging from single-board computers, backplanes, and enclosures, LPTA should do the job for which it's intended.

There may be additional benefits to LPTA -- provided this procurement method is applied to the right kind of purchases -- and that is enhanced industry competition. LPTA, with its emphasis on price, has the potential to bring more companies into the military's supply chain.

The kind of procurement approach that LPTA outlines offers the advantage of a growing number of companies competing for military work on the basis of price as well as quality. If this works out, the military could have a broad selection of technologies and components to find the right hardware for the job, even when budgets are tight.
I like the moral expressed in this story: "It's not the way all procurements should be run, granted, but ... LPTA should do the job for which it's intended."

It is important to remember that there are many methods of source selection. Why? Because they are a reflection that one size does not fit all, as I am always reminded when I go, on those rare occasions, clothes shopping. It is important, when choosing a method of source selection, that the most appropriate method be chosen for the desired outcome. You don't need to spend the money and time on a bespoke suit to wear every day to work. And you don't want to get married in that same suit.

What the US federal government calls LPTA, Guam, and ABA Model Procurement Code, calls a "multi-step bid" method of source selection. It's a variant on the generic competitive sealed bid procedure, where all proposed bids are evaluated for product acceptability and then lowest price is chosen.

Multi-step does not rank proposals, but does categorize proposals as technically "acceptable", "potentially acceptable" and "non-acceptable". Non-acceptable proposals are eliminated in the initial review. If a proposal has the potential to meet specifications with a little tweaking of either the bid specifications or the proposal or both, and that action is taken without prejudice to other technically acceptable proposals, the proposal gets added to the final pool of "technically acceptable" bids. At that point sealed price bids are opened for all technically acceptable bids, and low price wins. See 2 GAR § 3109(r) in Guam procurement regulations for more.

Sunday, January 12, 2014

Unfair and reasonable price and ranking conditions in solicitations

It is one thing to carefully tailor specifications to meet minimum needs. Another to tailor competition. And yet another to tailor out any judgment or consideration process. The following is another from Lexology.com (reg. req'd.), in association with the Association of Corporate Counsel, and its excellent coterie of contributors. It involves US federal government contracts and its laws and regulations.

This is a selection of excerpts from the article. You will need to read the whole article for context, citations, sources, etc.

Beware of protest-proof procurements by Thomas P. Barletta , Peter L. Wellington, Paul R. Hurst , Michael J. Navarre and Anthony Rapa, of the firm Steptoe & Johnson LLP
Some federal government agencies are taking extraordinary steps to try to insulate their source selection decisions from the bid protest process. Below, we discuss three examples of this phenomenon: (1) solicitations that call for awarding the contract to the highest technically rated offeror who proposes a “fair and reasonable” price; (2) solicitations that prescribe specific point scores for various technical features and call for ranking the technical merits of the proposals based solely on the total points earned; and (3) solicitations that provide for very limited, highly circumscribed cost/price evaluations.

Occasionally solicitations will provide for award to the highest technically rated offeror who has proposed a “fair and reasonable” price. Under such an approach, all proposals are subject to a threshold determination as to whether their proposed prices are “fair and reasonable.” Proposals that clear this bar are then evaluated strictly according to their respective technical merits. Price does not otherwise factor into the agency’s analysis of which proposal offers the best value to the government. The solicitation may even explicitly assert that the agency will not engage in a price/technical tradeoff analysis in evaluating proposals. An offeror who waits until after award to file a protest asserting that its price advantage outweighed the awardee’s technical advantage will likely be met with a motion to dismiss the protest as an untimely challenge to the terms of the solicitation. Therefore, potential offerors who believe that their pricing is likely to provide them with a competitive advantage should consider filing pre-award protests on the ground that this approach is contrary to fundamental principles of procurement set forth in the Federal Acquisition Regulation (FAR), statutes and case law.
[I point out here that this RFP format is specifically authorized in Guam procurement law (5 GCA §§ 5216, and 5121) for the procurement of professional services. Indeed, it is the form prescribed for the method of source selection for professional services first adopted, and later abandoned, by the ABA Model Procurement Code.]
It is well-established that source selection officials are required to meaningfully consider price in making source selection decisions. The FAR provides that "[w]hile the SSA may use reports and analyses prepared by others, the source selection decision shall represent the SSA’s independent judgment. The source selection decision shall be documented, and the documentation shall include the rationale for any business judgments and tradeoffs made or relied on by the SSA, including benefits associated with additional costs." See FAR § 15.308.

Furthermore, agencies are required by statute to make award “to the responsible source whose proposal is most advantageous to the United States, considering only cost or price and the other factors included in the solicitation.” See 41 U.S.C. § 3703(c) (formerly 41 U.S.C. § 253b(d)).

The Government Accountability Office (GAO) has consistently upheld these principles in requiring agencies to consider price when making best value determinations, and has sustained protests where agencies have failed to engage in price/technical tradeoff analysis.

In Cyberdata, GAO sustained a protest where a solicitation provided for downselecting quotations based on technical factors only. Offerors were to be ranked strictly based on their technical scores without regard to price, and the top twelve were to be invited to give oral presentations. Price was to be considered only when a smaller number of quotations were chosen from among the top twelve as offering the best value. GAO sustained the protest, holding that
"a best value analysis necessarily encompasses consideration of an offeror’s price or cost since, to be meaningful, a best value determination requires a weighing of the value and benefits associated with a firm's approach against their associated cost to the government. In a best value procurement, it is the function of the source selection authority to perform a tradeoff between price and non-price factors, that is, to determine whether one proposal's superiority under the non-price factor is worth a higher price. Even where, as here, price is stated to be of less importance than the non-price factors, an agency must meaningfully consider cost or price to the government in making its selection decision. Thus, before an agency can select a higher-priced proposal that has been rated technically superior to a lower-priced but acceptable one, the decision must be supported by a rational explanation of why the higher-rated proposal is, in fact, superior, and explaining why its technical superiority warrants paying a price premium."
It is also noteworthy that GAO invoked the “significant issue” exception to its timeliness rules in the Cyberdata protest, which had been filed after award, because the subject was “one of widespread interest to the procurement community.” However, there can be no assurance that GAO would invoke this rarely-used exception again in a similar situation, so it would be prudent for potential offerors to file pre-award protests when faced with solicitations that provide for award to the highest technically rated offeror with a “fair and reasonable” price.

We have also seen examples of solicitations that prescribe specific point scores for various technical features and call for ranking the technical merits of the proposals based solely on the total points earned. Under such an approach, the agency will merely confirm the presence or absence of the prescribed technical features in each proposal, add up the prescribed points for each feature found to be present, and select the proposal(s) with the highest point total(s). In some cases, the offerors may even be instructed to score themselves by submitting self-scoring worksheets. In any event, under this approach, the technical evaluation consists merely of mechanically comparing offerors’ point scores, without any judgments or analyses regarding the actual qualitative differences between the technical proposals. An offeror who waits until after award to file a protest asserting that its technical proposal is qualitatively better than other proposals regardless of their respective point scores will likely be met with a motion to dismiss the protest as an untimely challenge to the terms of the solicitation. Therefore, potential offerors who believe that their technical proposals will contain qualitative advantages not adequately captured by the point scores should consider filing pre-award protests on the ground that this approach is contrary to fundamental principles of procurement law.

In a number of post-award protests, GAO has strongly criticized technical evaluations that relied exclusively on point scores. It has consistently held that “[a]n award decision is not reasonable . . . where the agency makes its award decision based strictly on a mechanical comparison of the offerors’ total point scores.”

Sunday, November 21, 2010

The price is not always right

Any statement of procurement law to the effect that the award goes to the lowest responsive and responsible bid must be read with some implied qualifications. It is not simply a low bid that wins, but a reasonably low bid.

In the same way that a sole bid response must be closely evaluated for price reasonableness, so must an abnormally low bid.


This seems to be the case around the world.

Abnormally low offers - too good to be true? (UK)
According to the press, the existing contract was worth around £34 million a year. When it came up for renewal, the challenger, Morrison Facilities Services Limited (MFS) submitted a bid of around £23 million. However, it was beaten by the £17 million bid of Connaught PLC. The MFS bid and the other bids received were all around 25 per cent to 33 per cent higher than the Connaught bid.

At the hearing, a witness for MFS deconstructed Connaught's prices to show that, in MFS' view, it was simply physically impossible for Connaught to actually deliver the requirement at that low price. There was also evidence that the Council itself had queried Connaught's price and had twice sought confirmation.

Regulation 30(6) of The Public Contracts Regulations 2006 gives contracting authorities a right (not an obligation) to reject an abnormally low bid, provided proper investigation has taken place.

Given the tough economic times, contracting authorities are likely to be receiving a greater number of low-priced bids from bidders desperate to get a foot in the door. This case shows that contracting authorities will do well to be on their guard; if a contracting authority intends to award a contract to a very low bidder, it should make sure that proper investigation does take place and that there are objectively reasonable reasons for the low-price of the bid.

Contractor's Opportunistic Bidding Behavior and Equilibrium Price Level in the Construction Market (Taiwan)
The competitive bidding system has been to blame for abnormally low bids, which are considered as one of the main causes of poor project quality. Previous studies have regarded the pricing of bidders as an optimum decision based on contractor's cost and market competition level. However, the sell to produce characteristic of construction projects may induce contractors to offer a low bid and then make up the amount initially sacrificed from beyond-contractual reward (BCR) gained through cutting corners and claims.

The price level for projects with a strict owner is remarkably higher than for those with relatively less strict owners. Improvement in the construction management system of projects is crucial to lower the possibility that contractors gain BCR and do opportunistic bidding, and to further enhance project quality.

Public Procurement - India (India)
32 What constitutes an 'abnormally low' bid?

'Abnormally low' bids are those that vary from the estimated rates by more than 25 per cent, even after updating the scheduled rates to match the prevailing cost index.

33 What is the required process for dealing with abnormally low tenders?

Abnormally low price may lead to a conclusion of an anti-competition move and this is a ground to order re-tendering. Factors have been prescribed to judge the reasonableness of price (though these are usually resorted to if price is found to be too high (and not abnormally low).

Procurement Procedures Amended to Stop Malicious Low Bids (Taiwan)
The Public Construction Commission (PCC) has revised the “Procedures for Handling Bids With a Total Bid Price Less Than 80% of the Government Estimate in Accordance With Article 58 of the Government Procurement Act” to require agencies handling lowest-tender procurement projects to demand explanations from companies that win bids with abnormally low tenders. The agencies can also refuse to allow such bidders to win bids by providing security. This new provision can stop companies from maliciously using low bids to win contracts, and upgrade the quality of contract performance.

To help agencies evaluate whether an explanation given by a bidder is reasonable or not, another new provision stipulates directions for such explanations—why the bid price is so low, and how the low bid will not impair the quality of execution. If the explanation provided by the bidder is unrelated to completion of the subject of the procurement, it will not be accepted.

Damage to Treasury: Abnormally Low Tenders in Public Construction Works (Turkey)
A detailed analysis of the submitted questionnaires revealed a number of reasons for Abnormally Low Tenders (ALTs) and their adverse effect on the construction industry. Staying in the business, miscalculation of bid price, work experience document, and inaccuracy of the conceptual cost were found to be the main reasons behind ALTs. A better database system for contractors on market unit prices, a better quality control assessment in construction and postconstruction phases, full complete design documents in tender packages, and a better evaluation system on the assessment of ALTs are recommended by the study.

Beware if the contractor bid is too low (California)
Do not automatically accept the lowest bid. In fact, you should beware of any bid that is substantially lower than the others. It probably indicates that the contractor made a mistake or is not including all the work quoted by his or her competitors. You may be headed for a dispute with your contractor if you accept an abnormally low bid. It is also possible that this contractor will cut corners or do substandard work in order to make a profit on the job.

Surete du Quebec dumps security firm contract (Canada)
On Monday, the Surete du Quebec announced it was cancelling its contract with Secur-Action to provide security at its headquarters on Parthenais St.

The same day, Quebec's public security ministry announced on its website that it would not finalize a deal with Secur-Action to provide security at Montreal's courthouse or the courthouse on Gouin Blvd., built to hold trials of organized crime figures and street gang members.

Questions surrounding the company's bids came to light this month when Montreal Mayor Gerald Tremblay asked for an investigation after learning that Secur-Action had submitted an "abnormally low bid" to provide security at Montreal police headquarters on St. Urbain St. The one-year contract was for $874,802, according to La Presse.

The bid was much lower than a similar bid submitted several years ago by the firm Cartier, which had stopped applying for the contract because it was not profitable enough.

Read more: http://www.montrealgazette.com/news/Surete+Quebec+dumps+security+firm+contract/3595011/story.html#ixzz15yRnvtwo

The Procurement Rules and Regulations of the Royal Government of Bhutan:
5.4.5 Abnormally Low Bid

5.4.5.1 Where the prices in a particular bid appear abnormally low or the bid appears seriously unbalanced, the Procuring Agency may reject it only after seeking written explanations from the bidder submitting the low or seriously unbalanced bid. In the case of a bid which appears seriously unbalanced, the procuring agency shall request from the bidder an analysis of rates of the relevant items.

5.4.5.2 The Procuring Agency may take into consideration explanations which are justified on objective grounds including:
a. The economy of the construction method or the method by which the goods or services are to be provided; or
b. The technical solutions chosen; or
c. The exceptionally favourable conditions available to the bidder for the execution of the contract; or
d. The originality of the work, product or service proposed by the bidder.
e. The internal consistency of those prices with the construction methods and schedule proposed.

5.4.5.3 If the Procuring Agency decides to accept the abnormally low bid or the bid with the seriously unbalanced rates after considering the above factors, the bidder shall be required to provide additional differential security equivalent to the difference between the estimated amount and the quoted price in addition to the performance security.

The situation in Sweden:
31 What constitutes an ‘abnormally low’ bid?

There is no general definition of an abnormally low bid in the PPA or UPA. The contracting authority or entity has to determine if a bid is abnormally low based on the circumstances of the procurement. There is no precedent in case law regarding what constitutes an abnormally low bid.

32 What is the required process for dealing with abnormally low tenders?

A contracting authority or entity may refuse tenders that it considers abnormally low. Such refusal must, however, be preceded by a written request for an explanation of the low tender value which has not been satisfactorily answered by the tenderer. A request for an explanation may relate to details such as the economics of the construction method, the manufacturing process or the services provided, technical solutions or any exceptionally favourable conditions available to the tenderer for the execution of the work, supplies or services, the originality of the tenderer’s proposal, compliance with the provisions relating to employment protection and the possibility of the tenderer obtaining state aid. The contracting authority or entity shall verify those constituent elements by consulting the tenderer, taking into account the evidence supplied.

UPDATE JUNE 2, 2016   For a recent (as of the date of this Update) view on this subject from the perspective of the UK, see  Abnormally Low Tenders posted on the CMS Law Now website.
The rules around tendering for public contracts have been updated recently and are set out in the Public Contracts Regulations 2015 (“PCR 2015”).  Regulation 69(1) of the PCR 2015 directs that a contracting authority shall require a tenderer to explain the price or costs proposed in the tender where a tender appears to be abnormally low.  However, while this mandatory requirement on contracting authorities may appear clear, there are surprisingly few examples of this Regulation (or its non-mandatory predecessor - Regulation 30(6) of the Public Contracts Regulations 2006 (“PCR 2006”)) coming under judicial scrutiny in the United Kingdom.  Elsewhere in the EU, award decisions are more often challenged on the ground of abnormally low or high prices and can be a fertile ground for court appointed experts.
The main area of confusion arises in relation to what is meant by “abnormally low”.  In other words there is no explanation of the “trigger point” included in the PCR 2015 at which the contracting authority should require the tenderer to explain its tender.  This gives rise to a slightly odd position that it is required only to ask questions of the tenderer if the tender appears to be abnormally low but unless it asks the questions the authority may not know if the tender is abnormally low in the first place.

Read More at the article's link above.