FLIGHT DYNAMICS TOPICS Erika Rossetto – Star One

1. FLIGHT DYNAMICS TOPICS Erika Rossetto – Star One

2. FD Working Group • Erika Rossetto (Star One) • Dean Hope (Inmarsat) • Joe Chan (Intelsat) • Pascal Wauthier (SES) • David Zamora (Eutelsat) • Brian Swinburne (Astrium) • Lorenzo Arona (Avanti)

3. Activities • Meeting last June: • Possible improvements for CA; • Status of SDA’s Third-Party Space Data Search; • Security Versus Usability:  Concepts and Alternatives; • Improving communication between members; • Along 2014: • Meetings with Airbus, Boeing, ISODEX, GMV, ComSpoc, ISON.

4. OnorbitSummary • 334 launches in 2014 X 75 in 2009 In 2009, about 13000 objects cataloged, currently more than 17000! • SDA numbers • CA runs executed: 3452 • Conjunctions detected: 4166725

5. FD aspects on SDA • Space Data Association • Cooperated with other satellite owners/operators orbit ephemeris including maneuver effects • TLE to supplement drifters and non-cooperated satellites • Conjunction alerts currently based on miss-distances only • Monitoring to 7 day time span

6. FD aspects on SDA • OD Evaluation • Initially, then at least once a year

7. FD aspects on SDA • Ephemeris-TLE comparison • Discrepancy in ephemeris data • Time of last upload

8. FD aspects on SDA • CDM analysis Usingoperator’sephemeristoprovide a more realisticconjunctionanalysis

9. FD aspects on SDA • SDC plug-in allows the operators analyze CDM by themselves

10. FD aspects on SDA

11. FD aspects on SDA

12. Summary • FD working group has worked to help SDA provides a better service; • The FD aspects has been improved since last meeting; • SDA adds a valuable contribution for safety of satellite community.

13. SDA Users Meeting: SDA General Forum Status of SDC and the SDC PluginDan Oltrogge

14. SDA Objectives From 2014 • SDA • Grow Membership • Develop Government and Industry Relationships • Develop Space Insurance Relationships • Secure Access to Additional Data Sources • SDC • Rehost the SDC to Amazon Cloud • Reduce Operating Costs and Improve Service • Implement Data Sharing for RFI Mitigation • Carrier ID Database Prototype for FIFA World Cup

15. SDA Objectives From Last Year … • SDA • Grow Membership • Develop Government and Industry Relationships • Develop Space Insurance Relationships • Secure Access to Additional Data Sources • SDC • Rehost the SDC to Amazon Cloud • Reduce Operating Costs and Improve Service • Implement Data Sharing for RFI Mitigation • Carrier ID Database Prototype for FIFA World Cup

16. Space Data Center (SDC) • The SDC is the processing system of the SDA • SDC – Three Key Mission Areas: • Collision avoidance monitoring (Conjunction Assessment)/ Maneuver Planning Validation / Flight Safety • Radio Frequency Interference mitigation / Geolocation support • Contact information (operations center) for SDA Members • SDC reliable and secure operation: • High level data security and encryption • Geographically separated redundancy • SDC services redundancy

17. SDC Demo: Home Page…

18. Year-in-Review: SDC Achievements • Developed, tested & deployed Amazon SDC in 8 months • Transitioned from Rackspace to Amazon Web Services (AWS) • Transitioned SDC DB from MS SQL Server to Oracle (AWS RDS) • Conducted shadow mode operations • New SDC self-signed certs for improved ops & reduced cost • New Sophos Unified Threat Mgr (UTM) for all SDC transactions • Upgraded SDC Plugin for new Conjunction Data Message (CDM) • Drafted Orbit Hybrid Message under ISO/CCSDS auspices • Carrier ID Database and RFI Precomputed Sol’n Set prototypes • On-going SDC operations: • Four new operators w/ new ephemeris converters etc. • CDM & TLE comparisons, ephem. quality monitoring, OD verifications • JSpOC dialogue for CDM & TLE comparisons, cross-tags & issues • Coordinating SSA Data Sharing w/USSTRATCOM & JSpOC • Space debris mitigation & research (Iridium 47,91 & DMSP, spatial dens)

