Systems of the vehicle: the installed equipment in <genericSystems> and the flight control data in the remaining nodes.
The system description is organized in three levels. The library of system elements (systemElementsType) under <vehicles> defines each kind of equipment once, with its geometry and its mass. <genericSystems> installs these elements as components in the vehicle and groups them into systems (genericSystemsType). The system architectures of the model describe how the components are connected (systemArchitecturesType), and the power breakdowns of the analyses give the power that flows along these connections for a flight condition (powerBreakdownsType).
The figure follows one piece of equipment through the levels, the fuel cell stack of a propulsion unit. It is defined once in the library, installed as a component, connected to the power management unit, and the power it delivers at take-off is given for that connection. The installed components and the system architecture together form the level of the model, so that the figure shows four boxes for the three levels. Each box references the one before it by its UID.
The flight control nodes <cockpitControls>, <commandCases>, <controlDistributors> and <controlLaws> predate this system description and are not linked to it. They are described on their own pages.
The figure shows the order in which the flight control nodes act: a cockpit control, e.g. the roll stick, commands a command case, e.g. a roll, which reaches the control elements through a control distributor, directly or through a control function.