CNECTS CSO Draft_3-27-2026.pdf

[Type here]

Commercial Solutions Opening (CSO)

FA2518-26-S-CNECTS

Combat Forces Command (CFC) Communications, Network, Engineering, Cybersecurity, and Information Technology Services

(CNECTS, aka “Connects”) Space Acquisition & Integration Office (SAIO)

Record of Revision

Revision Description Date

1. DEFINITIONS

2. GENERAL INFORMATION

3. GOVERNANCE FRAMEWORK AND OPERATIONAL GUIDANCE

4. CSO APPROACH

5. SUBMISSION INFORMATION

6. ADDITIONAL INFORMATION

7. ATTACHMENT 1: PHASE I POWERPOINT BRIEFING & QUAD CHART FORMAT

8. ATTACHMENT 2: PHASE I WHITE PAPER FORMAT

9. ATTACHMENT 3: PHASE II PITCH SESSION FORMAT

10. ATTACHMENT 4: PHASE III TECHNICAL PROPOSAL & PWS FORMAT

11. ATTACHMENT 5: PHASE III PRICE PROPOSAL FORMAT

12. ATTACHMENT 6: EVALUATION AND SELECTION PROCESS

13. ATTACHMENT 7 – AREAS OF INTEREST (AOIS)

1. DEFINITIONS

• Area of Interest (AOI): A specific announcement posted under this CSO seeking innovative commercial solutions aligned to mission needs, which may result in the award of a commercial contract. AOIs may be issued at any time during the CSO period of availability. Closed AOIs will be issued under this CSO to request submission of solution briefs, pitches, and/or proposals. Also, it may include specific terms that apply to that AOI.

• Commercial Solutions Opening (CSO): A competitive, closed solicitation method used by United States Space Force (USSF), Combat Forces Command and executed by the USSF CFC SAIO to identify innovative technologies that support defense objectives.

• Innovative: Any new technology, process, or business practice—or novel application of an existing one—that enhances military effectiveness and supports U.S. national security.

• Small Business: A business that meets the size standards and criteria set forth in 13 C.F.R. § 121 and 15 U.S.C. § 632.

2. GENERAL INFORMATION

2.1 INTRODUCTION and BACKGROUND

2.1.1 As the USSF continues to reorganize, it has identified significant inefficiencies in managing four disparate but related IT support contracts. These contracts are managed by separate organizations, with multiple contracting officers and CORs, creating operational seams, redundant efforts, and barriers to enterprise-wide visibility. Strategic reallocation of the government's financial and intellectual resources will drive efficiencies in IT infrastructure, which is foundational to building future mission resilience, security, and capacity.

This CSO focuses on streamlining these efforts under the 21st CS to create a unified, agile, and secure digital ecosystem. The goal is to move from a reactive, siloed support model to a proactive, integrated, and data-driven enterprise service delivery framework.

2.1.2 The 21st Communications Squadron (21st CS) is releasing this Commercial Solutions Opening (CSO) to solicit innovative commercial solutions for the newly consolidated CNECTS acquisition in accordance with DFARS 212.70, Defense Commercial Solutions Opening. This initiative seeks to modernize and streamline the information technology services currently provided under four separate contracts:

2.1.2.1 Base Operating Support-Information Technology (BSO-IT), FA2517-24-F-0034

2.1.2.2 Cheyenne Mountain SFS 21 CS Communications Contract, FA8723-25-R-0007

2.1.2.3 Wing Information & Communications Support (WICS), FA2550-21-C-0005

2.1.2.4 Plans and Programs Engineering Design Support (PEDS), FA2550-22-C-0003

2.1.3 Under this CSO, all products, technologies, and services shall be treated as commercial items; products, technologies and services do not have to be “commercially available” to be submitted in response to this solicitation. The solution is treated as commercial whereby the Contracting Officer will utilize commercial procedures to develop and execute the resultant award.

2.1.4 NAICS for this CSO is 517810: All Other Telecommunications. It fully encompasses the specialized telecommunications services at the core of the CNECTS efforts. The small business size standard for this NAICS is $40.0 million.

2.2 KEY INFORMATION SUMMARY:

2.2.1 Acquisition is a Closed CSO-with Closed AOI(s).

2.2.2 Estimated Funding: TBD

2.2.3 Contract Type: Fixed Price (FAR-based) contract structure; other fixed price types may be considered to balance risk between government and contractor.

2.2.4 Set-Aside: This is a 100% set aside for 8(a) small businesses. Teaming arrangements are authorized with a 8(a) small business as the prime contractor.

2.2.5 Period: TBD

2.2.6 Security: Phase I submissions shall be Unclassified. Subsequent phases may require submission and/or performance at higher classification levels, as specified in the AOI and any draft or final DD Form 254.

3. GOVERNANCE FRAMEWORK AND OPERATIONAL GUIDANCE

3.1 GOVERNANCE FRAMEWORK

3.1.1 This Commercial Solutions Opening (CSO) is acquisition mechanism under the authority of the Space Acquisition and Integration Office (SAIO) and administered by the designated CSO Contracting Officer (CO) in support of 21st Communications Squadron.

3.2 OPERATIONAL GOVERNANCE GUIDANCE

