E2E Mission Performance Chains rationale and activities Michele - - PowerPoint PPT Presentation

e2e mission performance chains rationale and activities
SMART_READER_LITE
LIVE PREVIEW

E2E Mission Performance Chains rationale and activities Michele - - PowerPoint PPT Presentation

E2E Mission Performance Chains rationale and activities Michele Zundo System Support Division EOP-PEP Michele.zundo@esa.int Noordwijk, 23 st Jan 2018 Content 1. Challenges and concepts 2. Who are Actors/Users 3. Tasks in the domain of Mission


slide-1
SLIDE 1

Noordwijk, 23st Jan 2018

E2E Mission Performance Chains rationale and activities

Michele Zundo System Support Division EOP-PEP Michele.zundo@esa.int

slide-2
SLIDE 2

Noordwijk, 23st Jan 2018

Content

  • 1. Challenges and concepts
  • 2. Who are Actors/Users
  • 3. Tasks in the domain of Mission performance
  • 4. What is a Mission performance (tool) Chain.
  • 5. Mission Lifecycle Aà E and Mission performance
  • 6. Existing documentation, tools and framework
slide-3
SLIDE 3

Noordwijk, 23st Jan 2018

Mission Performance Chains

slide-4
SLIDE 4

Noordwijk, 23st Jan 2018

What is Mission performance ??

Satellite design

Payload design

L1 Algorithm L2 Algorithm Mission Performance

Operation Concept

slide-5
SLIDE 5

Noordwijk, 23st Jan 2018

Actors and Competences

Sat/Inst. Industry L1PP Industry Mission Scientist Operational GS

EOP-P Project

Instrument Engineer Processor Engineer GS Engineer

TEC support

L2PP Industry Study Manager

slide-6
SLIDE 6

Noordwijk, 23st Jan 2018

Common E2E Chain Tasks (examples)

Support industry design/implementation

  • f instrument/platform

Instrument and Platform requirements verification Calibration algorithm and implementation prototyping Monitoring algorithm prototyping Independent E2E assessment at ESA Shadow Space Segment Industry work Independent Verification Processing of

  • n-ground

characterisation Operational concept confirmation and refinement what-if analysis (e.g. calibration freq.) L1PP algorithm definition and prototyping Sensitivity analysis (error/effects on L1) Test Data Generation L2 algorithm and target simulation definition and prototyping Sensitivity analysis (errors/effects on L2/L3)

(Phase 0/A) Study and Mission Selection

Industry Project Scientist Ground Segment

slide-7
SLIDE 7

Noordwijk, 23st Jan 2018

Algorithms vs Engineering of Mission Performance Chain

1.Algorithm/requirements are specific, e.g: 2.Engineering, architecture, tools are common!

Passive Optical Instrument Active Optical Instrument Active MW Instrument Level 2 Retrieval Level 1 Calibration

Geometry Target generation Instrument Simulation Level 1 processing Level 2 processing Assessment Tools

“My mission is special” algo

slide-8
SLIDE 8

Noordwijk, 23st Jan 2018

Mission Performance and Lifecycle

Phase 0/A/B1

Feasibility study

Mission Level perf. estimation (L2) Candidate architecture

Cost Estimates Mission Selection

Phase B2/C/D

Detailed payload/ platform modelling Detailed L1PP/L2PP definition Definition of Products and Calibration Confirm Design and as-built Performance

Simplified Observing System Simulator Complete Instrument Simulator and GPPs

Architecture

Evolution not redesign

slide-9
SLIDE 9

Noordwijk, 23st Jan 2018

What is available today for Mission Performance Chains

Architecture definition (ARCHEO)

Standard Interface Definition (Generic E2E ICD) Simulators and GPP Building Block definition (BIBLOS) Template doc for SW/architecture requirement (annex to SAT-SRD) Open Source SW components for Algorithm (BIBLOS) Common function libraries e.g. Orbit, Attitude, CCSDS read/write (DFDL4S, EOCFI) Orchestration framework (openSF)

http://eop-cfi.esa.int/ SW Docs

slide-10
SLIDE 10

Noordwijk, 23st Jan 2018

Reference Architecture (ARCHEO)

slide-11
SLIDE 11

Noordwijk, 23st Jan 2018

BIBLOS component library

https://gmv-biblos.gmv.com/

slide-12
SLIDE 12

Noordwijk, 23st Jan 2018

Take away message

  • 1. Every mission needs to assess its performance
  • 2. Different use cases, actors and type of work however same framework can be

used which will eventually save time and money.

  • 3. Work in Phase 0/A/B should be seamlessly reused in C/D
  • 4. Experience and best practice exists
  • 5. Open licence SW tools, algo, documentation exists already