Field work, written down while it happens.

IVA sees the job through the technician’s glasses or phone, listens to what they say, and fills in the work order in the system you already use. The technician checks it and signs. Nobody types a report in the van.

No custom hardware. Pilots open for telecom field operations and industrial maintenance teams.

Work order WO-24817
Site
Tower BLR-0412, Whitefield
Asset
Radio unit, sector B, 1800 MHz
Fault found
Water in the jumper connector, raising a VSWR alarm
Work done
Replaced jumper and resealed. VSWR 1.9 before, 1.2 after
Parts used
1 jumper cable, 1.5 m; 1 weatherproofing kit
Evidence
4 photos and both readings, attached
Status
Resolved, ready to close
Technician sign-off
Waiting for review
Illustrative example. Blue text is what IVA wrote from the technician’s view and voice. Nothing is submitted until the technician signs.

The record is written last, and worst.

Enterprise AI can only reason over what someone wrote down. In field work, writing it down happens at the end of the shift, from memory, on a phone, by someone who would rather be on the next job. The fault, the fix and the evidence get compressed into “issue resolved.”

The distance between the work done and the work recorded is what IVA closes. We call it the capture gap.

Where a technician’s working hours go

Admin and information gathering 30%
Delivering service 28%
Self-reported estimates from a Salesforce survey of 350 US tradespeople and technicians, February–March 2025. The same survey found telecom and utilities skew further towards admin. Our own pilots will publish measured numbers on the pilots page.

From the job to the system of record, in one pass.

  1. See the job

    The technician wears commercially available AI glasses, or a phone in a chest mount. IVA captures photos, meter readings and their spoken notes while their hands stay on the work.

  2. Understand it

    IVA matches what it saw to the asset, your fault codes and your procedure. When something is missing, a reading, a serial number, a part, it asks by voice before the technician leaves.

  3. Write it back

    IVA drafts the completed record in your field-service, maintenance or trouble-ticketing system. The technician reviews it on site and signs. Then it’s submitted.

Built first for two kinds of crew.

Telecom field operations

Tower, fibre and site technicians whose work orders feed network operations and trouble-ticketing.

  • ReadingsVSWR before and after, optical power at handoff
  • EvidenceSite photos tagged to the asset and sector
  • ClosureFault cause coded to your taxonomy, not free text

Industrial maintenance

Maintenance crews on plant floors, in warehouses and on robot fleets, where the record feeds the maintenance system and the next shift.

  • ReadingsVibration, temperature, error codes from the panel
  • EvidenceBefore and after photos of the part replaced
  • HandoverWhat was tried, what worked, what to watch

A two-week field pilot, measured before it starts.

We run IVA with one crew at one site, against a baseline we measure together in the first two days. You keep the readout whether or not you continue.

What we measure

  • Minutes from job complete to record submitted
  • Records complete on first submission, without a call-back
  • Technician time spent on reporting per shift
  • First-time-fix rate on repeat visits to the same asset
  1. Days 1–2

    Baseline

    Shadow the crew and measure how records get written today. Agree the target fields with your operations lead.

  2. Days 3–12

    Run

    The crew works with IVA. Records go to a sandbox or your live system, your choice, with a person signing every one.

  3. Days 13–14

    Readout

    Before and after on every measure, failures included. Then you decide whether to continue.

A camera at work has to earn its place.

What we commit to in every pilot. The full policy is on the trust page.

The technician controls capture
Recording starts and stops with the technician, and the device shows when it’s on.
Nothing is submitted unsigned
IVA drafts. A named person reviews and signs every record before it reaches your system.
Your data stays yours
Media is kept only as long as you set, and never used to train shared models without your written agreement.
Every action is logged
Who captured what, what IVA wrote, and who signed, in an audit log you can export.

The memo

Enterprise AI is starving at the edge. The most valuable operational knowledge is created by people whose hands are busy, and it never reaches the system of record.

From The Capture Gap, a memo on why field work is where enterprise AI goes next. Draft 0.9, October 2026.

Read the memo

Built by someone who has sold into field operations.

IVA is built by Shivashish Borah, founder of AI Humane Technologies. His career has been where software meets operations: telecom order and service systems, presales architecture, and selling autonomous robots into industrial sites. Each taught the same lesson. A system of record is only as good as what the field puts into it.

Based in
Bengaluru
Background
Telecom OSS/BSS, industrial robotics go-to-market, presales solution architecture
Fellowship
Perplexity AI Business Fellow
Contact
shivashish@aihumane.in

Questions operations teams ask first

Do you make glasses?

No. IVA is designed to run on commercially available AI glasses, or on a phone in a chest or helmet mount. We choose hardware for your site during the pilot.

Which systems does IVA write to?

Field-service management, maintenance management (CMMS) and trouble-ticketing systems that have an API. We build the connector for your system during the pilot, and that work carries over to every team on the same system.

Does IVA submit records on its own?

No. IVA drafts the record and asks for anything missing. A named person signs every record before it reaches your system.

Where does the captured video and audio go?

Into storage you control, for as long as you set, and nowhere else. The trust page covers retention, access and what happens to bystanders.

What happened to the master plan?

The original master plan from July 2026 is archived here. It described a long path from consumer glasses to an enterprise platform. We’ve narrowed the starting point to field work, where the value can be measured in two weeks. The memo explains why.

Bring one crew. We’ll show you the before and after.

Book a field pilot

Tell us about your crew and where your work orders live. Shivashish replies personally.