T1TL Program Solicitation.pdf

SDA-PS-22-01

National Defense Space Architecture

Tranche 1 Transport Layer

Program Solicitation

28 October 2021

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

1 Introduction

The Space Development Agency (SDA) is issuing this solicitation to establish the foundation for

Tranche 1 (T1), the Initial Warfighting Capability Tranche, of the National Defense Space

Architecture (NDSA). The NDSA’s operational utility is predicated on the availability of a ubiquitous data and communications Transport Layer provided by a proliferated constellation of relatively small, mass-producible space vehicles (SVs) in low Earth orbit (LEO). The Tranche 1

Transport Layer (T1TL) SVs will be similar to those currently under development for the Tranche

0 Transport Layer with targeted technology enhancements, mission-focused payload configurations, increased integration, and greater production efficiencies. The T1TL will provide global communications access and deliver persistent regional encrypted connectivity in support of

Warfighter missions around the globe by serving as the backbone for Joint All Domain Command and Control (JADC2) built on low-latency data transport, sensor-to-shooter connectivity, and direct-to-weapon connectivity.

1.1 Motivation

SDA has determined that the proliferation of various mission functions across the NDSA using commodity SVs 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 of the architecture. The objective is to establish and demonstrate the ability to rapidly evolve development processes and field capability on a significantly faster timeline than traditional space systems acquisition. In pursuit of this objective, SDA requires each NDSA Contractor’s SVs and communications systems to be interoperable with the SVs and systems developed by all other

NDSA Contractors. Additionally, all SVs must operate in an integrated fashion through a common ground system.

1.2 Program Approach

This solicitation seeks Other Transaction (OT) proposals under the authority of 10 U.S.C. § 2371b for U.S. space industry builder-operator teams that will partner with SDA to jointly develop and operate the T1TL as part of the NDSA. The Government is purchasing a constellation of up to one hundred and twenty-six (126) T1TL SVs divided into six (6) orbital planes, to be awarded to multiple vendors, subject to available funding. Each Offeror shall propose to develop two (2) of the orbital planes, with the associated ground support and operations and sustainment capability.

Note that in order for SDA to make an OT award to the Offeror, 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.

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

