Skip to main content
CONPDS TRACKER

On-Premise Container OCR Infrastructure

The evidence source for every container that passes a camera. GPU-powered reads of ISO 6346 container numbers from any IP camera — published as open JSON via MQTT. The same engine that powers ConPDS Autogate, and a standalone feed for any RTSP camera writing into the same container-linked record chain Checker writes to. Your hardware. Your data. Your integration.
Capture RTSP cameras per lane or zone
Process On-device deep-learning OCR
Publish Open JSON via MQTT
On-premise · your GPU
No DMS lock-in
Powers Autogate
Read real customer outcomes →
No obligations — reply within 1 business day

What Is Container OCR Infrastructure?

On-premise container OCR infrastructure is the evidence source underneath the operation: it connects to IP camera streams, uses computer vision to detect and read ISO 6346 container numbers as containers pass, and publishes a container-linked record (number, camera, lane, timestamp, confidence) as structured JSON. Downstream systems — gate logic, the depot management system, the operational evidence layer — can act on the same structured record without retyping the container number. The same OCR engine powers ConPDS Autogate at the gate AND stands alone as an evidence source for any RTSP camera in the yard, the workshop, or the rail/Ro-Ro lane.
Container Depots Intermodal Terminals Ro-Ro Terminals Warehouses Port Facilities
ConPDS Tracker
Capture Multiple RTSP camera streams, grouped per lane, zone, or checkpoint
→
Process Motion-triggered deep-learning OCR powered by ConPDS Core engine
→
Publish Open JSON via MQTT — per camera or per camera group
→
Customer Integration
Subscribe Custom code subscribes to the MQTT broker and receives OCR data from Tracker
→
Process Data processed according to your custom algorithm and business rules
→
Act Update your systems — gate logic, DMS, TOS, WMS, API, database, or any platform
ISO 6346 / BIC / ISO TankHorizontal & vertical, single- & double-line
As low as about 30msUnder suitable deployment conditions
No DMS dependencyWorks with any management system
On-premiseYour hardware, your network, your data

Where Manual Container Number Capture Quietly Costs Money

200+ moves / day
Each movement manually read, typed, and verified by a gate officer — throughput ceiling tied to staff availability
→
1 typo
A single transposition error creates a data mismatch that may not surface until a dispute is raised weeks later
→
Weeks later
Documentation mismatch discovered during a claim — no verifiable record to resolve the dispute

Without Automated Container Monitoring

Container numbers entered manually — transcription errors create downstream data mismatches
Gate officer required for every movement — throughput ceiling tied to staff availability
No timestamped record of which truck carried which container at which moment
Data lives in paper logs or spreadsheets — not available to downstream systems in real time
Integration with DMS requires manual re-entry — doubling the error risk

With ConPDS Tracker

Container numbers read automatically from camera streams — OCR with validation at the point of recognition
Under suitable deployment conditions, up to 99% OCR accuracy with processing as low as about 30ms
Every read timestamped and attributed to camera and lane — full movement audit trail
Results available to any MQTT subscriber immediately — DMS, custom logic, database, alerts
Gate officer freed from data entry — focus shifts to exception handling

✗ 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

01
Camera Connection
Tracker connects to IP cameras via RTSP
02
Motion Detection
Vehicle presence triggers OCR processing
03
Container OCR
Container numbers read in real time
04
Result Selection
Best read selected across frames and camera angles
05
JSON → MQTT
Result published — any subscriber acts on the data
Steps 01–02 — Trigger

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.

Steps 03–04 — Read

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. Under suitable deployment conditions, Tracker can achieve up to 99% accuracy with processing as low as about 30ms.

Step 05 — Output

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.

Capability 01 — Identification

Container Number Recognition

Reads validated container numbers — including BIC-prefixed and ISO Tank formats — horizontal and vertical orientation, single- and double-line
ISO container type recognition: size and type codes validated against the container number standard
Rear camera speed up to 10kph · side camera up to 7kph · angles up to 30° horizontal and vertical
Capability 02 — Output

Open JSON Output via MQTT — Build Any Integration

Every read published as structured JSON to the MQTT broker — no proprietary format, no vendor lock-in
Published MQTT, REST, and database examples are for inspiration — production integrations are built to fit your exact needs
See the full Integration Guide →
Capability 03 — Infrastructure

On-Premise, Any Camera, Any Facility Size

Runs on your hardware — Windows 10+ / Linux Ubuntu 20+ — OCR and video stay on-premise; optional Checker cloud photo send when configured
GPU-accelerated processing scales with hardware as camera count grows
See full Technical Specifications →

What Container Operations Gain With Tracker Infrastructure

Up to 99% OCR Accuracy Under Suitable Deployment Conditions

Deep-learning ConPDS Core OCR with motion and object detection; results depend on camera placement, lighting, marking condition, angle, and vehicle speed.

Processing as Low as About 30ms Under Suitable Deployment Conditions

Under suitable deployment conditions, processing from camera frame to JSON result can be as low as about 30ms.

