Rahmenvereinbarung KI-Entwicklungsleistungen

The contract timeline is explicitly stated as follows:

• Contract Start Date: 01.12.2026
• Contract End Date: 30.11.2030
• Total Duration: The contract runs for four years, from December 1, 2026, to November 30, 2030.

Key milestones and phases include:

The implementation plan requires the inclusion of five mandatory phases, with the option to add more or subdivide existing ones. Each phase should specify its designation, description, duration, milestones, and dependencies.

Examples of phases provided are:

• Conception: Involves requirements analysis and technical concept development, with a duration of 4 weeks. Key milestones include "Concept finished" and "Client approval".
• Proof of Concept (PoC): Focuses on prototype development (e.g., with 50 test questions), lasting 6 weeks. A milestone is a "functional PoC".
• Minimum Viable Product (MVP): Extends functionality (e.g., to 200 questions) and integrates, taking 8 weeks. A key milestone is an "MVP ready for production".
• Productive Use: Includes Go-Live, training, and monitoring, lasting 4 weeks. The milestone is "Productive deployment".
• Operation: Covers maintenance, support, and further development, and is ongoing. The milestone is "Stable operation".

There are also generic milestones M1 (e.g., concept completed), M2 (e.g., prototype completed), and M3 (e.g., acceptance) with specific dates to be filled in. The earliest project start can be a specific date or "after commissioning," and the planned Go-Live can be a date or "X months after project start".

The core scope of work for this tender involves the development, implementation, or provision of solutions to specific problems for a defined target group. Examples include the provision of a functional prototype of an AI-powered assistant for citizen inquiries, intended to demonstrate technical feasibility and inform decisions on productive implementation. The tender allows for various types of call-offs, such as consulting/conception, Proof of Concept, prototype development, Minimum Viable Product (MVP) creation, implementation projects, integration projects, operations/maintenance packages, further development, support/analysis, and product development.

The Statement of Work summary and core deliverables are structured around several key aspects:

• Functional Requirements: The solution must meet concrete and measurable functional criteria, such as an AI assistant correctly answering a specified percentage of test questions, achieving a maximum response time, and being capable of asking clarifying questions.
• Quality Requirements: Specific performance indicators include availability (e.g., 95% during testing), an error rate below a defined threshold (e.g., <5% for test cases), and performance targets like response time for a high percentage of requests (e.g., <5 seconds for 90% of requests).
• Deliverables: The final handover typically includes a functional prototype runnable in a test environment, fully documented and versioned source code, technical documentation (covering architecture, data model, API description), operational documentation (for installation, configuration, and monitoring), and a detailed test protocol.
• Transition Criteria for Operation: To enable the operation of the solution, deliverables include deployment scripts, configuration files, environment variables, a monitoring dashboard or logging concept, a runbook for incident management, and contact information for support.
• Implementation Plan: The overall implementation is expected to follow a structured plan, potentially involving phases such as analysis and conception, Proof of Concept (PoC), MVP development, productive deployment (Go-Live), and ongoing operation. Each phase specifies a description, duration, milestones (e.g., "Concept completed," "PoC functional," "Prototype completed," "Acceptance"), and dependencies.