Critical know-how is trapped in experts' heads and scattered documents
When the expert is not there, the line stops
New hires take 2 months to reach basic autonomy
Turnover is the #1 problem - and every departure erases knowledge
20-60
Minutes to troubleshoot
without guidance
< 60%
OEE in some areas
Alpin Socks Factory - Cankiri, Turkey
Meet the People
Akin
Operator
First responder on the shop floor. When the light turns orange, he's there.
Alpin Socks
Seren
Mid Technician
The troubleshooter. Armed with a tablet and Yoshu.
Alpin Socks
Basri
Manager Tech
The decision maker. Validates, escalates, owns the process.
Alpin Socks
Stefano
Tech Support
The expert upstream. At Lonati HQ, he writes the playbook.
Lonati
Scenario 1 - The Known Problem
Error 142019. Again.
A Lonati GK machine throws Yarn Tension error 142019. Five times in one hour. The line is bleeding production.
ERR 142019 - YARN TENSION - LONATI GK
Scenario 1
Akin Calls Seren. Yoshu Has the Answer.
Seren arrives with her tablet. She opens Yoshu. Instantly, she sees:
Error history - what happened before on this machine
Actions taken - what was tried and when
The right procedure - step by step, validated by experts
No searching. No calling colleagues. No guessing.
Scenario 1
Sensor Replaced. Back to Production.
RESOLVED
Following Yoshu's procedure, Seren identifies a faulty sensor and replaces it. Green lights. Machine running.
A mid-level technician resolved in 5 minutes what used to take the entire shift to figure out.
Scenario 1 - Impact
That's the Yoshu Effect.
5 min
Time to Resolution
Was 20-60 min without Yoshu
100%
Procedures Available
Every error code covered, 24/7
L2
Resolution Level
Mid-tech resolves what needed a manager
0
Phone Calls Made
No interrupting the expert's day
?
But What Happens When Nobody Has the Answer?
Known problems are easy. The real test is what happens when a problem is genuinely new.
Scenario 2 - The Unknown Problem
Same Error. Fix Doesn't Hold.
Error 142019 is back. Seren follows the procedure, replaces the sensor - but the error keeps recurring. Defect rate is climbing.
She checks Yoshu again. This time:
NO EXISTING SOLUTION
All known procedures exhausted. This is genuinely new.
Scenario 2
Yoshu Bridges Two Companies
Basri validates it's a new problem. Through Yoshu, he escalates directly to Stefano at Lonati HQ - with full context: machine data, error history, every procedure already attempted.
Alpin Socks - Turkey
Lonati HQ - Italy
Scenario 2
Stefano Creates a New Procedure
At Lonati HQ, Stefano reviews the full context Yoshu provides. After running internal tests, he develops a new fix.
But here's what changes everything:
Yoshu records the new procedure in real-time as Stefano works through it
Every step is captured - not in a manual that takes months to update, but instantly
Scenario 2
Click. Fixed.
Back at Alpin, Seren applies Stefano's new procedure through Yoshu. The machine is running. Green lights.
NEW PROCEDURE DEPLOYED
This is the Yoshu Effect
One Fix. Every Factory.
Stefano solved it once. Yoshu published it to the network. Now 100% of Lonati users worldwide have the new procedure. Next time, any operator can resolve it in minutes.
Measurable Impact
Before & After Yoshu
Without Yoshu
60 minTroubleshooting time
L3-L4Escalation needed
2 moTraining to autonomy
0%Knowledge captured
MonthsNew procedure rollout
With Yoshu
< 5 minTroubleshooting time
L2Mid-tech resolves it
< 1 moTraining to autonomy
100%Every fix, every time
InstantPublished to network
The Scale Ahead
From One Factory to a Network
Alpin Socks is the beginning. The same Yoshu effect scales to every Lonati machine in the world.
1
Pilot Factory
Alpin Socks
→
150K+
Lonati Machines
Worldwide network
Every deployment makes the network smarter. Every fix is permanent. The Yoshu effect compounds.