SSL Payload Orbital Delivery System (PODS) FedEx to GTO/GEO

Transcription

1 SSL Payload Orbital Delivery System (PODS) FedEx to GTO/GEO June 11th, 2014 For more information, contact: Al Tadros, SSL Tel: (650)

2 Cost-Effective, Frequent, Quick Access to GTO/GEO for Small Payloads The Payload Orbital Delivery System (PODS) enables low-cost, hightempo access to GTO or GEO for small payloads FedEx to GEO 90 kg for standard form factor, 150 kg for extended form factor ~6-8 satellite launch opportunities per year with SSL Standardization of interfaces and form factor enables quick turnaround No need to coordinate with other payloads Launch vehicle independent payload interface does not change if the launch vehicle changes 2

3 SSL is a World Leader in Commercial Communications Satellites 3

4 SSL Has A Well-Established Capability In Hosted Payloads 4

5 Launch Frequency to GTO/GEO is Forecasted to Remain High 5

6 MicroSatellites Are Integrated and Dispensed from the ComSat Typical pre-release views for different launch locations are shown Launch location depends on microsatellite volume and ComSat configuration Payload sizing can go as small as CubeSat Mid East/West Faces If No E/W OMUX Anti-Nadir Side of North/South Panels Unused Battery Compartments On East/West Faces Antenna Tower 6

7 Concept for Resupply of Servicing Infrastructure in GEO 7

8 Deep Space Microsatellite Missions - GTO Drop-Off 8

9 SSL Uses a Variety of Launch Vehicles SSL launches on a variety of launch vehicles Ariane 5, Proton, Atlas, Falcon 9 Environmental Requirements envelope the requirements for each launch vehicle PODS does not have to interact with the launch vehicle Launch vehicle can change with no impact to the PODs There are a variety of options for drop-off location: Sub-GEO or Super-GEO GTO In-between GTO and GEO 9

10 MicroSatellite Ejection from Host The ejection is set up such that it is passively safe from the satellites recontacting each other (i.e., neither spacecraft is required to perform a maneuver to avoid recontact after ejection) The Host spacecraft commands / controls the ejection ~0.25 m/s ejection speed 0.5 deg/sec/axis maximum tumble rate < 5 degrees pointing error on ejection Upon ejection, data is provided to the MicroSatellite owner/operator to determine the location of the MicroSatellite 100 m range accuracy 2 km track accuracy The release sequence is monitored by video equipment on the Host 10

11 Payload Orbital Delivery System (PODS) Design Concept Standard PODS (1m x 0.5m x 0.4m) (L x W x H) Insert Microsatellite of Choice Low Separation Force Electrical Connector Low Tumble Rate Ejection Mechanism Launch Locks PODS Baseplate (stays with Host) 11 Extended Size Baseplate for Larger Payloads

12 MicroSatellite Mechanical Interface to GEO ComSat The MicroSatellite interfaces mechanically to the GEO ComSat via the PODS Ejection Mechanism (PEM) Baseplate. Primary structural interface to the MicroSatellite is the launch locks (Redundant Release Devices) Fittings on MicroSatellite will interface to the PODS Ejection Mechanism for deployment PODS Ejection Mechanism Fittings Launch Locks 12

13 Power & Data is Available for the MicroSatellite Power (optional) Power can be provided to the MicroSatellite on the ground and after launch for heaters, battery charging, etc. Available power: nominally 150W average, 300W peak; V More power can be made available if needed MicroSatellite State On as needed during AI&T Off during Host launch, LV-separation and Orbit Raising On prior to ejection for health monitoring, battery top-off, etc. Off ~10 seconds before MicroSatellite ejection No electric current flowing at IFD Interface at Separation/PODS Ejection Data Interface (optional): MIL-STD-1553 preferred; low volume for sporadic health data only Other options available 13

