Jump to content
The Wifcon Forums and Blogs

Koprince Law LLC

Members
  • Content Count

    543
  • Joined

  • Last visited

Everything posted by Koprince Law LLC

  1. Contrary to a common misconception, an offeror is not automatically entitled to “use” the past performance of parent companies, sister companies or other corporate affiliates. So when can an offeror rely on the past performance of an affiliate in submitting a proposal? A recent GAO opinion sheds some light on that question. Not meeting the GAO’s guidelines for describing the detailed involvement of the affiliate can have a harsh result—a sustained protest if award was made based on the affiliate’s past performance. In Language Select LLP, B-415097.2 (Nov 14, 2017), GAO considered the Social Security Administration’s issuance of a Federal Supply Schedule blanket purchase agreement to Cyracom International, Inc. for worldwide telephone interpreter services. The underlying Solicitation was based on best value, considering the factors of corporate experience (the most important factor), past performance, and evaluated price. Under corporate experience, vendors were to provide a “complete and full description” of three contracts demonstrating the firm’s relevant experience and how these contracts were “similar in size, scope, and complexity to the RFQ requirement.” Past performance ratings would be based on having each client from the three corporate experience contracts submit a completed past performance questionnaire form to SSA. SSA could contract the references and obtain past performance information from other sources. SSA would base its evaluation “‘in part’ by assessing the firm’s quality of service, its timeliness of performance, its management of personnel, and its business relations.” About a month before the evaluation was finalized, SSA contacted Cyracom for an explanation of the relationship between it and another entity (the name was redacted in the opinion but was referred to as Cyracom Affiliate), because Cyracom had listed the Cyracom Affiliate’s name on the past performance contracts. Cyracom responded that Cyracom Affiliate was a wholly-owned subsidiary of Cyracom, that “its services are provided and managed by the parent company,” and that Cyracom “uses its divisions ‘[Cyracom Affiliate]’ and ‘CyraCom’ for marketing to different industries.” In evaluating the proposal of Language Select LLP, which was the incumbent contractor, SSA rated its corporate experience as “good.” For Language Select’s past performance, SSA reviewed FAPIIS/PPIRS information, past performance questionnaires, and SSA reports on incumbent performance. SSA identified one termination for cause from FEMA, and weighing this termination for cause against the multiple strengths, it assigned a “very good” rating for past performance. For Cyracom, SSA assigned a “satisfactory” rating for the corporate experience factor, taking into account the similarities of the contracts submitted in terms of scope and complexity. However, SSA found weaknesses because the contracts were smaller than SSA’s requirement. For Cyracom’s past performance, SSA noted that each prior contract was identified as performed by Cyracom Affiliate, rather than Cyracom. SSA noted that Cyracom Affiliate was a wholly-owned subsidiary of Cyracom and that its services were “provided and managed by the parent company.” There was one termination for cause in Cyracom’s past performance record, which the evaluation panel deemed a “minor problem.” The summary of the adjectival ratings and prices were; Language Select: Corporate Experience – Good, Past Performance – Very Good, Price $34.7 million. Cyracom: Corporate Experience – Satisfactory, Past Performance – Very Good, Price $29.9 million. Noting that the price difference of 13.65 percent outweighed the minimal risk of awarding to Cyracom, the contracting officer awarded the contract to Cyracom. Language Select protested the award, arguing that the SSA engaged in unequal discussions when it asked Cyracom for its relationship to the Cyracom Affiliate. SSA argued that the question to Cyracom was just a clarification, as it had already deduced that the Cyracom Affiliate was affiliated with Cyracom based on “the fact that CII’s quotation was printed on stationery that depicted an affiliation, and that information available online did also.” GAO noted, with respect to affiliation, that where an agency observes apparent affiliation between companies but lacks evidence establishing the nature of the relationship in the procurement at issue, the potential for variations in the extent and nature of the relationship between two affiliated companies means that it is not reasonable for that agency simply to infer that the relationship will affect contract performance, or even to accept an offeror’s general representation that the performance of an affiliated company–positive or negative–should be attributed to that offeror. Before the agency can properly attribute the past performance of an affiliate to an offeror, it generally must have a factual basis showing the planned relationship between the companies on the contract at issue. Where, as here, the record before the agency does not indicate the involvement of the affiliate in performance of the contract, the agency cannot simply attribute the affiliate’s past performance to the offeror. GAO concluded that, when SSA sought an explanation of the role of the Cyracom Affiliate, it constituted discussions. Since Language Select did not receive an equivalent opportunity, SSA did not conduct discussions fairly and equally. Language Select also challenged the reasonableness of SSA’s past performance and experience evaluation, arguing that it was improper for SSA to attribute the Cyracom Affiliate’s experience to Cyracom. SSA argued that it is sufficient that an affiliate “shares management with the offeror” or where “the parent company manages the entire corporate family.” GAO disagreed, noting that “[a]bsent a factual basis to conclude that the awardee had a commitment of resources from other separate corporate subsidiaries, we found the attribution of those affiliates’ past performance and experience to the awardee to be improper.” GAO held that the stationary and online information showing the affiliate relationship and the statement by Cyracom that the Cyracom Affiliate “was a wholly-owned subsidiary and that its services were ‘provided and managed by'” Cyracom was not enough to demonstrate the factual basis. This decision is important because it sets guidelines for evaluating past performance based on affiliates. Generally, in preparing a proposal that uses affiliate past performance, the offeror must clearly demonstrate the factual basis for how the affiliate will be involved in performance and how the affiliate will share resources with the offeror. Merely noting the affiliation between the offeror and the affiliate is not sufficient for use of an affiliate’s past performance. View the full article
  2. Koprince Law LLC

    Thank you, Boise!

    Last week I had the fantastic opportunity to travel to Boise to speak at the Idaho Small Business Contracting Symposium. My talk focused on recent updates in the law relating to contracting with the Federal government. It was a broad topic I hope was valuable to all who attended. The symposium provided a wonderful opportunity to meet some clients face-to-face after having established a relationship over email and the phone and also to make some great new contacts. Huge thanks to Gary Moore and Lee Velton and the Idaho PTAC for organizing and inviting Koprince Law LLC to speak. Thanks to all who stopped by the table (and if you asked me where to get a copy of the Joint Ventures handbook, here’s a handy dandy link.) Next stop: Kansas SBDC Cybersecurity Forum in Manhattan, Kan., April 25, where I’ll be on the Identify, Protect, Detect, Respond, Recover panel. The event is sponsored by the Washburn Kansas Small Business Development Center. Registration is open. Hope to see you there. View the full article
  3. HUBZone companies owned by U.S. citizens will no longer be required to demonstrate that the ownership is “direct.” The SBA’s HUBZone program rules have long required that a HUBZone company owned by U.S. citizens be at least 51% directly owned by those citizens–as opposed to allowing the qualifying citizens to own those interests through legal vehicles like holding companies. But the SBA has had second thoughts, and effective May 25, 2018, the direct ownership requirement will be eliminated. In a direct final rule issued on March 26, the SBA writes that “[d]irect ownership is not statutorily mandated” by the portion of the Small Business Act governing the HUBZone program. The SBA has concluded that “the purposes of the HUBZone program–capital infusion in underutilized geographic areas and employment of individuals living in those areas–may be achieved whether ownership by U.S. citizens is direct or indirect.” The SBA explains: The regulations first implementing the HUBZone program were largely based on those governing the Small Disadvantaged Business (SDB) program, which is no longer in existence and which served different goals than the HUBZone program. The SDB program and SBA’s other currently active socioeconomic programs (including the 8(a) BD program, the WOSB small business program, and the SDVO small business program) are intended to assist the business development of small concerns owned and controlled by certain individuals, so requiring direct ownership for these programs is consistent with their purposes. The HUBZone program differs in that the program’s goals do not center on the socioeconomic status of the SBC owner but rather the location of the business and the residence of its employees. The SBA concludes: “[t]his direct final rule deletes the requirement that ownership by United States citizens in the HUBZone program must be direct, and instead it merely copies the statutory requirement that a HUBZone small business concern must be at least 51% owned and controlled by United States citizens.” The public is invited to submit comments on the direct final rule by April 25, 2018. The rule will automatically become effective on May 25 “unless significant adverse comment is received” by the April 25 deadline. If anyone makes adverse comments (significant or otherwise), it won’t be me. I’ve long felt that the direct ownership requirement is unnecessary for HUBZone companies owned by U.S. citizens, and applaud the SBA’s deletion of this requirement. Elimination of this requirement will allow greater flexibility for U.S. citizens to own HUBZone companies using vehicles that may make good sense from business, liability, and tax standpoints. It’s worth noting that the change only applies to HUBZone companies owned by U.S. citizens. HUBZone companies owned by Indian Tribes, ANCs, NHOs, CDCs and small agricultural cooperatives have separate requirements which are unaffected by this change. One final, slightly off-topic note: if you’re an SDB, don’t freak out about SBA’s statement that the SDB program “is no longer in existence.” The SDB program is still in existence. It’s right there in the SBA’s regulations, and SDB self-certification can still offer important benefits–for example, large prime contractors are required to meet SDB goals under typical subcontracting plans. I think what the SBA meant to say is that the SBA no longer operates the SDB program as a formal certification program, which is certainly true; the SBA stopped certifying SDBs in 2008. View the full article
  4. The DoD has issued a final rule making major changes in the DoD “Pilot” Mentor-Protege Program. The rule took effect on March 23, 2018. Among the major changes, DoD has both expanded and contracted the universe of potential proteges–and has included a mandatory certification that seems to completely misunderstand the SBA’s joint venture rules and processes. Here is my take on the good, the bad, and the ugly from the final rule. The Good Unlike the SBA’s mentor-protege program, the DoD mentor-protege program isn’t open to “ordinary” small businesses–instead, an eligible protege must fit within a permitted category. The old rule limited the universe of proteges to small disadvantaged businesses (including 8(a)s), SDVOSBs, HUBZones, WOSBs, and entities employing the severely disabled. The final rule adds (1) an entity controlled and owned by an Indian tribe; (2) an entity controlled by a Native Hawaiian organization; (3) an entity owned and controlled by socially and economically disadvantaged individuals (which sounds a lot like an SDB to me); (4) a so-called “non-traditional defense contractor,” which is defined as “an entity that is not currently performing and has not performed any contract or subcontract for DoD that is subject to full coverage under the cost accounting standards . . . for at least the 1-year period preceding the solicitation of sources by DoD for the procurement or transaction”; and (5) an entity that currently provides goods or services in the private sector that are critical to enhancing the capabilities of the defense supplier base and fulfilling key DoD needs. Expanding the universe of potential DoD proteges is a good step–although it’s undermined by a rather nonsensical size limit I’ll discuss momentarily. The final rule also extends the program through September 30, 2021, which is of course a good thing. Even though it was first established in 1990, the DoD Mentor-Protege Program remains a “pilot” program and requires occasional renewal. Perhaps in 2020, Congress will honor the program’s 30th birthday by finally removing the “pilot” label. The Bad The final rule adds a new size restriction: it says that an eligible protege must be “[l]ess than half the Small Business Administration (SBA) size standard for its primary North American Industry Classification System (NAICS) code.” I guess if the SBA’s program is the All Small Mentor-Protege Program, the DoD’s is now the “Half Small.” I don’t like restricting proteges in this manner. In my view, small is small. According to the final rule, there are only 85 proteges currently participating in the DoD Mentor-Protege Program. Imposing a Half Small limit will almost certainly further reduce the number of firms participating in the program. The final rule also imposes several requirements designed to ensure that there is no affiliation or control between mentor and protege. In my view, some of these go too far. For instance, the final rule requires the mentor and protege to certify that “[t]he owners and managers of the mentor firm are not the parent, child, spouse, sibling, aunt, uncle, niece, nephew, grandparent, grandchild, or first cousin of an owner or manager of the protege firm.” This rule goes well beyond the SBA’s affiliation regulation, under which familial relationships cause a presumption of affiliation only when the individuals in question are “married couples, parties to a civil union, parents, children, and siblings.” And even then, the SBA rule is rebuttable by showing a “clear line of fracture” between the firms; there doesn’t seem to be any such rebuttal opportunity at DoD. Similarly, the final rule requires the parties to certify that “[t]he mentor firm has not, during the 2-year period before entering into a mentor-protege agreement, employed any officer, director, principal stock holder, managing member, or key employee of the protege firm.” Again, this rule goes beyond the presumptions established in the SBA’s affiliation rules and appears completely unrebuttable, no matter what role the individual in question held at the mentor firm, and regardless of the individual’s ability to control the protege. I certainly understand that the DoD wants to ensure that the program isn’t abused, but I think these overly broad rules aren’t the right way to do it. Instead of completely preventing firms with these relationships from entering the program, the DoD would be better-served to ask for this information as part of the application, then refer the matter to the SBA for a formal size determination if the answers indicate a potential concern. The Ugly The very worst of these restrictions seems to completely misunderstand the SBA’s joint venture rules and processes. The DoD mentor-protege program now requires a mentor and protege to certify that “[t]he mentor firm has not engaged in a joint venture with the protege firm during the 2-year period before entering into a mentor protege agreement, agreement, unless such joint venture was approved by SBA prior to making any offer on a contract.” There are two glaring problems with this requirement. First, the SBA doesn’t approve joint ventures for non-8(a) contracts. For small business, SDVOSB, HUBZone, and WOSB/EDWOSB contracts, a joint venture must follow the SBA regulations, but the SBA will only review the joint venture if there is a protest of the apparent successful offeror. Because it is impossible to obtain SBA’s approval for non-8(a) joint ventures, any mentor and protege who formed a joint venture for a non-8(a) contract would be precluded from participating in the DoD mentor-protege program. Second, even for 8(a) contracts, the SBA typically doesn’t approve joint ventures “prior to making an offer on a contract.” Rather, the SBA need only approve the joint venture before award of the 8(a) contract. So even if the mentor and protege had been approved by SBA for an 8(a) contract, they would likely be precluded from participating in the DoD mentor-protege program, simply because of the way the SBA 8(a) joint venture process approval process works. In practice, this rule would seem to effectively prevent anyone from applying to the mentor-protege program if the parties had formed a joint venture within the prior two years. Because a single joint venture is almost never indicative of affiliation or control, I don’t see any good public policy purpose for this rule. And since the restriction seems to stem from a fundamental misunderstanding of the SBA’s joint venture processes, this part of the final rule is downright ugly. The Rest These aren’t the only changes included in the final rule, of course. Among other revisions, the final rule limits proteges to one DoD mentor-protege agreement at a time, and imposes a five-year eligibility period for each protege. The final rule also imposes new reporting requirements designed to allow the DoD to better track the progress of mentor-protege relationships. For those considering a DoD mentor-protege application, it’s well worth reading the entire final rule to become familiar with the new requirements–good, bad, ugly, and otherwise. View the full article
  5. What a week of college basketball! I don’t think anyone could have predicted a world in which UMBC knocked out Virginia and Loyola-Chicago is knocking on the door of the Final Four, but that’s where we are. Tonight, both of my teams–Duke and KU–are playing, so I’ll be spending my Friday evening watching some hoops. But before March Madness kicks off, it’s time for the SmallGovCon Week in Review. In this week’s edition, the GSA and OMB are seeking legislative fixes as they move forward with the “Amazon Amendment,” protests against the major ENCORE III contract have been denied, a contractor admits to a bribery and gratuity scheme, and much more. The GSA and OMB are seeking legislative fixes as they seek to implement the so-called “Amazon Amendment.” [FederalNewsRadio] The major ENCORE III contract has survived four bid protests. [Nextgov] Speaking of protests, Professor Steven Schooner of George Washington University offers a timely take on the RAND Corporation’s recent bid protest report. [SSRN] A defense contractor has pleaded guilty to a bribery and gratuity scheme involving “valuable gifts” such as Apple products, luxury handbags, and Beats headphones. [U.S. Department of Justice] The DOE isn’t waiting around–it’s issued a class deviation adopting increases in the micro-purchase and simplified acquisition thresholds. [U.S. Department of Energy] The FBI has issued a timeline for the recompete of its $30 billion IT services contract. [Nextgov] The VETS 2 IT contract is open for business after several protests were denied. [Washington Technology] View the full article
  6. SmallGovCon readers may recall that, in 2016, the Government Accountability Office proposed an electronic filing system for bid protests. GAO released a pilot version of its new system earlier this year, and Koprince Law LLC has had the opportunity to test it on several occasions through our bid protest work. Here are some first impressions on GAO’s Electronic Protest Docketing System. EPDS is very functional and easy to use. If you’ve ever clicked a link, selected an option from a drop-down menu, and uploaded a document to a website, you’d have no problems using the system. But even if you did run into trouble, GAO has published a comprehensive user guide and videos that thoroughly explain how to use the system. Upon logging in, the user’s dashboard displays a list of each protest it has pending before GAO. This list provides basic information about the protest—GAO’s docket number (or “B-number”), identification of the protester and agency, filing date, next due date, and case status. From this page, users can also file a new protest (once that feature is active upon EPDS’s formal roll-out) or intervene in a protest that’s currently pending. Users can drill-down into each individual protest to view even more detailed information, like the solicitation number, whether there is an intervenor or if the protest is consolidated, the protester’s size status, and the identification of the GAO attorney considering the protest. Links to filed documents also appear on this page: if allowed access by GAO, users can view the protest, agency report, comments, and any other filings made. It’s from this page that users can also file documents—a pretty simple process of selecting the type of filing from a drop-down menu, then attaching a PDF document. Registered users are notified of each filing via an instantaneous email and can access filed documents right away. Overall, we are very impressed with EPDS. But there are a couple tweaks that could make the system even more useful: A messaging function. We don’t mean an instant messaging function [does anybody miss AIM?], but instead an email-esque function where parties can discuss routine matters with GAO. For example, we recently needed to request access to a document following our admission to a protective order; rather than simply sending a message within EPDS, we had to prepare and upload a letter. GAO responded immediately, but sending an internal email would have been more efficient. EPDS does have a “no objection” button, which allows users to, for example, easily state that they have no objection to a protective order application. But a broader, simple messaging function would be useful for other quick communications. Indefinite storage of protest documents. Before EPDS, it was up to the parties how they would store bid protest documents. And under the pilot program, it still is. But could a party use EPDS as its primary document storage system? This could be a great convenience for bid protest attorneys, especially if certain documents will remain accessible on EPDS even after a protest is closed. That said, we would caution against any requirement that litigants only store documents within EPDS—even in 2018, there will still be occasions where an attorney or pro se protester will need access to protest documents offline. These issues don’t detract from EPDS’s functionality or its ease of use. GAO has obviously paid significant attention to developing an easy-to-use system. As EPDS is rolled-out, we expect it will be proven a tremendous leap forward for the GAO bid protest process. View the full article
  7. NAICS code appeals can be powerful, and while they’re infrequent, they often succeed. But NAICS code appeals are subject to a strict, 10-day deadline–and that deadline isn’t extended by deliberations with the Contracting Officer. In a recent NAICS code appeal decision, the SBA Office of Hearings and Appeals reiterated that the 10-day deadline isn’t affected by discussions with the procuring agency. OHA’s decision in NAICS Appeal of AMEL Technologies, Inc., SBA No. NAICS-5892 (2018) involved a NAVFAC solicitation for construction management services. NAVFAC issued the solicitation as a small business set-aside and assigned NAICS Code 236220 (Commercial and Institutional Building Construction), with an associated $36.5 million size standard. The solicitation was issued on January 25, 2018. AMEL Technologies, Inc. believed that the correct NAICS code was 541330 (Engineering Services), which ordinarily carries a $15 million size standard. AMEL apparently initiated discussions with the Contracting Officer shortly after the solicitation was issued, asking the Contracting Officer to change the NAICS code to 541330. The Contracting Officer didn’t respond to the request until March 1, 2018. The Contracting Officer didn’t address the merits of AMEL’s request, but simply stated that she considered the matter closed because AMEL had not filed a formal NAICS code appeal with OHA. AMEL subsequently filed a NAICS code appeal on March 6. OHA wrote that “nder applicable regulations, a NAICS code appeal must be filed within 10 calendar days after issuance of the solicitation, or within 10 calendar days of an amendment affecting the NAICS code or size standard.” OHA “has no discretion to extend, or waive, the deadline for filing an appeal.” OHA continued, “deliberations with a procuring agency which do not result in any change to the solicitation, do not extend the [NAICS] appeal deadline.” Therefore, “the fact that [AMEL] requested that the CO reconsider the NAICS code does not alter [AMEL’s] deadline for bringing a NAICS code appeal at OHA.” AMEL “filed this appeal 40 calendar days after issuance of the RFP.” Thus, “[t]he instant appeal is untimely and must be dismissed.” OHA dismissed AMEL’s NAICS code appeal. When an agency assigns an apparently erroneous NAICS code, it’s not a bad idea to approach the Contracting Officer about a change, as AMEL did. Doing so can avoid unnecessary administrative litigation. Additionally, giving the Contracting Officer the chance to reconsider before filing a NAICS code appeal may be beneficial from a “relationship standpoint.” However, as the AMEL Technologies case demonstrates, informal discussions about NAICS codes don’t extend the strict NAICS code appeal deadline–the 10-day clock keeps ticking. View the full article
  8. A CIO-SP3 SB contract holder could not protest the award of a task order to a competitor because the order was valued at less than $10 million. In a recent bid protest decision, the GAO confirmed that civilian task order awards–including those under CIO-SP3 SB–generally cannot be protested unless the value of the order exceeds $10 million. The GAO’s decision in AMAR Health IT, LLC, B-414384.3 (Mar. 13, 2018) involved a task order RFQ issued by the Department of Health and Human Services. HHS issued the RFQ as part of the CIO-SP3 SB Government-Wide Acquisition Contract. After evaluating quotations, HHS initially awarded the task order to AMAR Health IT, LLC at a price of nearly $14 million. Zolon Tech Inc., an unsuccessful competitor, ultimately filed two GAO bid protests challenging the award to AMAR. In response to the second protest, the HHS conducted discussions and evaluated final quotations. The HHS then awarded the task order to Zolon at a price of approximately $6.3 million. AMAR attempted to file a GAO bid protest challenging the award to Zolon. The GAO wrote that “[p]rotests filed with our Office in connection with the issuance or proposed issuance of a task or delivery order under a civilian agency IDIQ contract are not authorized except where the order is valued over $10 million, or where the protester can show that the order increases the scope, period, or maximum value of the contract under which the order is issued.” For purposes of determining the value of an order, the awardee’s price “is controlling since the terms of the order define the scope and terms of the contractual commitment between the contractor and the government.” The GAO rejected AMAR’s creative efforts to encourage the GAO to take jurisdiction. “Here,” the GAO wrote, “because the order at issue is valued at less than $10 million, we lack jurisdiction to consider the protester’s challenge.” The GAO dismissed the protest. It’s easy to understand AMAR’s frustration with the circumstances here. AMAR would have won the order itself but for two GAO protests from Zolon. Then, when AMAR attempted to return the favor, it was unable to do so because Zolon’s price was below the $10 million threshold. Because the awardee’s price governs, when AMAR was the awardee, the order was protestable; when Zolon was the awardee, it wasn’t. The AMAR Health IT case highlights the difficulty of attempting to protest a task order under CIO-SP3 or another multiple-award contract. Except in unusual circumstances, the GAO lacks jurisdiction to consider the award of a task order under a civilian multiple-award contract where the value of the order is less than $10 million. View the full article
  9. Under the SBA’s size regulations, when a size standard calls for a company’s size to be determined by its average annual receipts, the company’s ongoing fiscal year usually isn’t included. In a recent size appeal decision, the SBA Office of Hearings and Appeals rejected an argument that the SBA’s evaluation of a company’s size should have included receipts from the company’s current fiscal year. OHA’s decision in Size Appeal of Nordstrom Contracting & Consulting Corp., SBA No. SIZ-5891 (2018) involved a VA IFB for the replacement of air handling units at a VA Medical Center. The solicitation was issued as an SDVOSB set-aside under NAICS code 236220 (Commercial and Institutional Building Construction), with a corresponding $36.5 million size standard. Bids were due November 28, 2017. The VA opened bids on November 28 and announced that Williams Building Company, Inc. was the apparent successful offeror. Nordstrom Contracting & Consulting Corporation then filed a size protest against WBC, alleging that WBC’s receipts exceeded that $36.5 million size standard. The SBA Area Office evaluated the size protest. Because WBC had submitted its bid in November 2017, the Area Office used WBC’s last three completed fiscal years–2014, 2015, and 2016–as the basis of its measurement. After running the numbers, the Area Office concluded that WBC fell below the $36.5 million size standard. Nordstrom filed a size appeal with OHA. Nordstrom pointed to information from USASpending.gov indicating that WBC was awarded federal contracts exceeding $50 million in 2017. Nordstrom contended that the Area Office should have included WBC’s 2017 receipts because the Area Office’s size review was conducted in January 2018. OHA wrote that, under 13 C.F.R. 121.404(a), a company’s small business size status ordinarily is determined “as of the date the concern submits a written self-certification that it is small to the procuring activity as part of its initial offer (or other formal response to a solicitation), which includes price.” Additionally, under 13 C.F.R. 121.104(c), the SBA ordinarily calculates size under a receipts-based size standard by examining “the total receipts of the concern over its most recently completed fiscal years divided by three.” In this case, “it is undisputed that WBC self-certified as a small business with its bid on November 28, 2017.” OHA continued: Therefore, WBC’s three most recently completed fiscal years were 2014, 2015, and 2016. Fiscal year 2017 was not yet complete at the time of WBC’s self-certification, and thus is not included in the period of measurement. Accordingly, the Area Office correctly based its review on WBC’s average annual receipts over the time period 2014-2016. OHA denied Nordstrom’s appeal. As with many rules in government contracting, the rule discussed in the Nordstrom Contracting case has an exception: when a company has been in business less than three complete fiscal years, the SBA will use an alternate formula that includes revenues generated in the ongoing fiscal year. But as the Nordstrom Contracting size appeal demonstrates, a company’s size under a receipts-based size standard usually turns on the average of the last three completed fiscal years–and excludes revenues generated in the ongoing fiscal year. View the full article
  10. Koprince Law LLC

    SmallGovCon Week In Review: March 12-16, 2018

    This is a month my office (which represents several different teams) gets excited for. The first week of March Madness is here, which means you may have found yourself being less productive than usual–don’t worry, that’s expected! But even during a time as captivating as the NCAA tournament, the world of government contracting doesn’t slow down. In this week’s edition of the SmallGovCon Week in Review, a communications company has agreed to pay over $12 million to settle civil False Claims Act allegations, antitrust critics fear that a winner-take-all contract for the Defense Department’s cloud computing could help tech giant Amazon corner the government contract market, a construction company lost $40 million in four years in a scheme to illegitimately gain government contracts, and much more. A San Diego communications company will pay more than $12 million to settle False Claims Act allegations regarding SBIR contracts. [www.justice.gov] Amazon’s attempt to land a major Pentagon job has stoked some antitrust fears. [thehill.com] A construction company owner fraudulently obtained set-aside contracts–but only gets probation. [post-gazette.com] During Sunshine Week, senators cite issues with FOIA request backlog. [Federal News Radio] Alliant 2 SB has been awarded–now comes the inevitable protest phase. [Washington Technology] The Pentagon tells its leaders to talk more with contractors–but less with the press. [Government Executive] One commentator says that the DoD’s cloud strategy stifles innovation. [Federal News Radio] View the full article
  11. Under a multiple award contract, the underlying contract ordinarily governs whether a contractor qualifies as a woman-owned small business for purposes of task or delivery orders. As demonstrated in a recent SBA Office of Hearings and Appeals decision, if a company qualifies as a WOSB or EDWOSB at the time of its initial offer on the underlying multiple-award contract, it will also qualify as a WOSB or EDWOSB for each order issued against the contract, unless the contracting officer requests recertification in connection with a particular order. OHA’s decision in Island Creek Associates, LLC, SBA No. WOSB-110 (2018) involved a Marine Corps solicitation for services in support of the Global Combat Support Systems-Marine Corps/Logistics Chain Management Program. The solicitation was issued as a competitive task order procurement under the SeaPort-e multiple-award IDIQ contract. The agency issued the solicitation as a WOSB set-aside, but did not request that SeaPort-e contractors recertify their WOSB status for purposes of the task order competition. After evaluating proposals, the agency announced that ReMilNet, LLC was the apparent successful offeror. An unsuccessful competitor, Island Creek Associates, LLC, then filed a WOSB status protest challenging ReMilNet’s eligibility. The SBA Director of Government Contracting issued a decision finding ReMilNet to be an eligible WOSB. Island Creek appealed the determination. OHA asked the parties to address whether the SBA should have dismissed the initial WOSB status protest as untimely. OHA pointed out that in a 2017 case involving SBA’s similar SDVOSB rules, OHA held that a protest of a task order was untimely because it wasn’t filed within five business days of the award of the underlying multiple-award contract or an option under that contract. In that case, OHA noted that the contracting officer hadn’t requested recertification at the task order level, and thus there was no new SDVOSB certification to protest with respect to the task order. OHA wrote that “with regard specifically to orders under a Multiple Award Contract, SBA regulations state that a concern will retain its status as a WOSB or EDWOSB for the entire duration of the contract, unless the CO requests recertification in connection with a particular order.” In this case, “ReMilNet self-certified as a WOSB when it submitted its offer for the SeaPort-e contract in 2014, and no status protest was filed at that time.” Moreover, “it is undisputed that the CO here did not request recertification for the instant task order.” Accordingly, “Appellant’s protest was untimely because it was not filed within five days after award of ReMilNet’s SeaPort-e contract or an order requiring recertification.” OHA vacated the SBA’s decision and dismissed the appeal. When it comes to multiple-award contracts, there is a lot of confusion about when a company must qualify by size and/or socioeconomic status. As the Island Creek Associates case demonstrates, in the WOSB and EDWOSB context, the self-certification made in connection with the underlying contract ordinarily governs. View the full article
  12. An agency was not required to evaluate past performance under an SDVOSB set-aside solicitation that contemplated making award to the lowest-price, technically-acceptable offeror. According to a recent GAO bid protest decision, a past performance evaluation in the context of an LPTA set-aside is essentially duplicative of the agency’s evaluation of responsibility, meaning that a separate past performance evaluation isn’t necessary. GAO’s decision in Data Monitor Systems, Inc., B-415761 (Mar. 6, 2018) involved an Air Force solicitation for base operations and support services at Grissom Air Reserve Base. The solicitation was set-aside for SDVOSBs, and called for award to the lowest-price, technically acceptable offeror. Under the solicitation, the Air Force would evaluate two factors: technical merit and price. The solicitation did not include past performance as an evaluation factor. In a contemporaneous Determination and Findings, the Air Force found that evaluating past performance would not provide any significant benefit. In its D&F, the Air Force noted that, under an LPTA evaluation, offerors with limited or unknown past performance cannot be evaluated unfavorable, meaning that such offerors are entitled to an “acceptable” rating. Additionally, because the acquisition was an SDVOSB set-aside, any “unacceptable” past performance score would need to be referred to the SBA under the Certificate of Competency program, increasing the potential administrative burdens of conducting the acquisition. Data Monitor Systems, Inc. filed a pre-award bid protest challenging the terms of the solicitation. DMS argued, in part, that failing to include past performance as an evaluation factor was unreasonable and improper. The GAO wrote that “the FAR provides that past performance need not be evaluated if the contracting officer documents the reason past performance is not an appropriate evaluation factor for the acquisition.” And, in the context of a LPTA set-aside competition, the GAO “has previously questioned the value of including past performance as a separate evaluation factor precisely because the past performance evaluation is ultimately reduced to a matter of the firm’s responsibility, which will be evaluated, in any case, after source selection.” This is particularly true “given the difficulties associated with how to consider a neutral rating in the context of a pass/fail evaluation, which as noted by the agency’s D&F in this case, is the rating required for firms without any past performance record or where the record is not available.” The GAO concluded: “n sum, we see no basis to disturb the agency’s conclusion that performing a past performance evaluation in the context of a lowest-priced, technically-acceptable procurement, which is set aside for small businesses, is essentially duplicative of the agency’s responsibility determination . . ..” The GAO denied the protest. Past performance is, of course, an extremely common evaluation factor. But as the Data Monitor Systems case demonstrates, procuring agencies are not required to consider past performance in every acquisition. Where, as here, the acquisition will be set-aside for small businesses and award made on an LPTA basis, an agency may have good reason to forego an evaluation of past performance. View the full article
  13. Koprince Law LLC

    SmallGovCon Week In Review: March 5 – 9, 2018

    I am back in Kansas after spending some time in sunny Florida for the APTAC Spring 2018 Training Conference in Jacksonville. Next week, I hit the road again, this time to not-so-sunny (but still awesome) Washington State, where I’ll be giving a session at the 2018 Alliance Northwest Conference in Puyallup, WA. If you are attending the event, please be sure to connect. Now it’s time for the latest and greatest in government contracting. In today’s edition of the SmallGovCon Week in Review, the Pentagon has reportedly slashed a contract worth almost $1 billion that was awarded last month, a former contractor has been convicted of retaining classified information, the DOJ launches a national FOIA portal, and much more. The Pentagon has slashed an Amazon partner’s $950M cloud computing contract. [siliconangle.com] The State Department is updating contract language regarding requirements for contractors to cooperate with the agency Inspector General. [Federal News Radio] A former defense contractor has been convicted of unlawfully retaining classified information. [justice.gov] DOD defends its decision to move to commercial cloud with a single award. [fedscoop.com] The DOJ has announced the launch of a national FOIA portal. [justice.gov] View the full article
  14. An 8(a) Program participant was terminated from the 8(a) Program for failing to pay a subcontractor. According to the SBA, the non-payment reflected poorly on the 8(a) company’s character–and “good character” is a prerequisite for 8(a) Program participation. The decision of the SBA Office of Hearings and Appeals in Corporate Portfolio Management Solutions, SBA No. BDPT-567 (2018) was an appeal of the SBA’s decision to terminate Corporate Portfolio Management Solutions from the 8 (a) Program. The reason for the termination was CPMS’s failure to pay a subcontractor. In 2012, the SBA certified CPMS as an 8(a) Program participant. The following year, the GSA awarded CPMS an 8(a) prime contract. CPMS then hired a subcontractor, Procon Consulting, LLC, to perform some of the work under the GSA contract. By April 2016, CPMS owed Procon $68.688.53 for its subcontract work. In August 2016, Procon initiated arbitration before the American Arbitration Association to recover the amounts due. In December 2016, CPMS signed a consent order and judgment acknowledging that it owed Procon the full $68,688.53. CPMS agreed to pay Procon $75,000 in three installments, with the last installment due February 28, 2017. In June 2017, Procon filed a complaint in the Superior Court of the District of Columbia, seeking to enforce the arbitration consent order. Procon alleged that CPMS had failed to make any of the agreed-upon installment payments. In October 2017, the Court issued a judgment in favor of Procon. Procon didn’t limit itself to civil remedies. In July 2017, Procon sent a letter to the SBA asking for the SBA’s assistance in recovering the unpaid debt and urging the SBA to revoke Procon’s 8(a) certification. In August 2017, the SBA suspended CPMS from participating in the 8(a) Program. By notice dated October 27, 2017, the SBA informed CPMS that it was being terminated from the 8(a) Program. The SBA’s notice specified that the termination was due to a lack of business integrity because CPMS had failed to pay Procon and failed to comply with the arbitration order. CPMS appealed the termination to OHA. CPMS said that it had begun making payments to Procon and had taken other corrective actions such as implementing new corporate policies. However, CPMS did not dispute any of the underlying facts regarding its relationship with Procon. OHA wrote that “[t]he SBA has an affirmative responsibility under the Small Business Act to ensure that only eligible business concerns are admitted into, and remain in, the 8(a) BD program.” OHA explained, “[t]his ensures that public funds are properly administered, and that the benefits of the 8(a) BD program are limited to those small businesses that qualify to receive such benefits.” Here, even assuming that CPMS had begun making payments to Procon and had changed some of its internal corporate policies, “these contentions do not rebut SBA’s conclusion that [CPMS] engaged in conduct indicating a lack of business integrity when it failed to pay its subcontractor.” OHA dismissed the appeal. The Corporate Portfolio Management Solutions case shows that, when it comes to 8(a) Program participation, “good character” means more than avoiding criminal convictions. If an 8(a) Program participant doesn’t pay its bills, the SBA may terminate the participant from the 8(a) Program. View the full article
  15. Koprince Law LLC

    Thank You, APTAC!

    I am back in Kansas after a fantastic trip to Jacksonville, Florida, where I spent yesterday at the Association of Procurement Technical Assistance Centers Spring Conference. My morning general session focused on important recent developments in government contracting–everything from key provisions of the 2018 National Defense Authorization Act to the impact of the RAND Corporation’s bid protest report. It was great to see so many familiar faces. Thank you to all of the wonderful PTAC counselors who attended the session and asked great questions during the presentation and after. A big thanks to Scott Knapp of our local Kansas PTAC, who provided a warm introduction. And a special thank you to the attendees who took my advice and really did “live Tweet” about the great pink tie my daughter gave me last Father’s Day! Spending time with the PTACers is always one of the highlights of my professional year. If you’re a government contractor who hasn’t yet connected with your local PTAC, you’re missing out. Visit the APTAC homepage to find out more. View the full article
  16. If a prospective contractor wishes to file a size protest, it must act quickly: the protester ordinarily has five business days to initiate its protest. But does the deadline get extended if the agency takes corrective action in response to a bid protest? Maybe, maybe not. A recent SBA Office of Hearings and Appeals decision examines that question. The case of Chenega Support Services, LLC, SBA No. SIZ-5874 (Dec. 12, 2017) involved a solicitation for an Air Force contract for operating certain medical centers. The Solicitation was assigned NAICS Code 621399, Office of All Other Miscellaneous Health Practitioners, with a corresponding size standard of $7.5 million. On December 19, 2016, the Air Force awarded the contract to Prairie Quest, Inc. and notified Chenega Support Services, LLC of the award. Chenega and another party then filed timely GAO bid protests. In response to the bid protests, the Air Force issued a stop work order on January 10, 2017, and indicated on January 18, 2017, it would undertake corrective action by conducting a new past performance evaluation and new source selection decision. However, the Air Force did not terminate the award to Prairie Quest. Instead, the Air Force said that the award would remain in place pending the reevaluation, and would only be terminated if the reevaluation led to a different outcome. On October 3, 2017, the Air Force confirmed award to Prairie Quest. Chenega filed a size protest on October 10, 2017. The size protest was filed within five business days of the October 3 confirmation but was filed long after the initial award in December 2016. The SBA Area Office dismissed the size protest as untimely. The Area Office held that because the award had never been terminated, any viable size protest was due five business days after the award in December 2016–not five business days after the October 2017 confirmation of award. Chenega appealed to OHA. On appeal, Chenega argued that, because there had been a new source selection, “Prairie Quest could not have been the apparent awardee while the corrective action was ongoing, and no prospective awardee existed until the Air Force made its new selection decision in October 2017.” OHA looked at the underlying regulation regarding timeliness of size protests, which states in relevant part that “[a] protest must be received by the contracting officer prior to the close of business on the 5th day, exclusive of Saturdays, Sundays, and legal holidays, after the contracting officer has notified the protestor of the identity of the prospective awardee.” 13 C.F.R. § 121.1004(a)(2). OHA reasoned that “the regulations do not contemplate any exception if corrective action occurs after the award notification.” In making this decision, OHA reaffirmed the holding of EFT Architects, Inc., which we examined on the blog in 2013. The recent decision confirms that this timing issue is still coming up. But five years later, OHA is not inclined to reconsider its earlier ruling. That takes us back to to the underlying question: how does corrective action impact a size protest? As the Chenega Support Services case demonstrates, the answer is “it depends on the scope of the corrective action.” If the corrective action results in a termination of the original award, it seems clear that a new five-day window opens when a new award is announced. But where, as here, the agency does not terminate the original award while it undertakes a reevaluation, and then confirms the award to the original awardee, there is no new size protest window. View the full article
  17. March has arrived, and soon it will be time for all the March Madness fun. But first, I will be heading to sunny Florida for the APTAC Spring 2018 Training Conference on Monday. If you’re a PTAC counselor, I hope to see you there. In today’s edition of the SmallGovCon Week in Review, an Atlanta-based company that failed to deliver millions of emergency meals to Puerto Ricans struggling to recover from Hurricane Maria may have plagiarized its winning bid, a former quality-control officer who demanded kickbacks from construction businesses he monitored is going to prison, Guy Timberlake takes a look at the use of Product Service codes, and much more. Government contracts guru Guy Timberlake says that “fair opportunity is not the best value in Simplified Acquisitions for agencies or small business concerns.” [linkedin.com] An Atlanta-based contractor has been accused of plagiarizing its bid for a major Puerto Rico food supply contract. [usnews.com] The instigators of a kickback scheme at a South Carolina military base are heading to prison. [postandcourier.com] One commentator says that the Pentagon’s new $1 Billion cloud deal may signal a new era in government buying. [nextgov.com] The GSA says a recent rule change will simplify Schedule buys and reduce the proliferation of multiple-award contracts. [federalnewsradio.com] Two recent DHS procurements show how innovation is happening in government. [federalnewsradio.com] Guy Timberlake reminds contractors that NAICS codes are just part of the story–to truly understand how procurements are classified, you also need to think about Product Service Codes. [govconchannel.com] Congratulations to the 40 companies named as potential winners of the CIO-SP3 Small Business ramp-on. [washingtontechnology.com] View the full article
  18. Under the FAR, unbalanced pricing may increase performance risk and can result in the government paying unreasonably high prices. But the concept of unbalanced pricing is often misunderstood in practice. As the GAO wrote in a recent bid protest decision, unbalanced pricing doesn’t exist merely because some of an offeror’s line item prices are low. Rather, unbalanced pricing requires both understated and overstated line items–that is, some line items appear too high while others appear too low. The GAO’s decision in First Financial Associates, Inc., B-415713, B-415713.2 (Feb. 16, 2018) involved a DHS solicitation to administer the agency’s child case subsidy program. The solicitation was issued as a small business set-aside, and contemplated the award of a contract to the offeror providing the best value considering three factors: technical merit, past performance, and price. The solicitation apparently called for offerors’ pricing proposals to include breakdowns by contract line item numbers. After evaluating proposals, the agency awarded the contract to FEEA Childcare Services, Inc. An unsuccessful offeror, First Financial Associates, Inc., then filed a GAO bid protest. FFA challenged several aspects of the agency’s evaluation. Among its challenges, FFA alleged that FEEA’s pricing was unbalanced because FEEA allegedly had priced some CLINs “extremely low.” The GAO wrote that “balanced pricing exists where the prices of one or more line items are significantly overstated or understated, despite an acceptable total evaluated price (typically achieved through underpricing of one or more other line items.)” To prevail on an allegation of unbalanced pricing, “a protester must show that one or more prices in the allegedly unbalanced proposal are overstated; it is insufficient to show simply that some line item prices in the proposal are understated.” The GAO explained, “[w]hile both understated and overstated prices are relevant to the question of whether unbalanced pricing exists, the primary risk to be assessed in an unbalanced pricing context is the risk posed by overstatement of prices, because low prices (even below cost prices) are not improper and do not themselves establish (or create the risk inherent in) unbalanced pricing.” In this case, “FFA only claims that some of FEEA’s CLIN prices are understated; FFA does not allege that any of the awardee’s CLIN prices are overstated.” Therefore, “FFA provides no basis for us to question the agency’s price evaluation for allegedly failing to identify unbalanced prices.” In the competitive world of government contracts, it’s not unusual for competitors to question one another’s pricing, and “unabalanced pricing” is one of those terms that is often thrown around when a competitor’s pricing appears suspect. But as the First Financial Associates protest demonstrates, a proposal containing understated CLINs alone isn’t unbalanced–rather, unbalanced pricing requires both understated and overstated line items. View the full article
  19. Despite older case law to the contrary, the GAO ordinarily lacks jurisdiction to decide a protest challenging the award of a subcontract, even where the subcontract is alleged to have been made “for” the government, as in the case of some subcontracts awarded by DOE Management and Operation prime contractors. In a recent decision, the GAO confirmed that, except in very narrow circumstances, it won’t decide protests challenging subcontract awards. The GAO’s decision in Peter Vander Werff Construction, Inc., B-415676 (Feb. 6, 2018) involved the award of a subcontract by Lawrence Livermore National Security, LLC. LLNS is a M&O prime contractor to the DOE, responsible for the management and operation of the Lawrence Livermore National Laboratory in California. LLNS’s prime contract included FAR 52.244-5 (Competition in Subcontracting) which specifies that a prime contract shall select subcontractors “on a competitive basis to the maximum extent practicable with the objectives and requirements of the contract.” In March 2017, LLNS issued a competitive solicitation for the award of multiple master task agreements for general construction and design services. LLNS received 32 offers. After evaluating those offers, LLNS made 16 awards. LLNS informed the remaining offerors, including Peter Vander Werff Construction, Inc., that their offers were unsuccessful. PVWC filed a GAO bid protest challenging the evaluation. The DOE moved to dismiss the protest, arguing that the GAO lacked jurisdiction. The GAO wrote that, for several years, it “took jurisdiction over subcontract awards by prime contractors to the federal government where, as a result of the government’s involvement in the award process, or the contractual relationship between the prime contractor and the government, the subcontract, in effect, was awarded on behalf of–i.e., ‘by or for’–the government, and federal procurement laws and regulations otherwise would apply.” But in 1991, the U.S. Court of Appeals for the Federal Circuit issued a decision interpreting jurisdictional language similar to that governing the GAO. In that case, the Federal Circuit held that the General Service Administration’s Board of Contract Appeals lacked jurisdiction over subcontract procurements conducted “for” a federal agency, unless the prime contractor was a “procurement agent” as narrowly defined in other authority. After the Federal Circuit issued its decision, the GAO narrowed its jurisdiction over subcontract protests. Since the 1991 decision, the GAO will only take jurisdiction over a subcontract protest in two instances: first, “upon the written request of the federal agency that awarded the prime contract,” and second, “where we find that a subcontract essentially was awarded ‘by’ the government.” With respect to the second instance, GAO has “considered a subcontract procurement to be ‘by’ the government where the agency handled substantially all of the substantive aspects of the procurement and, in effect, took over the procurement, leaving to the prime contractor only the procedural aspects of the procurement, i.e., issuing the subcontract solicitation and receiving proposals.” In contrast, unlike its pre-1991 cases, the GAO will no longer take jurisdiction of a subcontract that was awarded “for” the government. In this case, there apparently was no written request by DOE that the GAO decide this matter. Additionally, the GAO found that this was not a subcontract issued “by” the Government. In that regard, the GAO wrote that “the record does not establish that the agency controlled essentially every meaningful aspect of the procurement.” Instead, “the evaluation and ultimate decision was made by LLNS,” the prime contractor. The GAO dismissed the protest. As the Peter Vander Werff Construction case demonstrates, the GAO’s jurisdiction over subcontract protests is very narrow. Contrary to older case law, the GAO no longer accepts jurisdiction based on the allegation that a subcontract was awarded “for” the government. View the full article
  20. To be eligible for a small business set-aside procurement seeking a manufactured product, an offeror has to either be the product’s manufacturer or otherwise qualify under the nonmanufacturer rule. Determining whether a business qualifies—either as the manufacturer or nonmanufacturer—can be a fact-intensive and confusing task. But it’s a vitally important one, as the penalty for not qualifying can be the loss of an awarded contract. Recently, however, the SBA Office of Hearings and Appeals provided important clarity on how a small business might qualify as a nonmanufacturer. Let’s take a look. Under SBA’s regulations, a firm may qualify as a nonmanufacturer if it meets four criteria: The business does not exceed 500 employees; It is primarily engaged in the retail or wholesale trade and normally sells the type of item being supplied; The business takes ownership or possession of the item(s) with its personnel, equipment, or facilities in a manner consistent with industry practice; and The business will supply the end item of a small business manufacturer, processor, or producer made in the United States (or gets a waiver of this requirement). 13 C.F.R. § 121.406(b)(1). Recently, the OHA considered what it takes to comply with the second of these requirements, when it considered a small business protest alleging the awardee did not normally sell the items procured by the government. At issue in SeaBox, Inc., SBA No. SIZ-5881 (2018) was a Marine Corps procurement seeking ISO dry and refrigerated cargo containers. The solicitation was issued as a total small business set-aside, under a manufacturing NAICS code (specifically, code 332439, for Other Metal Container Manufacturing). After QAF Technologies, Inc. was awarded the contract, SeaBox filed a protest alleging that QAF didn’t normally sell the type of items being procured. SeaBox’s argument was somewhat interesting—though SeaBox acknowledged that QAF sold similar items to the federal government, it said that federal government sales were not sales in “the retail or wholesale trade,” as required under the second nonmanufacturer rule criterion. This argument was rejected by the SBA Area Office, and SeaBox filed an appeal alleging the same at the OHA. But it wasn’t successful at OHA, either. After considering the regulatory history, the OHA concluded that federal government sales qualify as sales within the retail or wholesale trade. What’s more, the regulation doesn’t require a company to sell the exact items procured, but only the type of item being procured. Thus, QAF’s past sales of similar items to the federal government were sufficient to meet the second criterion to the nonmanufacturer rule. The OHA denied SeaBox’s appeal and affirmed that QAF was an eligible small business under the procurement based on its compliance with the nonmanufacturer rule. As mentioned, complying with the manufacturer rule or nonmanufacturer rule is a prerequisite for a small business’s eligibility for a small business set-aside under a manufacturing NAICS code. For help determining if you comply, give me a call. View the full article
  21. After a long week that included two ice storms here in the Midwest, I hope you’re ready for a relaxing weekend. But first, it’s Friday, which means that it’s time for the SmallGovCon Week In Review. In today’s edition, a Utah man pleads guilty to wire fraud and money laundering for his role in a scheme to obtain government construction contracts set aside for SDVOSBs, a former CEO pleads guilty to an $8.1 million “Made In The USA” marketing scheme and government contract fraud, the federal services market has experienced a jolt of dealmaking activity in recent months as companies position themselves to capture new government spending, and much more. SDVOSB fraud: a Utah man has pleaded guilty to wire fraud and money laundering charges. [justice.gov] Speaking of guilty pleas, a former CEO has pleaded guilty in relation to a scheme to sell Chinese-made combat boots as “Made in America.” [justice.gov] Merger mania? Dealmaking accelerates as federal contractors jockey for spending. [standard.net] Are RFIs a waste of time and money? [fcw.com] The GAO has sustained a protest of a $771 million award. [nextgov.com] One commentator says that increases in the micro-purchase and simplified acquisition thresholds are a “win-win.” [Federal News Radio] View the full article
  22. Civilian agencies may issue class deviations to quickly implement provisions of the 2018 National Defense Authorization Act increasing the micro-purchase threshold to $10,000 and the simplified acquisition threshold to $250,000. In a memorandum for civilian agencies issued on February 16, the Civilian Agency Acquisition Council says that agencies may elect to adopt interim authority allowing their Contracting Officers to take advantage of these higher thresholds, even as the FAR Council goes through the formal process of codifying those changes. The memorandum states that an official FAR Case has been opened to “implement that appropriate statutory changes in the FAR that are compelled” by the 2018 NDAA. However, “agencies may have a need to use the increased thresholds prior to publication of the FAR changes.” Therefore, the memorandum “constitutes consultation in accordance with FAR 1.404 with the Chair of the CAAC allowing agencies to authorize a class deviation to implement the changes.” The CAAC’s memorandum makes it relatively easy for agencies to adopt class deviations: the CAAC provides agencies with the relevant FAR text, together with “highlights of the appropriate FAR citations needing changes to implement the increased thresholds.” The highlighted provisions may serve “as a basis for issuing a class deviation.” The CAAC memorandum “is effective immediately, and remains in effect until the increased thresholds are incorporated into the FAR or is otherwise rescinded.” It’s very important to note that the CAAC memorandum is not itself a class deviation. Instead, it authorizes civilian agencies to adopt their own class deviations while the FAR Case is pending. If I don’t miss my guess, many Contracting Officers are going to be pushing their agencies for class deviations to take advantage of this new authority more quickly. We’ll keep you posted. View the full article
  23. As a contractor, you strive to do the best job for the fairest price and to develop a good working relationship with the government. But in government contracts—like in any other—disputes sometimes arise. So what’s the best way to protect your interests under the contract? Here are five things you should know about the basics of claims: What is a claim? A claim is a written demand to the agency requesting some type of relief under a contract. Unlike other means of resolving disputes, the Contract Disputes Act requires a contracting officer to respond, in writing, to a claim. If the Contracting Officer fails to do so, you can take your case directly to a judge under a theory called “deemed denial.” Under this process, the contractor and the government basically litigate their dispute before a judge with jurisdiction to consider the matter. A claim can help define your rights and obligations under a contract. If you have a dispute under your contract, a claim is generally the formal, legal way to get it resolved. Sometimes, a contracting officer might interpret a contractual provision differently or request that work be performed in a manner that differs from the solicitation. Other times, the agency might cause delays that increase your cost of performance. Whenever a dispute arises under a contract, you may wish to consider a claim—otherwise, you could risk losing money and adverse performance ratings (or even termination). File your claim with the contracting officer, not GAO or a Board of Contract Appeals. Perhaps because their bid protest decisions are so common, some contractors think that claims must be filed at the Government Accountability Office. Nope—disputes as to contract administration (in other words, claims) fall outside GAO’s jurisdiction. Other contractors hope to file a claim directly with a Board of Contract Appeals, like the Armed Services Board of Contract Appeals. Boards do get involved in claims but only at the appellate level after the Contracting Officer issues a decision (or a deemed denial). Claims are, instead, filed directly with the contracting officer for resolution. Each claim should be in writing and explain the factual and legal reasons why you’re entitled to the relief sought. This relief, moreover, could be money or some type of contract modification. The claim process is set by statute. The Contract Disputes Act governs the claim resolution process. In a nutshell, contractors generally have six years to file a claim (but try to avoid waiting this long—and make sure that a shorter period doesn’t apply in your case). You must do so, as mentioned, by sending your written claim to the contracting officer. Claims valued at greater than $100,000 have to be certified by the contractor. Once the contracting officer receives the claim, she has a soft 60-day response deadline. Her response should be in writing and give the reasons why a claim was accepted or denied. If the claim is denied, the contractor can appeal to appropriate Board of Contract Appeals or federal court. A claim doesn’t have to harm your relationship with the agency. One of the most common questions I hear from contractors considering a claim is whether it will hurt their relationship with the contracting officer. My response is simple: it doesn’t have to. The vast majority of contracting officers understand that claims are part of the cost of doing business. If a contractor presents a claim in a professional and civil manner, contracting officers usually reciprocate. And if a valid dispute exists, most contracting officers would rather resolve it through an early claim than have it blow up into something larger (and harder to fix). A claim simply doesn’t have to ruin a relationship. But if you still have concerns, consider a less-formal option. The FAR, for example, encourages contracting officers to use alternative dispute resolution proceedings if requested by a contractor. You can also request that your contract be equitably adjusted—though similar to claims, requests for equitable adjustment are usually less formal and might be viewed as less adversarial. Sometimes these approaches can also save time and money. No matter which option you choose, don’t let fear of ruining a relationship stop you from protecting your rights under a contract. *** So that’s it: five things you should know about the basics of claims. If you have a dispute with an agency under a contract and are considering a claim, call me to discuss your options. View the full article
  24. A subsidiary cannot file an SBA size protest on behalf of its parent company. Last week, I wrote about an SBA Office of Hearings and Appeals case holding that a parent couldn’t file a size appeal on behalf of its subsidiary. Unsurprisingly, it turns out that the same principles apply to initial size protests, too. OHA’s decision in Size Appeal of Conrad Shipyard, LLC, SBA No. SIZ-5873 (2017) involved a DOT solicitation for the construction of an ice-breaking tugboat. The solicitation was issued as a small business set-aside under NAICS code 336611 (Ship Building and Repairing), with a corresponding 1,250-employee size standard. Conrad Shipyard, LLC submitted a proposal. Conrad Shipyard, LLC is part of a family of companies ultimately owned by Conrad Industries, Inc. Conrad Shipyard, LLC has two wholly-owned subsidiaries: Conrad Orange Shipyard, Inc. and Conrad Shipyard Inc. (In this case, the two relevant companies are Conrad Shipyard, LLC and Conrad Orange Shipyard, Inc. For ease of reference, I am going to call them “Conrad Shipyard” and “Conrad Orange,” respectively). After evaluating competitive proposals, the DOT announced that Gulf Island Shipyards, LLC was the apparent successful offeror. Conrad Orange then filed a size protest, arguing that GIS was not an eligible small business. In the size protest, Conrad Orange stated that it was an interested party because it had submitted an offer in response to the DOT solicitation. The Conrad companies apparently realized their mistake. Five days after filing the initial size protest, Conrad Shipyard–the offeror–filed a “Notice of Amendment” to the size protest. Conrad Shipyard asked the the size protest be amended to reflect Conrad Shipyard, not Conrad Orange, as the protester. The SBA Area Office held that Conrad Orange was not an interested party because it did not submit an offer. The SBA Area Office dismissed Conrad Orange’s size protest. The SBA Area Office treated Conrad Shipyard’s “amendment” as a separate size protest, and dismissed it too, holding that it was untimely filed outside the five-day size protest window. Conrad Shipyard filed a size appeal with OHA. Conrad Shipyard alleged that it should have been permitted to correct a “minor, clerical error” by substituting Conrad Shipyard for Conrad Orange as the protester. Alternatively, Conrad Shipyard alleged that Conrad Orange was an interested party because “as a member of the same corporate family as [Conrad Shipyard], it has direct economic interest in the award to GIS.” OHA wrote that “[a] size protest against an awardee of a small business set aside contract may be filed by: any offeror the contracting officer has not eliminated from consideration for any procurement-related reason, the contracting officer, the SBA Area Director, and other interested parties.” A size protest filed by anyone other than the SBA or Contracting Officer “must be filed within five business days after the CO has notified the protestor of the identity of the apparent successful offeror.” Here, there was no dispute that the “amendment” filed by Conrad Orange was filed after expiration of the five-day period. Thus, if the SBA Area Office was correct to treat it as a separate protest, the amendment was untimely. Under the SBA’s size rules, OHA said, “protestors are not permitted to amend protests after the filing deadline.” Indeed, “[a]fter filing a protest, the regulation contemplates no further role for the protestor in the size determination process. It has no further submissions to make.” Otherwise, “new protest allegations could constantly be added up until issuance of the size determination.” Here, Conrad Shipyard’s “time for filing had expired, and the Area Office was not compelled to accept the October 11th filing as an amendment.” OHA then turned to Conrad Shipyard’s contention that Conrad Orange, as its wholly-owned subsidiary, was an interested party. OHA wrote that GAO has held in its bid protest cases that “a parent corporation has no standing to file a protest on behalf of a subsidiary, because it is not the parent who would be contracting with the Government.” OHA found the GAO’s reasoning persuasive. Here, “Appellant’s subsidiary attempted to file a protest on its behalf, but it was not the offeror on this procurement. Where a parent may not file for its subsidiary, a subsidiary surely may not file for its parent.” OHA denied the size appeal and affirmed the SBA Area Office’s decision. As I wrote in my post last week, in practice, parent and subsidiary companies often downplay or largely ignore the legal distinctions between them. But when it comes to the SBA size protest and appeals process, those distinctions are critical. As demonstrated in the Conrad Shipyard case, members of the same corporate family are not permitted to file size protests for one another. View the full article
  25. Love was in the air this week with Valentine’s Day falling on Wednesday. If all the chocolate and flowers distracted you from the latest and greatest in government contracting news, you’re in luck. It’s time for our weekly roundup, the SmallGovCon Week in Review. In today’s edition, a California father-and-son team pleaded guilty to using false financial statements and other lies in order to win more than $4 million in federal contracts, one commentator says the Department of Homeland Security must improve the quality of post-award debriefings, the GSA awarded its Alliant 2 small business small contract on Wednesday, and much more. A California father-and-son team pleads guilty to fraudulently obtaining more than $4 million in government contracts. [nbcsandiego.com] The GAO says that the DoD can improve its practices for developing acquisition program managers. [GAO] A new report says that a significant percentage of government contractors have experienced cybersecurity breaches. [Washington Technology] Speaking of cybersecurity, the DoD is warning contractors to better protect their networks, or risk losing contracts. [GovExec] One commentator says that DHS’ post-award debriefings are underwhelming, and offers ideas for improvements. [hstoday.us] The GSA has awarded the $15B Alliant 2 SB contract to 81 small businesses. [fedscoop.com] The DoD recently used Other Transaction Authority to make a $950 million award. But what the heck is Other Transaction Authority, anyway? [Federal News Radio] View the full article
×