ML Clustering for IT Ticket Categorization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Financial institutions face challenges in efficiently processing and categorizing large volumes of inconsistent issue ticket data from technology infrastructure, making it difficult to identify and resolve operational incidents effectively.

Innovation Solution

The implementation of a system that uses machine learning and natural language processing to automatically cluster and categorize IT support tickets and alerts, employing probabilistic models like Latent Dirichlet Allocation (LDA) for real-time data analysis and feedback-driven label tuning, allowing for dynamic re-clusterization and system-level monitoring.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual categorization of issue tickets is performed, then categorization accuracy can be maintained, but processing time and labor costs increase significantly

Engineering Contradiction:
Improvecategorization accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system enables self-service automated categorization where the machine learning model independently processes and categorizes issue tickets without human intervention. The model learns from historical data and automatically assigns categories, eliminating the need for manual categorization while maintaining high accuracy through continuous learning and feedback mechanisms.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual categorization process with an automated machine learning system. The ML model processes tickets using algorithms and patterns learned from data, substituting human cognitive processes with computational processes that can handle large volumes of tickets rapidly and consistently.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If automated categorization using machine learning is implemented, then processing speed and scalability improve, but initial system complexity and data processing requirements increase

Engineering Contradiction:
Improveprocessing speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-processing and cleaning issue ticket data before training the machine learning model. Historical data is prepared in advance with standardized formats, removed duplicates, and organized structures that reduce complexity during the actual categorization process. This upfront preparation simplifies the runtime operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces intermediary components such as data pre-processing layers, feature extraction modules, and model training pipelines that mediate between raw input data and the core categorization function. These intermediaries break down complex tasks into manageable stages, reducing overall system complexity by organizing the flow of data and operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If large volumes of issue ticket data are processed, then comprehensive coverage of infrastructure issues is achieved, but data inconsistency and noise increase

Engineering Contradiction:
Improvedata volumeVSAvoiddata consistency
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system applies local quality by implementing data cleaning and normalization specific to each data source and ticket type. Different preprocessing rules are applied locally to different sections of the data pipeline, addressing inconsistencies at their source rather than attempting uniform processing. This allows the system to handle diverse data formats and quality levels effectively.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent employs parameter changes by transforming raw data into standardized formats through feature extraction and normalization. The system adjusts data parameters such as text encoding, category mappings, and data structures to create consistent input for the machine learning model, converting unreliable raw data into reliable processed features.

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If real-time clustering and re-clusterization are performed, then dynamic adaptability to changing infrastructure issues is improved, but computational processing time increases

Engineering Contradiction:
Improvedynamic adaptabilityVSAvoidcomputational processing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system implements periodic action by performing full re-clusterization at scheduled intervals rather than continuously. Between these periodic full updates, the system applies incremental updates that only process new or changed data. This approach maintains dynamic adaptability while significantly reducing average computational processing time compared to continuous re-clusterization.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent applies dynamics by making the clustering system adaptable to changing conditions through incremental learning and adaptive parameter adjustment. The model can dynamically adjust to new issue types and patterns without requiring complete retraining, allowing real-time adaptability with minimal computational overhead through selective updates based on data drift detection.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11954444B2Systems and methods for monitoring technology infrastructure
Publication Date: 2024.04.09 ROYAL BANK OF CANADA
  • US11954444B2 patent drawing
  • US11954444B2 patent drawing
  • US11954444B2 patent drawing

AI summary

Systems and methods of monitoring technology infrastructure using alerts indicative service events and tickets indicative of incidents reported to the support system, including transmitting, to a client via a network, structured support data including issue data and correlation data. The issue data represents issues, which are fewer than the number of tickets, generated by processing textual data of the tickets through a clustering engine implementing a generative probabilistic model and generating the correlation data by associating alerts and tickets by correlating alert-specific identifiers and ticket-specific identifiers. The identifiers are of least one of identifier times, locations, names, or descriptions. A prioritization engine is also disclosed.