Skip to content
SteepGraph
Industrial Equipment · 3DEXPERIENCE

Nine Million Objects Into 3DEXPERIENCE Across Multiple Sites, on a Two-Day Go-Live Window

SmarTeam V5, SOLIDWORKS ePDM and a third legacy system migrated to 3DEXPERIENCE 2015x in a two-step, multi-site programme built on SteepGraph’s Data Migration Framework.

A Denmark-based industrial equipment manufacturer operating across multiple sites

At a glance

Industry
Industrial equipment manufacturing
Region
Denmark
Size
5,000–10,000 employees
Platform
3DEXPERIENCE
Our role
End-to-end responsibility through go-live, and support

Results

8,996,611

objects, relationships and files migrated

Go-live delivered inside a 2–3 day window

The challenge and what we did

The challenge

  • Diverse data types — SOLIDWORKS, AutoCAD, Inventor and ME10 data, scanned PDFs, and non-CAD data such as Office documents.
  • A migration data size of 8,996,611 objects, relationships and files, with the storage, transfer and processing that implies.
  • A two-step migration executed across multiple sites, with the coordination and synchronisation that required.
  • Poor source data quality — missing attributes, duplicate records and unsupported characters.

What we did

  • Extracted the data structure from the source system, including relationships and dependencies, to drive mapping and transformation.
  • Applied a selective migration strategy, transferring only the latest released and initial non-released data.
  • Used SteepGraph’s own Data Migration Framework to automate the migration process.
  • Managed a strict two-to-three-day go-live window through detailed planning, coordination and execution.
  • Used a delta migration to transfer only the changes made since the previous run, minimising downtime.

What we found

Three source systems fed this migration, and the data in them was not uniform: SOLIDWORKS, AutoCAD, Inventor and ME10 files sat alongside scanned PDFs and ordinary Office documents. The volume came to 8,996,611 objects, relationships and files. The estate was spread across multiple sites, which meant the migration had to be run in two steps and coordinated between them, and the source data carried the usual legacy problems — missing attributes, duplicate records and characters the target system would not accept.

What we built

The structure was extracted from the source first, relationships and dependencies included, so that mapping and transformation had something reliable to work against. Rather than move everything, a selective strategy carried only the latest released data plus the initial non-released data. SteepGraph’s Data Migration Framework automated the runs. The constraint that shaped the whole programme was the go-live window: two to three days, which left no room for a re-run, so the final cutover used a delta migration carrying only what had changed since the previous pass.

Filed under

  • Industrial Machinery
  • 3DEXPERIENCE
  • Data Migration
  • Engineering Data Management
  • Change Management
  • Data Migration Framework
  • SmarTeam
  • SOLIDWORKS ePDM
  • EBOM

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