Click to configure > Consumption types

This window allows configuration of all the consumption types that the system will consider. Please notice the difference between consumptions and inputs.

In the lower part: you will see a grid with the consumption types already configured, on which you can perform operations on the grid such as Insert, Save or Delete.

In the upper part: you will see the configuration of each record, where you can configure the parameters of a new insertion or edition.

CONFIGURATION PARAMETERS:

    • Code: code of the consumption type. For example: ELEC1, COST2...
    • Description: description of the consumption type.
    • Equivalence: numerical factor that will multiply the quantity read from monitoring sensors. For example: if the power meters provides Watts and we need to analyze KWs, we will multiply the number obtained by the monitorization sensor by 1/1000. We will put 0,001 in this field.
    • Units: the unit of the consumption type. The options shown will be the measurement units already configured.
    • Cost check: activate it if the consumption type is an economical cost. For examples: wages, salaries, etc.
    • Incentive check: activate it if the consumption type is used as an incentive. Generally used with employees, where an incentive will be calculated based on the activity ratio and the activity objective.
    • Auto check: consumptions can be associated with employees, processes and results. If you associate a specific consumption to each one of them in the button [Theor. Cons] of the windows: "Resources", "Process-Status-Result", "Process" and "Results", a consumption will be automatically calculated based on the time spent. For example: if an employee has associated consumption of x€ per hour, each hour spent working on a process will automatically calculate the consumption of that employee.

NOTE: for more information, please see: Theoretical Consumption

    • Currency: the currency that will be associated with this consumption. The options shown will be the currencies already configured.