Draft T1DES Program Solicitation.pdf

SDA-PS-22-03

National Defense Space Architecture Tranche 1 Demonstration and Experimentation System (T1DES):

Demonstration Space Vehicles Program Solicitation

XXXX 2022

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

1 Introduction

The Space Development Agency (SDA) is issuing this Other Transaction Authority (OT) solicitation for a prototyping effort to augment the National Defense Space Architecture (NDSA) Tranche 1 Transport Layer (T1TL) constellation with demonstration and experimentation capability. The Tranche 1 Demonstration and Experimentation System (T1DES) leverages the low latency data transfer and beyond line-of-sight command and control infrastructure established by the T1TL program to field and connect additional space vehicles with different mission payload configurations. This solicitation is for development, manufacture, and deployment of the T1DES space vehicles and mission-enabling ground systems.

1.1 Motivation

SDA is releasing the T1DES solicitation to demonstrate warfighter utility of specific payloads prior to potential incorporation in future Tranches.

1.2 Program Approach

This solicitation seeks OT proposals under the authority of 10 U.S.C. § 4022 for U.S. space industry builder-operator teams that will partner with SDA to jointly develop and operate T1DES as part of the NDSA. The Government is purchasing a set of twelve (12) T1DES SVs equipped with Offeror-sourced Demonstration payloads. The Government reserves the right to purchase additional SVs and supporting products and services under this OT in the future, in response to changing mission needs. T1DES SVs are delivered as an integrated stack with associated launch adapters, deployment mechanisms, ground infrastructure, and operations and sustainment capability.

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

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

B. 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.

C. 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.

For more information on Other Transactions please see:

https://aaf.dau.edu/aaf/contracting-cone/ot/

1.3 Program Plan and Schedule

The T1DES constellation will be launched as rideshares (3 SVs per launch) with the T1 Tracking Layer. The first launch will occur no later than (NLT) 30 April 2025 with three subsequent launches expected to follow on one-month intervals. Offerors are expected to plan their program https://www.law.cornell.edu/definitions/uscode.php?width=840&height=800&iframe=true&def_id=10-USC-1875391109-791309680&term_occur=999&term_src=title:10:subtitle:A:part:IV:chapter:139:section:2371b https://www.law.cornell.edu/definitions/uscode.php?width=840&height=800&iframe=true&def_id=10-USC-2032561260-548934770&term_occur=999&term_src=title:10:subtitle:A:part:IV:chapter:139:section:2371b https://www.law.cornell.edu/definitions/uscode.php?width=840&height=800&iframe=true&def_id=10-USC-308593337-791309681&term_occur=999&term_src=title:10:subtitle:A:part:IV:chapter:139:section:2371b https://www.law.cornell.edu/definitions/uscode.php?width=840&height=800&iframe=true&def_id=10-USC-308593337-791309681&term_occur=999&term_src=title:10:subtitle:A:part:IV:chapter:139:section:2371b https://www.law.cornell.edu/definitions/uscode.php?width=840&height=800&iframe=true&def_id=10-USC-308593337-791309681&term_occur=999&term_src=title:10:subtitle:A:part:IV:chapter:139:section:2371b https://www.law.cornell.edu/topn/small_business_act https://www.law.cornell.edu/uscode/text/15/638 https://www.law.cornell.edu/definitions/uscode.php?width=840&height=800&iframe=true&def_id=10-USC-1875391109-791309680&term_occur=999&term_src=title:10:subtitle:A:part:IV:chapter:139:section:2371b https://www.law.cornell.edu/definitions/uscode.php?width=840&height=800&iframe=true&def_id=10-USC-2032561260-548934770&term_occur=999&term_src=title:10:subtitle:A:part:IV:chapter:139:section:2371b https://aaf.dau.edu/aaf/contracting-cone/ot/ in accordance with the milestone dates and deliverables specified in Attachment 1 – Statement of Work and Technical Requirements Document of this solicitation.

1.4 Tranche 1 and T1DES Overview

SDA endeavors to strengthen deterrence and warfighting capabilities in space by delivering a robust, responsive, and resilient NDSA. The Tranche 1 (T1) architecture will deliver comprehensive capabilities designed to support a stressing regional conflict. The constellation will be interconnected with Optical Inter-Satellite Links (OISLs) that have significantly increased performance over existing radio frequency (RF) crosslinks. LEO orbits in conjunction with OISLs will reduce path loss issues but more importantly offer much lower latencies with higher throughput which are deemed critical to prosecute time sensitive targets in today’s wartime environment with a peer competitor. The Transport Layer will operate over Ka band RF up and downlinks, optical up and downlinks, as well as in-plane and cross plane optical links, and be dynamically networked for simpler hand-offs, greater bandwidth, and fault tolerance. T1DES will leverage T1TL services to enable the LEO Integrated Broadcast System (IBS-L), and other Tactical Satellite Communication (TACSATCOM) missions described herein.