• The following requirements apply to all AOIs published under this CSO:

3.2.1 AOI DEVELOPMENT & APPROVAL

3.2.1.1 All AOIs will clearly describe the technical problem, desired outcomes, and any constraints specific to the requirement.

3.2.1.2 AOIs shall use the format in Attachment 7 – AOI Template.

3.2.2 AOI PUBLICATION

3.2.2.1 Approved AOIs will be posted on SAM.gov.

3.2.2.2 Each AOI must include submission and evaluation instructions tailored to its scope.

3.2.3 EVALUATION & AWARD

3.2.3.1 Evaluations will follow the process in Attachment 6 – Evaluation Process.

3.2.3.2 CO will be responsible for conducting all evaluation phases and documenting results in accordance with federal acquisition regulations.

3.2.3.3 The Government reserves the right to award all, some, or none of the proposed solutions.

3.2.3.4 CO must apply the evaluation phases and factors described in Section 8 and ensure results are documented in accordance with established standards.

3.2.4 COMPLIANCE & RECORDS

3.2.4.1 Award will be made using a FAR-based contract.

3.2.4.2 CSO and AOI records will be maintained in accordance with USSF and DoD records management policies.

4. CSO APPROACH

4.1 APPLICABILITY

4.1.1 This CSO seeks innovative solutions to address 21st Communication Squadron mission challenges through advanced software engineering. The Government encourages a broad range of technical and business approaches aligned with the specific Areas of Interest (AOIs). Each AOI must describe the broad strategic scoped required and/or challenge aligned with mission priorities. All submissions in response to any AOI will be governed by this CSO.

4.1.2 Awards made under this CSO shall be fixed-price type, FAR-based contracts. The small business set-aside status determination for 100% 8(a) was approved on 11 November 2025.

Each AOI will be limited to 8(a) small business. The Government reserves the right to award any combination of proposals offering the best overall value. Contract type and pricing structure may vary as appropriate to each AOI’s requirements and available funding.

4.1.3 Proposals submitted under this CSO will be evaluated using a multi-phase process, as described in Attachment 6. The Government may fund all, some, or none of the proposals received and may fund only specific parts of the proposed solution. CO will adhere to s must apply the evaluation phases and factors described in Section 8 – Evaluation Framework and ensure results are documented in accordance with established standards.

4.1.4 The Government may choose to fund all or a portion of a proposed solution, based on mission efficacy and expected return on investment.

4.1.5 All formal communication between the Government and Offerors will occur via www.sam.gov. Industry engagement may also include virtual/oral pitch sessions or written clarifications, as determined by the evaluation phase.

4.1.6 Phase I submissions shall be Unclassified. Subsequent phases may require submission and/or performance at higher classification levels, as specified in the final AOI.

5. SUBMISSION INFORMATION

5.1 SUBMISSION OVERVIEW:

5.1.1 This CSO will be closed with an expiration date of 1 December 2026 from posting. It will be open for Phase I submissions in accordance with the AOIs outlined in Attachment 7. The acceptance date for Phase I submissions will be identified in the AOI(s).

5.1.2 The Government will amend the CSO to incorporate additional AOIs as needed. AOIs may be published by the CO following the governance and approval process in Section 4.

5.1.3 The Government will not reimburse companies for costs associated with submission for any phase.

5.1.4 Submissions for all phases shall be sent to the Contracting Team’s point(s) of contact listed in the AOI(s). All submissions shall follow this filename format:

5.1.4.1 Phase I: [AOI#]Phase[#][Document Type][CompanyName][YYYYMMDD]

5.1.4.2 Example: AOI2025_01_PhaseI_WhitePaper_ABC_Corp_Inc_20251015.pdf

5.1.4.3 Maximum filename length: 50 characters

5.2 RECEIPT CONFIRMATION:

5.2.1 To ensure submissions have been received by the Government, Offerors shall send a separate email (not containing attachments) to the Contracting Team’s point(s) of contact listed in the AOI immediately after emailing a submission. Hardcopies for any phase will not be accepted.

5.3 PROPRIETARY INFORMATION:

5.3.1 Offerors shall mark each page of submissions that contains proprietary information.

Offerors may assert restrictions on the use, release, or disclosure of data/software provided during contract performance in accordance with DFARS 252.227-7013, 7014, and 7017 (available at www.acquisition.gov).

5.3.2 To protect the proprietary interests of all parties, the Government has established a specific process for submitting sensitive data when teaming.

5.3.2.1 Direct Submission to Government: If a subcontractor or teaming partner does not wish to share proprietary information (e.g., detailed cost breakdowns, trade secrets, proprietary technical approach) with their prime contractor, they must submit that information directly to the Contracting Officer. Do not include it in the package you provide to your prime.

5.3.2.2 Inform Your Prime: After submitting your proprietary data to the CO, you must notify your prime contractor in writing (e.g., via email) that you have completed the direct submission. This confirms to the prime that their proposal submission is complete.

5.3.2.3 Proper Marking is Essential: Please follow the instructions noted under paragraph 5.3.1.

http://www.acquisition.gov/

5.4 TWO- OR THREE-PHASED SUBMISSION PROCESS:

5.4.1 This CSO may be conducted in two or three phases, at the discretion of the AOI Contracting Officer.

5.5 SUBMISSION PROCESS OVERVIEW:

5.5.1 Phase I (Required): All Offerors submit PowerPoint, White Paper, and ROM)

