0 T3TRK - Program Solicitation.pdf

Program Solicitation SDA-PS-25-02

Proliferated Warfighter Space Architecture

Tranche 3 Tracking Layer (T3TRK)

7 April 2025

DISTRIBUTION STATEMENT A. Approved for public release: distribution unlimited.

Contents 1 Introduction

1.1 Motivation

1.2 Program Approach

1.3 Program Plan and Schedule

1.4 T3 Transport and T3 Tracking Concept of Operations (CONOPS) Overview

2 System Description

3 Selection Process

4 Proposal Preparation Instructions

4.1 Volume I – Management and Processes

4.1.1 Executive Summary

4.1.2 Program Management

4.1.3 Security Performance

4.1.4 Facilities Management

4.1.5 Systems Engineering

4.1.6 Mission Assurance

4.1.7 Organizational Conflict of Interest

4.1.8 Key Personnel Résumés

4.1.9 Personnel Matrix

4.1.10 Technical Data and Computer Software Rights Assertions

4.2 Volume II – Technical Solution

4.2.1 Executive Summary

4.2.2 CONOPS Overview

4.2.3 Space Vehicle (SV) Overview

4.2.4 Spacecraft Bus

4.2.5 Manufacturability

4.2.6 Supply Chain

4.2.7 Test, Demonstration, and Verification

4.2.8 Launch Services Overview

4.2.9 Ground Segment Integration and Operations

4.2.10 Mission Operations, Sustainment, and Disposal

4.2.11 Appendices

4.3 Volume III – Integrated Master Schedule

4.3.1 Integrated Master Schedule (IMS)

4.3.2 Schedule Risk

4.3.3 Appendix – Portfolio IMS

4.4 Volume IV – Price and Rationale

4.4.1 Executive Summary and Pricing Rationale

4.4.2 Price Proposal Structure

4.4.3 Proposal Pricing Details

4.4.4 Government Furnished Equipment, Information, and Property

4.4.5 Major Teammate Proposals

4.5 Volume V – Past Performance

4.5.1 Executive Summary

4.5.2 Recent and Relevant Past Performance

4.6 Volume VI – Other Transaction (OT) Agreement

5 Submission Instructions

5.1 Submission of Major Teammate Proposals

6 Proposal Evaluations

6.1 Evaluation Methodology

6.1.1 Factor 1 – Schedule

6.1.2 Factor 2 – Technical Solution

6.1.3 Factor 3 – Past Performance

6.1.4 Factor 4 – Technical Management and Processes

6.1.5 Factor 5 – On-Orbit Performance Confidence Rating

6.1.6 Factor 6 – Price

6.2 Use of Non-Government Advisors

6.3 Number and Scope of Agreements to be Awarded

6.4 Negotiations and Award

6.5 Other Administrative Information

1 Introduction

The Space Development Agency (SDA) is issuing this Other Transaction Authority (OT) solicitation for a prototyping effort of the Proliferated Warfighter Space Architecture (PWSA) Tranche 3 (T3) Tracking Layer (T3TRK). T3TRK prototyping effort will accelerate the capability to provide global, persistent indications, detection, warning, tracking, and identification of conventional and advanced missile threats, including hypersonic missile systems. The T3 Tracking Layer will also demonstrate a missile defense capability. The T3 Tracking Layer scope includes the procurement and deployment of an anticipated minimum of 54 space vehicles (SVs) with infrared (IR) sensors, in six (6) orbital planes. Additional prototyping of satellites and sensor payloads may also occur under this OT in order to inform requirements and constellation design.

The fully deployed Tracking Layer is estimated to include more than 100 SVs in Low Earth Orbit (LEO) across multiple planes.

All references in this solicitation to Attachment 1a – Statement of Work (SOW) and Attachment 1c – Technical Requirements Document (TRD) pertain to the T3 Tracking Layer Statement of Work and Technical Requirements Document inclusive of its classified appendix.

1.1 Motivation

SDA has determined that the proliferation of various mission functions across the PWSA using commodity spacecraft buses is the most efficient and cost-effective means of evolving the architecture. To accomplish this, SDA employs a capability-focused business model prioritizing speed and lowering costs by harnessing commercial development to achieve proliferation and enhance resilience. The objective is to establish and demonstrate the ability to rapidly evolve development processes and field capability on a significantly faster timeline than historical space system acquisitions. In pursuit of this objective, SDA requires each PWSA Performer’s SVs and communications systems to be interoperable with the SVs and systems developed by all other PWSA performers including those to be deployed in previous Tranches. Additionally, all SVs must operate in an integrated fashion through a common ground system.

1.2 Program Approach

This solicitation seeks Other Transaction Agreement (OTA) proposals under the authority of 10 U.S.C. § 4022 for U.S. space industry builder-operator teams that will engage with SDA to develop and operate the T3 Tracking Layer as part of the PWSA. The Government is purchasing a nominal constellation of 54 (or more) satellites that are sufficient to meet constellation coverage and performance objectives for the T3 Tracking Layer. SDA anticipates purchasing these SVs divided into six (6) orbital planes, to be awarded to more than one (1) vendor, subject to available funding.

The T3 Tracking Layer constellation will include a mix of Missile Warning/Missile Tracking (MW/MT) and Missile Warning, Tracking and Defense (MWTD) infrared (IR) mission payloads.

