E2 Shop System Private AI Layer Blueprint Generator
This generator produces a structured architecture plan for adding a private AI assistant to E2 Shop System without moving data to a public cloud. It captures your version, database, hosting model, users and sensitive data, and returns a document you can send to IT and security. Export it as PDF or Word.
Fill in
E2 Shop System Private AI Layer Blueprint Generator
Private AI Layer Blueprint: E2 Shop System
Prepared for: Summit Sheet Metal Co
Scope: a private AI assistant for Not sure running on Microsoft SQL Server, hosted as: On-prem server. Named users: 60. Sites or plants: 1. Target go-live: Q1 2027 for read-only phase.
Principle: the assistant reads from a copy of the system, runs open-weight models on infrastructure the company controls, and changes data only through supported interfaces after a named person approves.
1. Context and use cases
Use cases in scope: Quote history retrieval, jobs due this week, material on order, last price paid, customer PO lookup.
Data that must never leave the site: Quoted margins, actual job cost, customer drawings, payroll data.
Available GPU: None yet.
2. Components
| Component | Design for E2 Shop System | Notes |
|---|---|---|
| Data access path | Read-only account on a database copy exposing an ai schema of views; E2 screens or supported import for approved writes | Read-only account; no direct writes to application tables |
| Retrieval index | Local vector store over documents and long-text fields, tagged with customer, job and document class | Embedding model runs locally |
| Model serving | Open-weight model on vLLM or Ollama, GPU: None yet | Sized for 60 named users; see sizing calculator |
| Tool server | Approved parameterised read actions exposed through MCP or similar | Every call logged; limits on rows returned |
| Identity and permissions | E2 user mapped to a role with views and index chunks filtered by role | Scope applied to queries and retrieval filters |
| Audit | Append-only log of user, prompt, tool calls, rows returned and answer | Retained on site per company policy |
3. Security controls for Summit Sheet Metal Co
Hosting: On-prem server. All inference, embeddings and indexes stay inside this boundary.
Data that must not leave: Quoted margins, actual job cost, customer drawings, payroll data. This data is excluded from any external service, and outbound network access from the AI components is blocked or limited to an allow list.
Access: users sign in through the company identity provider; the assistant enforces the same data scope as the system for each user. Database credentials are held in a vault and the account is read-only.
Write-back: disabled in phases 1 and 2; in phase 3 only for named actions, through supported interfaces, with human approval showing the exact change.
4. Rollout phases
| Phase | Scope | Exit criteria |
|---|---|---|
| 1: Read-only questions | Status and lookup questions over the use cases above, with the query shown to the user | Accuracy measured on a test set agreed with power users; scope tests pass |
| 2: Documents and drafts | Document Q and A and drafted messages or transactions that a user enters manually | Citations verified; no cross-scope leakage in tests |
| 3: Approved actions | A short list of write actions through supported interfaces with approval | Each action signed off by the business owner and IT |
5. Open questions for IT
1. Which database edition, version and replication options are licensed for Microsoft SQL Server? 2. Who owns the read-only copy and its refresh schedule? 3. Which identity provider and groups map to roles for 60 users across 1 site(s)? 4. Where will the GPU host sit, and how are model files approved and updated? 5. What is the retention period for audit logs? 6. Which customer or regulatory commitments restrict where data may be processed?
This is a planning document, not a security certification or legal advice. Table and API details differ by release, so verify each data access detail against your own system before building.
Get this blueprint reviewed
Send the exported plan and a Netray engineer will review it against your E2 Shop System setup and flag gaps. Optional; the generator is free without it.
Optional. The tool and every export work without this. No spam.
How to use the generator
Fill in the company, version, database, hosting model, user and site counts, and the use cases you want first. List the data that must never leave the site as specifically as you can, because the security section is built from it. Then export the document and use it as the agenda for a review with IT, security and the business owner.
- Start with two or three use cases, not ten
- Be specific about restricted data classes
- Pick the hosting model your policy allows
- Share the open questions with IT before the meeting
What the blueprint contains
The plan sets out the context, a component table (data access path, retrieval index, model serving, tool server, identity and audit), the security controls mapped to your inputs, a three-phase rollout and a list of open questions. The component choices follow a common pattern: read from a copy, retrieve documents locally, serve an open-weight model on your GPUs, and log everything.
- Data access path: Read-only account on a database copy exposing an ai schema of views; E2 screens or supported import for approved writes
- Identity: E2 user mapped to a role with views and index chunks filtered by role
- Phases: read-only, drafts, approved actions
Reading the output critically
Treat the blueprint as a starting hypothesis. Table names, interfaces and replication options vary by release, so have your administrator confirm each data access item. Check licensing for any database replication feature you plan to rely on, and decide who will own the model host, the index and the audit log after go-live.
Common mistakes
Teams often start by pointing the model at the production database, letting write-back arrive in the first release, or skipping role tests. Another frequent error is ignoring documents: much of the value is in drawings, certificates and procedures that never sat in the database.
- Production database used for AI queries
- No role or scope tests before go-live
- Write-back enabled too early
- No owner for the audit log
Frequently Asked Questions
Is this blueprint specific to E2 Shop System?
The data access path, identity mapping and component notes are tailored to E2 Shop System, but you should still verify table names, interfaces and licensing against your own release before building.
Does the plan require a public cloud?
No. The design keeps inference, embeddings, indexes and logs inside your boundary. You can choose on-prem server, private cloud or air-gapped hosting in the form.
Can I give the output to my security team?
Yes. It is formatted for sharing and lists controls and open questions. It is a planning document, not a certification, so your security team will still apply its own review.
Do I need a GPU before I start?
No. The form accepts none yet. The sizing calculator estimates GPU count from your usage, and a pilot can start on a single 24 GB or 48 GB GPU.
Netray builds private AI layers for shops running E2 on-prem, including quote retrieval. If you want this blueprint checked against your E2 version and database, ask for an expert review.
Related Tools
E2 Shop System AI Assistant Sizing and Value Calculator
Estimate peak concurrency, GPU count, index size, hours saved and payback for a private AI assistant on E2 Shop System.
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 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 QAD EE, ready to share with IT and security.
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 AI Assistant Sizing and Value CalculatorEstimate peak concurrency, GPU count, index size, hours saved and payback for a private AI assistant on E2 Shop System.
- JobBOSS Classic 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 JobBOSS Classic, ready to share with IT and security.
- 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 AI agents to ECI E2 Shop SystemHow to add AI agents to ECI E2 Shop System: a read-first tool layer over the E2 SQL database, human approval on writes, and a private on-prem model option.
- 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.