The T1DES constellation will consist of 12 SVs that share some bus requirements with T1TL SVs.

For example, T1DES SVs will include optical communications terminals (OCTs) to support in-plane and cross-plane links. T1DES constellation parameters are listed below.

Table 1 – Nominal T1DES Demonstration Constellation

Parameter Value Number of Planes 4 (TBR) T1DES SVs per Plane 3 Altitude 1000 km Inclination ~81 deg In-Plane Mean Anomaly Separation (TBR) Minimum Optical Links per SV 3x/2x Continuous Mission Data Downlink Ka Navigation APNT and GPS

The T1 Ground Segment includes two SDA Operation Centers (OCs) and multiple Ground Entry Points (GEPs) supporting T1 operations. Launch, Early Operations, and Checkout support of the T1DES SVs will be performed from Offerors’ facilities but will ultimately transition to nominal mission operations performed from the two SDA OCs. The SDA OCs plan, schedule, and execute operations of the T1 Enterprise. Mission partner facilities provide data that will be used for T1DES flight demonstrations and operations.

The system description and requirements can be found in Attachment 1 – Statement of Work (SOW) and Technical Requirements Document of this solicitation. Offerors shall propose a solution that meets the requirements as laid out in that attachment.

2 T1DES Solicitation

Within this solicitation, the following definitions are used:

• Prime: Offerors

• Major Subsystems: Elements of the SV and ground system design that have a significant impact on functionality. The following are examples of major sub-systems:

o Optical Communications Terminals o IBS-L and TACSATCOM Mission Payloads o Network Established Beyond the Upper Limits of the Atmosphere (NEBULA)

Operations – Vendor Architecture (NOVA) System o Networking and Data Routing o Encryption o Ka Mission Payload o Primary and Backup TT&C System

• 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 or more of the following subsystems or capabilities:

o Optical Communications Terminals o IBS-L and TACSATCOM Mission Payloads o Space Vehicle Bus o System Integration o Operations and Sustainment Personnel o Network Established Beyond the Upper Limits of the Atmosphere (NEBULA)

Operations – Vendor Architecture (NOVA) System 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 Overview

2.1 Proposal Preparation Instructions

Offerors shall submit their T1DES proposal via six (6) volumes. Specific volume contents and associated page limits are detailed below.

• Volume I – Governance shall contain a detailed description of Offerors’ proposed program management, systems engineering and engineering approaches, processes, and tools for executing the program on schedule and within the price proposed. This volume shall also contain résumés for key personnel that will perform the T1DES program and a complete listing of data rights asserted by Offerors and all of their subcontractors.

• Volume II – Technical shall contain a detailed description of Offerors’ proposed technical solution to accomplish the requirements defined in Attachment 1 – Statement of Work and Technical Requirements Document

• Volume III – Schedule shall contain a full 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 path from contract award through SV delivery. Offerors shall propose contingency plans to reduce scope to mitigate negative schedule variance. Any dependencies anticipated by Offerors based on the T1TL program shall be clearly identified and risk mitigation activities – if required – clearly explained.

• Volume IV – Price and Rationale shall contain Offerors’ Firm Fixed Price (FFP) and associated detail. Any cost savings anticipated based on prior work shall be identified.

• Volume V – Experience and Past Performance should contain at least one (1) and may contain up to four (4) recent (within the last five (5) years), relevant examples of on-time, on-cost/price delivery of complex systems, subsystems, or components, preferably space-related hardware, or software. Offerors shall also include at least one (1) and up to two (2) past performance examples for each major teammate.

• Volume VI – Draft Other Transaction (OT) Agreement The font in normal text for all volumes shall be no smaller than Times New Roman 12 pt., while text in figures and tables shall be no smaller than Times New Roman 10 pt. Line spacing shall not be less than 1.5. A table shall consist of at least two columns in every row. Tables 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 X 11 inches shall be counted as two (2) pages. 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 proposal shall not include UNSOLICITED “options” for multiple solutions and/or additional work not specifically requested elsewhere in this solicitation. Any such options proposed will not be evaluated and the proposal may be deemed nonconforming. The Government expects to make a single award but reserves the right to make no awards, a partial award, or multiple awards.

2.1.1 Volume I - Governance