14 Other MicroSatellite Design Considerations Dynamic Environment - The MicroSatellite will need to be tested to meet the dynamic environment typical of commercial satellite launch vehicles RF Environment - RF environment generated by the Host spacecraft should be considered in MicroSatellite CONOPS and comm design May govern when MicroSatellite comm can be turned on after release and separation Thermal Environment - The thermal environment that the MicroSatellite will see while hosted depends on the hosting location - the MicroSatellite will be thermally isolated from the Host Spacecraft Integration and Test Flow MicroSatellite delivery to SSL is required in time to meet the Host Spacecraft I&T schedule The typical ComSat launches months from the date of the contract signing Delivery schedule to SSL will depend on the type of payload, whether it has flown before on an SSL spacecraft, and whether a high-fidelity simulator exists. 14

15 Integration and Test (I&T) Flow Typical ComSat launch is months from signing of ComSat contract MicroSatellite Integration & Test MicroSatellite Propulsion/Bus Subsystem (SSM) Communications Panel Level Dispenser Integral to Spacecraft Spacecraft Assembly INITIAL REFERENCE PERFORMANCE PHASE Initial Spacecraft Level Test (includes Power and Data compatibility testing) THERMAL VACUUM PHASE Required Integration Path for first-time implementation in a particular location MicroSatellite Ground Segment Interface Testing Pre-Thermal Vacuum Interface Validation Thermal Vacuum Testing Post-Thermal Vacuum Checks DYNAMICS PHASE FINAL PERFORMANCE PHASE Antenna/ Tower Dynamics Build Dynamics Testing & Mass Properties Post-Dynamics Mechanical Verification Compact Antenna Test Range PIM, EMI/EMC Test Spacecraft Testing Solar Array Solar Array MicroSatellite Ground Segment I/F Verific. Opportunity MicroSatellite Final Performance & Health Solar Array FINAL OPERATIONS PHASE LAUNCH SITE PHASE Mechanical and Electrical Operations Packaging & Shipment Test Operations Final Launch Operations Combined Operations Launch Batteries Alternate (Recurring) Integration Path requires a high-fidelity simulator for earlier spacecraft test flow 15

16 SSL PODS Service Takes the MicroSatellite from I&T to Launch Items Typically Included in Firm Fixed Price Contract: Program Management Product Assurance Systems Engineering Support Host to POD ICD Host to POD Adaptor Analysis (e.g. Coupled Loads, Orbit Raising and Separation, Thermal) Integration of MicroSatellite to SSL Satellite Integrated testing SSL I&T security Launch Vehicle Contract ITAR / Export Control Paperwork Delivery of MicroSatellite to Launch Base Joint Launch Base Operations including Bi-Prop Loading if necessary Launch of MicroSatellite to GTO or Near-GEO Orbit 16

17 User s Guide Summary Table MicroSatellite Parameter Typical Value User Value Launch Frequency 6-8 SSL Launch Opportunities per year Maximum Volume 1m x 0.5m x 0.4m (Standard Sizing) Maximum Mass Center of Mass Available power State During Launch Data Connection Thermal Environment Launch Dynamics Ejection Speed Maximum Tumble Rate Dispensing Orbits Available Range Accuracy of Drop-Off In-track accuracy Release pointing accuracy Deployment Video Available 1m x 1m x 0.6m (Extended Sizing) 90 kg (Standard Sizing) 150 kg (Extended Sizing) Within 15 cm of MicroSatellite geometric center in any axis 150W average, 300W peak; V Off MIL-STD-1553 (optional); other interfaces possible -35 C to + 60 C non-operating + aero-thermal heating during launch Acoustic, static, vibration, shock envelope of common launch vehicles (Ariane 5, Proton, Falcon 9, Atlas) ~0.25 m/s 0.5 deg/sec/ axis GTO (at apogee), near GEO (300 km sub or super) 100 m 2 km 5 degrees per axis Yes 17

18 Summary The Payload Orbital Delivery System (PODS) enables cost-effective, hightempo access to GTO or GEO for MicroSatellites 6-8 launch opportunities per year with SSL Cost-effective access to GTO & GEO combined with recent advances in MicroSatellite technology enables many potential future missions SSL welcomes input from Users: In developing and co-proposing mission concepts that can take advantage of this unique platform Working with MicroSatellite providers to address mission-specific needs 18