Kronos CSO CAO 12NOV25.pdf

Kronos Program

Commercial Solutions Opening (CSO)

Dated 12 Nov 2025

Record of Revisions

Revision Description Date Initial Release 12 Nov 2025

Table of Contents

1. INTRODUCTION AND BACKGROUND

2. PURPOSE

3. CSO APPROACH

4. GENERAL INFORMATION

5. SUBMISSION INFORMATION

6. ADDITIONAL INFORMATION

ATTACHMENT 1: PHASE I – Initial Submission

ATTACHMENT 2: PHASE II – TECHNICAL, SOW, AND PRICE PROPOSAL

ATTACHMENT 3: REVIEW, EVALUATION AND SELECTION PROCESS

ATTACHMENT 4: AREAS OF INTEREST (AOI)

1. INTRODUCTION AND BACKGROUND 1

1.1 Space Systems Command, through its Kronos Program of Record, is issuing a 3 Commercial Solutions Opening (CSO) in accordance with Defense Federal Acquisition 4 Regulation Supplement (DFARS) 212.70, Defense Commercial Solutions Opening. 5 Under the Kronos Family of Systems CSO, the Government may award proposals 6 received in response to a general solicitation to acquire innovative products, technologies, 7 or services based on a review of solutions by scientific, technological, or other subject 8 matter expert peers within the program management office (PMO). “Innovative” for CSO 9 purposes, means any new technology, process, or method, including research and 10 development (R&D), or any new application of an existing technology, process or method, 11 that is new as of the date of the submission of a proposal. The Government may award 12 FAR-based or Other Transaction Agreement (OTA) awards as a result of this solicitation. 13 All awards under this CSO will be treated as commercial. 14

1.2 The Government is interested in a broad range of solutions spanning from foundational 16 cloud computing infrastructure to mission-specific software applications and software 17 development services to include, but are not limited to: 18

• Advanced cloud-native infrastructure and services 20

• Scalable and secure platform solutions 21

• Agile software development methodologies and tooling 22

• Mission-driven C2 applications 23

• Data integration, management, and visualization capabilities 24

• Artificial intelligence (AI), machine learning (ML), and decision-support tools 25

• Cybersecurity and zero-trust architectures 26

This CSO seeks to identify and leverage cutting-edge innovations that can enhance the 28 scalability, flexibility, interoperability, and resiliency of the Kronos program in alignment 29 with the evolving operational needs of the US Space Force (USSF) Command and Control 30 (C2) mission. 31

2. PURPOSE 33

2.1 This CSO is a competitive solicitation under DFARS 206.102-70(a). It is focused on 35 identifying and acquiring innovative technologies and services to support the mission of 36 the PMO. The Government seeks commercial innovative solutions (prototypes only) that 37 could fulfill requirements, close capability gaps, and provide potential technological 38 advancements. The Government’s Areas of Interest (AOIs) are outlined in Attachment 4. 39

3. CSO APPROACH 41

3.1 The Government encourages proposals that span a wide spectrum of possible technical 42 and business solutions in response to the specific AOIs. Each AOI will identify the interest 43 for an individual program requirement or a broadly defined interest area covering the full 44 range of program requirements. All submissions in response to any AOI will be governed 45 by this CSO unless otherwise noted in the individual AOI. 46

3.2 The Government anticipates making award(s) primarily using OTA authority. Where 47 appropriate, the Government may also award FAR-based contracts. If FAR-based 48 contracts are used, fixed-price type contracts are anticipated; incentives may be considered 49 when supported by risk analysis. 50

3.3 Upon favorable review and evaluation, the Government may choose to award an OTA for 51 Prototype phase as deemed appropriate for the transaction. The Agreements Officer will 52 negotiate directly with the Offeror on the terms and conditions of the OTA, including 53 payments, and will execute the OTA on behalf of the Government. 54

This CSO is focused on the prototype phase only. If the prototype phase is successful, the 55 Government reserves the right to transition to a follow-on production phase without 56 further competition as authorized under 10 U.S.C. § 4022(f). The decision to proceed with 57 a follow-on production award will depend on the successful results of the prototype, the 58 availability of funding and the approval of a future acquisition strategy. A follow-on 59 production award is not guaranteed. 60

