Welcome to CNECTS Industry Day 19 August 2026

Michael Tidwell

Rosalind Davis

Austin Frindt

CAO 18 August 2026

Highest Overall Classification:

UNCLASSIFIED

Agenda

Timeline Activity Presenters

0900 0930 Welcome, Agenda, ROEs, and Introductions SAIO

0930 1030 CNECTS Requirement SAIO | 21 CS

1030 1045 Short Break

1045 1115 Risks and Challenges 21 CS | SAIO | Industry

1115 1200 CSO Process and Acquisition Strategy SAIO

1200 1215 Short Break

1215 1300 Future Schedule and Q&A 21 CS | SAIO | Industry

Rules of Engagement

Meeting is being recorded and transcribed; AI assistance may be employed in the analysis of the transcription

Microphones will be muted

Please turn off all webcams in order to conserve bandwidth

Discussion and questions are highly encouraged please place questions or comments in the chat to be addressed at the earliest available opportunity

Nothing discussed today should be construed as government direction

Online

Introductions

21st Communications Squadron Customer | Requirement Owner Dave Hluska Director

Deputy Director Andre Farr Director of Plans & Sr Liaison Officer Schriever Chad Denaughel Director of Operations & Sr Liaison Officer Peterson Jeff Ewens Director of Missions & Sr Liaison Officer Cheyenne Mountain Rita Hahn Director of Future Alignment & Acquisition

SAIO Program Management | Contracting | Quality Assurance Michael Tidwell Program Manager Rosalind Davis Contracting Officer Austin Frindt Acquisition Advisor Clint Walker Quality Assurance Program Manager

SAIO Org Chart

Katharine Weimer Director, SAIO

Terri Dyke Division Chief SAIO/PKA

Danny Cowell Division Chief, SAIO /PKO Acting PKG Division Chief

Ethel Amutan Operations Manager

B. Eric Beckstrom Legal Advisor

Bridget Sherer Division Chief, SAIO /PMO

David Donahue Division Chief, SAIO/PMG

PROGRAM MANAGEMENT DIRECTORATE

Nicole Pilato SAIO Deputy Director

Acting PMA Division Chief

Jeremy Lubbert COCO Acting Division Chief, SAIO/DRX

SAIO Org Chart CNECTS

Ms. Katharine Weimer - Director

Ms. Nicole Pilato Deputy Director -

Program Management Directorate

Ms. Bridget Sherer - PMO Division Chief

Mr. Michael Tidwell PMO Program Manager

Mr. Jeremy Lubbert

COCO

Mr. Austin Frindt DRX Acquisition Advisor

Mr. Daniel Cowell PKO Contracting Division

Chief

Ms. Rosalind Davis PKO Contracting Officer

21st Communications Squadron CNECTS Industry Day Brief

Date: 11 Mar 2026

DAVID J. HLUSKA, NH-04, DAFC

Director, 21st Communication Squadron

Overall Classification: Controlled Unclassified Information (CUI)

~50 work centers across 3 bases 10+ 24x7 work centers

Manpower 158 Civilian Billets

137 SF funded 7 funded by NORAD-USNORTHCOM 14 funded by USSPACECOM

~400-450 Contractors

4 Contracts (~400 Contractors) NISC II--SSC (Mission Comms and BOS Comms at CMSFS and some Mission Comms at PSFB) WICS II--SAIO (Mission Comms and some BOS Comms at SSFB) Encore--21 CONS (BOS Comms at PSFB and Some BOS Comms at SSFB)

Customer Support (Mission & BOS Communications) 3 Space Force Installations 111 Mission Partners

2x CCMDs

NORAD & USNORTHCOM

USSPACECOM

2x FIELDCOMs equivalents

CFC HQ

STARCOM HQ

9 Deltas (Space, Space Base, Mission)

MDA, DIA, NRO

57-125 GSUs (includes 20+ off-base facilities) Combined: ~25K users, >30K devices, >40K phone lines Support to 48 GOs/equivalent & visiting DVs

