W E P U T T H E “ A C E ” I N S P A C E

Welcome to CNECTS Industry Day 11 March 2026

Michael Tidwell Rosalind Davis Austin Frindt

CAO 11 March 2026

Highest Overall Classification:

UNCLASSIFIED

Agenda Timeline Activity Presenters

0915 – 0945 Welcome, Agenda, ROEs, and Introductions SAIO

0945 – 1100 CNECTS Requirement SAIO | 21 CS

1100 – 1115 Short Break

1115 – 1145 Risks and Challenges 21 CS | SAIO | Industry

1145 – 1215 CSO Process and Acquisition Strategy SAIO

1215 – 1345 Break for Lunch

1345 – 1430 BIM Impact Discussion 21 CS | SAIO | Industry

1430 – 1500 Milestones and Future Engagement SAIO

Rules of Engagement

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

• Cell phones on silent

• Discussion and questions are highly encouraged

• Nothing discussed today should be construed as government direction

• SAIO is currently entertaining 30-minute one-to-one meetings with industry upon request

• All dates and requirements discussed are subject to change

In-Person

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

• Michael “Micky” Hovenkamp – Deputy Director

• Andre Farr – Director of Plans & Sr Liaison Officer Schriever

• Chad Denaughel – Director of Operations & Sr Liaison Officer Peterson

• Rita Hahn – Director of Missions & Sr Liaison Officer Cheyenne Mountain

• 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

Scott Brindus Division Chief, SAIO /PKG

Terri Dyke Division Chief SAIO/PKA

Danny Cowell Division Chief, SAIO /PKO

Ethel Amutan Operations Manager

B. Eric Beckstrom Legal Advisor

Johnathon Masters Division Chief, SAIO /PMA

David Donahue Division Chief, SAIO/PMG

PROGRAM MANAGEMENT DIRECTORATE

Nicole Pilato – SAIO Deputy Director

Acting PMO Division Chief

Jeremy Lubbert – ACTING COCO Division Chief, SAIO/DRX

SAIO Org Chart – CNECTS Ms. Katharine Weimer -

Director

Ms. Nicole Pilato – Deputy Director - Program

Management Directorate Acting PMO Division Chief

VACANT - PMO Division Chief

Mr. Michael Tidwell – PMO Program Manager

Mr. Jeremy Lubbert – Acting COCO

DRX Division Chief

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

• 8 Officer Billets

• 29 Enlisted Billets

• 174 Civilian Billets

• 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)

• PEDS—50 CONS (Engineering for 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

Director of Plans (DX)

ISSM

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

ISSO, RMF,

COMPUSEC,

TEMPEST

COMSEC

Cybersecurity Risk Management

Authority to Operate/Authority to Connect “Wing” IA Programs

Negligent Discharge of Classified Information (NDCI)

COMSEC

KeyMat Issuance

High Assurance Internet Protocol Encryptor (HAIPE) Compliance

Personnel Reliability Program (PRP)

Plans Project Management

Service Catalog Plans Development/Review

GSU Support Configuration Management

Resource Management Resource Advisors

Contracting Officer Representatives (COR) Functional Area Agreement Coordinator (FAAC)

Engineering Services Network and Cable Engineering

Plans

Resource Mgt

Engineering Mission, GSU and Configuration

Mgmt

AFNET Engineering Network & Cable

Circuit Actions FAB-T (Peterson)

Tech Control, SDIN

FAB-T/SATCOM, DRSN, GCCS

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

DRSN – Maintaining, troubleshooting, upgrading and installing Defense Red Switch

Network

GCCS – operates the Global Command and Control System

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

FAB-T/ SATCOM, GCCS,

DRSN

Director of Mission (DM)

Mission Comms Flight

(SCM)

Systems Center

Ensures 99.999% uptime for ITW/AA correlation center nodes

Maintain mission processors and circuits for SDA Mission

Focal point for NORAD and USSC missions

Test Control

Safeguards operational ITW/AA mission from anomalous test data

Safeguards operational SDA mission from anomalous test data

Systems Center Flight

(SCP)

Test Control Flight

(SCJ)

Systems Center Test Control

Director of Operations (DO)

LMR

Spectrum Management

Giant Voice

Cable Mapping

VM/CFP/CST/BECO

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

Cable Maintenance

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)

Transmission Systems

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

Network Maintenance

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

Systems Admin Section

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) Cont.

CMSFS N-NC SUPPORT

N-NC

File Services/

Web/DB/Virtualization

N-NC

Network Technicians and Engineering

ISSO, RMF

