Att 3 - CSP Template_30 Apr 2026.pdf

FA8652-26-S-C003

AFRL Enterprise CSO

Attachment 3

COMMERCIAL SOLUTIONS PROPOSAL (CSP) TEMPLATE

CONTENTS: COVER SHEET, TECHNICAL PROPOSAL, PRICE PROPOSAL, STATEMENT OF

WORK, AND ADDITIONAL DOCUMENTATION

1. Cover Sheet: The following information shall be contained in a stand-alone cover sheet:

a. Commercial Solutions Opening (CSO) number and Spiral number and title

b. Full company name and address

c. CAGE code

d. Unique Entity ID number

e. Business Size Classification and socioeconomic status

f. Point of contact, name, title, phone number, and email address

2. Technical Proposal:

a. The Technical Proposal shall describe the background and objectives of the proposed work, the approach, deliverables, the resources needed to execute, and data rights assertions. Include the nature and extent of the capability and how it addresses the Spiral Area of Interest (AOI), the innovative aspect of the solution, the intended results, and address possible integration or testing needs. Include ancillary and operational considerations such as certifications, algorithms, and any engineering/software development methodologies to be used. Provide a graphic display of major program milestones. Measurable milestones shall capture key activity points and shall clearly articulate milestone completion dates relative to the start of the effort.

b. Offerors seeking an Other Transactions for Prototype (OTP) shall refer to the AFRL

Enterprise CSO, Section 11 “Additional Compliance Criteria for 10 USC 4022 OTPs,” and address the elements therein.

c. Government Support Required: Identify the type of support, if any, the Offeror requests of the Government, such as facilities, equipment, data, and information or materials.

d. The issuing Mission Organization reserves the right to ask for additional technical information. Refer to the Spiral, or Step-Two Request for CSP, instructions for deviations from this template.

e. Due to the varying AOIs and potential solutions, Technical Proposal page limitations and formatting requirements will be identified in Spiral or Request for CSP.

3. Statement of Work (SOW):

a. The SOW shall be a separate and distinct document suitable for incorporation into the contract or OTP. Pages shall be numbered, and the initial page shall identify the document date beneath the title. DO NOT INCLUDE PROPRIETARY INFORMATION

IN THE SOW.

b. The proposed SOW shall accurately describe the work to be performed. The SOW shall\contain a summary description of the technical methodology as well as the task descriptions, but not in so much detail as to make the SOW inflexible. The SOW shall include the following sections:

1. OBJECTIVE: This section is intended to provide a brief overview of the project, rationale for why the work is being pursued and identify the overall objective(s) the offeror intends to accomplish.

2. SCOPE: This section describes the AOI to be investigated, goals, and milestones for the effort. Include a graphic display of major program milestones.

3. BACKGROUND: This section includes any information, explanations, or constraints to provide context for the project tasks and requirements. This section shall describe the relationship with previous and/or ongoing efforts, as applicable.

4. TASKS AND TECHNICAL REQUIREMENTS: This section provides a detailed description of the tasks necessary to perform the proposed work. These tasks will represent the work to be performed on any potential contract or OTP award and thus shall be considered contractually binding. This section shall be developed in an orderly progression, presented in sufficient detail to establish the feasibility of accomplishing the overall program goals. Note: The Government reserves the right to modify and negotiate the language in the SOW prior to any potential contract or OTP award.

4.1. Task descriptions shall be definite, realistic, and clearly stated. Use the phrase “the contractor/performer shall” whenever the work statement expresses a provision that is binding. Use “should” or “may” whenever it is necessary to express a declaration of purpose. Use “will” in cases where no offeror requirement is involved (e.g., power will be supplied by the Government).

4.2. Do not use acronyms or abbreviations without first defining them.

c. Due to the varying AOIs and potential solutions, the Spiral, or Request for CSP, instructions will specify SOW page limitations.

4. Price Proposal: The following describes the Price Proposal requirements:

a. The Price proposal shall include pricing information sufficiently detailed for meaningful evaluation of the proposal. The Price Proposal does not have a page limit restriction.

b. Proposed solutions are considered commercial items, technologies, or services;

therefore, the requirements of the Truthful Cost or Pricing Data Act are not applicable. However, other than certified cost or pricing data may be requested if the Contracting/Agreements Officer determines additional information is necessary to support a determination of a fair and reasonable price.

c. The responsibility for providing adequate supporting data and attachments lies solely with the offeror. Further, the offeror shall also bear the burden of proof in establishing reasonableness of proposed prices; therefore, it is in the offeror’s best interest to submit a fully supportable and well-prepared price proposal.

d. The Offeror shall provide an electronic version of the pricing model in a Microsoft (MS) Excel editable format. The electronic pricing model shall include active formulas demonstrating the mathematical calculation of the proposed price.

5. Additional Proposal Submission Content: Provide the following stand-alone documents files, as applicable. These documents do not affect, or add to, the page limits of the Technical Proposal, SOW, or Price Proposal.

a. Small Business Subcontracting Plan: Large business offerors shall submit either an individual subcontracting plan and/or master subcontracting plan (as applicable) in accordance with RFO 52.219-9, Small Business Subcontracting Plan, DFARS 252.219-7996, Small Business Subcontracting Plan (DoD Contracts) – Basic (DEVIATION 2026-O0037), and DFARS 252.219-7997, Small Business Subcontracting Plan (Test Program) (DEVIATION 2026-O0037), with their proposal.

If the Small Business Subcontracting Plan is not initially acceptable, the Contracting Officer may request additional information regarding the Small Business Subcontracting Plan.

b. Science and Technology Protection (S&TP). Refer to Section 11 of the AFRL Enterprise CSO. The offeror shall complete and submit S&TP Appendices 2-4 as part of its proposal.

c. DD Form 2345, Militarily Critical Technical Data Agreement. Refer to Section 11 of the AFRL Enterprise CSO. The offeror shall submit the approved DD Form 2345 as part of its proposal.

d. Organizational Conflict of Interest: The offeror shall perform an Organizational Conflict of Interest (OCI) analysis and submit the results of that analysis as part of its proposal. Specifically, the offeror shall analyze the planned acquisition for actual or potential OCI situations associated with the performance of the offeror, its proposed teammate(s), or subcontractor(s) under any contract or OTP that the offeror/teammate(s)/subcontractor(s)has been, or may be, awarded by any other federal agency. The offeror shall describe the methodology used to identify actual or potential OCI issues. If the offeror identifies any actual or potential OCIs, it shall also provide an OCI Mitigation Plan which will be incorporated as an attachment to any resulting contract or OTP. Any proposed avoidance or mitigation techniques shall be consistent with R-FAR 9.5 and the most recent decisions of the Government Accountability Office (GAO) and the U.S. Court of Federal Claims.

e. Responsibility: The offeror shall provide information that presents a brief verifiable self-assessment of the areas of responsibility described in R-FAR 9.104 and as supplemented by the DFARS.

f. Data Rights: Identify any assertions related to restriction, use, release, or disclosure of data and/or computer software and computer software documentation that will be delivered to the Government in the course of contract or OTP performance.

Utilize the format at DFARS 252.227-7992, Identification and Assertion of Use, Release, or Disclosure Restrictions (DEVIATION 2026-O0036). Rules governing these assertions are prescribed in DFARS clauses 252.227-7989, -7990, and -7992 and may be accessed at and https://www.acq.osd.mil/dpap/dars/dfars_far_overhaul_class_deviations.html.

https://www.acq.osd.mil/dpap/dars/dfars_far_overhaul_class_deviations.html