A field technician can complete a form and take clear photographs yet still attach the evidence to the wrong asset. The purchasing problem is not solved by screen size, camera resolution or a successful upload alone. The tablet, identification method and inspection application must keep the asset record, form response and attachments connected through capture, offline storage and backend review.
This guide uses an editorial inspection of two neighboring pumps to show where that relationship can break. It complements Rugged Tablet Field Operations and does not claim that an AIDC GO tablet includes a particular inspection application, attachment workflow or asset-management integration.
Begin with asset identity, not the camera button
The operator should identify the asset before opening or creating the inspection record. That identity might come from a barcode, an RFID event, a controlled list or another approved method. The project must define which value is authoritative and how the application shows that the current form belongs to it.
Consider two adjacent pumps, P-204 and P-205, with similar housings. The operator scans P-204, opens its inspection and photographs a damaged coupling. Before submitting, the operator walks to P-205. If the app keeps the prior form open without a clear asset banner, the next photo can be convincing but attached to the wrong record.
The useful interface evidence is not only the decoded label. Retain the selected asset ID, record ID, visible asset context, attachment question or field, file identity and final submission result for the same inspection.
Make the form carry the inspection context
The form should make it difficult to lose track of the active asset. Show the asset identifier and distinguishing context near the inspection fields, and define what happens when a new asset is scanned while a form is incomplete. A prompt to save, discard or remain on the current record is an application behavior to verify, not a tablet feature to assume.
Use the customer's real form when evaluating screen size and interaction. Include small labels, numerical readings, status choices, required notes and the actual photo questions. Rugged Tablet Screen Readability Outdoors explains how to evaluate those forms in the intended light and viewing positions.
If scanning is part of the workflow, verify how the identifier reaches the correct form field. Barcode Scanner Integration Methods separates keyboard, Intent and SDK paths; none of those paths independently proves that the application opened the intended asset record.
Treat each photograph as a record attachment
The ArcGIS Survey123 media and files documentation is one bounded application example. It describes image questions that can select a file or use a camera, and it explains that attachment keywords associate attachments with specific questions. It also notes that changing an image-question name requires corresponding existing attachment keywords to be updated.
That example shows why a photograph needs more context than a timestamp or file name. The application should associate it with the intended response and question. The project should preserve that relationship through editing, synchronization, export and report generation. These are application and data-model requirements, not guarantees made by a tablet camera.
Photo time, EXIF or location may support review, but none is sufficient by itself to prove asset identity. Neighboring equipment can share nearly identical coordinates, device time can be wrong, and a stored image may have been selected from the gallery rather than captured in the open form.
Follow one inspection through failure and recovery
In the editorial example, the technician scans P-204, completes three checks and takes a close-up in the form's coupling_photo question. The form saves locally because connectivity is unavailable. The technician then opens P-205, takes a general photo and submits when coverage returns. The second record appears in the backend, while the first remains unsent.
The correct conclusion is not that all evidence has uploaded because one record is visible. The Survey123 submit-results documentation describes an Outbox for completed surveys that have not yet been submitted and a later send action after reconnection. This is a named application example; another inspection system can use different states.
The operator or supervisor should compare the device queue with the backend record list, then submit or investigate the unsent P-204 record without copying its photograph into P-205. Use Offline Barcode Capture for the broader principle that a local pending state and an acknowledged backend result are different facts.
Compare the evidence at each layer
| Inspection layer | Evidence to retain | What it does not establish alone |
|---|---|---|
| Asset selection | Authoritative asset ID, scan or selection method and visible context | It does not establish that the open form is the intended record. |
| Form state | Record ID, asset banner, required fields and local save state | It does not establish that every attachment belongs to that form. |
| Photo attachment | Attachment identity, question or field and preview in the active record | It does not establish that the attachment reached the backend. |
| Submission | Local status, attempt time and application result | It does not establish that a supervisor can see the complete record and files. |
| Backend review | Asset, form values, attachment set and exception status | It does not establish that another pending device record does not exist. |
The rows should reconcile for one controlled inspection. A gallery showing the expected photographs without record IDs is not enough, and a submitted form count does not prove that every required attachment arrived.
Test the switches that cause wrong associations
Run the real application with two clearly labeled test assets. Start a form for the first, capture a photo, then scan or select the second asset before submission. Verify the prompt and resulting record. Repeat with a locally saved form, a failed attachment upload, an application restart and a later revisit that adds a reinspection photo.
Check how the application distinguishes the original inspection, correction and reinspection. Confirm whether attachment upload failure is visible separately from form submission failure. In the backend, compare the asset ID, record ID, question name, attachment count and file preview rather than relying only on a successful status banner.
Use Rugged Tablet Docking, Ports and Power if the project adds external scanners, cameras or powered peripherals. Their connection must be evaluated as part of the complete setup, not inferred from the presence of one matching port.
Bring the complete inspection record to procurement
Provide the asset-label examples, identification rules, application and OS versions, real forms, photo and file requirements, offline behavior, retention policy, expected backend view, peripherals, protective accessories and deployment conditions. Identify where technicians review photos and how supervisors resolve a record whose form arrives without every attachment.
Ask the application provider for versioned documentation covering asset selection, attachment association, local queues, retries, editing and audit history. Ask AIDC GO for the relevant tablet configuration and integration documents without assuming a specific application, camera workflow, mount or peripheral compatibility.
Use Rugged Tablets to compare published device directions, Field Service and Inspection for the industry context, then Integration & Support and Contact AIDC GO to present the complete workflow. Approval should depend on one asset's identity, form, photos and backend result remaining connected through the tested path.