ARIA · Asset Repair Intelligence and Assessment

Evidence to Engineering.

ARIA guides technicians through equipment identification, photo and evidence capture, and voice notes during Disassembly—then organizes confirmed evidence into an inspection report and quote draft for authorized engineer review.

  • Evidence linked to findings
  • Engineer approval required
  • Designed for repair-floor workflows

Product concept · Production no-go pending validation. Examples below use sample data.

How it works

Four actions. One traceable assessment.

Select a step to explore the sample workflow.

Disassembly and cleaning are performed by your team. ARIA documents and assesses what they capture.

SAMPLE WORKFLOW

Confirm the tag, model, and parts.

Confirm equipment identity and collect the required photos, inspection observations, and time-coded narration. Keep as-received, pre-clean, cleaning return, and post-clean evidence distinct.

View controlled workflow details

Receive → initial disassembly → component disassembly → pre-clean completeness gate → cleaning sent out/returned → post-clean inspection. Missing required evidence blocks the next controlled transition.

Choose what you need to do.

Sample data · Demo

See the report.

Demo video coming soon

The planned demonstration follows a component from linked evidence through authorized review to an inspection report and quote draft.

Every finding in the report links back to its source evidence, so you can see what was captured, who reviewed it, and which version was approved.

Understand engineer review · Sample data

Demo · Sample data

Review the evidence beside the finding.

Evidence references

P-2048 · IMP-01

Observation OBS-01
Visible surface loss reported at vane tip; cause and extent unconfirmed.
Photo IMG-0042
Illustrative reference only; no source photo attached to this demo.
Voice note AUD-0003 · 00:07
Illustrative transcript: “Check the vane tip.” No playable recording in this demo.
DRAFT · NEEDS MORE EVIDENCE

F-01 / Impeller

Suggested follow-up: capture a clear detail view and verify the applicable shop criteria.

Criteria: Not yet verified. No technical disposition approved.

Why this finding was suggested

The technician observation needs corroborating evidence. Approval requires complete evidence, applicable criteria and an authorized human reviewer.

Review status: Needs evidence · no reviewer assigned · draft v1.

Open the authenticated workspace →

Why ARIA

Designed to make repair work easier to follow.

Intended outcomes to validate in a repair-team pilot.

More consistent evidence

Guided capture and required-view checks help reduce missing context.

Less manual translation

Structured findings support assessment and estimating handoff.

Traceable decisions

Connect findings to evidence, criteria, versions, and reviewer approval.

Built for repair shops.

Shop oriented

Equipment on the bench. Technicians capturing evidence. Engineers reviewing. Estimating receiving the result.

Trust & controls

Human authority at every technical decision.

These are design controls; deployment-specific validation remains open.

Human approval and attribution

AI drafts are advisory. Only an authorized human reviewer can approve an assessment. Technical approval does not release a customer quote.

Role-based access and permissions

Explicit shop membership and project-scoped evidence define access. Organization roles never imply unrestricted access to shop evidence. Validate role enforcement before deployment.

Evidence provenance and version history

Evidence, versioned local rules, corrections, and reviewer decisions must stay linked. Published records require a new version for corrections.

Data use and model training

Data terms are agreed in writing before a pilot. Confirm storage, retention, security and model-training terms with the product owner before deployment; no certification is claimed here.

View lifecycle and validation details →

One-shop pilot

Start with a repair team.
Validate with real jobs.

Agree on success measures and validate capture completeness and engineer review before expanding.

See pilot scope ↓
Pilot scope · Draft · owner/customer agreement required

Covers: Identify equipment (tag, model, parts); confirm photos, observations and voice notes during Disassembly; Quality/Engineering check; inspection report and quote draft from approved findings.

Participants: One repair team or shop with named technicians, at least one engineer/quality reviewer and one estimating contact. Team size: TBD.

Equipment: Centrifugal pumps, vertical turbine pumps or other rotating equipment, selected with the customer. Initial equipment type: TBD.

Out of scope: Physical Disassembly and cleaning; dimensional measurement from photos; autonomous approval; ERP/estimating-system integration unless implemented and validated for the pilot.

Success: Agree measures and capture a baseline before starting. Discuss capture completeness, repeated engineering questions, report preparation time and estimating handoff issues. No performance promises.

Duration and number of real jobs: TBD. Commercial terms: TBD.

Data: Agree terms in writing before starting. At the end, review results together and decide whether to expand, adjust or stop. Production readiness and advanced capabilities require validation before deployment.

Step 1 of 3 · About you

About you

Keep this page open to preserve your entries while moving between steps.