- 10 Common Misconceptions About Lean Manufacturing
- Ten Reasons Why One Piece Flow Will Not Work
- The Best Visual Control in the World
- Give Me 60 Minutes and I'll Give You a Lean Transformation
- Toyota Owes Grandpa Ford
- Look Up from Your Work and Ask: ;Could We Flow This?
- Ouch! Change Hurts
- E-mail 5S
- The Top 5 Reasons for Using Production Preparation Process (3P)
- You've Gotta Go to Gemba More Often Than That!
- 5S Your Desk: And Other Tips for Office Productivity
- Skill Matrix Enables Suggestion System
- Work Content for Line Leads
- Strong Supervision: The Key to Long-term Kaizen
- The Four Elements for Sustaining Kaizen
- Keys to Sustaining 5S
- Top 10 Improvement Tools Named After Lean Sensei
- Intuition, Information and the Toyota Production System
- Nine Rules for Fighting Endless Meetings
Kaizen of the Month for May 2007: Windows Hack *or* Chopping Away at the Six Big LossesImproving OEE (Overall Equipment Effectiveness) by eliminating the six big losses is the focus of TPM (Total Productive Maintenance). Just as most industrial machinery is only 13% to 40% effective prior to TPM implementation, the same is true for personal computers running Microsoft Windows. The six big losses of TPM are, with some examples: 1) Unplanned breakdowns = overheating, crashes, electrical failures, etc. The first two are categorized as downtime losses, the second two as speed losses, and the third two as quality losses. These fit perfectly to the reduced OEE of personal computers. 1) Unplanned breakdowns = crashing applications Taking the example of 3 in bold, above, I lost some work on Friday thanks to Microsoft Windows' kind reminder to restart after it had installed some updates. The reminder looks like this: Well, no more. Life Hacker teaches how to Get rid of Windows Update restart nag.
This reminds me that there was a question posted some time ago on Autonomous Maintenance for the office. We'll get to that one soon. By Jon Miller - May 27, 2007 11:32 AM |
Comments
|
Jeez - you got me to spend about 30 seconds trying to "restart later" because I thought Windows was really trying to remind me! That's the beauty of Linux, all the layers of crap attempting to improve on a flawed operating system at the bottom are stripped away. I'd switch to Linux but don't have a 12-year-old in my household to do it for all the computers we use. (One is completely unusable because we tried to install a copy of Windows XP. Linux is open source and wouldn't care.) Similarly, a major auto company redoing and extending its order-to-delivery system is condemning itself to continued waste in all sorts of ways. It's layering on top of MRP, and preserving all sorts of constraints, including one that is a survival of the days of keypunched IBM cards. One new routine they're putting in place is to be written in COBOL, one of the early higher-level layers. It will run with every order - millions - and not all that fast. My about-to-retire spouse tried to explain how the routine should be written in assembly language - he says it would be so reliable that the programmer could die and it would never need maintenance - and run a thousand times (my exaggeration probably) faster because it's a closer layer to the bits that actually constitute the computer. But the current folks are afraid of a language that lives mostly in legend at their age. And they don't want to find one of the few gray-haired brainy guys still around who understand it. |











