# AI for Aptean Intuitive ERP: A Private Assistant Without a Platform Change > Source: https://netray.co/erp-ai/aptean-intuitive-erp-ai-integration > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: AI for ERP ## Short answer Aptean Intuitive ERP customers, many of them small and mid-size discrete manufacturers in electronics and medical device production, can add AI without moving off the platform: a private model reads the Intuitive database through read-only views and answers order, engineering change, and shop floor questions in plain language, with the underlying data shown alongside every answer and nothing sent to a public AI service. ## Kind platform ## Erp Family other ## Erp Products - Aptean Intuitive ERP ## Industries - Discrete Manufacturing - Electronics - Medical Device ## Region Global ## Persona IT Director ## Eyebrow Intuitive ERP + private AI ## Intro Aptean Intuitive ERP grew out of a product built for small and mid-size discrete manufacturers who needed a full ERP, order management, engineering with BOM and routing, planning, shop floor, and CRM, without the complexity of a Tier 1 system. A meaningful share of its installed base sits in electronics and medical device manufacturing, industries where engineering changes are frequent, traceability matters, and IT headcount is usually thin relative to the complexity of what the system actually needs to support. That combination, frequent engineering changes plus a small IT team, is exactly where an AI layer earns its keep fastest. When an engineering change comes through, someone has to work out which open orders, which BOMs, and which inventory it touches, today usually by running a report or two and cross-checking by hand. When a customer calls about an order, someone has to check status across order entry and shop floor screens. These are well-defined, repetitive lookups, not judgment calls, which makes them good first candidates for a grounded assistant rather than a reason to add headcount. Aptean's newer AI announcements are aimed primarily at its larger cloud ERP lines, so Intuitive ERP customers evaluating AI today are mostly looking at layering something on top of what they already run rather than waiting for a vendor-native feature scoped to this specific product. That is a reasonable path as long as the layer respects the existing database structure and security model rather than requiring a parallel data platform. For a medical device manufacturer specifically, the same architecture also has to respect the traceability and documentation habits that FDA 21 CFR Part 820 and, for many customers, ISO 13485 already require. An AI assistant that helps someone find information faster is useful; one that quietly changes how records are created or who can see what is not, so read-only access and a clear audit trail matter here as much as raw capability. ## Pain Points ### Engineering changes require manual cross-checking **Detail:** Working out which open orders, BOMs, and inventory positions a given engineering change affects is usually a manual exercise across Intuitive's engineering and order modules, done by whoever has time, not necessarily by the person best placed to catch a downstream issue. ### Order and shop floor status split across screens **Detail:** Answering a customer's order status question means checking order entry, job status, and sometimes shipping screens separately, which slows down customer service response time during busy periods. ### Small IT teams relative to system complexity **Detail:** Intuitive ERP customers are often small or mid-size manufacturers whose IT function is one or two generalists, not a team that can build or maintain a custom BI or AI platform on top of the ERP without outside help. ### Traceability expectations in regulated industries **Detail:** Electronics and medical device customers running Intuitive ERP often carry ISO 13485, FDA 21 CFR Part 820, or IPC traceability obligations that any new tool touching production or quality data has to respect, not work around. ### No vendor-native AI roadmap for this specific product **Detail:** Aptean's publicly visible AI investment is concentrated in its newer cloud platforms, leaving Intuitive ERP customers to add AI themselves if they want it now rather than as part of a future vendor release. ## Use Cases ### Engineering change impact lookup **Description:** Given a BOM or component change, lists the open orders, jobs, and inventory it affects, referencing engineering, order, and inventory records, so engineering and planning can sequence the change without a manual cross-check. **Erp Objects:** Engineering/BOM and routing tables, open order and job records, inventory allocation data **Outcome:** cuts the manual impact-check time for a routine engineering change from an hour or more to a few minutes ### Order and job status lookup **Description:** Answers a plain-language question about a specific order's current status across order entry, shop floor, and shipping, so customer service does not have to check three screens to answer one call. **Erp Objects:** Order entry and order line records, job/work order status, shipping records **Outcome:** cuts routine order status lookups from several minutes to a direct, sourced answer ### Component traceability and lot lookup **Description:** Answers where-used and lot history questions on a specific component or serialized item, useful for a quality investigation in a regulated electronics or medical device shop. **Erp Objects:** Lot and serial tracking records, BOM where-used data, receiving and shipping history **Outcome:** cuts traceability research from a manual multi-screen trace to a direct, sourced answer ### Purchase order and supplier follow-up drafting **Description:** Drafts routine follow-up messages on open purchase orders approaching their promise date, for a buyer to review and send, rather than writing each one from scratch. **Erp Objects:** Open purchase order records, vendor master, promise dates **Outcome:** buyers spend follow-up time on the suppliers that need real escalation, not routine status chasing ### MRP and planning exception triage **Description:** Surfaces which planned orders or shortages actually need a planner's attention today, instead of a planner reviewing the full exception list line by line every morning. **Erp Objects:** MRP planned order records, shortage and exception reports **Outcome:** planners work through the real exception list in a fraction of the time spent on a manual scan ### Quality and non-conformance summary support **Description:** Helps a quality engineer pull the relevant order, lot, and inspection history into one organized summary when investigating a non-conformance, for the engineer to review and act on. **Erp Objects:** Non-conformance and inspection records, lot and order history **Outcome:** cuts the time to assemble a non-conformance investigation packet from hours to a shorter, more focused review ### Natural-language questions across order and engineering data **Description:** Lets a manager ask a question once, such as which open orders are affected by a specific supplier delay, and get an answer grounded in Intuitive's actual data, without knowing which screen or table to check. **Erp Objects:** Order, engineering, inventory, and purchasing data accessed through read-only database views **Outcome:** fewer one-off report requests land on IT or the one person who knows the database structure ## Architecture **Overview:** The architecture reads the Intuitive ERP database through dedicated read-only views, respects the system's existing security model, and runs on infrastructure sized to a small or mid-size manufacturer's actual IT capacity. **Layers:** #### Intuitive ERP connector **Detail:** Read-only database views over order, engineering/BOM, inventory, purchasing, and quality tables, isolating the AI layer from any direct write path into production. #### Data and semantic layer **Detail:** A plain-language mapping of Intuitive's table and field structure to the terms customer service, planning, and quality staff actually use, plus an index over existing reports and procedure documents. #### Model serving **Detail:** An open-weight model (Llama, Qwen, Mistral, or Gemma class) served with vLLM or Ollama on a modest GPU footprint the company owns or a small private cloud instance. #### Retrieval and agents **Detail:** Retrieval-augmented generation grounds every answer in current order, engineering, and quality data; any agent proposing a write, such as a supplier follow-up draft, stops for human review before anything is sent. #### Governance and audit **Detail:** Query and response logging tied to the user's Intuitive login, giving a small IT and quality function a reviewable trail without needing a dedicated compliance program. ## Deployment Options ### Small on-prem footprint **Fit:** Manufacturers that already host Intuitive ERP on-site and want the AI layer on the same local network **Detail:** A single modest GPU server sized to the shop's actual query volume, sitting alongside the existing database rather than requiring a new data center build-out. ### Private cloud instance **Fit:** Manufacturers without in-house server hardware management capacity **Detail:** A dedicated, non-shared private instance that keeps data off a public AI API while avoiding the capital cost of owning GPU hardware. ### Hybrid with a hosted Intuitive ERP instance **Fit:** Manufacturers whose Intuitive ERP is already hosted by a partner **Detail:** The AI layer connects to the hosted database through the same secured network path the hosting partner already provides, keeping one governance model across both. ## Compliance ### Read-only access by default and full logging keep the assistant's use of quality and traceability data reviewable in the same way existing Intuitive ERP records are, without changing who can create or modify a quality record. **Framework:** FDA 21 CFR Part 820 / ISO 13485 (medical device customers) ### Lot and component traceability queries are grounded directly in Intuitive's own lot and BOM data, so an answer can always be traced back to the underlying record during a customer or internal audit. **Framework:** IPC and customer traceability requirements (electronics customers) ### Engineering, BOM, and order data stay on infrastructure the company controls, avoiding exposure of customer-owned designs or specifications to a public AI service. **Framework:** Data confidentiality and customer IP protection ### Assistant access mirrors each user's existing Intuitive ERP security role, so a customer service rep cannot see cost or engineering data they could not already see directly in the system. **Framework:** Segregation of duties ## Integration Notes - Connects to the Intuitive ERP database through dedicated read-only views rather than direct production table access. - Where Intuitive ERP exposes an API or integration layer for write-back actions, that path is used instead of direct database writes, preserving the system's built-in validation. - Existing reports and procedure documents can be indexed so the assistant is consistent with how the business already measures and describes things. - A lightweight identity mapping ties each user's Intuitive ERP login to what the assistant can see, avoiding a separate access model to maintain. - Sized for typical Intuitive ERP deployment scale: a single GPU server or a small private cloud instance is usually sufficient. - Customizations and add-on modules specific to a given implementation are mapped into the read-only views during discovery rather than assumed to match a generic schema. ## Product Fit ### Custom build **Why:** Intuitive ERP is not one of ERPray's current out-of-box connectors, so a purpose-built connector using the same read-only, retrieval-grounded architecture is the practical starting point. ### DataRay **Why:** Where quality procedures, customer specifications, or engineering documents sit outside Intuitive ERP as file shares or a document store, DataRay extends the same on-prem approach to that content. ## Engagement ### Discovery **Duration:** 1-2 weeks **Deliverables:** - Review of the Intuitive ERP version, customizations, and existing reporting tools in use - Use case shortlist ranked by frequency and current manual effort, with quality and traceability needs flagged early - Read-only view design covering order, engineering, inventory, and quality tables - GPU or private-instance sizing estimate scaled to company size ### Pilot **Duration:** 4-6 weeks **Deliverables:** - One or two use cases live in read-only mode for a defined user group - Model evaluation against real order, engineering, and quality data - Feedback loop with customer service, planning, or quality staff - Draft data flow documentation for IT and quality review ### Production **Duration:** 4-6 weeks **Deliverables:** - Hardened deployment with access mapped to existing Intuitive ERP security roles - Full audit logging for any regulated traceability use cases - Runbook covering model updates and monitoring for a small IT team - Short training session for the initial user group ### Scale **Duration:** Ongoing **Deliverables:** - Additional use cases added from the original shortlist as they prove out - Rollout to additional departments as adoption grows - Periodic review of common questions to spot new automation opportunities - Evaluation of newer open-weight models as they become available ## Buyer Questions - Does the vendor understand the Intuitive ERP database structure, or does schema mapping start from zero? - Does any part of the pipeline send engineering, order, or quality data to a public AI API by default? - Can the assistant's access be scoped to match our existing Intuitive ERP security roles? - How is a traceability or quality-related answer sourced back to the underlying record for an audit? - What GPU or infrastructure footprint does this actually require for a company our size? - How does a draft write action, like a supplier follow-up, reach a human for approval before it is sent? - What happens to our data and model configuration if we end the engagement? ## Faq ### Does Aptean offer AI directly for Intuitive ERP? **Answer:** Aptean's visible AI investment is concentrated in its newer cloud ERP platforms rather than Intuitive ERP specifically. Customers wanting AI value today generally add a private layer on top of their existing Intuitive ERP database rather than waiting for a vendor-native feature scoped to this product. ### Is this safe for a medical device manufacturer with FDA and ISO 13485 obligations? **Answer:** It can be, provided the assistant is read-only by default, every answer is traceable back to the underlying Intuitive ERP record, and access mirrors existing security roles. The tool should make finding information faster without changing how quality or traceability records are created or approved. ### How big a project is this for a small or mid-size manufacturer? **Answer:** Smaller than most expect. A pilot covering one or two high-value use cases, such as engineering change impact lookup and order status, is realistic in a matter of weeks on infrastructure sized to the company's actual query volume rather than an enterprise deployment. ### Does this require replacing our existing reports? **Answer:** No. Standard recurring reports stay where they are. The assistant is built for the ad hoc, plain-language questions that do not justify writing a new report, and it can reference existing reports to stay consistent with how the business already measures things. ### What is the realistic first use case? **Answer:** Engineering change impact lookup and order status lookup tend to show value fastest, since both are frequent, well-defined tasks with a clear existing manual process the assistant speeds up. Component traceability queries are a strong second use case for regulated customers. ### Can this work if we have added custom modules or fields to Intuitive ERP? **Answer:** Yes, but custom fields, added tables, or modified workflows need to be mapped into the read-only views during discovery. This is a normal part of scoping the project and does not require a different overall approach. ### Is on-prem necessary, or can we use a cloud AI service instead? **Answer:** On-prem or a dedicated private instance is the more defensible choice for most Intuitive ERP customers, especially those with customer-owned IP in their engineering data or regulated traceability obligations, because it avoids sending that data to a public AI API by default. ## Search terms Aptean Intuitive ERP AI, Intuitive ERP AI integration, Intuitive ERP AI copilot, on-prem AI for Intuitive ERP, Aptean Intuitive generative AI, Intuitive ERP natural language query, private LLM Intuitive ERP, Intuitive ERP engineering change AI, Intuitive ERP electronics manufacturing AI, Intuitive ERP medical device AI, Aptean ERP AI, Intuitive ERP traceability AI --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json