Introduction to Parameters

In this article we will show you the parameters that you can insert into the platform, as well as the methodology to follow for each type of variable. We'll also be explaining how does the platform's algorithm calculates all the data frequencies. Finally, we will share some extra tips to help you identify ans solve common issues.

All in all, the contents are:

• Introduction
• Available parameters
• How do parameters and their frequencies work?
• How do the calculations work?
• How can the inserted parameters be managed?
• Visualisation
• Golden Rules

Introduction

Our platform lets you visualise different type of data, in order to understand which types do you want to insert, we use the parameters.

A parameter is what allows us to understand which type of consumption or variable a device is monitoring. It is really important to correctly define a parameter, as alerts, visualisation of the values and other functionalities will depend on it.

It is important to understand that one device can have a lot of parameters but each of them must be unique. This means that you may have 15 parameters in one device but all of them must be different.

For example, if a datasource sends data from 2 gas sensors, in our platform this could not be represented by one device only, as it would cause the parameter gas to be repeated. Each sensor should be set up as a different device, each with its own gas parameter.

Available parameters

The platform accepts multiple parameters. We've listed all the available parameters and the units used for each one in the following spreadsheet:

Platform parameters spreadsheet

These parameters include both discrete and continuous variables. Each parameter has a 3-digit code. However, when inserting data, depending on the type of variable that is being inserted, some more digits may be necessary. 

Please go to section 3 to learn more about the insertion of parameters into the platform and the available frequencies for each of them.

How do parameters and their frequencies work?

In order to understand how a parameter can be inserted into the platform, we need to first explain the difference between discrete and continuous variables.

Instantaneous variables, such as temperature or power, are usually inserted using the 3-digits number shown in the excel file of the previous section: Available parameters.

Continuous variables, like consumed electricity and gas, can be added to the platform in two different ways:

1. Basic/accumulated parameter. The basic methodology implies data inserted cumulatively, i.e. every measure will be added to the previous one.
   This results in constantly increasing values and creates a link between the measures. This methodology is frequency-neutral, as it does not directly relate to a certain insertion frequency.

2. Discrete parameter. The discrete methodology implies that every measure will directly be uploaded into the platform, despite any prior measures.
   Every measure inserted into the platform will be independent of the others. This methodology directly relates to a specific insertion frequency.

Each device can store basic and discrete (or calculated) data for one parameter, but not two discrete or calculated frequencies. Be aware that if you store two resolutions, you will be using two datapoints.

Inserting with the basic methodology

While inserting through the basic methodology, you don't need to indicate the frequency you will be using, as the platform itself will identify it.

If data will be inserted through the basic methodology, the representation of each parameter will be the 3 digits that are represented in the excel file linked in the section: Available parameters.

When inserting data using this methodology, the software will carry out several calculations so as to determine the specific consumption for different frequencies. If you want to learn more about the calculations, you can navigate to the How do the calculations work? section.

Inserting with the discrete methodology

While inserting through the discrete methodology, you need to specify the frequency for sending data to the platform. You also need to indicate an "operation"  to understand the type of variable that is being monitored.

The code for discrete values' insertion is SSSFO, where:

• SSS is the 3-digit code for the parameter, as shown in the Available parameters section.
   

• F indicates the data insertion frequency. The following table lists the available values:

• Lastly, O represents the operation that will determine how the data has been discretised:

  Operation	O value
  Delta	1
  Average	2
  Maximum	3
  Minimum	4

  
  If you work with accumulated parameters (like electricity or water consumption), use the value '1'. The Delta operation means the value inserted is the difference between two time frames.
  E.g., active energy is 402, if we want to insert data as the consumption for the last 15 minutes the correct code would be 40201.
  
  If the parameter has instantaneous nature (such as temperature or power), choose a value from 2 to 4. The operation avg, max and min represent also time interval values.
  E.g. power's parameter ID is 401. If we want to insert average 15-minute power, the parameter would be 40102.

How do the calculations work?

To understand the calculations that the platform carries out once you introduce a parameter, we need to talk about the available frequencies that you be found in the platform:

• 5 minutes
• 10 minutes
• Quarter-hourly
• Half-hourly
• Hourly
• Daily
• Weekly
• Monthly

Note: For data sent in higher frequencies, we cannot assure you, the calculations will be made correctly, as the platform is designed to operate optimally with broader data resolutions.

Minute-level data can create unnecessary system load and may affect the reliability of certain calculations. For most energy management use cases, a resolution of 5, 10, or 15 minutes is usually sufficient and ensures stable performance and accurate results.

Calculations for discrete data insertion

When you insert discrete data, what you send is directly displayed in the analysis section in the frequency it has been inserted.

Imagine that data is inserted every half hour, and a value of 15 kWh is uploaded at 10:00h and a value of 20 kWh at 10:30h. Then, the hourly consumption could be calculated by adding the consumption of the two half-hourly introduced values, i.e. 35 kWh. If all the values of the day were uploaded, the same could be calculated for the daily frequency, and so on.

This procedure is exactly the one followed by the platform. Once you insert a parameter at a set frequency, the platform automatically calculates all smaller frequencies. I.e. if data is introduced every day: the weekly, monthly and yearly frequencies will be calculated. However, all the higher frequencies will remain blank.

This is why if you insert two frequencies using the same parameter, the calculations won’t match, because they are being mixed from the smaller frequency.

Note: If you are inserting data in a weekly resolution, the monthly resolution will not be calculated. This is due to the fact that months do not always start on the first day of the week, nor end on the last day of a week, and thus adding weekly calculations does not fully cover the monthly consumption in most cases. In order to not interpolate, the monthly data is not calculated, to be coherent with how the platform calculates lower resolution data.

Calculations for basic data insertion

How can the inserted parameters be managed?

After you start sending data to the platform, follow these steps to see and manage parameters from your devices:

1. Go to the Settings screen.

2. In the side menu, go to the datasources section.

3. Select the datasource where the devices are sending the data.

4. Once you find the device, click the Parameters option on its right to view them.

In this menu, you will be able to select and de-select all the parameters that have been received by your device.

In case you're receiving a parameter that is not useful to analyse, you have two options:

• De-select this parameter, and it will no longer cost a datapoint to you.

• Derive the parameter into a more useful one, e.g. from pulses to gas volume or energy.

Visualisation
 

Once you've introduced data and accepted the parameters, it is time to visualise them in the analysis screens. The table below shows which parameters are visible on each screen:

*Energy consumption refers to: 

• Electricity consumption

• Gas (kWh, volume and normalised volume)

• Water

• Diesel (kWh and volume)

• Produced electricity

• Thermal energy (heating and cooling)

• Compressed air volume

• Liquified natural gas

• Biomass

**On these functionalities you will be able to visualise every kind of parameters available on the platform.

***Please note that Power is included in the category "Others", together with Voltage and Current.

Golden Rules

1. Inserted data will prevail over data calculated.

2. "Discrete" data inserted always takes priority over "basic" (or cumulative) data inserted.

3. A device's parameter cannot have two discrete data resolutions at the same time.

4. When applying a cost to a certain consumption, the data needs at least a 30min resolution. Cost is not stored (nor charged) as a datapoint, but calculated over a consumption.

5. If discrete data is inserted outside its expected timestamp, it will be discarded. For example, if the platform expects data every 15 minutes but receives data at 13:59h instead of 14:00h, the reading will not be stored.
    

6. Discrete data with daily frequency is expected at 00h.