Preparing the account to use DEXMA Detect

This article includes information about how to configure Detect in the platform. Please note that the configuration is shared among Detect, Analyse and Optimise products.
This article is divided into the following sections:


Requirements to start using DETECT

Indispensable information

In order to start using DETECT you need, at least, the following information:

  • Electricity monthly consumption for, as a lower limit, 12 months. 18 months of data would be the optimal.
    • Data can be inserted with quarter-hourly, hourly, weekly or monthly frequencies. Hourly or quarter-hourly frequencies would be optimal but monthly frequencies are sufficient to use the product.
  • Information required about the buildings under study:
    • Their zip code (their whole address would be preferable but not indispensable)
    • Area (recommended but not indispensable)
    • Activity (needed to compare this building with similar buildings)
    • Reference temperatures used in that building for degree days calculation

Additional information

Including more than the basic information in your account, might unlock more functionalities and recommendations. Here is what you could add:

  • Supplies and Prices: This way, the energy costs will be calculated using your own tariff structures. 
  • Tags: You can add more information to your buildings to later filter the results offered by Detect.
  • Financial CAPEX and OPEX information: You could add your own CAPEX and OPEX values in order to customise the energy efficiency measures that are recommended among your buildings. Please note this cannot be performed directly in the platform and should be discussed with the team.


Detect's configuration process

The complete configuration flow you should follow in order to start using Detect, can be seen in the following scheme:



* Compulsory steps, considered as Basic configuration steps.


All the steps that have a rectangle can be done directly in the platform or in-bulk. All the steps that have a rhombus, should be performed directly in the platform's UI. In the following sections, you will be directed to other articles to help you follow each step.

If the language included in the graph is unfamiliar to you, don't hesitate to visit our platform's glossary. If you still would like to learn more, don't hesitate to ask the team for the on-boarding emails.


Basic configuration steps

In this section, you are going to learn how to include the basic information into the platform. This is the information required to use Detect. Please make sure you already have an account created on the platform (if not, contact the team).

This section is divided into:


Data insertion


There are multiple ways for you to insert the monthly electrical consumption into the platform. Please check the article explaining how to import data into the platform. Among the options described in the article, it is recommended to use excel import or FTP import.

Once the data has been introduced into the platform, you should accept the devices that have been created.


Locations creation


The way to organise the information in the platform is through the creation of locations. When creating them, you will be able to include all the needed information described in the previous section.

To create each location individually, please follow these steps. To create them in-bulk, please follow these steps. Please set the area only if it is known. Otherwise, set the area to 1 m2.


Note. If you have lots of buildings, you might be interested in organising them, i.e. not only creating the locations but also other entities to better organise them. For example, you could organise all your buildings geographically or by business model. This organisation is called the locations' hierarchy tree and can be created individually or in-bulk, by following the same steps as for the locations' creation.



Link devices to locations


Please follow this step in order to link your devices with your locations. The step should be performed in the locations' section of the UI or could be performed in-bulk.



Additional configuration steps

Use of tags

You could include more information about your buildings to later filter the results provided by Detect. Also to complement the basic information provided in the Basic steps. You could, for instance, include tags for:

  • The schedule of your buildings: Compare those buildings that are open during weekends vs. those that are not.
  • Available area for solar panels: Determine the maximum area that could be used in the building to install solar panels.
  • LEDs: Determine if a building has already switched to LEDs or not to better customise the recommendations.
  • Any other information you might find relevant to define the type of buildings you wish to include. As an example for a hotel:
    • Number of rooms
    • Is there a restaurant?
    • Is there a spa?
    • Is there a gym? ...

Please note that part of this information will only help to benchmark the buildings between them once the results have been provided. The rest will be used to customise the recommended energy efficiency measures.


So, how to include this information? Tags* are configured when creating the locations, both when creating the locations individually or during the in-bulk configuration process.

* There is a maximum of 50 tags per building.


Supplies and prices configuration


In case you would like to include energy costs in the platform, you could do it directly in the platform or by using the in-bulk configuration. If you don't have this information, Detect will use a price by default. There are two approaches that could be recommended in order to configure prices: 

  1. Configure a tariff structure for each building individually: This will allow you to calculate with a higher level of detail the energy costs and possible savings of each building.
  2. Configure some tariff structures and use them as templates for all the buildings: This would save you time while configuring the account but would still increase the exactitude of the calculations (vs. using the by-default price). In Spain, an example of templates would be to create: One tariff 2.0, one tariff 3.0A, one tariff 3.1A and one tariff 6.X.

For both options, you should read our articles explaining how supplies and prices are organised on the platform.

Was this article helpful?