# Epicor ERP 10 Private AI Layer Blueprint Generator

> Source: https://netray.co/tools/epicor-erp-10-private-ai-layer-blueprint-generator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Generate a private AI architecture plan for Epicor ERP 10 on-prem, covering REST and BAQ access, replica, retrieval, local model serving, security and rollout.

## Category

epicor

## Erp

Epicor ERP 10

## Industry

Discrete Manufacturing

## Audience

- CIO
- IT manager
- ERP architect
- Infrastructure engineer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Northfield Fabrication Inc

#### System version

**Key:** version

**Type:** select

**Options:**

- 10.2.700 or later
- 10.2.500 to 10.2.600
- 10.2.300 to 10.2.400
- 10.1.x

**Default:** 10.2.700 or later

#### Database engine

**Key:** db

**Type:** select

**Options:**

- SQL Server 2016
- SQL Server 2017
- SQL Server 2019

**Default:** SQL Server 2016

#### Hosting

**Key:** hosting

**Type:** select

**Options:**

- On-prem server
- Private cloud
- Air-gapped network

**Default:** On-prem server

#### Named users

**Key:** users

**Type:** number

**Default:** 120

#### Sites or plants

**Key:** sites

**Type:** number

**Default:** 1

#### Main use cases

**Key:** use_cases

**Type:** textarea

**Default:** Open jobs and parts shortages
Shipments due this week
Vendor late deliveries
Inventory by warehouse and bin

#### Data that must never leave the site

**Key:** never_leave

**Type:** textarea

**Default:** Customer prints and quality records
Costing and pricing data

#### GPU available

**Key:** gpu

**Type:** select

**Options:**

- None yet
- One 24 GB GPU
- One 48 GB GPU
- Two or more 48 GB GPUs
- Cloud GPU in a private tenancy

**Default:** One 24 GB GPU

#### Target go-live

**Key:** golive

**Type:** date

**Default:** 2027-03-01

**Blocks:**

#### Private AI Layer Architecture Plan: Epicor ERP 10

**Body:** Prepared for: {{company}}
System: Epicor ERP 10 {{version}} on {{db}}
Hosting: {{hosting}}
Named users: {{users}} across {{sites}} site(s)
Target go-live: {{golive}}

#### 1. Context and goals

**Body:** 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:
{{use_cases}}

Data that must stay on site:
{{never_leave}}

GPU position: {{gpu}}.

#### 2. Components

**Table:**

**Columns:**

- Component
- Design for {{company}}
- Notes

**Rows:**

**0:** Data access path

**1:** 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

**2:** Confirm which REST generation and authentication options the installed release supports.

**0:** Retrieval index

**1:** Local vector store over job travelers, drawings, certificates and SOPs from file shares referenced by Epicor

**2:** Every chunk carries source, site and access tags; untagged content is excluded.

**0:** Model serving

**1:** Open-weight model on vLLM or Ollama, sized for {{users}} named users on {{gpu}}

**2:** Model, quantisation and version recorded in the audit log.

**0:** Tool server

**1:** Tool server owning all credentials, exposing reviewed BAQ-backed read actions with row caps

**2:** Parameterised read actions only; row caps and column allow lists.

**0:** Identity and permissions

**1:** Restricted integration user plus a maintained mapping from Epicor security groups to companies, plants and BAQs, enforced by the tool server

**2:** Unknown users and unmapped content default to no access.

**0:** Audit

**1:** Append-only log of user, prompt, tool call, parameters, row counts and answer

**2:** Retained per {{company}} records policy; reviewed at each rollout phase.

#### 3. Security controls mapped to your inputs

**Table:**

**Columns:**

- Control
- Implementation
- Driven by

**Rows:**

**0:** Data residency

**1:** Replica, index and model all inside the {{hosting}} boundary; no outbound API calls at run time

**2:** Data that must never leave the site

**0:** Least privilege

**1:** Reduced Epicor security group for the integration user; read-only SQL login on the replica only

**2:** System version and role model

**0:** Network isolation

**1:** Dedicated segment for model and tool servers; only the tool server reaches the data source

**2:** Hosting

**0:** Prompt injection defence

**1:** Model receives bounded tool results only; no direct database or file access

**2:** Use cases

**0:** Write-back

**1:** Writes only via supported business objects or Service Connect workflows, after human approval of the exact payload

**2:** Phase 3 scope

#### 4. Rollout plan

**Table:**

**Columns:**

- Phase
- Scope
- Exit criteria

**Rows:**

**0:** 1: Read-only (weeks 1-6)

**1:** Approved read actions and document Q&A for a pilot group at one site

**2:** Accuracy review of sampled answers; no permission leaks in adversarial tests

**0:** 2: Drafts (weeks 7-12)

**1:** Summaries, reports and draft documents saved for human completion

**2:** Users edit rather than rewrite; audit log reviewed by IT and data owners

**0:** 3: Approved actions (week 13 onward)

**1:** Narrow, reversible transactions via supported interfaces after explicit approval

**2:** Rollback tested per action type; owner sign-off per action

#### 5. Open questions for IT

**Body:** 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

**Signatures:**

- IT lead
- Data owner
- Information security
- Business sponsor

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use it

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Bullets:**

- Readable secondary, log shipping or scheduled restore
- State the acceptable data lag in the plan
- Keep live-critical lookups on BAQs

#### Common mistakes

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Does this assume REST v2 is available?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** Yes. Select air-gapped hosting; models, embeddings and containers are staged through a controlled transfer and nothing calls an external service at run time.

## Search terms

Epicor ERP 10 AI architecture, Epicor 10 on-prem AI plan, Epicor 10 REST AI integration, private LLM Epicor 10, Epicor 10 AI blueprint, legacy ERP AI plan

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json