Fast Facts

CUI

CUI

Bldg 101

In the Mountain

Peterson SFBCheyenne Mountain SFS Schriever SFB

LOCATIONS

Squadron Programs Director Deputy Director (DD)

Director, Mission Support

Director (21 CS/CL)

SBD 1/CC

Director of Mission (DM) Senior Liaison Officer Cheyenne Mtn SFS

Director of Operations (DO) Senior Liaison Officer Peterson SFB

Director of Plans (DX) Senior Liaison Officer Schriever SFB

21st Communications Squadron

QA

FOIA, Records Mgt Publications Privacy Act Security Mgt

UPC

Knowledge Management

KEY

CIVILIAN

CNECTS

BIM

Director of Plans (DX)

ISSM

Plans and Resources CIV Flight Chief (SCX)Cyber Surety CIV Flight Chief (SCD)

ISSO, RMF,

COMPUSEC,

TEMPEST

COMSEC

CIV Cybersecurity Section Chief Risk Management

Authority to Operate/Authority to Connect

Negligent Discharge of Classified Information (NDCI)

CIV COMSEC Section Chief KeyMat Issuance

High Assurance Internet Protocol Encryptor (HAIPE) Compliance

Personnel Reliability Program (PRP)

CIV Plans Section Chiefs at 3 Locations Project Management

Service Catalog Plans Development/Review

GSU Support Configuration Management

CIV Resource Management Resource Advisors Contracting Officer Representatives (COR)

Functional Area Agreement Coordinator (FAAC)

Plans

Resource Mgt

Engineering Mission, GSU and Configuration

Mgmt

AFNET Engineering Network & Cable

Circuit Actions

FAB-T (Peterson)

Tech Control, SDIN, GCCS

FAB-T/SATCOM

CIV Section Chief

FAB-T/SATCOM Set-up, maintenance and operations of satellite communications

Circuit Action, Tech Control, SDIN

Circuit Actions Manages and maintains government-owned and/or leased circuits within the Global

Information Grid.

Tech Control Connects and maintains facility to facility circuitry SDIN Monitor, troubleshoot and maintenance of the local Department of Defense Information Network GCCS operates the Global Command and Control

System

FAB-T/ SATCOM

SSFB, CMSFS

Director of Mission (DM)

Secure Voice/MILSATCOM CIV Flight Chief (SCM)

Mission Comms CIV Flight Chief (SCM)

DRSN

DRSN Maintaining, troubleshooting, upgrading and installing Defense Red Switch

Network

DRSN

CIV Section Chief

CMSFS N-NC SUPPORT

N-NC

File Services/

Web/DB/Virtualization

N-NC

Network Technicians and Engineering

ISSO, RMF

N/NC

VM, CST, CFP

Director of Mission (DM)

Director of Operations (DO)

LMR

Spectrum Management

Giant Voice

Cable Mapping

CIV VM/CFP/CST/BECO

Section Chief

Vulnerability Mgmt (VM) detects.

Assess and remediates network vulnerabilities Communication Focal Point (CFP) -trouble ticket assignment/tracking, SITREP, PMI mgmt., ASI tracking/submission Client System Technician (CST) Desktop devices install/troubleshooting

(voice, NIPR/SIPR, Monitor, etc), Comm Closet to Desktop connectivity, Mission

Display, Mission Systems , Video Maintenance

Base Equipment Custodial Officer (BECO) Hardware/Software asset management Message Delivery Center (MDC)

SMART.NXT/SMART.R

CIV Cable Maintenance Section Chief

Cable Mapping Surveying and documenting cable fiber from Main Distribution Center to desktop Inside Plant (ISP) Fiber/Copper from Comm

Closet to desktop install/maintenance Outside Plant (OSP) - Fiber between buildings

Manhole Preventative Maintenance Inspections (PMI)

CIV Transmission Systems Section Chief

Land Mobile Radio (LMR) Programming and maintenance of two-way wireless communication system Giant Voice (Announcement

Towers) Preventative maintenance, trouble shooting, upgrades

