AQLYRON

HVAC/R service investigation · In development

A clearer case.
From fault report
to follow-up.

Stopped equipment. Uncertain identity. Readings that don’t agree. AQLYRON is being built to keep findings, technical reasoning, and the next useful question together.

Inspect the engineering Discuss future access

Inspect the current software evidence and a real local prototype. Customer access is not open yet.

AQLYRON FIELD RECORDED LOCAL PROTOTYPE
Actual Field prototype showing a synthetic stopped-system case and the next question: which units or served areas are affected.
An incomplete case, kept open. The captured prototype proposes another observation while equipment identity and cause remain unresolved.Inspect the full original capture

WHAT THE PROTOTYPE CONNECTS

  1. 01Capture the report
  2. 02Keep evidence distinct
  3. 03Review what follows
  4. 04Carry the case forward

The current local Field workflow connects capture, persisted case history, review, and handoff. Real equipment validation and customer operations remain ahead.

INSPECT THE BEHAVIOR

Four cases.
Actual recorded outputs.

Original synthetic inputs, executed against current AQLYRON code. Each record shows what the software returned and the limit of that result.

01

The next question changes.

An existing trace changes which record the model selects for review.

MODEL CHECK 02

Missing information stays missing.

An unknown system and an incomplete report leave the cause open.

SERVICE CHECK 03

A withdrawn finding changes the conclusion.

A dependent synthetic check becomes noncurrent when its evidence is withdrawn.

EVIDENCE CHECK 04

Restoration and cause remain separate.

A report that operation returned does not establish why it stopped.

OUTCOME CHECK

FOR SERVICE TEAMS

How much context does
your team reconstruct?

Use your own workload figures to estimate the monthly effort spent piecing a case back together. A baseline for a conversation, with the calculation visible.

Technicians × investigations × minutes ÷ 60

Monthly context-reconstruction hours from your inputs. No assumed product savings.

Build your workload baseline

A PRODUCT YOU CAN EXAMINE

Working foundations.
A clear development boundary.

The service and Field prototype run locally with synthetic cases. The engineering records are software evidence. Field performance, production operations, and customer value still need to be demonstrated.

See the capability map
Can my team use AQLYRON today?

No open trial or customer pilot is available today. We welcome technical evaluation discussions, interest in future access, and conversations about integration needs.

Choose a conversation