Υπ' αριθ. 10/2026 Διακηρυξη γ.Δ.Ο.Υ.Ε.Σ./Υ.Π.Τ.Π.

The contract timeline indicates a total duration for the delivery and receipt of the contract object of ten (10) months. Additionally, the total project schedule is foreseen for 10 months, with overlapping phases for greater efficiency. However, another statement specifies that the total duration of the project implementation is 9 months, also with overlapping phases for maximum efficiency.

The project is divided into the following phases:

• Phase A: Requirements Analysis (Ανάλυση Απαιτήσεων): This phase is stated to last 2 months. It includes two parallel sub-phases: NSLR Subsystem Requirements Analysis (Φ-Α1) and Form Handler Subsystem Requirements Analysis (Φ-Α2), both lasting 2 months.
• Phase B: System Installation and Parameterization (Εγκατάσταση και Παραμετροποίηση): This phase is stated as 4 months, but also as 5 months with partial overlap from Phase C. It comprises two parallel sub-phases: NSLR Subsystem Installation and Parameterization (Φ-Β1) and Form-Handler Subsystem Installation and Parameterization (Φ-Β2), both lasting 4 months.
• Phase C: System Testing and Parameterization (Δοκιμές Παραμετροποιήσεις): This phase is stated as 1 month, but also as 2 months with partial overlap with Phase B. It includes two parallel sub-phases: NSLR Subsystem Testing and Parameterization (Φ-Γ1) and Form Handler Subsystem Testing and Parameterization (Φ-Γ2), both lasting 1 month.
• Phase D: Pilot Operation (Πιλοτική Λειτουργία): This phase is 1 month.
• Phase E: Training (Εκπαίδευση): This phase is 1 month.
• Phase ST: Final Acceptance (Οριστική Παραλαβή): This phase is 1 month.

The contracting authority also reserves the right to optionally award maintenance services for three (3) additional years after the free warranty period ends.

Contract start date and end date are not explicitly stated.

The core scope of work for this tender involves the procurement, installation, and implementation of an "Integrated National System for Resolving Yellow Links and Managing Forms" (NSLR - Form Handler). This includes both software and equipment, along with associated warranty and maintenance services. The project is structured across distinct phases, emphasizing a "design – development – testing – production – support" lifecycle over a total duration of 10 months with overlapping phases.

The Statement of Work summary and core deliverables are categorized by project phase:

Phase A: Requirements Analysis (2 months)

• Deliverables:
• 2 X Finalized Requirements Analysis Documents for both NSLR and Form-Handler subsystems, including documented prioritization of user requirements.
• Updated Solution Architecture Design (Technical Architecture & Conceptual Design) for the NSLR subsystem, detailing the proposed architectural approach.
• 2 X Acceptance/Receipt Test Plans and Key Performance Indicators (KPIs) for both subsystems, outlining test scenarios, methodology, execution, success criteria, and expected results.
• 2 X Training Plans for both subsystems, defining objectives, schedules, content, location, tools, participants, and duration.
• Current State Study (AS-IS) for the NSLR subsystem, aiming to update and reformulate the existing Hellenic Police infrastructure.
• Application Study, Detailed System Specification (covering all requirements, use cases, ER and flow diagrams), and an updated Project Plan.
• Collection and confirmation of functional and non-functional requirements, mapping of business processes (BPMN diagrams), and conceptual system design.
• Finalization and prioritization of business processes, functional, and technical requirements.
• Design of Solution Architecture using diagrams.
• Finalization of backup policy and procedures.
• Preparation of system operation test scenarios and a test/control procedure guide.
• Updated conceptual system design, including entity-relationship diagrams, sequence diagrams, flowcharts, system architecture, user roles, system security, and system interconnectivity.
• Detailed study of Eulisa's Interoperability ICDs and meetings for initial definition of system interfaces.
• Identification and management plan for potential project risks.

Phase B: System Installation and Parameterization (5 months, with partial overlap from Phase C)

• Core Activities: Supply and installation of necessary equipment (servers, storage), installation of test-development, UAT, and production environments for both NSLR and Form-Handler subsystems, configuration of basic software platforms (databases, application server, IAM for SSO/RBAC), and initiation of software component implementation (source code development and open-source libraries) and interconnections.
• Deliverables:
• Installed System in operational readiness, including both NSLR and Form Handler subsystems, parameterized, tested, and with all necessary interconnections.
• System Equipment (Servers, Data Storage Subsystem, Firewalls, etc.) for Phase B1.
• Licenses for system software, databases, and application servers.
• Set of Documentation Manuals (operational & support) for the system, equipment, and software.
• Unit Tests for the developed code.
• Documentation of infrastructure compliance with CIS Benchmarks and best practices, including explanations for non-applicable or non-implemented settings.
• Completed files of the latest OWASP ASVS level 3 standard, detailing how requirements were met or explaining technical reasons for non-applicability/non-implementation.

Phase D: Pilot Operation (1 month)

• Purpose: An intermediate phase between User Acceptance Testing (UAT) and full production, where the system operates under real business load and undergoes operational testing.

General Deliverables (applicable across relevant phases):

• Weekly updates to the Project Implementation Committee (EPPE) and submission of an informative bulletin on completed and pending procedures.
• Readiness Certificate for Production Connection (joint statement that the system is ready for production integration, with eu-LISA confirmation if required).
• Error Resolution Table (list of all bugs with final status).
• Re-Test Report (results of re-tests).
• New Version Release Notes (description of changes, fixes, new features, known issues).
• Updated Documentation (user guides, technical manuals, configuration documents after final changes).
• Correction Acceptance Protocol (confirmation of implemented and tested fixes).