Attachment 2 Systems Requirement Document (SRD) (3).pdf

Acquisition Delta, Innovation and Prototyping Space Test Program (STP)

Space Test Experiment Platform 2.0 (STEP 2.0)

Attachment 2 Systems Requirements Document (SRD)

FA8809-24-R-B001

Version 1 Space Systems Command

Acquisition Delta, Innovation and Prototyping DoD Space Test Program

(SSC/SZIS)

Kirtland Air Force Base Albuquerque, NM 87117

STEP 2.0 IDIQ

Attachment 2 Systems Requirements Document (SRD) FA8809-24-R-B001 ii

Acquisition Delta, Innovation and Prototyping Space Test Program (STP)

Space Test Experiment Platform 2.0 (STEP 2.0)

SUBMITTED BY:

APPROVED BY:

DAVID J. LORE, Major, USSF Program Manager, STEP 2.0

BRIAN A. SHIMEK, Lt Colonel, USSF Director, DoD Space Test Program

Date Signed

Date Signed iii

Change History

Version Effective Date Prepared by Changes

1.0 10 May 2024 Maj LORE, DoD STP Document Creation

Table of Contents

1 GENERAL INFORMATION

1.1 SPACE TEST EXPERIMENT PLATFORM 2.0 CONTRACT OVERVIEW

1.2 STEP 2.0 DOCUMENT SCOPE

1.3 TERMINOLOGY

1.4 TYPES OF REQUIREMENTS

1.4.1 IDIQ STANDARD REQUIREMENTS

1.4.2 DELIVERY ORDER REQUIREMENTS

1.4.3 UNIQUE REQUIREMENTS

2 DOCUMENTS NOTES

2.1 APPLICABLE DOCUMENTS

2.2 COMPLIANCE, REFERENCE, AND GUIDANCE DOCUMENTS

3 PAYLOAD INTERFACE REQUIREMENTS

3.1 MECHANICAL INTERFACE

3.2 THERMAL INTERFACE

3.3 POWER INTERFACE

3.4 DATA INTERFACE

4 SPACECRAFT AND SPACE VEHICLE DESIGN REQUIREMENTS

4.1 SPACE VEHICLE MISSION AND MISSION DURATION

4.2 SPACE VEHICLE TYPES

4.2.1 FLIGHT PROVEN SPACECRAFT

4.2.2 GEOSYNCHRONOUS CAPABILITY

4.3 MATERIALS

4.3.1 PARTS, MATERIALS AND PROCESSES

4.3.2 FASTENED JOINTS

4.3.3 LOW OUTGASSING MATERIALS

4.3.4 CORROSION RESISTANCE

4.3.5 VENTING PROVISION

4.4 STRUCTURES AND MECHANISMS

4.4.1 MECHANISM DESIGNS

4.4.2 STRUCTURAL DESIGN REQUIREMENTS

4.4.3 MASS PROPERTIES

4.5 SPACE ENVIRONMENT DESIGN REQUIREMENTS

4.6 ELECTRICAL POWER SUBSYSTEM

4.7 THERMAL CONTROL SUBSYSTEM

4.8 EMISSIONS AND SUSCEPTIBILITY

4.9 BONDING

4.10 ATTITUDE DETERMINATION CONTROL

4.11 TELEMETRY, TRACKING AND COMMANDING

4.11.1 DATA TRANSMISSION

4.11.2 ENCRYPTION

4.11.3 COMMAND EXECUTION REQUIREMENTS

4.11.4 DATA HANDLING

4.12 SC PROCESSOR REQUIREMENTS

4.12.1 SC PROCESSOR LOADING

4.12.2 SC TIMING

4.12.3 SC PROCESSOR UPDATES

4.12.4 FAULT DETECTION AND RESPONSE

5 SPACE VEHICLE TESTING AND REQUIREMENTS VERIFICATION

5.1 FUNCTIONAL TESTING

5.2 ENVIRONMENTAL TESTING

5.2.1 SC COMPONENT AND SC ENVIRONMENTAL TESTING

5.2.2 SV ENVIRONMENTAL TESTING

GROUND COMPATIBILITY TESTING AND END-TO-END FULL SYSTEM 5.3

TESTING

5.4 WEEK IN THE LIFE TESTING

5.5 CONTAMINATION AND ENVIRONMENTAL CONTROL

5.6 MECHANICAL FUNDAMENTAL FREQUENCY

5.7 STORAGE

5.8 TRANSPORTATION

6 LAUNCH AND ON ORBIT REQUIREMENTS

6.1 LAUNCH VEHICLE SEPARATION SYSTEM

6.2 SPACE VEHICLE TO LAUNCH VEHICLE INTEGRATION

6.3 LAUNCH SITE TESTING AND BATTERY CHARGING

6.4 LAUNCH AND EARLY ORBIT OPERATIONS

6.5 DISPOSAL

6.6 GROUND SUPPORT EQUIPMENT

7 GROUND/MISSION OPERATIONS

7.1 PROVEN GROUND SEGMENT

7.2 GROUND SEGMENT AVAILABILITY AND RELIABILITY

7.3 GROUND SEGMENT ARCHITECTURE

8 SECURITY AND COMMUNICATIONS SECURITY REQUIREMENTS