Spectrum Management regulation and allocation of radio frequency spectrum

AFNET ISP/OSP

Non-AFNET ISP/OSP, Cable PMI, Antenna PMI VM

BECO, CST, CFP, MDC

CIV Communications Operations Flight Chief (SCO)

Network Maintenance Section Chief

Monitor network performance, conduct regular maintenance, troubleshoots issues, ensures optimal functionality and security

CIV Systems Admin Section Chief

File Services manages data storage servers as well as manages storage and performs file screening management Web Management management/administration and optimalization of servers that host websites and web applications DB Services Management and Maintenance of Database Servers Virtualization ensure VDI (Zero

Clients) environments run efficiently.

Deployment, management and optimizing virtual machines.

File Services/ Web/DB/Virtualization

Network Technicians

Network Monitoring & AFNET NIPRNet

Wireless

Director of Operations (DO)

CIV Network Operations Flight Chief

(SCN)

CNECTS Requirement and Legacy Contracts

Legacy PWSs and Consolidation D&F available at Sam.Gov or by request.

CNECTS Requirement

Four separate contracts require significant manpower, funding, and resources to manage

21 CS Realigning CIV leadership for all 3 sites Network admin and technicians covered

Web/Database/Virtual Desktop covered

Unclassified Voice services covered

21 CS contacted SAIO to determine feasibility of consolidation

SAIO determined that requirements across bases were similar in nature, with few outliers

SAIO issued a Consolidation Determination and Findings, which was approved by AFICC/KS in late 2025

Base Operating Support Information Technology (BOS-IT)

31 July 2027

North American Aerospace Defense Command Cheyenne Mountain Complex Integrated Tactical Warning/Attack Assessment (NCMC-ITW/AA) and Space Support Contract (NISSC)

30 November 2027

Wing Information and Communications Support (WICS II)

30 Mar 2028

Plans and Programs Engineering Design Support (PEDS)

28 June 2028

BOS-IT Historical Requirement

Supports 21 CS at Schriever and Peterson

FAB-T

Giant Voice

BECO

Client Systems Technicians (CST) Comm Focal Point NetOps/File Service/Web/DB/Virtualization Cable Shop Network Technicians Local Registration Authority (LRA) Enterprise Information Management Unclassified VoIP

BOS-IT Historical Requirement

Supports 21 CS at Schriever and Peterson

FAB-T

Giant Voice

BECO

Client Systems Technicians (CST) Comm Focal Point NetOps/File Service/Web/DB/Virtualization Cable Shop Network Technicians Local Registration Authority (LRA) Enterprise Information Management Unclassified VoIP

NISSC Historical Requirement

Supports 21 CS at CMSFS

FAB-T

Cybersecurity Giant Voice N/NC Cable Shop AFNET Cable Shop AFNET Vulnerability Management N/NC Vulnerability Management

BECO

Client Systems Technicians Comm Focal Point AFNET NetOps/File Service/Web/DB/Virtualization N/NC NetOps/File Service/Web/DB/Virtualization

Supports 21 CS at CMSFS AFNET Network Engineering AFNET Network Administration N/NC Network Engineering N/NC Network Administration Local Registration Authority (LRA) Special Security Reps (SSR) Network Operations Center (NOC) Technical Control Facility (TCF) Video Work Center Global Command and Control System (GCCS)

NISSC Historical Requirement

FAB-T

Cybersecurity Giant Voice N/NC Cable Shop AFNET Cable Shop AFNET Vulnerability Management N/NC Vulnerability Management

BECO

Client Systems Technicians Comm Focal Point AFNET NetOps/File Service/Web/DB/Virtualization N/NC NetOps/File Service/Web/DB/Virtualization

Supports 21 CS at CMSFS AFNET Network Engineering AFNET Network Administration N/NC Network Engineering N/NC Network Administration Local Registration Authority (LRA) Special Security Reps (SSR) Network Operations Center (NOC) Technical Control Facility (TCF) Video Work Center Global Command and Control System (GCCS)

