Jump to content
The Wifcon Forums and Blogs

Sign in to follow this  
  • entries
    361
  • comments
    17
  • views
    8,043

Entries in this blog

Koprince Law LLC

You’ve served your country with pride. Now, as a government contractor, it’s only fair that you get your piece of the pie. Here are five things you should know about the government’s contracting programs for veteran-owned small businesses and service-disabled veteran-owned small businesses:

  1. What is a veteran-owned small business?

As its name implies, a veteran-owned small business (or VOSB, in government-contracting speak) is a small business that is at least 51% unconditionally owned and controlled by a veteran. A service-disabled veteran-owned small business (SDVOSB) is a small business that is 51% unconditionally owned and controlled by a service-disabled veteran. These definitions sound relatively simple at first blush, but there are many nuances in the law. Just because a small is 51% owned by a veteran doesn’t necessarily make it an SDVOSB or VOSB in the eyes of the government.

Notably, the the government currently runs two separate SDVOSB programs: one operating under the SBA’s regulations; the other under the VA’s regulations. Although the programs’ requirements are largely similar, they’re not identical. It’s important for small businesses to understand which set of rules apply to them, and what those rules entail.

  1. Who “controls” the business?

Control can be a subjective concept. But to control the business, the veteran (or service-disabled veteran, as the case may be) must exercise unconditional authority over the company’s day-to-day affairs and long-term strategic decision-making. Again, it’s important to be aware of regulatory nuances. For example, the VA’s regulations generally require the veteran to work full-time for the company to meet the unconditional control requirement.

The SBA and VA have interpreted unconditional control quite strictly: they require the veteran to essentially be the end-all and be-all within the company, with unfettered discretion over even the most consequential decisions (like amending the company’s governing documents or dissolving the company) notwithstanding the input or beliefs of non-veteran owners. This narrow reading obviously raises significant concerns for any potential investors or partners, so the VA considered (but ultimately didn’t implement) a slightly scaled-back approach. But in 2017, Congress required the VA and SBA to implement a consolidated set of regulations, with the SBA taking the lead. It remains to be seen how strictly the unconditional control requirement will be under these forthcoming rules.

  1. What’s the benefit?

SDVOSBs and VOSBs are given some important preferences in government contracting. The most significant of these preferences is at the Department of Veterans Affairs: the VA must, in some cases, set aside work for either SDVOSBs or VOSBs. In other cases, the VA can award SDVOSBs or VOSBs sole source contracts. For non-VA agencies, only SDVOSBs (not VOSBs) are entitled to a contracting preference, although VOSB status can be helpful in more limited cases, like helping large prime contractors reach their subcontracting goals. Non-VA agencies, however, can set aside solicitations for SDVOSBs, and issue sole source awards to SDVOSBs in limited circumstances.

Overall, the government aims to award at least 3% of prime contract dollars annually to SDVOSBs. The government surpassed that goal in Fiscal Year 2016, awarding SDVOSBs contracts worth more than $16 billion.

  1. Can a business challenge my status?

Yes. If an SDVOSB or VOSB is given a contract under a contracting preference, a disappointed offeror can challenge the awardee’s status as a veteran-owned small business. Losing a challenge means that your business will lose its award.

These challenges are a double-edged sword. Not only does this mean that a competitor might dispute your eligibility, but you can also dispute that of a competitor that wins a contract. So if a business challenges your status—or if you believe that one of your competitors might not be eligible—make sure you can navigate the regulations to help protect your interests.

  1. How can your business apply?

Here’s where this socio-economic program gets a little tricky. For non-VA projects, a service-disabled veteran-owned small business simply has to self-certify as to its status in the government’s SAM database. It’s essential to do your due diligence before self-certifying. Incorrectly self-certifying can carry significant penalties—ranging from losing the award to being debarred.

For VA projects, however, SDVOSBs and VOSBs must be verified by the VA’s Center for Verification and Evaluation before the bid date. Joint ventures seeking SDVOSB awards also have to be verified. This verification process can take several weeks and involve some back-and-forth—in fact, we’ve seen cases where the VA relies on outdated regulations to question a joint venture’s eligibility, when the joint venture agreement was fully compliant with current regulations. If you’re considering seeking verification for your small business (or joint venture), act fast—and get help.

***

Veterans deserve our respect and gratitude for the selfless service. The SDVOSB and VOSB contracting preferences are but one small way our country can begin to repay this debt.

If you’re interested in seeing if you qualify for SDVOSB or VOSB status or would like to learn more, please give me a call.


View the full article

Koprince Law LLC

It’s the Friday before Thanksgiving, which means if you haven’t gone shopping yet, you may be facing the chaos of the grocery stores this weekend in preparation. Or, perhaps, you’re skipping the extensive meal preparation and going for something very simple (as a college student in North Carolina, I once classed it up by having Bojangles for Thanksgiving. Fantastic sweet tea, special seasoning, and no dishes!)

Even around the holidays, the world of government contracting doesn’t slow down that much. In this pre-Thanksgiving edition of SmallGovCon Week in Review, we take a look at two men facing five years in prison for fraudulently obtaining $20 million in contracts at Fort Gordon, the 2018 NDAA’s effect on GAO bid protests, new legislation intended to give equal consideration to VOSBs for contract awards, and much more.

  • Two people admitted their involvement in a conspiracy to fraudulently obtain $20 million in contracts at Fort Gordon. [The Augusta Chronicle]
  • Two trucking companies found guilty of Service Contract Act violations are still working at America’s largest ports. [USA Today]
  • The 2018 National Defense Authorization bill includes a compromise on disputed language aimed at reducing the number of bid protests. [Government Executive] (See my take on the issue here).
  • Government sources say OFPP wants agencies to set goals for using “best-in-class contracts” and implement demand management by analyzing procurement data and making decisions on how and who to buy from. [Federal News Radio]
  • U.S. Rep. Brian Fitzpatrick introduced legislation aimed at giving veteran-owned small businesses equal consideration for contract awards that companies in other ownership-preference categories currently enjoy as part of various set-aside programs. [The Ripon Advance]
  • A former procurement officer employed at a nuclear research and development facility of the U.S. Department of Energy was indicted for orchestrating a scheme to obtain a $2.3 million contract through fraudulent means. [U.S. Dept. of Justice]
  • The American Small Business League has argued that large federal contractors mislead agencies and the public by overstating their use of small businesses as subcontractors to meet statutory goals. In U.S. District Court in San Francisco last Friday, attorneys for the advocacy group successfully pried out the previously non-public names of suppliers and other subcontractors used by Sikorsky Aircraft Corp. [Government Executive]

View the full article

Koprince Law LLC

GAO bid protests succeeded almost half the time in Fiscal Year 2017.

According to the GAO’s latest Bid Protest Annual Report, the effectiveness rate of GAO bid protests was 47% in the recently-completed fiscal year.  The statistics are striking, because they come just as Congress is finalizing the 2018 National Defense Authorization Act, which includes measures aimed at reducing bid protests.  But with bid protests succeeding at a nearly 50% clip, why does the protest “reform” debate seem to center almost entirely on discouraging contractors to protest, rather than on decreasing the number of flawed source selection evaluations?

The GAO’s annual report indicates that 17% of protests were sustained in Fiscal Year 2017.  That’s the stat that will get bandied about by those who contend that protests are largely frivolous.  “Less than a fifth of protests get sustained!” they’ll say.  But using the sustain rate as evidence of protest frivolity is misleading.

When a protest is filed at GAO, the procuring agency has two options: fight the protest, or voluntarily take “corrective action” to address the flaws alleged by the protester.  Although agencies rarely say it out loud, a decision to take corrective action typically is a tacit admission that the evaluation was flawed.  In other words, the agency counsel has reviewed the protest and thought, “I’m not sure I can win this one.”  When an agency has a losing hand, corrective action is the right move.

The GAO knows this, and uses the effectiveness rate statistic to measure how often the protester obtains “some form of relief from the agency . . . either as a result of voluntary corrective action or our Office sustaining the protest.”  And as I mentioned at the outset, that all-important statistic was at a sky-high 47% in FY 2017.  That’s higher than in any recent year, although not a major outlier: the effectiveness rate has been 43% or higher since FY 2013.

Recently, Congress has been debating so-called reforms to the bid protest process.  I discussed the proposals in-depth in a July post, but the underlying rationale appears to be that protests are ever-increasing and typically frivolous.  Thus, protest “reform” is aimed almost entirely at discouraging contractors to protest in the first place–or outright prohibiting certain protests.  For example, the 2017 National Defense Authorization Act jacked the GAO’s jurisdictional threshold for most DoD task and delivery order protests from $10 million to $25 million.  Lose a $22 million DoD order?  Sorry, no protest allowed.  The Senate’s versions of the 2017 and 2018 NDAAs would have imposed other poorly-conceived restrictions.

Why is there a popular belief that protests are both pervasive and frivolous?  The discussion seems driven by the sky-is-falling comments of some agency officials, who make it sound like every other acquisition is being frivolously protested. One former high-ranking official even went full-on Scarlet Letter and suggested creating a “shame list” for losing protesters.  (Hint: the result of every GAO protest already is available on the GAO’s website).

Sure, it stinks when you’re the contracting officer on the receiving end of a protest, but the fact remains that protests only occur on a very low percentage of acquisitions.  Headlines like “Drowning in Protests” may catch some eyeballs, but they’re not particularly factual.  Indeed, GAO protests were down 7% in Fiscal Year 2017, while the effectiveness rate was up.  But you probably won’t see many articles with headlines like “Not Drowning in Protests.”

That’s not to say that frivolous protests never occur, although GAO has the power to deal with that problem on its own.  My point, rather, is that protest “reform” efforts seem to focus almost entirely on getting contractors to protest less often, without acknowledging that some of the best ways to decrease protests involve internal government reforms rather than punitive measures directed at contractors.

What could government be doing to reduce protests?