Works With Existing Cameras

Any IP camera supporting RTSP streams — no proprietary hardware required, no ripping out existing infrastructure. Axis, Hikvision, Bosch, Vivotek and others.

No Management System Dependency

Works with any DMS, TOS, or WMS — or none at all. Published MQTT, REST, and database paths are illustrative; production integrations are built to your exact needs.

Fully On-Premise

OCR and video processing run on your hardware. Tracker can be configured to automatically send photos to Checker cloud when you want that archive path. You own the data and control retention, access, and compliance.

Centralised OCR Engine Updates

Update Tracker once — every connected camera stream benefits instantly. No manual firmware upload per camera, no per-device reconfiguration. Cameras with built-in OCR require individual updates; Tracker doesn't.

Motion-Triggered Processing

OCR runs only when a vehicle is detected — not continuously across all streams. GPU load stays proportional to actual traffic, reducing hardware requirements and energy use at facilities with variable throughput.

Concurrent Multi-Stream Processing

One Tracker installation processes multiple camera streams simultaneously — 5, 20, or 50+ cameras handled by a single OCR engine. No separate system per camera, no per-stream licensing complexity.

Scales to Any Facility

From a single gate camera at a small depot to multi-lane, multi-site terminal deployments — same software platform, same open output format, same central update model throughout.

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.

Open Platform · Any DMS · Any Workflow

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.

See the Integration Guide →
Pre-Built Solution · DepotMaster Depots Only

ConPDS Autogate — Ready to Deploy

Complete gate automation programme built on Tracker — ConPDS provides automation electronics, software, integration, commissioning, and support; your contractor builds site infrastructure to ConPDS specifications. Requires DepotMaster.

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 automation programme built on Tracker for DepotMaster depots — ConPDS owns the automation outcome; your contractor builds site infrastructure to ConPDS specifications. Each product works independently; together they cover the full container lifecycle on a single container-linked record chain.

ConPDS Tracker

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.

ConPDS Checker

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.
ConPDS Autogate

Gate Operations Infrastructure

Complete gate automation programme for DepotMaster depots — ConPDS provides automation electronics, software, integration, commissioning, and support. Tracker's OCR output becomes barrier decisions and self-service driver interaction; gate evidence is stored in DepotMaster.

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

Edge / On-Premise Processing On-Premise OCR Customer Data Ownership Open JSON / MQTT Output Any IP Camera Compatible No Management System Dependency Windows & Linux Support
All processing runs on-premise on your GPU hardware — container numbers and video frames never leave your network
You own the data ConPDS Tracker produces — data retention, access controls, and GDPR obligations are your responsibility and under your control
OCR results published via MQTT in standard JSON — integrates with any DMS, TOS, WMS, or logistics platform
Full architecture, deployment, and authentication details in the Technical Specifications. Integration paths and output formats in the Integration Guide.

Technical Specifications

Performance Highlights
Accuracy
Up to 99% under suitable deployment conditions
Processing time
As low as about 30ms under suitable deployment conditions
Standards
ISO 6346 · BIC · ISO Tank
Camera protocol
RTSP / RTSP-S
Platform Requirements
OS
Windows 10/2016+ · Linux Ubuntu/Debian 20+
GPU
Nvidia CUDA · Intel HD
RAM
Min. 8GB (16GB+ recommended)
Architecture
On-premise, GPU-accelerated
See the full Technical Specifications — complete OCR performance benchmarks, camera requirements, hardware specifications, authentication methods, and architecture details.

Frequently Asked Questions — ConPDS Tracker

