Vehicles

An ANPR system that turns the gate register into something you can search

An ANPR system can help a gate team find recorded vehicle movements by plate or time. AI Alerto by PGAK assesses the capture view, vehicle approach and operating conditions before defining a searchable log and its review workflow. Plates can be missed or misread, so the pilot compares captured records with observed traffic and keeps an agreed fallback. This page covers project scope across real gates; the vehicle and number plate recognition page explains the capability.

Check my cameras →WhatsApp about this solution

Treat this page as evaluation guidance. Product availability and site suitability require an approved configuration and technical test. Published scenarios are illustrative, not verified customer results.

Sound familiar?

The gate register is a paper notebook, filled in inconsistently, and unreadable after a month.
Material left on a truck and reconciling which one took three weeks and never fully resolved.
Resident and staff vehicles stop at the gate every single day for a check nobody actually performs.
You need to confirm plate readability across all intended lanes before accepting an ANPR proposal.

Where searchable vehicle records can help

The value is concentrated in a few situations. Outside them, plate recognition is an expensive way to produce a log nobody reads.

Dispatch and material movement

Factories and warehouses can compare captured vehicle records with dispatch records when investigating a movement. Confirm the fields and timestamps available, measure missed or incorrect reads, and agree any after-hours alert separately.

Gates with heavy repeat traffic

Housing societies, office parks and campuses can assess registered-vehicle lists and visitor records. Any barrier action requires compatible hardware, agreed operating rules, a tested safety workflow and a manual fallback; a plate read alone is not permission to admit a vehicle.

Contractor and fleet oversight

Sites where vehicles belong to other people. Arrival and departure times become evidence for billing disputes rather than a matter of recollection.

Multi-gate estates

Large sites where a vehicle entering gate one and leaving gate three is currently two unrelated notebook entries. One searchable record across gates is the whole point.

The camera is the project

A usable plate image depends on the approach, field of view, exposure, lighting and vehicle speed. The survey checks these conditions and the intended software and processing setup together, then the pilot measures performance on actual traffic.

Plate height, not general coverage

A wide overview image may show a vehicle without enough detail to read its plate. Assess mounting position, capture distance, angle and the plate size in the image; a dedicated capture view may be needed.

Enough pixels across the plate

The plate must occupy enough of the frame to resolve characters. This is a lens, distance and angle calculation done at survey — not something a better model rescues later.

Test coverage across every intended lane

Camera count depends on lane geometry, plate size in the image, approach angle, occlusion, speed and lighting. Some gates need a dedicated camera for each lane; confirm the layout and test all intended lanes before specifying hardware.

Headlights, rain and night

Headlight glare, rain, shadows and changing light can affect plate capture. Include representative daytime and night traffic in the pilot, and record where exposure or illumination changes are needed.

Test the plates and traffic your gate receives

Test the plate formats and conditions your gate actually receives, including motorcycles, trucks, damaged plates and partial obstruction where present. Measure correct reads, incorrect reads and missed vehicles against an independent traffic record. Retain the agreed snapshot and manual review workflow; a difficult image is a reason to record uncertainty, not invent a plate number.

Sizing the hardware, honestly

Processing requirements depend on the selected cameras, resolution, frame rate, number of streams and enabled analytics. Size the intended deployment and test it under the expected traffic load before quotation. Confirm whether processing hardware, camera changes, installation and barrier integration are included as separate items.

What to check before deployment

Camera and recorder streams: Confirm RTSP access or ONVIF discovery, stream stability and the views that matter. Do not send camera passwords in the enquiry form.
On-site processing: Ask which processing device is needed, how it is sized, what runs locally and what information leaves the site.
Alert acceptance: Test agreed zones in daytime and at night. Record useful alerts, nuisance alerts, missed events and end-to-end alert delay.
Complete commercial quote: Confirm enabled cameras, sites, subscription, setup, hardware, taxes and support. Use the assessed scope to compare proposals.

Get a site-specific AI video analytics price.

ANPR system — common questions

Which ANPR camera is best for a factory gate?

