MISSION REQUIREMENTS DOCUMENT (MRD)
SPACE TEST PROGRAM (STP)
Version 4.4
19 June 1997
TRI-SERVICE EXPERIMENTS MISSION 6
(TSX-6)
Approved by: _____________ ______
Colonel Thomas U. Mead Date
Director, Space Test Program
1. Technical Scope and General Requirements 11.1 System Definition 11.1.1 Mission Description 11.1.2 Interface Design 11.2 Characteristics 21.2.1 Performance Characteristics 21.2.2 Physical Characteristics 21.2.3 Reliability 31.2.4 Maintainability 31.2.5 Environmental Conditions 31.2.6 Environmental Assessment 31.3 Design and Construction 31.3.1 Electromagnetic Compatibility 31.3.2 Magnetic Control 31.3.3 Contamination Control 41.4 Training 41.5 SC Characteristics 41.5.1 Telemetry, Tracking, and Commanding (TT&C) Subsystem 41.5.2 Thermal Control Subsystem (TCS) 41.5.3 Attitude Control Subsystem (ACS) 41.5.4 Electro Explosive Devices (EEDs), Non-Explosive Actuators (NEAs), and Firing Circuits 41.5.5 Separation Mechanisms 51.5.6 Propulsion Subsystem 51.6 Software 51.7 Safety 52. Deliverables 52.1 Contract Funds, Cost, and Schedule Status 52.2 Experiment-to-Spacecraft Interface Control Document (ICD) 62.3 Operations Documentation 62.3.1 Operations Requirements Summary (ORS) 62.3.2 System Integration and Test (I&T) Plan 72.3.3 Space Vehicle Handbook (SVH) 72.3.4 Operations Manual 72.3.5 Software Users Manual (SUM) 72.3.6 Timing of Flight Operations Support Documents 72.4 Launch Site Procedures (LSP) 82.5 Data Accession List 82.6 GIDEP Alert Responses 82.7 Security Plan 82.8 Flight Operations Support 82.9 Design Reviews 82.9.1 System Requirements Review/System Concept Review 82.9.2 Preliminary Design Review 92.9.3 Critical Design Review 92.9.4 Pre-Integration Review 92.9.5 Pre-Ship Review 92.9.6 Launch Readiness Review 92.10 Engineering Analyses 92.11 Detailed Design Drawings 93. Options 93.1 Propulsion Subsystem 93.2 Telemetry, Tracking, and Commanding (TT&C) Subsystem 103.3 Post Launch Anomaly Support 103.4 Storage 10Technical Scope and General Requirements
All requirements identified in this document shall be contractually binding. Specific text within this document that is informational in nature or could constitute a derived requirement is identified with italics.
This document establishes mission level performance requirements for spacecraft (SC) design and fabrication, experiment integration, testing, ground station development, Launch Vehicle (LV) integration, launch site testing, ascent and early orbit operations, and post-launch operations support and handover operations for the Space Vehicle (SV).
The Tri-Service Experiments Mission 6 (TSX-6) shall fully support the Polymer Battery Experiment (PBEX) and OPREX Spacecraft Evaluation Module (OSEM) experiment in meeting each experiment's success criteria. Option vehicles will fly similar experiments.
- SVS-LV Interface
The Space Vehicle System (SVS) shall be compatible with the LV. The LV contractor is responsible for preparation and configuration management of the LV-to-SV ICD, but input, coordination, and signature is required of the SC Contractor. Delivery of SC interface requirements shall be accomplished thirty days prior to the SC Critical Design Review (CDR). The SC Contractor shall provide vital interface information to the LV contractor for timely development and verification of the LV-to-SV ICD. The final version of the LV-to-SV ICD shall be a compliance document for the SC Contractor. The SC Contractor shall support all interface design meetings.
- SVS-Comanifested SV Interface
The SVS may be co-manifested with a second SV on a single LV. If so, the SVS shall be fully compatible with the co-manifested space vehicle. The SVS transmissions, emissions, and electro-magnetic fields shall cause no interference to the co-manifested SVS. The SC Contractor shall support all interface design meetings.
- SVS-Communication Interface
The SVS will be operated from remote ground stations. The SC Contractor shall provide a minimum of three stand-alone ground stations; the SVS shall be fully compatible with these ground stations. The SC Contractor shall incorporate all necessary inputs from the Government, including, but not limited to: experiment data, command and telemetry requirements, SV information, ascent command and telemetry requirements, LV information, command and telemetry scripts, and all necessary training materials (see 1.4 below). The SC Contractor shall allow for access to the SV by Government personnel.
- SC-Experiments Interface
The SC Contractor shall satisfy the experiment requirements as defined in the Experiment Requirements Documents (ERDs). The SC Contractor shall monitor SC to Experiment interface status to assure the experiments are supplied with the required environment (e.g., power, data communication) in support of the TSX-6 Mission Failure Liability Indemnification Plan. A comprehensive history of the interface data and environment shall be provided to the Government upon request. If any environment exceeds experiment design specifications (defined in the ICD and operations documentation), this shall be reported immediately (not later than 24 hours) after the incident.
The SV, Ground Control Stations (GCS), and Ground Support Equipment (GSE) shall satisfy mission objectives and requirements. The GSE shall perform the functions required to inspect, test, operate, evaluate, calibrate, measure, assemble, disassemble, handle, transport, safeguard, store, service, repair, and maintain the SVS and GCS during all phases of SVS ground operations at the SC Contractor's facilities, test sites, and launch site. The mission shall provide capability to uplink and downlink all experiment state of health data. This data shall be encrypted per National Security Agency guidelines or by an alternative method with Government approval.
- Structure
The SVS shall be designed and verified to withstand the static and dynamic stresses, strains, and vibrations associated with the LV (refer to the Operations Requirements Summary and System Test Plan). For initial design purposes, the SVS shall fit within a dynamic envelope 46 inches in diameter, 79 inches in length. Length measurement shall include the separation system (see 1.5.5), propulsion subsystem (see 1.5.6), and Government-furnished antenna assembly.
- Mass Properties
The mass properties of the SV shall be compatible with LV insertion capabilities, using appropriate SC weight growth margins, substantiated by SC Contractor and Government previous experience. For initial design purposes, the target SV weight shall not exceed 475 lbs, including all experiments and the separation system. The optional propulsion system (see 1.5.6) is not included in this weight. Mass reports shall be provided with the proposal and reported to the Government on a monthly basis until launch.
The overall SV system shall have a demonstrated reliability of 90% over the three year life of the SC. Reliability shall be determined using MIL-HDBK-217F as a guideline, or by an alternate method with Government approval. The SV shall also achieve a safe state autonomously, should an anomaly occur while out of contact. The SV shall include a back-up mode to the standard telemetry and command data link and a software upload capability (see 1.6).
The Offeror shall demonstrate to the Government that its design and sparing approach addresses maintainability of the SC from fabrication through launch. In particular, the SC Contractor shall design the SC for pre-launch maintainability to ensure that the SC is available at the required time for delivery to the Government (DD250).
All mission elements shall withstand all environments (e.g., EMI, shock, and thermal) to be encountered from component fabrication and system assembly through integration, transport, ground operations, storage, launch, and on-orbit operations. For initial design purposes, launch loads shall be the most stressing (a worst-case envelope) of the Taurus and Pegasus XL environments.
The SC Contractor shall support an environmental assessment, required by the Government to measure environmental impacts as a result of TSX-6 efforts.
All hardware and software shall be designed to meet applicable operational, reliability, environmental, and safety requirements. The mission shall be designed so that all hardware is capable of storage, under controlled conditions, for as long as two years. The SC Contractor shall define adequate safety margins to be incorporated into the design.
The mission shall meet the electromagnetic compatibility requirements as defined in the ERDs, final versions of the ICDs, and the requirements of the LV. SC- and GSE-generated electromagnetic interference (EMI) will not degrade the experiments' capability to operate and meet mission objectives. Before launch, the SC Contractor shall demonstrate mutual compatibility under worst case operating conditions.
The mission shall not have magnetic fields that are incompatible with the LV. Any magnetic fields shall meet the requirements defined in the ERDs and in the final versions of the ICDs. SC- and GSE-generated magnetic fields shall not degrade the experiments' capability to operate and meet mission objectives. Before launch, the SC Contractor shall demonstrate mutual compatibility under worst case operating conditions.
The SV environment shall be controlled by the SC Contractor such that contamination detrimental to experiment performance will not be experienced at any time. The environment required to accomplish this goal shall be defined by the SC Contractor, and shall comply with requirements defined in the ERDs and in the final version of the Operations Requirements Summary (ORS).
The SC Contractor shall train experiment agency personnel and associated contractors for on-orbit operations. This training shall include sufficient instructors, training devices, aids, equipment, documents, facilities, and associated software to assure mission requirements are met. Training shall include detailed subsystem and ground operations descriptions, operations scenarios during each mission phase, and contingencies. The SC Contractor shall support all necessary activities (specified in the ORS, see 2.3.1). The SC Contractor shall be responsible for supporting additional rehearsals if schedule slips occur.
The TT&C subsystem shall be compatible with the ERDs, ORS, final versions of the ICDs, and GCS hardware and software. Link margins shall be sufficient to support a 10-6 bit error rate for uplink and downlink between the SC processor and the GCS data storage. The contractor shall define a method of disabling the SC transmit capability at the SC end-of-life.
Thermal Control Subsystem (TCS)
The TCS shall monitor, report, and control the temperatures of the experiment structures, components, and experiment packages as specified in the ERDs and final versions of the ICDs during all mission phases.
Attitude Control Subsystem (ACS)
The SVS shall meet the stability and pointing requirements, as defined in the ERD, in all phases of the mission. The ACS shall collect and provide attitude and attitude rate data to the accuracy and rate specified in the ERDs and final versions of the ICDs.
Electro Explosive Devices (EEDs), Non-Explosive Actuators (NEAs), and Firing Circuits
Design and testing of all EEDs, NEAs, and Firing Circuits shall comply with the range safety regulations. Debris from these systems shall be contained. The SC Contractor shall demonstrate that EEDs will not damage any part of the SV or LV. Note: The OSEM experiment contains two pyro devices (TBD) to uncage the antenna after launch.
The separation system shall provide for both electrical and mechanical interface separations, and shall be compatible with the 38.81 inch diameter, 4 inch high Pegasus separation system interface. The separation system shall be capable of providing a safe separation relative to the LV. Debris resulting from all separations shall be contained.
The SVS shall be designed to accommodate the addition of a propulsion subsystem. The propulsion subsystem, if required, shall be capable of transferring the SVS from the circular parking orbit (if any) to the operational orbit.
Ground operations software required for the mission shall be used during ground testing and shall perform all necessary mission functions. The software user-interface shall be window-driven, documented, and must display meaningful engineering units. The Government shall have full insight into the software design and architecture, including the opportunity to review all contractor-developed source code and verify commercial off-the-shelf (COTS) product performance.
Flight software shall be fully tested before integration into the SC, and flight and near-flight versions of flight software shall be used during SC system-level ground testing. The SC shall have the capability to upload executable software on orbit to patch or fully replace the on-board flight code.
The mission shall be in a safe condition at all times prior to launch and during all LV operations. All launch site operations shall be compliant with the required range safety documents. Mishap prevention programs shall be in accordance with the compliance documentation. All ground operations shall meet the requirements of MIL-STD-1574, AFFTCR 127-3, Eastern and Western Range 127-1, as applicable to the launch site.
The SC Contractor shall submit to the Government quarterly financial status reports of projected expenditures, accrued expenditures, forecasted billing, and projected termination liability. The SC Contractor shall also provide the Government with detailed information regarding:
(1) SC Contractor costs relating to contract performance and
(2) Schedule status including subcontractor and Government-provided hardware or services.
The data shall include past, current, and forecasted funds, cost, and schedule information. The data shall be delivered to the Government throughout the period of contract performance.
Experiment-to-Spacecraft Interface Control Document (ICD)
Following contract award, the SC Contractor shall consult with the Government and experimenters to finalize the interface definition. The interface definition is documented in an Interface Control Document (ICD), which will supercede the ERD, and shall be completed by, and be a part of, the Critical Design Review (CDR). A preliminary ICD information review shall be made available at the time of the Preliminary Design Review (PDR).
The SC Contractor shall transmit sufficient information to allow OSEM operations personnel to operate the system safely and successfully for its design life.
Operations Requirements Summary (ORS)
The SC Contractor shall prepare and provide an ORS to manage experiment integration, experiment test, and flight operations requirements. The ORS is a preliminary document to the documents listed in subsequent subparagraphs of para 2.3. The SC Contractor shall request and incorporate experimenter ORS inputs for the Government, including the following:
- handling requirements;
- requirements for tests to determine experiment health after arrival at the SC Contractor’s facility, SV health during the I&T process, and SVS health at the launch facility;
- requirements for tests (e.g., vibration, thermal vac) to ensure the SV will survive to meet its design life on orbit (testing should simulate as closely as possible the anticipated on-orbit environment);
- restrictions to commanding during environmental and functional tests;
- specifications on cleanliness and contamination control;
- hazardous operations;
- specifications for consumables where applicable;
- specifications for ground power;
- requirements for all Electrical Ground Support Equipment (EGSE), including transportation responsibility from the delivery site to the space vehicle integration site, to the launch vehicle integration site, and then back to the delivery site;
- requirements for all Mechanical Ground Support Equipment (MGSE), including transportation responsibility from the delivery site to the space vehicle integration site, to the launch vehicle integration site, and then back to the delivery site;
- data exchange and data processing;
- experimenter-provided test support equipment.
- initialization requirements, including power and timing, sunlight, data rates and data evaluation;
- sequencing;
- normal operations requirements, including identification and usage of modes;
- projected anomalous situations and remedies;
- associated data rates and power profile (SV usage and power availability), sunlight and time constraints;
- data exchange methods and protocol;
- requirements for redundancy management and other contingency operations.
- System Integration and Test (I&T) Plan
The System I&T Plan shall be derived from the ERD, ICD, and ORS. Experiment hardware will not be delivered until the space platform is ready for experiment integration (see 2.9.4). Readiness shall be demonstrated via successful integration with the experiment simulator. Adequate testing of components, space vehicle subsystems, ground support equipment, software, and space vehicle integrated functions shall be required prior to the start of the experiment I&T phase. The System I&T Plan shall include a definition of any needed Government facility resources, a schedule to support program office verification activities (program office personnel will be present), test exit criteria, and detailed plans and procedures for all I&T activities before delivery to the launch site.
The SC Contractor shall prepare and provide the SVH to define in detail the organization and operation of the space vehicle and its subsystems, including software. The SVH shall also define and provide formats for all commands, data, and telemetry.
The SC Contractor shall prepare and provide an Operations Manual containing detailed steps for the following post-launch activities:
- GCS initialization, checkout, and operation
- SV initialization and checkout
- Nominal operations
- Contingency operations
- Software Users Manual (SUM)
The SC Contractor shall prepare and provide a SUM for each major configurable element of software provided for use at the ground operations location. SUMs for SC software are included in the SVH. The SUM should provide information for SC Contractor and OSEM personnel to integrate, troubleshoot, and operate software configuration items along with the main operations architecture.
Timing of Flight Operations Support Documents
The preliminary version of the ORS should be delivered to the Government at least thirty days prior to the Preliminary Design Review (PDR) for review and feedback. The preliminary versions of the SVH and Operations Manual, along with the final version of the ORS, should be delivered to the Government at least six months prior to Initial Launch Capability (ILC) but not later than thirty days prior to the Critical Design Review (CDR). The preliminary version of the SUMs should be submitted to the Government approximately six months prior to delivery of ground operations hardware and software. The final version of the SUM shall be delivered to the Government along with the ground operations training. All documents are to be configuration managed by the SC Contractor. The final versions of the SVH and Operations Manual shall be delivered to the Government two months prior to ILC.
The SC Contractor shall work with the LV contractor to define procedures and associated contingencies for integrating the space vehicle into the Launch Vehicle (LV) and preparing the Space Vehicle System (SVS) for launch. Working with the LV contractor includes support of launch vehicle working groups, readiness reviews, and rehearsals.
The SC Contractor shall list all documents generated in support of the program and provide Government access to them. This list shall include an indentured drawing tree or similar drawing index. One example of effective access to documentation is through use of an FTP site, where program office personnel can download current versions of documents whenever necessary.
The SC Contractor shall outline all efforts the SC Contractor plans to take in response to a GIDEP alert which applies to the program.
The SC Contractor shall submit a plan describing the steps the SC Contractor shall take to protect sensitive and critical information. The SC Contractor shall protect all aspects of the mission related to equipment defined on the Militarily Critical Technologies List (MCTL).
The SC Contractor shall provide technical support to the program for resolution of anomalous situations through the period of performance.
The SC Contractor shall conduct the design reviews listed in the following subparagraphs at the appropriate stages of spacecraft development. Design reviews are formal gatherings of Government and SC Contractor personnel to review the design and provide comments. Closure of action items requires Government approval. The SC Contractor shall provide the Government with design review documents containing pertinent design and test information, mission parameters, LV considerations, risk assessments, and a detailed reliability assessment at least 10 work days prior to the design review date (see 2.10). Design reviews should correspond to significant steps in the mission processes.
System Requirements Review/System Concept Review
A discussion of requirements, to include an updated Requirements Matrix with all requirements listed, a method proposed for meeting those requirements, capability of concept to meet requirements, and verification and product assurance plans for each requirement.
An overview of the mission concept, to include preliminary SC and ground station design, preliminary integration & test plans, a detailed schedule, presentation of metrics (see 2.10) and presentation of draft interface documents (see 2.2). Concept must have significant detail analysis and be sufficiently conceived in design to be credible to the Government.
A detailed presentation of the mission, including final SC and ground station design, requirements verification matrix, software review, finalized I&T plans, updated cost and schedule performance, updated metrics, and presentation of final interface documents.
Demonstration that the SC is ready for experiment delivery. A synopsis of build/assembly of the SC. Demonstrate ICD compliance. Present final, detailed I&T procedures and updated cost/schedule/metrics.
Review of system test data. Demonstration that the SV is ready for delivery to the launch site, personnel are ready to support LV I&T, and launch site procedures will not damage the SV.
Demonstrates that the SV is ready for launch. Review anomalies and deviations.
SC Contractor shall notify the Government at least one week in advance of all qualification and acceptance testing. The SC Contractor shall provide static and dynamic structures models, thermal, mass properties, coupled loads, ADACS stability, power, EMI/EMC, communications links, and reliability analyses for review. Test documents, as requested by the Government, shall be delivered at least 10 days prior to test. All system level acceptance tests will be witnessed by the Government. Test results shall be delivered upon request.
Drawings shall include electrical schematics, wiring drawings and lists, mechanical and electrical layouts, materials list, approved parts list, and coatings. The SC Contractor shall make these available to the Government in a contractor central repository (see 2.5) and be delivered to the Government upon request.
If exercised under the appropriate CLIN, the following become requirements.
The propulsion subsystem shall be capable of transferring the SVS from a 325 nmi circular parking orbit to the 450 nmi operational orbit.
Telemetry, Tracking, and Commanding (TT&C) Subsystem
The spacecraft communications frequency and equipment shall be compatible with the Air Force Satellite Control Network (AFSCN).
The SC Contractor shall provide manpower support for anomaly resolution.
The SC Contractor shall provide a conditioned storage location for the SV system. The SC Contractor shall perform all tasks necessary to prepare the SV for storage, perform state-of-health checks periodically during storage, remove the SV from storage, and perform pre-shipment health checks and required maintenance after removal from storage.
|
NEWSLETTER
|
| Join the GlobalSecurity.org mailing list |
|
|
|
