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 Bridge contract. Show all posts
Showing posts with label Bridge contract. Show all posts

Sunday, October 18, 2015

A bridge not FAR enough

United States Government Accountability Office Report to Congressional Requesters, October 2015

Note that the usual caveats of this blawg apply: read the articles in original at the links. I cut, paste, omit, rearrange, paraphrase and otherwise take great liberties with the material.  Do not rely on my version.
SOLE SOURCE CONTRACTING: Defining and Tracking Bridge Contracts Would Help Agencies Manage Their Use
Certain members of the Committee on Homeland Security and Governmental Affairs, United States Senate, asked GAO to assess the use of bridge contracts by federal agencies. This report examines (1) the insights of selected agencies into their use of bridge contracts; (2) key characteristics of selected bridge contracts; and (3) the reasons why bridge contracts are being used.

When a contract is set to expire and there is a continuing need for services, but the follow-on contract is not ready to be awarded, the government can extend the existing contract or award a short-term sole-source contract to an incumbent contractor. These types of contracting arrangements have been referred to as “bridge contracts” and are used to ensure there is no gap in services. While bridge contracts can be a necessary and appropriate tool, their use has also been associated with negative effects, such as higher contract prices due to a lack of competition and the inefficient use of staff and resources.

Because bridge contracts are not defined in the FAR, GAO constructed a definition based on its prior work and that of other federal agencies. GAO reviewed policies and procedures at three agencies that were among those with the highest number of potential bridge contracts. The agencies included in GAO’s review—the Departments of Defense (DOD), Health and Human Services, and Justice—had limited or no insight into their use of bridge contracts, as bridge contracts were not defined or addressed in department-level guidance or in the Federal Acquisition Regulation (FAR).

However, GAO found that two DOD components, the Navy and Defense Logistics Agency, have instituted definitions, policies, and procedures to manage and track their use. The components took these steps due to concerns that bridge contracts were being used too frequently and reducing competition. Federal internal control standards stipulate that management should identify, analyze, and monitor risks associated with achieving objectives, such as maximizing competition. Staff from the Office of Federal Procurement Policy (OFPP), which provides direction for government-wide procurement policies so as to promote efficiency and effectiveness in government acquisitions, acknowledge that the use of bridge contracts may introduce risks related to a lack of competition.

Without a definition of bridge contracts and guidance for tracking and managing their use, agencies are not able to fully identify and monitor these risks and increase opportunities for competition.

Based on our reviews of contract documentation and information provided by agency officials, we found that the most commonly cited reasons for the use of a bridge contract across the 73 contracts were related to acquisition planning issues—in particular the late completion of key acquisition planning documentation, such as statements of work, that are needed to begin a solicitation. Acquisition planning activities generally begin when the program office identifies a need, involves research and preparation of acquisition documents by both the program office and the contracting office, and concludes when the contracting office issues a solicitation. Our prior work has identified challenges that agencies faced in relation to acquisition planning on contracts for services, such as defining their needs and providing guidance to program offices on timeframes for pre-solicitation activities, such as defining requirements in a statement of work document.

Acquisition planning delays, such as revisions to statements of work and delays in source selection, as well as an inexperienced and overwhelmed acquisition workforce, bid protests, and budget uncertainties contributed to the use of bridge contracts in the cases GAO studied. Often, more than one of these factors led to the use of a bridge contract. Of the 26 cases in GAO's review where follow-on contracts were awarded, 23 were awarded competitively, in some instances leading to savings. The fact that competition occurred in almost all cases, which can save the government money, highlights the importance of better management controls over use of bridge contracts.

To gain insights into the selected agencies’ use of bridge contracts, we collected and analyzed any policies and procedures on bridge contracts and interviewed officials about their knowledge of the use of bridge contracts and any management controls that may be in place. The agencies we reviewed had limited or no insights into their use of bridge contracts. None of the agencies have agency-level policies to manage and track their use of bridge contracts, nor do their acquisition regulations define bridge contracts. HHS officials told us that their agency has no overarching policy because the agency does not have a standard definition for bridge contracts. Officials at DOD said that, at the department-level, the agency did not have any policies because bridge contracts had not previously been raised as a specific concern at the department. DOJ officials indicated they see defining bridge contracts as a government-wide issue, and officials from one of their components told us that the concept of defining bridge contracts was a new one to them.