Volume I shall not exceed fifteen (15) pages of content exclusive of title pages and tables of contents, figures, and/or tables. Any pages in excess of the first fifteen (15) pages of content, other than those noted below as specifically excluded from the overall page limit, will be removed from Offerors’ proposal and not evaluated.

2.1.1.1 Executive Summary

Offerors shall present their proposed team construct and expected contributions by each major teammate. The Executive Summary should include a summary of Offerors' programmatic and systems engineering approaches, to include the cost and risk management approaches.

2.1.1.2 Program Management

Offerors shall detail the people, processes and tools planned to manage and conduct the program to a successful completion on time and within the agreed upon price. Offerors shall discuss their program, personnel, cost, and risk management approaches, including any processes and tools.

Offerors shall include a list of the primary risks on the project, the planned mitigations, and the approach for managing risks throughout the system life cycle. Schedule management shall be discussed in Volume III; however, Offerors 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. Offerors should describe its processes to staff the program with qualified personnel, identify and manage critical vendors and subcontractors, and control costs within an FFP environment. Offerors 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.

Offerors shall plan the program using the program reviews identified in Section 2.1 of Attachment 1 - Statement of Work and Technical Requirements Document and in accordance with other dates specified throughout Attachment 1. If Offerors believe that an alternate review structure (e.g., combining certain reviews) is more appropriate and meets the needs of the Government for insight into the design and understanding of challenges and risks at appropriate stages of the development, Offerors are free to propose it and the rationale behind their belief. For each review combined, omitted, or added, Offerors shall clearly delineate during what remaining review(s) the information traditionally provided shall be discussed. Table 3 identifies mandatory milestone payment events.

If Offerors omit these reviews, then they shall clearly identify an equivalent event that will be used in lieu of the mandatory review for milestone payments as specified.

Offerors shall clearly and explicitly state the need for, justification for, and mission impact of any anticipated waivers to requirements, Government standards, and compliance documents identified in Attachment 1 – Statement of Work and Technical Requirements Document.

2.1.1.2.1 Subcontractor and Supply Chain Management

Offerors shall address their subcontractor and supply chain management methodologies. Offerors should describe how they will minimize the effect on the program from fluctuations in supply chain availability and subcontractor deliveries.

Offerors should include a table showing the delivery schedule of critical parts. Offerors should propose a contingency plan in response to supply shortages for all critical parts to include pricing, supply, and delivery information.

2.1.1.2.2 Subcontractor Workload

Where applicable, Offerors shall present a strategy for managing delivery performance of major subcontractors who will be supporting multiple SDA contracts concurrently in addition to T1DES.

2.1.1.2.3 Nontraditional Defense Contractors (NDC) / Nonprofit Research Institution If applicable, Offerors shall identify which of their subcontractors constitutes an NDC or a nonprofit research institution in accordance with 10 U.S.C. § 3014. Offerors shall identify the extent of participation of NDC(s) and/or nonprofit research institution(s) to Offerors’ T1DES program.

2.1.1.3 Systems Engineering

Offerors shall detail the Systems Engineering processes and methods that will be used to execute the T1DES program. Offerors 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 Government expects that Offerors will utilize Systems Engineering best practices.

2.1.1.4 Mission Assurance

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

2.1.1.5 Organizational Conflict of Interest

Offerors shall clearly identify any real or perceived organizational conflicts of interest (OCI) for themselves or any of their teammates that would arise from their participation in the T1DES program. If Offerors believe that they and their teammates have no organizational conflicts of interest, then they should explicitly state this position.

If Offerors believe that an OCI exists or may exist upon award, then Offerors shall include an OCI mitigation plan as an appendix to this volume. The OCI mitigation plan will not be included in the Volume I page limit.

2.1.1.6 Personnel Résumés

Personnel résumés shall not exceed one (1) page each. The personnel résumés shall be included as attachments to this volume and will not be included in the Volume I page limit.

Offerors shall identify the key personnel planned to be assigned to this program from Offerors and major teammates as appropriate. Résumés should be in bullet format and include:

• Summary statement highlighting experience and expertise

• Current role with Offerors or teammate to include current assignments and programs

• Planned role within the T1DES program

• Evidence of applicable mission experience or understanding

• Education (academic and military, if applicable)

• Military, Government, or Commercial space-related experience (if any)

• Anticipated percentage of time to be assigned to this program

• Active clearance or eligibility for up to Top Secret

• Signed statement agreeing to support the T1DES program if awarded

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

Key personnel shall include:

From Offeror:

• Program Manager

• Chief Engineer

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

• If Offeror is developing any of the major subsystems, the subsystem lead(s)

From each major teammate:

• Program Manager

