← Explore the field loop

For technicians

Your tools. Your judgment. A job that stays together.

Keep the unit, readings, photos and findings in context. Spend less attention managing the app and more attention understanding the equipment.

Field-first product direction
The machine, the readings, the work.Beautified product visualization · example data
HVAI / Service techniciansTrane / RTU 04

YCD180B3LCHB · Serial 607100868D. The original nameplate remains inspectable. Unsupported configuration facts stay unknown.

Inspect the original plate ↗

Beautified product visualization, not an Android capture. Example equipment context; the complete physical field loop remains in development.

Service technicians / IN DEPTH

The work behind the interface.

Purpose, prerequisites and the evidence that belongs to the task.

You have a machine to understand and work to explain. HVAI is being built to keep the equipment identity, probe readings, photos and findings together—so you spend less effort managing disconnected records and leave the next person better informed.

01

Keep your setup with the job

The site, unit, circuit and confirmed tool roles are designed to carry through the visit. The goal is less repeated entry and fewer decisions you already made at the machine.

02

Understand where the reading belongs

See the physical role, circuit, source and freshness beside the value. Eligible calculations and system relationships help explain the evidence while missing observations stay visible.

03

Leave a story the next person can use

Keep photographs, notes and readings with the intended visit. Review what you found, what you changed and what remains open, so another person can understand the work.

THROUGH THE TASK

Keep the context
at each step.

Open a step to inspect what needs to stay clear.

01Arrive with the machine in focus

Confirm the site and physical unit, then inspect identity and applicable references. Uncertain facts remain reviewable before they influence the next step.

02Work with clear state

Connection, valid telemetry and interpretation should be separate signals. Stable controls and visible tap alternatives support inspection as values update or circuits change.

03Explain what the evidence supports

Use eligible values, graphs and system relationships to understand the observation. Leave unsupported conclusions open and identify the next missing piece of evidence.

04Leave a readable account

Review the findings, work performed and remaining questions. The goal is a record that carries the technician’s understanding forward to the next reader.

STATUS & EVIDENCE

Intended benefits need real field evaluation.

The brief does not claim measured time savings, reduced callbacks or a return on investment. Dark and outdoor-oriented Sun experiences are design directions. Dependable performance needs declared phones, tools and conditions, with real technicians assessing the complete task.