Training a controls technician has an awkward economics problem: the useful practice is diagnosing faults, and you cannot break real equipment to create them. So training defaults to classroom theory, and the actual diagnostic skill gets learned slowly, in the field, at customer expense.
Status: product concept, in active development. This is something we are building, not something you can buy today. We publish our roadmap because the engineering thinking behind it is the useful part — and because we would rather show you the design than imply a finished product.
Designed Capabilities
- Virtual mechanical rooms and panels — equipment you can open and inspect.
- Interactive meters and technician tools — take a reading the way you would on site.
- Wiring and signal tracing — follow the circuit to find the break.
- Sequence-of-operations exercises — understand what the system is supposed to do.
- Fault diagnosis scenarios — the failures that recur in the field.
- Instructor scenario editor — add faults specific to your installed base.
- Skills scoring and remediation — identify who needs which practice.
- Desktop non-VR accessibility mode — training that does not require a headset per trainee.
Diagnosis Is the Skill Worth Training
Anyone can be shown where a component is. The valuable and slow-to-acquire skill is working out why a system is misbehaving from incomplete evidence. Building scenarios around that — and scoring the diagnostic path, not just the final answer — is the design intent. The desktop mode exists because per-seat VR hardware is the usual reason training programmes stall.
Tell us if this matches a problem you have — early input shapes what we build first, and we will give you an honest view of where it stands.