• Chief Engineer

• If Major Teammate is developing any of the major subsystems, the subsystem lead(s)

2.1.1.7 Personnel Matrix

The personnel matrix shall be submitted as an attachment to this volume and will not be included in the Volume I page limit.

Offerors shall compare and contrast their submitted personnel résumés against the T1DES requirements to validate corporate and individual experience and expertise thereby giving the Government confidence in Offerors’ probability of success. Format for this comparison is entirely up to Offerors but this section of the proposal should stand alone for evaluation.

2.1.1.8 Technical Data and Computer Software Rights Assertions Offerors shall clearly delineate all limitations on data, hardware, and computer software rights for technical data, hardware, or computer software provided by Offerors and all their teammates, using Attachment 5 of the Draft OT Agreement. 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. Offerors 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 5. Any item related to the performance of this effort and not contained in Attachment 5, 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 Draft Other Transaction (OT) Agreement.

2.1.2 Volume II - Technical

Volume II shall not exceed forty (40) pages of content exclusive of title pages and tables of contents, figures, and/or tables. Any pages in excess of the first forty (40) pages of content, other than those noted below as specifically excluded from the overall page limit, will be removed from Offerors’ proposal, and not evaluated. The Government anticipates that Volume II will be classified Secret. Offerors may choose to submit the entire volume at the Secret level or submit an unclassified volume with a classified addendum. Submitting classified information with Volume II in the formats described here is encouraged, but not required Offerors.

2.1.2.1 Executive Summary

Offerors shall present their proposed solution concept for twelve (12) T1DES SVs. 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, the means by which they communicate with each other and the ground to include anticipated data rates by spectral band, and the means by which they accomplish or demonstrate mission objectives. Integrated into this graphical representation shall be Offerors’ milestone-driven integrated master schedule for capability delivery, culminating in an in-orbit delivery and performance per SDA’s schedule requirements.

2.1.2.2 Space Vehicle (SV) Overview

The Overview shall summarize the T1DES SV system design in terms of the Key Parameter Specification, in addition to Offerors’ supporting design information, including but not limited to:

• SV block diagram

• Delta-V budget

• High-level mass budget

• Power budget with power modes

• Vehicle configuration showing all major components and significant dimensions

• Backup TT&C system design

• Link budgets for mission demonstrations

• Latency budget within the SV for mission demonstrations

This section should also include an overview of the SV Concept of Operations (CONOPS).

A detailed Master Equipment List (MEL) with mass, power, Manufacturing Readiness Level (MRL), and Technology Readiness Level (TRL) or other flight heritage shall be included as an Appendix and will not count against the Volume II-page limit. The level of detail required in the MEL is not specified but is expected to decompose to assemblies below the subsystem level.

The power budget should include the duty cycle and current best estimate for each component by power mode, as well as the orbit average power generated in each power mode and enough information to determine the battery depth of discharge.

2.1.2.2.1 T1DES Payload Architecture and Design

Offerors shall present their overall payload architecture and design. For each payload element below, Offerors shall include, but not be limited to a discussion 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 its mission. Proposals should also address any needed test and certification requirements and plans. Plans must include schedule and risk assessments for subject completion. Lastly, Offerors shall detail their trade-space analyses for critical payload subsystems, including power amplifiers, software defined radios, and antennas.

2.1.2.2.2 T1DES Mission Payloads

Offerors shall provide a detailed description of each of its mission payloads, as defined in Attachment 1 – Statement of Work and Technical Requirements Document. Offerors shall provide detailed payload performance parameters particularly, RF link budgets covering the full fields of regard, demonstrating how each payload satisfies its mission application. Offerors shall describe the CONOPs for using each mission payload individually on each SV and as a user of T1TL. Offerors shall describe how the payloads are integrated with the bus. In addition to these, Offerors shall provide a detailed, quantitative argument in response to the following technical considerations associated with the T1DES mission payloads:

1. Enumerate the trade space for mission payload antennas. Present candidate antenna designs and discuss their merits and shortcomings considering factors including RF performance, stowed volume, and antenna sharing. Offerors shall present their approach to the trade between closing the link at low elevation angle and power flux density on the ground at nadir.

2. Examine the problem of distributing IBS-L messages. The T1DES NOVA must interact with SUPERNOVA and other ground systems to route messages earmarked for different geographic regions around the world to the correct satellite at the correct epoch to ensure uninterrupted service to receivers on the ground. Handoffs from rising and setting SVs must be managed such that no messages are dropped. All this must occur with a schedule of broadcast frequencies that preclude interference where geographic regions overlap.

