From field evidence to follow-up

Mobile visual inspection software for large industrial assets

EPOVIS is mobile visual inspection software for large industrial assets: teams use a handheld iOS device for guided capture, then use Web review to examine traceable evidence, coordinate repair and reinspection, and keep final quality decisions with authorized humans.

Who this is forQuality teams evaluating a mobile workflow for large robots, complex assemblies, power-plant piping or other assets that are difficult to cover from fixed viewpoints.

Quality inspection and traceability, from the field.

Evaluate a mobile workflow for visible appearance and assembly checks, traceable evidence, repair and independent reinspection.

What does the mobile inspector use?

An iPhone-based field workflow with Web coordination. Confirm device compatibility, spatial guidance and capture conditions for your scenario.

Which quality records should stay connected?

Connect the asset/SN, inspection criteria, images, findings, repair and independent reinspection. Confirm batch genealogy, MRB and other QMS requirements separately.

How do we assess a lightweight, low-cost start?

Start with one scenario. Confirm existing-device compatibility and a written scope covering subscription, usage, setup and services. Validate weak-network requirements in the pilot.

When should you use mobile visual inspection instead of a fixed camera station?

Choose the inspection approach from the asset, required viewpoints and production pattern—not from the AI label alone.

Choose a mobile workflow

Use mobile visual inspection for large assets, distributed inspection points or changing viewpoints that a fixed camera station cannot reliably cover. EPOVIS connects guided iOS capture with traceable evidence, Web review, repair and independent reinspection.

Choose a fixed station

A fixed camera station is generally the better fit for repeatable, high-throughput views in a controlled line. For an EPOVIS mobile deployment, validate lighting, coverage, device support, model performance and acceptance criteria in the actual scenario.

How the workflow fits together

Define the inspection task
Choose the asset, inspection point, applicable scheme and visible condition to inspect. Confirm the device, viewpoints, acceptance criteria and excluded checks for the deployment.
Guide handheld capture
Use the iOS workflow to guide a field inspector through required views. Check visibility, lighting and coverage; keep the source image and context available for review.
Complete Web review
Use Web review to examine findings and source evidence, coordinate repair and independent reinspection, and leave unresolved cases for an authorized human decision.

A captured image is not a passed inspection. A repair is not a passed reinspection. A result for inspected items does not establish whole-plant yield or authorize shipment.

What does EPOVIS automate, and what remains a human decision?

EPOVIS assists guided capture, evidence organization, AI-supported review and follow-up. It does not replace non-destructive testing and does not authorize shipment release. Device support, model performance, integrations and acceptance criteria must be validated for the actual inspection scenario.

Define a useful pilot.

Bring one asset type, a few representative inspection points, an agreed defect standard and the people responsible for review. Agree sample coverage, false positives, missed defects, review time and acceptance criteria before measuring results. Confirm device support, data retention, access permissions and integration scope in the proposal.

Plan a mobile vs fixed-station inspection pilot

Choose one inspection task before choosing the equipment. Test handheld and fixed-station capture against the same scope and required views. If a method cannot meet a required condition, keep that gap open; a lower price or faster capture does not cancel it out.

Agree acceptance criteria before the trial. Use the blank worksheet to record evidence for each method, a decision, an owner and the next action. There is no automatic score or default winner.

Inspection scope: Name the visible condition, inspection point and acceptance criterion. Keep specialist measurements and internal-defect tests in their own procedures.
Access and coverage: Can each method capture all required views safely? Include awkward angles and obstructed points. Record any view that cannot be judged.
Capture repeatability: Repeat captures across operators, lighting and camera positions. Record unclear images and retakes instead of selecting only the best image.
Representative cases: Use the same agreed normal, defective and ambiguous examples for each method. Keep trial results separate from examples used to prepare the inspection.
Work and throughput: Measure setup, capture, retakes and human review separately. Compare complete tasks at the required pace, including a product changeover.
Evidence recovery: Ask another reviewer to recover the asset/SN, point, criteria, original image and decision. Check that repair and reinspection remain distinct.
Connectivity and recovery: Test the required network conditions. Verify capture storage, synchronization and AI access separately; record what happens after an interruption.
Total scoped cost: Obtain like-for-like written estimates for devices, fixtures, lighting, software, usage, storage, setup, training and integration. List assumptions and exclusions.

Download the blank pilot worksheet (CSV)

A planning worksheet for your own evaluation. It does not certify an inspection process or establish a supplier's features, accuracy, offline support or cost.

EPOVIS is software connecting an iPhone field workflow with Web coordination and traceable inspection evidence. Bring your representative task and device requirements to a scoped demonstration; confirm compatibility and available capabilities before rollout.

See how field capture and Web review connect.

These pages describe the intended EPOVIS workflow. Confirm the supported devices, feature availability and acceptance scope for your deployment during the scenario demo.