What peopleask us

Yes. Without CAD files the physical machine is measured by 3D scanning (photogrammetry or LiDAR) and turned into a digital twin. At project start we review whatever CAD, drawings and photographs exist and choose the most suitable method.

A typical first project runs 8–10 weeks: 1–2 weeks for the digital twin, 3–6 weeks for scenario development, 1 week for test and pilot. Discovery takes 1–4 weeks before that. Machine complexity and the number of scenarios move these ranges.

With the training that repeats most and costs most. One machine, one line or one procedure. Scope grows after the pilot runs — a large scope on day one usually means nothing to show for months.

From you: CAD data or drawings for the machine, the relevant procedure document, a risk assessment for safety scenarios, a small group for the pilot sessions and one point of contact. From us: the digital twin, a working scenario, a short guide and the pilot report.

No. The platform is shared; scenarios are written for you, from your assembly instructions, maintenance procedures and risk assessment.

Standalone headsets and PC-connected headsets, plus a desktop client for participants without a headset. Whether the hardware you own is compatible is checked together before installation. We do not publish a model list, because compatibility shifts with versions.

Two to four participants share a scene in one session. Those without a headset follow the same scenario from a desktop, so group size is not capped by headset count.

Scenarios are modular. When a machine is revised or a procedure changes, only the affected step is updated and the update is pushed to devices centrally; the content is not rebuilt.

It does. The session runs over the local network and the data never leaves the site. Internet is only needed for content updates and for joining from another city.

You own it. In local network mode it never leaves the site. When the cloud is used, records are held as your organisation’s and export to your own learning management system through SCORM or xAPI. Our privacy page covers the personal-data frame.

It does not. The Regulation on the Procedures and Principles of Occupational Health and Safety Training requires start-of-work training to be hands-on and face to face, and the fourth topic of basic training to be face to face in hazardous and very hazardous workplaces. Virtual reality can be used as a practical tool inside those sessions but does not remove the obligation. Which topic goes by which method is decided with your safety specialist.

Not if it runs at the plant with the instructor present: participant and instructor are in the same room, which makes it face-to-face training. If the parties are in different places the session can run remotely, and then the regulation’s distance-learning rules apply.

Virtual reality has measured results in industrial training; our case studies page reports them with links to the companies’ own publications and to peer-reviewed work. We do not quote figures for our own projects, because we have no publishable measurement yet. What happens in your plant is what the pilot measurement will show.

The duration of every step, the type of mistake made (wrong order, wrong part, skipped step, missed check) and completion per scenario. Put one participant’s repeats side by side and a competence curve appears.

Yes. The session result exports as a SCORM package or as xAPI statements, both standards that common learning management systems read.

There are two lines: content development and platform use. Content development is priced per project against machine complexity and the number of scenarios. The platform side depends on simultaneous users and the modules chosen. A firm number needs a conversation about scope.

The pilot is a project stage, so its scope and cost sit in the proposal. The discovery call is free — that is where we work out the scope and a realistic schedule together.