>
Community >
Forums
|
|
|
02/03/2012 10:19 AM
|
|
|
1. A rule for calculating cycle time of a process is to head out on the floor with a stopwatch. However, is it ever more appropriate to use solid production data when it's available?
2. When you're determining the cycle time at the bottom of the VSM, do you divide the C/T by the number of operators in the process to get the value added process time? Just how does the crewing and shifts impact the cycle time? Any resources that might go a little deeper into this?
|
|
|
|
|
02/03/2012 02:54 PM
|
|
|
1) Your "solid production data" is not nearly as solid as you think it is. Head out to the floor and carefully observe. Challenge your data.
2) Cycle time has more than one definition, and it is important to be clear about what you mean when you use the term. See my post on this -
http://theleanthinker.com/2010...ime-cycle-time/
In any case, dividing by the number of operators does not get you your value added processing time. You can really only determine that by actually watching the operation and parsing out which operations truly advance the work vs. just moving things around, etc.
Mod note: edited to clarify authorship of link
Edited: 02/03/2012 at 02:55 PM by Lean Moderator
|
|
|
|
|
02/03/2012 06:06 PM
|
|
|
Daniel,
Here is a definition of Cycle Time that may help you:
The amount of time to accomplish the standard work sequence for one product, excluding queue (wait) time. This is another way of describing what Mark was referring to regarding item #2.
Ken
|
|
|
|
Note: These forums are moderated by the Lean Enterprise Institute. All posts are reviewed prior to appearing on the site. Views expressed in these forums do not necessarily represent the views of the Lean Enterprise Institute.
Send to a Friend
