Simat Labs
Book a demo

Vehicle & Plate Recognition

Vehicle & Plate Recognition

ANPR for gates and parking — plate reading, occupancy, and access lists on edge hardware.

HQ Parking — Gate 1

--:--

LIVE·CAM-G1·plates only · on edge
CAM-G1 · entry lane
scanning…
closed

Reads today

1,912

Occupancy

184/240

Read time

62 ms

22-48193
allow · whitelist
Gate 1 · in·99%·reading
10-71265
visitor · pre-registered
Gate 1 · in·97%·1m ago
35-02918
deny · not on list
Gate 2 · in·98%·4m ago

edge-gate-01 · healthy

Arabic + Latin plates

Vehicle & Plate Recognition (ANPR) reads licence plates and vehicle attributes at gates, barriers, and parking entrances, including the Arabic and Latin plate formats used across Jordan, Saudi Arabia, and the UAE.
It gives facilities, compliance, and security teams automatic gate decisions, parking occupancy, and a searchable log of every vehicle movement, replacing manual logbooks and guard checks.

Recognition runs on an edge unit at the gate, so a barrier opens whether or not the network is up. Plate reads and events sync to a central dashboard; raw video stays at the site.Allow lists, deny lists, and visitor passes are managed centrally, and every read carries the image crop, lane, and timestamp for audit.

Regional plate reading

Reads Arabic and Latin plates across GCC and Jordanian formats, day and night, at the speeds typical of gates and ramps.

Gate and access control

Allow and deny lists, visitor passes with time windows, and barrier control from the edge unit — with a manual override for guards.

Parking occupancy

Entry and exit counts per lot and level give live occupancy, average stay, and overstay alerts for compounds, malls, and offices.

Powered by IFA

Runs as a module on the IFA edge box beside your cameras.

About IFA

The IFA dashboard

One dashboard for every module

Every IFA module reports into the same web dashboard. A new module shows up with its charts, events, and automations the day it is deployed — nothing is coded per module.

Plant overview — today

HourDayWeek·group by: line

Events per hour

Line 3 · QA failsDock 4 · crossings
020406006:0008:0010:0012:0014:0016:00Dock 4 · crossingsLine 3 · QA fails

Events by severity

Critical6
Warning41
Info137

184 events · 2 modules · 4 cameras

Streams

  • Line 3 — labeleronline · 24 fps · 41 ms
  • Dock 4 — closeonline · 20 fps · 38 ms
  • Dock 4 — fardegraded · 11 fps · 2 reconnects
  • Line 1 — capperoffline · last seen 09:12

Automation runs

  • Label fail → email shift leadok11:42
  • 5 fails in 10 min → capture + WhatsAppok11:38
  • Dock 4 far offline → emailsuppressed11:20
  • Session closed → reportok10:57

Live camera monitoring

Every camera as a health card: online, degraded, or offline, with frame rate, latency, and uptime, and a live view from the edge box when it is streaming. Refreshes on its own.

Charts derived from events

Pick a metric, group by line, zone, severity, or product, and bucket by hour, day, or week. Line, bar, area, stacked, and pie — all built from the events a module emits, never hand-coded.

Event log and notifications

Every event, filterable by module, type, and severity, with the frame that triggered it. Email and WhatsApp notifications go out through automations, with a per-run record of what was sent and what was suppressed.

No-code automations

A drag-and-connect flow builder: a trigger (a module event, a camera going offline, a schedule), logic (filter, window, cooldown, time gate), then actions — send an email, send a WhatsApp message, capture the frame, generate a report.

Reports for managers

A report action turns a session or a shift into a readable document — totals, shares, per-product detail — attached to the notification email and kept in the dashboard's report list.

ANPR questions

Which plate formats are supported?

Jordanian, Saudi, and Emirati plates in both Arabic and Latin characters, plus common formats from neighbouring countries. New formats are added by training on samples from your own gates during the pilot.

What hardware is needed at the gate?

A camera with a clear view of the lane and an edge unit beside the barrier. Existing gate cameras often work; where they do not, we specify a camera with the right angle and IR for night reads. The edge unit connects to the barrier controller via a relay or your access-control system.

Does it connect to our parking or access system?

Yes. Reads and decisions are available through an API and webhooks, and the edge unit can trigger barriers directly. Allow lists can be synced from your access-control or visitor-management system rather than maintained twice.

How is plate data handled?

Plate reads are personal data in most jurisdictions, so retention is configurable per site and reads can be purged on a schedule. Raw video stays on the edge unit; only reads, crops, and events sync to the dashboard, which runs on-premise or in your chosen cloud region.

Last updated: