(U) 00. HADES_Section L_20260901_v4.4.pdf

UNCLASSIFIED

HYBRID ARCHITECTURE AND DEVELOPMENT FOR

EXPERIMENTAL SYSTEMS (HADES) SERVICES

PART IV – REPRESENTATIONS AND INSTRUCTIONS

SECTION L – INSTRUCTIONS, CONDITION AND NOTICES

TO OFFERORS

FA8809-26-R-B002

SPACE SYSTEMS COMMAND (SSC)

SYSTEMS DELTA 89 (SYD89)

INNOVATION AND PROTOTYPING DELTA (SD)

INNOVATION AND PROTOTYPING DIVISION GROUND (SDG)

KIRTLAND AFB, NM

31 JULY 2026

Distribution Statement A. Approved for public release. Distribution is unlimited.

Destruction Notice: For unclassified, limited documents, destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

i

Innovation and Prototyping Division Ground

SSC/SYD89/SDG

Kirtland AFB, NM

9/1/2026

HYBRID ARCHITECTURE AND DEVELOPMENT FOR

EXPERIMENTAL SYSTEMS (HADES) SERVICES

PART IV – REPRESENTATIONS AND INSTRUCTIONS

SECTION L – INSTRUCTIONS, CONDITION AND NOTICES TO

OFFERORS

(U) Contents

(U) Contents ................................................................................................................................................................... i

1. (U) PROGRAM OBJECTIVES

1.1 (U) Overview

1.2 (U) GSE Overview

2. (U) GENERAL INSTRUCTIONS

2.1 (U) General Information

2.1.1 (U) Point of Contact

2.1.2 (U) Debriefings

2.1.3 (U) Discrepancies

2.1.4 (U) RFP Documents and Bidders’ Library

2.1.5 (U) Source Selection Information and Secure Communications

2.1.6 (U) Proposal Validity Statement

2.1.7 (U) Use of Non-Government Advisors

2.2 (U) Proposal Organization and Page Limits

2.2.1 (U) Proposal Organization

2.2.1.1 (U) Proposal Organization Table

2.2.1.2 (U) Page Size and Format

2.2.1.3 (U) Page Definition

2.2.1.4 (U) Visual Displays and Graphics

2.2.1.5 (U) Applicability

2.3 (U) Proposal Preparation

2.3.1 (U) Classified Information

2.3.2 (U) Cross-Referencing

2.3.3 (U) Table of Contents

2.3.4 (U) Acronyms and Abbreviations

2.3.5 (U) Electronic Submission Requirements

2.3.5.1 (U) General Submission Instructions

2.3.5.2 (U) File Format and Compatibility

2.3.5.3 (U) File Naming and Labeling

2.3.5.4 (U) Cost/Price Volume Requirements

2.3.5.4.1 (U) Electronic Format Requirements

2.3.5.4.2 (U) Spreadsheet and Formula Requirements

2.4 (U) Proposal Submittal and Deadline

2.4.1 (U) Electronic Delivery Instructions

2.4.2 (U) Deadline and Late Submission Policy

3. (U) VOLUME I – EXECUTIVE SUMMARY

4. (U) VOLUME II – TECHNICAL

4.1 (U) General ii

4.1.1 (U) Volume Organization

4.2 (U) Contractor Work Breakdown Structure (CWBS)

4.3 (U) Technical Subfactors and Instructions for Specific Content

4.3.1 (U) Subfactor 1, Program Management Criteria (Sec M 4.3.1)

4.3.1.1 (U) Staffing/Labor Profile (Sec. M. 4.3.1.1)

4.3.1.1.1 (U) Staffing Matrices

4.3.1.1.2 (U) Labor Profile Matrices

4.3.1.2 (U) Personnel Security (Sec. M. 4.3.1.2)

4.3.1.3 (U) Small Business (Sec. M. 4.3.1.3)

4.3.2 (U) Subfactor 2, Systems Engineering Criteria (Sec. M 4.3.2)

4.3.2.1 (U) Systems Engineering Approach and Methodology (Sec. M 4.3.2.1)

4.3.2.2 (U) Hybrid Environment Expertise (Sec. M 4.3.2.2)

4.3.2.3 (U) Cybersecurity and Configuration Management (Sec. M 4.3.2.3)

4.3.3 (U) Volume II, Attachment 1 – Cross-Reference Matrix

4.3.3.1 (U) Cross-Reference Matrix

5. (U) VOLUME III – COST/PRICE

5.1 (U) General Instructions

5.1.1 (U) Volume Organization

5.1.2 (U) Rounding

5.1.3 (U) Future Ground System Development Scenario (PWS – Not Priced)

5.2 (U) Introductory Section of the Cost/Price Volume

5.2.1 (U) Time-Phased, Person-Loading Graph

5.3 (U) Cost/Price Summaries Estimating Techniques and Methods

5.3.1 (U) Offeror’s Total Proposed Price (TPP) Calculation

5.3.2 (U) Cost Element Summaries

5.4 (U) Discussion of Cost Elements by Task Order CLIN

5.4.1 (U) Mapping of Technical Proposal to Basis of Estimate

5.4.2 (U) Contractor Work Breakdown Structure (CWBS) Summaries

5.4.3 (U) Labor Hour Basis of Estimate

5.4.3.1 (U) Rationale & Justification

5.4.4 (U) Rates

5.4.4.1 (U) Forward Price Rate Agreement/Forward Pricing Rate Recommendation (FPRA/FPRR)

5.4.4.2 (U) Section L, Appendix B Instructions (Labor Rate Pricing Tables)

5.4.4.3 (U) Section L, Appendix C Instructions (Labor Rate Cost Element Summary Tables)

5.4.5 (U) Cost Estimating Relationships (CERs)

5.4.6 (U) Travel by CLIN

5.4.7 (U) Other Direct Costs (ODCs)

5.4.8 (U) Subcontractor/Inter-Divisional Transfers

6. (U) VOLUME IV – PAST PERFORMANCE

