Space Network (SN) Access System (SNAS) Orientation & Training Part 2

1. Space Network (SN)Access System (SNAS) Orientation & Training Part 2 December 10, 2008

2. Agenda • Demand Access System • Overview • State Vector generation • Generate Resource Allocation Requests • Monitor Real-Time Operations • Generate Playback Requests • Scheduling Preparation • Import TDRS Unscheduled Time • Import TCWs / TSWs • Import PSAT/UAV to generate TSWs • Generate Use-defined TDRS Constraints • Import Bulk Schedule Requests • Graphical Timeline • Functionality • Scheduling adjustments

3. SNAS MOC Client Training Section 1Demand Access System Overview State Vectors SSCs Scheduling User Performance Data Playback Requests

4. SNAS – DAS Capabilities • SNAS primary customer interface for Demand Access System (DAS) • Provides mechanism for import or generation, and transfer of orbiting or stationary state vectors based on user input of geocentric (position & velocity) or geodetic (latitude, longitude, & altitude) coordinates • Supports full DAS/Mission Operations Center (MOC) interface for scheduling, service monitoring, and real-time control of DASMAR services • Provides local External Processing System (EPS) interface for manual or automatic exchange of DAS files between SNAS MOC Client and EPS directories

5. DAS Goals • The goals of the DAS are to provide: • Immediate access to TDRS 1-7 services by the customer • Extended duration services • Simplified resource scheduling and operation • Reduction of service cost • DAS capabilities allow new operational methods for: • 1) Immediate science alerts. • 2) Polling of spacecraft. • 3) Autonomous requests for MA service.

6. DAS Operations Concept (1 of 6) • DAS provides Customers with available time windows for MAR services • Dedicated Customers are always guaranteed service (i.e. dedicated customer requests can be allocated to resources that have already been previously allocated to a non-dedicated customer) • Non-dedicated Customer requests are assigned resources remaining after allocation to dedicated Customers • Customers access DAS through the SNAS MOC Client residing on a workstation in their MOC • Scheduling Concepts • Any TDRS: A single request will automatically generate continuous support coverage including all TDRS-to-TDRS transitions (handovers). i.e., one schedule for 3 years of continuous service • Set of TDRS: A single request for each TDRS within a set of TDRS that will provide continual overlapping global coverage. i.e., 3 schedules provides 3 years of continuous service • Specific TDRS: request using the conventional event-by-event support request to meet specific operational needs • Real Time Control and Monitoring • Ground Control Message Requests (GCMRs) for reacquisition and reconfigurations are provided through SNAS • User Performance Data is provided every 60 seconds for every DAS event scheduled though SNAS

7. DAS Operations Concept (2 of 6) • DAS via SNAS provides an interface to request Multiple Access Return (MAR) Services and retrieval of Archived Data Services for customer playback • DAS via SNAS serves as a Planning Tool and Scheduling Tool for users • Planning includes computation of customer emitter line-of-sight visibility time periods to TDRS and identification of TDRS handovers, if needed • Scheduling includes processing Customer requests for MAR or Playback services • DAS via SNAS will notify Customers on the status of all Scheduled and Ongoing Services, and Service Requests

8. DAS Operations Concept (3 of 6) • User Service Request and Scheduling • MAR Services may be requested up to 30 seconds prior to service initiation • For future time periods, the implication is that shared resources are available and there is TDRS line-of-sight visibility • An Active Service Schedule will be provided for all services being scheduled within 96 hours, updated as required • Based on last ephemeris, Dedicated Customers are scheduled up to 96 hours in advance • Based on last ephemeris, Non-Dedicated Customers are scheduled 72 hours in advance • If Non-Dedicated Customers are “bumped”, they will be notified • The Active Schedule shows Playback Services along with MAR services • Specific Event Details with applicable SSCs can be called up by a Customer for a scheduled MAR or a playback service

