In-house Financial Services Sydney, Australia Company newsroom

Large Australian bank

IT Operations Automation · Risk Management

The bank wanted a proactive way to monitor a complex IT environment, predict critical service outages, and reduce the impact of infrastructure failures on customers and employees.

700 features were selected and productionised
accuracy was around 60%
incidents over the past three years
predict IT outages four weeks into the future

Reported impact

Business outcome

The bank can predict high-priority incidents affecting customer-critical systems up to four weeks in advance, improve IT service management quality, reduce outage risk, increase resilience and reliability, and support quarterly regulatory reporting.

  • Customer Experience
  • Productivity Improvement
  • Risk Reduction

Solution

DXC worked with the bank’s IT team to build an AIOps-based predictive outage solution for a complex banking estate. Historical system-level log data and service-management metrics from hundreds of banking systems, including customer-facing platforms and back-end credit card and processing systems, were ingested and analyzed to identify patterns linked to future incidents. DXC data scientists used a design thinking process, SME interviews, workshops, and feature engineering to select and productionise 700 features inside the bank’s big data cluster. An AIOps model then continuously observes operating signals, generates outage likelihood risk scores, and feeds iterative learnings back into the model for ongoing accuracy improvement. The resulting predictions and next-best-action insights are surfaced in a dashboard so service managers can intervene before failures occur, and the same data also supports quarterly APRA regulatory reporting.

Data flow

Historical log and service-management data from hundreds of customer-facing and back-end banking systems are ingested into the bank’s big data cluster, where 700 engineered features were productionised. The AIOps model analyzes three years of incident data, generates outage risk scores and next-best-action insights, and publishes warnings to a dashboard used by service managers and for APRA regulatory reporting.

Solution architecture

3 components · 3 layers
  1. Compute
    • AIOps model Continuously analyzes service-management and log data to generate future outage risk scores and support automated issue resolution activities.
  2. Storage
    • big data cluster Hosts the productionised feature set and underlying data used to train and run the predictive outage models.
  3. Serving
    • dashboard Presents advance warnings, risk insights, and next best actions for service managers to act on before systems fail.

Architecture clues

  • AI explainability and transparency were required to satisfy governance needs
  • Consumes historical system-level log data from hundreds of banking systems
  • Covers both mission-critical customer-facing systems and back-end processing systems
  • Model outputs are used for quarterly APRA regulatory reporting
  • Solution built for a bank in Sydney, Australia
  • Uses a continual AIOps observe-engage-act cycle for continuous learning

Evidence from the source

"700 features were selected and productionised within the bank’s big data cluster, ensuring the creation of the most accurate algorithms."
"DXC data scientists used a design thinking approach and worked hand in hand with the bank to design, prototype and build AI models to consume historical system-level log data from hundreds of banking systems."
"It has fundamentally changed the bank’s approach to system outages — with the ability to predict issues up to four weeks out."
"The objective of this project was to create and support a robust solution that could predict outages in the bank’s IT environment."
"The resulting model uses data, AI and ML to analyse various service management metrics, identify patterns and produce a risk score determining the likelihood of future outages or incidents."
"the data is also used to support quarterly regulatory reporting to the Australian Prudential Regulation Authority (APRA)."
Transparency Evidence & methodology 85/100 reference value · 94% 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 value85/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 scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence94%
  • Source authority25/25
    The deployment is described by the adopting organization or a government source.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 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. Large Australian bank

    Large Australian bank customer story

    First-party
    https://dxc.com/insights/customer-stories/ai-and-ml-help-predict-and-resolve-it-outages-before-they-occur
    Source type
    Customer-published story
    Published
    Jun 29, 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 Jun 29, 2026 · DXC Technology · 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.