The same product runs better on machine 2
Compare the recipes and see which setpoints explain the gap, instead of blaming the equipment.
RMS
Best recipe
The problemThe best batch happened once, and nobody knows how to repeat it.
intellifix · Best recipe
Production lines
What it does
The best run, turned into the standard.
The ideal recipe on each machine, comparing the standard with the best real run.
- Standard recipe versus the best real run
- Golden batch by product and machine
- Setpoint tuning to repeat the best result
Real screens
This is the product, not a mockup.
intellifix · Best recipe
intellifix · Best recipe
How it works
From the data that comes in to the decision that goes out.
-
1
Batch history is loaded
Every run of the product on each machine comes in with its setpoints and its result.
-
2
Runs get ranked
Yield, quality and consumption decide which run was actually the best, not the one people remember.
-
3
Standard versus best real run
The two recipes are compared setpoint by setpoint, so the difference is visible instead of being a hunch.
-
4
The tuned recipe becomes the standard
It goes back to the machine as the new reference, and the next batch is measured against it.
Requirements
What it takes to go live.
Data it needs
Batch history
This is the hard requirement. Without it, the capability has nothing to read.
What the plant needs
- Batch history with setpoints and result per run.
- Product and machine register, so a run knows where it happened.
- A criterion for best: yield, quality or consumption.
- Who approves a change to the standard recipe.
Where it acts in the plant
The stage of the operation it plugs into.
Results delivered
What becomes possible.
- The best run stops being a story and becomes a recipe anyone can load.
- The gap between two machines running the same product finally has a name: the setpoints.
- A change to the standard recipe goes in with the run that justifies it attached.
- Every new batch is measured against the best one, not against the average.
Examples of use
On the floor, it looks like this.
The batch everybody remembers
The run from last quarter is found, opened and turned into a repeatable recipe.
The raw material changed
Find the recipe that held the result with the new supplier and make it the standard.
Benefits by role
What each person gets.
Operation
The shift opens the recipe already tuned, with the setpoints that held the best result.
Quality and process
Standard and best real run side by side, and a change defended with the run that proves it.
Management
Which products still run below their own best, and where tuning the recipe pays off first.
Integrations
It does not work alone.
Every capability reads from and feeds the others. What this one exchanges inside the operation:
IPM
Monitor the process
Readings per stage are what make a batch comparable. Without them, history is a start and an end, with nothing in between.
Open capability
APC
Stabilize the process
This capability says which setpoints to hold. Stabilization is what holds them while the process drifts.
Open capability
QCP
Quality and deviations
The quality result of the batch is what ranks the run, and what says the new standard is really better.
Open capability
RMS
Want to see this on your own data?
Bring the history of one product on two machines. In the demo we find the best run and compare the setpoints.