Use case

Every vehicle at the gate becomes something the site can act on.

Plate reads from Vailient Plates enter Canvas as events, so gate staff, plant managers and building teams work from the same record.

Demo data
Canvas gate event list on the fictional demo plant: each plate read with its plate image, province, vehicle type, location and camera

From a plate read to a response

A plate is recognised, checked against what the site expects, and routed. A known supplier truck is simply logged. Something unexpected opens a ticket.

  • Time on site for each vehicle, and where it was last seen
  • Rules for who is expected and when
  • Cameras placed on the map for context
Demo data
A Canvas vehicle record on the fictional demo plant built from gate plate reads: one vehicle with its details, sightings and plate image
Cars parked in rows in a cobbled car park, seen from above
Illustrative photo

How a site sets it up

  1. Place the cameras

    At the gate, the barrier or the car park entry.

  2. Define the rules

    Who is expected, and what should be done when someone is not.

  3. Route the events

    Choose who is told and how.

Demo data
A truck timeline in Canvas on the fictional demo plant, not customer data: one plate with its gate passes on a map and a timeline

Mitsui Bussan

Supplier truck dwell time at a Samut Prakan factory

How plate reads at the gate became an operational view of waiting time.

A supplier gate at a Samut Prakan factory

Read the story

Turn the gate into a source of facts.

Request a demo and see plate events in Canvas.