📡 Telecommunications
Telco ITSM operates at a scale that no other sector matches: millions of network CIs, real-time incident detection across geographically distributed infrastructure, and SLA commitments to enterprise customers that carry financial penalties. The convergence of OSS/BSS with modern ITSM platforms is the defining challenge of telco IT service management.
Service Architecture
ITIL Implementation Journey
Telecom ITIL 4 Implementation Roadmap
Click any step to expand · 6 steps
Key Use Cases
1. Network CI Impact Analysis
When a core router fails, the impact cascades across thousands of customers:
Core Router (PE-PARIS-01) — down
→ MPLS VPN customers impacted: 847 enterprise circuits
→ Residential broadband impacted: ~120,000 subscribers
→ Voice (VoIP) degraded: 34,000 lines
→ CDN nodes isolated: 3 edge PoPs
Auto-actions:
→ P1 incident created (customer impact > 10,000)
→ Enterprise account managers notified (SLA at risk)
→ Network operations bridge opened
→ Media monitoring activated (social sentiment)CMDB query for impact:
Parent CI: PE-PARIS-01 (Core Router)
→ Child relationships: 847 MPLS circuits
→ Each circuit → Customer account → SLA tier
→ Financial exposure: sum(penalty per SLA breach hour)2. Major Incident on Live Networks
Change management on live telco networks requires extreme caution — a bad config push can take down millions of subscribers.
Change risk gate for network changes:
| Risk Factor | Score |
|---|---|
| Number of subscribers potentially impacted | 0–25 pts |
| Change window (off-peak vs peak traffic) | 0–15 pts |
| Rollback time (< 5 min = low risk) | 0–20 pts |
| Previous changes on this CI in 30 days | 0–15 pts |
| Test on lab environment | 0–25 pts |
| Total → Risk Level | LOW / MEDIUM / HIGH / CRITICAL |
- CRITICAL: Board-level CAB approval, dual-sign-off from NOC Director
- HIGH: Standard CAB + NOC engineer on standby
- MEDIUM: Change Manager approval only
- LOW: Self-approval with NOC notification
3. SLA per Customer Segment
| Segment | Availability | MTTR | Penalty |
|---|---|---|---|
| Consumer Broadband | 99.0% | 8 hours | None (fair usage) |
| SME Connectivity | 99.5% | 4 hours | Credit = 1 day/breach |
| Enterprise MPLS | 99.9% | 2 hours | Credit = 1 week/breach |
| CNI / Government | 99.99% | 30 min | SLA liquidated damages |
4. BCP for Telco Core Systems
| Scenario | Response | RTO |
|---|---|---|
| Primary core DC power loss | Switch to warm DC | < 30 min |
| BSS billing outage | Read-only mode + manual billing | < 1 hour |
| OSS platform failure | Fallback to manual NOC procedures | < 2 hours |
| Submarine cable cut | Reroute traffic via alternate paths | < 15 min |
5. Field ITAM — Radio Equipment
Telcos own millions of physical network assets in the field:
- Track all RAN equipment by site, cabinet, and slot
- Auto-update CMDB when equipment is swapped during field interventions
- Manage equipment lifecycle: provision → install → in-service → EOL → decommission
- Integrate with field service management for work order dispatch
CapEx vs OpEx
| Category | CapEx | OpEx | Trend |
|---|---|---|---|
| RAN infrastructure (towers, antennas) | ✅ | — | CapEx (owned assets) |
| 5G Core (virtualised on cloud) | — | ✅ | Shifting to OpEx |
| OSS/BSS platforms | ✅ + ✅ | ✅ SaaS | Mixed |
| ITSM platform | — | ✅ SaaS | OpEx preferred |
| NOC operations | — | ✅ | Managed NOC growing |
Tool Selection Guide
| Context | Platform | Reason |
|---|---|---|
| Tier 1 operator (global) | ServiceNow + AIOps (Moogsoft/Dynatrace) | CMDB at scale, AI event correlation, enterprise SLAs |
| Regional operator | BMC Helix + TrueSight | Strong network CI management, multi-tenancy |
| Digital/MVNO | Jira SM + PagerDuty | Lightweight, fast, DevOps-native, low cost |
| OSS/BSS-first integration | SMAX + NetCracker | OpenText ecosystem, deep OSS integration |
← Back to Industries Overview · Template Library