On-Prem AIFree templatePDF, Excel, Word exportMicrosoft Dynamics NAV

Dynamics NAV Private AI Layer Blueprint Generator

Generate a plan for putting a private AI assistant beside Dynamics NAV. The document covers the SQL and web service access paths, retrieval, model serving, permissions and a phased rollout, ready to share with IT and security.

Fill in

Live preview
Download:

Dynamics NAV Private AI Layer Blueprint Generator

NAV Private AI Layer Plan: Harbour Components Inc

System: Dynamics NAV 2017 on SQL Server 2016, hosting: On-prem server. Scale: 90 named users, 3 NAV companies or plants. Target go-live: Q1 2027.

Context

Item availability and where-used, open purchase lines by vendor, customer balances, lot traceability lookups, search of quality records.

Goal: natural-language access to NAV data and documents with all processing inside Harbour Components Inc infrastructure.

Components

ComponentDesignNotes
Data access pathRead-only SQL replica with per-company views; published pages, queries and codeunits as web services for logic-bound readsCompany name is part of every NAV table name
Change detectionTimestamp columns or SQL change data capture feeding the indexAvoid full nightly rebuilds
Retrieval indexAttachments, comments, item text, external documents linked from recordsLocal vector store
Model servingOpen-weight model via vLLM or Ollama, GPU: One 24 GB class GPUQuantise if memory is tight
Tool serverMCP server with named read actions, parameter checks and row limitsNo free-form SQL from the model
Identity and permissionsMap Windows user to NAV user; apply permission sets and company access in tool code or via delegationTest with a low-privilege user
AuditLocal log of question, calls, queries and answerAlign retention with policy

Security controls

RequirementControl
Never leaves site: Customer price lists, supplier contracts, payroll, export-controlled drawings.No external APIs; inference and index inside the On-prem server boundary; egress blocked
Least privilegeSELECT-only SQL login on curated views; narrow web service identity
Calculated fieldsFlowField values recomputed from ledger entries and reconciled to NAV pages
Write-backDrafts only, human approval, posting through codeunit or page web services
TraceabilityEach answer cites the view or service behind it

Three-phase rollout

PhaseScopeExit criteria
1. Read-only questionsPilot group, curated views, document searchAgreed test set answered correctly and permissions verified
2. DraftsDrafted documents and summaries reviewed by usersLow rework rate in review
3. Approved actionsSmall list of actions through web servicesAudit log reviewed by IT and finance

Open questions for IT

1. Can we provide a readable SQL copy and how current must it be? 2. Which pages, queries and codeunits are already published as web services? 3. Which authentication is configured on the service tier? 4. Are security filters used on tables the assistant will read? 5. Which C/AL customisations change standard posting or calculations? 6. What is the plan for moving to Business Central, and should views be designed for repointing?

Prepared by / Date
IT architect / Date
Business owner / Date
Security reviewer / Date

A starting plan. Verify object names, web service availability and OData version for your NAV build and customisations.

Get an expert review of your NAV AI blueprint

Optional: send the exported plan for comments on gaps and sequencing. The generator is free regardless.

Optional. The tool and every export work without this. No spam.

How to use the generator

Choose your NAV version and database engine, then describe the questions users should be able to ask. Record the data that must stay on site. The output includes a components table, controls tied to your inputs, a three-phase rollout and a list of questions for your DBA and NAV developers.

  • Pick the exact NAV version
  • List published web services you already have
  • State if multiple companies share a database
  • Export to Word for review

The design behind the plan

NAV stores data in SQL Server with the company name inside every table name, and exposes pages, queries and codeunits as web services. The plan uses SQL on a replica for broad reads and web services where NAV logic and permissions matter, with a tool server in front and an open-weight model on local GPUs.

Common mistakes

Reading FlowField-style values straight from tables, forgetting the company prefix, running the assistant with a super permission set and writing to tables with SQL. The plan flags each of these and keeps write-back behind approval and supported services.

Frequently Asked Questions

Does it work for NAV 2009?

The generator targets NAV 2013 to 2018, where web services and SQL Server are standard. NAV 2009 deployments with the classic client need a different integration approach.

Is anything uploaded?

No. The document is assembled in your browser from the values you type.

Does it assume cloud services?

No. Every component runs inside your network, including the model and the audit log.

Can I reuse it for Business Central?

Partly. The structure applies, but Business Central has API v2.0 and different table naming, so use the Business Central generator.

If you would like help validating this plan against your NAV customisations, Netray can review it with your team.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Software