powerBreakdownsType

complexType · extension complexBaseType · sequence

Power flows in the systems for given flight conditions

A power breakdown gives the power that flows through the systems of the vehicle in a flight condition: the mass flow, heat flow, electric power and mechanical power that the connections of the system architectures carry. It is the analysis level of the system description: each flow references a connection of a system architecture (systemArchitecturesType). The ends of a connection are installed system components (genericSystemsType), other parts of the vehicle such as a fuselage, a wing or a fuel tank, other systems, or external elements such as the ambient.

Static and transient cases

A static case holds the flows at one flight condition, given by altitude and speed or by a flight point (staticCaseType). A transient case holds them along a trajectory: each value is a vector with one entry per flight point of the trajectory (transientCaseType). A static case also gives the state of the switchable parts of the systems in its configuration (systemControlDevicesType).

Power flows

A power flow belongs to one of four categories, each with its own value:

Rules

Sankey diagram of the electric and mechanical power flows at take-off of a fuel cell propulsion unit: the fuel cell stack (370 kW) and the battery (147 kW) feed the power management unit, which passes 434 kW to the inverter, 58 kW to the compressor and 20 kW to the electrical power supply (ata24); the inverter feeds the motor with 425 kW, the motor the gearbox with 408 kW and the gearbox the propeller with 400 kW. The losses of the power management unit, the inverter, the motor and the gearbox (5.2, 8.7, 17.0 and 8.2 kW) branch off as gray bands

The figure shows the electric and mechanical power flows at take-off of the propulsion unit whose architecture is shown for systemArchitectureType. The fuel cell stack and the battery deliver 517 kW to the power management unit, of which 400 kW reach the propeller as shaft power. The losses drawn are not part of the data; they follow from the balance of each component, e.g. 17.0 kW at the motor, which takes 425 kW and delivers 408 kW. The mass flows and heat flows of the same case are not drawn. The values illustrate the data and are derived from typical efficiencies; they are not those of the study the architecture is taken from.

One flow of each category of this case, and the specification of the case, which switches the battery on through the control device of its connection:

<powerBreakdowns>
    <staticCases>
        <staticCase uID="takeOff">
            <name>Take-off</name>
            <specification>
                <altitude>0</altitude>
                <machNumber>0.2</machNumber>
                <environment>
                    <atmosphericModel>ISA</atmosphericModel>
                </environment>
                <configuration>
                    <controlElements>
                        <controlElement>
                            <controlDeviceUID>batteryContactor_pod1</controlDeviceUID>
                            <controlParameter>1</controlParameter>
                        </controlElement>
                    </controlElements>
                </configuration>
            </specification>
            <powerBreakdownData>
                <powerFlow>
                    <name>Battery to power management unit</name>
                    <connectionUID>batteryToPmu_pod1</connectionUID>
                    <electricPower>
                        <electricPowerValue>147100</electricPowerValue>
                        <directCurrent>800</directCurrent>
                    </electricPower>
                </powerFlow>
                <powerFlow>
                    <name>Motor shaft</name>
                    <connectionUID>motorShaft_pod1</connectionUID>
                    <mechanicalPower>
                        <mechanicalPowerValue>408200</mechanicalPowerValue>
                        <torque>649.6</torque>
                    </mechanicalPower>
                </powerFlow>
                <powerFlow>
                    <name>Compressed air</name>
                    <connectionUID>airSupply_pod1</connectionUID>
                    <massFlow>
                        <massFlowValue>0.4221</massFlowValue>
                        <singlePhaseMassFlow>
                            <pressure>253300</pressure>
                            <temperature>411.3</temperature>
                            <massComposition>
                                <species>
                                    <share>1</share>
                                    <type>Air</type>
                                </species>
                            </massComposition>
                        </singlePhaseMassFlow>
                    </massFlow>
                </powerFlow>
                <powerFlow>
                    <name>Coolant loop</name>
                    <connectionUID>coolantLoop_pod1</connectionUID>
                    <heatFlow>
                        <heatFlowValue>370000</heatFlowValue>
                        <sourceTemperature>353.15</sourceTemperature>
                        <sinkTemperature>343.15</sinkTemperature>
                    </heatFlow>
                </powerFlow>
                ...
            </powerBreakdownData>
        </staticCase>
    </staticCases>
</powerBreakdowns>
Static case with one flow of each category

Attributes

NameTypeConstraintsUseDefaultDescription
@externalDataDirectoryxsd:stringoptionalDirectory of the external file the element was read from, as URI
@externalDataNodePathxsd:stringoptionalPath of the parent element in the merged dataset, at which the element was inserted from an external file
@externalFileNamexsd:stringoptionalName of the external file the element was read from

Child elements

NameTypeConstraintsOccurrenceHow often the element may appear at this place. The schema writes it as minOccurs and maxOccurs on the declaration.DefaultDescription
sequenceThe children below must appear in exactly this order. Each may repeat as often as its own occurrence allows.
staticCasesstaticCasesType[0..1] optionalCases at a single flight condition
transientCasestransientCasesType[0..1] optionalCases along a trajectory

Used by

In a dataset · 1 path

In the schema · 1 declaration

TypeName
aircraftAnalysesTypepowerBreakdowns