1 / 8

Test plans and preparations: RMS, SVT, SOVT

Test plans and preparations: RMS, SVT, SOVT. D. Teyssier (ESAC) with inputs from P. Morris (IPAC). SVT-1. The SVT ( System Validation Test ) aims at validating the external interfaces from the MOC to the satellite, and the satellite TM and TC database definition (the MIB’s)

zelia
Download Presentation

Test plans and preparations: RMS, SVT, SOVT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test plans and preparations: RMS, SVT, SOVT D. Teyssier (ESAC) with inputs from P. Morris (IPAC)

  2. SVT-1 • The SVT (System Validation Test) aims at validating the external interfaces from the MOC to the satellite, and the satellite TM and TC database definition (the MIB’s) • There are 3 phases (SVT-0, SVT-1, SVT-2), making use of an increasing level of realism and complexity from one SVT to the other • SVT content based on procedures for normal and contingency operations • Current schedule is: • SVT-0: August 2006 • SVT-1: December 2007 • SVT-2: June 2008 RMS, SVT, SOVT

  3. SVT-1 • The content of the HIFI SVT-1 is based on the current procedures for manual commanding at MOC (as described in the IUM) RMS, SVT, SOVT

  4. RMS • The RMS (Reference Mission Scenario) is important first near-E2E exercise involving the MPS, real CDMU and ACMS --- RMS is industry driven • Currently planned in early November (TBC) • Warm (room temp) conditions • In principle uses the uplink chain expected in normal operations: • AORs in HSpot  submission  HOTAC tool (“activate”)  CUS build  schedule  execute on Herschel  downlink • In practice several extra steps needed to pull this chain together… e.g., • Submission via CVS (not HSpot submission tool) • Configure HIFI for RT operation (e.g., new LCU safety tables) • Pre-validate AOR cases with new CUS code (not in public HSpot) • Etc, etc. RMS, SVT, SOVT

  5. RMS RMS expectations • Clearly some HIFI AOT functionality will be tested, but time and lab temperatures will keep this very limited • AORs are all essentially new cases, no parallel setup available to check egregious errors with OBSW, command timing, etc. • No sources (only those internal to HIFI) • Frequency and load-switch differential stability unvalidatable. • Manual effort involved in creating AORs and pre-validating sequence parameters in offline CUS environment (IST CUS build is current for operating HIFI, but HSpot 3.0.3 by now out of sync). • “UplinkContext” from scheduled observations is not yet developed, so no expectation to automatically feed SPG or offline P/L processing environments. RMS, SVT, SOVT

  6. RMS RMS Status • AORs delivered (~12 hours testing, including simulated slewing between AOR celestial targets) • No SScans • Generally too wide for warm LO’s, but may be possible to construct a new narrow scan, with maximum reasonable redundancy (12) for at least 6 steps, i.e. to cover 2GHz in the SIS bands or 1.2 GHz in the HEB bands. Feasibility TBC by MPIfR. Probably deferred to SOVT-1. • “Warm” LCU safety tables required for bands 5-7 (TBC by MPIfR), involving additional effort by ESA/SRON to rebuild if AORs in these bands are included. TBD if AORs in 5-7 should be deferred to SOVT-1. • FSwitch Modes (± 120, 240 MHz) TBC by MPIfR. RMS, SVT, SOVT

  7. RMS RMS Timeline RMS, SVT, SOVT

  8. SOVT • SOVT (System Operation Validation Test) shall test the complete mission operation chain • Validation of overall ground and space segment behaviour and performance from E2E in its different operational configurations • Validation of mission planning process and interfaces • Validation of data transfer processes and access mechanisms • Validation of OBSM interfaces for payload elements • Validation of the HSC/DPC’s capability to receive and process all the data from the MOC • SOVT will happen just after SVT campaigns (Jan and June 08 resp.) • SOVT plan is written by ESA (SOVT-1 has version 0.1, July 07), HIFI inputs limited so far – expected is a more complete RMS-like set of AOT • Also the first (and only ?) opportunity to test peak-up RMS, SVT, SOVT

More Related