Compliance requirements
A bidder may be excluded if, by the submission deadline, it has unpaid and unscheduled national tax, payment or environmental charge arrears of EUR 100 or more. Arrears are treated as scheduled only if they have been rescheduled lawfully and payments under the schedule have been made. The contracting authority will check Estonian bidders against public tax records. A foreign bidder must provide a certificate from the competent authority in its country of establishment, issued no more than 30 days before the submission deadline; if no such certificate is issued, it must provide an explanation and its own confirmation.
The bidder must have filed all annual reports whose filing deadlines have passed by the submission deadline. The contracting authority will check Estonian bidders against public register data. A foreign bidder must provide equivalent evidence from the competent register or authority; if filing is not mandatory or such evidence is unavailable, it must explain this and submit its latest approved annual report.
The bidder must not be bankrupt or in liquidation, have suspended business activities, be subject to bankruptcy or liquidation proceedings, be undergoing compulsory dissolution, or have received a warning of removal from the register. The contracting authority may check this until the contract is signed. A foreign bidder must provide equivalent evidence from its competent register or authority, or its own confirmation if such evidence is unavailable.
Qualification criteria and exclusion grounds
The bidder’s average net turnover over the three most recent financial years completed by the date the contract notice was published must be at least EUR 500,000. If the bidder has operated for fewer than three financial years, the average is calculated over its completed years of operation. For a joint tender, the members’ turnover is aggregated. The bidder must provide turnover figures by financial year; Estonian bidders’ figures will be checked in the business register. If the bidder has a valid reason for not providing the information, it may demonstrate its financial standing using another document accepted by the contracting authority.
The bidder must have successfully completed at least one connected-device and cloud-service development project, accepted by the client within the 36 months preceding publication of the contract notice, whose result reached pilot or serial production. The bidder must describe the project, client, its role and the acceptance date, and provide the client’s confirmation or contact details for verification. Joint tenders and reliance on another entity’s capacity, including a subcontractor’s, are permitted; the relevant entity must provide a commitment.
The offer must confirm that the solution meets all Must and Should system requirements. The completed price form must include the hourly rate, and the proposed milestone dates must not be later than the latest dates in section 3 of the technical description. Assumptions in the price form and schedule must not restrict the requirements, make the offer conditional, or require greater or earlier input from Miridon than specified in section 13 of the technical description.
The bidder must submit six short descriptions, K1–K6, in one PDF, each on a separate page of no more than one A4 page and in at least 11-point type. The project manager must be able to communicate in Estonian. The offer, including the short descriptions and key-person project descriptions, may be in Estonian or English; evidence in another language must be accompanied by an Estonian or English translation. Acceptance tests will take place at Miridon’s premises in Estonia.
The bidder must accept the ownership and handover terms in section 14 of the technical description and identify any pre-existing intellectual property to be used, including its name, description and use in the solution. The licence specified in clause 12.3 of the purchase contract applies to that intellectual property. The bidder must identify all subcontractors and the part of the work assigned to each, or state that none will be used.
The bidder must name five key personnel: a project manager, electronics engineer, firmware engineer, software and cloud engineer, and mechanical engineer. One person may fill up to two roles. For each key person, the bidder must provide comparable project information using the prescribed form, including the product and a brief description; the person’s role and work; participation period; the month and year the product reached pilot or serial production (or, for the software and cloud engineer, entered production use); whether the electronics or firmware project involved a battery-powered, low-power device; and a client contact able to confirm the project. A key person who is not the bidder’s employee must be identified through their employer as a subcontractor. The named personnel must perform their assigned roles; replacement is permitted only by a person with equivalent experience and with Miridon’s prior written consent. Only projects entered on the required form will be assessed.
If the bidder offers an equivalent instead of a referenced standard, specification, product or production method, it must identify the equivalent and the reference it replaces and explain why it is equivalent. The bidder must meet the quality threshold: the combined K1–K6 technical approach score must be at least 9, no K1–K6 score may be zero, and each key-person role must have at least one comparable project. Offers that fail the threshold will be rejected.