1. THEMIS FDMO CDR Peer Review − Management Topics 1June 1-2, 2004 Management Topics Manfred Bester

2. THEMIS FDMO CDR Peer Review − Management Topics 2June 1-2, 2004 Management Topics Overview Ground System Schedule Personnel Plan Ground Systems Costs IT Security Risk Management Document Status PDR Peer Review RFA Status

3. THEMIS FDMO CDR Peer Review − Management Topics 3June 1-2, 2004 Ground Systems Schedule THEMIS MOC and SOC Configuration During Phase C / D Development of Detailed Operations Plans and Procedures Flight Dynamics Software Configuration and Verification with GNCD Support FOT Training in Classroom and During Mission I&T End-to-end Data Flow Testing with NASA/GN and TDRSS Launch and Mission Simulations Dress Rehearsals Peak Activities In Phase D, Taper Down During Phase E

4. THEMIS FDMO CDR Peer Review − Management Topics 4June 1-2, 2004 Ground Systems Schedule

5. THEMIS FDMO CDR Peer Review − Management Topics 5June 1-2, 2004 Operations Org Chart All Aspects of THEMIS Operations Are Performed at UCB / SSL GSFC / GNCD Provides Support in Form of Consulting and Certification Additional Consulting Support by AI Solutions

6. THEMIS FDMO CDR Peer Review − Management Topics 6June 1-2, 2004 O&GS Team Members THEMIS Operations & Ground Systems Team –Mission Operations Manager (M. Bester) Mission Operations –Deputy Mission Operations Manager (M. Lewis) –Flight Controllers (M. Eckert, J. McDonald, T. Neal, J. Thorsness, TBH, TBH) –Programmer/Analyst (J. Din) –Student Aides (4) Science Operations –Science Operations Manager (T. Quinn) –Programmer/Analysts (J. Vernetti, TBH) –Student Aides (4) Flight Dynamics –Flight Dynamics Lead (S. Frey) –Flight Dynamics Engineers (J. McDonald, TBH, TBH) –Student Aides (2) Ground Station Operations –Ground Station Manager (R. Sterling) –Ground Station Technician (H. Bersch) –Student Aide (1) IT Network Systems –IT Network Systems Manager (J. Loran) –System Administrators (R. Boyd, W. Herrick, C. Quan, B. Satow, K. Edgecomb)

7. THEMIS FDMO CDR Peer Review − Management Topics 7June 1-2, 2004 Team Member Background Physics / Astrophysics / Astronomy Aerospace / Aeronautical Engineering Electrical Engineering Mechanical Engineering Computer Science Undergraduate Students

8. THEMIS FDMO CDR Peer Review − Management Topics 8June 1-2, 2004 Team Member Roles Roles and Responsibilities Operations Management Team Flight Operations Team Flight Dynamics Team Science Instrumentation Team Science Operations Team Engineering Support Team

9. THEMIS FDMO CDR Peer Review − Management Topics 9June 1-2, 2004 Management Team Duties of the Operations Management Team Interface with Project Management and Systems Engineering Oversee Mission Operations Oversee Science Operations Oversee Flight Dynamics Operations Oversee Ground Station Operations Oversee IT Network Systems Operations

10. THEMIS FDMO CDR Peer Review − Management Topics 10June 1-2, 2004 Flight Operations Team Duties of the Flight Operations Team Participate in Probe Integration and Testing as Test Conductors Support Launch and Mission Simulations Support Launch Operations Plan and Support Real-time Contacts Monitor Health and Safety of the Constellation and Each Probe Generate Command Loads Perform Probe Command and Control Functions Perform Probe Data Trending Analyses Interface with Science Instrumentation Team Interface with Science Operations Team Deliver Telemetry Data to the Science Operations Center Maintain Telemetry and Command Databases Maintain Probe Simulator Test Flight Software Patches and New Procedures on Probe Simulator Prior to Upload