Because of its role to provide direction for government-wide procurement policies, regulations, and procedures and to promote economy, efficiency, and effectiveness in government acquisitions, we interviewed staff at the Office of Management and Budget’s (OMB) Office of Federal Procurement Policy (OFPP) to discuss their views on the benefits and challenges on the use of bridge contracts. We also used federal internal control standards as criteria for assessing agencies’ insights into the use of bridge contracts.

To identify key characteristics of selected bridge contracts and assess the reasons why bridge contracts are being used, we selected a nongeneralizable sample of 73 bridge contracts for services. We focused on service contracts since agency officials and our prior work indicated that bridge contracts were predominantly used for services. We conducted a high level review of the 73 contracts—collecting and reviewing contract award and extension documentation, such as justification and approval (J&A) documents, price negotiation memorandums, relevant contract modifications, and file memoranda.

We then selected a subset of 29 contracts from 6 of the 8 components for a more in-depth review, based on several factors, specifically the contract value, obtaining a mix of contract extensions and stand-alone bridge contracts, and the location of the contract files. For this in-depth review, we reviewed the bridge contract, the contract preceding it, and, if awarded at the time of our review, the follow-on contract. The results from the sample of contracts included in our review are not generalizable, but are designed to provide illustrative examples of the characteristics and rationale for the use of bridge contracts at the selected agencies and components and supplement the information obtained from our interviews and review of agency policies and procedures. We also interviewed contracting and program officials to discuss the facts and circumstances related to the award of the bridge contracts for the subset of 29 contracts in our sample, and the challenges, if any, related to their use.

The federal government contracts for a variety of services, from elevator maintenance to program management support, and often has a need to continue these services beyond the lifespan of an individual contract. However, in certain situations, it may become evident that a base contract and any option years will expire before a subsequent contract to meet the same need can be awarded. In these cases, because of time constraints, contracting officers generally use one of two options: (1) extend the existing contract for up to 6 months or (2) award a short-term stand-alone contract to the incumbent contractor on a sole-source basis to avoid a lapse in services. While these contracting options have been informally referred to as bridge contracts by some in the acquisition community, no formal definition of bridge contracts exists nor is there a requirement to track them in the Federal Acquisition Regulation (FAR). For the purposes of this report, we established the following definitions:
• Bridge contract. An extension to an existing contract beyond the period of performance (including option years), or a new, short-term contract awarded on a sole-source basis to an incumbent contractor to avoid a lapse in service caused by a delay in awarding a follow-on contract.
• Predecessor contract. The contract in place prior to the award of a bridge contract.
• Follow-on contract. A longer-term contract that follows a bridge contract for the same or similar services. This contract can be competitively awarded or awarded on a sole-source basis.
Contract extensions and the award of stand-alone bridge contracts are established in different ways. If a contracting officer needs a bridge contract and opts to extend an existing, predecessor contract, the contracting officer may use a number of different authorities to do this. If the predecessor contract included the “option to extend services clause,” the contracting officer could use this clause to extend the contract for up to six months, based on the FAR. If the contracting officer determines that a new short-term sole-source contract should be awarded to avoid a gap in services, the FAR generally requires that the contract award be supported by a written justification known as a justification and approval document (J&A). The J&A must include sufficient facts and rationale to justify the use of a sole-source contract.

While OMB has stated that noncompetitive contracts can play an important role in helping agencies address the needs that arise during emergencies, we and others have noted that competition is the cornerstone of a sound acquisition process and OMB has issued guidelines for federal agencies to increase competition and reduce their spending on sole-source contracts.

