Estratto del documento

Example: Possible service loss and risk

Post reviews will require a real regulation. Some issues will disappear from the TC - so the mean value will change → we should book the team for an offer such that this variation is small, otherwise we may have risk for future changes. Possibly, then we should leave the version of review days, one of the north ends.

Risk: There is very important (society, payload) → this is very serious both for society and commercial missions.

Design process

All the modules will have to work together → concurrent legacy. All the subsystems are interconnected and will affect each other. So in concurrent running, we don't work in sequence but the various experts are working parallel. Another very important aspect to consider is the overall closure.

Mission repeated could fail to be objectives, technical/electric/payload reliability, schedule adhesion, budget. How much do we need to risk to assure reliability? We use probability for the production to get increased cost will ∇ use? by our mission.

Study requires → products/story line/planning resource risk for copies, the new machine ends leave to study a backup solution (?). Absolutely above the prospect, so obviously, e.g., if we can't avoid a certain border.

Other examples: If a choice I was planning for mightiest get dusted on its basis, then I plan to have another one planned. Sometimes we perform tests just to understand the possible future mission (e.g., human Mars) if feasible.

Example: Possible service modes

RHUth poppy receivers will require a fuel regulation -> some wires will disappear from the TC - so its water ratio will change -> we should book the team panel and offer such that this variation is small; otherwise, we may lose pb for a true dynasty possibly ☐➍ we should leave the version of leave day one of the week CMSRHU there is many instrument (sci, ☐⧄, payload) -> this is very common both for scientific and commercial missions.

Design process

All the # ☐ both will then work together -> concurrent legacy. All the subsystems are interconnected and will affect each other. So in current legacy, we don’t work in separate but the various experts are working w// Another very important aspect to consider is the descent capture.

Mission repeated caused - p. dynamics, curriculum, elective, payload, reliability/, schedule advisory, budget. How much do we need to risk -> ☐ mass variability. We use reproduction -> let misused cost wild. Highest realism -> in the collected -> ☐

Study represents -> product + strong land fleury resource RHU the obey the answer was always leave of stage eDocking solution (⨁) abs. in the project, so elevators e.g., if up can ‘n ☐ a certain barlear. Other e.g. - of a dance I wo for magistrate gets chest on the leg I plan to use another one 1:20

Sometimes was prefer exists just to understand so for possible future mission so on human on Mars? Feasible. In space missions, it is very important to consider also the political and economic issues.

Tech readiness levels (TRL)

Standard classification from 1 (less developed) to 9 (new development) of the development of a certain technology. TRL 1 - 0, just a basic idea. TRL 9 - system proven many times successfully in real missions. Let’s perform a flight (so we build and launch) for ESA. Year must have analyzed at least TRL 6. Also for the software, there is a TRL classification. The level of the SW/HW is certified by the subject that counts.

Process flow (I/D)

Different kinds of missions will have to be managed in # ways. For example, if we consider 3 missions:

  1. S/C empty burn
  2. S/C controlled Earth
  3. S/C reentry Pluto

We’ll have # objects to be considered and # constraints to foreseen.

  1. Solar cell will decoy path, top
  2. Helium H2/propulsion (RSI, TCS), BGS (Power)

To enlarge the orbit flow, we can use propulsion or park a gravity assist (- fly with a planet).

Mission objectives

  • Requirements
  • Payload (PL)
  • MA mission analysis
  • ADCS TCS EPS
  • Operations OS

Study of the mission from the subset of which we obtain the result we opt at the end of the we obtain the history of the orbit of our SC. One payload (which is related to the pol of the mission) will be some required and some house held.

MA propulsion ADCS environment configuration:

  • Propulsion system selection
  • Propellant budget
  • Propellant loading definition and symbol
  • Decision keeping nodes
  • Orbit selection ΔV or propulsion budget
  • Launcher selection
  • Vertical visibility
Anteprima
Vedrai una selezione di 10 pagine su 113
Appunti di Space systems engineering and operations SSEO Pag. 1 Appunti di Space systems engineering and operations SSEO Pag. 2
Anteprima di 10 pagg. su 113.
Scarica il documento per vederlo tutto.
Appunti di Space systems engineering and operations SSEO Pag. 6
Anteprima di 10 pagg. su 113.
Scarica il documento per vederlo tutto.
Appunti di Space systems engineering and operations SSEO Pag. 11
Anteprima di 10 pagg. su 113.
Scarica il documento per vederlo tutto.
Appunti di Space systems engineering and operations SSEO Pag. 16
Anteprima di 10 pagg. su 113.
Scarica il documento per vederlo tutto.
Appunti di Space systems engineering and operations SSEO Pag. 21
Anteprima di 10 pagg. su 113.
Scarica il documento per vederlo tutto.
Appunti di Space systems engineering and operations SSEO Pag. 26
Anteprima di 10 pagg. su 113.
Scarica il documento per vederlo tutto.
Appunti di Space systems engineering and operations SSEO Pag. 31
Anteprima di 10 pagg. su 113.
Scarica il documento per vederlo tutto.
Appunti di Space systems engineering and operations SSEO Pag. 36
Anteprima di 10 pagg. su 113.
Scarica il documento per vederlo tutto.
Appunti di Space systems engineering and operations SSEO Pag. 41
1 su 113
D/illustrazione/soddisfatti o rimborsati
Acquista con carta o PayPal
Scarica i documenti tutte le volte che vuoi
Dettagli
SSD
Ingegneria industriale e dell'informazione ING-IND/05 Impianti e sistemi aerospaziali

I contenuti di questa pagina costituiscono rielaborazioni personali del Publisher leonardoperi di informazioni apprese con la frequenza delle lezioni di Space systems engineering and operations e studio autonomo di eventuali libri di riferimento in preparazione dell'esame finale o della tesi. Non devono intendersi come materiale ufficiale dell'università Politecnico di Milano o del prof Lavagna Michele.
Appunti correlati Invia appunti e guadagna

Domande e risposte

Hai bisogno di aiuto?
Chiedi alla community