Initiatives

Initiatives

Welcome to the initiatives section of APPLiA.

Currently, the EPREL exchange model allows only for upload of the technical documentation in form of a PDF-file.

The templates are in the form of Excel in order to allow for directly inserting the respective values (in Column E, fields are marked in light blue). It could then be transformed into a PDF-file by means of well-known software tools. The resulting PDF-file would contain – if filled out correctly – the technical information as required in Art 12(a)-(f) of Regulation 2017/1369. It could be then uploaded to EPREL.

This can be done:

- through the graphical web interface to EPREL

- by inserting it as annex to an XML-file, join both in a ZIP-file and uploading that ZIP-file manually

- by uploading (when made available by the Commission) the Zip-file by means of a system to system interface.

In all these cases reference to Article 12.5 has to be made (eg in the web interface by checking the boxes for mandatory upload for Art 12(a),(b),(c),(d),(e),(f))

Column B therefore gives the reference to this Article.

In the discussion with the EC services APPLiA has always proposed that the long-term objective is to work towards a parametrised data transfer into EPREL, taking the example from the public part where this is implemented as best practice also for the compliance information. This would mean that only values are transmitted whereas units and further description are not necessary anymore. Such transfer will reduce upload traffic and it can ensure language neutrality at the supplier’s side.

To prepare for this, this Excel Template contains already so called Key Field Names or identifiers (Column C). When in future parameterised data transfer value by value in xml would be possible, these fields would serve as the identifier for the respective value. Key Field Names are not necessary for the current pdf-files, but still helpful. For instance, Key Field Names ensure that this template is not dependent on an order, in case a supplier chooses to use this template but for technical reasons not in the same order. A value can always be identified by its key field name.