Databricks Logistics North America

Pilot Company

Document Processing · IT Operations Automation

Pilot Company needed a better way to support fuel bill-of-lading document processing and billing automation because hundreds of handwritten form formats defeated OCR and RPA approaches, leaving a critical fuel billing workflow slow, error-prone, and expensive.

90% decrease in overall processing costs
99% fueling efficiency from pump to profit
99% reduction in manual processing leads to faster revenue recognition
Intelligent document processing at 98.6% accuracy with Databricks Agent Bricks

Reported impact

Business outcome

Pilot Company improved fuel bill-of-lading document processing and billing automation with measurable results including 99% fueling efficiency from pump to profit, 90% decrease in overall processing costs, and Intelligent document processing at 98.6% accuracy with Databricks Agent Bricks, while giving teams a faster path from governed data to production decisions.

  • Cost Reduction
  • Productivity Improvement
  • Speed to Market

Solution

Pilot Company uses Databricks Data + AI Platform to support fuel bill-of-lading document processing and billing automation. The implementation replaced a legacy state where hundreds of handwritten form formats defeated OCR and RPA approaches, leaving a critical fuel billing workflow slow, error-prone, and expensive. Handwritten bills of lading and fuel delivery photos move through production data pipelines and land in Delta Lake, giving teams one trusted data foundation. Unity Catalog governs access, lineage, and compliance across sensitive datasets. MLflow, Agent Bricks, and Amazon Bedrock operationalize models, agents, and analytics that deliver structured billing records and automated billing decisions. Pilot Company improved fuel bill-of-lading document processing and billing automation with measurable results including 99% fueling efficiency from pump to profit, 90% decrease in overall processing costs, and Intelligent document processing at 98.

Data flow

Handwritten bills of lading and fuel delivery photos land on a shared platform, pipeline services clean and standardize them, governance controls enforce trusted access, and AI, model-serving, and analytics services deliver structured billing records and automated billing decisions.

Solution architecture

6 components · 4 layers
  1. Compute
    • Databricks Data + AI Platform Databricks Data + AI Platform unifies engineering, analytics, governance, and AI workloads for fuel bill-of-lading document processing and billing automation.
    • MLflow MLflow tracks experiments, versions, and release workflows for models that support fuel bill-of-lading document processing and billing automation.
  2. Storage
    • Delta Lake Delta Lake stores curated handwritten bills of lading and fuel delivery photos so every team works from one trusted data foundation.
  3. Serving
    • Agent Bricks Agent Bricks packages domain-specific agents that automate parts of fuel bill-of-lading document processing and billing automation.
    • Amazon Bedrock Amazon Bedrock runs foundation models for summarization, reasoning, and conversational steps inside fuel bill-of-lading document processing and billing automation.
  4. Governance
    • Unity Catalog Unity Catalog applies centralized access controls, lineage, and auditability across sensitive datasets.

Architecture clues

  • 90% decrease in overall processing costs
  • 99% fueling efficiency from pump to profit
  • 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

One of our biggest roadblocks was evaluating models,
We moved to a multi-modal model and had controlled access through Databricks. Feeding the model the actual photos of the BOL rather than extracted text boosted our accuracy all the way up to 94.3%,
We think it’s because of the model’s ability to preserve spatial reasoning — the layout of the checkboxes and form sections. These things previously were lost.
We’ve tried traditional robotic process automation (RPA), but the forms varied so much it wasn’t feasible,
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

    Pilot Company customer story

    First-party
    https://www.databricks.com/customers/pilot-company
    Source type
    Vendor-published customer story
    Published
    Nov 24, 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 24, 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.