Rahmenvereinbarung KI-Entwicklungsleistungen

The contract is scheduled to run from December 1, 2026, to November 30, 2030. The implementation plan requires five phases, which can be further detailed. These phases include: Concept, lasting 4 weeks; Proof of Concept (PoC), lasting 6 weeks; Minimum Viable Product (MVP), lasting 8 weeks; Productive phase (Go-Live, training, monitoring), lasting 4 weeks; and an ongoing Operations phase (maintenance, support, further development). Key milestones mentioned within these phases include "Concept completed," "PoC functional," "MVP production-ready," and "Productive implementation." Additionally, general milestones (M1, M2, M3) are referenced with placeholders for specific dates, such as "prototype completed" and "acceptance." The earliest project start is indicated as either a specific date or "after commissioning," and the planned Go-Live is a specific date or "X months after project start." The contractor is also required to submit a project and milestone plan before beginning implementation.

The core scope of work for this tender involves the development, implementation, or provision of solutions to solve specific problems for a defined target group. The nature of the work can vary, including consulting/conception, Proof of Concept (PoC), prototyping, Minimum Viable Product (MVP) development, full implementation projects, integration projects, operation/maintenance packages, further development, support/analysis, and product development.

A key objective is the delivery of a functional prototype, for example, a "KI-gestützter Assistent für Bürgeranfragen im Bereich Baurecht" (AI-supported assistant for citizen inquiries in construction law), aiming to demonstrate technical feasibility and serve as a basis for productive implementation decisions.

Core deliverables include:

• A functional prototype, executable in a test environment.
• Fully documented and versioned source code.
• Technical documentation, covering architecture, data model, and API description.
• Operational documentation, including installation, configuration, and monitoring instructions.
• A test protocol with a specified number of test cases (e.g., 50 test cases).
• For operational handover, deliverables also include deployment scripts, configuration files, environment variables, a monitoring dashboard or logging concept, a runbook for incident management, and contact details for support within the warranty period.

The solutions must meet defined acceptance criteria, encompassing:

• Functional requirements: Concrete and measurable capabilities, such as an AI assistant correctly answering a high percentage of test questions (e.g., 80% of 50 test questions) with a maximum response time (e.g., 5 seconds) and the ability to ask clarifying questions.
• Quality requirements: Specific values for performance, availability (e.g., 95% during the test phase), and error rate (e.g., < 5% for test cases), and response time performance (e.g., < 5 seconds for 90% of requests).
• Security requirements: Definition and agreement of security aspects during concept and design phases, covering authentication, authorization, data protection, encryption, logging, traceability, protection against common vulnerabilities (e.g., OWASP Top 10), and compliance (e.g., DSGVO, NIS2, CRA). These requirements must be documented and are part of the acceptance criteria.
• Security tests: Execution of static code analysis (SAST), dynamic security tests (DAST), dependency checks, and manual security reviews for critical components (e.g., authentication, data access) before milestone handover, with documented results provided to the client.

The project typically follows phases such as analysis and conception, Proof of Concept (PoC), MVP development, productive deployment, rollout, and ongoing operation, maintenance, and further development. Objectives often include time savings through automation, error reduction, and improved traceability and transparency.