CONPDS CHECKER

AEMS Documentation Integration: How to Connect Photo Documentation to Maersk AEMS

Q: Can ConPDS integrate with M&R systems beyond Maersk AEMS?

Yes. ConPDS supports integration with a broad range of M&R, DMS, and shipping line systems via REST API, FTP, SFTP, and email — including CMA-CGM, IMARS, MSC OVMR, Hapag FIS, Seaco, Triton, EOS, DepotMaster, and custom APIs. If your system is not yet supported, we will add the integration on request.

Manual photo exports after reefer PTI inspections create delays and documentation gaps. With a configured AEMS distribution rule, Checker can deliver the photo set immediately or after a configured delay and log every attempt.

Trusted by container depots and reefer technicians across Europe — from single-depot operators to large-scale terminal operators processing tens of thousands of photos monthly.

No obligations — reply within 1 business day

What Is AEMS Documentation Integration?

AEMS documentation integration is the configured connection between structured container inspection photo records and the Maersk AEMS Container Maintenance & Repair APIs. A tenant rule can deliver records immediately or after a configured delay, linked to the container and estimate, with every attempt logged.

ConPDS implements AEMS documentation integration through its API-based connection to Maersk's platform. Checker validates the container number with ISO 6346 check-digit verification; wrong recognition is flagged for retake or manual entry. After synchronization, a configured tenant rule can push the photo set to AEMS immediately or after a delay, with the attempt logged.

Photos captured in the field on the technician's existing smartphone — no specialist hardware

Container number validated via on-device OCR with ISO 6346 check-digit verification; wrong recognition flagged with retake or manual entry

Direct API connection to Maersk's AEMS platform — no intermediate steps

Works offline — after synchronization, a configured AEMS rule runs according to its immediate or delayed trigger

Every distribution event logged automatically — a continuous audit trail of what was sent, when, and to which system

Automatically retrieves open AEMS estimates for the container — if one pending-approval estimate exists, photos attach instantly; if multiple exist, the technician selects from a list in seconds

Why Manual AEMS Documentation Integration Fails Under Operational Conditions

A reefer depot processing 60 PTI events per day generates 300+ inspection images that must reach AEMS correctly — associated with the right container, in the right format, without delay. Without integration, every one of those images passes through a chain of manual steps where errors accumulate and documentation gaps become routine.

Manual Process Failures

Photos exported from WhatsApp threads, email attachments, and shared folders — no structured container linkage

Manual renaming required before upload — a single transposition makes a file permanently unfindable

AEMS upload completed hours or days after inspection — documentation is stale when it arrives

Inspection photos on personal devices — evidence disappears when a technician leaves

Operational Consequences

Warranty claims challenged because spare part serial number photos are missing or mislinked

Shipping line disputes extended because AEMS record and photo documentation are out of sync

No verifiable capture context — after a normal chat send, original camera metadata is not reliably available

No audit trail — the depot cannot prove what was sent, when, or to which system

With manual methods: a technician completes a reefer PTI, and photos may remain in a chat thread until someone exports and renames them. With AEMS documentation integration via ConPDS: the photo set is linked to the container number and can be delivered under a configured tenant rule, immediately or after a set delay, with each attempt logged.

How AEMS Documentation Integration Works in Practice

Capture

Field photo intake

Validate

ISO 6346 OCR check

Sync

Auto-upload on connect

Attach to Estimate

Auto or user-select

STEP 01

Capture Inspection Photos in the Field

The technician uses ConPDS Checker on their existing smartphone. On-device OCR with ISO 6346 check-digit verification reads the container number at capture; wrong recognition is flagged with retake or manual entry. Photos, video clips (up to 30 seconds), and voice annotations can all be captured per inspection event.

STEP 02

Container Number Validated at Capture

Checker verifies the ISO 6346 check digit at capture. Wrong recognition is flagged; if the number is not recognized, the technician can retake the photo or type the container number manually, reducing container-linking errors.

STEP 03

Automatic Sync to the ConPDS Platform

When connectivity is available, photos sync automatically from the device to the ConPDS central platform. The full photo set is immediately visible in the web dashboard — office teams see exactly what was captured in the field, in real time, without chasing the technician for files.

STEP 04

Automatic Estimate Retrieval and Photo Attachment in AEMS

ConPDS connects to Maersk's AEMS platform and retrieves the open estimates for that container with status pending approval — then attaches the photo set without any manual selection required.

Smart Attach Logic

One open estimate — photos attach automatically. The technician does nothing further.

Multiple open estimates — a list of estimate numbers is shown in the app. The technician taps the correct one and attachment completes in a single step.

Every attachment event is logged in the audit trail — estimate number, container, timestamp, and confirmation — creating a continuous, searchable record of what was sent and when.

In Practice Illustrative sequence: a reefer workshop completes a PTI, the user confirms the relevant estimate when selection is needed, and the configured AEMS rule delivers the photo set immediately or after its set delay. The delivery attempt is logged; no fixed one-minute timing is implied.

Container Inspection Workflows That Require AEMS-Integrated Documentation

AEMS documentation integration supports the full range of reefer inspection and repair events. Each workflow type generates a distinct photo set — all delivered to AEMS via the same structured, automated Maintenance & Repair (M&R) workflow. In each of these workflows, delayed or mislinked photo documentation directly increases the likelihood of warranty disputes, estimate rejection, or payment delays.

Pre-Trip Inspection (PTI) Documentation

Exterior condition, visible defects, and unit identification can be delivered to AEMS when a tenant rule is configured, immediately or after a configured delay.

Defect and Damage Documentation

Specific faults identified during PTI — location, nature, and extent of each defect photographed in detail and linked to the container and repair estimate.

Spare Part Serial Number Capture