6.1 (U) General Instructions

6.1.1 (U) Commercial Client Authorization: Guidance and Alternatives

6.2 (U) Early Proposal Information

6.3 (U) Recent and Relevant Contracts

6.3.1 (U) Specific Content

6.3.1.1 (U) Mapping to TO’s

6.3.1.2 (U) Optional TO-Specific Notation

6.3.1.3 (U) Contract Submission Limits

6.4 (U) Past Performance Volume Organization

6.4.1 (U) Section 1 – Volume Organization

6.4.2 (U) Section 2 – Prime Contractor Narratives

6.4.3 (U) Section 3 – Subcontractor Narratives

6.5 (U) Specific Volume Content

6.5.1 (U) Section 1 – Volume Introduction

6.5.1.1 (U) Introduction

6.5.1.2 (U) Organizational Structure and Responsibilities iii

6.5.1.3 (U) Organizational Structure Change History

6.5.1.4 (U) Contract Data Matrix

6.5.1.5 (U) Past Performance Questionnaire and Tracking Record

6.5.2 (U) Section 2 –Prime Contractor Narratives

6.5.2.1 (U) Instructions for Completing the Relevancy Matrix

6.5.2.2 (U) Contract Performance

6.5.2.2.1 (U) Guidance on Quality Ratings

6.5.3 (U) Section 3 – Relevant Past/Present Performance (Subcontractors)

6.6 (U) Past/Present Performance Questionnaire Responsibilities

6.6.1 (U) Offeror Responsibilities and “Best Efforts” Standard

6.6.2 (U) Treatment of Missing Questionnaires

6.6.3 (U) Alternative Performance Documentation

6.7 (U) Past Performance Volume Attachments

6.7.1 (U) Attachment 1 – Performance Questionnaire

6.7.2 (U) Attachment 2 – Standard Transmittal Letter

6.7.3 (U) Attachment 3 – Subcontractor/Teaming Partner Consent Form

6.7.4 (U) Attachment 4 – Commercial Client Authorization Letter

6.7.5 (U) Attachment 5 – Past Performance Questionnaire Tracking Record

6.7.6 (U) Summary of Attachment Requirements

6.7.7 (U) Offeror Certification

7. (U) VOLUME V – CONTRACT DOCUMENTATION

7.1 (U) Model Contract/Representations and Certifications (Sec. M, 7.5)

7.1.1 (U) Instructions for Completing the Model Contract

7.1.2 (U) Use of the Model Contract in Contract Award

7.2 (U) Model Contract: Sections A through K

7.2.1 (U) Section A – Solicitation/Contract Form

7.2.2 (U) Section B – Supplies or Services and Costs/Prices

7.2.3 (U) Section G – Contract Administrative Data

7.2.4 (U) Section H – Special Contract Requirements

7.2.5 (U) Section I – Contract Clauses

7.2.6 (U) Section J – Attachments to the Model Contract

7.2.6.1 (U) OCI Mitigation Plan

7.2.6.2 (U) Rates

7.2.6.3 (U) Small Business Subcontracting Plan

7.2.6.4 (U) Technical Data Rights

7.2.6.5 (U) Associate Contractor Agreements

7.3 (U) Exceptions to Solicitation Requirements

7.3.1 (U) Statement of Agreement

7.3.2 (U) Authorized Offeror Personnel

7.3.3 (U) Government Offices

7.3.4 (U) Offeror Summary Table

7.3.5 (U) Financial Information

7.4 (U) Potential Organizational Conflict of Interest (OCI)

7.4.1 (U) Offeror Responsibilities

7.4.2 (U) Government Rights and Offeror Obligations

7.4.3 (U) Resolution of OCI Issues

7.4.4 (U) Disclosure Requirements

7.4.4.1 (U) Affirmative Disclosure Obligation

7.4.4.2 (U) What to Disclose (If Applicable)

7.5 (U) Financial Capability Review

7.6 (U) Discussion of Business Systems and Offeror’s Unique Approach

7.6.1 (U) Offeror’s Business Systems

7.6.1.1 (U) Companies with Approved Business Systems

7.6.1.2 (U) Companies with Business System Deficiencies

7.6.1.3 (U) Companies Not Required to Have Government-Approved Business Systems iv

7.6.1.3.1 (U) Accounting System

7.6.1.3.2 (U) Estimating System

Tables

Table 1. (U) Proposal Organization Table 2. (U) Volume II – Technical Volume Organization Table 3. (U) Example Format for Staffing Matrix Per Task Order XX (Task Order Name) Table 4. (U) Example Format for Total Staffing Matrix Rollup Table 5. (U) Example Format for Time-Based Labor Allocation Table by TO Table 6. (U) Example Format for Time-Based Labor Allocation by Position Table 7. (U) Example Cross-Reference Matrix (Technical, Cost/Price, Past Performance) Table 8. (U) Volume III – Cost/Price Organization Table 9. (U) Example Element Summary Table 10. (U) Example Cost Element Summary Table 11. (U) Example Mapping of Technical Proposal Table 12. (U) Example Mapping of Technical Proposal to BOE Table 13. (U) Subcontractor/Inter-Divisional Transfers Cost/Price Analysis Table 14. (U) Timeline of Organizational Structure Changes (Example) Table 15. (U) Relevancy Matrix Overview Table 16. (U) Summary of Section L Attachment Requirements Table 17. (U) Offeror Summary Table

UNCLASSIFIED

Copy no. ____ of ____ copies Innovation and Prototyping Division Ground

SSC/SYD89/SDG

Kirtland AFB, NM

9/1/2026

HYBRID ARCHITECTURE AND DEVELOPMENT FOR

EXPERIMENTAL SYSTEMS (HADES) SERVICES

PART IV – REPRESENTATIONS AND INSTRUCTIONS

SECTION L – INSTRUCTIONS, CONDITION AND NOTICES TO OFFERORS

1. (U) PROGRAM OBJECTIVES.

