16th AIR FORCE

COMMERCIAL SOLUTIONS OPENING – CALL 0010

FA7037-23-S-C0001

Topic: 007 Air Force Information Network (AFIN)

Long Haul Communications - Integrated Support

(LHC-IS)

Table of Contents

1. INTRODUCTION AND BACKGROUND

2. PURPOSE

3. CSO CALL APPROACH AND OVERVIEW

4. GENERAL INFORMATION

5. SUBMISSION INFORMATION

1. INTRODUCTION AND BACKGROUND

1.1 HQ CCC, under Air Combat Command (ACC), is responsible for executing Connect Portfolio enterprise requirements and analysis. These responsibilities include determining DISN service requirements, provisioning, programming, funding, and circuit management, in addition to managing the DAF CMO and Mobile Satellite Services (MSS). HQ CCC serves all DAF units, as well as Department of Defense (DoD) and federal service tenants on Air Force installations worldwide that require inter-base DISN connectivity.

1.2 The MAJCOM Circuit Management Office offers circuit management and customer support to field units across all DAF MAJCOMs. To fulfill its mission, HQ CCC works in conjunction with the Defense Information Systems Agency (DISA) and the Defense Information Technology Contracting Organization (DITCO) to secure necessary DISN services. It also collaborates with other support contracts, such as the General Services Administration (GSA) Enterprise Information Solutions (EIS) and DISA-GSA Future Commercial Satellite Acquisition (FCSA). Furthermore, HQ CCC oversees the development, sustainment, and support of software applications like the Telecommunications Certification Office Support System (TCOSS) and the Technical Control Administrative Tool Set (TCATS), which are critical for the DAF's corporate and base-level DISN circuit management and funding operations.

1.3 The Air Force needs innovative solutions for:

• Strategic advisory on DISN policies, billing structures, and network architecture to drive enterprise optimization.

• Advanced analytics of telecommunications usage and costs to identify inefficiencies and deliver actionable cost-saving recommendations.

• Integrated oversight and documentation of enterprise-wide DISN network transitions and modernization initiatives.

• Standardized validation and approval workflows for circuit/service provisioning in alignment with DoD and DISA directives.

• End-to-end tracking of communication circuits from initial request to decommissioning via systems like TCOSS.

• A centralized help desk infrastructure providing MAJCOMs and base-level personnel with rapid resolution of circuit inquiries.

• Continuous maintenance, administration, and updates for software code, websites, and database structures supporting TCOSS and TCATS.

• Robust Risk Management Framework (RMF) package oversight and system administration compliant with DISA STIGs.

• Coordinated management of commercial mobile satellite asset activations, transfers, and deactivations across the Joint force.

• Accurate maintenance of MSS records, comprehensive annual SATCOM expenditure reporting, and MAJCOM MSS manager list oversight.

• Remote instructional programs and dedicated hardware/service provisioning help desk support.

• A comprehensive management framework including activity reporting, meeting participation, and system feedback loops.

• In-depth analysis of policy impacts on LHC tools and the appointment of an Accountable Property Officer (APO) for government IT hardware.

• Dynamic creation and management of Program Designator Codes (PDC) and Standard Lines of Accounting (SLOA) integration.

• Rigorous preparation, validation, and tracking of monthly customer invoices and annual billing projections.

• Proactive monitoring of funding data, uncollected expenditure tracking, and delinquent bill notification workflows.

1.4 All awards resulting from this CSO Call will be for the delivery of services, but the Government is specifically interested in approaches that leverage innovation—whether through technology, process improvement, or novel methodologies—to meet or exceed the capability needs described in Attachment 6.

2. PURPOSE

2.1 This Commercial Solutions Opening (CSO) Call, in accordance with 10 USC 3458, Federal Acquisition Regulation-Overhaul (RFO) 6.101, and R-DFARS 212.70 Defense Commercial Solutions Opening, is a competitive solicitation of proposals focused on technologies to meet the 16th Air Force’s mission. The 16th Air Force seeks the best available approaches to meet the capability objectives described herein.

2.2 "Innovative" means any technology, process, or method, including research and development, that is new as of the date of proposal submission, or any new application of an existing technology, process, or method as of that date.

2.3 The Government anticipates a single award under this CSO for an integrated solution encompassing all topic areas and capabilities described in Attachment 6.

