From a note at the machine to standard work
Follow one filter, F-101, from a note at 02:40 to a change every shift holds.
1Capture2Connect3Execute4Verify
One cycle, four steps
Before step 1: one problem, one owner, success criteria agreed up front.
-
A note at the machine, at 02:40.
The shift lead adds a photo and a few words on the phone at 02:40.
-
The note lands next to the machine data.
The analysis looks back over earlier batch changes and the order of products. Each blockage came after the thick material; batch changes after other products did not block. That becomes a hypothesis.
-
Your people test it on the floor.
They test it at the next three batch changes after the thick material. It holds, so it goes into standard work.
A disproved hypothesis is a valid outcome.
-
Every shift confirms it is done.
Each shift confirms it with a photo, a reading or a sign-off.
F-101Open
- Problem
- F-101 blocks after batch change
- Owner
- Process engineering
- Success
- No F-101 stop after a batch change
23:20Running the thick material.
Voice · 0:12Photo02:40
“Blocked again, after the switch from the thick material. Flushed longer, pump at half until it ran clear.”
04:30Line running, pump back up.
06:00Handover: F-101 blocked at 02:40.
02:40“Blocked again, after the switch from the thick material. Flushed longer, pump at half until it ran clear.”
Hypothesis to test
After the thick material, the filter stays clear with a longer flush and the pump at half.
Same patternMon 13:20Tue 04:10Wed 14:40Thu 02:05
Proposed by the analysis. Your people decide.
Hypothesis to testAfter the thick material, the filter stays clear with a longer flush and the pump at half.
Test on the floor After the thick material: flush longer, pump at half until it runs clear.
- Batch change 1Thu 15:40
- Batch change 2Fri 06:20
- Batch change 3Fri 20:10
Standard work updatedF-101: after the thick material, flush longer, pump at half until it runs clear.
Standard workF-101: after the thick material, flush longer, pump at half until it runs clear.
- PhotoSat 06:00
- ReadingSat 14:00
- Sign-offSat 22:00
Fits how you already improve
Oppr works inside the way you already improve. It adds what the shift saw, next to the data, and a check on every shift.
Lean
A tested change goes where it belongs, into standard work.
SQDC
The morning meeting sees the shift's note next to the trend.
DMAIC
Analyse on the timeline. Improve with a floor test. Control with the shift check.
How we start
We digitize only what an improvement needs.
- First week
A process walk with the people who run the line.
- First month
Data and notes on one timeline, the first floor test.
- Then
The first improvement holds and goes into standard work.
- After
Your team runs the cycle, then the next line, only if the case justifies it.
What it takes to start
A local extract from your historian or ERP, or the Excel files your teams keep, is usually enough. Notes go in on the phone the shift already carries.
We provide the platform and the IT behind it, and we keep it running.
Data and IT questions How much time it takes from your teamStart with one problem on one line.
Tell us one problem in your process. We reply with a few questions. If Oppr is a good fit, we walk the line with your people.