5.5.2 Phase II (Optional): Selected Offerors invited to pitch sessions at Government discretion

5.5.3 Phase III (Final): Selected Offerors submit full proposal package (Technical Proposal, PWS, Price Proposal, etc.)

5.5.4 The Government reserves the right to proceed directly from Phase I to Phase III.

5.6 PHASE I – POWERPOINT AND WHITE PAPER:

5.6.1 Phase I submissions will be evaluated in accordance with Attachments 1 and 2.

5.6.2 Acceptance dates will be listed in the AOI(s) (Attachment 7).

5.6.3 Submissions must be concise but technically descriptive.

5.6.4 All PowerPoints must include a Quad Chart per the template in Attachment 1.

5.6.5 Questions and answers will be posted on www.sam.gov during submission period.

5.7 PHASE II – PITCH SESSION:

5.7.1 If utilized, Phase II provides an opportunity for Offerors to present and discuss their proposed solution in greater depth following Phase I evaluation.

5.7.2 The Government may invite Offerors to participate in a virtual or in-person Pitch Session to address technical merit, operational applicability, and alignment with mission objectives.

5.7.3 Phase II is optional; CO may proceed directly from Phase I to Phase III at their discretion.

5.7.4 Phase II content and evaluation criteria are described in Attachment 3.

5.8 PHASE III – FULL PROPOSAL:

5.8.1 Only by invitation from CO.

5.8.2 Must follow Attachments 4–6 for format and content.

5.8.3 Offerors will have 30–45 days to submit after request.

5.8.4 Offerors must be registered in SAM.gov, meet FAR 9.1 responsibility requirements, and be eligible for award under applicable law/regulation.

http://www.sam.gov/

5.9 Evaluation And Selection Process:

5.9.1 Each AOI submission will be evaluated independently in accordance with Section 8 - Evaluation Framework and the detailed procedures in Attachment 6.

5.9.2 Evaluation is based on technical approach, projected timeline, and available funding.

5.9.3 Price will be assessed for fairness/reasonableness per DFARS 212.70.

5.9.4 Selections may be made at any phase; award is not guaranteed.

5.9.5 The CO will notify Offerors of selection/non-selection generally within 45 days.

5.9.6 If funding is not available, selected solutions may be retained in the Government’s solution repository for up to one years for future consideration

6. ADDITIONAL INFORMATION

6.1 DATA RIGHTS

6.1.1 It is the Government’s intention to acquire only the Technical Data, Computer Software, and Computer Software Documentation rights necessary to satisfy agency needs. The Government seeks to acquire the minimum rights necessary for operational use, testing, and maintenance. Offerors retain all rights to proprietary technologies and background intellectual property. Specific data rights will be negotiated based on the nature of the solution and Government operational requirements. These data rights provisions apply to all AOIs and awards under this CSO.

6.2 FOREIGN PARTICIPATION

6.2.1 Foreign firms are not eligible to participate in this CSO. The research, test data, and other deliverables under a resultant contract or agreement may contain Military Critical Technology List (MCTL) information whose export is restricted by the Export Control Act (Title 22, U.S.C.

§ 2751, et seq.) or DoDI 5000.83, Technology and Program Protection to Maintain Technological Advantage.

6.3 CYBERSECURITY REQUIREMENTS

6.3.1 In accordance with DFARS 252.204-7019 and 252.204-7020, the Contracting Officer cannot award a contract unless the successful Offeror has a current NIST SP 800-171 DoD assessment posted in the Supplier Performance Risk System (SPRS). All AOI awards must verify compliance prior to contract award. Offerors should review CMMC 2.0 requirements and be prepared to comply if specified in the AOI or resultant contract.

6.4 NON-GOVERNMENT ADVISORS

6.4.1 Proprietary information submitted in any phase may be provided to non-Government advisors supporting the Government in the evaluation of Offeror submissions. All non- Government advisors must have signed non-disclosure agreements and be bound by organizational conflict of interest (OCI) restrictions. Submission under this CSO constitutes consent for such advisors to participate in evaluations.

6.5 PROCUREMENT INTEGRITY, STANDARDS OF CONDUCT, ETHICAL

CONSIDERATIONS, AND CONFLICTS OF INTEREST

6.5.1 The Government will review all submissions for the existence or appearance of a conflict of interest (COI). Offerors must disclose any actual or potential COI early in the process.

6.5.2 Organizational Conflict of Interest (OCI): Offerors shall perform and submit an OCI analysis with their Phase II and/or Phase III proposal in accordance with FAR 9.5 and applicable GAO/US Court of Federal Claims decisions. If an OCI exists, Offerors must submit a mitigation plan for Government review.

6.5.3 Responsibility: To be considered for award under Phase III, Offerors must meet the requirements of FAR 9.104, be registered in SAM, and have a satisfactory performance record.

6.6 DEBRIEFINGS

6.6.1 The Government will conduct written, post-award debriefings for Phase III upon request only, in accordance with FAR 52.212-1(l). Debriefings will address the evaluation factors contained in Attachment 6 and any AOI-specific criteria but will not include a comparison of submissions, since there is no common PWS.

