# AI for 3DEXPERIENCE and ENOVIA That Works With Your Business Objects, Not Around Them

> Source: https://netray.co/erp-ai/dassault-3dexperience-enovia-ai-integration
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: AI for ERP

## Short answer

AI for Dassault 3DEXPERIENCE and ENOVIA places a private language model beside 3DSpace, reading parts, engineering changes and documents through supported web services under the asking user's identity. Engineers and change coordinators ask in plain English and receive answers citing the underlying business objects, while IP and controlled data stay in your environment.

## Kind

platform

## Erp Family

mfg-systems

## Erp Products

- Dassault Systemes 3DEXPERIENCE
- ENOVIA

## Industries

- Aerospace
- Defense
- Automotive
- Industrial Equipment
- High-Tech

## Region

Global

## Persona

PLM Architect

## Eyebrow

3DEXPERIENCE + private AI

## Intro

ENOVIA grew out of the MatrixOne data model, where everything is a business object identified by type, name and revision, connected by relationships and governed by policies with states. That model is flexible enough that two ENOVIA installations can look very different, with custom types, attributes and Java Program Objects layered over the standard engineering and change applications.

On the 3DEXPERIENCE platform the same data is surfaced through 3DSpace, 3DDashboard and role-based apps. Users move between these apps all day, but cross-cutting questions still fall into the gaps: which change actions are open against this product, which of its parts are in a pending state, and what did a similar previous change decide.

Answering them means knowing the type and relationship names, writing the right query, and respecting the project and collaborative-space security that governs visibility. That knowledge sits with a few architects, so engineers wait, or they export and analyze data in spreadsheets, which defeats the access model.

Below is how a private AI layer fits next to 3DEXPERIENCE: what it reads, how it preserves the platform's security, where it helps change and release teams, and where Dassault's own capabilities are the simpler answer.

## Pain Points

### Custom schema, scarce expertise

**Detail:** Years of customization add types, attributes and relationships that only a handful of architects understand. Ad hoc questions depend on them.

### Change navigation is slow

**Detail:** Tracing a change request through change actions to affected items, then to downstream ERP and manufacturing, crosses apps and often multiple exports.

### Collaborative-space security is hard to replicate

**Detail:** Exports used for analysis bypass project and collaborative-space controls. Teams then manage sensitive data in uncontrolled copies.

### Documentation is scattered

**Detail:** Requirements, test reports and supplier documents live as document objects, shared drives and email. Finding the governing statement takes time.

### ERP handoff is a recurring audit finding

**Detail:** Released structures reach the ERP through integrations with their own mapping rules. Differences in effectivity and variants are discovered late.

## Use Cases

### Change action impact analysis

**Description:** From a change request or change action, list affected items, parent assemblies and linked documents, then draft an impact summary for the board with object citations.

**Erp Objects:** Change Request, Change Action, affected items, Part, Document, relationships

**Outcome:** Faster board preparation, with analysts reviewing and correcting drafts instead of assembling them.

### Natural-language product structure queries

**Description:** Ask where a part is used, which revision is released in a product, or what changed between two revisions of an assembly.

**Erp Objects:** Part, EBOM relationships, revisions, policy states

**Outcome:** Routine structure questions move from architects to the engineers who ask them.

### Requirement and spec retrieval

**Description:** Answer from controlled specifications and test reports, citing the document object, revision and section.

**Erp Objects:** Document objects, file versions, requirement objects where used

**Outcome:** Less time hunting for the governing requirement before design reviews.

### Release gate checks

**Description:** Check pending items for missing approvals, unreleased children, absent attributes or unmapped ERP fields against your own release rules.

**Erp Objects:** Policy states, route and task objects, required attributes

**Outcome:** Fewer releases bounced late in the process.

### PLM to ERP structure comparison

**Description:** Compare released engineering structures with ERP manufacturing BOMs and list quantity, unit and effectivity differences.

**Erp Objects:** EBOM, ERP BOM and item master, integration mapping tables

**Outcome:** Differences caught at handoff rather than during the first build.

### Supplier and part reuse suggestions

**Description:** Suggest existing parts and approved sources when a new part is being defined, using attributes and past usage.

**Erp Objects:** Part attributes, classification, manufacturer equivalents, ERP vendor records

**Outcome:** Reduced duplicate part creation where classification is reasonably clean.

### Dashboard Q&A

**Description:** Answer questions about program status, open changes and release backlog that feed 3DDashboard views, with the query shown.

**Erp Objects:** Change objects, state counts, program or project attributes

**Outcome:** Managers can ask follow-up questions instead of requesting new dashboard widgets.

## Architecture

**Overview:** The AI service sits beside 3DSpace and uses the platform's authentication and web services. It retrieves evidence under the user's identity, hands it to a private model, and returns cited answers. Write actions are limited to drafts the user submits in the platform.

**Layers:**

#### Identity and access

**Detail:** 3DPassport authentication with delegated tokens or a scoped service account for indexing, so collaborative-space and project security is evaluated by the platform.

#### Data access

**Detail:** 3DEXPERIENCE web services for object search and expansion, plus read-only database views or MQL-based extraction for on-premises ENOVIA where web services do not cover a custom type.

#### Retrieval layer

**Detail:** Structured object lookups with relationship expansion, and a vector index over document content that retains type, name, revision and state for citation.

#### Model layer

