CONPDS CHECKER

Send inspection photos to Maersk AEMS with less manual work

Save your office team the work of exporting, renaming and uploading photos separately. ConPDS Checker sends container-linked inspection photos to the matching AEMS estimate through configured delivery rules.

No customer-side development is required for the standard workflow. ConPDS configures the connection with you; API access, shop details and testing are still required.

See setup requirements · We will review your workflow and confirm what is needed.

Spend less time handling AEMS photos

Reduce repeated file handling

For photos covered by your configured AEMS workflow, Checker handles delivery from the stored inspection record. Staff can avoid a separate round of exporting, renaming and uploading the same files.

Make photos accessible to the office

Once synchronized to your company’s ConPDS Checker server, inspection photos are available for office teams in the web dashboard, under the relevant container record.

Use the relevant estimate

Checker looks for estimates that match the container and your configured AEMS criteria. A single match can be used automatically; multiple matches require a user to select the intended estimate.

See delivery outcomes

Delivery attempts and their outcomes are logged in Checker. Staff can see which sends need attention and investigate them from the stored inspection record.

What the AEMS integration does

ConPDS Checker connects inspection photos to Maersk AEMS through its Container Maintenance & Repair APIs. Photos are associated with a container and a matching estimate, and delivery follows the rules configured for your operation. Repair management and approval decisions remain in AEMS.

The connection supports photo documentation for PTI, damage inspections and repair work. It adds photo distribution to your existing process without requiring you to build an AEMS connector.

Where the time savings come from

The saving comes from removing repeated handling between capture and delivery. Your team captures and reviews inspection photos in Checker, while the configured connection handles eligible AEMS sends. Time otherwise spent collecting files, renaming them and uploading them separately can be used for inspections and follow-up. Staff still handle exceptions such as several matching estimates or a failed send.

How photos reach Maersk AEMS

Capture

Identify the container

Synchronize

Make photos accessible

Match estimate

One match or user selection

Deliver

Review the send outcome

STEP 01

Capture and identify

Take inspection photos in ConPDS Checker. Container-number recognition and an ISO 6346 check-digit check help identify the container; users can retake the image or enter the number manually when needed.

STEP 02

Synchronize to Checker

Photos upload to your company’s ConPDS Checker server when connectivity is available. They are then available for authorised office teams in the web dashboard, under the relevant container record.

STEP 03

Match the AEMS estimate

Checker looks up AEMS estimates for the container using the configured shop codes, order statuses and, where applicable, repair mode. If exactly one estimate matches, it can be selected automatically. If several match, a user selects the intended estimate in Checker and confirms the send.

Estimate matching

One match: the send can proceed without a selection prompt.

Several matches: a user selects the intended estimate and confirms Send.

No match: review the lookup criteria and estimate availability.

STEP 04

Deliver and review

Configured rules can initiate delivery immediately or after a set delay. The send must satisfy the estimate and attachment requirements, and the attempt and outcome are logged. AEMS availability and processing affect when photos can be viewed in AEMS.

Standard setup without customer development

For the standard Checker-to-AEMS photo workflow, you do not need to develop or maintain an API connector. ConPDS configures the existing integration with you and tests the agreed workflow.

What standard onboarding involves

Your team provides the operational details and helps arrange authorised AEMS API access. Together we confirm the shop codes, estimate-matching criteria, photo scope and delivery timing, then test representative cases before enabling routine delivery.

A customer IT contact may still be needed for access or security requirements. This is part of onboarding and configuration; it does not, by itself, require customer software development.

When additional integration work may be needed

Connecting an additional business system, importing photos through an unsupported channel, or changing the standard data mapping or workflow may require additional integration work.

ConPDS reviews those requirements separately and identifies any changes needed from your team or another system provider before work starts.

Setup timing depends on access, configuration and testing. We confirm the scope and expected timetable for your operation. Explore Checker integrations.

Photo documentation for PTI and repair work

Use the configured AEMS photo workflow for relevant PTI, damage and repair records. The photos delivered depend on your selected photo scope, matching estimate and configured delivery rules.

Pre-trip inspection documentation

