1. 4593-4 Sept. 2008EFW INST+SOC PDR RBSP EFW SOC and ConOps Science Operations Center and Concept of Operations (SOC and ConOps) John Bonnell Space Sciences Laboratory University of California, Berkeley

2. 4603-4 Sept. 2008EFW INST+SOC PDR EFW SOC and ConOps Outline Science Operations Center (SOC) –Requirements –Organization –Description: Data Products Data Processing Flow –Development: Schedule and Milestones Test Plan Status EFW Concept of Operations (ConOps) –Instrument Commissioning: Turn-On and Check Out Boom Deploys –Nominal Operations: Conditions for Nominal Operations State-of-Health Monitoring and Trending Commanding and Day-to-Day Operations

3. 4613-4 Sept. 2008EFW INST+SOC PDR EFW SOC Requirements The EFW SOC allows the EFW SOC and Science teams to: –Process and distribute EFW science data in a timely, accurate, and configuration-controlled fashion. –Efficiently command and control the EFW instrument, both during ground testing and on-orbit operations. Governing documents: –RBSP Mission Requirements Document. –RBSP Data Management Plan. –RBSP EFW SOC Requirements Document. –RBSP EFW SOC Software Development Plan.

4. 4623-4 Sept. 2008EFW INST+SOC PDR EFW SOC Organization EFW PM Keith Goetz (UMN) EFW SysEng Dave Curtis (UCB) EFW SOC Lead John Bonnell (UCB) EFW CTG Lead William Rachelson (UCB) EFW SDC Lead TBD (UCB) The EFW SOC will be: Developed at UCB. Hosted from UCB. UCB has played a similar role on previous missions: CRRES, Polar, FAST, THEMIS. EFW Instrument I&T occurs at UCB, and SOC development builds on the GSE required to support that effort: GSE→Test SOC→FLT SOC.

5. 4633-4 Sept. 2008EFW INST+SOC PDR EFW SOC Data Products Data LevelDescriptionTime to AvailabilityUsers L0Raw de-commutated telemetry data retrieved from MOC. APID-separated daily files generated by SOC (EFW L0+). Binary files. Typically daily retrieval and processing and/or reprocessing to pick up long-latency Burst data. Processing time < 6 hours. SOC, archives. L1L0 + Time-tagged RAW waveform and spectral in spinning spacecraft coordinate system. Software and CAL files read L1 data files and produce data in physical units. ISTP-Compliant CDFs. Daily production and/or re- processing. Processing time < 6 hours. SOC, EFW Team, archives. L2L1 + Time-tagged waveform and spectral data in calibrated physical units [V, mV/m, (V/m) 2 /Hz, etc.] in despun spacecraft coordinate system and relevant geophysical coordinate systems. ISTP-Compliant CDFs. QuickLook L2 data and Summary Plots. JPG and PDF (TBD) plot files (6 and 24-hr). Available internally daily for purposes of instrument operations and data validation. Pushed weekly or bi-weekly to MOC as validated by EFW-SOC and SCI teams. [Requirement is XXX/YYY days] SOC, EFW Team, RBSP Science Team, Other End Users (Archives, Virtual Observatories, GIs, etc.). L3L2 + VxB removal for DC E-field estimate.< 2 months. L4L3 + global E field pattern estimates< 1 year.

6. 4643-4 Sept. 2008EFW INST+SOC PDR EFW SOC Top-Level Data Processing Diagram RBSP MOC CTG-CTG SOC-NRT SOC-PDP SDC-MDP EFW Instrument DATA ARCHIVES: SOH L0+, L1, L2, QL, CAL, L3+ SDC-DVAL SDC-BSEL RBSP EFW SOC Command-Telemetry-Ground Support (CTG) and Science Data Center (SDC) elements. SDC-ODP SDC-MAG SDC-SDA SDC-CAL EMFISIS SOC MAG data OTHER RBSP and GEOPHYSICAL DATA Sources EFW Supporting DATA ARCHIVES: EMF-MAG STATE MOC OGPD SOC-logs