Navy, and Defense Logistics Agency (DLA) DLA—established policies in 2012 and 2013, respectively, regarding the use of bridge contracts. Both components’ policies were established to reduce reliance on bridge contracts and note that bridge contracts can be an impediment to competition. DLA’s policy further states that bridge contracts may be indicative of a lack of adequate preparation for follow-on acquisitions. DLA officials we spoke with told us that there was concern at DLA regarding the impact bridge contracts could have on competition, since they effectively delay competition by extending existing contracts or awarding sole-source contracts to incumbent contractors. Officials said that they hope the policy will increase competition at DLA by focusing management attention on the use of bridge contracts and tracking their use. In both cases, these components’ policies go beyond the standard J&A requirements for sole-source contracts to specifically address bridge contracts:
• Explanation as to why the need for a bridge contract is not due to lack of advanced planning or inadequate procurement execution.
• Justification for the length of the bridge contract.
• Discussion of actions to be taken to avoid additional bridge contracts.
Navy further requires:
• Certification of the urgency of the requirement.
• Signature of the program manager and the contracting officer.
In addition, one activity within the Army—the Health Care Acquisition Activity (HCAA), which was not included as part of our review—issued a policy memorandum in November 2008 that established a definition and an approval and tracking mechanism for bridge contracts. Similar to the policies at the Navy and DLA, HCAA’s policy was established due to concern over the increasing reliance on bridge contracts at the activity. In particular, the policy stated that there was concern that bridge contracts, which prevent competition, were being awarded to expand the scope of the original requirement, which was increasing costs. The policy and compliance branch at HCAA developed a tracking system to account for the number of bridge contracts awarded. According to HCAA officials, issuing the policy memorandum and requiring officials to report their use of bridge contracts has enhanced the activity’s ability to track bridge contract use and prevented the award of bridge contracts that increase the scope of work established by the predecessor contract.

The fact that the full length of a bridge contract, or multiple bridge contracts for the same requirement, is not readily apparent from the review of an individual J&A presents a challenge for those agency officials responsible for approving the use of bridge contracts. Approving officials, signing off on individual J&As, would not have insight into the total number of bridge contracts that may be put in place by looking at individual J&As alone. Without a definition and a policy for bridge contracts, J&A documentation generally provides information on the individual contract covered by the J&A, and on the anticipated period of performance and estimated contract value at the time of award, rather than a full picture of the cumulative time and cost associated with bridging a gap in services for a requirement.

The FAR requires that contracting officers establish that the prices paid for contracts are fair and reasonable and expresses a preference for comparison of prices obtained through competition. Because competition is absent with the award of a bridge contract, contracting officers’ fair and reasonable price determinations become imperative. To determine the extent to which the price paid by the government changed when a bridge contract was awarded to the incumbent contractor for the same services acquired under a previous contract, we conducted a price analysis for 10 of the 29 bridge contracts included in our in-depth review. We found that for 5 of the 10 contracts, the price paid for services on the initial stand-alone bridge contract or contract extension increased from that of the predecessor contract. Of the remaining 5 contracts, in 4 cases the price paid remained the same, and for the remaining contract the price decreased.

Follow-on contracts were competitively awarded for 23 of 26 contracts included in our in-depth review. The 3 remaining follow-on contracts were awarded on a sole-source basis. As noted above, competition generally leads to more favorable pricing. The fact that the vast majority of follow-on contracts were competed after the bridge contract expired highlights the urgency of ending bridge contracts as soon as possible. For example, one contracting official responsible for a contract told us that by awarding the follow-on contract competitively, the incumbent contractor had to re-evaluate what price the market demands for these services. Competition has generally been considered to be associated with achieving more favorable prices, and we and others have cited potential savings from competition in prior work.

