Table of Contents
1.1 Purpose. This document identifies the Evolved Expendable Launch Vehicle (EELV) system performance requirements and goals derived from the EELV Operational Requirements Document (ORD).
1.2 Overview of EELV Program. 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.
1.3 Document Overview. This document 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 A-specification.
1.4 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.
2.0 APPLICABLE DOCUMENTS.
2.1 Compliance Documents. None.
2.2 Reference Documents. EELV Payload Database Document.
3.0 SYSTEM REQUIREMENTS.
3.1 System Definition.
3.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.
3.1.2 System Segments.
3.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.
3.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, storage, integration, check-out, processing, launch, telemetry, tracking and control through CCAM, and recovery/refurbishment (if any) for the EELV system.
3.1.3 Government Furnished Equipment (GFE). GFE shall be defined in the Contractor prepared system specification.
3.1.4 System Functions. The EELV system shall perform the major functions identified below.
3.1.4.1 Manufacturing. This function includes the manufacturing of all launch vehicle components, subsystems, and subassemblies.
3.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.
3.1.4.3 Receipt and Checkout. This function includes initial receipt, unloading, and checkout of launch vehicle elements/subsystems/subassemblies.
3.1.4.4 Launch Vehicle Storage. This function includes the capability to store launch vehicle elements/subsystems/subassemblies prior to use in the system.
3.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.
3.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.
3.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.
3.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.
3.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.
3.1.4.10 Refurbishment. This function includes activities required to refurbish ground equipment and facilities for reuse.
3.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.
3.1.4.12 Integrated 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.
3.2 System Characteristics.
3.2.1 Performance Requirements. The EELV system shall meet the following performance requirements. The system shall meet all non-tradable performance requirements simultaneously. All performance requirements specified in this document are tradable except for the following: reliability; lift capability; launch rates; orbital parameter, attitude and rate accuracies; all payload environments and accommodations (including CCAM); and any required by law.
3.2.1.1 Lift Capability. The EELV system shall provide a sufficient range of lift capability to accommodate the Government portion of the National Mission Model in RFP Annex C-1. The EELV MLV and HLV shall have the capability to inject into geosynchronous transfer orbits on either the ascending or descending leg. The EELV MLV shall have the capability to fly directly to 12-hour, highly elliptical, critically-inclined orbits and the capability to perform short duration upper stage burns for circularizing low altitude orbits. This is a non-tradable requirement. Vehicle sizing shall be based on performance estimation techniques which shall provide a 99% assurance of the vehicle fully meeting mass to orbit requirements while considering possible uncertainties in EELV and environmental parameters, such as propellant loading, Isp, and atmospheric density.
3.2.1.2 Launch Operational Requirements.
3.2.1.2.1 Transition. The EELV system shall accommodate the Transition Schedule included in RFP Annex C-2.
3.2.1.2.2 Launch Rates. The system shall have sufficient throughput to support the range of Government requirements in RFP Annex C-1. This is a non-tradable requirement. The system shall also be resilient enough to recover from a downing event or other delays which may cause the system not to meet the launch rate requirements in RFP Annex C-1.
3.2.1.2.3 Schedule Dependability. The EELV system (ground and launch vehicle segments) shall launch within 7 calendar days of the scheduled launch time. Attributable delays include EELV equipment-caused delays, processing delays and weather delays. The schedule shall be considered firm 90 days prior to the scheduled launch date.
3.2.1.2.4 Launch Responsiveness. The EELV shall be capable of repeatedly responding to priority requests for launches within a minimal time (MLV goal of 30 calendar days, HLV goal of 60 calendar days) from the date of launch request, assuming the availability of a processed payload ready for mating with the EELV.
3.2.1.2.5 Hold Requirements.
3.2.1.2.5.1 Mission Ready Hold. The system shall be capable of holding in a mission ready status for a minimum of 30 days. Mission ready means the system can move from the mission ready hold state to launch within 24 hours of notification.
3.2.1.2.5.2 Fueled Vehicle Hold. The system shall be capable of maintaining a ready-to-launch status with propellants loaded for at least two hours.
3.2.1.2.6 Launch Abort Requirements. The system shall be capable of performing a fail-safe abort such that the payload and launch system are protected following a launch abort anytime prior to launch commit.
3.2.1.2.7 Recycle. The system shall be capable of recycling, following a fueled vehicle hold, to enable launch within the launch window on the next calendar day. The system shall also be capable of performing recycling on at least two successive days.
3.2.1.3 Post Launch Operations Requirements. The LV shall be capable of providing real time telemetry data from launch through the completion of CCAM and disposal operations.
3.2.1.4 On-Orbit Operations Requirements.
3.2.1.4.1 Payload Separation Command and Verification. The EELV system shall provide a separation enable signal to the payload, and a payload separation complete signal to ground control via telemetry channels. The system shall also have the capability to provide a separation command to the separation system.
3.2.1.4.2 Orbital Parameter Accuracy. The accuracy at injection point with 3s probability shall be in accordance with the following table. These are non-tradable requirements.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DSCS |
ñ70 |
ñ1.5 |
ñ0.1 |
ñ0.4 |
ñ0.5 |
N/A |
|
ADV MILSAT |
ñ100 |
ñ0.9 |
ñ0.1 |
ñ0.3 |
N/A |
ñ0.75 |
|
DMSP w/AKM |
ñ9 |
ñ7 |
ñ0.05 |
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 A |
ñ60 |
ñ2 |
ñ0.1 |
ñ0.2 |
N/A |
ñ0.2 |
|
Mission B |
ñ2 |
ñ2 |
ñ0.05 |
ñ1* |
N/A |
ñ0.05 |
|
Mission C |
±180 |
±180 |
±0.1 |
N/A |
N/A |
N/A |
|
Mission D |
ñ2 |
ñ2 |
ñ0.05 |
ñ1* |
N/A |
ñ0.05 |
3.2.1.4.3 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 and maintaining a commanded roll rate in either direction of up to 5.0 ± 0.5 (3s) rpm. 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 EELV MLV shall have the capability to provide spin rates from 5 ± 0.5 (3s) to 70 ± 5.0 (3s) rpm. Spin axis orientation shall be accurate to within 3o (3s). The requirements in this paragraph are non-tradable.
3.2.1.4.4 Separation State Vector. The LV shall provide position, velocity, and attitude of the payload to the payload at the separation point in real time.
3.2.1.4.5 Contamination & Collision Avoidance Maneuver. Following payload separation, the LV shall perform a collision and contamination avoidance maneuver. The CCAM shall be designed to preclude recontact with the payload and to minimize payload exposure to LV contaminants. 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 requirements in this paragraph are non-tradable.
3.2.1.5 Recovery and Disposal Requirements. The system shall provide for safe disposal or recovery of all LV components and all non-deployed payload equipment. The subsections of this paragraph are non-tradable requirements.
3.2.1.5.1 Low Earth Orbit Disposal. Disposal of EELV components from low earth orbit shall be in ocean areas:
a. No Closer than 200 NM from foreign land masses
b. No closer than 50 NM from US Territories and States
c. North of 60 degrees south latitude
d. Outside normal shipping lanes
3.2.1.5.2 Orbital Debris. The LV stages which are orbital shall be safely deorbited whenever practical. If not deorbited, then the following shall be met:
3.2.2.1 Interfaces.
3.2.2.1.1 Coordinate System. The coordinate system shall be defined in the Contractor prepared system specification.
3.2.2.1.2 Payload Accommodation. The EELV must accommodate the Government payloads in RFP Annex C-1 and shall provide standard interfaces and services (such as mechanical interfaces, power, environmental conditioning, etc.). This is a non-tradable requirement. 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 ASE/services. The weight of the ASE shall be considered payload weight.
3.2.2.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. This is a non-tradable requirement. The Payload Database Document may be used for reference information regarding current payloads.
3.2.2.1.4 Envelope. The envelope shall be sufficient to provide a minimum of one inch clearance between the payload and the fairing under worst case dynamic conditions and shall accommodate the maximum static payload envelopes shown below. This is a non-tradable requirement. The Payload Database Document may be used for reference information regarding current payloads.
31.74"
208.51"
MLV 143" HLV 480"
Class Class
197.5"
143" 180"
3.2.2.1.5 Payload Mass Properties. The LV shall be capable of accommodating the mass properties of the Government payloads in the National Mission Model. This is a non-tradable requirement. The Payload Database Document may be used for reference information regarding current payloads.
3.2.2.1.6 Range Interfaces. The EELV system shall comply with the interface requirements of the appropriate range facilities and equipment required to support EELV operations.
3.2.2.1.7 Payload Substitution. To maximize operational flexibility and reduce costs, EELV shall accommodate payload substitution (with another payload normally assigned for launch on the same size LV) prior to payload mate, up to five days before a scheduled launch. The EELV system shall facilitate rapid payload substitution so that schedule delays are minimized or avoided. Payload substitution should not drive additional launch processing other than activities normally required for payload mating.
3.2.2.2 Launch Vehicle Design Reliability. Design reliability, including hardware, software, and firmware, from launch commit through CCAM shall be at least 98% for the LV. This is a non-tradable requirement.
3.2.2.3 Design Considerations and Margins.
3.2.2.3.1 Performance and Design Margins. Performance margin shall be defined in the Contractor prepared system specification. The Government has an objective of a 15 percent performance margin. Design margin and verification of chosen design margin values shall be defined in the Contractor prepared system specification and Requirements Verification Matrix, respectively.
3.2.2.3.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.
3.2.2.3.3 Weight Growth Margins. Appropriate weight growth margins shall be maintained for all hardware commensurate with the maturity of the hardware and the phase of design.
3.2.2.3.4 Pogo Stability. The EELV shall be designed to maintain pogo stability regardless of payload configuration.
3.2.2.3.5 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.
3.2.2.3.6 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.
3.2.2.3.7 Product Improvement. The EELV system shall facilitate incorporation of pre-planned program product improvement features without significant impact to the baseline design.
3.2.2.4 System Diagnostics.
3.2.2.4.1 Pre-Launch Diagnostics. The system shall include integrated vehicle health monitoring and fault detection/isolation capability as required to meet the EELV system requirements.
3.2.2.4.2 In-Flight Diagnostics. The flight vehicle shall telemeter key data (compatible with range equipment) to assess performance, verify that the vehicle is operating within its design, qualification and acceptance limits, and provide a basis for identification of malfunction and failure.
3.2.2.5 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.
3.2.2.5.1 Software. Computer hardware and operating system resources for the EELV system shall be selected in the following order of priority: (1) Commercial off-the-shelf (COTS), (2) Military off-the-shelf (MOTS), and (3) EELV developed (including modified COTS and MOTS). Software design shall use the following order of priority in make-buy-reuse decisions: (1) COTS software, (2) reusable software components, and (3) EELV-developed software (including modified COTS and modified reusable software components). Proprietary software used within the EELV system shall either be COTS or have the data rights owned by the Government.
3.2.2.5.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 addressed in the Contractor prepared system specification.
3.2.2.5.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.
3.2.2.5.4 Computer Resource Reserves. Reserve requirements for processor, primary memory, peripheral data storage (secondary memory), and data transmission media capacity/throughput shall be addressed in the Contractor prepared system specification.
3.2.2.5.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.
3.2.3 Environments.
3.2.3.1 Natural Environments. The EELV system shall be capable of withstanding and protecting the payload from the natural environments during pre-launch and launch operations.
3.2.3.2 Induced Environments. The LV shall be capable of withstanding induced environments during pre-launch, launch, flight, and on-orbit operations.
3.2.3.3 Payload Flight Environments. The requirements specified in the subsections of this paragraph are non-tradable.
3.2.3.3.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.
3.2.3.3.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 worst case values (lowest at any frequency) in Table 2, as appropriate for EELV MLV and HLV. Provisions shall be made for application of sound attenuation measures for individual payload programs which may seek to reduce exposure to acoustic noise.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||
3.2.3.3.3 Pyro Shock. The maximum expected shock spectrum at the payload interface in g's (value at 95% probability with 50% confidence) for a resonant amplification factor (Q) of 10 shall not exceed the values specified in Table 3 in any direction (assuming the separation system is provided by the payload).
|
|
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
3.2.3.3.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.
3.2.3.3.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.
3.2.3.3.6 Thermal. The EELV shall have the capability to control the thermal environments within the payload fairing during appropriate phases of flight. The Payload Database Document may be used for reference information regarding current payloads.
3.2.3.3.7 Free Molecular Heating. The maximum free molecular heating shall be compatible with the payload during all phases of flight. The Payload Database Document may be used for reference information regarding current payloads.
3.2.3.3.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.
3.2.3.4 Ground Environments.
3.2.3.4.1 Transportation. System hardware shall be designed to withstand normal handling and transportation environments.
3.2.3.4.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 of the events.
3.2.3.4.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. This is a non-tradable requirement. The Payload Database Document may be used for reference information regarding current payloads.
3.2.3.4.4 Processing Contamination Control. The airborne particle concentrations shall not exceed Class 100K during payload integration.
3.2.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. This is a non-tradable requirement.
3.2.3.5.1 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. The Payload Database Document may be used for reference information regarding current payloads.
3.2.3.5.2 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.
3.2.3.5.3 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.
3.2.3.5.4 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.
3.3 Integrated Logistics Support (ILS). An ILS program shall be established to insure a disciplined, unified and iterative approach to the management and technical activities necessary to: (a) integrate support considerations into system equipment design, (b) develop support requirements that are related consistently to readiness objectives, to design, and to each other, (c) acquire the required support, and (d) 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 program including the use of standard Air Force logistics systems as one alternative.
3.3.1 Personnel and Training. Training data and training facilities/equipment shall be provided to train personnel (Air Force or equivalent Contractor) to satisfy operations or maintenance requirements. The overall goal is to reduce the total Government and Contractor manpower required to operate and maintain the system to an absolute minimum. Initial training shall be provided by the Contractor. Follow-on training requirements shall be determined as part of the ILS program.
3.3.2 Standard Procedures and Data Systems. The EELV shall utilize standard procedures for maintenance, supply, processing, flight planning and launch operations of the system encompassing the needs of the missions in the RFP Annex C-1. To the extent that EELV procedures involve interaction with standard Air Force logistics system, EELV data system shall be compatible with those of the logistics systems.
3.3.3 Transportability. Whenever possible, efficient 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.
3.3.4 Supportability. The EELV system shall be supportable via a logistics system configured to enable conduct of launch operations commensurate with the Government missions in the National Mission Model (RFP Annex C-1). 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.
3.3.5 Maintainability. The EELV system shall be sufficiently maintainable to allow meeting launch rate and schedule dependability requirements. Emphasis shall be placed on rapid fault isolation, 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.
3.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.
3.4 Facilities and Services. These requirements are concept dependent. However, launch facilities, infrastructure and services across the EELV vehicle family and launch sites shall be standardized to the maximum extent practicable. The Contractor prepared system specification shall address all required facilities and services as appropriate for the EELV concept.
3.5 Other. The requirements specified in the subsections of this paragraph are non-tradable.
3.5.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, EPA-17 chemicals and EPCRA Section 313 chemicals.
3.5.2 Safety Requirements. The system shall meet all range imposed safety requirements. The EELV system shall also provide effective overall system safety by minimizing hazardous conditions and operations, and by providing safety margins. The EELV system design shall be such that hazards to personnel, to the system, and to the associated equipment are either eliminated or controlled throughout all phases of the life cycle.
3.5.3 Security Requirements. EELV shall provide a security system to deter, detect, and impede intruders, and facilitate the interception and neutralization of hostile elements by security personnel before those elements can access or damage mission critical components. EELV shall have security measures appropriate for payload classifications up to and including Top Secret/Sensitive Compartmentalized Information.
4.0 QUALITY ASSURANCE PROVISIONS.
4.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.
4.2 Verification Approach.
4.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.
4.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.
4.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.
4.3 Requirements Verification . 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.
| 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 | ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3.2.1.1 Lift Capability |
|
|
|
|
|
|
|
3.2.1.2.1 Transition |
|
|
|
|
|
|
|
3.2.1.2.2 Launch Rates |
|
|
|
|
|
|
|
... |
|
|
|
|
|
5.0 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.
6.0 ACRONYMS AND ABBREVIATIONS.
AGE Aerospace Ground Equipment
ASE Airborne Support Equipment
CCAM Collision, Contamination Avoidance Maneuver
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
ER Eastern Range
GEO Geosynchronous Earth Orbit
GFE Government Furnished Equipment
GSE Ground Support Equipment
HLV Heavy Lift Variant
HVAC Heating, Ventilation and Air Conditioning
ILS Integrated Logistics Support
LAN Longitude of Ascending Node
LEO Low Earth Orbit
LV Launch Vehicle
MLV Medium Lift Variant
MOTS Military Off-The-Shelf
N/A Not Applicable
NMI Nautical Miles
ODS Ozone Depleting Substance
ORD Operational Requirements Document
PIF Payload Integration Facility
RAAN Right Ascension of Ascending Node
RF Radio Frequency
RPIE Real Property Installed Equipment
RPM Revolutions Per Minute
SPD System Performance Document
TBD To Be Determined
TSE Test Support Equipment
WR Western Range