Three awards are planned for 18 SVs each with either MW/MT or MWTD capability. Each Offeror may propose up to two submissions; one to develop and deliver 18 MW/MT and/or one to develop and deliver 18 MWTD SVs. Each submission shall deliver 18 satellites in two (2) orbital planes, with the associated launch integration, ground support, and operations and sustainment (O&S) capability. Each of the planes will be populated by a single launch on the NSSL contract.

Note that for SDA to make an OT award to the Offeror, at least one of the following conditions must be met:

1. There is at least one (1) nontraditional defense contractor or nonprofit research institution participating, to a significant extent, in the prototype project.

2. All significant participants in the transaction other than the Federal Government are small businesses (including small businesses participating in a program described under section 9 of the Small Business Act (15 U.S.C. 638)) or nontraditional defense contractors.

3. At least one-third of the total cost of the prototype project is to be paid out of funds provided by sources other than the Federal Government.

4. The senior procurement executive for the agency determines in writing that exceptional circumstances justify the use of a transaction that provides for innovative business arrangements or structures that would not be feasible or appropriate under a contract or would provide an opportunity to expand the defense supply base in a manner that would not be practical or feasible under a contract.

1.3 Program Plan and Schedule

The Offeror will propose launch dates for their first and second planes. The Offeror is expected to plan their program in accordance with the milestone dates and deliverables specified in Attachment 1a – SOW and Attachment 1c – TRD of this solicitation. The government’s objective date for the Functional Acceptance Review for the first plane is fourth quarter fiscal year 2029

(4QFY29).

1.4 T3 Transport and T3 Tracking Concept of Operations (CONOPS) Overview

This acquisition assumes the Tranche 3 Tracking Layer SVs are placed into their insertion orbits.

SDA will undergo a continuous checkout and commissioning process to prepare each plane for acceptance into operations conducted out of the Operations Centers (OCs) at Grand Forks, AFB (OC-N) and Redstone Arsenal, AL (OC-S).

After being placed into an insertion orbit by a Government provided NSSL launch vehicle, each plane of SVs will undergo LEOPs, which includes the Separation / Initialization / Checkout / Orbit Raising (SICO) phase and the Functional Acceptance Test (FAT).

SICO includes initial acquisition of the SVs, SV and payload initialization and aliveness checks, orbit raising and phasing to the operational orbit, and Offeror preparation for Government Tranche 3 Program Integrator (T3PI), and Ground Segment (GS) integrator-led acceptance testing.

FAT is then conducted to ensure that each system delivered by the Offeror, comprised of a plane of SVs integrated with the Offeror’s Network Established Beyond the Upper Limits of the Atmosphere (NEBULA) Operations – Vendor Architecture (NOVA) ground system, is fully mission capable. Once FAT and the subsequent Functional Acceptance Review (FAR) are successfully completed, each plane of Tranche 3 SVs will be transitioned to the Operations phase, with operations conducted from the OCs.

T3 commissioning activities will be conducted by the Offeror in coordination with the Tranche 3 Program Integrator and the GS integrator, and these activities will be conducted from the Offeror’s facilities in T3.

SUPERNOVA instances serving LEOPs may exercise a subset of the operational SUPERNOVA’s functional capabilities but will replicate the SUPERNOVA-NOVA interface and key capabilities required to assess NOVA and SV functional capability prior to transition to Operations.

SDA envisions the “exit state” of the commissioning phase to be very similar to the “entry state” to Operations, which is a fully functional, optically-interconnected, and networked plane of SVs commanded and controlled by Offeror personnel using their NOVA ground system with verified interfaces and connectivity with SUPERNOVA.

Once commissioning is complete, each plane of SVs will undergo a similar set of functional tests from the OCs during a brief Operational Acceptance Test (OAT) and begin their transition to Mission Operations. The Offeror will continue to support their vehicles for a period of up to five

(5) years of operations following the transition to Mission Operations, plus the time necessary for disposal.

2 System Description

The T3 Tracking Layer is a pLEO constellation at an altitude of about 1000 km, consisting of six

(6) orbital planes with nine (9) SVs in each plane. Notional constellation parameters are provided in the SOW. Each SV is equipped with an IR mission payload, Optical Communications Terminals (OCTs), and Ka-band communications payloads as well as an S-band backup TT&C system.

The T3 Tracking Layer constellation will include a mix of MW/MT and MWTD infrared (IR) mission payloads. The intent is to achieve near-continuous global stereoscopic coverage for Missile Warning and Missile Tracking and along with SVs equipped with an IR mission payload capable of generating fire control quality tracks for Missile Defense.

This system includes on-orbit calibration capability, on-board processing of Tracking data, and minimization of solar outages. Each SV will have multiple pointing modes to include Nadir- and Ram-Fixed, Off-Earth Inertial Point/Track, Sun Pointing, Solar Avoidance Pointing, and Safe. The SVs must be able to conduct continuous operations without power or thermal constraints.

The T3 Tracking Layer SVs will include OCTs to support crosslinks in-plane, cross-plane, and to the Transport Layer, as well as space-to-ground optical links. Every T3 Tracking Layer SV will be interoperable with all PWSA SVs, and all other T3 Tracking Layer SVs, regardless of vendor.