A variety of reasons caused delays that resulted in the use of bridge contracts, but late completion of documentation needed to solicit follow-on contracts was the most frequent reason that we identified across our sample of 73 contracts. Contracting officials told us that acquisition workforce problems—such as inexperienced staff and frequent turnover of contracting and program office staff—also led to the use of bridge contracts and influenced other delays, such as late completion of acquisition planning documentation and challenges during source selection. The majority of agency officials that we interviewed identified bid protests as a common reason for the use of bridge contracts, and we found that bid protests had caused delays in only eight of the 29 contracts included in our in-depth review and that bid protests created substantial delays in awarding follow-on contracts.

Our in-depth review of 29 contracts further underscored that acquisition planning issues frequently led to the use of bridge contracts and provided additional insights into the nature of these issues. For example, the majority of the contracting officials that we interviewed cited the late submission of key acquisition planning documentation from program officials as one of the most common reasons why bridge contracts are needed. For 18 of the contracts, contracting officials told us that the statement of work, in particular, was either submitted late by the program office, required multiple rounds of revisions before it was ready to be published, or a combination of those two factors contributed to the need for a bridge contract. Acquisition planning challenges stemming from the coordination of program and contracting offices have been highlighted in some of our past work.

Contracting officials from multiple agencies told us that late statements of work were often a symptom of a lack of knowledgeable and seasoned staff in program offices. We found that acquisition workforce challenges—in particular, inexperienced and overwhelmed staff, as well as staff turnover—led to the use of bridge contracts and influenced other delays, such as the late completion of acquisition planning documentation and challenges during source selection. Contracting officials from multiple agencies told us that late statements of work were often a symptom of a lack of knowledgeable and seasoned staff in program offices. We have found and reported on government-wide acquisition workforce challenges for many years, including DOD’s efforts to rebuild the capacity of its acquisition workforce.

Contracting and program officials from all three agencies cited staff turnover as another driver of bridge contracts. As a point of comparison, the Navy had greater institutional knowledge regardless of staff turnover due to the high level of detail provided in their J&As and contract documentation.

The majority of agency officials that we interviewed identified bid protests as a common reason for the use of bridge contracts. While contract documentation cited bid protests as reasons for delay in five of the contracts in our high-level review, when we reviewed the contracts in-depth we found that bid protests caused delays in only eight of the 29 contracts but that the protests introduced substantial delays to the acquisition process.

In seven of the eight instances of bid protests that we identified, the incumbent contractor protested the award of a follow-on contract to a new vendor or the terms of the solicitation. However, only two of those protests were sustained. Most of the losing incumbents were unsuccessful in obtaining follow-on contracts. We also found that as a result of the incumbent’s protests, incumbent vendors kept providing services — in a noncompetitive environment — well after the predecessor contracts expired.

While bridge contracts can be a useful tool in certain circumstances to avoid a gap in services, they are typically envisioned to be used for short periods of time. When these noncompetitive contracts are used frequently or for prolonged periods of time, the government is at risk of paying more than it should for goods and services. Because we found that almost all of the bridge contracts in our review were ultimately followed by competitive contracts—which can lead to savings for the taxpayer—the importance of awarding these contracts in a timely manner is heightened.

Bridge contracts have been identified not only across the three agencies and eight components included in our review, but at other agencies as well, as evidenced by our past work and that of others. Thus, the importance of defining and tracking bridge contracts. A uniform, government-wide definition and strategies for tracking and managing the use of bridge contracts would help ensure all agencies have better insights into their use of these contracts and provide agencies with the information necessary to manage their use. Otherwise, agencies are left without a complete picture or understanding of how long a bridge contract has been in place. Without such information, it is difficult for agencies to take steps to reduce their reliance on noncompetitive bridge contracts or remediate internal deficiencies—such as issues related to acquisition planning or challenges with the acquisition workforce—that may lead to delays in the award of follow-on contracts.

we recommend that the Administrator of OFPP take the following two actions:
1. Take appropriate steps to develop a standardized definition for bridge contracts and incorporate it as appropriate into relevant FAR sections, and
2. As an interim measure, until the FAR is amended, provide guidance to agencies on
• a definition of bridge contracts, with consideration of contract extensions as well as stand-alone bridge contracts; and
• suggestions for agencies to track and manage their use of these contracts, such as identifying a contract as a bridge in a J&A when it meets the definition, and listing the history of previous extensions and stand-alone bridge contracts back to the predecessor contract in the J&A.

