Framework architecture

The AVEVA XR framework is made of Runtime elements, Non-runtime elements, and SDK components.

The Framework

The framework is made of a common layer that abstracts the functionalities and gives a unified access to them and a target specific layer that deals with platform-specific, such IO and rendering.

The SDKs

The XR Framework can be integrated into a third-party solution. It's made available in the form of a nuget (name XR SDK) and currently supports the Windows only. The SDK can be used to directly access and manage a 3D scene, run a pre-built XR application or implement a mixed approach.

The XR Plugin SDK can be used to develop third-party plugins that again are supported only on the Windows target.

The Authoring tools

XR Studio allows you to build application content to be consumed by the XR Framework on a specific or multiple platforms. An application can contain both scene content and logic scripted in one of the two supported proprietary languages: XML or XRS.

The suite includes several tools that have been specifically designed to simplify application development and also a complete set of runtime applications that can run XR content developed inside XR Studio.

The Runtime elements

A runtime element is an application that embeds the XR Framework and that is capable of running an XR application.

There's at least one runtime application for each target. This allows an XR application to be distributed on one or multiple targets leveraging the corresponding runtime.

Some runtime elements can be distributed as part of a project solution while others are platform runtime emulators that can be uniquely paired with XR Studio in order to perform test and debugging.

Note: In the above drawing the emulated runtimes are those having a dashed border.