Engineering & PLMFree templatePDF, Excel, Word exportDassault ENOVIA

ENOVIA Private AI Layer Blueprint Generator

This generator drafts an architecture plan for a private AI assistant on on-prem ENOVIA or 3DEXPERIENCE. It starts from the supported interfaces and the user's security context.

Fill in

Live preview
Download:

ENOVIA Private AI Layer Blueprint Generator

1. Context

Meridian Propulsion Corp runs 3DEXPERIENCE R2023x on Oracle (Air-gapped). 500 named users across 4 site(s). Target go-live: 2027-06-30.

Use cases: Engineering item and structure queries, change action impact, document Q and A, lifecycle state questions.

Must stay on site: Export controlled technical data, program designs, supplier proprietary data.

2. Components

ComponentDesign for 3DEXPERIENCE R2023xNotes
Data access pathMQL and Java API (Context per user) or JPOs for custom schema; 3DSpace web services where deployedNo direct reads of kernel tables
Retrieval indexLocal index over document files and object metadata with type, policy, state and revision on each chunkRe-indexed by modification date per type
Model servingOpen-weight model on vLLM, GPU: 4 x 80 GB or moreLocal embeddings and reranker
Tool serverNamed actions: find object, expand structure, where-used, change action impactParameterised, read-only
Identity and permissionsPerson, role and security context of the real user; policy state access applied by the kernelLive re-check before display
AuditLog of user, security context, calls, object ids and answerImmutable store

3. Security controls mapped to your inputs

Hosting: Air-gapped. Weights, packages and updates arrive by controlled media and the model host has no outbound route.

For Export controlled technical data, program designs, supplier proprietary data.: contexts are opened per user with their security context; indexed text carries policy and state and is re-verified before display.

No model-composed MQL that modifies objects. Phase 3 writes use supported operations so triggers and policy checks fire.

4. Rollout

PhaseScopeExit criteria
1: Read-onlyObject, structure, change and document Q and A for one programAccuracy on a reviewed set of questions
2: DraftsChange action summaries, review packsReviewer acceptance
3: Approved actionsSupported creates and promotes with approvalTrigger behaviour tested in non-production

5. Open questions for IT

1. Which types, policies and attributes are customised? 2. Are 3DSpace web services deployed and secured? 3. How does 3DPassport or SSO map to ENOVIA persons? 4. Where are file stores and what read path may extraction use? 5. Which triggers fire on writes?

Prepared by / Date
PLM owner / Date
IT security / Date

A starting plan. Heavily customised ENOVIA models differ per site, so confirm every type, policy and attribute name with your administrators.

Plan review for ENOVIA

Optional: a short review of your plan with attention to security contexts and custom schema.

Optional. The tool and every export work without this. No spam.

How to use it

Choose your platform release, database and hosting, then list the use cases and the data that cannot leave. The air-gapped option changes the controls text to cover media-based updates. Export the plan and bring it to your PLM and security owners.

The method behind it

ENOVIA authorises by person, role and security context, then applies policy state access. The plan opens a context per user so the kernel enforces this, uses MQL, the Java API or web services for bounded reads and keeps writes to supported operations that fire triggers.

Reading the plan

Customisation is the main risk. The plan's tool actions must be written against your own types and attributes. The open questions list is a good agenda for a workshop with your ENOVIA developers.

Common mistakes

Using a super-user context, letting a model run raw MQL, and quoting content without its policy state. Another is assuming cloud 3DEXPERIENCE features apply to an on-prem platform.

Frequently Asked Questions

Does it cover 3DEXPERIENCE on Dassault's cloud?

No. It targets platforms you run yourselves. Cloud tenancies have different interfaces and data boundary questions.

MQL or web services?

Use web services for standard modelers if deployed and secured, and MQL or JPOs for custom schema and precise control. Either way, wrap each as a named action.

How large a GPU estate for 500 users?

A common range is two to four 80 GB GPUs, but it depends on model size and concurrency. Use the companion calculator and then test under load.

Is air-gapped really workable?

Yes. Model weights, containers and packages are imported through a controlled process, and nothing in the stack needs internet access at run time.

Netray can review your plan with your ENOVIA team. The generator itself is complete without contact.