# Dynamics GP Private AI Layer Blueprint Generator

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

## Short answer

Enter your GP environment and get a plan for a private AI assistant: curated views, tool server, model serving, controls and rollout.

## Category

on-prem-ai

## Erp

Microsoft Dynamics GP

## Audience

- CIO
- IT manager
- GP administrator
- Controller

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Lakeside Distribution Co

#### GP version

**Key:** version

**Type:** select

**Options:**

- GP 2016
- GP 2018
- GP 18.2 to 18.4
- GP 18.5 or later

**Default:** GP 18.4

#### Database engine

**Key:** db

**Type:** select

**Options:**

- SQL Server 2014
- SQL Server 2016
- SQL Server 2017
- SQL Server 2019 or later

**Default:** SQL Server 2017

#### Hosting

**Key:** hosting

**Type:** select

**Options:**

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

**Default:** On-prem server

#### Named users

**Key:** users

**Type:** number

**Default:** 60

#### GP companies (databases)

**Key:** sites

**Type:** number

**Default:** 2

#### Main use cases

**Key:** usecases

**Type:** textarea

**Default:** Open receivables and payables questions, inventory by site, open purchase orders, month-end variance explanations, vendor document search.

#### Data that must never leave the site

**Key:** neverleave

**Type:** textarea

**Default:** Bank account numbers, payroll, customer credit terms, vendor contracts.

#### GPU available

**Key:** gpu

**Type:** select

**Options:**

- None yet
- One 24 GB class GPU
- One 48 to 80 GB class GPU
- Two or more GPUs

**Default:** One 24 GB class GPU

#### Target go-live

**Key:** golive

**Type:** text

**Default:** Q3 2027

**Blocks:**

#### GP Private AI Layer Plan: {{company}}

**Body:** System: Dynamics {{version}} on {{db}}, hosting: {{hosting}}.
Scale: {{users}} named users, {{sites}} company databases plus the DYNAMICS system database.
Target go-live: {{golive}}.

#### Context

**Body:** {{usecases}}

Goal: ask questions in plain language and get answers sourced from GP and documents, with all processing on {{company}} infrastructure.

#### Components

**Table:**

**Columns:**

- Component
- Design
- Notes

**Rows:**

**0:** Data access path

**1:** Read-only replica of DYNAMICS and company databases; curated views over master, open, work and history tables

**2:** Union open and history tables where needed

**0:** Write path

**1:** eConnect or Integration Manager after human approval; none in phase 1

**2:** No SQL writes

**0:** Retrieval index

**1:** Vendor documents, item notes, scanned files on shares, report text

**2:** Local vector store

**0:** Model serving

**1:** Open-weight model on vLLM or Ollama, GPU: {{gpu}}

**2:** Separate host from the GP SQL server

**0:** Tool server

**1:** MCP server with named read actions, parameter validation, row limits

**2:** Company database chosen from the user's allowed list

**0:** Identity and permissions

**1:** Map user to GP security roles and company access; filter in tool code

**2:** Do not reuse GP SQL logins

**0:** Audit

**1:** Local log of question, calls, queries, answer, approver

**2:** Retain per policy

#### Security controls

**Table:**

**Columns:**

- Requirement
- Control

**Rows:**

**0:** Never leaves site: {{neverleave}}

**1:** No external APIs; inference and index inside the {{hosting}} boundary; blocked egress

**0:** Sensitive tables

**1:** Payroll and bank views excluded by default and added only with owner sign-off

**0:** Least privilege

**1:** Dedicated SELECT-only SQL login on curated views

**0:** Write-back

**1:** Draft, approve, then submit through eConnect with the approver recorded

**0:** Traceability

**1:** Every figure links to the view and filter that produced it

#### Three-phase rollout

**Table:**

**Columns:**

- Phase
- Scope
- Exit criteria

**Rows:**

**0:** 1. Read-only questions

**1:** Finance and purchasing pilot, curated views

**2:** Controller signs off a test set reconciled to GP reports

**0:** 2. Drafts

**1:** Draft invoices, vendor emails and summaries for review

**2:** Low rework rate

**0:** 3. Approved actions

**1:** Few actions through eConnect after approval

**2:** Audit log reviewed by IT and finance

#### Open questions for IT

**Body:** 1. Can a readable replica or restore be provided for DYNAMICS and each company database?
2. Which third-party add-ons have their own tables?
3. How are GP users and roles managed, and are broad roles common?
4. Is multi-currency in use and how should amounts be presented?
5. Which integration methods are installed and supported for write-back?
6. What are the support and migration plans for GP?

**Signatures:**

- Prepared by
- IT lead
- Controller
- Security reviewer

**Notes:** A starting plan. Verify table contents, document type logic and integration support against your GP build and add-ons.

## Content

**Intro:** This generator produces an architecture plan for a private AI assistant on Dynamics GP, built around curated SQL views for reads and supported integrations for any write. It is meant to be handed to IT, finance and security.

**Sections:**

#### How to use the generator

**Body:** Enter your GP version, SQL Server version, user count and the number of company databases. Describe the first questions finance and purchasing want answered and list the data that must not leave the site. The plan repeats those restrictions in its controls table and proposes a rollout that proves accuracy before enabling any write.

**Bullets:**

- Count every company database
- List add-on modules with own tables
- Name sensitive tables to exclude
- Agree the test set with the controller

#### The design behind the plan

**Body:** GP data sits in SQL Server across a system database and one database per company, with separate open, work and history tables. The plan builds curated views over those tables, runs the model on a separate host and routes any writes through eConnect or another supported method after human approval.

#### Common mistakes

**Body:** Using only open tables, reusing GP user logins for the assistant, ignoring multi-currency columns and treating document type codes as universal. Each is covered by the open questions and controls so they are decided before build starts.

**Cta:** If you want an outside review of this plan against your GP environment, Netray can go through it with your team.

**Faq:**

#### Does this replace SmartList or SSRS?

**Answer:** No. Those remain good for fixed questions. The assistant adds ad hoc questions and document search on top of the same data.

#### Can the assistant post transactions?

**Answer:** Only in a late phase, after a person approves a draft, and through a supported integration such as eConnect. The default plan is read-only.

#### Does it handle multiple companies?

**Answer:** Yes. The tool server selects a company database from the user's allowed list, and the plan notes this as a control.

#### Is data uploaded anywhere?

**Answer:** No. The document is generated in your browser.

## Search terms

Dynamics GP AI architecture, GP private LLM plan, Dynamics GP SQL views AI, GP eConnect write-back AI, on-prem AI Dynamics GP, air-gapped GP AI, GP chat with data

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