NVIDIA Energy Global

EPRI

Enterprise Knowledge Search · Real-time Analytics

EPRI needed to run advanced AI for sensitive utility documents and weather-planning workflows locally, because energy-sector research data could not leave controlled environments and shared compute delays limited how quickly researchers and planners could test new scenarios.

150 tokens/sec aggregate across 10 concurrent Power Chat users
240x faster than CPU-only for the DGX Station ensemble workflow
35 tokens/sec for a single Power Chat user after warm-up
39 seconds for one ensemble member on DGX Station versus 964 seconds on CPU-only

Reported impact

Business outcome

EPRI can now run a 120B-class local document assistant at 35 tokens per second for one user or 150 aggregate tokens per second for ten concurrent users, while DGX Station compresses a 50-member weather ensemble from an estimated 10+ CPU hours to 150 seconds, giving grid planners more time to act without sacrificing air-gapped deployment requirements.

  • Compliance
  • Productivity Improvement
  • Risk Reduction

Solution

EPRI built two local AI workflows on NVIDIA deskside systems so energy researchers could keep performance, sovereignty, and compliance without relying on external networks. Power Chat runs on DGX Spark and Dell Pro Max with GB10 to host a 120B-class open-weight model, a one-million-token document cache, and inference on a single local system. It serves technical documents, logs, and reports through a natural-language interface using a NVIDIA vLLM NGC container with prefix caching, all inside air-gapped or connectivity-limited environments. For planning and grid operations, EPRI uses DGX Station with AI weather models such as GenCast, FourCastNet, CorrDiff, and CBottle to downscale weather data, generate high-resolution ensemble forecasts, and give grid planners more time to evaluate scenarios. Across both workflows, coherent unified memory, local DGX software, and on-prem deployment let EPRI prototype, fine-tune, and operate energy AI without exposing regulated data or waiting on shared infrastructure queues.

Data flow

Technical documents and logs are loaded into Power Chat’s local cache on DGX Spark for natural-language retrieval, while weather and climate grids feed DGX Station models such as GenCast, FourCastNet, CorrDiff, and CBottle to produce ensemble forecasts and downscaled outputs for grid operators and planners.

Solution architecture

10 components · 3 layers
  1. Compute
    • DGX Spark Hosts the local LLM-based document-analysis workflow on deskside hardware.
    • Dell Pro Max with GB10 Provides the hardware form factor EPRI uses for local Spark deployments.
    • NVIDIA DGX Station Runs the heavier AI weather-prediction and downscaling workflows for grid planning.
  2. Serving
    • Power Chat Acts as EPRI’s local document research assistant for utility and R&D teams.
    • NVIDIA vLLM NGC Container Serves the open-weight LLM for Power Chat with prefix caching.
    • NVIDIA Earth-2 Supplies the broader weather-model platform that supports EPRI’s downscaling and planning workflows.
    • NVIDIA FourCastNet Provides an AI weather model used in EPRI’s transmission-planning workflows.
    • NVIDIA CorrDiff Downscales coarse weather grids into higher-resolution local forecasts.
    • NVIDIA CBottle Generates high-resolution atmospheric states for forecast comparison and refinement.
  3. Orchestration
    • NVIDIA DGX OS Provides the integrated software stack that simplifies local AI prototyping on DGX Spark.

Architecture clues

  • DGX Spark uses 128 GB of coherent unified memory to fit a 120B-class model and large KV cache on a deskside system.
  • DGX Station uses Grace Blackwell unified memory so EPRI can run large ensemble forecasts locally without dedicated data-center infrastructure.
  • Power Chat keeps model weights, the document cache, and inference entirely on the local system and can operate air-gapped.

Evidence from the source

Both workflows run entirely on premises and are air-gap capable, with no external network dependency.
NVIDIA DGX Station GB300 generates a full 50-member GenCast ensemble weather forecasts in 150 seconds, compared to an estimated 10+ hours on a CPU server.
Power Chat runs a 120-billion-parameter open-weight LLM entirely on one deskside system, streaming 35 tokens/second to a single researcher and 150 tokens/second aggregate across 10 concurrent users.
The result is a private, cost-effective AI assistant that keeps a one-million-token KV cache for document recall across sessions.
Users select technical relevant documents that are loaded into the model's memory via cache-augmented generation.
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
    5 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. NVIDIA

    EPRI customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/epri/
    Source type
    Vendor-published customer story
    Published
    Sep 30, 2026
    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 Sep 30, 2026 · NVIDIA · 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.