Attachment_3_ASLON_Example_MRD.docx

AGILE SMALL LAUNCH OPERATIONAL NORMALIZER (ASLON)

Mission Requirements Document (MRD)

Basic: April, 2018

REVISION HISTORY

1. INTRODUCTION

OVERVIEW:

This document provides the launch vehicle mission requirements for the Agile Small Launch Operational Normalizer (ASLON) Orbital mission, which will be launched under a Small Rocket Program-Orbital (SRP-O) contract.

The goals of the ASLI mission are to launch an orbital demonstration mission to deliver a 12U to 36U (TBD) spacecraft to a TBD orbit.

The mission responsibility of the Launch Services Contractor (LSC) will end when Space Vehicle (SV) has been deployed.

ASLON is a Mission Assurance Category 1 or Category 2 (TBD) mission.

ASLON is a class TBD payload.

SCOPE:

This Mission Requirements Document (MRD) is the controlling source and authority for the mission requirements. In addition to specifying mission requirements, this MRD will:

Identify roles and responsibilities and interfaces among the various contractors and Government agencies supporting the mission.

Document data provided by the agencies furnishing the SV to be used by the LSC in developing the Launch Vehicle (LV) configuration, integrating the SV, targeting the LV, processing the flight hardware, and conducting the mission.

Identify constraints and environments required by the SV.

Identify test-and-analysis requirements to verify interfaces between the SV and LV and to verify required SV characteristics.

This MRD will be maintained by the USAF SMC/LEX (RSLP) office. In many cases, the detailed requirements and data will be specified in other documentation, which will be referenced herein. This includes documents such as the SRP-O Performance Work Statement (PWS) and the LV/SV Interface Control Document (ICD), which identifies detailed SV interface requirements and the range requirements documentation developed in accordance with the Universal Documentation System (UDS).

ROLES AND RESPONSIBILITIES:

The roles and responsibilities of the agencies and contractors that will support the mission are described below:

Payload Program Office (PPO):

The PPO provides the SV. PPO’s activities and responsibilities include:

Participation in program management Provision of SV range-safety documentation at the request of the USAF Shipping the SV to the launch site

LEX:

The RSLP branch (LEX) of the USAF’s Launch Enterprise Directorate (USAF/SMC/LE), located at Kirtland AFB, NM, is responsible for SRP-O launch systems and launch operations. Its activities and responsibilities include:

Participation in program management (lead for launch segment) Range support LV integration SV interface and mating Mission Assurance Contractor (MAC):

A mission assurance contractor, under contract to the LEX, shall provide Mission Assurance and Independent Verification and Validation support for the LV. Higher-level risks identified by the MAC will be sent to PPO in monthly status updates provided by the Mission Manager (MM), and overall risk assessments of the program will be addressed in design reviews and readiness reviews.

LSC:

A launch-services contractor, under contract to the LEX, will provide the LV design, the LV and LV GSE, integration and interface to the SV(s), vehicle mating, mission planning, and launch of the LV.

The LSC shall ensure that Associate Contractor Agreements are completed for the following associate contractors:

METIS contractor Arctic Slope Federal Space and Federal

TASC

Tecolote Research, Inc.

If necessary, the LSC shall also ensure that Non-Disclosure Agreements are completed for the above contractors.

Additional Performance Work Statement Requirements Space Debris Assessment Report (SDAR):

The LSC shall perform analysis and produce a SDAR to demonstrate compliance with AFI 91-217 Attachment 2 for the LV (the SV shall not be included in this report/analysis). (CDRL A0xx) Mission Requirements Mission Scenario: The vehicle will be launched from a TBD coast launch site.

Launch Vehicle Description Vehicle Configuration:

The final launch vehicle configuration will be LSC proposed.

Payload Integration:

LSC shall integrate the SV(s).

Telemetry (TM):

The LV TM shall be selectable. The transmitters shall have sufficient power to provide adequate link margins as defined by Range Flight Safety Documentation.

The LSC shall be responsible for all housekeeping, instrumentation, and position data links.

Launch Conditions Position:

LSC Proposed Environmental Control:

The LSC shall ensure the motors used are maintained within environmental limits in accordance with Air Force Technical Order (TO) specifications for motor exposure. (Applies to GFP motors only) Date/Time:

The SV(s) mission is scheduled for TBF, Fiscal Year 20TBD (FYTBD). There will be no back-up vehicles built for this mission.

Range Coordination:

All test operations at the range will be conducted in accordance with an approved Operations Requirement (OR) for the mission (to be published), and applicable range documents.

Trajectory Profile:

The mission flight profile will be a TBD degree inclination TBD orbit, with an altitude of TBD NMI Insertion Accuracy (3-Sigma):

The maximum dispersions of the payload orbit after deployment shall be within TBD NMI altitude for insertion apse, TBD NMI non-insertion apse, and TBD inclination.

Attitude Control (3-Sigma);

The LV shall control its attitude at the time of payload deployment to ±1º of the desired attitude with drift rates ≤ 1 º/sec about each axis Collision/Contamination Avoidance Maneuver;

The LV shall perform C/CAM as necessary to minimize payload contamination and preclude re-contact between the deployed payloads or other objects and the launch vehicle.

Measurements:

Vehicle status consisting of guidance, GPS and attitude data, environmental data (to include thermocouple data), and housekeeping functions shall be measured via telemetry. The LV position, velocity, and attitude shall be measured on-board throughout the flight via the LV inertial measurement unit (IMU) and shall be displayed real-time at the range via LV TM.

Data Handling/Distribution:

Handling and distribution of telemetry data will be as described in the OR.

Post processed Trajectory Measurements:

Kinematic Instrumentation: Instrumentation to provide accurate reporting of the position, velocity, and acceleration, of the payload are required. Acceptable tolerances on this instrumentation are 1.0 m per axis in position, 1.0 m/sec per axis in velocity, and 1.0 m/sec2 per axis in acceleration. Acceptable tolerance for post launch pointing data is 2.5 degrees per axis. This data required at a data rate of 50 Hz or better.

Payload Characteristics Space Vehicle Envelope

TBD height

TBD width

Space Vehicle Mass Properties Weight: TBD lbs.

Center of Gravity: TBD of Space Vehicle Environments:

The design shall include definition of the following payload flight environments: Acoustic, Shock, Random and/or sine vibration, Transient loads, and Steady state acceleration. These environments shall be documented in the LV/SV ICD.

Payload Access:

The LV shall provide access to the payload after fairing encapsulation without removing the fairing or breaking electrical connections. Fairing access shall support conditioned air and / or gaseous nitrogen purge of the fairing volume during ground operations and prior to launch. If needed, associated GSE doors shall be included to allow for cabling pass-through during ground processing, while maintaining environmental controls within the fairing.

The opening size shall be defined by the LSC.

Separation System:

TBD configuration Electrical Interfaces:

TBD

Range Tracking:

The LV shall include a GPS range safety tracking system or Autonomous Flight Safety System capable of providing sufficient LV status data for range safety.

ACRONYM LIST

REFERENCES

PAGE L - 8 of 8