Rays SensingSite flows · logistics sites and yards

Gate counts, dock dwell times and yard occupancy for logistics sites.

Count trucks, vans, cars and people in and out of every gate, time how long vehicles wait at docks and in waiting areas, and see how full your yard and car park are. Measured with radar and LiDAR at your site, day and night.

128-line LiDAR · own recordingone frame
One LiDAR frame seen at an angle, close up: the scene as grey points and two tracked objects, each in a 3D box. Points and shapes only, no image of a face

Four questions it answers

Each one becomes events in the log, figures on the console and columns in the export.

Illustration: a logistics site seen from above in late afternoon light, a warehouse with trucks at the loading docks, a truck parking and the entrance gate, with sensor poles at the gate and in the yard Illustration
Gate, docks and truck parking: the three zones a site-flows installation measures.
01

Gate in and out, by class

How many trucks, vans, cars and people came in and went out, per gate, per hour and per day?

You getCounts per gate, class and direction

02

Dwell at docks and waiting areas

How long does a truck wait before it reaches a dock, and how long does it stay there?

You getDwell time per visit, per dock and per waiting area

03

Yard and parking occupancy

How many places are taken in the yard, the truck parking and the car park, now and over the day?

You getLive occupancy and a daily profile per zone

04

Zone alerts

A person in a vehicle-only zone, a vehicle parked where it should not be, an entry after hours.

Alerts and records, not a safety system.

You getAn alarm on the console, by e-mail or by SMS, and a record in the event log

Where the sensors go

A typical layout. The positions for your site come out of the site visit.

Typical sensor layout on a logistics siteA site plan: the gate on the left with lanes in and out, an internal road marked as a vehicle-only zone, a waiting area, a warehouse with its docks and dock area, a car park and a yard for truck parking. Radar and LiDAR units watch the gate, the waiting area, the dock area, the car park and the yard; an optional camera sits at the gate. The sensors connect to an edge computer on the site, and operators use the console in a browser.inoutGateVehicle-only zoneWaiting areaWarehouseDock areaCar parkYard / truck parkingEdge computerConsolein a browser
Radar and LiDAR at the gate count every crossing by class and direction; units over the docks and the yard time each visit and measure occupancy. A camera can be added at the gate where you want one. All sensors connect to the edge computer at the site; operators use the console in a browser.

The data you get

Every crossing, visit and alarm is an event in the log. The console shows them on the site map; the same data comes out as CSV files for your own tools.

  • We do not read number plates; a visit is followed as an anonymous track from gate to dock where the sensors cover the route between them.
  • Data comes out as CSV; connection to your yard or dock system is checked during feasibility.

Event log

Example of the export format, not measured data

Event log — Example of the export format, not measured data
TimeGate / zoneClassEventDwell
07:31:08Gate 1TruckIn—
07:31:40Waiting areaTruckEnter—
07:42:52Waiting areaTruckExit00:11:12
07:43:30Dock 3TruckEnter—
07:58:17Gate 2VanOut—
08:05:44Zone B · vehicles onlyPersonAlarm—
08:31:02Dock 3TruckExit00:47:32
CSV export · Daily summary

CSV export

Example of the export format, not measured data

timestamp,zone_id,class,event,dwell_s
2026-10-01T07:31:08,gate_1,truck,in,
2026-10-01T07:42:52,waiting_area,truck,exit,672
2026-10-01T07:58:17,gate_2,van,out,
2026-10-01T08:05:44,zone_b,person,alarm,
2026-10-01T08:31:02,dock_3,truck,exit,2852

Daily summary

  • Per gate: vehicles and people in and out, by class, per hour and per day
  • Per dock and waiting area: number of visits, average and longest dwell
  • Per zone: occupancy over the day, the peak and when it happened
  • Alarms: count per zone and type, each linked to its event in the log

The console

Site map with live tracks, zones you draw yourself, alarms, the event log and CSV export, in a browser.

Try the simulated console → Interactive · simulated, no real sensor data
LiDAR recording seen from above: the scene as grey points, each tracked person or object in a box with the path it followed
128-line LiDAR · own recording

What stays on site

  • LiDAR and radar measure distance, position, shape and speed. They do not capture faces or identifiable images.
  • A camera is optional. Where you want one, we set it up with you: what it sees, what is stored, for how long and who can view it.
  • The edge computer at your site does the processing. Counts and events go to the console, which runs on servers within the EU, and to the exports, and alerts can also be sent by e-mail or SMS; images are not sent off site unless agreed.

What we install, what you provide

We install the radar and LiDAR units, a camera where agreed, the edge computer and the console; you provide a mounting point and power for each sensor, a network connection or a place with mobile coverage, and the reference data for the evaluation. The full list, on the pilot page →

Day, night and weather

Radar and LiDAR need no light, so the counts continue at night. Radar is largely unaffected by rain and fog; dense fog and heavy snow shorten what LiDAR sees, and we position the two so that one covers for the other. A camera needs light.

Start with one gate

A pilot on one gate or one area, with the success criteria agreed before we install.

How a pilot works →
Site flows enquiry

Tell us about your gates and yard

Which gates, docks or zones, and what you want to know about them.

What you receive, and attachments
  • A first sensor layout for your gates and yard
  • A proposal for a pilot on one gate or one area
  • A quote for your site

You can attach a site plan or photos here, or send them by email later.

Name and work email are required.

What to measure
Reply within one working day.

We use these details only to answer your request. Privacy policy