Skip to main content

Using Area as a Divisor in Reports

In report templates, you can now use an entity’s area as a divisor for calculating specific consumption (e.g. kWh / m²).

There are two types of areas supported:

  • Individual areas – specific area values set for an entity (e.g. storage, sales floor, offices)
  • Aggregated areas – automatically calculated sums:
    • GLA – Gross Leasable Area
    • GFA – Gross Floor Area (GLA + shared + other)
    • TFA – Total Floor Area (GFA + extra)

Both types can be used as divisors in specific consumption calculations.

How Areas Work in the Entity Hierarchy​

Enectiva uses a tree structure (e.g. site → building → tenant).
Area values follow this structure:

  • Areas are entered at the lowest relevant level (e.g. tenant or unit)
  • Higher-level entities get automatically calculated area values as the sum of their children
  • The system automatically accounts for:
    • historical changes of area values
    • entity structure changes
    • manual overrides (if allowed)

Each entity always has a meaningful “current area” available.

Time-Based Area Validity​

Each area has historical values over time:

  • Area values can change over time
  • The report always uses the area valid during the reporting period
  • If the area has changed over time, different values will be used for different years

Example​

  • In 2024, the area was 1000 m²
  • In 2025, it changed to 1200 m²

→ Report for 2024 will use 1000 m²
→ Report for 2025 will use 1200 m²

Aggregated Areas (GLA, GFA, TFA)​

Aggregated areas are automatically calculated:

  • GLA = sum of all leasable areas
  • GFA = GLA + shared + other areas
  • TFA = GFA + extra areas

Key properties:

  • Calculated from individual areas of the entity and its subtree
  • Cannot be entered manually
  • Always reflect the current valid state of data

Using Area in Reports​

  • Areas can be used only as divisors in specific consumption calculations
  • Areas cannot be used as weighting factors
  • Typically used in these blocks:
    • SEIEOY
    • AEIEOY
    • and other blocks with specific consumption logic

Behavior for Zero or Missing Area​

  • If the area for a period is 0, the result will be invalid (division by zero)
  • If the area is not defined at all, specific consumption cannot be calculated

👉 Recommendation: Make sure all relevant entities have properly defined areas before using them in reports.

Summary​

  • Areas allow calculation of consumption per square meter
  • The system automatically:
    • sums areas in the hierarchy
    • handles time-based changes
  • Supported area types:
    • Individual areas
    • Aggregated areas (GLA, GFA, TFA)