8.1 REGULATION

8.2 ENCRYPTION REQUIREMENTS

1 GENERAL INFORMATION

1.1 Space Test Experiment Platform 2.0 Contract Overview

The Department of Defense (DoD) Space Test Program (STP) is a multi-service program supporting Army, Navy, Air Force, and Space Force space test missions. DoD STP provides space access for Science and Technology (S&T) experiments throughout the DoD. S&T experiments are provided by the DoD Laboratories, (e.g., Air Force Research Lab (AFRL) and Naval Research Laboratory (NRL) and any experimenter that has a DoD sponsor (e.g., universities, interagency cooperation, and international partners).

The Space Test Experiment Platform 2.0 (STEP 2.0) program is the STP contract vehicle for a multiple award Indefinite Delivery/Indefinite Quantity (IDIQ) contract with separate Delivery Orders (DOs) to procure proven spacecraft (SC) and mission operations for science and technology (S&T) experiments. Specific payload(s) (PL) for integration onto the host SC and the required orbit information will be determined at the time of each DO request for proposal release.

1.2 STEP 2.0 Document Scope

This IDIQ Systems Requirements Document (SRD) defines the key system and subsystem level requirements to support each DO. This document includes requirements for SC fabrication, PL integration, Space Vehicle (SV) testing, Launch Vehicle (LV) integration, launch site testing, ascent, launch, and early orbit check-out and one year of experiment mission operations support to include the ground segment. Changes or modifications to the SRD requirements stated herein will be included at the DO level.

This IDIQ SRD also discusses the division of responsibility between the PL and SC provider as well as common provision for mechanical, thermal, power, and data interfaces that will be provided by the SC. The information provided in the IDIQ SRD combined with a DO will serve as the foundation for mission specific interface control documents (ICDs) to be delivered for each mission.

1.3 Terminology

SC refers to the SC bus with no PL(s). A PL is the space-borne hardware and software components of an experiment (e.g., instruments, booms, and antennas) supplied as Government Furnished Property (GFP) from STP or reimbursable customers. The PL suite is the combination of all PLs on the mission. The SV is the SC integrated with the PL suite. The STEP 2.0 IDIQ contract will be managed by DOD STP. The mission specific Principal Investigators (PIs) are representatives from each experiment organization, leading the individual instrument development. The STEP 2.0 DO specific contractor(s) will be responsible to Government to integrate each of the experiment PL(s) to the SC.

Ground segment solution consists of the ground station/system, mission operations facility, and communication network infrastructure providing command and control of the SV and distribution of PL data to the Government customer(s).

The term "to be determined (TBD)" means that the contractor should determine the missing requirement in coordination with the Government.

The term "to be reviewed (TBR)" means that the requirement may be deemed appropriate by the contractor or the Government and may be changed by the Government in the course of the system definition.

The term "to be supplied (TBS)" means that the Government will supply the missing information in the course of the system definition.

1.4 Types of Requirements

Mission requirements include both mission-specific (standard) requirements, consistent with the Statement of Work (SOW), this document, DO requirements, and mission-unique requirements. All requirements will be designated by curly brackets that include the requirement number.

1.4.1 IDIQ Standard Requirements

{2.4.1.a} All STEP 2.0 SVs shall meet the IDIQ SRD Standard Requirements within this document, unless when modified in each DO . At the IDIQ level, all offerors within the pool must possess the capability to produce a Space Vehicle with integrated payload integration and delivery not to exceed 24 months on any subsequent delivery order.

1.4.2 Delivery Order Requirements

DO requirements are implementations of the requirements that are dependent on the specific mission being flown and will be specified in each DO. DO requirements are considered to be in scope of the IDIQ SRD and may be tailored for each DO’s requirements, as required. Delivery periods for Space Vehicles on Delivery Orders (DOs) may not exceed 24 months as enumerated at the IDIQ level.

Moreover, the delivery period for each subsequent Delivery Order is dependent upon payload delivery specifications.

1.4.3 Unique Requirements

Unique requirements are not part of the IDIQ SRD but may be required and paid for by STP, Government mission partner(s), or PL customer(s) for a particular mission. Each DO may specify any unique requirements, as needed.

2 DOCUMENTS NOTES

Any tailoring of documents will be defined in each DO. The Government will have final approval of all tailoring proposed by Space Vehicle Contractor (SVC).

2.1 Applicable Documents

{2.1.a} The SVC shall meet the requirements of the following documents in the order of precedence:

1. STEP 2.0 Delivery Order (DO) Statement of Work (SOW)

2. STEP 2.0 Delivery Order (DO) Systems Requirements Document (SRD)

3. STEP 2.0 Delivery Order (DO) Payload Requirements Document (PLRD)

4. STEP 2.0 Indefinite Delivery Indefinite Quantity (IDIQ) Statement of Work (SOW)

5. STEP 2.0 Indefinite Delivery Indefinite Quantity (IDIQ) Systems Requirements Document

(SRD)

2.2 Compliance and Reference Documents

These documents listed in Attachment 20, contain information relating to the work required by this IDIQ SRD. The mission specific reference documents will be specified and may be tailored in each DO. The documents listed in Appendix B, to include any updates, are applicable.

3 PAYLOAD INTERFACE REQUIREMENTS

{3.a} The SV shall host and support the operation of PL(s) to be defined upon release of each DO request for proposal.

{3.b} The Government will identify and provide the PL(s).

3.1 Mechanical Interface

{3.1.a} SC mechanical interface(s) to PLs shall provide mechanical support, and alignment with respect to the SC attitude reference for all PLs in PL suite as defined in each DO.

{3.1.b} PL(s) shall be mounted to the SC such that the field of regard and/or field of view is unobstructed as described in each DO.

{3.1.c} The mechanical interface provided to attach and secure the PLs to the SC shall survive loading as defined in SMC-S-016.

3.2 Thermal Interface

{3.2.a} The SV shall maintain the PL interface operating and survival temperature limits during all mission phases as defined in each DO.

{3.2.b} The SC shall monitor the PL bulk temperatures at the SC-to-PL interface.

{3.2.c} The SC shall report the PL bulk temperature data in SC telemetry.

3.3 Power Interface

{3.3.a} The SC shall, at a minimum, meet the most stressing case of the PL(s) power requirements as specified in each DO.

{3.3.b} The SC shall continuously supply the orbit average power (OAP) requirement for each PL as specified in each DO from initialization through end of mission.

{3.3.c} The SC shall provide power for each PL of a voltage to be specified in each DO.

{3.3.d} The SC shall provide power lines and connectors for the PL(s) as defined in each DO.

{3.3.e} The SV shall provide for automatic dropout (power shedding) of PL and SC non-essential loads when under low voltage or over-current conditions are encountered.

{3.3.f} The SV shall be powered off during LV integration and launch.

{3.3.g} The SV shall power on and begin SV initialization following SV separation from the LV.

3.4 Data Interface

{3.4.a} The SC shall support data interfaces as defined in each DO.

{3.4.a.1} The SC shall assure adequate SC capacity when the SC and the PL(s) are operating at maximum data rates under normal operating conditions.

{3.4.b} The SC shall maintain data integrity of SC and PL data stored on the SC.

{3.4.c} The SC shall maintain data rates for all PLs in PL suite as required in each DO.

{3.4.d} The SC shall detect and respond to communication faults with the PL(s).

{3.4.e} The SC shall communicate with the PL at a frequency as defined in each DO.

{3.4.f} The SC shall provide the data necessary to determine the time and time tag the PL(s) data outputs from the PL to the timing precision to be specified in each DO.

{3.4.f.1} The SC shall provide Global Positioning System (GPS) time to the PL suite as required in each DO.

{3.4.g} The SC shall provide on orbit SV telemetry or data to any PL as required in each DO.

{3.4.h} The SC shall transfer uplinked commands or data to the appropriate PL via the interface(s) per each DO. Note: There is no requirement for the SC to interpret PL commands.

{3.4.i} The SC shall transfer PL data to the ground segment as defined in each DO.

Note: There is no requirement for the SC to interpret PL data.

4 SPACECRAFT AND SPACE VEHICLE DESIGN REQUIREMENTS

4.1 Space Vehicle Mission and Mission Duration

{4.1.a} The SV shall survive launch.

{4.1.b} The SV shall operate for the mission duration from Launch and Early Operations (LEOP) through SV disposal.

{4.1.c} The SV design life shall be a minimum of one year or as defined in each DO.

4.2 Space Vehicle Types

{4.2.a} The SC shall range in size from 6U CubeSats to Multi-Manifest Design Specification (MMDS) Rev 1.0a Class 2 SC, and any size in between to be specified in each DO.

{4.2.b} The SV shall have a mass compatible with the separation system and launch requirements for the SC form factor.

Note: The Cal Poly CubeSat Design Specification (CP-CDS)-R14 defines the mass and volume specifications for CubeSats.

{4.2.c} The SC shall serve as the platform for experimentation of S&T PLs for the DO duration.

{4.2.d} The SV shall operate in either Low Earth Orbit (LEO) or Geosynchronous orbit.

{4.2.e} The SC and mission shall be a risk class C/D hybrid or class D based on Technical Operating Report (TOR)-2011(8591)-5 to be specified in each DO .

4.2.1 Flight Proven Spacecraft

{4.2.1.a} Each SC shall be flight proven.

{4.2.1.a.i} A flight proven SC shall have a flight history of a minimum of 365 consecutive days of on orbit operations within the last 5 years in the proposed mission orbit.

Note: The mission orbit will either be LEO or Geosynchronous, to be specified in each DO.

{4.2.1.a.ii} SC on-orbit operations of less than 365 days, with a launch date within the last five years may be acceptable for the following situations when one or more of the following conditions are true:

• The SC is currently on-orbit and will reach the 365 days of on-orbit operation within 30 days following release of IDIQ Request for Proposal (RFP) solicitation.

• PL mission requirements were less than 365 days but the SC continued to operate for the full 365 days.

{4.2.1.a.iii} Incremental SC updates (parts obsolescence, batteries, flight software updates, Internal Research and Development (IRAD) improvements, etc.) since last flight may meet the flight proven requirements if they are detailed, justified, and accepted by the Government. The SV flight heritage shall be credited for either LEO or geosynchronous orbit, as previously flown.

4.2.2 Geosynchronous Capability

Each DO will specify if there is a requirement for a geosynchronous orbit. The following requirements will be applicable for a geosynchronous mission.

{4.2.2.a} SV shall operate in a geosynchronous environment.

{4.2.2.a.i} The SC shall withstand the radiation environment at geosynchronous orbit to meet requirements in each DO.

{4.2.2.a.ii} The SC shall perform station keeping at geosynchronous orbit to meet the one-year on-orbit requirement and comply with end-of-life / disposal requirements as defined in Section 6.5.

{4.2.2.a.iii} The SC shall have the proper navigation and position information necessary to meet each DO.

{4.2.2.a.iv} The SV shall operate within the thermal environment at geosynchronous orbit to meet each DO.

4.3 Materials

4.3.1 Parts, Materials and Processes

{4.3.1.a} The SV harnesses and cables shall be designed and manufactured to National Aeronautics and Space Administration (NASA) GSFC-EEE-INST-002 Level 3.

{4.3.1.b} When commercial, non-space rated parts are used within the SV, the parts shall follow a formal parts up-screening process approved by Government program office.

4.3.2 Fastened Joints

{4.3.2.a} The SV fastened joints shall be designed and manufactured to conform to American Institute of Aeronautics and Astronautics (AIAA) S-114-2005.

4.3.3 Low Outgassing Materials

{4.3.3.a} SV materials shall be low outgassing with < 1% Total Mass Loss (TML) and < 0.1% Collected Volatile Condensable Material (CVCM) when tested under conditions of American Society for Testing and Materials (ASTM) E595.4.4.4.

4.3.4 Corrosion Resistance

{4.3.4.a} The SV materials shall be corrosion resistant in accordance with Military Standard (MIL-

STD)-1568D .

4.3.5 Venting Provision

{4.3.5.a} The SV shall direct outgassing venting areas away from PL contamination sensitive surfaces as specified in each DO.

4.4 Structures and Mechanisms

4.4.1 Mechanism Designs

{4.4.1.a} The SV mechanisms shall be built and tested to AIAA S-114A-2020.

{4.4.1.b} The SV mechanisms shall be designed for testing in a 1g environment.

{4.4.1.c} The SV shall neither create nor release any orbital debris.

4.4.2 Structural Design Requirements

{4.4.2.a} The SV shall withstand and subsequently operate after exposure to all mechanical and thermal environmental exposures including ground testing, transport, and launch as specified per the requirements of each DO.

{4.4.2.b} SV structural models and design factors of safety shall be validated/verified by 1) test, 2) analysis, 3) demonstration or 4) inspection.

