Orbital Pegasus - Manual (Page 54)

Release 7.0 Apr 2010 43
Pegasus User’s Guide
conducting the launch operation. Due to the
variability in complexity of different payloads and
missions, the content, quantity, and schedule of
readiness reviews are tailored to support the
mission-unique considerations.
6.3. Mission Planning and Development
Orbital will assist the customer with mission
planning and development associated with
Pegasus launch vehicle systems. These services
include interface design and configuration control,
development of integration processes, launch and
launch vehicle related analyses, launch
documentation, facilities planning, launch
campaign planning to include range services and
special operations, and integrated schedules.
Orbital will conduct the working group meetings
described in this section, and support spacecraft
design reviews.
6.3.1. Baseline Mission Cycle
The procurement, analysis, integration, and test
activities associated with the Pegasus launch of a
payload typically occur over a 24- to 30-month
baseline mission cycle. This baseline schedule,
detailed in Figure 6-3, is not meant to be a rigid
structure, but a template for effective mission
management and payload integration. Throughout
this time, Orbital will work closely with personnel
from the customer and other organizations
involved in the launch to ensure a successful
mission. The schedule in Figure 6-3 shows a
typical 24-month mission. The baseline mission
cycle includes:
 Mission management, document exchanges,
meetings, and reviews required to coordinate
and manage the launch service;
 Mission and payload integration analysis;
 Design, review, procurement, testing and
integration of all mission-unique hardware;
and
 Range interface, safety, and launch site flight
and operations activities and reviews.
6.4. Interface Design and Configuration
Control
Orbital will develop a mission-unique payload ICD
to define the interface requirements for the
payload. The ICD documents the detailed
mechanical, electrical, and environmental
interfaces between the payload and Pegasus as
well as all payload integration specifics, including
Ground Support Equipment (GSE), interface
testing, and any unique payload requirements.
The ICD is jointly approved by the customer and
Orbital. An integrated schedule will also be
developed.
6.5. Safety
Ground and flight safety is a top priority in any
launch vehicle activity. Pegasus launch vehicle
processing and launch operations are conducted
under strict adherence to US Government safety
standards. The lead range at the integration and
launch sites are the ultimate responsibility for
overall safety. These ranges have established
requirements to conduct launch vehicle and
satellite processing and launch operations in a
safe manner for both those involved as well as the
public. Launch vehicle and payload providers
must work together with the range safety
organizations to ensure all safety requirements are
understood and implemented.
6.5.1. System Safety Requirements
In the initial phases of the mission integration
effort, regulations and instructions that apply to
spacecraft design and processing are reviewed.
Not all safety regulations will apply to a particular
mission integration activity. Tailoring the range
requirements to the mission-unique activities will
be the first step in establishing the safety plan.
Pegasus has three distinctly different mission
approaches effecting the establishment of the
safety requirements:
(1) Baseline mission: Payload integration and
launch operations are conducted at VAFB,
California.