TWiki> Public Web>LessonsLearned2013 (revision 16)EditAttach

Herschel Lessons Learned Meeting: "Operations from Cradle to Grave"

Where ESAC / Rooms D1/D2
Duration up to 3 days
Start Tue 28 May 09:00
End Thu 30 May 16:00

* NO ABSTRACT :==> Record a "Lesson" instead !!! HERE :==> *


DEADLINE for ABSTRACTS: eob May 6 2013 (The Science Operations Coordination Group will assess the inputs received on May 7. Registrations will be accepted up to May 13.)

Scope and goals

Programme for the Meeting

Objectives of the Lessons Learned exercise

Top-level objectives for the end-May 2013 Lessons Learned Meeting

  • Capture the good, the bad, and the ugly, in particular "best practices" to be passed on for future missions, but should also document particular problems and in general important experience.

  • Generate conclusions and recommendations based on the above.

  • Propagate the above LL output (into ESA and towards future missions) as appropriate.

  • Generate a written Report and presentation(s).

Outline scope for the "Operations from Cradle to Grave" LL Meeting (May 28-30)*

The details will be elaborated as material is submitted. [Material = Abstracts or "Lessons" submitted to the above-described repository (or one of its ICC equivalents).]

The overall Mission design concept and methodology
   • Mission Design & Technical drivers (incl. orbit, space environment, lifetime, science data bandwidth, ACMS & pointing, DTCP/GS, …)
   • Structure of the Science Ground Segment (SGS), division of responsibilities, and organisation
   • Concept of Smooth Transitions
   • (Herschel Common Science System) HCSS - Concept, development, and components (MDB, CUS, HSpot, Configuration Control, Build System, System Integration, Testing and Validation)
   • Calibration (Standards & modelling; cross-calibration: Herschel-Herschel, Herschel-other missions)

Operations Processes and Procedures
   • Operations preparations
   • Support to instrument level tests
   • End-to-end tests and simulations
   • LEOP and Commissioning Phase
         * Calibration, in-flight performance, evaluation, verification, and optimisation
   • PV Phase
         * AOT-release, calibration, in-flight performance, evaluation, verification, and optimisation
   • Science Demonstration Phase
         * KP-release, A&A Special Issue, information provision for AO-1
   • Routine Science Phase
         * Calibration, in-flight performance, evaluation, verification, and optimisation
         * Scheduling strategy, policies, flexibility, re-planning
         * Community Support - Level of service provided to community (excl. downlink)
         * Helpdesk
         * Information provision (documentation, mailings, and web)
         * Workshops (uplink/HSpot, downlink/HIPE, topical)
         * Observing programme maintenance/replanning, programme conflicts & optimisation, duplications tools, HOTAC tools, HOTAC meetings
         * Downlink (other than DP and Archive)
         * Mission DataBase (MDB) / Versant ...

Data processing
   • Providing data to observers - pipeline processing, standard products, HSA population, on demand reprocessing, and interactive data processing
   • HIPE provision - design rationale, technical choices (Java, Jython), scope, implementation, ...
   • HIPE use - performance, user friendliness & support, interaction with other packages, ...

Herschel Science Archive (HSA)
   • User friendliness and support , HSA population, on-demand reprocessing, interaction with other archives & VO

Science Management
   • Amount of GT, proprietary time
   • Concept of Key Programme
   • Concept of Science Demonstration Phase (SDP)
   • Scheduling philosophy ("best use of helium" as the principal driver)
   • Handling of calibration observations 

Methodology of the exercise

  • Material, in the form of Abstracts of proposed talks will be gathered, with the deadline for receiving abstracts being eob on May 6 2013. (Registrations will be accepted up to May 13.)

  • An effort will be made to associate an "Advocate" with each key area of the meeting, who could:
    • present a summary/distillation of the collected views
    • lead the discussion in the meeting
    • write up the key conclusions afterwards as input to the overall summary.

Programme for the Meeting

Registration & Abstract Submission

Accommodation & Transportation

Edit | Attach | Watch | Print version | History: r31 | r18 < r17 < r16 < r15 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r16 - 2013-05-08 - LeoMetcalfe
This site is powered by the TWiki collaboration platform Powered by Perl