Well, when 47% of protests succeed (despite the protester having the burden of proof!) it means that evaluators are messing up a lot of source selections.  Also, when the GAO’s stats suggest it’s essentially a coin flip as to whether a protested source selection was defensible, that’s reason for a potential protester to move forward, even without a slam dunk initial case.  Improving source selection training and processes would improve the underlying source selections, which would be the best thing anyone could do to reduce protests.

Additionally, as OFPP has pointed out, improved communication with industry–particularly in debriefings–is likely to reduce protests, as well.  In debriefings, agencies often act like they’re guarding Coke’s secret formula, rather than discussing the outcome of a competitive procurement.  Our clients sometimes come away from post-award debriefings with little more than a just-the-facts-ma’am  recitation of the minimal information required by FAR 15.506–or worse, a PowerPoint debriefing in which three-quarters of the slides simply regurgitate generic information about the FAR and solicitation’s evaluation factors.  I understand the agency’s thought process (“the more information we give them, the more they’re likely to use it against us”), but it’s often dead wrong.  The client walks out of the debriefing (or closes the PowerPoint slideshow) feeling as though the agency is hiding something.  In my experience, minimalist debriefings increase protests.

Congress seems to recognize that OFPP may be on to something, because the conference version of the 2018 NDAA includes a provision entitled “Enhanced Post-Award Debriefing Rights,” which would require the DoD to provide additional information in certain debriefings.  Unfortunately, this provision is limited to DoD awards of $100 million or more, although small businesses and “nontraditional contractors” could request an enhanced debriefing in the case of an award exceeding $10 million.

The move toward enhanced debriefings is a step in the right direction, but I worry that it won’t be enough to address the underlying issue–and not just because enhanced debriefings will be limited to large DoD procurements. So long as many agency officials believe that the best policy in a debriefing is to supply the bare minimum required by law, offerors may still walk away with the sense that the agency is hiding something.  Congress can’t legislate a culture change, but that’s really what’s needed to make debriefings truly effective in reducing protests.

Like any other contracting process, the bid protest process should always be evaluated to see if it can be improved.  But the GAO’s statistics (and those compiled by others) make very clear that the sky isn’t falling.  I’m not suggesting a public “shame list” for agency officials who poorly plan or execute an acquisition.  But instead of squawking about how bid protests are ever-increasing and frequently frivolous, acquisition officials ought to get their own houses in order first.


View the full article

Koprince Law LLC

Here at SmallGovCon, we often write about nuanced, complex government contracting legal issues.  This isn’t one of them.

The moral of today’s story comes straight from the personal superhero files of Captain Obvious: not reading the performance work statement in your own contract is a pretty bad idea.

The PWS at issue in Sterling Design, Inc., ASBCA No. 61099 (2017) was part of a contract between the Air Force and Sterling Design, Inc.  Under the contract, SDI was to repair a power supply unit for a fixed price of $7,395.  The contract gave SDI 30 days from receipt of the power unit to complete the repairs.  However, SDI did not complete the repairs until several months after the 30-day period had elapsed.

SDI then filed a claim for $5,925, alleging that the government had delayed SDI’s work.  The contracting officer denied the claim, and SDI appealed to the Armed Services Board of Contract Appeals.

At the ASBCA, SDI introduced a whopping 893 pages of emails with governmental officials.  The crux of SDI’s argument was that the emails represented SDI’s attempts to obtain necessary contractual information, and that the government delayed the contract either by failing to respond to these emails, or by responding late.

The problem?  The information SDI sought in its emails was already contained in the PWS.  Although SDI asserted at various times that it either didn’t have the PWS, or didn’t have a complete copy, the Air Force provided the ASBCA with evidence that it had transmitted the entire PWS to SDI before the 30-day performance period began.

The ASBCA wrote that “[w]hile it appears that Air Force contracting officials could have responded to [SDI’s owners’] inquiries more quickly, most or all of his questions would have been answered if he had simply read the PWS.”  The ASBCA denied the appeal, holding “SDI has failed to prove that the government delayed the contract.”

As a government contracts attorney, I’ve often seen a variation on what happened in Sterling Design: contractors, eager to get to work, sometimes read only the PWS and skip past those boring (but essential) FAR clauses and other legal mumbo jumbo elsewhere in the contract.  Skipping the legalese is, of course, a bad idea, too–but Sterling Design is the first time I’ve heard of a contractor skipping the PWS.

I guess there’s a first time for everything.


View the full article

Koprince Law LLC

As a branch of the Treasury Department, the United States Mint would usually be subject to federal procurement laws, like bid protests. As one contractor recently discovered, however, certain activities at the Mint have been exempted from many federal procurement laws, including GAO protest review.

Simply put, the GAO can’t decide a bid protest of Mint procurements.

A-Z Cleaning Solutions, B-415228 (Nov. 6, 2017), involved a procurement for janitorial services at the Mint facility in San Francisco, California. A-Z Cleaning was named an unsuccessful offeror. Following notification, A-Z Cleaning filed a protest before GAO, challenging the Mint’s best-value trade-off decision.

The Mint moved to dismiss the protest, arguing that GAO lacked jurisdiction to hear the case. The Mint’s argument was based on the interaction between the Competition in Contracting Act (the “CICA”) and specific statutes addressing Mint activities.

Under the CICA, GAO has the authority to decide “a protest submitted . . . by an interested party.” See 31 U.S.C. § 3553(a). Protests are a “written objection by an interested party to . . . [a] solicitation or other request by a Federal agency for offers for a contract for the procurement of property or services.” 31 U.S.C. § 3551(1)(A). Federal agency is defined as “an executive agency[.]” 40 U.S.C. § 102(5). What this collection of statutes means is that GAO generally has jurisdiction to decide protests of procurements conducted by executive branch agencies.

The Mint, as a branch of the Treasury Department, is an executive agency. Accordingly, its procurement decisions should be subject to protest before GAO. A separate statute, however, complicates matters.

In 1996, Congress expressly exempted Mint procurements for operations and programs from the CICA. Pursuant to 31 U.S.C. § 5136, “provisions of law governing procurement or public contracts shall not be applicable to the procurement of goods or services necessary for carrying out Mint programs and operations.” The statute also defined Mint operations and programs as follows:

(1) [T]he activities concerning, and assets utilized in, the production, administration, distribution, marketing, purchase, sale, and management of coinage, numismatic items, the protection and safeguarding of Mint assets and those non-Mint assets in the custody of the Mint, and the [Mint Public Enterprise Fund]; and (2) includes capital, personnel salaries and compensation, functions relating to operations, marketing, distribution, promotion, advertising, official reception and representation, the acquisition or replacement of equipment, the renovation or modernization of facilities, and the construction or acquisition of new buildings[.]

In A-Z Cleaning, the Mint argued that the janitorial services it ordered were “functions relating to operations” of the Mint; therefore, the procurement of such services was excepted from procurement laws—including the CICA—and thus outside of GAO’s jurisdiction.

GAO agreed with the Mint’s argument. After walking through the statutes laid out above, GAO said:

Because the establishing legislation provides that federal procurement laws and regulations do not apply to the procurement of goods or services necessary for carrying out the Mint’s operations and programs, and those operations and programs are defined broadly enough to encompass substantially all of the Mint’s activities, we conclude that the Mint is not subject to the terms of CICA. Furthermore, because the bid protest jurisdiction of our Office derives from CICA, we must conclude that the Mint is not subject to that jurisdiction.

GAO further explained that its conclusion regarding the Mint was consistent with prior decisions regarding the Presidio Trust and United States Postal Service, which are subject to similar exemptions. Accordingly, GAO dismissed the protest.

What does GAO’s decision in A-Z Cleaning mean for Mint bidders? Clearly, GAO believes that it lacks authority to decide pretty much any bid protest of a Mint procurement. (As noted above, while the statutes may not be 100% clear on the extent of the prohibition, the GAO believes that the jurisdictional ban applies to “substantially all” of the Mint’s activities).  The Court of Federal Claims may still be an option; however, not all contractors are interested in full-blown courtroom litigation against the government. Simply put, for contractors bidding on Mint jobs, the potential protest options are considerably narrower than normal.


View the full article

Koprince Law LLC

When an agency opens discussions with offerors, those discussions must be fair.

In a recent decision, GAO recommended the reopening of competition for a contract worth up to $283 million based, in part, on a finding that an agency had engaged in misleading and unequal discussions.

Discussions are a type of exchange between an agency and each offeror before award of a solicitation that allows offerors a chance to revise their proposals to address weaknesses. In discussions, GAO noted, “an agency may not mislead an offeror through the framing of a discussion question into responding in a manner that does not address the agency’s actual concerns, or otherwise misinform the offeror concerning a problem with its proposal”, and the agency cannot favor one offeror over another.

Unfortunately, GAO found that the Census Bureau had engaged in just such unequal conduct in a major solicitation dealing with mobile devices related to the 2020 census.

In AT&T Corp., B-414886 (Oct. 5, 2017), AT&T protested issuance of a task order to CDW Government LLC under a request for proposals for a mobile devices solution to support the 2020 Decennial Census. The Census Bureau sought proposals for a fixed-price task order. Proposals needed to demonstrate “usability, performance, and security requirements; continuous, reliable cellular network coverage; and a technology refresh assessment.”

Evaluation would be on a best-value basis considering factors including past performance and technical approach. The technical approach “required offerors to address 13 elements including, as relevant here, a description of the specific mobile device proposed and why it was selected; how the offeror would provide a cellular service solution and maximize signal strength/reliability by designating the best carriers for each area; and how the offeror would address the requirements for technology refresh cycles for mobile devices.”

The agency received four proposals, including proposals from AT&T and CDWG. After completing an initial technical evaluation, the agency opened discussions with offerors and requested revised technical proposals. After evaluating revised proposals, the CDWG was rated technically highest, with a price of $283,492,962, while AT&T was ranked second, with a price of $191,850,841. As is relevant here, AT&T’s proposal was assigned a technical risk related to its multi-carrier solution.