3. Processing signals onboard is known to be resource intensive, consuming hundreds of watts. Offerors shall present payload design alternatives that effectively manage this condition in a small satellite system. Discuss the risks associated with each alternative.

Optical Communication Terminals (OCT)

Offerors shall provide a detailed description of the optical communication terminals (OCTs), including the placement on the SV, individual and total field of regard, and ability to create and maintain space-to-space links. Offerors should identify the anticipated power requirements, data rate, bit error rate, and any other parameters considered key by Offerors. Offerors should provide a link budget demonstrating the closure of the optical links and clearly state any 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). Offerors shall identify the compliance of their current system with the SDA OCT Standard v3.0, detail any non-compliant components of their design and describe the path to full compliance for those components.

2.1.2.2.3 Ka Mission Payload System

Offerors shall provide a detailed description of Ka-band subsystems. Offerors should identify the number of terminals, frequency of operation, bandwidth, anticipated power requirements, anticipated data rate, bit error rate, and any other parameters key to mission performance. Offerors should identify the antenna configurations, field of regard, and deployment mechanisms for each of the antenna systems. Offerors should provide link budgets demonstrating the closure of required radio frequency (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). Offerors shall include a description of the space-to-ground communications solution to accomplish checkout and early operations.

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

Offerors shall provide a detailed description of the RF communications subsystems used for telemetry, tracking, and control (TT&C). Offerors should identify the number of terminals, frequency of operation, bandwidth, anticipated power requirements, anticipated data rate, bit error rate, and any other parameters key to mission performance. Offerors should identify the antenna configurations, field of regard, and deployment mechanisms for each of the antenna systems.

Offerors should 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). Offerors shall include a description of the space-to-ground communications solution to accomplish checkout and early operations.

2.1.2.2.5 Networking and Data Routing

Offerors should describe the networking capabilities enabled by their technical solution. Offerors should detail the compliance of their system with the SDA NEBULA Standard v3.0, identify any non-compliant components of their design, and identify the path to full compliance for those components. Offerors should indicate how their design supports networking with T1TL. Offerors should discuss their plans for connecting to T1TL and provide estimates of system performance.

2.1.2.2.6 Navigation

Offerors should describe the proposed implementation of navigation capabilities including a description of:

• How an assured position, velocity, and timing (PVT) solution is provided on board the satellite utilizing Global Positioning System (GPS), OCTs, clock(s) and system components as required,

• The orbit propagator,

• The trust engine/integrity audit and how the PVT solution would be utilized to ensure the validity of the received GPS signals and PVT sensor data in order to meet DoDI 4650.8,

• The selected Global Navigation Satellite System (GNSS) receiver(s) and clocks, and how these will be integrated to provide an assured PVT solution for all satellite systems,

• How the vendor will transition to a constellation PVT solution provided from the ground.

2.1.2.2.7 Space Vehicle (SV) Bus Design

Offerors shall present their SV design based on the manufacture or purchase of commoditized SV buses per the definition included in Attachment 1 – Statement of Work and Technical Requirements Document. Should Offerors elect a non-commoditized bus alternative, they shall present their process for commoditizing the alternative bus.

Offerors shall provide a detailed description of the SV bus including the size, weight, and power available for the payloads. Offerors shall present a discussion of the bus heritage to include:

• Where and how many have flown in their orbits

• Design life and experienced flight life

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

If the proposed bus has not flown, Offerors 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; telemetry, tracking and control, propulsion; etc.), Offerors shall provide a detailed description of the subsystem as well as system heritage (similar to that for Bus Design and Heritage above). Offerors shall discuss specialty engineering (e.g., radiation, electromagnetic interference, contamination control, etc.)

issues and approaches as appropriate. Offerors should discuss the overall fault management approach, including the safe mode implementation.

2.1.2.2.8 Cybersecurity

The Risk Management Framework (RMF), per DoD Instruction 8510.01, will be used by Offerors to obtain separate authorities to operate (ATO) from the Government for the ground and space segments. The ground segment refers to any ground stations, networks, or ground-based antennas supporting the SVs during launch and early operations, transition to operations, and operations.

For the TIDES SVs, the Government has pre-selected the security controls that Offerors must implement for to achieve the desired cyber protection and resiliency. These security controls are included as Contractor and System requirements in the T1DES System Security Accreditation Appendix_Draft RFP.xlsx document in the Bidder’s Library. In their proposal, Offerors can provide arguments to add or remove any SV security controls to the Government AO for consideration and approval.