11. THEMIS FDMO CDR Peer Review − Management Topics 11June 1-2, 2004 Flight Dynamics Team Duties of the Flight Dynamics Team Maintain and Archive State Vectors for the Constellation Perform Orbit Determination Perform Attitude Determination Oversee Generation of Mission Planning Products Perform Maneuver Planning Assist Flight Operations Team with Maneuver Execution Perform Thruster Calibration Perform Post-maneuver Analysis and Calibration Perform Propellant Bookkeeping Deliver Ephemeris Products to the Science Operations Center

12. THEMIS FDMO CDR Peer Review − Management Topics 12June 1-2, 2004 Science Operations Team Duties of the Science Operations Team Develop and Maintain Data Processing Software Assess Completeness of Recovered Science Data Provide Feedback for Science Data Recovery to the Flight Operations Team Perform Data Processing Functions Perform Data Archiving Functions Generate and Distribute Media Provide Online Access to Archived Data

13. THEMIS FDMO CDR Peer Review − Management Topics 13June 1-2, 2004 Engineering Support Team Duties of the Engineering Support Team Monitor Health and Safety of Each Probe During Early Orbit Commissioning Provide Sustaining Engineering Support to the Flight Operations Team

14. THEMIS FDMO CDR Peer Review − Management Topics 14June 1-2, 2004 Science Instrumentation Team Duties of the Science Instrumentation Team Monitor Health and Safety of the Science Instruments Perform Instrument Data Trending Analyses Provide Feedback for Instrument Control to the Flight Operations Team

15. THEMIS FDMO CDR Peer Review − Management Topics 15June 1-2, 2004 MOC Staffing MOC Staffing During Launch & Early Orbit Operations UCB Flight Operations Team 24 Hour Staffing with Prime and Secondary Shifts Critical Commanding During Prime Shift Only Swales and UCB Engineering Team on Console During Prime Shift Instrument Scientists on Console During Instrument Commissioning Additional Support Teams Monitor Probe Status Remotely MOC Staffing During Normal Operations THEMIS Follows FAST / RHESSI / CHIPS Model Normal Operations Eventually Run with 8 x 5 Staffing Transition to Autonomous Operations After First Tail Season Orbit and Attitude Maneuvers Always Treated as Special Operations

16. THEMIS FDMO CDR Peer Review − Management Topics 16June 1-2, 2004 Ground Systems Costs Cost Effective Approach Based on Successful FAST / RHESSI / CHIPS Model Mission Operations, Science Operations, Flight Dynamics and Ground Station Operations Integrated Into One Coherent Facility Phase-in THEMIS Operations Team Gradually Hire New Personnel to Enlarge Existing Operations Team Ground Systems Costs Remain Within CSR Budget Ground System Development Fully Funded Required Trade Study Performed in Phase B

17. THEMIS FDMO CDR Peer Review − Management Topics 17June 1-2, 2004 Ground Systems Support Supporting Analyses RF Link Analysis Data Volume Analysis Ground Station and TDRSS Coverage Analysis Maneuver Analysis Tracking Accuracy Analysis Interface Control Documents Probe to Ground Stations Ground Stations to MOC MOC to SOC, FDC to MOC, FDC to SOC Support Agreements with Various Organizations NASA/GSFC GNCD (Code 570) NASA/GSFC MSP (Code 450) Ground Stations (WGS, MILA, AGO, HBK) and Space Network

18. THEMIS FDMO CDR Peer Review − Management Topics 18June 1-2, 2004 NASA GSFC/GNCD Support FDAB Support –Analysis of Orbit Determination Accuracy (M. Beckman) –GTDS Software Support (Updates) –GMAN Maneuver Planning Support (R. DeFazio) –Support of MSASS/MTASS (R. Harman) –Training of UCB Personnel (S. Frey) on GTDS –Training of UCB Personnel (TBH) on GMAN –Training of UCB Personnel (J. McDonald) on MSASS/MTASS –FDMO Peer Reviews (K. Richon) FDF Support –Assignment of BGS Transmit and Receiver Tracker IDs –Verification and Certification of BGS Two-way Doppler Tracking –Orbit Determination Support Following Launch GSFC/GNCD Support

