The video provides an overview of the elements that make up the WorkLink toolset within Scope AR, focusing on how it fits into augmented reality (AR) use cases.
Components of WorkLink Toolset:
WorkLink Create (Authoring Platform):
- Browser-based authoring platform where creators build AR experiences starting from 3D information.
- Authors focus on creating AR content for training and other applications.
WorkLink App (Execution Platform):
- End users interact with the WorkLink app, executing and viewing AR experiences authored in WorkLink Create.
- Allows for remote assist or calling functionality, enabling users to share AR experiences and augment their field of view.
Analyze (Content Management System - CMS):
- Refers to the Content Management System where all data for AR experiences, projects, and user interactions is stored.
- Represents the centralized storage center for managing AR content.
- A visual representation of the entire architecture is presented.
- WorkLink Create (yellow icon) for authoring, WorkLink App (gray icon) for end-user execution, and the WorkLink CMS for data storage and management.
Project vs. Scenario Distinction:
- Initiated in WorkLink Create, contains all information related to a specific AR experience.
- Exported as a zip file, shareable between authors.
- Generated from a completed project, exported as a Dot scope file.
- Represents the final, viewable version of an AR instruction in the WorkLink App.
- Cannot be edited in Create, serves as the compressed, exported version for end-user viewing.
- Describes the interaction between WorkLink Create and the project data during authoring.
- Completed projects follow a gray line to become scenarios for end-user consumption.
Usage Data Generation:
- When end users view instructions in the WorkLink App, usage data is generated, represented by a blue line.
- This data reflects how users engage with and view the AR instructions.
In conclusion, this module summarizes the basics, including opening the WorkLink app, understanding end-user experiences, and establishing a shared vocabulary. Concepts such as linear vs. non-linear experiences, Standalone mode, Device mode, and Interactive mode are introduced, along with an overview of the entire solution architecture.