System F6 Paul Eremenko Tactical Technology Office Defense Advanced Research Projects Agency (571) February 2010 Approved for Public Release. Distribution Unlimited.

1 Approved for Public Release. Distribution Unlimited. Program Goals Single Payload Monoliths Fractionated Cluster Fractionated Cluster Fractionatable Monolith Status quo Payload separation with no resource sharing or closed-loop cluster flight Monolithic spacecraft equipped with F6 Tech Package Heterogeneous distribution and sharing of bus & payload functions Infrastructure/Bus Support Function Distribution Mission/Payload Function Distribution LowHigh Low High Monolith  Replace monolithic satellites with wirelessly-networked, resource-sharing clusters –Develop & demo safe, efficient, and autonomous multi-body cluster flight techniques –Develop & demo secure/robust real-time distributed avionics capability over wireless links –Demonstrate a cyber security hardware/software paradigm to fortify the distributed and shared information infrastructure  Develop an F6 Developer’s Kit providing open interface standards & reference designs  Develop 24/7 LEO-to-ground communications capability  Develop a value-centric design and acquisition tool set

2 Technologies, Experiments, and Needs Approved for Public Release. Distribution Unlimited.

3 Flexibility Scalability Ability to scale system functionality in response to demand volatility. Ability to deploy incrementally. Ability to create systems bigger than launch capability. Evolvability Ability to respond to technological obsolescence through mid-life deployment of new functionality Adaptability Cluster reconfiguration can enable new functionality once system is on orbit Maintainability Ability to replace failed modules throughout the system’s lifecycle Approved for Public Release. Distribution Unlimited.

4 Survivability Graceful degradation of system functionality in response to hostile acts. Target spreading. Signature reduction. De-correlation of failure events across the system (e.g., “architectural self-insurance” during launch). Fault Tolerance Graceful degradation of system functionality in response to failure Robustness Approved for Public Release. Distribution Unlimited.

5 Payload Isolation Requirements decoupling across multiple payloads Simplified IA&T Reduced undesirable/unmodeled interactions during integration, assembly, and test (IA&T). Geographically- dispersed integrated testing. Reduced Barrier to Entry Enables small satellite manufacturers to create or participate in development of large systems. Increased number of competitive opportunities. Production Learning Mass production and learning effects across “infrastructure” modules may reduce unit costs Other Attributes Approved for Public Release. Distribution Unlimited.

6 F6 Payload Module F6 Infrastructure Module A F6 Infrastructure Module B F6 Tech Demo Self forming wireless network Distributed resource sharing Transfer of critical functionality Commanded cluster geometries Defensive “scatter” maneuvers Demo payload operation 3 rd Party Launch Launch of ORS/AFRL SARSat to common orbit 3 rd Party Module Entry Network authentication Autonomous cluster entry Fully functional payload operation ORS SARSat (3 rd Party) Module Terrestrial Infrastructure Third-Party Components High-Bandwidth Wireless Links Wired Links Relative Nav Sensing LEGEND F6 Demo Launch All three demo modules launched on dedicated Minotaur-IV Hosted SSAEM Payload Hi Data Rate Ground Comm Mission Processor 24/7 GEO Comm Relay Mission Processor Robust to ground interference Relative navigation Multi-level info assurance security Packet-level encryption GEO Comm Relay (Optional 24/7 TT&C) Low-Bandwidth Wireless Links Ground control system Payload tasker/user INTERNET/ SIPRNET Sustainment Additional payload and infrastructure modules for future operational capability 5 Hypothetical LEO Demo Scenario Approved for Public Release. Distribution Unlimited.

7 F6 Module A GEO Communications Satellite Third-Party Components High-Bandwidth Wireless Links Wired Links Relative Nav Sensing LEGEND F6 Demo Launch Two F6 demo modules launched as rideshare on STP EELV ESPA ring Co-Orbital Slot Entry F6 modules enter GEO slot of F6-enabled ComSat Network authentication Cluster geometry formation F6 Tech Demo Self forming wireless network Distributed resource sharing Transfer of critical functionality Commanded cluster geometries Defensive “scatter” maneuvers Hosted F6 Tech Package Robust to ground interference Relative navigation Packet-level encryption Missile Warning IR Payload Backup Subsystem Sustainment Additional payload and infrastructure modules for future operational capability 4 Terrestrial Infrastructure F6 Module B LaserComm Payload Upgraded Subsystem Multi-level info assurance security Geosynchronous Orbit Ground control system Payload tasker/user INTERNET/ SIPRNET Hypothetical GEO Demo Scenario Approved for Public Release. Distribution Unlimited.

8 Military Utility Summary Development Launch Operations Retirement Development Semi-Autonomous Operations TIME FRACTIONATED MONOLITHIC $ $ Semi-Autonomous Operations Incremental Deployment Component Upgrade Life Sustainment FLEXIBILITY ROBUSTNESS Increased Cost Development Nominal Launch Operations Retirement Launch Failure RebuildRelaunch Increased Cost Development Incremental Deployment Semi-Autonomous Operations Launch Failure Rebuild/ Relaunch TIME $ $ FRACTIONATED MONOLITHIC On Orbit Failure Cost Utility Payload Delay Launch Failure On Orbit Failure Decreased Utility due to: Cost Utility MISC ATTRIBUTES LaunchRetirement / Launch TIME $ $ Launch Payload Module Failure Event FRACTIONATED MONOLITHIC Failure Event Rebuild Relaunch Smaller per-module NRE reduces space industry barrier-to-entry Requirements decoupling between modules simplifies IA&T for large systems Residual on orbit infrastructure requires re-launch of payload only TIME Planned Reconstitution Relaunch Cost Utility Approved for Public Release. Distribution Unlimited.

9 Program Schedule TasksFY08FY09FY10FY11FY12FY13FY14 Phase 1: Concept & System Development Phase 2: Detailed Design Phase 3: Integration, Assembly, and Test Phase 4: Launch Integration & Demo PDR = Preliminary Design Review CDR = Critical Design Review Third-Party Residual Ops Launch1 Launch 2 (TBD) Third-Party Launch PDR and Go/No-Go HIL1HIL2 (* All principal design features simulated) HIL3* CDR and Go/No-Go HIL4 (** All software written, key hardware breadboarded) HIL5** FRR and Go/No-Go HIL6HIL7***HIL8 Third-Party HIL Demo (*** All software qualified, all hardware in EDUs) FRR = Flight Readiness Review HIL = Hardware-in-the-Loop Demo Approved for Public Release. Distribution Unlimited.

10 Approved for Public Release. Distribution Unlimited. Fractionated Space System Architecture