Choose the camera after checking capture distance, mounting angle, plate detail, approach speed and day/night lighting. A general overview camera may not provide a suitable plate image. Assess existing equipment and confirm any camera changes, coverage limits and test criteria before quotation.

What is an ANPR system?

Automatic Number Plate Recognition uses cameras and software to read visible registration plates and create searchable records. Confirm which vehicle details, direction, timestamps and snapshots the proposed workflow captures. It can support a gate register, but missed or incorrect reads still need a review process.

How accurate is ANPR on Indian number plates?

PGAK has not published a read rate. Measure correct reads, incorrect reads and missed vehicles at your gate against observed traffic, including representative daylight and night conditions. Camera setup, plate condition, approach and the recognition workflow all matter. Agree the acceptance criteria and fallback before rollout.

Can ANPR run on our existing gate camera?

Possibly, if the camera provides a suitable stream and a readable plate image under the intended operating conditions. The survey checks mounting, distance, angle, resolution, speed and lighting. Repositioning or a dedicated capture camera may be required; the assessment records any limitations before quotation.

Do we need one camera for each lane?

Not as a universal rule. Assess every intended lane for plate detail, angle, occlusion, speed and lighting. Some layouts require dedicated cameras per lane; other layouts need a different arrangement. Confirm camera count through the site survey and a representative gate test.

Can ANPR open a boom barrier automatically?

Automatic barrier opening is something a site may configure and test, not a PGAK default: recognition of a registered vehicle can trigger an action at the gate only where suitable barrier hardware is in place and can accept a trigger. Barrier supply and its electricals are a separate scope from recognition, so it is worth confirming what your gate already has before assuming automation is included.

Start with a free audit of your own cameras.

Share your phone number, city and camera count. We will discuss your priority use case and agree the assessment scope, timing and next step with you.

Get my free audit →See pricing

From a working install

The camera, and the screen the guard actually uses

Two photographs from a PGAK gate installation. They show where the camera actually sits and what the guard actually sees — the part a buyer can check against their own gate. They prove a fitting and a working console, not a read rate.

A small bullet camera on a bracket fixed to an existing gate pillar, mounted at about 1.5 metres and angled along the lane — Mounted on the pillar that was already thereThis installation uses a bullet camera on a bracket fixed to the existing gate pillar, with no new pole or civil work and one cable run. The available mounting point, cabling and capture view need checking separately at your gate.Conditions: This photograph shows one installation, mounted at about 1.5 metres and aimed along the lane in daylight. The height and angle annotations describe this setup; the image wording about roof height is not a universal mounting rule. Your camera, capture distance, approach angle, lighting and software need to be assessed together and tested on representative vehicle passages.

The PGAK gate console listing vehicle reads with approve and deny buttons, allow-list labels and per-read diagnostics, with all number plates blurred — Every read is a decision someone makesThe console a gate operator works from. Each arrival is a card to approve or deny, allow-listed vehicles are marked as staff or contractor, and every read shows its own working — how many frames agreed, the margin, and how many pixels wide the plate was. As shown, each read waits for the operator's decision; any automatic admission is something a site may configure and test, not a default.Number plates are blurred here. A registration number identifies a person, so it is removed before anything is published — including in a screenshot used to sell the product.

These show one gate, one camera position and one set of lighting conditions. They are evidence that the system has been fitted and operated, not a measurement of how it would read plates at your site — that depends on your gate, your lighting and your lane, and it is tested on your own footage before anything is quoted.

Who you are dealing with

A registered Ludhiana company that builds the software it sells.

PGAK Innovations Pvt. Ltd. is incorporated in Punjab, engineers its own AI layer, and runs the free camera audit itself — the people who answer the phone are the people who built the product. About the company →

Founded: 2023, Ludhiana
Registered office: BK Towers, 2480/2, Gill Rd, Ludhiana 141003
CIN: U62013PB2023PTC058631
Leadership: Puneet Garg · Ankur Kaplesh · Aditya Mittal; Why PGAK was built →
Talk to us: +91 62839 93600 WhatsAppOpen Mon–Sat 09:00-19:00