In its protest, AT&T argued that both it and CDWG were initially “evaluated to have potential bias in their multi-carrier approaches, but only CDWG’s technical exchange addressed potential bias.”

In talks with CDWG, the agency “expressed concern that ‘CDWG’s pre-negotiated rates with [DELETED] [presented] a risk that could result in bias during the cellular carrier analysis,’–that is, the rates could affect carrier selection” and asked, “[h]ow does CDWG plan to ensure that its pre-negotiated rates with cellular carriers are unbiased?” Although the decision does not exactly spell this out, I believe what the agency was concerned with was that the mobile device provider would have too cozy of a relationship with one carrier and therefore not get the best rates, technology, or cellular coverage for the government. In response to these questions, CDWG revised its proposal (in a manner redacted in the decision), and the agency upgraded CDWG’s technical score by finding it had eliminated the risk of bias.

“Unlike the exchange with CDWG, the agency’s technical exchange with AT&T did not mention bias, even though the evaluators expressly raised a concern about bias for both companies.  Instead, the agency asked, “[how] does AT&T plan to include multiple cellular carriers into their cellular network approach?'” AT&T answered that it would use certain methods to determine the best-value carrier.

GAO concluded that

the record as a whole demonstrates the impropriety in the conduct of discussions. To the extent the agency contends that it was concerned about CDWG’s rates, and AT&T’s lack of detail–rather than bias–the record does not support the agency’s contentions.  As noted above, AT&T’s response was found lacking because it did not address bias in carrier selection.  To the extent the agency was concerned with the potential bias in each offeror’s approach, and raised bias with CDWG, it was obligated to similarly raise this concept with AT&T.  Accordingly, the agency’s discussions with CDWG were misleading and unequal in this respect, and we sustain the protest.

GAO recommended that “the agency reopen the competition, conduct discussions, accept revised proposals, reevaluate, and make a new selection decision in accordance with the evaluation criteria set forth in the RFP” and award costs to AT&T.

We have touched on inequality in discussions on SmallGovCon before.  For instance, GAO has noted that an agency cannot allow one offeror, but not others, to make revisions to a proposal as part of discussions. As the AT&T case demonstrates, when an agency conducts discussions, those discussions must be fair. Here, the lack of fairness could end up changing the result of an award worth a quarter billion dollars.


View the full article

Koprince Law LLC

The period of performance under a government contract, measured in “days,” meant calendar days–not business days, as the contractor contended.

In a recent decision, the Armed Services Board of Contract Appeals applied the FAR’s general definition of “days” in holding that a contractor had not met the contract’s performance schedule.

The ASBCA’s decision in Family Entertainment Services, Inc., ASBCA No. 61157 (2017) involved an Army contract for grounds maintenance services at Fort Campbell, Kentucky and the surrounding area.  The contract was awarded to Family Entertainment Services, Inc. in May 2015.

(Side note: Family Entertainment Services apparently performed the contract under a “doing business as” name; IMC. That was probably a good call on the contractor’s part, because “Family Entertainment Services” doesn’t exactly conjure up mental images of landscaping).

The government subsequently issued a task order to FES.  The task order specified that mowing services would be completed every 14 days.  However, FES was unable to consistently provide the mowing services within 14 calendar days.

In August 2015, the government terminated a portion of the contract for convenience.  FES then filed a claim for $81,692.34.  FES argued, in part, that the government had not properly computed the performance schedule, which FES said should have been measured in business days, not calendar days.  The Contracting Officer denied the claim, and FES appealed to the ASBCA.

At the ASBCA, FES argued that the contract’s use of the term “days” was ambiguous, and should be meant to refer to business days.  The ASBCA disagreed.

The ASBCA noted that the contract included FAR 52.212-4 (Contract Terms and Conditions–Commercial Items).  That clause incorporates FAR 52.202-1 (Definitions), which states, in relevant part: “[w]hen a solicitation provision or contract clause uses a word or term that is defined in the Federal Acquisition Regulation (FAR), the word or term has the same meaning as the definition in FAR 2.101, in effect at the time the solicitation was issued . . . .”

FAR 2.101 succinctly says: “Day means, unless otherwise specified, a calendar day.”

Applying the FAR provisions in question, the ASBCA wrote that “there is only one reasonable way to interpret the contract.”  FES’s “opinion that ‘day’ should mean ‘work day’ is not a reasonable interpretation of the contract.”

The ASBCA denied the appeal.

The definition of “day” can make all the difference when it comes to various deadlines under which contractors must operate.  The FAR 2.101 definition doesn’t apply in every setting.  For example, FAR 33.101 includes some important nuances when it comes to protests and claims.  And, of course, the contractor and government can always contractually agree to a different definition, including a definition based on business days.

That said, oftentimes there is no other relevant FAR provision, and no agreed-upon contractual definition.  In those cases, as Family Entertainment Services indicates, the definition in FAR 2.101 will likely apply–and that means calendar days.


View the full article

Koprince Law LLC

Happy Veterans Day to all our SmallGovCon readers. We hope that you will take some time today and tomorrow to honor the strength, loyalty and commitment that our brave veterans dedicated to this country. Veterans, we are deeply grateful for your service.

This edition of SmallGovCon Week In Review brings a look at six large companies with a high reliance on government contracts, the “Amazon Amendment” and how Amazon is looking to expand it’s operations through government procurement, the removal of Fair Pay and Safe Workplaces Rule, tips for WOSBs to succeed in the federal marketplace, and much more.

  • In a $3.7 trillion federal government budget, there are going to be a lot of companies doing well–here are the top six. [The Motley Fool]
  • Forbes offers tips for female business owners who are frustrated by the lack of opportunities and showcases the huge opportunity for women to get a piece of the set-aside contracts for women-owned businesses. [Forbes]
  • Amazon has an opportunity to dramatically expand its hold on the logistics space as it tries to capture $53 billion in defense procurement. [Freight Waves]
  • An alleged kickback and bribery scheme that went on for six years before being discovered has led to a Government contracting officer and his contractor facing a heap of trouble. [PNWC’s Government Contracting Update]
  • Federal contractors will not face requirements aimed at protecting employees from wage and unsafe working conditions under rule the Trump administration finalized on Monday. [Government Executive]
  • Effective November 6, 2017, the FAR Council finalized a final rule amending the Federal Acquisition Regulation for the removal of the Fair Pay and Safe Workplaces requirements. [Federal Register]
  • At least 125 companies were discovered to owe the federal government a total of $40,633,951 in unpaid taxes while still receiving federal contract awards totaling more than $134 million. [Live 5 News]
  • A jury deadlocked in a case against two men accused of SDVOSB fraud. [Arkansas Online]
  • An elaborate scheme between a former Army official and a contractor has led to an 18 month sentence and forfeiture of over a quarter of a million dollars. [Department of Justice]
  • A look at what did, and did not, make it through the conference version of the 2018 National Defense Authorization Act. [Nextgov]

View the full article

Koprince Law LLC

Asking new employees to sign arbitration agreements is common in the commercial business world. But it can be a big no-no in government contracting.

In a recent bid protest decision, GAO sustained a protest where a Reston, Virginia company required its proposed key personnel to sign binding arbitration agreements.  In other words, requiring key personnel to arbitrate employment disputes cost the original awardee a $41 million contract.

The problem with doing so, according to the decision in L3 Unidyne, Inc., B-414902 (Oct. 16, 2017), is that it seems to have been contrary to the Fiscal Year 2010 Defense Appropriations Act.

Defense appropriations bills, which are passed by Congress annually, serve the primary purpose of funding the Department of Defense for the upcoming fiscal year. But it is common practice for lawmakers to use the opportunity to introduce a number of policy concerns, or occasionally bizarre pet projects, into a bill that they know will pass.

According to L3 Unidyne, the 2010 Act precludes the expenditure of funds on any federal contract in excess of $1 million, unless the contractor agrees not to enter into a binding arbitration agreement for certain types of employment claims, including discrimination claims under title VII of the Civil Rights Act of 1964. The 2010 requirement has been incorporated into the DFARS, where contracts will contain the clause at DFARS 252.222-7006 (Restrictions on the Use of Mandatory Arbitration Agreements).

The procurement in question sought various services in connection with the Navy’s towed sonar array. The Navy issued the solicitation to holders of the Seaport-e IDIQ contract. The work was to last a maximum of two years. Importantly, the solicitation required offerors to provide letters of intent from proposed key employees.

The Navy received several proposals, only one of which was found technically acceptable, that of Leidos, Inc. of Reston, Virginia. The Navy announced that Leidos had won the award at an evaluated cost of $41.4 million.

One of the unsuccessful offerors, L3 Unidyne, Inc., of Norfolk, Virginia, filed a protest. It argued that Leidos had required key employees to sign arbitration agreements contrary to the 2010 Defense Appropriations Act, and that the Navy failed to evaluate Leidos’ proposal for compliance.

The evidence showed that Leidos had required four proposed key employees to sign arbitration agreements as a condition of employment. Leidos’s submitted letters of intent for the employees included the following language: “All new hires and rehires of Leidos must execute an Arbitration Agreement prior to commencement of employment.”

GAO sustained the protest, holding:

As noted, the record shows that four of Leidos’s key employees were proposed as contingent hires. Each of them executed a letter of intent agreeing to accept employment with Leidos, and each of those letters of intent expressly conditioned the individual’s employment on execution of an arbitration agreement. As the protester correctly notes, there is no evidence in the record to show that the agency ever meaningfully considered whether or not the Leidos proposal complied with the statutory requirements described above in light of the terms of the letters of intent.

GAO added that the Navy “could not properly have considered the Leidos proposal awardable without resolving whether or not the arbitration agreements here violate the statutory prohibition.”

What is unclear from the case is why L3 relied solely on the 2010 appropriations bill, rather than DFARS 252.222-7016 or more recent statutory authority. There are no dates in the opinion, but it is fair to assume that the solicitation came out in 2017, maybe 2016 at the earliest. It is hard to imagine it reaching all the way back to 2010. It is possible, but again unclear from the case, that L3 cited the 2010 bill because that was in effect when the parties received the underlying Seaport-e contract. Regardless, GAO noted that “Although the provision to which the protester refers related to fiscal year 2010 funds, Congress repeatedly has reenacted identical provisions, most recently in the Consolidated Appropriations Act, 2017 . . . .”

