4593-4 Sept. 2008EFW INST+SOC PDR RBSP EFW SOC (in support of INT) and ConOps Science Operations Center (In Support of INT) and Concept of Operations (SOC

1EFW INST+SOC PDR3-4 Sept. 2008

RBSP EFWSOC (in support of INT) and ConOps

Science Operations Center

(In Support of INT)

and

Concept of Operations

(SOC and ConOps)

John Bonnell

Will Rachelson

Matt Born

Space Sciences Laboratory

University of California, Berkeley


EFW SOC and ConOpsOutline (EDIT THIS)

• 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


EFW SOCRequirements

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


EFW SOCOrganization

EFW PMKeith Goetz (UMN)

EFW SysEngMichael Ludlam (UCB)

EFW SOC LeadJohn Bonnell (UCB)

EFW CTG LeadWilliam Rachelson (UCB)

EFW SDC LeadMatt 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.


EFW SOCTop-Level Data Processing Diagram

RBSP MOCCTG-CTG

SOC-NRT

SOC-PDP SDC-MDP

EFWInstrument

DATAARCHIVES:

SOHL0+, L1, L2, QL,

CAL,L3+

SDC-DVAL

SDC-BSEL

RBSP EFW SOC Command-Telemetry-Ground Support (CTG) and Science Data Center (SDC) elements.

SDC-ODPSDC-MAG

SDC-SDA

SDC-CAL

EMFISISSOC

MAG data

OTHERRBSPand

GEOPHYSICAL DATA

Sources

EFWSupporting

DATAARCHIVES:

EMF-MAGSTATEMOCOGPD

SOC-logs

SOC-CDR

I-CDR


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


EFW SOCData Products (make sure agree with SDMP)

Data Level Description Time to Availability Users

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

L1 L0 + 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.

L2 L1 + 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.).

L3 L2 + VxB removal for DC E-field estimate. < 2 months.

L4 L3 + global E field pattern estimates < 1 year.


EFW SOCCTG Block Diagram

GSE


EFW SOCNRT Block Diagram

RBSP MOCEFW SOC

CTG

MOC L0 to

SOC L0+ processing

L0+ to L1 Processing

EFWL0+

Archive

EFWL1

Archive

SOC and SCI team input required

Autonomous Operation

External Process or Resource

NRT DataAnalysis

And Display

Near-Real Time Data Acquisition, Processing, and Display (Science and SOH)


EFW SOCDevelopment Plan: Schedule and Milestones

Phase CSCIs/Modules Milestone Date(no later than)

Supports

I (Core Instrument

Support)GSE

GSECTGNRT

Nov 2008 EFW IDPU ETU Board-Level Tests and Instrument I&T

II (Core MOC Data

Products)Test SOC

Phase I +METUTCMDP-I (SCLK only)

Oct-Nov 2009 EFW IDPU FLTBoard-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 SimsSDC 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.

RBSP-EFW CDR 2009-09-30 11

EFWGSE

• Rachelson presentation here.

RBSP-EFW CDR 2009-09-30 12

EFWScience Data Center

• Products Under Development– SDC-NRT data analysis tool, EFW Plot

• Planned Products– SDC-BSEL burst selection tool– SDC-DVAL data validation and release tool– SDC-MDP L0 retrieval and archiving service– SDC-MAG ancillary magnetic data retrieval, integration, and archiving

service– SDC-ODP ancillary data retrieval and archiving service– SDC-PDP L0->...->L4 conversion and archiving service– SDC-SDA scientific data service– CAL calibration data service

RBSP-EFW CDR 2009-09-30 13


• SDC-NRT Analysis Tool– Requirements

• Acquire instrument data– Scriptable operation allows tie-in to the EFW CTG for data during I&T, etc.– Network interface will allow tie-in to forthcoming SOC-MDP during flight.

• Process instrument data– Decompression of DeltaMod-2– Decommutation of data packets as defined in the CTM

• Display instrument data– View, save, and print customizable plots of data– View statistics about data

– Value-added features• User interface requires little to no training• Import from and export to legacy tools, including tplot• Unit testing and use-case testing maintains quality• Generic back-end design allows for reuse in SDC-BSEL, SDC-DVAL, and SDC-SDA

products.

RBSP-EFW CDR 2009-09-30 14


RBSP-EFW CDR 2009-09-30 15


RBSP-EFW CDR 2009-09-30 16


RBSP-EFW CDR 2009-09-30 17


RBSP-EFW CDR 2009-09-30 18


RBSP-EFW CDR 2009-09-30 19


RBSP-EFW CDR 2009-09-30 20


RBSP-EFW CDR 2009-09-30 21


RBSP-EFW CDR 2009-09-30 22


• Present state of support for I&T– Communication

