PMCP SS Draft RFP Letter.pdf

UNITED STATES SPECIAL OPERATIONS COMMAND

7701 TAMPA POINT BOULEVARD

MACDILL AIR FORCE BASE, FLORIDA 33621-5323

SOF AT&L-KP 26-38

30 April 2026

Contracting Officer (USSOCOM-KP) Alicia Rasich 7701 Tampa Point Blvd MacDill AFB, FL 33621-5323

SUBJECT: Draft Request for Proposal (RFP) for H9240226RE003, Program Manager Counterproliferation (PMCP) Service Support Contract

PURPOSE

The purpose of this draft RFP is to provide prospective offerors with the opportunity to provide feedback on the upcoming solicitation for the subject competitive source selection. Formal proposals are not being requested at this time.

DISCLAIMER

This Draft RFP is issued solely for informational and planning purposes. It does not constitute a formal solicitation or a promise to issue a formal solicitation in the future. This Draft RFP does not commit the Government to contract for any supply or service whatsoever. Furthermore, the Government is not seeking proposals at this time and will not accept unsolicited proposals. Respondents are advised that the Government will not pay for any information or administrative costs incurred in response to this Draft RFP;

all costs associated with responding to this Draft RFP will be solely at the interested party's expense.

BACKGROUND

The Special Operations Forces Acquisition, Technology and Logistics (SOF AT&L) core mission is to provide rapid and focused acquisition, technology, and logistics support to SOF Warfighters. Under SOF AT&L, the Program Manager for Counterproliferation (PMCP) is chartered with the procurement, development, testing, training, fielding, and sustainment of technologies in support of Electronic Warfare (EW), advanced Counter Improvised Explosive Device (C-IED) operations and Explosive Ordnance Disposal (EOD) for improvised explosive device threats and Counter-Unmanned System (C-UxS) threats.

To accomplish this mission, PMCP relies on Contractor expertise across the full acquisition and fielding lifecycle, from requirements analysis and system development through sustainment and operations.

ATTACHMENTS FOR REVIEW

The following draft documents shall be provided for industry review upon request and verification:

• Attachment 1: PWS General Information, dated 28 April 2026

• Attachment 1a: PWS Appendix 1, dated 06 March 2026

• Attachment 1b: PWS Appendix 2, dated 06 March 2026

• Attachment 1c: PWS Appendix 3, dated 06 March 2026

• Attachment 2: DD Form 254

• Attachment 3: Pricing Matrix

• Attachment 4: Section L, dated 01 April 2026

• Attachment 4a: DCAA Pre-Award Survey of Prospective Contractor Accounting System Checklist

• Attachment 4b: Past Performance Relevancy Matrix

• Attachment 4c: Letter of Commitment

• Attachment 5: Section M, dated 01 April 2026

• Attachment 6: Past Performance Questionnaire (PPQ)

• Attachment 7: Quality Assurance Surveillance Plan (QASP)

CYBERSECURITY MATURITY MODEL CERTIFICATION (CMMC) 2.0 REQUIREMENTS

Offerors are hereby notified that this requirement will be governed by the Cybersecurity Maturity Model Certification (CMMC) 2.0 framework. In accordance with the recently published final rules, the formal solicitation and resulting contract will require compliance with CMMC 2.0. The offeror is required to be certified as CMMC Level 2 (Self) at proposal submission and CMMC Level 2 (Third Party Certification) within 12 months of award.

To ensure industry partners are adequately prepared for the formal solicitation, the anticipated clause language for DFARS 252.204-7021 and 252.204-7025 is provided at the end of this letter in full text.

INSTRUCTIONS FOR FEEDBACK

Interested industry partners are encouraged to submit a request, including company name and CAGE code to the below Points of Contact (POCs). This information will be used to verify in the System for Award management (SAM) and the Supplier Performance Risk System (SPRS) that the offeror can receive CUI documents. After successful verification, the documents will be provided for review and submission of questions, comments, or suggestions. We are particularly interested in feedback regarding the clarity of evaluation criteria, pricing structure, and feasibility of the past performance relevancy measures.

Please submit your feedback using the RFP Q&A Template provided with this RFP Letter to the POCs listed below no later than 1300 hours ET on 1 June 2026.

POINTS OF CONTACT

All communications regarding this Draft RFP must be directed to the following:

• Primary POC (Contract Specialist): Blake Martin, blake.j.martin.civ@socom.mil

• Secondary POC (Contracting Officer): Alicia Rasich, alicia.a.rasich.civ@socom.mil

We look forward to your valuable feedback.

Alicia Rasich Contracting Officer

SOF AT&L-KP