1.1 (U) Overview The HADES acquisition is for a new, single Indefinite Delivery/Indefinite Quantity (IDIQ) contract for follow-on services supporting the Space Systems Command System Delta 89/Innovation and Prototyping Division Ground (SSC/SYD89/SDG) at Kirtland Air Force Base, NM. This contract will provide engineering, development, integration, and sustainment services supporting the United States Space Force (USSF) Research and Development Space and Missile Operations (RDSMO) Ground System Enterprise (GSE).

This solicitation includes the HADES IDIQ contract and four initial Task Orders (TOs):

• Task Order 01: Transition (No Separate Performance Work Statement (PWS))

• Task Order 02: Ground Control (Section L, Attachment D)

• Task Order 03: JAGUAR (Section L, Attachment E)

• Task Order 04: Ground Support (Section L, Attachment F)

These initial TOs are representative of the types, scope, and complexity of work anticipated under future Task Orders issued against the IDIQ contract.

The SSC/SDG mission is to operate and sustain an affordable, multi-mission Ground Support Equipment (GSE) that supports simultaneous Research & Development (R&D) and demonstration missions across multiple classification levels. The organization develops innovative solutions to reduce Operations & Maintenance (O&M) costs and provides a test bed to prove out emerging concepts. Additionally, SSC/SDG strives to remain a viable choice for all new ground Command and Control (C2) programs. SSC/SDG operates in a dynamic environment requiring rapid response to emerging requirements while maintaining operational continuity across developmental, test, and operational missions. SSC/SDG provides a collaborative partnership among these units to seamlessly develop and rapidly field new capabilities, standardize satellite operations, and exploit core competencies and strengths.

1.2 (U) GSE Overview The GSE represents the entire ground infrastructure that falls under the RDSMO program. At its foundation, the primary components of the GSE include, but are not limited to, two instances of physical infrastructure hosting fully virtualized instances of core and mission-unique ground system software supporting multiple simultaneous missions across multiple classification levels. This infrastructure is supported by core Common User Equipment (CUE) and communications equipment (COMM). The GSE also encompasses mission-unique software (MUS) requiring development, integration, testing, and sustainment. Supporting these operational elements are configuration management infrastructure across ground system components, operational floors, and missions, as well as cybersecurity controls and compliance frameworks. Additionally, facilities that fall under the RDSMO program are included within the GSE. Contractors will be responsible for systems engineering, software development and integration, testing and verification, configuration management, cybersecurity support, and sustainment activities across the full system lifecycle.

UNCLASSIFIED

2. (U) GENERAL INSTRUCTIONS.

This section provides general instructions for preparing and submitting proposals in response to this Request for Proposal (RFP). Offerors must comply with all instructions in this Section L to ensure their proposals are complete, compliant, and eligible for evaluation.

1. The Offeror's proposal must include all data and information requested by Section L and must be submitted in accordance with these instructions. The proposal shall be compliant with the requirements stated in the HADES IDIQ PWS (Section J, Attachment 1), TO PWSs (Section L, Attachments D-F), and Model Contract (Sections A-K). Non-conformance with the instructions provided in Section L may result in the proposal being determined non-compliant and ineligible for award in accordance with Section M, paragraph 2.

2. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The Government intends to make award without negotiations in accordance with RFO 15.203. Therefore, Offerors are strongly encouraged to submit their most competitive proposal initially and to include their best terms and pricing. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale, specific details, and concrete examples demonstrating how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of the Offeror's facilities, experience, or capabilities and will base its evaluation solely on the information presented in the Offeror's proposal as assessed against the evaluation factors and criteria in Section M.

3. Elaborate brochures, marketing materials, detailed artwork, or other embellishments are unnecessary and are not desired. Proposals should focus on substantive content addressing the evaluation criteria in Section M.

4. The proposal validity period is 270 calendar days from the proposal due date as specified in Section A, Block 9.

The Offeror shall include a clear statement in Volume V (Contract Documentation) confirming that the proposal is valid through this date in accordance with Section L, paragraph 2.1.6.

5. In accordance with RFO 4.309 (Storage, handling, and contract files), the Government will retain one electronic copy of all unsuccessful proposals for the official contract file. Unless the Offeror requests otherwise in writing, the Government will delete additional electronic copies of unsuccessful proposals after the retention period specified in RFO 4.309 Table 4-3.

2.1 (U) General Information

2.1.1 (U) Point of Contact The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. All communications regarding this solicitation must be directed to the PCO identified below:

Lt Col John Purcell, PCO

SSC/SYD89/SFPEO-SCP/PK

Email: john.purcell.3@spaceforce.mil Phone: (505) 853-7664

Questions or requests for clarification must be submitted in writing via email to the address above. Telephone inquiries will not be accepted except for administrative matters (e.g., file transfer issues, SAM.gov access problems).

2.1.2 (U) Debriefings Offerors may request a pre-award or post-award debriefing in accordance with RFO 15.206-2 or RFO 15.301-1, respectively. Debriefing requests must be submitted in writing to the PCO within the timeframes specified in RFO 15.206-2(a) (pre-award) or RFO 15.301-1(a) (post-award). Failure to request a debriefing within the specified timeframes may result in loss of the right to a debriefing and may affect protest timeliness.

2.1.3 (U) Discrepancies If an Offeror believes that the solicitation contains an error, omission, inconsistency, or ambiguity, the Offeror shall notify the PCO in writing as soon as possible, but no later than 14 calendar days before the proposal due date. The notification must include identification of the specific solicitation section and paragraph containing the alleged error or ambiguity, a detailed explanation of the issue, supporting rationale, and a proposed remedy or clarification. The Government will respond to questions through written amendments to the solicitation issued via SAM.gov. Offerors are responsible for monitoring SAM.gov for amendments and must acknowledge all amendments in accordance with the instructions in each amendment. The Government is not bound by oral explanations or instructions, and only written amendments to the Solicitation will modify its requirements. Offerors are reminded that the Government

UNCLASSIFIED