3.4 Awards resulting from this CSO will be made based on the process described in 61 Attachment 3. The Government reserves the right to fund all, some, one, or none of the 62 Phase 2 proposals submitted. The Government may elect to fund only part of a submitted 63 proposal and may incrementally fund any or all awards under this CSO. All awards are 64 subject to the availability of funds. 65

3.5 All coordination and communication between Offerors and the Government will be 66 conducted as specified in Section 4. 67

4. GENERAL INFORMATION 69

4.1 POINT OF CONTACT: 71

4.1.1 CSO & AOI General Questions – General CSO Questions may be sent via email to 73 the CSO Technical Team at SSC.BMZ.SYD85@spaceforce.mil . Due to the large amount 74 of expected interest in this CSO, and to maintain a written record of questions, this is the 75 only email address that will be used for general question communication. 76 The following shall be utilized in the email subject line: (AOI x) Kronos CSO General 78 Question(s). 79

4.2 CLASSIFIED INFORMATION: All Phase I and II submissions shall be unclassified. 81 For Phase II submissions, offerors should possess all required personnel security 83 clearances, facility clearances, and other infrastructure requirements necessary to perform 84 any proposed classified work in accordance with the draft Contract Security Classification 85 Specification (DD Form 254) without reliance on Government resources. 86 As a wide variety of responses, as well as potential awards of diverse scope and associated 88 classified classification levels under this CSO are possible, the Government will provide 89 award specific security details for individual award actions as required. A draft DD Form 90 254 will be provided with a Phase II request for proposal, as necessary. 91

5. SUBMISSION INFORMATION 93

5.1 SUBMISSION OVERVIEW: This CSO is a one-time call for potential prototype 95 solutions. The acceptance start date for Phase I submissions will be identified by 96 individual AOIs. The Government will amend the CSO to incorporate additional AOIs 97 as needed. Submissions received outside an open AOI window will not be reviewed. 98

• The Government will not reimburse companies for the costs associated with 99 submissions for any phase. 100

• Submissions for all phases shall be sent electronically. Hardcopies for any phase will 101 not be accepted. 102

• Offerors shall mark each page of the Phase I and Phase II submissions that contain 103 proprietary information. 104

5.2 TWO PHASED SUBMISSION PROCESS: This CSO will be conducted in two phases. 106

Phase I is structured to provide the Government with an initial call for solutions while 107 Phase II captures proposal submission. The Government reserves the right to select none 108 of the submissions. 109

5.2.1 Phase I Submissions: Phase I submissions will be sent to the CSO email org box 111 by the date and time specified under reach respective AOI. 112

5.2.2 Phase II - Technical, SOW, and Price Proposal: Phase II submissions will be 114 submitted to the PCO in accordance with request for proposal procedures. Phase II 115 proposals will only be accepted from Offerors who, upon review of Phase I submission, 116 have received a request from the Contracting Officer to submit a full proposal 117 (Technical, Price, and Statement of Work (SOW)). Phase II proposal will be sent to the 118 PCO in accordance with submission procedures outlined in the request for proposal. 119 Proposals shall not be submitted to the general questions email address. 120

6. ADDITIONAL INFORMATION 122

6.1 DATA RIGHTS: It is the Government’s intention to acquire only Technical Data, 124

Computer Software, and Computer Software Documentation data rights necessary to 125 satisfy agency needs. For FAR-based contracts, the Government will follow DFARS 126 252.227-7013/ -7014/ -7017. For OTAs, the Government will negotiate data/IP rights 127 consistent with OTA authority. 128

6.2 FOREIGN PARTICIPATION: Foreign participation may be considered subject to export 130 control restrictions (ITAR/EAR), national security considerations, and disclosure of any 131 foreign ownership, control, or influence (FOCI). The research and test data produced 132 under a resultant contract or agreement may contain Military Critical Technology List 133 (MCTL) information whose export is restricted by Export Control Act (Title 22, U.S. Sec 134 2751, et seq.) or the Export Administration Act of 1979, as amended (Title 50, U.S.C., 135 App. 2401, et seq.). Request certification and registration from the Defense Logistics 136 Services Center (DLSC), Federal Center, 74 North Washington, Battle Creek, MI 49016-137

3412 as soon as possible. 138