N/NC

VM, CST, CFP

CNECTS Requirement and Legacy Contracts

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

21 CS Requirement History

• Early 2000s

• Office of Management and Budget (OMB) Circular A-76

• Gov vs CTR cost comparison

• CTR determined “best value”

• 48% RIF

• 2009

• Resource Management Decision (RMD) 802

• Government Contract Reform

• Dep SecDef issued contract insourcing

• 21 and 50 Communications Squadron insource

• 20% RIF

21 CS Requirement History (contd)

• 2011

• Budget Control Act of 2011 – Gov wide sequestration

• Reduce Gov manpower to 2010 levels

• Insourced billets from RMD 802 cut

• 21CS/50CS left with no CTR support and limited CIV staff

• Limited MIL billets realigned to augment losses

• 21CS and 21SW realigned leaving 25% overall staffing

• 2020

• SBD6 Established

• MIL Billets converted to Cyber Defense

• MIL Communications Squadron support outsourced to CTR

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

NISSC Historical Requirement

• Supports 21 CS at CMSFS

• FAB-T

• Cybersecurity

• Giant Voice

• Cable Shop

• Vulnerability Management

• BECO

• Client Systems Technicians

• Comm Focal Point

• NetOps/File

Service/Web/DB/Virtualization

• Supports 21 CS at CMSFS

• Network Engineering

• 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)

• Supports 21 CS at CMSFS

• Defense Red Switch Network (DRSN)

• MILSTAR

• PNVC

• Unclass VoIP

• Unclass TDM

• LMR

• Circuit Actions

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)

• Circuit Actions

PEDS Historical Requirement

• Supports 21 CS at Cheyenne Mountain SFS

• Network Engineering

• Cable Engineering

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 10:40

Risks and Challenges

Industry risk will be covered during the CSO discussion.

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.

CNECTS

(Communications, Network, Engineering, Cybersecurity, and

Information Technology Services) Commercial Solutions Opening

(CSO) Overview

Austin Frindt

SAIO/DRX

11 March 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

• “Effective immediately... 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 Acquisition Pathway.”

• Executive Order: Modernizing Defense Acquisitions And Spurring Innovation In The Defense Industrial Base, 9 April 2025

• “Incorporate… a first preference for 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 under the Adaptative Acquisition Framework.”

• Executive Order: Ensuring Commercial, Cost-effective Solutions In Federal Contracts, 16 April 2025

• “It is the policy of my Administration that agencies shall procure commercially available products and services, including those that can be modified to fill agencies’ needs, to the maximum extent practicable.”

UNCLASSIFIED

UNCLASSIFIED

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

Why Now?

• 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 “Thumbtack” App

How do CSOs Work?

UNCLASSIFIED

UNCLASSIFIEDDFARS: Defense Federal Acquisition Regulation Supplement

A CSO is a solicitation method, not a contract https://uscode.house.gov/view.xhtml?req=(title:10%20section:3458%20edition:prelim)%20OR%20(granuleid:USC-prelim-title10-section3458)&f=treesort&edition=prelim&num=0&jumpTo=true https://uscode.house.gov/view.xhtml?req=(title:10%20section:3458%20edition:prelim)%20OR%20(granuleid:USC-prelim-title10-section3458)&f=treesort&edition=prelim&num=0&jumpTo=true https://uscode.house.gov/view.xhtml?req=(title:10%20section:3458%20edition:prelim)%20OR%20(granuleid:USC-prelim-title10-section3458)&f=treesort&edition=prelim&num=0&jumpTo=true

• 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 “Changes” clauses

• 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

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, should include Pitch Days, or will result in contract or Other Transaction (or the option for both/either)*

*More info available in backup slides

How do CSOs Work? (cont.)

UNCLASSIFIED

We are here

• 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 as “Recommended,” “Selectable,” or “Not Selectable”

• Government may award all, some, or none of a proposed solution (portions of an otherwise “Not Selectable” proposal may be awarded)

• Government may award as many “Recommended” or “Selectable” proposals as it has funding for

• ONE award is anticipated for CNECTS

• The offeror with the “Recommended” 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 “Not Selectable” White Papers will be eliminated from the competition

• Offerors with “Selectable” White Papers will be held and issued an RFP only if no awards result from “Recommended” White Papers

• 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 “Recommended” 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

Satisfied C om petition

How do CSOs Work? (cont.)

UNCLASSIFIED

UNCLASSIFIED

Step One – White Papers

Step Two – Proposal

AOI will consist of desired CNECTS services as illustrated in WBS and Bidders’ Library info

