KnowledgeSphere
Independent 3DEXPERIENCE services

3DEXPERIENCE, ENOVIA and CATIA V5 support.

A 3DPassport sign-in loop, a promote that fails for one role, an xCAD save that leaves half a structure, an assembly that takes twenty minutes to open: each needs a reproducible test. Bring one issue to a free support session of up to 5 hours. We record the release, FD level, users and operation, then agree the next diagnostic step.

I run 3DEXPERIENCE or CATIA

One failed operation, a slow assembly or an interface that drops transfers.

Request 5 hours of free supportOr discuss a scoped project
I'm a Dassault Systèmes partner

Your customer needs integration, customisation or platform work your team can't staff this month.

Discuss a work packageHow the specialist bench works
We work with
  • 3DEXPERIENCE cloud & on-premise
  • ENOVIA
  • CATIA V5 / 3DEXPERIENCE CATIA
  • SOLIDWORKS · Creo · NX · Inventor · AutoCAD connectors
  • MQL · JPO · EKL
  • SAP
  • Dynamics 365
  • REST · middleware
Who we help

Three reasons people get in touch.

Companies using Dassault Systèmes software

Something on 3DEXPERIENCE or in CATIA is failing, slow or due for an upgrade.

Example requirement “Promote to Released fails for the quality role since the last FD, and the error only names a trigger.”

  • Access, maturity and sign-in incidents
  • Slow CATIA assemblies and xCAD save failures
  • Release and FD upgrades
Request support
Dassault Systèmes partners

Your customer project needs a defined ENOVIA work package or a second specialist.

Example requirement “We need access-matrix testing and a JPO impact review for an R2026x upgrade, three days a week for six weeks.”

  • Configuration and test execution
  • Upgrade and customisation impact reviews
  • Escalations and support cover
Discuss a partner requirement
Engineers and administrators

You want to work through a specific CATIA or ENOVIA task with a specialist.

Example requirement “I want to understand cache and CGR loading on our own V5 assembly before we change anything.”

  • One-to-one consultations
  • CATIA assembly diagnostics
  • ENOVIA administration topics
Enquire about training or consultation
What the work looks like

Practical problems, practical outcomes.

Three examples of the kind of problem we take on.

Diagram: a support ticket is recorded, reproduced and isolated, ending in a findings note that lists what fails, what passes, the cause and the next test
Support

Incidents that keep coming back

A promote fails for one security context, a conversion job dies overnight, or the same access ticket returns after every FD. We reproduce it, correlate the logs and leave a written record.

Typical problems

  • Promote fails with a trigger message
  • Jobs that fail without telling anyone
  • Access fixed per user, again and again
  • No notes after go-live

What you get

  • Reproducible incident record
  • Evidence from 3DSpace, FCS or client logs
  • A tested fix or the next test
  • Notes your admins can keep

Technical support

Diagram: a promote runs a check trigger that either lets the object reach Frozen or blocks it, with the extension inventoried and covered by regression tests
Customisation

Customisations you can still upgrade

We inventory JPOs, triggers, EKL rules and widgets, record what invokes each one, and leave tests you can rerun on the next release.

Typical problems

  • Triggers nobody dares touch
  • Checks that block valid promotes
  • Custom code blocking an FD upgrade
  • Manual steps users work around

What you get

  • Inventory with extension points
  • Valid, rejected and repeat tests
  • Configuration before code
  • Handover notes for your team

Customisation and automation

Released BOM flowing from 3DEXPERIENCE through validation to ERP, with a retry queue 3DEXPERIENCE EBOM-1042 Rev B · Released Validate UoM · plant children first ERP Material + BOM Posted ✓ Error queue MAT-5521: UoM missing fix → replay Daily reconciliation: PLM vs ERP example data · all items matched
Example integration patternNothing fails silently
Integration

ERP transfers you can trace

Agree whether ERP receives the EBOM or a manufacturing structure, who owns plant and unit of measure, and how a failed or repeated transfer is recognised and recovered.

Typical problems

  • BOMs re-keyed into ERP by hand
  • Transfers that fail silently
  • Duplicates after a retry
  • Nobody owns plant or UoM

What you get

  • EBOM/MBOM scope agreed
  • Field mapping with owners
  • Transfer identity and acknowledgement
  • Reconciliation and a runbook

PLM, CAD and ERP integration

How an engagement starts

Three ways to start. Pick the one closest to where you are.

One specific symptom

Start with free support

Up to 5 hours to understand the issue and tell you what to check or do next. No obligation.

Request free support
Need a scope first

Essentials assessment Paid

A written problem statement, recommended next steps, a proposed scope and an effort estimate. You approve the fee before it starts.

Ask about an assessment
Scope already clear

Discuss a scoped project

Upgrade, migration, integration, customisation or configuration with a defined goal. We reply with questions, then a proposal.

Discuss a project
For Dassault Systèmes partners

We support Dassault Systèmes partners with customer delivery.

When your team is fully booked or a project needs a specialist, we work alongside your consultants on implementation, troubleshooting and customer support. You keep the customer relationship.

Hands-on

The person you talk to does the work

No hand-off from sales to a junior team. The first conversation is with the people who will read the logs.

Independent

No licences to sell

Our advice isn't tied to selling software. Where standard configuration does the job, we'll say so.

Fast response

Published coverage and response targets

Weekday evenings 17:30–23:30 IST and a Saturday half-day. New enquiries answered by the next coverage day. See the targets.

Written

Clear notes, not just calls

Findings, next steps and scope are written down, so your team can act on them and keep them. See sample deliverables.

Questions

Before you get in touch

What's the catch with 5 hours of free support?

There isn't one. It's how we show what working with us is like. You bring one specific issue, we spend up to 5 hours understanding it and telling you what to check or do next, and there's no obligation afterwards. If the issue isn't a good fit, we'll say so early.

Are you a Dassault Systèmes partner or reseller?

No. KnowledgeSphere is an independent services and implementation team. We don't sell licences. We work directly for companies that use Dassault Systèmes software, and alongside DS partners on their customer projects.

What can 5 hours of free support actually achieve?

Enough to understand a specific problem properly: when it happens, what it affects, what has already been tried and what to check next. Some issues are resolved in that time; many aren't. Either way you get an honest view of the next step.

What should I send in my first message?

A short description of the problem, the product and release if you know it, and how it affects your work. Please don't send passwords, credentials, confidential CAD files or customer data at first contact.

Do you work with our existing partner or IT team?

Yes. We can work alongside your partner, your internal administrators or both. We keep each other informed so nobody is surprised.

Do you support 3DEXPERIENCE on-premise and on the cloud?

Both. What can be configured or customised differs between on-premise and cloud, so we confirm what your release and deployment allow before proposing anything.

Describe the failed operation, release and deployment.

Describe it in a few lines. If it's a good fit, we'll use up to 5 hours of free support to understand it and tell you plainly what to check or do next.