4.4.2.1 Quasi-static Loads

{4.4.2.1.a} The SV shall withstand launch acceleration loads as defined by the mass acceleration curve specified in a SV-to-LV ICD.

4.4.2.2 Random Vibration

{4.4.2.2.a} The SV shall withstand the launch load induced random vibration following a proto-qualification or flight proof testing strategy 3 decibels (dB) above acceptance for 1 minute per axis to comply with flight proof testing as defined within SMC-S-016 and each DO.

4.4.2.3 Acoustic

{4.4.2.3.a} The SV shall withstand the mission launch acoustic environment.

{4.4.2.3.b} The SV shall be vibration tested to demonstrate the SV’s ability to withstand the launch acoustic environment per SMC-S-016 or as specified in each DO.

4.4.2.4 Shock

{4.4.2.4.a} The SV shall withstand and subsequently operate after exposure to the maximum predicted mechanical shock environment for the mission as specified in each DO.

4.4.3 Mass Properties

{4.4.3.a} Non-CubeSat SV mass properties (e.g., mass, volume, Center of Gravity (C/G), moments of inertia) shall comply with the design specifications defined in the most recently released MMDS for Class 1 and 2 SV.

{4.4.3.b} CubeSat SV mass properties shall comply with the most recently released design specifications as defined in the Cal Poly CubeSat Design Specification or design specifications as defined in the proven CubeSat separation system’s specification documents.