7. 4653-4 Sept. 2008EFW INST+SOC PDR EFW SOC Data Processing Organization SOC is divided into two parts: Command, Telemetry, and Ground Support (CTG). Science Data Center (SDC) CTG consists of a single CSCI, CTG. SDC consists of 9 CSCIs: NRT – Near-real Time data processing and display. METUTC -- MET↔UTC Time Conversion PDP – Processed Data Production. DVAL – Data Validation BSEL – Burst Data Selection MDP – MOC Data Products Processing. MAG – MOC and EMFISIS Data Products Processing. ODP – Other RBSP and Geophysical Data Products Processing. SDA – Science Data Analysis. CAL – EFW Calibration Parameter Production.

8. 4663-4 Sept. 2008EFW INST+SOC PDR EFW SOC CTG Block Diagram GSE

9. 4673-4 Sept. 2008EFW INST+SOC PDR EFW SOC NRT Block Diagram RBSP MOC EFW SOC CTG MOC L0 to SOC L0+ processing L0+ to L1 Processing EFW L0+ Archive EFW L1 Archive SOC and SCI team input required Autonomous Operation External Process or Resource NRT Data Analysis And Display Near-Real Time Data Acquisition, Processing, and Display (Science and SOH)

10. 4683-4 Sept. 2008EFW INST+SOC PDR EFW SOC PDP and DVAL Block Diagram RBSP MOC MOC L0 to SOC L0+ processing L0+ to L1 Processing L1 to L2 Processing QL Data and Plot Production. EFW L0+ Archiv e EFW L1 Archiv e EFW L2 Archive (internal) EFW QL Archive (internal) L2 and QL Validation L2 and QL transfer to external access EFW L2 and QL Archive (ext. access) SOC and SCI team input required Autonomous Operation EFW EMF- MAG Archiv e External Process or Resource Processed Data Products (PDP and DVAL): Acquisition, Production, Validation, and Delivery. STATE (EPHE M/ATT) Archive CAL Archiv e CTGCTG

11. 4693-4 Sept. 2008EFW INST+SOC PDR EFW SOC BSEL Block Diagram RBSP MOC EFW SOC CTG EFW L2 Archive (internal) EFW QL Archive (internal) SOC and SCI team input required Autonomous Operation EFW Burst (B1 and B2) Ground Selection External Process or Resource EFW EMF- MAG Archiv e STATE (EPHE M/ATT) Archive OTHE R Data Source s OTHER Data Acq. EFW Comman d Archive Burst Selection ( BSEL): Generation, Validation, Delivery, and Archiving. MET↔UTC Conversion

12. 4703-4 Sept. 2008EFW INST+SOC PDR EFW SOC MDP and MAG Block Diagrams RBSP MOC MOC Data Products Retrieval (non-Data, non-SOH) EFW STAT E Archiv e SOC and SCI team input required Autonomous Operation EMFISIS SOC MAG data EMF-MAG Data Acq EFW EMF- MAG Archiv e SOH Archiv e External Process or Resource RBSP MOC QuickLook MAG data ATT/EPHEM to STATE Processing Other MOC Data Products (OMDP) Processing MOC Data Produc ts Archiv e EFW OMDP Archiv e SCLK (MET↔UTC), MOC Data Products and MAG Data Processing: Retrieval, Validation, Processing, and Archiving. SCLK Kernel Processing EFW SCLK Archiv e

13. 4713-4 Sept. 2008EFW INST+SOC PDR EFW SOC SDA and CAL Block Diagrams L1 to L2 Processing (TDAS or SDT) EFW L1 Archiv e EFW L2 Archive (internal or external) SOC and SCI team input required Autonomous Operation EFW EMF- MAG Archiv e External Process or Resource Science Data Analysis (Internal and External) CAL Parameter Estimation and Production STATE (EPHE M/ATT) Archive CAL Archiv e L2 to L3+ Processing (TDAS or SDT) External Users (ISTP CDF End Users) CAL Production EFW L1 Archiv e EFW L2 Archiv e EFW EMF- MAG Archive STATE (EPHEM /ATT) Archive CAL Archiv e EFW SOH/HS K Archive Plasma Data (eg. ECT- HOPE Vion) CAL Archiv e