What a project here involves

Compatible cameras and recorders you already own are reused wherever they are suitable. Detection runs on an on-site processing unit, and camera suitability, stream access, processing hardware and network are all confirmed at the assessment — with anything extra itemised in the quote before you commit.

What the quote is made of

Component	What decides it	Price
Cameras reused	Which existing cameras give a usable view for each use case — confirmed on a still image of each view.	Quoted per site
Cameras moved or added	Only where a use case needs a view no camera has (plates and faces usually do). Each one named in the quote.	Quoted per site
On-site processing unit	Detection runs here, next to the recorder. Model, quantity and warranty depend on camera count and analytics.	Quoted per site
Software / licences	Which analytics on which cameras, the term, and the basis for renewal.	Quoted per site
Installation and configuration	Stream setup, zones, schedules, alert routing and commissioning.	Quoted per site
Pilot	Agreed scenes, acceptance criteria and duration before rollout.	Quoted per site
Support	Hours, response versus fix time, and who replaces failed hardware.	Quoted per site
Taxes	Stated separately on the quote.	Quoted per site

How it is evaluated

1. Self-check — Two minutes, nothing sent — find likely blockers.
2. Scope on paper — Cameras, use cases and acceptance tests, written down.
3. Site assessment — PGAK checks streams, views and network on your cameras.
4. Pilot against criteria — Precision, recall, false alerts and delay, agreed in advance.
5. Written proposal — Itemised as above; you decide whether to roll out.

Evidence for this page

Plate reading fitted to an existing gate pillar. Photographed on site in daylight, with the camera mounted at roughly 1.5 metres. The image annotation refers to this installation and is not a universal height specification. Night performance and other camera positions are not demonstrated by this photograph. Not proved: Plate-reading accuracy, missed reads and performance in other lighting or traffic conditions are not established by these photographs. Assess the camera view and software together, then measure representative vehicle passages at your site. See it →

Calculator · C09

ANPR and vehicle logs: estimate it for your site

Use your own measurements. The result is the staff time released, shown separately from any cash, using the formula below. It runs in your browser and nothing is sent anywhere.

Fields start empty. A blank is “not entered”, not zero; type 0 where 0 is true.

Vehicle passages per day (per day)

Operating days per month (days)

Old handling seconds per vehicle (seconds)

New handling seconds per vehicle (seconds)

Exceptions per month (per month)

Unread or misread plates a guard handles by hand.

Minutes per exception (minutes)

Money (optional)

Loaded hourly cost of the staff whose time is released (₹ per hour)

Salary plus benefits and overheads, per working hour. Needed only if you enter a realisation above 0%.

Realisation: share of released hours that becomes cash (%)

0% unless you can name the mechanism — overtime that stops, a post not refilled, a contract reduced.

Other cash change you can evidence (optional) (₹ per month)

Only from your own records. May be negative.

Recurring incremental cost (₹ per month)

Licences, support, connectivity. Enter 0 if there is none.

One-off setup capital (₹)

Hardware, installation, commissioning. Enter 0 if there is none.

Enter every amount on the same basis — all including GST or all excluding it. Nothing here adds or removes tax. Values are nominal rupees, not discounted.

Result

Enter your own figures, or load the worked example, to see the result.

How it is calculated

hours = passages per day × days × (old − new seconds) ÷ 3600 − exceptions × minutes per exception ÷ 60

Worked example (illustrative inputs)

200 a day; 26 days; 45 old; 15 new; 50 exceptions at 2 minutes.

staff time released: 41.667 hours a month.

Formula version 1.0.0. The full standalone tool: anpr gate time.

What this does not tell you

Hours released are capacity, not cash. They become cash only through a mechanism you state — overtime that stops, a post that is not refilled — entered as the realisation fraction.
The 'after' values are your assumptions or pilot measurements. PGAK publishes no effectiveness figure for this feature.

Evidence status: Installation photographs only; recognition performance not verified.

Discuss your camera setup

Share your phone number, city and camera count. We will clarify the intended use case and agree assessment scope and timing with you. Do not submit camera credentials or footage.