# Epicor Eclipse Private AI Layer Blueprint Generator

> Source: https://netray.co/tools/epicor-eclipse-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 Eclipse built on scheduled extracts, a local reporting store and an on-prem model.

## Category

epicor

## Erp

Epicor Eclipse

## Industry

Wholesale Distribution

## Audience

- CIO
- IT manager
- ERP architect
- Infrastructure engineer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Harbor Electrical Supply

#### System version

**Key:** version

**Type:** select

**Options:**

- Eclipse current release
- Eclipse one to two releases back
- Eclipse older release
- Not sure

**Default:** Eclipse current release

#### Database engine

**Key:** db

**Type:** select

**Options:**

- Progress OpenEdge (vendor managed)
- Progress OpenEdge (customer access)
- Extract files only
- Local reporting database (SQL Server)

**Default:** Progress OpenEdge (vendor managed)

#### 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:** 90

#### Sites or plants

**Key:** sites

**Type:** number

**Default:** 8

#### Main use cases

**Key:** use_cases

**Type:** textarea

**Default:** Stock by branch and transfers
Open orders and customer history
Purchase orders and receipts
Vendor performance

#### Data that must never leave the site

**Key:** never_leave

**Type:** textarea

**Default:** Cost, margin and rebate data
Customer pricing agreements

#### 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-05-01

**Blocks:**

#### Private AI Layer Architecture Plan: Epicor Eclipse

**Body:** Prepared for: {{company}}
System: Epicor Eclipse {{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 for Epicor Eclipse that reads from scheduled extracts and Epicor-supported interfaces into a local reporting store. Because the source is extract based, freshness is stated on every answer and the assistant remains read-only.

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:** Scheduled extracts or reports to file and any Epicor-supported interfaces for your release, loaded into a local reporting database with typed tables

**2:** Confirm entitlements and formats with Epicor; do not guess table names.

**0:** Retrieval index

**1:** Local vector store over price lists, product data sheets, contracts and branch procedures, plus exported report text

**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 with parameterised read actions over the reporting store; refuses stock-critical answers if the extract is older than a set threshold

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

**0:** Identity and permissions

**1:** Directory groups mapped to branches and roles; branch and sensitivity columns in the reporting store; unknown users denied

**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:** Loader writes only to the reporting store; assistant reads only from it; no credentials to Eclipse in the model path

**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:** Read-only unless Epicor provides a supported write interface for your release; any write is a draft completed by a person in Eclipse

**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:** Who hosts Eclipse, and what data access does the contract allow?
Which interfaces and extract formats are available for our release?
What extract frequency is permitted?
Which fields identify branch and sensitivity?
How do pricing, rebate and matrix logic need to be handled?
Who confirms extract completeness after each load?

#### Approvals

**Signatures:**

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

**Notes:** Starting point for discussion, not a design guarantee. Eclipse interfaces and permitted access vary by release, licence and hosting; confirm with Epicor before design.

## Content

**Intro:** This generator creates a private AI architecture plan for Epicor Eclipse. It assumes extract-based access into a local reporting store and puts data freshness and branch permissions at the centre of the design.

**Sections:**

#### How to use it

**Body:** Select your Eclipse release band and how you can access data (vendor-managed, customer access, extract files only or an existing reporting database). Add user and branch counts, GPU position and use cases written as the questions branch staff ask. List restricted data such as cost, margin and rebates.

**Bullets:**

- Ask Epicor for the data dictionary and interface list
- State the acceptable extract delay
- Keep cost and rebates in a restricted class
- Start with two or three branches

#### What the plan contains

**Body:** Context, a component table with the extract path, retrieval index, model serving, tool server, identity and audit, security controls tied to your inputs, a three-phase rollout, open questions for IT and approvals. Freshness thresholds are part of the tool server design.

#### Why freshness matters

**Body:** With extracts, answers are only as current as the last load. The plan records an as-of time on each answer and lets the tool server refuse stock-critical questions when the extract is stale, sending users to the Eclipse screen instead.

**Bullets:**

- Show the as-of time in every answer
- Set a staleness limit per question type
- Validate row counts after each load

#### Common mistakes

**Body:** Common errors are guessing table names, recomputing price or rebate logic from flat extracts, screen scraping, and omitting branch columns so per-user filtering is impossible. The plan avoids each by design.

**Cta:** If you want an engineer to review the extract design or to build the reporting store and assistant on your servers, Netray can help. The generator is free without contact.

**Faq:**

#### Can this work if Epicor hosts our Eclipse?

**Answer:** Often yes, through scheduled extracts or supported interfaces into a store you control, if your contract allows it. Confirm entitlements with Epicor first; the plan lists this as an open question.

#### Is the data real time?

**Answer:** No. It is as fresh as the latest extract, and the plan shows an as-of time on every answer. For stock-critical decisions, users confirm in Eclipse before acting.

#### How are branch permissions applied?

**Answer:** The reporting store carries branch and sensitivity columns and the tool server filters every query and retrieval by the user's branches, mapped from directory groups. Unknown users get no access.

#### Can the assistant place orders?

**Answer:** Not by default. Unless Epicor provides a supported write interface for your release, the assistant prepares drafts that a person completes in Eclipse.

## Search terms

Epicor Eclipse AI architecture, Eclipse ERP private AI plan, Eclipse ERP data extract AI, distribution ERP on-prem LLM, Eclipse ERP chat with data, Epicor Eclipse AI blueprint

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