Frequently asked questions

Every project follows the STARK 4D method: Discover, Design, Develop, Deploy. We always start with a Discover phase in which we map your challenge, your audience and your success criteria. After that we design an approach, build the training in close collaboration with your subject matter experts, and support the rollout. The first module is usually available within 2 to 6 weeks.

No. We work for asset owners, grid operators, EPC contractors, service contractors and project organisations, from dozens of employees to thousands. The scale of the project shapes the approach, not the size of the organisation.

A first module is available in 2 to 6 weeks, depending on complexity and on how available the source material is. For time-critical situations, an approaching shutdown, a project start or an onboarding deadline, we work to an accelerated schedule. We start with whatever is most urgent.

Always. Your experts are the source of the content. We structure that knowledge, translate it into an effective learning format, and make sure the training still holds five years from now. The collaboration is more intensive during the Discover and Design phases and less time-consuming during the build.

Yes. Modern standalone headsets such as the Meta Quest 3 are intuitive and require no technical background. In our experience, operators and technicians, older generations included, get comfortable quickly. We always build a short introductory environment that lets people settle in before they start the first scenario.

No. Our VR modules run on standalone Meta Quest headsets: no PC, no network connection, no IT installation required. Headsets can be charged and synchronised through a simple MDM solution. Two to four headsets per site are usually enough for a shift rotation.

Yes. Our VR modules are xAPI compatible and send behavioural data to an LRS or an xAPI-compatible LMS. For platforms that only support SCORM, we build a SCORM wrapper that passes completion and basic data through. We help with the technical integration.

Not always, but it helps. During the Discover phase we prefer to spend a day on site. To build the VR environment we use technical drawings, P&ID schematics, photographs and video. Where an on-site visit is not possible, we work from digital documentation and video recordings.

Our content works in any SCORM 1.2 or SCORM 2004 compatible LMS. Platforms we commonly work with include Cornerstone, SAP SuccessFactors, Moodle, TalentLMS, Docebo and Totara. Where there is any doubt, we always test the integration before go-live.

Yes. We build SCORM-conformant content as standard, which works in any compatible LMS. If you have no LMS, we advise on a suitable option based on your scale and your requirements.

Yes. We take existing slide decks, PDF procedures, classroom material or dated e-learning and rebuild them into modern, effective formats. We always start with an analysis of what can be kept and what has to be revised.

No. We do not write the technical content ourselves, because that knowledge is yours. We structure your existing procedures, HAZOP reports, work instructions and expert knowledge, and make them accessible and applicable through the right training formats. Validation of the content always sits with your own experts.

We build training available in several languages as standard. That means professional localisation including voice-over in the target language, not automated translation. Commonly used languages: Dutch, English, German, Polish, Romanian and Turkish. Others are possible on request.

Every project has a content validation round with the client’s subject matter experts. We work iteratively: after each build phase a prototype is validated before we build further. That stops mistakes from being discovered only at the end of the project.

The cost depends on the complexity of the simulated environment, the number of scenarios and the platforms required. We are happy to give a first indication in an introductory conversation, based on your specific situation. A good yardstick: compare the investment with the cost of a single avoided incident, or with the saving on travel for classroom training.

A digital induction module for one location, including knowledge assessment and completion records, usually takes us 1 to 3 weeks to build. The cost is significantly lower than a VR simulation. For projects with a fixed deadline we work in phases: the most critical content first, then extension.