The system description and requirements can be found in Attachment 1a – Statement of Work and Attachment 1c – Technical Requirements Document of this solicitation. The Offeror shall propose a solution that meets the requirements as laid out in these attachments. Technical Requirement Document To-Be-Refined (TBR) values reflect flexibility. The Offeror may propose an alternate specification with justification. Government agreement on TBR values is expected by SRR.

3 Selection Process

Within this solicitation, the following definitions are used:

• Prime: The Offeror

• Major Teammate: A member of the Prime's development team with a different CAGE code from the prime Offeror, that either accounts for no less than five (5) percent of the proposed cost and/or develops one (1) or more of the following subsystems or capabilities:

o IR Sensor(s) o Onboard IR Mission Data Processor o Optical Communications Terminals o Space Vehicle Bus o System Integration o Operations and Sustainment People, Processes or Tools o NEBULA Operations – Vendor Architecture (NOVA) System o NOVA Ground Infrared Mission Data Processing

If the following subsystems are not procured as commercial off-the-shelf systems (COTS) and/or require significant modifications, then the developer of the subsystem shall be considered a Major Teammate:

o Networking and Data Routing o Encryption o Ka Mission Payload o Backup TT&C System

Major Teammate proposals (regardless of teammate tier) shall contain the information requested in Section 4.4. to allow the Government to review the proposed price and supporting rationale. Major Teammates shall not submit Management & Processes, Technical Solution (or other) volumes. Note that certain information regarding Major Teammates is requested elsewhere in the solicitation but this information should be included as part of the Prime’s proposal.

Major Teammate proposals shall follow the same font, spacing, table, and margin formatting instructions that apply to the Prime.

• Commercial off-the-shelf: COTS products are defined as software or hardware products that are commercially ready-made and available for sale, lease, or license to the general public. For the purposes of this solicitation, products that are less than TRL 7 cannot be considered COTS. If a product requires modifications as part of the T3 Tracking program, then it cannot be considered COTS.

4 Proposal Preparation Instructions

The Offeror shall submit their Tranche 3 Tracking Layer proposal via six (6) volumes. Specific volume contents and associated page limits are detailed below. The Offeror should feel free to arrange the order of the information within each volume as they see fit for clarity, and where page limitations apply, focus on the most critical information. In addition, the Offeror should focus on demonstrating the depth of their design, demonstrating thorough analysis that it achieves the necessary performance, rather than echoing all Government requirements in their response. All volumes must be delivered for each MW/MT and/or MWTD submissions.

Proposals must remain valid for a period of 180 days from proposal due date.

Volume/Section Title Page Limit Due at 1200 EST on 22 May

Volume I Management and Processes 20 pages Table of Contents/Cross Reference

Matrix

Section 1-1 Executive Summary

Section 1-2 Program Management Section 1-3 Security Performance Section 1-4 Facilities Management Section 1-5 Systems Engineering Section 1-6 Mission Assurance Section 1-7 Organizational Conflict of Interest (OCI) ** Section 1-8 Key Personnel Résumés ** Section 1-9 Personnel Matrix ** Section 1-10 Technical Data and Computer Software

Rights Assertion

Volume II Technical Solution 55 Pages (Excludes Appendices)

Table of Contents/Cross Reference Matrix

Section 1 Executive Summary Section 2 CONOPS Overview Section 3 Space Vehicle Overview Tranche 3 Tracking Layer

Payload Architecture and Design

Infrared Mission Payloads Optical Communications

Terminal (OCTs)

Ka Mission Payload Telemetry, Tracking and Control

(TT&C)

Network and Data Routing Red-Side Processing (RSP) Navigation Section 4 Spacecraft Bus Bus Design and Heritage Cybersecurity Encryption Section 5 Manufacturability Section 6 Supply Chain Section 7 Test, Demonstration, and Verification Section 8 Launch Services Overview Section 9 Ground Segment Integration and

Operations

Section 10 Mission Operations, Sustainment, and Disposal

Section 11 ** Appendices Radiometry Analysis 5 pages Metric Analysis 5 pages

Commercial Data Sheets Parameter Specification Excel Master Equipment List (MEL) Excel or Word Mission Availability and

Reliability 5 pages

Volume III Integrated Master Schedule 22 May

Section 1 Integrated Master Schedule (IMS) Unlimited Section 2 Schedule Risk 5 pages Section 3 Appendix – Portfolio IMS 5 pages Volume IV Price and Rationale Unlimited 22 May

Section 1 Executive Summary and Pricing

Rationale

Section 2 Price Proposal Structure Bidding Unit CLIN Structure

Work Breakdown Structure

(WBS)

Milestone Payments

On Orbit Performance Penalty Payment

Section 3 Proposal Pricing Details Additional Pricing Data

Section 4 Government Furnished Equipment, Information, and Property

Section 5 Major Teammate Proposals Volume V Past Performance Section 1 Executive Summary 2 pages Section 2 Recent and Relevant Past Performance Citations (up to 4) to include

POC info 4 pages each (NTE 16 pages)

Volume VI Other Transaction Agreement (OTA) Unlimited Note: Page numbering shall re-start at the beginning of each section or volume.

Note: Classified Addendums are included in the page count identified above.

Note: ** Excluded from page count Note: Cover pages, tables of contents, appendices, cross references and acronym tables are not part of the page count in any volume

• Volume I – Management and Processes shall describe how the Offeror’s proposed program management, systems and mission engineering approaches, processes, and tools enable the Offeror to execute the program on schedule and within the price proposed. This volume shall also contain résumés for key personnel who will perform the T3 Tracking

