Strivr platform setup

To understand the different components of the Strivr platform setup, first refer to the Strivr System Overview page for a high-level overview of the Strivr platform. For more detailed information on Strivr systems architecture, please reach out to your Strivr account representative.

Strivr Cloud

Prior to setting up the customer tenant, Strivr’s Customer Engineering team works with customers to highlight prerequisites and give recommendations on Customer MDM (Mobile Device Management) and network setup. Once the prerequisites and best practices are in place, Strivr Engineering works on provisioning a customer-specific tenant. This involves various backend services which support key features of the Strivr platform such as device management, content management, analytics, and third-party content support. Strivr Cloud powers Strivr portal and connectivity from the headsets to the cloud services for key activities such as health check (heartbeat), telemetry uploads and content downloads.

Strivr Portal Access

Once Strivr Cloud services have been set up, the Strivr implementation team works with the customer to obtain access to the Strivr Portal, if applicable. Please reach out to your Strivr account executive or implementation team for more information on portal access.

For a more detailed walkthrough on the Strivr Portal, please refer to Strivr Portal Overview.

The Strivr Portal can be accessed on the following devices and browsers:

Device Browser/Device Type Support
Laptop/PC

 

 Google Chrome ✔
Microsoft Edge ✔
Mozilla Firefox ✔
Opera ✔
Safari ✔
Mobile Devices iPhone ✔
iPad ✔
Android ✔

Locations

Within the Strivr platform, locations represent groups of devices typically available in a geographic business location. Locations allow customers to select a subset of their total headset fleet when deploying content or selecting a unique application settings file. Also, when viewing analytics data in the Strivr Portal, customers can filter data by location.

Customers should develop and maintain a clear and consistent naming scheme for locations across the organization. For example:

  • Alphanumeric location names used within the organization (e.g. 1234-SUP)

  • Public facing store names which are easily identified by end customers. (e.g. 4th and Arnold).

Note: The maximum character limit for the location name is 63 characters

Here are some factors to keep in mind when deciding on a location naming scheme:

  1. Multiple locations can exist within the same physical location

    Because content is deployed to all headsets in a selected location, you may need to create separate locations per headset model if you will be deploying content sets specific to headset models with a location. Similarly, you may need to create separate locations per learner type if each learner type is to receive a specific set of content.

  2. Users of the Strivr Portal need to identify a location by its name

    Because users of the Strivr Portal need to select locations from a list when filtering data, when deploying content to headsets, and more. it’s important that the naming scheme makes sense when viewed in a list.

  3. Some non-location specific headsets may exist

    Some headsets may fall outside of any location and need specific content. For example, an organization may maintain travel headsets that are moved between physical locations, or an organization may maintain a set of headsets for content review or IT testing.

Strivr Content Management

Strivr’s content management functionality deploys content from Strivr Cloud to a customer’s device fleet over the internet. Strivr content is typically deployed to headsets via a WiFi connection, the details of which are available in Network/WiFi setup. Strivr content is securely stored in Android internal storage, and thus is not accessible via a USB connection from an external device. Furthermore, it can only be accessed by Strivr Player (Strivr in-headset software) and not by any other application. For more information, refer to Data and file storage overview. Strivr content is stored locally on the headsets and is playable even when the headset is not connected to WiFi. This mode of operation is called offline mode and is especially helpful when headsets are deployed to locations where there is inconsistent access to the internet. Strivr content can be deployed to devices in the following ways:

Default content is a content set inherited by any new location created within the Strivr Portal or automatically via the location assigner functionality within device setup. Default content ensures that every new location inherits a uniform content set, unless it explicitly needs a unique content set. Once devices are added to locations via the Strivr Portal or during device setup, the default content set gets deployed automatically to the headsets that belong to that location.

This method deploys a specific content set to a specific set of locations that already exist in the Strivr Portal. This method is preferred when new content needs to be deployed to a fleet of devices already assigned to an existing location. This method can also be used for bulk device setup when multiple content sets need to be deployed to multiple locations. In this case however, if there are new locations that do not yet exist, they will have to be created before conducting any location-specific deployments. Refer to this article for a detailed procedure to deploy content to headsets.

Deployment of third-party content is a two step process that comprises both deployment of the content metadata, and the core experience APK file which is remotely installed on a device via the customer’s MDM. For more information on this procedure, refer to this article.