3. CSO CALL APPROACH AND OVERVIEW

3.1 This CSO Call seeks the best commercial approaches to meet various technology objectives of 16th Air Force. All items, technologies, and services acquired using a CSO Call will be treated as commercial items. The Government encourages proposals that span a wide spectrum of possible technical and business solutions in response to the specific technology topics stated in Attachment 6. The Government reserves the right to award funding to any combination of proposals which offer the best overall value to the Government, and to oversee any and all processes and approaches once initiated. Awards of efforts as a result of this announcement will be in the form of contracts or other transactions (OT) as codified in 10 U.S.C. §2371b (section 2371b).

3.2 Funding for participation in this program is highly competitive and the price of proposed technologies should be considered. Awards resulting from this CSO Call will be made based on the evaluation results of a two-stepped proposal process described in Section 5. The Government reserves the right to fund all, some, one, or none of the proposals submitted; may elect to fund only part of a submitted proposal;

and may incrementally fund any or all awards under this CSO Call. All awards are subject to the availability of funds.

3.3 All coordination and communication between Offerors and the Government will be conducted using the Sam.Gov website and the points of contact associated with this CSO Call, as specified in Section 4.

3.4 Note: Do not include Proprietary, classified, confidential, or sensitive information in responses. The government may use contractor support personnel to intake and process white papers and proposals.

Whitepaper responses are not offers and cannot be accepted by the U.S. Government to form a binding contract or agreement. This notice shall not be construed as a commitment by the Government to issue a solicitation, or ultimately award a contract, nor does it restrict the Government to a particular acquisition approach.

The Government will in no way be bound to this information if any formal solicitation is issued. This request for white papers is issued solely for information and planning purposes and to identify interested sources. Further, unsolicited proposals will not be accepted. Funding is not available at this time. Release of this request for white papers should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought.

Response to this CSO Call is voluntary and no reimbursement will be made for any costs associated with providing information in response to this and any follow-on information requests. All submissions become Government property and will not be returned.

4. GENERAL INFORMATION

4.1 POINT OF CONTACTS. Questions regarding the content of this CSO Call should be sent to 16af.cso.workflow@us.af.mil.

4.2 CLASSIFIED INFORMATION. Offerors are encouraged to submit unclassified white papers to simplify and expedite reviews and response by the Government. If an Offeror deems that a white paper contains classified information refer to paragraph 5.2.1.3 for submission instructions. Classified submissions must be handled, labeled, and stored in accordance with the National Industrial Security Program (NISP) Operating Manual.

mailto:16af.cso.workflow@us.af.mil

Offerors must possess all required personnel security clearances, facility clearances, and other infrastructure requirements necessary to perform any proposed classified work in accordance with the Contract Security Classification Specification (DD Form 254) without reliance on Government resources.

5. SUBMISSION INFORMATION

5.1 SUBMISSION OVERVIEW. Step I submissions shall include both the Quad Chart and White Paper prepared in accordance with the formats at Attachments 1 and 2 respectively. Each company may submit one white paper and one quad chart for this CSO Call. Submissions should address all TOPICS and all requirements outlined in Attachment 6. Step I submissions shall be submitted by 1500 CST on

18 May 2026 but offerors are encouraged to monitor Sam.gov for any specific amendments to the CSO Call that may have updated information. The Government will invite select Offerors to submit full proposals based on favorable evaluation results of Step I submissions. Step II submissions will be requested ONLY by the Contracting Officer and will contain separate submission instructions and timelines within the Request for Proposal (RFP) letter.

5.2 TWO-STEP SUBMISSION. This CSO Call will be conducted in two steps as follows:

5.2.1 STEP I. Interested offerors must submit Quad Charts and White Papers in accordance with instructions provided in this CSO Call. Step I submissions will be evaluated against criteria as described in Attachment 7 of this CSO Call. Due to the requirements and financial scope of this CSO Call, offerors must ensure that submissions are succinct yet descriptive. Proposals will not be evaluated beyond page length limitations. Proposals that lack technical depth and rigor or are not within the 16th Air Force mission will be assessed accordingly.

5.2.1.1 All Quad Charts should include the information indicated on the sample template in Attachment 1.

5.2.1.2 The White Paper narrative expands on the Quad Chart presentation.