Layer program and a complete listing of data rights asserted by the Offeror and all of its subcontractors, teammates, and/or vendors.

• Volume II – Technical Solution shall contain a detailed description of the Offeror’s proposed technical solution to accomplish the requirements defined in Attachment 1a – SOW and Attachment 1c – TRD.

• Volume III – Integrated Master Schedule shall contain a complete Integrated Master Schedule. This volume shall also provide: an analysis of schedule risks; identification of key milestones; entrance criteria, key accomplishments and exit criteria for significant reviews and activities; and a clear presentation and analysis of the critical paths(s) from contract award through SV delivery.

• Volume IV – Price and Rationale shall contain the Offeror’s Firm Fixed Price and associated detail.

• Volume V – Past Performance shall contain at least one (1) and may contain up to four

(4) recent (within the last five (5) years), relevant examples of delivery of complex systems, subsystems, or components, preferably space-related hardware or software. Examples must include the Offeror’s schedule and cost/price results for each.

• Volume VI – Other Transaction Agreement (OTA) shall contain the Offeror’s proposed T3 Tracking Other Transaction Agreement, including all attachments.

Normal text for all volumes shall be in Times New Roman font, and the font size shall be no smaller than 12 pt. All text in figures and tables for all volumes shall be in Time News Roman Font, and the font shall be no smaller than 10 pt. A table shall consist of at least two (2) columns in every row. Tables or figures that are deemed attempts to circumvent these text formatting restrictions will be removed from the proposal and not evaluated. All margins (top, bottom, left, and right) shall be no smaller than one (1) inch. Single line spacing shall be used for all text in paragraphs, bulleted lists, and tables. All .pdf pages, in all volumes, formatted larger than 8.5 inches by 11 inches shall be counted as two (2) pages. All .pdf pages, in all volumes, formatted larger than 11 inches by 17 inches will be removed from the proposal and not evaluated. Line numbers shall be applied to all text sections in all volumes and shall be set within the left margin of the page so as not to reduce the usable size of the page. Title pages and tables of contents, tables of figures, and tables of tables will not count against the page counts of the respective volumes and will not be evaluated for content. Note: Nonconforming proposals may be rejected without review.

• A Table of Contents shall be incorporated into Volume I & II and will include a listing of the section titles and subsection titles. Page numbers for each title must be indicated. The Table of Contents shall also include a listing of illustrations and tables with page numbers.

• A cross-reference matrix for Volume I & II is also required. This matrix shall indicate the proposal volume section, subsection, and paragraph, cross-referenced with the appropriate SOW paragraphs, applicable solicitation instructions; evaluation criteria, and deliverables/CDRLs, as applicable.

• A glossary of acronyms and terms for Volume I & II is required. The use of acronyms without definitions within the proposal volume is acceptable; however, the Offeror shall ensure that all acronyms are defined in the glossary for that volume. These pages will not be included in the page count for any volume.

4.1 Volume I – Management and Processes

Volume I shall not exceed the pages limits identified in the table above. Any pages in excess of the allowable content, other than those specifically excluded from the overall page limit, will be removed from the Offeror’s proposal and not evaluated.

4.1.1 Executive Summary

The Offeror shall present their proposed system management and processes solution for the T3 Tracking Layer, including their team construct and expected contributions by each Major Teammate. The Executive Summary should include a summary of the Offeror's programmatic and systems engineering approaches, to include the cost and risk management approaches.

4.1.2 Program Management

The Offeror shall demonstrate their ability to manage and conduct the program to a successful completion on time and within the agreed upon price. The Offeror shall discuss their program, personnel, cost, and risk management approaches, including any processes and tools. The Offeror shall include a list of the primary technical and schedule risks on the project, the planned mitigations, and the approach for managing risks throughout the system life cycle. Risks and mitigations should be focused on execution of the proposed effort. Decisions made while developing the proposed solution (e.g., investments made prior to proposal submission, etc.) are appropriate to cite as risks or mitigations. Schedule management shall be discussed in Volume III;

however, the Offeror is free to cross-reference Volumes I and III if doing so will be of benefit in explaining the value and quality of their approach. The Offeror should describe processes to staff the program with qualified personnel, identify and manage critical vendors and subcontractors, and control costs within a FFP environment.

The Offeror shall describe the schedule and performance risk associated with other commitments by the Prime and subcontractor teams and facilities during the period of performance, including, but not limited to, commitments to other SDA programs. If the Offeror supports other SDA programs, the Offeror shall clearly define how they will support T3 Tracking with minimal disruptions to their existing SDA programs, inclusive of personnel and facilities.

The Offeror shall describe their approach to retaining or obtaining appropriately cleared staff and facilities to support classified work.

The Offeror shall document planned communications with the Government, detailing the purpose, entrance criteria, key accomplishments anticipated, exit criteria, and documentation methodologies for each meeting, review, or key management milestone within the program.

The Offeror shall plan the program using the program reviews identified in Section 2.1 of Attachment 1a – SOW and in accordance with other dates specified throughout Attachment 1a.

The Offeror shall explicitly state the need for any anticipated waivers to Government requirements, standards, and/or compliance documents specified in Attachment 1a – SOW and Attachment 1c – TRD, and its classified appendix. Waivers shall describe how the Offeror’s approach will meet mission needs and provide supporting trades analysis.