6.3 NON-GOVERNMENT ADVISORS: In order to review submissions resultant from any 140 phase, PROPRIETARY information may be given to Federally Funded Research and 141 Development Centers (FFRDC), Systems Engineering and Technical Assistance (SETA), 142 Systems Engineering and Integration (SE&I), and/or Advisory and Assistance Services 143 (A&AS) contractors working for the Government. The non-Government advisors will 144 have signed a non-disclosure agreement with the Government prior to reviewing 145 submissions. 146

6.4 PROCUREMENT INTEGRITY, STANDARDS OF CONDUCT, ETHICAL 148

CONSIDERATIONS, AND CONFLICTS OF INTEREST: All offerors shall fill out the 149 attached Organizational Conflict of Interest (OCI) Mitigation Plan Checklist and include 150 a plan as applicable. 151

6.5 OFFEROR FEEDBACK: For FAR-based contracts, the Government will provide notice 153 of results in accordance with FAR 52.212-1(l) and will address the evaluation factors 154 contained herein only, as applicable. It will not include a comparison of submissions 155 against a common PWS or SOW as the CSO provides no common PWS or SOW that 156 interested parties must respond to and instead represents opportunity for submission of a 157 variety of innovative commercial items, technologies, and/or services that represent 158 meaningful submissions of diverse scope and price. For OTAs, the Government may 159 provide summary feedback after each phase at the Government’s discretion consistent 160 with OTA authority. 161

6.6 GOVERNMENT FURNISHED PROPERTY (GFP) AVAILABILITY: GFP is not 163 anticipated to be made available under any resulting contract or agreement, but a 164 determination regarding GFP will be made for each award. In accordance with FAR 165 45.201(b), the contractor is responsible for all costs related to making the property 166 available for use, such as payment of all transportation, installation, or rehabilitation costs. 167

6.7 NETWORK ACCESS AND CLASSIFIED INFRASTRUCTURE: Support will be 169 determined for each award for testing, validation, and deployment and demonstration 170 purposes. 171

ATTACHMENT 1: PHASE I – Initial Submission 173

PHASE 1A: OVERVIEW BRIEFING 175

The function of Phase I is to receive initial solutions for the respective AOIs from potential offerors. 177 Each Offeror shall submit their plans to provide an innovative solution addressing the specific AOI 178 described in Attachment 4. The following Quad Chart must be included as the first content slide in 179 the Phase I overview briefing submission. Quad Charts shall not exceed 1-page in landscape view 180 and must follow the formatting guidelines on the slide template below. All fonts must be Times New 181 Roman ≥12pt. Briefings shall be limited to no more than five slides, not including a title slide and 182 the Quad Chart, with file size not greater than 10MB. Briefing submissions shall be provided in PDF 183 format. Briefings should provide visuals and further elaborate on the information provided on the 184 Quad Chart. Graphics Interchange Format (GIFs), videos/movies, or clips are permitted. 185

PHASE IA – WHITE PAPER FORMAT 188

1. The White Paper narrative expands on the overview briefing and must be 8.5 x 11 inches with 190 one-inch margins, no longer than five pages, single-spaced, with text in Times New Roman, 191 and no smaller than 12-point font. Each Offeror shall describe their plans to provide an 192 innovative solution to the individual AOI. 193

2. The White Paper shall contain a cover sheet containing the following information. The cover 195 sheet will not count against the page limitation. 196

(a) CSO number, AOI number, and AOI name 198

(b) Project Title 199

(c) Full company name and address 200

(d) CAGE code 201

(e) Unique Entity ID number 202

(f) Business Size Classification (large, small, or other) 203

(g) Current Facilities Clearance Level 204

3. White Papers must be submitted electronically as a PDF not exceeding a file size of 10 MB. 206

Pages in excess of the page limitation will not be read or reviewed. 207

4. The White Paper should provide sufficient information on the technical approach being 209 submitted to allow for review by a technical expert. Expand as deemed necessary on the 210 following sections of the overview briefing: Objective; Description of the Effort; Benefits of 211 the Proposed Approach; Technical Challenges; Solution Approach; State of Solution; Major 212 Milestones by Government fiscal year and month; and the Rough Order of Magnitude (ROM) 213 price estimate. Offeror must also disclose any foreign ownership, control, or influence (FOCI). 214 Do not include corporate or personnel qualification, past experience or any supplemental 215 information not requested. 216