NISSC Historical Requirement (contd)

Defense Red Switch Network

(DRSN)

MILSTAR

PNVC

Unclass VoIP Unclass TDM

LMR

NISSC Historical Requirement (contd)

Defense Red Switch Network

(DRSN)

MILSTAR

PNVC

Unclass VoIP Unclass TDM

LMR

WICS Historical Requirement

Supports 21 CS at Schriever SFB Global Broadcast Operations Center (GBSOC) Wideband Global Satellite

FAB-T

GCCS

SDIN

Database Power/System Safety/Operations Systems

ISSO

Technical Control Facility (TCF)

WICS Historical Requirement

Global Broadcast Operations Center (GBSOC) Wideband Global Satellite

FAB-T

GCCS

SDIN

Database Power/System Safety/Operations Systems

ISSO

Technical Control Facility (TCF)

PEDS Historical Requirement

Network Engineering Cable Engineering

PEDS Historical Requirement

Network Engineering Cable Engineering

Projected Rollout

Mission Systems Operations Space Digital Integrated Network

(SDIN)

Location: Schriever, GSUs

Classification: Secret

Ops Tempo: 24/7/365

Cybersecurity Posture: RMF

Continuity: NO FAIL

Global Command and Control System (GCCS)

Location: Schriever, CMSFS

Classification: Secret

Ops Tempo: M-F

Cybersecurity Posture: Ops

Continuity: 24 Hr Turn

Steel Pipe

Location: Schriever

Classification: Secret

Ops Tempo: 24/7/365

Interdependencies: SDIN

Continuity: NO FAIL

Modernization of Enterprise Terminals (MET) Earth Terminal

Location: Schriever, Radomes AG1 and AG2

Classification: Secret

Ops Tempo: 24/7/365

Interdependencies: DCSS

Cybersecurity Posture:

OPS/IAT Level 2

Continuity: NO FAIL

Family of Advanced BLOS Terminal (FAB-T) Command Post

Location: Schriever, FAB-T Tower, Antenna, and Radome

Classification: Secret

Ops Tempo: 24/7/365

Cybersecurity Posture: OPS, IAT Level 2

Continuity: NO FAIL

Short Break

Please return by

Risks and Challenges

Risk Considerations | Knowledge Capture

Schedule 60 to 90-Day Transition Period

Applies to each legacy requirement Base/RA Access Clearance Verification/Finalization

Cost Incumbent/Knowledge Capture

Legacy Systems/Requirements Modernization/Integration Historical Architectures

Key Personnel Requirements Still in Development Open to Input

Critical Knowledge Base AFIs DAFMANs Confined Space

Risk Consideration (contd)

Cost Risks Consolidation External Program Funding Travel Requirements Software License Management Technology Refresh/Obsolescence

Schedule Risks Contract Award Timeline Phase-in Schedule Security Clearance Processing Cybersecurity Certifications

IAT II

IAM II

CMMC 2

Confined Space Access

Risk Consideration (contd)

Performance Risks Consolidation Inefficiency CFP Consolidation Cyber RMF Compliance COMSEC Management Mission System Maintenance Cable Plant Documentation

Performance Risks Entry Level Position Retention Confined Space Project Management and Coordination IT Asset Management/Handoff DRSN Expertise Special Security Representatives

Quality Assurance and Surveillance

COR Engagement Continuity

Embedded SME Support Regular Feedback

Semi-monthly Tagups SAIO Led COR Attended CTR SME Support Recommended

Monthly Surveillance Reporting CPAR Documentation Support SAIO Managed

Quarterly Program Management Reviews (PMRs)

SAIO Led Cost Schedule Performance Risk Deliverable Staffing

Commercial Solutions Offerings (CSO) Overview and Proposed Acquisition Strategy

Please provide comments and discussion on

CSO process, white paper format, and evaluation factors during this time.

Highest Overall Classification:

CNECTS

(Communications, Network, Engineering, Cybersecurity, and Information Technology Services)