4.1.2.1 Subcontractor and Supply Chain Management

The Offeror shall address their subcontractor and supply chain management methodologies. The Offeror shall include a table showing the delivery schedule of critical parts. The Offeror shall present a strategy for managing delivery performance of major subcontractors with finite production capacity to accomplish this program.

The Offeror should describe how they will minimize the effect on the program from fluctuations in supply chain availability and subcontractor deliveries. The Offeror should propose a contingency plan in response to supply shortages for all critical parts to include pricing, supply, and delivery information. The Offeror shall include a sparing plan for critical and long lead parts/units addressing acquisition of critical spares, inventory sources, and associated risks.

The Offeror should provide an assessment of hardware, firmware, and software maintainability, including the availability of manufacturer/developer support for all elements of the design to ensure that enduring product support for security patches and maintenance support remains available over the operational life of the system.

4.1.2.2 Nontraditional Defense Contractors (NDC) / Nonprofit Research Institution

If applicable, the Offeror shall identify which of their subcontractors constitutes an NDC or a nonprofit research institution in accordance with 10 U.S.C. 2302(9). The Offeror shall identify the extent of participation of NDC(s) and/or nonprofit research institution(s) to the Offeror’s T3 Tracking Layer program.

4.1.3 Security Performance

The Offeror shall describe the Offeror's security approach and ability to comply with the security requirements of this solicitation. It should contain the Offeror's security approach, the approach to meeting the clearance requirements for proposed personnel, facility locations, and classified information safeguarding.

4.1.3.1 Facilities Clearance

The Offeror shall identify its proposed location(s) for performing classified efforts for this program. The Offeror is required to hold a current Top Secret facility clearance issued by DCSA in accordance with 32 CFR Part 117 and must provide the complete address and CAGE Code of the facility using Attachment 2 – Personnel & Facilities Template.

4.1.3.2 Key Personnel Clearances

The Key Personnel in the positions of Program Manager, Chief Engineer, Chief Software Engineer, IR Mission Payload Lead, Assembly, Integration and Test (AI&T) Lead, Information Security Certified Professional MUST have current, Top Secret (TS) clearances with SCI eligibility and be available to work at contract start. The Offeror shall provide the required information for the Key Personnel using Attachment 2 – Personnel & Facilities Template.

4.1.3.3 Foreign Ownership and Controlling Interest

The Offeror shall describe its approach for satisfying all requirements of this solicitation related to Foreign Ownership, Control, or Influence (FOCI). The Offeror's security approach should identify, at a minimum, the following:

Compliance with Disclosure of Ownership or Control by a Foreign Government (DFAR 252.209- 7002) and shall include submission of a current SF 328, "Certificate Pertaining to Foreign Interests (FOCI)" if applicable. Offerors must provide the same information for each proposed subcontractor or subsidiary if applicable. If Offerors are foreign owned, they must have an approved FOCI mitigation plan and/or a Cognizant Security Agency (CSA) Security Control Agreement (SCA), or Special Security Agreement (SSA). For Companies that will require access to Collateral, SCI, or COMSEC information, a National Interest Determination (NID) is required.

4.1.3.4 Contract Security Classification Specification (DD254)

The Offeror shall complete Attachment 1f – DD254 and must include the CAGE code and address of all locations where classified work is anticipated.

4.1.4 Facilities Management

The Offeror shall detail the secure facilities that will be used to execute the T3 Tracking program.

The Offeror may reasonably assume that SDA will support co-use arrangements but should not assume that facilities can be newly certified on a schedule suitable for supporting this program.

The Offeror shall include a table listing the primary facilities or rooms to be used. For each item, the Offeror shall provide the area, the maximum classification level, the certification status, the certifying organization, and networks and voice communications capabilities available for use.

The Government expects that regular access to classified networks is important for execution of this program.

4.1.5 Systems Engineering

The Offeror shall demonstrate how their proposed systems engineering processes and methods will be used to deliver a fully compliant T3 Tracking system. The Offeror shall clearly identify their approach to systems engineering and detail the use of any processes and tools that will be used on the program. The Offeror shall identify any reference material, such as corporate command media or published standards, that are used as the basis for their systems engineering approach and discuss how such material will be tailored for the T3 Tracking program. The Government expects that the Offeror will utilize system engineering best practices.

4.1.6 Mission Assurance

The Offeror shall describe the mission assurance approach and Offeror’s quality systems. The Offeror should include a discussion of relevant standards and certifications. In particular, the Government is interested in how the Offeror plans to tailor – if applicable – existing mission assurance processes and tools to meet the requirements of a proliferated LEO constellation designed for a 60-month operational mission life.

4.1.7 Organizational Conflict of Interest

The Government has determined there is potential organizational conflict of interest due to the nature of the anticipated separate solicitations and contracts for the entire Tranche 3 Program. The entire, fully integrated T3 program will likely include multiple T3 SV contractor(s)/performers (primes and subs) and T3 Ground contractor(s)/performers (primes and subs) who will interface with the T3TRK Performer. Therefore, if a T3TRK Performer intends to bid or perform on both T3 SV and T3 non-SV contracts/agreements, there may be an OCI. In addition, the Space Development Agency’s OCI policy clearly states that SDA SETA must remain OCI free within

