For airport security and terminal operations teams. Review a perimeter event with the sightings around it, and see where queue areas and halls pass the thresholds you set, from one platform and the cameras already installed.
- 1Perimeter · Fence-line zone entry
- 2Terminal · Queue and hall counts
- 3Restricted areas · Entry outside permitted hours
- 4Parking · Plate reads; dwell limits
The problems we start from
Who it is for
- Airport security operations
- Terminal operations
- Landside and car-park management
A perimeter alert arrives with no context
An operator sees that a line was crossed, not what else was seen nearby before and after.
Queue pressure is noticed too late
A hall is full before anyone opens another lane.
Security and operations work from separate pictures
The same cameras serve both teams, through different tools.
One workflow, step by step
Review a perimeter event, then read the terminal
Scenario. A person enters a fence-line zone after hours. The same morning, a check-in hall passes its queue threshold.
The perimeter rule raises an alert
A zone along the fence line, on a schedule, raises an alert when a person enters. The alert leads to the sighting and its still.
Look at the neighbouring cameras
Group look-alike sightings on the cameras either side. They are candidates to compare.
Trace a vehicle on the landside roads
Where a vehicle is involved and its plate was read, see its stops in time order on a map.
Mark and assign the alert
A named operator marks it Acknowledged or False positive and assigns it.
Watch the queue areas
A count rule on each camera that views a queue area raises an event when the number of people in its view reaches your threshold. The figure is a count of the people the camera is following, and each of them is also kept as a sighting.
Read occupancy by area
People counted by hour for each camera, filtered by the floor and area labels on the cameras.
Measures
Four measures, each with a definition.
Defined so that two people would compute the same number. None is a result: the values come from your pilot.
- Queue estimate
- The number of people counted in the view of a camera that covers a queue area. A count, not a wait time.
- Measured from: Count events and occupancy figures.
- Threshold duration
- How long a camera's count stayed at or above its threshold.
- Measured from: Computed from count events read through the API. Not a built-in chart.
- Incident response
- The median time from a perimeter alert being raised to its being marked.
- Measured from: Alert statistics in Insights.
- Coverage
- The share of cameras online, by area.
- Measured from: Camera health in Insights.
Events of interest
Events for the perimeter, landside and terminal.
Each says what it needs and where it stops. The rules you set on a camera raise these events, and the alerts that go with them.
Zone entry
A person or vehicle enters a perimeter, fence line or restricted area.
- When
- A followed object enters the drawn zone.
- Limit
- The detector looks for people and vehicles rather than motion, which reduces but does not remove false detections from animals, reflections and headlights. A badly placed zone edge can also catch passers-by.
Line crossing
A person or vehicle crosses a line you draw, in the direction you choose.
- When
- A followed object crosses the line one way, the other way, or either way.
- Limit
- An object that is only partly in view near the line can be counted as crossing, or missed. A crossing inside the rule's repeat limit is not recorded.
Restricted-area access
A person enters a room, floor or yard at a time when entry is restricted.
- When
- A person enters the zone outside the permitted hours.
- Limit
- The rule knows the time, not the person: it cannot tell an authorised entry from an unauthorised one.
Queue too long
The number of people in the view of a camera that covers a queue area reaches the number you set.
- When
- The count of people in the camera's view reaches the threshold.
- Limit
- A count of everyone the camera can see: not a count inside a drawn queue zone, and not a wait time. Staff and passers-by in view are counted too.
Occupancy threshold
The number of people or vehicles in a camera's view reaches the capacity you set.
- When
- The count of the chosen object type reaches the threshold.
- Limit
- It counts what one camera can see, so a space covered by several cameras needs a rule on each.
Item left behind
A bag, case or stopped vehicle stays still beyond the time you set.
- When
- A backpack, handbag, suitcase or vehicle stays still past the limit.
- Limit
- Only the detected item types are covered, anywhere in the camera's view. A bag beside its seated owner can be reported.
Vehicle stopped where it should not
A vehicle stays in a no-stopping zone, a fire lane or an emergency bay beyond the time you set.
- When
- A vehicle's time inside the zone passes the limit.
- Limit
- A vehicle held in traffic inside the zone is reported like a parked one.
Camera offline
A feed stops arriving. The platform keeps trying to reconnect and shows the camera as offline until the picture returns.
- When
- The feed is still missing after repeated reconnection attempts.
- Limit
- A camera that streams a frozen picture can look healthy. The alert repeats while the feed stays down.
Use cases
What airport security and operations teams use it for.
What the current release does for this kind of site.
Perimeter entry
An alert, linked to the sighting's still, when a person enters a fence-line zone
Restricted areas outside hours
An entry during the hours an area is closed
Queue thresholds
An event when the people in view of a queue-area camera reach a number
Occupancy by area
People counted by hour, filtered by floor and area
Item left on a concourse
A bag left still beyond a set time, for an operator to check
Vehicles stopped at the kerb
An event when a vehicle stays in a kerb zone beyond its limit
What it needs
- Zones drawn for each fence-line section, on cameras labelled with their floor and area
- A camera whose view is each queue area, seen from above without heavy occlusion: a count covers the whole view
- An assessment of how streams can be read from your video management system
- A decision on which cameras are analysed: each person a camera follows is kept as a sighting, and there is no count-only mode
Pilot objective
On one fence-line section and two queue areas, show that perimeter entries reach a reviewer with context, and compare the queue counts with a manual count at agreed times.
Read the pilot guideBoundaries
- No connection to access-control or screening systems is packaged. Any link is scoped and assessed separately.
- One machine per deployment. High availability has not been validated, so the platform should not be the only way an event is noticed.
- No aviation-security certification or regulatory approval is claimed.
- A queue or hall figure is a count of the people the camera is following. Each is also kept as a sighting, with a still where a frame was captured, for the retention period; there is no count-only mode. Choose which cameras are analysed with that in mind.
- Face search is not offered in the current release and is not part of this workflow.
Capabilities used
The same platform. Different rules.
Each site gets its own cameras, modules and rules. Nothing is custom-built; everything is configured.
Explore an airport security and operations walkthrough.
Choose a fence-line section and two queue areas. We will show a perimeter review and the queue counts on footage from them.