Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Structure assets

Even in a rather small project, an extremely large number of assets accumulate very quickly.

To keep track, it is therefore extremely important to structure assets in a meaningful and traceable way.

eliona offers 2 ways to structure and display assets:

  • Functional sorting

  • Geographical sorting

Nesting of assets

Assets can be nested within one another. Nesting is a hierarchical organization of assets. An asset is assigned a parent asset.

Example

The asset "Land" contains the asset "Building".

The asset "Building" contains an asset "Floor".

The asset "Floor" contains the asset "Room".

The asset "Room" contains the asset "Sensor".

The nesting then looks as follows: Land > Building > Floor > Room > Sensor

Geographical sorting

Geographical sorting displays assets sorted by location. This allows you, for example, to see all sensors located on a floor at a glance.

Functional sorting

Functional sorting sorts assets according to their affiliation with a higher-level system.

Example:

In a building there is a ventilation system. This ventilation system is distributed throughout the entire building: the control system is in the basement, in all rooms there are several fans and temperature sensors each, and there are more fans on the roof.

For eliona, each individual fan, temperature sensor, etc. is a separate asset.

With geographical sorting, it would be extremely difficult to keep track of each individual asset. The user would have to navigate to each individual floor and each individual room just to see a few assets.

In addition, the user would have to know exactly how many assets there are in total.

Functional sorting makes everything much easier: there is one asset for the entire ventilation system. All assets that functionally belong to the ventilation system are subordinate to this asset.

Last updated

Was this helpful?