Orbital Minotaur I - Manual (Page 63)

Minotaur I User’s Guide Section 6.0 – Mission Integration
6.4. Documentation
Integration of the payload requires detailed, complete, and timely preparation and submittal of interface
documentation. SD/SDL is the primary communication path with other U.S. Government agencies, which
include—but are not limited to—the various Ranges and their support agencies, the U.S. Department of
Transportation, U.S. State Department, and U.S. Department of Defense. The major products and
submittal times associated with these organizations are divided into two areas—those products that are
provided by the customer, and those produced by Orbital. Customer-provided documents represent the
formal communication of requirements, safety data, system descriptions, and mission operations
planning.
6.4.1. Customer-Provided Documentation
Documentation produced by the customer is detailed in the following paragraphs.
6.4.1.1. Payload Questionnaire
The Payload Questionnaire is designed to provide the initial definition of payload requirements, interface
details, launch site facilities, and preliminary safety data. Prior to the Mission Kickoff Meeting, the
customer shall provide the information requested in the Payload Questionnaire form (Appendix A).
Preliminary payload drawings, as well as any other pertinent information, should also be included with the
response. The customer’s responses to the payload questionnaire define the most current payload
requirements and interfaces and are instrumental in Orbital’s preparation of numerous documents
including the ICD, Preliminary Mission Analyses and launch range documentation. Orbital understands
that a definitive response to some questions may not be feasible prior to the Mission Kickoff Meeting as
they will be defined during the course of the mission integration process.
6.4.1.2. ICD Inputs
The LV-to-payload ICDs (mission, mechanical and electrical) detail all the mission specific requirements
agreed upon by Orbital and the customer. These key documents are used to ensure the compatibility of
all launch vehicle and payload interfaces, as well as defining all mission-specific and payload- unique
requirements. As such, the customer defines and provides to Orbital all the inputs that relate to the
payload. These inputs include those required to support flight trajectory development (e.g., orbit
requirements, payload mass properties, and payload separation requirements), mechanical and electrical
interface definition, payload unique requirements, payload operations, and ground support requirements.
6.4.1.3. Payload Mass Properties
Payload mass properties must be provided in a timely manner in order to support efficient launch vehicle
trajectory development and dynamic analyses. Preliminary mass properties should be submitted as part
of the MRD at launch vehicle authority to proceed. Updated mass properties shall be provided at
predefined intervals identified during the initial mission integration process. Typical timing of these
deliveries is included in Figure 6.2-1.
6.4.1.4. Payload Finite Element Model
A payload mathematical model is required for use in Orbital’s preliminary coupled loads analyses.
Acceptable forms include either a Craig-Bampton model valid to 120 Hz or a NASTRAN finite element
model. For the final coupled loads analysis, a test verified mathematical model is desired.
Release 3.0 March 2014 50