Made2Manage Private AI Layer Blueprint Generator
This free generator creates a private AI architecture plan for Made2Manage on SQL Server. Enter your environment and the data that must stay on site, then export the plan for your IT team and Made2Manage administrator.
Fill in
Made2Manage Private AI Layer Blueprint Generator
Private AI Layer Architecture Plan: Made2Manage
Company: Summit Fabrication Co System and version: Made2Manage, Made2Manage on SQL Server (current) Database: SQL Server 2016 or 2017 Hosting: On-prem server Named users: 45 Sites or plants: 1 GPU: 1-2 x 48 GB class GPUs Target go-live: 2027-02-28
Context and objectives
Summit Fabrication Co wants an AI assistant over its Made2Manage data and documents that runs inside its own environment (On-prem server). The assistant must answer questions in natural language, show the data behind each answer, respect existing user permissions and remain read-only until approvals are in place.
Main use cases: Job status and shortages for the shop floor. Delivery date questions for sales. Search of job travelers, inspection records and supplier certs.
Data boundaries
The following data must never leave the site and must stay out of any external service: Customer pricing. Job cost and margin. Customer drawings under NDA.
All processing, indexing and model inference run on infrastructure controlled by Summit Fabrication Co.
Components
| Layer | Design | Notes for Summit Fabrication Co |
|---|---|---|
| Data access path | Read-only SQL Server copy with an ai schema of views over item master, sales orders, purchase orders, jobs, routings and job BOMs | Core tables use short identifiers and f-prefixed columns; confirm on Summit Fabrication Co's Made2Manage on SQL Server (current) schema |
| Retrieval index | Vector index of job travelers, drawings, inspection records and supplier certs tagged with job, part or order number | Scoped by job and customer |
| Model serving | Open-weight model on vLLM or Ollama sized to 1-2 x 48 GB class GPUs | Isolated VLAN when hosting is On-prem server |
| Tool server | Typed read tools such as job status, parts short for a job and open orders for a customer | Tools return rows the user can inspect |
| Identity and permissions | Map Made2Manage user groups to assistant roles; restrict cost, margin and pricing | Application-level security must be mirrored |
| Audit | Append-only log of questions, tool calls and returned row sets | Reviewed with the plant controller |
Security controls
| Control | Implementation | Driven by |
|---|---|---|
| Network isolation | Model, index and tool server in a dedicated zone with no outbound internet route | Hosting: On-prem server |
| Data minimisation | Only approved views and document sets are exposed; excluded data is never indexed | Data that must never leave the site |
| Least privilege | Read-only service identity; per-user filtering of tool calls | 45 named users |
| Model governance | Open-weight model pinned by version, weights checksummed, updates via change control | GPU: 1-2 x 48 GB class GPUs |
| Audit and retention | Append-only log of questions, tools, sources and users with an agreed retention period | Internal audit and compliance |
| Write-back control | No writes in phases 1 and 2; later writes only through supported APIs with named approvers | Risk appetite of Summit Fabrication Co |
Rollout plan
| Phase | Scope | Exit criteria |
|---|---|---|
| 1. Read-only questions | Approved views and documents for a pilot group; answers show their sources | Accuracy sampled by owners; no permission leaks in review; log reviewed weekly |
| 2. Drafts | Assistant drafts emails, summaries and suggested changes for a person to copy | Users edit less over time; no unreviewed output leaves the system |
| 3. Approved actions | Selected actions executed through supported APIs after human approval | Approver named per action; rollback tested; go-live target 2027-02-28 |
Open questions for IT
1. How fresh must answers be: real time, minutes or daily? 2. Which companies, databases or libraries are in scope across 1 site(s)? 3. Who owns document permissions and how are they mapped to Made2Manage roles? 4. Which customisations or custom tables must be exposed? 5. What is the backup, monitoring and patching plan for the GPU host? 6. Who approves any write-back and through which supported interface? 7. Is a pilot group of 10 to 20 users available for phase 1?
Approvals
Starting-point document, not a final design. Confirm table names, interfaces and security behaviour for your exact release with your vendor or implementation partner. Nothing you enter leaves your browser.
Optional Made2Manage plan review
We can review the generated plan against your schema and security model.
Optional. The tool and every export work without this. No spam.
How to use the blueprint
Describe the questions people ask in the shop and the office: which jobs are short material, when a sales order will ship, where the inspection record for a lot is. Choose hosting and GPU honestly, because they drive the model sizing and network design. The tool turns your answers into a plan with components, controls, a three-phase rollout and questions for IT.
What Made2Manage specifics it assumes
The plan assumes a SQL Server database, a reporting copy and a schema of views over jobs, routings, BOMs, sales orders, purchasing and inventory. It assumes the shop has customisations, so it asks IT to confirm table mappings. Security is application-level, so the plan mirrors Made2Manage groups in the tool layer. Writes are held back until phase 3 and use supported routes.
Reading the output and common mistakes
Use the open questions to drive a short meeting with your administrator and controller. Typical mistakes are letting a model compose SQL against production, forgetting custom fields, and exposing job cost to everyone. Replace placeholder wording with your own table and group names before the plan goes to management.
Frequently Asked Questions
Will Made2Manage data leave our network?
Not under this plan. The reporting copy, retrieval index and open-weight model all run on your servers, and the hosting option can be air-gapped.
Do we need to change Made2Manage?
No changes are needed for read-only use. The plan reads from a SQL Server copy through views. Later write-back would use supported routes only.
Is this suitable for a small shop?
Yes. A single GPU is typically enough for a small user base. If you only need a few fixed reports, standard reporting may be simpler.
Can the output be edited?
Yes, export it to Word or PDF and edit freely. The tool runs in your browser.
If you want help turning this plan into a working pilot on your Made2Manage data, Netray can review it with you. The generator is free regardless.
Related Tools
Made2Manage AI Assistant Sizing and Value Calculator
Estimate GPU count, token volume, index size, hours saved and payback for a private on-prem AI assistant on Made2Manage.
On-Prem AIOn-Prem AI Security Hardening Checklist
A practical control checklist for securing self-hosted language models, covering model provenance, network isolation, data governance, host hardening, and audit readiness.
On-Prem AIOn-Prem AI Deployment Checklist
A 30-point pre-deployment checklist covering use cases, hardware, security, model operations, and rollout for self-hosted enterprise LLMs.
ERP OperationsERP Database Read-Only Access Request Form
A scoped, time-boxed request for a read-only SQL login or reporting role on an ERP database, with owner approvals.
More Other ERPs tools
See all- Infor VISUAL Work Order Status and Structure Reference
- Infor VISUAL Manufacturing Scheduling Checklist
- Infor XA (MAPICS) Period End Close Checklist
- Infor VISUAL Database Table Reference
- Infor XA (MAPICS) Application Module Reference
- IBM i Commands for Infor XA Administrators Reference
- Acumatica Generic Inquiry Design Template
- Acumatica Manufacturing Edition Setup Checklist
- Sage X3 Import Template Worksheet
Keep exploring
Free tools
- Macola Private AI Layer Blueprint GeneratorGenerate a shareable architecture plan for adding a private, on-prem AI assistant to Macola, with components, security controls and a three-phase rollout.
- Made2Manage AI Assistant Sizing and Value CalculatorEstimate GPU count, token volume, index size, hours saved and payback for a private on-prem AI assistant on Made2Manage.
- SAP S/4HANA On-Prem Private AI Layer Blueprint GeneratorFill in your version, database, hosting and use cases to get an architecture plan for adding a private, on-prem AI assistant to SAP S/4HANA, with components, security controls and a three-phase rollout.
AI on your ERP
- AI for Aptean Made2Manage: A Private Assistant on Top of Your M2M DataAdd AI to Aptean Made2Manage without a rip-and-replace: a private LLM grounded in your M2M SQL Server data for order, shop floor, and MRP questions.
- AI for Aptean Intuitive ERP: A Private Assistant Without a Platform ChangeOn-prem AI for Aptean Intuitive ERP: a private assistant grounded in your Intuitive database for order, engineering, and shop floor questions.
Integrations
- How to add AI agents to Made2ManageHow to add AI agents to Made2Manage: a tool layer over the SQL Server database, MRP exception triage, PO expediting drafts and human approval before any write.
- How to use ChatGPT with Made2ManageUsing ChatGPT with Made2Manage: exports versus live access, custom GPT actions over a safe API, enterprise data controls, and when a private model is the better call.