Oil painting in blue: a yard coordinator in a high-visibility vest holds a tablet at the gate, with trailers backed up to the docks
  1. Home
  2. NexLog OS
  3. Academy
  4. YMS

Yard Management System from gate to dock.

Yard, gatehouse and dock scheduling in the same MDM as the WMS and TMS: dock scheduling, call-to-dock, gate kiosk, check-in and check-out, exception playbooks, dwell time and turn time.

From gate to dock, without queues

Scheduling, self-service gate check, check-in, call-to-dock and check-out become events with auditable timestamps. Whatever the playbook can't solve escalates to Control Tower.

  1. SchedulingdockSchedules and time window
  2. Gate kioskCPF, CNH, CT-e and NF-e
  3. Check-inyardVehicles · waiting
  4. PlaybooksNo appointment or document
  5. Call-to-dockSMS, push or app
  6. Loading and unloadingWMS wave
  7. Control TowerUnresolved exception
  8. Check-outDwell time and turn time

Illustrative yard flow.

Overview

The NexLog OS YMS controls the yard, gatehouse and dock scheduling: dock scheduling, call-to-dock, gate kiosk, check-in and check-out and exception playbooks.

Dwell time and turn time KPIs come from the same events that feed the WMS and TMS, with no parallel spreadsheet.

Core entities

The canonical YMS model, shared with WMS waves and TMS routing.

EntityCodeDescription
Dock appointmentdockSchedulesTime window reserved for a specific dock; integrates with TMS routing and WMS waves.
Yard vehicleyardVehiclesVehicle present in the yard; tracks check-in, position, status (waiting, loading, released) and check-out.

Operational flows

Six flows for a yard without queues.

Dock scheduling

Online dock scheduling with time windows, recurrence and capacity by vehicle type.

Call-to-dock

Automatically calls vehicles in the yard to available docks, via SMS, push or app.

Gate kiosk

Self-service for drivers: CPF, CNH, CT-e, NF-e, photo and LGPD consent form.

Check-in and check-out

Records with auditable timestamps; feeds dwell time and turn time per dock.

Playbooks

Automatic handling of occupancy, missing documents, missed time windows and critical exceptions.

Exception engine

Escalates to Control Tower the exceptions the playbook can't solve.

REST endpoints

Endpoints grouped under /api/v1/yard/.

EndpointMethods
/api/v1/yard/dock-schedulesGET, POST
/api/v1/yard/vehiclesGET
/api/v1/yard/check-inPOST
/api/v1/yard/check-outPOST
/api/v1/yard/call-to-dockPOST

Convention: endpoints in kebab-case, versioned under /api/v1/, and collections in camelCase.

KPIs the YMS delivers

Dwell time

Average time a vehicle stays in the yard between check-in and check-out.

Turn time

Time between call-to-dock and vehicle release; the main driver of dock productivity.

The YMS as the link between WMS and TMS

The yard costs more than it seems

Every minute of waiting in the yard means demurrage, daily charges, contractual penalties and lower OTIF. The NexLog OS YMS works on that link: Dock Appointment (dockSchedules) and Yard Vehicle (yardVehicles) share the same MDM as the WMS (waves) and the TMS (routing).

As a result, scheduling becomes a decision informed by real capacity, not by a spreadsheet.

Self-service at the gate

The kiosk turns check-in into self-service: the driver enters their CPF and CNH, registers the CT-e and NF-e, takes a photo and accepts the LGPD consent form. Call-to-dock notifies the driver when the dock is free and directs them there automatically.

Playbooks, exceptions and Control Tower

Unexpected occupancy, missed time windows, incomplete documents and vehicles without an appointment are handled by configurable playbooks that try to resolve them without human intervention.

Whatever slips through goes to the Control Tower exception engine, traceable by the same correlationId as the corresponding shipment and order. That is what makes the YMS a first-class module of the supply chain operating system.

Frequently asked questions

Do I need IoT/RFID in the yard?

Optional. The YMS works with manual check-in at the kiosk; IoT and RFID speed up real-time location.

What about drivers without an appointment?

They are handled by the exception engine and can be fitted into a free window or rescheduled.

Scheduling by vehicle type?

Yes. Docks can be restricted by type (rigid truck, semi-trailer, VUC), height, length and compatibility with hazardous loads.

Does the kiosk work offline?

Partially. It syncs as soon as the connection returns, preserving the timestamps.

Does it integrate with WMS and TMS?

Yes. The same shipment and the same order know the corresponding dock and wave.

What about LGPD and biometrics?

Consent flows are built in; biometrics are optional, with a dedicated consent form.

Ready to cut dwell time?

Thirty minutes with a CCX engineer, at no cost, to integrate the yard, gatehouse and docks with the same MDM as the WMS and TMS.