SOC–NOC Collaboration: Alarm-to-Ticket Automation

[DELIVERABLES]
AUTOMATION
[IMPACT]
Efficiency
[ROLE]
Automation Engineer
[SERVICES]
ALARMS • Tickets • FIELD
[THE STORY]

Operations teams were drowning in noisy alarms and manual ticket handling, slowing response time during incidents. I built an automation pipeline that cleans and suppresses alarms, extracts critical details, correlates events, and automatically creates and assigns tickets to the right teams/field crews. It also calculates customer impact and flags blackout zones when a major area is affected—resulting in faster triage, fewer duplicate tickets, and clearer outage visibility.

[SOLUTION]

An end-to-end SOC–NOC workflow that transforms raw alarms into clean, enriched incidents with automatic ticket creation, smart assignment, and real-time customer impact/blackout classification.

GITHUB
[ARCHITECTURE]
Python
JavaScript
MySQL
Jobs
Workflow
[DEVELOPMENT SPECIFICATIONS]
WORKFLOW
Business Process
DATABASE
MySQL
JOBS
Air Flow
[USER FLOW]
USER FLOW

Alarms received → Clean + suppress + normalize → Extract & enrich critical context → Correlate + apply rules → Create ticket → Auto-assign to team/field → Compute customer impact + blackout % → Update ticket + dashboard until resolution

[DETAILS]
  • Ingest and load alarms at scale (batch/stream-ready)
  • Cleaning, deduplication, and suppression to reduce noise
  • Extraction of critical alarm context for actionable incidents
  • Automated ticket creation with correct severity and metadata
  • Smart assignment to relevant teams and field dispatch groups
  • Customer impact calculation (count + blackout % classification)
  • Dashboards and audit logs for end-to-end operational visibility