Thus, GAO recommended that the Navy go back and “determine as an initial matter whether the Leidos proposal violates the statutory prohibition against requiring individuals to enter into arbitration agreements as a condition of employment.” GAO also recommended that the Navy pay L3 its costs, including attorneys’ fees—which, if this result is any indication, were probably very well-earned.

The L3 Unidyne case is an important reminder to defense contractors that they may be prohibited from requiring employees or independent contractors to sign mandatory arbitration agreements covering certain claims. Contractors would be wise to review their practices, and adjust them if necessary, before the issue comes to light in a bid protest with a contract hanging in the balance.


View the full article

Koprince Law LLC

When a contractor leases equipment to the government, the contractor typically expects that the government will take good care of that equipment.  But a recent Armed Services Board of Contracts Appeals case reveals the government does not always take such proper care of leased goods or equipment.

What happens then? Well, the contractor may be able to recover damages under the contract and common law principles.

In Assessment and Training Solutions Consulting Corporation, ASBCA No. 61047 (2017), the ASBCA sustained a contractor’s claim for damages resulting from the government’s negligence in taking care of boats leased from the contractor.

By way of background, ATSCC leased three of its boats to the Navy for use in maritime training. Under the contract maintenance requirements, ATSCC was responsible for performing quarterly preventative maintenance and inspection on all three boats and repairing any identified issues. The contractor was to “bear the cost of performing repairs unless it can be proven that such repairs were due to negligence or willful damages caused by the government.”

During the Navy’s operation of these boats, multiple issues arose, including a boat grounding, a boat accident, using the wrong oil, filling freshwater tanks with diesel fuel, operating when engines were overheated, failing to fill out pre-operation and post-operation checklists, leaking coolant and oil, and a cracked manifold in an engine, each issue requiring repair.

On December 15, 2015, ATSCC submitted a claim to the Navy contracting officer for damages due to “the negligence of U.S. Government (USG) personnel,” but took responsibility for some of the repairs. When the Navy failed to issue a final decision for over a year, ATSCC appealed the deemed denial to the Board.

The Board rejected the Navy’s argument that because the contract specifically addressed negligence, common law bailment principles were inapplicable. Instead, the Board agreed with ATSCC’s common law bailment theory because both the contract and common law bailment had the same criteria for liability – negligence. Thus, the principles of common law bailment were founded upon the underlying contract and applicable to the Board’s evaluation.

For those unfamiliar with the principals of common law bailment, a brief explanation is warranted. Under common law bailment, when one party, the bailee, pays another party, the bailor, to use the bailor’s goods, the bailment is for the mutual benefit of the parties (i.e., the bailor receives money and the bailee receives full use of the goods). As the Board wrote:

The law of bailment imposes upon the bailee the duty to protect the property by exercising ordinary care and to return the property in substantially the same condition, ordinary wear and tear excepted. When the government receives the property in good condition and returns it in a damaged condition, a presumption arises ‘that the cause of the damage to the property was the [g]overment’s failure to exercise ordinary care or its negligence.

Applying this standard, the Board disagreed with the Navy’s argument that it took ordinary care of ATSCC’s boats, noting that one boat’s “‘blown’ engine is not ‘ordinary wear and tear.’” The Board found that the Navy’s acceptance of the boats established they were in good condition when received. The Board rejected that Navy’s argument that the boats were not in its exclusive control, finding that the damage occurred during the Navy’s operating and training in which ATSCC did not participate. Thus, the Navy’s return of damaged boats established that the Navy was responsible for at least some of the damage.

As demonstrated in Assessment Training, ordinary wear and tear is expected in leasing items to the government. However, Assessment Training confirms that the government cannot absolve itself of liability for its own negligence in taking care of leased goods or equipment, especially when it fails to exercise ordinary care.


View the full article

Koprince Law LLC

Affiliation might be one of the scariest words to small business government contractors. But why?

Here are five things you should know about affiliation:

  1. It can make a small business large.

To qualify as a small business for purposes of a government contract, a business has to be small under the size standard associated with the North American Industry Classification System (NAICS) code assigned to the solicitation. In addition to considering the firm’s own revenues or employee count, the SBA will add the size of any affiliates. So if your business’s size, together with that of any affiliates, exceeds the applicable size standard, your business won’t be eligible for the award.

  1. How is affiliation found?

Affiliation is, at its most basic, a determination that one business can control another, or that a third party controls both. The SBA will find two companies to be affiliates when one has the power (either by taking some action or withholding consent) to control the affairs of another (or a third party has the power to control both)—even if that control isn’t actually exercised.

The SBA may consider all aspects of the parties’ relationship (the totality of the circumstances, in legal-speak) to determine whether this ability to control exists. Some of the most common reasons for finding affiliation, however, are when firms share common ownership or management, one entity is basically a spin-off or is economically dependent on another, or a company is unusually reliant on another as its ostensible subcontractor.

  1. Another bidder or the contracting officer may challenge the awardee’s size.

The SBA may determine affiliation in a variety of contexts, but an affiliation analysis often arises due to a formal size protest. After your business is named the awardee under a small business set-aside solicitation, another bidder (or even the contracting officer) may file a protest questioning your company’s size. If so, and if the protest satisfies certain jurisdictional prerequisites, it will be up to you to show that affiliation doesn’t exist.

If your business’s size is successfully protested in connection with a set-aside solicitation, you won’t be eligible to receive the award. If the contract has already been awarded, it will likely be terminated. Affiliation should therefore be taken very seriously.

  1. Joint ventures enjoy some protection from affiliation.

Many of the small business owners I speak with operate under the belief that their business will be exempt from affiliation with its joint venture partner. This isn’t true—the members of a joint venture enjoy some special affiliation benefits, but not blanket immunity. Don’t let this same mistaken assumption jeopardize an award to your joint venture.

  1. Affiliation can be fractured (or mitigated).

Affiliation should be a serious concern for every small government contractor. If you’re concerned that your small business might be affiliated with another company, there are steps you can take to try to fracture that affiliation before you submit an offer on a small business solicitation. Doing so could help save a contract.

***

Affiliation can make your small business large and, in doing so, jeopardize an award. If you have concerns about affiliation, please call me to discuss.


View the full article

Koprince Law LLC

I am back in Lawrence after a great trip to Washington, DC where I attended the Native American Contractors Association 2017 Federal Contracting Policy and Advocacy Conference.  I was part of a great panel yesterday on the future of federal contracting.  The panel spoke about GAO bid protests, the move away from lowest-price technically-acceptable procurements, the need to improve the HUBZone program, and other important topics facing the contracting community in the years to come.

A huge “thank you” to Mike Anderson, Chelsea Fish, and the entire NACA leadership team for organizing this fantastic event and inviting me to participate.  And a big thanks also to everyone who attended the panel and stopped by the Koprince Law LLC booth.  It was wonderful to see so many old friends and make plenty of new ones.

Next on my travel agenda: the National Veterans Small Business Engagement.  If you will be attending the NVSBE, I look forward to seeing you in St. Louis.


View the full article

Koprince Law LLC

It’s a Sunday afternoon and instead of watching football (CHIEFS!), you’re shopping for a new refrigerator. You explain to the salesman your must-haves: a black refrigerator with a bottom-drawer freezer and an in-door water dispenser. But rather than showing you refrigerators that meet your criteria, he insists on showing you stainless steel models with the freezer on the side.

If the refrigerator doesn’t meet your needs (or your wants), odds are you won’t buy it. The federal government is no different: if it identifies salient characteristics in a solicitation, proposals that deviate from them likely aren’t going to win the award.

This refrigerator-shopping scenario (which, by the way, sounds like a nightmare) is basically what happened in Phoenics Corporation, B-414995 (Oct. 27, 2017). There, the Navy issued a solicitation for a ground-penetrating radar and named three brand-name items that would meet its needs. Alternatively, an offeror could propose a different model if that model met several salient characteristics listed by the Navy.

Included among these characteristics was a requirement that the radar “have an external and removable locking pin to hold arm secure whether in operation or storage mode.” The solicitation further cautioned that an internal gear mechanism was not acceptable.

Phoenics submitted the lowest-priced quote, but its product was deemed unacceptable by the Navy. Although the gear mechanism in Phoenics’ proposed radar “positively locks the arm with an integral locking insert/pin in either the operating or storage mode,” its locking mechanism was not external and removable. Instead, the locking mechanism was “performed via a control button/lever within easy reach of the operator.” Because Phoenics’ proposed radar did not meet the salient characteristics, the Navy found it unacceptable.

Phoenics then filed a GAO bid protest, saying its product basically met the Navy’s salient characteristics. In response, GAO denied this challenge and stated that Phoenics did not refute the agency’s allegation that the locking pin was neither external nor removable. In other words, GAO said that when it comes to salient characteristics, close isn’t good enough.

From my vantage, Phoenics might have had more luck had it challenged the Navy’s identified salient characteristics as part of a pre-award protest. Offerors can be hesitant to challenge the terms of a solicitation for fear it might lead to animosity by the contracting officer.

But in our practice, we find that concern to be somewhat overblown: if done professionally and civilly, a pre-award challenge to ambiguous or unnecessary terms can be advantageous to both offerors (who have clarity over the requirements) and the government (who will get the best possible proposals). Here, for example, Phoenics might have argued that the salient characteristics overstated the government’s minimum needs by excluding a product like the one Phoenics ultimately offered.

In a footnote, GAO suggested the same thing. It wrote that “to the extent that there was a conflict between the brand name products and the salient characteristics, we find that any resulting ambiguity was patent—that is, apparent on its face.” As such, “Phoenics was required to protest any such defect in the terms of the RFQ prior to the date set for receipt of quotations, which it did not.”