Commercial Solutions Opening (CSO) Overview

Austin Frindt

SAIO/DRX

19 August 2026

Overview

Why Now?

How do CSOs Work?

Sample Process Flow

Backup (BAA Process)

SECDEF Memo: Directing Modern Software Acquisition to Maximize Lethality, 6 March 2025

I am directing the use of Commercial Solutions Openings and Other Transactions as the default solicitation and award approaches for acquiring capabilities under the Software

Executive Order: Modernizing Defense Acquisitions And Spurring Innovation In The Defense Industrial Base, 9 April 2025 commercial solutions and a general preference for Other Transactions Authority, application of Rapid Capabilities Office policies, or any other authorities or pathways to promote streamlined acquisitions

Executive Order: Ensuring Commercial, Cost-effective Solutions In Federal Contracts, 16 April 2025 shall procure commercially available products and services

UNCLASSIFIED

UNCLASSIFIED

CSOs permanently authorized by section 803 of the FY22 NDAA (Pub. L. 117-81)

How do CSOs Work?

Definition (Austin): An open-ended, general request for good ideas

Authority: Section 803 of the FY22 NDAA provided the DoD with permanent CSO authority, codified in 10 U.S.C. 3458

Implementation: DFARS 212.70 (note commerciality)

Implications:

Competitive, Treated as Commercial, Innovative:

Any technology, process, or method, including research and development, that is new as of the date of submission of a proposal, or

Any application that is new as of the date of submission of a proposal of a technology, process, or method existing as of such date.

Similar to

How do CSOs Work?

UNCLASSIFIED

UNCLASSIFIEDDFARS: Defense Federal Acquisition Regulation Supplement

A CSO is a solicitation method, not a contract

Meets CICA requirement for competition if CSO (DFARS 212.7004(a)(3)):

Describes the evaluation factors for selecting proposals to include

Technical and importance to agency programs as the primary evaluation factors;

Price to the extent appropriate, but at a minimum to determine that the price is fair and reasonable; and

Relative importance of the factors, and

The method of evaluation

How do CSOs Work?

UNCLASSIFIED

UNCLASSIFIED

CICA: Competition in Contracting Act DFARS: Defense Federal Acquisition Regulation Supplement

Proposals not evaluated against each other since they are not submitted in response to a common PWS [DFARS 212.7004(c)]

10 USC 3458(c)(3):

Notwithstanding [the definition of commerciality in FAR 2] products and services acquired using the authority under subsection (a) shall be treated as commercial products and commercial services. [Implemented by DFARS 212.7002(c)]

Key implications of commercial contract:

No approved accounting system required No Cost Accounting Standards (CAS) No certified cost or pricing data Fixed-price type contracts Extremely limited set of clauses are included

How do CSOs Work? (cont.)

UNCLASSIFIED

Streamlined measures meant to make contracting with the Government easier

DFARS: Defense FAR Supplement, FAR: Federal Acquisition Regulation, USC: United States Code

Similar method to Broad Agency Announcements (BAAs) BAAs were a successful and proven method, but only applied to R&D (more on BAAs in backup)

CSOs offer even greater flexibility than BAAs

Contracts awarded from CSOs are always considered commercial Results in Fixed-Price type contracts Meant to attract non-traditional defense contractors May use all types of funds, including O&M

CSO blends flexibility of BAA with streamlined procedures of commercial

How do CSOs Work? (cont.)

Develop Areas of Interest / Problem Statement Conduct Market Research Acquisition Planning / Clearance

Issue Solicitation (Post CSO)

Evaluate white papers or proposals / invite bidders to pitch

Select solution(s)/request proposal/Negotiate Notify unsuccessful offerors

Award ContractAward

Note: Steps 1-4 are iterative and can blend and/or overlap

Satisfied Competition

How do CSOs Work? (cont.)

UNCLASSIFIED

We are here

Step 1: Develop Areas of Interest (AOIs) Meet with operators/users/functional experts/subject matter experts etc. to identify need, capability gap, or area for solution

