At twenty to six, the NOC lights up with a fibre cut alarm on a ring that feeds a bank branch and two ATMs. The splicer rostered for that patch has phoned in sick. The next splicer is forty minutes away, and the CCTV technician cannot fuse a cable. The restoration clock is ticking, and the branch manager rings every ten minutes.
Absence on a field team is not only a rota gap. It is also a skills gap, a distance gap and a restoration-time gap. Here is how tower, fibre, ISP, CCTV and network maintenance firms can cover for it. The telecom and field technology services hub has the wider picture.
Know who can do what
Draw a one-page skill matrix with each technician as a row. Across the top, list the tasks: fibre splicing, OTDR testing, tower climbing, rooftop radio alignment, router and switch configuration, CCTV camera commissioning, DVR or NVR setup, customer premises installation, cable laying. Mark each cell as independent, with supervision, or none. The dispatcher then knows whom to ring first.
The network maintenance providers competency page describes how such a matrix can be maintained.
Cluster-based standby
- 1
Divide the city into clusters
Use travel time, not distance. A cluster is the area one technician can reach in about forty minutes on a bike.
- 2
Pick one standby per cluster
The standby holds the laptop, splicing kit or router stock, and keeps his phone on. He is paid a fixed standby allowance.
- 3
Post the standby roster weekly
Send it to the NOC and the dispatcher every Friday. Mark each engineer's backup.
- 4
State the response time
For example, a ticket assigned to a standby is acknowledged within ten minutes and the technician is en route within thirty.
- 5
Rotate fairly
Do not give the same person every Sunday. Use a rotation sheet that everyone can see.
Ticket reallocation rules
- The dispatcher may move any open ticket once half its SLA window has gone.
- A ticket crossing clusters is allowed only if the travel time is stated and the engineer agrees.
- A tower or height job requires a second person on site, so a lone technician cannot cover it.
- Customer-premises installation tickets are rescheduled, not forced, when a technician is absent and no one else is free.
Leave in monsoon and festival weeks
Rain brings cable cuts, water ingress in joint closures and tower works postponed. Festival weeks bring home visits, road closures and shop closures. Announce a blackout period for leave sixty days ahead and offer a swap: a compensatory day the week after. Engineers who know the rule in advance plan around it. Those who learn it at the last minute resign.
What to record
- Absence by cluster and by skill, split into planned and sudden.
- Tickets reassigned and tickets that missed the SLA clock.
- Standby calls and response times.
- Leave refused in blackout weeks and the swap offered.
These numbers also show where training is needed. For a design of such records, see the internet service providers attendance process and our attendance, shift and leave service.
Questions that always come next
Who covers when the standby is also absent? Name a second standby for every cluster, and agree a fallback to the neighbouring cluster for the first hour only. What about the new joiner who is not yet on the matrix? Mark him as supervised for his first month and never place him alone on a customer's roof. And what about outsourced crews? Tell the vendor's supervisor the same response time and keep the same ticket rules; read the telecom infrastructure companies page for site safety expectations.
Also think about tools. A spare splicing machine, a laminated cheat sheet of router commands and a stock of drop cable in the standby's bike box turn a forty-minute trip into a fifteen-minute repair.
A weekly check that keeps cover alive
- Review the skill matrix every Friday against the leave calendar.
- Look for any skill held by only one person in a cluster.
- Plan cross-training for that skill within the month.
- Check the standby kit: charged laptop, OTDR, splicer, spare ONT, crimping tool, spare cameras and drop cable.
Planned leave against sudden calls
Planned leave, training days and compensatory offs can be loaded into the roster a week early, so the standby plan stays calm. Unplanned absence is different. Ask each engineer to message the dispatcher before five thirty on the morning of the shift, not at dispatch time. Record the reason in a few words. A pattern of Monday absence after a long weekend, or of absences in one cluster, points to something to talk about, such as a long commute or a harsh supervisor.
