Skip to content
SteepGraph
Electrical & Electronics · 3DEXPERIENCE

An ENOVIA Estate Moved to 3DEXPERIENCE With Revision Sequences and Vaults Intact

ENOVIA migrated to 3DEXPERIENCE 15x across change management, SOLIDWORKS CAD specifications, documents, libraries and vaults, with a delta migration run after go-live.

An Ireland-based electrical and electronics manufacturer

At a glance

Industry
Electrical and electronics manufacturing
Region
Ireland
Platform
3DEXPERIENCE
Our role
Data Migration Framework, migration iteration execution, performance, scalability, go-live and support

The challenge and what we did

The challenge

  • Performance issues across the migration runs.
  • Conflicts in common components data when receiving information simultaneously from two distinct source applications.
  • Conflicts in files derived from those two different source applications.
  • Memory issues specifically during the migration of historical data.
  • Complexity in migrating SQL to SQL, particularly for historical data and revision sequences, and in indexing the data efficiently after loading.

What we did

  • Migrated revision sequences intact, preserving the chronological order and integrity of revisions through the transition.
  • Migrated the stores, locations and vaults structures across to the target system.
  • Resolved the performance issues through database tuning and the use of adapters.
  • Ran a delta migration after go-live to capture data created during downtime, so the system stayed current without a complete reload.

What we found

The migration ran out of ENOVIA into 3DEXPERIENCE 15x, and the scope was broad: change management, CAD specifications for SOLIDWORKS data, parts, drawing prints and generic customer documents along with their files, common components data such as routes, tasks and issues, libraries, export control classes, workspaces, vaults, projects, business units and plants. Two distinct source applications fed the same target, which produced conflicts in both the common components data and the files themselves. History was the hardest part — migrating it raised memory issues, and moving revision sequences from SQL to SQL without losing their order was the most delicate piece of the work.

What we built

Revision sequences were migrated with their chronological order and integrity preserved. Stores, locations and vaults were carried across as structures rather than rebuilt. Performance was brought under control through database tuning and adapters, and indexing was addressed after the load rather than being allowed to stall it. After go-live a delta migration captured everything created during the downtime window, so the system was current on day one without a full reload.

Filed under

  • Electronics & Semiconductor
  • 3DEXPERIENCE
  • Data Migration
  • Change Management
  • Engineering Data Management
  • ENOVIA

The services and products this project used, and an expert to talk to about yours.

Talk to a 3DEXPERIENCE expert

We’d like to use Google Analytics cookies to understand how visitors use this site. No analytics cookies are set unless you accept. Privacy Policy