DMS Group

Follow one truck

From the data that enters through the ETL to the gate out and the billing line: nine steps, one Gate Operating System, next to your TOS.

Works with the TOS, cameras and barriers you already run

Before the barrier

The truck is known before it arrives, then read and checked at the gate.

1
Data in (ETL)
2
Appointment (VBS)
3
Virtual Kiosk check-in
Gate in: cameras + OCR
In detail

From the TOS to the gate camera

1 · Appointments and moves arrive from the TOS by JSON push (API key) or CSV over SFTP; Excel discharge plans are dropped by hand or received at a dedicated address, with history kept. 2 · The truck has an appointment in our VBS: the gate knows who is coming, for which container and which operation. 3 · The driver checks in at the Virtual Kiosk before the gate; the transaction reaches the TOS in real time. 4 · Existing IP cameras film, the OCR reads container, plate and chassis, and the GOS matches the read with the appointment.

Image link

5 · GOS decision and barrier

Appointment found: the barrier opens, whatever its brand. Otherwise the clerk decides.

Ghost Barrier, any brand
Force or refuse, reason mandatory
Reason mailed to the dispatcher
Image link
Pilot

6 · Seal, damages, EIR

Seal read or entered on PC or tablet; damage inspection backed by the OCR reads.

One EIR per pass
Opened by a signed link
PDF to the carrier
Image link
In production

7 · Yard and ship side

Every pass recorded by yard area and lane on a tablet.

Yard area and lane per pass: in production
Ship-side lots by vessel and voyage: roadmap
Non-blocking alerts on seals and yards: roadmap
Image link

8 · Gate out and TOS event

GATE_IN / GATE_OUT events sent back to the TOS, with a retry queue.

Retry queue if the TOS does not answer
EIR at the exit, depending on the yard
Status: pilot
Image link
Roadmap

9 · Billing and reports

Every move becomes a billable line, with a daily CSV export to the billing system and the clerk's Excel exports.

One billable line per move
Daily CSV export
ERP connector
Image link

Always on: resilience

The GOS runs on site with a cloud relay; if the internet drops, gates keep running on the local network.

On site (active) + cloud relay (passive)
Nothing lost when the link drops
Status: pilot

Next to your TOS, not in its place

The GOS reads and writes your terminal operating system; it does not replace it. It plugs into what the terminal already has: TOS, cameras, barriers.

Formats

JSON, CSV over SFTP, gate events

JSON push with an API key, CSV over SFTP, GATE_IN / GATE_OUT events with a retry queue.

Gate
OCR

Your cameras, your barriers, our gate

Read container, plate and chassis with your existing IP cameras, match the appointment and open any barrier brand.

Image link
Kiosk
Clerk

Check in before the gate

Drivers check in before the gate, the transaction reaches your TOS in real time and the clerk follows every lane on one screen.

Image link
Yard
Tablet

After the gate

Every pass recorded by yard area and lane on a tablet; a live yard map shows cameras, gates, kiosks, barriers and readers by status.

Image link
Image link

© 2026 DMS Group