Do I qualify to be an OASIS+ vendor?

The Offeror may submit a maximum of five distinct QPs for each Domain. QPs may be either Relevant or Non-Relevant QPs as defined in Section L.5.2.1 (download the solicitation).

To be considered a QP, each submitted project must meet all of the following minimum criteria:

1. Be classified as one of the following:

• A single contract - including prime contracts, subcontracts, and commercial contracts; or
• A single task order awarded under an indefinite delivery task order contract (Definite Quantity, Requirements, or Indefinite Quantity), Blanket Purchase Agreement (BPA), or Basic Ordering Agreement (BOA), including single or multiple award; or
• A task order under a Federal Supply Schedule contract (FAR 8.405-2) or BPA (FAR 8.405-3); or
• An Other Transaction Authority (OTA) award issued under 10 U.S.C. 4021 or other applicable authority; or
• A “Collection of Task Orders” as defined in Section L.5.2.1.
  • i. Offerors are limited to the submission of one “Collection of Task Orders” per Domain submission. 

2. Be a contract or order for services as defined in FAR part 37;

3. Meet or exceed a minimum Average Annual Value (AAV) (as defined below) specified within OASIS+ Domain Qualifications Matrix and Scorecards (see Attachment J.P-1 in the solicitation posted to SAM.gov), for each proposed Domain;

• Qualifying Projects submitted in the name of the protégé must only meet or exceed 50 percent of the minimum AAV specified within Attachment J.P-1. This applies to relevant and non-relevant QPs. This reduced threshold does not apply to projects submitted in the name of the offering Mentor Protege-Joint Venture (MP-JV) entity itself.

4. Be ongoing (with at least six months of completed performance from the Request for Proposal (RFP) closing date) or completed within five years before June 15, 2023. There is no minimum period of performance for completed projects; and

5. Cannot have an associated record of negative past performance (e.g. on a 5 point scale, average of scores <3.0).

To be considered a FEP, each submitted project must meet all of the following minimum criteria:

1. Be a prime award for a contract, grant, cooperative agreement, or other transaction between the Offeror (or joint venture member/proposed Small Business (SB) subcontractor) and the Federal Government. Note: grants and cooperative agreements are only allowable under Section L.5.3.4.

2. Be any of the following:

• A single contract; or
• A single task order awarded under an indefinite delivery task order contract (Definite Quantity, Requirements, or Indefinite Quantity), BPA, or BOA, including single or multiple award; or
• A task order under a Federal Supply Schedule contract (FAR 8.405-2) or BPA (FAR 8.405-3); or
• An Other Transaction Authority (OTA) award issued under 10 U.S.C. 4021 or other applicable authority; or
• A single contract, grant, or cooperative agreement under the SB Innovation Research (SBIR) or SB Technology Transfer (STTR) program. (Only allowable under Section L.5.3.4)

3. Meet or exceed a minimum AAV of $250K.

• FEPs submitted in the name of the protégé must only meet or exceed a minimum AAV of $125K. This reduced threshold does not apply to projects submitted in the name of the offering MP-JV entity itself.

4. Be ongoing (with at least six months of completed performance from the RFP closing date) or completed within five years before June 15, 2023. There is no minimum period of performance for completed projects; and

5. Be a contract or order for services as defined in FAR part 37.

FEPs are not mandatory, but do help to receive additional credits for qualifying projects as addressed in the Domain Qualification Matrix. In addition to the QPs submitted under Section L.5.2.2, the Offeror may submit additional FEPs to demonstrate experience. The quantity of allowable FEPs varies on a Domain-by-Domain basis and can be found in Attachment J.P-1 within each Domain Qualifications Matrix.

Relevance has the greatest opportunity for credits, demonstrating you’ve performed work in the domain. It can be determined Automatically Relevant through NAICS/PSC.

The Offeror may submit a QP for automatic relevance consideration. To be considered, the QP must have an assigned PSC or project-specific NAICS code that matches one of the codes in Attachment J.P-4, OASIS+ Domains Auto-Relevant NAICS Codes and PSCs, for the proposed Domain(s). If a project qualifies for automatic relevance consideration under this criteria, the Offeror must submit the FPDS report and/or contract award document indicating the PSC or project-specific NAICS Code. Non-federal projects, including federal subcontracts, are ineligible for automatic relevance consideration and must be verified using Standard Relevance Verification at Section L.5.2.3.1.2.

If the QP is a task order issued under a MA-IDIQ where multiple NAICS Codes are allowable at the order level (e.g., OASIS, MAS, HCaTS, BMO, GSA GWACs), the NAICS code assigned to the IDIQ that automatically applies to all task orders in FPDS is not eligible to automatically validate the order-level NAICS code. For these task orders, Offerors must submit one of the following types of supporting documentation:

• FPDS report and/or contract award document indicating the task order PSC, which is designated in FPDS at the order level;
• Task Order Solicitation identifying the claimed NAICS code; or
• Supporting documentation that all potential NAICS Codes assigned to the MA-IDIQ are considered automatically relevant for that Domain; or
• Standard Relevance Verification documentation at Section L.5.2.3.1.2

For example:
For a task order issued under legacy OASIS Pool 1, the FPDS report for the task order would contain NAICS Code 541330, because that was the Primary NAICS Code assigned to OASIS Pool 1, and all Master Contracts awarded under Pool 1. Therefore, all task orders awarded under the OASIS Pool 1 contracts reflect NAICS Code 541330 in FPDS. However, the OCO will have selected and assigned the PSC to the order in FPDS that best identifies the service procured. For instance, the PSC reported for this OASIS Pool 1 task order in FPDS is R706 Support - Management: Logistics Support, which is related to NAICS Code 541614 Process, Physical Distribution, and Logistics Consulting Services, which is also included in legacy OASIS Pool 1. Although the FPDS report would reflect NAICS Code 541330, this task with PSC R706 would be considered automatically relevant for the Logistics Domain under OASIS+, per the list of Auto-Relevant NAICS Codes and PSCs for that Domain in Attachment J.P-4.

Relevant work does not need to be the primary purpose of the project, but the Offeror must clearly demonstrate (e.g., via a distinct CLIN or section within a PWS) that the relevant portion of the work meets the minimum QP criteria for the proposed Domain (e.g., ≥ $500K average annual value for Technical and Engineering Domain). The average annual value of relevant work is not entered into the OSP, but the offeror shall identify within the submitted documentation that the relevant work meets or exceeds the average annual value for the proposed domain. 

In accordance with Subsection L.5.1.7.1 and L.5.1.7.2, the Offeror shall provide contract documentation, which may include the Award Form or SOW/PWS/SOO that describes the general scope, nature, complexity, and purpose of the services the customer acquired under the contract. Additionally, the Offeror must tag those specific written passages in the contract documentation that support a relevance determination in the proposed Domain(s) in accordance with the scope of each Domain outlined in Section C.2. 

If contract documentation alone cannot demonstrate relevance, Offerors may submit the Project Verification Form (either from the OSP or Attachment J.P-3) to demonstrate relevance and include a narrative statement clearly explaining how the project is relevant to each proposed Domain where relevance is claimed (not to exceed 1,000 characters, including spaces, per Domain). The Offeror must also include the QP minimum average annual dollar value for each proposed Domain (e.g., $500K average annual value, see Attachment J.P-1) and the dollar value of the relevant work for each proposed Domain, which must be validated and signed by a CO with cognizance over the submitted project. If the cognizant CO’s signature is unattainable, the Government will accept the signature of the COR or other Government Employee with cognizance over the submitted project. The Project Verification Form must include both cognizant CO’s and verifying Government Employee’s direct telephone numbers and email addresses.