AWS Automotive United Kingdom

Motability Operations

Predictive Maintenance

Motability Operations wanted to use connected vehicle data to predict breakdowns before they happened so it could reduce disruption for disabled customers, improve service quality, and prove out a scalable predictive-maintenance architecture.

49 percent of breakdowns were predicted
6 months collecting and training data
6,500 vehicles
Less than 0.5 percent of people chose to opt out

Reported impact

Business outcome

In a 6,500-vehicle pilot, Motability Operations predicted 49 percent of breakdowns, corrected seven major faults, saw less than 0.5 percent customer opt-out, and improved customer experience by intervening proactively before failures occurred.

  • Customer Experience
  • Productivity Improvement
  • Risk Reduction

Solution

Motability Operations ran a predictive-maintenance pilot on AWS to use connected vehicle data more proactively across the Motability Scheme fleet. Working with AWS Professional Services, the team spent six months collecting and training data for foundational ML models, then used Amazon SageMaker to build models that predict whether a vehicle is likely to break down in the near future. The AWS-based approach relied on serverless and managed services so the team could focus on business value instead of infrastructure and security complexity. In practice, vehicle telemetry and maintenance context flow into the ML pipeline, predictions identify likely failures ahead of time, and operations teams intervene before breakdowns happen. This created an early proof point for AI-driven fleet support that can improve customer experience at national scale.

Data flow

Connected vehicle data is collected into Motability Operations' predictive-maintenance workflow, used to train Amazon SageMaker models, and converted into predictions that help teams intervene before vehicles break down.

Solution architecture

1 components · 1 layer
  1. Compute
    • Amazon SageMaker Builds, trains, and deploys the ML models that predict likely vehicle breakdowns.

Architecture clues

  • Created foundational ML models before wider rollout.
  • Focuses on proactive intervention rather than reactive breakdown handling.
  • Pilot intentionally used serverless and managed services for flexibility, scalability, and cost-efficiency.

Evidence from the source

Less than 0.5 percent of people chose to opt out.
Motability Operations spent 6 months collecting and training data for its solution’s foundational ML models.
The pilot consisted of 6,500 vehicles. In total, 49 percent of breakdowns were predicted, and seven major vehicle faults were corrected.
To create these models, Motability Operations used Amazon SageMaker.
Transparency Evidence & methodology 75/100 reference value · 85% 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 confidence85%
  • 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 provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/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. AWS

    Motability Operations customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/motability-operations
    Source type
    Vendor-published customer story
    Published
    Jul 22, 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

Date evidence

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