Hi everyone,
I'm working with a CSP team that's setting targets for Mean Time to Repair/Restore/Resolve (MTTR) within Autonomous Networks fault management and would value the community's experience.
Rather than a single number, we're looking for practical ranges (and what's driving them) across domains:
- RAN / Access
- IP/MPLS Core / IP Core
- Optical / Transport
- Telco Cloud / Platform services
To keep comparisons apples‑to‑apples, please note which MTTR you use (Repair vs. Restore/Recovery vs. Resolve), how you start/stop the clock, and any assumptions (on‑net vs. off‑net, urban vs. rural, protected vs. unprotected services, severity).
Helpful inputs include:
- Internal target bands or anonymized "typical" values
- Public SLA objectives you use as external anchors
- Any design patterns (e.g., protection/FRR, automation/runbooks, remote test/OAM) that materially change MTTR
If you can share a link, brief context, or a contact willing to compare ranges offline, that would be fantastic.
Thanks in advance for your insights and feel free to reach me privately in case you needed more context.
#AIandData#CustomerExperience#ZeroTouchAutomation------------------------------
Javier Ponce Betti
TM Forum - Regional Manager
jbetti@tmforum.org------------------------------