Engineering & PLMFree calculatorPDF, Excel, Word exportAutodesk Vault Professional

Autodesk Vault AI Assistant Sizing and Value Calculator

This calculator sizes a private AI assistant on an on-prem Autodesk Vault: GPUs, daily tokens, index storage and payback. It suits teams from a few dozen to a few hundred users.

Your numbers

users
35 %
$/h
$/GPU/month
$

Your results

GPU estimate
1
Monthly value
$23,153
Daily active users
32
Questions per day
221
Tokens per day
617,400
Peak concurrent requests
0.3063
25% of daily questions in the busiest hour, about 20 seconds per answer.
Vector index size
5.76
2 chunks per page and about 6 KB per chunk.
Hours saved per month
386 hrs
Monthly GPU cost
$1,100
Simple payback
1.4 months

Planning estimate. Confirm throughput on your hardware and minutes saved in a pilot.

Save results:

Tokens per day by named users

Sweeps Named users from 20 to 1000, holding your other inputs fixed.

Index build and sizing notes

Optional: notes on planning the initial index build for a larger Vault.

Optional. The tool and every export work without this. No spam.

How to use it

Enter named users, daily active share and questions per user from pilot logs if you have them. Set tokens per question to match your retrieval depth. Enter GPU cost as a monthly equivalent. The chart shows how daily token volume grows with users.

Formulas and assumptions

Questions per day equal users times active share times questions per user. Tokens per day multiply that by tokens per question. Peak concurrency assumes 25 percent of questions in the busiest hour at about 20 seconds each. GPU count is the larger of the model floor and peak streams times 25 tokens per second divided by GPU throughput.

Reading the result

Daily tokens help you size throughput, but peak concurrency drives GPUs. The index estimate counts only text-bearing documents, so enter PDFs and Office files, not every CAD file. Payback is shown as zero when value does not exceed GPU cost.

Common mistakes

Counting every Vault file as a document, using average rather than busy-hour load, and ignoring Job Processor and embedding capacity during the initial index build, which can be heavy for a large vault.

Frequently Asked Questions

How long does the first index build take?

It depends on file counts, parsing speed and hardware. Large vaults can take hours to days. Plan the build outside working hours and keep it separate from the live assistant's GPU.

Should the index include old revisions?

Usually only released and latest working versions. Old revisions add size and can mislead answers unless chunks are labelled with revision and state.

What if the result shows one GPU?

That is common. Consider failover separately, since a single GPU is a single point of failure for the assistant, though not for Vault itself.

Can I trust the monthly value?

Only as much as the minutes-saved input. Measure it with timed tasks and apply a realistic adoption rate.

Netray can compare these results with a measured pilot on your Vault. The calculator is usable on its own.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Software