SECURITY & CYBERSECURITY THE HIDDEN COST OF
SECURITY SYSTEM DOWNTIME Ask any facilities or estates manager running more than a handful of sites what keeps them up at night, and a security fault rarely tops the list on its own. The priority, says John Lodge, Director of Service Growth at Chubb Fire & Security UK & Ireland, is what happens next.
A missed service visit, an unresolved issue or incomplete record all seem manageable in isolation. But repeat engineer callouts, temporary workarounds and the admin that comes with chasing them down add up fast across a large or geographically dispersed estate.
Why it gets harder at scale Keeping on top of security systems takes more than sticking to a maintenance schedule. Responsibility shifts from site to site and is dependent on what's installed and who's accountable. Portfolios are diverse and rarely look the same at every location.
One site might be an office running modern access control and networked CCTV. Another a warehouse with an ageing intruder alarm panel nearing the end of life. Each fails differently and each gets missed differently. A perimeter intrusion system might sit quietly non-compliant for months if nobody's testing detection zones. However, an access control fault often announces itself immediately, as soon as someone can't get through a door. Video analytics can also degrade gradually, with a camera slipping out of focus or a blind spot appearing after a shelving reset.
This is where the real challenge sits. Individual sites can be operating with no immediate issues with scheduled engineering visits and faults are logged when they’re discovered. However, those responsible for the estate- wide picture often have no, or limited, visibility.
Knowing servicing is happening somewhere isn't the same as knowing where it's overdue, which faults are still open, who's supposed to act next, or whether the same problem keeps cropping up at different sites. On a five-site estate, that gap is an inconvenience. On fifty sites, it's a genuine blind spot.
The cost that doesn't show up on the
fault log When something goes wrong, the instinct is to get it fixed and move on. However, the cost of that downtime doesn't end when the engineer leaves.
A single fault can mean follow-up visits, a member of staff manually covering a situation they were never trained to manage, or building users left inconvenienced with no clear visibility on what’s happening. It can also mean a site manager improvising: propping a door open ‘just for today’ or delaying a delivery because access control is down and nobody wants to take responsibility. None of that gets logged as a security cost, but it's a real one.
34 | TOMORROW’S FM
Multiply that by a busy estates team fielding calls and trying to work out whether this is a one-off or the third time this quarter, and the real cost starts to show. It's rarely one dramatic failure that causes the damage. It's the accumulation of small, unresolved issues, each absorbing a bit more time, each slightly eroding confidence in the system, until the team is managing by firefighting rather than by plan.
It’s worth stressing again that scale can make a situation worse. Issues repeated across dozens of locations start eating serious time, not because any single fault is severe, but because there's no consistent way of seeing them together.
That's why finishing the job matters as much as fixing it. An engineer signing off a visit isn't the end of the story if that visit flagged a defect or recommended follow- up work. There needs to be a clear, visible route from ‘someone found a problem’ to ‘someone fixed it’, not a note buried in a file nobody reopens.
Start with a simple framework A structure goes a long way toward bringing order to what can potentially cost your state downtime and lost revenue:
1. Know the estate - An up-to-date asset register that includes what's installed, the location, and condition is the starting point. But for security systems, that needs to go further. Security systems should show which systems are monitored and which aren't, as well as which sites connect to an alarm receiving centre.
2. Assign ownership - Be clear who owns what at site level, who has the wider view and who picks it up when something needs pushing further. An unresolved fault on a monitored system can affect how the response is classified and may result in an incorrect follow up.
3. Schedule centrally - One schedule beats a dozen site diaries, and it's far easier to spot what's coming up and what's slipping into 'overdue.'
4. Keep evidence - Service records, test results, fault reports and proof something got fixed must be kept consistently, not scattered across engineers' notebooks and inbox threads.
5. Chase down exceptions - Faults and missed activity need logging, assigning and tracking through to completion, with a process to escalate when something stalls.
twitter.com/TomorrowsFM
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62
