Orbital Pegasus - Manual (Page 50)

Release 7.0 Apr 2010 39
Pegasus User’s Guide
5.5.2. Payload Support at Launch Panel
Operator Station
Since it is not possible to accommodate payload
personnel on the carrier aircraft during flight,
Orbital will provide a dedicated operator to monitor
and control payload ASE during launch
operations. The operator, know as the Payload
LPO, will monitor critical payload data, send
commands, and adjust ASE settings per payload-
provided procedures as required at the direction of
the Launch Conductor (LC). The LC is in contact
with the Payload LPO via a RF voice link provided
by the Range. All steps performed by the Payload
LPO shall be documented in payload-provided
procedures and called out in the Launch Checklist.
The payload customer is expected to provide
training on all actions performed by the Payload
LPO during integrated testing.
6. MISSION INTEGRATION
6.1. Mission Management Structure
Successful integration of payload requirements is
important in achieving complete mission success.
Pegasus has established a mission team
approach to ensure all customer payload
requirements are met and that all launch services
are provided. A baseline of requirements and
services is documented in an initial Interface
Control Document (ICD) using a payload
questionnaire as input to the ICD. As the mission
evolves the team is responsible for documenting,
tracking, and implementing new customer
requirements and/or changes. A Configuration
Control Board (CCB) ensures the requirement
changes can be supported. Open communication
between the Pegasus program and the payload
customer is essential for ensuring complete
customer satisfaction. To facilitate the necessary
communication and interaction, the Pegasus
mission integration approach includes establishing
a mission team, frequent telecons, holding
periodic working group meetings and supporting
readiness reviews.
An organizational structure has been established
to support each Pegasus mission. This
organizational structure is used to manage
payload integration, mission preparations, and to
execute the mission. Open communication
between Orbital and the customer, emphasizing
timely transfer of data and prudent decision
making, ensures efficient launch vehicle/payload
integration operations and early identification and
effective resolution of any issues.
The Pegasus and customer roles in mission
integration are illustrated in Figure 6-1. The
Program Managers, one from the customer and
one from Orbital, execute the top level
management duties, providing overall
management of the launch services contract.
Within each organization, one person will be
identified as the Mission Manager and will serve
as the single point of contact in their respective
organization for that mission. The customer
should appoint a Payload Mission Manager within
its organization. All payload integration activities
will be coordinated and monitored by the Mission
Managers, including mission planning, launch
range coordination, and launch operations.
The Payload Mission Manager is responsible for
identifying the payload interface requirements and
relaying them to the Pegasus Mission Manager.
The Pegasus Mission Manager is responsible for
ensuring all the payload launch service
requirements are documented and met.
Supporting the Pegasus Mission Manager with the
detailed technical and operational tasks of the
mission integration process are the Pegasus
Mission Engineer, the system integration team,
and the launch site team.
6.1.1. Orbital Mission Responsibilities
As the launch service provider, Orbital’s
responsibilities fall into 5 areas: 1) Program
Management; 2) Mission Management; 3) Mission
Engineering; 4) Launch Site Operations; and 5)
Safety.