# MAPICS and Infor XA Private AI Layer Blueprint Generator

> Source: https://netray.co/tools/mapics-xa-ibm-i-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 MAPICS and Infor XA, with components, security controls and a three-phase rollout.

## Category

other-erp

## Erp

Infor XA

## Audience

- CIO
- IT manager
- ERP administrator
- ERP consultant

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Lakeshore Industrial Corp

#### System version

**Key:** version

**Type:** select

**Options:**

- Infor XA 7.x
- Infor XA 6.x
- MAPICS XA 5.x or earlier
- Not sure

**Default:** Infor XA 7.x

#### Database engine

**Key:** db

**Type:** select

**Options:**

- DB2 for i on IBM i 7.3
- DB2 for i on IBM i 7.4
- DB2 for i on IBM i 7.5
- Not sure

**Default:** DB2 for i on IBM i 7.4

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

#### Sites or plants

**Key:** sites

**Type:** number

**Default:** 3

#### Main use cases

**Key:** usecases

**Type:** textarea

**Default:** MRP exception questions for planners. Purchase order status for buyers. Item and customer order lookups for customer service.

#### Data that must never leave the site

**Key:** never

**Type:** textarea

**Default:** Cost rollups and margins. Customer contract pricing. Controlled technical data.

#### 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-06-30

**Blocks:**

#### Private AI Layer Architecture Plan: MAPICS and Infor XA

**Body:** Company: {{company}}
System and version: MAPICS and Infor XA, {{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 MAPICS and Infor XA 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:** Journal-fed or scheduled replica of approved XA files on x86, with views and a glossary of terse XA field names, reached over JDBC or ODBC

**2:** File names are release specific; discover them via the DB2 for i catalog on {{db}}

**0:** Retrieval index

**1:** Vector index of drawings, POs and quality records tagged with XA item or order numbers

**2:** Built off-box from the IBM i

**0:** Model serving

**1:** Open-weight model on vLLM or Ollama on an x86 GPU server sized to {{gpu}}

**2:** IBM i does not run inference

**0:** Tool server

**1:** Typed read tools over the replica (MRP exceptions, PO status, item availability)

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

**0:** Identity and permissions

**1:** Least-authority IBM i service profile, row and column access control where used, XA roles mirrored in the tool layer

**2:** Watch adopted authority paths

**0:** Audit

**1:** Append-only log plus IBM i journal of service-profile access

**2:** Reviewed with the IBM i security administrator

#### 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 MAPICS and Infor XA 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 drafts a private AI architecture plan for MAPICS and Infor XA on IBM i. It covers the DB2 for i data path, change capture, off-box model serving and authority mapping, and exports to PDF or Word.

**Sections:**

#### How to use the blueprint

**Body:** Enter your XA release, IBM i level, user count and sites, then describe the questions planners, buyers and customer service ask. List the data that must not leave the site. The generator produces a plan that keeps the Power system as the system of record and moves analysis, retrieval and inference to x86 servers on your network.

#### What XA and IBM i specifics it assumes

**Body:** XA data sits in DB2 for i files that are readable over SQL. The plan assumes journaling on key files for change capture, a replica for analytical work, and a curated glossary because field names are terse. It treats the application's RPG and CL programs as the only valid write path, and it assumes a least-authority service profile.

#### Reading the output and common mistakes

**Body:** Use the open questions for the IBM i administrator: which files are journaled, which libraries are in scope and who owns authority reviews. Typical mistakes are querying the production partition with heavy SQL, using a broadly authorised profile and writing into files directly. Adjust names to your own libraries before circulating the plan.

**Cta:** If you want an expert look at this plan for your XA and IBM i setup, Netray can review it. The generator itself needs no contact.

**Faq:**

#### Does the model run on the IBM i?

**Answer:** No. The plan places model serving, retrieval and the tool server on x86 hardware. The IBM i remains the system of record and supplies data through JDBC reads or a replica.

#### What if journaling is not enabled?

**Answer:** Then change capture needs a scheduled extract instead, or journaling must be started on the files you need. The open questions section flags this for your administrator.

#### Can it work air-gapped?

**Answer:** Yes. Choose the air-gapped hosting option and the plan keeps the replica, index and model inside the enclave, with model files brought in on controlled media.

#### Is the plan a replacement for migration?

**Answer:** No. It lets users ask questions of XA data today. A migration decision is separate, though a governed data layer can help any later move.

## Search terms

MAPICS and Infor XA AI architecture, MAPICS and Infor XA private AI, MAPICS and Infor XA 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