What is ConPDS Tracker and what does it do? ▼
ConPDS Tracker is an on-premise container number OCR engine. It connects simultaneously to multiple IP camera RTSP streams, uses deep-learning recognition to read validated container numbers — including BIC-prefixed and ISO Tank formats — in real time, and publishes results as JSON via MQTT — per camera or per camera group. Any system that can subscribe to an MQTT topic can consume and act on that data: a DMS, TOS, WMS, a custom integration, or a direct database write. No management-system dependency and no proprietary lock-in. It can also be configured to send photos to Checker cloud.
Does ConPDS Tracker require DepotMaster or any specific depot management system? ▼
No. ConPDS Tracker is completely independent of any depot management system. It publishes container number data in open JSON format via MQTT — any software that can subscribe to MQTT can integrate with it. If your facility runs DepotMaster and you want a complete gate automation programme, ConPDS Autogate is the pre-built path built on Tracker.
What camera hardware does ConPDS Tracker work with? ▼
ConPDS Tracker works with any IP camera that outputs an RTSP or RTSP-S stream using H.264, H.265, or HEVC encoding — minimum resolution 1280×960 at 12fps. Cameras from manufacturers including Axis, Hikvision, Bosch, and Vivotek are compatible under these requirements, as is any other vendor whose cameras support standard RTSP output. In most cases, existing on-site cameras are compatible without replacement. ConPDS provides onsite consultation on camera placement, angles, and configuration to ensure optimal read accuracy for your specific installation.
Who owns the data ConPDS Tracker produces? ▼
You do. ConPDS Tracker runs on your hardware on your network — OCR results and video processing stay on your infrastructure. It can be configured to automatically send photos to Checker cloud when you want that archive path. You control data retention periods, access rights, and GDPR obligations for your installation.
What is the accuracy and speed of ConPDS Tracker's OCR? ▼
Under suitable deployment conditions, ConPDS Tracker can achieve up to 99% container number recognition accuracy using the ConPDS Core OCR engine with motion detection and object detection, with processing as low as about 30ms from frame capture to JSON result. Rear camera reads support vehicles moving up to 10kph; side camera reads support up to 7kph.
Can I build my own integration on top of ConPDS Tracker? ▼
Yes — that is the design intent. Every OCR result is published as standard JSON to an MQTT broker on topics per camera or camera group. Published MQTT, REST, and database examples are for inspiration; production integrations with external systems are built to fit the customer's exact needs. ConPDS can help design and build that engagement on top of Tracker's output data.
What is ConPDS Autogate and how does it relate to Tracker? ▼
ConPDS Autogate is the complete gate automation programme built on Tracker — Autogate + Tracker + DepotMaster. ConPDS provides automation electronics, software, integration, commissioning, and ongoing support; your contractor builds gate, kiosk, power, and network infrastructure to ConPDS specifications. Tracker does the OCR; Autogate turns those results into barrier decisions and self-service driver interaction. Requires DepotMaster.

Related Resources

Tracker Technical Specifications

Complete OCR performance benchmarks, camera requirements, hardware specifications, authentication methods, and on-premise architecture details.

see full technical specifications →

Tracker Integration Guide

MQTT/JSON output format, three integration paths (MQTT, REST API, direct database), and the Open Platform vs Autogate decision.

see integration options →

Container Operational Evidence Platform

The platform category Tracker feeds — camera OCR events, mobile capture, and gate transactions tied into one container-linked evidence chain.

explore the operational evidence platform →

What Is Container Operational Evidence?

How validated container records become defensible evidence across inspection, repair, gate, wash, and audit workflows.

read the category definition →

ConPDS Autogate — Complete Gate Automation

Complete gate automation programme — ConPDS provides automation electronics, software, integration, commissioning, and support; your contractor builds site infrastructure to ConPDS specifications. Requires DepotMaster.

see how ConPDS Autogate turns Tracker into a complete gate solution →

Container Inspection Evidence Layer

ConPDS Checker — the mobile evidence layer for inspection, repair, lease return, and PTI. Container-linked records (photo, video, audio) tied to the same container number Tracker reads at the gate.

explore the container inspection evidence layer →

How to Maintain an Audit Trail for Container Inspections

Timestamped OCR reads, gate events, and photo records — how a structured audit trail links every container movement to retrievable evidence.

read the container inspection audit trail guide →
Customers across Europe, Africa, Australia & the Middle East
Alisan Den Hartogh Aktas APM Terminals Autamarocchi CCIS Contrepair Cut Coal Eimskip Eurobox Gruppospinelli HRS Isotank Central James Group International Medlog Namops Logistics Porpet QTerminals Kramer Rotterdam Rhespa Europe SDT Marine & Cargo Washmed Werra Kombi Terminal Zuidnatie Zwennis Containers
Read real customer outcomes →

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.

✗ Without Automated OCR
✗
Transcription errors enter your DMSA single transposed digit creates a mismatch that may not surface until a dispute is raised weeks later — with no camera record to correct it.
✗
Gate throughput capped by staffEvery movement requires a gate officer to read, type, and verify — throughput ceiling rises and falls with headcount, not container volume.
✗
No timestamped movement recordThe only evidence of a container movement is a manual log entry — which can be wrong, incomplete, or missing entirely.
✗
Data reaches systems late and incorrectlyManual entry introduces lag and transcription errors before data reaches your DMS, TOS, or WMS.
✓ With ConPDS Tracker
✓
OCR reads published at sourceContainer numbers read directly from camera frames — no human transcription in the loop. Under suitable deployment conditions, accuracy can reach up to 99%; reads are timestamped at capture.
✓
Gate throughput independent of headcountTracker processes every movement automatically — gate officer attention freed for exception handling, not data entry.
✓
Every read timestamped and camera-attributedContainer number, camera, camera group, and timestamp logged for every movement — unambiguous, unedited, retrievable.
✓
Structured JSON processing as low as about 30msUnder suitable deployment conditions, Tracker can process a read in as little as about 30ms before publishing the result to MQTT.

Two paths forward — pick the one that fits your operation:

Open Platform

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.

DepotMaster Depots

ConPDS Autogate — Ready to Deploy

Complete gate automation programme built on Tracker — ConPDS provides automation electronics, software, integration, commissioning, and support. Requires DepotMaster.

See ConPDS Autogate →
No obligations — reply within 1 business day