19. SDC Rehost to Amazon • December 2013 • Amazon configuration • January/February 2014 – Conversion begins • Login/Ephemeris conversion • April/May 2014 • CA conversion • June 2014 • SDC AWS testing and performance tuning • July 2014 • SDC AWS Shadow Operations • New self-signed security certificate implementation • August 2014 • SDC AWS live operations

20. SDC Transition to Amazon Cloud • Substantial SDC hosting cost reduction • Multi-region (continent), dual-AZ topology • Amazon AWS regions are separate geographic areas • Each region has multiple, isolated locations known as Availability Zones, connected by low-latency links.

21. AWS High Availability • Window Application Servers • All SDC Windows services redundant across multiple AZs • Ephemeris Processing • Conjunction Analysis • Data Retrieval • Message Processing • All AZ instances process queued jobs on FIFO basis. • AWS CloudWatchmonitors Windows service health. • Any Windows service outage covered by other AZs. • Can perform system maintenance w/o SDC outage ! • Amazon RDS automatically replicates SDC DB and recovers from DB failure scenarios for Multi-AZ deployments w/o administrative intervention

22. SDC Security on AWS • SDC system security is a SDA priority • The SDC incorporates by design layered security and defense-in-depth strategies (monitoring, alerting, disaster recovery and forensic analysis) to help ensure a trusted and secure environment • Greatly reduces susceptibility to FREAK-style attacks

23. SDC Plugin • SDC Plugin provides easy access to user-friendly, tailored analysis of SDA member data • Augments SDC rich repository of SOAP and REST web services for automated machine-to-machine interface • Allows SDC users to obtain any/all SDC data they are authorized to access • SDC ephemerides and maneuvers populated by operators • SDC RF parameters and RFI alerts to be populated as well. • Automatically ingests JSpOC CDMs and performs 9-way comparisons of conjunctions and two 3-way positional compares • Upgraded SDC Plugin for JSpOC CDMs July 2014 • Free to SDA members; requires business-level STK-Pro license

24. SDA Users Meeting, 16 March 2015 RFI Mitigation FUNCTIONS in the sdcSteve Smith and Dan Oltrogge

25. Reference signal SDC/RFI – Introduction • RFI background • RF interference is the major operational problem affecting customer services on geostationary satellites • ~85-90% of customer issues are due to RFI • RFI only affects a small amount of capacity but has a cost and service impact if not quickly resolved • Investigating RFI is time consuming – we are always seeking methods and processes to improve response • Geolocation – key mitigation technique • One of the main techniques used to identify interfering signals • Requires precise satellite ephemeris data for ‘affected’ and adjacent satellites • Needs RF payload data for ‘affected’ and adjacent satellites Adjacent satellite My Satellite The signal we want to locate Monitoring station(s)

26. SDC/RFI – Geolocation Support • How can SDC help with geolocation? • Investigation often needs accurate RF data on other satellites • SDC already contains the precise ephemeris data • Need to extend data sharing to include RF payload data • SDAalready has a means of securely holding and exchanging data with the users • It already has a legal framework to protect user’s data • SDC pre-computed geolocation solution sets • Analyze an RFI event submitted by an SDC user • Use knowledge of payload data for all satellites, to provide a ranked order of geolocation scenarios, to input into the user’s geolocation system

27. Normalized RF Data & Approach • Gathered relevant RF input data • SDA/AGI developed standardized Excel templates • Eutelsat, Intelsat, SES submitted payload RF data for handful of satellites • AGI developed analytical software EMISSION for geolocation pre-computation

28. SDC/RFI – Carrier ID Database • Prototype hosted by SDC for World Cup 2014 • Operational database required in preparation for SNG CID users in 2016 (FCC ruling)

29. SDC/RFI – Planned Functions

30. EMI Solution Set Identification of Optimal Neighbors (EMISSION) • EMI is chief concern for SatComm operators • RFI mitigation initiatives • Inter-operator satellite operator Carrier ID Database • Equipment install training/cert programs • Geolocation of interfering signals • Constructing a geolocation “Solution Set” w/normalized inputs can take days to weeks • “EMISSION” Tool constructs in minutes • Authoritative ephemerides + maneuvers + RF data + antenna patterns + aggregate reference emitters + geolocation sites + STK & ODTK under the hood