6.7 GOVERNMENT-FURNISHED PROPERTY (GFP)

6.7.1 GFP is not anticipated to be made available under any resulting contract, but determinations will be made at the AOI/award level. If provided, contractors are responsible for all associated costs (e.g., transportation, installation, rehabilitation) in accordance with FAR 45.201(b).

6.8 BASE SUPPORT / NETWORK ACCESS

6.8.1 Base access and/or network access for testing, validation, and demonstration will be determined for award. Requirements will be specified in AOI-specific instructions or subsequent contract documentation.

6.8.1.1 Evaluated for Technical Merit & Applicability, Importance to Agency Programs, and Price (fair and reasonable per FAR 12.209), plus compliance with Attachments 4–6.

6.8.1.2 Offerors must meet FAR 9.104 responsibility and be registered in SAM.gov.

6.8.1.3 The Government reserves the right to:

• Proceed directly from Phase I to Phase III, or

6.8.1.4 Award some, none or all of the proposal.

7. ATTACHMENT 1: PHASE I POWERPOINT BRIEFING & QUAD CHART FORMAT

7.1 PURPOSE

7.1.1 The Phase I PowerPoint briefing provides the initial visual summary of the proposed solution. The Quad Chart serves as the first content slide and must concisely communicate the key elements of the offering for rapid Government assessment.

7.2 QUAD CHART REQUIREMENTS

7.2.1 Format: Landscape orientation, one page maximum.

7.2.2 Template: Must follow the Government-provided Quad Chart template (Times New Roman, font size ≥ 12 pt).

7.2.3 Placement: Quad Chart must be the first content slide after the title slide in the briefing.

7.2.4 Content Areas:

7.2.4.1 Objective – Brief problem statement and intended outcome.

7.2.4.2 Description of Effort – Summary of technical approach.

7.2.4.3 Benefits of Proposed Approach – Expected advantages and impact to AOI.

7.2.4.4 Technical Challenges/Solution Approach – Key risks and planned mitigation.

7.2.4.5 Major Milestones – By Government fiscal year and month.

7.2.4.6 ROM Price Estimate – Rough Order of Magnitude cost.

7.3 POWERPOINT BRIEFING REQUIREMENTS

7.3.1 Format: Microsoft PowerPoint (.pptx) only.

7.3.2 Length: Maximum of five (5) content slides plus title slide.

7.3.3 File Size: Not to exceed 10 MB.

7.3.4 Font: Times New Roman, font size ≥ 12 pt.

7.3.5 Content:

7.3.5.1 Visually elaborate on Quad Chart elements.

7.3.5.2 Include graphics, diagrams, or images where beneficial.

7.3.5.3 Ensure alignment with AOI-specific requirements in Attachment 7.

7.3.5.4 Security Level: Phase I submissions shall be Unclassified. Subsequent phases may require submission and/or performance at higher classification levels, as specified in the AOI and any draft or final DD Form 254.

7.3.5.5 For classified content, contact the AOI Contracting Officer for submission instructions.

7.4 SUBMISSION INSTRUCTIONS

7.4.1 Submit Quad Chart and PowerPoint briefing together to the AOI Contracting Officer identified in the AOI.

7.4.2 Clearly mark file names with CSO#, AOI#, and Company Name.

7.4.3 Follow AOI-specific submission timelines in Attachment 7.

Topic #, Project Title

Objective: Clear concise (1-2 sentences) description of the goal of the effort (>12-pt font).

Description of Effort: Brief description of the technology or solution proposed (>12-pt font).

Core Concept: Brief description of the innovation or capability being proposed.

Key Technical Elements: Identify the primary technologies, methods, or tools that will be employed.

AOI Alignment: State how the approach specifically addresses one or more AOIs.

Technical Maturity: Indicate the current Technology Readiness Level (TRL) and any relevant demonstration history.

Expected Benefits: Summarize key anticipated impacts to SDA mission effectiveness (e.g., accuracy, latency, interoperability). (>12-pt font)

Challenges:

* Bulleted list of technical or timeline challenges. (>12-pt font)

Major Goals and Milestones to Capability Delivery (FY):

* Bulleted list must include anticipated delivery date of functioning capability.

(>12-pt font)

Proposed Funding ($K):

8. ATTACHMENT 2: PHASE I WHITE PAPER FORMAT

8.1 PURPOSE

8.1.1 The Phase I White Paper expands upon the PowerPoint briefing and Quad Chart to provide additional narrative detail for Government evaluation. It should clearly describe the proposed solution in the context of the AOI, without introducing unrelated corporate or personnel qualifications.

8.2 GENERAL REQUIREMENTS

8.2.1 Page Size: 8.5 x 11 inches, one-inch margins.

8.2.2 Length: Maximum of two (3) narrative pages plus cover page.

8.2.3 Format: Single-spaced, Times New Roman, font size ≥ 12 pt.

8.2.4 Submit as a PDF, file size not to exceed 10 MB.

8.2.5 Pages exceeding the limit will not be evaluated.

8.2.6 Cover Page: Must meet requirements in Attachment 4, Section 1.