Note, the final CSO may contain an optional “pitch” in between steps one and two (at the Government’s discretion)

• 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 offeror with most promising “Recommended” White Paper

• How do CSOs Work?

Sample Process Flow

UNCLASSIFIED

Legal Review DAFFARS 5301.602-2 Abbreviations

Clearance DAFFARS 5301.90 AoI Area of Interest CAA Clearance Approval Authority

Debriefs FAR 15.505, 506 CSO 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)

We are here

CNECTS CSO Approach (contd)

• Contract Type Considerations

• Fixed-price contract structure anticipated

• Potential incentive fee on select CLINs under consideration

• Contract type designed to balance risk between government and contractor

• Seeking industry feedback on contract type approach and incentive structures

CNECTS CSO Approach (contd)

• Preliminary Submission Requirements

• White paper submission anticipated as initial phase

• Format, length, and content requirements under development

• Potential for oral pitches and/or capability demonstrations

• Seeking industry input on optimal submission approach

Areas for Industry Input

• White Paper Format and Content

• What is the optimal page length for white papers to adequately convey your approach?

• What content areas should be required vs optional?

• Should white papers be structured by WBS element, functional area, location, or integrated narrative?

• What attachments or supplementary materials should be permitted?

• Are there formatting standards that facilitate or hinder your ability to respond effectively?

Areas for Industry Input (contd)

• Oral Presentations and Demonstrations

• Would a "Pitch Day" format be effective for this requirement?

• What is the optimal duration for oral pitches?

• Should oral pitches focus on technical approach, key personnel, or both?

• Would live or recorded capability demonstrations add value to the evaluation?

• What demonstration scenarios would best showcase your capabilities?

• Should demonstrations be conducted at contractor facilities, government facilities, or virtually?

• 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?

• Industry Risk Consideration

• What risks do you foresee from the contractor perspective?

• What risks should the government be aware of in structuring this acquisition?

• How can the CSO process be structured to mitigate identified risks?

• Are there transition risks that should be specifically addressed?

• What market conditions may impact pricing or performance?

• Period of Performance

• What transition period and option period structure is optimal for this requirement?

• How does period of performance impact your ability to invest in innovation and modernization?

• Are there considerations for phase-in/phase-out periods?

• 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?

Discussion Questions

• Open Forum

• What aspects of the CSO process require additional clarification?

• Are there barriers to participation that we should address?

• What additional information would help you prepare the most competitive response?

• How can we structure the evaluation to best assess your capabilities?

• What lessons learned from other CSO procurements should we consider?

Break for Lunch

Please return by 1345

Base Infrastructure Modernization

Please provide comments and discussion on BIM experiences and information during this time.

TASK ORDER 3 Town Hall 13/15 January 2026

Introductions and Program

March 16, 2026 67Base Infrastructure Modernization |

Government Points of Contact Who we are

CUI

BIM Program Management Office -- AFLCMC/HNIB -- PEO Cyber & Networks (C&N)

Base Area Network (BAN) Program Manager: Wayne Anderson Task Order 3 Program Manager: Capt Joshua Souza Deputy Program Manager: Celine Lizotte

Contract Officer: Capt Nancy Bahnasy Contract Specialist: Terri Rutkiewicz

Primary COR: Capt Joshua Souza Deputy COR: Katie Poole

BIM Task Order 3 Contractor: CACI, Inc.

Contractor Program Manager: John Wall

BIM is an enterprise-wide effort in the Connect Portfolio seeking to bring existing Air Force Information Network (AFIN) Infrastructure (Classified and Unclassified) into the 21st Century by providing critical IT updates.

Transitioning from current Government Owned Government Operated (GOGO) NIPR and SIPR networks to Government Owned Contractor Operated (GOCO).

Bottom Line Up Front

SCOPE & SERVICES

March 16, 2026 70Base Infrastructure Modernization |

BIM Services – Vendor AOR

End User Devices2 Base Area Network LONG HAUL

Notes:

1. NIPRNet IL5

2. Unit Funded

3. NIPRNet/SIPRNet

BAN – Base Area Network BIM – Base Infrastructure Modernization BoD – Bandwidth on Demand BYOAD – Bring Your Own Approved Device CEDC – Component Enterprise Data Center COPE – Corporately Owned, Personally Enabled DoDIN – DOD Intranet EBN – Edge Building Node EUS – End User Service GFE – Government Furnished Equipment GSU – Geographically Separated Unit IoT/IIoT – Internet of Things/ Industrial Internet of things ISN – Installation Services