252.204-7021 Contractor Compliance With the Cybersecurity Maturity Model Certification Level Requirements.

As prescribed in 204.7504(a), use the following clause:

CONTRACTOR COMPLIANCE WITH THE CYBERSECURITY MATURITY MODEL CERTIFICATION LEVEL

REQUIREMENTS (NOV 2025)

(a) Definitions. As used in this clause—

“Controlled unclassified information” means information the Government creates or possesses, or information an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Governmentwide policy requires or permits an agency to handle using safeguarding or dissemination controls (32 CFR 2002.4(h)).

“Current” means—

(1) With regard to Conditional Cybersecurity Maturity Model Certification (CMMC) Status—

(i) Not older than 180 days for Conditional Level 2 (Self) assessments and Conditional Level 2 (certified third-party assessment organization (C3PAO)) assessments, with—

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Conditional CMMC Status date (see 32 CFR 170.16 and 170.17); and

(B) A corresponding affirmation of continuous compliance by an affirming official (see 32 CFR 170.4); and

(ii) Not older than 180 days for Conditional Level 3 (Defense Industrial Base Cybersecurity Assessment Center (DIBCAC)) assessments, with—

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Conditional CMMC Status date (see 32 CFR 170.18); and

(B) A corresponding affirmation of continuous compliance by an affirming official;

(2) With regard to Final CMMC Status—

(i) Not older than 1 year for Final Level 1 (Self), with—

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Final CMMC Status date (see 32 CFR 170.15); and

(B) A corresponding affirmation of continuous compliance, not older than 1 year, by an affirming official;

(ii) Not older than 3 years for Final Level 2 (Self) assessments and Final Level 2 (C3PAO) assessments, with—

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Final CMMC Status date (see 32 CFR 170.16 and 170.17); and

(B) A corresponding affirmation of continuous compliance, not older than 1 year, by an affirming official; and

(iii) Not older than 3 years for Final Level 3 (DIBCAC) assessments, with—

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Final CMMC Status date (see 32 CFR 170.18); and https://www.acquisition.gov/dfars/part-204-administrative-and-information-matters#DFARS_204.7504

(B) A corresponding affirmation of continuous compliance, not older than 1 year, by an affirming official; and

(3) With regard to affirmation of continuous compliance (32 CFR 170.22), not older than 1 year with no changes in compliance with the requirements at 32 CFR part 170.

“Cybersecurity Maturity Model Certification (CMMC) status” means the result of meeting or exceeding the minimum required score for the corresponding assessment. The potential statuses are as follows:

(1) Final Level 1 (Self).

(2) Conditional Level 2 (Self).

(3) Final Level 2 (Self).

(4) Conditional Level 2 (C3PAO).

(5) Final Level 2 (C3PAO).

(6) Conditional Level 3 (DIBCAC).

(7) Final Level 3 (DIBCAC).

“Cybersecurity Maturity Model Certification unique identifier (CMMC UID)” means 10 alpha-numeric characters assigned to each CMMC assessment and reflected in the Supplier Performance Risk System (SPRS) for each contractor information system.

“Federal contract information (FCI)” means information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government. It does not include information provided by the Government to the public, such as on public websites, or simple transactional information, such as information necessary to process payments.

“Plan of action and milestones” means a document that identifies tasks to be accomplished. It details resources required to accomplish the elements of the plan, any milestones in meeting the tasks, and scheduled completion dates for the milestones, as defined in National Institute of Standards and Technology Special Publication 800-115 (32 CFR 170.21).

(b) Framework. The Cybersecurity Maturity Model Certification (CMMC) is a framework for assessing a contractor’s compliance with applicable information security protections (see 32 CFR part 170).

(c) Duplication. The CMMC assessments will not duplicate efforts from any other comparable DoD assessment, except for rare circumstances when a reassessment may be necessary, for example, when there are indications of issues with cybersecurity and/or compliance with CMMC requirements.

(d) Requirements. The Contractor shall—

(1)(i) Have and maintain for the duration of the contract a current CMMC status at the following CMMC level, or higher: CMMC Level 2 (Self) for all information systems used in performance of the contract, task order, or delivery order that process, store, or transmit FCI or CUI; and

(ii) Consult 32 CFR 170.23 related to the flowdown of the CMMC requirements, and flow down the correct CMMC level to subcontracts and other contractual instruments;

(2) Only process, store, or transmit FCI or CUI on contractor information systems that have a CMMC status at the CMMC level requiredin paragraph (d)(1) of this clause, or higher;