Replaced parts photographed before and after replacement. Serial numbers captured and stored against the container record, creating a traceable warranty claim trail linked to the specific unit.

Post-Repair Condition Confirmation

The unit photographed after repair to confirm it has been returned to operational standard. Delivered to AEMS as a complete before-and-after record.

Configured AEMS Distribution

For configured event types, a tenant rule can deliver photos immediately or after a set delay. Every attempt is logged with success or failure.

Multi-System Distribution

Beyond AEMS, the same photo set can be distributed simultaneously to IMARS, MSC OVMR, Hapag FIS, leasing company portals, or your own DMS — one capture event, multiple destinations.

Estimate-Linked Photo Attachment

ConPDS retrieves open AEMS estimates with status pending approval for the container. If one exists, photos can attach automatically. If several exist, the technician selects from a numbered list, reducing the risk of attaching photos to the wrong estimate.

What AEMS Documentation Integration Delivers for Your Operation

Rule-Based Delivery Timing

A configured tenant rule can deliver photos to AEMS immediately or after a set delay, with every attempt logged.

Accurate Container Linkage

On-device OCR verifies the ISO 6346 check digit; wrong recognition is flagged for retake or manual entry, reducing mislinked documentation.

Fully Offline-Capable

Core capture functions run on-device. Photos synchronize when connectivity returns, after which any configured AEMS rule runs according to its immediate or delayed trigger.

Warranty Claim Traceability

Spare part serial numbers linked to the container record create a defensible warranty claim trail. Claims tied to structured AEMS-delivered photo evidence are resolved faster and disputed less frequently.

Complete Audit Trail

Every API push to AEMS is logged — container number, photo set, timestamp, delivery confirmation. The depot can demonstrate exactly what was sent and when, at any point in the future.

No Disruption to Existing Systems

ConPDS adds the photo documentation layer your current AEMS workflow is missing — without replacing or disrupting the repair management processes already in place.

Security, Compliance, and Data Governance

Privacy-by-design 256-bit HTTPS Encryption Full Audit Trail Role-Based Access Control Configurable Retention Periods On-Device Encryption

Photos are stored encrypted on the device until upload, and a local copy is retained for about seven days after successful upload. HTTPS encrypted transport and role-based access apply to the central archive. Checker mobile capture retains the timestamp and can include device-recorded location when enabled and available; location is context, not independent proof of presence. Distribution attempts and later record changes are logged.

Frequently Asked Questions

What is AEMS documentation integration? ▲

AEMS documentation integration connects structured container inspection photo records to the Maersk AEMS Container Maintenance & Repair APIs. When the tenant rule is configured, delivery can trigger immediately or after a configured delay, and every attempt is logged with success or failure.

Does integrating photo documentation with AEMS replace the system itself? ▲

No. ConPDS adds the structured photo evidence layer that AEMS and similar M&R systems do not natively provide. Container records, repair workflows, and cost approvals remain in AEMS; ConPDS delivers the inspection photos that support them.

Does ConPDS work offline during AEMS-integrated reefer inspections? ▲

Yes. Checker OCR and capture run offline. Photos are stored encrypted on the device until upload and synchronize when connectivity returns. Any configured AEMS distribution rule then runs according to its immediate or delayed trigger, with the attempt logged.

Is the photo data shared with AEMS secure and privacy-by-design? ▲

Yes. Photos are encrypted on-device and transmitted via 256-bit HTTPS. All distribution events — including API pushes to AEMS — are logged automatically in a continuous audit trail with full traceability. ConPDS supports GDPR-governed workflows throughout.

Which Maersk AEMS API workflow does ConPDS connect to? ▲

ConPDS integrates with the Maersk AEMS Container Maintenance & Repair APIs. After a PTI or repair event, ConPDS retrieves all open estimates for the container with status pending approval. If one estimate is open, photos are attached automatically. If multiple estimates are open, the technician selects from a list in the app — the correct estimate is confirmed in one tap, with no manual AEMS navigation required.

Can ConPDS integrate with M&R systems beyond Maersk AEMS? ▲

Yes. ConPDS supports integration with CMA-CGM, IMARS, MSC OVMR, Hapag FIS, Seaco, Triton, EOS, DepotMaster, and custom APIs via REST, FTP, SFTP, and email. If your system is not yet supported, we will add the integration on request. The same structured photo documentation workflow that serves AEMS integration can distribute simultaneously to multiple systems from a single capture event.

How long does AEMS documentation integration take to implement? ▲

There is no public fixed implementation-time band. ConPDS scopes AEMS setup after reviewing tenant requirements, credentials, API access, and test-environment availability.

Ready to Eliminate Manual AEMS Uploads?

ConPDS can connect structured PTI records to AEMS under a configured tenant rule, with delivery attempts logged from the Checker archive to the receiving system.

What Happens Without AEMS Documentation Integration

✗ Warranty claims denied or delayed — spare part serial number photos exist but are not linked to the correct container record in AEMS, making the claim unverifiable.

✗ Shipping line review windows missed — photos arrive in AEMS hours or days after inspection, after the window for dispute-free approval has passed.

✗ No delivery proof — the depot cannot demonstrate that documentation was sent to AEMS, when it was sent, or what it contained — making any dispute about documentation receipt impossible to resolve.

✗ Inspection history lost on personnel change — PTI photos stored in WhatsApp threads, email attachments, and shared folders become inaccessible when a technician leaves, taking months of AEMS-relevant documentation with them.

✗ Offline gaps leave inspections undocumented — without offline capability, poor signal in port yards or remote depot areas means inspections are completed but photos never captured or delivered to AEMS.

With ConPDS, every PTI event — regardless of connectivity, technician, or location — generates a structured, container-linked photo set delivered straight into Maersk's AEMS platform with a complete audit trail from capture to confirmation.