(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://www.dau.edu/guidebooks/Shared%20Documents/Other%20Transactions%20(OT)%20G uide.pdf

1.3 Program Plan and Schedule

The first plane of the T1TL constellation will be launched no later than (NLT) September 30, 2024 with the launches of subsequent planes following on one month intervals. The Offeror is expected to plan their program in accordance with the milestone dates and deliverables specified in

Attachment 1 – Statement of Work and Technical Requirements Document of this solicitation.

1.4 T1TL Concept of Operations (CONOPS) Overview

After launch, each plane has three (3) months to obtain operational orbit and complete a

Verification On-Orbit Test using the Offeror’s facilities. After completion of the Verification On-

Orbit Test, the SVs transition to operations utilizing the Government’s Operations Centers, including the Offeror’s installed NEBULA Operations – Vendor Architecture (NOVA) ground system. At this point, the SVs have entered the security boundary of the Government Operations

Centers and will no longer be allowed to connect to non-Government ground stations, antennas, networks, or systems. The plane then completes a Functional On-Orbit Test utilizing the

Government Operations Centers and antennas, the Offeror’s NOVA, and the SDA Unified

Planning Environment and Resources for NEBULA Operations – Vendor Agnostics

(SUPERNOVA) system. Upon successful completion of the Functional On-Orbit Test, the

Government takes ownership of the SVs and they enter operations. The Offeror will continue to support the operations and sustainment of their vehicles for a period of up to five (5) years.

2 System Description

The T1TL constellation will consist of six (6) orbital planes with twenty-one (21) T1TL SVs in each plane. The constellation parameters are defined in Table 1. Every T1TL SV will be interoperable with all T1TL SVs, regardless of vendor. The T1TL SVs will include Optical

Communications Terminals (OCTs) to support in-plane and cross-plane crosslinks, links to terrestrial OCTs (ground, air, and maritime), and crosslinks to compatible SVs outside the

Transport Layer. The T1TL SVs, in conjunction with the SDA Operations Center (OC) will form a communication network that will provide low-latency, high throughput data transfer to and from any location on the globe.

The T1TL SVs will also have the capability to demonstrate communication and data transfer via the Link 16 network. This includes the ability to relay messages beyond the line of sight between the SDA OC and in-theater Link 16 ground, maritime, and airborne users. All SVs will have an on-board battle management processor (Battle Management, Command, Control, and

Communications (BMC3)) for supporting on-orbit mission related processing, increased bus automation (in support of more autonomous resiliency), and mission-driven network management.

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

Table 1 - Nominal T1TL Constellation

Parameter Value

Number of Planes 6

SVs per Plane 21

Altitude 1000 km

Inclination ~81 deg

Nodal separation between planes ~31 deg

In-Plane Mean Anomaly Separation ~17 deg

Anomaly Phasing Between Consecutive Planes ~10 deg

Minimum Optical Links per SV 4

Mission Payload(s) Link 16 and BMC3

Mission Data Downlink Ka

Navigation APNT and GPS

The system description and requirements can be found in Attachment 1 – Statement of Work and

Technical Requirements Document of this solicitation. The Offeror shall propose a solution that meets the requirements as laid out in that attachment.

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

o BMC3 o Optical Communications Terminals o Link 16 o Space Vehicle Bus o System Integration o Operations and Sustainment Personnel o 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

3.1 Proposal Preparation Instructions

The Offeror shall submit their Tranche 1 Transport Layer (T1TL) proposal via five (5) volumes.

Specific volume contents and associated page limits are detailed below.

Volume I – Governance shall contain a detailed description of the Offeror’s 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 T1TL program and a complete listing of data rights asserted by the Offeror and all of its subcontractors.

Volume II – Technical shall contain a detailed description of the Offeror’s 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 space vehicle (SV) delivery.

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

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. All margins (top, bottom, left, and right) shall be no smaller than one (1) inch. 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.

3.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 the Offeror’s proposal and not evaluated.

3.1.1.1 Executive Summary

The Offeror shall present their proposed system governance solution for the T1TL, 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.

3.1.1.2 Program Management

The Offeror 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. 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 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, 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 its processes to staff the program with qualified personnel, identify and manage critical vendors and subcontractors, and control costs within a firm fixed price environment. 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 1 - Statement of Work and Technical Requirements Document and in accordance with other dates specified throughout Attachment 1. If the Offeror believes 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, the Offeror is free to propose it and the rationale behind their belief.

For each review combined, omitted, or added, the Offeror shall clearly delineate during what remaining review(s) the information traditionally provided shall be discussed. Table 4 identifies mandatory milestone payment events. If the Offeror omits 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.

The Offeror shall explicitly state the need for any anticipated waivers to Government standards and/or compliance documents identified Attachment 1 – Statement of Work and Technical

Requirements Document.

3.1.1.2.1 Subcontractor and Supply Chain Management

The Offeror shall address their subcontractor and supply chain management methodologies. The

Offeror should describe how they will minimize the effect on the program from fluctuations in supply chain availability and subcontractor deliveries.

3.1.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 T1TL program.

3.1.1.3 Systems Engineering

The Offeror shall detail the Systems Engineering processes and methods that will be used to execute the T1TL program. 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

Government expects that the Offeror will utilize Systems Engineering best practices.

3.1.1.4 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 relatively short on-orbit lifetime.

3.1.1.5 Organizational Conflict of Interest

The Offeror 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 T1TL program. If the Offeror believes that they and their teammates have no organizational conflicts of interest, then they should explicitly state this position.

If the Offeror believes that an OCI exists or may exist upon award, then the Offeror 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.

3.1.1.6 Personnel Résumés

Personnel résumés shall not exceed two (2) pages 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.

The Offeror shall identify the key personnel planned to be assigned to this program from the

Offeror and major teammates as appropriate. 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

Planned role within the T1TL 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

Signed statement agreeing to support the SDA T1TL 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 T1TL program if awarded.

At a minimum, 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

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

The Offeror shall compare and contrast their submitted personnel résumés against the SDA T1TL requirements to validate corporate and individual experience and expertise thereby giving the

Government confidence in the Offeror’s probability of success. Format for this comparison is entirely up to the Offeror but this section of the proposal should stand alone for evaluation.

3.1.1.8 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, using the format shown in Table 2. 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 Table 2. Any item related to the performance of this effort and not contained in Table 2, 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.

Table 2 - Technical and Data Rights Assertion Template

Company

Asserting

Data Rights

Hardware/Technical

Data/Computer Software to be Furnished with

Restrictions

Summary of

Intended Use in the

Conduct of the

Effort

Basis for

Assertion

Asserted

Rights

Category

Name of

Person

Asserting

Restrictions

(NAME) (LIST) (NARRATIVE) (LIST) (LIST) (LIST)

Table 2 shall be included as an attachment to Volume I and will not be included in the page count.

3.1.2 Volume II - Technical

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

3.1.2.1 Executive Summary

The Offeror shall present their proposed solution concept for two (2) planes of the T1TL. The

Executive Summary shall include an Operational Viewpoint (OV)-1 or equivalent high-level overview of the proposed solution. The graphics shall depict the space vehicles, 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 provide data to the warfighter. Integrated into this graphical representation shall be the Offeror’s milestone-driven integrated master schedule for capability delivery, culminating in an in-orbit delivery and performance per SDA’s schedule requirements.

3.1.2.2 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

Vehicle configuration showing all major components

Backup TT&C system design

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.

3.1.2.2.1 Tranche 1 Transport Layer Payload Architecture and Design

The Offeror shall present their overall payload architecture and design. For each payload element below, the Offeror 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, and must include schedule and risk assessments for subject completion.

3.1.2.2.1.1 Optical Communication Terminals (OCT)

The Offeror shall provide a detailed description of the optical communication terminals, including the placement on the SV, individual and total field of regard, and ability to create and maintain space-to-terrestrial and space-to-space links. The Offeror should 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 creation 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.0, detail any non-compliant components of their design, and describe the path to full compliance for those components.

3.1.2.2.1.2 Ka Mission Payload System

The Offeror shall provide a detailed description of Ka-band subsystems used for the mission payload communications. The Offeror 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. The Offeror should identify the antenna configurations, field of regard, and deployment mechanisms for each of the antenna systems. The

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

3.1.2.2.1.3 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 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. The Offeror should identify the antenna configurations, field of regard, and deployment mechanisms for each of the antenna systems. The

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

3.1.2.2.1.4 Link 16

The Offeror shall provide a detailed description of data packaging and interface requirements to enable receipt and transmission of Link 16 information to airborne, maritime and/or ground assets.

The Offeror shall include a list of systems and customers for which this has previously been accomplished or state that the Offeror does not have specific previous experience in this area. In particular, the Offeror should identify specific user equipment to which Link 16 information has been successfully transmitted (if accomplished previously). The Offeror should identify the field of regard, anticipated power requirements, anticipated data rate, bit error rate, and any other parameters key to mission performance. The Offeror should provide a link budget demonstrating the closure of the 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). Additionally, the Offeror shall detail their trade-space analyses for their Link