Offerors should discuss their cyber resilience strategy, including any resiliency plans, trusted boot systems, security guarantees, and measurements and measurement frequencies. Offerors should discuss any novel solutions and trade-offs required to produce a highly resilient space vehicle to minimize cyber risk. Offerors should describe how the compromise of a single SV will not impact the T1TL network and highlight key aspects of cyber resilience that will be a part of their solution.

If desired, Offerors may include discussions related to the cyber resiliency of their system in the classified addendum.

2.1.2.2.9 Encryption

Offerors should describe the proposed implementation of security concerns, such as red-black isolation, encryption, and command authentication. Offerors should describe the encryption systems and technologies used on the SV and how these systems will obtain certification and interoperate with the T1TL SVs, NDSA and T1DES ground systems, and tactical radios used for mission demonstrations.

2.1.2.3 Manufacturability

Offerors shall present their manufacturing and assembly-line processes, including diagrams and illustrations, captured in digital form, to demonstrate their ability to produce high-quality repeatable fabrication of the SVs including (1) assembly of key parts, (2) testing of individual parts and assemblies to ensure they, Offerors, shall present their manufacturing and assembly-line processes, captured in digital format, to demonstrate their ability to produce high-quality repeatable fabrication of the SVs including:

1. assembly of key parts,

2. testing of individual parts and assemblies to ensure they meet the reliability and availability standards associated with the SV,

3. assembly and test of SV subsystems,

4. integration and test of subsystem hardware, and integration and test of software with the hardware subsystems.

The digital media shall be submitted in MP4 (.mp4) format and the duration of the video shall be less than ten (10) minutes. Any video content that exceeds the ten (10) minute time requirement will not be evaluated. The Government is primarily interested in videos that show actual hardware, assembly lines and personnel that will be employed by Offerors in the design, development, assembly, integration, test, and delivery of the SVs. Videos that are created using 3-D computer-aided visualization programs are not preferred but will be accepted if they clearly demonstrate critical manufacturing and assembly assets that will be employed during T1DES program execution. Any such videos depicting manufacturing and assembly assets that do not yet exist must explicitly indicate development schedules substantiating the availability of those assets during T1DES program execution. Video narration will be accepted but must be accompanied by a transcript, which shall be submitted as a separate .pdf file and will not count against the Volume II page limit.

Videos shall be submitted via DoD Secure Access File Exchange (SAFE): https://safe.apps.mil/ as part of the proposal submission. Videos shall be a single file which shall not exceed the size limits of a single DoD SAFE submission.

While Offerors are free to include content that they consider important to demonstrating their capabilities, video inspection shall, at a minimum, present the system-level assembly, integration, and test (AI&T) process for the SV bus.

In addition to the video, Offerors should explain their ability to procure or manufacture commoditized buses1 at low cost and high reliability while achieving economies of scale as demonstrated in the commercial sector. Offerors shall identify risks in their manufacturing processes or the manufacturing processes of their major teammates and shall identify their planned responses to those risks, including strategies for overcoming the inability of Offerors or a major teammate to produce the required number of components. Offerors shall provide estimates of the manufacturing capacity of themselves (if applicable) and any major teammate, as identified in the Section 2, inclusive of current contracts and any potential contracts within the Tranche 1 timeframe.

2.1.2.3.1 Supply Chain

Offerors should address production capacity, supply chain capacity, supply chain security, and production scalability issues for the SV buses and key payloads including, but not limited to, IBS- L and TACSATCOM mission payloads, OCTs, processors, and network and cryptographic equipment.

2.1.2.4 Test, Demonstration, and Verification

Offerors 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, ground, and space-based testing according to the test and demonstration requirements and descriptions provided herein. Offerors should address requirements verification at the component, subsystem, system, vehicle, and constellation levels up to and through environmental tests. Offerors should 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 Offerors. For cases where test activities are expected to be accomplished outside of Offerors’ direct control, Offerors should identify their approach to manage test conduct and the experience level of the organization Offerors plan to use to conduct the test. Of particular interest to SDA is Offerors’ approach to conducting tests and demonstrations in concert with the SDA OC prior to

1 A commodity space vehicle utilizes an existing bus design that can be easily manufactured and reused across multiple space vehicles 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 economies of scale.

https://safe.apps.mil/ launch and during early orbit operations and checkout, as well as use of the SVs in conjunction with warfighter exercises once in orbit. Throughout discussion of their test activities, Offerors should clearly identify live, virtual, and constructive tests and demonstrations, if applicable, and any elements expected to be provided by the Government to facilitate completion of their verification program. Offerors should describe the suggested approach for verification that the proposed SVs are fully compatible with the integrated ground segment, T1TL, and the SDA OCs.

2.1.2.5 Launch Services Overview