19. THEMIS FDMO CDR Peer Review − Management Topics 19June 1-2, 2004 NASA GN and SN Resource Requirements in PSLA THEMIS PSLA Currently Reviewed by GSFC/MSP (Code 450) PSLA Under MSP Configuration Control Compatibility Test Van (CTV) for GN/SN End-to-end Testing Additional Documentation Requirements RF ICD (Probe to GN and SN) – Submitted to GSFC/MSP Network Requirements Document (NRD) − Draft in 2004 RF Compatibility Test Plan (CTP) − Draft in 2005 Data Flows and Scheduling for Ground Testing & Mission Operations Simulations Supported and Coordinated by GSFC/MSP Ground System Development Support of Experiments with Berkeley Ground Station to Determine Accuracy of Two-way Doppler Tracking GSFC/MSP Support

20. THEMIS FDMO CDR Peer Review − Management Topics 20June 1-2, 2004 AI Solutions Support Supply FreeFlyer Provide Spacecraft Definition Files for THEMIS Probes Provide Software User Training Flight Dynamics Support Maneuver Planning Operations Support

21. THEMIS FDMO CDR Peer Review − Management Topics 21June 1-2, 2004 Network Plan & IT Security NASA Network Security Requirements Driven by NPG 2810.1, Security of Information Technology GSFC IT Security Outlined in Document 290-004, IONet Access Protection Policy and Requirements Establishes IT Network Systems Security Measures and Controls for Access to Critical NASA Resources Documentation Requirements Information Technology Security, Risk Management and Contingency Plans Closed IONet Security Compliance Dedicated, Isolated Network and Workstations for TDRSS Access Configuration Control by System Administrator Network Certification and Scanning Personnel Screening

22. THEMIS FDMO CDR Peer Review − Management Topics 22June 1-2, 2004 Documents Relevant to Ground Systems Risk Management NPG 7120.5B, NASA Program and Project Management Processes and Requirements NPG 8000.4, Risk Management Procedures and Guidelines NPD 8700.1, NASA Policy for Safety and Mission Success NPG 8715.3, NASA Safety Manual NPG 2810.1, Security of Information Technology NPD 8621.1, Mishap Reporting and Investigating Policy NPG 8621.X (Draft), NASA Procedures and Guidelines for Mishap Reporting, Investigating and Record Keeping SP-6105, NASA Systems Engineering Handbook Risk Management Approach Continuous Risk Management (CRM) Identify, Analyze, Plan, Track and Control Risks Risk Management

23. THEMIS FDMO CDR Peer Review − Management Topics 23June 1-2, 2004 Risk Management Summary of Risk Areas and Vulnerabilities Risk AreaVulnerability Ground SystemsFacility Infrastructure (Physical Access, Power, HVAC) Network Access (T-1 Line, Open Internet, Firewalls) IT Security Natural Disasters (Earthquake, Fire, Wind, Flood) Personnel Safety Berkeley Ground Station External Ground Stations Interfaces to External Scheduling Offices Access to NORAD Orbital Elements Generation of Ephemeris and Mission Planning Products Command and Control Systems (ITOS, MPS) Emergency Response Systems (SERS, Email, Paging Services) Operating Systems Systems Automation Flight Software Simulators

24. THEMIS FDMO CDR Peer Review − Management Topics 24June 1-2, 2004 Risk Management Summary of Risk Areas and Vulnerabilities Risk AreaVulnerability Flight SystemsPower Systems Attitude Control Systems Communications Systems Sensors Flight Computers Flight Software Instruments Instrument Computers Solid State Recorders Safe Modes Work-arounds Natural Disasters (Meteorite Hits, Solar Events) On-orbit Accidents (Collisions)