4.5 Space Environment Design Requirements

{4.5.a} The SV shall withstand the natural space environment as defined in MIL-STD-1809 or as specified in each DO.

4.6 Electrical Power Subsystem

{4.6.a} The SC shall supply full power to PLs continuously for at least 365 consecutive days post LEOP and Normal Operations Readiness Review (NORR) acceptance or as defined in each DO .

{4.6.a.i} PL duty cycle scenarios, if required, will be defined in cooperation between the SVC, STP, and the PL providers on a preliminary basis during PL accommodation design effort.

{4.6.b} The SC batteries shall comply with SMC-S-017, as applicable.

{4.6.c} The SC shall have fault detection and response that includes protection from electrical faults.

{4.6.c.i} The SV shall detect low voltage conditions.

{4.6.c.ii} The SV shall detect over-current conditions.

{4.6.c.iii} The SC shall have automatic SV safety responses when a fault is detected.

{4.6.c.iv} SC shall provide automatic dropout (load shedding) of PL and bus nonessential loads.

{4.6.d.} The SC shall provide overcurrent protection for the SC components, subsystems and PL(s).

{4.6.d.i} The SC shall monitor voltage for each bus component and each PL.

{4.6.e} The SC shall report voltage for each bus component and each PL as part of normal SV telemetry.

