Use-case scenario · Housing society · 8 cameras
The society gate register nobody could read
Society security fails at the gate, because the gate is a notebook and a guard who changes every six months. The fix was making the log write itself.
- Sector
- Residential / housing society
- Location
- Punjab
- Cameras
- 8 existing cameras at gates and common areas
The challenge
- The visitor register was a paper notebook that was never read back and often illegible.
- Residents queued behind delivery vehicles at the boom barrier.
- Nobody could answer who had entered the premises on a given evening.
- Guard turnover meant institutional memory of regular visitors reset constantly.
What we did
Register resident vehicles once
Recognised plates are logged on entry and exit without a stop, which removed most of the queue immediately.
Photo-log every non-resident entry
Visitors and deliveries become timestamped records with a snapshot — searchable, legible and not dependent on handwriting.
Common areas, narrowly scoped
Parking, clubhouse and pump room alert only on defined situations. Children playing in the common area generate nothing.
Processing kept on the premises
Because the society is residential, all video processing runs on a device on site — a point the residents' committee asked about first.
What changed
Searchable
Gate log, replacing an unreadable notebook
No stop
For registered resident vehicles at the boom
On-site
Processing — no resident video leaves the society
The concern this scenario addresses
The register used to be a notebook nobody read. Now every entry has a photo and a time, and we can actually look something up.
Typical of residents' committee member — illustrative, not a customer quote.
Illustrative scenario, not a report of a completed project. It shows how PGAK would be configured for a site of this type and the outcomes such a setup is designed to achieve; the figures are modelled, not measured at a named customer.