GSA Alliant 2: Focus now on Product Service Codes (PSCs)

GSA Alliant 2 and Alliant 2 SB will be released on or about June 20 with a 60-day turn. GSA announced via GSA Interact that vendors should be cautious about relying on the draft since the final RFP will contain major changes. However, there is one area you can work hard right now: Product Service Codes (PSCs).

Pesky PSCs encompass 40 percent of the available evaluation points. Bidders must prove that they have up to seven distinct projects across three PSC groups to gain maximum points. How do bidders prove the PSC code? The draft RFP requires that bidders submit the most recent Federal Procurement Data System-Next Generation (FPDS-NG) report identifying the PSC code.

Your first step is to search on FPDS-NG for the relevant experience projects you plan to use in your proposal. What should you do if the PSC code you want to claim is not reflected in the FPDS-NG report or if there is no report?

Your only option is to contact the Contracting Officer (CO) or Contracting Officer’s Representative (COR) to sign the Relevant Experience PSC Group Project Template identifying the revised or missing PSC. While you cannot use the draft template and must wait for the final, you can contact your CO or COR now to determine if they will be willing to sign this template once the final RFP is released.

Remember, while 60 days to respond may seem like a long time, the days will fly by while you research your FPDS-NG reports, contact contracting officials, and gather all of the required contract documentation required to back up your claims. Begin your research today so you are prepared when GSA releases the final RFPs.