The twelve T1DES SVs will integrate to the SDA Tranche 1 Tracking Layer launch vehicles, 3 SVs per launch on USSF/NSSL launch services utilizing an EELV secondary payload adapter (ESPA) or alternative multi-manifest adaptor.

Offerors shall describe their plan to perform analyses necessary to ensure successful integration and launch with the Tracking T1 SVs including management of mass constraints. Offerors shall present their architecture and deployment/separation systems design(s) for the T1DES constellation in each case. Offerors shall provide an overview of LV integration activities, as well as its plan for SV-LV integration tasks at the launch facility in each case. Offerors shall also describe how it will keep the Government informed of progress via technical interchange meetings and its IMS. Offerors shall identify any unique launch service needs (such as a T-0 dry nitrogen purge) or additional accesses required to support launch vehicle integration. If the proposed bus has flown on an NSSL class launch vehicle, Offerors shall provide the bus heritage. For pricing purposes, Offerors shall assume that all launches will be conducted from Vandenberg Space Force Base.

2.1.2.6 Ground Segment and Operations

Offerors shall present their approaches to operating the T1DES constellation as a user of T1TL.

The approach includes their solution for NEBULA Operations – Vendor Architecture (NOVA) software that runs at the factory and the SDA OCs, and integrates with the SDA Unified Planning Environment and Resources for NEBULA Operations – Vendor Agnostic (SUPERNOVA) provided by O&I contractor. Offerors shall define functions that the T1DES NOVA will provide.

Offerors shall describe their use of COTS software and tools and the resultant benefits to integrated operations. Offerors shall describe how their ground system will provide SV system health and status data to the integrated ground operations management systems for continuous situational awareness and performance monitoring. Offerors shall describe their approach to shift the control of the T1DES constellation to the SDA OCs as part of the development of the integrated ground system.

Offerors shall describe their concept, level of automation, and staffing requirements for nominal operations. Offerors shall describe their approach for anomaly resolution, discrepancy reporting, and planned and unplanned system maintenance. Offerors should list the documentation and training anticipated to be provided to SDA operations personnel. Offerors should describe the systems and approach for maintaining inventory accountability and control.

Offerors shall describe their T1DES NOVA Critical Mission Functions, including their approach to managing TACSATCOM and IBS-L messages from external data sources.

2.1.2.7 Offerors Mission Operations, Sustainment, and Disposal Offerors shall define the facilities and systems that will be used to support launch and early operations (LEOPs) from the vendor facility and how they will transition to constellation operations at the SDA OCs. Offerors shall clearly identify the anticipated locations of SV communications systems, ground antennas, and processing facilities that will be utilized during LEOPs. Offerors shall clearly identify the ability of their facilities to support operations at Secret classification and what network connections are currently available. Offerors should provide an overview of the LEOPs plan for orbit raising and SV and constellation level initialization and checkout. Offerors shall describe their on-orbit check-out plan and test flow to demonstrate full operational capability of their SVs, mission payloads, and networked orbital planes prior to delivery to the Government and transition to operations. Offerors shall identify the support that they will provide to the SDA OC(s) during nominal constellation operations, surge support, and anomaly operations. Offerors shall describe the disposal plan for each SV and how that plan will reliably dispose of decommissioned SVs.

2.1.2.7.1 Mission Design

Offerors shall provide CONOPs for T1DES SVs, including initialization, networking with T1TL, and executing IBS-L and TACSATCOM missions. Offerors should clearly identify any mission constraints or limitations. Offerors shall describe how they will integrate with the T1DES mission partners at mission partner facilities for IBS-L and TACSATCOM payload operations.

2.1.2.8 Appendices

The following appendices shall be included as attachments to Volume II and will not count against the Volume II-page count.

2.1.2.8.1 Mission Demonstration Plan

Offerors shall outline their plan for executing one or more Mission Demonstration event(s) which will validate the mission capabilities of the IBS-L and TACSATCOM mission payloads and applications. The Mission Demonstration event(s) will occur after the completion of Offerors’ Functional On-Orbit Test (FOOT). Offerors shall define the end-to-end flow of the Mission Demonstration event(s), inclusive of the users at mission partner facilities, SUPERNOVA and NOVA ground systems, T1TL, and the T1DES SVs. Offerors shall describe how their proposed capstones will demonstrate the T1DES mission payloads can be utilized with a resilient data transport architecture in LEO to support IBS-L and TACSATCOM operations. Offerors shall clearly list their initial assumptions made during event design, anticipated dependencies during event conduct, and geophysical or temporal constraints expected which could potentially hinder event success. Offerors shall indicate the entrance criteria, key accomplishments, and exit criteria for each event. Offerors shall clearly identify the participants in the Mission Demonstration event(s), anticipated Government Furnished Equipment (GFE), and any other assumptions of capability required to complete the Capstone event(s). Offerors shall identify anticipated event locations and timelines. The Mission Demonstration Outline shall include an OV-1 graphic including the participants and data flows at a minimum. The Mission Demonstration Plan is limited to eight (8) pages (exclusive of title pages and tables of contents, figures, and/or tables). Any pages beyond this limit will be removed from the appendix and will not be evaluated.

