CATEGORY DEFINITION
Container Operational Evidence Platform
Container evidence infrastructure turns inspection, repair, wash, gate, lease-return, and compliance activity into a defensible record: container-linked, timestamped, retained, access-controlled, and retrievable on demand. ConPDS sits underneath Checker, Tracker, and Autogate — built for the disputes, audits, repair claims, and gate exceptions that informal documentation cannot survive.
Used by container depots, repair workshops, shipping-line operations, leasing-company workflows, and automated gates across Europe.
No obligations — reply within 1 business day
What Is an Operational Evidence Platform?
The platform captures the record of what happened to a container at the moment the operation happens — then keeps that record tied to the validated container number for as long as the business needs it. It is not a folder of pictures. It is the infrastructure that links media, metadata, user action, work context, distribution, retention, and retrieval into one defensible chain.
ConPDS implements this category across three evidence sources.
Checker captures mobile inspection, repair, PTI, and wash evidence.
Tracker reads container numbers from RTSP camera streams and publishes camera evidence as structured OCR events.
Autogate turns gate-in and gate-out into EIR-linked, audit-logged operational records. Together they create a platform layer that a DMS, shipping-line integration, auditor, or customer portal can rely on.
Container-linked from the first capture event — not renamed or matched manually afterward
Validated against the ISO 6346 container number standard before the record is accepted
Retained under role-based access, configurable retention, and EU-hosted GDPR-aligned infrastructure
Distributed to customers, agents, shipping-line systems, DMS platforms, FTP/SFTP destinations, email, API endpoints, and guest portals with every event logged
Retrieved by container number, work order, depot, date range, inspection type, gate event, or customer request
EVIDENCE LANES
Three Capture Sources, One Container Record
ConPDS turns mobile work, camera reads, and gate events into one validated operational record that downstream systems, auditors, and customers can rely on.
photo_camera
Mobile Capture
Inspection, repair, PTI, wash, lease return, and stuffing.
videocam
Camera OCR
Container number reads from gate, yard, and workflow cameras.
sensor_door
Gate Events
Bookings, barriers, EIR context, and exceptions.
Validated container record
MSCU 123456 7
media + metadata + user + timestamp + access log
hub
Integrations
DMS, M&R, API, FTP/SFTP, MQTT, email, and shipping-line flows.
policy
Audit
Retention, access control, distribution history, and review logs.
manage_search
Retrieval
Search by container number, date, workflow, work order, or customer.
Why This Category Exists
Container operations have become evidence-heavy. A repair charge needs before, during, and after records. A lessor audit needs condition history. A gate dispute needs an EIR-linked event trail. A wash certificate needs before-and-after proof. A GDPR or customer access request needs a trace of who saw what, when. Informal documentation was built for convenience; operational evidence has to survive challenge.
The Pressure on Operations
More disputes are decided by the quality of the evidence, not by the quality of the work performed
Shipping lines and leasing companies expect records to be produced quickly, not reconstructed manually
Multi-site operations need the same evidence standard across depots, teams, shifts, and subcontracted workflows
Repair, gate, audit, and wash workflows each create risk when records are missing, misfiled, or unverifiable
The Platform Response
Standardised capture rules replace individual filing habits and chat-thread discipline
Metadata preservation makes the record independently verifiable when challenged later
Retention and access policy move evidence control from personal devices to the operation
Audit-logged retrieval turns evidence production from a recovery project into an operational function
How Legacy Workflows Fail
Legacy workflows can still move images from one person to another. That is not the same as producing evidence. The difference becomes visible when a counterparty challenges the record.
chat
WhatsApp Threads
Fast in the moment, weak under challenge. Metadata is stripped, records are mixed with conversation, and retrieval depends on a phone, a person, and a thread still existing.
folder_shared
Shared Drives
Folders store files; they do not enforce container number validation, naming standards, distribution logs, or retention rules across teams and depots.
mail
Email Attachments
Email moves evidence out of the workflow. Attachments are resized, forwarded, renamed, and separated from the work order or container event that gives them meaning.
photo_camera
Camera-Only Capture
A camera creates an image. It does not prove which container it belongs to, which user captured it, which event it supports, who received it, or whether it was later retrieved.
What the Platform Produces
01
Capture
Mobile, camera, or gate event
02
Validate
ISO 6346-linked record
03
Retain
Policy-controlled evidence
04
Produce
Audit-logged retrieval
CONTAINER RECORD
Validated, Container-Linked Operational History
Every inspection, repair, wash, PTI, gate event, video note, audio note, and distribution event stays attached to the validated container number. The record is searchable chronologically and can be produced by container number instead of by memory, file name, or inbox archaeology.
METADATA
Timestamp, Location, User, Camera, and Context
Operational evidence is only defensible when the context survives. ConPDS preserves capture metadata and operational context so a counterparty can see when the record was created, where it came from, which workflow produced it, and who accessed or distributed it later.
DISTRIBUTION
Evidence Packages That Can Be Proven Sent and Received
Evidence can be sent by email, FTP, SFTP, REST API, shipping-line integration, DMS integration, or guest portal. Each access and distribution event becomes part of the same audit trail, reducing disputes about whether evidence was shared and when.
RETRIEVAL
On-Demand Production for Disputes and Audits
A disputed charge, lessor audit, customer request, or compliance review becomes a search task, not a reconstruction project. Operations teams can retrieve records in seconds and provide the evidence package with its audit context intact.
Where Checker, Tracker, and Autogate Fit
photo_camera
Checker — Mobile Evidence Source
Field teams capture inspection, repair, PTI, wash, lease-return, and stuffing records on smartphones, with offline operation and ISO 6346 validation.
videocam
Tracker — OCR Infrastructure
RTSP camera streams become structured OCR events: container number, camera, lane, timestamp, confidence, and downstream integration data.
sensor_door
Autogate — Gate Evidence Source
Automated gate-in and gate-out produce EIR-linked evidence as a by-product of correct gate operation: OCR, booking validation, barrier decision, and exception handling.
The product pages explain each evidence source in detail. This page defines the category they serve together: the operational evidence layer for container operations.
Evidence, Audit, and Retention Controls
ISO 6346 Validation
Continuous Audit Trail
Role-Based Access Control
Configurable Retention
GDPR-Aligned EU Hosting
Guest Portal Retrieval
Every capture event is tied to the container number and retained under the customer's evidence policy
Every view, export, and external distribution event is logged against a user, timestamp, and record
Retention periods can reflect repair-claim windows, lease-return obligations, audit cycles, and customer requirements
Guest portal access lets external parties retrieve evidence without exposing unrelated records
Category Leader Position
ConPDS is not a generic media tool adapted to container work. It is a specialised evidence platform built around the real records container operations must defend: ISO 6346-validated container histories, repair evidence, gate evidence, audit logs, distribution records, and workflow-specific integrations.
Frequently Asked Questions
What is an operational evidence platform for containers? ▲
It is the system that captures, validates, retains, distributes, and retrieves the defensible record of container operations. The record is linked to the validated container number and carries the metadata and audit trail needed to survive disputes, audits, repair claims, and gate exceptions.
Does it replace our depot management system? ▲
No. A DMS manages bookings, inventory, work orders, and operational state. The operational evidence platform captures the proof behind those operations and can integrate with the DMS, shipping-line systems, and customer workflows.
Which ConPDS products make up the platform? ▲
Checker captures mobile inspection and repair evidence. Tracker reads container numbers from cameras and publishes OCR evidence. Autogate automates gate workflows and creates EIR-linked gate evidence. They can run separately or together depending on the operation.
Why not use WhatsApp, email, or shared drives? ▲
Those tools can move images, but they do not enforce container number validation, metadata preservation, retention policy, access control, or distribution audit trails. They create weak records exactly when the operation needs defensible evidence.
Which teams use this platform? ▲
Depot operations, M&R managers, reefer workshops, wash stations, gate teams, shipping-line asset teams, leasing-company contacts, compliance leads, and customer-service teams all use the same container-linked record chain for different decisions.
Turn Container Operations Into Defensible Evidence
If your team can perform the work but cannot always prove what happened later, the operational risk is in the evidence chain. ConPDS helps container operators standardise capture, preserve metadata, govern retention, and retrieve the record when the disputed charge, lessor audit, customer request, or gate exception arrives.
