TABLE 9B- EELV COMMERCIAL MISSION MODEL PAYLOAD LAUNCH VEHICLE
REQUIREMENTS 175
EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)
PRE-EMD MODULE CALL FOR IMPROVEMENT
ANNEX 6
SYSTEM PERFORMANCE DOCUMENT
This page intentionally left blank.
TABLE OF CONTENTS
1.1 SCOPE 140
1.2 Purpose 140
1.3 Overview of EELV Program 140
1.4 Document Overview 140
1.4.1 Quantitative Requirements 140
1.4.2 Qualitative Requirements 140
1.5 Precedence 140
2. APPLICABLE DOCUMENTS 141
2.1 Compliance Documents 141
2.2 Reference Documents 141
3. REQUIREMENTS 142
3.1 System Definition 142
3.1.1 System Description 142
3.1.2 System Segments 142
3.1.2.1 Launch Vehicle Segment 142
3.1.2.2 Ground Segment 142
3.1.3 Government Furnished Equipment (GFE) 142
3.1.4 System Functions 142
3.1.4.1 Manufacturing 142
3.1.4.2 Transportation 143
3.1.4.3 Receipt and Checkout 143
3.1.4.4 Launch Vehicle Storage 143
3.1.4.5 Vehicle Element Processing 143
3.1.4.6 Integration 143
3.1.4.7 Functional Testing 143
3.1.4.8 Launch and Flight Operations 143
3.1.4.9 Recovery 143
3.1.4.10 Refurbishment 143
3.1.4.11 Subassembly Refurbishment Overhaul 144
3.1.4.12 Logistics Support 144
3.2 System Requirements 144
3.2.1 Performance 144
3.2.1.1 Performance: Mass to Orbit* 144
3.2.1.1.1 Payload Mass Growth 145
3.2.1.1.2 Performance Margin 145
3.2.1.1.3 Flight Performance Reserve 145
3.2.1.1.4 Dry Weight Growth Margins 146
3.2.1.2 Performance: Accuracy* 146
3.2.1.2.1 Orbital Parameter Accuracy 146
3.2.1.2.2 Attitude and Rate Accuracies 146
3.2.2 Mission Reliability 147
3.2.2.1 Vehicle Design Reliability* 147
3.2.2.2 Limit Load Conditions 147
3.2.2.3 Stiffness and Deflections 147
3.2.2.4 Pogo Stability 147
3.2.2.5 Human Performance/Human Engineering 148
3.2.3 Standardization 148
3.2.3.1 Launch Pads* 148
3.2.3.2 Infrastructure 148
3.2.3.3 Operations Procedures 148
3.2.3.4 Launch Vehicles 148
3.2.3.5 Payload Interfaces* 148
3.2.3.5.1 Payload Separation Requirements 149
3.2.3.6 Payload Accomodation* 149
3.2.4 Cost 149
3.2.5 Timeliness (Schedule Dependability) 149
3.2.6 Launch Rate Capabilities 150
3.2.6.1 Launch Rate (Basic)* 150
3.2.6.1.1 Resiliency (Maximum Sustainable Launch Rate) 150
3.2.6.2 Crisis Response (Unscheduled Launch) 151
3.2.6.3 Responsiveness 151
3.2.7 Design Flexibility 152
3.2.8 Launch and Flight Operations Requirments 152
3.2.8.1 Mission Ready Hold 152
3.2.8.2 Launch Recycle 152
3.2.8.3 Launch-Ready Hold 152
3.2.8.4 Next Day Readiness 152
3.2.8.5 Launch Abort Capability 152
3.2.8.6 Recovery and Disposal Requirements 152
3.2.8.6.1 Low Earth Orbit Or Suborbital Trajectories 152
3.2.8.6.2 Orbital Debris 153
3.2.9 System Diagnostics 153
3.2.9.1 Pre-Flight Diagnostics 153
3.2.9.2 In-Flight Diagnostics 153
3.2.10 System Data 153
3.2.10.1 Pre-Flight Data 153
3.2.10.2 In-Flight Data 153
3.2.11 Computer Resources 154
3.2.11.1 Hardware and Software 154
3.2.11.2 Programming Languages 154
3.2.11.3 Software Supportability 154
3.2.11.4 Computer Resource Reserves 154
3.2.11.5 Other Software Considerations 154
3.2.12 Range Interfaces 155
3.3 Integrated Logistics Support (ILS) 155
3.3.1 Training & Training Support 155
3.3.2 Standard Procedures and Technical Data 155
3.3.3 Packaging, Handling, Storage, and Transportation 155
3.3.4 Supportability 156
3.3.5 Maintainability and Maintenance Planning 156
3.3.6 Support Equipment 156
3.4 Safety, Security, Environmental and Transition Requirements 156
3.4.1 Safety Requirements 156
3.4.1.1 Genera 156
3.4.1.2 System Safety 157
3.4.1.3 Range Safety 157
3.4.1.3.1 Flight Safety 157
3.4.1.3.2 Flight Termination System 157
3.4.2 System Security 158
3.4.3 Environments 158
3.4.3.1 Natural Environments 158
3.4.3.2 Induced Environments 158
3.4.3.3 Ground Environments 158
3.4.3.3.1 Transportability 158
3.4.3.3.2 Transportation Environmental Monitoring 158
3.4.3.3.3 Thermal and Humidity* 159
3.4.3.3.4 Processing Contamination Control* 159
3.4.3.3.5 Electromagnetic Compatibility (EMC)* 159
3.4.3.3.6 EMI Safety Margin (EMISM) 159
3.4.3.3.7 Range Radiated Emissions 159
3.4.3.3.8 Lightning Protection 159
3.4.3.3.9 Grounding and Shielding 159
3.4.3.4 Environmental Constraints 159
3.4.3.4.1 Hazardous Materials Management 160
3.4.4 Transition Operations 160
3.5 Payload-Related Requirements* 160
3.5.1 Payload Interfaces and Accomodations 160
3.5.1.1 Coordinate System 160
3.5.1.2 Payload Accommodation 160
3.5.1.3 Payload Access 160
3.5.1.4 Payload Fairing Envelope 161
3.5.1.5 Payload Mass Properties 161
3.5.1.6 Payload Encapsulation 161
3.5.1.7 Payload Volume Growth 161
3.5.2 Payload Flight Environments 161
3.5.2.1 Acceleration Loads 161
3.5.2.2 Acoustic Environment 161
3.5.2.3 Shock 161
3.5.2.4 Flight Contamination Control 162
3.5.2.5 Ascent Heat Flux 162
3.5.2.6 Thermal 162
3.5.2.7 Free Molecular Heating 162
3.5.2.8 Pressure Decay Rate 162
3.5.3 Payload Substitution 162
3.5.4 Contamination & Collision Aviodance 162
4. QUALITY ASSURANCE PROVISIONS 163
4.1 Inspections and Quality Control 163
4.2 Verification Approach 163
4.2.1 Analysis 163
4.2.2 Demonstration 163
4.2.3 Test 163
4.3 Requirements Verification 163
5. PREPARATION FOR DELIVERY 165
6. ACRONYMS AND ABBREVIATIONS 166
LIST OF TABLES
TABLE
Table 1: Government Portion Reference Missions 145
Table 2: Orbital Parameter Accuracies 146
Table 3: Payload Interface 149
Table 4: Launch Rate Relationships 150
Table 5: Responsiveness Timelines 151
Table 6: Example Requirements Verification Matrix 164
TABLE 7A - EELV DoD Mission Model 169
TABLE 7A (Cont.) 170
TABLE 7B- EELV DOD MISSION MODEL PAYLOAD LAUNCH VEHICLE REQUIREMENTS 171
TABLE 8A- EELV NASA MISSION MODEL 172
TABLE 8B- EELV NASA MISSION MODEL PAYLOAD LAUNCH VEHICLE REQUIREMENTS 173
TABLE 9A- EELV COMMERCIAL MISSION MODEL 174
TABLE 9B- EELV COMMERCIAL MISSION MODEL PAYLOAD LAUNCH VEHICLE
REQUIREMENTS 175
EELV Transition Schedule 176
Table 10A - Government EELV Transition Schedule - No. of Missions 177
Table 10B - DoD EELV Transition Schedule - No. of Missions 177
Table 10C- NASA EELV Transition Schedule - No. of Missions 177
ANNEXES
ANNEXES
Annex A: National Mission Model ..................................................................................171
Annex B: Transition Schedule..........................................................................................179
Annex C: Standard Interface Specification ....................................................................182
Annex D: Classified SPD Annex............................................................... Under
separate cover
0.1 SCOPE
0.2 Purpose
This document identifies the Evolved Expendable Launch Vehicle (EELV)
system performance requirements and goals derived from the EELV
Operational Requirements Document (ORD).
The primary requirement of the EELV program is to execute the Government
portion (DoD and NASA) of the National Mission Model at lower recurring
costs than those of current expendable systems. The program shall also
maintain or improve reliability, capability, and operability.
This document, including its unclassified and classified Annexes, establishes
performance and verification requirements for the development and
deployment of the EELV system. It is intended to be the foundation for the
Contractor prepared System/Segment/Subsystem Specifications.
0.4.1 Quantitative Requirements
In sections denoted by an asterisk (*) and in subsections thereof, quantitative requirements designated as threshold values are non tradable and must be met or exceeded by the EELV system. Quantitative values stated as objectives or goals are tradable. If both a threshold and an objective/goal value are provided, the trade space is between these values.
Threshold values for all other requirements should be met unless doing so would have a significant adverse impact on program costs.
If only an objective/goal value is provided, the system must provide some
capability with respect to the subject requirement, the magnitude of that
capability being determined by trades considering performance and cost.
0.4.2 Qualitative Requirements
Where requirements are qualitatively stated, the system must provide some
capability/features with respect to the subject requirement, the specifics of
the capability/features being determined by trades considering performance
and cost.
0.5 Precedence
In the event of conflicts between the documents referenced herein and the
contents of the SPD, the requirements of this document shall be considered
the superseding requirements. The contracting officer shall be notified of any
instances of conflicting requirements.
1.
APPLICABLE DOCUMENTS
1.1
None
EELV Payload Database Document.
2. REQUIREMENTS
2.1.1 System Description
The EELV system will be used to deploy Government payloads. The EELV system
consists of the Launch Vehicle (LV) Segment and the Ground Segment. The EELV
system includes all equipment, facilities, and launch base infrastructure
necessary to launch a payload, place it in the required delivery orbit, provide
specified environments, provide EELV system maintenance, and perform any
necessary recovery/refurbishment operations. The major EELV system elements
and external interfaces shall be defined and illustrated in the Contractor
prepared system specification.
2.1.2 System Segments
2.1.2.1 Launch Vehicle Segment
The LV segment consists of the means for transporting the payload from the
launch site to the delivery orbit, through completion of the contamination and
collision avoidance maneuver (CCAM) and stage disposal. It includes, but is not
limited to, production, assembly, propulsion, guidance and control, electrical
power, tracking and telemetry, communication, ordnance, flight termination,
payload separation, structural elements, payload fairing, software, and
appropriate vehicle/ground and vehicle/payload interfaces that are necessary
to meet mission requirements. The payload and its unique Airborne Support
Equipment (ASE), though transported by the EELV, are not considered as part of
the EELV system.
2.1.2.2 Ground Segment
The ground segment consists of all existing, modified or new construction,
facilities, and the equipment, software, and utilities necessary to support the
planning (mission, flight, and launch operations), storage, integration, check-out,
processing, launch, telemetry, tracking and control through CCAM, and
recovery/refurbishment (if any) for the EELV system.
2.1.3 Government Furnished Equipment (GFE)
GFE shall be defined in the Contractor prepared system specification.
2.1.4 System Functions
The EELV system shall perform the major functions identified below.
2.1.4.1 Manufacturing
This function includes the manufacturing of all launch vehicle components,
subsystems, and subassemblies.
2.1.4.2 Transportation
This function includes activities and procedures necessary to transport launch
vehicle elements/subsystems/subassemblies from the manufacturing source to the
launch site.
2.1.4.3 Receipt and Checkout
This function includes initial receipt, unloading, and checkout of launch vehicle
elements/subsystems/subassemblies.
2.1.4.4 Launch Vehicle Storage
This function includes the capability to store launch vehicle
elements/subsystems/subassemblies prior to use in the system.
2.1.4.5 Vehicle Element Processing
This includes the activities that are required for the assembly and test of the
vehicle elements, such as the core, strap-on booster, and upper stage, from the
various subsystems and subassemblies, such as tanks, structure, propulsion
systems, and avionics. Element testing includes the activities required to verify
the functionality of EELV elements in the assembled condition.
2.1.4.6 Integration
Integration includes all the activities required to mate vehicle elements and
payload to each other and includes the necessary tests to verify satisfactory
mechanical and electrical interfaces among all elements and the launch
facility.
2.1.4.7 Functional Testing
This function includes the activities required to verify the functionality of an
EELV in the integrated condition. This function also includes the final checkout
required prior to launch of the integrated fueled vehicle and payload.
2.1.4.8 Launch and Flight Operations
This function includes all activities necessary for launching an EELV, including
flight planning, support for the ascent flight (including range safety related
functions), payload delivery, and deorbit/maneuvering of vehicle components for
disposal or recovery.
2.1.4.9 Recovery
This function includes the activities required for recovery and return of
reusable components, if any, of the EELV after mission completion.
2.1.4.10 Refurbishment
This function includes activities required to refurbish ground equipment and
facilities for reuse.
2.1.4.11 Subassembly Refurbishment Overhaul
This function includes rebuilding and repairing EELV subassemblies for reuse
after failures during prelaunch processing, or after recovery of reusable
components, if any.
2.1.4.12 Logistics Support
This function includes all activities necessary to provide a supportable design,
integrate support requirements with readiness objectives, and maintain
operational capability at minimum cost.
The spacelift system shall improve upon current systems. The following
subsections delineate the EELV requirements.
EELV shall have the ability to accurately deliver the government portion of the
NMM reference missions to required orbit(s). The mission masses and required
orbits are defined in Table 1. The complete NMM includes all DoD, intelligence,
civil and commercial expendable launch missions projected for EELV and serves
as the consolidated national forecast of spacelift requirements for the future
based on documented customer (payload) needs. SPD Annex A presents the
complete NMM including the commercial requirements.
2.2.1.1 Performance: Mass to Orbit*
The threshold requirement is to deliver the required mass to the desired orbit
(Table 1) of the government portion of the mission model
1 - DMSP w/AKM - Spacelift vehicle required only to achieve transfer orbit, DMSP is on a ballistic trajectory
2 - GPS IIF launch weight is unknown. Estimate between 2500 and 4480 lbs.
3 - SBIR LEO spacecraft will be launched 2-4 at a time.
4 - 8500 lbs to Mission A is greater than Atlas IIAS capability of 8150 lbs.
5 - Launch Site may be either east or west coast.
6 - 17000 lbs to Mission B is equivalent to Atlas IIAS capability from the west coast only.
7 - The capability to achieve higher orbits by coasting, restarting, and executing a short duration burn with
the final stage is also required.
8 - 13500 lbs to Mission C is design goal for Titan IV - SRMU - Centaur (although Centaur is structurally
limited to 12700 lbs).
9 - 41000 lbs to Mission D is greater than TIV- SRMU - NUS specification of 38800 lbs.
10 - The capability to achieve higher orbits by coasting, restarting, and executing a short duration burn with
the final stage is desirable but needs to be weighed against the added complexity and risk.
11. - Based on maximum capability of currently launch vehicle
12. - Launch Energy C3=17 km2/sec2
13. - Equivalent missions (Reference SPD Classified Annex)
14 - For the first TSX-8 mission in (FY 01) the payload launch weight (TBD) will be made compatible with the
MLV lift capability to the delivery orbit (TBD) when launched from ETR
Table 1: Government Portion Reference Missions
2.2.1.1.1 Payload Mass Growth
Growth potential is a goal for EELV. It is the degree to which the system
approach or hardware design enables an increment in performance capabilities
of the spacelift system without necessitating unplanned redesigns (of
hardware or operations) or a decrease in performance margin. EELV shall
have a preplanned Payload Mass Growth capability of at least 5% (threshold)
for the MLV, with an objective of 15%. For the HLV there is no threshold
value: the objective is to be able to accommodate a 5% Payload Mass Growth.
2.2.1.1.2 Performance Margin
Performance margin is the difference between the lift capability indicated by a
3s-assurance performance estimation technique and the usable (advertised)
lift capability (NMM Payload Mass plus Payload Mass Growth capability) of
an EELV vehicle. Performance margin provides for a robust operable system.
Performance margin will not be considered to be usable lifting capacity or
flight performance reserve, nor will it be considered Payload Mass Growth.
EELV shall have a threshold performance margin of 2%. As an objective,
EELV shall have a performance margin of 5%.
2.2.1.1.3 Flight Performance Reserve
EELV performance shall provide a 3s (99.865%) assurance of the vehicle fully
meeting mass to orbit requirements (including payload mass growth and
performance margin capabilities) while considering possible uncertainties in
EELV and environmental parameters such as propellant loading, Isp, and
atmospheric density.
2.2.1.1.4 Dry Weight Growth Margins
Appropriate launch vehicle dry weight growth margins shall be maintained
for all hardware commensurate with the maturity of the hardware and the
phase of design.
2.2.1.2 Performance: Accuracy*
2.2.1.2.1 Orbital Parameter Accuracy
The accuracy at the final orbit injection point for each payload mission is
defined by the following six variables: apogee, perigee, inclination, argument
of perigee, LAN and RAAN, these values are defined in the national mission
model and reflect the payload customer's requirements. The EELV shall have
orbital parameter accuracies within these 3 sigma values (threshold) or
better (objective).
**See Requirements is Table 2: Orbital Parameter Accuracies
2.2.1.2.2 Attitude and Rate Accuracies
During park orbit or transfer orbit coasts, the EELV shall be capable of orienting the upper
stage/payload to any desired attitude and holding attitude to within 6o (3s). Also during
park orbit or transfer orbit coasts, the EELV shall be capable of providing a
commanded roll rate in either direction of between 0.5 and 2.0 degrees per
second. (Thresholds)
Prior to separation, the EELV shall be capable of pointing the upper
stage/payload to any desired attitude and either minimizing all rotation rates
(3-axis stabilized missions) or providing a spin about the longitudinal axis (spin-stabilized missions). For 3-axis stabilized missions, attitude errors shall be no
greater than 1.4o (3s) about each axis and rotation rates shall be less than
0.2o/sec (3s) about each axis. For spin-stabilized missions, the MLV EELV shall
have the capability to provide payload spin rates of 5 + 0.5 (3s) rpm, and 55 + 11
(3s) rpm for GPS IIF only. Spin axis orientation shall be accurate to within 3o
(3s). (Thresholds)
2.2.2 Mission Reliability
Mission reliability, measured from launch commit, is the probability of
successfully placing the payload into its delivery orbit with the required
delivery accuracy and then executing a collision avoidance maneuver.
Mission reliability takes into account both vehicle design and process
reliabilities. Vehicle design reliability accounts for potential mission failure
modes 2.2.2.1 Vehicle Design Reliability*
For all missions, EELV vehicles shall have a vehicle design reliability of 0.98
2.2.2.2 Limit Load Conditions
The LV shall be designed to withstand limit loads, which include quasi-static
and static-elastic aerodynamic loads, plus the extreme expected dynamic
loads (value at 99% probability with 90% confidence) contributed by flight
dynamic pressures and buffet. The LV shall also be designed to withstand
limit loads from other conditions such as, but not limited to, transients due to
liftoff, gust, maximum acceleration, ignitions and shut-downs, separations,
thermal conditions, and any other significant events, including handling,
storage and transportation. Pressure vessels and pressurized structures
shall be designed to withstand instantaneous worst case combinations of
internal pressure and other loads.
2.2.2.3 Stiffness and Deflections
Adequate stiffness shall be provided to all structural subsystems and
attachment structures between system elements so that no contact occurs
except at attachment points. This provision shall pertain during ground
transportation and handling, launch, flight, and during separation events.
2.2.2.4 Pogo Stability
The EELV shall be designed to maintain pogo stability regardless of payload
configuration.
2.2.2.5 Human Performance/Human Engineering
Human performance considerations and human engineering approaches shall
be incorporated in the design of all EELV processes and new equipment, and in
the modification of existing equipment for EELV. Emphasis shall be placed on
designs which minimize the potential for human errors which would result in
schedule delays, mission aborts, or flight failures. Human engineering design
approaches shall also focus on facilitating rapid processing timelines and
system maintainability.
2.2.3 Standardization
The EELV system shall standardize vehicle and ground hardware and their
associated operations processes. Standard payload interfaces shall be
developed in collaboration with EELV users. EELV shall use standardized
hardware/software and processes, as well as streamlined spacelift operations
with flexibility to support a broad variety of missions. The following
paragraphs describe the elements of standardization.
2.2.3.1 Launch Pads*
Launch pads that are required to support the Government portion of the NMM
shall be able to launch all configurations of EELV to be launched from that
site (threshold). Prior to HLV IOC it is not a requirement for platforms to be
configured for the HLV.
2.2.3.2 Infrastructure
The infrastructure shall provide standardequipment and processes to support
the launch of the EELV. As a threshold, equipment and processes will be
standardized for each launch vehicle configuration. . As an objective,
equipment and processes will be standardized for all vehicles.
2.2.3.3 Operations Procedures
Operational launch procedures shall be standardized in order to establish a
team capable of launching any configuration of EELV. As a threshold, the
operational launch procedures shall be standard for each vehicle
configuration at each launch site, and as an objective, standard for all
vehicle configurations at all launch sites.
2.2.3.4 Launch Vehicles
The system shall incorporate commonality between medium and heavy lift
variants to the maximum extent practical. Launch vehicle elements for each
vehicle class shall be useable independent of the particular mission being
flown. Performance analyses and performance margins for the EELV design
shall consider unit-to-unit variability of launch vehicle elements (e.g.
engines, motors).
2.2.3.5 Payload Interfaces*
The EELV as a threshold shall have a single standard interface for each
vehicle class in the EELV family. Unique payload mounting or multiple-manifested-satellite-dispensing requirements will be satisfied with a payload-provided adapter to the standard interface or dispenser, and these items shall
be considered a part of the payload mass. As an objective, there would be only
one payload interface for all vehicles in the EELV family. Specific standard
interface requirements are contained in SPD Annex C.
2.2.3.5.1 Payload Separation Requirements
The EELV shall provide a separation enable signal to the payload-provided
separation system, and shall provide a positive separation verification to the
ground. The EELV shall also have the capability to provide a separation
activation signal to the separation system. Following separation, the launch
vehicle shall provide capability to avoid payload contamination and avoid
collision of the payload with any launch vehicle components or debris. See
SPD Annex C Paragraph 3.2.7, for specific requirements.
2.2.3.6 Payload Accomodation*
EELV shall provide standard payload accommodations, environments and
services. All government payloads requiring EELV support shall conform to
these standard accommodations, environments and services. EELV shall be
able to provide sufficient, reliable, predictable and repeatable services (fuel,
power, etc.), environments (noise, vibration, shock, cleanliness, etc.), and the
physical envelope (access, volume, diameter, length) for the payload. Unique
payload needs shall be satisfied by payload-provided Airborne Support
Equipment (ASE) and the ASE shall be considered a part of payload mass. (See
Section 3.5) Specific standard interface requirements are contained in SPD
Annex C.
2.2.4 Cost
Using current systems as a cost baseline, the total Life Cycle Cost (less the
$2B for development) and the annual fixed cost for launching the Government
portion of the NMM shall be reduced by 25% (threshold ) from those of
current launch systems. An objective is a 50% reduction in these costs.
2.2.5 Timeliness (Schedule Dependability)
The EELV shall consistently launch on time based on need and schedule.
EELV shall be robust enough to be minimally affected by outside influences
such as weather conditions, daylight restrictions and electromagnetic
radiation, or by component/equipment failures during launch processing.
Given the system is not in a stand down mode, the EELV shall provide at least a
0.80 probability of launching no more than 10 calendar days after
theaccountable launch date confirmed 90 days prior. An objective is at least a
0.90 probability of launching no more than 10 calendar days after the
accountable launch date.
2.2.6 Launch Rate Capabilities
EELV shall have launch rate capabilities and improved responsiveness to
support scheduled and unscheduled launch needs and to recover from
schedule delays caused by downing events or unscheduled launches. The total
capacity of the launch system is comprised of the Basic Launch Rate
(threshold) plus capabilities for satisfying Resiliency and Crisis Response
(objectives).
Table 4: Launch Rate Relationships
EELV shall have the capability to achieve the Basic Launch Rate as a normal
course of operations with routine maintenance to support the Government
portion of the NMM requirements. Due to uncertainties in future launch
rates, EELV must have the flexibility to efficiently operate over a range of
potential processing rates. As an infrastructure design threshold, the rates
for the medium vehicle are 11 at CCAS, and 4 at VAFB; for the heavy vehicle,
the rates are 1 at CCAS, and 2 at VAFB. However, the expected rates for the
medium vehicle are: 11 maximum, 3 minimum, with an average of 8 at CCAS, and
4 maximum, 0 minimum, with an average of 2 at VAFB. For the heavy vehicle,
the expected rates are: 1 maximum, 0 minimum, with an average of 1 at CCAS,
and 2 maximum, 0 minimum, and an average of 1 at VAFB. The maximum planned
system rate is 14 launches. The launch rates must be achievable taking into
account maintenance of the system and its infrastructure, weather delays,
launch range conflicts with other spacelift systems, and other typical launch
delays.
2.2.6.1.1 Resiliency (Maximum Sustainable Launch Rate)
Resiliency is measured as the maximum sustainable (two shift operations; three
shifts during launch countdown) launch rate with scheduled maintenance. It
facilitates the timely, efficient, and dependable execution of the national
space launch mission. EELV must be resilient enough to recover on a timely
basis from a downing event or other delays which could cause the system to
not meet the government portion of the NMM. To achieve resiliency, EELV, as
an objective, shall have the capability for 5 additional launches (2 medium and
1 heavy), East Coast 1 medium and 1 heavy, West Coast) above the Basic
Launch Rate.
2.2.6.2 Crisis Response (Unscheduled Launch)
A crisis may require an increase in launch rates above the maximum
sustainable (resilience) rate to provide on-orbit support to the warfighter.
Crisis response will allow the insertion of unscheduled payloads into the
schedule with minimal delay of previously scheduled payloads. The increased
launch rate required for crisis response and subsequent schedule recovery is
for a short duration and not sustainable. The objective is to be able to call up
and launch 3 unscheduled medium payloads (2 East and 1 West) within a 2
month period every 12 months from each site and be back on schedule within 6
months (assuming the current schedule is at the maximum sustainable launch
rate). Schedule time allocated for scheduled facility maintenance can be
postponed to accommodate an unscheduled launch or to facilitate subsequent
schedule recovery.
EELV shall support an unscheduled DoD launch within the required call-up
time. In providing this capability as well as supporting scheduled launch and
post-failure schedule recovery requirements (see 3.2.6.1 and 3.2.6.1.1), EELV
should improve over current processing timelines for: (1) assembly and
checkout of launch vehicles; (2) mechanical and electrical mating of
spacecraft with the launch vehicle; (3) checkout and maintenance of the
launch pad and launch processing facilities; (4) checkout of the integrated
vehicle and verification of payload interfaces; (5) fueling and final checkout
of the launch vehicle at the launch pad; and (6) verification of range
interfaces. For medium vehicles the threshold call up response time for an
unscheduled launch is 45 days with an objective of 30 days; for the heavy
vehicle the threshold is 90 days and an objective of 60 days. This time interval
includes processing the vehicle, mating the launch vehicle with the payload,
and conducting launch operations. An unscheduled launch must still meet the
timeliness requirement.
Table 5: Responsiveness Timelines
2.2.7 Design Flexibility
Design Flexibility, an objective of EELV, is the degree to which the system
approach or hardware design enables an increment or decrement in spacelift
system performance capabilities without having to redesign hardware or
operations. Additionally, the EELV shall be flexible enough to accommodate
payloads that may require unique payload-provided payload adapters or ASE,
on-pad services or somewhat longer processing timelines without impacting
other scheduled launches.
reference missions (to
be used for performance and cost trades) at a cost effectiveness better than
current launch systems. (Note that Missions A,B,C,D are reference missions to
be used only for performance trades and cost estimating, and are not threshold
performance requirements) Additionally,For support missions the actual a
threshold EELV requirements areis to deliver the masses of the payloads defined
in the SPD Classified Annex to the delivery orbits specified therein. The EELV
shall have the capability to inject into geosynchronous transfer orbits on either
the first ascending or descending leg. Following payload separation, the LV
shall perform a collision and contamination avoidance maneuver.
DoD
PAYLOAD
ORBIT
CURRENT
LAUNCH
APOGEE
PERIGEE
INCLINATION
NOTES
PORTION
VEHICLE CLASS
WT(LBS)
(NM)
(NM)
(DEGREES)
AFSPC
ADV
MILSATCOM
GTO
ATLAS IIAS
8150
19300
100
27
DMSP
POLAR
TITAN II
4410
480
-1408
98.6
1
DSCS
GTO
ATLAS II
6125
19196
124
26.5
GPS IIF
SEMI SYNC
DELTA II 7925
TBD
10998
100
38.8
2
SBIRLEO
LEO
DELTA II
TBD
TBD
TBD
TBD
3
SBIRGEO
GTO
ATLAS IIAS
7800
19324
90
27
OTHER DoD
TSX
POLAR
DELTA II 7925
6000
500
500
90
14
NPOESS
POLAR
DELTA II 7925
6840
450
450
98.2
SUPPORT
MISSION A
GTO
ATLAS IIAS
8500
19324
90
27
4,13
MISSION B
LEO
ATLAS IIAS
17000
100
100
63.4
5, 6, 7,13
MISSION C
GEO
TITAN IV-CENT
13500
19323
19323
0
8,13
MISSION D
POLAR
TITAN IV-NUS
41000
100
100
90
9, 10,13
NASA
AIM
GTO
DELTA II 7920
4060
19322
100
28.7
11
DISCOVERY
PLNTRY
DELTA II 7920
2000
N/A
N/A
28.5
12
EOS AM
SUN-SYNC
DELTA II 7920
11220
380
380
98.2
EOS PM
SUN-SYNC
DELTA II 7920
7000-8000
380
380
98.2
EOS CHEM
SUN-SYNC
DELTA II 7920
7900
380
380
98.2
Apogee
Perigee
Inc
ArgPer
LAN
RAAN
(nmi)
(nmi)
(deg)
(deg)
(deg)
(deg)
DSCS
70
1.5
0.1
0.4
0.5
N/A
ADV MILSAT
100
2.0
0.1
0.3
N/A
0.75
DMSP w/AKM
9
7
0.1
Variable
Variable
Variable
NPOESS
TBD
TBD
TBD
TBD
TBD
TBD
SBIRGEO
TBD
TBD
TBD
TBD
TBD
TBD
SBIRLEO
TBD
TBD
TBD
TBD
TBD
TBD
GPS IIF
210
4
0.4
TBD
N/A
0.2
MLV-N
TBD
TBD
TBD
TBD
TBD
TBD
AIM
TBD
TBD
TBD
TBD
TBD
TBD
DISCOVERY
TBD
TBD
TBD
TBD
TBD
TBD
EOS AM
TBD
TBD
TBD
TBD
TBD
TBD
EOS PM
TBD
TBD
TBD
TBD
TBD
TBD
EOS CHEM
TBD
TBD
TBD
TBD
TBD
TBD
Mission Mission
A**60**2**0.1**0.2**N/A**0.2**
Mission Mission
BB****
2**
2**
0.1**
1***
N/A** 0.1
Mission C
**
**
**
**
**
**
Mission D
**
**
**
**
**
** Reference SPD Classified Annex
flight failures that have their genesis in the hardware design of system
hardware, component integration architecture, and software,(including those
pertaining to staging events and CCAMs). (vehicle design reliability),Process
reliability includes consideration of failure modes introduced by as well as
manufacturing, infrastructure, assembly, reliability and ground processing,
and system integrating activities (including payload mating activities
performed by EELV). of the launch vehicle (process reliability). For all MLV
missions, EELV shall have a mission reliability of 0.975 at 50% confidence level
(threshold) or better (objective). ,at 50% confidence level. For an HLV flights
to GEO and LEO Polar, EELV shall have a mission reliability of 0.97 at 50%
confidence level (threshold), with an objective of better than 0.975, at 50%
confidence level.
at 50% confidence level (threshold) or better (objective)., at 50% confidence
level.
2.2.8 Launch and Flight Operations Requirments
Once the launch system is at the 24 hours until launch point in its countdown,
it shall be able to hold at that point for 10 days and still be able to launch
within 24 hours.
2.2.8.2 Launch Recycle
At any time up to its last recycle time (approximately T-9 seconds) before
launch, EELV shall be capable of repeatedly recycling within 5 minutes
(threshold) to the standard last hold point (as close to T=0 as practical ) in
the launch countdown for immediate re-entry into the launch procedure. An
objective is to accomplish this recycle as close to instantly as possible.
2.2.8.3 Launch-Ready Hold
The EELV shall be capable of maintaining a launch-ready (fueled vehicle)
hold status necessary to support any given payload launch window
requirement, and be capable of re-entering the launch sequence with minimal
delay. The system shall be capable of holding at the standard last hold point
for at least 2 hours (threshold) with an objective of 4 hours following a
launch recycle.
2.2.8.4 Next Day Readiness
EELV shall be capable of launching within the prescribed launch window on
the next calendar day following a fueled vehicle hold and launch scrub
occurring at or before its last recycle point. As a threshold the EELV system
shall be able to perform the next day readiness for 2 successive days with an
objective of 10 successive days.
2.2.8.5 Launch Abort Capability
Anytime prior to launch commit, the EELV system shall be capable of
performing a safe abort in a manner that protects and provides for the intact
recovery of the payload and launch system.
2.2.8.6 Recovery and Disposal Requirements
The system shall provide for safe disposal (including trajectory and debris
dispersions) or recovery of all the spacelift system vehicle components and
all non-deployed payload equipmen
. 2.2.8.6.1 Low Earth Orbit Or Suborbital Trajectories
Based on existing mandates, disposal or recovery from low earth orbit or
suborbital trajectories shall be in accordance with international
agreements.
EELV shall comply with National, DoD and USSPACECOM orbital debris
minimization policies to minimize residual orbital debris after launch. The LV
stages which are orbital shall be safely deorbited whenever practical. If not
deorbited, then the following shall be met:
a. Stages and other components left in orbit or allowed to decay
naturally must initially be placed in a disposal orbit such that the
probability of their collision with other objects is substantially
reduced. Specifically, the collision probability shall be at least a
factor of 100 lower than if the LV stage/component remained in the
payloadÕs delivery/mission orbit.
b. Stages and/or components shall be designed to minimize their break-up characteristics due to explosions, hypervelocity collisions, and
the effects of space environment. Where practical, EELV shall
incorporate space debris minimization features. Pressurized
components shall be vented and otherwise designed to minimize the
likelihood of explosion.
2.2.9 System Diagnostics
The EELV System (including all vehicles) shall have an integrated health
monitoring system. The purpose of this system is to measure and report how
well the EELV System performs relative to intended design parameters within
all mission phases. This capability will allow the user to monitor, evaluate,
fault isolate, and record the EELV system performance.
2.2.9.1 Pre-Flight Diagnostics
The system shall include built in tests, integrated vehicle system
2.2.9.2 In-Flight Diagnostics
Use of in-flight vehicle system health monitoring, fault detection, fault
isolation and anomaly resolution for vehicle system components should be
used where appropriate to achieve the mission reliability requirements.
2.2.10 System Data
2.2.10.1 Pre-Flight Data
Ground segment equipment shall provide information to support the launch
decision.
2.2.10.2 In-Flight Data
The LV shall be capable of providing real time telemetry data from launch
through the completion of CCAM and disposal operations. The flight vehicle
shall telemeter key data (compatible with range equipment) to: support range
safety needs; assess system and subsystem performance; assess payload
environment; determine the flight trajectory and delivery accuracy; verify
that the vehicle is operating within its design, qualification and acceptance
limits; and provide a basis for identification of causes for both flight and
vehicle- induced payload malfunctions and failures. The EELV system shall be
able to process telemetry launch data for quick-look data review within 2
(threshold) hours (objective 30 minutes) following data receipt at an EELV
facility and process launch and flight data for the post flight data analysis
and report within 7 (threshold) working days (objective 3 working days) of
data receipt at an EELV facility.
2.2.11 Computer Resources
EELV computer resources include all computer software, firmware, and the
associated computational equipment that comprise the launch vehicle
segment, ground segment, and any software/firmware/hardware support
environments/equipment.
2.2.11.1 Hardware and Software
To reduce the cost of software development and software maintenance,
computer hardware and software for the EELV system shall be appropriately
selected from among the following options: (1) Commercial off-the-shelf
(COTS), (2) Military off-the-shelf (MOTS), (3) reusable software components,
and (4) EELV-developed software (including any modified versions of COTS
and/or reusable software components). Proprietary software used within the
EELV system shall either be COTS or have the data rights owned by the
Government.
2.2.11.2 Programming Languages
Programming language(s) shall be selected that provide a cost-effective
solution over the entire EELV system life cycle. Programming language
requirements shall be provided and addressed in the Contractor prepared
system specification.
2.2.11.3 Software Supportability
Software supportability considerations shall be incorporated into the EELV
design. The Contractor prepared system specification shall address
characteristics of the EELV software needed for ease of maintenance, as well
as characteristics of the software support environment(s) necessary for
efficient post-deployment support.
2.2.11.4 Computer Resource Reserves
Reserves for processor, primary memory, peripheral data storage (secondary
memory), and data transmission media capacity/throughput shall be provided
and shall be addressed in the Contractor prepared system specification.
2.2.11.5 Other Software Considerations
To the extent practical, the software used in the EELV system shall
provide the following capabilities within each functional processing
element: (1) measurement of computer resource utilization information,
(2) logging of system events to support anomaly resolution (including
software anomalies) and system performance verification, and (3)
restart/reinitialization of software to recover from anomalies.
The system shall interface and be compatible with current spacelift ranges
and their existing infrastructure, if they are used, including facilities and
equipment for integration, check-out, processing, Telemetry Tracking and
Commanding (TT&C) and launch operations. The system shall interface and be
compatible with future range upgrades under the Range Standardization and
Automation (RSA) program. EELV shall have sufficient signal strength and be
compatible with current ground, airborne, and space based telemetry relay
systems if they are used.
vehicle
health monitoring, and fault detection/isolation capabilities as required to
meet the EELV system requirements. This capability shall be designed to meet
the system oporability and reliability requirements. reduce operator
involvement, and with consideration of human factors.
2.2.12 Range Interfaces
2.3 Integrated Logistics Support (ILS)
An ILS program shall be established to ensure a disciplined, unified and
iterative approach to the management and technical activities necessary to:
(a) integrate support considerations into system equipment design, (b) develop
and acquire support requirements that are related consistently to readiness
objectives (launch rate, timeliness, responsiveness), to design, and to each
other, (c) and provide the support during the operational phase at minimum
cost. The ILS program shall determine the most effective support concepts
through a Logistics Support Analysis (LSA) program including the use of
standard Air Force logistics systems as one alternative.
2.3.1 Training & Training Support
Type I training, shall be provided by the Contractor to train personnel (Air
Force or equivalent Contractor) to satisfy operations and maintenance
requirements. The overall objective is to certify a government infrastructure
that is proficient in standard launch base procedures, all tasks performed by
government personnel as necessary to operate and maintain the system. All
necessary equipment (e.g. simulators, PC based training equipment) ,course
materials and logistics support for training equipment shall be provided as
necessary to enable implementation of an organic Air Force training
capability.
2.3.2 Standard Procedures and Technical Data
The EELV shall utilize standard procedures and digitized technical data in
Joint Continuous Acquisition and Life Cycle Support (JCALS) format for
maintenance, engineering data/drawings, trouble shooting, supply, processing,
flight planning, launch operations, and post processing of the system
encompassing the needs of the missions in the NMM, SPD Annex A. Technical
Manuals delivered for use by Air Force personnel must be managed using the
standard Air Force Technical Order Management System. All technical data
shall be organized similar to Air Force Technical Orders and have a
disciplined change process in place. Air Force Technical Orders- shall be
validated and maintained for major integrated system test and countdown
operations performed by government personnel. A technical publications
library shall be maintained on-site for use by contractor and government
personnel. This library shall contain all publications necessary to operate
the EELV system in a safe and efficient manner.
2.3.3 Packaging, Handling, Storage, and Transportation
Transportation of EELV system components shall be via existing or currently
being developed air, sea or ground transportation vehicles. Modification of
transportation vehicles or new transportation vehicles shall be specified only
when justified economically. The packaging methods shall ensure system,
equipment, and support items are properly preserved, packaged, handled, and
transported for short and long storage or environmental considerations.
2.3.4 Supportability
The EELV system shall be supportable via a logistics system configured to
enable flexible and efficient conduct of launch operations commensurate with
the Government missions in the National Mission Model. The EELV logistics
system shall also be capable of supporting changes in planned mission
operations, and facilitating recovery from delay situations caused by
equipment failure during launch processing. Supply support shall incorporate
a sparing approach optimized to reduce standing stock levels and to encourage
flexible and responsive sparing. Contractor data systems for supply and
support maintenance data collection shall be interoperable with those of the
Air Force logistics systems.
2.3.5 Maintainability and Maintenance Planning
The EELV system shall be sufficiently maintainable to allow meeting launch
rate and schedule dependability requirements. Emphasis shall be placed on
rapid fault detection and isolation (Objective: 99% of the time to 3 or less
LRU's'; 95% to 2 or less LRU's and, 90% to 1 LRU), ease of access for
maintenance, and ease of removal of faulty components for repair or
replacement. Schedules for maintenance of system equipment and facilities
shall be sufficiently short and flexible to have minimal, if any, impacts on
system readiness. The EELV Contractor may use the Air Force Core
Automated Maintenance System (CAMS) or a designated follow-on which is
available at no cost. Air Force personnel shall be provided electronic access
to Contractor maintenance management information systems if CAMS is not
used. As a minimum, the maintenance planning database shall include failure
data, launch vehicle processing schedules, and all other data that impact the
ability of the system to meet launch schedules and windows in a timely
manner.
2.3.6 Support Equipment
The EELV system shall utilize existing support equipment to the greatest
extent possible, including possible modifications to existing equipment. To the
extent that it complies with spacelift system requirements, maximum use of
non-developmental items is required. Equipment owned, operated and/or
maintained by the government must be supported using the standard Air Force
logistics infrastructure.
2.4 Safety, Security, Environmental and Transition Requirements
2.4.1.1 Genera
Wing safety, contractor safety, and maintenance controllers will help
ensure EELV contractor compliance with Range Safety requirements and
support mishap investigations (in accordance with AFI 91-204, Safety
Investigations and Reports) as necessary. HQ AFSPC will provide the ranges
with policy and safety compliance as necessary.
2.4.1.2 System Safety
The EELV program shall include a system safety program in accordance with
the tailored EWR 127-1. System safety program objectives are to minimize loss
of personnel and resources due to mishaps and preserve the combat capability
of the Air Force by ensuring system safety is applied throughout a system life
cycle. Hazard analyses shall be performed on the overall system design to
identify critical components, and safety critical issues will be addressed and
documented during system design and deployment. The identification and
analyses of system safety requirements are an integral part of an effective
man-machine design for aerospace systems. Programs shall comply with the
system safety requirements of the tailored EWR 127-1 including range
approval of all hazardous procedures. Users must obtain wing issued Missile
System Safety Approvals, Flight Termination System Approvals, Facility
System Safety Approvals, and Ground Operation Approvals. Refer to the
tailored EWR 127-1 for detailed compliance requirements.
2.4.1.3 Range Safety
The objective of the Range Safety program is to ensure that the general
public, launch area personnel, foreign land masses, and launch area
resources are provided an acceptable level of safety and that all aspects
of prelaunch and launch operations adhere to public laws and national
needs. The mutual goal of the Ranges and the EELV program shall be to
launch vehicles and payloads safely and effectively with commitment to
public safety. EWR 127-1 shall be tailored for the EELV program. The
EELV system shall comply with the tailored EWR 127-1 or obtain
appropriate deviations or waivers. EWR 127-1 specifies that new programs
and major program modifications require phased safety reviews at critical
milestones such as at concept, preliminary, and critical design reviews, and
120 days prior to shipment to either range.
2.4.1.3.1 Flight Safety
The EELV system shall provide sufficient vehicle, trajectory and
performance data to permit the development of flight safety criteria,
selection and scheduling of tracking and telemetry antenna assets,
accurate collision avoidance runs, radio frequency interface analysis, link
margin analyses and other range safety analyses. Users must obtain
preliminary and final Flight Plan Approvals and provide all necessary flight
support data, as specified in the tailored EWR 127-1, prior to approvals.
The flight safety objectives are to conduct missions from the safest
approach, methodology or position acceptable and to minimize risk to the
greatest extent possible. EELV shall be capable of providing real time
tracking and telemetry data during launch that provides safety personnel
with the ability to determine vehicle performance, detect a violation of
flight criteria, and terminate the flight throughout all launch phases. The
data shall include performance, guidance, and Flight Termination System
(FTS) data as required by EWR 127-1, paragraph 2.5.5.
2.4.1.3.2 Flight Termination System
All launch vehicles shall have a flight termination system that has an
overall system reliability threshold of 0.999 (at a 95% confidence level).
This reliability requirement shall be satisfied by using the design (including
block redundancy) and testing guidelines in the range regulation.
2.4.2 System Security
EELV shall provide secure and survivable systems as necessary to support
mission requirements. Program protection will be applied throughout the
system's lifecycle to maintain technical superiority, system integrity and
availability. Safeguarding the integrity of the system acquisition,
deployment and operation is necessary to maintain the high level of
effectiveness of EELV operations. Physical security countermeasures
shall protect against compromise or loss of information and resources due
to unauthorized access to facilities, equipment, payloads, data, and shall
protect operations against espionage, sabotage, damage, tampering, and
theft. Data and communication links carrying classified information, up to
and including Top Secret/Sensitive Compartmentalized Information, shall be
protected according to NSA and Air Force COMSEC requirements from
disclosure, intrusion, and other forms of information warfare. Data and
communication links carrying sensitive unclassified and critical information
shall be protected according to its sensitivity or criticality level from
disclosure, intrusion, and other forms of information warfare.
The spacelift system in general must be tolerant of the environment during
pre-launch and launch operations. It is not intended; however, that the
system be processed/launched during periods outside normal indigenous
environmental conditions. Ground operations (pre-launch) must take into
account the typical weather conditions that exist at either coast, e.g.
thunderstorms and lightning. Ground operations shall also be tolerant of
earthquakes which are prevalent at the western launch site. Launch
operations must likewise consider lightning and winds (ground and aloft).
The launch vehicle shall incorporate robust tolerances to withstand
environmental and structural extremes associated with: transport from
production facilities to storage or the launch base, processing, launch, and
flight in atmospheric and exoatmospheric regimes. These environmental and
structural extremes include handling loads, wind loading while on-stand,
flight loads, temperature, humidity, acoustics, vibrations and in-flight RF
environments.
2.4.3.3 Ground Environments
2.4.3.3.1 Transportability
System hardware shall be designed to withstand normal handling and
transportation environments without any detrimental effects to the
systems.
2.4.3.3.2 Transportation Environmental Monitoring
Critical hardware items shall be monitored and data recorded during
shipping to provide complete time histories of the most severe environments,
as well as summaries thereof.
2.4.3.3.3 Thermal and Humidity*
The EELV shall have the capability to control the thermal and humidity
environments inside the fairing throughout all phases of launch processing.
See SPD Annex C, paragraph 3.3.3 for specific requirements. The Payload
Database Document may be used for reference information regarding
current payloads.
2.4.3.3.4 Processing Contamination Control*
The airborne particle concentrations shall not exceed Class 100K in
locations occupied by the payload during payload integration. See SPD
Annex C for specific other specific requirements.
2.4.3.3.5 Electromagnetic Compatibility (EMC)*
The LV shall not emit electromagnetic interference (EMI) that harms or
interferes with the payload or any ground equipment, nor shall the LV be
susceptible to EMI. See SPD Annex C, paragraph 3.2.3 for specific
requirements.
2.4.3.3.6 EMI Safety Margin (EMISM)
The payload and LV integrated system shall be designed to provide EMC with
a safety margin for DC (no-fire threshold) and positive safety margin for RF
for ordnance circuits and EMISM for all non-ordnance circuits. Payload
and LV designs shall incorporate the necessary provisions to assure intra-system EMISM of the payload and LV individual segments and inter-system
EMC of each segment with its associated AGE and EAGE. See SPD Annex C,
paragraph 3.2.3.6 for specific requirements. The Payload Database
Document may be used for reference information regarding current
payloads.
2.4.3.3.7 Range Radiated Emissions
The flight configured LV/payload shall be compatible with the launch site
RF requirements. The LV and payload shall each be responsible for the
individual system compatibility with the worst case theoretical value.
2.4.3.3.8 Lightning Protection
Lightning protection shall be provided for the LV, payload, and all
hardware, structures, and personnel. Electrical circuits shall be designed
to minimize damage due to lightning strikes.
2.4.3.3.9 Grounding and Shielding
EELV system components shall be grounded as necessary to protect
against inadvertent electrical charges or static charge buildup.
Electrically sensitive portions of the system shall be shielded from non-essential electrical environments.
2.4.3.4
The EELV system shall operate within applicable laws and regulations
without waivers and minimize the use and generation of hazardous materials
at all sites to include launch and manufacturing sites (contractor and
subcontractor).
2.4.3.4.1 Hazardous Materials Management
The EELV system shall not use materials designated as Class I Ozone-Depleting Substances (ODSs) in manufacturing, maintenance, launch
processing or system disposal. The design shall identify, justify, minimize
and/or eliminate requirements for the usage of Class II ODSs, and EPCRA
Section 313 chemicals.
2.4.4 Transition Operations
The EELV system shall be capable of being deployed and operated with the
absolute minimum disruption to current launch base operations and
facilities.
2.5
The EELV goal is to move rapidly toward standard payload interfaces and
services to reduce system complexity and enhance responsive spacelift
capability. However, spacelift systems should be flexible enough to
accommodate payloads that may require unique payload adapters or ASE,
and longer payload processing timelines without adversely impacting the
overall responsiveness of the spacelift system. Payload programs will be
responsible for delivering a flight-ready payload to the launch base. The
payload will comply with EELV standard interfaces and streamlined
processing. Payload processing (except as noted above) will minimize
constraints placed on spacelift mission operations. The payload provider
will be responsible for ensuring payload compatibility with the spacelift
system.
2.5.1 Payload Interfaces and Accomodations
2.5.1.1 Coordinate System
The standard interface coordinate system is defined in SPD Annex C
(Standard Interface Specification), paragraph 3.1.1.
2.5.1.2 Payload Accommodation
The EELV shall accommodate the Government payloads in the NMM and
shall provide standard interfaces and services (such as mechanical
interfaces, power, environmental conditioning, etc.). The Payload Database
Document may be used for reference information regarding current
payloads. Current or new payloads having unique interface/services needs
(such as special power conditioning) shall provide appropriate payload
adapters/ASE/services. The weight of the adapters/ASE shall be
considered payload weight. EELV shall facilitate direct communication
between the payload and its ground station. EELV will not provide any
communication hardware unique to the payload. 2.5.1.3 Payload Access
Access shall be provided for safe-and-arm initiation, ordnance installation,
propellant fill and drain, and access to umbilical and electrical
connectors. The Payload Database Document may be used for reference
information regarding current payloads.
2.5.1.4 Payload Fairing Envelope
The envelope shall be sufficient to provide a minimum of one inch clearance
(threshold) between the payload and the fairing under worst case dynamic
conditions. The Payload Database Document may be used for reference
information regarding current payloads. See SPD Classified Annex for
specific payload information. See SPD Annex C, paragraph 3.1.3 for specific
requirements.
2.5.1.5 Payload Mass Properties
The LV shall be capable of accommodating the mass properties of the
Government payloads in the National Mission Model plus any planned
Payload Mass Growth capability. The Payload Database Document may be
used for reference information regarding current payloads.
2.5.1.6
If adopted, all payload encapsulation shall be performed off-pad for
maximum efficiency in processing and launch operations. During the
transition to EELV systems, encapsulation may be conducted on the launch
pad.
2.5.1.7 Payload Volume Growth
EELV shall have a planned Payload Volume Growth of at least a 5% (threshold) at constant diameter, with an objective of 10% at constant diameter.
2.5.2 Payload Flight Environments
2.5.2.1 Acceleration Loads
The maximum thrust-axis and lateral-axes accelerations of the LV shall not
exceed those acceptable by the Government payloads in the National
Mission Model. See SPD Annex C, paragraph 3.6, for specific requirements.
2.5.2.2 Acoustic Environment
The free-field maximum expected sound pressure levels (value at 95%
probability with 50% confidence) in decibels for the empty fairing shall not
exceed the values acceptable by the Government payloads in the NMM.
Provisions shall be made for application of sound attenuation measures for
individual payload programs which may seek to reduce exposure to acoustic
noise. See SPD Annex C, paragraph 3.8 for specific requirements.
2.5.2.3 Shock
The maximum expected shock spectrum at the payload interface (assuming
the separation system is provided by the payload) in g's (value at 95%
probability with 50% confidence) for a resonant amplification factor (Q) of
10 shall not exceed in any direction the values acceptable by the
Government payloads in the NMM. See SPD Annex C, paragraph 3.9 for
specific requirements.
2.5.2.4 Flight Contamination Control
After lift-off, the contamination level for all surfaces inside the fairing
shall be no greater than those acceptable by the payload. The Payload
Database Document may be used for reference information regarding
current payloads.
2.5.2.5 Ascent Heat Flux
The heat flux to the payload from all LV sources (which may include, but are
not limited to, heat flux from the inner fairing and stage plume) shall be
compatible with the payload during all phases of ascent. The Payload
Database Document may be used for reference information regarding
current payloads.
2.5.2.6 Thermal
The EELV shall have the capability to control the thermal environments
within the payload fairing during appropriate phases of flight. See SPD
Annex C, paragraph 3.4.2 for specific requirements. The Payload Database
Document may be used for reference information regarding current
payloads.
2.5.2.7 Free Molecular Heating
The maximum free molecular heating shall be compatible with the payload
during all phases of flight. See SPD Annex C, paragraph 3.4.4 for specific
requirements. The Payload Database Document may be used for reference
information regarding current payloads.
2.5.2.8 Pressure Decay Rate
The pressure decay rate shall be compatible with the payload during all
phases of the flight. The Payload Database Document may be used for
reference information regarding current payloads.
2.5.3 Payload Substitution
To maximize operational flexibility and reduce costs, prior to payload mate
the EELV shall allow payload substitution with another payload already
pre-integrated ( integration planning and analysis completed) and prepared
(payload processing completed) for launch on the same size LV. The EELV
system shall facilitate rapid payload substitution so that schedule launch
date delays are minimized or avoided. Payload substitution should not drive
additional launch processing other than activities normally required for
payload mating.
2.5.4 Contamination & Collision Aviodance
Debris from all LV sources, including but not limited to Reaction Control
System operation and LV staging events, shall not impinge on any surface of
the payload with sufficient kinetic energy to penetrate, nick, scratch,
indent, fracture, or otherwise harm the payload. The CCAM shall be
designed to preclude recontact with the payload and to minimize payload
exposure to LV contaminants.
3. QUALITY ASSURANCE PROVISIONS
3.1 Inspections and Quality Control
The Contractor shall apply parts, materials, and process controls during
production of all items to ensure that a reliable system will be flown.
Complete records indicating relevant test and inspection data and
nonconformance reports, if any, shall be maintained for the EELV system
items and shall be made available for review during the service life of the
system.
3.2.1 Analysis
Analysis may be used for determination of qualitative and quantitative
properties and performance of an item by study calculations and modeling.
Similarity analysis may be used in lieu of tests when it can be shown that an
item is similar or identical in design to another item that has been certified
previously to equivalent or more stringent criteria.
3.2.2 Demonstration
Demonstration may be used for determination of qualitative and quantitative
properties and performance of an item and is accomplished by example.
Verification of an item by this method would be by using it for its designed
purpose and may require no special test for final proof of performance.
3.2.3 Test
Test may be used for the determination of qualitative and quantitative
properties and performance of an item by technical means, which requires the
use of external resources such as volt meters, recorders, and any test
equipment necessary for measuring performance. Newly designed items shall
be qualified for the EELV system. Items that incorporate significant changes
in design, manufacturing processing, environmental levels, or performance
requirements shall be requalified for the EELV system.
The mechanism for maintaining traceability of the requirements verification
will be a Requirements Verification Matrix as shown in example Table 4. An
equivalent verification matrix accounting for all requirements shall be
incorporated into the Contractor prepared system specification.
Table 6: Example Requirements Verification Matrix
Verification Method: I=Inspection, A=Analysis, D=Demonstration, T=Test, N/A=Not
Applicable
Verification Phase: E=Engineering, Q=Qualification, A=Acceptance, S=Storage,
L=Service Life, P=Prelaunch
Verification Number
SPD Paragraph
Reference
Responsible
Contractor
Verification Method
Verification Phase
Verification Result
Comment
3.2.1.1 Lift
Capability
3.2.1.2.1 Transition
3.2.1.2.2 Launch
Rates
...
4. PREPARATION FOR DELIVERY
EELV items shall be packaged, labeled and delivered commensurate with
regulatory requirements and the requirements of the selected transportation
mode(s) and involved facilities or bases. The EELV system and components
shall be delivered to the launch operator certified flight worthy. As an
objective, the hardware shall be delivered to the launch operator with no
pending actions or waivers.
5. ACRONYMS AND ABBREVIATIONS
AFOSH Air Force Occupational Safety and Health
AFSPC Air Force Space Command
AGE Aerospace Ground Equipment
ASE Airborne Support Equipment
CCAM Collision, Contamination Avoidance Maneuver
CCAS Cape Canaveral Air Force Station
COMSEC Communications Security
COTS Commercial Off-The-Shelf
DC Direct Current
DoD Department of Defense
EAGE Electrical Aerospace Ground Equipment
EELV Evolved Expendable Launch Vehicle
EMC Electromagnetic Compatibility
EMI Electromagnetic Interference
EMISM EMI Safety Margin
EPA Environmental Protection Agency
EWR Eastern and Western Range Regulation
GEO Geosynchronous Earth Orbit
GFE Government Furnished Equipment
GTO Geosynchronous Transfer Orbit
HLV Heavy Lift Variant
HQ Headquarters
ILS Integrated Logistics Support
IOC Initial Operational Capability
LAN Longitude of Ascending Node
LEO Low Earth Orbit
LRU Line Replaceable Unit
LSA Logistics Support Analysis
LV Launch Vehicle
MLV Medium Lift Variant
MOTS Military Off-The-Shelf
N/A Not Applicable
NMI Nautical Miles
NMM National Mission Model
NSA National Security Agency
ODS Ozone Depleting Substance
ORD Operational Requirements Document
OSHA Occupational Safety and Health Administration
RAAN Right Ascension of Ascending Node
RF Radio Frequency
RPM Revolutions Per Minute
RSA Range Standardization and Automation
SER Safety Equivalency Report
SPD System Performance Document
T Launch Countdown Time
TBD To Be Determined
TT&C Tracking, Telemetry & Commanding
VAFB Vandenberg Air Force Base
SPD ANNEX A
TABLE 7A - EELV DoD Mission Model
The EELV DOD MM reflects the DOD requirements of the AFSPC National Executable Mission Model (04 Jan. 1996).
Included in the mission model are the requirements for Delta class, Titan II, Atlas I/II, and Titan IV class vehicles. Excluded from the Mission Model are
requirements for small launch vehicles, Medium Light and Medium Light II launch vehicles, launch vehicles that are already on contract and heavy lift vehicle
requirements prior to FY05. (V) designates west coast launches
* - Realizing there is a conflict between the NMM and the Government's Call for Improvement (CFI) instructions, plan for first operational
flight of GPS IIF for 1Q FY02. The Government will resolve this issue in the Pre-EMD Module.
TABLE 7A (Cont.)
FY01
FY02
FY03
FY04
FY05
FY06
FY07
FY08
FY09
FY10
GPS IIRF/GAP
GPS IIRF/GAP
GPS IIRF/GAP
DMSP/LON (V)
GPS IIF/LON
DMSP/LON (V)
DMSP/LON (V)
GPS IIF/LON
GPS IIF/LON
GPS IIF/LON
TSX-8
DMSP/LON (V)
GPS IIRF/GAP
GPS IIF/LON
GPS IIF/LON
GPS IIF/LON
GPS IIF/LON
GPS IIF/LON
GPS IIF/LON
GPS IIF/LON
DSCS III
GPS IIRF/GAP
GPS IIRF/GAP
TSX-11(V)
GPS IIF/LON
GPS IIF/LON
NPOESS (V)
NPOESS (V)
GPS IIF/LON
SBIRS GEO
DSCS III
NPOESS (V)
ADV MILSATCOM
GPS IIF/LON
GPS IIF/LON
SBIRS LEO
SBIRS GEO
SBIRS GEO
MISSION B(V)
SBIRS GEO
SBIRS GEO
SBIRS GEO
NPOESS (V)
SBIRS LEO
SBIRS LEO
ADV MILSATCOM
TSX-N (V)
MISSION A
SBIRS LEO
SBIRS LEO
ADV MILSATCOM
MISSION A
MISSION A
MISSION A
SBIRS LEO
SBIRS LEO
ADV MILSATCOM
MISSION A
MISSION B (V)
ADV
MILSATCOM
ADV MILSATCOM
ADV MILSATCOM
MISSION B
(V)
MISSION B (V)
SBIRS GEO
ADV MILSATCOM
MISSION B (V)
SBIRS LEO
MISSION A
ADV MILSATCOM
MISSION C
SBIRS LEO
MISSION B (V)
MISSION A
MISSION D (V)
East Coast
2
3
5
5
4
8
10
8
5
8
West Coast
0
2
0
4
1
3
1
3
1
2
Total DoD
2*
5
5
9
5
11
11
11
6
10
FY11
FY12
FY13
FY14
FY15
FY16
FY17
FY18
FY19
FY20
GPS IIF
ADV
MILSATCOM
ADV
MILSATCOM
ADV
MILSATCOM
ADV
MILSATCOM
ADV MILSATCOM
ADV
MILSATCOM
ADV MILSATCOM
GPS IIF
GPS IIF
GPS IIF
GPS IIF
ADV
MILSATCOM
ADV
MILSATCOM
ADV
MILSATCOM
ADV MILSATCOM
ADV
MILSATCOM
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
GPS IIF
SBIR GEO
NPOESS (V)
MISSION A
SBIRS GEO
GPS IIF
GPS IIF
SBIRS GEO
GPS IIF
GPS IIF
SBIRS GEO
MISSION A
SBIRS GEO
MISSION C
NPOESS (V)
GPS IIF
SBIRS GEO
MISSION C
TSX-N (V)
SBIRS GEO
TSX-N (V)
MISSION A
SBIRS LEO
MISSION D
(V)
MISSION A
SBIR GEO
NPOESS (V)
MISSION D
(V)
NPOESS (V)
MISSION A
NPOESS (V)
MISSION D
(V)
SBIRS LEO
SBIRS LEO
MISSION A
TSX-N (V)
MISSION A
MISSION D
(V)
MISSION B (V)
MISSION A
MISSION A
MISSION D (V)
SBIRS LEO
MISSION B (V)
MISSION D
(V)
SBIRS LEO
MISSION C
MISSION B (V)
SBIRS LEO
SBIRS LEO
MISSION D (V)
SBIRS LEO
SBIRS LEO
SBIRS LEO
MISSION C
SBIRS LEO
MISSION D (V)
SBIRS LEO
SBIRS LEO
SBIRS LEO
MISSION D (V)
SBIRS LEO
SBIRS LEO
SBIRS LEO
SBIRS LEO
SBIRS LEO
Total
Average
East Coast
9
9
7
9
9
8
8
9
9
6
140
7
West Coast
1
4
1
2
2
3
0
4
2
1
38
1.9
Total DoD
10
13
8
11
11
11
8
13
11
7
178
8.9
Total Govt
194
TABLE 7B- EELV DOD/NASA MISSION MODEL PAYLOAD LAUNCH VEHICLE REQUIREMENTS
The EELV DOD/NASA MM PL Requirements are based upon mission information in the AFSPC National Executable Mission Model (04 Jan. 96) and Booster Separation Requirement responses to the Payload Requirements Questionnaire for the Evolved Expendable Launch Vehicle Program (6 March 95). For Payloads for which mission data was unavailable, the maximum capacity of the currently assigned launch vehicle was assumed.
| DoD | PAYLOAD | ORBIT | CURRENT | LAUNCH | APOGEE | PERIGEE | INCLINATION | NOTES |
| PORTION | VEHICLE CLASS | WT(LBS) | (NM) | (NM) | (DEGREES) | |||
| AFSPC | ADV MILSATCOM | GTO | ATLAS IIAS | 8150 | 19300 | 100 | 27 | |
| DMSP | POLAR | TITAN II | 4410 | 480 | -1408 | 98.6 | 1 | |
| DSCS | GTO | ATLAS II | 6125 | 19196 | 124 | 26.5 | ||
| GPS IIF | SEMI SYNC | DELTA II 7925 | TBD | 10998 | 100 | 38.8 | 2 | |
| SBIRLEO | LEO | DELTA II | TBD | TBD | TBD | TBD | 3 | |
| SBIRGEO | GTO | ATLAS IIAS | 7800 | 19324 | 90 | 27 | ||
| OTHER DoD | TSX | POLAR | DELTA II 7925 | 6000 | 500 | 500 | 90 | 14 |
| NPOESS | POLAR | DELTA II 7925 | 6840 | 450 | 450 | 98.2 | ||
| SUPPORT | MISSION A | GTO | ATLAS IIAS | 8500 | 19324 | 90 | 27 | 4,13 |
| MISSION B | LEO | ATLAS IIAS | 17000 | 100 | 100 | 63.4 | 5, 6, 7,13 | |
| MISSION C | GEO | TITAN IV-CENT | 13500 | 19323 | 19323 | 0 | 8,13 | |
| MISSION D | POLAR | TITAN IV-NUS | 41000 | 100 | 100 | 90 | 9, 10,13 | |
| NASA | AIM | GTO | DELTA II 7920 | 4060 | 19322 | 100 | 28.7 | 11 |
| DISCOVERY | PLNTRY | DELTA II 7920 | 2000 | N/A | N/A | 28.5 | 12 | |
| EOS AM | SUN-SYNC | DELTA II 7920 | 11220 | 380 | 380 | 98.2 | ||
| EOS PM | SUN-SYNC | DELTA II 7920 | 7000-8000 | 380 | 380 | 98.2 | ||
| EOS CHEM | SUN-SYNC | DELTA II 7920 | 7900 | 380 | 380 | 98.2 |
1 - DMSP w/AKM - Spacelift vehicle required only to achieve transfer orbit, DMSP is on a ballistic trajectory
2 - GPS IIF launch weight is unknown. Estimate between 2500 and 4480 lbs.
3 - SBIR LEO spacecraft will be launched 2-4 at a time.
4 - 8500 lbs to Mission A is greater than Atlas IIAS capability of 8150 lbs.
5 - Launch Site may be either east or west coast.
6 - 17000 lbs to Mission B is equivalent to Atlas IIAS capability from the west coast only.
7 - The capability to achieve higher orbits by coasting, restarting, and executing a short duration burn with the final stage is also required.
8 - 13500 lbs to Mission C is design goal for Titan IV - SRMU - Centaur (although Centaur is structurally limited to 12700 lbs).
9 - 41000 lbs to Mission D is greater than TIV- SRMU - NUS specification of 38800 lbs.
10 - The capability to achieve higher orbits by coasting, restarting, and executing a short duration burn with the final stage is desirable but needs to be weighed against the added complexity and risk.
11. - Based on maximum capability of currently launch vehicle
12. - Launch Energy C3=17 km2/sec2
13. - Equivalent missions (Reference SPD Classified Annex)
14 - For the first TSX-8 mission in (FY 01) the payload launch weight (TBD) will be made compatible with the MLV lift capability to the delivery orbit (TBD) when launched from
ETR
TABLE 8A- EELV NASA MISSION MODEL
| The NASA requirements are based upon NASA Long Range Launch Planning-Compatibility with DOD/EELV Program ( K. Poniatowski - 8 Feb. 95) and the AFSPC NMM 04 Jan. 96. |
| FY01 | FY02 | FY03 | FY04 | FY05 | FY06 | FY07 | FY08 | FY09 | FY10 |
| DISCOVERY | AIM | DISCOVERY | EOS-PM2 | DISCOVERY | EOS-CHEM2 | DISCOVERY | EOS-AM3 (V) | ||||
| SOLAR | ||||||||||
| East Coast | 0 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 1 | 0 |
| West Coast | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 |
| Total | 0 | 0 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 |
| FY11 | FY12 | FY13 | FY14 | FY15 | FY16 | FY17 | FY18 | FY19 | FY20 | |
| DISCOVERY | EOS-PM 3 | DISCOVERY | EOS-CHEM 3 | DISCOVERY | DISCOVERY | DISCOVERY | ||||
| East Coast | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 1 | 0 |
| West Coast | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 |
| Total | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 0 | 1 | 0 |
TABLE 8B- EELV NASA MISSION MODEL PAYLOAD LAUNCH VEHICLE REQUIREMENTS
The EELV Mission Model Payload requirements are based upon mission information in the AFSPC National Mission Model (4 Jan. 96), the U. S. Civilian
Government Expendable Launch Vehicle Payload Compendium (NASA - April 94), and data provided by payload program offices. For payloads in which mission data
was unavailable, the maximum capability of the currently assigned launch vehicle was assumed.
* Throw Weight and Orbit data based upon the maximum capability of the currently assigned launch vehicle.
** Throw weight includes the weight of the separated space vehicle, the space vehicle to launch vehicle adapter (if supplied by the space vehicle), and all other
unique hardware required on the launch
Notes:
1 -Throw weight is current EOS-AM I configuration. Delta II 7920 is the baseline vehicle for spacecraft design for future EOS AM spacecraft.
TABLE 9A- EELV COMMERCIAL MISSION MODEL
Commercial Mission Model specified in EELV CFI five Commercial missions per year, 4 east coast, 1 west coast, no heavy lift.
SPD ANNEX B
Table 10A - Government EELV Transition Schedule - No. of Missions
(Titan II Class) (Delta II Class) (Atlas IIAS Class) (Titan IV Cent. Class) (Titan IV-NUS Class) Table 10B - DoD EELV Transition Schedule - No. of Missions
(Titan II Class) (Delta II Class) (Atlas IIAS Class) (Titan IV Cent. Class) (Titan IV-NUS Class) Table 10C- NASA EELV Transition Schedule - No. of Missions
(Delta II Class)
CURRENT
THROW
APOGEE
PERIGEE
INCLINATION
LAUNCH ENERGY
PAYLOAD
COAST
ORBIT
VEHICLE CLASS
WT
(LBS.)
**
(NM)
(NM)
(DEGREES)
C3 (km2/sec2)
NOTES
* AIM
EAST
GTO
DELTA II 7920
4060
19323
100
28.7
N/A
* DISCOVERY
EAST
PLANETARY
DELTA II 7920
2000
N/A
N/A
28.5
17
EOS AM
WEST
SUN-SYNCH
DELTA II 7920
11220
380
380
98.2
N/A
1
EOS PM
WEST
SUN-SYNCH
DELTA II 7920
7000-8000
380
380
98.2
N/A
EOS CHEM
WEST
SUN-SYNCH
DELTA II 7920
7900
380
380
98.2
N/A
SOLAR PROBE
EAST
PLANETARY
DELTA II 7920
TBD
N/A
N/A
N/A
17
FY01
FY02
FY03
FY04
FY05
FY06
FY07
FY08
FY09
FY10
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
East Coast
0
4
4
4
4
4
4
4
4
4
West Coast
0
1
1
1
1
1
1
1
1
1
Total
0
5
5
5
5
5
5
5
5
5
FY11
FY12
FY13
FY14
FY15
FY16
FY17
FY18
FY19
FY20
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT A
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT B
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
COMLSAT C
East Coast
4
4
4
4
4
4
4
4
4
4
West Coast
1
1
1
1
1
1
1
1
1
1
Total
5
5
5
5
5
5
5
5
5
5 
TABLE 9B- EELV COMMERCIAL MISSION MODEL PAYLOAD LAUNCH VEHICLE REQUIREMENTS
CURRENT
THROW
APOGEE
PERIGEE
INCLINATION
LAUNCH
ENERGY
PAYLOAD
COAST
ORBIT
VEHICLE
CLASS
WT (LBS.) **
(NM)
(NM)
(DEGREES)
C3 (km2/sec2)
COMLSAT A
EAST
GTO
DELTA II
TBD
TBD
TBD
TBD
N/A
COMLSAT B
EAST
GTO
ATLAS IIA
TBD
TBD
TBD
TBD
N/A
COMLSAT C
WEST
LEO
DELTA II
TBD
TBD
TBD
TBD
N/A
Launch Vehicle
FY01
FY02
FY03
FY04
FY05
FY06
FY07
FY08
FY09
FY10
Titan II
1
0
0
0
0
0
0
0
0
0
EELV
0
1
0
1
0
1
1
0
0
0
Delta II
8
1
2
2
0
0
0
0
0
0
EELV
2
3
4
4
5
9
7
6
4
5
Atlas IIAS
0
1
0
0
0
0
0
0
0
0
Atlas IIA
3
0
1
0
0
0
0
0
0
0
EELV
0
3
2
5
2
4
4
4
3
4
Titan IV Centaur
3
2
0
0
1
0
0
0
0
0
EELV
0
0
0
0
0
0
0
1
0
0
Titan IV-NUS
1
2
1
1
1
1
0
0
0
0
EELV
0
0
0
0
0
0
0
1
0
0
Launch Vehicle
FY01
FY02
FY03
FY04
FY05
FY06
FY07
FY08
FY09
FY10
Titan II
0
0
0
0
0
0
0
0
0
0
EELV
1
1
0
1
0
1
1
0
0
0
Delta II
6
1
1
0
0
0
0
0
0
0
EELV
2
3
3
4
3
7
7
5
3
4
Atlas IIAS
0
1
0
0
0
0
0
0
0
0
EELV
0
3
2
5
2
4
4
4
3
4
Titan IV Centaur
3
2
0
0
1
0
0
0
0
0
EELV
0
0
0
0
0
0
0
1
0
0
Titan IV-NUS
0
0
0
0
0
0
0
1
0
0
EELV
0
0
0
0
0
0
0
1
0
0
Launch Vehicle
FY01
FY02
FY03
FY04
FY05
FY06
FY07
FY08
FY09
FY10
Delta II
2
1
1
2
0
0
0
0
0
0
EELV
0
0
1
1
2
2
1
1
1
1
Atlas IIA
3
0
1
0
0
0
0
0
0
0