Offline Field Capture That Survives a Refinery
Every vendor says the app works offline. Test it in a vessel, in gloves, with 200 photographs and a permit expiring in forty minutes.
Field capture is the layer that determines whether the rest of the system holds trustworthy data, and it is the layer most often demonstrated in ideal conditions. Real conditions are confined spaces with no signal, gloved hands, poor light, a permit clock, and a technician who will revert to paper the moment the tool is slower than a notebook. These are the properties that decide whether it is used.
Offline has to mean fully offline
Partially offline tools — those that cache reads but require connectivity to create records, look up an asset or attach a photo — fail in exactly the places inspection happens. The test is whether a technician can complete an entire inspection, including asset lookup, form completion, photographs, sketches and sign-off, with the device in airplane mode from start to finish.
The second half of the test is sync. When connectivity returns, records must merge without loss, without duplication and without a stale server copy overwriting field work. Ask to see a deliberate conflict during evaluation, not a description of how conflicts are handled.
Interface constraints that are not negotiable
- Usable in gloves: large targets, no precision gestures, no small dropdown lists.
- Readable in direct sun and in a dark vessel — high contrast, not a light-grey aesthetic.
- Minimal typing. Numeric entry, pick-lists and voice notes beat free text at a CML face.
- Forms that mirror the technique sheet, in the order the work is physically performed.
- Resilient to interruption — a permit call or an evacuation must not lose ten minutes of entry.
Photographs and sketches are data, not attachments
A photograph filed against a job is nearly useless three years later; a photograph bound to a specific CML, weld or component is evidence. The tool should attach media to the location within the asset hierarchy automatically, compress sensibly for later sync without destroying diagnostic detail, and keep the original where it matters. Sketch and annotation over the photograph at the point of capture is worth more than any amount of later office markup.
What to test in a real evaluation
- Complete a full inspection in airplane mode, with 20+ photographs, then sync.
- Force a conflict: edit the same record on two devices offline, then sync both.
- Hand the device to your least tech-enthusiastic technician and watch without helping.
- Time it against the paper process for the same scope — if it is slower, adoption will fail regardless of features.
- Check battery consumption over a full shift with the screen and camera in real use.
Frequently Asked Questions
Why do offline inspection apps fail so often?
Three recurring reasons: they are only partially offline and break on asset lookup or media attachment; sync is naive and either loses field work or produces duplicates; and the interface was designed for an office device rather than a gloved hand in bad light. All three are visible in a properly-run field trial and invisible in a conference-room demo.
Should technicians use company devices or their own?
Company devices in almost all cases. Hazardous-area classification alone often mandates it, and beyond that you need control over the OS version, storage, battery condition and camera quality. Personal-device programmes tend to generate support load that exceeds the hardware saving within a year.
How do we handle intrinsically safe area requirements?
Use certified intrinsically safe tablets or phones appropriate to the area classification, and confirm the software runs on the OS versions those devices actually ship with — certified hardware often lags several OS releases behind consumer devices, and an app requiring the latest OS will simply not run on it.
What happens to data if a device is lost or damaged on site?
That is what the sync design is for. Records completed before the last sync are already safe; work since then is lost unless the tool syncs opportunistically whenever any connectivity appears. Ask specifically how frequently and how granularly the tool syncs, and whether partial records survive.
See it running on your own workflow
Thirty minutes, your job types and your reporting formats, co-presented by an ASNT NDT Level III. Affordable, accessible, fully customizable — request a demo and a tailored quote.
Related: Inspection management software · NDT reporting software · Work order management · NDT inspection software guide