Evolved Expendable Launch VehicleRideshare User’s GuideMay 2016Space and Missile Systems CenterLaunch Systems Enterprise Directorate (SMC/LE)483 N. Aviation Blvd.El Segundo, California 90245-2808DISTRIBUTION STATEMENT A: Approved for public release.
APPROVED BY:LEON.CLAIRE.NMN.1503817221Digitally signed byLEON.CLAIRE.NMN.1503817221DN: c US, o U.S. Government, ou DoD, ou PKI,ou USAF, cn LEON.CLAIRE.NMN.1503817221Date: 2016.07.16 17:42:08 -07'00'CLAIRE E. LEON, SES, DAFDirectorLaunch Systems Enterprise DirectorateDate SignedJOHN S.R. ANTTONEN, Colonel, USAFDirectorAdvanced Systems and Development DirectorateDate Signed-2DISTRIBUTION STATEMENT A. Approved for public release.
Contents1.0 INTRODUCTION .61.1 Scope .61.2 Purpose .61.3 Configuration Control .61.4 Definitions .61.5 Reference Documents .71.5.1 Air Force Documents .71.5.2 Department of Defense Documents .71.5.3 Other Documents .72.0 ORGANIZATIONAL RESPONSIBILITIES .82.1 Launch Systems Enterprise Directorate, Los Angeles Air Force Base, California .82.2 Advanced Systems Development Directorate, Kirtland Air Force Base, New Mexico .82.3 Headquarters, Air Force Space Command (AFSPC), Peterson Air Force Base, Colorado.82.3.1 Directorate of Plans and Requirements .82.3.2 Directorate of Air, Space, and Cyberspace Operations .82.4 Launch Vehicle Contractor .82.5 Auxiliary Payload Provider.83.0 RIDESHARE SELECTION PROCESS.93.1 Auxiliary Payload Selection and Rideshare Assessment .93.2 Rideshare Matching Process . 103.3 Flight Opportunity Notice . 103.4 APL Recommendation Plan . 113.5 Leading Edge Integration (LEI) . 113.6 APL Manifesting. 114.0 RIDESHARE EXECUTION PROCESS . 114.1 Do-No-Harm . 114.2 Rideshare Integration . 124.3 Integration Meetings and Compliance Reviews. 124.4 Auxiliary Payload Integration Timeline. 134.5 Launch Site Integration Support . 154.6 Mass Simulator Requirements . 154.8 Facilities and Processing . 164.9 Access to Auxiliary Payloads – Timelines. 164.10 Payload Battery Charging and Monitoring Restrictions . 164.11 Aborts and Recycles . 16-3DISTRIBUTION STATEMENT A. Approved for public release.
4.12 Auxiliary Payload Data Requirements . 165.0 RIDESHARE STANDARD SERVICE (RSS) CAPABILITIES . 175.1 CubeSat Integration (3U or 6U) . 175.1.1 Mechanical Interface . 185.1.2 Electrical Interface . 185.1.3 Battery Charging . 185.1.4 Launch Site Processing . 185.1.5 LV Purge . 195.1.6 Power to SV after IPS Integration. 195.1.7 Payload access on LV . 195.1.8 Separation System . 195.1.9 Telemetry . 195.1.10 SV to LV Integration . 195.2 Aft Bulkhead Carrier (ABC) Integration . 195.2.1 Mechanical Interface . 205.2.2 Electrical Interface . 205.2.3 Battery charging . 205.2.4 Launch Site Processing . 205.2.5 LV Purge . 215.2.6 Power to SV after IPS Integration . 215.2.7 Payload access on LV . 215.2.8 Separation System . 215.2.9 Telemetry . 215.2.10 SV to LV Integration . 225.3 ESPA Integration . 225.3.1 Mechanical Interface . 225.3.2 Electrical Interface . 225.3.3 Battery Charging . 225.3.4 Launch Site Processing . 235.3.5 LV Purge . 235.3.6 Power to SV after IPS integration . 245.3.7 Payload access on LV . 245.3.8 Separation System . 245.3.9 Telemetry . 245.3.10 SV to LV Integration . 245.4 ESPA Grande Integration. 245.4.1 Mechanical Interface . 24-4DISTRIBUTION STATEMENT A. Approved for public release.
5.4.2 Electrical Interface . 255.4.3 Battery charging . 255.4.4 Launch Site Processing . 255.4.5 LV Purge . 265.4.6 Power to SV after IPS Integration . 265.4.7 Payload access on LV . 265.4.8 Separation System . 265.4.9 Telemetry . 265.4.10 SV to LV Integration . 275.5 A-Deck integration. 275.5.1 Mechanical Interface . 275.5.2 Electrical Interface . 275.5.3 Battery Charging . 275.5.4 Launch Site Processing . 275.5.5 LV Purge . 285.5.6 Power to SV after IPS Integration . 285.5.7 Payload access on LV . 285.5.8 Separation System . 285.5.9 Telemetry . 295.5.10 SV to LV Integration . 296.0 ACRONYMS AND ABBREVIATIONS . 30-5DISTRIBUTION STATEMENT A. Approved for public release.
1.0 INTRODUCTION1.1 ScopeThe Rideshare User’s Guide (RUG) provides guidelines and information for preliminaryspacecraft design, launch vehicle (LV) integration, and mission planning for auxiliary payloads(APLs) seeking access to space via Rideshare Standard Service (RSS).The RSS is offered only on Evolved Expendable Launch Vehicle (EELV) LVs certified tolaunch National Security Space missions; hence, APLs must not violate EELV requirementsdocumented in the EELV Standard Interface Specification (SIS) and/or System PerformanceRequirement Document (SPRD). APL requirements are not addressed in the SIS but theirrequirements are derived from the SIS.1.2 PurposeThe RUG formally defines RSS and outlines the specific services provided by the LaunchVehicle Contractor (LVC) under contracts administered by the Space and Missile SystemsCenter (SMC) Launch Systems Enterprise Directorate (SMC/LE). Any services requested bythe APL beyond those specified in the RUG are by definition “non-standard” and will requireadditional funding beyond SMC/LE’s RSS funding. All costs resulting from non-standardrideshare related activities will be funded by the APL customer or its sponsor. Additionally,the APL(s) must abide by the process of do-no-harm to the primary mission.1.3 Configuration ControlThe RUG is a government-owned guide for APL users. Revisions to this document arecoordinated with key stakeholders, suppliers, industry, etc. and are publically released uponfinal approval by the Director, Launch Systems Enterprise Directorate (SMC/LE) and Director,Advanced Systems and Development Directorate (SMC/AD).Changes to the RUG can be driven by changes in the LVC-controlled interfaces, environments,services, etc; therefore, users should contact SMC/LE and SMC/AD for the most up to dateinformation, such as launch environments related to each LV.1.4 DefinitionsAuxiliary Payload (APL) – The space vehicle(s) with associated adapters and interfaces thatutilize launch capability not required by the EELV Primary Payload.APL Provider (APLP) – The organization providing an APLAuxiliary Standard Interface Plane (ASIP) – The standard interface on the LV [e.g. ESPAring adapter, ABC, etc.] to which the APL mates to for rideshare purposeEELV Mission - Safe delivery of an EELV Payload to its intended orbit and disposal of EELVorbital components.EELV Payload – The EELV Primary Payload and EELV Auxiliary Payload (whenmanifested) delivered to space by the EELV System with associated adapters and interfaces.-6DISTRIBUTION STATEMENT A. Approved for public release.
Evolved Expendable Launch Vehicle (EELV) System – The EELV Launch VehicleSegment and EELV Ground Segment along with associated operation and support services andpersonnel that provide the capability to perform all EELV Missions.Family of Flight Configurations – A product line of launch vehicles offered by a launchvehicle contractor (e.g. Atlas V, Delta IV, Falcon 9).Ground Segment – All facilities, equipment, software, utilities, and launch base infrastructurenecessary to support mission planning; launch vehicle storage; payload encapsulation, mating,and transportation; check-out; processing; launch; and telemetry, tracking and control of theEELV Launch Vehicle Segment.Launch Vehicle – A particular instantiation of an EELV Launch Vehicle Segment.Launch Vehicle Contractor (LVC) – The contractor providing launch services, including itssubcontractors.Launch Vehicle Segment – A family of flight configurations that each include structuralelements, propulsion, guidance and control, electrical power, tracking, telemetry and control,ordnance, flight termination, software, payload fairing, and payload separation initiation.Primary Payload (PPL) – The space vehicle(s) with associated adapters and interfaces thatestablish the EELV mission requirements.PPL Provider (PPLP)-The organization providing a PPL1.5 Reference Documents1.5.1 Air Force Documents Air Force Space Command (AFSPC) Manual (AFSPCMAN) 91-710, Range Safety UserRequirements (as tailored for the APL)Evolved Expendable Launch Vehicle (EELV) Standard Interface Specification (SIS)Air Force Instruction 10-1202, Space Test Program ManagementAir Force Instruction 10-1202 AFSPCSUP, Space Test Program ManagementAFSPCI 13-1213, Launch Scheduling and Forecasting Procedures1.5.2 Department of Defense Documents MIL-STD-461G, Requirements and Test Methods RE101 (B-Field emissions) and RE102(E-Field emissions)SMC-S-016MIL-STD-1576, Electroexplosive Subsystem Safety Requirements and TestMethods for Space Systems1.5.3 Other Documents Aft Bulkhead Carrier (ABC) Auxiliary Payload User’s Guide, May 2014-7DISTRIBUTION STATEMENT A. Approved for public release.
2.0 ORGANIZATIONAL RESPONSIBILITIES2.1 Launch Systems Enterprise Directorate, Los Angeles Air Force Base, CaliforniaSMC/LE is responsible for developing and maintaining the LV performance database for allEELV missions, coordinating with Headquarters, Air Force Space Command (HQ AFSPC) toidentify candidate Rideshare missions in conjunction with the Department of Defense (DoD)Space Test Program (STP), coordinating with the PPL program office and contracting with theLVC to provide RSS for designated missions. SMC/LE is also responsible for reportingavailable spacelift margin.2.2 Advanced Systems Development Directorate, Kirtland Air Force Base, New MexicoThe DoD STP, as executed by the Advanced Systems Development Directorate (SMC/ADS),is responsible for executing the APL identification, selection/matching, and manifest processin accordance with Air Force Instruction (AFI) 10-1202, AFSPCSUP AFI 10-1202, andAFSPCI 13-1213. DoD STP is responsible for APL evaluation and selection, coordination oftechnical and programmatic deliverables with the primary payload program office,coordinating with SMC/LE, and development and approval of an APL Recommendation Plan(ARP) with SMC and HQ AFSPC.2.3 Headquarters, Air Force Space Command (AFSPC), Peterson Air Force Base,Colorado2.3.1 Directorate of Plans and RequirementsThe Directorate of Plans and Requirements (AFSPC/A5) at HQ AFSPC is responsible foridentifying AFSPC rideshare and EELV performance requirements. This directorate is alsoresponsible for identifying Air Force and AFSPC APL flight requirements.2.3.2 Directorate of Air, Space, and Cyberspace OperationsAll APL missions to be manifested are coordinated with the Directorate of Air, Space, andCyberspace Operations (AFSPC/A2/3/6) at HQ AFSPC for launch forecasting and scheduling,as described in AFSPCI 13-1213, Launch Scheduling and Forecasting Procedures. TheSpacelift and Range Operations Branch (AFSPC/A3S) is responsible for concurrence with LVselection for rideshare missions, as well as concurrence with APL manifest packages for finalapproval. AFSPC/A2/3/6 is also responsible for coordinating with PPL operator and, if anassessment determines that the APL bears too great a negative impact on operational missions,they may disapprove its integration. AFSPC will issue LV requirements letters to SMC/LEthat identify both PPL and APL launch requirements.2.4 Launch Vehicle ContractorThe LVC is described as the contracted launch service provider and its subcontractors thatprovide the launch vehicle and rideshare integration services. LVC is responsible for deliveringthe requisite technical documents and other materials to the above-mentioned organizations asdescribed in section 3.2.5 Auxiliary Payload ProviderThe APLP should participate in the APL identification and manifesting process as defined inAFI 10-1202, AFI 10-1202 AFSPCSUP, and AFSPCI 13-1213. The APLP is responsible for-8DISTRIBUTION STATEMENT A. Approved for public release.
developing, building, and supplying an APL that meets the RUG criteria. It is responsible forgenerating and delivering the requisite technical documents and other materials to SMC/LE,STP (SMC/ADS), and the LVC in order to ensure proper fulfillment of performancerequirements, compliance and compatibility, as described in this composition and the mostcurrent EELV requirements. The APLP (working with and through their sponsoringorganization) should be prepared to fund any non-standard services required for their mission.For example, APLP should be prepared to supply a flight-qualified mass simulator to replacetheir payload as a schedule risk mitigation for the primary mission; schedule for a masssimulator need will be determined during the launch mission execution process.3.0 RIDESHARE SELECTION PROCESSRSS consists of a set of standardized processes for acquiring, integrating, verifying, and flyingAPLs on EELV missions to provide affordable, frequent and timely access to space. This RUGprovides descriptions of those standard services. Final launch environments will be definedand documented in the LVC-controlled Interface Control Document (ICD) as part of theindividual launch mission execution process. The descriptions of the environments encompass“worst case” flight environments which are dependent on the LV and the mission trajectory.In accommodation of APLs, RSS encompasses the required Mission Kit hardware (defined insection 4.0), APL-to-LV rideshare integration and launch services, and program and missionmanagement as outlined in each APL class appendix. Non-standard APLs may procure nonstandard services on a mission-unique basis, at additional cost to the APL customer or itssponsor (e.g., APLs that require fairing access doors post encapsulation, gaseous nitrogen T-0purge, etc.) SMC/LE encourages rideshare users to identify and generate a composition of nonstandard requirements as early as possible with STP so that appropriate contractual andtechnical provisions can be made. RSS capability offerings will be provided at theGovernment’s discretion.3.1 Auxiliary Payload Selection and Rideshare AssessmentSTP is the designated initial contact for all APLs seeking launch opportunities on DoDmissions. Candidate APLs, and/or their sponsoring organizations, should participate in theannual HQ AFSPC APL data call process and submit the basic information on theirrequirements as defined in the data call (see Figure 1: Rideshare Process). Candidate APLsmust coordinate with STP to ensure adequate performance and compatibility between the PPLand APLs. In this capacity, STP will facilitate relationships between appropriate PPL programoffices and APL customers. SMC/LE and STP will identify EELV excess performance marginand useful mission trajectories among manifested missions, and prioritize a list of theopportunities that should be targeted for rideshare missions. Figure 1 describes the APL tomission matching and APL approval for manifesting process.-9DISTRIBUTION STATEMENT A. Approved for public release.
HQ AFSPC AnnualAPL Data Call(Aug/Sep)STP RideshareMatching(2 Months)APLsDoD, NASA,NRO, etc.SMC/LELV ExcessMarginHQ AFSPCdesignatedRideshareLaunchesRideshareMatching ResultsBriefing to HQAFSPCSTP issues FONsto APLs(2 Weeks)LSDO Release(May)STP CreatesARPs forRideshareMissions(1 month)HQ AFSPCReceives ARPfrom STP(1 Month)HQ AFSPC TaskLetter toSMC/LE forApprovedRidesharesSMC/LE & STPExecute Plan (LEIs,APLs MOA/MOU,etc.)Figure 1: Rideshare Process3.2 Rideshare Matching ProcessHQ AFSPC initiates the rideshare matching process annually and provides STP with all HQAFSPC APL data call information, such as EELV excess performance margin, missiontrajectories, and planned launch dates for currently manifested missions. STP then uses thedata to perform a rideshare matching exercise which identifies potential APL candidates forrideshare on the currently manifested missions. Results of the rideshare matching exercise arereviewed and approved by the STP director and forwarded to HQ AFSPC for final approval toproceed with planning designated rideshare missions.3.3 Flight Opportunity NoticeOnce STP has permission from HQ AFSPC to plan a rideshare mission for a specific launch,STP will notify candidate APLs via a Flight Opportunity Notice (FON). When STP sends outthe FON, it will include a deadline for APLs to accept or reject the offer for flight. A FONdoesn’t constitute being manifested on the mission; it is only a potential flight opportunity.Once the Memorandum of Agreement/Memorandum of Understanding (MOA/MOU) issigned by all parties and the Mission Requirements Document (MRD) is completed and sentto SMC/LE, the APLs can then be considered manifested to the mission.-10DISTRIBUTION STATEMENT A. Approved for public release.
3.4 APL Recommendation PlanSTP will submit an APL Recommendation Plan (ARP) to HQ AFSPC listing all the APLs,APL size and mass, and orbit requirements for the rideshare mission. Some of the APLinformation may not be mature, but should meet the initial requirements for HQ AFSPC toreview. If HQ AFSPC approves the ARP for the mission, HQ AFSPC will issue a taskingletter to SMC/LE to designate the mission as a Rideshare and identify the number and types ofAPLs to include on the manifest.3.5 Leading Edge Integration (LEI)After the ARP is approved and tasking letter issued, STP will work with SMC/LE to build anacquisition package to accomplish a Leading Edge Integration (LEI) effort. The package willinclude the primary payload name, projected launch date, potential orbit(s), and any other toplevel mission elements or constraints required to determine the feasibility of the candidate APLmission. SMC/LE will then contract the LVC(s) to conduct an LEI study to determine thecompatibility of the PPL and the APL(s). Mission unique requirements (non-standard services)needed by APLs will also be determined and defined in this compatibility study.3.6 APL ManifestingSTP will initiate a MOA, if transfer of funding is required, or a MOU with each APL todocument the roles and responsibilities of the STP Program Office and the APL’s organizationand clearly delineate necessary support required of each organization to ensure successfulmission execution. STP will create a MRD to document the mission requirements of all theAPLs for SMC/LE to put on contract with the LVC(s) for LEI purposes. Once the MOA/MOUis signed by all parties and the MRD is completed and sent to SMC/LE, the APLs can then beconsidered
Evolved Expendable Launch Vehicle Rideshare User's Guide May 2016 Space and Missile Systems Center Launch Systems Enterprise Directorate (SMC/LE)