14. 4723-4 Sept. 2008EFW INST+SOC PDR EFW SOC Development Plan: Schedule and Milestones PhaseCSCIs/ModulesMilestone Date (no later than) Supports I (Core Instrument Support) GSE CTG NRT Nov 2008EFW IDPU ETU Board-Level Tests and Instrument I&T II (Core MOC Data Products) Test SOC Phase I + METUTC MDP-I (SCLK only) Oct-Nov 2009EFW IDPU FLT Board-Level Tests and Instrument I&T III (Core SDC) Flight SOC Phase II + PDP, MDP-II, ODP, SDA, CAL-I (Ground). Launch – 6 m (TBD) (Oct 2011 – 6 m) Mission Sims SDC Inter-Operability. EFW Commissioning. IV (Full SDC) Flight SOC Phase III + DVAL, BSEL, MAG, CAL-II (On-Orbit). Launch + 60 days (Dec 2011) Normal Mission Ops.

15. 4733-4 Sept. 2008EFW INST+SOC PDR EFW SOC Test Plan Detailed GSE-SOC test plan under development (due Q2 or Q3, 2009; supports SDP Phase II). CSCI elements will be tested in isolation to establish basic functionality (test cases; error cases and signaling). –Example: phased introduction of DCB functions and testing using GSE. Elements are brought together into full modules and fed instrument data from known sensor excitations to verify module-level functionality and requirements fulfillment. –Example: basic instrument functional tests during I&T. End-to-end testing at each stage of integration to weed out problems early. –Example: testing of complete PDP chain as early as possible during Phase D using data from SC I&T and environmental tests.

16. 4743-4 Sept. 2008EFW INST+SOC PDR EFW SOC Current Status Current Status consistent with Phase I Development (Core Instrument Support through GSE): –GSE module can: Communicate with the DCB via the SC Emulator and GSEOS –Raw data. –CCSDS packetized data. Display received data in hexdump format. Detect errors in CCSDS/ITF data. Generate PPS/SP signals with SC Mini-Emulator. Upcoming efforts include (Nov 2008): –Development of board-level GSE support (BEB and BEB SciCal esp.). –Modification of existing NRT IDL modules for EFW packet formats.

17. 4753-4 Sept. 2008EFW INST+SOC PDR EFW ConOps Instrument Commissioning EFW Commissioning consists of two phases: –Initial instrument turn on and check out. –Radial and axial boom deploys. –May occur at RBSP MOC (using Test SOC) or at EFW SOC (using Flight SOC). Turn-On and Checkout consists of stowed functional tests (duplicates of SC-level I&T procs and data). InstrumentActivity Duration Telemetry Requirements Constraints & Notes EFWTurn-On and Check Out 2x2 hrsNRT: ~4 kbps. Stored: ~8 kbps. Should occur after or in conjunction with EMFISIS Turn-On and Check Out b/c of shared analog data (EFW, MAG, and SCM). EFWBoom Deploys2 weeks (both observa tories in parallel) NRT: ~4 kbps for initial step; 1-2 kbps thereafter. Stored: <5.25 kbps (Survey TM). Boom deploys must occur in sunlight. Sensor Diagnostic Tests will drive spacecraft floating potential.

18. 4763-4 Sept. 2008EFW INST+SOC PDR EFW ConOps Instrument Commissioning: Radial Booms Deploy Initial EFW boom deploy plan already developed: RBSP_EFW_TN_003C_EFW_BoomDeploySequence.doc. Boom deploy power controlled by MOC (SC service). Boom deploy commanding through EFW SOC (test or flight). Spin rate changes during staged, pairwise boom deploy illustrated below. Spin rate vs. boom stroke and time during deploy used to monitor state of deploy and abort, if required. Baseline 13-day parallel deploy schedule between both observatories; required durations based on recent THEMIS-EFI experience (parallel ops on THD and THE, June 2007). Fine wire unfurling