Node ITSM – IT Service Management ITB – Information Transfer Building NIPRNet/SIPRNet – Non- Secure Internet Protocol Router Network/Secure Internet Protocol Router RRE – Risk Reduction Effort SDP – Service Delivery Point TDC – Theater Deployable Comm UEM – Unified Endpoint Management VOIP/VoSIP – Voice Over Internet Protocol/ Voice Secure Internet Protocol WiFi – Wireless Fidelity ZT – Zero Trust

ITSM Platform: discovery, cyber security, IT planning, system integration, testing/evaluation, analysis/guidance, software mgmt, systems administration, hardware/software procurement, software configuration, architecture infrastructure mgmt., system mgmt, configuration mgmt database, data analytics

VoIP/VoSIPIoT/IIOT

GSUs

CEDC or ISN

TDC

Provider/Edge Router

ZT Gateway

Wave 11

ITSM & UEM

Storefront

Print

EUS

DoDIN

BIM3

SDP

Router

ITB/EBN Inside/Outside PlantWall Plates

Routers/Switches

Network Distribution

Provides the optimal combination of wired and/or wireless infrastructure to connect users to on- and off-premise enterprise services.

Inside and Outside Plant (I/OSP) Infrastructure

Maximize Wireless Across Installations

Wired BAN Infrastructure per Mission Requirements

Base Perimeter

Provides prioritized transport for maximum data throughput and optimized user bandwidth consumption

Software-defined BAN to Streamline Management Functions

Network Addressing & Translation (IPv6)

Monitoring Metrics

“First 400 FEET”

March 16, 2026Controlled Unclassified Information (CUI) 71Base Infrastructure Modernization | |

Crosswalk: Comm Sq & BIM Services

SQUADRON BASE OPERATIONS FLIGHT

LMRs

Marquee Management

Tech Control

Network Management / Infrastructure

Network Operations

Inside Plant / Outside Plant Cable Infrastructure

Voice Operations and Infrastructure

Continuity Of Operations (COOP)

PA System

JWICS Support

Giant Voice

Ground Radio

CAT/EOC Support

Service Desk – Remote (NIPR/SIPR) / Comms Focal Point

(CFP)

IT Asset Management

Device Management / CST

Vulnerability Management

Exec/VIP Support

Mobile Devices / PWCS

Telephone Devices and User Support (User Focused)

Telephone Operators

VTC Operations (NIPR/SIPR)

Network Distribution

Network Availability & ITSM

Network Distribution

Network Distribution

• BIM Vendor will provide systems configuration, switching, routing, and data transport services and equipment for black core, unclassified, and secret-level networks.

• Comm Squadron will provide network operations for mission systems as required.

Network Distribution• BIM Vendor will comply with base COOP and disaster recovery plan; even during wartime.

• Comm Squadron will build and maintain the COOP plan, directing the on and off boarding of capabilities as required.

• BIM Vendor will integrate BAN solution with existing telephony and maintain copper and upgrade to fiber as required.

• Comm Squadron will continue to provide telephony services by maintaining and upgrading equipment as required.

• BIM Vendor will be only implementing ISP/OSP for the relevant implementations under BIM.

• Comm Squadron will no longer be required to provide this service for AFNET.

• BIM Vendor will monitor, manage, and respond to alerts on their network’s availability and performance for black core, unclassified, and secret-level networks.

• Comm Squadron will monitor, manage, and respond to alerts on functional and mission systems as required.

SPECIAL MISSION FLIGHT

SATCOM (Systems, Nodes, Antennas and Radios)

Coalition, Mission Networks and PMO Systems

Special Mission

Expeditionary Comms

Mission Defense Teams

SQUADRON LEADERSHIP

Commander, Deputy, & Flight Leadership

Command Support Staff

Administrative Support Staff(s)

PLANNING & SUPPORT FLIGHT

Publications

Quality Assurance

Resource Advisor

Knowledge Management

FOIA/PII/Records Management

Frequency Management

Comms planning

COMSEC

Software License Management

Wing Cyber Security Office/Information Assurance

CURRENT COMM SQUADRON

FUNCTIONS

BIM VENDOR

SERVICES

EXPECTED IMPACT TO COMM SQUADRON FUNCTIONS

IM

P

A C

T

IM

P

A C

T

IM

P

A C

T

IM

P

A C

T

IM

P

A C

T

All services are for NIPR & SIPR domains, though implementation may not be simultaneous (IAW EITaaS PCD)

Network Operations

March 16, 2026 72Base Infrastructure Modernization |

