Snowflake Energy Dublin, Ohio

IGS Energy

Predictive Maintenance

IGS Energy's legacy on-premises platform and manual solar monitoring process could not reliably handle terabyte-scale forecasting data or accurately detect rooftop-solar underperformance, creating cost, complexity, and customer-experience risk.

40 to 50 billion rows
75% cost savings by moving the training of customer-level forecasting models in Databricks to a unified model in Snowflake
exceed a terabyte
minutes to generate forecasts for hundreds of thousands of customers

Reported impact

Business outcome

IGS cut forecasting-model training costs by 75%, reduced forecast generation from about half an hour to minutes for hundreds of thousands of customers, and improved solar anomaly detection so customer issues can be identified with less manual effort and fewer false results.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement

Solution

IGS Energy rebuilt its demand-forecasting and solar-performance analytics on Snowflake so data science could work directly on the large energy datasets that drive commodity purchasing and customer service. Weather signals, historical energy consumption, account attributes, and contract dates flow into Snowflake, where the company stores and queries 40 to 50 billion rows of data that can exceed a terabyte. Instead of training hundreds of thousands of customer-level models in Databricks, the team now trains a single unified forecasting model in Snowflake, cutting training overhead while preserving accuracy. For solar operations, IGS used Streamlit and Snowpark to prototype an anomaly-detection application that combines weather data with solar-array specifications to flag underperforming rooftop systems. Marketplace datasets can be joined in place, keeping forecasting, feature engineering, application development, and stakeholder review inside one governed Snowflake environment.

Data flow

Weather data, historical usage, account details, and contract dates land in Snowflake, where IGS stores terabyte-scale energy data and trains a unified demand-forecasting model instead of per-customer models. For rooftop solar, Streamlit and Snowpark use weather inputs and array specifications to score performance anomalies, and the resulting forecasts or alerts are consumed by commodity-purchasing teams and customer-service operations.

Solution architecture

4 components · 4 layers
  1. Ingest
    • Snowflake Marketplace Provides third-party datasets that can be joined with IGS data without additional ETL or schema maintenance.
  2. Compute
    • Snowpark Lets the data science team develop predictive models and data products directly inside the Snowflake environment.
  3. Storage
    • Snowflake Stores and queries the large forecasting and solar-performance datasets that underpin IGS Energy's analytics workflows.
  4. Serving
    • Streamlit Powers the internal anomaly-detection application used to test and demonstrate solar-performance insights with stakeholders.

Architecture clues

  • IGS replaced hundreds of thousands of customer-level models with a single unified forecasting model in Snowflake.
  • Marketplace datasets are joined directly inside Snowflake to avoid extra extract, load and transform work.
  • The anomaly-detection application combines weather data with rooftop-solar array specifications.

Evidence from the source

Moving from hundreds of thousands of individual forecasting models in Databricks to one unified model in Snowflake helped IGS achieve 75% cost savings in training — without sacrificing accuracy.
Previously, the process to train all these models and generate predictions took a half hour.
Thanks to Streamlit’s ease of use, Shah’s team created an initial anomaly detection application for internal stakeholders in just two weeks for testing.
The data produced in this process could add up to 40 to 50 billion rows and exceed a terabyte.
The unified model on Snowflake is super quick; we’re talking minutes to generate forecasts for hundreds of thousands of customers.
Transparency Evidence & methodology 90/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 value90/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/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
    5 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. Snowflake

    IGS Energy customer story

    First-party
    https://www.snowflake.com/en/customers/all-customers/case-study/igs-energy/
    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 Jun 24, 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 9, 2026 · Snowflake · 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.