I remember a couple of years ago I was at Melbourne international airport arriving from overseas and calculated the average of cleared passenger every minute and found out that it takes each passenger around 1.5ch minutest to clear. Then a big number of passengers arrived at the queue and it become more packed. The supervisor at the time introduced two more agents. the move helped maintain the same average. I shared my observation with the supervisor and she was so happy to know that someone knows what she was doing. Great video. Thank you
Given how old this video is, I figure you might not see this comment. But you might want to know that the textbook company Cengage is using your video (with credit, but I don't know if it's with payment) in their textbook Operations and Supply Chain Management by David A. Collier and James R. Evans. If they aren't paying you, you might want to look into this. I've already had one other content creator this semester tell me they did not know that their work was being used in this way.
Good concept and explanation. May be I did not get it completely and have questions in mind The concept is - if we control one of the three parameters, (incoming rate/Avg. Queue time/Outgoing Rate) we can have a better user experience and suggestion is to cut the line (half or one/third) meaning we loose the incoming traffic. Now. in a typical business scenario for example eCommerce website, loosing the incoming traffic or cutting the queue, will result in loosing the business?? to which "Little Law does not care but business does"? Alternatively, I believe, We do not (or should not) have control over incoming traffic. Does it make sense rather than cutting on the queues, make the process (throughput) faster? this can/may be achieved by parallel processing (increased throughput) by keeping the queue size max 10 people and keep on creating new queues as more traffic comes in and a new server for throughput. Benefits: keeping the user experience same across the board (queue size has a cap) Serve more incoming requests. (Create new 'queue' & 'server instance' when queue reaches the cap) Increase throughput? (More queue and more Servers mean more throughput) Happy and fast experience (Happy customers means $$$$$) I know this comes with a cost of creating a separate(new) Server for every queue but the process can be managed/load balanced and advance techniques. Hence providing More business $$$ and no kicking out the customers upfront (Cut the queue) Again I might be way off but just attempting to understand little's law and look at it more closely
Hi folks, amazing video. If I want to create a just-in-time process then I need to set L=1 into L=Lambda *W ? If not, how to model just-in-time using Little’s Law? Thank you in advance.
You are talking about Little's Formula right? Processes like a processor in a computer. Because everything you just said applies to my Operating Systems class.
It appears that when describing Little's Law, verbosity and loquaciousness; of the detail and time it takes to describe it, does not apply; however, the factor of 'waiting' and 'customer annoyance' still remains an issue. Come on, now; I'm just joking. : ) Hmm? The failures of utilizing Little's Law kind of reminds me of our Federal and Government agencies, and especially the DMV. ; )
@@ProjectsinLessTime Funny, thank you.😉 While in my youth, I use to read a lot and peruse through my Websters dictionary to write down unfamiliar words for fun. Regrettably, my vocabulary has diminished a bit since then. But a few of the word that I liked the most; a few that still come to mind are; mellifluous, lugubrious, grandiloquent, and portentous. However, with the people I associate with, I rarely get to use these words in my daily spoken speech. I do love the sound of, loquaciousness, and funnier, I tend to write in this style; often writing more than necessary, pleonastically, 😆rather than in talking. Well, maybe my wife would disagree. Anyway, I appreciate the comment. I am happy that I made your day. ; ) Very kind regards.❤️
I remember a couple of years ago I was at Melbourne international airport arriving from overseas and calculated the average of cleared passenger every minute and found out that it takes each passenger around 1.5ch minutest to clear. Then a big number of passengers arrived at the queue and it become more packed. The supervisor at the time introduced two more agents. the move helped maintain the same average. I shared my observation with the supervisor and she was so happy to know that someone knows what she was doing.
Great video. Thank you
Little's Law never dies. Also Thank you Pinnacle!
Given how old this video is, I figure you might not see this comment. But you might want to know that the textbook company Cengage is using your video (with credit, but I don't know if it's with payment) in their textbook Operations and Supply Chain Management by David A. Collier and James R. Evans. If they aren't paying you, you might want to look into this. I've already had one other content creator this semester tell me they did not know that their work was being used in this way.
Thanks! No one has asked me, but as long as I get some credit, that's cool.
So really it is just velocit(throughput)y x time(queue time) = distance(inventory) that you can travel ...
😍
Good concept and explanation.
May be I did not get it completely and have questions in mind
The concept is - if we control one of the three parameters, (incoming rate/Avg. Queue time/Outgoing Rate) we can have a better user experience and suggestion is to cut the line (half or one/third) meaning we loose the incoming traffic.
Now. in a typical business scenario for example eCommerce website, loosing the incoming traffic or cutting the queue, will result in loosing the business?? to which "Little Law does not care but business does"?
Alternatively,
I believe, We do not (or should not) have control over incoming traffic. Does it make sense rather than cutting on the queues, make the process (throughput) faster? this can/may be achieved by parallel processing (increased throughput) by keeping the queue size max 10 people and keep on creating new queues as more traffic comes in and a new server for throughput.
Benefits:
keeping the user experience same across the board (queue size has a cap)
Serve more incoming requests. (Create new 'queue' & 'server instance' when queue reaches the cap)
Increase throughput? (More queue and more Servers mean more throughput)
Happy and fast experience (Happy customers means $$$$$)
I know this comes with a cost of creating a separate(new) Server for every queue but the process can be managed/load balanced and advance techniques. Hence providing More business $$$ and no kicking out the customers upfront (Cut the queue)
Again I might be way off but just attempting to understand little's law and look at it more closely
Hi folks, amazing video. If I want to create a just-in-time process then I need to set L=1 into L=Lambda *W ? If not, how to model just-in-time using Little’s Law? Thank you in advance.
Great explaination!!!
legend
Thanks for your explanation!
Great teacher!!
You are talking about Little's Formula right? Processes like a processor in a computer. Because everything you just said applies to my Operating Systems class.
whats the future of IT sector in India according to u.....?
Really nice :)
Cudos to you !
Isn't it about limiting the WIP?
It appears that when describing Little's Law, verbosity and loquaciousness; of the detail and time it takes to describe it, does not apply; however, the factor of 'waiting' and 'customer annoyance' still remains an issue. Come on, now; I'm just joking. : ) Hmm? The failures of utilizing Little's Law kind of reminds me of our Federal and Government agencies, and especially the DMV. ; )
here to reply because you used loquaciousness in a complete sentence. such rarity. ;-)
@@ProjectsinLessTime Funny, thank you.😉 While in my youth, I use to read a lot and peruse through my Websters dictionary to write down unfamiliar words for fun. Regrettably, my vocabulary has diminished a bit since then. But a few of the word that I liked the most; a few that still come to mind are; mellifluous, lugubrious, grandiloquent, and portentous. However, with the people I associate with, I rarely get to use these words in my daily spoken speech. I do love the sound of, loquaciousness, and funnier, I tend to write in this style; often writing more than necessary, pleonastically, 😆rather than in talking. Well, maybe my wife would disagree. Anyway, I appreciate the comment. I am happy that I made your day. ; ) Very kind regards.❤️
thank you :)
I am not get wat it is 17.5
average customer waiting in line
homeboy is out of breath he should slow down and practice his script more
im dyinggg