Today
Every order variant starts with someone copying an old BOM and editing it by hand. Invalid combinations reach production. And the variant knowledge sits with a few people.
An example
At Conveyra Fördertechnik, a conveyor layout arrives with 46 m of straight sections, 4 curves and 2 lifts at a belt width of 800 mm. The agent derives a BOM with 312 items and blocks a drive that is too small for the stated 500 kg load.
Your data, wherever it lives
Customer requirements arrive today by e-mail and as PDF specifications, layouts as CAD drawings, the product structure and past variant BOMs sit in the PLM and ERP, and the configuration rules in spreadsheets only a few people maintain. demi reads, understands and links them per option and assembly, with your rights. The AI derives the BOM in minutes instead of hours of copying and blocks invalid combinations before production, and engineering decides on every deviation.
Where the data lives today
- E-mails
- PDFs
- CAD & drawings
- PLM
- ERP
- Office files
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the PLM, ERP, CAD and spreadsheets. demi replaces nothing and links configuration rules, modular product structures, layouts and past variant BOMs; each option is tied to the assemblies it brings in. demi writes back only after approval.
- 2 · PermitPermission Layer
Engineers approve variant BOMs, and product management approves changes to the rule set. Both are recorded.
- 3 · ActIntelligence Layer
The agent maps requirements to options and derives the BOM from the rule set, even straight from a layout with lengths and curves; invalid combinations are blocked, not just flagged. Anything that needs new design work goes on the deviation list, each line with its rule.
How it runs
- 1
The customer requirement or layout comes from the quote or CAD.
- 2
The agent maps the requirements to options.
- 3
It checks the combination against the rule set.
- 4
It derives the BOM by rule.
- 5
The deviation list goes to engineering.
What changes
Faster order engineering
Invalid variants stopped before production
Variant knowledge kept in rules, not in heads
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.
Your numbers
Result
+432 hfreed per year
Assumptions and calculation
demi derives a rule-compliant variant with its bill of materials; you check and approve.
3 h → 2.1 h per case
How we calculate
40 variants × 3 h × 30% × 1.0 (manual) × 12 months = 432 h
Value per year, before demi costs
Freed per year+432 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
+€28,080
gained per year
432 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 packageQuestions about this use case
Can it use our existing configuration rules?
Yes. Rules from your configurator, your ERP or your spreadsheets are taken over, not reinvented. Where rules only exist implicitly in old BOMs, the agent proposes them and product management confirms them.
What happens to requirements outside the rules?
They go on the deviation list, with a reference to the requirement that caused them. Engineering decides whether a special solution is needed. If it becomes a new option, it is added to the rule set after release.
Does it work for furniture and other configurable products?
Yes. The principle is the same: options, rules, assemblies. Conveyor line, pump unit or wall unit, the agent works with your rule set and your product structure.
Does the BOM get written back?
Yes, once engineering has released it. demi writes back only after that release. Every variant stays linked to the requirements it came from.