PHASE IB – PITCH SESSION AND FORMAT* 218

1. Offerors may be invited to an optional pitch session to expand upon the proposed 220 concept/technology/solution virtually. The Government will provide the Offeror 45 minutes for 221 the Offeror’s pitch and additional time if needed by the Government for follow-up 222 questions/discussion. 223

2. Offerors shall provide a virtual pitch to answer Government’s questions based on Phase IA 225 submittal. . In addition to the pitch, the Government, at its discretion, may request an additional 226 written submission to further supplement the information provided in Phase I overview brief. 227

3. During the pitch session, the Offeror must detail/address: 229

(a) Real-time clarification of the white paper’s content to include answering Government 230 questions. 231

(b) Integration environment understanding: The solution brief will detail the integration 232 strategy and include a detailed description of the integration environment. 233

(c) Any proposed investment by the vendor or on behalf of the vendor for the proposed 234 prototype solution. 235

*Note: The Government reserves the right to forgo a 1B pitch session and go directly to Phase 237

II. 238

ATTACHMENT 2: PHASE II – TECHNICAL, SOW, AND PRICE PROPOSAL 241

The Phase II proposal submission shall conform to the following: 242

1. Cover Sheet: The following information shall be contained in a cover sheet submitted with the 244 proposal: 245

(a) CSO number, AOI number, and AOI name 246

(b) Full company name and address 247

(c) CAGE code 248

(d) Unique Entity ID number 249

(e) Business Size Classification (large, small, or other) 250

(f) Offeror’s socioeconomic status 251

(g) Point of contact, name, title, phone number, and email address 252

(h) Current Facility Clearance Level 253

2. Technical Approach: The following describes the technical approach requirements: 255

(a) The Technical Approach shall describe the background and objectives of the proposed 256 work, the approach, deliverables, the resources needed to execute, and additional details of 257 data rights assertions. Include the nature and extent of the capability and how it addresses 258 the AOI, the innovative aspect of the solution, the intended results, and address possible 259 integration or testing needs. Include ancillary and operational considerations such as 260 certifications, algorithms, and any engineering/software development methodologies to be 261 used. Provide a graphic display of major program milestones. Measurable milestones 262 should capture key activity points and should be clearly articulated and defined in time 263 relative to the start of the effort. Submissions may refer to previous submitted information 264 from Phase I, but do not duplicate it. 265

(b) Government Support Required: Identify the type of support, if any, the Offeror requests of 266 the Government in general, such as facilities, equipment, data, and information or materials. 267

(c) The Government reserves the right to ask for additional technical information in the Phase II 268 request for proposal. 269

(d) Due to the varying AOIs and potential solutions, Technical Proposal page limitations and 270 formatting will be identified in the Phase II request for proposal. 271

3. Statement of Work (SOW): The following describes the SOW requirements: 273

(a) The SOW must be a separate and distinct document suitable for incorporation into a contract 274 or agreement. Pages should be numbered and provide line numbers. The initial page should 275 have a date (document date) shown under the title. Proprietary information should not be 276 included in the SOW. 277

(b) The proposed SOW must accurately describe the work to be performed. The SOW must also 278 contain a summary description of the technical methodology as well as the task descriptions, 279 but not in so much detail as to make the SOW inflexible. The SOW should include the 280 following sections: 281

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

2. SCOPE: This section includes a statement of what the SOW covers. This should 286 describe the AOI to be investigated, goals, and milestones for the effort. Provide a 287 graphic display of major program milestones. 288

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

4. TASKS AND TECHNICAL REQUIREMENTS: This section contains the detailed 296 description of tasks that are necessary to perform the proposed work. These tasks 297 will represent the work to be performed in any potential contract or agreement award, 298 and, thus, shall be considered contractually binding. This section should be 299 developed in an orderly progression and presented in sufficient detail to establish 300 the feasibility of accomplishing the overall program goals. The Government reserves 301 the right to modify and negotiate the language in the SOW prior to any potential 302 contract or agreement award. 303

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

“the contractor shall” whenever the work that is a mandatory obligation. Use 306 “should” or “may” whenever it is necessary to express work that is aspiration 307 or not compulsory. 308

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

(c) Due to the varying AOIs and potential solutions, SOW page limitations will be identified 313 in the Phase II request for proposal. 314