Further articles on this GAO report:
Bridge Contracts Need Improved Oversight, Says GAO

Temporary 'Bridge Contracts' Risk Overpayments

When a 'short-term' extension is a bridge too far

Monday, March 16, 2015

Bridge contracts vs Planning principle

This post involves a GAO decision involving, on one hand, the planning principle, and on the other the concept, replete with moral hazard, of a "bridge contract". Since Guam will soon be debating the adoption of bridge contracting as a method of source selection, I thought this is an instructive case study.

The planning principle is a core principle of American procurement philosophy, and likely other robust regimes. In the federal sphere, the Federal Acquisition Regulations ("FAR") devote SubPart 7 to it. The main theme of this policy is: 
     Agencies shall perform acquisition planning and conduct market research for all acquisitions in order to promote and provide for—
(1) Acquisition of commercial items to the extent practicable;
(2) Full and open competition to the extent practicable;
(3) Selection of appropriate contract type; and,
(4) Appropriate consideration of the use of pre-existing contracts, including interagency and intra-agency contracts, to fulfill the requirement, before awarding new contracts.

The importance of (2), "full and open competition", is underscored by FAR Subpart 6.301(c): "Contracting without providing for full and open competition shall not be justified on the basis of — (1) A lack of advance planning by the requiring activity...."

The importance of (2), "full and open competition", in this case runs up against the "to the extent practicable" qualifier when the contract awarded is based on the Section 8(a) Small Business rules.

This particular case seems to be concerned primarily with the interplay of (2) and (4), in circumstances involving the granting of a bridge contract. Here, it is worth pointing out that a bridge contract is, or should be, an absolute last resort, tailored to the particular circumstances, because it is awarded without competition, a pillar principle of procurement. It is the feature of no competition which saturates bridge contracts with moral hazard.

In should be noted that the ABA Model Procurement Code, which forms the basis for most of Guam's procurement law, has broadly similar principles and purposes. Though not as fully formed as the FAR version, the ABA version as reflected in Guam law provides "All procurements of supplies and services shall, where possible, be made sufficiently in advance of need for delivery or performance to promote maximum competition and good management of resources." (5 GCA § 5010.)

In Guam law, the emphasis on and primacy of planning is emphasized by the limitations placed on "emergency procurement" of supplies ("goods and supplies" per the literal statute, but "goods" is not a defined term in the procurement law, but "supply" is defined as somewhat analogous to the term "goods" under the UCC). Notwithstanding the gubernatorial power to declare emergencies for whatever cause or effect, the procurement law proscribes contracting for supplies and services in an "emergency" unless the "emergency" is not man-made: "Emergency means a condition posing an imminent threat ... which could not have been foreseen through the use of reasonable and prudent management procedures...." (5 GCA § 5030(x).)

And so, to the chase, but note: This case also involved the particular requirements of the Small Business Set Aside preference scheme (Section 8(a)), which impinged on the outcome of the decision, the details of which I skim over (read the whole decision at the link):


Matter of: eAlliant, LLC: B-407332.4; B-407332.7, December 23, 2014
eAlliant, LLC, of San Diego, California, protests the award of a sole-source bridge contract (No. N65236-15-C-1003), for a period of 1 month, followed by up to five 1‑month options, to Systems Integration and Management, Inc. (SIM), of Arlington, Virginia.

The Navy currently fulfills its requirement for service desk operations through a contract for business operations administrative support services (BOASS) at its New Orleans office. SIM is the incumbent contractor; the incumbent contract was due to expire on September 30, 2014.

The Navy began the acquisition process for the follow-on contract in October 2011. On December 9, 2011, the Navy issued a request for proposals. Following the receipt of proposals, award was made to eAlliant on September 7, 2012.

