Currently, the EPREL exchange model only allows for the upload of technical documentation in the form of a PDF file.
The templates are in the form of an Excel sheet to allow directly inserting the respective values. 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 Article 12(a) to (f) of Regulation (EU) 2017/1369. It could be then uploaded into EPREL.
This can be done:
- through the graphical web interface to EPREL
- by inserting it as annex to an XML file, joining both in a ZIP file and uploading that ZIP file manually
- by uploading the ZIP file by means of a system-to-system/e-Delivery interface.
In all these cases, reference to Article 12.5 has to be made (e.g., in the web interface by checking the boxes for mandatory upload for Article 12(a), (b), (c), (d), (e), (f)).
The column B in the respective template gives the reference to the relevant paragraph.
In its discussions with the Commission services, APPLiA has always proposed that the long-term objective was to work towards a parametrised data transfer of the compliance part information into EPREL, taking the example from the public part where this is implemented. This would mean that only values are transmitted whereas units and further description would not be necessary anymore. Such transfer would reduce upload traffic and it could ensure language neutrality from 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 parametrised data transfer value by value in xml would be possible, these fields could serve as identifiers 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 the templates are not dependent on an order, in case a supplier chooses to use a template but for technical reasons not in the same order. A value can always be identified by its Key Field Name.