4. Price Volume: The following describes the Price submission requirements: 316

(a) The Price submission must include pricing information sufficiently detailed for meaningful 317 evaluation of the proposal. The Price Proposal does not have a page limit restriction. 318

(b) For FAR-based contracts, since all proposals are considered commercial items, 319 technologies, or services, the requirements of the Truthful Cost or Pricing Data Act are not 320 applicable. However, if the Contracting Officer determines additional information is 321 necessary to support a determination of a fair and reasonable price, other than certified cost 322 and pricing data may be requested. For OTAs, Agreement Officer must ensure the 323 Government pays a price that is reasonable relative to scope, risk, and market conditions. 324 Data rights are negotiated separately and not evaluated as price. 325

(c) The responsibility for providing adequate supporting data and attachments lies solely with 326 the Offeror. Further, the Offeror also bears the burden of proof in establishing 327 reasonableness of proposed prices; therefore, it is in the Offeror’s best interest to submit a 328 fully supportable and well-prepared price proposal. 329

(d) The Offeror shall prepare the Price submission to include an electronic version of the pricing 330 model in a Microsoft (MS) Excel editable format. The electronic pricing model shall include 331 active formulas demonstrating the mathematical calculation of the proposed price. 332

5. Additional Proposal Submission Content: 334

(a) Small Business Subcontracting Plan: If FAR-based contract is indicated by the Government 336 and the offeror is other than small business, offerors shall submit either an individual 337 subcontracting plan and/or master subcontracting plan (if available) in accordance with FAR 338 52.219-9 Small Business Subcontracting Plan (Sep 2023), DFARS 252.219-7003 Small 339 Business Subcontracting Plan (DoD Contracts) – Basic (Dec 2019) and DFARS 252.219-7004 340 Small Business Subcontracting Plan (Test Program) (Dec 2022) with their Phase II proposal. 341 The Offeror's small business subcontracting plan shall include, but is not limited to, details 342 regarding the commitment/targets for each category of small business, veteran-owned small 343 business, service-disabled veteran-owned small business, small, disadvantaged business, 344 HUBZone, and women-owned small business concerns. The plan shall describe for each 345 category the total value subcontracted expressed in dollars and percentage of total 346 subcontracted value if an individual subcontracting plan. The plan shall also state the extent 347 and nature of work to be performed by small business concerns, the method used to develop 348 goals, the method used to locate potential suppliers, if the goals include indirect costs (if so, 349 describe the cost allocation method) and describe the efforts the Offeror will make to assure 350 small businesses have an equitable opportunity to compete for subcontracts. If the small, 351 disadvantaged business goal does not meet or exceed the 5% threshold, in accordance with 352 DFARS 219-705-4, substantial explanation/rationale shall be provided. The plan shall also 353 provide the name and duties of the contractor's subcontracting plan administrator. 354

If the Small Business Subcontracting Plan is not initially acceptable, the Contracting Officer 356 may request additional information regarding the Small Business Subcontracting Plan. 357

(b) Organizational Conflict of Interest: Regardless of whether FAR-based contract or OTA, the 359 Offeror shall perform an Organizational Conflict of Interest (OCI) analysis and submit the 360 results of that analysis as part of the Offeror’s Phase II proposal. Specifically, the Offeror shall 361 analyze the planned acquisition for actual or potential OCI situations associated with the 362 Offeror or any of the Offeror’s proposed teammates or subcontractor’s performance under any 363 contract or agreement the Offeror or the Offeror’s teammates or subcontractors has been or 364 may be awarded by any federal agency or other entity. The Offeror shall describe in detail the 365 methodology used to identify actual or potential OCI issues. If the Offeror identifies any actual 366 or potential OCIs with respect to the performance of the Offeror or the Offeror’s subcontractors 367 or teammates, the contractor shall provide an OCI Mitigation Plan to be incorporated as an 368 attachment to any resulting contract or agreement. Any proposed avoidance or mitigation 369 techniques shall be consistent with FAR 9.5 and the most recent decisions of the Government 370 Accountability Office (GAO) and the U.S. Court of Federal Claims. 371