**Detail:** Open-weight models served locally with vLLM or Ollama, sized to concurrency, with no outbound inference calls.

#### Governance layer

**Detail:** Per-user audit of prompts and retrieved objects, evaluation sets drawn from real change records, and prompt rules that forbid answering outside retrieved evidence.

## Deployment Options

### On-premises ENOVIA

**Fit:** Programs with classified or controlled data and self-managed platform

**Detail:** All components run on customer GPUs inside the existing network zone, with retrieval through internal services. Suitable for air-gapped environments.

### Private cloud tenancy

**Fit:** Customers running the platform on dedicated infrastructure in their own cloud

**Detail:** Model hosting in the same tenancy and region with private connectivity and customer-managed keys.

### Hybrid with Dassault-hosted platform

**Fit:** Customers on a vendor-managed deployment who want inference under their control

**Detail:** The AI service runs in the customer's environment and calls platform APIs for entitled objects only. Review contract terms on API use and data movement first.

## Compliance

### Controlled technical data remains in a boundary you manage, access is user-level and logged, and nothing is sent to public inference endpoints. Your export-control program continues to govern who may be a user.

**Framework:** ITAR and EAR

### Where CUI is processed, the AI stack follows your system security plan: access control, audit, encryption and media handling are documented with the deployment.

**Framework:** CMMC Level 2 and NIST SP 800-171

### Answers cite released revisions and states; drafts never alter baselines. Formal change records stay in the platform.

**Framework:** AS9100 and configuration control

### For automotive suppliers, change summaries can reference affected control plans and PPAP documents, with approvals kept in the formal process.

**Framework:** IATF 16949 change and PPAP linkage

## Integration Notes

- Authenticate through 3DPassport; keep tokens short-lived and scoped, and avoid shared service accounts for question answering.
- Map your custom types and attributes in a configuration file so the AI layer queries them by real names rather than guessing.
- Expand relationships selectively, such as EBOM and change affected-item links, to keep requests light on the platform.
- On-premises ENOVIA databases are Oracle or SQL Server; read-only views are acceptable for indexing only if they do not bypass security for question answering.
- Retain state and revision as metadata so answers can say whether an item is in work or released.
- Index incrementally by modification date and schedule bulk loads outside engineering hours.

## Product Fit

### Custom build

**Why:** Type models and customizations differ per site, so connectors, prompts and change-drafting agents are built for your schema.

### DataRay

**Why:** A fit when engineering documents, shared drives and ERP data need one private chat interface.

## Engagement

### Discovery

**Duration:** 2 to 3 weeks

**Deliverables:**

- Schema walk-through of types and relationships
- Question inventory from change and release teams
- Security and export-control review
- Interface access plan

### Pilot build

**Duration:** 5 to 6 weeks

**Deliverables:**

- Authenticated connector
- Structure and change retrieval
- Cited answer interface
- Evaluation set

### Workflow agents

**Duration:** 4 weeks

**Deliverables:**

- Change impact draft
- Release gate checks
- ERP structure comparison
- Admin dashboard of usage

### Hardening

**Duration:** 2 to 3 weeks

**Deliverables:**

- Access regression tests
- Upgrade runbook
- Model update process
- Training

## Buyer Questions

- Are queries evaluated with the user's collaborative-space and project access?
- How are custom types and attributes handled, and who maintains the mapping?
- Which platform versions and APIs are supported?
- Can every answer cite object type, name and revision?
- What data leaves the platform and where is it stored?
- How are write actions limited and approved?
- What happens at a platform upgrade?
- Which questions would built-in dashboards or search already solve?

## Faq

### Does this work with on-premises ENOVIA as well as the 3DEXPERIENCE platform?

**Answer:** Yes, with different access paths. The platform exposes web services, while older on-premises installations may need supported extraction methods for custom types. In both cases, the aim is to keep access control in force and avoid bulk exports that bypass it.

### Can the model learn our product data permanently?

**Answer:** Normally it should not. Retrieval fetches current objects at question time, so changes appear immediately and access rules apply. Fine-tuning on product data is optional and raises IP and export-control questions that should be decided separately.

### Do you need to touch CATIA models?

**Answer:** No. Questions are answered from business-object metadata and documents. Geometry analysis is a separate scope and is not needed for impact, BOM or release questions.

### How is this different from Dassault's built-in assistants?

**Answer:** Built-in features are the easier route for tasks inside the apps. A separate layer fits when you need your own hosting, cross-system answers with ERP and quality data, or rules specific to your change process.

### Can it approve changes?

**Answer:** No. It prepares impact summaries and checks. Routes, approvals and signatures stay with named users in the platform.

### How long before value shows?

**Answer:** A read-only pilot over structure and change questions is usually meaningful within one to two months of access being granted. The schedule depends mostly on access approvals and how much customization needs mapping.

### What does it cost to run?

**Answer:** Main costs are GPU hardware or cloud instances, engineering time for mapping and evaluation, and ongoing maintenance. Open-weight models avoid per-token fees, though total cost depends on concurrency and document volume.

## Search terms

3dexperience ai, enovia ai integration, dassault plm ai, enovia llm, 3dexperience private ai, enovia change action automation, enovia bom chatbot, ai for plm aerospace, on-prem ai enovia, 3dspace web services ai, dassault systemes generative ai plm, enovia erp integration

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