For rules on how to use the fields, see Detail form.

• Template: Identifier of the template. It is unique in the application. This is initialized by the application, but it is preferable to change it to a more meaningful code.
• Name: Name of the reading point template for easier identification of the template.
• Unit: The name of the reading unit to be selected from among the units defined for the application.
• No. of decimals: Number of digits after the decimal taken into account in the reading values. Enter 0 if the readings are always whole numbers.
• Type: A reading point may be of the "simple" or "meter" type.
  • Select "meter" if the reading point has a value that always increases. You can then use it (among other things) to track costs. Upon reaching the maximum value, a meter will return to the minimum value.
  • Select "simple" if the reading point has a fluctuating value to be monitored and is not linked to a cost. In this case, the Type of cost and Unit price values are not accessible.
• Minimum Value and maximum Values: These are the limits of the authorized reading values. In the case of a reading point that returns to zero once the maximum value has been reached, such as an electricity meter (which will be a "meter" type), the minimum value is 0 and the maximum value is the one at which it returns to zero. These fields are required. If you do not have a precise maximum value, enter a very high number.
• Category: Value (from a modifiable list) allowing you to classify reading point templates.
• Type of cost: Type of cost to which the cost of the measured values is attributed. The cost type is to be selected from a list whose settings can be set by the application administrator (see Values list).
• Unit price: Price of the unit of measure. For example, with an electric meter you enter kWh as the unit and €0.50 if the price is 50 cents per kWh.