Guide

How to Reduce PID Call-Outs on Temporary and Remote Sites

Updated 29 September 2026 · 5 min read

Perimeter intrusion detection systems (PIDS) on temporary and remote sites generate a steady stream of engineer visits, and many of them are not caused by the detection equipment itself. Teams that want to reduce PID call-outs usually get the quickest results by looking at power, communications and physical tampering, and by checking these remotely before anyone is dispatched.

Why engineers get sent to PID systems

When a perimeter system reports a fault or goes quiet, the receiving centre or hire desk often has little to go on. Without more information the safe option is to send someone. The most common underlying causes are:

CauseWhat happensCan it be checked remotely?
Power lossMains or generator supply fails and the system runs on battery or stopsYes, with power monitoring
Flat batteriesSolar or backup charging cannot keep up and the battery runs downYes, with state of charge and charging data
Communications dropoutThe system stops reporting because of signal or router problemsPartly, by checking connectivity and last report time
Tamper or tiltA post, tower or cabinet is knocked, moved or interfered withYes, with tilt, movement and location data
Genuine equipment faultA sensor, cable or controller failsUsually needs a site visit

The problem with dispatching blind

An engineer sent without information may arrive to find a flat battery they have no replacement for, a router that just needed restarting, or a system working normally after a brief signal loss. Each of those is a wasted or repeated journey, often at night or at the weekend.

Meanwhile the perimeter may be partly or wholly unprotected. Knowing the likely cause before dispatch means the right person goes with the right parts, or nobody goes at all.

There is a contractual side too. Many temporary security contracts include response times and availability commitments. A call-out that fixes a flat battery after the system has already been down for hours still counts against availability, whereas spotting the falling battery the day before keeps the perimeter protected and the visit planned.

How to reduce PID call-outs with remote triage

The goal is to answer a few questions from the office before deciding to send anyone:

  • Is the system powered? Check supply status and whether it is running on battery.
  • How long can it last? Check battery state of charge and whether charging is working.
  • Is it connected? Check signal and when the site last reported, and whether other equipment on the same site is reporting.
  • Has anything moved? Check tilt, movement and GPS location against where the equipment was installed.
  • Is it a pattern? Check whether the site has had similar faults recently.

Turning triage into clear actions

Once the likely cause is known, the response can be matched to it. A simple decision table helps the hire desk or control room act consistently.

What the data showsLikely response
Power and battery healthy, connection lostTry a remote router restart or wait a set time before dispatch
Battery falling, charging not workingPlan a visit with a replacement battery or fuel before it goes flat
Mains or generator supply lostContact the site or arrange a fuel delivery
Tilt or movement detectedTreat as urgent and contact the site or security response
Power, battery and connection all healthy, fault persistsDispatch an engineer for a likely equipment fault

Preventing the next call-out

Triage deals with the fault in front of you; trend data helps stop it happening again. Look at which sites repeatedly lose power or connection. A site with marginal signal may need a different antenna position or connectivity type. A solar-powered perimeter that runs short every winter may need more panel area, a larger battery or a backup fuel cell.

Set alerts that fire before the system fails rather than after, such as a low state of charge warning or a site that has missed its usual reporting interval. That gives time to fix the cause during normal working hours.

Finally, record the outcome of every call-out: what the engineer found and whether the visit was needed. After a few months, those records show which causes are most common on your sites and where changes to power, connectivity or installation practice will have the biggest effect.

Where TrackSyte fits

TrackSyte does not analyse or filter intrusion alarms; that remains the job of the detection system and the monitoring centre. What it provides is the supporting picture: power, battery state of charge and charging, connectivity, device tilt and movement, and GPS location for each PID installation, along with Ajax security system integration where used.

The TrackSyte Portal groups this on one map with critical, warning and information alerts, and notifications by email, webhook or Slack, so teams can check the basics before deciding whether an engineer needs to go.

FAQs

What is a PID system?

A perimeter intrusion detection system uses sensors such as fence-mounted detectors, beams, radar or video analytics to detect people crossing or tampering with a site boundary.

Why do PID systems on temporary sites need so many visits?

They often run on batteries, solar or generators and rely on cellular links, so power and communications problems are common alongside genuine equipment faults.

Can remote monitoring tell me if an intrusion alarm is genuine?

Power and connectivity monitoring does not verify intrusion alarms. It helps you rule out or confirm power, battery, communications and tamper causes before dispatching an engineer.

Why monitor tilt on perimeter equipment?

A tilted post, tower or cabinet may mean it has been struck or tampered with, and detection coverage may be affected. Tilt alerts flag this without waiting for a patrol.

Check power and connectivity before you dispatch

TrackSyte shows power, battery, connectivity, tilt and location for every PID installation in one portal. Book a demo to see how it supports your triage process.