Record exterior condition, visible defects and unit identification. See reefer PTI and repair photo documentation for the wider workshop workflow.

Defect and damage documentation

Photograph the location, nature and extent of visible defects, linked to the container record and the relevant repair estimate.

Spare-part documentation

Photograph replaced parts and their serial numbers before and after replacement, keeping the photos with the container’s inspection record.

Before-and-after repair photos

Keep photos taken before and after repair in the container record. Send the relevant photos to AEMS through the configured workflow.

The same inspection record can support delivery to other configured destinations. Available formats, matching rules and setup requirements depend on each receiving system. See supported Checker integrations.

Security and record retention

Privacy-by-design HTTPS encrypted transport Logged delivery attempts Role-based access control Configurable retention On-device encryption

Photos are stored encrypted on the device until upload. HTTPS encrypted transport and role-based access apply to the central archive. Inspection records follow the configured retention policy, and delivery attempts and later record changes are logged. A recorded send outcome does not mean that Maersk has reviewed or approved the estimate.

Questions about AEMS setup and delivery

Do we need our own developers to connect to Maersk AEMS? ▲

No customer-side development is required for the standard Checker-to-AEMS photo workflow. ConPDS configures and maintains the existing connector. Your team helps arrange authorised API access, confirms shop and workflow details, and takes part in testing. Additional systems or changes outside this workflow are assessed separately.

What do you need from us to get started? ▲

We need your relevant Maersk shop codes, authorised AEMS API access and a contact who understands the inspection and estimate workflow. We agree which photos to send, the estimate-matching criteria and the delivery timing, then test the setup together. An IT contact may be needed for access or security requirements.

How does Checker choose the AEMS estimate? ▲

Checker queries AEMS for the container using your configured shop codes, order statuses and optional repair-mode filter. If exactly one estimate matches, it can proceed automatically. If several match, a user must select the intended estimate; Checker does not choose arbitrarily. In the web dashboard, the user selects the estimate and confirms Send.

What happens if no estimate matches? ▲

Photos cannot be attached until a suitable estimate is available. Review the container number, shop and configured lookup criteria, then resolve the issue before sending again. Checker does not attach the photos to an unrelated estimate to complete the send.

Are photos sent immediately after capture? ▲

Photos first need to synchronize to Checker. Delivery then follows the configured rule, which may run immediately or after a set delay. Estimate matching, connectivity and AEMS processing also affect completion. An immediate trigger does not guarantee immediate visibility in AEMS.

Does this replace AEMS or our repair-management system? ▲

No. AEMS continues to hold the estimate and support the repair and approval process. Checker provides the inspection-photo record and the configured connection for delivering photos to the relevant estimate.

Can technicians capture photos without a connection? ▲

Yes. Checker supports offline photo capture and container-number recognition. Photos synchronize when connectivity returns. AEMS lookup and delivery require connectivity and run after the photos are available to the configured workflow.

Can AEMS receive every file stored in Checker? ▲

This connection sends supported inspection photos. The state of the estimate and its available attachment capacity can limit a send. Checker also supports video and audio capture, but those capabilities do not imply delivery of those media through the AEMS photo connection. MP4 video is not sent through this connection.

What happens if an AEMS send fails? ▲

The delivery outcome is recorded in Checker so staff can review the cause and take appropriate action, including a manual retry after resolving the issue. Photos remain in the Checker record under the configured retention policy. A failed send is not proof of delivery, and a successful send does not mean Maersk has reviewed or approved the estimate.

How long does setup take, and what does it include? ▲

ConPDS confirms the setup scope and timetable after reviewing your AEMS access, shop details, delivery rules and test cases. Standard Checker onboarding and activation are included in the subscription. We confirm whether your requested AEMS scope is standard or requires separately quoted integration work before starting. There is no fixed implementation time for every customer.

For destination settings and the current Send workflow, see the AEMS sending guide.

Reduce manual photo handling in your AEMS workflow

Show us how your team captures inspection photos and sends them to AEMS today. We will demonstrate the standard Checker workflow and confirm the access, configuration and testing needed for your operation.

Standard workflow without customer-side development. Additional integration requirements are scoped separately.