(c) Responsibility: The Offeror shall provide information that presents a brief verifiable self-373 assessment in the areas of responsibility as described in FAR 9.104 as supplemented by 374 DFARS and Department of the Air Force Federal Acquisition Regulation Supplement. 375 Elements of responsibility to address include but are not limited to, management of 376 government property, capability, resources, competency, capacity, credit, integrity, 377 perseverance, tenacity, and limitations on subcontracting. 378 Inability to perform in compliance with the limitations of subcontracting clause FAR 52.219-380 14 is a matter of responsibility for small businesses. The Contracting Officer will follow the 381 Small Business Administration Certificate of Competency procedure at FAR subpart 19.6 382 when a small business concern would otherwise be selected for award but is considered not 383 responsible. 384

(d) Space Contractor Responsibility Watchlist (CRWL): In accordance with Section 1601 of the 386

National Defense Authorization Act (NDAA) for FY 2025 (P.L. 118-159) and DAFGM2025-387 63-01, the PCO may not award a contract to a contractor included on the CRWL without 388 making a determination of responsibility and obtaining the approval of the SAF/SQ. A 389 contractor that has been notified that it has been added to the CRWL may respond to this CSO 390 but must submit documentation describing how it has addressed the conditions that resulted in 391 its inclusion on the CRWL and why those conditions will not impact performance on a contract 392 resulting from this CSO. Proposed subcontractors must notify the prime Offeror if they receive 393 notification from the SAE that they have been added to the CRWL. In order to be considered 394 for a subcontract, a proposed subcontractor that has been added to the CRWL must submit 395 documentation describing how it has addressed the conditions that resulted in its inclusion on 396 the CRWL and why those conditions will not impact its performance on a subcontract to a 397 contract resulting from this CSO. The proposed subcontractor may submit CRWL-related 398 documentation through the prime Offeror or directly to the Contracting Officer as long as the 399 information is received prior to the proposal due date. 400

Note: CRWL does not apply to operation and maintenance contracts, professional services 402 contracts for Government support (e.g., FFRDC, A&AS). 403

(e) Rights in Technical Data, Computer Software, and Computer Software Documentation: An 405

Offeror may provide with its submissions assertions to restrict, use, release, or disclosure of 406 data and/or computer software and computer software documentation that will be provided in 407 the course of contract or agreement performance. For FAR-based awards, rules governing 408 these assertions are prescribed in DFARS clauses 252.227-7013, -7014, and -7017 and may be 409 accessed at www.acquisition.gov. For OTA awards, data rights are subject to negotiation. 410

ATTACHMENT 3: REVIEW, EVALUATION AND SELECTION PROCESS 412

The Government will review and evaluate submissions in multiple phases, as described below. 413 Progression from one phase to another, and ultimately to award, is at the sole discretion of the 414 Government, subject to review and evaluation results and availability of funds. Solutions will be 415 evaluated on the basis of the merit of the proposed concept in addressing the Areas of Interest and 416 not against other vendor’s solution briefs submitted in response to the same Area of Interest. 417

1. Phase IA – PowerPoint and White Paper Submission: 419

a. Purpose: The Government will identify Phase IA submissions that demonstrate 420 sufficient Government interest and technical merit based on the AOIs outlined in 421 Attachment 4, to justify further consideration. 422

b. Review: Phase IA submissions will be reviewed against the factors below: 423

i. Government Interest – Contribution to mission need and alignment of the 424 proposed solution with the AOI description. Should the Government be 425 interested in the submission, it will then be reviewed for technical merit. 426

ii. Technical Validity - Technical validity and reasonableness, alignment with 427 the AOI description. 428

iii. Proposed Vendor Investment – Any proposed investment by the vendor or 429 on behalf of the vendor for the proposed prototype solution. 430

c. Outcome: Based on the review, offerors may be: 431

i. Invited to a pitch session (optional); 432

ii. Invited to submit a Phase II proposal; or 433

iii. Notified that the submission will not be pursued. 434

2. Phase IB – Pitch Session (optional): 436

a. Purpose: The Government may invite offerors to expand on their Phase IA 437 submissions to answer Government’s specific questions to, but not limited to, 438 demonstrate technical challenges, business viability and integration potential not 439 already addressed in white paper. 440

b. Review: Phase IB pitch sessions will be reviewed against the factors below: 441

i. Government Interest – Contribution to mission need and alignment of the 442 proposed solution with the AOI description. 443

ii. Technical Validity: Technical validity and reasonableness, alignment with 444 the AOI description, demonstration of an understanding of the integration 445 environment. 446