{4.6.f} The SC shall monitor current for each bus component and each PL.

{4.6.g} The SC shall report current for each bus component and each PL as part of normal SV telemetry.

{4.6.h} The SC shall provide a common, single-point ground for all SC and PL electrical elements.

4.7 Thermal Control Subsystem

{4.7.a} The SC shall control the PL(s) temperatures within safe limit during ground testing, transport, launch, and on-orbit mission phases for all orbital conditions as specified in each DO.

{4.7.a.i} The SC shall control all SV temperatures within required survival temperature limits when PL(s) are in a powered down state.

{4.7.a.ii} The SC shall control all SV temperatures within required operational temperature limits when PL(s) are in a powered on state..

{4.7.b} The SC shall report temperature(s) for each bus component and each PL as part of normal SV telemetry.

4.8 Emissions and Susceptibility

{4.8.a} The SV shall comply with Electromagnetic Compatibility (EMC) grounding practices in accordance with MIL-STD-1542B Section 5.1.3.

{4.8.b} The SV shall comply with conducted and radiated emissions and susceptibility limits set by the most recent version of MIL-STD-461(G).

4.9 Bonding

{4.9.a} SV bonding shall comply with SMC-S-020.

4.10 Attitude Determination Control

{4.10.a} The SC shall control the SV attitude as defined in each DO.

{4.10.b} The SC shall report time-tagged attitude knowledge as defined in each DO.

{4.10.c} The SC shall control high frequency motion (jitter) as defined in each DO.

{4.10.d} The SC shall autonomously acquire a safe mission attitude upon separation from the LV.

{4.10.e} The SC shall autonomously maintain a safe attitude state when normal attitude control is lost.

{4.10.f} The SC shall maintain a power positive condition when normal attitude control is lost.

{4.10.g} The SC shall recover to normal operation by either ground command or autonomously.

{4.10.h} The SC shall prevent damage to the SV when recovered to the normal mission timeline.

4.11 Telemetry, Tracking and Commanding

{4.11.a} The SC command and data handling (C&DH) subsystem should use a digital data bus for interface of the SC subsystem hardware and PL data .

{4.11.b} Overall capability of the SC communication subsystem (data rates, frequencies, modulations, etc) will be determined in each DO.

{4.11.c} The SC frequencies for use by telemetry, tracking, and command (TT&C) will be defined in each DO.

4.11.1 Data Transmission

4.11.1.1 Downlink Bit Error Rate

{4.11.1.a} The SC C&DH communications link between the SV and the ground facility shall function at a bit error rate (BER) of no more than 10-6.

4.11.1.2 Data Quality and Retransmission

{4.11.1.2.a} The SC shall identify unrecognized or poorly formatted commands and report in the telemetry downlink for ground retransmission.

{4.11.1.2.b} The SC shall reject unrecognized or poorly formatted commands.

{4.11.1.2.c} The SC shall re-transmit both SC and PL data upon identification of missing or invalid telemetry blocks.

{4.11.1.2.d} The SC shall retain all data for retransmission, unless commanded otherwise from the ground, for a minimum of 48 hours.

{4.11.1.2.e}The SC shall transmit to the ground SC health and status.

{4.11.1.2.f}The SC shall transmit to the ground ephemeris data including but not limited to timing and attitude.

4.11.1.3 Link Margin

{4.11.1.3.a} The SC link margin for the TT&C downlink between the SC and the ground station(s) shall be at least 3 dB.

4.11.2 Encryption

{4.11.2.a} The SC shall encrypt all SC TT&C, and PL uplink and downlink signals using an End Cryptographic Unit (ECU) per the requirements of each DO and Section 8 below.

{4.11.2.b} The ECU shall be National Security Agency (NSA) approved.

{4.11.2.c} The SC shall be capable of powering on/off the cryptographic equipment without processing commands through the C&DH subsystem in response to a fault condition.

{4.11.2.d} The SC shall autonomously reset the cryptographic unit when there is an absence of an output within a sliding 18 hour window.

{4.11.2.e} The SC shall autonomously power-cycle the cryptographic unit when there is an absence of an output within a sliding 24 hour window.

{4.11.2.f} The cryptographic unit shall transition to a known and repeatable algorithm/key/Vehicle Command Count (VCC) configuration upon reset or power-cycled.

{4.11.2.g} The SC shall be capable of downloading the cryptographic unit logs if the cryptographic unit has the capability.

{4.11.2.h} The cryptographic unit shall not enter bypass mode or any equivalent functional state in the absence of ground commanding.

4.11.3 Command Execution Requirements

{4.11.3.a} The SC C&DH subsystem shall provide command decryption, command verification, command execution, and command storage for later execution.

{4.11.3.b} The SC shall execute or direct real-time commands to the appropriate interface within one second of receipt or as specified in each DO.

{4.11.3.c} The SC shall store commands and execute the command to within one second of the designated time or as specified in each DO.

{4.11.3.d} The SC shall accurately record and timestamp all commands and execution status (i.e., accepted, rejected) in the command logging for downlink to the ground.

