Skip to main content
Streamlit Dashboard — Portfolio Project

Operations Backlog & Service Quality Dashboard

Backlog aging analysis, SLA compliance tracking, workload distribution analysis, root cause investigation, and bottleneck scoring with an interactive Streamlit dashboard.

PythonPandasNumPySciPyPlotlyStreamlit

Simulation Note: This project uses a synthetic/sample dataset. Financial impact, savings, ROI, and SLA-cost estimates are modeled scenarios for analytical demonstration and do not represent actual NTC financial figures.

Modeled Estimate (synthetic data)

51.7%
SLA Breach Rate
78%
SLA Compliance
8.5h
Avg Resolution Time
85/100
Network Bottleneck
45%
Top 20% Ticket Load
12%
Critical SLA Breach

Interactive Dashboard

SLA Compliance by Category

Hourly Ticket Volume Pattern

Avg Resolution Time by Category

Bottleneck Score by Team

Business Problem

The support/ops team has a growing backlog. Leadership wants visibility into bottlenecks, SLA breaches, and resource allocation.

Methodology

Step 1

Data Loading

Loaded support ticket dataset with categories, priorities, resolution times, SLA compliance, agent workload, and aging data

Step 2

Data Preparation

Cleaned and transformed data, calculated aging buckets, SLA compliance rates, and agent performance metrics

Step 3

Multi-Dimensional Analysis

Analyzed backlog aging, SLA compliance by category/team, workload distribution, root causes, and bottleneck scoring

Step 4

Dashboard Deployment

Deployed multi-page Streamlit dashboard with aging analysis, SLA compliance, workload distribution, and root cause views

Key Insights

01

Persistent Backlog Problem

15-20% of tickets remain in open backlog at any time. 25% of open tickets are aged more than 7 days, indicating systemic bottlenecks in resolution workflows.

02

SLA Compliance Gap

Overall SLA compliance is 78% (target: 90%). Installation category is worst at 65% compliance due to complex setup processes. Billing is best at 92%.

03

Uneven Workload Distribution

Top 20% of agents handle 45% of tickets. Peak hours (10 AM - 2 PM) see 40% of daily ticket volume. Weekend volume is 30% lower but staffing remains the same.

04

Bottleneck Identification

Network team has highest bottleneck score (85/100). Hardware tickets take 2x longer to resolve than Software tickets. 20% of agents handle 60% of high-priority tickets — burnout risk.

05

Root Cause Patterns

Critical tickets have 12% SLA breach rate — unacceptable for customer satisfaction. Average resolution time is 8.5 hours across all categories.

Business Recommendations

Modeled Estimate (synthetic data)
01

Resource Reallocation

Move 2 agents from Billing to Network Ops. Expected impact: Reduce Network bottleneck by 25%. Investment: $0 (internal reallocation).

$0 investment
02

Process Optimization

Streamline Installation process (currently 24h avg resolution). Implement escalation triggers for tickets aging > 3 days. Improve SLA compliance to 85%.

03

Workload Balancing

Implement round-robin assignment for high-priority tickets. Cross-train agents to handle multiple categories. Reduce agent burnout risk by 40%.

04

Preventive Measures

Automated ticket routing based on category and agent skills. Proactive monitoring for hardware issues before they become tickets. Reduce ticket volume by 15%.

Technical Highlights

Backlog Analysis

  • ▸Ticket aging bucket analysis
  • ▸SLA compliance tracking
  • ▸Resolution time distribution

Workload & Bottleneck

  • ▸Agent workload distribution
  • ▸Bottleneck scoring model
  • ▸Peak hour identification

Statistical Testing

  • ▸Chi-Square for priority vs SLA
  • ▸Kruskal-Wallis for resolution time
  • ▸Mann-Whitney U for team comparison

Dataset

Support ticket dataset with categories, priorities, resolution times, SLA compliance, agent workload, and aging data.

Project Outcome

Modeled Estimate (synthetic data)

Identified resource reallocation opportunities ($0 investment) and process improvements projected to raise SLA compliance from 78% to 85%+. The bottleneck scoring model enables leadership to prioritize team resources where they have the most impact.