TRESCOS Joint Venture, which was an offeror and whose team included SIM, filed a protest in our Office on September 14 challenging the award. The agency advised our Office that it would take corrective action, and we dismissed the protest. The Navy again made award to eAlliant on January 25, 2013. On January 29, TRESCOS filed a protest in our Office challenging this second award. On March 15, the Navy decided to take corrective action, and our Office subsequently dismissed the protest.

The Navy issued an amendment to the RFP on May 17, 2013, conducted discussions, and on June 17 received revised technical and cost proposals. On July 29, 2014, the agency again made award to eAlliant. Based on information the agency identified during debriefings, the agency concluded that corrective action was required to address concerns regarding the cost realism evaluation. On August 1, TRESCOS filed another protest with our Office. Also on August 1, the agency took corrective action by terminating eAlliant’s award. Our Office subsequently dismissed TRESCOS’s protest.

Following the termination of the award to eAlliant, the Navy decided it would reevaluate offerors’ technical and cost proposals. Based on the projected award date for the contract of October 3, and the need for adequate time to transition to the new contractor, the agency concluded that an unacceptable break in service could not be avoided without awarding a bridge contract to ensure continuity of the critical services. Based on the limited time remaining prior to the expiration of the incumbent contract, the agency concluded that SIM was the only viable source capable of maintaining continuity of services, given its experience and large qualified workforce.

The Navy’s J&A (a written determination of justification and approval for the non-competitive award of a bridge contract) approved the sole-source award of a 1-month bridge contract, with five 1-month options, to SIM for the following reasons: (1) SIM currently is performing the same work under the incumbent contract; (2) the incumbent contract was due to expire on September 30, 2014; (3) several rounds of protests and corrective actions had delayed the award of the follow-on contract causing difficult acquisition planning; (4) a transition period would be required for any contractor who would be awarded the follow-on contract; (5) SIM possessed the required workforce in place in New Orleans capable of meeting the requirement without a transition; and (5) an interruption in service was unacceptable due to the critical nature of the agency’s functions being supported by the services.

eAlliant contends that the sole-source award of a bridge contract to SIM was improper for the following reasons: (1) the J&A improperly excluded eAlliant from consideration for the bridge contract; (2) the need for a sole-source contract was caused by the agency’s lack of advance planning....

CICA (the federal Competition in Contracting Act) requires that agencies solicit offers from as many potential sources as is practicable when using the unusual and compelling urgency exception to limit competition. As our Office has held, an agency nonetheless may limit a procurement to the only firm it reasonably believes can properly perform the work in the time available.

Noncompetitive procedures may not properly be used where the agency created the urgent need through a lack of advance planning. While an agency may not justify a noncompetitive award on the basis of urgency where the agency’s requirements have become urgent as a result of a lack of advance planning, such planning need not be entirely error-free or successful. Our review of an agency’s decision to conduct a noncompetitive procurement focuses on the adequacy of the rationale and conclusions set forth in the J&A; where the J&A sets forth a reasonable justification for the agency’s actions, we will not object to the award.

To the extent eAlliant argues that the Navy failed to meet its obligation to solicit offers from as many potential sources as practicable in seeking to enter into a sole-source 8(a) bridge contract, we find that there was no obligation for the agency to do so. The section 8(a) program has both competitive and noncompetitive components, depending on the dollar value of the requirement. Generally, where the acquisition value exceeds $4 million, a section 8(a) contract must be competed among section 8(a) firms; section 8(a) acquisitions with values less than $4 million, such as the one initially sought by the Navy for the bridge contract, may be awarded on a noncompetitive basis. Because of the broad discretion afforded a contracting officer to award a noncompetitive contract under section 8(a) of the Small Business Act, our review of actions related to noncompetitive acquisitions under the 8(a) program is generally limited to determining whether government officials have violated regulations or engaged in fraud or bad faith.