{4.11.3.e} The SC shall include in the SC telemetry a counter for valid and invalid received commands.

{4.11.3.f} The SC shall support a commanding mechanism that, following the receipt of an invalid command, inhibits acceptance of subsequent commands within the same command sequence.

{4.11.3.g} The SC shall keep the data and pass the file, with notification, to the ground if an error is detected in a command data file.

4.11.4 Data Handling

4.11.4.1 Data Storage Requirements

{4.11.4.1.a} The SC shall contain sufficient on-board memory to include 100% margin for all SV data (SC and PL data) for a minimum of 48 hours.

{4.11.4.1.b} The SC shall provide partitioning control for on-board SC data storage allotment(s) for each PL contained within each DO.

4.11.4.2 Data Latency

{4.11.4.2.a} The SC shall transmit to the ground all SV data within 24 hours of collection or as specified in each DO.

{4.11.4.2.b}The SC shall transmit to the ground SC health and status.

{4.11.4.2.c}The SC shall transmit to the ground ephemeris data including but not limited to timing and attitude.

4.11.4.3 Data Formatting

{4.11.4.3.a} SC telemetry blocks shall be unambiguously formatted to permit identification of the data origin and the sequencing of the block within the source telemetry stream.

{4.11.4.3.b} Sequencing information shall be unchanged when the data is re-transmitted, allowing reconstruction of the original data stream.

4.12 SC Processor Requirements

4.12.1 SC Processor Loading

{4.12.1.a} The SC shall have a processor(s) capable of software peak processor(s) loading (including process execution, interrupt, and interface handling) not to exceed 70% of the processor(s) capability.

4.12.2 SC Timing

{4.12.2.a} The SC shall maintain an on-board time reference time synchronization to within 100 msec with respect to UTC or as specified in each DO.

{4.12.2.b} The SC shall provide time data at least once per second to each PL or as specified in each

DO.

4.12.3 SC Processor Updates

{4.12.3.a} On-board SC command/telemetry software/firmware shall be capable of being updated and/or modified while on orbit through ground commands.

{4. 12.3.b} The SC shall include the capability to verify all updated changes.

4.12.4 Fault Detection and Response

{4.12.4.a} The SC shall have fault detection and response capability designed to safe the SV when faults are detected as specified in each DO.

{4.12.4.b} The SC shall execute automatic SV safety responses when a fault is detected.

5 SPACE VEHICLE TESTING AND REQUIREMENTS VERIFICATION

{5.a} All SC/SV testing shall comply with safety practices defined within AFI-91-202 and MIL-

STD-882E.

5.1 Functional Testing

{5.1.a} The SC shall successfully pass full functional testing prior to integration of the PL(s).

{5.1.b} SC functional testing shall verify and validate all SC functions for all subsystems including verifying the ability to change encryption keys.

{5.1.c} Results of the SC testing will be provided to the Government at the SC Acceptance Review.

{5.1.d} SV factory testing shall successfully validate all PL interfaces.

{5.1.e}Testing shall include mechanical (fit-check), power and data flows between the SC and PL.

{5.1.f} The SV shall successfully pass full functional testing prior to environmental verification testing.

{5.1.g} Results of the SV testing will be provided to the Government at the Test Readiness and Test Data Reviews.

{5.1.h} The SV Fully Integrated System Test (FIST) shall be used as a baseline prior to and post-environmental testing as part of SV survival verification.

{5.1.i} Functional tests of mechanisms shall be in accordance with AIAA S-114A-2020 to verify non-interference, proper lubrication, adequate torque margins, and strength under worst case loading as defined within SMC-S-016.

5.2 Environmental Testing

5.2.1 SC Component and SC Environmental Testing

{5.2.1.a} Units without previous higher qualification shall be subject to flight proof testing as defined within SMC-S-016.

{5.2.1.b} SC-level environmental testing results shall be presented at the SC Acceptance Review.

Note: Identical SC units and/or components previously qualified to higher flight levels and successfully flown on other SC may be accepted for space flight upon approval by the Government.

5.2.2 SV Environmental Testing

{5.2.2.a} SV structural and thermal testing shall be used to validate models used for design and analysis to demonstrate and validate the flight qualification status of the SV as defined within SMC- S-016.

{5.2.2.b} The SV structure and mechanisms shall be verified to withstand the static and dynamic stresses, strains, shocks, vibrations, temperature, pressure, and vibro-acoustic environments (if applicable) associated with assembly, integration, test, shipping, handling, storage, launch, and on orbit operations as associated with SMC-S-016 and AIAA S-114A-2020.

{5.2.2.c} The SV testing shall be in accordance with flight proof methodology as defined in SMC-S- 016.

{5.2.2.d} The SV testing shall verify, at a minimum, the capability of the SV to survive vibration, acoustic (if required), separation/pyro shock, thermal vacuum, and thermal balance experienced throughout all mission phases as defined in each DO.

{5.2.2.e} Launch loads for the purposes of flight proof verification testing for all SVs will be specified in each DO and/or as specified by the LV provider on a mission specific basis in the LV provider’s SV-to-LV ICD based on an analysis of the integrated PL stack and LV ascent.