8.3 CONTENT GUIDANCE

8.3.1 The White Paper must align directly with the AOI identified in Attachment 7 and should only expand upon elements presented in the PowerPoint/Quad Chart. At a minimum, include:

8.3.2 Objective – Problem statement and intended outcome.

8.3.3 Description of the Effort – Technical concept, approach, and key activities.

8.3.4 Benefits of the Proposed Approach – Operational, cost, or schedule advantages.

8.3.5 Technical Challenges – Anticipated risks and mitigation strategies.

8.3.6 Solution Approach – How the proposed concept addresses AOI needs.

8.3.7 Major Milestones – By Government fiscal year and month.

8.3.8 ROM Price Estimate – Rough Order of Magnitude cost aligned with proposed scope.

8.4 PROHIBITED CONTENT

8.4.1 Do not include:

8.4.1.1 Corporate or personnel qualifications

8.4.1.2 Past performance information

8.4.1.3 Supplemental material not requested

8.5 CLASSIFIED SUBMISSIONS

8.5.1 Phase I submissions shall be Unclassified. Subsequent phases may require submission and/or performance at higher classification levels, as specified in the AOI and any draft or final DD Form 254. For classified submissions:

8.5.1.1 Contact the AOI Contracting Officer for secure submission instructions.

8.5.1.2 Ensure classified data is handled in accordance with applicable security protocols.

8.6 SUBMISSION INSTRUCTIONS

8.6.1 Submit the White Paper electronically to the Contracting Officer identified in the AOI.

8.6.2 Clearly mark file names with CSO#, AOI#, and Company Name.

8.6.3 Submissions must be received by the AOI-specific deadline in Attachment 7.

8.6.4 The requirement for a cover sheet is applicable for all Phase I White Papers submitted in response to new AOIs published.

9. ATTACHMENT 3: PHASE II PITCH SESSION FORMAT

9.1 OVERVIEW

9.1.1 Phase II is an optional intermediate step in the CSO evaluation process, conducted at the Government’s discretion. It provides Offerors the opportunity to present, demonstrate, and discuss their proposed concept, technology, or solution in greater depth following Phase I evaluation.

9.2 The Government may:

9.2.1 Invite Offerors to a Phase II Pitch Session based on technical merit, applicability, and alignment to the AOI.

9.2.2 Proceed directly from Phase I to Phase III without conducting a Pitch Session.

9.2.3 Request supplemental written information in addition to the live or virtual pitch.

9.3 PITCH SESSION FORMAT

9.3.1 Duration: 30 minutes for Offeror presentation, followed by Government-led Q&A. Additional time may be provided for discussion as needed.

9.3.2 Format: Virtual (preferred) or in-person, based on operational requirements, security considerations, and scheduling.

9.3.3 Submission of Materials: Offerors shall submit all supporting materials in advance of the session in accordance with Government-provided instructions. Classified material may only be presented in accordance with Government security protocols and pre-coordination.

9.4 REQUIRED CONTENT

9.4.1 The Offeror’s Pitch Session presentation shall include:

9.4.1.1 Executive Summary: Summarize the concept and how it aligns with the AOI and objectives.

9.4.1.2 Technical Approach:

• Core technology or capability description.

• Innovation elements and differentiators from existing solutions.

• Demonstrations, models, or visual aids, if available.

9.5 OPERATIONAL APPLICABILITY:

9.5.1 How the solution integrates into 21ST CS and CNECTS operations.

9.5.2 Scalability, adaptability, and interoperability considerations.

9.5.3 ESTIMATED PRICE/SCHEDULE:

9.5.3.1 Rough Order of Magnitude (ROM) price.

9.5.3.2 Notional schedule for development, integration, testing, or demonstration within the DoD.

9.5.4 DATA RIGHTS ASSERTIONS:

9.5.4.1 Identification of any Intellectual Property (IP) involved.

9.5.4.2 Associated restrictions on Government use.

9.5.4.3 Proposed data rights consistent with DFARS 227 requirements.

9.5.5 RISK ASSESSMENT:

9.5.5.1 Key technical, schedule, and integration risks.

9.5.5.2 Mitigation strategies.

9.5.6 MISSION IMPACT:

9.5.6.1 Benefits to mission capabilities, decision-making, and 21CS readiness.

9.5.6.2 Potential cross-mission or cross-service applicability.

9.5.7 GOVERNMENT ROLE IN PHASE II

9.5.7.1 Evaluation: Phase II sessions will be assessed using the evaluation factors in Attachment 6.

9.5.7.2 Non-Government Advisors: If applicable, advisors supporting the evaluation will be under Non-Disclosure Agreements (NDAs) and bound by conflict-of-interest restrictions.

9.5.7.3 Clarifications: The Government may request follow-up information to clarify or expand on concepts discussed.

9.5.8 SELECTION PATHWAYS

9.5.8.1 Following Phase II, the Government may:

• Invite the Offeror to submit a Phase III Proposal.

• Request additional refinement or re-submission for consideration in a future AOI cycle.

• Decline advancement if the solution is determined not to meet technical, operational, or enterprise needs.

Note: The Government reserves the right to forgo Phase II and go directly to Phase III.