16 transmit power and antenna system along with their proposed system configuration; this analysis should describe the considerations and conclusions for the proposed design and meeting the stated requirements. This analysis shall be included as an appendix to this volume and will not count against the page limit, as described in Section 3.1.2.8.1.

3.1.2.2.1.5 Battle Management Command, Control, and Communication (BMC3)

The Offeror shall describe the Battle Management Command, Control, and Communication

(BMC3) module and detail its hardware configuration, performance specifications, features that support secure operations, and the sizing rationale applicable to the key processing elements. The

Offeror shall describe how their BMC3 module integrates with both the ground and space segments of Tranche 1 and how the BMC3 module interacts with the SV. The Offeror shall describe how their BMC3 module has been designed to support the hosting of a Secure Interoperable-middleware

Layer and how their design features will help support the implementation of future distributed processing. The Offeror should describe how their approach to loading and running SV applications, both on the ground and in orbit, is secure.

The Offeror shall provide a description of the system architecture that is traceable to the BMC3

System Requirements. A preferred architecture is modular, scalable, and is based on open standards at its interfaces. The Offeror should explain how decisions about their BMC3 module design relate to future mission application processing expectations. The Offeror should identify the essential aspects of the design that enable a cyber-secure BMC3 solution. The Offeror should identify major hardware and software interfaces, all applicable standards with which the design will comply, and any proprietary or unique systems elements.

The Offeror shall provide an assessment of the following items:

Availability of manufacturer/developer support for all elements of the design over the operational life of the system. This support shall include, but not be limited to upgrades, defect fixes, and security patches

Availability of replacement hardware over the operational life of the system to support sustainment of BMC3 aspects on the ground

3.1.2.2.1.6 Networking and Data Routing

The Offeror should describe the networking capabilities enabled by their technical solution. The

