SYSPRO AI Assistant Sizing and Value Calculator
Estimate GPUs, index size and monthly value for a private AI assistant on SYSPRO. Enter your named users, usage pattern and cost assumptions to see peak concurrency, daily token volume and payback. It uses plain formulas you can check and change.
Your numbers
Share of named users who ask the assistant something on a given day.
Includes retrieved context. Short SQL answers run lower; document questions run higher.
Time the user would otherwise spend finding the answer. Measure it in a pilot.
Amortised hardware plus power and hosting per GPU, or the monthly rate for private cloud GPUs.
Aggregate throughput with batching for your chosen model and quantization. Measure with vLLM on your hardware.
Your results
Planning model. Formulas: questions/day = users x active share x questions each; tokens/day = questions x tokens; GPUs = ceil(peak-hour tokens per second / tokens per second per GPU); value = questions/day x 22 working days x minutes saved / 60 x hourly cost. The 20% peak-hour share and 20 second request time are fixed assumptions. Validate throughput with your own model and prompts.
GPUs needed vs questions per active user
Sweeps Questions per active user per day from 2 to 60, holding your other inputs fixed.
Validate my sizing
Optional: have the numbers checked with a measured pilot on your hardware. The calculator works fully without it.
Optional. The tool and every export work without this. No spam.
How to use it
Enter the number of named SYSPRO users and the share who use the assistant daily. Add questions per active user, average tokens per question, documents and pages for the index, minutes saved, loaded hourly cost and GPU monthly cost. The tokens per second per GPU input is the most important assumption, so replace the default with a number from a test on your hardware.
- Start with a pilot group size and read hours saved.
- Raise tokens per question if you use long documents.
- Use the chart to see how demand scales with users or usage.
The method behind it
Daily tokens are questions times tokens per question. Peak load assumes 20% of daily questions land in the busiest hour, converted to tokens per second and divided by per-GPU throughput. Concurrency uses the same arrival rate times a 20 second request time. Index size assumes about three chunks per page, each around 9 KB for text and vectors. Value is minutes saved converted to hours, times 22 working days and hourly cost.
How to read the result
Typical SYSPRO questions are stock by warehouse, order and job status, shortages and purchase receipts, so many answers are short SQL results plus a few lines of explanation. If the GPU count is one, plan a second for resilience once the assistant is relied on. If payback days exceed 30, either the usage is low, the time saved is small, or the hardware is oversized for the load.
Common mistakes
Counting named users as active users, ignoring retrieved context in the token count, trusting vendor throughput numbers for a different model, and claiming time saved without a pilot measurement. Another is forgetting that model quality, not just speed, decides whether people keep using the tool. Treat value as a hypothesis until a pilot confirms it.
Frequently Asked Questions
Why is tokens per second per GPU an input?
It depends on the model, quantization, context length and batching. Public numbers rarely match your workload, so measure with vLLM on your hardware and enter the sustained figure.
Does the GPU estimate include redundancy?
No. It is the minimum for peak-hour load. For a production assistant, add at least one spare GPU or a failover plan.
How reliable is the value figure?
It is only as good as minutes saved per question. Measure that in a pilot by timing a sample of tasks with and without the assistant.
What does the index size include?
An estimate of text chunks and vectors for the documents you enter. It excludes the ERP database copy, which is sized separately by your DBA.
Want these numbers tested against your real SYSPRO data and prompts? Netray can run a measured pilot on your own GPUs and report throughput and accuracy.
Related Tools
SYSPRO Private AI Layer Blueprint Generator
Generate a shareable architecture plan for adding a private, on-prem AI assistant to SYSPRO: read replica, e.net business objects, retrieval index, local model serving, permissions and audit.
On-Prem AIOn-Prem GPU Sizing Calculator for ERP AI
Work out how much GPU memory and how many cards you need to serve an open-weight model to your ERP users on-prem.
On-Prem AIvLLM Throughput Estimator
Estimate aggregate tokens-per-second throughput for a vLLM deployment from model size, GPU class, and batch depth, accounting for continuous batching gains.
On-Prem AIOn-Prem AI ROI Calculator
Turn hours saved per employee into annual net benefit, payback months, and 3-year ROI for an on-prem AI investment.
More Other ERPs tools
See all- Infor VISUAL Work Order Status and Structure Reference
- Infor VISUAL Manufacturing Scheduling Checklist
- Infor XA (MAPICS) Period End Close Checklist
- Infor VISUAL Database Table Reference
- Infor XA (MAPICS) Application Module Reference
- IBM i Commands for Infor XA Administrators Reference
- Acumatica Generic Inquiry Design Template
- Acumatica Manufacturing Edition Setup Checklist
- Sage X3 Import Template Worksheet
Keep exploring
Free tools
- SYSPRO Private AI Layer Blueprint GeneratorGenerate a shareable architecture plan for adding a private, on-prem AI assistant to SYSPRO: read replica, e.net business objects, retrieval index, local model serving, permissions and audit.
- Infor XA AI Assistant Sizing and Value CalculatorSize the GPUs and estimate the monthly value and payback of an on-prem AI assistant for Infor XA users.
- SYSPRO Month-End Close ChecklistTick-off checklist for closing a period in SYSPRO across inventory, purchase orders, WIP, receivables, payables and the general ledger.
ERP fixes and how-tos
- How to Add AI to SYSPRO On-Prem Without Moving Your DataReference architecture for adding a private AI assistant to on-prem SYSPRO: SQL Server read replica, e.net business objects, retrieval, local GPU and audit.
- How to update SYSPRO (and how to check the latest version)Find your SYSPRO version, learn how releases and updates are named, and follow a safe sequence to update a SYSPRO 8 installation with a rollback plan.
- SYSPRO API integration: e.net business objects, REST, EDI and OfficeHow to integrate with SYSPRO 8: e.net business objects, web service and REST options, EDI and Office integration, with a table of which route fits which job.
AI on your ERP
- AI for SYSPRO production and job costingHow AI reads SYSPRO WIP jobs, labor and material postings to explain job cost variances and late work orders, with read-only access and on-prem hosting.
- AI for SYSPRO Manufacturing Operations: From Work Centers to AnswersSYSPRO Manufacturing Operations generates data on work centers, routings, and WIP - see how private AI turns it into shop floor answers on-prem.
Integrations
- How to add an AI chatbot to SYSPROAdd an AI chatbot to SYSPRO for staff and customers: grounded in e.NET and SQL data, role-aware answers, portal embedding, and fully on-prem with open models.
- How to use ChatGPT with SYSPROHow to use ChatGPT with SYSPRO: exporting data vs live access, custom GPT actions over a SYSPRO API, enterprise data controls, and when a private model is better.