As Phoenics Corporation reiterates, an offeror simply won’t be successful if it doesn’t propose what the government wants. And if the government’s salient characteristics appear overly restrictive, the best time for legal action might be before proposals are due—not after award.


View the full article

Koprince Law LLC

Although the temperatures outside may be dropping, things are heating up in the contracting world. Now one month into the 2018 federal fiscal year, agencies have new budgets and there is a lot money to be spent. We will keep a close eye on awards, regulation changes, and related issues to federal contracting all year long, right here on SmallGovCon.

Let’s get the weekend started off by recapping the latest federal contracting news. In this edition of SmallGovCon Week In Review, we look at the potential for a DUNS replacement, a three-year prison sentence for accepting kickbacks in exchange for contracts, awards for GSA’s $5 billion VETS 2 IT services vehicle, and much more.

  • Defense contractors have two months to comply with one of the most complicated Pentagon regulations to hit their desks in years. [Bloomberg Government]
  • The General Services Administration is considering a potential replacement to DUNS, and has asked for feedback. [FCW]
  • GSA announced awards to 70 SDVOSBs under its Veterans Technology Services 2 (VETS 2) Government-wide Acquisition Contract. [GSAWashington Technology]
  • GSA also released three requests for information under its Federal Acquisition Service. [Federal News Radio]
  • Ongoing efforts to modernize federal IT are starting to bear fruit, but several questions remain. [fedscoop]
  • Will a plan to charge $350 for each protest filing stop frivolous protests? [Federal News Radio]
  • South Carolina contractor sentenced to two years in prison after unlawfully obtaining more than 100 contracts worth hundreds of millions of dollars. [The State]
  • More bad behavior: a former employee at the Merchant Marine Academy in Kings Point was sentenced to three years in prison after receiving over $150,000 in kickbacks . [Newsday]
  • Still more trouble: an FDA supervisor and contractor have been charged with bribery and conspiracy relating to a kickback scheme dating nearly six years. [United States Department of Justice]

View the full article

Koprince Law LLC

You might think that if you send an email with the delivery receipt option and the delivery receipt comes back, the email was delivered. But when an offeror submits a proposal by email, does a delivery receipt mean that the agency necessarily received the proposal in its inbox?

At least under the facts of one recent GAO bid protest, the answer was “no.” In that case, the GAO held that an email delivery receipt wasn’t sufficient to demonstrate that the agency received the electronic proposal.

In ManTech Advanced Systems International, Inc., B-414985, (Oct. 20, 2017), the GAO examined a proposal submitted by ManTech to provide cyber security services to the Air Force. ManTech submitted its proposal under a task order solicitation issued under the Air Force’s Cyber Security and Information Systems Technical Tasks IDIQ.

The task order proposals were to be submitted electronically via e-mail to the contract specialist, at the specialist’s email address, no later than 1:00 p.m. Central Daylight Time on July 17, 2017. The solicitation provided that receipt of proposals would be acknowledged by return e-mail.

ManTech sent its email with the proposal to the designated email address on July 17, 2017, at 1:25 p.m. Eastern Daylight Time (EDT) “and received confirmation of completed delivery through its Microsoft Outlook delivery receipt feature.”

Between 1:30 and 2 p.m. EDT, ManTech attempted to confirm receipt. First, it contacted the Air Force and learned the proposal had not been received, so ManTech resent the proposal to the designated inbox, the agency employee it had spoken to, and the contract specialist. Then it sent the email without the cover letter.

Finally, the agency told ManTech to stop trying because it was past the deadline. The agency later informed ManTech that, because the proposal hadn’t been received on time, the agency hadn’t considered ManTech for award.

ManTech filed a GAO bid protest challenging the agency’s decision. ManTech argued that the Air Force should have considered the proposal because the proposal was timely sent to the correct email address, and ManTech received confirmation that it had been received.

ManTech relied heavily on email tracking records from its Microsoft Outlook delivery system. ManTech submitted a declaration from its Director of Network Services to argue that “since it did not receive a bounce back indicating that the e-mail containing the proposal had been rejected, it must have been accepted by the agency’s e-mail exchange server.”

The Air Force responded by tracing the path of an email to its email system:

when an e-mail is sent to any recipient that is at an organization that is part of the Department of Defense, it is first scanned by the enterprise e-mail security gateway (EEMSG) for malicious content.  EEMSG delivers the e-mail to the recipient’s e-mail exchange server if no malicious content is found. The recipient’s e-mail exchange server then performs additional scans based on the specific policies of the recipient organization. The recipient’s server can block, quarantine, drop, or deliver the e-mail to the recipient’s e-mail box.  The Air Force reports that the e-mails sent by ManTech were received by the EEMSG system, which scanned them and attempted to deliver them to the specified Air Force e-mail address. However, based on the content, they were rejected by the Air Force server.  ManTech did not receive a bounce back because the EEMSG inbound system cannot initiate a connection to the internet.

GAO wrote that “t is an offeror’s responsibility to deliver its proposal to the proper place at the proper time.” Moreover, the offeror “has the burden of showing that it timely delivered its proposal to the agency at the specified address.”

Here, “ManTech has demonstrated that it timely sent its proposal to the agency, and that it reached the EEMSG server.” However, “ManTech has failed to establish that its proposal was actually delivered to the agency’s designated e-mail prior to the time set for the receipt of proposals, and thus, has failed to meet its burden of showing the proposal was timely delivered to the agency.”

We have covered electronic timeliness issues on SmallGovCon before, as GAO seems to issue an opinion on the topic every six months. Most of these cases haven’t gone well for the protester. For example, GAO has denied a protest when an initial government server receives a proposal on time, but the proposal doesn’t make it to the final destination until after the deadline. The same result held even when the protester asserted the late email was the result of faulty government servers. And along the same lines (and pretty close to the result here), the GAO denied a protest where the offeror’s proposal was rejected by the agency’s spam filter.

To be clear, my colleagues and I here at SmallGovCon aren’t big fans of these decisions (or the decision in ManTech). Why should a contractor be punished if a government server malfunctions, or a government spam filter rejects a proposal, or (as here) the government server simply “rejects” the proposal after a scan? It seems to us that if the proposal is under government control at the time specified in the solicitation, that should be enough, in most cases, to require the government to evaluate it.

Encouragingly, the Court of Federal Claims may agree. As we discussed in the latter half of this post, the Court has issued several decisions that seem to be at odds with the GAO’s strict view. For companies like ManTech, the Court–not the GAO–is probably the better forum for a protest of this nature.

That said, offerors submitting proposals electronically should be aware of the tough rules that often apply.  As ManTech Advanced Systems International demonstrates, even an email delivery receipt may not be enough to prove that an electronically-submitted proposal actually arrived at the correct place.


View the full article

Koprince Law LLC

Participants in the SBA’s 8(a) Program must timely submit their annual review packages to the SBA.

In a recent decision, the SBA Office of Hearings and Appeals held that the SBA may terminate a participant from the 8(a) Program for failing to provide the required information–even if the 8(a) company’s owner has had personal difficulties that contributed to the failure.

OHA’s decision in KC Consulting, LLC, SBA No. BDPT-563 (2017) involved the 8(a) Program participation of a Michigan-based small business.  On January 8, 2016, KC Consulting received a letter from the SBA requesting that the company provide its 8(a) annual review information.  KC Consulting did not provide the information.  The SBA sent a second letter in March 2016; again, KC Consulting didn’t comply.

On April 12, 2017, the SBA issued a Termination Letter to KC Consulting.  In the letter, the SBA stated that KC Consulting would be terminated from the 8(a) Program because of its repeated failure to submit the required annual review information.

KC Consulting filed an appeal with OHA, arguing that it should not be terminated from the 8(a) Program.  KC Consulting admitted that it failed to submit the annual review information despite SBA’s requests for it.  But KC Consulting explained that its President and Managing Member had been undergoing some personal difficulties: his parents had both passed away, and he was in the midst of divorce proceedings.  KC Consulting said that these issues had a significant impact on the firm, and asked for another year in the 8(a) Program to get the company “back on track.”

OHA noted that the SBA’s 8(a) Program regulations allow the SBA to terminate a participant for “[a] pattern of failure to make required submissions or responses to SBA in a timely manner,” including the timely submission of annual review information.  Here, KC Consulting “admits the violation and confirms SBA’s grounds for termination.”  It is “of no consequence that [KC Consulting’s] violation was not intentional.”

OHA dismissed the appeal.

As the KC Consulting case demonstrates, the SBA takes the 8(a) annual review very seriously.  Although it’s an area of broad discretion, the SBA has the right to terminate a company from the 8(a) Program for repeatedly failing to submit the annual review information, or other relevant information requested by the SBA–even if the 8(a) owner’s personal troubles made compliance more difficult.


View the full article

Koprince Law LLC

I was grocery shopping the other day, and I had to make the tough choice between the name-brand cereal and the store-brand cereal. I don’t know about you, but with some products, the name brand has a certain flavor that the store brand just can’t replicate. When it comes to government contracts, the same is true–sometimes the government wants a certain brand or supplier and will accept no substitutes.

GAO recently held that, where an agency required quotations including parts from one approved source of supply, and an offer is submitted that proposes an “alternate product,” the agency can reasonably reject the bid–and that a protest of the approved source restriction itself is untimely if it isn’t filed before the proposal deadline.

The additional wrinkle in this decision is that, if the vendor wishes to protest the sole-supply-source restriction in the solicitation, the protest has to be made before the submission deadline for the solicitation. Therefore, the protester’s argument that it should be considered an alternate source was dismissed as untimely because the alternate-source issue is a term the protester should have raised prior to the solicitation submission deadline. This is yet another variation on the tricky rules of bid protest timeliness–in this case, involving the issue of proposing an alternative to the approved source set forth in the solicitation.

