1. 4593-4 Sept. 2008EFW INST+SOC PDR RBSP EFW GSE and SOC-GSE GSE and SOC-GSE (Science Operations Center In Support of INT) John Bonnell Will Rachelson Matt Born Space Sciences Laboratory University of California, Berkeley

2. 4603-4 Sept. 2008EFW INST+SOC PDR EFW GSE and SOC-GSE Outline Science Operations Center (SOC) –Requirements –Organization –Description: Data Products Data Processing Flow –Development: Schedule and Milestones Test Plan Status

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 (DOC-REF). –RBSP-EFW UCB Performance Assurance Matrix (GSE and SOC tabs). –RBSP EFW SOC Requirements Document (DOC-REF). –RBSP EFW SOC Software Development Plan (DOC-REF). Contributing Documents: –RBSP Science Data Management Plan (DOC-REF).

4. 4623-4 Sept. 2008EFW INST+SOC PDR EFW SOC Organization EFW PM Keith Goetz (UMN) EFW SysEng Michael Ludlam (UCB) EFW SOC Lead John Bonnell (UCB) EFW CTG Lead William Rachelson (UCB) EFW SDC Lead Matt Born (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 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 SOC-CDR Jan 2010 I-CDR

6. 4643-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, 1 of which is directly relevant to INT efforts: 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.

7. 4653-4 Sept. 2008EFW INST+SOC PDR EFW SOC Data Products Data LevelDescriptionTime to AvailabilityUsers L0Raw de-commutated, APID-separated telemetry data retrieved from MOC. 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. Latency <= 7 days. 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. Latency <= 1 week. SOC, EFW Team, RBSP Science Team, Other End Users (Archives, Virtual Observatories, GIs, etc.). L3L2 + VxB removal for DC E-field estimate.Latency <= 1 month. L4L3 + global E field pattern estimatesLatency <= 1 year.

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 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.

11. 4693-4 Sept. 2008EFW INST+SOC PDR BACKUP SLIDES

12. 4703-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.

13. 4713-4 Sept. 2008EFW INST+SOC PDR This page intentionally almost blank