SDA; therefore, a contractor cannot concurrently be an SDA SETA contractor and a T3TRK Performer.

As a part of the proposal, the Offeror shall provide the Agreements Officer with complete information of previous, potentially impending, or ongoing work that is in any way associated with this acquisition for themselves and their major teammates. The Offeror shall provide a written assessment addressing why there is no current OCI and whether a future OCI is likely or if OCI will be avoided for the life of the T3TRK Agreement. In the event there is a known OCI or if the bidder intends to bid on future T3 Program acquisitions, the Offeror shall include an OCI Plan in addition to the Assessment. Any such OCI Plan shall address how the Offeror will periodically review and take steps to mitigate, neutralize, or avoid an OCI, if one arises, during the term of this T3TRK Agreement. If no OCI exists, the Offeror need only provide the Assessment, but the Assessment must include the approach/rationale for how OCI is monitored, mitigated or avoided after award and throughout the life of the program. If a conflict exists, both the Assessment and the OCI Plan are required to be a complete proposal.

The resulting Agreement will include a mutually agreeable OCI limitation applicable to the related Government scope of work, at either a prime contract level, at any subcontract tier, or both. During evaluation of proposals, the Government may also, after engagement with the Offeror and after consideration of ways to avoid the conflict of interest, insert a special provision addressing eligibility for future contract awards within the existing Tranche 3 Program.

4.1.8 Key Personnel Résumés

The Offeror shall identify the key personnel planned to be assigned to this program from the Offeror and Major Teammates as appropriate using Attachment 3 – Resume Template. Résumés should be in bullet format and include:

• Summary statement highlighting experience and expertise

• Current role with the Offeror or teammate to include current assignments and programs with particular attention paid to efforts currently underway for SDA to include percentage of time already applied to other SDA programs or projects

• Planned role within the T3 Tracking Layer program

• Evidence of applicable mission experience or understanding

• Education (academic and military, if applicable)

• Anticipated percentage of time to be assigned to this program; if already dedicated to an

SDA effort the Offeror should clearly indicate how current duties would be absorbed by alternate personnel (if applicable) so as to preclude any negative impacts to ongoing efforts

• Signed statement agreeing to support the SDA T3 Tracking Layer program, if awarded

Proposed staff members not currently employed by the Offeror may be included as appropriate. In those cases, the Offeror shall include signed contingent offer letters. These letters should be signed by both the Offeror and the proposed staff member and should state the willingness of the proposed staff member to join the Offeror in support of the SDA T3 Tracking Layer program, if awarded.

At a minimum, Key Personnel shall include the following positions:

From Offeror:

• Program Manager

• Chief Engineer

• Chief Software Engineer

• IR Mission Payload Lead

• Assembly, Integration, and Test (AI&T) Lead

• Information Security Certified Professional

• Subsystem Lead(s) (if Offeror is developing any of the major subsystems. The major subsystems are those listed in the Major Teammate definition in Section 3.)

From each Major Teammate:

• Program Manager

• Chief Engineer

4.1.9 Personnel Matrix

The personnel matrix shall be submitted using Attachment 4 – Personnel Matrix. The Offeror shall align their submitted personnel with the SDA T3 Tracking Layer requirements.

4.1.10 Technical Data and Computer Software Rights Assertions

The Offeror shall clearly delineate all limitations on data, hardware, and computer software rights for technical data, hardware, or computer software provided by the Offeror and all of its teammates, in the format shown in Attachment 1d - Data Rights Assertions Table. It is the Government’s assumption that no hardware, technical data, or computer software will be provided with less than “Government Purpose Rights” and that the vast majority of information generated will be provided with “Unlimited Rights” to the Government. The Offeror shall clearly identify those elements to be provided with less than “Unlimited Rights” and identify the rationale for their assertion(s) using the format shown in Attachment 1d. Any item related to the performance of this effort and not contained in Attachment 1d, shall be delivered upon request to the Government, with no less than “Government Purpose Rights”. The terms “Unlimited Rights”, “Government Purpose Rights”, “Limited Rights”, and “Restricted Rights” are defined in Volume VI – Other Transaction Agreement (OTA).

4.2 Volume II – Technical Solution

Volume II shall not exceed the pages limits identified in the table above. Any pages in excess of the allowable content, other than those specifically excluded from the overall page limit, will be removed from the Offeror’s proposal and not evaluated. With the exception of Commercial Data Sheets, Volume II appendices may also be classified.

4.2.1 Executive Summary

The Offeror shall present their proposed solution concept for two (2) planes of the T3 Tracking Layer and its NOVA ground system. The Executive Summary shall include an Operational Viewpoint (OV)-1 or equivalent high-level overview of the proposed solution. The graphics shall depict the SVs, their payloads, and the means by which they provide data to the Warfighter. The

Offeror’s milestone-driven IMS for capability delivery, culminating in an in-orbit delivery and performance per SDA’s schedule and technical requirements, shall be integrated into this graphical representation.

4.2.2 CONOPS Overview

The Offeror shall provide a CONOPS for the operation of the T3 Tracking constellation, including network maintenance and initialization, spacecraft maintenance and on-orbit calibration, data transfer, and direct-to-Warfighter communications. The Offeror shall clearly identify any mission constraints or limitations to include radiation upsets and recovery plans.

4.2.3 Space Vehicle (SV) Overview

