AWS Software / SaaS Germany

Empolis

Enterprise Knowledge Search

Empolis wanted to enhance its knowledge-management SaaS products so users no longer had to manually search through manuals and operating procedures for answers, troubleshooting guidance, and product information.

Reported impact

Business outcome

Empolis created a generative AI assistant that lets users search and query millions of documents conversationally, helping customers such as KUKA troubleshoot machinery faster, learn more about their equipment, and prevent operational issues.

  • Customer Experience
  • Productivity Improvement

Solution

Empolis extended its knowledge-management SaaS portfolio with a generative AI assistant called Empolis Buddy by building on Amazon Bedrock. The assistant is integrated into existing Empolis products and can query millions of documents, including standard operating procedures and manufacturing manuals, to surface precise answers for end users. Empolis developed the offering with AWS and validated it in collaboration with customer KUKA, using Bedrock to access large language models without managing the underlying model infrastructure itself. This architecture lets the assistant sit on top of large enterprise document corpora and deliver advanced search, troubleshooting, and operational guidance in natural language. The result is a reusable generative AI knowledge layer that helps industrial users learn faster, resolve issues sooner, and prevent operational problems.

Data flow

Millions of manuals, standard operating procedures, and product-information documents are queried through Empolis Buddy, which uses Amazon Bedrock to turn document content into natural-language answers for end users.

Solution architecture

1 components · 1 layer
  1. Compute
    • Amazon Bedrock Hosts the large language models used by Empolis Buddy to answer questions across large document collections.

Architecture clues

  • Built as an extension of existing knowledge-management SaaS products.
  • Targets large industrial document corpora rather than a narrow single-manual workflow.
  • Validated in a proof of concept with customer KUKA.

Evidence from the source

Empolis used Amazon Web Services (AWS) to develop a virtual assistant – known as the Empolis Buddy – powered by large language models on Amazon Bedrock.
The generative AI assistant can access and query millions of documents, such as standard operating procedures and manufacturing manuals.
This ability helps users learn more about their machinery, troubleshoot problems faster, and prevent operational issues.
Together with its customer KUKA ... Empolis formulated a proof of concept for a generative AI assistant in April 2023.
Transparency Evidence & methodology 75/100 reference value · 88% confidence · 2 sources

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 confidence88%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency9/10
    2 source references 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. AWS

    Empolis customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/empolis/
    Source type
    Vendor-published customer story
    Published
    Mar 15, 2024
    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
  2. Global Database

    Empolis Information Management GmbH

    Independent secondary
    https://de.globaldatabase.com/company/empolis-information-management-gmbh

    According to the latest account statement, there are currently 189 of employees working for Empolis Information Management GmbH.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.