iii. Proposed Vendor Investment – Any proposed investment by the vendor or 447 on behalf of the vendor for the proposed prototype solution. 448

c. Outcome: Based on the pitch session review, offerors may be: 449

i. Invited to submit a Phase II proposal; or 450

ii. Notified that the submission will not be pursued. 451

3. Phase II – Proposal - Technical, SOW, and Price Information: 453

a. Purpose: The Government will assess the technical, business, integration potential 454 and cost aspects of the proposal in detail. The specific evaluation criteria for Phase II 455 proposals will be provided in the RFP and may include, but is not limited to, the 456 following evaluation factors: 457

b. The Government will ensure vendors meet the following un-rated criteria before 458 being evaluated: 459

i. Government Interest – Contribution to mission need and alignment with the 460 AOI description. The Government will choose the proposal(s) that best aligns 461 with the mission priorities and has the greatest potential impact in meeting the 462 needs identified in the AOI 463

ii. Security and Accreditation Posture – Ability to comply with applicable 464 cybersecurity frameworks. The Government will choose the proposals that 465 clearly demonstrate compliance with cybersecurity frameworks, robust risk 466 management, and data protection will be prioritized to ensure security 467 integrity and operational continuity. 468

iii. Vendor viability - Demonstrated ability to meet current and projected 469 program demands. The Government will choose the proposal with the best 470 capacity, proven track record, and scalable solution that aligns with the 471 Government’s current and projected needs. 472

iv. OCI Mitigation plan, if applicable – Completed OCI checklist and 473 mitigation plan, if applicable. 474

c. Evaluation: After meeting the un-rated criteria, Phase II proposals will be evaluated 475 against the factors below: 476

i. Technical Merit - Technical executability, alignment with the AOI 477 description, compliance with modern software practices, and standards 478 compliance. The Government will choose the proposal(s) that demonstrate 479 technical feasibility, innovation, and alignment with engineering best 480 practices will be favored, as these factors contribute to the long-term success 481 of the project. 482

ii. Integration Feasibility - Ability to integrate into existing mission operations. 483 The Government will choose the proposal that presents a low-risk, high-484 impact integration plan and minimizes disruption to existing systems and 485 operations will be prioritized. 486

iii. Price – The Government will choose the proposal that demonstrate a 487 reasonable, affordable price that is justified and aligned with the scope and 488 technical merit. Pricing will not be evaluated on a lowest-price basis but must 489 demonstrate value commensurate with scope. Vendors must also provide any 490 proposed investment by the vendor or on behalf of the vendor for the proposed 491 prototype solution including investment source and background information. 492

d. Evaluation Method: Scientific, technological, or other subject-matter expert peer 493 review will be performed. 494

e. Proposals will not be evaluated against each other, as they are not submitted in 495 response to a common PWS or SOW. 496

b. Outcome: The Government may: 497

i. Select proposals for negotiation leading to award 498

ii. Fund all, some, part of, or none of the proposals 499

f. Other Award Considerations 501

To be eligible for FAR-based awards under DFARS 212.70, offerors must: 503

• Be registered in the System for Award Management (SAM) at www.sam.gov; 505

• Be determined responsible under FAR 9.104; 506

• Have updated required representations and certifications (FAR 52.204-26) 507

• Comply with DFARS 252.204-7019/7020 (current NIST SP 800-171 assessment 508 posted in Supplier Performance Risk System (SPRS), if applicable) 509