Instructions for format and content are located in Attachment 2. Each offeror shall include in the white paper a preliminary Technology Readiness Level (TRL) assessment of the proposed technology that conforms to the technology objectives and an expected TRL at the conclusion of the effort. The offeror shall perform a TRL assessment according to the Department of War Technology Readiness Assessment Guidance. The offeror must address the overall proposed TRL for the system, application, or process – not just individual components.

5.2.1.3 White paper and quad chart submissions shall be sent to 16af.cso.workflow@us.af.mil for review and shall include “Call 0010 LHC-IS” in the subject line of the email. If there is a need for a classified white paper/quad chart submission, send an email to 16af.cso.workflow@us.af.mil to receive instructions for classified submissions.

5.2.2 Notification of Selection. All offerors providing Step I submissions will be contacted by the Government, either with an email letter informing them that the effort proposed is not of interest to the Government at this time or with a request for a formal price and technical proposal by a specific date.

5.2.3 STEP II. Step II proposals will only be accepted from Offerors who upon review of Step I submissions, are invited by the Contracting Officer to submit a full proposal. In order to be considered for award under Step II, offerors must be registered in the System for Award Management (SAM) at www.sam.gov, be considered responsible within the meaning of RFO 9.1, have a satisfactory performance record, and otherwise be eligible for award based on federal law and regulation.

5.2.3.1 Proposal Submission. Upon notification for a proposal by the

Contracting Officer, offerors have 15 calendar days to prepare and submit a proposal in accordance with the format and instructions at Attachments 3-5. Each proposal shall include a Statement of Work (SOW) and detailed pricing. All pages shall be numbered.

5.2.3.2 Proposal Review, Evaluation and Selection Process. Each proposal will be evaluated on its technical merit according to the criteria and process detailed in Attachment 7. Proposal selection will be primarily based on technical merit, importance to agency programs, and funding availability. Qualified Government personnel will conduct reviews and, if necessary, convene panels of experts for evaluation.

5.3 Rights in Technical Data, Computer Software and Computer Software Documentation.

Offerors shall mark each page of its white paper that contains proprietary information.

It is the Government’s intention to acquire only that necessary to satisfy agency needs and this will be negotiated on a case-by-case basis. An offeror may provide with its white paper assertions to restrict, use, release or disclosure of data and/or computer software and computer software documentation that will be provided in the course of contract performance. Rules governing these assertions can be found in RFO Part 27 and R-DFARS Part 227 and may be accessed at https://www.acquisition.gov/far-overhaul.

mailto:16af.cso.workflow@us.af.mil http://www.sam.gov/ https://www.acquisition.gov/far-overhaul https://www.acquisition.gov/far-overhaul

ATTACHMENT 1: QUAD CHART FORMAT

The following information must be included in the Step I Quad Chart. Quad Charts shall not exceed 1-page in landscape view. Quad Charts must follow the formatting guidelines on the slide template below.

ATTACHMENT 2: STEP I WHITE PAPER FORMAT

The White Paper narrative expands on the Quad Chart presentation and must be 8.5 x 11 inches with one-inch margins, no longer than two pages, single-spaced, with text in Times New Roman, no smaller than 12-point font. All white papers must specify the project title, the Offeror’s organization, CAGE code, the specific topic areas, and Call number associated with the submission (see Attachment 6). Pages in excess of the page limitation will not be read or evaluated. White Papers must not exceed a file size of 10 MB.

The White Paper must be limited only to further explanation of the information conveyed in the Quad Chart, as deemed necessary by the Offeror. The information should provide sufficient information on the proposed solution to allow for an assessment by a technical expert.

Expand as deemed necessary on the following sections of the Quad Chart:

• Objective and integrated solution approach across all capability areas

• Description of the effort

• Benefits of the Proposed Technology

• Technical and integration challenges and proposed mitigations

White paper and quad charts shall be sent to 16af.cso.workflow@us.af.mil for review.

If there is a need for a classified white paper/quad chart submission, send an email to 16af.cso.workflow@us.af.mil to receive instructions for classified submissions.

ATTACHMENT 3: STEP II TECHNICAL PROPOSAL FORMAT

(DO NOT SUBMIT UNLESS INVITED BY CO IAW Section 5.2.3 above)