2.1.2.8.2 Commercial Data Sheets

Offerors may submit commercial data sheets as a list of up to ten (10) hyperlinks to publicly available downloadable .pdf data sheets on Offerors’ websites or their subcontractor’s websites.

Each downloadable .pdf file shall be no more than two (2) pages, resulting in a cumulative maximum of twenty (20) pages of commercial data sheets. Links will be accessed in the order provided in the proposal and only the first twenty (20) pages will be evaluated. Any pages beyond the twenty (20) page limit will be discarded.

2.1.2.8.3 Offerors Parameter Specification

Offerors shall complete the value column in each worksheet of the T1DESKeyParameterSpecification.xlsx file in the Bidder’s Library and shall include the completed .xlsx file as an appendix to Volume II. All values in the table shall be provided in the units specified. Upon selection for award and at the discretion of the Government, the proposed values in this table may be included in the final Statement of Work and Technical Requirements Document in lieu of the current threshold and objective values specified in Attachment 1 – Statement of Work and Technical Requirements Document. All units are SI units, unless otherwise specified.

2.1.3 Volume III - Integrated Master Schedule

Volume III shall not exceed ten (10) pages of content exclusive of title pages and tables of contents, figures, and/or tables. Any pages in excess of the first ten (10) pages of content.

other than those noted below as specifically excluded from the overall page limit, will be removed from Offerors’ proposal and not evaluated.

2.1.3.1 Integrated Master Schedule (IMS)

The IMS shall include the schedule for Offerors’ SV solution. Offerors shall clearly indicate the anticipated schedule margin for launch activities, where margin is calculated as the number of calendar days between the date of completion of the final SV for the launch and the corresponding delivery date to the launch site. Offerors shall identify the dates for all major reviews and program milestones and include entrance criteria, key accomplishments, and exit criteria for each milestone.

If the milestones proposed correspond to payments anticipated by Offerors, this Volume should so state and link (electronically if possible) to the appropriate section in Volume IV – Price and Rationale so that the justification for the payment appears in Volume III – Integrated Master Schedule and the payment amount, terms, conditions and Government acceptance criteria for payment appears in Volume IV – Price and Rationale.

At least two of the pages shall be a separable, standalone detailed Gantt chart (or similar illustration) clearly presenting Offerors’ milestone-driven integrated master schedule, including key program milestones and critical paths. This chart should include dependencies, assumed Government or major teammate hardware, software, or information deliveries and/or approvals, tests, demonstrations, reviews, and/or any other key activities in Offerors’ proposed program.

Offerors shall clearly delineate the primary critical path within their schedule and any additional critical paths deemed appropriate to justify their ability to deliver the proposed SVs on time and on cost. Offerors shall discuss the critical path analysis used to determine the primary and secondary critical paths. Offerors shall discuss their approach to managing progress against the baseline schedule. Offerors shall include delivery dates of components from all major teammates and shall clearly identify which of these components lie on the critical path.

Offerors shall identify maturation and risk reduction plans for any space vehicle components that are at a TRL of less than six (6) at the time of the proposal. Offerors shall identify the top schedule risks and outline their approach(es) to mitigate the risks and ensure timely delivery. Offerors shall identify which teammate deliveries and which external dependencies produce the most risk to on-time delivery.

Offerors shall deliver their complete IMS in Microsoft Project-compliant native format as well as .pdf format in conjunction with this volume. The complete IMS shall include schedule details down to at least Level 3 of the work breakdown structure (WBS) and details to at least the subassembly level for high-risk areas and to the subsystem level elsewhere. IMS content shall be tailored to address each WBS element’s unique design, development, assembly, integration, and test activities, as applicable.

The delivered IMS files (Microsoft Project and .pdf format) will not count against the Volume III-page limit, however, the Gantt chart is included in the page limit.

2.1.4 Volume IV - Price and Rationale

Volume IV has no page limit.

2.1.4.1 Executive Summary and Pricing Rationale

Offerors shall detail their pricing assumptions and rationale that guided their FFP submission.