Skip to content
Product data & engineeringMachinery & Plant EngineeringConveying & Intralogistics

Size drives from catalogue data

Load, speed and acceleration calculated, motor and gearbox picked from the catalogue, the sizing documented.

Today

Drive sizing for conveyors and machines is recalculated in spreadsheets for every project. Oversized drives cost money, undersized ones fail. Later, hardly anyone knows which assumptions an old sizing was based on.

An example

At Conveyra Fördertechnik, a 12 m roller conveyor has to move pallets up to 500 kg at 0.2 m/s. The agent calculates torque and start-up acceleration, picks a 400 V geared motor from the approved list and documents the margin.
Fictional company, typical workflow.

Your data, wherever it lives

Today layouts and loads sit in CAD, old sizings in calculation spreadsheets on the drive, motor and gearbox data in manufacturers' PDF catalogues and on their websites, the approved drive list in the PLM. demi reads, understands and links them per project and drive, with your rights. The AI sizes the drive in minutes instead of hours, with a versioned calculation and documented margins, and the design engineer decides.

Where the data lives today

  • CAD & drawings
  • Office files
  • Folders & drives
  • PDFs
  • Web & portals
  • PLM
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

    The case needs data from the CAD, PLM, spreadsheets and file share. demi replaces nothing and links layouts and loads to supplier catalogue data, the approved drive list and past sizings. demi only writes back after approval.

  2. 2 · PermitPermission Layer

    Engineers approve the sizing, and only engineering management changes the approved drive list. Every approval is recorded.

  3. 3 · ActIntelligence Layer

    The agent calculates torque and power in your existing sizing tool or in a coded, versioned calculation, never in the language model. It selects from approved catalogue items and documents inputs, results and margins with their sources.

How it runs

  1. 1

    Load, speed and cycle come from the layout.

  2. 2

    The agent calculates torque and power deterministically.

  3. 3

    It picks motor and gearbox from the approved list.

  4. 4

    The sizing, with all margins, goes for release.

What changes

  • Correctly sized drives

  • Approved parts reused

  • Sizings anyone can follow

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

+216 hfreed per year

Assumptions and calculation

demi calculates load and dynamics, picks motor and gearbox from the catalogue and documents it; you check.

2 h → 1.4 h per case

How does it run today?

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

How we calculate

30 drive sizings × 2 h × 30% × 1.0 (manual) × 12 months = 216 h

Value per year, before demi costs

Freed per year+216 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€14,040

gained per year

216 h ÷ 1,760 h per role = 0.1 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

Can we follow how the result was calculated?

Yes. Calculations run in your sizing tool or in a coded calculation with a version number, not in the language model. The same inputs always give the same result. Every sizing names its formulas, inputs and version.

Can it use our approved drive list?

Yes, and only that list if you say so. Supplier catalogue data provides the technical values; the approved list decides what may be selected. If no suitable drive is on it, the agent says so instead of picking something else.

How is the sizing documented?

As a sizing sheet with load assumptions, calculation steps, the selected drive and its margins, filed with the project. If the layout changes, the sizing is recalculated and both versions stay visible.

What if a supplier's catalogue data changes?

New catalogue versions are read in and compared with the old one. The agent shows which existing sizings use a changed item, so engineering can review them.

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