IBM Energy Germany

Wintershall Dea

After a merger, Wintershall Dea needed a scalable way to connect data, skills, and AI use cases across the larger organization because existing projects were isolated, difficult to scale, and not supported by a common delivery platform or operating model.

2,000 PDF documents
20 use cases actively pursued
60 employees attended a six-day data science workshop
80+ AI use cases identified

Reported impact

Business outcome

Wintershall Dea established a scalable AI operating model, identified dozens of viable use cases, trained more than 100 employees, automated document extraction work, and launched well-integrity AI into production with a stronger citizen-data-science community behind it.

  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

Wintershall Dea partnered with IBM Consulting to build an AI-at-scale capability that combined platform architecture, operating-model design, and employee enablement. IBM adapted its AI@Scale methodology to the company’s existing Microsoft Azure data platform and used assessments to define a roadmap for a new center of competence, citizen-data-science community, and repeatable MLOps-based architecture. IBM then helped Wintershall Dea provision the technical environment, customize templates, run enablement sessions, and apply IBM Garage methods so business units could qualify and develop both small “firefly” projects and larger enterprise use cases. That framework supported solutions such as PDF extraction workflows that automate manual engineering tasks and well-integrity models that analyze live subsea sensor data for anomaly detection. Instead of treating AI as a sequence of pilots, Wintershall Dea created a structured platform for moving proofs of concept into production and for scaling successful ideas across operations, engineering, geoscience, and business functions.

Data flow

Business and operational data from across Wintershall Dea feeds into the Azure-based AI platform, teams use AI@Scale templates and MLOps workflows to develop and test solutions, and resulting models are pushed into business-unit or production environments such as PDF extraction and live well-sensor monitoring.

Solution architecture

4 components · 2 layers
  1. Serving
    • Microsoft Azure Hosts the component-based technical foundation and MLOps environment used for Wintershall Dea’s AI work.
  2. Orchestration
    • IBM Consulting Co-developed Wintershall Dea’s AI center of competence, roadmap, and deployment approach across technical and organizational dimensions.
    • IBM AI@Scale Provided the methodology, assessments, templates, and scaling patterns used to move AI ideas into production.
    • IBM Garage Guided the qualification and development of business use cases into full AI solutions.

Architecture clues

  • The technical foundation uses a component-based architecture on Microsoft Azure with MLOps practices.
  • The well-integrity use case connects AI to live sensor data and is expanding to more wells and countries.
  • Wintershall Dea’s “firefly” concept lets business units launch small scalable AI projects with CoC support.

Evidence from the source

“Applying AI, the engineering team was able to automate the process” of extracting key values from more than 2,000 PDF documents.
“IBM was able to adapt its IBM AI@Scale methodology to accommodate the existing platform”
“Over 100 Wintershall Dea employees have undergone AI and data science training”
“Today, Wintershall Dea, together with IBM, has identified more than 80 possible AI and data science use cases”
“the team developed a component-based architecture using the Microsoft Azure platform and services.”
Transparency Evidence & methodology 86/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 value86/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 specificity16/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 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. IBM

    Wintershall Dea customer story

    First-party
    https://www.ibm.com/case-studies/wintershall-dea
    Source type
    Vendor-published customer story
    Published
    May 27, 2024
    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

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.