Industrial Equipment
Nine million objects from SmarTeam and ePDM
Across multiple sites, live inside a 2–3 day window.
Dassault Systèmes 3DEXPERIENCE
3DEXPERIENCE Migration, Upgrades and Implementation.
We move product data onto 3DEXPERIENCE from SmarTeam, SOLIDWORKS PDM, Windchill and older ENOVIA releases, fit it to how your engineers work, keep it current on-premises or on the cloud, and connect it to SAP and the systems around it.
- Dassault Systèmes C&SI partner
- 12 case studies on 3DEXPERIENCE
- 30+ PLM migration programmes
- ISO 27001 certified
Migration · onto it
Data Migration Framework
- SmarTeam
- SOLIDWORKS PDM
- Designer Central
- ENOVIA V6
- Windchill
- Oracle Agile
Integration · both ways
Integration Framework
- SAP
- Oracle
- Dynamics
- Odoo
- Jira
- Polarion
Upgrades · every release
Test Automation Suite
- 2015x → 2018x
- 2017x → 2021x
- On-premises → Cloud
Where are you today?
Start From Where Your Data Is Today.
Every 3DEXPERIENCE programme we take on starts from one of these six places. Pick yours to see what the work involves and where to go next, with a delivered result wherever one is published.
Moving onto 3DEXPERIENCE from SmarTeam or SOLIDWORKS PDM
A migration, not an upgrade. CAD files, assemblies, BOMs and their revisions are mapped onto the 3DEXPERIENCE data model, to your own servers or straight to the cloud.
What the work involves
- CAD, BOM and non-CAD data mapped and linked
- Big bang, incremental or on demand
- Direct to the cloud with Dassault’s Transition Assistant, or on-premises first
Delivered from here
Moving CATIA V5 data to POWER’BY and the Unified Product Structure
UPS puts CAD and BOM in one data model, so getting there transforms the data. Where customisation is light we migrate directly; where it is heavy we upgrade first and move to UPS second.
What the work involves
- Direct or two-step, chosen by how customised you are
- Attributes, types and links mapped to the UPS schema
- Root assemblies corrected to their latest revisions
Delivered from here
MTorres
Designer Central to POWER’BY in ten months
Migrated and tested with no stop in operations.
Upgrading ENOVIA V6 or an older 3DEXPERIENCE release
The release is rarely the hard part. What was built on it is. We sort every customisation into keep, replace with standard, or retire, then upgrade, re-test and cut over in a window you plan.
What the work involves
- Every JPO, trigger and schema change triaged
- Data upgraded and reconciled
- Regression tests re-run before cutover
Delivered from here
Industrial Equipment
Two million CAD objects upgraded in a weekend
From 2015x to 2018x.
Moving from on-premises 3DEXPERIENCE to 3DEXPERIENCE Cloud
3DEXPERIENCE Cloud runs Dassault’s baseline. JPOs, triggers and custom schema do not move across as they are, so each one is retired, covered by a current app, or rebuilt as a widget, web service or EKL.
What the work involves
- Fit check against the cloud baseline
- Integrations moved onto published APIs
- Data migrated and reconciled
Moving to 3DEXPERIENCE from Windchill, Teamcenter, Oracle Agile or a home-grown PLM
A platform change. Parts, structures, documents and changes are extracted from the source’s own model, reshaped for 3DEXPERIENCE, and reconciled record by record before engineering signs off.
What the work involves
- Extraction by API, database, files or custom
- Full history, or latest release only: your call
- Every exception listed in the reconciliation
Delivered from here
Ericsson
Over a billion records from 40+ applications into 3DEXPERIENCE
The story is one load from that programme: Windchill Product Analytics.
Already live on 3DEXPERIENCE, and it has to do more
New roles and apps, dashboards that answer management’s questions, change processes that match how you work, and ERP receiving the released BOM without anyone re-keying it.
What the work involves
- Roles, apps and change processes configured
- Dashboards and widgets for each role
- SAP and other ERP connected on our framework
Delivered from here
Renewable Energy
230+ widgets, one view from BU head to CEO
NETVIBES dashboards built per department and role.
Functional areas
From CAD to the CEO’s Dashboard.
3DEXPERIENCE runs engineering, change, manufacturing and programme management on one data model. These are the areas we have implemented, migrated and upgraded, under the role names Dassault uses today, each with a customer story behind it.
CATIA · SOLIDWORKS
Engineering data and multi-CAD
- Collaborative Designer for CATIA V5
- Collaborative Designer for SOLIDWORKS
ENOVIA
BOM and product structure
- Product Release Engineer
- Product Structure Editor
ENOVIA
Engineering change
- Change Manager
- Change Execution
ENOVIA
Configuration and effectivity
- Configuration Engineer
ENOVIA
Documents and libraries
- Collaborative Industry Innovator
DELMIA
Engineering to manufacturing
- Manufacturing Items Engineer
ENOVIA
Projects and portfolios
- Project Manager
- Project Portfolio Manager
3DEXPERIENCE
Dashboards and search
- Enterprise Data Science
- 3DEXPERIENCE OnePart
Migration onto 3DEXPERIENCE
Every Route In Runs the Same Six Stages.
SmarTeam, SOLIDWORKS PDM, Designer Central, Windchill or Agile: the source changes, the method does not. Each run is configured for your source and your 3DEXPERIENCE data model, fixes problems before the data lands, and ends in a record-level reconciliation.
Extract
Is the right data coming out?
- Parts, BOMs and documents
- CAD files and their links
- API, database, files or custom
Transform
Did it change as expected?
- Mapped to your data model
- CAD and BOM onto UPS
- Revisions and states mapped
Validate
Will 3DEXPERIENCE accept it?
- Naming and numbering rules
- Mandatory attributes
- Duplicates and missing links
Correct
Fixed before it lands?
- Invalid values cleaned
- Broken links rebuilt
- Assemblies to latest revision
Load
In order, and at volume?
- Parts before structures
- Parallel, multi-threaded loads
- Delta loads for cutover
Reconcile
Does it match?
- Record-level counts and deltas
- Structures and files
- Every exception, listed
Delivered onto 3DEXPERIENCE
All 12 case studiesEricsson
Over a billion records from 40+ applications into 3DEXPERIENCE
The story is one load from that programme: Windchill Product Analytics.
Industrial Equipment
Nine million objects from SmarTeam and ePDM
Across multiple sites, live inside a 2–3 day window.
MTorres
Designer Central to POWER’BY in ten months
Migrated and tested with no stop in operations.
More on this:Data Migration FrameworkData migration servicesUPS migration, simplifiedWebinar: the MTorres UPS migration
Implementation
Build It the Way the Next Release Expects.
How you extend 3DEXPERIENCE decides what every upgrade costs, and whether you can move to the cloud at all. So we start from Dassault’s roles and apps, configure before we build, and build in the forms that move with the platform.
LayerStandard, configuredExtended, in forms that move
What people see3DDashboard
Standard, configured
- Roles and apps by user group
- Dashboards by department
- Views and columns
Extended, in forms that moveCustom dashboard widgets
How work movesChange and lifecycle
Standard, configured
- Change actions and approvals
- Maturity states
- Routes and notifications
Extended, in forms that moveEKL rules for your own checks
What the data isData model
Standard, configured
- Types and attributes
- Naming and numbering
- Access by role
Extended, in forms that moveWeb services for your own logic
How the product is builtStructures and CAD
Standard, configured
- EBOM and MBOM
- CATIA ↔ ENOVIA continuity
- Configuration and variants
Extended, in forms that moveCAD and BOM automation
What we keep to a minimumNew JPOs, triggers and custom schema. They slow every upgrade, and they do not move to the cloud as they are.
Delivered on 3DEXPERIENCE
Renewable Energy
230+ widgets, one view from BU head to CEO
NETVIBES dashboards built per department and role.
Fashion Retail
Forty enhancements, then the upgrade to 2021x
Migration scripts rewritten to run in parallel.
Around the rollout:Implementation servicesRole-based training and adoptionAgenticOS (AI) for Implementation
Upgrades and cloud
Two Ways to Stay Current. Both Start With What You Built.
Dassault ships a new 3DEXPERIENCE release every year, with functional deliveries in between. On-premises, you decide when to move; on the cloud, the platform moves on Dassault’s schedule. Either way, the effort is set by what was customised.
PathWhat movesYour customisationWho upgrades, and whenHow it is proven
On-premises release upgradeWhat movesYour estate, to a current releaseYour customisationTriaged: keep, replace with standard, or retireWho upgrades, and whenYou, in a window you planHow it is provenRegression suite re-run before cutover
Move to 3DEXPERIENCE CloudWhat movesOnto Dassault’s cloud baselineYour customisationJPOs, triggers and custom schema rebuilt as widgets, web services or EKLWho upgrades, and whenDassault, on its scheduleHow it is provenRegression suite re-run at every update
Delivered on 3DEXPERIENCE
Industrial Equipment
Two million CAD objects upgraded in a weekend
From 2015x to 2018x.
Aerospace
2017x to 2021x, and a move to Azure, in three days
On-premises to Azure private cloud with the upgrade.
MTorres
A three-day upgrade on the two-step route to UPS
2017x to 2021x first, then POWER’BY.
Ericsson
Five years of automated 3DEXPERIENCE regression testing
Around 2,500 use cases, re-run on every release.
More on this:Upgrade and modernisationTest Automation SuiteQuality assuranceApplication maintenance and support
Integration
From Released in 3DEXPERIENCE to Ready in SAP.
When a change action is released, SAP or your other ERP needs the parts, the EBOM or MBOM and the documents that go with them. On our Integration Framework each exchange is a configured flow: checked, mapped to the other system’s model, delivered and logged, with every failure alerted.
Delivered on 3DEXPERIENCE
Oil & Gas
One search across SmarTeam and ePDM
Built as a custom ONEPART connector.
Electric Vehicles
Issue and change intelligence on NETVIBES
Twenty-five widgets, and the connectors behind them.
More on this:Integration FrameworkSystem integration services
Runs in Docker, on your servers or hosted by SteepGraph.
3DEXPERIENCE services
Tell Us Where Your 3DEXPERIENCE Estate Is Today.
Bring the starting point: the source system and rough volumes, the release you are on, or the systems on the other side. We’ll show you how we would approach it, and say plainly where we wouldn’t.
FAQ
Frequently Asked Questions
It is a migration, not an upgrade. CAD files, assemblies, BOMs and their revisions are mapped onto the 3DEXPERIENCE data model and reconciled before anyone signs off. You choose big bang, incremental or on demand, and either straight to 3DEXPERIENCE Cloud with Dassault’s Transition Assistant or on-premises first. One programme moved nearly nine million objects, relationships and files from SmarTeam and SOLIDWORKS ePDM, and went live inside a 2–3 day window.
The Unified Product Structure puts CAD and BOM data in one data model, shared across CATIA, ENOVIA and DELMIA. Getting there from Designer Central or SmarTeam transforms the data, so plan it as a migration rather than an upgrade. Where customisation is light we migrate directly; where it is heavy we upgrade to a current release first and move to UPS second. One machinery manufacturer made the move in ten months without stopping operations.
It depends far more on what was customised than on how many releases you are behind. So we start there: every JPO, trigger and schema change is sorted into keep, replace with standard, or retire. Then the data is upgraded, the regression tests are re-run, and the cutover happens in a window you plan. We have taken 2015x to 2018x, with two million CAD objects, over a single weekend, and 2017x to 2021x in three days.
It turns mostly on what you have customised and how you integrate. 3DEXPERIENCE Cloud runs Dassault’s baseline and takes each new release on Dassault’s schedule. JPOs, triggers and custom schema do not move across as they are, so each one is retired, covered by a current app, or rebuilt as a widget, a web service or EKL. We start with a fit check of your customisations and integrations against the cloud baseline.
Through our Integration Framework. When a change action is released, the parts, EBOM or MBOM and documents are checked on the way in, mapped to SAP’s model and delivered, with every run recorded and every failure alerted and retried. The same framework connects Oracle, Microsoft Dynamics, Epicor, IFS and Odoo, ALM tools such as Jira and Polarion, and EPLAN.