About This Architecture

A three-tier hierarchical RCA engine that progressively refines unstructured support tickets through technical anomaly extraction, business keyword clustering, and contextual AI vector discovery. Tier 1 scans SAP error signatures and applies agglomerative sub-clustering; Tier 2 locks tickets to predefined business objects (PO, GRN, SES, PR, STO, ASN) using cosine similarity; Tier 3 processes long-tail conversational tickets via BERTopic, UMAP, and HDBSCAN in compressed vector space. A unified quality gate applies centroid calculation, hard cosine pruning (0.85 threshold), few-shot ITIL prompting via Phi-3, and programmatic deduplication across all tiers. This architecture solves the challenge of automating RCA categorization at scale while maintaining business context and technical precision across heterogeneous ticket sources.

People also ask

How do you build a scalable root cause analysis system that combines SAP error detection, business object classification, and AI vector clustering for enterprise ticket management?

This three-tier hierarchical RCA engine progressively refines tickets through technical anomaly extraction (Tier 1), business keyword sub-clustering (Tier 2), and contextual AI vector discovery (Tier 3), then applies a unified quality gate with centroid-ranked sampling and few-shot ITIL prompting via Phi-3 to generate deduplicated technical titles.

3-Tier Hierarchical RCA Engine Architecture

AutoadvancedRCAmachine-learningclusteringNLPenterprise-systemsticket-classification
Domain: Data EngineeringAudience: Data engineers and ML practitioners building root cause analysis (RCA) systems for enterprise ticket classification
2 views0 favoritesPublic

Created by

July 23, 2026

Updated

August 6, 2026 at 10:52 AM

Type

architecture

Need a custom architecture diagram?

Describe your architecture in plain English and get a production-ready Draw.io diagram in seconds. Works for AWS, Azure, GCP, Kubernetes, and more.

Generate with AI

AI-generated. Verify before production use. Learn more

Report this diagram