Databricks Energy Global

Puma Energy

Real-time Analytics · Supply Chain Optimization

Puma Energy needed a better way to support global fuel stockout prediction, safety reporting, and customer analytics because fragmented regional systems and slow refresh cycles meant frontline teams waited hours for insights and could not prevent fuel disruptions fast enough.

15% reduction in fuel stockouts by using predictive alerts
20%+
98-99% modernizing fuel access in underserved communities
Decrease in data latency, going from 4–5 hours to under 5 minutes

Reported impact

Business outcome

Puma Energy improved global fuel stockout prediction, safety reporting, and customer analytics with measurable results including 98-99% modernizing fuel access in underserved communities, Decrease in data latency, going from 4–5 hours to under 5 minutes, and 20%+, while giving teams a faster path from governed data to production decisions.

  • Cost Reduction
  • Customer Experience
  • Scalability

Solution

Puma Energy uses Databricks Data + AI Platform to support global fuel stockout prediction, safety reporting, and customer analytics. The implementation replaced a legacy state where fragmented regional systems and slow refresh cycles meant frontline teams waited hours for insights and could not prevent fuel disruptions fast enough. Global fuel operations data and inventory levels move through Lakeflow Jobs and land in Delta Lake, giving teams one trusted data foundation. Unity Catalog governs access, lineage, and compliance across sensitive datasets. Databricks SQL, MLflow, and Model Serving operationalize models, agents, and analytics that deliver predictive stockout alerts and safety audit reports.

Data flow

Global fuel operations data and inventory levels land on a shared platform, pipeline services clean and standardize them, governance controls enforce trusted access, and AI, model-serving, and analytics services deliver predictive stockout alerts and safety audit reports.

Solution architecture

8 components · 5 layers
  1. Compute
    • Databricks Data + AI Platform Databricks Data + AI Platform unifies engineering, analytics, governance, and AI workloads for global fuel stockout prediction, safety reporting, and customer analytics.
    • MLflow MLflow tracks experiments, versions, and release workflows for models that support global fuel stockout prediction, safety reporting, and customer analytics.
  2. Storage
    • Delta Lake Delta Lake stores curated global fuel operations data and inventory levels so every team works from one trusted data foundation.
  3. Serving
    • Databricks SQL Databricks SQL serves curated dashboards and ad hoc analysis to predictive stockout alerts and safety audit reports.
    • Model Serving Model Serving exposes real-time predictions and AI outputs to predictive stockout alerts and safety audit reports.
    • Agent Bricks Agent Bricks packages domain-specific agents that automate parts of global fuel stockout prediction, safety reporting, and customer analytics.
  4. Orchestration
    • Lakeflow Jobs Lakeflow Jobs schedules ingestion and transformation of global fuel operations data and inventory levels into reusable datasets.
  5. Governance
    • Unity Catalog Unity Catalog applies centralized access controls, lineage, and auditability across sensitive datasets.

Architecture clues

  • 98-99% modernizing fuel access in underserved communities
  • Automated ingestion and transformation pipelines keep source data synchronized for downstream analytics and AI.
  • Centralized governance, lineage, and access controls are enforced through Unity Catalog.
  • Delta Lake provides the shared storage layer for curated lakehouse datasets.
  • Operational AI workflows are deployed directly beside governed data and analytics assets.

Evidence from the source

Our teams wanted speed and control, but the setup made us choose one or the other,
Puma Energy is a downstream energy company that supplies fuel, lubricants and aviation products across Latin America, Africa and Asia-Pacific. With a purpose to “energize communities,” the business sought to predict fuel
The infrastructure wasn’t built to scale how the business needed — everything required too much DevOps effort.
The vision is for Databricks to become the central highway that connects tools within the business, not just for data ingestion, but also for orchestrating decisions and outcomes across the enterprise.
Transparency Evidence & methodology 100/100 reference value · 89% 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 value100/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
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • 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 provenance10/10
    The publication date comes from the source page or publisher.
  • 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. Databricks

    Puma Energy customer story

    First-party
    https://www.databricks.com/customers/puma-energy
    Source type
    Vendor-published customer story
    Published
    Nov 21, 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 Nov 21, 2025 · Databricks · 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.