GAO’s decision, W K Engineering Int’l, Inc., B-414932, (Oct. 13, 2017), involved an RFQ issued by the DLA for headrest pad assemblies associated with aircraft ejection seats.  The RFQ required that vendors submit one headrest for first article testing, and also noted that “[o]nly quotes from the approved source of supply or authorized dealers are acceptable. The dealer must provide a copy of the letter from the approved source of supply approving them to act as a dealer/distributor with their quote.  Quotes from secondary dealers will not be accepted.” The approved source of supply was AMI Industries, Inc., and the agency indicated the specific part number and listed no other approved suppliers.

The solicitation also incorporated the terms and conditions set forth in the DLA master solicitation for automated simplified acquisitions. Under these terms, alternate products would not be evaluated if the solicitation was “automated,” and the DLA, with GAO concurrence, contended that the solicitation was indeed automated through DIBBS, the DLA’s Internet Bid Board System.

WK Engineering submitted its bid with an alternate product to that required in the solicitation and did not include a letter from AMI approving WKE as a dealer of AMI’s product. WKE, upon submission for its quotation, received a notification from the DIBBS system that “[o]ffers of alternate products will not be evaluated for the current procurement.” DLA awarded the purchase order to AMI, the approved source of supply.

GAO dismissed WKE’s protest, holding that, as applicable to WKE, “[a] protester is not an interested party to protest an award to an approved source where the protester would not be eligible for award because it is not itself an approved source for the item.” This seems fairly straightforward, at least as GAO describes it. If the solicitation says quotations must include an approved source of supply, and a quotation does not include that source of supply (or indicate the vendor will act as a dealer for the source of supply), then the protester could never be awarded the bid, so it is not an interested party to protest.

The second part of GAO’s opinion is more nuanced. WKE argued that it should be considered equally with AMI, the approved source, because it is a “qualified manufacturer of similar parts.” GAO held that this amounted to a challenge “based upon alleged improprieties in a solicitation, which are apparent prior to the time set for receipt of initial quotations, [which] must be filed prior to the time set for receipt of initial quotations” under 4 C.F.R. § 21.2(a)(1).

According to the GAO, since the requirement to use the specific source was clearly apparent in the RFQ, WKE should have been able to formulate its objection upon reading the RFQ, and therefore any protest was due prior to the proposal deadline. A problem that is clear on the face of the solicitation is sometimes called a patent defect, and patent defects ordinarily cannot be challenged after the date proposals are due. Since the protest was not filed until after award was made, this part of the protest was also dismissed.

GAO’s holding is another reminder that, if a contractor believes there is an improper requirement or error in a solicitation, a protest must be made before any submission deadline. In this particular example, if a potential vendor thinks there should be alternatives to an approved source of supply, any protest of that issue is probably due before the quotation deadline. If you wait too long, GAO will not usually give you a second chance to raise this kind of issue in a protest.


View the full article

Koprince Law LLC

If you’re a winner under a solicitation, you can’t challenge the ground rules under which you won–at least under the facts of a recent GAO bid protest decision.

In that decision, GAO concluded that the protestor of a solicitation’s terms lacked standing when the protester was subsequently identified as an awardee under the solicitation.

Daekee Global Co., Ltd., B-414899 et al., (Oct. 10, 2017), involved an IDIQ procurement for ship husbanding services in the Navy’s Seventh Fleet area of operation. Performance of the contract was to occur at both commercial and military ports throughout Korea, Japan, Russia, and Taiwan. The Solicitation broke down the services required into a number of CLINs, which included ship movement, fleet handling, waste disposal, transportation, and cargo loading, among others.

The solicitation anticipated making multiple awards to the lowest priced bidders that did not take exception to the solicitation’s terms. According to GAO, “to be considered for award, offerors needed to submit by the solicitation closing a signed proposal (with acknowledgment of all amendments) that shows the offeror is not taking exception to any solicitation term; includes the certifications and representations contained in the solicitation; and includes unit prices and total prices for all line items and sub line items in the solicitation.” Bidders were also to include a signed letter stating they were not taking exception to any of the solicitation’s terms and possessed the requisite licenses and approvals for operation.

Prior to the closing date for the solicitation, Daekee Global Co., Ltd. filed a protest challenging the terms of the solicitation. Daekee raised a number of concerns with the structure of the solicitation, including concerns about regulatory compliance and the fairness of subsequent task order competitions.

Despite filing a timely protest, Daekee also submitted a proposal in response to the solicitation. While Daekee’s protest was pending, the Navy evaluated proposals and determined Daekee was a presumptive awardee. The Navy planned to make an award to Daekee as soon as the protest’s performance suspension period was lifted.

Because Daekee was a presumptive awardee under the Solicitation, the Navy moved to dismiss the protest, arguing that Daekee was not an “interested party” within the meaning of the GAO’s Bid Protest Regulations. While Daekee was pleased to discover it was a presumptive awardee, it contended its protest should still be resolved on its merits because significant questions regarding the structure of the Navy’s procurement remained outstanding. Specifically, Daekee reiterated concerns about the fairness of competition at the task order level.

GAO was not convinced. According to GAO, the question was one of competitive prejudice. As GAO explained:

Competitive prejudice is a required element of every viable protest, and where none is shown, we will not sustain a protest. In the context of a protest challenging the terms of a solicitation, competitive prejudice occurs where the challenged terms place the protester at a competitive disadvantage or otherwise affect the protester’s ability to compete.

Since Daekee had been identified as an apparent awardee under the Solicitation, GAO concluded Daekee had not been at a competitive disadvantage under the solicitation’s terms. As for Daekee’s allegations regarding the fairness of competition at the task order level, GAO concluded these challenges were premature.

In our experience, it’s not exactly common for an agency to announce, in the midst of a pre-award GAO bid protest, that the protester will be awarded a contract once the protest concludes. That said, Daekee Global Co. suggests that an agency might be able to eliminate any pre-award bid protest simply by announcing an intent to award a contract to the protester. It remains to be seen whether GAO’s decision is truly that broad, or whether there might be exceptions under which a protester could show competitive prejudice despite being named as an awardee.


View the full article

Koprince Law LLC

After a 30-degree shift in temperatures here in Lawrence overnight, I think it is safe to say fall has officially arrived. The kids and I will be adding some extra layers while we go trick-or-treating on Tuesday evening.

Candy is on the agenda next week, but today’s treat is the latest SmallGovCon Week in Review. In this edition, the SBA will soon issue a proposed rule to implement a mandatory WOSB certification, a provision in the NDAA would shorten the GAO’s time frame for resolving DoD protests, a business owner will spend 20 months in prison for GSA Schedule fraud, and much more.

  • Bye-bye, WOSB self-certification: the SBA says it is 30-60 days away from issuing a proposed rule to implement mandatory WOSB certification. [Federal News Radio]
  • A provision in the 2018 National Defense Authorization Act would force the GAO to resolve Defense Department related bid protests within 65 days instead of the current 100 day time frame, but could this plan backfire? [Nextgov]
  • A business owner will spend 20 months in prison and pay more than $1 million in restitution as part of a plea deal in a GSA Schedule fraud case. [United States Department Of Justice]
  • Have you worked with your PTAC yet?  If you’re not aware of the free resources that PTAC counselors provide for government contractors, this video provides a great overview. [YouTube]
  • Federal Times takes a look at three ways to help subcontractors receive their share of a winning bid. [Federal Times]
  • Category management “shrinks the playing field of [small business] competitors that are out there,” according to a top SBA official.[Federal Times]
  • A Florida man is facing federal bribery and wire fraud charges in connection with a kickback conspiracy for federal defense contracts. [News4JAX]
  • The slow nature of Department of Defense acquisition makes it difficult to keep up with cybersecurity defense. [Federal News Radio]
  • The GAO put the brakes on a $238 million contract for the Census Bureau’s 2020 mobility operations, sustaining a bid protest filed by AT&T. [fedscoop]
  • The SBA Inspector General says that agencies shouldn’t be able to claim 8(a) and HUBZone credit for firms that have left those programs. [SBA Office of Inspector General]
  • The GSA is looking for a new way to classify contractors and grant and loan recipients. Is Dun & Bradstreet on its way out? [fedscoop]
  • A massive $2.4 billion classified NSA contract is under protest by one of the losing bidders. [Nextgov]
  • A coalition of moderate House Democrats wants to expand a governmentwide security certification process for cloud computing to all types of government information technology. [Nextgov]

View the full article

Koprince Law LLC

Whether you are an active small business federal contractor, or an entrepreneur still getting your business off the ground, you are going to need a cybersecurity plan. Many DoD contractors, in particular, face a pending deadline to comply with NIST 800-171, as mandated by DFARS 252.204-7012.

The Kansas SBDC Cybersecurity Center for Small Business wants to help.

Located in downtown Lawrence, Kansas—just across town from us coincidentally—the Cybersecurity Center, housed at the KU Small Business Development Center, is the only SBDC in the country with an office dedicated to helping small businesses contend with the growing threat of data breaches. According to Director Brian S. Dennis, the center can be a resource for small businesses across the country, not just those in the state of Kansas.

Mr. Dennis has been the director of the Cybersecurity Center since it was founded in July. He was gracious enough to answer a few questions:

Q: Don’t hackers target only huge businesses? Why does a small business need to worry about cybersecurity? 

A: The International Data Corporation released a report in 2016 estimating that by 2020 over $101 billion dollars will be spent by companies trying to protect their digital footprint. America’s small businesses have not made a dedicated effort to build cybersecurity into their P&Ls [Profits and Losses]. That lack of funding on the small business side has been noticed by hackers. Small businesses are the backdoor into big business. A Fortune 500 company or the U.S. Government can throw as many dollars as they want at the threat of a cybersecurity breach, but all it takes is one small business vendor to take down the whole thing. A prime example of this is the 2013 Target data breach. The billion dollar retailer announced a huge data breach of customer information and it happened because of a third-party vendor had been granted access to the Target network.  The growing threat of a data breach is forcing the U.S. Government and corporate America to rethink how they choose their vendors.

Q: What causes most cybersecurity breaches?  

