MongoDB Manufacturing Global

Vaillant

Predictive Maintenance · Real-time Analytics

Vaillant needed to handle exploding IoT telemetry from connected HVAC devices because its Azure CosmosDB environment required constant manual scaling, suffered repeated crashes and slow queries, and blocked predictive maintenance and API-driven service innovation.

MongoDB Atlas decreased database size by over 99%.
MongoDB Atlas increased API throughput by 250 percent.
The migration took 90 minutes with no downtime.
Today, the platform stores over 1.9 billion records.

Reported impact

Business outcome

After moving to MongoDB Atlas, Vaillant eliminated downtime, cut database size by more than 99%, increased API throughput by 250%, and created a platform that supports remote troubleshooting, real-time analysis, and more efficient field service for connected HVAC systems.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Vaillant migrated its connected-HVAC platform from Azure CosmosDB to MongoDB Atlas on Microsoft Azure after explosive device growth made manual scaling, slow queries, and nightly outages routine. IoT telemetry from tens of thousands of internet-connected devices now lands in Atlas as a single, auditable operational store, where the aggregation framework and secondary indexes support real-time analytics for monitoring and predictive-maintenance workflows. Atlas's managed scaling removed write-limit headaches, and the migration itself took about 90 minutes after the team redesigned the schema. Vaillant also keeps some analytics at the edge to reduce network traffic, exposes device data through APIs for partners and engineers, and uses Atlas security features such as VNet peering-only mode to protect sensitive operational data. The platform now underpins services such as serviceASSIST and future guided-repair experiences for field technicians.

Data flow

Sensor state changes from connected HVAC devices stream into MongoDB Atlas on Azure, where aggregation and indexing support real-time monitoring and predictive-maintenance analysis, while selected analytics stay at the edge to reduce network traffic and service data is exposed through APIs and technician applications.

Solution architecture

2 components · 2 layers
  1. Storage
    • MongoDB Atlas Stores and scales Vaillant's IoT telemetry, APIs, and analytics workloads for connected HVAC products.
  2. Orchestration
    • Microsoft Azure Hosts the Atlas deployment Vaillant uses for its cloud-based connected-device platform.

Architecture clues

  • Intelligent edge processing is used so not all data must be sent to the cloud.
  • The solution runs MongoDB Atlas on Microsoft Azure.
  • VNet peering-only mode is used to protect sensitive device data.
  • Vaillant plans to extend the platform through serviceASSIST and guided repair workflows for field engineers.

Evidence from the source

"MongoDB Atlas’ VNet peering-only mode ensures that data is kept secure and access is limited."
"Today, we have over 1.9 billion records and there has been no downtime at all, and our customers immediately noticed the performance improvements."
"We had 70,000 devices generating 600,000 transactions per second."
"With MongoDB Atlas, powerful secondary indexing, and the aggregation framework, the team has decreased its database size by over 99% all the while increasing the throughput of its API by 250 percent."
Transparency Evidence & methodology 95/100 reference value · 79% 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 value95/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 impact25/25
    5 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • 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 evidence20/20
    4 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. MongoDB

    Vaillant customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/vaillant
    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

Date evidence

  • First archived Apr 13, 2024 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jul 18, 2025 · MongoDB · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.