The Offeror shall present an overview of the SV, including but not limited to:

• SV block diagram

• Delta-V budget

• High-level mass budget

• Power budget with power modes

• Thermal management strategy

• Vehicle configuration showing all major components

• Backup TT&C system design

• Resiliency feature to protect against directed energy attack mechanisms

The Space Vehicle Overview shall also include an overview of the SV concept of operations (CONOPS) including, but not limited to, a description of SV states and modes to be implemented in service of all required mission operations, and transitions between those states and modes.

4.2.3.1 Tranche 3 Tracking Layer Payload Architecture and Design

The Offeror shall present their overall payload architecture and design and include (but not limited

to) details of payload hardware, software, control, data transfer capability and/or limitations, and power requirements. Proposals shall demonstrate a clear understanding of each payload’s mission application and the technical solution’s ability to accomplish the tracking mission. Proposals shall also address any needed test and certification requirements and plans.

4.2.3.2 Infrared Mission Payloads

The Offeror shall provide a detailed description of the infrared mission payloads, including the projected size, weight, and power (SWAP) requirements, placement on the SV, maturity by component (TRL/MRL), technical capability, operational application, and image processing methods for the MW/MT infrared sensor or MWTD infrared sensor (assuming differing designs).

The Offeror shall describe the ground AI&T approach for each, including details of sensor calibration and environmental testing approach, and any radiation testing required. The Offeror shall provide a description of how on-orbit calibration, solar avoidance, continuous imaging operations, and pointing modes will be implemented. The Offeror shall propose how calibration will be completed on-orbit for initial operations and how it will be updated through the life cycle.

The Offeror shall propose one or multiple IR spectral bands based on SDA’s stated mission objectives of detecting and tracking infrared targets (both bright and dim, and both static and moving), including hypersonic vehicles and other advanced missiles. The Offeror shall propose a detection and processing architecture for use on-board each Tracking SV and on the ground that:

a) performs sensor-level processing to calibrate data and update calibration solutions as needed,

b) suppresses backgrounds and detects candidate events to transmit to ground or Transport SV BMC3 units, and

c) generates 2D tracks to transmit to ground or Transport SV BMC3 units.

The Contractor shall also propose a fusion processing architecture that performs fusion of track data from multiple Tracking SVs from the vendor’s own planes into 3D tracks. The 3D tracks will be formatted as standardized OPGA-8 messages to support interoperability within the MW/MT/MD community and Realtime Transfer Service (RTS). This function will support test, requirement verification, and algorithm tuning on the ground, both prior to launch and during operations. The Offeror shall describe their on-board data storage, lossless compression approach, and management of both raw and processed data for prioritization and routing based on the requirements of the ground IR MW/MT/MD mission.

The Offeror shall provide analysis supporting their design approach including, but not limited to, the following:

• Trades analysis conducted to achieve optimal design performance

• IR mission data processing architecture

• IR Sensor configuration

• Spectral band choice

• Radiometry budget and accuracy

• IR sensor on-board data processing throughput and data management/storage approach

• Line-of-Sight budget and state vector accuracy

• Stray light management approach

• Target tracking performance (MDT, NET, coverage)

• Resiliency

4.2.3.3 Optical Communications Terminals (OCTs)

The Offeror shall provide a detailed description of the OCTs, including placement on the SV, individual and total fields of regard, and ability to create and maintain space-to-terrestrial and space-to-space links. The Offeror shall identify the anticipated power requirements, data rate, bit error rate, and any other parameters considered key by the Offeror. The Offeror should provide a link budget demonstrating the closure of the optical links and clearly state any assumptions used in the development of the link budget. The Government expects that the link budgets will be developed using industry standards for margin (e.g., 3 dB). The Offeror shall identify the compliance of their current system with the SDA OCT Standard v3.2, detail any non-compliant elements of their design, and describe the path to full compliance for those elements.

4.2.3.4 Ka Mission Payload

The Offeror shall provide a detailed description of Ka-band subsystems used for the mission payload communications. The Offeror shall identify the anticipated modulation and coding implementations, information rates, power requirements, bit error rate, and any other parameters key to mission performance. The Offeror shall identify the antenna configurations, field of regard, field of view, and deployment mechanisms for each of the antenna systems. The Offeror shall provide link budgets demonstrating the closure of required RF links and clearly state all assumptions used in the development of the link budget. The Government expects that the link budgets will be developed using industry standards for margin (e.g., 3 dB).

4.2.3.5 Telemetry, Tracking, and Control (TT&C)

The Offeror shall provide a detailed description of the RF communications subsystems used for telemetry, tracking, and control (TT&C). The Offeror shall identify the anticipated modulation and coding implementation, information rates, power requirements, bit error rate, and any other parameters key to mission performance. The Offeror shall identify the antenna configurations, field of regard, and field of view supporting link closure at the required information rate, including the impact of blockages. The Offeror shall provide link budgets demonstrating the closure of required RF links and clearly state all assumptions used in the creation of the link budget. The Government expects that the link budgets will be developed using industry standards for margin (e.g., 3 dB).

4.2.3.6 Networking and Data Routing

The Offeror shall describe the networking capabilities enabled by their technical solution. The Offeror should detail the compliance of their system with the SDA NEBULA Standard v3.06, identify any non-compliant elements of their design, and identify the path to full compliance for those elements. The Offeror should discuss their plans for on-orbit network initialization and provide estimates of system performance.