Step 2: Conduct Market Research (MR) MR may look different than for a traditional contract. Focus should be on what is missing rather than what is known

Step 3: Conduct Acquisition Planning Determine if CSO should be One-Step/Two-Step, Open/Closed/Staggered Closed, Basic with Calls, or should include Pitch Days.

How do CSOs Work? (cont.)

UNCLASSIFIED

Step 4: Obtain Clearance Clearance requirements still apply to CSOs

Step 5: Issue Solicitation (Post CSO) Competition requirements of FAR 6 have been met

Step 6: Evaluate White Papers and/or Proposals Must be reviewed by Government technical experts Must be evaluated IAW terms of the CSO Primary evaluation factors shall always be:

Technical, Importance to agency programs, Funds availability

How do CSOs Work? (cont.)

UNCLASSIFIED

SATISFIED Competition

Step 7: Select Solution(s)/Request Proposal/Negotiate Categorize White Papers Government may award all, some, or none of a proposed solution (portions of it has funding for ONE award is anticipated for CNECTS

The offeror with the White Paper that offers the most promising solution based on the eval criteria, as determined by the subjective judgment of the SME review board, will be issued an RFP

If a negotiated agreement can be reached at a fair and reasonable price, that offeror will win the award Otherwise, the process moves to the next most promising solution

How do CSOs Work? (cont.)

UNCLASSIFIED

RFP: Request For Proposal, SME: Subject Matter Expert

Step 8: Notify Offerors Notify offerors of results of White Paper evaluation results

Offerors with White Papers will be eliminated from the competition Offerors with White Papers will be held and issued an RFP only if no awards result

Step 9: Award Contract If over $100M, SAE approval and Congressional notification is required

Delegated to SCO (DAFFARS MP5301.601(a)(i), line 56)

How do CSOs Work? (cont.)

UNCLASSIFIED

DAFFARS: Department of the Air Force Federal Acquisition Regulation Supplement MP: Mandatory Procedures SAE: Senior Acquisition Executive SCO: Senior Contracting Official

The offeror with the White Paper that offers the most promising solution, as determined by the subjective judgment of the SME review board, will be issued a Request for Proposal (RFP)

CSO

WP

AOI

Proposal

CNECTS is anticipated to be a Two-Step, Closed CSO, with one awardee:

Two-Step:

Negotiate/ Award Contract

How do CSOs Work? (cont.)

UNCLASSIFIED

UNCLASSIFIED

Step One White Papers

Step Two Proposal

AOI will consist of desired CNECTS services as illustrated in

Note, the final CSO is likely to contain an

Competitive procedure under FAR 6.101 and DFARS 206.101-70(b) (RFO)

All products/services are treated as commercial notwithstanding the definition under FAR Subpart 2.101

Authority from DFARS 212.70 used in conjunction with FAR part 12 procedures

Primary evaluation factors are technical, importance to agency needs and funds availability

Does not require the use of DoD Source Selection Procedures

Limited to Fixed Price contract types, including FPIF

Evaluated through SME review

How do CSOs Work? (cont.)

UNCLASSIFIED

FAR: Federal Acquisition Regulation FPIF: Fixed Price Incentive (Firm Target), RFO: Revolutionary FAR Overhaul, SME: Subject Matter Expert

Recap:

CNECTS is anticipated to be a Two-Step, Closed CSO, with one award to the

How do CSOs Work?

UNCLASSIFIED

Legal Review DAFFARS 5301.602- 2 Abbre via tions

Clearance DAFFARS 5301.90 AoI Area of Interest CAA Clearance Approval Authority

Debriefs FAR 15.505, 506 CS O Commercial Solutions Opening SADA Services Acquisition Decision Authority (DAFI 63- 138 para 2.5)

SAIO Commercial Solutions Openings Process Map

START

STOP

(Goal: 60-90 days from White Paper receipt to Contract Award)

BUSINESS/

CONTRACT

CLEARANCE

CSO

PRE-AWARD

TRAINING

MARKET

RESEARCH

RAD

REQUEST

PROPOSAL(S)

EVALUATE

PROPOSAL(S)

BUCKETIZE

RESPONSES

EVALUATE WHITE

PAPERS

If necessary

DFARS 212.70 - Defense Commercial Solutions Openings

BUSINESS

CLEARANCE

RECEIVE WHITE

PAPERS

POST CSO

Approval by CAA to Issue CSO

SCO APPROVAL and

CONGRESSIONAL

NOTIFICATION

(If over $100M)

AWARD

CONTRACT(S)

LEGAL REVIEW

FORM THE TEAM/

ESTABLISH MFT

(Goal: 90-120 days from identification of need to Business Clearance)

POST-AWARD

DEBRIEFINGS

Conditional contract clearance if negotiating

NEGOTIATE LEGAL REVIEW

ACQUISTION PLAN

PREPARE

CSO/AoIs

SADA

DETERMINATION

TO REQUEST

PROPOSAL(S)

CNECTS CSO Approach

Contract Type Considerations Fixed-price contract structure required Potential incentive fee on select CLINs under consideration Contract type designed to balance risk between government and contractor Specific contract type and CLIN structure will be negotiated with selected offeror

CNECTS CSO Approach (contd)

Preliminary Submission Requirements White paper submission anticipated as initial phase Format, length, and content requirements under development

Market Research indicates 7 pages as the preferred length Updated draft CSO will be made available on SAM.gov

Potential for oral pitches and/or capability demonstrations Pitches and/or capability demonstrations should be technical in nature, focusing on proven capability Government may present a series of historical scenarios for industry to respond to as part of the capability demonstration in real time

Food for Thought

Fixed Price Contract Type and Structure Is firm-fixed-price appropriate for all service areas, or should some CLINs be structured differently?

Which CLINs or service areas would benefit from incentive fee structures?

What performance metrics should drive incentive fee determinations?

How should the contract accommodate technology refresh and modernization over the period of performance?

What flexibility mechanisms would support evolving mission requirements?

Food for Thought (contd)

Teaming and Subcontracting How does the closed CSO approach impact teaming arrangements?

What timeline is needed to finalize teaming agreements prior to submission?

Are there small business teaming considerations we should address?

Short Break

Please return by

Draft AOI and Problem Statement

Consolidated Area of Interest (AOI): CNECTS

The 21st Communications Squadron (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 Space Force Station (CMSFS), replacing a fragmented and high-risk multi-contract environment.

Consolidated Area of Interest (AOI): CNECTS

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 common operating picture during 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.

Detailed Problem Statement:

The 21st Communications Squadron (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 enterprise suffers from a systemic "revolving door" effect, where entry-level contractors in roles like the call center and help desk 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 Technical Control Facilities (TCFs) 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.

The core of the immediate problem is executing a massive and complex contract transition without degrading vital C2 capabilities.

The incoming single-award 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.

The 21st 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.

CNECTS Milestones

Virtual Industry Day August 19th

Virtual Industry Day 1:1s August 20th September 1st

Contact Michael Tidwell or Rosalind Davis to schedule Limited to 30 Minutes

Draft CSO Release 15 September Acquisition Plan Finalized 1 October CSO Release 15 October Initial Submission Due 1 December Selection Complete and Proposal Request 4 January 2027 Target Negotiations Complete 15 April SADA Signed ADM 1 May Award 15 May Phase In Begins (Assuming 60-day Transition) 1 June 2027 Full Performance Begins 1 August 2027

CLASSIFICATION

CLASSIFICATION MARKING

Questions, Comments, Concerns, Discussion?

Thank you for attending CNECTS Industry Day

Hosted by the Space Acquisition and Integration Office Michael S. Tidwell Program Manager Rosalind Y. Davis Contracting Officer Austin Frindt Acquisition Instructor

CLASSIFICATION

CLASSIFICATION MARKING

Backup

Broad Agency Announcement (BAA) Easier to understand CSOs if we first understand BAAs

Broad Agency Announcement (BAA) (FAR 35.016): Competitive selection of basic and applied research and that part of development not related to the development of a specific system or hardware procurement

A BAA is general in nature identifying areas of research interest, including criteria for selecting proposals, and soliciting the participation

Requires a peer or scientific review as a method of evaluation The BAA technique shall only be used when meaningful proposals with varying technical/scientific approaches can be reasonably anticipated.

Explanation

BAAs may be Open, Closed, or a combination thereof:

Open years (must be updated annually) White papers and/or proposals may be submitted at any time within the open period

Closed The BAA has a fixed closing date and white papers and/or proposals will only be accepted if received before the closing date (late proposal rules generally apply)

The BAA has a fixed closing date, but also allows for proposals/white papers after the closing date; however, the funding of proposals received after the closing date is significantly reduced (late proposal rules do not apply)

Explanation (cont.)

A basic BAA is published, containing overarching information, serving as a framework for identifying the technical areas and giving the basic terms and administrative information Requests for white papers and/or proposals are transmitted via Calls that are published separately from the basic BAA at various times during the open period of the basic BAA

Similar in concept to IDIQ contracts and BPAs

Explanation (cont.)

BAAs may be One-Step or Two-Step:

One-step BAA explains how proposals will be evaluated

1) Proposals (full technical and cost) are submitted by each offeror.

The proposals are reviewed in accordance with the solicitation criteria and all, some, or none selected for award

Two-Step BAA explains how white papers will be reviewed and evaluated and how proposals will be evaluated, if requested

1) White Papers containing a proposed technical approach and rough order of magnitude (ROM) are submitted by each offeror

2) Proposals (full technical and cost) may be submitted by offerors with favorably evaluated white papers

