CNECTS CSO Final Draft v1.0.docx

Commercial Solutions Opening (CSO)

FA2518-26-S-CNECTS

Combat Forces Command (CFC) Communications, Network, Engineering, Cybersecurity, and Information Technology Services (CNECTS, pronounced “Connects”) Space Acquisition & Integration Office (SAIO)

[Type here]

Record of Revision

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.

Commercial Solutions Opening (CSO): A competitive, 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.

Closed CSO: Only open for one AOI, closes out/cancels as soon as award is made.

Closed Period AOI: This type of AOI allows for solution briefs, company pitches, and/or proposal submission at any time within a specified period set forth in each Closed Period AOI. Once the submission deadline is reached, evaluations will begin and no additional submissions will be accepted.

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.

GENERAL INFORMATION

INTRODUCTION and BACKGROUND As the USSF continues to reorganize, it has identified significant inefficiencies in managing four disparate but related Information Technology (IT) support contracts. These contracts are managed by separate organizations, with multiple contracting officers and Contracting Officer Representatives (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 Communications Squadron (21 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.

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

Base Operating Support-Information Technology (BOS-IT), FA2517-24-F-0034 Cheyenne Mountain SFS 21 CS Communications Contract, FA8723-26-R-B006 Wing Information & Communications Support (WICS), FA2550-21-C-0005 Plans and Programs Engineering Design Support (PEDS), FA2550-22-C-0003

1.1.1 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.

1.1.2 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.

KEY INFORMATION SUMMARY

This solicitation is for a Closed CSO - with one Closed Period AOI.

Estimated Funding: Funding lines consistent with historical requirements are available for the award of this CSO.

Contract Type: Fixed Price (RFO Subpart 16.2) contract structure; a combination of fixed price types may be considered to balance risk between the Government and contractor.

Set-Aside: This is a 100% set aside for small businesses. Teaming arrangements are authorized with a small business as the prime contractor in accordance with RFO 52.219-14 Limitations on Subcontracting.

Period: The Government anticipates a 60-day Phase-In Period, One Year Base Period, Five Option Years, and One 6-month extension.

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.

In the event of any conflict, the official terms of the CSO and AOI take precedence over any answers provided during Q&A or industry day sessions. Any inconsistencies between the two will be resolved in favor of the CSO and AOI.

CSO APPROACH

AUTHORITY

This Commercial Solutions Opening (CSO) is an approved 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 21 CS.

AOI PUBLICATION

Approved AOI will be posted on SAM.gov.

AOI will include submission and evaluation instructions tailored to its scope.

EVALUATION & AWARD

Evaluations will follow the process in Attachment 4 – Phased CSO Process Overview.

The Government will be responsible for conducting all evaluation phases and documenting results in accordance with Revolutionary Federal Acquisition Regulation Overhaul (RFO).

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

The Government will apply the evaluation steps and factors described in Attachment 5 – Evaluation and Selection Process and ensure results are documented in accordance with established standards.

This acquisition is being conducted under the guidelines of R-DFARS 212.70. Award will be based on a review of proposals by a subject-matter expert peer review process. This method does not use any aspects of RFO Subpart 15.2 – Evaluation and Award. The use of the CSO process does not obligate the Government to determine a competitive range or conduct negotiations as outlined in RFO 15.204.

COMPLIANCE & RECORDS

Award will be made using a FAR-based contract.

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

APPLICABILITY

This CSO seeks innovative solutions to address 21 CS mission challenges through commercial solutions and industry best practices. The Government encourages a broad range of technical and business approaches aligned with the specific Area of Interest (AOI). All submissions in response to this AOI will be governed by this CSO.

Award made under this CSO shall be fixed-price type, FAR-based contract. The small business set-aside status determination for 100% small business was approved on 13 May 2026. AOI is limited to small business primes. The Government will award the single proposal offering the best overall value. CLIN and pricing structure may vary within the fixed-price family as appropriate to the AOI, requirements, and available funding. Individual Job Orders (IJOs) may be utilized for surge requirements, significant upgrades or modifications to mission systems, or other special projects as needed.

Proposals submitted under this CSO will be evaluated using a multi-phase process, as described in Attachment 4 – Phased CSO Process Overview. The Contracting Officer will adhere to and must apply the evaluation steps and factors described in Attachment 5 – Evaluation and Selection Process and ensure results are documented in accordance with established standards.

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

Primary method of communication will be via www.sam.gov. Offerors are responsible for monitoring www.sam.gov for all amendments issued against this CSO. The Contracting Officer, rosalind.davis.3@spaceforce.mil is the sole point of contact for this acquisition.

SUBMISSION INFORMATION

SUBMISSION OVERVIEW

This CSO will be closed at 00:01 MST on 16 November 2026. It will be open for Phase I submissions in accordance with the AOI outlined in Attachment 6 – Area of Interest until that time.

The Government will not reimburse companies for costs associated with submissions for Phases I-II.

Electronic copies of each White Paper shall be submitted through the Solicitation Module of the Procurement Integrated Enterprise Environment (PIEE) suite at https://piee.eb.mil/. All submissions shall follow this filename format:

Phase I: [AOI#]Phase[#][Document Type] [CompanyName][YYYYMMDD] Example: AOI2025_01_Phase_I_WhitePaper_ABC_Corp_Inc_20251015.pdf Maximum filename length: 50 characters

1.1.3 Correspondence during all Phases shall be sent to the Contracting Team’s point of contact listed in the AOI.

1.1.4 White Papers submitted by mail, email, or hand-carried will not be evaluated.

1.1.5 White Papers sent through proprietary or third-party File Transfer Protocol (FTP) sites or DoD SAFE will not be retrieved.

1.1.6 All white papers received after the exact time specified for receipt shall be treated as late submissions and will not be considered.

1.1.7 For instructions on how to post an offer, please refer to the Posting Offer demo: https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf

RECEIPT CONFIRMATION

To ensure submissions have been received by the Government, Offerors shall send a separate email (not containing attachments) to the Contracting Team’s point of contact listed in the AOI immediately after their PIEE submission to obtain written email confirmation of receipt from the Contracting Officer that all electronic files comprising the complete white paper were received.

The Offerors are responsible for ensuring all electronic files are virus-free and shall run an anti-virus scan before submission.

Hardcopies for any documents will not be accepted.

FILE COMPATIBILITY

Each electronic white paper submissions shall be in the form of a searchable PDF, editable native files (if requested), and free of password protection Accessible links to outside documents or websites will not be accessed or adjudicated Do not embed sound or video (e.g., MPEG) files into the white paper.

PROPRIETARY INFORMATION

Offerors shall mark each page of submissions that contain proprietary information. Offerors may assert restrictions on the use, release, or disclosure of data/software provided during contract performance in accordance with Class Deviation-2026-O0036 available at www.acquisition.gov).

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

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, prime and all applicable teaming partners should jointly notify the Contracting Officer via email at the earliest possible opportunity, but NLT 15 days prior to submission deadline. The Contracting officer will provide specific submission instructions at that time.

TWO- OR THREE-PHASE SUBMISSION PROCESS

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

SUBMISSION PROCESS OVERVIEW

Phase I (Required): All Offerors submit a White Paper and ROM Phase II (Optional): Selected Offerors invited to pitch sessions at Government discretion Phase III (Final): Selected Offeror submits full proposal package (Technical Proposal, PWS, Price Proposal, Quality Control Plan, etc.)

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

PHASE I –WHITE PAPER

Phase I submissions will be evaluated in accordance with Attachment 1 – Phase I White Paper Format.

Acceptance dates will be listed in Attachment 6 – Area of Interest (AOI).

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

PHASE II – PITCH SESSION

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

By CO initiation only, Offerors may be invited to participate in a virtual or Pitch Session to address technical merits, operational applicability, and alignment with mission objectives.

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

Phase II content and evaluation criteria are described in Attachment 2 – Phase II Pitch Session Format.

Phase III – FULL PROPOSAL Only by invitation from CO.

Must follow instructions found in Attachment 3 – Phase III Technical Proposal & PWS for instructions and content requirements.

Offerors will be provided detailed timeline expectations for final proposal at time of selection.

Offerors must be registered in SAM.gov, meet RFO Subpart 9.1, Responsible Prospective Contractors, requirements, and be eligible for award under applicable law/regulation.

EVALUATION AND SELECTION PROCESS

Each AOI submission will be evaluated independently in accordance with Attachment 5 - Evaluation and Selection Process and the detailed procedures in Attachment 6 – Area of Interest (AOI).

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

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

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

The CO anticipates notification of Offerors of their exclusion or inclusion in the next Phase within 45 days of the submission deadline.

ADDITIONAL INFORMATION

DATA RIGHTS

It is the Government’s intention to acquire only the Technical Data, Computer Software, and Computer Software Documentation rights necessary to satisfy agency needs IAW Class Deviation DFARS 227.7202.

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 this CSO.

The rationale for each assertion will be requested of Offerors that are invited to Phase III (IAW Class Deviation CO 2026-O00036, under DFARS 252.227-7994).

FOREIGN PARTICIPATION

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.

CYBERSECURITY REQUIREMENTS

In accordance with R-DFARS 252.204-7019 and 252.204-7020, R-DFARS 252.240-7997, NIST SP 800-171 DoD Assessment Requirements (Deviation 2026-O0025), 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).

Final Offeror selected for Phase III must provide evidence of cybersecurity compliance prior to final contract award. Offerors should review CMMC requirements and be prepared to comply with all applicable requirements effective on the date of contract award.

NON-GOVERNMENT ADVISORS

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.

PROCUREMENT INTEGRITY, STANDARDS OF CONDUCT, ETHICAL CONSIDERATIONS, AND CONFLICTS OF INTEREST 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 prior to their Phase I submittal, or as soon as practical following submission.

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 RFO Subpart 9.5, Organizational and Consultant of Interest, and applicable GAO/US Court of Federal Claims decisions.

If an OCI exists, Offerors must submit a mitigation plan for Government review.

RESPONSIBILITY

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

DEBRIEFINGS

The Government will conduct written post-award debriefings upon request only, in accordance with FAR 52.212-1(l).

Debriefings will address the evaluation factors contained in Attachment 5 – Evaluation and Selection Process and any AOI-specific criteria but will not include a comparison of submissions, since there is no common PWS.

GOVERNMENT-FURNISHED PROPERTY (GFP)

GFP is not anticipated to be made available under any resulting contract, but final determinations will be made during Phase III.

If provided, contractors are responsible for all associated costs (e.g., transportation, installation, rehabilitation) in accordance with RFO 45.201(b).

MANDATORY SOURCES

In order to support Supply Chain Risk Management and mitigate cost risk, contractors will be required to adhere to all Mandatory Source requirements and may be allowed to make purchases through government sources where allowable.

BASE SUPPORT / NETWORK ACCESS

Base access and/or network access for testing, validation, and demonstration will be provided at time of award.

CONTRACTOR TEAMING ARRANGEMENTS (CTAs) Whether structured as a joint venture/partnership and/or protégé/mentorship arrangement acting as a prime contractor or via prime-subcontractor agreements, finalized agreements must be disclosed prior to beginning Phase II.

Offerors will be required to identify and provide the primary point of contact for each team member participating in the agreement.

While the Government does not require a written copy of this agreement until Phase III, it reserves the right to contact individual members to verify an agreement has been finalized.

Finalized agreements must contain percentage of workshare, scope of effort, and estimated period of performance (Government requires a period of performance that begins on or before 16 November, 2026 and concludes no earlier than the end of the contract base year).

ATTACHMENT 1: PHASE I WHITE PAPER FORMAT

PURPOSE

The Phase I White Paper shall provide sufficient narrative detail for the Government to evaluate the proposed solution. The White Paper shall clearly explain how the solution addresses the applicable Area of Interest (AOI) and shall not include unrelated corporate experience, past performance, or personnel qualifications.

GENERAL REQUIREMENTS

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

Length: Maximum of seven (7) pages plus cover page.

Format: Single-spaced, Times New Roman, font size ≥ 12 pt for text, Arial family font size ≥ 10 pt for tables and graphics. Tables and graphics may be landscape, but all other text must be portrait.

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

Pages exceeding the limit will not be evaluated.

CONTENT GUIDANCE

The White Paper must align directly with the AOI identified in Attachment 6 – Area of Interest. At a minimum, include:

Objective – Problem statement and intended outcome.

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

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

Technical Challenges – Anticipated risks and mitigation strategies.

Solution Applicability – How the proposed concept addresses AOI needs.

Major Milestones – By Government fiscal year and month.

Rough Order of Magnitude (ROM) Price Estimate – The ROM cost must be aligned with the AOI scope. The ROM shall be one number that captures the total estimated price for the entire period of performance (including options and material costs).

ADDENDUM PAGES EXCLUDED FROM PAGE LIMIT

Offerors may include a separate White Paper Addendum, maximum of 5 pages, that will not count toward the seven-page maximum for the Phase I White Paper.

The addendum is intended to provide limited supporting information necessary to clarify the proposed solution and the Offeror’s understanding of the requirement.

The White Paper Addendum shall be clearly labeled “White Paper Addendum—Excluded from Page Limit” and submitted as a separate section or file.

Addendum pages must identify the applicable Area of Interest (AOI), Offeror name, and solicitation number.

The following material may be included in the addendum and excluded from the seven page limit:

1.1.8 Terms, definitions, and acronyms necessary to understand the White Paper.

1.1.9 Assumptions underlying the proposed solution, including assumptions regarding Government-furnished information, facilities, equipment, access, interfaces, data, or support.

Dependencies and constraints that may affect technical feasibility, schedule, implementation, interoperability, security, or performance.

1.1.10 Clarifying technical diagrams, tables, interface descriptions, or data-flow illustrations that directly support the White Paper narrative.

1.1.11 Past performance with restrictions. Offerors may provide a summary of relevant past performance to demonstrate experience performing work similar in scope, complexity, technical focus, and operational environment to the applicable Area of Interest (AOI).

1.1.12 Each past-performance example shall be limited to one-half page and include only the following information: Suggested Past-Performance Example Format:

Past Performance Example [#] Work Type/Technical Scope: [Describe the requirement generically.] Offeror Role: [Prime contractor/subcontractor/etc.] Duration: [e.g., “36 months”] Scale and Complexity: [Generalized size, scope, users, sites, systems, or technical environment.] Results Achieved: [Quantifiable outcomes.] Relevance to AOI: [Explain direct applicability to the proposed solution.]

1.1.13 Past-performance examples are limited to [two] examples and may not exceed [one] page total. Past-performance information provided beyond these limits will not be reviewed as relevant information.

1.1.14 The Government will review only the relevance and demonstrated results of the experience described.

1.1.15 The Government will not contact customers or conduct independent past-performance verification during this phase.

1.1.16 If the Offeror is invited to proceed to a subsequent phase, the Government may request additional information or substantiating documentation.

1.1.17 The addendum may be used only when necessary to provide information expressly requested or otherwise permitted by this Commercial Solutions Opening (CSO), such as to clarify or document a limited matter identified by the Government. It is not intended to supplement, expand, or circumvent the seven-page White Paper limitation.

1.1.18 The Government will consider information in an addendum only to the extent it is relevant to, and properly submitted for, the specific permitted purpose. Offerors shall ensure that all substantive technical content necessary to evaluate the proposed solution is included in the White Paper.

1.1.19 The addendum shall not include substantive technical narratives that belong in the White Paper; additional solution descriptions; marketing materials; corporate experience; personnel resumes or qualifications; pricing or cost information; or any other information not specifically authorized by this CSO.

1.1.20 Information submitted outside these limitations may be disregarded and will not be used to cure omissions or deficiencies in the White Paper.

PROHIBITED CONTENT

Corporate or personnel qualifications Past performance information, other than allowed information “Addendum Pages” Supplemental material not requested

CLASSIFIED SUBMISSIONS

1.1.21 Phase I submissions shall be Unclassified. If subsequent Phases require submission at higher classification levels, contact the Contracting Officer for specific submission instructions.

1.1.22 Ensure CUI data is handled in accordance with applicable security protocols.

SUBMISSION INSTRUCTIONS

Submit the White Paper electronically through the Solicitation Module of the Procurement Integrated Enterprise Environment (PIEE) suite at https://piee.eb.mil/.

Clearly mark file names as directed in 4.1.3.

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

SAM REGISTRATION AND REPRESENTATIONS AND CERTIFICATION GATE

As an initial eligibility gate for Phase I White Paper consideration, each Offeror shall maintain an active registration in the System for Award Management (SAM) and ensure that all applicable representations and certifications are current, accurate, and complete.

Offerors that do not meet this requirement may be ineligible for further consideration under the CNECTS CSO, including participation in Government-facilitated teaming and partnering activities or evaluation for advancement to a subsequent phase.

The Offeror is responsible for ensuring its SAM information remains current throughout the CSO process.

FAR 4.1201 requires Offerors and quoters to complete electronic annual representations and certifications in SAM and review/update them as necessary, but at least annually.

FAR 4.1202 prescribes use of the applicable solicitation provision for annual representations and certifications.

ATTACHMENT 2: PHASE II PITCH SESSION FORMAT

OVERVIEW

Phase II is an optional, intermediate phase 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.

Presentation attendance is strictly limited to personnel that intend to provide active support upon contract award. Individuals who are not direct employees of the Offeror, or of an identified teaming partner that will be directly involved in contract performance, are prohibited from attending and will be asked to exit the session. This restriction explicitly excludes outside proposal development consultants.

ALLOWANCES

The Government may:

Invite Offerors to a Phase II Pitch Session based on evaluation and selection results IAW Attachment 5- Evaluation and Selection Process.

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

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

PITCH SESSION FORMAT

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

1.1.24 Format: Virtual based on operational requirements, security considerations, and scheduling.

1.1.25 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.

REQUIRED CONTENT

1.1.26 Executive Summary: Summarize the technical approach and how it aligns with the AOI and objectives.

1.1.27 Detailed Technical Approach: Includes core capability description, innovation elements, differentiators from existing solutions, and demonstrations, models or visual aids if needed.

1.1.28 Operational Applicability: How the solution integrates into the 21CS and CNECTS daily operational requirements, considering scalability, adaptability, and interoperability.

1.1.29 Data Rights Assertions: Identification of any Intellectual Property associated with your solution, associated restrictions on Government use, and proposed data rights consistent with R-DFARS 227 requirements.

1.1.30 Risk Assessment: Key technical, schedule, and integration risks and their associated mitigation strategies.

1.1.31 Mission Impact: Benefits to mission capabilities, decision making, and 21 CS readiness.

1.1.32 Estimated Price and Schedule: ROM value, aligned with Phase I submission, and associated assumptions along with a notional schedule for PWS development, Phase-in, and contract execution.

GOVERNMENT ROLE IN PHASE II

Evaluation: Phase II sessions will be assessed using the evaluation factors in Attachment 5 – Evaluation and Selection Process.

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

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

Selection Pathways: Following Phase II, the Government may:

Invite an Offeror to submit a Phase III Proposal.

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

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

ATTACHMENT 3: PHASE III TECHNICAL PROPOSAL & PWS

GENERAL OVERVIEW

Once the Government determines the Offeror that will be invited to Phase III, the Government reserves the right to communicate with only that Offeror regarding a submission for Phase III.

During Phase III the Government will communicate with the single Offeror regarding their final submission and address any issues as both parties work towards finalizing the requirement and a contract award.

If the parties cannot successfully negotiate a contract, as determined at the sole discretion of the Government, the Government reserves the right to invite the next apparent successful Offeror to participate in Phase III.

Once the Government has engaged with the Offeror, no further communication with the previous Offeror will be entertained until after the contract has been awarded.

This process shall continue until an agreement is successfully reached and a contract is awarded.

SUBMISSION REQUIREMENTS:

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 in Phases I and II and address the entirety of the requirement.

1.1.33 Phase III submission will include the PWS and Quality Assurance Surveillance Plan (QASP) as developed in partnership with Government Subject Matter Experts, the acquisition team, and the requirement owner.

1.1.34 Phase III will include the Cost Volume as developed and negotiated simultaneously with the PWS so that the Government and Contractor have full visibility into the risk picture associated with the expected quantity and quality of services to be provided by the contract.

1.1.35 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 as agreed upon in the PWS.

COVER SHEET REQUIREMENTS

The Cover Sheet shall contain the following:

CSO and AOI Number and AOI Title (if applicable) Full Legal Company Name and Address CAGE Code Unique Entity ID Number Business Size Classification (NAICS specified in the AOI) Socioeconomic Status (e.g., Small Business - 8(a)) Point of Contact Information – Name, Title, Phone Number, Email Address.

Date of Submission

ATTACHMENT 4: PHASED CSO PROCESS OVERVIEW

PHASE I – WHITE PAPER - 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 6 – Area of Interest and instruct them to move on to Phase II.

PHASE II – PITCH SESSION - If Phase II is utilized, the Government will review the Pitch Session content and any supplemental written material requested by the Government and make a determination as to which Offeror is most likely to have the highest potential level of success in fulfilling the requirements.

PHASE III – TECHNICAL, PWS, AND PRICE PROPOSAL - The Government will request a full proposal from the single Offeror that is determined to have the highest potential level of success and best value to the Government in fulfilling the requirements of this AOI as outlined in Attachment 6.

Proposals need not be evaluated against each other since they are not submitted in response to a common PWS.

The Government may elect to fund a portion of a proposal or fund a portion of any mix of the proposal under this CSO.

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

ATTACHMENT 5: EVALUATION AND SELECTION PROCESS

EVALUATION CRITERIA

All phase submissions will be evaluated against the following criteria. Technical Merit/Applicability and Importance to Agency Programs are of equal importance and, when combined, are more important that Price/Value.

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 operational 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 21 CS, 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.

SELECTION PROCESS

1.1.36 All Phase I submissions will be categorized as Recommended, Selectable, or Non-Selectable. Only proposals categorized as Recommended will automatically advance to the next phase. Offerors rated as Selectable may be advanced to the following Phase in the event that the initial round of pitches fail to identify a desirable candidate. Non-Selectable Offerors will not be considered further and will receive appropriate notification at the conclusion of each Phase.

1.1.37 Definition of Categorization for All Phases (as applicable):

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 submission 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: Submission may be categorized as “Selectable” if it meets the following when assessed holistically:

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 Non-Selectable: Submission may be categorized as “Non- 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

FINAL SELECTION

At the conclusion of Phase II, once the Government identifies the Offeror that is the best-suited (i.e., the apparent successful offer), the Government reserves the right to communicate with only that Offeror to finalize the requirement, address any remaining issues, if necessary, and finalize a contract with that Offeror. These issues may include minor issues with technical and price issues.

If the parties cannot successfully address any remaining issues, as determined pertinent at the sole discretion of the Government, the Government reserves the right to communicate with the next best-suited Offeror based on the original analysis and address any remaining issues.

Once the Government has begun communications with the next best-suited Offeror, no further communications with the previous Offeror will be entertained until after the contract has been awarded.

This process shall continue until an agreement is successfully reached and a contract is awarded.

2 | Page

ATTACHMENT 6 – AREA OF INTEREST (AOI)

PURPOSE

This attachment identifies the current, singular Area of Interest (AOI) available under this Commercial Solutions Opening (CSO), including its applicable status and submission deadline.

The AOI identified herein will be closed at 00:01 MST on 16 November 2026. The Government will not accept White Papers submitted in response to this AOI after this submission deadline.

PROBLEM STATEMENT

The 21 CS is facing a critical operational vulnerability. Its ability to provide uninterrupted, high-availability communication and mission command services across three geographically separated bases is fundamentally at risk due to its reliance on a highly fragmented support structure. The enterprise is currently sustained by a mix of Government civilians and multiple contractors operating under four distinct legacy contracts, each with different end dates. This has created a disjointed operational environment characterized by inconsistent processes, poor coordination, and single points of failure in manpower and expertise.

This fragmentation manifests in numerous, daily operational challenges:

Systemic Operations Failure: The contracted support currently lacks a consolidated service desk, leading to an inability to manage high ticket volumes, differentiate support across networks (N/NC, Mission, AFNET), or respond effectively to major incidents. A widespread, automated network isolation event, for example, could generate thousands of tickets that would overwhelm the current structure, as the man-hour requirement for manual software re-installation would far exceed available personnel.

Pervasive "Revolving Door" and Expertise Gaps: The 21 CS suffers from a systemic "revolving door" effect, where entry-level contractors in roles like the call center and Communications Focal Point (CFP) use their positions as stepping stones to acquire certifications and clearances, only to depart for higher-paying jobs. This creates a continuous training burden on Government personnel and leads to a constant lack of experienced technicians. This is compounded by the challenge of maintaining highly specialized knowledge for legacy mission systems for which replacement parts are no longer commercially available.

Manual and Inefficient Cybersecurity Posture: Cybersecurity processes are largely manual and fragmented. The meticulous verification of EMSEC documentation and the continuous management of configurations and permissions result in significant backlogs, delaying the deployment of secure systems and increasing the risk of non-compliance with AFCYBER TASKORDs. There is no scalable, integrated framework to manage this workload or forecast future growth.

Breakdown in Governance and Coordination: There are documented instances of mission partners and incumbent contractors circumventing established Government oversight and configuration management protocols, leading to unauthorized network alterations and unilateral decision-making. This lack of coordination extends to critical outage response, where the absence of a standardized reporting framework prevents teams from providing an accurate common operating picture to leadership, leaving critical C2 systems vulnerable to prolonged downtime.

Operational Friction and Inefficiency: Simple, day-to-day tasks are complicated by the lack of standardization. A request for a Visio license, the unexpected arrival of IT equipment for a GSU at the BECO, or a request to provide Public Address announcements into a new facility all require ad-hoc coordination across multiple work centers and contracts. Furthermore, critical life-safety systems, such as the emergency notification from the Colorado Springs Airport or the Giant Voice system, are vulnerable to single points of failure, with no clear, unified process for restoration.

Executing a massive and complex contract transition without degrading vital C2 capabilities: The incoming single, awarded prime contractor must seamlessly phase its services into this active, fragmented environment. This requires executing a rapid workforce transition to hire, clear, and onboard approximately 400 technical contractors under tight, overlapping timelines, all while ensuring the remaining Government civilians and incumbent contractors operate as a unified front to support no-fail missions.

Inability to achieve the Vision: The 21 CS envisions a future where a single, integrated partner provides a unified, proactive, and resilient communications enterprise. In this future state, a consolidated service desk uses intelligent tools to manage incidents and prioritize resources effectively. A stable, well-trained workforce is maintained through an internal, repeatable training program, reducing turnover and eliminating single points of failure. Cybersecurity is managed through a scalable, integrated framework that automates compliance and verification. Governance is strictly enforced, and innovation is incentivized. Most importantly, the transition to this new state is executed flawlessly, with zero gaps in service delivery for the critical missions that depend on it.

CONSOLIDATED AOI

The 21 CS invites Offerors to propose a holistic, single-award solution to consolidate, manage, sustain, and modernize the entire communications and Information Technology (IT) enterprise supporting missions across Peterson SFB, Schriever SFB, and Cheyenne Mountain SFS. This AOI seeks a comprehensive approach to seamlessly unify communication services and integrate critical mission systems across Peterson SFB, Schriever SFB, and the Cheyenne Mountain SFS, replacing a fragmented and high-risk multi-contract environment.

The core of this AOI is to find a partner who can execute a zero-failure contract and workforce transition while simultaneously delivering transformative improvements in service delivery, cybersecurity, and operational efficiency. The Government seeks a solution that provides not just sustainment, but a fundamental re-imagining of how IT services are managed and delivered in a complex, no-fail national security environment.

The ideal partner will present a comprehensive strategy that addresses the following interwoven capability areas as a single, integrated effort:

Seamless Enterprise & Workforce Transition: A detailed, actionable plan to recruit, hire, clear, and onboard approximately 400 technical contractor personnel under tight, overlapping timelines. This plan must guarantee zero degradation of service during the phased transition from four distinct legacy contracts with staggered end dates, ensuring uninterrupted support for critical Command and Control (C2) and mission systems. The solution must foster a unified operational culture between the incoming contractor workforce and the enduring Government civilian communication specialists.

Unified Communications Focal Point & Operations: A consolidated, standardized, and scalable support framework to effectively manage high ticket volumes across the enterprise. The solution must differentiate support requirements across distinct networks (N/NC, Mission, AFNET), provide robust incident management for emerging major incidents (e.g., mass network isolation events), and establish a clear, synchronized reporting and prioritization framework to give Government leadership a real-time insight into critical outages.

Integrated Cybersecurity & Compliance Management: A scalable, integrated framework to manage cybersecurity workload volumes, including the meticulous verification of Emission Security (EMSEC) documentation, continuous configuration monitoring, and privileged access management. The solution must include an internal, repeatable training program to maintain workforce readiness and proactively address Government compliance and cybersecurity directives (e.g., AFCYBER TASKORDs).

Legacy & Mission Systems Sustainment: A robust plan for maintaining and troubleshooting a wide array of specialized and legacy systems and their dependent analog endpoints, (fire alarms, gate intercoms) and unique mission systems. This includes providing "touch maintenance," logistics, and full configuration management of facilities.

Proactive Governance & Innovation: A management approach that actively enforces Government oversight, configuration management protocols, and contractual boundaries to prevent unauthorized network alterations. The solution must foster a culture of compliance that provides alternate solutions to systemic problems like failures to communicate and high contractor turnover in entry-level roles, moving beyond reactive, "zero-initiative" performance.

RECOMMENDED OFFERORS

Recommended Offerors’ White Papers will adequately:

Demonstrate AOI Understanding and Overall Solution Alignment:

A holistic, single-award approach to consolidate, manage, sustain, and modernize the communications and IT enterprise.

Enterprise support across Peterson SFB, Schriever SFB, and Cheyenne Mountain SFS.

The need to replace the existing fragmented, multi-contract operating environment.

How the solution integrates all capability areas as one coordinated operating model, rather than as separate CFP, cybersecurity, logistics, or staffing solutions.

How the proposed approach supports a complex, high-availability, no-fail national-security environment.

How the solution provides both:

· Immediate sustainment and continuity; and

· Transformative improvements in service delivery, cybersecurity, governance, and operational efficiency.

Provide a Zero-Degradation Enterprise and Workforce Transition Plan:

Transition from four distinct legacy contracts with staggered end dates.

Recruit, hire, clear, and onboard approximately 400 technical contractor personnel.

Execute the transition under tight and overlapping timelines.

Maintain uninterrupted support throughout transition activities.

Prevent degradation, gaps, or interruptions to critical Command and Control (C2) and mission-system support.

Identify a phased transition approach, including sequencing, milestones, decision points, and transition governance.

Explain how incoming personnel, incumbent contractors, and Government civilian communications specialists will operate as a unified team during transition.

Describe how the Offeror will establish a unified operational culture with the enduring Government civilian workforce.

Identify transition risks, including workforce availability, onboarding timing, knowledge transfer, and contract overlap, and provide mitigation measures.

Describe how mission-essential knowledge will be captured and retained before incumbent personnel depart.

Explain how the Offeror will maintain accountability, communications, escalation, and continuity during each phase of the transition.

Establish a unified Communications Focal Point and Operations Framework:

A consolidated service desk or unified communications focal point.

A standardized approach for intake, triage, tracking, routing, escalation, and closure of service requests and incidents.

The ability to manage high ticket volumes across the enterprise.

A method to differentiate support requirements across:

· N/NC networks

· Mission networks

· AFNET

A major-incident-management approach capable of responding to enterprise-scale events, including mass or automated network-isolation events that could generate thousands of tickets.

A process to prioritize mission impacts and allocate technical resources effectively during high-demand events.

A synchronized reporting and prioritization framework for critical outages.

Real-time or near-real-time status reporting for Government leadership.

Defined coordination mechanisms with Technical Control Facilities (TCFs) during outages and restoration activities.

A method to improve accuracy, timeliness, and consistency of outage reporting.

A scalable operations model that reduces reliance on ad hoc cross-work-center coordination for routine requests.

Deliver Integrated Cybersecurity and Compliance Management:

Management of cybersecurity workload volumes at enterprise scale.

Verification and management of Emission Security (EMSEC) documentation.

Continuous configuration monitoring.

Privileged-access management.

A repeatable internal training program that sustains workforce readiness.

A proactive approach to implementing Government cybersecurity and compliance directives, including AFCYBER TASKORDs.

A plan to reduce manual, fragmented cybersecurity processes and associated backlogs.

A method to improve timeliness and reliability of secure-system deployment.

A method to forecast, absorb, and manage future cybersecurity workload growth.

Defined integration between cybersecurity personnel, operations personnel, configuration managers, and mission partners.

Sustain Legacy, Specialized, and Mission Systems:

Maintenance and troubleshooting of specialized and legacy systems.

Sustainment of unique mission systems.

Support for dependent analog endpoints,…