IBM Software / SaaS global

IBM CIO Organization

Enterprise Knowledge Search · IT Operations Automation

IBM’s CIO Organization needed to help new and early-tenure professionals manage IBM Z environments more independently because the mainframe skill curve was steep and subject matter experts were spending too much time answering routine questions, handling incidents, and guiding patching work.

10% faster incident resolution
3 of 35 use cases prioritized for initial adoption
300+ users are using watsonx Assistant for Z
50% decrease in time to patch Db2 systems

Reported impact

Business outcome

The CIO Organization shortened onboarding, sped incident resolution and Db2 patching, and gave hundreds of users a more confident way to operate IBM Z without as much reliance on scarce experts.

  • Productivity Improvement
  • Speed to Market

Solution

IBM CIO deployed watsonx Assistant for Z as an on-premises generative AI and automation layer for mainframe operations. Running on an existing Red Hat OpenShift cluster, the assistant uses curated IBM Z knowledge and retrieval-augmented generation to answer product and operational questions, helping newer staff get digestible guidance without waiting for senior experts. The team also prioritized incident analysis and Db2 patching as early use cases: watsonx Assistant for Z can ingest incidents from a third-party workflow automation platform, suggest actions based on documentation and similar past events, and interact with Ansible-based automation plus change-management workflows to open, route, and close patching requests. This turns the assistant from a Q&A bot into an orchestration surface for routine mainframe operations. Because the CIO organization iterated with the product team during rollout, the deployment also improved the product itself while giving IBM a reusable pattern for bridging mainframe skills gaps with grounded AI plus operational automation.

Data flow

User questions and incidents enter watsonx Assistant for Z, RAG grounds responses in curated IBM Z content, incidents are enriched with historical and workflow-platform context, and the assistant can trigger Ansible-backed automations and change requests before reporting status back to the operations user.

Solution architecture

3 components · 2 layers
  1. Serving
    • Red Hat OpenShift Hosts the assistant on-premises inside the CIO’s existing infrastructure.
  2. Orchestration
    • IBM watsonx Assistant for Z Delivers curated answers and automation orchestration for IBM Z operations, incident handling, and patching.
    • Ansible Executes the automation retrieved by the assistant for patching and other mainframe operations tasks.

Architecture clues

  • Automation is triggered through third-party workflow tooling and Ansible integrations.
  • RAG is used specifically to reduce hallucination risk by responding only from ingested content.
  • The assistant was deployed on-premises on an existing OpenShift cluster.

Evidence from the source

“10% faster resolution of incidents”
“300+ users are using watsonx Assistant for Z”
“50% decrease in time to patch Db2 systems”
“The model used by IBM watsonx Assistant for Z addresses a common cause of potential hallucinations by leveraging Retrieval Augmented Generation (RAG) architecture”
“deployed watsonx Assistant for Z on-premises on an existing Red Hat OpenShift cluster.”
Transparency Evidence & methodology 96/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 value96/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 impact25/25
    3 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. IBM

    IBM CIO Organization customer story

    First-party
    https://www.ibm.com/case-studies/watsonx-assistant-for-z
    Source type
    Vendor-published customer story
    Published
    Nov 4, 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.