(3) Complete on an annual basis, and maintain as current, an affirmation, by the affirming official (see 32 CFR 170.4), of continuous compliance with the requirements associated with the CMMC level required in paragraph (d)(1) of this clause in the Supplier Performance Risk System (SPRS) (https://piee.eb.mil) for each CMMC UID applicable to each of the contractor information systems that process, store, or transmit FCI or CUI and that are used in performance of the contract;

(4) Ensure all subcontractors and suppliers complete prior to subcontract award, and maintain on an annual basis, an affirmation, by the affirming official (see 32 CFR 170.4), of continuous compliance with the requirements associated with the CMMC level required for the subcontract or other contractual instrument for each of the subcontractor information systems that process, store, or transmit FCI or CUI and that are used in performance of the subcontract; and

(5) If the Contractor has a CMMC Status of Conditional, successfully close out a valid plan of action and milestones (32 CFR 170.21) to achieve a CMMC Status of Final.

(e) Reporting. The Contractor shall—

(1) Submit to the Contracting Officer—

(i) The CMMC UID(s) issued by SPRS for contractor information systems that will process, store, or transmit FCI or CUI during performance of the contract; and

(ii) Any changes in the CMMC UIDs generated in SPRS throughout the life of the contract, task order, or delivery order, if applicable;

(2)Enter into SPRS the results of a current self-assessment for each CMMC UID, not covered by a C3PAO assessment or DIBCAC assessment, applicable to each of the contractor information systems that process, store, or transmit FCI or CUI and that are used in performance of the contract; and

(3) Complete in SPRS on an annual basis and maintain as current an affirmation of continuous compliance by the affirming official (see 32 CFR 170.4) for each self-assessment, C3PAO assessment, or DIBCAC assessment required under the contract in SPRS.

(f) Subcontracts. The Contractor shall—

(1) Insert the substance of this clause, including this paragraph ( f) and excluding paragraph (e)(1), in subcontracts and other contractual instruments, including those for the acquisition of commercial products and commercial services, excluding commercially available off-the-shelf items , if the subcontract or other contractual instrument will contain a requirement to process, store, or transmit FCI or CUI; and

(2) Prior to awarding a subcontract or other contractual instrument, ensure that the subcontractor has a current CMMC certificate or current CMMC status at the CMMC level that is appropriate for the information that is being flowed down to the subcontractor based on the requirements at 32 CFR 170.23.

(End of clause)

252.204-7025 Notice of Cybersecurity Maturity Model Certification Level Requirements.

As prescribed in 204.7504(b), use the following provision:

NOTICE OF CYBERSECURITY MATURITY MODEL CERTIFICATION LEVEL REQUIREMENTS (NOV 2025)

(a) Definitions. As used in this provision, “controlled unclassified information (CUI),” “current,” “Cybersecurity Maturity Model Certification (CMMC) status,” “Cybersecurity Maturity Model Certification unique identifier (CMMC UID),” “Federal contract information (FCI)”, and “plan of action and milestones” have the meaning given in the Defense Federal Acquisition Regulation Supplement 252.204-7021, Contractor Compliance With the Cybersecurity Maturity Model Certification Level Requirements, clause of this solicitation.

(b)(1) Cybersecurity Maturity Model Certification (CMMC) level. The CMMC level required by this solicitation is: CMMC Level 2 (Self). This CMMC level, or higher (see 32 CFR part 170), is required prior to award for each contractor information system that will process, store, or transmit Federal contract information (FCI) or controlled unclassified information (CUI) during performance of the contract.

(2) The Offeror will not be eligible for award of a contract, task order, or delivery order resulting from this solicitation if the Offeror does not have, for each of the contractor information systems that will process, store, or transmit FCI or CUI and that will be used in performance of a contract resulting from this solicitation—

(i) The current CMMC status entered in the Supplier Performance Risk System (SPRS) (https://piee.eb.mil) at the CMMC level required by paragraph (b)(1) of this provision; and

(ii) A current affirmation of continuous compliance with the security requirements identified at 32 CFR part 170 in SPRS.

(c) Plan of action and milestones. If the Offeror has a CMMC Status of Conditional, the Offeror shall successfully close out a valid plan of action and milestones (32 CFR 170.21) to achieve a CMMC Status of Final.

(d) CMMC unique identifiers. The Offeror shall provide, in the proposal, the CMMC unique identifier(s) (CMMC UIDs) issued by SPRS for each contractor information system that will process, store, or transmit FCI or CUI during performance of a contract, task order, or delivery order resulting from this solicitation. The Offeror also shall update the list when new CMMC UIDs are generated in SPRS. The CMMC UIDs are provided in SPRS after the Offeror enters the results of self-assessment(s) for each such information system.

(End of provision) https://www.acquisition.gov/dfars/part-204-administrative-and-information-matters#DFARS_204.7504