9. DAS Operations Concept (4 of 6) • Service States • Service States include Granted, Pending and Rejected • Granted – State Vector is current (within 96 hours) and resources are available • Pending – State Vector can not be propagated this far or is not current, or resources have not been identified • Rejected – No resources are available or TDRS requested is not available (all or nothing) • Pending applies to orbiting customer emitters and non geostationary platforms • Even when Granted, all non-dedicated customer services can be pre-empted • Service Modifications and Reconfigurations • DAS Customers may modify or delete requested services at any time • Once the service starts, a DAS Customer may request reconfigurations of most of the service configuration parameters (SSCs) in near real-time Should a receiver signal lose lock, DAS automatically attempts to reacquire the signal • A Customer may request a forced re-acquisition

10. DAS Operations Concept (5 of 6) • Customer Data Archiving - Nominal Operations • DAS provides real-time data to Customers during service • DAS also archives user data • DAS routes user data upon user request (i.e., no FTP access by users) at a rate dependent on the bandwidth that NISN IOnet can support • Users request data archiving duration in the Customer SSC for each SIC • SSC specifications address the length of time that user data is archived (7 days default; up to 30 days) • DAS automatically removes data when time expires or a default time is passed • Users are notified when their data storage duration limit is approaching • DAS generates an alert when the RAID storage capacity reaches some pre-determined threshold, and purging can be used to recover available storage capacity • At 95% disk full or at a specified preset threshold value, the DASCON takes proactive action to recover storage by deleting user data files - ‘first-in-firstout’ one by one to a level of 50% available storage space • DAS customers are notified beforehand, if this occurs

11. DAS Operations Concept (6 of 6) • Playback Planning & Scheduling Operations • To search for archived telemetry data files for Playback, the user provides Start and Stop times to be searched and the spacecraft identifier (SIC) • DAS will perform a search of all archived files for the specified SIC between the requested time window start and stop times • In response to a Playback Search Request, DAS will return a list of available files (time segments) for playback that fall within the time window • Each time a receiver loses signal LOCK, a file is closed; and a new file is opened when the receiver signal is reacquired • While this may present a large number of files for a customer to scroll through, it will be easy to quickly identify periods when no service was being provided • As a final step, the user can then select a specific single file for playback and then proceed with scheduling a time to download the file at a specified TCP port number and IP address

12. DAS and SDIF Status • System Status Indicators panel will automatically update showing the current connection state of the Client with the server processes such as SDIF • Graphic Status panel useful for determining SDIF-DAS connection status • Shows condition of all server processes but also provides status of SDIF used to exchange data to/from DAS for SIC

13. Orbital View & Vector (OVV) Options • Several options exist to import data into the local SNAS via the MOC Client (that gets stored into the SNAS database) • Manually generate • Geocentric and Geodetic State Vectors • Import from files • State Vectors (defined in SN/CSM ICD, table 9-2) • Improved Interrange Vectors (IIRV) (defined in SN/CSM ICD, table 9-2) • TDRS Communication Window (TCW) (defined in 452-ICD-SNAS/EPS, table 5-8 ) • Predictive Site Acquisition Table (PSAT) (defined in FDF ICD, table 4-3, and, 452-ICD-SNAS/EPS, table 5-6) • User Antenna View (UAV) (defined in FDF ICD, table 4-8, and, 452-ICD-SNAS/EPS, table 5-7) • TDRS Scheduling Windows (TSW) (defined in SN/CSM ICD, table 7-12)

14. State Vectors - Manual • State Vectors are used to transmit site prediction and satellite acquisition data used by NCC and DAS • Manually generated vectors • Geocentric vector panel Geodetic vector panel

15. State Vectors - Import • SNAS can import files with Type 1 through Type 8 vectors • Message type/class = 03/10 • Vector type • 1 = Routine on-orbit (free flight) • 2 = Forced (special orbit update) • 3 = Spare • 4 = Maneuver ignition • 5 = Maneuver cutoff • 6 = Reentry • 7 = Powered flight • 8 = Stationary • Coordinate System: Geocentric

16. ‘OVV’ Options – Importing Vectors • Once a menu option is selected file selection panel allows the user to locate and choose a state vector file for import into SNAS database and transmission to NCC, DAS, or Both

