Jump to content
The Wifcon Forums and Blogs

Lionel Hutz

Members
  • Posts

    107
  • Joined

  • Last visited

Recent Profile Visitors

3,059 profile views
  1. If you work for DoD, take a look at Force Health Protection Guidance (Supplement23) Revision 3, Attachment 8, 20 December 2021. It may be applicable to your situation.
  2. When deobligating funds and closing out a contract, unless the government is making a payment or waiving some contractual requirement as consideration for the release of claims, the government will have a hard time enforcing any release signed by the contractor. See, e.g., Supply & Service Team GmbH, ASBCA No. 59630 (March 1, 2017), ("Moreover, SST received nothing from the government from its agreement to sign these de-obligation modifications, which means that that they lacked consideration and they could not be deemed to be binding upon SST in any event.") I know that doesn't answer your question and you will have supervisors and policy memos that tell you to try to get a "bilateral" mod to deobligated funding. But, from an enforceability standpoint, they are both administrative actions/notifications by the government that are not binding on the contractor. It's just that in some cases you get the contractor to acknowledge that you have deobligated funding, and in other cases you don't.
  3. You've received good advice. I'll just add one more thing for application of this and other E.O.s in the future - make sure you are using and interpreting the correct terminology. You've asked whether contractors whose contract period of performance have expired are "still incumbents." Incumbent means, "holding an indicated position, role, office, etc., currently." This has led to your question. Is a company, whose contract period of performance has expired, considered an incumbent, i.e., current, contract holder? However, the word incumbent does not appear anywhere in the E.O. Rather, the order states, "When a service contract expires, and a follow-on contract is awarded for the same or similar services, the Federal Government’s procurement interests in economy and efficiency are best served when the successor contractor or subcontractor hires the predecessor’s employees, thus avoiding displacement of these employees." (Emphasis added.) It then directs inclusion of a clause in solicitations, contracts and subcontracts for services "that succeed a contract for performance of the same or similar work." In part, the clause requires the contractor to provide the contracting officer with a list of names of contractor employees working during the last month of contract performance. So, there is no requirement that there be uninterrupted service, only that the contracting officer determine that the contract is a follow-on for same or similar services. Barring guidance from the FAR Council or agency regulations, I would expect such a determination to be made on a case by case basis within the discretion of the contracting officer, subject to a protest that the determination is unreasonable. Also, keep in mind that unless the existing (or recently completed) contract has a clause requiring the contractor to provide a list of names, the government might not have a list of contractor employees to give to the successor contractor, and the existing contractor is under no obligation to provide the information.
  4. Two interesting (to me) points from the opinion: (1) While the court enjoined the vaccine mandate, the injunction stated that the OMB Determination and FAR Council Guidance likely complied with the APA and 41 U.S.C. § 1707, stating "Although the procedural path taken by the agencies was, at times, inartful and a bit clumsy, the Court finds based on the record before it that the Defendants likely followed the procedures required by statute." (2) The court found the EO exceeded the president's authority under the FPASA stating, "FPASA’s goal is to create an 'economical and efficient system for…procurement and supply.' Kahn, 618 F.2d at 788 (emphasis added). While the statute grants to the president great discretion, it strains credulity that Congress intended the FPASA, a procurement statute, to be the basis for promulgating a public health measure such as mandatory vaccination." It also states, "neither OSHA nor the executive branch is permitted to exercise statutory authority it does not have.... In this case, the FPASA was enacted to promote an economical and efficient procurement system, and the Defendants cannot point to a single instance when the statute has been used to promulgate such a wide and sweeping public health regulation as mandatory vaccination for all federal contractors and subcontractors." In other words, FPASA is a statute aimed at promoting economical and efficient procurement system, and the E.O.'s vaccine mandate is a "public health regulation" that exceeds the scope and purpose of the statute. However, later in the opinion, the court rejected the plaintiff's argument that improving procurement efficiency was pretextual and stated, "the subsequent OMB Determination provided ample support for the premise that a vaccine mandate will improve procurement efficiency." Putting these two points together, the Court seems to be saying that the the government has offered ample support that a vaccine mandate will improve procurement efficiency (which meets the intent and scope of FPASA) and that the government likely followed the administrative procedures required by statute to implement the mandate. However, because the mandate ALSO involves implementing public health measures, the mandate exceeds the government's authority under the FPASA. I think the Court's statement that "Defendants cannot point to a single instance when [FPASA] has been used to promulgate such a wide and sweeping public health regulation as mandatory vaccination for all federal contractors and subcontractors," is a red herring. FPASA was passed in 1949. How many global pandemics have we faced since that time? The lack of examples has less to do with the scope and authority of FPASA and more to do with the lack of a public health emergency that could even rise to the level of potentially impacting procurement efficiency. I make no prediction as to the final outcome. But I am interested to see if an appellate court will find that an E.O. issued under and facially compliant with FPASA exceeds the scope of FPASA because it also involves matters of public health.
  5. In addition, the Safer Federal Workforce Task Force guidance specifically calls out Cooperative Agreements as being included. It defines contract and contract-like instruments to include (among other instruments): https://www.saferfederalworkforce.gov/downloads/Draft contractor guidance doc_20210922.pdf
  6. "You miss 100% of the shots you don't take. - Wayne Gretsky" - Michael Scott
  7. FAR 2.101 defines multiple award contract as follows: Multiple-award contract means a contract that is— (1) A Multiple Award Schedule contract issued by GSA (e.g., GSA Schedule Contract) or agencies granted Multiple Award Schedule contract authority by GSA (e.g., Department of Veterans Affairs) as described in FAR part 38; (2) A multiple-award task-order or delivery-order contract issued in accordance with FAR subpart 16.5, including Governmentwide acquisition contracts; or (3) Any other indefinite-delivery, indefinite-quantity contract entered into with two or more sources pursuant to the same solicitation. I do not think it answers the question, but it is interesting that paragraph (3) calls out a contract [not contracts] with two or more sources. Is the "Any other" language from paragraph (3) meant to imply that the FAR 16 contracts referenced paragraph (2) are also a single contracts? i.e., a Multiple-award contract is a single contract with multiple sources and the distinction is whether it is awarded under subpart 16.5 or any other authority. Or, is "Any other" meant to distinguish between multiple contracts awarded under 16.5 (in accordance with the language cited by Joel), and single contracts with multiple sources under other authority? I could see an argument either way. In either case, it seems a single contract with multiple sources is contemplated by the FAR. (Edit: I apologize. I am re-reading this and I did not articulate my thoughts very well. But it is Friday evening, and I'm too tired to rewrite it. Oh well.)
  8. I know the initial question was about issuing 2 RFPs vs 1, but I recommend consulting legal counsel regarding the plan to ask offerors to submit proposals granting different levels of data rights. 10 U.S.C. § 2320 - Rights in technical data, paragraph (a)(2)(H), prohibits the government from requiring a contactor to relinquish rights in technical data as a condition for award of a contract. (And welcome back Vern!)
  9. Also see 5 CFR § 2635.702, which states in part: The government can recognize a contractor through a formal past performance evaluation and it is up to the contractor to recognize its own employees.
  10. Freyr, to follow up on what Joel and Ji said, check out FAR 36.207, which describes "unit-price" contracts as a type of fixed-price contract. It is in the context of construction contracting, but there is no reason it cannot also be used for supplies or services.
  11. I agree that "Law Clerk" is usually reserved for a law school graduate that assists a Judge (usually) or Attorney (less often). "Legal Assistant," or "Paralegal" refers to someone that is qualified to perform substantive legal work under the supervision of an attorney. Per the American Bar Association: Also this from the ABA:
  12. There is more to life than acquisition regulations. Again, you have to take a look at the rules of professional responsibility for the state you are located. What you consider to be "true legal support" is irrelevant. As an example, see the "Unauthorized Practice Rules" in the Virginia Rules of Professional Conduct (https://www.vsb.org/pro-guidelines/index.php/unauthorized-practice-rules/) They state in part: I'm not telling you your legal clerk is practicing law, but research (especially if the clerk is applying that research to a specific scenario) and editing and redlining contracts/agreements may come close depending on the exact nature of the work performed and the definition of legal work in your state. This is one of those cases where you shouldn't try to have your cake and eat it too. Either, the law student is doing "legal work" (i.e., practicing law) in which case s/he should be supervised by an attorney and may be called a legal/law clerk. Or, the law student is providing administrative and business support, in which case call them an Acquisition Clerk or Business Intern or something along those lines. Calling the law student a legal clerk, but arguing the law student does not do "legal work" seems like a needlessly confusing arrangement.
  13. Probably a good research project for your Legal Clerk. In my opinion, the issue is less about what the position is called, and more about what the law student is doing. Specifically, the law student should not engage in anything that could be construed as the practice of law unless they are being supervised by an attorney or have some other exception. A law student may provide legal advice under the supervision of an attorney because the attorney essentially accepts responsibility for the law student’s work product. A law student providing legal advice on his/her own is most likely practicing law without a license. Look to your state bar association for rules on what constitutes the practice of law in your jurisdiction as well as the limits of what a law student or paralegal is permitted to do.
  14. Bob, thanks. I must have just read the case in the past 6 months and for some reason it got stuck in my head as being newer.
×
×
  • Create New...