| Term | Definition | |
|---|---|---|
| Virtual Desktop | The player interface | |
| Facilitator | The controller of the exercise, responsible for delivering injects, managing flow, supporting players, and observing decisions | |
| Facilitator Dashboard | The web application used by the Facilitator to run the exercise | |
| Editor | The exercise design application | |
| Exercise | The logic and content associated with a training session | |
| Scenario | The story the forms the basis for the exercise | |
| Persona | Simulated individual or organisation with goals and attributes. In gaming, a Non-Player Character (NPC). | |
| Faction | A means of organising Personas into groups with shared goals and attributes | |
| Disposition | How favourable the persona views the goals of the training audience | |
| Channels (Methods) | A means of delivering information to the player Popular channels:
Pop-up channels:
Information-based channels:
Exercise-logging channels:
Monitoring and altering channels:
Collaboration-based channels:
Other social channels:
Other/misc:
| |
| Serial | Sits within the MEL to split the narrative into sections | |
| AXS (Active eXercise System) | Home to 3 AI assistants which aid the exercise planning and designing process | |
| FIEMA (Framework for Information Environment Measurement and Analysis) | An AI assistant that aids geopolitical and hybrid warfare exercises and thinks in terms of military and State-level actions | |
| LISA | An AI assistant that aids in the plotting of MELs, featured within AXS and Sidekick | |
| Canvas | A brainstorming tool featured within AXS which can be used for client sign-off | |
| Pulse | A monitoring and performance dashboard which provides a control-room view of the exercise | |
| Observer | A non-participating role, usually silent, who watches the exercise to assess performance or gather lessons learned | |
| Adjudicator | Observes the evolution of the information space and actions/inactions of the training audience, determining how the information space should change | |
| PoL (Pattern of Life) | A predefined pool of content used to simulate audiences predominantly | |
| Stack/Stax | Stack of content used in Pattern of Life | |
| Deck | The set of buttons on the Pattern of Life control | |
| Smartwords | Dynamic placeholders that act like variables, automatically pulling in data | |
| Ventura | A library containing exercises and Personas | |
| Branching | Using multiple MELs or stopping/starting PoLs to make exercises more responsive to player choices | |
| Fidelity | The level of realism or detail in the exercise |
| Term | Definition | |
|---|---|---|
| Player | A human. A primary participant in the exercise who makes decisions, receives injects, and experiences consequences based on their role | |
| Actor | A persona who plays a significant part in the exercise | |
| EXCON (Exercise Control) | The team that manages and runs the live exercise | |
| TTX | Table Top eXercise. | |
| MEL (Master Events List) | Primary timeline that drives all injects | |
| Inject | A single piece of exercise content or event | |
| Training Audience (TA) | Same as the player | |
| Training Objectives | The purpose of the exercise. The specific skills, behaviours, or decision-making abilities the exercise is designed to test/strengthen | |
| Learning Outcomes | Knowledge, skills, or behaviours expected from the exercise | |
| Role | Assigned to a player to ensure they’re fulfilling their training objectives (usually corresponds to a Player’s IRL job role within an organisation) Note: Conducttr allows a job role to be filled using Role or Position. There are 5 Roles in Conducttr and unlimited Positions. See the section on Roles for a complete discussion. | |
| Position | Refers to what permissions or role players fulfil during an exercise | |
| Team | A grouping of players within an exercise, mirroring real-world organisational structures | |
| Role-playing | The ability to play as a Persona who is not yourself (uses Impersonation or matching email) | |
| NPC (Non-Playable Character) | Stakeholder played by the computer or simulation | |
| Red Team | Adversarial team that introduces friction | |
| Inciting incident | The first disruptive event that kicks off the crisis scenario and drives players into action | |
| Decision point | A moment where players must make a choice that influences the scenario | |
| Data point | Attached to a question, a way of collecting data about player responses |
| Term | Definition | |
|---|---|---|
| World | An administrative domain that includes an exercise library and one or more hubs | |
| Exercise Library | A collection of slots where exercises (the training session content) have been uploaded from the Scenario Editor | |
| Session | A record of an exercise run. Each time a Facilitator runs an exercise, a session is created | |
| Hub | A simulation space representing a business entity where exercises are run. Facilitators log into a Hub to select and run an exercise | |
| Facilitator | A user who can run exercises without needing prior experience with Conducttr or using the Scenario Editor | |
| Administrator | A user who holds the master copy of an exercise and manages its availability, presentation, Facilitator access, and updates | |
| World Admin | A role that oversees the creation of hubs and management of facilitators, exercise publishing, notifications, and reporting from a central web application |