Skip to content
Data & IT: legacy data, formats, connectorsPumps & ValvesMachinery & Plant EngineeringMetal & MachiningTool & Mold Making+1

From the file share into PLM, cleanly

demi derives part number, revision, assembly and status from file names, title blocks and folders and moves the files in after approval.

Today

Twenty years of design work sit on the file share: hundreds of thousands of files in customer and project folders, named like shaft_new_final2 and without a reliable part number or revision. For a PLM rollout, someone would have to open and classify every file. So rollouts drag on for years, or the legacy data stays outside.

An example

Norvelta is introducing a PLM. The file share holds about 240,000 files from 25 years, sorted by customer and mold number, with names like Kern_neu_final2.dwg. demi assigns 204,000 files with certainty, finds 31,000 duplicates and sends 4,800 files without a clear revision to engineering for review. After approval demi moves the molds into PLM customer by customer, starting with the molds for running series.
Fictional company, typical workflow.

Your data, wherever it lives

Your design data lives today in folders on the file share and the NAS: CAD models, drawings and PDFs from many years, with part numbers and orders in the ERP and the new PLM still empty. demi reads, understands and links them, with your rights. The AI classifies hundreds of thousands of files that someone would otherwise have to open one by one, and engineering approves what goes into PLM.

Where the data lives today

  • NAS & hard disks
  • Folders & drives
  • CAD & drawings
  • PDFs
  • PLM
  • ERP
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: the file share, NAS, CAD, PLM and ERP. demi replaces nothing and reads each file with its path, name, date, title block and the references between assemblies and parts; part numbers, orders and customers come from the ERP. For each file this gives a proposal for part number, revision, assembly and release status, every value with its origin.

  2. 2 · PermitPermission Layer

    Folder rights stay in force: customer projects are visible only to those who can see them today. A file goes into PLM only after the responsible person in engineering has approved the proposal, and every transfer is recorded.

  3. 3 · ActIntelligence Layer

    The agent recognizes patterns in names and folders, reads title blocks and follows assembly references. It finds duplicates through identical files and identical geometry under different names. Certain proposals go for approval in batches, uncertain ones for review one by one, and after approval demi writes the data into PLM through its import interface.

How it runs

  1. 1

    Connect the file share, NAS, ERP and the new PLM

  2. 2

    Read names, paths, title blocks and assembly references of every file

  3. 3

    Propose part number, revision, assembly and status per file, with origin

  4. 4

    Review duplicates and uncertain cases, approve certain proposals in batches

  5. 5

    Move the files with metadata into PLM after approval, folder by folder

What changes

  • Legacy data moves into PLM instead of staying on the file share

  • Duplicates and orphaned files cleaned up before the move

  • The PLM rollout does not stall on legacy data

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+320 hfreed per year

Assumptions and calculation

demi proposes part number, revision and status for each file and finds duplicates; engineering approves.

5 min → 3 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

800 CAD files × 5 min × 40% × 1.0 (manual) × 12 months = 19,200 min = 320 h

Value per year, before demi costs

Freed per year+320 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$20,800

gained per year

320 h ÷ 1,760 h per role = 0.2 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

How does demi know part number and revision when the file name says nothing?

From several sources at once: the drawing's title block, the folder path, references from the assembly, orders in the ERP and the file date. Each proposal shows where every value comes from. If the sources disagree, the file goes to review instead of being guessed.

How does demi find duplicates on the file share?

demi recognizes identical files by their content, even under another name. For parts the agent also compares geometry and so finds copies with small differences. It proposes which file leads; engineering decides.

Does engineering have to stop work for the migration?

No. The files stay on the file share until you retire it. After approval demi moves folder by folder and shows at any time what is already in PLM and what is still missing. Files changed during the switch are flagged for reconciliation.

Does it work with our PLM?

demi writes through the import and programming interfaces common PLM systems offer, or produces an import package your PLM reads in. We clarify which route fits in a conversation. You define the target structure, number ranges and attributes beforehand.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases