Today
Every printed flight part or implant needs proof of the powder, the parameters and the machine it came from, and that its witness coupons passed. That data sits in machine files, lab results, certificates from subcontractors and spreadsheets tracking powder reuse. Today someone assembles each part's pedigree by hand, and a deviation in the powder or a layer image often surfaces only when the customer asks.
An example
At Rennhardt Aerospace, 24 brackets AB-7740 in Ti6Al4V, printed in one build job on machine 2, are up for release. The pedigree shows that the powder lot is in its ninth cycle and that its last analysis is at 0.18 % oxygen, just under the 0.20 % limit. From layer 812, the layer images show a raised edge on three brackets at the plate border where the recoater scrapes; the tensile coupons from the same job are fine. Quality releases 21 brackets, blocks three pending CT and has the powder lot refreshed with virgin powder.
Your data, wherever it lives
A printed part's data sits in many places today: build files and layer images on the printer and in folders, powder certificates as PDFs, sieving and reuse cycles in spreadsheets, tensile tests in the LIMS, heat treatment on the subcontractor's certificate, lots in the ERP. demi reads, understands and links them per part, with your rights. The pedigree is ready in minutes instead of after hours of searching, and quality decides on release.
Where the data lives today
- Machines & sensors
- Photos, video & audio
- Databases
- PDFs
- Office files
- QM system
- ERP
- Folders & drives
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
Data sources in this case: printers, the LIMS, the QMS, the ERP, spreadsheets and the file share. demi replaces nothing and links powder lots with sieving, blending and analyses, build jobs with parameter set, machine log and layer images, plus heat treatment, HIP, tensile tests, CT and dimensional inspection. Every part gets a pedigree from powder to release.
- 2 · PermitPermission Layer
Build files and parameter sets are your know-how and often export-controlled, so only cleared people see them. Quality and production see the pedigree, the customer only the released version. Only an authorised person in quality may release or block a part, and every decision is recorded with a name.
- 3 · ActIntelligence Layer
The agent checks every pedigree with fixed rules against the specification and the process approval: powder reuse cycles and oxygen content, parameter set, build chamber atmosphere, coupon positions and test results. On the layer images it marks anomalies with layer and position. The language model reads certificates and logs and explains each deviation; quality decides whether a part is released.
How it runs
- 1
For each build job, demi takes the build file, parameter set, machine log and layer images from the printer.
- 2
The agent assigns the powder lot with its sieving, blending, reuse cycles and analyses.
- 3
Heat treatment, HIP, tensile tests, CT and dimensional inspection join each part as soon as they are booked.
- 4
It checks every pedigree against specification and process approval and marks each deviation with its evidence.
- 5
Quality decides on release, block or retest, and the pedigree goes into the part's file.
What changes
A complete pedigree per part, from powder to release
Deviations surface before release, not at the customer
Release documents for customer and authority without a hunt
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
+192 hfreed per year
Assumptions and calculation
demi links powder, build job, post-processing and tests per part; quality releases it.
2 h → 1.2 h per case
How we calculate
20 build jobs × 2 h × 40% × 1.0 (manual) × 12 months = 192 h
Value per year, before demi costs
Freed per year+192 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
+€12,480
gained per year
192 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
What data does the printer provide for the pedigree?
Build job, parameter set and machine log with build chamber oxygen and recoater events, plus the layer images and, where available, melt pool monitoring data. demi reads the files the machine writes anyway. How they get from the machine to demi, we clarify in a conversation.
How does demi track reused powder across many build jobs?
Through the powder lots in the sieving, blending and loading bookings. Each blend gets a new lot with its parent lots, cycles and analysis values. If a booking is missing, the agent shows the gap instead of assuming an origin.
Does demi judge the layer images itself?
The agent marks anomalies such as raised edges, short feeds or spatter with layer, position and affected part. Your quality team sets the criteria it marks by. Whether a part is fine is for quality to decide, after a CT scan if needed.
Who releases a printed part?
An authorised person in your quality team, as today. The agent prepares the pedigree and the release document and names every open deviation. Signature, block and concession stay with that person, and everything is recorded.
