EpicorFree calculatorPDF, Excel, Word exportEpicor ERP 10Discrete Manufacturing

Epicor ERP 10 AI Assistant Sizing and Value Calculator

This calculator sizes a private AI assistant for Epicor ERP 10 on-prem. It estimates peak GPU need, index size, time saved and payback, using assumptions you can change.

Your numbers

users

Users licensed to use the assistant.

40 %

Share of named users who ask at least one question on a given day.

questions

Pilot logs give the real figure; 5 to 15 is common once habit forms.

tokens

Question, retrieved BAQ rows and document chunks, plus the answer. Smaller models with shorter context keep this near 3,000.

documents

Job packets, drawings, certs and SOPs on the shares Epicor references.

pages

Average across the document set.

minutes

Time saved versus asking a planner or running a BAQ yourself.

per hour

Salary plus benefits and overhead for the people asking.

per GPU per month

Hardware amortised over 36 months plus power, cooling, support and rack space.

tokens/s

Aggregate tokens per second under batching for your model and quantisation. Measure it; this is the most sensitive assumption.

one-time

Integration, document pipeline, security review and pilot.

Your results

GPUs needed (before redundancy)
1
Peak-hour tokens per second divided by throughput per GPU, rounded up. Add a spare GPU if you need failover.
Monthly value
$24,192
Hours saved x loaded hourly cost. Treat as an upper bound until a pilot confirms the time saved.
Questions per day
288
Named users x active share x questions per active user.
Tokens per day
1,008,000
Questions per day x tokens per question.
Peak concurrent requests
1
Assumes 25 percent of daily questions land in the busiest hour and each request holds a slot for about 15 seconds.
Vector index size
2.9491
Gigabytes, assuming 2 chunks per page, 1024-dimension float32 embeddings and 50 percent index overhead. Original files are extra.
Hours saved per month
504 hrs
Questions per day x minutes saved, over 21 working days.
Simple payback
2 months
One-time cost divided by monthly value minus GPU cost. Shows 0 when value does not exceed GPU cost.

Planning estimate only. Tokens per second, time saved per question and peak share vary widely; replace the defaults with measurements from your own pilot before committing to hardware.

Save results:

Simple payback vs minutes saved per question

Sweeps Minutes saved per question from 1 to 15, holding your other inputs fixed.

Epicor ERP 10 sizing review

Optional: send your numbers and get an engineer's second opinion on GPU count, index size and the value assumptions.

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

How to use it

Enter named users, the share active on a typical day and questions per active user. Set tokens per question to include retrieved BAQ rows and document chunks. Enter your one-time implementation cost to see payback, and the sweep shows how sensitive payback is to the minutes saved per question.

  • Smaller plants often fit on one 24 GB GPU
  • Do not count licence holders who rarely log in as active
  • Include integration and security review in one-time cost
  • Compare against simply building more BAQs

The method

Peak load is modelled as 25 percent of daily questions in the busiest hour, converted to tokens per second and divided by GPU throughput. Concurrency assumes each request occupies a slot for about 15 seconds. Index size multiplies documents, pages, chunks per page and a float32 embedding with overhead. Value is hours saved over 21 working days times loaded cost.

Reading the sweep

The payback line falls sharply as minutes saved rise, then flattens. If payback is long at your realistic minutes-saved figure, the case may rest on fewer errors or faster quotes rather than time alone. A value near GPU cost means a smaller model or shared hardware may be the better choice.

Common mistakes

The usual mistakes are applying the busiest-hour throughput from a benchmark to mixed real prompts, ignoring retrieval context in tokens, and treating ERP 10 as static. If an upgrade is coming, keep hardware reusable and BAQ names stable.

Frequently Asked Questions

Is one GPU enough for an ERP 10 plant?

Often yes for 50 to 250 named users with a 7B to 14B model, because peak concurrency is low. Confirm with measured throughput and your busiest-hour question volume before buying.

Why is payback zero in some cases?

Payback shows zero when monthly value does not exceed monthly GPU cost, because the project would not recover its one-time cost. Increase realistic minutes saved or reduce cost, for example with a smaller model or shared hardware.

Does the calculator include licensing?

No. Open-weight models have no per-user licence, but your own server, database and operating system licences are outside this estimate. Add them to one-time or monthly cost if they apply.

How should I estimate minutes saved?

Time a handful of real questions the old way: finding a job status or shortage across screens and BAQs. Use the average of those timings, then discount for questions where the assistant is wrong or incomplete.

If you want the numbers checked against your ERP 10 usage, Netray can review them with you. The calculator needs no contact.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Comparisons

Software