31. EMISSION Tool • SDA is ideal trusted framework for behind-the-scenes RF analytics such as “EMISSION” • Large quantity of proprietary RF data req’d: Neighbor S/C #2 Neighbor S/C #1 Interfered S/C ⁞ GeolocSites Geoloc_01 Geoloc_02 ⁞ GeolocSites Geoloc_01 Geoloc_02 ⁞ GeolocSites Geoloc_01 Geoloc_02 ⁞ S/C Chars Ephemeris Covariance Maneuvers ⁞ S/C Chars Ephemeris Covariance Maneuvers ⁞ S/C Chars Ephemeris Covariance Maneuvers ⁞ Rank-ordered solution sets by Ix region & location Ref Emitters Calibrator_01 Calibrator_02 ⁞ Transponder Connectivity Conn_01: U/L Channels, D/L mapping, LOs, Antenna Patterns ⁞ Ref Emitters Calibrator_01 Calibrator_02 ⁞ Transponder Connectivity Conn_01: U/L Channels, D/L mapping, LOs, Antenna Patterns ⁞ Ref Emitters Calibrator_01 Calibrator_02 ⁞ Transponder Connectivity Conn_01: U/L Channels, D/L mapping, LOs, Antenna Patterns ⁞ EMISSION Interfered S/C Geoloc Site Predicted Perf Score Rank Neighbor S/C Ref Emitter #2 ⁞ Ref Emitter #1

32. EMISSION Process Flow ⁞ ⁞ - - - - SDA Trusted Framework - - - SDA Trusted Framework - - - SDA Trusted Framework - - - - - SDC Operator-Proprietary Orbit DB SDC Operator-Proprietary RF DB Satellite Operator Operators populate and maintain their authoritative RF data and antenna patterns Interf S/C Orbit & ΔV Data Neighbor S/C #2 RF Data Neighbor S/C #1 RF Data Neighbor S/C #2 RF Data Neighbor S/C #1 RF Data Interf S/C RF Data ① - - - - - - - - - - SDC Trusted Framework - - ② Operator specifies Ix S/C Freq, Polarity ③ - - - - - - SDA Trusted Framework - - - - - - SDA Trusted Framework - - - - - ⑦ ④ RF data and antenna patterns Operator-proprietary SDC orbit ephemeris & maneuver data Rank-Ordered Geolocation Solution Sets - - - - - - - - - - - - - - - - EMISSION ⑤ Assess geolocation performance ⑥ Viable candidate solution sets • STKX/Object Model • STK Comm: • C/N, C/No, EbNo etc. • STK for chain access/visibility • Simulate TDOA/FDOA • Extended Kalman Filter • Estimates geolocation performance • Incorporates S/C, ΔTAT, meas & geolocerrors - - SDA Trusted Framework - - - - - - - - - - - SDA Trusted Framework - - - - - - - SDA Trusted Framework - - - - - - - SDA Trusted Framework - - - - - - - -

33. Reference signal EMISSION/STK Viable Candidates • To be viable neighboring geolocation satellite, need Local Oscillator commonality Adjacent satellite My Satellite EMISSION auto-ingests each S/C’s full RF parameters and antenna patterns and instantiates only those channels with LO commonality LO C LO 3 Viable Reference Emitter Frequency LO B LO 2 Freq (MHz) Interference Frequency LO A LO 1 Monitoring station(s) Interfered S/C Neighbor S/C

34. Complete Specificity of S/C RF …

35. Status and Next Steps • EMISSION now able to ingest operator RF parameters and instantiate “heavy” STK Comm objects for full RF analysis • In process of hooking up fully-functional ODTK TDOA/FDOA filter to evaluate geolocation performance at interference site. • Operators/AGI explore suitability of candidate geolocation solution set viability metrics (C/N vs C/No vs EbNo vs …) • Operators/AGI conduct operational tech evaluations of prototype • When validated, AGI will develop final EMISSION software • Implement web and windows services to populate required RF params • Operators to develop methods to routinely load RF data to SDC using new SDC windows services

