Oracle Public Sector Finland

City of Lohja

Enterprise Knowledge Search

As its internal document archive grew, the City of Lohja needed a better way for HR support and ICT helpdesk teams to retrieve current guidance than manual keyword search, which made it hard for employees to find accurate information quickly.

Chatbot can answer approximately 85% of support questions

Reported impact

Business outcome

The City of Lohja improved internal communication and information retrieval, built a chatbot that answers roughly 85% of support questions, and reduced the support workload by giving supervisors and employees faster access to up-to-date guidance.

  • Productivity Improvement

Solution

The City of Lohja built an internal support chatbot on Oracle Autonomous AI Lakehouse and Oracle APEX to turn a growing municipal document archive into a searchable knowledge base. OCI Enterprise AI connects large language models to the source documents, extracts entities such as projects, decisions, and people, and stores those relationships in Oracle Autonomous AI Database with Oracle Graph. Oracle AI Vector Search complements the graph model with semantic retrieval so the chatbot can find relevant guidance even when users do not match the source wording. Oracle APEX provides the low-code application layer that exposes the combined graph-and-vector retrieval experience to city employees. This architecture gives support teams a governed RAG-style system that uses context and relationships, not only keywords, to answer internal HR and IT questions and reduce support workload.

Data flow

Internal HR and IT documents are analyzed by OCI Enterprise AI, which extracts entities and relationships into Oracle Autonomous AI Database and Oracle Graph; Oracle AI Vector Search indexes the same content semantically; Oracle APEX exposes a chatbot that combines graph and vector retrieval to answer employee questions from the centralized knowledge base.

Solution architecture

6 components · 3 layers
  1. Compute
    • OCI Enterprise AI Connects large language models to source documents and extracts entities and relationships from municipal content.
  2. Storage
    • Oracle Autonomous AI Lakehouse Hosts the centralized knowledge base built from the city's internal document archive.
    • Oracle Autonomous AI Database Stores the structured document graph and retrieval data used by the chatbot.
  3. Serving
    • Oracle APEX Provides the low-code application layer for the employee-facing chatbot.
    • Oracle Graph Preserves contextual relationships between projects, decisions, people, and other entities from city documents.
    • Oracle AI Vector Search Performs semantic similarity search so answers can be found by meaning rather than exact keywords.

Architecture clues

  • Entities such as projects, decisions, and people are extracted from source documents
  • Graph and vector retrieval are combined to go beyond basic RAG
  • Low-code APEX frontend sits directly on the Oracle AI and database stack

Evidence from the source

By combining graph and vector queries, the chatbot surfaces related insights that basic RAG can miss.
Oracle APEX ... can answer approximately 85% of support questions.
The solution also uses Oracle AI Vector Search to run semantic similarity searches that can find information by meaning even when keywords don’t match.
Transparency Evidence & methodology 90/100 reference value · 74% 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 value90/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence74%
  • 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 provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/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. Oracle

    City of Lohja customer story

    First-party
    https://www.oracle.com/customers/city-of-lohja/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.