Forgive me Ian, but this video is really confusing. You suggest the cycle times are in minutes and seconds which would mean the total time should be 27 minutes. I believe the mean has been calculated wrongly, partly because the total should be 27 not 25 and also because 25/10 should equal 2 minutes 30, not 2 minutes 50. So actually the mean should be 27/10 = 2.7, therefore 2 minutes 42. If the cycle times are purely in minutes then I understand that the total time would be 25 minutes but as explained, the mean should be 2 minutes 30, if this is the case. Then the mode and median become 2 minutes 18. Although I doubt this is the case judging from the set of numbers in your data. I understand the outcome is the same, that the mean is an overestimate compared with the mode and median, but the mathematics confused me! Any clarification from yourself would be a great help, and appreciated.
+Tom Brown Hi Tom. My mistake with this video was not keeping the information uniform across the explanation. I used 2.3 - which to the audience doesn't say anything - is it 2 minutes and 30 seconds (60 + 60 + 30 =150 seconds total) or is it 2 minutes and .3 of a minute (60 + 60 + 18 = 138 seconds) ? I should have kept it all in seconds and then converted afterwards. Your analysis isn't incorrect, but your viewpoint depends upon how you interpret the time. Either way, leaving it up to the audience to assume is not good so I dropped the ball on this one. Thanks for your input.
It cant happen, because if the 6th operation is 3:25 send it the last. While calculating median, you take all your data and put it in sequence - Lower to higher.
![[LIVE] นาทีนี้ต้องพี่ทนาย | ทนายแก้ว vs ทนายไพศาล | #คุยให้เด็กมันฟัง EP.47 (02/11/67)](http://i.ytimg.com/vi/HmquaO-PL_M/mqdefault.jpg)
Brilliant Ian.
Hello thx 4 you video , how do you do if you take time on 3 workers m you are saying that you scale down ,, but in reality how did you do it .. thx
Forgive me Ian, but this video is really confusing. You suggest the cycle times are in minutes and seconds which would mean the total time should be 27 minutes. I believe the mean has been calculated wrongly, partly because the total should be 27 not 25 and also because 25/10 should equal 2 minutes 30, not 2 minutes 50. So actually the mean should be 27/10 = 2.7, therefore 2 minutes 42.
If the cycle times are purely in minutes then I understand that the total time would be 25 minutes but as explained, the mean should be 2 minutes 30, if this is the case. Then the mode and median become 2 minutes 18. Although I doubt this is the case judging from the set of numbers in your data.
I understand the outcome is the same, that the mean is an overestimate compared with the mode and median, but the mathematics confused me! Any clarification from yourself would be a great help, and appreciated.
+Tom Brown Hi Tom. My mistake with this video was not keeping the information uniform across the explanation. I used 2.3 - which to the audience doesn't say anything - is it 2 minutes and 30 seconds (60 + 60 + 30 =150 seconds total) or is it 2 minutes and .3 of a minute (60 + 60 + 18 = 138 seconds) ? I should have kept it all in seconds and then converted afterwards. Your analysis isn't incorrect, but your viewpoint depends upon how you interpret the time. Either way, leaving it up to the audience to assume is not good so I dropped the ball on this one. Thanks for your input.
Tom Brown he specifically said it was in seconds. I understood perfectly
Thanks for sharing the video
For cycle time should one consider also loading and unloading time..
UNMESH CHANDAK no bro. What are you loading? Loading & unloading is periodic work not cycle able work
@@Zepeda117 hi Daniel
How can that be periodic
If the operator need to load part for every cycle run.
Explained in very interesting way.Thanks
Can you share any ideas regarding Kanban calculation for packaging materials such as trays & shipping box. Many thanks in advance, god bless you sir!
Thank you for your feedback. Let me know if you would like me to cover something else. Take care Ian
Thank you Ian, very useful video
Ian. Why is it a bad idea to use your lowest time as your benchmark? Wouldn’t that have the most value added work percentage?
But with averaging being removed, I can't slack and hide my slacking in the "average" mix with Joe, Jim, James, and Jeremy. I'll stick out!
Trank you, Ian! Now I unterstand it.
this was so helpful! thank you for posting this :D
Hello I have a question
What if the sixth observation below was 3.25 what would it happen?
It cant happen, because if the 6th operation is 3:25 send it the last. While calculating median, you take all your data and put it in sequence - Lower to higher.
The cycle time is not the most common, is the lowest repeatable, in this case 2:15
Thanks so much
It not only shows you a better average , it also gives a better average to shoot for 2:30 is better than 2:50
Kiew-nik Neptune Thank you.
do you have facebook that I can follow you?
What about lowest cycle time ?
Sure - you can analyse why the lowest time occured, but it's often a rarity. Always worth looking into.
oi ... my OCD is kicking in ... I would never write 2 min 30 seconds as 2.30 to me that's 2 min 18 seconds.
I'd rather write it as 2:30
I agree. 2.5 minutes (in decimals) is equal to 2:30 (2 minutes 30 seconds)