Offeror 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. The Offeror should indicate how their design supports networking and data routing both with and without the use of the BMC3 module to provide onboard network control and management. The Offeror should discuss their plans for on-orbit network initialization and provide estimates of system performance.

3.1.2.2.1.7 Navigation

The Offeror 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 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 and/or BMC3 processor, and

The PNT Situational Awareness system including antenna concepts and trades

3.1.2.2.2 Space Vehicle (SV) Bus Design

The Offeror 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 the Offeror elect a non-commoditized bus alternative, they shall present their process for commoditizing the alternative bus.

3.1.2.2.2.1 Bus Design and Heritage

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

Where and how many have flown

Design life and experienced flight life

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

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.

3.1.2.2.2.2 Space Vehicle (SV) Subsystems

For each of the major subsystems (e.g. electrical and power; attitude control; telemetry, tracking and control; etc.) the Offeror shall provide a detailed description of the subsystem as well as system heritage (similar to that for Bus Design and Heritage above). 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 implementation.

3.1.2.2.2.3 Cybersecurity

The Risk Management Framework (RMF), per DoD Instruction 8510.01, will be used by the

Offeror to obtain separate authorities to operate (ATO) from the Government for the ground segment and for the space segment. For T1TL, the ground segment refers to any ground stations, networks, or ground-based antennas supporting the T1TL SVs during launch and early operations, transition to operations, and operations. The Government has already performed Step 2 of the RMF process by selecting security controls that the Contractor must implement for the ground segment and for the space segment to achieve the desired system categorization. These security controls are included in the RMF Process and Security Controls for T1TL Ground and Space Segments.xlsx document in the Bidder’s Library. In their proposal, the Offeror may provide arguments to add or remove any security control while still achieving the security objectives of both the T1TL space segment and ground segment. The Government Authorizing Official will make the final determination on the security controls that shall be implemented.

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

If desired, the Offeror may submit classified discussions related to the cyber resiliency of their system. Each page of these submissions will count as a full page of Volume II, regardless of the amount of text on the page. The allowable page count for the Unclassified Volume II will be reduced by the number of pages in the classified submission. Offerors wishing to submit a classified submission shall follow the instructions in Section 3.2.

3.1.2.2.2.4 Encryption

The Offeror should describe the proposed implementation of security concerns, such as red-black isolation, encryption, and command authentication. The Offeror should 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 T1TL vendors and the ground.

3.1.2.2.3 Interoperability

The Offeror should discuss how interoperability between vendor-agnostic SVs is enhanced and enabled by their technical solution. This section should detail other programs for which the vendor has enabled interoperability, how they tested – or would test – this requirement, and the additional capability for the customer shown by this process. The Offeror should discuss situations in which they have led or at least participated in the development and acceptance of industry standards.

Simply stating that the Offeror will work with SDA to ensure interoperability will not be sufficient for this section; the Offeror shall detail instances in which they instantiated interoperability in theirs’ and other vendor’s systems, subsystems or components. The Offeror should define the verification, interoperability, and compatibility tests that they plan to perform and the benefit that those tests will bring to SDA.

3.1.2.3 Manufacturability

The Offeror 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 the

Offeror in the design, development, assembly, integration, test and delivery of T1TL 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 T1TL 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 T1TL 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 they consider important to demonstrating their capabilities, video inspection shall, at a minimum, present the system-level assembly, integration, and test (AI&T) process and shall capture the assembly-line process and assembly of at least the following SV components:

SV Bus

OCT

Link 16 https://safe.apps.mil/

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 the Offeror or a major teammate to produce the required number of components. The Offeror shall provide estimates of the manufacturing capacity of themselves (if applicable) and any major teammate, as identified in

Section 3, inclusive of current contracts and any potential contracts within the Tranche 1 timeframe.

3.1.2.3.1 Supply Chain

The Offeror shall address production capacity, supply chain capacity, supply chain security, and production scalability issues for the T1TL SV buses and key payloads including, but not limited to, OCTs, Link 16, and cryptographic equipment.

3.1.2.4 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, 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 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 the Offeror. For cases where test activities are expected to be accomplished outside of the Offeror’s direct control, the Offeror should identify their approach to manage test conduct and the experience level of the organization the Offeror plans to use to conduct the test. Of particular interest to SDA is the Offeror’s approach to conducting tests and demonstrations in concert with the SDA OC prior to 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.

3.1.2.5 Launch Services Overview

SDA will procure launch services through the use of the National Security Space Launch Phase 2 contract. The Offeror shall describe how twenty-one (21) of their SVs will integrate onto a single