intends to make award without negotiations in accordance with RFO 15.203. Offerors should not rely on the opportunity to clarify or revise proposals after submission and should submit their best proposal initially.

2.1.4 (U) RFP Documents and Bidders’ Library The solicitation documents are available on SAM.gov (www.sam.gov) under Solicitation Number FA8809-26-R- B002. Offerors are strongly encouraged to subscribe to email notifications on SAM.gov for this solicitation to receive real-time alerts when amendments or additional information is posted, download all solicitation documents immediately and verify file integrity, monitor SAM.gov regularly for amendments throughout the solicitation period and retain all solicitation documents and amendments for reference during proposal preparation. Oral presentations will not be conducted for this acquisition.

2.1.5 (U) Source Selection Information and Secure Communications All exchanges of source selection information between the Government and Offerors will be controlled by the PCO in accordance with RFO 2.101 and RFO 3.104. Source selection information will be transmitted to Offerors using one of the following secure methods:

• Encrypted Email: Email may be used if both the Government and Offeror can send and receive encrypted email. All emails containing source selection information must include "Source Selection Information - See RFO 2.101 & 3.104" in the subject line.

• DoD Safe: The Government may use DoD Safe (https://safe.apps.mil/) to transmit large files or source selection sensitive documents. Offerors will receive a download link via email (if required).

2.1.6 (U) Proposal Validity Statement The Offeror's shall clearly state that their proposal is valid for 270 calendar days from the proposal’s due date.

2.1.7 (U) Use of Non-Government Advisors Proposal information submitted in response to this solicitation will be made available to individuals working for the following organizations: as non-Government advisors for evaluation advisement and proposal analysis.

The Aerospace Corporation 2350 E. El Segundo Blvd., El Segundo, CA 90245

All non-Government advisors have signed nondisclosure agreements (NDAs) with the Government that strictly prohibit the release or disclosure of proposal information outside the source selection team, the use of proposal information for any purpose other than supporting this source selection, and/or the disclosure of source selection sensitive information. In addition, these non-Government advisor contract(s) require the contractor to execute associate contractor agreements reasonably necessary to conduct services. Therefore, the Offeror is highly encouraged to work with these contractor(s) to secure any agreement deemed reasonably necessary as an additional safeguard.

The Offeror shall submit written notification to the PCO if it objects to the release of its proposal information to the above-mentioned non-Government advisors. This objection must be transmitted via mail or email no later than 15 calendar days after solicitation release

2.2 (U) Proposal Organization and Page Limits Proper organization ensures efficient evaluation and enables evaluators to locate information required to assess proposals against the evaluation criteria in Section M. Page limits are strictly enforced, and pages exceeding the specified limits will not be read or evaluated.

2.2.1 (U) Proposal Organization

2.2.1.1 (U) Proposal Organization Table Offerors shall organize the proposal in accordance with Table 1 (Proposal Organization) below. Each volume shall be submitted as a separate electronic file with the file naming convention specified in Section L, paragraph 2.3.5.3.

All volumes must be submitted to be considered for award. Each volume shall be complete and stand-alone, with minimal cross-referencing between volumes.

http://www.sam.gov/ https://safe.apps.mil/

UNCLASSIFIED

Table 1. (U) Proposal Organization

Volume

Section L Para. Volume Title Page Limit Evaluated

I 3.0 Executive Summary 3 Not Scored

II

4.0 Technical Proposal See Below Yes (M 4.0)

4.3 Technical Volume Narrative - -

4.3.1 -Subfactor 1: Program Management Criteria 25 Yes (M 4.3.1)

4.3.1.1

4.3.1.2 4.3.1.3

- Staffing/Labor Profile narrative (staffing and labor profile matrices, as well as resumes do not count against page limit)

- Personnel Security Requirements

- Small Business

Incl. Above Incl. Above

Yes (M 4.3.1.1) Yes (M 4.3.1.2) Yes (M 4.3.1.3)

4.3.2 -Subfactor 2: Systems Engineering Criteria 32 Yes (M 4.3.2)

4.3.2.1 4.3.2.2 4.3.2.3

- Systems Engineering Approach and Methodology

- Hybrid Environment Expertise

- Cybersecurity and Configuration Management

Incl. Above Incl. Above Incl. Above

Yes (M 4.3.2.1) Yes (M 4.3.2.2) Yes (M 4.3.2.3)

4.3.3 Vol II, Attachment 1, Cross-Reference Matrix Unlimited Not Scored

2.3.4 Vol II, Attachment 2, Acronyms and Abbreviations Unlimited Not Scored

4.2 Vol II, Attachment 3, Contractor Work Breakdown Structure Unlimited Not Scored

- VOLUME II TOTAL PAGE LIMIT:

(Excludes CWBS and Cross-Reference Matrix) 57 -

III 5.0 Cost / Price Unlimited Yes (M 5.0)

IV

6.0 Past Performance See Below Yes (M 6.0)

6.4.1 • Section 1: Volume Introduction Unlimited Not Scored

6.5.2 • Section 2: Prime Contractor Narratives (max 5 contracts, ~4 pages each) * see Section 6.6.3 20 Yes

6.5.3 • Section 3: Subcontractor Narratives (major subs only, ~3 pages each) * see Section 6.6.3 10 Yes

VOLUME IV TOTAL PAGE LIMIT:

(Sections 2 & 3 Only) (Excludes Section 1, Matrices, Forms, & Tracking Records)

30 -

V 7.0 Contract Documentation Unlimited Compliance Review Only

Total Evaluated Narrative Page Limit (Volume I: 3 + Volume II: 57 + Volume IV: 30) 90 -

UNCLASSIFIED

2.2.1.2 (U) Page Size and Format

2.2.1.3 (U) Page Definition A page is defined as one face of an 8.5 × 11-inch sheet, not including foldouts, containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Pages shall have line spacing no less than single-spaced, and text size no less than 12-point Times New Roman (or equivalent serif font), 10-point minimum for headers, footers, tables, charts and figures. Margins shall be no less than 1.0 inch (top/bottom) and 0.75 inch (sides). Pages shall be numbered sequentially by volume. Page limits are MAXIMUMS and are strictly enforced.

Pages exceeding the specified limit will not be read or evaluated.

The following are counted toward page limits: all narrative text pages, all tables, charts, graphs, and figures (including those embedded in narrative), organizational charts, diagrams, and flowcharts, sample documents, templates, or examples, title pages for sections or subsections, and pages with headers/footers only if they contain proposal content.

The following pages are excluded from page count limits: volume cover pages (one per volume), volume table of contents (one per volume), section dividers clearly marked "DIVIDER" or "SECTION X BEGINS," blank pages inserted for formatting clearly marked "This page intentionally left blank," acronym lists and glossaries (one per volume), and attachments specifically designated as "Unlimited" in Table 1. All other pages containing any text, graphics, tables, or images are counted toward page limits.

2.2.1.4 (U) Visual Displays and Graphics Offerors are encouraged to use tables, charts, graphs, diagrams, and figures to clearly convey information. All visuals must be legible (minimum 10-point font, 300 DPI resolution recommended), clearly labeled with titles and legends, and referenced in the narrative. Color is permitted, but information must be discernible in grayscale. Visual displays count toward page limits (one page per 8.5 × 11-inch or 11 × 17-inch foldout).

2.2.1.5 (U) Applicability These requirements apply to all proposal volumes (I-V), responses to Evaluation Notices (ENs), and Final Proposal Revisions (FPRs). Externally generated documents (e.g., CPARS reports, financial statements) may be submitted in their original format if legible. Requests for exceptions must be submitted to the PCO at least 15 calendar days before the proposal due date.

2.3 (U) Proposal Preparation

2.3.1 (U) Classified Information The Government does not anticipate the need for classified responses to this solicitation. All proposal volumes (Volumes I–V) shall be UNCLASSIFIED. The only anticipated need for classified information is to support past performance references for classified programs. In such cases, Offerors shall provide unclassified descriptions of the work performed in the unclassified proposal volumes and may submit a one-page classified key to enable Government correlation to specific classified contracts.

Under no circumstances shall Offerors include classified material in any unclassified proposal volume (Volumes I– V). The Government will not accept or evaluate classified information in any proposal volume except as specified below. The sole exception is a one-page classified key for past performance cross-references, submitted as a standalone classified supplement. This classified key is the only classified material that will be accepted with the proposal. The classified key shall be provided within a one-page, standalone classified supplement.

The Offeror shall submit at the appropriate classification (TOP SECRET/SENSITIVE COMPARTMENTED INFORMATION, TOP SECRET, SECRET, etc.) level. Each entry in the classified key shall be referenced to the unclassified proposal volume, page number, and paragraph number to which it applies. The one-page classified key will not count against the page limitations for Volume II, paragraph 4.0.

If the Offeror wishes to submit a classified key, the Offeror shall submit the request in writing to the PCO (information found in Sec L, 2.4). The PCO shall provide requested information by encrypted email or DoD SAFE transmittal.

UNCLASSIFIED

2.3.2 (U) Cross-Referencing Each volume shall be written on a stand-alone basis to minimize cross-referencing to other volumes. Evaluators will review each volume independently and are not required to search other volumes for information that should be contained within the designated volume. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal and will not be evaluated.

Cross-references within the same volume (e.g., from one section of Volume II to another section of Volume II) are permitted and may be used to avoid unnecessary repetition, provided the referenced information is clearly identified and easily located. Exception: Volume II, Technical Proposal, may reference the Small Business Subcontracting Plan submitted in Volume V, Contract Documentation, for the sole purpose of demonstrating compliance with the Small Business participation evaluation criterion under the Program Management subfactor in Section M. The substantive description of the small business approach shall remain in Volume II; Volume V may be cited as supporting documentation.

2.3.3 (U) Table of Contents Each volume shall contain a Table of Contents with electronic hyperlinks or bookmarks to major sections and subsections (at least down to the second level). The Table of Contents shall appear at the beginning of each volume and shall not count against the page limitations for that volume. Offerors shall ensure that hyperlinks/bookmarks function correctly in the submitted electronic files to facilitate efficient evaluation.

2.3.4 (U) Acronyms and Abbreviations Each volume shall contain a glossary defining all abbreviations and acronyms used in that volume. Glossaries shall be placed at the end of each volume and do not count against the page limitations for their respective volumes.

Acronyms should be spelled out on first use in the text, followed by the acronym in parentheses (e.g., Ground System Enterprise (GSE)) and may be used alone thereafter.

2.3.5 (U) Electronic Submission Requirements

2.3.5.1 (U) General Submission Instructions Offerors shall submit electronic copies of their proposals via the Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil/, in accordance with the instructions in Section 2.4.1. The proposal shall be organized into separate electronic files by volume (Volumes I–V) to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments.

Each volume shall be a separate electronic file, clearly named in accordance with Section L, 2.3.5.3. The primary evaluation format for narrative content shall be PDF, and Offerors shall provide searchable PDF files (with "Select," "Print," and "Copy" enabled) for all narrative volumes. Native format files (e.g., Microsoft Excel for cost models, Microsoft Project for schedules) shall also be provided where required. These native files will be used for detailed analysis and validation of calculations. If any files are compressed (e.g., in .zip format), the Offeror shall ensure that the Government can open the files using standard tools available on Government workstations, and proprietary or non-standard decompression software shall not be required. Offerors shall verify that all submitted files are free of viruses and malware and can be opened on a Microsoft Windows 11 environment.

The Government is not responsible for corrupt, unreadable, or password-protected files. Offerors are strongly encouraged to submit proposals early enough to identify and resolve any technical issues prior to the submission deadline.

2.3.5.2 (U) File Format and Compatibility All electronic files shall be submitted in the following formats, as applicable:

• PDF: Adobe Acrobat-compatible PDF files (with “Select,” “Print,” and “Copy” enabled) for all narrative volumes. PDFs shall be text-searchable (i.e., not image-only scans).

• Microsoft Word: .docx for any editable narrative documents, if requested.

• Microsoft Excel: .xlsx for all cost/pricing models and spreadsheets.

• Microsoft Project: .mpp for any schedule files, if applicable.

• Microsoft PowerPoint: .pptx for any briefing-style materials, if applicable.

https://piee.eb.mil/

UNCLASSIFIED

All electronic files shall be compatible with Microsoft Windows 11 and current versions of Microsoft Office and Adobe Acrobat Reader available on Government workstations.

2.3.5.3 (U) File Naming and Labeling Electronic files shall be named using the following convention:

[Offeror Name]_[Volume]_[Section]_[Date]

Example: CompanyXYZ_Vol_II_Technical_20260722.pdf

Each volume shall include a cover page clearly identifying Solicitation number (FA8809-26-R-B002), Volume title and volume number, Offeror name, Submission date, Classification level (if applicable).

2.3.5.4 (U) Cost/Price Volume Requirements The Cost/Price Volume shall comply with the following electronic format and technical requirements to facilitate Government evaluation and analysis.

2.3.5.4.1 (U) Electronic Format Requirements The official copy of the Offeror's Cost/Price Volume (Volume III) shall be submitted in the electronic formats specified in Section 2.3.5.2. In the event of any discrepancies in data across files in different formats, the Microsoft Excel file(s) containing the original calculations shall be considered controlling for evaluation purposes.

2.3.5.4.2 (U) Spreadsheet and Formula Requirements All Microsoft Excel files submitted in the Cost/Price Volume shall:

a. Use formulas (not hard-coded values) for all calculated fields, including subtotals, totals, rates, and escalation factors, to preserve the calculation logic.

b. Include all cost/pricing models used to develop the estimate, with all tabs and linkages intact.

c. Use the “Group and Outline” feature, where appropriate, to facilitate Government review and drill-down into detail.

d. Use the “link cell” feature for workbooks that span multiple spreadsheets, ensuring that all links are functional and contained within the submitted files (no links to external files).

e. Be consistent with the Offeror’s approved estimating system and replicate the logic and mathematical formulas reflected in the official copy of the proposal.

Offerors should ensure that all Excel files open without error, that all formulas are visible and traceable, and that no cells required for evaluation are locked or password protected.

2.4 (U) Proposal Submittal and Deadline

2.4.1 (U) Electronic Delivery Instructions Proposals shall be submitted electronically via the Procurement Integrated Enterprise Environment (PIEE) (https://piee.eb.mil/) in accordance with Section 2.3.6.1 and the solicitation-specific PIEE instructions provided in Section A or by separate notice.

Proposals shall be addressed and delivered to the Procuring Contracting Officer (PCO):

SSC/SYD89/SFPEO-SCP/PK

Attn: Lt. Col John Purcell Email: john.purcell.3@spaceforce.mil

Offerors are responsible for completing any required PIEE registration and role assignment in advance of proposal submission. Offerors must also ensure all required volumes and files are successfully uploaded and submitted in PIEE prior to the proposal deadline. It is prudent that the Offeror allow sufficient time to resolve any technical issues before the deadline. If an Offeror experiences technical issues with PIEE that may affect timely submission, the Offeror shall immediately document the issue (e.g., screenshots, error messages, timestamps) and notify the PCO via email as soon as practicable, prior to the submission deadline, describing the issue and attempted resolution steps. The Government is not responsible for proposals that are not successfully delivered due to technical issues, transmission errors, or other problems within the Offeror’s control.

https://piee.eb.mil/

UNCLASSIFIED

2.4.2 (U) Deadline and Late Submission Policy Proposals shall be RECEIVED by the PCO no later than 1300 Mountain Time (MT) on 17 September 2026.

Proposals received after the specified date and time shall be treated in accordance with RFO 52.215-1.

Mountain Time should be interpreted as Mountain Standard Time (MST) [November – March] or Mountain Daylight Time (MDT) [March – November] as applicable on the proposal due date.

3. (U) VOLUME I – EXECUTIVE SUMMARY.

The Executive Summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal and will not be used in evaluation for any criteria

Any material presented in the Executive Summary shall be considered informational only and shall not be considered as meeting the requirements for any portions of other volumes of the proposal. Evaluators will not rely on the Executive Summary to assess compliance with, or responsiveness to, specific Section L instructions or Section M evaluation criteria.

4. (U) VOLUME II – TECHNICAL.

4.1 (U) General The Technical Volume shall be specific, complete, and internally consistent. Legibility, clarity, and coherence are critical to effective evaluation. Proposals will be evaluated against the Technical subfactors and criteria defined in Section M, Evaluation Factors for Award.

Using the instructions provided in this Section L, paragraph 4.0, the Offeror shall describe, as specifically as possible, the actual methods, processes, tools, and organizational approaches it will use to accomplish and satisfy the Technical subfactors.

All requirements specified in the solicitation, including the HADES IDIQ PWS (Section J, Attachment 1) and the initial Task Order PWSs are mandatory. By submitting a proposal, the Offeror represents that it will perform all requirements specified in the solicitation. It is not necessary or desirable for the Offeror to state that it “understands” or “will comply with” the requirements.

Cost/Price information (e.g., specific dollar amounts, rates, or fee percentages) shall NOT be included in the Technical Volume. High-level references to affordability or cost-effectiveness are permissible, but all detailed pricing information shall be confined to Volume III, Cost/Price.

4.1.1 (U) Volume Organization Volume II shall provide a consolidated technical proposal with a Cross-Reference Matrix providing traceability between the proposal, PWS requirements, and Section M evaluation criteria. Volume II shall be organized according to the following general outline:

Table 2. (U) Volume II – Technical Volume Organization

Section L Para.

Volume II Sec. Content

4.3 - Technical Volume Narrative

4.3.1 1 -Subfactor 1: Program Management Criteria

4.3.1.1 4.3.1.2 4.3.1.3

• Staffing/Labor Profile

• Personnel Security Requirements

• Small Business

4.3.2 2 -Subfactor 2: Systems Engineering Criteria

UNCLASSIFIED

4.3.2.1 4.3.2.2 4.3.2.3

• Systems Engineering Approach and Methodology

• Hybrid Environment Expertise

• Cybersecurity and Configuration Management

4.3.3 3 Vol II, Attachment 1, Cross-Reference Matrix

2.3.4 4 Vol II, Attachment 2, Acronyms and Abbreviations

4.2 5 Vol II, Attachment 3, Contractor Work Breakdown Structure

4.2 (U) Contractor Work Breakdown Structure (CWBS) The Offeror shall define a CWBS to at least the third level that:

• Provides traceability to the HADES IDIQ and Task Order PWSs

• Maps to Government Level 1 PWS elements: 5.0 Basic Services

• Remains consistent with the technical approach and is used consistently across Volumes II (Technical), III

(Cost/Price), and IV (Past Performance)

Submit the CWBS as Volume II, Attachment 3 in the native excel format and does not count against the Volume II page limit.

4.3 (U) Technical Subfactors and Instructions for Specific Content The Technical Volume (Volume II) shall address each Technical subfactor in the structure and order specified below. Offeror responses shall demonstrate adequacy, tailoring, and feasibility for executing the HADES Basic IDIQ and all initial Task Order PWSs. Offerors shall follow these instructions to ensure their proposals are complete, compliant, and aligned with the evaluation criteria in Section M.

Offerors shall clearly label each subfactor section in Volume II and organize content in the same order. The instructions in this Section L, paragraph 4.3, correspond directly to the Technical evaluation criteria in Section M, paragraph 4.3. Offerors shall provide their own Cross-Reference Matrix (Volume II, Attachment 1; Table 7) to show where in their proposal each instruction and evaluation criterion is addressed.

a. (U) Future Ground System Development PWS The Government has provided a Future Ground System Development PWS in the Bidder’s Library. This Future Ground System Development PWS is an evaluation scenario only and will not be awarded as an initial Task Order under this solicitation. The Future Ground PWS shall be used only to inform the Offeror’s description of its Staffing approach and Systems Engineering lifecycle, approach, and methodology under Subfactor 2 (Section L

4.3.2.1 and 4.3.2.2), and demonstrate the Offeror’s ability to plan and execute a future, multi-mission, multi-classification ground system within the HADES environment. The Future Ground PWS shall not be priced or mapped to any CLINs in Volume III (Cost/Price), included in the Total Proposed Price (TPP) or Total Evaluated Price (TEP), or treated as an actual Task Order to be awarded as part of this source selection.

4.3.1 (U) Subfactor 1, Program Management Criteria (Sec M 4.3.1)

4.3.1.1 (U) Staffing/Labor Profile (Sec. M. 4.3.1.1) The Offeror shall provide an organizational chart that illustrates the IDIQ management structure and planned workforce structure; management and key personnel positions must align to Position titles in the Staffing Matrices.

The Offeror shall describe how they will address all initial Task Orders and are expected to be able to support concurrent Task Orders. Description of staffing approaches shall explain the Offeror’s approach to temporary headcount changes, turnover, and attrition associated with concurrent Task Order fulfillment, noting that the Jaguar Task Order does not authorize cross-matrixed personnel.

The Offeror shall propose key personnel and provide resumes for each proposed key personnel on the contract. For resumes, the Offeror shall remove individual names (use anonymous identifiers). Resumes will not count against the volume II page limits.

Additionally, Offerors shall address in narrative form how their proposed HADES staffing model (including labor categories, management structure, and surge/transition handling) could be adapted to execute a future ground system effort as described in the Future Ground System Development PWS and discuss qualitatively how they would augment and reallocate labor (e.g., by phase or discipline) to support concurrent execution of the initial Task Orders and a Future Ground System Development effort. Offerors are not required to provide discrete staffing matrices or labor-hour tables (Tables 3–6) for the Future Ground scenario.

The Offeror shall provide staffing matrices and labor profile matrices in accordance with the instructions below. The narrative for the section Staffing/Labor profile is limited to fifteen (15) pages. The staffing matrices and labor profile matrices do not count against the fifteen (15) page limit.

4.3.1.1.1 (U) Staffing Matrices Using the formats in Table 3 (below), and for each Task Order, the Offeror shall provide completed staffing matrices that cover the first 12 months, starting with the first day after the transition period has ended: *Staffing matrix per task order does not account against the Volume II page limit.

• Task Order 02: Ground Control (Section L, Attachment D)

• Task Order 03: JAGUAR (Section L, Attachment E)

• Task Order 04: Ground Support (Section L, Attachment F)

Table 3. (U) Example Format for Staffing Matrix Per Task Order XX (Task Order Name)

GWBS

(Level 1)

CWBS

(Level 2, 3+)

Position Labor Cat Company/ Subcontractor

# People Total Hours (per Task Order)

Totals per Task Order (Total # People)

(Total # Hours)

Using Table 4 (below), Example format for Total Staffing Matrix Roll-up, the Offeror shall provide a completed Matrix to show the collective staffing work in total for all TOs. *Total Staffing Matrix Roll-up does not count against the volume II page limit.

Table 4. (U) Example Format for Total Staffing Matrix Rollup

NGWBS

(Level 1)

CWBS

(Level 2, 3+)

Position Labor Cat Company/ Subcontractor

# People Total Hours

People)

Hours)

4.3.1.1.2 (U) Labor Profile Matrices The Offeror shall provide a time-based summary of labor hours by Task Order for the first 12 months post-transition and a time-based summary of labor hours by position (or labor category) for the first 12 months post-transition.

The Offeror shall provide a breakout of labor hours associated with each position per month for the 12- months after transition period. Use a format similar to that in Tables 5 and 6 produced in MS Excel. The excel document submission does not count against the Volume II page limit. Offerors may also submit a MS project file as an attachment to this volume; MS Project file will not count against page limit.

Table 5. (U) Example Format for Time-Based Labor Allocation Table by TO

Task Order Month Total

Hours M1 M2 M3 M4 M5 M6 M7 M8 M9 M10 M11 M12

UNCLASSIFIED

Ground Control 60 60 60 20 20 20 20 20 20 20 20 60 400

JAGUAR 0 0 0 0 0 0 20 0 0 0 20 60 100

Ground Support 0 0 0 20 0 20 70 100 50 20 0 0 280

Total Hours 60 60 60 40 20 40 110 120 70 40 40 120 780

Table 6. (U) Example Format for Time-Based Labor Allocation by Position by TO

Example Categories Month 1 Month 2 Month 3 Month 4 Month 5 Month ….

System Administrator 12 15 22 7 15 27

Network Engineer 12 15 22 7 15 27

ISSE 12 15 22 7 15 27

PM 12 15 22 7 15 27

Systems Engineer 12 15 22 7 15 27

CRO 12 15 22 7 15 27

The Government will assess whether the proposed labor hours and skill mix are sufficient and appropriately time-phased to perform the workload as defined by the initial TO PWSs.

"Sufficient" means adequate to accomplish all PWS requirements within specified timelines.

"Appropriately time-phased" means labor is allocated to align with task dependencies, critical path activities, and mission support continuity requirements.

4.3.1.2 (U) Personnel Security (Sec. M. 4.3.1.2) The Offeror shall describe its approach to meeting personnel security requirements for work performed at the Unclassified/CUI, Secret, and TS/SCI levels in support of HADES.

At a minimum, the Offeror shall describe: (1) Recruitment Strategy for Cleared Personnel, (2) Clearance Processing Approach and Timeline Assumptions, (3) Retention Strategy for Cleared Personnel, (4) Contingency Planning for Clearance-related Issues.

4.3.1.3 (U) Small Business (Sec. M. 4.3.1.3) The Offeror shall (1) provide its Small Business Participation Commitment Document (SBPCD) and (2) describe how its approach ensures meaningful small business participation throughout contract performance.

At a minimum, the Small Business responses shall address:

• Small Business Participation Commitment Document (SBPCD):

o The SBPCD shall demonstrate compliance with the 25% small business participation requirement of the total subcontracted value, as well as the congressionally mandated 5% goal for small disadvantaged business (SDB). The 5% goal is included within the 25% and not in addition to.

o Explain the methodology used to calculate this percentage, and o Identify, to the extent known at proposal time:

The small business concerns expected to participate (e.g., SB, SDB, WOSB, HUBZone, VOSB, SDVOSB).

Their anticipated roles and responsibilities.

UNCLASSIFIED

The approximate percentage of total contract value and percentage of total subcontracted value associated with each.

Small Businesses listed in the SBPCD should also be listed in any Small Business Subcontracting Plans submitted in accordance with R-DFARS 215.104-70(a)(3).

• Description of Meaningful Small Business Participation:

o The Offeror shall describe how its approach ensures that small businesses will receive meaningful work with appropriate complexity and variety, o Management and Monitoring of Small Business Participation:

The Offeror shall describe how it will manage and monitor small business participation, and

How the Offeror will identify and address any shortfalls in small business participation during contract performance.

4.3.2 (U) Subfactor 2, Systems Engineering Criteria (Sec. M 4.3.2)

4.3.2.1 (U) Systems Engineering Approach and Methodology (Sec. M 4.3.2.1) The Offeror shall describe its Systems Engineering (SE) lifecycle for HADES and all initial Task Orders and the Future Ground System Development PWS Task Order evaluation scenario, noting that such Task Orders may be executed concurrently, including at least the following phases:

• Concept exploration and alternatives analysis.

• Requirements definition, decomposition, and allocation.

• Architecture and design.

• Development and integration.

• Verification and validation (V&V), to include quality assurance and independence of V&V.

• Deployment and transition to operations.

• Operations, sustainment, and eventual decommissioning or disposal, as applicable.

For each phase, the Offeror shall:

• Describe the key SE activities to be performed.

• Identify the primary inputs and outputs (e.g., requirements baselines, design artifacts, test plans, acceptance criteria).

• Describe the entry and exit criteria for transitioning between phases.

Additionally, the Offeror shall include a high-level notional development timeline and schedule utilizing Microsoft Project and a high-level architectural diagram of the Future Ground System Development PWS proposed ground system. The MS Project schedule and high-level architectural diagram does not count against the Volume II page limit.

4.3.2.2 (U) Hybrid Environment Expertise (Sec. M 4.3.2.2) The Offeror shall explain how its SE processes will support simultaneous execution of multiple Task Orders requiring software intensive systems, integration of mission-unique software with common core services, cybersecurity accreditation and assurance, and how such processes will be applied in both cloud and/or local implementations. The identified systems engineering approach shall illustrate cost/schedule/performance trade-offs and highlight system uptime, cost reduction, and responsiveness to emergent requirements. The Offeror shall explain how the SE approach supports rapid insertion of new technologies while maintaining operational continuity and mission assurance.

4.3.2.3 (U) Cybersecurity and Configuration Management (Sec. M 4.3.2.3) The Offeror shall provide processes that demonstrate their approach to integrating Cybersecurity and Configuration Management (to include control of supporting documentation) into their Systems Engineering lifecycle to maintain system configuration across the ground system infrastructure, operational floors, and missions.

4.3.3 (U) Volume II, Attachment 1 – Cross-Reference Matrix

4.3.3.1 (U) Cross-Reference Matrix The Offeror shall provide a Cross-Reference Matrix as Volume II, Attachment 1. The purpose of this matrix is to enable efficient evaluation by mapping, for each applicable requirement and evaluation criterion, where the corresponding response can be found in the Offeror’s proposal.

UNCLASSIFIED

The Government has provided a Section L to Section M Cross-Reference Table (see Section L, paragraph 2.2.1.1, Table 1) as an informational reference showing how the proposal instructions in Section L align with the evaluation criteria in Section M.