4.2.3.7 Red-Side Processing (RSP)

The Offeror shall describe the proposed approach to implementing a red-side processing capability to host dynamic network management applications, including which processing unit the capability is expected to be hosted on, the processing, memory, and storage resources reserved for hosted applications, and a description of how this capability meets all functional and interface requirements.

4.2.3.8 Navigation

The Offeror shall describe their proposed navigation solution and its expected performance.

4.2.4 Spacecraft Bus

The Offeror shall present their SV design based on the manufacture or purchase of commoditized SV buses1. Should the Offeror elect to propose a non-commoditized bus alternative, they shall

1 A commodity spacecraft bus utilizes an existing design that can be easily manufactured and reused across multiple SVs and for multiple missions. A commoditized bus has been designed for manufacture and is suitable for, or currently being produced by, an assembly line-like process at scale.

present their process for commoditizing the alternative bus in addition to detailed justification for their bus selection.

4.2.4.1 Bus Design and Heritage

The Offeror shall provide a detailed description of the bus including the size, weight, and power available. The Offeror shall present a discussion of the bus heritage to include:

• How many have flown and in what orbits

• Design life and experienced flight life

• Types and frequency of experienced anomalies and their solution(s)

• Any major modifications required to meet the T3 Tracking Layer objectives

If the proposed bus has not flown, the Offeror shall provide the heritage from an existing bus (if applicable) and the changes made to reach the proposed bus design along with the rationale for each proposed change.

For each of the major subsystems (e.g., electrical and power, attitude control, TT&C, etc.) the Offeror shall provide a detailed description of the subsystem as well as system heritage. Block diagrams are encouraged where they provide greater insight into the design approach. The Offeror shall discuss specialty engineering (e.g., radiation, electromagnetic interference, contamination control, etc.) issues and approaches as appropriate. The Offeror should discuss the overall fault management approach, including the safe mode and recovery implementation.

4.2.4.2 Cybersecurity

The Offeror shall discuss their approach to implementing required Risk Management Framework (RMF) controls and cybersecurity in their integrated space and ground system.

4.2.4.3 Encryption

The Offeror shall describe the proposed implementation of security concerns, such as red-black isolation, encryption, and command authentication. The Offeror shall describe the encryption systems and technologies used on the space vehicle and how these systems will obtain certification and interoperate with the systems of other PWSA vendors and the ground.

4.2.5 Manufacturability

The Offeror shall present their manufacturing and assembly processes to demonstrate their ability to produce high-quality repeatable fabrication of the SVs including:

• Assembly of key parts,

• Testing of individual parts and assemblies to ensure they meet the reliability and availability standards associated with the SV,

• Assembly and test of SV subsystems and payloads,

• Integration and test of subsystem hardware,

• Integration and test of software with the hardware subsystems. A key focus of this demonstration is the IR mission payload for assembly, integration, and test.

The Offeror shall describe their AI&T flow and how it supports the on-time delivery of the T3 Tracking SVs. The Offeror should explain their ability to procure or manufacture commoditized buses at low cost and high reliability while achieving economies of scale as demonstrated in the commercial sector. The Offeror shall further detail planned mitigations for any manufacturing-related risks cited in Volume I, including strategies for overcoming the inability of the Offeror or a Major Teammate to produce the required number of units. The Offeror shall provide estimates of the manufacturing capacity of their organization (if applicable) and any Major Teammate, as defined in Section 3, inclusive of current contracts and any potential contracts within the Tranche 3 timeframe.

If currently under agreement with SDA, the Offeror shall clearly and concisely document the ability to produce T3 Tracking SVs, to include all payloads, within manufacturing constraints imposed by ongoing SDA efforts.

4.2.6 Supply Chain

The Offeror shall address the production and supply chain capacity available for this program, including potential contingency plans. The Offeror shall address supply chain security, and production scalability issues. SDA values vendor diversity to enable supply chain resiliency;

please list expected vendors for key components including SV bus, dispenser, IR Payload, payload control electronics, image collection modules, IR Focal Plane Array, OCTs and cryptographic and networking equipment. If specific vendor information is identified in Appendix A (Detailed Master Equipment List), it is acceptable to include a reference to Appendix A in Volume II. If key component vendors are not mentioned in Appendix A, list them in the Volume II text.

4.2.7 Test, Demonstration, and Verification

The Offeror shall present their hardware and software, ground and orbit-based test and demonstration approach(es). This section should address all aspects of test and demonstration to include modeling, simulation, analysis, emulation, and ground and space-based testing. The Offeror should address requirements verification at the component, subsystem, system, vehicle, and constellation levels up to and through environmental tests. The Offeror shall specifically address requirements verification of the IR mission payload and image processing. The Offeror shall describe test approaches, methodologies, performance, verification, documentation, and staffing. This section should include sample test artifacts from previous programs, and identification of test platforms and hardware maintained by the Offeror. The Offeror shall address facility and hardware cleanliness requirements and contamination monitoring approach throughout AI&T and launch integration. The Offeror shall specifically address test approach for the IR mission payload to include calibration, image processing, and space environment survivability.

The Offeror shall describe its test approach for verification of the SV interface with the Ground Segment.

For cases where test activities are expected to be accomplished outside of the Offeror’s direct control, the Offeror should identify their approach…