Built to survive a bad network day
Most parking systems are demoed on a good day. The design decisions that matter are the ones that show up during a power cut, a monsoon, and a 6pm shift change happening at once.
Four decisions that define the system.
Decisions happen at the edge
The controller decides whether a barrier opens. Not a server in another city. A WAN outage degrades reporting, never lane operation — transactions buffer locally and reconcile on reconnect.
Read before the driver stops
Long-range tag reads and ANPR capture happen on approach, not at a halt. Dwell time is the only lever that meaningfully changes queue length, and it is won in the approach, not the barrier.
Degrade, never halt
Every lane has a fallback path. Plate unreadable, tag missing, power out — each has a defined next step that keeps the lane moving. A stopped lane is a failure; a slower lane is not.
Everything is a record
Plate, timestamp, lane, operator, payment method and image are written for every movement. That record is what makes revenue computable and disputes resolvable.
Four layers, one accountable vendor.
The failure most sites suffer is not technical — it's that four different companies own these four layers and none of them owns the outcome.
Field devices
Cameras, barriers, loop detectors, photocells, long-range readers, POS terminals and LED displays. Selected per lane geometry, not per catalogue page.
The controller
Every device on site terminates here. Local rules engine, local transaction buffer, local device health. This is the layer that keeps a site alive during an outage.
Site operations
Trained marshals, cashiers and supervisors working to a written SOP, with an escalation tree. The layer most vendors leave to you.
Dashboard & reporting
Occupancy, revenue, device health and searchable vehicle logs — rolled up across every site in a portfolio.
Ask what happens to the 2%.
Every ANPR vendor quotes a recognition rate. At 98% on a site handling 5,000 vehicles a day, that is 100 cars whose plate was not read — and what the system does with those 100 matters more than the headline percentage.
A system that stops those vehicles and waits for a marshal has effectively created 100 queue events. A system that falls through to a tag read, then a ticket, clears them without anyone noticing. That fallback design is the question worth asking, and very few vendors volunteer the answer.
Fallback chain, per lane
- ANPR reads the plate on approach
- RFID / FASTag if the plate is unreadable
- Ticket if neither resolves
- Manual override, logged and attributed
Each step is automatic. The driver experiences a slower lane, never a stopped one.
See it running on a live site
We'll arrange a walkthrough of an operating deployment — including what it looks like when something fails.