Skip to article content
NUMERISH / INSIGHTSTelecommunications

Calculating service-impact minutes across a telecom incident

Use a worked example to distinguish elapsed incident time from the customer impact that accumulates as individual services recover.

A mechanical stopwatch shows its marked dial in close-up.
Telecommunications / Numerish Insight
Jump to a section
  1. 01Calculate the intervals that actually count
  2. 02Use the measure for a decision

An incident that lasts an hour can affect customers very differently. One circuit may be unavailable throughout, while another loses service for only ten minutes. Counting incidents alone gives a poor basis for prioritising recurring faults. Service-impact minutes provide another view when the measurement unit is explicit.

Calculate the intervals that actually count

Imagine three distinct services lose connectivity at 09:00. One recovers at 09:10 and the other two at 09:30. The outage lasts thirty minutes overall, but the services accumulate seventy unavailable service-minutes. If a fourth ticket duplicates one of those services, exclude the duplicate from the calculation. Record the chosen time zone and any uncertainty about the first observed impact.

Use the measure for a decision

Compare impact between similar service populations and periods. A high figure at a shared access point may justify a reliability review even if its incident count is low. Keep contractual availability calculations separate because the applicable measurement windows and exclusions may differ. The restoration record gives analysts the service identities and recovery evidence needed to explain their operational measure.

Explore the Numerish telecommunications workflows.

KEEP EXPLORING

More to discover in Numerish.

Explore related insights and practical enterprise workflows.

Browse all insights
FROM INSIGHT TO ACTION

Put the ideas to work.

Explore the Numerish connected enterprise platform.

Explore ERP360