A: Almost any cybersecurity professional you speak to today will tell you that if there were no human users, there would be no cybersecurity threat. As end users of systems, we are flawed in our approach to internet safety. Ransomware is a prime example of this. The FBI estimates that $24 million was paid in ransoms in 2015. By 2016 that number was over $1 billion. Ransomware only works when a user on the receiving end of an exchange takes an action. We need to incorporate training across the board that enables each and every user with the knowledge of how to remain safe in the digital age.

Q: It seems like things change so quickly. How can a small business find out if its practices are sufficient or if it is at risk without knowing it? 

A: It all starts with planning. Creating a plan that works and can be tested is paramount to a small business surviving a cyber event. The threat of a digital interruption is looming over all of us and there is no silver bullet that will prevent every single attack or occurrence. But if a small business can build a plan that follows five steps, the likelihood of survival increases. Those steps are:

  1. Identify — What structures and practices do you have in place to identify cyber threats?
  2. Protect — What are the basic practices you have in place to protect your systems?
  3. Detect — What do you use to identify someone or something malicious?
  4. Respond — How will you deal with a breach if and when one occurs?
  5. Recover — How will you get your business back to normal after a breach?

Q: What if a small business is not as secure as it could be—by its nature, a small business has to choose where to put its resources, why does it need to spend money on cyberseucrity? 

A: According to Symantec, nearly half of all cyber attacks these days are targeted on small business. Small businesses are the entry point into larger operations. When your business decides to allocate resources away from cybersecurity, your opportunities will begin to diminish. The hard part is understanding where to potentially shift money and resources to ensure that this can even happen. America’s Small Business Development Center (ASBDC) has over 1,100 business consultants and advisers working across America. Find a local SBDC near you and ask them for help. A good business consultant can help you get a better grasp of your P&Ls and determine where dollars can be set aside for your cyber effort. The service is free, but the commitment is your time and effort.

[Ed. Note: SBDCs are funded in part by the U.S. Small Business Administration, which helps keep consulting costs down—services are often free.]

Q: Seriously though, what’s the worst that could happen? Is a business going to lose its contracts? Something worse?

A: The Federal government is moving swiftly to ensure that its vendors and contractors are secure. The National Institute of Standards and Technology (NIST) has created a framework for cybersecurity that is already being rolled out by the Department of Defense. DOD contractors have to complete the framework by December 31st of this year. And this is just the start. If you make the decision to not properly protect your business and you are doing business with the government, you will lose contracts, that is a guarantee. Losing contracts is just the start. The something worse that is looming on the horizon is the legal responsibility. Several states are looking at what types of recourse clients/consumers will have against a small business that allows data to be breached.

Q: What do you see coming in the future? 

A: There is no crystal ball for guessing what the next cyber threat will look like, but the general consensus is that cyber criminals will continue to prey upon our inability to properly train end users. Ransomware is a direct result of poor training. Attacks that started against users demanding ransoms in the hundreds of dollars range have morphed into attacks against municipalities demanding millions of dollars. Ransomware is easy to send out and easy to collect. Unfortunately, it will be here until someone develops a dedicated way to fight it.

The future will also hold the possibility for more business and industry to pick up the torch of the NIST Framework. The Framework is probably the best start to a business being protected. Banking, insurance and finance industries will be watching closely as the Framework is rolled out this year.


View the full article

Koprince Law LLC

When an agency takes corrective action in response to a bid protest, the agency voluntarily agrees to do something (such as re-evaluate proposals, re-open discussions, or even cancel a solicitation) to address the alleged problems identified in the protest. Corrective actions are quite common: in FY 2016, more than 23% of GAO bid protests resulted in corrective actions.

But what happens when a protester doesn’t like the scope of the agency’s proposed corrective action? As a recent GAO decision demonstrates, corrective actions can themselves be protested–but challenging an agency’s corrective action can be an uphill battle.

Booz Allen Hamilton, Inc., B-414822.5 (Oct. 13, 2017) involved a protest over a GSA procurement for support services requested by the Army Research, Development and Engineering Command, Software Engineering Directorate. Raytheon was named the apparent successful offeror for a task order award, which Booz Allen Hamilton, Inc. protested, alleging that Raytheon had an unmitigated organizational conflict of interest, and that there were issues with the evaluation of price and technical proposals.

The parties subsequently engaged in outcome prediction alternative dispute resolution, where GAO indicated it was likely to sustain the protest. GSA then took corrective action.  GSA filed a notice of corrective action with GAO, which explained its proposed actions as follows:

GSA intends to review the scope of its analysis of Organizational Conflicts of Interest (OCI) and correct and/or supplement that analysis and/or take other action as it deems necessary to ensure the OCI analysis sufficiently addresses the impaired objectivity OCI concerns or otherwise satisfies the Federal Acquisition Regulation subpart 9.5.

GSA also indicated that it would review the evaluation record to ensure Raytheon and BAH were evaluated equally. In the event of discrepancies, GSA would re-evaluate proposals and make a new best value determination.

BAH objected to the proposed corrective action, arguing that it “did not provide adequate details and does not commit the agency to resolve the issues raised by the protester.” GAO nevertheless dismissed the protest as academic. GAO did advise BAH that if it was dissatisfied with the results of the corrective action, it could file another protest.

Three days after GAO’s dismissal, BAH filed a protest with GAO, challenging the terms of the corrective action. Specifically, BAH took issue with GSA’s repeated use of “and/or” within its proposed corrective action and the fact that GSA stated it would “take other action as it deems necessary [.]”According to BAH, these broad statements did not commit GSA to any specific corrective action.

GAO did not agree. As GAO explained, the legal standard for protesting a corrective action is high:

As a general rule, agencies have broad discretion to take corrective action where the agency has determined that such action is necessary to ensure fair and impartial competition. An agency’s corrective action need not address every protest issue, but must render the protest academic by granting the requested relief. The details of implementing the corrective action are within the sound discretion and judgment of the contracting agency, and we will not object to any particular corrective action, so long as it is appropriate to remedy the concern that caused the agency to take corrective action.

In the context of BAH’s protest, GAO was satisfied by GSA’s proposed corrective action. As GAO explained, “we do not interpret GSA’s statement that it may take ‘other action as it deems necessary’ to mean that the agency could elect to utterly ignore the OCI and technical evaluation issues identified in the agency’s notice.” Moreover, GAO concluded BAH’s arguments “merely anticipate adverse actions by the agency,” which were speculative. Accordingly, GAO dismissed BAH’s protest as premature.

Interestingly, the Court of Federal Claims has occasionally applied greater scrutiny to proposed corrective actions than is typically the case at GAO. For example, in Dell Federal Systems, L.P. v. United States, 133 Fed. Cl. 92 (2017), the Court enjoined a proposed corrective action, writing that the agency’s proposed actions amounted to a “blunderbuss approach to corrective action that neither the record nor the law supports.” While the Court, too, is largely deferential to agencies in this area, the Court may nonetheless be the better bet for an offeror challenging a corrective action.

So what is the takeaway for protesters? In short, GAO affords agencies wide discretion to craft and implement corrective actions as they see fit, and challenges to corrective action before GAO are likely to be dismissed as premature. Accordingly, protesters may win the protest battle only to lose the protest war during corrective action. Moreover, protesters concerned with a proposed corrective action may wish to consider taking the challenge to the (potentially) more receptive ears of the Court of Federal Claims.


View the full article

Koprince Law LLC

An agency’s oral advice, given at a pre-proposal conference, did not amend the solicitation or legally bind the agency.

In a recent bid protest decision, the GAO reiterated that offerors rely on oral advice from agencies at their own risk–particularly when the oral advice in question appears to contradict the plain language of the solicitation.

GAO’s decision in Technology and Telecommunications Consultants, Inc., B-415029 (Oct. 16, 2017) involved an Air Force solicitation seeking IT services in support of the Air Command Personnel Recovery Division.  The solicitation was issued as a competitive 8(a) set-aside under the GSA’s 8(a) STARS II GWAC.

The solicitation provided a list of tasks that the awardee wold be expected to perform.  Under one of these tasks, the solicitation stated that the awardee would be expected to provide support to the Air Force Special Operations Command at Hurlburt Field, Florida.  However, the solicitation did not state that offerors were required to propose an employee specifically dedicated to AFSOC support.

Before the due date for proposals, the agency held a pre-proposal conference.  During the conference, attendees asked about the AFSOC position.  The Contracting Officer’s Representative said that the “AFSOC position is still funded and yes, it is still a requirement.”

After evaluating proposals, the agency announced that the task order had been awarded to a company named Constellation West.  The incumbent contractor, Technology and Telecommunications Consultants, Inc., filed a GAO bid protest challenging the award.

TTC argued that CW’s proposal was technically unacceptable because CW failed to propose an employee specifically dedicated to providing AFSOC support.  TTC contended, in part, that the statement made by the COR at the pre-proposal conference demonstrated that the Air Force required an employee specifically dedicated to this function.

“Contrary to TTC’s position,” the GAO wrote, “our cases have frequently concluded that offerors rely upon oral advice from an agency at their own risk.”  Oral advice “does not operate to amend the solicitation or otherwise legally bind the agency.”

This is “particularly the case, where, as here, the oral advice directly conflicts with the plain language of the solicitation.”  The GAO concluded: “TTC cannot use the erroneous oral advice effectively to revise the solicitation’s plain language in order to support its interpretation.”

The GAO denied TTC’s protest.

Pre-proposal conferences (and similar events) can be very helpful for prospective offerors.  But as the Technology and Telecommunications Consultants protest demonstrates, the oral advice provided at these events cannot modify the terms of the solicitation, or otherwise legally bind the agency.  Listener, beware.


View the full article

Koprince Law LLC

In a GAO bid protest, recovering costs after an agency takes corrective action turns on whether or not the agency unduly delayed the corrective action.

A recent GAO case shows that, in certain circumstances, an agency may be able to fight a protester almost to the bitter end, then take corrective action without necessarily having crossed the “unduly delayed” line.

