Tobias Weckenmann · Maren Huxel · Tobias Weckenmann
--- a/docs/documentation/sizing/propulsion_design/overview.md 0 → 100644
+++ b/docs/documentation/sizing/propulsion_design/overview.md 0 → 100644
+# Overview {#mainpage}
+The propulsion_design tool provides the engine data and the engine integration on the aircraft. The steps are shown in the following figure:
+
+![](figures/propulsion_design_flow.png)
+
+Required inputs for propulsion design are therefore:
+
+    - The thrust to weight ratio (First from initial_sizing sizing then from constraint_analysis).
+    - The MTOW of the aircraft.
+    - The type of propulsors and the according thrust share.
+
+With this the engines are designed one by one with the following approach:
+
+![](figures/engine_sizing.png){html: width=600}
+
+The outputs are the engine xml file as well as the different deck values as csv files in projects as well as the following xml snippet for each engine:
--- a/docs/documentation/sizing/propulsion_design/overview.md 0 → 100644
+++ b/docs/documentation/sizing/propulsion_design/overview.md 0 → 100644
+![](figures/xml_output.PNG){html: width=1200}
+
+Readout of the engine data can and should only be done using the engine library!
+
+The csv files contain engine data that depends on the operating point. The operating point is defined as
+
+    - Flight Mach number
+    - Flight altitude 
+    - Low pressure spool speed / power setting
+
+An example is shown in the following figure.
+
+![](figures/deck_example.PNG)
+
+The data is readout by the engine library which has an efficient parser for the deck values using a linear interpolation between two existing deck values. Penalties, like shaft power offtake or bleed air offtake, are also calculated using the engine library. The description of the engine library can be found here as well.
+The description of the engine library can be found [here](../../../libraries/engine/).