Národný emisný informačný systém II (NEIS II)

The contract timeline is as follows:

The contract start date, referred to as the commencement of the work (T0), is the next working day after the client dispatches a "Call" (Výzva). The contractor is not permitted to begin work before receiving this "Call".

The total duration for the performance of the work is a maximum of 29 months from the start date of the performance.

Key milestones and phases include:

• The contractor is required to prepare a detailed schedule for the work within 7 calendar days from the start of performance. This detailed schedule must adhere to the framework time schedule in Appendix No. 2 and the financial schedule of invoicing milestones in Appendix No. 3.
• The detailed schedule must propose a division of the work into Increments, with each Increment being a standalone functional unit ready for handover and acceptance.
• The detailed schedule only becomes effective upon approval by the Project Steering Committee.
• The overall "Realization phase" spans 29 months, starting from the commencement of the work performance. This phase includes the following sub-phases and associated invoicing milestones:
• Analysis and Design: This phase is scheduled to conclude by T0 + 6 months and represents the 1st invoicing milestone.
• Implementation and Testing: This phase is scheduled to conclude by T0 + 24 months and represents the 2nd invoicing milestone.
• Deployment and Trial Phase: This phase is scheduled to conclude by T0 + 29 months and represents the 3rd invoicing milestone.

The core scope of work for this tender involves the delivery of a functional, stable, efficient, and secure NEIS II (National Environmental Information System II). This system is intended to support data management and quality for the agenda of the Slovak Hydrometeorological Institute (SHMÚ) and ensure compliance with legislative requirements under Laws No. 146/2023 Z. z. and 190/2023 Z. z.

The Statement of Work (SOW) summarizes the project into a "Realizačná fáza" (Implementation Phase) lasting 29 months, followed by 48 months of "Podpora prevádzky (SLA)" (Operations Support (SLA)) from the date of work handover.

The core deliverables and phases include:

• Analysis and Design Phase (Analýza a Dizajn): This phase, lasting up to T0* + 6 months, includes detailed solution design, requirements analysis (functional, non-functional, technical), user research, motivational architecture, business architecture (existing and target), process descriptions, information architecture, user journey mapping, graphic design, UX/UI prototyping (optional), data architecture, application architecture, integrations (OpenAPI), technological architecture, specifications for software licenses and source codes, Service Level Agreement (SLA) and performance requirements, availability, backup and recovery, security requirements, data migration strategy, and implementation/deployment schedules.
• Implementation and Testing Phase (Implementácia a testovanie): This phase, lasting up to T0 + 24 months, involves development, data migration, integrations, and various testing types: functional testing (FAT), system and integration testing (SIT), load and performance testing, security testing (SW/HW and cybersecurity), user experience testing (UX), and user acceptance testing (UAT). Documentation deliverables include an Application manual, User manual, Administration manual, Installation manual, Troubleshooting guide, and Configuration manual.
• Deployment and Trial Phase (Nasadenie a skúšobná fáza): Lasting up to T0 + 29 months, this phase includes deploying the solution to production, preparing the production environment (technical and administrative), installing the solution, making it available to selected users, and providing prior training. It concludes with the acceptance of the launch into production.
• Operational Support and Maintenance (Prevádzka a údržba): This includes flat-rate services, on-demand services, Helpdesk/user support levels, incident resolution based on SLA parameters, and ensuring the required Information System availability.
• Final Handover Package: Upon project completion, a complete package for the operation and maintenance of the Information System must be delivered. This includes the full current source code, build/deploy scripts, infrastructure definitions (IaC), a list of used library versions and license information, configuration templates (without sensitive data), technical and user documentation (including operational and security procedures), an export of monitoring and operational data, and a list and secure handover of keys/secrets. The provider must ensure valid license rights for any pre-existing software components and continuously update a Software Bill of Materials (SBOM) listing components and dependencies.

(*T0 = start of work performance)