AR & VR Control Center — bRRAIn Docs

Integrated AR and VR headset and glasses control plane for immersive bRRAIn surfaces.

AR & VR Control Center

A control plane for connecting AR glasses and VR headsets to your bRRAIn — pushing scene data, streaming Handler responses, and routing operator commands.

What it does

Most enterprise AR / VR deployments hit the same wall: the headset is great, but tying it back to a system of record is hard. The Control Center handles:

  • Device fleet management — register devices, assign to operators, track location and state.
  • Session orchestration — match an operator with a headset to a bRRAIn organization and a scene context.
  • Streaming pipelines — high-fidelity scene streaming from your bRRAIn back to the headset.
  • Voice and gesture intake — captured input reaches the bRRAIn Handler.
  • Spatial annotation — operators drop markers in 3D that bRRAIn records as graph entities.

Use cases

  • Field-service technicians wearing AR glasses get bRRAIn-summarized procedure steps overlaid on equipment.
  • Training sessions in VR rehearse high-stakes procedures with bRRAIn-driven scenarios.
  • Remote-expert assistance — an operator in HQ shares an AR view with a field technician.
  • Operations-center walkthroughs of the digital double.

Installing

Per-organization subscription with per-device entitlement. Pairs naturally with 3D Digital Double Control & Simulation Center.

After install:

  • A device-fleet page appears under your Console.
  • The first-time wizard walks you through registering your first device.

Supported devices

  • VR headsets — Meta Quest 2/3/Pro, HTC Vive, Valve Index, Pimax.
  • AR headsets — Apple Vision Pro, Microsoft HoloLens 2, Magic Leap 2.
  • AR glasses — Xreal, Vuzix, Rokid.
  • Mobile AR — iOS ARKit and Android ARCore via a companion mobile app.

Device registration

Each device registers via a short pairing flow:

  1. Open the bRRAIn AR/VR companion app on the device.
  2. Sign in.
  3. The device shows a one-time code.
  4. In the Console, paste the code into the Pair device dialog.
  5. Assign the device to an operator (or to a pool).

Scene streaming

The Control Center streams scene data from your Vault and from the Digital Double extension to the device:

  • Equipment models with state overlays.
  • Procedure steps with checkmark progression.
  • Operator instructions with TTS readback.
  • Real-time telemetry overlays.
  • Remote-expert annotations.

Bandwidth and rendering quality are tuned per-device class. Tethered headsets (Vision Pro, HoloLens) get full-fidelity streams; standalone headsets get adapted streams.

Voice and gesture

Captured audio is streamed to the bRRAIn Handler for transcription and response. Handler responses are returned as TTS audio.

Gestures (point, select, pinch, swipe) drive in-scene interaction and can fire bRRAIn actions (mark a record, fire a workflow, summon an expert).

Spatial annotation

Operators in AR can drop spatial markers in the world. Each marker becomes a bRRAIn record with:

  • Spatial coordinates (lat/long for outdoor, room-relative for indoor).
  • The capturing operator and timestamp.
  • An audio note.
  • An optional photo.
  • Tags pulled from the surrounding context.

Markers can persist (visible to others later) or be ephemeral (one-session only).

Remote expert

A remote expert (typically in the Console) can drop into the operator's scene as a co-present avatar:

  • See exactly what the operator sees.
  • Annotate the scene; the operator sees the annotations live.
  • Talk through voice.
  • Trigger bRRAIn actions on behalf of the field operator (with approval-gate enforcement).

Device cameras and microphones can capture sensitive data. The Control Center enforces:

  • A green LED on devices when streams are live.
  • Audible chimes on session start and end.
  • Per-session capture-and-retain policies.
  • Geofenced auto-disable in privacy zones.

Scopes required

  • Read and write in the extensions/ar-vr zone.
  • Read access to the Digital Double scene library (when paired).
  • Permission to spawn one non-human actor per registered device.

Where to next