Proposals are reviewed in same manner as One-step

Explanation (cont.)

White Papers Scientific Technical experts will review the white paper to determine its overall technical value and interest to the Government Offerors that submitted white papers found to be of interest may be requested to submit formal technical and cost proposals by a specific date

Proposals Scientific Technical experts will review the proposal in accordance with criteria specified in the BAA or Call Proposals are reviewed solely on the criteria published in the BAA.

The proposal must stand on its own merits as submitted

Evaluation

Proposals will be categorized as either Selectable or Not Selectable Selectable

Proposals are recommended for acceptance if sufficient funding is available

Not Selectable Even if sufficient funding existed, the proposal should not be funded

Remember: the Government reserves the right to award some, all, or none of a proposal

When only some of the proposal is desired, the selected part may be categorized as Selectable, though the overall proposal may be categorized as Not Selectable

The Government may make as many awards as it has funding for

Award

Awards from a BAA may result in a non-FAR-

Grant Cooperative Agreement (CA) Other Transaction (OT) for Research Technology Investment Agreement (TIA)

Assistance Instruments are appropriate when the goal is to accomplish a public purpose A FAR-based contract is appropriate when the goal is to purchase goods or services for the direct benefit of the government Thus, BAAs are typically posted at both Grants.gov and SAM.gov (GPE)

Contracts and Assistance Instruments

Differences Between CSOs and BAAs (cont.)

Similarities

Competitive procedure under FAR 6.101 (RFO) Meaningful proposals with varying technical/scientific approaches can be reasonably anticipated Many variations: closed, open, closed/open with one or two step procedures Can result in the award of a contract or OT as long as specified in solicitation Does not require the use of DoD Source Selection Procedures Evaluated through Peer or Scientific Review Primary evaluation factors are technical, importance to agency needs and funds availability

CSO BAA

Differences Between CSOs and BAAs

Differences

All products/services are treated as commercial notwithstanding the definition under FAR Subpart 2.101

All funding types, including O&M, may be used

Limited to Fixed Price contract types, including FPIF

Use Part 12 procedures in conjunction with FAR Part 35 when procuring R&D

No Commercial Item Determination is required

May award a grant or cooperative agreement

May exceed $100M without SPE Approval

CSO BAA

X

X X

X

X X (OTs okay) X