3. Session Outline (30 Minutes)
I. Context & The Pre-Study | 5 min
- The Shift: Transitioning from legacy email communication to Zammad within Munich's city administration.
- Proving the Case: Utilizing LLMs to analyze historical ticket data to calculate automation potential and project significant time savings before development began.
II. Architecture: Integration & Pipeline | 6 min
- Event-Driven Design: Connecting to Zammad via the city-internal Kafka message bus.
- Real-time Processing: How new tickets are captured and routed to the AI component seamlessly.
III. The Two-Stage Process | 12 min
- Step 1: Classification & Extraction: Analyzing thematic context through rule-based logic and LLM-powered information extraction.
- Step 2: Response Generation: A RAG (Retrieval-Augmented Generation) approach leveraging a knowledge base maintained by subject matter experts.
- Human-in-the-Loop: Integrating response drafts into the agent UI for review vs. automated "dark processing" for high-confidence categories.
IV. Scaling & Lessons Learned | 4 min
- Multi-Tenant Capability: Designing for configurability and deployment across various city departments.
- Key Benefits: Efficiency gains, response consistency, and establishing a "Single Voice of the City."
V. Q&A | 3 min
- Open discussion on technical tooling, model selection, and legal/privacy frameworks.
Leon Lukas
Here is the translation of the biography, keeping the tone professional and suitable for a conference or website profile:
Leon Lukas has been the team lead of the AI Competence Center for two years and has played a key role in the development and implementation of AI solutions within the city administration. While he initially trained models and built systems himself, he is now responsible for the architecture and projects at it@m, the city’s IT service provider. For more information on AI in the City of Munich, visit: ki.muenchen.de.