AI at the gate · session 3 of 4
A perimeter system counts movement, dwell time and line crossings. It cannot tell a resting rider from a reconnaissance. This session is about the gap between the alert and the answer.
Six alerts as they actually arrive: loitering at the fence line, an unattended bag, the third false alert of the shift, a view blocked by a parked lorry, two alerts at once with one officer. An intrusion that turns out to be a cat. Each one trains the same habit - verify, then decide, then close the alert with a reason.
Corporate pricing on request. Course funding application status: pending.
The scenario
A perimeter system is patient and literal. It sees movement in a zone, a person standing still for longer than a threshold, a body crossing a line. It reports each one with the same flat certainty. What it never reports is what the movement is.
That gap is the whole job. The alert tells an officer where to put his eyes; his eyes make the decision. He has to close the alert so that the next person can see the shift as it actually was. A post that leaves alerts open has a record that says nothing.
Three false alerts teach an officer to slow down or to stop looking. Both are dangerous, and the difference between them is whether the reasons were written down and counted.
The six decisions are the ones that actually go wrong on a quiet shift. They are, in the order the run puts them:
What changes, and for whom
For the officer on patrol
The screen tells you where, never what. This session rehearses the fast verification that keeps a shift moving without teaching you to stop believing the alerts. The habit that decides whether a real breach is caught.
For the supervisor
An officer drowning in false alerts quietly stops checking, and the shift looks normal until the night it is not. The session trains the officer to record dismissals with reasons, which turns fatigue into evidence you can act on.
For the agency
The analytics gets better when somebody counts the false alerts by type. An agency whose officers close alerts properly ends up with a system that suits its own site instead of one nobody trusts.
These are descriptions of the work the training addresses. They are not client results and not a promised saving.
What the officer does, in order
About ten minutes at the post, on the officer's own phone, with a supervisor on site.
The marker goes on the camera pole at the rear fence line. The overlay marks the wall line, the blind side and the safe approach.
The alert point, the walk line and who to call appear over the live picture, anchored to the pole rather than floating on the screen.
Each is a real alert, with immediate feedback on what the analytics could and could not know.
The run closes with the five-field record, the same as every other course here.
Every session writes the same record, so four sessions make one page of that officer's training history, and the same five fields are asked of the newest officer and the most senior one - which is the part of it that is fair. The run is written to the agency's list in the five fields the checklist reads.
This page is the session. The run itself is on the player: open it here - the practice run needs no camera. It is session 3 of 4 in AI at the gate.
This is post training, so there is no assessor to satisfy - but the record matters anyway: it is how an agency shows what its officers were trained on, in what order, and when.
| Field | What it carries |
|---|---|
| Name | As written in the agency's own staff record. Nothing else is stored about the officer. |
| NRIC / FIN | The last four characters only. The full number is never entered and never leaves the phone. |
| Training provider | Whichever name the checklist route puts here: the agency's own name when the agency delivers the training in-house, or the service provider's name when a provider delivers it - in that case the checklist also asks the agency to submit the provider's invoice showing simulation training was used. The field is left blank on purpose: it is typed, not assumed. |
| Course title | States the technology: the training programme or session plus Augmented Reality (AR) Simulation Training. |
| Date of training | The date the run was completed, written from the device at the time of the run. |
The record lives on the officer's own phone until it is exported or printed, so the habit is: run it, then save the list. The house standard is 80 per cent, which is a fair bar for six decisions, and a failed run is a re-run rather than a mark against an officer.
Every course here is honest about what it is and what it is not, because a package that oversells itself is the one that lets an agency down in front of an assessor. Read these before you book anything.
Questions about this session
AI at the gate · session 3 of 4
Fix one marker at the real point, open the session on a phone, and see whether the overlay holds where your officers actually stand. That is a fair test, and it takes three minutes.
Corporate pricing on request. Course funding application status: pending.