Legal

Fair Usage Policy

Applies to all MAGES VTC SIM Title Licenses — Last updated: April 2026

💡

The short version

A SIM Title License is a flat annual fee — it does not depend on how many users you have or how many hours they train. You pay once per title, per year, and your entire organisation can use it freely. This policy simply prevents the license from being used to serve people outside your organisation or to resell access to others.

Contents

  1. What this policy covers
  2. How SIM Title Licensing works
  3. What is allowed
  4. MAGES SIM Builder — Simulation Content Limits
  5. MAGES VTC — Usage Limits (By Tier)
  6. Actions Library Reference
  7. Enforcement
  8. Questions

1. What this policy covers

This Fair Usage Policy applies to all SIM Title Licenses issued as part of a MAGES Virtual Training Center (VTC) subscription. It does not apply to Platform Licenses (per-user seat licenses), which are governed by the standard subscription agreement.

The purpose of this policy is to define what constitutes normal, intended use of a SIM Title License — and to be clear about the boundaries that protect the value of the license model for all customers.

2. How SIM Title Licensing works

When you license a SIM title, you pay a single flat annual fee for that title. This fee is:

All users covered by your Platform License can access any SIM title you have licensed, as many times as needed, for the duration of the annual license period.

This is intentional. We want you to train as much as possible. The flat fee model exists so that cost is never a reason to limit training.

3. What is allowed

The following uses are fully within the scope of a SIM Title License:

4. MAGES SIM Builder — Simulation Content Limits

The following limits apply when creating a new simulation using MAGES SIM Builder. They define the scope of content and complexity included under fair usage per licensed title.

Category Description Fair Usage Limit
Simulation Session Duration Maximum continuous time for a single XR training session. Up to 30 minutes per scenario walkthrough (average).
Simulation Actions Procedural or behavioral actions within one simulation. Up to 30 distinct user-triggered interactions (e.g., insert, cut, remove, activate, select).
Custom Mechanics Simulation logic or interactive behavior not available in the standard MAGES SUITE SDK. Available upon request (may incur additional development costs and delivery time depending on complexity).
Anatomical 3D Models Access to detailed, modular human anatomy via the MAGES VAPPS (Virtual Anatomical Patient & Props System). Includes full-body anatomical systems for both male and female models: Cardiovascular, Circulatory, Digestive, Endocrine, Integumentary, Muscular, Nervous, Reproductive, Respiratory, Skeletal, and Urinary.
3D Surgical Tools & Devices Use of surgical instruments, implants, life-support machines, and other medical devices provided within the ORamaVR standard asset library. Unlimited use of available library items; custom tool creation available upon request; subject to scope and complexity.
Custom 3D NPCs Non-player characters (NPCs) created based on Subscriber's specifications (e.g., clinicians, patients, assistants). Up to 3 custom NPCs per simulation*.
Custom 3D Models Additional 3D objects not in the standard library. Up to 50 custom models per simulation*.

*Complexity and optimization level may affect total number of allowable models.

Simulation workflows may be linear or branching, including conditional logic, decision trees, or randomized outcomes. All logic types are supported under Fair Usage if the total number of user-triggered actions per SIM does not exceed the defined limit (30 actions). Exceeding this threshold may impact delivery time and pricing. Simulation performance varies depending on the XR device used. Each SIM is optimized and validated for performance on supported headsets, but rendering quality, latency, and interaction responsiveness may differ based on the technical specifications and limitations of each HMD model.

5. MAGES Virtual Training Center — Usage Limits (By Tier)

The following limits apply per licensed user per month. Each tier reflects the size of your organisation.

The VTC tab shows limits for running live training sessions. The Custom SIM tab shows additional limits that apply only if you have built your own simulation using MAGES SIM Builder and are deploying it to your VTC — simulations taken directly from the MAGES library are not subject to these limits.

Tier 1: Up to 5 users
  • JARIA voice (speech-to-text): 10 hrs/month
    Voice input from trainees to JARIA during sessions
  • JARIA voice (text-to-speech): 20 hrs/month
    JARIA speaking feedback and guidance to trainees during sessions
  • Analytics sessions: 150 sessions/month
    Post-session data uploaded to the ORamaVR portal for review and reporting
  • Multiplayer (Photon): Up to 5 concurrent users
    Maximum simultaneous users in a shared XR session
Tier 2: Up to 50 users
  • JARIA voice (speech-to-text): 50 hrs/month
    Voice input from trainees to JARIA during sessions
  • JARIA voice (text-to-speech): 100 hrs/month
    JARIA speaking feedback and guidance to trainees during sessions
  • Analytics sessions: 1,500 sessions/month
    Post-session data uploaded to the ORamaVR portal for review and reporting
  • Multiplayer (Photon): Up to 50 concurrent users
    Maximum simultaneous users in a shared XR session
Tier 3: Up to 99 users
  • JARIA voice (speech-to-text): 100 hrs/month
    Voice input from trainees to JARIA during sessions
  • JARIA voice (text-to-speech): 300 hrs/month
    JARIA speaking feedback and guidance to trainees during sessions
  • Analytics sessions: 3,000 sessions/month
    Post-session data uploaded to the ORamaVR portal for review and reporting
  • Multiplayer (Photon): Up to 99 concurrent users
    Maximum simultaneous users in a shared XR session
Tier 4: 100+ users
  • JARIA voice (speech-to-text): 200 hrs/month
    Voice input from trainees to JARIA during sessions
  • JARIA voice (text-to-speech): 600 hrs/month
    JARIA speaking feedback and guidance to trainees during sessions
  • Analytics sessions: 6,000 sessions/month
    Post-session data uploaded to the ORamaVR portal for review and reporting
  • Multiplayer (Photon): 100+ concurrent users
    Maximum simultaneous users in a shared XR session

Per-user limits mean that each licensed user has access to their own usage pool. Sharing logins to bypass limits is prohibited under the Fair Usage Policy. Multiplayer concurrency limits refer to the maximum number of users participating simultaneously in a single shared XR session. JARIA knowledge base creation assumes an average of ~1,500 characters per page.

Actions Library Reference

The following action types count toward the 30-action fair usage limit per simulation.

Action Type Example
InsertPlace the scalpel on the table.
RemovePull the cap of the bottle.
UseSterilize the patient's hand.
TrajectoryTake the scalpel and cut the skin.
ActivatePump the syringe.
QuestionWhich step comes next?

6. Enforcement

ORamaVR monitors aggregate usage patterns through the VTC analytics platform. In cases where usage patterns suggest activity outside the scope of this policy, ORamaVR reserves the right to:

Our intent is always to find a licensing structure that works for the customer. Enforcement action is a last resort, not a first response.

7. Questions

If you are unsure whether a specific use case falls within this policy, please ask before proceeding. We would rather clarify upfront than have an issue arise later.

Contact us at info@oramavr.com or through the contact form on our website.