9. Technical and Other Requirements Related to the Use of the NEN System

9.1. Recommended hardware and software configuration of a NEN System User

9.1.1 The recommended hardware and software configuration for the NEN System User's workstation, enabling the proper use of the NEN system and access to all NEN system services and functionalities, are as follows:

9.1.2 NEN System Users can verify the compatibility of their devices with the hardware and software requirements using the testing component available on the public portal of the NEN system Compatibility Test.

9.1.3 When using the NEN system, document formats that comply with section 4 of the Decree of the Ministry of the Interior No. 194/2009 Coll., laying down the details of using and operation of Information system of Data Boxes, shall be used.

9.2. Encoding, encryption, public key certificates

9.2.1 The NEN system website is encoded in the UTF-8 character set. Data between the client (browser) and the server are transmitted encrypted using the HTTPS protocol. For this purpose, a server certificate issued by the Certification Authority Thawte is installed on the server.

9.2.2 Contracting authorities are recommended to test and verify the functionality of their encryption key before commencing a procurement procedure for each administered public contract that will utilize encrypted submissions.

9.2.3 The NEN system enables the generation of a certificate for encrypting and decrypting the submissions (of tenders) from economic operators. Certificate generation takes place on the client side. The certificate with the private key is not stored in the NEN system. In the event of a lost certificate with the private key, it cannot be restored from the NEN system, and it will no longer be possible to proceed with the procurement process.

9.3. Attachment size

9.3.1 The NEN system supports attaching files up to a maximum size of 100 MB per file. The system supports bulk attachment of multiple files using the "drag and drop" method, with the total size of the uploaded files limited to 1 GB.

9.3.2 Larger attachments must be divided into separate files using the ZIP algorithm. The ZIP format with extensions ZIP and 001, 002, etc., is supported.

9.3.3 In the case of an exported ZIP file containing data related to the procurement procedure, the size of the generated ZIP file can be individually adjusted, with a size limit of 2 GB.

9.4. Compliance demonstration of the NEN system with requirements for electronic tools

9.4.1 The NEN system is certified pursuant to the Decree No. 260/2016 Coll., on determining detailed conditions relating to electronic tools, electronic actions in public procurement and the certificate of conformity.

9.5. Licensing conditions

9.5.1 The legal owner of licenses for software directly used in the NEN system or required for the operation of the NEN system is the NEN System Administrator. Additionally, officially freely distributed and free of charge third-party software may be used for the operation of the NEN system.

9.5.2 The NEN System Operator is not authorized to transfer any license fees for software required for the operation of the NEN system to NEN System Users or condition the use of the NEN system for NEN System Users by purchasing licenses that are not customary for regular work with the NEN System User's workstation.

9.6. Providing basic information of the public contract on the contracting authority's profile in a structured format

This feature is used to download data about public procurement of a contracting authority within a definite range specified by the "from" and "to" dates. The output will include data on public contracts that have been published on the profile of the contracting authority within the specified time period.
This feature is based on the requirement stated in Annex No. 8 to the Decree No. 168/2016 Coll., on publication of forms for the purposes of the Act on Public Procurement, as amended. It adheres to the basic principle of ensuring transparency in public procurement.

Description of the data structure generated at the start of a procurement process:

1. The list of public contracts initiated pursuant to the Act No. 137/2006 Coll., on Public Contracts, as amended, is generated in the XSD structure pursuant to the Decree No. 133/2012 Coll., on the publication of notices for the purposes of the Public Procurement Act, as amended.

2. The list of public contracts initiated pursuant to the Act No. 134/2016 Coll., on Public Procurement, as amended, is generated in the XSD structure pursuant to the Decree No. 168/2016 Coll., on the publication of forms for the purposes of the Act on Public Procurement, as amended.

3. The list of public contracts initiated pursuant to the Act No. 137/2006 Coll., on Public Contracts, as amended, which will require intervention (e.g., indicating the actual price paid) is generated in the XSD structure pursuant to the Decree No. 168/2016 Coll., on the publication of forms for the purposes of the Act on Public Procurement, as amended.

Description of XML generation based on the "from" and "to" dates:

• this describes the determination of which public contracts should be in the XML and in what structure
  From XX.XX.XXXX to 30.9.2016 - XML is generated pursuant to the Decree No. 133/2012 Coll. From 1.10.2016 to XX.XX.XXXX - XML is generated pursuant to the Decree No. 168/2016 Coll.

Description of XML content based on the "from" and "to" dates:

• general rule regardless of changes in legislation;

• determination of which version of the public contract should be included in the XML, whether the latest or valid within the required time period.

XML generated in September 2016 - will contain data current as of September 2016 (at the time of generation).
XML generated in January 2017 - will contain data current as of January 2017 (at the time of generation).
The XML will always contain the current format of the public contract to the time interval of generation to ensure that the applicant always receives the same response when querying the same period.

The latest information on the public contract will be provided to the contracting authority if the "to" interval is the current date.

The query range must not simultaneously include contracts under the ZVZ and the ZZVZ, thus excluding the date of October 1, 2016 (the effective date of the ZZVZ). If the NEN System User enters this incorrect “from” and “to” range to export the profile, they will be shown a user message about this fact. This situation occurs when the user enters a range that includes contracts under both the ZVZ and the ZZVZ, for example, from=24.9.2016&to4.10.2016.

However, if the NEN System User wants to display data for this period, they need to search for it as 1) from=24.9.2016&to30.9.2016 and 2) from= 1.10.2016&to4.10.2016. The date 1.10.2016 must be the boundary value of the searched period.
A public contract will be included in the selected interval only if it has been published on the contracting authority's profile during that period.