Capgemini Public Sector Germany

German Federal Employment Agency

Document Processing · IT Operations Automation

The BA needed a privacy-compliant way to reduce the manual effort of turning Requests for Change and user stories into high-quality Jira tickets under increasing workload and limited staff capacity.

Reported impact

Business outcome

The BA automated most ticket creation work, reduced manual effort on summarizing and formatting, and established a reusable on-premises AI agent pattern that fits public-sector privacy and security requirements.

  • Compliance
  • Productivity Improvement
  • Scalability

Solution

The German Federal Employment Agency worked with Capgemini to automate RFC and user-story conversion into Jira tickets using a coordinated on-premises multi-agent architecture. Incoming change requests are first analyzed by a reader agent, then broken into steps by a planner agent, transformed into structured Jira content by a creator agent, and checked for consistency and duplicates by a reviewer agent before human approval. The deployment was built to manage large RFC documents and LLM token limits while fitting the agency’s privacy and security requirements. After pilot integration with selected departments, the system was fully connected to the agency’s local Jira environment and orchestrated with CrewAI using privacy-compliant models including Aleph Alpha, LLaMA, and Mistral. This lets the BA keep all data on premises while automating repetitive formatting, summarization, and copy-paste work so staff can focus on oversight and decision-making.

Data flow

RFCs and user stories are read and extracted by the reader agent, decomposed by the planner agent, turned into structured Jira tickets by the creator agent, checked by the reviewer agent, and then sent to human reviewers before entering the agency’s local Jira instance.

Solution architecture

9 components · 3 layers
  1. Compute
    • Aleph Alpha Provides privacy-compliant model capability for the on-premises ticketing workflow.
    • LLaMA Provides privacy-compliant model capability for the on-premises ticketing workflow.
    • Mistral Provides privacy-compliant model capability for the on-premises ticketing workflow.
  2. Serving
    • Jira Serves as the agency’s local ticketing environment where the generated work items are created and managed.
  3. Orchestration
    • reader agent Analyzes Requests for Change and user stories to extract the information needed for ticket creation.
    • planner agent Breaks the extracted request into actionable steps for ticket generation.
    • creator agent Generates the Jira ticket title, description, category, and metadata.
    • reviewer agent Checks generated tickets for consistency and duplicates before human approval.
    • CrewAI Coordinates the specialized AI agents inside the agency’s on-premises architecture.

Architecture clues

  • Human-in-the-loop approval remains in place
  • Integrated into the agency’s secure local Jira environment
  • Mechanisms were added to handle large RFC documents and LLM token limits
  • Runs fully on premises

Evidence from the source

"Capgemini and the BA developed a multi-agent AI system that automatically transforms Requests for Change and user stories into Jira tickets, supported by human oversight."
"Privacy-compliant models such as Aleph Alpha, LLaMA, and Mistral are orchestrated via CrewAI, an open-source platform for multi-agent coordination."
"Today, the system is fully integrated into the BA’s local Jira instance and operates entirely on-premises."
Transparency Evidence & methodology 75/100 reference value · 84% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence84%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Capgemini

    The German Federal Employment Agency automates Jira processes with AI agents - Capgemini India

    First-party
    https://www.capgemini.com/in-en/news/client-stories/the-german-federal-employment-agency-automates-jira-processes-with-ai-agents/
    Source type
    Vendor-published customer story
    Published
    Dec 5, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Dec 5, 2025 · Capgemini · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.