CATEGORY DEFINITION
Container Inspection Infrastructure
Container inspection infrastructure is the system underneath the inspection workflow: mobile capture, validated container number recognition, audit trails, retention policy, integration output, and retrieval. ConPDS gives depots, terminals, repair workshops, wash stations, and gates one evidence infrastructure layer instead of disconnected apps, folders, cameras, and chat threads.
Built for operators who need inspection records to survive disputes, audits, repair claims, lease returns, gate exceptions, and multi-site standardisation.
No obligations — reply within 1 business day
What Counts as Inspection Infrastructure?
Inspection infrastructure is what makes an inspection record operationally reliable after the field worker taps capture. It validates the container number, keeps the record tied to the correct workflow, stores metadata, enforces access control, distributes the output, and makes the record retrievable months or years later.
ConPDS implements that infrastructure through
Checker for mobile capture,
Tracker for on-premise OCR, and
Autogate for gate events. The same evidence logic supports depot inspection, repair, reefer PTI, wash, lease return, stuffing, gate-in, gate-out, and audit workflows.
Validated container number recognition at capture or camera read
Offline mobile workflows for yards, workshops, and wash bays with unreliable signal
Capture metadata, access history, distribution events, and retention policy attached to the record
Outputs for DMS, M&R, shipping-line, email, FTP/SFTP, REST API, MQTT, and guest portal workflows
FACILITY CONTEXT
Where Inspection Infrastructure Lives
The same evidence layer follows the container through the physical operation: gate lane, yard, workshop, wash station, and the systems that need the record later.
sensor_door
Gate lane
Autogate and Tracker capture OCR reads, booking context, barrier events, and EIR-linked exceptions.
inventory_2
Yard and handover
Checker records condition, seal, pickup, return, and lease events while staff work around the container.
construction
Workshop / wash
Repair, PTI, wash, and before-after evidence stay attached to the same container record.
Shared evidence layer
container number
capture metadata
audit trail
integration output
INFRASTRUCTURE MAP
How the Inspection Stack Fits Together
Each ConPDS product can run independently, but the evidence value is strongest when mobile capture, camera OCR, and gate events feed the same validated record layer.
photo_camera
Checker
Mobile capture for inspection, repair, PTI, wash, and lease return.
videocam
Tracker
On-premise container number OCR from RTSP camera streams.
sensor_door
Autogate
Gate events linked to OCR reads, bookings, kiosks, and EIR context.
ConPDS evidence layer
Validate container number
Attach metadata
Log access
Apply retention
Operational Systems
DMS, M&R, shipping-line, API, FTP/SFTP, MQTT, and email workflows.
Evidence Retrieval
Search by container number, workflow, date, site, customer, or work order.
Audit Production
Produce records with capture context, distribution history, and access logs.
Why Inspection Infrastructure Matters
Inspection work is no longer only a field task. It now feeds repair authorisation, lease return disputes, off-hire claims, gate events, CSC and lessor audits, customer evidence requests, and operational reporting. A phone camera can take a picture; infrastructure makes the record defensible.
Without Infrastructure
Photos are captured but not reliably tied to the validated container number
Records depend on staff discipline, folder naming, and chat history
OCR data, photos, work orders, and gate events live in separate systems
Audit and dispute retrieval becomes a manual reconstruction project
With ConPDS
Every record is container-linked before it enters the archive
Evidence follows a standard workflow across sites, shifts, and facility types
Mobile, OCR, gate, and integration events become one evidence chain
Records are searchable, audit-logged, and producible when challenged
The Inspection Infrastructure Stack
MOBILE CAPTURE
Inspection, Repair, PTI, Wash, and Lease Return
Checker gives field teams a structured capture workflow on standard smartphones. Photos, video, audio, annotations, timestamps, GPS, user identity, and validated container numbers become a retrievable evidence record.
OCR INFRASTRUCTURE
Container Number Recognition From Cameras
Tracker reads container numbers from RTSP camera streams on customer-controlled GPU hardware and publishes open JSON via MQTT. It gives gates, depots, and customer systems a container recognition layer without cloud dependency.
GATE EVIDENCE
Automated Gate Events With EIR Context
Autogate links OCR reads, kiosk activity, reservation matching, barrier events, lift-operator job cards, and gate-out confirmation into the same operational evidence model.
INTEGRATION OUTPUT
Evidence Where the Operation Already Works
Records can be sent into AEMS, DepotMaster, EOS, IMARS, OVMR, FIS, custom APIs, FTP/SFTP destinations, email workflows, and guest portals with distribution history logged.
Where the Infrastructure Is Used
domain
Container Depots
Gate-in, repair, lease return, EIR, and yard evidence under one retrieval model.
ac_unit
Reefer Workshops
PTI and repair evidence with photo, video, audio, AEMS distribution, and technical record history.
local_car_wash
Wash Stations
Before-and-after proof of service linked to container number, timestamp, and invoice review.
sensor_door
Gate Operations
OCR validation, booking match, kiosk flow, and EIR-linked event records.
Inspection Infrastructure Must Be Defensible Infrastructure
A useful inspection record must be valid when a counterparty challenges it. That means the infrastructure must carry container association, metadata, access control, retention, distribution history, and retrieval together.
ISO 6346 validation
Offline capture
Audit logging
Role-based access
Retention control
DMS integration
MQTT / REST output
Container Inspection Infrastructure FAQ
What is container inspection infrastructure? ▲
It is the operational layer that creates, validates, retains, distributes, and retrieves inspection records across container workflows. It includes mobile capture, OCR, audit trails, integrations, and retrieval rather than just a capture app.
Does this replace a depot management system? ▲
No. ConPDS sits under and around the DMS as the evidence layer. It pushes validated records into existing systems and keeps the evidence chain available when the DMS, customer, auditor, or shipping line needs it.
Can it be deployed one layer at a time? ▲
Yes. Many operators start with Checker for mobile inspection evidence, add Tracker for OCR infrastructure, and later connect Autogate where gate automation becomes the next operational bottleneck.
Scope the inspection infrastructure your operation needs.
Tell us which inspection, OCR, gate, audit, and integration surfaces matter most. We will map the smallest ConPDS stack that turns those records into defensible operational evidence.
