Today
Before release, engineers check limits, sizing and safety factors by hand. The same checks are repeated in every project, and under time pressure one gets skipped now and then. The error only shows up in production or at the customer.
An example
Before pumping station PS-12 at Hartwig & Brunn Pumpenwerk is released, designed for Q 120 m³/h and H 80 m, the agent recalculates pipe losses and NPSH with the company's own tool. It reports that the NPSH margin at maximum flow falls below the internal rule and cites the section of the in-house standard.
Your data, wherever it lives
Design data sits today in CAD and the PLM, your calculations in spreadsheets and the department's own tools, standards as licensed PDFs in the standards library and in-house rules in the DMS. demi reads, understands and links them per product and project, with your rights: only people with a license see a standard's text. The same checks run before every release in minutes, even under deadline pressure, and the responsible engineer decides on every deviation.
Where the data lives today
- CAD & drawings
- PLM
- Office files
- PDFs
- DMS & archive
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, CAD, DMS and spreadsheets. demi replaces nothing and links design data, your calculation tools, the standards library and in-house rules to the product and project. demi writes back only after approval.
- 2 · PermitPermission Layer
Standards stay licensed per person, so everyone sees only the standards they hold a license for. The responsible engineer makes the release decision, and every check goes into the project file.
- 3 · ActIntelligence Layer
The agent prepares the inputs and runs your existing calculation tools or coded, versioned calculations, for example for pressure losses, NPSH or safety factors; the language model does not calculate itself. It compares the results with the limits and reports every deviation with its clause.
How it runs
- 1
The design is submitted for checking before release.
- 2
The case needs the inputs from PLM and CAD.
- 3
The calculation runs in your existing tool.
- 4
It compares the results with the standard and in-house rules.
- 5
The check report, with clauses, is attached to the release.
What changes
Fewer design errors reaching production
The same checks in every project
Standards knowledge available to every engineer
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
+216 hfreed per year
Assumptions and calculation
demi checks the limits against standard and in-house rule and cites the clause; you judge and decide.
2 h → 1.4 h per case
How we calculate
30 standards checks × 2 h × 30% × 1.0 (manual) × 12 months = 216 h
Value per year, before demi costs
Freed per year+216 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
+$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 packageQuestions about this use case
Does the AI do the calculations itself?
No. Calculations run in your existing tools or in coded, versioned calculations that always return the same result for the same inputs. The model prepares the inputs, compares and explains. Every result can be recalculated.
Which standards can it check?
The standards and in-house rules you have and are licensed for. demi brings no standards texts of its own; it works with your library. Anything that can be expressed as a limit, a formula or a rule can be checked.
How are the results documented?
Every check produces a report with inputs, tool and version, result, limit and clause. The report is attached to the project and the design revision, so you can see later what was checked against which revision.
Who decides on release?
The responsible engineer. The agent reports deviations and never releases anything itself. The decision and its reason are recorded, also when a deviation is accepted on purpose.
