1. Initiatives

    Welcome to the initiatives section of APPLiA.

Specific explanatory notes for each column


For easier overview column B references to the letters a - f of Article 12.5 of Regulation (EU) 2017/1369 (see also above).


For easier overview column B references to the letters a - f of Article 12.5 of Regulation (EU) 2017/1369 (see also above).

(a) a general description of the model, sufficient for it to be unequivocally and easily identified;

(b) references to the harmonised standards applied or other measurement standards used;

(c) specific precautions that shall be taken when the model is assembled, installed, maintained or tested;

(d) the measured technical parameters of the model;

(e) the calculations performed with the measured parameters;

(f) testing conditions if not described sufficiently in point (b).

(n/a) not applicable is used when a value is a technical parameter, that is neither clearly measured nor calculated. Yet, the authors of the template propose to enter that value for clarity's sake.


Proposal for a unique identifier of the respective values. Can be used in future when parameterised XML transfer might be possible. Will also be helpful in case different suppliers would choose templates with the same content but in a modified order


Textual description of the field


Will be used by the supplier to enter the values of the technical information to be registered. These can be measured parameters, results of calculations or textual explanations. It is important, that acc. to Article 12.6 of the framework directive When data other than those specified in paragraph 5 or not available in the public part of the database would become necessary for market surveillance authorities and/or the Commission for carrying out their tasks under this Regulation, they shall be able to obtain them from the supplier on request


Physical unit of the value.


In practice the format of the value or prameter is relevant, eg whether a figure is given as 3.10 or 3.1.

There are several notations for how to distinguish between data types, none of them universal. For these templates we use the following notations


INTEGER --> non-fractional (natural) number, here only positive , eg 3, 190, 0, 55...

NUM/x, where 'x' is an integer --> a floating point decimal number, where x is the number of fixed digits, eg NUM/2 could be 2.32 or 0.10 or 3.00, the value must have the expected numbers of digits
NB: actually NUM/0 equals integer, however, for clarity we use INTEGER for NUM/0.

FLOAT --> any a floating point decimal number, with no predefined number of fixed digits


STRING/x, where 'x' is an integer --> a sequence of x alphanumeric characters. The alphanumeric character could be any of the alphapet or any special character, except (to be future proof the following reserved XML characters <  & (possibly also > ' " and should also be avoided, but that will depend on the EPREL XML parser.

Other data types

BOOLEAN--> logical value, can be either TRUE or FALSE

ENUM --> is a list of fixed and defined values, values are usually strings or characters (notation also used in EPREL documentation), eg ENUM --> 'A+++', 'A++', 'A+', 'A', 'B', C', 'D',  in this template the list is given as comment 1.

hh:mm --> a time length where hh and mm are positiv integers. hh represent the hours and can be any integer, mm are minutes and ranges from 0 - 60


Whereas Column C gives the reference to the framework regulation 2017/1369, here reference is made to the Article or Annex in the specific delated act, which is here usually – if not mentioned otherwise – Regulation (EU) 1061/2010.

For instance, this is important for calculations according to Art 12.5.(e) because often the formula can be found at the quoted place.


This template has been developed within the respective product specific working group of APPLiA to the best of the knowledge of the participating persons and companies.

By no means APPLiA claims that this is the only way to meet the legal requirements. Any supplier bears the responsibility for the correctness and completeness of the uploaded data when registering a product model.