On-Premise Container OCR Infrastructure
The evidence source for every container that passes a camera — on-premise, GPU-powered, reading container numbers from any IP camera, and publishing container-linked reads in open JSON via MQTT. The OCR engine that powers ConPDS Autogate, and a standalone evidence source for any RTSP camera writing into the same container-linked record chain Checker writes to. Your hardware. Your data. Your integration.
What Is Container OCR Infrastructure?
Where Manual Container Number Capture Quietly Costs Money
Without Automated Container Monitoring
With ConPDS Tracker
✗ Before: Manual Container Number Entry
A damage dispute is raised three months after gate-out. The gate register shows a container number — but a transposition error means it does not match the container that actually departed. There is no camera evidence, no timestamp, and no way to reconstruct what happened. A disputed charge without defensible evidence becomes a direct operational cost.
✓ After: ConPDS Tracker
The same dispute is raised. Tracker's OCR log shows the exact container number read from the camera at the moment of movement, the camera and lane, and the timestamp. The record is human-untouched, container-linked, and produced on demand — defensible by default.
How ConPDS Tracker Container OCR Infrastructure Works
Motion-Driven Processing
Tracker monitors all connected camera streams continuously. Processing is triggered by motion detection — OCR runs only when a vehicle is present in the frame, keeping hardware load proportional to actual traffic volume.
OCR & Best-Result Selection
The ConPDS Core OCR engine reads validated container numbers — including BIC-prefixed and ISO Tank formats — across multiple frames and camera angles. Tracker selects the highest-confidence result — up to 99% accuracy at 30ms processing time.
Open JSON Output via MQTT
Every confirmed read is published as a JSON message to the MQTT broker — container number, camera ID, camera group, timestamp, and confidence score. Any subscribed system receives it instantly: your DMS, a custom integration, a database writer, or ConPDS Autogate.
Three Capabilities That Make Tracker Infrastructure, Not a Product
Tracker does not prescribe what happens after a container number is read. It produces a container-linked evidence record — accurate, structured, on-premise — and leaves the business logic entirely to the operation that owns the data.
Container Number Recognition
Open JSON Output via MQTT — Build Any Integration
On-Premise, Any Camera, Any Facility Size
What Container Operations Gain With Tracker Infrastructure
What Do You Want to Build on Tracker's OCR Output?
Tracker publishes container numbers as open JSON via MQTT — what happens next is your choice. Two paths: build your own integration on the Open Platform, or deploy ConPDS Autogate for full gate automation at DepotMaster depots.
Build Your Own Integration
Subscribe any system to the MQTT feed — your DMS, TOS, WMS, a custom webhook, or a direct database write. No ConPDS middleware required.
ConPDS Autogate — Ready to Deploy
Complete gate automation built on Tracker — cameras, kiosk totem, barrier, intercom, and full DepotMaster integration. Tracker's OCR output becomes barrier decisions and self-service driver interaction.
See ConPDS Autogate →The ConPDS Evidence Platform: Tracker · Checker · Autogate
Tracker is the OCR infrastructure — the evidence source for every container that passes a camera. Checker is the mobile evidence layer for inspection, repair, and lease return. Autogate is the complete gate installation built on Tracker for DepotMaster depots. All three write to the same container-linked record chain — one container number, one operational evidence record, across what the camera sees, what the technician captures, and what the office needs to govern.
Container OCR Infrastructure
On-premise container number OCR. Connects to any IP camera, reads container numbers via deep-learning recognition, and publishes container-linked reads as open JSON via MQTT. Independent of any DMS, TOS, or WMS. The evidence source that powers Autogate AND stands alone for any RTSP camera in the operation.
Mobile Inspection Evidence Layer
The mobile evidence layer for inspection, repair, lease return, and PTI — iOS and Android. Field technicians produce container-linked records (photo, video, audio) tied to the same ISO 6346 container number Tracker reads at the gate. One container, one chain of evidence.
Gate Operations Infrastructure
Complete automated gate built on Tracker — cameras, kiosk totem, barrier, intercom, and full DepotMaster integration. Tracker's container-linked reads become barrier decisions and self-service driver interaction; the EIR-as-evidence is a by-product of the gate running correctly. Designed for DepotMaster depots.
Tracker is the evidence source. Checker is the evidence layer for the work the camera cannot see. Autogate closes the loop at the physical gate. Each product works independently — and together they cover the full container lifecycle on a single container-linked record chain.
Architecture, Data Ownership & Integration
Technical Specifications
Frequently Asked Questions — ConPDS Tracker
Start Reading Container Numbers Automatically
Manual container number entry creates errors that compound downstream — wrong numbers in your DMS, mismatched records, and no camera evidence when disputes arise. ConPDS Tracker eliminates manual entry at the source.
Two paths forward — pick the one that fits your operation:
Build Your Own Integration
Deploy Tracker, subscribe to the MQTT feed, and build exactly the business logic your facility needs — any DMS, any workflow, any size.
ConPDS Autogate — Ready to Deploy
Complete gate automation with kiosk, barrier, and DepotMaster integration — built on Tracker, delivered as one system.
See ConPDS Autogate →