17. SSC Administration • SNAS DBA or MOC “Mission Manager” function used to maintain default SSC parameter values • Important for maintenance of DAS parameter values, since the values themselves are sent to DASCON rather than just the SSC code

18. SSC Administration – New Mission • When a SIC is created for a new mission using DAS by the WSC DBA, the SIC creation panel will automatically require the WSC DBA to enter values for a default SSC (provided by the mission) • Once the default DAS SSC is created, the SNAS Client generates 10 SSC copies using the default baseline so that the MOC Manager or WSC DBA can configure the additional SSCs without having to start from an empty template

19. SSC Administration – DAS SSCs (1 of 6) • Functionality provided to maintain default SSC parameter values by the SNAS O&M DBA or MOC Manager • Important for maintenance of DAS parameter values, since the values themselves are sent to DASCON rather than just the SSC code

20. SSC Administration – DAS SSCs (2 of 6) • There are five panels that are used to maintain the DAS SSC parameters with the General panel show here • The panels have context-sensitive that help provide the range for all fields permitting textual data entry

21. SSC Administration – DAS SSCs (3 of 6) • The 2nd panel provides entry for the Q-channel parameter values

22. SSC Administration – DAS SSCs (3 of 6) • The 3rd panel provides entry for the Data Format Parameter values

23. SSC Administration – DAS SSCs (5 of 6) • The 4th panel provides entry for the I-Channel Data Format Parameter values

24. SSC Administration – DAS SSCs (6 of 6) • The 5th panel provides entry for the Q-Channel Data Format Parameter values

25. DAS Scheduling – TDRS Visibilities (1 of 2) • DAS Scheduling starts with determining a TDRS Visibility • Selecting TDRS Visibility Request option, the user provides the window start and stop times, and TDRS ID (Maximum Lines limits the returned number of rows) • Selecting a TDRS of ‘ANY’ returns all TDRS IDs

26. DAS Scheduling – TDRS Visibilities (2 of 2) • A Resource Allocation Request (RAR) can be generated by highlighting a TDRS visibility row and clicking on Create Request • The scheduler can make adjustments to the Start and Stop times copied from the original visibility and Submit to DAS

27. DAS Scheduling – RAR (1 of 2) • A Resource Allocation Request (RAR) can be generated by selecting the RAR option from DAS Request list under Scheduling • The Resource Allocation Request panel appears with the current date occupying the Start Time and a Stop time of 14 days into the future

28. DAS Scheduling – RAR (2 of 2) • A Resource Allocation Request (RAR) can be generated by selecting the RAR option from DAS Request list under Scheduling • The Resource Allocation Request panel appears with the current date occupying the Start Time and a Stop time of 14 days into the future

29. DAS Scheduling – RAMR (1 of 2) • Using the RAMR option from the DAS Request list under Scheduling, the DAS Scheduler can select a RAR that has been Granted, and modify it with a Resource Allocation Modification Request (RAMR) • Select a RAR or RAMR and click on the Create Request button

30. DAS Scheduling – RAMR (2 of 2) • The RAMR panel appears with the supplied parameters from the selected RAR which the Scheduler can modify (Start or Stop times, or any of the SSC parameters), and then clicks on the Submit button to transmit it to the DAS

31. DAS Scheduling – RADR (1 of 2) • Using the RADR option from the DAS Request list under Scheduling, the DAS Scheduler can select a RAR or RAMR that has been Granted, and delete it from the schedule with a Resource Allocation Delete Request • Select a RAR or RAMR, and then click on the Create Request button

32. DAS Scheduling – RADR (2 of 2) • The RADR panel appears with the supplied parameters from the selected RAR which the Scheduler cannot modify, then clicking on the Submit button to transmit to the DAS

33. DAS Scheduling – PBKR (1 of 2) • Using the PBKS option from the DAS Requests list under Scheduling, the Playback Search panel is displayed for the Scheduler to enter the search range Start and Stop times • Click on the Submit button to send the search request to the DAS to find any available playback files