{5.2.2.f} Pressure and leakage verification tests shall be required if the SV contains a propulsion system or other pressurized subsystems or components.

5.2.2.1 Quasi-static Loads

{5.2.2.1.a} The SV shall be tested to acceleration load factors as defined by the mass acceleration curve within the latest version of the MMDS or the acceleration loads specified in a mass acceleration curve to be provided by LV in each DO requirements.

{5.2.2.1.b} These loads should be applied at the C/G of the SV using the maximum PL(s) mass.

{5.2.2.1.c} The SV Quasi-static Loads testing may be waived based on sufficient design factor safety with agreement by the Government, and/or as specified in each DO.

5.2.2.2 Random Vibration

{5.2.2.2.a} The SV shall be tested to verify survival of the launched induced random vibration environment following a flight proof testing strategy as defined within SMC-S-016.

{5.2.2.2.b} If the maximum predicted environment (MPE) of the LV is unknown, the random vibration acceptance levels shall be specified in each DO and/or may be derived based on the SV mass following the National Aeronautics and Space Administration (NASA) General Environmental Verification Standard (GEVS) (GSFC-STD-7000B).

{5.2.2.2.c} Strategies for force limiting specific resonant frequencies of primary structures may be permitted with Government review and approval.

5.2.2.3 Acoustic

{5.2.2.3.a} The SV shall be acoustically tested in accordance with SMC-S-016 and TOR- 2011(8591)-2 vol 1 and 2, as specified in each DO.

5.2.2.4 Shock

{5.2.2.4.a} The maximum predicted mechanical shock environment shall be developed in cooperation between the SVC, Government, and STP’s PL customers.

{5.2.2.4.b} The SV shall be tested to survive the maximum mechanical shock environment in accordance with SMC-S-016 and TOR-2011(8591)-2 vol 1 and 2.

5.2.2.5 Thermal Vacuum and Bake-Out

{5.2.2.5.a} The SV shall undergo a thermal bake-out in a vacuum of at least 10-4 torr as specified in each DO requirements documentation or as agreed upon jointly in the SC-to-PL ICD to minimize contamination concerns from SV outgassing.

{5.2.2.5.b} SV thermal vacuum testing shall include a minimum of four cycles with full functional tests conducted at the high and low extremes of the first and last cycles in accordance with SMC-S- 016.

{5.2.2.5.c} SV thermal vacuum testing shall include a thermal balance test.

{5.2.2.5.d} The results of the thermal balance testing shall be used to update and validate SV thermal models per SMC-S-016.

{5.2.2.5.e} Simulated operations representative of the mission activities and scenarios, including typical commanding, tracking, telemetry contacts, and PL operations shall be conducted during the thermal vacuum testing as specified in each DO.

5.2.2.6 EMI/EMC Test

{5.2.2.6.a} Electronic emissions and susceptibility testing shall be in accordance with MIL-STD- 461G (or current version) procedures with the SV in a fully functional configuration.

{5.2.2.6.b} Tailoring of MIL-STD-461G standard to a minimum do-no-harm list of RE102, RS103, CE101, CE102, CS101 and CS114 may be allowed with approval by the Government.

5.3 Ground Compatibility Testing and End-to-End Full System Testing

{5.3.a} SC factory and launch base compatibility tests shall exercise typical data flow including commanding, PL data collection, SC processing, and data downlink operations as part of End-to-End validation testing.

{5.3.b} End-to-End testing shall verify command and data flows between PL, SC, and ground segment including data transmissions from the PL Operations Center (POC) and /or PL data delivery point as defined in each DO or agreed upon by the Government.

{5.3.c} End-to-End testing shall also verify the ability of the ground segment to change communication security (COMSEC) keys.

{5.3.d} The End-to-End testing shall occur after all encryption equipment has been integrated on the SC and ground segment, and all hardware and software configuration changes to support the Risk Management Framework (RMF) process have been completed.

Note: Government deployable equipment may be made available to support these tests.

5.4 Week in the Life Testing

{5.4.a} The SV shall demonstrate extended operations through ground testing for one week of operation to include operations of all PL(s).

5.5 Contamination and Environmental Control

{5.5.a} The SC, SV, and its PL(s) shall be controlled to a minimum cleanliness environment of ISO 8 (class 100,000 level) (ISO 14644-1) or as specified in each DO. .

{5.5.b} Temperature and humidity shall be controlled to avoid condensation on the space hardware or electrostatic discharge during all phases of integration, assembly, testing, shipping, handling, and storage through launch as specified in each DO.

5.6 Mechanical Fundamental Frequency

{5.6.a} The SV and separation system shall demonstrate and/or verify a minimum first fundamental frequency of 35Hz in both the LV axial and lateral directions when supporting the required PL mass as defined in each DO.

5.7 Storage

{5.7.a} The SC/SV shall be capable of being stored for up to six months while awaiting launch or as specified at each DO.

5.8 Transportation

{5.8.a} SC/SV transportation shall limit mechanical loads, vibration, and shock to the levels used for design and verification as specified in Section 5.2.2 or in each DO.

{5.8.b} SC/SV transportation shall maintain temperature, humidity, and contamination control as specified in Section 5.5 or in each DO.

