Understanding the hierarchy of locations

Follow

The platform provides a powerful tool for multi-location projects in which you want to keep a logical structure and have indicators by area quickly and efficiently.

The platform allows organising locations by hierarchical or geographical criteria. Therefore, this allows analysing your locations in a more detailed manner, for instance adding the energy consumption of electricity, gas, water ... To go back to the basics related to the locations, check out our article: What is a location?

This article includes the following sections:

  1. Elements of the hierarchy
  2. Golden rules about the hierarchy of locations
  3. Configuration of a hierarchy of locations
  4. Examples of different hierarchy of locations
     

Elements of the hierarchy

 The schema of the hierarchy in the platform is the following. We have 4 different elements explained below. 

01_ac3d515239b71440f6ef95c4674729fe50be71759d92c9e47699dda9f5ed6b16.png

 

  • Global: the root of the project
  • Zone: sublevel. It might represent a hierarchical zone or a geographical area (Europe, Spain, University Campus...)
  • Location: the platform's main logical unit. Depending on your account, a location can be a single office, a building, a factory, an airport, etc.
  • Sublocation: one step below the location. It represents one region of the location, for example: a  floor, a room, a zone of a building, etc

Depending on the element you create, you will be able to configure different things. The following table indicates the different possibilities that the elements can have:

02_0d60821dd77d6d84c8d43f254ebc932c098ed8366de88d93e3c91ec14ae3d618.png



 

Golden rules about the hierarchy of locations 

These golden rules about the hierarchy of locations should be taken into account before the hierarchy structure is decided.

  • Devices can only be associated with one element (root, zone, location or sublocation).
  • Several reports are configured through reference meters in certain locations. This means that only one device in that location or sublocation is going to be included in the report.
  • Ratios (or KPI) are applied to locations or sublocations. The ratios affect ALL the devices in that location or sublocation. 
  • Tags can only be applied to locations and sub-locations, so if you feel you will need them to benchmark your portfolio, take it into account!

The heritage concept

The heritage concept is the most important golden rule and should be the main reason to define how you will organise your hierarchy of locations. 

If you assign a device to a zone, the locations and sublocations below it will inherit the device assigned to that zone. Or if you assign a device to a location, it will appear also in the sublocations below. That will help to configure the projects quicker. For example, if some of your buildings are located in the same city, you can assign the devices from "Outdoor weather station" to the "Zone" (which represents the city), so all the locations below will inherit the corresponding weather device. So you just need to assign it once instead of configuring it in each location.

The heritage concept will be applied in all the configuration and visualisation menus. For example, if you are configuring the reference meters of a Sublocation, you will be able to select the devices which are in the location above. And if you are representing a graph, you will be able to display all the devices that are in the location above as well.

dexma-hierarchy-04.png

 

Following an example:

dexma-Understandingthehierarchyoflocations_01.png

- If the element of the hierarchy Sublocation 1 was chosen, the devices assigned to Test, Zone 1, Location 1, Sublocation 1 and Sub-Sublocation 1 would be the ones available. 

- If the element of the hierarchy Location 2 was chosen, the devices assigned to Test and Location 2 would be the ones available.  

- If the element of the hierarchy Test was chosen, ALL the devices in the account would be the ones available.

 

 

 

Configuration of a hierarchy of locations


In order to view the hierarchy tree, you should go to Settings > Locations > and click on the "Hierarchy tree" button. Here you can drag and drop the zones, locations and sublocations to the desired path. Just select the element and move it to the final element. 
 
dexma-hierarchy-02.png

 
 

View of the hierarchy of locations

You can visualise your account from a desired point of the tree. Thus, you can select each location quickly with the tool located on the top of the screen:
 
dexma-hierarchy-01.png
 
You can also use the tags configured in your locations to filter by tag. If you select a tag, only information belonging to the locations that have that tag will be displayed:
 
dexma-hierarchy-03.png
In this case, the tags represent buildings built in the decades of 2000 or 2010.


4. Examples of different hierarchy of locations

Use of location hierarchy and tags to filter by country or by type of building

dexma-hierarchy-05.png

In this example we use as the first level of hierarchy countries (in case the Company is acting in more than one country) and the second level of hierarchy as cities, both being zones (in green). The following level in the hierarchy would be locations and would represent a building in that specific city (in yellow). In the example we have two type of buildings, schools and hospitals, which have been tagged as such in each location configuration:

dexma-hierarchy-06.png

This distribution allows the comparison of buildings in the same region in both reports and dashboards. Moreover, it allows a report to be created for each specific location automatically.

Selecting the country level in the hierarchy, limits the analysis to those devices that are within the zones and locations under that country:

dexma-hierarchy-07.png

The tags also allow to filter the devices in the analysis screens by type of building:

dexma-hierarchy-08.png

Further more, we can use the hierarchy and tags in to analyse multiple devices in Advance Analytics, by aggregating the consumptions for all the locations under a hierarchy level, or to add only the consumption of those locations with a given tag.

Was this article helpful?