Att 3 - CSP Template_DRAFT.pdf

FA8652-26-S-C003

AFRL Enterprise CSO

Attachment 3

COMMERCIAL SOLUTIONS PROPOSAL (CSP) TEMPLATE 1

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

WORK, AND ADDITIONAL DOCUMENTATION 4

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

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

b. Full company name and address 8

c. CAGE code 9

d. Unique Entity ID number 10

e. Business Size Classification and socioeconomic status 11

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

2. Technical Proposal: 14

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

b. Offerors seeking an Other Transactions for Prototype (OTP) shall refer to Section 11 26 of the AFRL Enterprise CSO for additional criteria for 10 USC 4022 OTP and address 27 the elements therein. 28

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

d. The issuing Technical Directorate reserves the right to ask for additional technical 34 information. Refer to the Spiral, or Step-Two Request for CSP, instructions for 35 deviations from this template. 36

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

3. Statement of Work (SOW): 41

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

IN THE SOW. 45

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

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

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

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

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

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

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

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

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

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

b. Proposed solutions are considered commercial items, technologies, or services; 89 therefore, the requirements of the Truthful Cost or Pricing Data Act are not 90 applicable. However, other than certified cost or pricing data may be requested if 91 the Contracting/Agreements Officer determines additional information is necessary 92 to support a determination of a fair and reasonable price. 93

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

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

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

a. Small Business Subcontracting Plan: Large business offerors shall submit either an 107 individual subcontracting plan and/or master subcontracting plan (as applicable) in 108 accordance with FAR 52.219-9, Small Business Subcontracting Plan, DFARS 109 252.219-7996, Small Business Subcontracting Plan (DoD Contracts) – Basic 110 (DEVIATION 2026-O0037), and DFARS 252.219-7997, Small Business 111 Subcontracting Plan (Test Program) (DEVIATION 2026-O0037), with their proposal. 112 If the Small Business Subcontracting Plan is not initially acceptable, the 113 Contracting Officer may request additional information regarding the Small 114 Business Subcontracting Plan. 115

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

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

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

e. Data Rights: Identify any assertions related to restriction, use, release, or disclosure 138 of data and/or computer software and computer software documentation that will 139 be delivered to the Government in the course of contract or OTP performance. 140 Utilize the format at DFARS 252.227-7992 (DEVIATION 2026-O0036). Rules 141 governing these assertions are prescribed in DFARS clauses 252.227-7989, -7990, 142 and -7992 and may be accessed at www.acquisition.gov and 143 https://www.acq.osd.mil/dpap/dars/dfars_far_overhaul_class_deviations.html. 144 http://www.acquisition.gov/ https://www.acq.osd.mil/dpap/dars/dfars_far_overhaul_class_deviations.html