SITREP arendus- ja hooldustööd

This compliance-only document merely lists six mandatory “yes/no” declarations (4-month bid validity, no sanctions, EU/EEA/WTO location, etc.) and warns that at each mini-competition under the SITREP framework you will have to submit CVs of developers who already meet the (unstated) skill requirements in PEE Annex 3.2—so if you cannot instantly field those exact profiles, skip the bid.

This document is merely the blank template for the joint-bid authorisation form (Lisa 3.1) that must be filled in and uploaded only if the offer is submitted as a consortium; it contains no technical requirements, qualification criteria or evaluation rules.

This is a 100% price-based (lowest hourly rate wins) framework tender for full-stack SITREP system development & maintenance services where any compliant bidder will be admitted to the framework and later compete in mini-competitions, so bid only if you can offer the cheapest full-stack developer hour and are prepared to team up or subcontract.

This is only the explanatory Hankepass template for the Estonian Ministry’s “SITREP development & maintenance” open tender – it shows bidders the electronic ESPD questions on company data, size and contact details but contains no mandatory technical/financial criteria, so firms must wait for the full procurement documents to decide whether to bid.

This document contains only Siseministeeriumi infotehnoloogia- ja arenduskeskuse’s (SMIT) standard “Framework Agreement General Terms & Conditions” (mandatory for every supplier) and gives no specific technical, qualification or award criteria for the SITREP development/maintenance tender itself.

This is only the draft framework-agreement template for the “SITREP development & maintenance” tender; it shows that SMIT will sign multi-supplier framework contracts (no lotting) and award individual jobs through mini-competitions, but it contains no mandatory technical requirements, qualification thresholds or award criteria—bidders must wait for the full procurement documents to decide whether to bid.

This mandatory Git-based source-code-management document requires bidders to use SMIT’s GitLab instance, follow Git-flow or feature-branch workflows, create JIRA-linked pull-requests that pass automated Bamboo builds and SonarQube quality-gates, and allow SMIT code review before any delivery—so only firms already fluent in CI/CD tooling and willing to work wholly inside SMIT’s toolchain should pursue the SITREP development/maintenance framework contract.

This mandatory framework tender for SITREP system development/maintenance (SMIT) requires bidders to deliver microservice-based, containerised Java solutions that pass SMIT’s CI/CD pipeline (Bamboo/SonarQube), run ≥2 instances, use UTF-8/i18n, English code/comments, Estonian business terms, and are hosted on SMIT’s platform—firms must prove prior public-sector Java/DevOps experience and ability to join future mini-competitions.

This is a technical description (not a tender notice) of Estonia’s SITREP crisis-reporting web system (Java Spring Boot + PostgreSQL back-end, Vue.js front-end) that merely explains the existing architecture; it contains no mandatory requirements, qualification thresholds, selection or award criteria, deadlines, prices or submission rules, so it cannot be used to decide whether to bid—companies should wait for the full procurement documents.

This mandatory CV template requires at least 36 months of full-stack development experience and 36 months of Java SpringBoot usage, making it suitable only for seasoned developers who can document these exact qualifications.

This is a single-lot framework tender for mandatory SITREP system development & maintenance services where bidders must submit a full-stack developer CV (Lisa 3.2), comply with SMIT’s source-code and technical standards (Lisa 2.1-2.2), and will be ranked solely on price in subsequent mini-competitions, so only IT firms able to offer lowest hourly rates while meeting these fixed technical requirements should bid.