@dopiotrek This was the point I needed for Automating Confusion (issue 37), your post on AI has its limits on a small factory floor: https://t.co/Dpr8qShAM3. Thanks!
Will Your People Share What They Know With AI?
One post argues that people who think AI is coming for their jobs will keep what they know to themselves. No source this week measures whether that happens...
https://t.co/Dpr8qShAM3
#Manufacturing#AI#TheoryOfConstraints
@BlueCollarAI_ This was the point I needed for Automating Confusion (issue 36), your post on AI drafts schedules and the person who knows the work signs off: https://t.co/JhHK64gs6N. Thanks!
Toyota's SAP Team Added Locks After AI-assisted Upgrade
Toyota added locks after an automatic retry ran against a system that had just restarted. A schedule can go stale the same way. If you keep redoing...
https://t.co/JhHK64gs6N
#Manufacturing#AI#TheoryOfConstraints
@VedantOps This was the point I needed for Automating Confusion (issue 35), your post on sample data versus real factory data: https://t.co/wFMfritonA. Thanks!
Siemens Reports 20% More Throughput and Names No Baseline
Siemens says an initial customer deployment increased throughput by 20% and names no customer or baseline. An arXiv paper reports its tardiness...
https://t.co/wFMfritonA
#Manufacturing#AI#TheoryOfConstraints
@DavidCrysler@JasonPremoMFG Your point that a shop can have every screen and scheduler imaginable and still have no one owning the next order made Issue 34. Thank you for adding it to Premo's thread. https://t.co/vcwBiRO2xk
@JasonPremoMFG Your 2010 schedule boards story is in Issue 34. The part that stuck with me: the ownership came from people moving the magnets themselves, not just from the data. https://t.co/vcwBiRNuHM
@Oldhandai@oimatrixioYT Your line "You watch it run" made Issue 34. It is the same habit AI agents need: check the result, not the claim. https://t.co/vcwBiRO2xk
@izziebuilds@proof_of_nick Your "prove-out ritual" is in Issue 34. Even when the code is accurate, someone still has to prove out the first part on the machine. Thank you for saying it so plainly. https://t.co/vcwBiRNuHM
@OSHBuilt Your swing set demo is the lead story in Issue 34. What got me was your API telling Claude "we can't do that" and Claude redesigning inside the 45 degree limit. The software did the enforcing. https://t.co/vcwBiRO2xk
Who Enforces the Rules in Your Shop?
OSH Cut's design check rejected AI-designed tube parts, and the AI redesigned them to fit the laser. A benchmark found AI models slip when scheduling requirements are...
https://t.co/vcwBiRNuHM
#Manufacturing#AI#TheoryOfConstraints
@mkadnk@7SwanSwimming@OSHBuilt This was the point I needed for Automating Confusion (issue 33), your point that a $30k-$200k agent-ready system would force you to double your $60/hour shop rate: https://t.co/IeQT7gGKVF. Thanks!
@OSHBuilt@izziebuilds Your point that: "There's no reason for the machine to be involved in planning or scheduling or DFM... It's a solved problem." made it into Automating Confusion (issue 33): https://t.co/IeQT7gGd67. Thanks!
97% Say AI Runs Their Workflows. 62% Still Call Planning Their Hardest Problem.
Fictiv found 97% of leaders say AI is embedded everywhere while 62% call planning their hardest problem, ERP builders on X say...
https://t.co/IeQT7gGKVF
#Manufacturing#AI#TheoryOfConstraints