AdvancedDELMIAworks / IQMS EnterpriseIQAI integration / Oracle database and web services

How to Add a Private AI Layer to DELMIAworks (IQMS) On-Prem

Question
how to add AI to DELMIAworks IQMS EnterpriseIQ on-prem

Also searched as

  • DELMIAworks AI integration without cloud
  • IQMS Oracle database AI assistant
  • private LLM for DELMIAworks ERP

Short answer

DELMIAworks, formerly IQMS EnterpriseIQ, runs on an Oracle database that you can read through a standby or replicated copy. A private AI layer queries well-known tables such as ARINVT for items, indexes documents locally, serves an open-weight model on your own GPUs, and writes back only through the vendor's supported interfaces after a person approves.

Applies to: On-premises DELMIAworks / IQMS EnterpriseIQ on Oracle Database; confirm your release and Oracle version, and note that cloud-hosted DELMIAworks is managed by the vendor

Steps to add a private AI layer to DELMIAworks / IQMS EnterpriseIQ

  1. 1Confirm the Oracle version and edition, the DELMIAworks release, and whether you hold licences for Data Guard, Active Data Guard or GoldenGate.
  2. 2Create a read-only copy: Active Data Guard standby if licensed, otherwise a periodically refreshed copy through RMAN duplicate or Data Pump exports.
  3. 3Create a dedicated Oracle user with SELECT on a curated set of objects or on views in its own schema, never on the full IQMS schema.
  4. 4Define views for items (ARINVT), customers (ARCUSTO), orders, work orders, purchasing and inventory movements, with documented columns and status meanings.
  5. 5Index work instructions, quality records, drawings and customer documents in a local vector store, tagged by plant, customer and document class.
  6. 6Serve an open-weight model with vLLM or Ollama on local GPUs behind a tool server with an audit log.
  7. 7Map DELMIAworks users and groups to roles and apply row and column scope through views or the tool server.
  8. 8Phase the rollout from read-only questions to drafts to approved write-backs through supported vendor interfaces.

How DELMIAworks data can be reached

DELMIAworks is built on an Oracle database, with application objects in an IQMS schema. Long-standing tables include ARINVT for inventory items, ARCUSTO for customers, and ORDERS, PO and WORKORDER families for sales, purchasing and production. Column names should be verified against your release, but the Oracle foundation means standard SQL clients, JDBC and ODBC all work with a suitable account.

Oracle gives you strong options for isolation. A standby opened read-only (Active Data Guard) or a GoldenGate-fed copy keeps analytical load off production. Views in a dedicated schema, with SELECT granted only on them, are the cleanest way to restrict columns.

For changes, use the vendor's supported interfaces and screens. DELMIAworks has substantial business logic for production, costing and plant scheduling, and direct DML against its tables is risky.

-- Read-only query against the item master (verify column names in your release)
SELECT a.itemno, a.descrip, a.class, a.rev
FROM iqms.arinvt a
WHERE a.itemno LIKE 'AX-%'
FETCH FIRST 50 ROWS ONLY;
-- Dedicated user with access to curated views only
CREATE USER ai_reader IDENTIFIED BY "<from vault>";
GRANT CREATE SESSION TO ai_reader;
GRANT SELECT ON ai_views.v_items TO ai_reader;
GRANT SELECT ON ai_views.v_open_orders TO ai_reader;

Reference architecture

Point the assistant at a read-only Oracle copy, and put a tool server in front of it. The tool server offers parameterised reads such as stock by item and warehouse, open orders by customer, work order status by press or line, and purchase order lines past due. For plastics and process manufacturers that use DELMIAworks, add reads for tooling and production monitoring data where your release exposes it.

The retrieval layer indexes documents and long-text fields separately from the transactional data. Oracle 23ai includes vector search, but a separate vector store such as pgvector or Qdrant keeps the AI workload off the ERP database and works on older Oracle versions too.

For air-gapped or sovereign deployments the stack, including embeddings and the audit log, stays on site. The architecture supports a customer's own controls on controlled technical data; it does not assert any certification.

Permissions and data scope

DELMIAworks maintains users, groups and plant-level rights inside the application, whereas the assistant reads through an Oracle account. Rebuild the relevant scope in views and the tool server: identify the person, find their DELMIAworks groups and plants, and allow only the corresponding views and rows.

Oracle Virtual Private Database can add row-level predicates keyed to a session context, which fits multi-plant companies. Cost, price and margin columns remain restricted to finance and management roles, and the document index is filtered on plant and customer tags before retrieval.

Test with users from two plants and with a supervisor versus a controller, and confirm that results differ as the application would.

Write-back, sizing and phased rollout

Write-back uses vendor-supported routes only, and a user approves the exact change. In early phases, have the assistant prepare the transaction and let a user enter it in DELMIAworks.

A mid-size manufacturer with 100 to 400 named users typically needs one to two 48 GB class GPUs for a 14B to 32B parameter model, plus a modest CPU server for the vector store. Document volume, especially scanned quality records, sets index size.

