Epicor ERP 10 Private AI Layer Blueprint Generator
This generator produces a private AI architecture plan for an on-premises Epicor ERP 10 installation. It accounts for the release-dependent REST options and defaults to a read-only replica so analytical load stays off production.
Fill in
Epicor ERP 10 Private AI Layer Blueprint Generator
Private AI Layer Architecture Plan: Epicor ERP 10
Prepared for: Northfield Fabrication Inc System: Epicor ERP 10 10.2.700 or later on SQL Server 2016 Hosting: On-prem server Named users: 120 across 1 site(s) Target go-live: 2027-03-01
1. Context and goals
This plan describes a private AI layer over Epicor ERP 10 on premises. Because ERP 10 is an older release line, the plan treats REST generation and authentication options as items to verify and prefers a read-only replica for bulk access.
Main use cases: Open jobs and parts shortages Shipments due this week Vendor late deliveries Inventory by warehouse and bin
Data that must stay on site: Customer prints and quality records Costing and pricing data
GPU position: One 24 GB GPU.
2. Components
| Component | Design for Northfield Fabrication Inc | Notes |
|---|---|---|
| Data access path | Executable BAQs and REST services available on the installed 10.x build; read-only SQL Server copy of the Erp schema for history; Service Connect for scheduled extracts if needed | Confirm which REST generation and authentication options the installed release supports. |
| Retrieval index | Local vector store over job travelers, drawings, certificates and SOPs from file shares referenced by Epicor | Every chunk carries source, site and access tags; untagged content is excluded. |
| Model serving | Open-weight model on vLLM or Ollama, sized for 120 named users on One 24 GB GPU | Model, quantisation and version recorded in the audit log. |
| Tool server | Tool server owning all credentials, exposing reviewed BAQ-backed read actions with row caps | Parameterised read actions only; row caps and column allow lists. |
| Identity and permissions | Restricted integration user plus a maintained mapping from Epicor security groups to companies, plants and BAQs, enforced by the tool server | Unknown users and unmapped content default to no access. |
| Audit | Append-only log of user, prompt, tool call, parameters, row counts and answer | Retained per Northfield Fabrication Inc records policy; reviewed at each rollout phase. |
3. Security controls mapped to your inputs
| Control | Implementation | Driven by |
|---|---|---|
| Data residency | Replica, index and model all inside the On-prem server boundary; no outbound API calls at run time | Data that must never leave the site |
| Least privilege | Reduced Epicor security group for the integration user; read-only SQL login on the replica only | System version and role model |
| Network isolation | Dedicated segment for model and tool servers; only the tool server reaches the data source | Hosting |
| Prompt injection defence | Model receives bounded tool results only; no direct database or file access | Use cases |
| Write-back | Writes only via supported business objects or Service Connect workflows, after human approval of the exact payload | Phase 3 scope |
4. Rollout plan
| Phase | Scope | Exit criteria |
|---|---|---|
| 1: Read-only (weeks 1-6) | Approved read actions and document Q&A for a pilot group at one site | Accuracy review of sampled answers; no permission leaks in adversarial tests |
| 2: Drafts (weeks 7-12) | Summaries, reports and draft documents saved for human completion | Users edit rather than rewrite; audit log reviewed by IT and data owners |
| 3: Approved actions (week 13 onward) | Narrow, reversible transactions via supported interfaces after explicit approval | Rollback tested per action type; owner sign-off per action |
5. Open questions for IT
Which exact 10.x release and patch is in production, and is REST v2 present? Is a readable SQL Server copy available, and how current must it be? Which security groups map to which plants and BAQs? Is an upgrade to Kinetic planned that should shape BAQ naming? Who approves the integration user and its rights? What is the support position on customisations that affect reported numbers?
Approvals
Starting point for discussion, not a design guarantee. REST and authentication capabilities vary across 10.x builds; verify against your installed release before committing to a tool design.
Epicor ERP 10 architecture review
Optional: have an engineer review your generated blueprint against your environment and flag gaps before you buy hardware.
Optional. The tool and every export work without this. No spam.
How to use it
Enter your 10.x release band, SQL Server version, hosting model, user and site counts, and the GPU you have. Describe the use cases as real questions from your team and list data that must not leave the building. The plan is generated as you type; export it to PDF or Word for IT review.
- Find your exact release in Help > About
- Name the data owner for costing information
- Say whether an upgrade to Kinetic is planned
- Leave GPU as None yet if you are still sizing
What the plan contains
Context and goals, a component table (data access, retrieval index, model serving, tool server, identity, audit), controls mapped to your inputs, three rollout phases, open questions for IT, and approvals. Release-dependent items such as REST generation and token support appear as questions to resolve, not assumptions.
Why a replica first
ERP 10 sites often run near capacity on the production SQL Server. A read-only copy gives the assistant freedom to run analytical queries and build an index without competing with shop floor transactions. It also provides a place to apply views that flatten joins, which keeps answers consistent.
- Readable secondary, log shipping or scheduled restore
- State the acceptable data lag in the plan
- Keep live-critical lookups on BAQs
Common mistakes
Typical errors are assuming newer REST features exist on an older build, running the assistant under a manager account, and letting the model write free-form SQL. The plan routes the model through reviewed BAQs and a tool server that owns credentials.
Frequently Asked Questions
Does this assume REST v2 is available?
No. REST generation and token support vary across 10.x builds, so the plan lists them as items to verify. If only an older REST generation is present, the tool server can use it, or fall back to BAQs and the replica.
Should we upgrade to Kinetic first?
Not necessarily. A read-only layer over BAQs and a replica works on ERP 10 now, and well-named BAQs carry over to an upgrade. If an upgrade is funded, align timelines so you avoid rework.
Can the model write to ERP 10?
Only in phase 3 through supported business objects or Service Connect, after a person approves the exact payload. Direct database writes are excluded by design.
Can we run this fully air-gapped?
Yes. Select air-gapped hosting; models, embeddings and containers are staged through a controlled transfer and nothing calls an external service at run time.
If you would like an engineer to check the plan against your ERP 10 build or to deliver it on your servers, Netray can help. The generator is free without contact.
Related Tools
Epicor ERP 10 AI Assistant Sizing and Value Calculator
Estimate GPUs, index size, hours saved and payback for a private AI assistant on Epicor ERP 10 on-premises.
EpicorEpicor REST API v2 URL Builder
Fill in server, instance, company and service to get a ready OData URL, a curl command and the required headers for the Epicor REST API v2.
EpicorEpicor Kinetic Database Tables Reference
Look up the main Erp.* tables in Epicor Kinetic with what each holds and the columns that identify a row. Useful when writing BAQs and SQL.
On-Prem AIGPU Sizing Calculator for LLM Inference
Work out how many GPUs you need to serve a given open-weight model to your user base, based on memory footprint and token throughput.
More Epicor tools
See all- Epicor Kinetic Job Status Reference
- Epicor BAQ Query Template Generator
- Epicor BPM Directive Design Template
- Epicor DMT Import Template Worksheet (Part and BOM)
- Epicor MRP Run Checklist
- Epicor Kinetic Upgrade Checklist
- Epicor Security Group Design Worksheet
- Epicor Kinetic Customization Change Request Form Template
- Epicor Kinetic Go-Live Cutover Plan Template
Keep exploring
Free tools
- Epicor 9 and Vantage Private AI Layer Blueprint GeneratorGenerate a private AI plan for Epicor 9 or Vantage on Progress OpenEdge, including SQL read path, replica, retrieval, local model serving and rollout.
- Epicor Kinetic Private AI Layer Blueprint GeneratorGenerate a shareable private AI architecture plan for Epicor Kinetic on-premises, with components, security controls, rollout phases and open questions for IT.
- Epicor ERP 10 AI Assistant Sizing and Value CalculatorEstimate GPUs, index size, hours saved and payback for a private AI assistant on Epicor ERP 10 on-premises.
ERP fixes and how-tos
- Epicor ERP 10 AI Integration Without Cloud: Private ArchitectureAdd a private AI assistant to Epicor ERP 10 on-prem: REST and BAQ access, SQL replica, Service Connect, local LLM, role mirroring, audit and phased rollout.
- How to Add AI to Epicor Kinetic On-Premises Without Moving Your DataReference architecture for a private AI assistant on Epicor Kinetic on-premises: BAQ and REST v2 access, SQL replica, local LLM, roles, audit and rollout.
- Shortage, Scrap, WIP, BOM, GL and Sales Reports in Epicor KineticWhere to find the Epicor Kinetic shortage, scrap, WIP, BOM, general ledger and sales reports, and how to build each one as a BAQ when the standard report falls short.
AI on your ERP
- AI for Epicor Kinetic, Beyond What Prism CoversAdd AI to Epicor Kinetic beyond Prism: private LLM over BAQs, BPM data, and REST v2, on-prem or private cloud, with honest guidance on when Prism already covers you.
- Private AI for Epicor Kinetic Cloud, Outside the Multi-Tenant BoundaryRun a private LLM on Epicor Kinetic private cloud or Kinetic Cloud data via BAQs, REST v2 and Data Fabric, keeping sensitive manufacturing data off shared AI.
Integrations
- How to connect Power BI to Epicor KineticConnect Power BI to Epicor Kinetic using BAQ OData feeds, a data warehouse or a SQL replica, with an on-prem gateway, key dashboards and natural-language Q&A.
- How to build an MCP server for Epicor KineticDesign a Model Context Protocol server for Epicor Kinetic: which read tools to expose, BAQ and REST v2 mapping, auth, stdio vs HTTP transport and audit logging.