We therefore see no merit in eAlliant’s argument that the Navy’s attempt to enter into a sole-source 8(a) contract was improper, given the authority of agencies to do so on a noncompetitive basis. In any event, the protester conflates the process for award of a sole-source 8(a) contract and the requirements for awarding a sole-source contract under CICA’s urgent and compelling exception to full and open competition. Whereas FAR § 6.302-2(c)(2) requires agencies to solicit offers from as many potential sources as is practicable, the 8(a) sole-source provisions do not have such a requirement.

Next, to the extent eAlliant argues that after the Navy abandoned its attempt to award a bridge contract to an 8(a) firm on a noncompetitive basis, the agency failed to meet its obligation to solicit offers from as many potential sources as is practicable in awarding the 1-month sole-source bridge contract to SIM, we disagree. As discussed above, while an agency must solicit as many offerors as practicable when seeking to award a sole-source contract under the urgent and compelling exception to full and open competition, the agency may limit a procurement to the only firm it reasonably believes can properly perform the work in the time available.

Here, the Navy concluded by August 22, 2014, that its needs for the bridge contract could not be met through the 8(a) program within the timeframe needed to avoid a disruption in services. The agency therefore concluded that it needed to execute a 1-month sole-source bridge contract under the urgent and compelling exception to full and open competition. The agency executed a J&A which stated that SIM was the only firm capable of meeting the agency’s need to ensure continuity of service after the expiration of the incumbent contract on September 30.

Assuming, as the agency states, that the transition to a new contractor would require up to three weeks, and the agency’s abandoned pursuit of a sole-source 8(a) contract on August 21, the record shows that the agency would have had approximately two and a half weeks to issue a solicitation for the bridge contract, receive and evaluate proposals, and make an award. Although the protester argues, generally, that there was enough time to accomplish these tasks, we do not think that the protester demonstrates that the agency unreasonably concluded that there was not enough time to conduct a competition, and ensure a timely transition that would avoid an interruption of services. On this record, we find that the Navy reasonably concluded that SIM was the only firm that could meet the agency’s requirement to ensure uninterrupted services.

Next, eAlliant argues that the Navy’s need to award a 1-month sole-source bridge contract on an urgent and compelling basis was the result of the agency’s failure to conduct adequate advance planning. In this regard, eAlliant argues that the Navy improperly delayed making an award for its underlying requirement until July 2014. As discussed above, however, the record reflects that the agency began its acquisition for the follow-on requirement in December 2011, more than 2 years prior to the expiration of the incumbent contract on September 30, 2014. The agency made awards on September 7, 2012, and January 25, 2013, each of which was followed by protests and corrective action.

The Navy again attempted to award the on-going contract for these services on July 29, 2014, which left two months for transition--which, the agency stated, was “more than sufficient time” for transition. The Navy contends that the urgency that justified the award of the disputed bridge contract to SIM arose from the protest that followed the award to eAlliant on July 29, 2014, rather than the history of the procurement prior to that award. We agree with the agency. As our Office has held, an immediate need for services that arises as a result of an agency’s implementation of corrective action in response to a protest does not constitute a lack of advance planning.

Next, eAlliant argues that the Navy could have conducted a competition for the bridge contract following its corrective action on August 1, and the failure to do so demonstrates a lack of advance planning. In this regard, the protester cites the agency’s acknowledgement that there was “more than sufficient time” for transition to a new contractor at the time of the July 29, 2014, award. eAlliant contends, therefore, that the agency should have also had enough time to conduct both the transition as well as a competition for the bridge contract. We disagree with the protester.

The Navy first attempted to bridge its needs with a short-term sole-source 8(a) award. As also discussed above, the agency’s decision to pursue a sole-source 8(a) contract was a matter within the agency’s discretion. Although this attempt was not successful, our Office has recognized that such efforts do not need to be error-free, nor do they need to be successful. In light of the agency’s unsuccessful attempt to enter into an 8(a) contract, and the time lost to that effort, we think the agency reasonably concluded that an noncompetitive 1-month sole-source bridge contract was required.