A truck yard management system controls vehicle flow from booking to departure: carriers reserve arrival slots, the gate captures vehicle and container identity automatically, the yard knows which trailer is in which slot, and drivers are directed to the right place at the right time. It shortens turnaround, reduces road queueing and gives the site a live picture of a space usually managed from a whiteboard.
Trucks queueing on the public road are not a traffic problem. They are a scheduling problem the yard has exported to the municipality.
- Slot booking that spreads arrivals across the day
- Automatic plate and container number capture at the gate
- Live trailer and slot visibility across the yard
- Turnaround measured per stage, not just gate to gate
Everyone arrives at eight and the yard is a whiteboard
Without arrival management, a distribution centre receives its day in two or three surges. Carriers arrive when it suits their route, the gate processes them in order, and the yard absorbs the difference — which it cannot, so the overflow queues on the approach road. That queue is a safety issue, frequently a municipal nuisance issue, and a cost the carriers price back into their rates as waiting time.
Inside the fence, the yard is usually managed by radio and memory. Which trailer is in slot 14, whether the one in slot 22 is loaded, which unit the shunter should move next, and how long the vehicle at the far end has been standing — all of it lives with whoever is on shift. Trailers get lost in plain sight, empties accumulate, drivers wait for instructions in a language nobody at the gate shares, and detention charges arrive weeks later against a timeline nobody recorded.
- Unmanaged arrivals produce surges the yard cannot absorb, so queues reach the road.
- Trailer locations live on a whiteboard and in the shift supervisor's memory.
- Shunting is directed by radio, so moves are duplicated and empties accumulate.
- Drivers wait without instructions they can read in their own language.
- Detention claims are disputed because nobody recorded the stage timings.
Solution overview
Swedish Technology addresses the arrival pattern first, because no amount of yard technology fixes a day where everything arrives at eight. Carriers book slots against the site's real capacity by hour and load type, so the workload is spread and the yard has a plan before the first vehicle appears. That is a commercial arrangement as much as a technical one — slots only hold if carriers are expected to keep them — and we say so plainly, because sites that deploy booking without carrier engagement get an expensive first-come-first-served yard.
At the gate, capture is automated. Plate recognition identifies the vehicle and, where containers are involved, container number recognition reads the code and validates it against the ISO 6346 check digit — so a misread is rejected at the gate rather than propagating into the yard record and being discovered at load-out. Inside, trailer positions are tracked by slot, shunt moves are issued as tasks rather than shouted over a radio, and the driver receives instructions on their phone in their own language. Every stage is timestamped, which turns a detention dispute into a document.
How the solution works
- 1Publish real capacity Slots defined by hour, dock type and load profile from what the site can actually handle, not from an aspiration. Overbooked slots discredit the system in a week.
- 2Carriers book and are held to it Booking through a portal with the reference the driver carries. Adherence is a commercial expectation supported by data, not an assumption.
- 3Capture identity at the gate Plate and container number read automatically, container codes validated against the ISO 6346 check digit so misreads are rejected rather than recorded.
- 4Direct the driver Instructions to the driver's phone or a gate display in their language — where to go, where to wait, and what happens next.
- 5Manage the yard as slots and tasks Trailer positions tracked by slot, shunt moves issued as tasks with confirmation, and standing time visible rather than discovered.
- 6Measure every stage Arrival, gate, yard, dock, departure timestamped separately, so turnaround is diagnosable and detention is evidenced.
Key capabilities
Reference architecture
The gate is the data capture point and the yard is the state model. Both must continue operating when the connection does not.
Deployment options: Cloud with an offline-capable gate. A yard cannot stop admitting vehicles because a connection dropped, so the gate operates locally and reconciles.
Hardware options
Outdoor equipment reading moving vehicles in glare, dust and heat — a harder problem than an indoor reader by a considerable margin.
| Device | Where it is used | Selection notes |
|---|---|---|
| ANPR cameras | Gate lanes, in and out | Reads vehicle plates on approach. Accuracy depends on lane geometry, approach speed and lighting far more than on the camera specification, and GCC plates vary by emirate in format and layout. |
| Container number cameras | Gate lanes, side and rear views | Reads ISO 6346 container codes. Multiple angles matter because a code can be obscured by dirt, damage or door position, and check-digit validation catches the misreads that remain. |
| Driver interface at the gate | Gate lane, at cab height | Kiosk or intercom at the right height for a truck cab, multilingual and readable in direct sun. Getting the height wrong is a surprisingly common and expensive mistake. |
| Yard slot identification | Parking slots and trailer positions | Marked slots with scannable identifiers, or tags on trailers where the operation justifies it. Marked slots plus disciplined scanning solve most of the problem cheaply. |
| Trailer tracking tags | Own-fleet trailers, high-volume drop-and-hook operations | GPS or BLE on trailers where continuous location earns its cost. For most yards, slot scanning at each move is sufficient and far cheaper. |
| Yard displays | Waiting area, gate approach | Calling vehicles forward by booking reference so drivers can wait in the vehicle rather than at an office window. |
Swedish Technology supplies and integrates gate and yard equipment from established manufacturers, specified for UAE outdoor conditions and local plate formats.
AI capabilities
Applied to the reading problem at the gate and to the scheduling problem behind it.
- Plate recognition — Reads vehicle plates across the varied formats used in the UAE and neighbouring states, with confidence scoring that routes uncertain reads to a person instead of guessing.
- Container code recognition — Reads ISO 6346 container numbers from multiple angles and validates the check digit, so a misread is rejected at the gate rather than discovered at load-out.
- Document reading — Captures delivery notes and permits at the gate, which matters where the driver and the guard share limited language.
- Arrival and turnaround prediction — Learns real arrival behaviour against booked slots and predicts congestion, so slot capacity is set from evidence rather than from optimism.
Integrations
These can be designed within project scope.
| System | Integration point & data exchanged | Direction |
|---|---|---|
| WMS and warehouse systems | Expected loads, dock readiness and receipt status, so yard sequencing reflects whether the warehouse can actually take the vehicle. | bi-directional |
| TMS and carrier systems | Booking, arrival confirmation and departure returned to carriers, which is what makes slot adherence commercially real. | bi-directional |
| Dock management | Yard and dock allocation working as one flow rather than two queues. → Loading Dock Management | bi-directional |
| Warehouse visitor management | One driver arrival serving both the safety and access record and the yard operation. → Warehouse Visitor & Contractor Management | bi-directional |
| Access control and barriers | Gate barriers released against a valid booking and a successful identity capture. | outbound |
| ERP and finance | Stage timings supporting detention and demurrage settlement with evidence rather than assertion. → Oracle E-Business Suite | bi-directional |
The integrations above are designed and implemented within project scope using vendor APIs, webhooks or standard connectors. They do not imply partnership, certification or endorsement by the system owner unless stated on that vendor's official pages.
Dashboards & analytics
- Live yard — Every slot, trailer and vehicle with status and standing time — the whiteboard, made accurate.
- Turnaround by stage — Gate, yard, dock and departure timings, which shows whether the delay is the yard's or the warehouse's.
- Slot adherence — Booked against actual arrival by carrier, which is the report that makes the commercial conversation possible.
- Gate performance — Read accuracy, manual interventions and processing time per lane.
Security & deployment
The gate must keep admitting vehicles through a network interruption, so it holds booking and authorisation data locally and reconciles afterwards — a yard that stops at the fence creates the road queue the system was bought to remove. Manual override is always available to the gate operator and is recorded with their identity, because plate and container recognition will fail on damaged, dirty or unusual vehicles and the operator must be able to proceed. Where the site is bonded or handles customs-controlled cargo, gate records and container identity form part of the customs trail and their integrity matters accordingly.
Data privacy
Yard systems capture vehicle plates, driver identity and movement timings for a population of people who are not employees and who are usually in a hurry. Plate and container capture are properties of the vehicle and the cargo; driver identity is personal data and should be collected for access and safety purposes rather than accumulated because the gate makes it easy.
Two practical points. Identity documents should be verified and reduced to an attribute rather than retained as scans in a gatehouse, and the notice explaining what is captured should be readable by drivers in the languages they actually speak. Where the site sits in a free zone, the estate operator may also be capturing the same vehicle at its own gate, so responsibilities are worth establishing rather than assuming. Under UAE Federal Decree-Law No. 45 of 2021 the site operator is the controller for what it captures, and retention should distinguish operational timings — needed for a detention claim — from identity data, which usually needs a much shorter life.
Industry use cases
UAE & GCC considerations
Proximity to Jebel Ali and the region's other major ports means many facilities here handle container traffic directly, which makes ISO 6346 container code capture a genuine requirement rather than an option — and makes check-digit validation valuable, because an identity error on a container is expensive to unwind. Bonded and customs-controlled cargo adds requirements on gate records that should be established with the relevant customs authority at design stage.
Two local conditions shape gate design. Vehicle plate formats vary across the emirates and neighbouring states, and cross-border traffic from Saudi Arabia and Oman is routine, so recognition must handle that variety rather than a single national format. And driver populations are highly multilingual with limited English, which makes visual, multilingual instruction at the gate and on the phone a functional requirement — a driver who cannot read the instruction will stop and ask, and the lane stops with them.
Implementation approach
- 1Measure the current pattern Record actual arrivals, yard occupancy and turnaround for a fortnight. This produces the slot capacity model and usually surprises the site.
- 2Carrier engagement Agree booking expectations with the carriers who generate most of the volume, before deployment. Booking without this becomes an ignored calendar.
- 3Gate design and installation Lane geometry, camera positions, driver interface height and lighting — the physical work that determines read accuracy.
- 4Yard slot model Mark and identify slots, define the yard map and agree the shunt task process with the team who will run it.
- 5Booking go-live Start with the largest carriers and highest-volume load types, expanding as adherence establishes itself.
- 6Tune capacity Adjust slot profiles from measured turnaround. The first capacity model is always wrong somewhere, and the data corrects it quickly.
Why Swedish Technology
- We start with the arrival pattern, because no yard technology fixes a day where everything arrives at eight.
- We say plainly that slot booking needs carrier engagement — it is a commercial arrangement supported by software, not a software feature.
- Container codes are validated against the ISO 6346 check digit, so misreads are rejected at the gate rather than propagated.
- Gate design starts with lane geometry and lighting, which determine read accuracy far more than camera specification does.
- Drivers get instructions in their own language, because a driver who stops to ask stops the lane.
Limitations & prerequisites
- Slot booking only works if carriers keep slots. Without commercial engagement it becomes a calendar people ignore, and the yard reverts to first-come-first-served at higher cost.
- Plate and container recognition accuracy depends on lane geometry, speed, lighting and the condition of the plate or container. Manual fallback is a permanent part of the design.
- Yard capacity is physical. Better scheduling improves flow within the available space; it does not create more of it.
- Trailer tracking tags add cost that is justified in high-volume drop-and-hook operations and often not otherwise — marked slots plus disciplined scanning solve most cases.
- Turnaround improvement is limited by the warehouse. If the dock cannot unload faster, yard scheduling relocates the wait rather than removing it.
- References to customs and data protection obligations are general guidance, not legal advice.
FAQ
A system that controls vehicle flow from arrival booking to departure: slot booking, automated identity capture at the gate, live visibility of which trailer is in which slot, shunt task management, and stage-level timing of every movement.
Slot booking, and carrier engagement to make it stick. The queue is the visible result of unmanaged arrivals, so spreading arrivals across real capacity is the only intervention that removes it — gate speed alone just moves the queue a few metres.
Only if it is a commercial expectation rather than an invitation. Sites that deploy booking without engaging their main carriers end up with an ignored calendar. Adherence reporting by carrier is what makes that conversation possible.
Good with well-positioned multi-angle cameras, and importantly it is verifiable: ISO 6346 container codes carry a check digit, so a misread can be rejected at the gate rather than entering the yard record. Dirt, damage and door position still cause failures, so a manual path is required.
Usually not. Marked slots with scannable identifiers and disciplined scanning at each move solve most yards at a fraction of the cost. Trailer tags earn their place in high-volume drop-and-hook operations with large own-fleet trailer pools.
By timestamping each stage separately — arrival, gate, yard, dock, departure. A detention claim then becomes a comparison of records rather than a monthly argument about who kept whom waiting.
Yes. The gate holds booking and authorisation data locally and continues admitting vehicles, reconciling when connectivity returns. A gate that stops creates exactly the road queue the system exists to prevent.
It will remove the scheduling and coordination component of it, which is usually substantial. It cannot make the warehouse unload faster — if the dock is the constraint, yard scheduling relocates the wait rather than removing it, and the stage-level data will show you that clearly.
Discuss your site with an engineer
Tell us the venue, the expected visitor volume and the systems you already run. We reply with a technical view, a realistic scope and the next sensible step — a site survey, a working demonstration, or a full technical and commercial proposal.
Sources & evidence
- UAE Federal Decree-Law No. 45 of 2021 — Personal Data Protection Law — Governs collection, retention and cross-border transfer of visitor personal data in the UAE.
- ISO 6346 — freight containers coding, identification and marking — Standard defining container identification codes and the check digit used to validate them.
- Dubai Customs — Customs authority requirements relevant to bonded and customs-controlled cargo movements.
Vendor and product names are trademarks of their respective owners; references are for technical context and do not imply partnership, certification or endorsement.