Comm Squadron, BIM Vendor & 16th AF R&R Model

The BIM Concept of Operations outlines the responsibilities of key parties, to include Comm Squadrons and the enterprise vendor.

*Requires BIM vendor support/participation, but Comm Sqdn is OPR *GSUs 1067 process through MAJCOM

Comm Squadron Will Execute…

• On-Premise Services, Clouds & Applications

• POTS, VoIP, and Cloud-hosted Telephony Systems

• Tactical Systems and Simulators for Training or Mission Planning Purposes

• Mission Systems/Networks and ATO Process

• BAN Risk Management Framework*

• GSUs out of scope for BIM*

16th Air Force Will Execute…

• Operations of Base Boundary

• Cyber Security CONEMP updates

• Support Delivery of EIT Services

• Enforce Network Security Requirements

• Enterprise-Wide Cyber Risk Management

• Data Analysis of Captured Network Data

• Provide SMEs to Support Strategy, Design and Transition

BIM Vendor Will Execute…

All services are for NIPR & SIPR domains, though implementation may not be simultaneous (IAW EITaaS PCD)

BIM Vendor will execute to SLAs for the following scope:

• Fiber Infrastructure (ISP/OSP)

• Holistic Wired & Wireless Across Installations

• Bandwidth Scalability

• On-Site Service Restoration

• Network Health and Performance Monitoring

• Risk Management Framework Artifacts

BIM at 21 CS

March 16, 2026Controlled Unclassified Information (CUI) 74Base Infrastructure Modernization | |

• 21st Communications Squadron Civilian Personnel will provide all support to the base and its customers through the administration of both the legacy BITI network and the modernized network.

• As the BIM TO3 vendor CACI will maintain the ability to provide this support if required.

• The BIM TO3 vendor CACI will provide a modernized solution to replace the current network at Peterson SFB, Schriever SFB, and Cheyenne Mountain SFS to include hardware, maintenance systems, and ISP/OSP cable infrastructure.

• The BIM TO3 vendor CACI will provide support to the 21st Communications Squadron through the development patches and changes to be deployed on modernized hardware.

• The 21st Communications Squadron will utilize these patches and changes to keep hardware and systems operational and within compliance.

Augmented Support

March 16, 2026Controlled Unclassified Information (CUI) 75Base Infrastructure Modernization | |

• The BIM TO3 vendor CACI is a partner in the greater 21st Communication Squadron team. The BIM TO3 PMO expects CACI to be responsive and provide support as needed to all stakeholders aboard Peterson SFB, Schriever SFB, and Cheyenne Mountain SFS to include all current and future contractors.

• BIM TO3 has 2 government site leads provided by the 21st Communication Squadron as well as technical points of contact from each site. This team can provide insight into the work being done at the site and will aid in communication with the BIM TO3 PMO and CACI.

• CACI has a local site lead who can provide any support and guidance on the BIM TO3 scope of work and current tasks at any time.

Communication

CNECTS Milestones• Industry Day – March 11th

• Industry Day 1:1s – March 12th – 1 April

• Contact Michael Tidwell or Rosalind Davis to schedule

• Limited to 30 Minutes

• Draft CSO Release – 23 March

• Acquisition Plan Finalized – 1 May

• CSO Release – 1 June

• Initial Submission Due – 15 July

• Selection Complete and Proposal Request – 1 August

• Target Negotiations Complete – 31 October

• SADA Signed ADM – 20 November

• Award – 1 December

• Phase In Begins (Assuming 60-day Transition) – 1 June 2027

• Full Performance Begins – 1 August 2027

CNECTS Engagement Opportunities

• SAIO will continue 1:1 engagements until 1 April

• Draft CSO release

• Provide feedback on submission, evaluation, and proposal structure and format

• Provide feedback on final CLIN structure

• Provide feedback on opportunities for government clarification

• Potential future RFIs to streamline acquisition strategy

• Questions may be sent directly to the acquisition team

• Answers to consolidated Q&As will be posted to SAM.gov

Projected Rollout

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 of all offerors capable of satisfying the Government’s needs

• 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

• The BAA is “open” for an extended period, generally one to five 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)

• “Staggered-Closed”

• 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

Explanation (cont.)

• BAAs may be general in nature and have “Calls”:

• 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

• The basic BAA is usually “open,” and the Calls are usually “Closed” or “Staggered-Closed”

• 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 of an offeror’s proposal may be 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 and/or Proposals are “Peer Reviewed”

• 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-based “assistant instrument” rather than a contract

• 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

Introductions and Program Overview