For residential communities and the teams that guard them. Keep a sighting of each vehicle and person the gate camera follows, raise an alert on after-hours activity in shared spaces for a guard to review, and give the committee a weekly summary instead of a recorder nobody watches. Alerts appear in the dashboard and on the event stream your own tools can read.
- 1Main gate · Arrivals as sightings, with stills
- 2Walkways · After-hours zone entry
- 3Common areas · People counts and items left
- 4Parking · Vehicle search; dwell limits
The problems we start from
Who it is for
- Managing committee
- Facility manager
- Gate and patrol guards
The gate log records what was typed, not what happened
A visitor book or app holds an entry when a guard makes one. The camera saw every crossing.
Nobody watches the shared spaces at night
Lobbies, car parks and terraces are recorded, and reviewed only after a complaint.
The committee has no evidence
Questions about a night, a vehicle or a guard post are answered from memory.
One workflow, step by step
Resolve a gate-to-building exception
Scenario. A resident reports an unfamiliar vehicle parked overnight in the basement.
Keep a sighting of each arrival
Each vehicle and person the gate camera follows becomes a sighting with its time and, where a frame was captured, a still. Plates are read where they are legible.
Find the arrival
Search the gate camera for that evening by vehicle type, colour or plate.
Add direction with a line rule
A line across the gate lane raises an event, with direction, when something crosses it. Crossings inside the rule's repeat limit are not recorded, so it is not a complete log.
Follow it inside
Look for the same plate, or for look-alike sightings, on the car park and lobby cameras. These are candidates to compare, not a confirmed path.
Check the stills
Open each still. For the minutes around it, use your recorder.
Record the outcome
Today a finding is recorded in the product only as a note on an alert. A review that starts from a resident's report and a search has no alert, so the outcome goes in your own incident record.
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.
- Gate arrivals
- Vehicle and person sightings on the gate camera, by hour. Direction needs a line rule.
- Measured from: Sightings on the gate camera, and counts by type and hour in Insights.
- After-hours events
- Zone entries in a shared space during its closed hours, per area per week.
- Measured from: Events on the after-hours rules.
- Unresolved exceptions
- Alerts still marked New after a time you agree.
- Measured from: The alert queue, by status.
- Cameras online
- The share of cameras online, with each camera that has been offline for more than an hour named.
- Measured from: Camera health in Insights and the weekly brief.
Events of interest
Events for gates, lobbies and shared spaces.
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.
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.
After-hours presence
A person or vehicle is in an area during the hours it should be empty.
- When
- Zone entry inside a scheduled window.
- Limit
- The schedule follows the clock, so authorised late work raises it unless that camera is excepted.
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.
Loitering
A person stays in an area longer than the time you set.
- When
- Time inside the zone passes the limit.
- Limit
- If a person is lost and found again, the timer can restart, so long stays may be reported late.
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.
Plate on watchlist
A plate that is read matches an entry on your organisation's watchlist.
- When
- A plate read matches a watched plate exactly, with commonly confused characters treated as the same, or within one character.
- Limit
- A plate that cannot be read cannot be matched. A near match must be compared by a person before anyone acts.
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 a community security team uses it for.
What the current release does for this kind of site.
Gate arrivals
Each vehicle and person the gate camera follows, as a sighting with its time and, where a frame was captured, a still
Vehicle search
Find a vehicle by type, colour or plate
After-hours activity
An entry to a lobby, car park or terrace during its closed hours
Crossing direction at the gate
An event, with direction, when a line across the gate lane is crossed
Weekly brief for the committee
Movements, alerts, false alarms and camera health in one page
Camera health
Cameras that have gone dark, named
Blocked vehicle
An alert when a plate you have listed is read
What it needs
- A camera that sees the full width of each gate lane
- Zones drawn for the shared spaces you choose, with their closed hours
- A recipient list for the weekly brief, if it is switched on
- A written policy on who may search, and on how long records are kept
Pilot objective
On the main gate and two shared spaces, show that each arrival the gate camera follows is kept as a sighting with a usable still, and measure how many after-hours events a guard judges worth acting on.
Read the pilot guideBoundaries
- VisionObject is not a visitor-management or delivery-confirmation system: it does not know who was expected or approved.
- Matching sightings with visitor, resident or access records needs an integration assessed for your site. None is packaged.
- Pending approvals and visits without a check-out can only be measured with visit records from your gate system.
- A watchlist alerts on the plates you name. There is no list of residents' vehicles that alerts on everything else.
- There is no resident profile and no list of residents. A plate's read history is kept, has no retention period yet, and can be searched by the roles that may search; each such search is written to the audit log. Sighting records are deleted after the period you set; events have no retention period in the current release.
- Face search is not offered in the current release, and no list of faces can be enrolled for residents.
Capabilities used
The same platform. Different rules.
Each site gets its own cameras, modules and rules. Nothing is custom-built; everything is configured.
Review incidents across your residential community.
Choose the gate and the shared spaces that matter. We will show the gate sightings, the after-hours events and the weekly brief on footage from them.