In Evergreen Flying Services, Inc., B-414238.10 (Oct. 2, 2017), the Department of the Interior issued a solicitation in September of 2016, asking for private aircraft to help fight wildfires.

DOI wanted to hire up to 33 planes for four years, with an optional six-month extension. The idea was that the planes would be offered to the Bureau of Land Management exclusively for the 2017 fire season.

A month later, DOI received proposals from 15 firms. It evaluated offers and settled on six firms and 33 individual planes (firms could offer the use of multiple aircraft). DOI announced the awards in December 2016.

Evergreen Flying Services, Inc., a small business from Rayville, Louisiana, was one of the unsuccessful offerors. It filed a GAO bid protest the day after Christmas. Four days later, it filed a supplemental protest. Evergreen challenged the agency’s evaluation of its proposal, the best value determination, and the availability of the awardee’s aircraft.

In January 2017, before submitting an agency report, DOI chose to take corrective action. Over the next two months, it reevaluated proposals and increased Evergreen’s ratings, but still did not select it for award. Evergreen protested again, on March 3.

This time DOI fought the protest. It filed a request for dismissal (which GAO denied) and then filed an agency report on April 5. The report included each awardee’s complete schedule of services/supplies, aircraft questionnaires, and DOI’s evaluation sheets for each awardee.

Evergreen poured through the documents, seized on some issues, and filed a supplemental protest (and comments on the agency report) on April 17. The supplemental protest, for the first time, alleged flaws relating to the other offerors and the agency’s evaluation of their proposals, including minor but technical flaws such as unsigned or typewritten names instead of signatures, and reliance on supporting documentation that was outside the solicitation’s five-year window.

GAO asked for a supplemental agency report. Two days before it was due, DOI chose to take corrective action by cancelling the solicitation altogether. DOI said that the fire season was rapidly approaching and it did not have time to reevaluate proposals again. It also said it could acquire the planes it needed through other means: most of the offerors, including Evergreen, had “on-call” contracts with DOI for fire suppression services.

GAO dismissed Evergreen’s latest protests on May 4.

Evergreen and other offerors then protested the decision to cancel the solicitation and lost. The result, therefore, of three protests, two supplemental protests, one agency report, one request for dismissal, and two corrective actions, was zero contracts.

By then, Evergreen (which was using DC-based government contracts lawyers) had, no doubt, spent a significant amount of money on legal fees. It filed a request for a recommendation of costs, arguing that the agency had unduly delayed taking corrective action in the face of a clearly meritorious protest. It had been 235 days (nearly eight months) since the solicitation came out, and 130 days since Evergreen’s initial protest.

GAO wrote that, when a procuring agency takes corrective action in response to a protest, “our Office may recommend reimbursement of protest costs where, based on the circumstances of the case, we determine that the agency unduly delayed taking corrective action in the face of a clearly meritorious protest, thereby causing the protester to expend unnecessary time and resources to make further use of the protest process in order to obtain relief.”  A protest is “clearly meritorious” where “a reasonable agency inquiry into the protester’s allegations would reveal facts showing the absence of a defensible legal position.”  And, with respect to promptness, “we review the record to determine whether the agency took appropriate and timely steps to investigate and resolve the impropriety.”

Because the better part of a year had passed during which time the agency fought the protester by filing a motion to dismiss (which it lost) and an agency report, Evergreen probably thought it had a good case for costs, at least on the “unduly delayed” side of the ledger.

But that is not the way GAO saw it. GAO said that the measure of undue delay is not whether the corrective action was prompt with respect to the protester’s initial grounds, but rather whether the corrective action was prompt with respect to the first “clearly meritorious” grounds of protest.

Thus, in order to recover costs back to the December protest and initial corrective action, “the central consideration . . . is whether Evergreen’s December protest included clearly meritorious protest ground that the agency expressly committed to rectify, but failed to, such that the protester was forced to continue its bid protest litigation to get relief.”

GAO said that the initial December 2016 protests did not include “any protest grounds that we consider clearly meritorious on their face.” As for the second protest, which again DOI fought hard against, GAO said that it was not necessarily meritorious either, just that the “argument required further record development and response from the agency to determine whether the protest ground had merit.”

Finally, GAO said that because the final corrective action took place two days before the supplemental agency report was due, the agency did not unduly delay taking it—adding that the arguments brought after reviewing the awardees’ and the evaluation documents may not have had merit.

In other words, DOI’s corrective action was not delayed. In fact, it was two days early. GAO denied the request for costs. GAO noted that the purpose of recommending costs is not to reward a protester for winning. It is to “encourage agencies to take prompt action to correct apparent defects in competitive procurements.”

Evergreen Flying Service shows that just because a protester “wins” does not mean GAO will recommend an award of costs, even when the protest process takes a long time. In our practice, we often suggest that clients assume that protest costs won’t be reimbursed, even if there is a corrective action or “sustain” decision, and consider an award of costs to be a potential bonus that may (or may not) accompany a successful protest. With the twin hurdles of “undue delay” and “clearly meritorious” to surmount, a recovery of costs is not a given.


View the full article

Koprince Law LLC

A non-SDVOSB company couldn’t protest the terms of a VA SDVOSB set-aside solicitation, despite entering into a joint venture agreement with an SDVOSB–because the joint venture hadn’t started the process of becoming verified by the VA.

In a recent bid protest decision, GAO held that because neither the protester nor the joint venture was included in the VIP database, or likely to be included during the protest process, the protester wasn’t an “interested party” under the GAO’s bid protest regulations.

The GAO’s decision in Owl, Inc.; MLB Transportation, Inc., B-414962, B-414692 (Oct. 17, 2017) involved a VA solicitation for wheelchair van transport services for the beneficiaries of the Atlanta VA Medical Center.  The solicitation was issued as an SDVOSB set-aside.

Before the due date for proposals, two companies filed pre-award GAO protests.  Both companies argued that the solicitation’s scope of work was vague and that the pricing schedule was unfair, among other grounds of protest.

The VA moved to dismiss the protest filed by MLB Transportation, Inc.  The VA argued that MLB was not an interested party to pursue the protest because it was not a verified SDVOSB listed in the VIP database.

MLB conceded that it was not an SDVOSB, but stated that it had entered into a joint venture agreement with an SDVOSB to pursue the contract.  MLB acknowledged that the joint venture wasn’t listed in the VIP database, and “had not begun its VIP system application until after the time that it filed its protest.”

The GAO wrote that, under its bid protest regulations “[o]nly an ‘interested party’ may protest a federal procurement; a protester must be an actual or prospective bidder whose direct economic interest would be affected by the award of a contract or the failure to award a contract.”  In this case, GAO said, “[w]e agree with the agency that where neither MLB or its claimed joint venture are listed on the VIP website or likely to be approved to be listed on the VIP website during the protest process, the protester is not an interested party to pursue its protest.”

The GAO dismissed MLB’s protest.  (The second protest wasn’t dismissed, but was denied on the merits).

Interestingly, the GAO didn’t hold that a company must be listed in the VIP database to challenge the terms of an SDVOSB set-aside.  Instead, the GAO indicated that a company might be eligible to protest if it was “likely to be approved” during the course of the protest process.  In MLB’s case, then, the biggest problem may not have been that its joint venture was unverified, but that the joint venture hadn’t even started its application when the protest was filed.

It’s possible, of course, that MLB didn’t realize that joint ventures must be separately verified to win VA SDVOSB set-aside contracts.  In my experience, it’s rather common for contractors to assume that so long as the joint venture’s lead member is verified, the joint venture qualifies.  Not so.

As the GAO confirmed back in 2011, joint ventures must be separately verified in the VIP database.  And as MLB Transportation demonstrates, when the joint venture isn’t separately listed in VIP, and has yet to submit an application, the joint venture (and its non-SDVOSB member) are likely out of the running for a viable pre-award GAO protest.


View the full article

Koprince Law LLC

My Cubs couldn’t pull off the World Series repeat, losing badly to the Dodgers last night in the National League Championship Series.  And you know what?  I’m okay with it.  We Cubs fans are a different breed: after 108 years, many of us  thought we’d never see a title.  So after the amazing championship last year, all of 2017 felt like playing with house money.  Yankees fans might be grumbling that it’s been a whopping eight years since their last title, but Cubs fans like me will always have 2016.

Enough baseball–time to move on to what’s really important on your Friday, the SmallGovCon Week In Review!  This week, we bring you articles ranging from government employees taking illegal gratuities, a sharp decrease in the number of successful small business contractors, investigators find major problems with many of the Census Bureau’s sole source contracts, and more.

  • A 40-month prison sentence was handed down to the former comptroller of the Norfolk Ship Support Activity for conspiring with others to essentially force a government prime contractor to use a specified subcontractor. [United States Department of Justice]
  • Federal agencies met the governmentwide small business goal for the fourth straight year in fiscal 2016, but the number of small  business prime contractors has gone down by 25% since 2010. [Federal News Radio]
  • After helping to steer millions of dollars in contracts to a North Carolina defense contractor, a former employee of the Navy has now been sentenced to three years and four months in prison for his role in the scheme. [The Virginia Pilot]
  • Listen to Larry Allen on Federal Drive with Tom Temin as he discusses what GSA has in store for contractors this year. [Federal News Radio]
  • A whistleblower suit has led to a False Claims Act settlement of $2.6 million to resolve civil allegations that the company submitted false claims for payment to the DoD for unqualified security guards. [wtop]
  • Government investigators found problems with 90% of the no-bid contracts awarded by the Census Bureau, resulting in overpayment to contractors by about $9 million. [New York Post]
  • Congressional members have submitted a request for information on data security vetting for government contracts. [Homeland Preparedness News]
  • GSA Administrator nominee Emily Murphy wants the GSA to make it easier for new companies to do business with the government so competition remains robust. [Federal News Radio]
  • The Indian Health Service agency has come under fire for awarding a contract to a company that had previously paid $10 million to settle allegations of submitting false claims to the government. [Bristol Herald Courier]

View the full article

Sign in to follow this  
×