Skip to main content

Energy Consumption

Energy Consumption is primarily determined by the **Runtime Energy Consumption **. In cases where additional energy is consumed by an asset which does not directly relate to runtime, Custom Energy Consumption may be modelled as well.

Direct Energy Consumption

The Direct Energy Consumption property is measured in Kilowatt Hours per Month and represents the amount of energy required to operate the single asset while it is active.

Typically, conceptual assets like Business Processes or Applications do not consume any energy. In an on-premise scenario, the usual contributors are physical hardware assets such as Physical Servers, Storages and network devices.

In a cloud context, the cloud provider forwards the energy consumption of services to the consumer. If you are using a Virtual Server which is provided by a cloud provider, that Virtual Server will have a Direct Energy Consumption attached to it even though it is not a physically tangible asset.

Total Energy Consumption

The Total Energy Consumption property is measured in Kilowatt Hours per Month and represents the amount of energy required to operate the asset and any asset it directly or indirectly depends upon.

In the example above, the Energy Consumption of App 1 is computed as follows:

Cost NameFractionEffective Energy Consumption
App 1 Direct Energy Consumption100%0 kWH
100% of VM 1 Total Energy Consumption100%4 kWh
100% of DB 1 Total Energy Consumption100%8 kWh
Total Energy Consumption12 kWh

Just like other Cost Model components, Energy Consumption is subject to Cost Splitting. If multiple assets rely on a single underlying asset, the Energy Consumption will be split accordingly. For example:

In this example, the Energy Consumption of App 1 is computed as follows:

Cost NameFractionEffective Energy Consumption
App 1 Direct Energy Consumption100%0 kWH
VM 1 Total Energy Consumption50%2 kWh
DB 1 Total Energy Consumption100%8 kWh
Total Energy Consumption10 kWh

Here we perform an even split which is suitable in most situations. You can also customize this behavior using Distribution Weights.

Custom Energy Consumption

In addition to the predefined Runtime Energy Consumption, Txture supports custom energy consumption as well. It can be used to account for any consumed energy which is not covered by the runtime alone, such as energy consumption for hot-standby systems.

Custom Energy Consumptions are modeled using regular properties. Add the desired properties in the Structure Editor and ensure that they are tagged with the semantic tag Direct Custom Energy Consumption. An arbitrary number of these properties may exist per Asset Type. Every individual Direct Custom Energy Consumption property must be measured in Kilowatt Hours per Month.

When using custom energy consumptions, it is often desirable to have a per-asset summary of the custom costs as a property. Add a property in the Structure Editor, and tag it with the semantic tag Total Custom Energy Consumption. The Direct Custom Energy Consumptions of the asset (plus its associated Total Custom Energy Consumption from child assets) will be written into that property. This is also illustrated in the following example:

The property names in the example above only serve illustrative purposes. These properties can be named arbitrarily, as long as they are tagged correctly with the corresponding semantic tags, as shown in the example.

Different Asset Types can have different Custom Energy Consumption properties

Different Asset Types may have different Direct Custom Energy Consumption properties. There is no need to use the same set of custom energy consumption properties on every Asset Type. Please keep in mind that all custom energy consumption properties will be aggregated into the single Total Custom Energy Consumption property, which should be the same across all Asset Types.

The calculation of the Total Custom Energy Consumption is subject to cost splitting if an asset is utilized by more than one parent. This mechanism is identical to the cost splitting for Runtime Energy Consumption and and can be fine-tuned via Distribution Weights.

Grand Total Energy Consumption

The Grand Total Energy Consumption property of an asset is measured in Kilowatt Hours per Month and is the sum of:

  • Its Total Runtime Energy Consumption
  • Its Total Custom Energy Consumption

Please note that all of these sub-totals already include associated energy consumptions from the child assets.