genericSystemType

A system of the vehicle, e.g. the fuel system or the electrical power supply, with the components installed in it. Each component is an installed instance of an element of the library (systemElementsType). How the components are connected is described in a system architecture (systemArchitectureType).

A system may have no components. It is then only declared, so that the systems of a vehicle can be set up first and their components added later, e.g. by another partner.

Mass and center of gravity

The mass of a system is the sum of the masses of all its components, positioned or not. Its center of gravity is formed from the positioned components only; a component without position has a mass but no location (see componentType). This reflects the view of the system architect, who often knows the equipment and its mass before its place in the vehicle.

Relation to the mass breakdown

The mass breakdown (massBreakdownType) gives the masses top-down, e.g. the mass of all systems in <mSystems>, as they result from sizing. The systems here describe them bottom-up from the installed equipment. The two sums often differ, because the bottom-up description lacks the masses of details that are not modeled as components, e.g. brackets, fasteners or fluids.

The fuel cell system of one propulsion unit with its three components. The compressor is a body of revolution about the z-axis of its element and is turned by 90° about the y-axis, so that its axis lies along the x-axis of the aircraft:

<genericSystem uID="fuelCellSystem_pod1">
    <name>Fuel cell system, pod 1</name>
    <components>
        <component uID="heatExchanger_pod1">
            <name>Heat exchanger, pod 1</name>
            <systemElementUID>heatExchanger</systemElementUID>
            <transformation>
                <translation>
                    <x>9.36</x>
                    <y>4</y>
                    <z>0.45</z>
                </translation>
            </transformation>
        </component>
        <component uID="fuelCellStack_pod1">
            <name>Fuel cell stack, pod 1</name>
            <systemElementUID>fuelCellStack</systemElementUID>
            <transformation>
                <translation>
                    <x>11.35</x>
                    <y>4</y>
                    <z>1</z>
                </translation>
            </transformation>
        </component>
        <component uID="compressor_pod1">
            <name>Compressor, pod 1</name>
            <systemElementUID>compressor</systemElementUID>
            <transformation>
                <rotation>
                    <x>0</x>
                    <y>90</y>
                    <z>0</z>
                </rotation>
                <translation>
                    <x>10.9</x>
                    <y>4</y>
                    <z>0.55</z>
                </translation>
            </transformation>
        </component>
    </components>
</genericSystem>

System with three installed components

Attributes

Name	Type	Use	Description
`@externalDataDirectory`	`xsd:string`	optional	Directory of the external file the element was read from, as URI
`@externalDataNodePath`	`xsd:string`	optional	Path of the parent element in the merged dataset, at which the element was inserted from an external file
`@externalFileName`	`xsd:string`	optional	Name of the external file the element was read from
`@uID`	`xsd:ID`	required	UID

Child elements

Name	Type	OccurrenceHow often the element may appear at this place. The schema writes it as minOccurs and maxOccurs on the declaration.	Description
allThe children below may appear in any order. Each may appear at most once.
`name`	`stringBaseType`	[1..1] required	Name
`description`	`stringBaseType`	[0..1] optional	Description
`components`	`componentsType`	[0..1] optional	Components

genericSystemType

Attributes

Child elements

Used by

In a dataset · 2 paths

In the schema · 1 declaration