36. SDA New Product Development John Mackey March 16, 2015

37. Today: SDA Missions • Increase safety of flight – functions already operational • Automatic Conjunction Assessment (CA), using operator’s ephemeris • Reduce false alarms, missed events • Minimize time and resources devoted to CA • Include planned maneuvers (unique capability) • Deal with the growing problem of RFI – ongoing development • RFI Alerts to focused distribution • RFI historical event search: data support • Generation of geolocation data sets from high quality ephemeris • Library of Reference Emitters • Carrier ID database • Reliable contacts for satellite operators – functions operational • Encourage and promote operational best practices SDA Enhances its Members’ Satellite Operations

38. SDA – A Trusted Platform • Over the last 5 years, SDA has built a trusted platform for the secure exchange of satellite operational data • Technical infrastructure of the SDC: security, data access, etc. • Legal structure and agreements that provide protections and enforcement mechanisms to ensure that data is only used for intended purposes • These are UNIQUE CAPABILITIES • What opportunities exist to leverage our investments to generate new value for our current and future members?

39. SDA Evolution • No Decisions Taken Yet! • But consensus view of Directors is that the SDA should evolve into new areas & applications that build on our capabilities • Some of the Ideas & Concepts: • Geolocation As A Service • Interference Event Database • Inter-operator sharing of cyber-threat data • Ground infrastructure database • Occasional Use Capacity Finder • Aggregation of space weather observations • Space Based SSA sensor data consolidation

40. Next Steps • Continue to collect ideas & concepts • Evaluation / Prioritization • Dialog with members (and potential members) • Identification of enabling technologies • Business case development • How can you help? • Reach out to us with your ideas & thoughts: John.Mackey@inmarsat.com

41. Government Activities March 2015

42. Government 2014 Accomplishments • Signed groundbreaking SSA data sharing agreement with U.S. Government • USG signed 1st agreement with non-satellite operator • Attended multiple meetings with U.S. Government entities to discuss SSA data sharing, including EMI challenges • JFCC Space Operator talks – Enhance communications with satellite operators; better collaboration. SDA has participated in all meetings. • Meetings with senior leaders – promote better collaboration • FAA/STPI/IDA – space traffic management

43. Government 2014 Accomplishments, cont. • Participated on multiple panels to promote SDA and data sharing • AMOS • Secure World Foundation/IFRI • SIA DOD Commercial SATCOM Workshop • U.S. – Japan Space Cooperation Workshop

44. Government 2014Data Sharing Agreement • Groundbreaking Agreement • Allows SDA close collaboration with USG to, e.g. exchange higher quality data than publicly available • Orbital Data Request (ODR) submitted • SDA / USG: Multiple technical discussions on data to be shared • Objective: Optimal data shared – Combine aspects of JSpOC catalog plus satellite operator and maneuver data (SDC) • Exploring best technical means to exchange data between JSpOC and SDC for flight safety

45. Government 2015 • Begin sharing data with JSpOC • Continue discussions with U.S. Government regarding best practices • Continue to engage governments outside of the U.S. in dialog to share relevant data and explore emerging issues such as EMI/RFI mitigation • Enlist government and civil agencies who operate satellites to join the SDA

46. SDA Current Participants Multi-national, open to all space operators, in all orbital regimes The Space Data Association (SDA) is a not-for-profit association formed by satellite operators to provide reliable and efficient data-sharing critical to the safety of the space environment and the RF spectrum *Data Contributors

47. 2014 Debris Events Dr. T.S. Kelso SDC Operations Manager

48. Summary of 2014 Events

49. Notable Events: Iridium 47 • First public TLEs: 2014 Sep 26 • Event occurred: 2014 Jun 7 @ 0330 UTC • Operational satellite • Reportedly remains operational • Recent optical SOI shows still stable

50. Notable Events: Iridium 91 • First public TLEs: 2014 Dec 3 • Event occurred: 2014 Nov 30 @ 1615 UTC • Operational satellite • Reportedly remains operational • Recent optical SOI shows still stable