...
| Table of Contents | ||||
|---|---|---|---|---|
|
About Launch
Launch provides VR content management functionality for you to seamlessly roll out your immersive training.
...
Once your content is created in Storyflow, you can use Launch to determine who gets the content, how they get it, and the format it is delivered in. Launch provides VR content management functionality for you to seamlessly roll out your immersive training.
...
Create content bundles and configurations from Storyflow and control how that content is deployed.
Manage learner profiles.
View session data from training sessions.
Manage devices.
...
Launch Permissions
| Note |
|---|
Only individuals with the Identity Launch Organization Admin permission or the Identity Launch Organization Member permission can view and edit Launch Launch |
...
There are permissions specific to Launch and you can learn about them and grant them using this article.
...
Using Launch you can deliver your VR training. Click here to learn more.
Anatomy of Launch
...
See the individual pages for a description of each component of Launch.
...
...
...
...
...
...
...
...
...
...
...
...
...
Screen
...
1. Organization: This is the dropdown that allows you to view the Launch Space for this Organization.
2. Home: This area provides a dashboard of your Launch area. For more info, click here.
Space Details: You can set up one or several Organizations in Launch. If your company has different departments that you want to separate, you can create more than one organization to which you can assign people with certain permissions.
Training Overview: Quickly see the number of learners in the space and how many sessions have been completed. Use the View Sessions/Learners link to jump to that area of Launch.
Collaborators: Individuals who have created the training or have permission to do so. Learners are not listed here – you can find them in the Learners section.
3. Learners: In this area you can view learners and drill down to see their training sessions and device logs. For more info, click here.
4. Modules: In this area you can see and create modules from uploaded Storyflow content. You will then use these Modules to distribute training to learners. For more info, click here.
5. Content: Content from Storyflow can be uploaded here and must be done before you can create a Module. For more info, click here.
6. Launchers: Launchers allow learners to connect to the learning. With a [Module] created, you can create a launcher. A launcher connects the [Module] to a 5 digit launch code. When the launch code is used to launch the training module in the headset, the data collected is connected to the learner specified in the launcher. Note that you would only use this feature if you were NOT connecting to an LMS.
For more info, click here.
7. Sessions Overview: This provides an overview of training sessions completed by learners in Dashboard form.
8. Scenarios: This area allows you to break down analytics by scenario. When you choose a scenario you are then able to view stats such as number of pass/fail, or time in scenario, and more. For more info, click here.
9. Sessions: A more detailed look at learner sessions. Any Storyflow test assessments added via Resources will be able to be viewed here. XAPI statements are captured and you can see what the learner looked at, pointed at, experienced and more. If LRS Credentials have been added and the LRS Credentials have been added to a Module, then all Session data will be available in the LRS. For more info, click here.
10. Collaborators: While a list of collaborators can be seen by both Admin and Members in the Home area, the Collaborators area can only been seen with the permission Launch Organization Admin. This is where an admin will view and manage collaborators in the space. For more info, click here.
11. LRS Credentials: If you have an external LRS service that you would like to use, you can set up your LRS credentials by navigating to this area. Choose Create Credentials and complete the fields. The information will be available through your LRS service. For more info, click here.
12. WebGL: If you have a WebGL version of your training app (training done in browser) it can be configured here. Then you can associate it with a Module. Speak to Motive staff if you have further questions on this topic. For more info, click here.
13. Applications: This feature works in conjunction with Launch Pad allows you to set up a configuration that will give you a code to launch a whole app from launchpad. You can find more information on this topic in the following articles: Using Launch Pad to Launch Apps and Configuring a Launch Module for LSDK.
14. Devices: VR Headsets (Devices) are provisioned within Launch. For a given device you can see the errors, warnings, and debug statements as training is in session. Click on the View Details button next to the device name. This is very helpful information to send Motive staff when a support ticket is created to assist with resolving issues on the developer side. For more information, click here.
15. Admin: In this area, Admins can see and edit Launch Spaces. For more information, click here.
| Info |
|---|
The majority of the features in this area are for distributing, understanding, and managing VR training. Therefore, please refer to the Launch Essentials Pathway in Motive Academy for further information. |