6 LAUNCH AND ON ORBIT REQUIREMENTS

6.1 Space Vehicle to Launch Vehicle Separation System

{6.1.a} The SV’s separation system shall be designed in accordance with the SV-to-LV ICD as specified in each DO.

{6.1.b} The SV-to-LV separation system shall have redundancy and/or reliability as specified in each DO.

{6.1.c} The SV-to-LV separation system shall contain any orbital debris created by the separation.

{6.1.d} The SC shall prevent unplanned separation, power-on, or mechanical deployments during the launch phase of the mission in accordance with AFSPCMAN 91-710, Vol. 3, Sec 3.2.

{6.1.e} The SC shall provide a means to sense separation from the LV.

6.2 Space Vehicle to Launch Vehicle Integration

{6.2.a} SV to LV integration shall be conducted in accordance with the LV-to-SV ICD and as specified in each DO.

6.3 Launch Site Testing and Battery Charging

{6.3.a} All ground operations shall meet the requirements of AFSPCMAN-91-710 Volume 3, or latest version, as applicable to the launch site to include power on and deployment inhibits.

6.4 Launch and Early Orbit Operations

{6.4.a} The SV shall be capable of being launched in an unpowered state.

{6.4.b} The SV shall be capable of maintaining autonomous operation in a safe hold at least up to 48 hours after orbit insertion.

{6.4.c} The SV shall control deployments and RF transmissions during separation from the LV as specified in the LV-to-SV ICD.

{6.4.d} The SV shall be subjected to and successfully pass full functional check-out testing prior to the end of LEOP.

6.5 Disposal

{6.5.a} The SV shall be designed to be disposed in compliance with United States Government Orbital Debris Mitigation Standard Practices 2019 (ODMSP), AFI 91-202, SMC-S-015, SMC-S-022, and each DO, as required.

6.6 Ground Support Equipment

{6.6.a} The GSE shall safely perform the functions required to: inspect, test, operate, evaluate, calibrate, measure, assemble, disassemble, handle, transport, safeguard, store, service, repair, and maintain the SV during all phases of ground operations at the SVC’s facilities, test sites, LV integration site and launch site.

7 GROUND/MISSION OPERATIONS

7.1 Ground Segment

{7.1.a} The ground segment solution shall be capable of command uplink and SC telemetry / PL data downlink as defined in each DO.

7.2 Ground Segment Availability and Reliability

{7.2.a} The ground segment shall have a system availability of 95 percent for real-time SV contact functions as defined in each DO to include data storage, in any sliding 30 calendar day window {7.2.b} The ground segment shall operate with a minimum of 95 percent reliability.

7.3 Ground Segment Architecture

{7.3.a} The ground segment architecture shall have the capability to uplink commands, downlink SC telemetry and PL data, and data distribution to PL provider(s).

{7.3.b} The ground segment architecture shall:

1. Be compliant with DOD Instruction (DoDIs) 5000.02T, 8310.01, 8320.07, 8330.01, 8510.01, 8581.01, 4630.09, 4650.01, and 3222.03 in addition to Committee on National Security Systems Polies (CNSSP)-12, CNSSP-32 and National Institute of Standards and Technology (NIST) SP 800-53 Rev 5.

2. Demonstrate compliance with applicable IT standards, protocols, and interfaces for the sharing of DoD data, information, and IT services as specified in each DO.

3. Demonstrate compliance with performance specifications as specified in each DO.

4. Ensure interoperability and electromagnetic compatibility as specified in each DO.

5. Interface with ground station networks, servers, and data providers as required to support specific missions.

6. Interface with PL or mission partner POCs for receipt of PL commands and transfer of PL and SC mission data as specified in each DO.

7. Disseminate and archive commands and telemetry data between space operations, mission planners, and mission partners.

8. Operate the SV from a Mission Operations Center.

9. Schedule ground station contacts with SV for uplink and downlink as specified in each DO.

10. Support on-orbit SV flight software updates.

11. Enable near real-time downlink and commanding of the SV.

12. Perform ranging as required by each DO.

8 SECURITY AND COMMUNICATIONS SECURITY REQUIREMENTS

8.1 Regulation

{8.1.a} The SV and ground segment shall comply with the security requirements of the RMF cyber security process within DoDI 9510.01.

{8.1.b} The SV and ground segment shall be compliant with RMF cyber security requirements through end-of-life.

{8.1.c} The SV and ground segment shall comply with processing DoD CUI (NIST SP 800-171 revision 2 and, NIST SP 800-172) and classified DoD information (DoD National Industrial Security Program Operating Manual (NISPOM)), as required.

{8.1.d} The SV and ground segment shall comply with the following AO accreditation(s) / assessment(s), as required:

1. Interim Authority-to-Test (IATT).

2. Authority-to-Connect (ATC).

3. Authority-to-Operate (ATO).

4. Agent of the Security Control Assessor (ASCA) assessment.

8.2 Encryption Requirements

{8.2.a} SV and ground segment command uplink and data telemetry downlink shall be capable of implementing encryption per NSA guidelines.

{8.2.b} NSA certified cryptographic equipment shall be used to secure uplink and downlink of SV and PL data during transmission.

4.4.3 Mass Properties

Untitled