10. ATTACHMENT 4: PHASE III TECHNICAL PROPOSAL & PWS FORMAT

10.1 GENERAL OVERVIEW

10.1.1 The Phase III submission is the Offeror’s complete, final package for Government evaluation and potential award. It must be precise, self-contained, and directly responsive to the CSO, the applicable AOI, and any specific instructions in the Phase III Request for Proposal (RFP). All content should be tailored to the solution proposed and address applicability. Submissions shall be provided electronically in both searchable PDF format (for the technical narrative) and Microsoft Word format (for the PWS). Supporting files (e.g., spreadsheets, diagrams, schedules) should be provided in their native editable format.

10.2 COVER SHEET REQUIREMENTS

10.2.1 The Phase III proposal shall include a cover sheet containing the following information:

10.2.1.1 CSO and AOI Number and AOI Title (if applicable)

10.2.1.2 Full Legal Company Name and Address

10.2.1.3 CAGE Code

10.2.1.4 Unique Entity ID Number

10.2.1.5 Business Size Classification (NAICS specified in the AOI)

10.2.1.6 Socioeconomic Status (e.g., Small Business - 8(a))

10.2.1.7 Point of Contact Information – Name, Title, Phone Number, Email Address

10.2.1.8 Date of Submission

10.3 TECHNICAL PROPOSAL REQUIREMENTS

10.3.1 The Technical Proposal should be sufficiently detailed to demonstrate the Offeror’s understanding, feasibility, and technical merit, while maintaining clarity and conciseness. The narrative should cover:

10.4 BACKGROUND AND OBJECTIVES

10.4.1.1 Summarize the problem or need addressed by the proposed solution.

10.4.1.2 Identify the CNECTS mission relevance and alignment with the applicable AOI.

10.4.1.3 Provide relevant context, including prior work, related programs, or operational challenges.

10.5 MILESTONES AND SCHEDULE

10.5.1.1 Include a table or graphic showing all major milestones.

10.5.1.2 Present activities by fiscal year to match the Technical Proposal timeline.

10.6 TECHNICAL APPROACH

10.6.1.1 Describe the concept, methodology, and technologies to be applied.

10.6.1.2 Identify innovative aspects, differentiators, and advantages over existing solutions.

10.6.1.3 Address possible integration with existing USSF/Combat Forces Command/S33Z systems and workflows.

10.6.1.4 Include operational considerations (e.g., certifications, security requirements, algorithms, software development methodologies).

10.7 DELIVERABLES AND OUTCOMES

10.7.1.1 Provide a clear list of deliverables with measurable acceptance criteria.

10.7.1.2 Specify intended operational outcomes and benefits to the 21st CS.

10.8 MAJOR PROGRAM MILESTONES

10.8.1.1 Present a graphic timeline of milestones by Government fiscal year and month.

10.8.1.2 Include key development, test, and delivery events.

10.9 GOVERNMENT SUPPORT REQUIREMENTS

10.9.1 Identify any Government-furnished property (GFP), facilities, data, or other support required to execute the proposed effort.

10.10 DATA RIGHTS ASSERTIONS

10.10.1 Identify any Intellectual Property (IP) involved, along with proposed data rights assertions in accordance with DFARS 252.227-7013, 7014, and 7017.

10.10.2 Provide rationale for each assertion.

Note: Phase III Technical Proposal page limits and formatting specifications will be identified in the individual Phase III RFP.

10.11 PERFORMANCE WORK STATEMENT (PWS) REQUIREMENTS

10.11.1 The final PWS must be a standalone, contract-ready document suitable for incorporation without modification, and must exclude proprietary information. The PWS should contain:

10.11.2 OBJECTIVE

10.11.2.1 Briefly describe the overall purpose of the effort and the operational need it addresses.

10.11.3 SCOPE

10.11.3.1 Define the breadth of work to be accomplished, including AOI focus, goals, and high-level deliverables.

10.11.3.2 Identify the intended impact on mission capabilities.

10.11.4 TASKS AND TECHNICAL REQUIREMENTS

10.11.4.1 Detail the specific tasks to be performed, broken down by base and option periods.

10.11.4.2 Present tasks in a logical sequence aligned with the proposed schedule.

10.11.4.3 Use binding language (“The Contractor shall…”) for mandatory requirements.

10.11.4.4 Clearly separate optional tasks from base tasks.

10.11.5 STANDARDS AND CONSTRAINTS

10.11.5.1 Reference applicable standards, security requirements, and compliance criteria.

10.11.5.2 Identify constraints such as access restrictions, export controls, or special certifications.

10.11.6 ADDITIONAL REQUIREMENTS

10.11.6.1 CROSS-REFERENCING:

• The Technical Proposal and PWS should be consistent and cross-referenced for traceability.

10.11.7 FLEXIBILITY:

10.11.7.1 PWS should avoid excessive detail that would hinder flexibility in execution, while still providing sufficient clarity for evaluation.

10.11.8 REVIEW AND NEGOTIATION:

10.11.8.1 The Government reserves the right to modify the PWS language during negotiations prior to award.

11. ATTACHMENT 5: PHASE III PRICE PROPOSAL FORMAT

11.1 PRICE PROPOSAL INSTRUCTIONS