19. 4773-4 Sept. 2008EFW INST+SOC PDR EFW ConOps Instrument Commissioning: Axial Booms Deploy Axial boom deploy occurs after radial boom deploy is complete, and observatory mass properties and dynamics confirmed (typically no significant delay required). Axial booms deployed singly, in stages using motor deploy system to ≈5-m stroke (≈10-m tip-to-tip). Final deploy lengths trimmed in roughly 10-cm increments using Survey axial E-field and SC potential estimates to reduce common- mode signal (expected duration of trim phase is 2 weeks, but is outside of commissioning phase).

20. 4783-4 Sept. 2008EFW INST+SOC PDR EFW ConOps Validity Conditions for Nominal Operations Sensors Illuminated -- All EFW sensors illuminated (goal for aft axial sensor). Attitude Known -- Post-processed Observatory attitude (spin axis pointing and spin phase) known to accuracy better than 3 deg. Ephemerides Known -- Post-processed Observatory position and velocity known to accuracy better than (10 km, 30 m/s, 0.1 deg; 3-sigma). Booms Settled -- EFW radial booms within 0.5 deg of nominal position. DC B-Field Known – Post-Processed DC B-field known to accuracy better than 1%. EFW-MAG-SCM Relative Orientation Known – Post-processed relative orientation of EFW, MAG, and SCM sensor axes known to better than 2 degrees.

21. 4793-4 Sept. 2008EFW INST+SOC PDR EFW ConOps Instrument Health and Status Monitoring Instrument State-of-Health (SOH) monitored through near-real- time or playback engineering data via the SOC-CTG. SOH compared against red/yellow limit database. Off-Nominal conditions leads to: –Notification of EFW SOC personnel (page, e-mail). –Issuance of scripted commands, for certain, well-known off-nominal conditions (example: CRRES DDD-false commanding and resets). Long-term trending and storage of SOH data: –New solution in GSEOS as part of CTG efforts or… –Incorporation into existing UCB MOC BTAPS database (decision: part of Phase III development, 2010 time frame).

22. 4803-4 Sept. 2008EFW INST+SOC PDR EFW ConOps Normal On-Orbit Operations Commanding –Complete instrument state (sensor biasing and data collection) set by ~50 commands. –Instrument configuration changes infrequently (~1/few weeks, after initial commissioning phase). –~daily commanding to support ground selection of burst segments as needed. –~monthly Sensor Diagnostic Tests (bias sweeps) to confirm and optimize instrument biasing. Data Management –12 kbps daily average: ~ 5 kbps continuous Survey data (32 S/s E and V; auto- and cross-spectral data products). ~ 7 kbps Burst1 and Burst2 data (0.5 and 16 kS/s E, V, and SCM data). Burst Management –Higher-rate waveform data (E, V, and SCM) collected continuously and banked into SDRAM and FLASH in seconds to minutes long segments (many days of B1 storage; many hours of B2 storage). –Each segment tagged with “Burst Quality” computed on-board from DC or AC fields data cues (DC Spin-Fit E; SC Potential; Filter Bank AC E or B). –B1 playback is through ground selection based on Survey data and other data sources (geophysical indices, etc.); on-board with Burst Quality allows for autonomous selection and playback, as needed (vacations, illness, ennui, etc.). –B2 survival and playback selection on-board is based on Burst Quality; playback selection includes option for ground selection based on Survey data and other data sources (geophysical indices, etc.). –B1 and B2 support for time-tagged campaign modes available as well (e.g. BARREL support). Inter-Instrument Burst Data –EFW message includes axial sensor status (illuminated/eclipsed), sensor sweep status (static/sweeping), and current burst-valuation algorithm ID and value.

23. 4813-4 Sept. 2008EFW INST+SOC PDR EFW ConOps Command Generation EFW-SOC shall generate commands by reference to UTC, as well as MOC data products (predicted ephemerides, etc.) and other data assets (e.g.. Geomagnetic indices). EFW commands shall be validated as needed by running command load on EFW TestBed (ETU) and verifying appropriate change of state, data production, and instrument configuration. Command validation shall occur prior to transmission of command load from EFW-SOC to RBSP-MOC. Verification of current MET↔UTC SCLK Kernel shall occur prior to translation of EFW commands from UTC to MET. Command receipt will be verified after transmission using standard MOC data products.

24. 4823-4 Sept. 2008EFW INST+SOC PDR This page intentionally almost blank