25. THEMIS FDMO CDR Peer Review − Management Topics 25June 1-2, 2004 Risk Management Summary of Risk Areas and Vulnerabilities Risk AreaVulnerability ProceduresNormal Operations Procedures Contingency Procedures DocumentationNormal Operations Procedures Contingency Procedures Personnel and Facility Contact Lists Interface Control Documents Circuit Diagrams Test Reports On-line Manuals Lessons Learned Database PersonnelTraining and Experience Personnel Turn-over (Preservation of Know-how) Personnel Workload Personnel Management Communications within Team BudgetAdequacy of Financial Resources

26. THEMIS FDMO CDR Peer Review − Management Topics 26June 1-2, 2004 Risk Analysis Estimate Likelihood (Probability), Consequences (Impact) and Time Frame in Which Action Must Be Taken to Prevent Harm Results of Analysis Stated Quantitatively to Facilitate Assignment of Priorities Priorities Calculated by Multiplying Assigned Impact (1-5) by Assigned Probability (1-5) with GPMC Assigned Colors Probability 5510152025 448121620 33691215 2246810 112345 12345 Impact

27. THEMIS FDMO CDR Peer Review − Management Topics 27June 1-2, 2004 Risk Mitigation Provide Operational Redundancy in Ground Systems Provide Online Back-up Systems Where Practical Purchase Spares of Critical, Single String Items, if Practical Gradually Replace Unreliable or Obsolete Equipment Perform Regular Hardware Systems Maintenance Provide Back-up Power Provide Multiple Workstations for Telemetry and Command Support Keep Versions of Operating Systems and Operational Software Up-to-date Back-up MOC at GSFC Conduct Interface Tests at Various Stages RF and Data Compatibility and End-to-end Data Flow Tests Probe Replacement Powerful Option to Increase Probability of Mission Success

28. THEMIS FDMO CDR Peer Review − Management Topics 28June 1-2, 2004 Risk Mitigation Begin Operations Team Training Early in the Program Participation as Test Conductors During I&T Extensive Probe Simulator and Classroom Training Flight Dynamics Training and Certification by NASA / GSFC GNCD Team Member Certification for Operational Readiness Collaborate Closely with Swales and Hammers TLM / CMD Database, ITOS Page and Procedure Development & Testing Remote Probe Monitoring Communications Between Team Members Encourage Open Communications Amongst Team Members Take Advantage of Lessons Learned Database System Regular Access to NASA LLIS

29. THEMIS FDMO CDR Peer Review − Management Topics 29June 1-2, 2004 Status of Relevant Documents Required DocumentAssigneeDue DateStatus THEMIS Mission Requirements Document (MRD)TaylorJun 2004Signed THEMIS Information Technology Security Plan (ITSP)BesterFeb 2004Signed THEMIS Project Data Management Plan (PDMP)QuinnMay 2004Draft THEMIS Project Service Level Agreement (PSLA)GSFC/451May 2004Draft THEMIS RF Interface Control Document (RFICD)BesterMay 2004Draft THEMIS RF Compatibility Test Plan (RFCTP)GSFC/450May 2005 THEMIS Network Requirements Document (NRD)GSFC/451Aug 2004 THEMIS Command Format SpecificationTaylorJul 2003Draft THEMIS Telemetry Data Format SpecificationTaylorOct 2003Draft THEMIS Telemetry Packet Data Format SpecificationTaylorSep 2003Draft THEMIS Ground Systems Interface Control DocumentBesterJun 2004Started THEMIS Ground Operations CoordinationLeBoeufOct 2003Signed THEMIS Mission Operations Plan (MOP)BesterAug 2004 THEMIS Mission Operations Support Plan (MOSP)BesterOct 2005 THEMIS Contingency PlanBesterOct 2005