• Submit a Small Business Subcontracting Plan if a large business (per FAR 510

52.219-9, DFARS 252.219-7003/7004. 511

To be eligible for OTA awards under 10 U.S.C. §§ 4021-4022, offerors must: 513

• Demonstrate capability, resources and integrity to perform; 515

• Be in good standing (not debarred/suspended, and not on the SSC Contractor 516

Responsibility Watchlist); 517

• Comply with program-specific security and cybersecurity requirements, as 518 applicable; 519

• Disclose potential organizational conflict of interest. The Government may 520 require a mitigation approach before award; 521

• While sam.gov registration is not required for OTA awards, offerors are 522 encouraged to register to facilitate payment and administrative actions. 523

ATTACHMENT 4: AREAS OF INTEREST (AOI) 525

The Kronos PMO is interested in innovative products, technologies, and services related to the AOIs 527 listed below. The level of detail provided for each topic or the order in which they appear is not 528 intended to convey any information regarding relative priority. 529 AOI 01: Operational Command and Control 531 The Kronos PMO is seeking innovative solutions that enable end-to-end C2 functionality, including 533 planning, preparation, execution, and assessment, within a unified, interoperable framework. Key 534 capabilities include developing and prioritizing commander’s intent; supporting both deliberate and 535 dynamic target development and effects-based operations; conducting capability and feasibility 536 analysis; facilitating commander’s decision-making and force assignment; monitoring real-time 537 mission execution with adaptability to changing conditions; performing combat assessment; and 538 providing comprehensive shared situational awareness across joint, and allied partners. The 539 innovative solution must be scalable, modular, and extensible to support evolving mission needs and 540 emerging technologies. Cloud-native design, DevSecOps practices, AI/ML integration, advanced 541 data management, and zero trust cybersecurity principles are highly desired. Submissions should 542 demonstrate how the proposed solution delivers a cohesive, resilient, and adaptable C2 capability 543 aligned with U.S. Space Force operational priorities and enables agile, data-driven decision-making 544 across the Kronos Enterprise. 545

Phase I Accepted Until

Phase I PowerPoint and White Paper 12:00 pm MT on 11 Dec 2025

AOI General Questions SSC.BMZ.SYD85@spaceforce.mil

AOI 02: Battle Management 551

The Kronos PMO is seeking an integrated Space Attack Planning Toolkit to enable advanced 553 effects-based planning and coordination across the Kronos Enterprise. The desired solution will 554 support the ability to match space resources to effects-based requirements by synthesizing 555 commander’s guidance, effects, and operational priorities with real-time resource status, including 556 tactical units and ISR assets. The solution should expedite C2 planning and enhance coordination 557 between operational and tactical levels. Key capabilities include integration of tactical C2 558 assessment tools to enable rapid course of action development, feasibility modeling, probability 559 of success analysis, and collateral impact assessment. The solution should support tactical C2 560 planning by providing real-time status, warnings, and orders to tactical units, while capturing and 561 managing CONOPs and CONEMPs to ensure coherent command relationships and execution 562 pathways. Additionally, the toolkit must enable tactical C2 monitoring and visualization of 563 ongoing effects, support dynamic guidance updates, and facilitate responsive coordination with 564 tactical units within established rules of engagement. The solution must be modular, scalable, and 565 designed for seamless integration with the broader Kronos C2 architecture, with an emphasis on 566 agility, real-time data integration, and operational relevance. 567

Phase I Accepted Until

Phase I PowerPoint and White Paper 12:00 pm MT on 11 Dec 2025

AOI General Questions SSC.BMZ.SYD85@spaceforce.mil

AOI 03: Space Intelligence 573

The Kronos PMO is seeking an integrated Intelligence solution to enhance decision advantage for 574 joint and coalition forces across the Kronos Enterprise. The desired solution must unify three core 575 intelligence capabilities: battlespace characterization, collection operations, and targeting. 576 Battlespace characterization should enable continuous understanding and prediction of adversary 577 capabilities, tactics, dispositions, centers of gravity, and courses of action, with dynamic assessments 578 that inform targeting and operational decision-making. Collection operations must support the 579 tasking and synchronization of ISR assets and exploitation resources to acquire actionable data on 580 the operational environment, adversary activity, and infrastructure, closing intelligence gaps and 581 enhancing situational awareness. The targeting component must provide a continuous, analytic 582 process to select, prioritize, and engage targets in alignment with commander objectives, integrating 583 intelligence at every stage of the targeting cycle. The solution must facilitate seamless coordination 584 across functional disciplines and between operational and tactical levels. Scalability, modularity, and 585 interoperability with the broader Kronos C2 architecture are essential, with emphasis on real-time 586 data integration, dynamic visualization, and AI/ML-driven analytic capabilities. Submissions should 587 clearly demonstrate how the solution enhances intelligence-driven operations and supports timely, 588 informed, and effective decision-making across the joint force. 589

Phase I Accepted Until

Phase I PowerPoint and White Paper 12:00 pm MT on 11 Dec 2025

AOI General Questions SSC.BMZ.SYD85@spaceforce.mil