In-Headset Software

During the platform deployment phase, Strivr deploys in-headset software including Strivr Player (the core content runtime application responsible for playing native Strivr and third-party content) and, for Strivr Player versions earlier than 2.0, HMD Manager, a headset manager application. In-headset software is responsible for such key tasks as content download and runtime, telemetry uploads, and device health reporting.

Software Availability

Strivr provides the capability for a customer’s IT administrator to manage and download Strivr Player versions via the Manage Player Version page of the Strivr Portal. Customers can download the latest Strivr Player releases from this page for internal testing and deployment. For more information on the latest Strivr Player releases and corresponding release notes, refer to Strivr System Overview.

Software distribution

Strivr’s platform provides the capability for customers to set up devices with a specific Player version such that when devices are set up for the first time, the provisioning workstation will download the stipulated Strivr Player version from Strivr cloud, preload it to the headset via USB and perform installation followed by registration to the specific customer tenant.

Strivr recommends the customer’s project and IT teams work with the Strivr account team to align on the software versions for Strivr Player and Platform Manager that need to be deployed to the fleet and communicate the correct versions to the provisioning partner, prior to the deployment.

Strivr Player upgrades can also be distributed to existing devices over the air via the customer’s or Strivr’s MDM. This is discussed in detail in the sections below.

Device Setup

Strivr Portal provides the capability to headlessly prepare a device with the configured in-headset software version and content version, and enroll it in the customer’s or Strivr’s MDM system. Device setup is used for the following purposes:

  1. Strivr’s in-house operations team uses device setup to provision headsets on behalf of customers.

  2. Customers can use device setup to prepare and configure devices for their own fleets for specific use cases including content reviews, IT assessment tests, new location deployments, and re-imaging unprovisioned devices.

  3. A customer’s independent implementation partners can use device setup to prepare and configure devices on their behalf.

Please reach out to your Strivr account team to evaluate the device setup use case and get access to this functionality. For more information, refer to the device setup documentation.

Application Settings

Strivr works with the customer to define requirements that drive the in-headset experience for a learner over the course of a training session, and to customize the acclimation experience within the in-headset software. This can include configuration in the following areas:

  • User self-identification functionality and the corresponding format (refer to the Self-Identification section below for more information)

  • The order of or removal of specific acclimation screens pertaining to headset fitting, controller use, handedness selection, health & safety warning etc.

  • Customization of the health & safety warning headers and text.

  • Enablement, disablement, and customization of voice recording consent screens

  • List of available languages and locales

  • Optional telemetry encryption

  • Content throttling limitations (refer to the Content Throttling section below for more information)

Strivr recommends the customer work with the Strivr implementation team to provide requirements for in-headset configuration.

Self Identification

Self identification ties a learning session to a predefined ID which can be an enterprise-wide identifier such as an employee ID.

  • Customers can guide learners by customizing prompt text that appears on the self identification screen.

  • Customers can customize the keyboard to represent an alphanumeric qwerty setup, a purely numeric keypad, or an uppercase character-only keypad.

  • Customers can define the length of the self identification ID.

Content Throttling

Content throttling determines the amount of bandwidth that a headset can consume while downloading content. A customer can configure this setting in the following ways:

  • Define multiple start times and end times within the span of a day.

  • Define a maximum upload speed and a download speed along with the units for each.

  • Define and customize the above two settings for each day of the week.

Keep in mind that the default timezone used by the content throttling functionality in the application config leverages Universal Time Coordinated (UTC).

For more information on deploying and configuring content throttling as part of the Strivr Player settings on the Strivr Portal, work with your Strivr account and technical team.

Default Application Configuration Settings

When a new customer tenant is created, a default application configuration can be assigned to the tenant. This default application configuration is assumed by any new locations that are created during device setup. This functionality is available on the administrative section of the Strivr Portal. Please work with your Strivr account team to define the application configuration that you would like to deploy to your device fleet.

Deploying Application Configuration Settings OTA

Specific application configurations can also be deployed to devices that belong to a subset of existing locations. This use case is especially helpful for testing and content review, when customers may want different settings. A common example is configuring test or content review headset locations with no throttling such that the content can be freely downloaded. This functionality is also available within the administrative section of the Strivr Portal. Please work with your Strivr account team to conduct location specific deployments.