Phase one: inventory, order and production status for 4 to 6 weeks. Phase two: document Q and A and drafts. Phase three: a short, reviewed list of approved write-backs.

Honest limits

Oracle licensing is the main trap: Active Data Guard and GoldenGate are separately licensed options, so confirm entitlements or use a refreshed copy. Real-time production monitoring data may be high volume and is better summarised than fed raw to a model.

If the vendor offers an AI feature in your release, test it first; it may cover simple cases. A private layer is worth building when you need cross-system questions, document retrieval and control over where the model runs.

Try it here, free

DELMIAworks (IQMS) Private AI Layer Blueprint Generator

Open full tool

Fill in your version, database, hosting and use cases to get an architecture plan for a private, on-prem AI assistant on DELMIAworks (IQMS), ready to share with IT and security.

Common pitfalls

  • !Granting SELECT on the whole IQMS schema instead of curated views.
  • !Assuming Oracle replication options are licensed when they are separate options.
  • !Feeding raw machine-monitoring streams to the model instead of summaries.
  • !Skipping plant-level scope in a multi-plant deployment.
  • !Writing to application tables with SQL and bypassing production and costing logic.

How an ERP-grounded AI assistant handles this

ERPray can connect to an Oracle-based ERP through the read-only pattern described here and show the query behind each answer. Netray's custom build service handles the views, tool server and document index for DELMIAworks, with the model on your own hardware.

See ERPray

Frequently asked questions

What database does DELMIAworks use?

On-premises DELMIAworks, formerly IQMS EnterpriseIQ, runs on Oracle Database. Confirm the Oracle version and your licensed options before choosing a replication approach.

Do I need Active Data Guard?

Not strictly. It is a convenient way to get a read-only standby, but it is a licensed option. A periodically refreshed copy through RMAN or Data Pump works for many status and planning questions.

Can I use Oracle 23ai vector search?

Yes, on that version, but a separate vector store keeps the AI workload off the ERP database and also works with older Oracle releases. Choose based on your version and operations team.

Does it work for multi-plant companies?

Yes, if plant scope is enforced in views, Oracle VPD or the tool server, and mirrored as metadata filters on the document index.

Related

How-to

How to Run Live Scheduling in Global Shop Solutions

Live Scheduling in Global Shop Solutions builds a finite-capacity schedule from job routing operations against defined work centers, then presents it as a drag-and-drop board that shop supervisors adjust to reflect real shop floor priorities. Its accuracy depends on work centers, standard hours, and shop floor data collection all being kept current, since the schedule is only as good as the routing and capacity data feeding it.

CIO briefing

QAD vs Plex: Which Fits a Discrete Manufacturer?

Neither is universally better. Plex is a single cloud platform that combines ERP with MES, quality and shop floor control, which suits plants that want one system and are willing to adopt its standard processes. QAD is a configurable ERP strongest in multi-site, multi-country manufacturing, with a longer history on Progress and more deployment choices. Decide on your processes, footprint and integration needs, not on brand.

Advanced

How to Add a Private AI Layer to QAD Enterprise Edition On-Prem

QAD EE runs on a Progress OpenEdge database, which can be read through the OpenEdge SQL-92 engine over JDBC or ODBC without touching the 4GL application. A private AI layer reads a replica or reporting copy, indexes documents locally, serves an open-weight model on your own GPUs, and writes back only through QXtend or another supported QAD interface with human approval.

Advanced

How to Add a Private AI Layer to Global Shop Solutions On-Prem

Global Shop Solutions keeps jobs, routings, inventory, purchasing and quality data in one database that can be read through ODBC or the vendor's report and export tools. A private AI layer works from a read-only copy, builds a documented semantic layer over the tables you actually use, serves an open-weight model locally, and writes back only through vendor-supported import or API routes with approval.

Advanced

How to Add a Private AI Layer to Classic JobBOSS On-Prem

Classic JobBOSS stores its data in a Microsoft SQL Server database, so a private AI layer can read job, operation, material, customer and delivery data through a read-only login on a restored or replicated copy. Documents stay in a local index, the model runs on your own GPU, and any change to JobBOSS goes through its own screens or supported import tools after a person approves.

How-to

DELMIAworks Web API: How to Integrate and Where to Get Support

DELMIAworks offers a web-based API for integration, and the technical documentation sits behind the customer support portal for licensed customers, so confirm access and licensing with your account team first. Alongside it, many sites integrate through the Oracle database, import and export utilities, and middleware. Pick the route by direction of data and risk.

AI for ERP

AI Agents for ERP, Running On-Prem

A practical guide to on-prem AI agents for ERP: what they can safely automate, where human approval belongs, and how to design the guardrails.

AI for ERP

AI for Global Shop Solutions, Built for How Job Shops Actually Run

Add AI to Global Shop Solutions without sending your quoting, scheduling, and job cost data outside your shop. Private, on-prem AI for GSS job shops.

Stuck on DELMIAworks / IQMS EnterpriseIQ?

Talk to engineers who work inside DELMIAworks / IQMS EnterpriseIQ every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Software