30. THEMIS FDMO CDR Peer Review − Management Topics 30June 1-2, 2004 FDMO PDR Peer Review RFAs RFATitleRationaleReviewerResponseStatus FDMO-1Investigate monthly lunar perturbation effects to determine optimal time during month to launch. Lunar perturbations can be used to reduce fuel required if judicious selection of launch date is made. However, lunar perturbations can also increase fuel required by decreasing orbit energy & negatively impacting orbit inclination. RichonThe THEMIS team has already built tools which allowed investigation of lunar perturbations on orbits P1, P2 and P3 as well as on the LV insertion orbit in order to minimize potential for re-entry on the science orbits, and to maximize the potential for re-entry within 10 years for the LV to adhere to orbital debris requirements. Lunar effects due to different launch dates on the P3, P4 and P5 orbits were found to be very small. CLOSED FDMO-2Decide on one pre-injection nomenclature for each probe. Should not be names associated with integers 1-5 since the probes will be numbered Probe 1, Probe 2, etc. post-launch according to their final orbit positions (similar to TDRSS). Currently probes are designated as “Themis 1, Themis-2,…”, “red,green…”, and “A,BC…”. Multiple names for same probe causes confusion & misidentification of specific probes. RichonThe team agreed that the pre- launch assignment of probe names shall be THEMIS A-E. These names are uniquely related to the CCSDS telemetry and command IDs for each probe bus. Probe constellation IDs P1-P5 are assigned post-launch, once the probes and their instruments have been checked out and the probe placement decision has been made. CLOSED FDMO-3Resolve time tag issue.HarmanThe THEMIS attitude sensor read- out timing and attitude determination system is closely modeled after the FAST system which has been operational on orbit for 7.5 years. CLOSED

31. THEMIS FDMO CDR Peer Review − Management Topics 31June 1-2, 2004 FDMO PDR Peer Review RFAs RFATitleRationaleReviewerResponseStatus FDMO-4Get initial 3 rd -stage separation states (attitude & orbit) for each probe from Boeing. Needed for orbit injection analysis. If Delta PMA is being done, these states should be available soon. RichonUCB received the nominal launch trajectory ephemeris from KSC. These data are used to perform subsequent studies such as communications coverage and probe re-contact analyses. CLOSED FDMO-5GMAN modeling issues: define each ‘maneuver mode’ including type of maneuver, which thrusters used, pulsed/continuous, etc. Then determine if GMAN can model maneuver correctly. Several questions regarding whether GMAN can be used to model finite maneuvers in all maneuver configurations. RichonAll anticipated orbit and attitude maneuvers have been summarized and analyzed. Bob DeFazio verified that all planned maneuvers can be modeled with GMAN. CLOSED FDMO-6Determine ground station contact tracking requirements such as pass frequency & duration, number of stations, for maneuver planning & recovery versus regular OD, etc. RichonMark Beckman performed an OD covariance analysis showing the number of passes and arc lengths required to meet THEMIS OD 3-σ position requirements of 100 km near apogee and 10 km near perigee. In case of the P1 orbit, the required position accuracy can be achieved with 4 BGS passes taken over a 5.5-day arc. Some of the orbit fine tuning maneuvers require a delta V of 30-50 cm/s. An adequate pre-maneuver orbit solution can be obtained by collecting two-way Doppler data from three different ground stations, e.g. Berkeley, Wallops Island and Santiago. Further analyses are under way. CLOSED

32. THEMIS FDMO CDR Peer Review − Management Topics 32June 1-2, 2004 FDMO PDR Peer Review RFAs RFATitleRationaleReviewerResponseStatus FDMO-7Determine UCB station capabilities including support for perigee passes. Mission depends heavily on UCB antenna for tracking. Need to know if orbit determination constraints can be met. RichonTwo-way Doppler tracking capabilities of the Berkeley Ground Station were demonstrated with equipment on loan from Wallops Flight Facility. The 1-σ error of range rate measurements is expected to be 3.5 mm/s in a 10-s integration time. Due to the low orbital inclination the maximum azimuth and elevation rates during a pass support will be less than 0.5 deg/s. The Berkeley Ground Station is capable of tracking with maximum azimuth and elevation rates of 8.0 and 3.0 deg/s, respectively. CLOSED FDMO-8ITOS-to-MSASS interface code to be provided to UCB. Harman used successfully for other mission. RichonUCB will provide interface code to extract attitude sensor data from ITOS and reformat these to be compatible with MSASS/MTASS input. CLOSED FDMO-9Real-time attitude determination - is this a requirement? If so, which software? Possibly use MTASS with modifications. HarmanReal-time attitude determination is required for maneuver support. A ground-based real-time ADS will be implemented, based upon the quaternions that are derived from sun sensor and IRU data and are propagated on-board, and are in turn sent to the ground. CLOSED

