# Macola Private AI Layer Blueprint Generator

> Source: https://netray.co/tools/macola-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 shareable architecture plan for adding a private, on-prem AI assistant to Macola, with components, security controls and a three-phase rollout.

## Category

other-erp

## Erp

Exact Macola

## Audience

- CIO
- IT manager
- ERP administrator
- ERP consultant

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Components Inc

#### System version

**Key:** version

**Type:** select

**Options:**

- Macola 10.x
- Macola ES (earlier release)
- Not sure

**Default:** Macola 10.x

#### Database engine

**Key:** db

**Type:** select

**Options:**

- SQL Server 2016 or 2017
- SQL Server 2019 or later
- Progress (older release)
- Not sure

**Default:** SQL Server 2019 or later

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

#### Sites or plants

**Key:** sites

**Type:** number

**Default:** 1

#### Main use cases

**Key:** usecases

**Type:** textarea

**Default:** Order status and shipping dates for customer service. Item availability and open PO lookups for purchasing. Questions across vendor certs and quotes stored on the file share.

#### Data that must never leave the site

**Key:** never

**Type:** textarea

**Default:** Customer pricing and contract terms. Cost and margin fields. Export-controlled drawings and quality records.

#### GPU available

**Key:** gpu

**Type:** select

**Options:**

- Not yet purchased
- 1 x 24 GB class GPU
- 1-2 x 48 GB class GPUs
- 2-4 x 80 GB class GPUs
- Existing GPU server

**Default:** 1-2 x 48 GB class GPUs

#### Target go-live

**Key:** golive

**Type:** date

**Default:** 2027-03-31

**Blocks:**

#### Private AI Layer Architecture Plan: Macola

**Body:** Company: {{company}}
System and version: Macola, {{version}}
Database: {{db}}
Hosting: {{hosting}}
Named users: {{users}}
Sites or plants: {{sites}}
GPU: {{gpu}}
Target go-live: {{golive}}

#### Context and objectives

**Body:** {{company}} wants an AI assistant over its Macola data and documents that runs inside its own environment ({{hosting}}). 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:
{{usecases}}

#### Data boundaries

**Body:** The following data must never leave the site and must stay out of any external service:
{{never}}

All processing, indexing and model inference run on infrastructure controlled by {{company}}.

#### Components

**Table:**

**Columns:**

- Layer
- Design
- Notes for {{company}}

**Rows:**

**0:** Data access path

**1:** Read-only SQL Server reporting copy of each Macola company database, with an ai schema of curated views over item, order, PO, customer and vendor tables

**2:** Table names carry module prefixes and an _sql suffix; confirm columns on {{company}}'s {{version}} install

**0:** Retrieval index

**1:** Vector index of drawings, POs, certs and SOPs, each chunk tagged with Macola item, order or vendor key

**2:** Built from the file shares {{company}} already uses

**0:** Model serving

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

**2:** Host has no outbound route when hosting is {{hosting}}

**0:** Tool server

**1:** MCP or REST wrapper offering typed read actions (order status, item availability, open POs)

**2:** No free SQL against base tables

**0:** Identity and permissions

**1:** Map each Macola user and company access to the assistant session; default deny on cost and margin

**2:** Macola security is application-level, so it must be mirrored

**0:** Audit

**1:** Append-only log of question, user, tool calls, views and row counts

**2:** Reviewed weekly during phase 1

#### Security controls

**Table:**

**Columns:**

- Control
- Implementation
- Driven by

**Rows:**

**0:** Network isolation

**1:** Model, index and tool server in a dedicated zone with no outbound internet route

**2:** Hosting: {{hosting}}

**0:** Data minimisation

**1:** Only approved views and document sets are exposed; excluded data is never indexed

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

**0:** Least privilege

**1:** Read-only service identity; per-user filtering of tool calls

**2:** {{users}} named users

**0:** Model governance

**1:** Open-weight model pinned by version, weights checksummed, updates via change control

**2:** GPU: {{gpu}}

**0:** Audit and retention

**1:** Append-only log of questions, tools, sources and users with an agreed retention period

**2:** Internal audit and compliance

**0:** Write-back control

**1:** No writes in phases 1 and 2; later writes only through supported APIs with named approvers

**2:** Risk appetite of {{company}}

#### Rollout plan

**Table:**

**Columns:**

- Phase
- Scope
- Exit criteria

**Rows:**

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

**1:** Approved views and documents for a pilot group; answers show their sources

**2:** Accuracy sampled by owners; no permission leaks in review; log reviewed weekly

**0:** 2. Drafts

**1:** Assistant drafts emails, summaries and suggested changes for a person to copy

**2:** Users edit less over time; no unreviewed output leaves the system

**0:** 3. Approved actions

**1:** Selected actions executed through supported APIs after human approval

**2:** Approver named per action; rollback tested; go-live target {{golive}}

#### Open questions for IT

**Body:** 1. How fresh must answers be: real time, minutes or daily?
2. Which companies, databases or libraries are in scope across {{sites}} site(s)?
3. Who owns document permissions and how are they mapped to Macola 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

**Signatures:**

- Prepared by
- IT lead
- Security / compliance
- Business sponsor

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

## Content

**Intro:** This free generator produces a shareable architecture plan for adding a private AI assistant to Macola on SQL Server. Fill in your environment and constraints, then export the plan to PDF or Word for your IT lead and reseller.

**Sections:**

#### How to use the blueprint

**Body:** Start with the fields that change the design most: hosting, database engine, the data that must never leave the site and the GPU you have. Write the use cases as real questions people ask today, such as which orders are late for a customer or what is on hand for an item across locations. The generated plan then maps these to a reporting copy, curated views, a retrieval index and a local model, with a rollout table you can paste into a project plan.

#### What Macola specifics it assumes

**Body:** Macola 10 runs on SQL Server and keeps each company in its own database. The plan therefore calls for a read-only copy per company, a dedicated schema of views, and a service login limited to SELECT. Because Macola enforces its security in the application, the plan mirrors user and company access in the tool layer instead of trusting database logins alone. Writes are excluded from early phases and, later, use supported import or SDK routes only.

#### Reading the output and common mistakes

**Body:** Treat the open questions as the agenda for your IT meeting: how fresh must data be, who owns document permissions, and who approves write-back. Common mistakes are querying production, covering only one company database, skipping an audit log and indexing documents without the Macola key. Replace the generic wording with names from your own environment before circulating the plan.

**Cta:** If you would like a second pair of eyes on this plan for your Macola environment, Netray can review it and the views it implies. The tool works fully without us.

**Faq:**

#### Does this plan send Macola data to a cloud?

**Answer:** No. The plan keeps the reporting copy, retrieval index and open-weight model inside your network, including an air-gapped option. You choose the hosting model in the form.

#### Do I need Macola 10 on SQL Server?

**Answer:** The plan assumes SQL Server because it allows a readable copy and curated views. Progress-based releases need an export step into a reporting database, which the open questions section flags.

#### Is the output a finished design?

**Answer:** It is a structured starting point. Table names, customisations and security rules must be confirmed against your own Macola database with your reseller or administrator.

#### Can I edit the generated document?

**Answer:** Yes. Export to Word or PDF and edit freely. Nothing is stored on our side unless you choose to request the optional review.

## Search terms

Macola AI architecture, Macola private AI, Macola on-prem AI plan, private AI blueprint ERP, on-prem LLM architecture template, AI architecture document generator, air-gapped AI plan template

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