• L0 files written to disk by GSEOS are located and read without issues.– Decommutation

• APIDs 0x241 – 0x259 are fully implemented• APIDs 0x100 and 0x260 – 0x26a are not yet implemented. (ETA <2

weeks)– Decompression

• Delta Mod-2 decompression is implemented and tested.• No other compression algorithms are currently used by flight software.

– Output• Plots are sufficiently configurable to allow inspection of data to the

level required for verification of operation.

RBSP-EFW CDR 2009-09-30 25


• Security Processes for SDC Software Product Development– Confidentiality

• Unintentional disclosure of information is prevented by access control. [LDAP]• Unintentional disclosure of credentials is prevented by secure channels. [HTTPS]

– Integrity• Source changes are restricted by access control. [LDAP]• Source changes are reversible through version control. [SVN]• Inadvertent failures are detectable by automated testing. [Python]• Catastrophic information loss is prevented through data backup. [rsync]


RBSP EFWSOC (in support of INT) and ConOps

Concept of Operations

(ConOps)


EFW ConOpsInstrument 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).

Instrument ActivityActivity Duration

Telemetry Requirements

Constraints & Notes

EFW Turn-On and Check Out

2x2 hrs NRT: ~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).

EFW Boom Deploys NNN Weeks(both observatories 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.


EFW ConOpsInstrument 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 NNN-day parallel deploy schedule between both observatories incorporated into

current Mission Timeline (DOC-REF).

RBSP-EFW SPB Deploy

0.00

2.00

4.00

6.00

8.00

10.00

12.00

14.00

16.00

0 10 20 30 40 50 60

Boom Stroke (cable+fine wire)

Sp

in R

ate

[RP

M]

X-Deploy (predicted)

Y-Deploy (predicted)

Fine wire unfurling


EFW ConOpsInstrument 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 N weeks, and occurs in parallel with other instrument commissioning activities).


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


EFW ConOpsInstrument 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).


EFW ConOpsNormal On-Orbit Operations (1)

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


EFW ConOpsNormal On-Orbit Operations (2)

• 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 (DOC-REF; Filter Bank AC E or B, cues from other instruments).

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


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


• This page intentionally almost blank


BACKUP SLIDES


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

EFWL0+

Archive

EFWL1

Archive

EFWL2

Archive(internal)

EFWQL

Archive(internal)

L2 and QL Validation

L2 and QL transfer to

external access

EFWL2 and QL

Archive(ext. access)

SOC and SCI team input requiredAutonomous Operation

EFWEMF-MAG Archiv

e


Processed Data Products (PDP and DVAL):Acquisition, Production, Validation, and Delivery.

STATE (EPHE

M/ATT)Archive

CALArchiv

e

CTG


EFW SOCBSEL Block Diagram

RBSP MOCEFW SOC

CTG

EFWL2

Archive(internal)

EFWQL

Archive(internal)


EFW Burst(B1 and B2)

Ground Selection


EFWEMF-MAG Archiv

e

STATE (EPHE

M/ATT)Archive

OTHER Data Source

s

OTHERData Acq.

EFW Comman

d Archive

Burst Selection ( BSEL):Generation, Validation, Delivery, and Archiving.

MET↔UTC Conversion


EFW SOCMDP and MAG Block Diagrams

RBSP MOC

MOC Data Products Retrieval

(non-Data, non-SOH)

EFWSTATE Archiv

e


EMFISISSOC

MAG data

EMF-MAGData Acq

EFWEMF-MAG Archiv

eSOH

Archive


RBSP MOCQuickLookMAG data

ATT/EPHEM to STATE Processing

Other MOC Data Products

(OMDP) Processing

MOC Data

Products

Archive

EFWOMDPArchiv

e

SCLK (MET↔UTC), MOC Data Products and MAG Data Processing:Retrieval, Validation, Processing, and Archiving.

SCLK Kernel Processing

EFWSCLKArchiv

e


EFW SOCSDA and CAL Block Diagrams

L1 to L2 Processing(TDAS or

SDT)

EFWL1

Archive

EFWL2

Archive(internal or external)


EFWEMF-MAG Archiv

e


Science Data Analysis (Internal and External)CAL Parameter Estimation and Production

STATE (EPHE

M/ATT)Archive

CALArchiv

e

L2 to L3+ Processing(TDAS or

SDT)

External Users

(ISTP CDF End Users)

CAL Production

EFWL1

Archive

EFWL2

Archive

EFWEMF-MAG

Archive

STATE (EPHEM

/ATT)Archive

CALArchiv

e

EFW SOH/HS

KArchive

Plasma Data

(eg. ECT-HOPE Vion)

CALArchiv

e


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


• This page intentionally almost blank