Accenture Energy United States

Duke Energy

Real-time Analytics

Duke Energy needed to go beyond current US EPA regulations and replace slow physical inspection-based leak surveys with a rigorous end-to-end way to detect, monitor, and remediate methane emissions across its natural gas distribution assets.

find leaks in minutes instead of days
net-zero methane goals for 2030

Reported impact

Business outcome

The platform is already giving Duke Energy more accurate, holistic decision support and near real-time leak detection, helping crews find leaks in minutes instead of days, repair them faster, and improve resilience in gas operations while supporting methane-reduction goals.

  • Productivity Improvement
  • Risk Reduction

Solution

Accenture, Avanade, and Microsoft helped Duke Energy build a first-of-its-kind, end-to-end Azure-based cloud platform for its natural gas distribution business. The implementation ingests satellite monitoring data and operating signals tied to pipelines, gas meters, and other assets, then uses analytics and artificial intelligence to quantify baseline methane emissions, prioritize likely leaks, and attach precise geolocation context for field response. The platform packages the resulting insights into graphic dashboards so leadership and operations teams can review findings at different levels of detail and coordinate remediation. Instead of relying only on physical inspections, Duke Energy now has a near real-time monitoring workflow that detects issues faster, improves repair prioritization, and provides a shared cloud foundation for wider asset and jurisdiction coverage as the program scales.

Data flow

Satellite monitoring data and emissions signals from natural gas distribution assets flow into the Azure-based cloud platform, where analytics and AI quantify baseline emissions, prioritize findings, and attach geolocation context. The resulting insights are delivered through graphic dashboards to leadership and operations teams so they can locate leaks quickly and coordinate remediation across pipelines, meters, and other assets.

Solution architecture

5 components · 4 layers
  1. Ingest
    • satellite monitoring Provides the remote sensing input used to detect and monitor baseline methane emissions across Duke Energy's gas assets.
  2. Compute
    • analytics Quantifies baseline methane emissions and prioritizes findings so teams can focus on the most important leaks first.
    • artificial intelligence Helps identify leaks and system vulnerabilities from monitoring data so repairs can happen faster and more proactively.
  3. Serving
    • graphic dashboards Present prioritized findings and holistic operational insights to leadership and field teams.
  4. Orchestration
    • Azure-based cloud platform Hosts the end-to-end methane monitoring workflow and brings emissions data, asset context, analytics, and response workflows together.

Architecture clues

  • Baseline methane emissions are monitored across natural gas distribution assets including pipelines and gas meters.
  • Findings are quantified and prioritized in graphic dashboards for multiple levels of the organization.
  • Satellite monitoring feeds the detection workflow and provides pinpoint geolocation context for field response.
  • The implementation is described as a first-of-its-kind, end-to-end Azure-based cloud platform.

Evidence from the source

"The platform is already delivering results with more accurate, holistic insights for leadership decision-making."
"The result is a first-of-its-kind, end-to-end Azure-based cloud platform that monitors baseline methane emissions from natural gas distribution assets (e.g., pipelines, gas meters), using satellite monitoring, analytics and artificial intelligence."
"The solution quantifies and prioritizes findings in graphic dashboards, making data easily consumable at multiple levels of the organization."
"With pinpoint-accurate geolocation data, workers are finding leaks in minutes compared to physical inspection of pipelines and other assets -- and repairing them more quickly."
Transparency Evidence & methodology 70/100 reference value · 93% 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 value70/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 scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence93%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 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 transparency10/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. Accenture

    Duke Energy's AI Methane Detection Platform | Accenture

    First-party
    https://www.accenture.com/en/case-studies/utilities/duke-energy-powers-ai-platform
    Source type
    Vendor-published customer story
    Published
    Aug 13, 2026
    Supports
    • Customer
    • Industry
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • Business outcome
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Aug 13, 2026 · Accenture · First-party
    Open date source