The Technical Proposal portion of the Step II submission shall not exceed 25 pages, excluding cover page and table of contents. Any pages submitted in excess of the 25-page limit will not be considered or evaluated.

Suggested page limitations for individual sections are listed below; however, these are guidelines not strict limits.

I. ABSTRACT. [1 page suggested.]

II. SCOPE. This proposal is submitted in response to the 16th Air Force Commercial Solutions Opening (CSO) Call on….. [Cite the Project Title. 8 pages suggested.]

a. Objective. [A clear and concise description of the objective of the proposed project.]

b. Background. [Provide the necessary technical and scientific background to support the scientific and technical merits of the proposed project.]

c. Programmatics. This effort will support the ACC HQ CCC initiative 003 aimed at developing [capability area or topic title] technologies or methodologies. [Describe the Offeror’s management plan for the proposed project; list supporting and collaborating organizations and subcontractors;

clearly identify roles and responsibilities of each organization and subcontractor supporting the project].

d. Relevance. [Describe the relevance of the proposed project in terms of mission, end-user needs and the technology maturity of the proposed project.]

III. CREDENTIALS. [Describe the Offeror’s qualifications to perform the proposed work across all capability areas. 2 pages suggested.]

IV. WORK TO BE PERFORMED. [Provide details of the work to be performed by task and subtask. 9 pages suggested.]

a. General. [Provide an overview.]

b. Detailed Tasks. [Describe the details of all tasks needed to perform the proposed work. Clearly distinguish base period tasks and option tasks as appropriate.]

V. PERFORMANCE SCHEDULE. [Depict the tasks and sub-tasks and the duration of performance of each in a Gantt chart or other suitable chart. Briefly describe the proposed period of performance. 2 pages suggested.]

VI. REFERENCES. [List any relevant documents used to develop the technical approach. 1 page suggested]

ATTACHMENT 4: STEP II PRICE PROPOSAL FORMAT

(DO NOT SUBMIT UNLESS INVITED BY CO IAW Section 5.2.3 above)

The price proposal must include pricing information sufficiently detailed for a meaningful evaluation. Since this CSO Call is limited to commercial solutions, detailed cost breakdowns are not required. However, the offeror must provide sufficient supporting data for the Contracting Officer to determine price reasonableness. The offeror bears the burden of establishing a reasonable price.

The Offeror shall prepare the Price Proposal (with the exception of the narrative information described below) using Microsoft Excel format, but shall merge all Price Proposal documents into one Adobe PDF file for ultimate proposal submission. Include the Topic Number and the Project Title on all pages. Retain the Excel version for subsequent Government request.

Format requirements:

• Paper Size – 8.5 X 11-inch paper

• Margins 1-inch

• Spacing – single

• Font – Times New Roman, 12 Point

Cover sheet attached to the price proposal shall include:

• Full company name and address of Prime Contractor

• CSO Call number and Title

• Point of contact, name, title, and phone number

• CAGE code

• Unique Entity Identifier (UEI)

• Identification of any Government property required for performance

NOTE: If an Offeror takes exceptions to the requirements called out in the announcement, the exceptions should be clearly stated in the price proposal.

ATTACHMENT 5: STEP II STATEMENT OF WORK (SOW) FORMAT

(DO NOT SUBMIT UNLESS INVITED BY CO IAW Section 5.2.3 above)

A SOW must be included in with the full proposal as part of the Step II submission. The SOW does not have a page limit but should be approximately 3–5 pages in length and must be a separate and distinct document suitable for incorporation into the procurement instrument. Do not include proprietary data or markings in the SOW. Pages must be numbered and the initial page must show the document date under the title.

The proposed SOW must accurately describe the work to be performed, and performance metrics based on your proposed solution and the objectives in the SOO. The proposed SOW must also contain a summary description of the technical methodology as well as the task description, but not in so much detail as to make the SOW inflexible. The SOW template should include the following sections and specifically respond to the Statement of Objectives (SOO) the Government provided with the Request for Proposal (RFP):

1. OBJECTIVE. This section is intended to give a brief overview of the project and should describe why the work is being pursued and what the Offeror intends to accomplish.

2. SCOPE. This section includes a statement of what the SOW covers. This should describe all capability areas, goals, and milestones for the effort.

