Orbital Minotaur I - Manual (Page 64)

Minotaur I User’s Guide Section 6.0 – Mission Integration
6.4.1.5. Payload Thermal Model for Integrated Thermal Analysis
An integrated thermal analysis can be performed for any payload as a non-standard service. A payload
thermal model will be required from the payload organization for use in Orbital’s integrated thermal
analysis if it is required. The analysis is conducted for three mission phases:
a. Prelaunch ground operations
b. Ascent from lift-off until fairing jettison
c. Fairing jettison through payload deployment
The preferred thermal model format is Thermal Desktop, although FEMAP and SINDA/G can also be
provided. There is no limit on model size; however, larger models may increase the turn-around time.
6.4.1.6. Payload Drawings
Orbital prefers electronic versions of payload configuration drawings to be used in the mission specific
interface control drawing, if possible. Orbital will work with the customer to define the content and desired
format for the drawings.
6.4.1.7. Program Requirements Document (PRD) Mission Specific Annex Inputs
In order to obtain range support, a PRD must be prepared. This document describes requirements
needed to generally support the Minotaur launch vehicle. For each launch, an annex is submitted to
specify the range support needed to meet the mission’s requirements. This annex includes all payload
requirements as well as any additional Minotaur I requirements that may arise to support a particular
mission. The customer completes all appropriate PRD forms for submittal to Orbital.
6.4.1.7.1. Launch Operations Requirements (OR) Inputs
To obtain range support for the launch operation and associated rehearsals, an OR must be prepared.
The customer must provide all payload pre-launch and launch day requirements for incorporation into the
mission OR.
6.4.1.8. Payload Launch Site Integration Procedures
For each mission, Orbital requires detailed spacecraft requirements for integrated launch vehicle and
payload integration activities. With these requirements, Orbital will produce the integrated procedures for
all launch site activities. In addition, all payload procedures that are performed near the LV (either at the
integration facility or at the launch site or both) must be presented to Orbital for review prior to first use.
6.4.1.9. ICD Verification Documentation
Orbital conducts a rigorous verification program to ensure all requirements on both sides of the launch
vehicle-to-payload interface have been successfully fulfilled. As part of the ICD, Orbital includes a
verification matrix that indicates how each ICD requirement will be verified (e.g., test, analysis,
demonstration, etc.). As part of the verification process, Orbital will provide the customer with a matrix
containing all interface requirements that are the responsibility of the payload to meet. The matrix clearly
identifies the documentation to be provided as proof of verification. Likewise, Orbital will ensure that the
customer is provided with similar data for all interfaces that are the responsibility of launch vehicle to
verify.
6.4.2. Orbital Produced Documentation, Data, and Analyses
Mission documentation produced by Orbital is detailed in the following paragraphs.
Release 3.0 March 2014 51