11.1.1 The Price Proposal submission must include pricing information sufficiently detailed for meaningful evaluation of the proposal. For pricing purposes, Offerors should assume a contract start date of approximately ninety (90) days after submission of the proposal. The Price Proposal does not have a page limit restriction.

11.1.2 Since all proposals are considered commercial items, technologies, or services, the requirements of the Truthful Cost or Pricing Data Act are not applicable. However, if the Contracting Officer determines additional information is necessary to support a determination of a fair and reasonable price, other than certified cost and pricing data may be requested.

11.1.3 The responsibility for providing adequate supporting data and attachments lies solely with the Offeror. Further, the Offeror must 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.

11.1.4 The Offeror shall prepare the Price Proposal submission to include an electronic version of the pricing model in a Microsoft (MS) Excel editable format. The Excel file must:

11.1.4.1 Contain all cost elements that roll up to the total proposed price.

11.1.4.2 Show formulas in all calculation cells, with links intact where applicable.

11.1.4.3 Clearly identify base and option periods (if applicable).

11.1.4.4 Include labor category details (titles, rates, hours, and extended amounts).

11.1.4.5 Include material/equipment lists with unit prices and extended totals.

11.1.4.6 Identify any travel costs with assumptions (e.g., number of trips, duration, per diem rates).

11.1.4.7 Break out subcontractor costs, including the basis for estimate (quotes, market data).

11.1.4.8 Match all totals to the Summary Pricing Table provided in the main proposal document

11.2 PRICE PROPOSAL CONTENT REQUIREMENTS

11.2.1 The Price Proposal must contain, at a minimum:

11.2.2 SUMMARY PRICING TABLE

11.2.2.1 Total proposed price by Contract Line-Item Number (CLIN), sub-CLIN (if applicable), and any separately priced Contract Data Requirements List (CDRL) items.

11.2.2.2 Identification of base and option period pricing, if applicable.

11.2.3 BASIS OF ESTIMATE (BOE)

11.2.3.1 Narrative describing the estimating methodology used (e.g., prior sales data, vendor quotes, market rates).

11.2.3.2 Key assumptions (quantities, performance period, labor mix, materials).

11.2.4 LABOR AND MATERIAL BREAKDOWN (IF APPLICABLE)

11.2.4.1 Labor categories, proposed hours, and fully burdened labor rates.

11.2.4.2 Major material/equipment costs with supporting rationale.

11.2.5 SUBCONTRACTOR/PARTNER PRICING (IF APPLICABLE)

11.2.5.1 Identify subcontracted portions of work and associated costs.

11.2.5.2 Describe the basis for subcontract pricing (quotes, catalog pricing, market research).

11.2.6 SUPPORTING MARKET DATA

11.2.6.1 Evidence supporting the commerciality of the item/service (product literature, commercial price lists, historical sales data).

11.2.6.2 Documentation to demonstrate proposed prices are fair and reasonable (per FAR 12.209).

11.2.7 EXCEL PRICING MODEL (REQUIRED)

11.2.7.1 Fully functional MS Excel file with all formulas intact.

11.2.7.2 Must match the summary pricing table in totals.

11.2.7.3 Clearly labeled tabs (e.g., “Labor,” “Materials,” “Travel,” “Subcontracts,” “Summary”).

11.2.7.4 Include assumptions or tab notes explaining key pricing drivers.

11.2.8 BURDEN OF PROOF

11.2.8.1 The responsibility for providing adequate supporting data rests solely with the Offeror.

Offerors bear the burden of proof in establishing the reasonableness of their proposed prices.

Failure to provide adequate support may result in an evaluation finding of “price not reasonable,” which may render the proposal unawardable.

11.2.9 FILE NAMING AND SUBMISSION INSTRUCTIONS

11.2.9.1 Price Proposals shall be submitted in accordance with the instructions provided in the Phase III, Request for Proposal (RFP), for the specific AOI. As a general rule:

• File Name Format: CSO-<AOI#>-PriceProposal-<CompanyName>-<Date>

• Example: CSO-AOI2025_01-PriceProposal-ABCSystems-2025-05-15.xlsx

• Price Proposal and supporting files must be transmitted via the method specified in the AOI solicitation (e.g., secure file transfer, encrypted email).

12. ATTACHMENT 6: EVALUATION AND SELECTION PROCESS

12.1 EVALUATION CRITERIA

12.1.1 All phase submissions will be evaluated against the following criteria, each of equal importance:

• Technical Merit/Applicability – The degree to which the proposed solution demonstrates sound and innovative technical approach, directly meets the stated AOI objectives, and reflects the technical feasibility for integration into the CNECTS operation environment.

• Importance to Agency Programs – The extent to which the proposed solution directly supports the goals of consolidation and modernization by advancing the needs of the 21st Communication Squadron, filling critical capability gaps, and measurably enhancing the performance, security, and resilience of supported USSF missions.

• Price & Value to the Government– Price will be evaluated to the extent to which the proposed price reflects the total cost of ownership, including efficiencies gained from consolidation, reduced long-term sustainment costs promised by automation, and the overall value of the proposed innovation. No award will be made unless the Government determines the final negotiated price to be fair and reasonable.