3. BACKGROUND. The Offeror must identify appropriate documents that are applicable to the effort to be performed. This section includes any information, explanations, or constraints that are necessary to understand the project tasks and requirements. This section should describe the effort’s relationship to previous and ongoing efforts.

4. TASKS AND TECHNICAL REQUIREMENTS. This section contains the detailed description of tasks that are necessary to perform the proposed work. These tasks will represent the work to be performed in any potential contract award, and, thus, shall be considered contractually binding. This section should be developed in an orderly progression and presented in sufficient detail to establish the feasibility of accomplishing the overall program goals. This section should clearly distinguish base period tasks from optional tasks. The SOW must contain every task to be accomplished and the metrics by which these tasks will be measured, generally depicted in a Services Summary. Note: The Government reserves the right to modify and negotiate the language in the SOW prior to any potential contract award.

4.1. Task descriptions must be definite, realistic, and clearly stated. Use the phrase

“the contractor shall” whenever the work statement expresses a provision that is binding. Use “should” or “may” whenever it is necessary to express a declaration of purpose. Use “will” in cases where no Offeror requirement is involved (e.g., power will be supplied by the Government. Use active voice in describing work to be performed.

4.2. Do not use acronyms or abbreviations without first defining them. Place abbreviations and acronyms in parentheses following the first usage of the spelled-out phrase.

4.3. If presentations and meetings are identified in the Offeror’s schedule, the Offeror must include the following statement in the SOW: “Conduct presentations and meetings at times and places specified in the contract schedule.”

4.4. The desired project structure consists of base period tasks, focused on demonstrating the feasibility of the technology, and option tasks, which cover design, fabrication, testing, and evaluation of the final product. Execution of ordering period tasks will be dependent upon and determined by the contractor’s performance during and the results produced from the base period tasks.

ATTACHMENT 6: SOLICITATION TOPIC

TOPIC: 007, Air Force Information Network (AFIN)

The 16th AF seeks innovative and novel solutions to 1) prevent, detect, and repel cyber-attacks,

2) advance capabilities to install, support and prevent intrusion of systems, 3) advance capabilities of the AF global communications network infrastructure, 4) advance capabilities of AF computer hardware and software.

CALL 0010 CAPABILITY NEEDS (List not inclusive)

The HQ CCC intends to award an Indefinite Delivery, Indefinite Quantity (IDIQ) contract to fund successful efforts beginning in Fiscal Year 2027. The anticipated period of performance is seven years, executed via individual one-year ordering periods. The Government reserves the right to fund all, some, one or none of the proposals submitted; may elect to fund only part of a submitted proposal; and may incrementally fund any or all awards under this CSO Call. All awards are subject to the availability of funds.

The offeror is not limited to the specific examples provided and is encouraged to propose alternative approaches, technologies, and methodologies that demonstrate a superior ability to achieve the desired outcomes. The level of detail provided for each topic or the order in which they appear is not intended to convey any information regarding relative priority. All awards resulting from this CSO Call will be for the delivery of services, but the Government is specifically interested in approaches that leverage innovation—whether through technology, process improvement, or novel methodologies—to meet or exceed the capability needs described below.

1. Provide Enterprise Long-Haul Communications Management and Analysis:

• Policy and Technical Expertise:

o Subject matter expertise in Defense Information Systems Network (DISN) policies, services, billing structures, and strategic goals.

o Ability to provide technical support, policy guidance, and funding analysis to DAF customers.

o Working knowledge of DAF/DoD network architectures (e.g., JRSS, DISA MPLS).

o Capability to research, analyze, and articulate the impact of DoD, DAF, and DISA policies.

• Data Analysis and Reporting:

o Analyze large volumes of telecommunications data to identify trends, perform root-cause analysis, and recommend cost-saving measures.

o Research provisioning documents using systems like TCOSS, TIBI, and

WWOLS-R.

o Validate and ensure the use of correct funding codes (PDCs) and understand DoD/DAF financial cycles (PEM, POM).

• Project and Program Management:

o Manage and process DAF NIPRNET and SIPRNET connection orders.

o Oversee enterprise-wide DISN transition and modernization projects.

o Prepare high-level communications (briefings, papers) for senior leadership in accordance with AFH 33-337 The Tongue and Quill.

