E2 Shop System AI Assistant Sizing and Value Calculator
This calculator estimates what a private AI assistant on E2 Shop System needs in GPUs and index storage, and what it might be worth in saved time. Enter your usage and assumptions; the formulas are stated so IT and finance can check them.
Your numbers
Licensed or named E2 users who could use the assistant.
Includes retrieved rows or document chunks placed in the prompt.
Wall time per question under load; used for concurrency.
Batched throughput of your model on your GPU. Measure with your own model; this is an assumption.
Depreciation, power, space and support, or rental rate.
Your results
Planning estimate only. Tokens per second per GPU depends on model, quantization, context length and serving settings; measure your own. Time-saved figures are assumptions to be validated in a pilot.
Monthly value and GPU cost vs named users
Sweeps Named users from 10 to 300, holding your other inputs fixed.
Validate these numbers with a pilot
Netray can measure real throughput and time saved on your E2 Shop System data. Optional; the calculator is free without it.
Optional. The tool and every export work without this. No spam.
How to use it
Start with named users and the share active on a typical day, then estimate questions per active user. Set average prompt plus answer tokens high enough to include retrieved rows or document chunks, since those dominate. Enter the tokens per second your chosen model achieves on your GPU; if you do not know it, run a short benchmark in vLLM or Ollama.
- Defaults reflect a typical E2 site
- Change one input at a time
- Use the chart to see how cost and value scale with users
The formulas
Questions per day equals users times active share times questions per user. Peak concurrency is the busiest-hour questions divided by 3600 times seconds per answer. GPUs equal peak tokens per second divided by tokens per second per GPU, rounded up, with one spare added to cost. Index size assumes about 2 chunks per page at 6 KB each. Hours saved use 21 working days per month.
- Concurrency = (questions per hour / 3600) x seconds per answer
- GPUs = ceil(peak tokens per second / GPU throughput)
- Value = hours saved x loaded hourly cost
Reading the results
If net monthly benefit is negative, either usage is too low for the hardware or the time-saved assumption is optimistic. Small deployments often fit on one GPU, so the spare GPU doubles the cost; a smaller model or shared hardware can change the answer. Treat payback as directional and confirm minutes saved by timing a few real tasks in a pilot.
Common mistakes
Sizing on named users instead of concurrency overstates GPUs. Ignoring retrieved context understates tokens. Counting every minute saved as cash overstates value; time saved only becomes money if it is redeployed.
- Assuming all saved time is cashable
- Using vendor peak throughput instead of measured throughput
- Forgetting redundancy and maintenance
- Forgetting document volume when sizing storage
Frequently Asked Questions
How is the GPU count calculated?
Peak tokens per second needed in the busiest hour, divided by the aggregate tokens per second one GPU delivers with batching, rounded up to at least one. Measure throughput with your own model; the default is an assumption.
Why is a spare GPU included in cost?
A single GPU is a single point of failure for the assistant. The cost line adds one spare so you see a redundant design; remove it mentally if you accept downtime or run a smaller pilot.
Is the value figure real savings?
It is the loaded cost of time saved. It becomes cash only if the time is redeployed or avoids hiring or overtime. Validate minutes saved per question with a pilot.
How accurate is the index size?
It is a rough estimate based on about 6 KB per chunk and 2 chunks per page. Embedding dimension, chunking and metadata change it, but for most deployments it is within a factor of two.
Netray can run a short pilot on your own E2 data to replace these assumptions with measured numbers. Ask for a review of your sizing if you want a second opinion.
Related Tools
E2 Shop System Private AI Layer Blueprint Generator
Fill in your version, database, hosting and use cases to get an architecture plan for a private, on-prem AI assistant on E2 Shop System, ready to share with IT and security.
On-Prem AIPrivate AI Total Cost of Ownership Calculator
Model the full 3-year cost of an on-prem AI deployment, including amortized hardware, power, staff time, and support, against comparable API spend.
On-Prem AIQAD EE AI Assistant Sizing and Value Calculator
Estimate peak concurrency, GPU count, index size, hours saved and payback for a private AI assistant on QAD EE.
More On-Prem AI tools
See all- On-Prem LLM Total Cost of Ownership Calculator
- GPU Sizing Calculator for LLM Inference
- On-Prem vs Cloud AI Cost Comparison Calculator
- Self-Hosted LLM Hardware Estimator
- Air-Gapped AI Readiness Assessment
- LLM API vs Self-Hosted Cost Calculator
- RAG Infrastructure Sizing Calculator
- Open-Weight Model Selector
- On-Prem AI ROI Calculator
Keep exploring
Free tools
- E2 Shop System Private AI Layer Blueprint GeneratorFill in your version, database, hosting and use cases to get an architecture plan for a private, on-prem AI assistant on E2 Shop System, ready to share with IT and security.
- JobBOSS Classic AI Assistant Sizing and Value CalculatorEstimate peak concurrency, GPU count, index size, hours saved and payback for a private AI assistant on JobBOSS Classic.
- JobBOSS to E2 Shop System Migration ChecklistA practical checklist for moving a small shop from JobBOSS to E2 Shop System, from data audit through cutover and first month close. Works in reverse too.
ERP fixes and how-tos
- How to Add a Private AI Layer to E2 Shop System On-PremHow to add a private on-prem AI assistant to E2 Shop System: database views, quote and job data, document retrieval, role scope, sizing and phased rollout.
- How to Create a Quote in E2 Shop SystemHow to build a quote in E2 Shop System, from header setup through routing, material, and outside processing, to converting an accepted quote into a job.
- E2 Shop System Error 5093: Causes and How to TroubleshootE2 Shop System (Shoptech) error 5093: how to isolate whether it is a database, permission, driver or network problem, and the checks to run before calling support.
Guides
- Job Shop ERP Comparison: JobBOSS, E2 Shop System, ProShop and Global ShopJob shop ERP comparison for CNC machine shops: JobBOSS2, E2 Shop System, ProShop, Global Shop Solutions and Epicor Kinetic, and the questions to ask.
- ERP for Metal Fabricators: What the System Must HandleERP for metal fabricators and sheet metal shops: nested material, multi-level BOMs, heat number traceability, outside processing, and shop floor data.
- ERP for Forging Companies: Requirements and System OptionsWhat a forging ERP must handle: heat number traceability, billet yield, die tracking, furnace batches and outside heat treat, and how common systems compare.
AI on your ERP
- AI for ECI JobBOSS2 and E2 Shop SystemAdd AI to ECI JobBOSS2 or E2 Shop System for faster quoting, tighter scheduling, and shop-floor answers, without sending your job data to the cloud.
- AI for E2 Shop System in Metal Fabrication: Quote History, Material Yield and Delivery RiskPrivate AI for E2 Shop System fabricators: sheet and plate quoting history, nesting yield, welding job costs and delivery risk, answered from your own data.
Integrations
- How to add an AI chatbot to ECI E2 Shop SystemHow to add an AI chatbot on top of ECI E2 Shop System for staff and customers, grounded in E2 data, role-aware, and able to run fully on-prem with open models.
- How to use Claude with ECI E2 Shop SystemHow to use Claude with ECI E2 Shop System: MCP connectors, Anthropic API, AWS Bedrock or Vertex options, data handling, and the on-prem alternative.
Software
- ECI E2 Shop SystemIndependent profile of ECI E2 Shop System, a job shop ERP: what it does, core modules, integration options, strengths, limits, alternatives and AI use cases.
- ECI JobBOSS2Independent profile of ECI JobBOSS2, a job shop ERP: what it does, main modules, integration options, strengths, limits, alternatives and where AI can help.