12.1.2 All phase submissions will be evaluated by a subject-matter expert peer review process.

12.1.3 All phase submissions will be categorized as Recommended, Selectable, or Non-selectable as follows:

12.1.3.1 Recommended: Submissions are recommended for acceptance if sufficient funding is available and normally are displaced only by other Recommended submissions. To be categorized as “Recommended,” a white paper must meet all the following:

• Strong technical merit

• Addresses the AOI directly

• Shows high potential impact to mission areas

• Project scope reasonable and feasible within expected cost/schedule boundaries

• High value for the associated cost

• Selectable: submissions are recommended for acceptance if sufficient funding is available, but at a lower priority than Recommended submissions. A Selectable submission may require additional development. To ensure a diversity of approaches, a Selectable submission may be prioritized over a Recommended submission if the Selectable submission presents a unique approach unlike any of the Recommended submissions. A submission may be categorized as “Selectable” if it meets any of the following:

• Acceptable technical merit

• Relevant to the AOI but may have limitations, open questions, or lower mission impact

• Shows moderate potential impact to mission areas

• Project scope reasonable and feasible within expected cost/schedule boundaries, but may need clarification or refinement

• Acceptable value for the associated cost

12.1.3.2 Not Selectable: Even if funds were available, the submission should not be funded.

Submissions may be categorized as “Not Selectable” if it meets any of the following:

• Insufficient technical merit

• Does not align with the AOI

• Shows insufficient potential impact to mission areas

• Project scope unreasonable and/or infeasible within expected cost/schedule boundaries

• Insufficient value for the associated cost

12.2 PHASE-BY-PHASE EVALUATION PROCESS

12.2.1 Phase I – PowerPoint and White Paper

12.2.1.1 The Government will review Phase I submissions and select the Offeror(s) that have the greatest potential to meet the needs of the AOI outlined in Attachment 7.

12.2.2 Phase II – Pitch Session

12.2.2.1 If Phase II is utilized, the Government will review the Pitch Session content and any supplemental written material requested by the Government.

12.2.3 Phase III – Technical, PWS, and Price Proposal

12.2.3.1 The Government will review Phase III proposals and award to the Offeror(s) that have the greatest potential to meet the needs of this AOI outlined in Attachment 7.

12.2.4 Price Evaluation Crosswalk to Attachment 5

12.2.4.1 The Government will review the Microsoft Excel pricing model submitted in Phase III to confirm:

• All formulas are functional and calculations are transparent.

• All cost elements (labor, materials, travel, subcontracts) are clearly broken out and match the Summary Pricing Table.

• Basis of Estimate (BOE) assumptions are documented.

• Pricing is consistent with the technical approach and PWS tasks.

• Subcontractor costs are traceable to supporting documentation.

• Failure to provide a complete Excel pricing model meeting these requirements may result in the proposal being downgraded for Price or deemed incomplete.

12.2.4.2 Proposals need not be evaluated against each other since they are not submitted in response to a common PWS. The Government reserves the right to fund all, some, one, or none of the proposals submitted. The Government may elect to fund a portion of a proposal or fund a portion of any mix of proposals under this CSO.

12.2.4.3 Price shall be considered to the extent appropriate, but at a minimum, to determine that the price is fair and reasonable.

NOTE: Price evaluation in this Attachment is directly tied to the Price Proposal content and structure defined in Attachment 5. Offerors must ensure their Phase III pricing submissions comply fully with Attachment 5 to avoid delays or negative impacts on evaluation results.

13. ATTACHMENT 7 – AREAS OF INTEREST (AOIs)

13.1 PURPOSE:

13.1.1 This attachment defines the current Areas of Interest (AOIs) under the CSO and status.

All AOIs will be a single solicitation under the CSO and will be closed.

Table 16-1, AOI Master Record

AOI Number Title Posting Date Close Date Funding Ceiling

AOI-

2026_01

BOS-IT [MM/DD/YYYY] [MM/DD/YYYY] TBD

13.2 AOI EXAMPLE TEMPLATE

AOI Number: [CSO-Year_XX] AOI Title: [Descriptive Title] Posting Date: [MM/DD/YYYY] Closing Date: [MM/DD/YYYY] NAICS Code: [Primary NAICS for this AOI] Set-Aside Status:

Submission Method: [Email, SAM.gov, website, etc.] Primary Point of Contact: Name, Title, Email, Phone Funding Ceiling: [Dollar Amount or Funding Pool Statement] Background: [Why the AOI exists, mission relevance] Description of Desired Capabilities: [Technical focus areas and goals] Performance Expectations and Integration Considerations: [Testing, certification, operational environment] Security Requirements: Phase I submissions shall be Unclassified. Subsequent phases may require submission and/or performance at higher classification levels, as specified in the AOI and any draft or final DD Form 254.

Submission Instructions: All submissions must comply with Attachments 1–6 of this CSO. Phase I submissions are limited to the Quad Chart and White Paper formats defined in Attachments 1 and 2. If classified submission is required, coordinate with the Contracting Officer for secure transmittal.

Evaluation: Evaluated per Attachment 6 criteria. AOI-specific priorities or weighting (if applicable).

Funding Statement: Explicit statement of funding ceiling or shared pool.