2. Comprehensive Circuit Management and Provisioning Support

• Circuit Provisioning and Lifecycle Management:

o Execute all circuit and service provisioning functions IAW DoD, DAF, and DISA directives.

o Validate, approve, deny, and create circuit orders in systems like DISA

Marketplace (DMPSF).

o Manage the full lifecycle of Communication Service Authorizations

(CSAs), from initial request to final disconnection.

o Maintain the accuracy of the master circuit database (TCOSS).

• Coordination and Customer Support:

o Coordinate with diverse stakeholders (HQ CCC, DISA/DITCO, GSA, MAJCOMs, vendors) to ensure smooth transitions of services.

o Act as a central help desk for MAJCOMs and base-level personnel, providing assistance and tracking for all circuit-related actions.

3. Full Lifecycle Support for TCOSS/TCATS Applications

• Software Development and Maintenance:

o Maintain, sustain, and enhance the TCOSS/TCATS software code, structure, and functions.

o Maintain the associated public-facing website's code, data, and structure.

• System and Database Administration:

o Administer TCOSS application and web servers (physical or virtual), including backups, replication, and security.

o Maintain and administer database structures, data content, integrity, and the database management systems per DISA STIGs.

o Load and manage application data.

• Security and Customer Support:

o Support application and network security, including the maintenance of the Risk Management Framework (RMF) package.

o Provide direct customer support to all users of the TCOSS/TCATS applications.

4. Manage Mobile Satellite Service (MSS)

• MSS Program Management:

o Provide subject matter expertise for the DAF's Commercial MSS program.

o Coordinate service actions (activation, deactivation) with commercial providers.

o Manage MSS database records within the TCOSS system.

o Maintain the MAJCOM MSS manager list and coordinate the transfer of assets between units.

• Customer Support and Reporting:

o Provide comprehensive customer support on MSS hardware, services, costs, and ordering procedures.

o Conduct remote training for users.

o Complete the annual Commercial SATCOM expenditure report.

5. Effective Program and Contract Management

• Program Management and Reporting:

o Establish and execute a comprehensive Project Management Plan (PMP).

o Conduct effective contract administration, including regular COR meetings and providing status/activity reports.

o Provide feedback on all systems and processes within the contract's scope.

• Technical and Administrative Support:

o Provide technical expertise for DAF policy and governance.

o Advise on how new policies affect LHC tools like TCOSS/TCATS.

o Appoint an Accountable Property Officer (APO) to manage government-furnished hardware.

o Maintain and update all continuity documentation (process guides, procedural documents).

o Handle ad hoc tasks relevant to the LHC mission as they arise.

6. Enterprise Long Haul Communications Financial Support

• Financial Processing and Management:

o Perform financial management functions according to DoD, DAF, and DISA directives.

o Create, track, and manage Program Designator Codes (PDCs) and enter Standard Lines of Accounting (SLOA) into financial systems (TIBI).

o Create funding documentation to support customer orders in the DISA Marketplace.

• Billing and Analysis:

o Analyze, prepare, validate, and send monthly and annual customer bills and invoices.

o Track delinquent bills and report on financial discrepancies.

o Run monthly, annual, and ad hoc reports on funding, billing, unbillable, and uncollected expenditures.

• Customer Support:

o Act as the primary financial support contact for MAJCOMs, FOAs, DRUs, and base-level personnel for all LHC financial inquiries.

ATTACHMENT 7: EVALUATION CRITERIA AND SELECTION PROCESS

The Government will review each Quad Chart and White Paper (Step I) and select offerors with the greatest potential to meet the operational needs of 16th Air Force based on the capability areas in Attachment 6. A determination will first be made whether each offeror is technically qualified and has a comprehensive understanding to execute the proposed solution based on the information stated in the Quad Chart/White Paper.

The offeror is advised that only Firm Fixed Price (FFP) or Fixed Price Incentive (FPI) contracts may be awarded as a result of this CSO Call.

The Government will determine the most technically competent and capable of the qualified offerors using the criteria below:

• Criteria (Factors) for Selecting Quad Chart/White Paper for Full Proposal Submission:

o Technical merit/applicability, o Importance to 16th Air Force mission, and o Fund availability

• Relative Importance: All Factors are of equal importance

• Method of Evaluation: Peer or scientific review