CONPDS AUTOGATE
What Makes Up an Automated Container Gate System?
A complete gate automation programme combines ConPDS-supplied lane electronics and software with customer-built site infrastructure — barrier, kiosk totem, power, network, and GPU server — all scoped to ConPDS specifications. Requires DepotMaster as the reservation system and operational source of truth.
ConPDS owns the automation outcome · Customer owns site infrastructure · DepotMaster required
Lane Components Per Gate
Each automated lane combines ConPDS-supplied automation electronics with customer-built site infrastructure — all scoped to ConPDS specifications during site assessment. Exact bill of materials can vary by design. See the subscription model for the full supply split.
ConPDS-supplied lane electronics
IMAGE CAPTURE
LPR Camera
Dedicated camera for automatic licence plate recognition
Mounted on barrier structure or separate pole with clear front-plate view
IMAGE CAPTURE
Container OCR Cameras (×5)
High-resolution cameras for container number OCR and contextual views
Two cameras on each side, one overhead — five per lane
NETWORK
Industrial PoE Switch
Powers and connects cameras, kiosk devices, and barrier-control interface
Industrial-grade with SFP modules included
GATE CONTROL
Barrier-Control Interface
DIN-mounted network relay for controlled open signals
Fully integrated with ConPDS GateOperator logic
DRIVER INTERACTION
Kiosk Computing Device
Industrial PoE-powered compute module — ConPDS-supplied
Runs the ConPDS kiosk application for gate-in and gate-out flows inside the customer-built totem cabinet
Customer-built site infrastructure
DRIVER INTERACTION
Kiosk Totem Cabinet
Outdoor enclosure with touchscreen, QR scanner, and intercom — built by the customer's contractor
Houses the ConPDS-supplied kiosk computing device
GATE CONTROL
Motorised Barrier & Safety Sensors
Motorised barrier controllable via the ConPDS-supplied relay interface — customer-supplied
Optical safety sensors and ground loops required for safe vehicle detection
System-Level Components — Not at the Gate
These components are required for the Autogate to operate but are not physically mounted at the gate lane.
01
Central GPU Server
Runs the OCR engine, event analytics, video acquisition, workflow logic, and DepotMaster integration. Customer-supplied to ConPDS specifications. Dedicated hardware is preferred; supported virtualised deployments can be used where suitable GPU access is available.
02
Kiosk Monitoring PC
Operator workstation with two large displays for live gate supervision, camera feeds, kiosk states, and manual exception handling. Customer-supplied; ConPDS provides the monitoring software.
A two-gate installation typically runs 12 cameras (6 per lane) — the Central GPU Server must be dimensioned to support the total camera count across all active gates.
Central GPU Server — Recommended Specifications
Video storage: If the VMS is hosted on the same machine, an additional 3 × 4 TB SATA/SCSI HDD (RAID 5) is recommended. When the VMS runs on a separate machine, this storage is not required.
Software Components and Microservices Deployed
All software is installed and configured during the one-time implementation project, then maintained under the subscription. Remote deployment begins after site infrastructure validation; on-site commissioning and go-live are part of the project scope.
OCR & Gate Processing
OCR ENGINE
ConPDS Tracker
Video analytics, OCR engine, and result publisher
Container number and licence plate recognition in real time
WORKFLOW
GateOperator Backend
Orchestrates gate-in and gate-out event sequencing
Triggers barrier decisions on DepotMaster match confirmation
Communication & Monitoring
MESSAGING
MQTT Broker
Message Queuing Telemetry Transport for real-time event distribution
Connects OCR results to gate logic and monitoring interfaces
DIAGNOSTICS
Remote Monitoring & Health Watchdog
Remote event logger and centralised log viewer
System health watchdog with configuration backup and restore
Kiosk & Video Management
DRIVER INTERFACE
Kiosk Totem Application
Gate-in and gate-out driver workflows on the touchscreen
VNC supervision for remote kiosk screen monitoring
VIDEO
Vivotek VSS Integration
Video Management System with ConPDS API integration
Camera stream mapping and recording management
Compliance, Security, and Data Handling
On-Premise Video Processing
Container Number Validation
Full Gate Event Audit Trail
Local Image Copy Can Be Retained On-Premise
Secure Transmission to DepotMaster
Yard Capacity Control Where Configured
OCR and video processing operate locally and do not depend on internet connectivity. Standard automated gate transactions require connectivity to DepotMaster for booking validation and confirmation. Raw camera footage is analysed on-site before required booking and event data is exchanged.
Required booking and event data — including captured images where the workflow needs them — are exchanged securely with DepotMaster's SaaS servers via REST API. The system can also retain a local image copy on-premise. Data does leave the site, but only to DepotMaster's secured servers.
Data security, access control, and data-protection obligations for stored data are governed by DepotMaster's infrastructure and data processing agreements — not by ConPDS Autogate directly. Depots should confirm data handling obligations with their DepotMaster agreement.
Every gate event — match, mismatch, manual override, and driver acceptance — is logged in a continuous, timestamped audit trail, accessible via DepotMaster and retrievable on demand for operational review or dispute resolution.
Where configured, the system supports a maximum number of trucks permitted inside the yard simultaneously — when the limit is reached, the kiosk displays a clear message to the driver and the barrier stays closed. Once a truck exits and capacity clears, the barrier opens automatically and the driver is notified on the kiosk to proceed.
System Integrations and Deployment Model
Integration Flexibility. DepotMaster's REST API is the reservation system of record today — Autogate validates Tracker results against DepotMaster reservations and keeps DepotMaster as the operational source of truth. MQTT messaging and JSON outputs are also available for third-party consumers that need gate event data (for example a TOS, WMS, or logistics platform). Other DMS targets require project-specific design.
DepotMaster · REST API
MQTT output
JSON output
Vivotek VSS · API
ISO 6346 check-digit validation
LPR OCR microservice
Container OCR microservice
Gate Cameras
Container OCR + licence plate capture
Video
ConPDS Tracker
GPU processing on-premise, barrier decision, kiosk coordination
REST API
DepotMaster
Reservation matching, EIR records, SaaS
DepotMaster REST API
Reservation lookup, match/mismatch response, and barrier trigger all run through a single REST API connection to DepotMaster.
On-Premise Processing
OCR and video processing operate locally and do not depend on internet connectivity. Standard automated gate transactions require connectivity to DepotMaster for booking validation and confirmation.
Secure Data Transmission
Images and booking data transmitted to DepotMaster's SaaS servers via encrypted REST API. The system can retain a local image copy on-premise.
Open Output Formats
Gate event data is also available via MQTT and JSON outputs for third-party consumers such as a TOS, WMS, or logistics platform.
Integration is configured by ConPDS during site commissioning — typically without custom development work from the depot. Other DMS targets beyond DepotMaster require project-specific design.
Technical Frequently Asked Questions
How is data handled and transmitted — does it leave the site? ▼
OCR and video processing operate locally and do not depend on internet connectivity. Standard automated gate transactions require connectivity to DepotMaster for booking validation and confirmation. Required booking and event data are exchanged securely with DepotMaster's SaaS servers via REST API; the system can also retain a local image copy on-premise. Data does leave the site, but only to DepotMaster's secured servers. Data security, access control, and data-protection obligations for stored data are governed by DepotMaster's infrastructure and data processing agreements — depots should confirm their obligations under their DepotMaster agreement.
How are container numbers validated, and how are recognition errors handled? ▼
Captured container numbers are validated against ISO 6346 check-digit logic at the moment of capture — catching common OCR misreads such as character substitutions in dirty or damaged container numbering before the data reaches DepotMaster. When validation fails, the event is treated as a mismatch and routed through the standard exception flow: on-screen kiosk message, intercom, and office resolution with the decision logged in the audit trail. Tracker recognition performance under suitable conditions is described on the Tracker product pages; Autogate does not publish a separate recognition SLA.
Customers across Europe, Africa, Australia & the Middle East
See What Each Annual Fee Covers
The architecture determines what gets installed. The subscription model describes the recurring per-gate fee; the deployment phases describe the one-time project scope.
No obligations — reply within 1 business day