EELV-M (Evolved Expendable Launch Vehicle-Medium) class launch vehicle, including any custom adapters or separation required to attach to the launch vehicle. The Offeror should include graphics of all twenty-one (21) vehicles integrated onto a representative launch vehicle. The

Offeror shall clearly identify any limitations that their design imparts on the launch vehicle and shall identify the total mass of the SVs and any adapter systems and/or leave behind mass. The

Offeror shall identify any particular launch services (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

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.

class launch vehicle, the Offeror shall provide the bus heritage. For pricing purposes, the Offeror shall assume that all launches will be conducted from Vandenberg Space Force Base.

3.1.2.6 Ground Segment and Operations

The Offeror shall present their approaches to operating their constellation through their NEBULA

Operations – Vendor Architecture (NOVA) software and integrating with the SDA Unified

Planning Environment and Resources for NEBULA Operations – Vendor Agnostic

(SUPERNOVA) provided by the SDA Operations and Integration (O&I) contractor. The Offeror shall define which functions their NOVA will provide, which functions are assumed to be provided by SUPERNOVA, and how the two systems will interact during operations and maintenance activities. The Offeror shall describe their use of COTS software and tools and the resultant benefits to integrated operations. The Offeror 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. The Offeror shall describe their approach to shift the control of their SV planes to the operations center as part of the development of the integrated ground system.

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

The Offeror should describe the suggested approach for verification that the proposed SVs are fully compatible with the integrated ground segment and the SDA Operations Center (OC).

3.1.2.7 Mission Operations, Sustainment, and Disposal

The Offeror 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 OC. The Offeror shall clearly identify the anticipated locations of SV communications systems, ground antennas, and processing facilities that will be utilized during

LEOps. The Offeror shall clearly identify the ability of their facilities to support operations at

SECRET classification and what network connections are currently available. The Offeror should provide an overview of the LEOps plan for orbit raising and SV and constellation level initialization and checkout. The Offeror 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. The Offeror shall identify the support that they will provide to the SDA OC during nominal constellation operations, surge support, and anomaly operations. The Offeror shall describe the disposal plan for each SV and how that plan will reliably dispose of decommissioned SVs.

3.1.2.7.1 Mission Design

The Offeror shall provide a CONOPs for the operation of the T1TL Constellation, including network maintenance and initialization, data transfer, and direct-to-warfighter communications.

The Offeror should clearly identify any mission constraints or limitations.

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

3.1.2.8.1 Link 16 Trade Space Analysis

The Offeror shall describe their trade-space analyses for their Link 16 transmit power and antenna system along with their proposed system configuration. This analysis should describe the considerations and conclusions for the proposed design and meeting the stated requirements. This analysis is limited to five (5) pages. Any pages beyond the limit will be removed from the volume and will not be evaluated.

3.1.2.8.2 Commercial Data Sheets

The Offeror may submit commercial data sheets and/or previously delivered detailed designs submitted to other customers as part of system or subsystem delivery. However, the set of submitted commercial data sheets is limited to twenty (20) pages total and no more than two (2) pages per separate item, inclusive of any title pages. Any pages beyond the twenty (20) page limit will be discarded.

3.1.2.8.3 Parameter Specification

The Offeror shall complete the value column in each worksheet of the

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

3.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 the Offeror’s proposal and not evaluated.

3.1.3.1 Integrated Master Schedule (IMS)

The Offeror shall present the milestone-driven IMS designed to meet the Government’s notional milestones provided in Section 2.1 of Attachment 1 – Statement of Work and Technical

Requirements Document and launch schedule identified in Section 4 of Attachment 1 – Statement of Work and Technical Requirements Document. The Offeror shall clearly indicate the anticipated schedule margin for each launch, 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. The Offeror 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 the Offeror, 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 the Offeror’s 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 the Offeror’s proposed program.

The Offeror 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. The Offeror shall discuss the critical path analysis used to determine the primary and secondary critical paths. The Offeror shall discuss their approach to managing progress against the baseline schedule. The Offeror shall include delivery dates of components from all major teammates and shall clearly identify which of these components lie on the critical path.

The Offeror 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. The Offeror shall identify the top schedule risks and outline their approach(es) to mitigate the risks and ensure on time delivery. The

Offeror shall identify which teammate deliveries and which external dependencies produce the most risk to on time delivery.

The Offeror 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…