One photo, one part, one cycle: a fake-proof inspection system for a 146-vessel German shipping fleet
Germany flag
Build · Maritime · Germany

workspace_premium One photo, one part, one cycle: a fake-proof inspection system for a 146-vessel German shipping fleet

For a German shipping company operating a 146-vessel fleet, XMARTECH built a mobile inspection system that captures more than a quarter of a million verified inspections a year and makes a faked one physically impossible to submit.

auto_awesome App Development Story

We build for the failure before it happens — here is what that looked like on this project.

This page is structured as buyer questions with answer-first evidence, so clients can quickly understand risk, solution logic, and measurable outcomes.

crisis_alert Problem shape

Offline field app with real-world inspection integrity constraints

insights Lead outcome

250k+ verified inspections/year · 146 vessels · duplicate submissions blocked by design

category Delivery mode

Build

250k+

verified inspections per year

146

vessels in one fleet

159

distinct part checks tracked

4 months

fleet-wide go-live timeline

menu_book The whole story, in one paragraph

Faking was removed by construction, not by after-the-fact detection.

Before this system, crews photographed parts on personal phones and sent them by messenger to a supervisor who retyped vessel, part, date and time into spreadsheets. Across a 146-vessel fleet, that inbox became the bottleneck and old photos could be resent as fresh checks. XMARTECH changed the model: each part can be uploaded only once per inspection cycle, then locks until the next cycle opens, and every capture requires four live photos from four angles with geotag and timestamp. The system does not try to catch fake submissions later; it blocks them from being entered in the first place.

map Story map

gpp_badWhat was breaking or what was the risk?

The problem was administrative collapse first, fraud second. Every inspection depended on personal phones and chat threads, then manual supervisor re-entry into spreadsheets. With 146 vessels submitting through one stream, inbox sorting became continuous and error-prone, and an old photo could be resent as a new check because verification lived in human attention, not system rules.

build_circleHow do you stop a sailor from faking an inspection?

XMARTECH enforced four controls at capture: admin-provisioned per-vessel access, due-parts checklist gating, live capture only with geotag and timestamp, and four-angle evidence per part. Then the hard lock: once a part is submitted, that upload slot closes for the cycle and cannot be submitted again until the next one. Duplicate or recycled-photo submissions are rejected by the workflow itself.

precision_manufacturingHow was it built to hold?

This is a closed internal iOS app on company-issued vessel devices, provisioned by admin credentials per vessel. Inspections are captured offline-first and auto-upload on reconnection, with satellite connectivity serving normal operations. System validation enforces capture criteria (part binding, non-blank evidence, four angles, geotag, timestamp), then a human reviewer performs final part-match judgment in the admin panel. Automation covers what machines can verify; reviewers handle what requires domain judgment.

How it's wired

From chat-thread re-entry to a locked inspection cycle.

Before u2014 manual flow

Crew personal phone -> messaging app -> single supervisor inbox -> manual read -> hand-typed spreadsheet. No system lock, no structured audit path.

After u2014 enforced capture flow

Company iOS device -> per-vessel login -> due-parts checklist -> four-angle live capture with geotag/timestamp -> submit lock -> review in one admin panel.

iOS
Offline-first capture
Geotag + timestamp
Four-angle verification
Cycle lock
Admin panel

monitoringWhat did it produce?

  • 250k+ verified inspection records per year across 146 vessels
  • 159 distinct part checks across weekly and monthly cycles
  • Every record bound to one vessel, one part, one cycle, one live four-angle capture
  • Duplicate/faked submissions blocked at entry, not detected later
  • Fleet-wide go-live across all 146 vessels in 4 months (2023)
  • Manual chat sorting and hand re-entry removed; two supervisors now review instead of transcribe

info No fabricated time-saved baseline is claimed. The defensible shift is operational: data-entry work is removed, and supervisors now validate structured records in one admin panel.

flare The part they did not ask for

XMARTECH made faked inspections impossible to submit in a German shipping fleet app — not by detecting fraud after the fact, but by design. Each part can be uploaded only once per cycle and then locks until reopening, so re-sent old photos are rejected before review. Every capture requires four live photos from four angles, with location and time stamped at capture, so printed photos or phone screens cannot stand in for the real part.

// The system blocks the attack before it exists as data.

quizBuyer questions, answered

What was actually breaking?

Inspection operations ran through personal phones and chat, then manual spreadsheet transcription by supervisors. At fleet volume, the inbox outpaced human sorting, and old images could be resent as fresh checks because proof lived in thread reading, not system constraints.

What happens when the connection drops at sea?

The app is offline-first: captures are written on-device and upload automatically when connectivity returns. Satellite connectivity is normal, but inspections complete when work is done, not when the network is healthy.

How does the system know the photo is the right part?

System checks enforce what is machine-verifiable (fresh timestamp, geotag, non-blank image, four-angle completion). Final part-match confirmation is done by a human reviewer. Automation is used where it is trustworthy; judgment stays with reviewers.

Product surfaces

Inspection surfaces on the vessel

What crews actually use at sea: due-parts checklists, weekly cadence, and pending-submission state — before a part can lock for the cycle.

tuneUnder the hood

Admin-provisioned per-vessel credentials Closed internal app on company-issued iOS devices Due-parts checklist gating by weekly/monthly cadence Live capture only (no camera-roll import) Geotag + timestamp bound at capture 4 required angles per part before submit unlock Single-submission lock per part per cycle Offline-first capture + auto-sync on reconnection Two-stage verification: system criteria + human part-match review Single admin panel with vessel-segregated records

A logger records history. A system like this prevents bad history.

XMARTECH turned inspection trust from a supervisor workload into a workflow constraint: if evidence does not meet capture rules, the record cannot exist.

forumDirect conversation model

01

You share business goals, constraints, and deadlines.

02

You talk directly with the engineering team, not only account managers.

03

We turn strategy into a scoped delivery plan and execution timeline.

auto_graph Project-type focus

  • Offline-first user flows
  • Device-level reliability
  • Release-safe iteration
arrow_back Back to all work Discuss a similar project arrow_forward