Entwicklung, Implementierung, Hosting, Wartung und Support einer modularen Quartiers-App für das "Europa-Viertel am Waldhügel" in Rheine

The contract timeline includes the following:

The core development of the app is structured into three mandatory release stages, which are binding contractual milestones:

• Version 1.0 – Grundsystem (Basic System): Targeted for completion 9 months after the contract award.
• Version 2.0 – Information und Orientierung (Information and Orientation): Targeted for completion 15 months after the contract award.
• Version 3.0 – Servicefunktionen (Service Functions): Targeted for completion 21 months after the contract award.

While no specific contract start or end dates are provided, the project milestones are relative to the "contract award" (Auftragsvergabe).

The total duration of the contract includes the development phase and a period for ongoing operations. There are "Laufende Betriebskosten, bestehend aus: Laufende Kosten für 5 Jahre" (Ongoing operating costs for 5 years) covering hosting, maintenance, and support. Additionally, an "Optionale Verlängerung um 12 Monate nach Ablauf der Vertragslaufzeit" (Optional extension for 12 months after the contract term) is mentioned. This indicates a minimum contract duration encompassing the development period (up to 21 months) plus 5 years of operation, with a possibility of a 12-month extension.

Other project phases and activities include:

• Sprint planning, Jour Fixes, project status reports, risk management, acceptance control, and test management.
• 3 training sessions.
• 3 public presentation events.

The core scope of work for this tender involves the development, implementation, hosting, maintenance, and support of a modular district app for the "Europa-Viertel am Waldhügel" in Rheine.

The project aims to create and operate a modular digital district platform comprising:

• A mobile app (iOS/Android or PWA).
• A backend system.
• An administration interface.
• Interface integration.
• Hosting services.
• Support and maintenance services.

The primary objectives of the district app include:

• Controlling and managing mobility-related processes.
• Digitally supporting a largely car-free district.
• Integrating municipal and external services.
• User administration and legitimation.
• Communication between the district, users, and administration.

The solution must be modular, multi-client capable, extensible, and open to interfaces.

The implementation is structured into three mandatory release stages:

• Version 1.0 – Basic System (Target completion: 9 months after contract award):
• Setup and configuration of the operating environment (web server, backend, web frontend).
• Provision of a test environment.
• Data maintenance capability by the client.
• Core functionalities include rights and roles concept, registration and legitimation, access management (including connection to the parking operating system), parking management, underground waste system, and access control.
• Version 2.0 – Information and Orientation (Target completion: 15 months after contract award):
• EFA interface (public transport).
• Map function.
• Dashboard.
• News/communication function.
• Version 3.0 – Service Functions (Target completion: 21 months after contract award):
• Sharing offers.
• Application for special permits (interface to city administration).
• Help and feedback system.

Functions not explicitly assigned to a version (e.g., payment processes, push service, BundID preparation) must be allocated to specific versions by the bidder, subject to client approval.

Additional core deliverables and requirements include:

• Project Methodology: Agile implementation, including sprint planning, Jour Fixes, project status reports, risk management, acceptance control, and test management.
• Hosting and Operation: Hosting in Germany, DSGVO-compliant, with a minimum availability of 99.5%, including backup and restore concepts and scalability.
• Support: Defined support hours (Monday-Friday, 08:00-16:00) with specified reaction and resolution times for critical incidents.
• Maintenance: Security updates, bug fixes, performance optimization, and monitoring.
• Training Concept: Training for administrators, case workers, technical service providers, and support personnel, covering backend operation, role management, approval processes, monitoring, and support processes, along with providing presentations, manuals, and FAQ documents.
• Public Relations: Organization of three local public relations events for project presentation.
• Data Protection and IT Security: DSGVO-compliant implementation (e.g., contract processing, deletion concepts, data minimization, consent management, rights of data subjects) and IT security measures (e.g., TLS encryption, password rules, MFA/biometric options, logging, intrusion detection, monitoring, backup concept, role model), aligning with BSI basic protection requirements.
• Documentation: Provision of system, API, operational, administrator, user documentation, architecture diagrams, and data model descriptions.