34. DAS Scheduling – PBKR (2 of 2) • The Playback Availabilities panel appears with a list of playback files that the Scheduler can then select from, and after supplying the Desired Transmit Start Time, Destination IP address and Port number, then click on the Create Request • A response will be sent back from the DAS indicating the request was supplied

35. DAS Scheduling – PBKMR (1 of 2) • Using the RBKMR option from the DAS Request list under Scheduling, the DAS Scheduler can select a PBKR or PBKMR that has been Granted, and modify the parameters of the initial request using a PBKMR • Once the PBKMR option is selected, a list of previous scheduled PBKR and PBKMR is displayed

36. DAS Scheduling – PBKMR (2 of 2) • The PBKMR panel appears with the supplied parameters from the selected PBKR or PBKMR which the Scheduler can modify, then clicks on the Submit button to transmit the request to the DAS

37. DAS Scheduling – PBKDR (1 of 2) • Using the RBKDR option from the DAS Request list under Scheduling, the DAS Scheduler can select a PBKR or PBKMR that has been Granted, and modify the parameters of the initial request using a PBKDR • Once the PBKDR option is selected, a list of previous scheduled PBKR and PBKMR is displayed

38. DAS Scheduling – PBKDR (2 of 2) • Selecting a PBKR or PBKMR from the list of DAS events then clicking on the Submit button the PBKDR is transmitted to the DAS after the confirmation panel is acknowledged

39. DAS Event Control/Monitoring (1 of 10) • Real-time Controllers can monitor the performance of the scheduled DAS events when a DASMAR service goes active when using the Active Schedule Summary panel • The DASMAR event will turn to green when the event goes active

40. DAS Event Control/Monitoring (2 of 10) • Selecting an active event, the Controller can view the services by clicking on the Display Services button • To view the event parameters being used click on the Parameters button to display the SSC

41. DAS Event Control/Monitoring (3 of 10) • The set of SSC parameters panels appear and selectable to view

42. DAS Event Control/Monitoring (4 of 10) • To generate a GCMR select the Generate GCMR button • The GCMR Menu appears allowing the Controller to select either a Service Reconfiguration or generate a Signal Reaquisition Request

43. DAS Event Control/Monitoring (5 of 10) • Selecting the Service Reconfiguration the Controller can modify the event’s parameters and transmit the reconfiguration to effect the on-gong event • A notification panel appears confirming that the request was sent

44. DAS Event Control/Monitoring (6 of 10) • Selecting the Signal Reacquisition Request option the Controller can sent out a reacquisition request • A notification panel appears confirming that the request was sent

45. DAS Event Control/Monitoring (7 of 10) • To view the event’s service periods select the Service Periods button

46. DAS Event Control/Monitoring (8 of 10) • An active event’s User Performance Data can be monitored by selecting the User Performance Data Summary option from under the Control/Monitor on the Main Control menu The UPD Summary panel displays events that have gone active and shows which services that may require action by the Controller

47. DAS Event Control/Monitoring (9 of 10) • The UPD Details panel displays the parameters of the selected event and shows parameters that are within or out of limits • The Controller can modify an events parameters by sending a Service Reconfiguration request or send a Signal Reacquisition request by clicking on the Submit GCMR button (see slides 42 – 44)

48. DAS Event Control/Monitoring (10 of 10) • To set user defined limits for monitoring UPDs select the UPD Parameter Warning/Critical Range Summary page • The Range Summary page appears allowing the Controller to reset low and high range limits for warnings and critical levels

49. SNAS MOC Client Training Section 2Scheduling Preparation Overview Retrieving TUTs Import PSAT/UAV Generating TSWs from PSATs/UAVs Import TCWs/TSWs Generating Bulk SAR File using Recurrent Scheduling Ingesting Bulk Schedule Files

50. Scheduling Preparation • Typical Scheduling Process • Retrieve TUT information • TCW conversion to TSWs • Import Orbital Data Products • Generate or import TSW file • Update TDRS user constraints (manually) • Generate SARs (manually or by importing a bulk file) • Review NCC SRM / USM status • Correct Requests using RRs or SDRs