Introduction to Procedures and the Procedure Builder
Introduction
In SynergyXR, a Procedure defines a training program containing 3D models, detailed interactions and voice guidance, all embedded in a single intricate piece of content to be placed in a Space.
In the Procedure Builder, users can import content and place it in the 3D scene – define what the trainee must do to complete the training procedure, and how the system reacts to the trainee’s interactions – and define errors and warnings the trainee can trigger during the training.
Structure of Procedures
Interactions of a Procedure is defined by a sequence of Steps that can be structured into Step Groups. A Step Group can be seen as a chapter of a training Procedure – it does not introduce any functional change to the Procedure but is a convenient way of structuring a Procedure increasing the readability and maintainability.
A Step consists of the following elements:
- Title: A textual description of what this step does. The title must be unique – the Procedure Builder automatically adds a trailing integer to ensure uniqueness in case a user reuses a title.
- Guidance: Users can write textual guidance that will be shown on the Procedure Panel when a trainee is completing the training. Using AI-enhanced text-to-speech the Procedure Builder can generate synthetic voice guidance from the text, providing an instant preview to the user.
- Operation(s): Each Step contains at least one Operation that defines what the trainee must do to complete the Step and proceed in the Procedure. In case more than one Operation is defined in a Step, the trainee can complete all the Operations in arbitrary order, but must complete them all to proceed to the next Step.
- Action(s): As part of an Operation users can define how the system reacts to the trainee performing said Operation. Actions are divided into "Actions Before" which are executed before the trainee performs the Operation and "Actions After" which are executed after the trainee performs the Operation.

Whereas Steps define the main flow of the Procedure, where the trainee must complete each Step to progress to the next, Events are used to define possible interactions running alongside the main Steps of the Procedure.
The figure on the left shows how it is possible to enable and disable multiple Events running in parallel with the main Procedure Steps.
Events are often used to describe potential errors the trainee can accidentally make during the Procedure.