Waste — Automating Manual Process Steps Through Macros
Six Sigma – iSixSigma › Forums › General Forums › Tools & Templates › Waste — Automating Manual Process Steps Through Macros
- This topic has 6 replies, 3 voices, and was last updated 8 years, 7 months ago by
Jeremiah Lewis.
-
AuthorPosts
-
December 18, 2013 at 7:20 am #54625
Automation of manual process steps through Macros – Which Lean Tool is used and in which type of waste this can be classified?
0December 18, 2013 at 11:47 am #196369If you’re talking Excel or Word, that’s probably the VBA or Visual Basic Application tool. Of course, macros also have the ability to significantly increase work if they’re not developed or used appropriately.
From a Lean perspective, you’re eliminating extra movements and wasted time.
0December 19, 2013 at 2:34 am #196376
Prabhu VParticipant@prabhuvspjInclude @prabhuvspj in your post and this person will
be notified via email.Automated process is known for eliminating labor costs, it is one of a family of four work processes characterized (Artisan Process, Project Process, Operations Process, Automated Process)
From my opinion, it may attack all 8 types of wastes as defined by the Lean principles as below.Transport
Inventory
Motion
Waiting
Over processing
Over production
Defects
Skills (Under-utilized)Regards
Prabhu V.
0December 19, 2013 at 7:59 am #196377Lean technique that can be used is ‘Just in Time (JIT)’ to identify and eliminate waste. Waste type is ‘Over Processing’.
0December 19, 2013 at 7:38 pm #196380Hi Rajiv,
As far as I understand, Automation can not be a primary Lean Solution. We have to optimize the process first, reduce wastes and then think of (possible) automation. Goal of Automation is more about Poka-yoke than reducing/eliminating wastes.
Think this in terms of a Highway; you may reach faster, the wrong destination!
So, I hope you have optimized the manual steps and then thinking of writing a macro to speed it up.
0December 30, 2013 at 7:12 am #196431
Jeremiah LewisParticipant@jerestatInclude @jerestat in your post and this person will
be notified via email.I echo all that has been noted about VBA macros. Don’t automate a bad process.
Also, you may get caught up in writing code so much that the time spent writing, debugging, and maintaining code may be more than would be saved from automating the process. Writing the code may be an educational experience and therefore good to do but be careful.
0December 30, 2013 at 7:18 am #196432
Jeremiah LewisParticipant@jerestatInclude @jerestat in your post and this person will
be notified via email.Most of the time, the process you automate will be too complex to just record and have VBA write the code for you. You almost always will have to modify the code somewhat.
If your code is versatile enough to handle the nuances of data entry, user errors, and consistently get the correct output then it is worthwhile. This will not only save time but ensure that the output is correct.
I recommend trying to make it break the system and doing a series of DOE’s on the code to test its robustness.
0 -
AuthorPosts
You must be logged in to reply to this topic.