33. THEMIS FDMO CDR Peer Review − Management Topics 33June 1-2, 2004 FDMO PDR Peer Review RFAs RFATitleRationaleReviewerResponseStatus FDMO-10Multi-satellite critical operations: need to have at least two prime workstations supporting, plus at least one hot back-up for emergencies. Normally one has one prime and one back-up for any critical operation for a single-satellite mission. UCB will have to be able to support multiple satellites with critical operations. RichonThe ground systems design includes at least 10 ITOS workstations, including a designated prime and back-up for each probe. Furthermore, any of these workstations can be assigned to any probe. In addition, two ITOS workstations will be connected to the Closed IONet for communications via TDRSS with one probe at a time. CLOSED FDMO-11MSASS is not capable of performing magnetometer alignment. Determine if UCB needs to acquire MTASS in addition to MSASS for this function. HarmanUCB will obtain ADS which includes both MSASS and MTASS. A software usage agreement is in the process of being finalized. CLOSED FDMO-12Include pre-launch operations (Simulation planning & support, launch preparations) in future FD&MO reviews. Ensure resource requirements are identified & included in planning. RichonPre-launch operations and simulations including green card exercises were included in the MPDR presentations already and will be presented in more detail in upcoming reviews. CLOSED FDMO-13Provide access to latest mission information to peer panel at least two weeks before review. RichonThe review team will receive most recent mission documentation at least two weeks prior to future peer reviews. CLOSED

34. THEMIS FDMO CDR Peer Review − Management Topics 34June 1-2, 2004 FDMO PDR Peer Review RFAs RFATitleRationaleReviewerResponseStatus FDMO-14Maneuver calibration procedures need to be documented. Each orbit & attitude maneuver should be analyzed post-maneuver for efficiency & accuracy. Results should be applied to future maneuver planning. Also needed for bookkeeping of fuel used. RichonThe UCB team has received sample procedures from GSFC FDAB and from Swales for EO-1 maneuver planning and execution. Applicable elements of these procedures will be incorporated into the THEMIS procedures. CLOSED FDMO-15Document who is responsible for fuel-used bookkeeping (propulsion engineer or Flight Dynamics Engineer or other FOT member). One entity should have responsibility for this function. It is particularly critical at the end of life when probes must perform a controlled reentry. RichonA dedicated member of the THEMIS flight dynamics team, namely the propulsion engineer will be responsible for bookkeeping the fuel usage. CLOSED FDMO-16Institute Command Authorization Meetings (CAMs) for all orbit & attitude maneuvers. Requires participation & ‘signoff’ from all relevant subsystems & systems (FOT, flight dynamics, thermal, power, C&DH, scientists, etc.). Best practices. Reduces risk. RichonCommand Authorization Meetings (CAMs) will be held prior to any critical command operation, including execution of orbit and attitude maneuvers as well as critical instrument operations such as boom deployment or HV turn- on. Such meetings are common practice already with all missions currently operated by UCB, i.e. FAST, RHESSI and CHIPSAT. CLOSED

35. THEMIS FDMO CDR Peer Review − Management Topics 35June 1-2, 2004 FDMO PDR Peer Review RFAs RFATitleRationaleReviewerResponseStatus FDMO-17Provide MAP Anomalous Forces technical paper to UCB. Outgassing of instruments & other hardware may introduce anomalous forces creating torques on probes). RichonUCB received a copy of the MAP anomalous force paper. CLOSED FDMO-18Provide JON/WBS to Code 595 for THEMIS support. Code 595 flight dynamics engineers cannot support THEMIS without charge number. Angelopoulos & Richon GNCD has received a JON for support of THEMIS flight dynamics support. CLOSED