了解如何提升工作效率和提高质量标准，学会分析和改善服务业或制造业商务流程。主要概念包括流程分析、瓶颈、流程速率和库存量等。成功完成本课程后，您可以运用所学技能处理现实商务挑战，这也是沃顿商学院商务基础专项课程的组成部分。
响应力单元班次 7 视频课程
Loading...
Из курса от партнера University of Pennsylvania
运营管理概论（中文版）
29 оценки
Из урока
第 4 单元 - 质量
质量并不是运营管理唯一的重点，但是质量对于企业长期发展和成功至关重要。本模块将介绍运营中与质量的几个主要方面，导致缺陷的常见原因、发现质量问题以及保障可靠性和标准的常用实践方法。本模块教学结束后，您将了解缺陷可能发生的原因，并且能针对质量和稳定性提出合理的方法。
Познакомьтесь с преподавателями
Christian TerwieschAndrew M. Heller Professor at the Wharton School, Senior Fellow Leonard Davis Institute for Health Economics Co-Director, Mack Institute of Innovation Management
The Wharton School
So far in this module, we have assumed that every customer that comes through our
process would be willing to wait, and would be able to wait until it is their
turn. That means as a consequence of that, we
assume that every unit of demand that came to us was served eventually.
Maybe not as quickly as the naive analysis would've suggested, but everyone that came
into the process would be leaving the process as a served customer.
In this session, we consider what happens if customers are unwilling or unable to
wait. In that case, customers will leave the
process before we've actually served them. In other words, our outflow, our completed
flow rate, will differ from the inflow from the demand rate.
We'll introduce a simple mathematical tool that helps us predict what fraction of the
demand we will be able to serve in this case.
Once again, we will focus on process flow diagrams that are very simple and just
include one resource, potentially those with multiple servers.
Now, on the very left of the slide, we see the situation that we've analyze so far in
this module. We have a resource and we have a waiting
line. Now, let's move from the very left to the
right. You can imagine that customers are
impatient and after a while, get tired of waiting and they abandon the waiting line.
Examples of this would be an emergency room where patients after a couple of
hours waiting might just quit or a call center where customers hang up if you have
had them wait too long. Further on the right, we can imagine that
some customers might not even enter the system when the line is very busy.
Think about a drive thru restaurant. Imagine, you're pulling in at a
McDonald's, where there are three parking lots at a busy road.
If all these three parking lots are full, well, pulling in will not work and you
have to keep on driving on. So, the customer gets lost from the
perspective of the server, if there's not enough space to store them here in
inventory. In the very extreme case, waiting time is
just not an option. If you cannot serve the customer
immediately, the customer will be lost. Notice all these cases are related, as we
move from, for example, to the very left to the right here.
We are just adding some impatience of the customer as we move from here to here.
We have basically just said that the size of this inventory equals to zero.
We have focused the previous session on this very left case.
We will focus this session on the right case.
Now, there are mathematical models to also analyze the cases in between, but they're
a little bit more tedious than what I would like to do in this first course on
operations management. Consider yet another health care example.
We previously talked about emergency rooms.
Big inventories in front of a resource. Next, consider the case of trauma care.
Patients that have to be moved to trauma care, they're so acutely sick that waiting
is not an option. What happens if all the trauma bays and
all the trauma capacity in a hospital is busy?
The hospital goes in what is called diversion.
It tells the regional fire and rescue to stop sending ambulances or helicopters.
Simply put, the demand rate is shut down. Now, let's analyze the situation.
As before, we have a random demand process.
Say, for the sake of argument, a patient comes in every three hours.
We will enforce in this session here that the CVa is equals to one, in that we're
dealing with exponential inter-arrival times.
On the service process, we find that in this trauma center, patients stay on
average in a trauma bay for two hours. This is nothing else but our good old
friend, the processing time. Again, it is naive to believe that Dr.
Toyota like, the patients would stay exactly two hours in the hospital buthe
can have many distribution. So, it turns out that the standard
deviation of this distribution will not matter for our analysis.
The magic number that we want to compute is a probability with which an incoming
customer will not be served. This is an important number.
Once I know this probability, I can multiply this with the demand rate.
And I can compute the number of customers that get lost, as well as the number of
customers that get served. So, how do we find that probablity?
It turns out that there's a big mathematical formula that computes a
probability as a function of the numbers of servers, the processing time, and the
inter-arrival time. I will show you that formula just in a
moment, but you will thank me one day that you will not have to use it.
Here's how I want you to find out the probability.
The first thing I want you to do is compute the ratio between the processing
time and the inter-arrival time. I would prefer that you don't try to
interpret that number just call it r for ratio.
Next, you look at how many resources do you have or how many services do you have
in that resource. And so, in this case we have three trauma
bays, m3. = three.
And then, the last thing that you need to do is you need to go into a big table that
I will provide you. And in this table, you're going to go in
to row r and you're going to go into column m.
And where row and column meet, you will have the diversion probability.
In this case, 2.55%.. Again, once you have this number, you are
in good shape. If you want to figure what percentage of
the time and the date the hospital is on diversion, just multiply 24 hours with
2.55%.. If you want to figure out how many
patients that you're going to lose because of diversion, remember that we have a
patient arriving every a units of time, Which is one every three hours so eight
patients per day. And if you multiply this with 2.55%,
you'll figure out how many patients we lose.
Similarly, if you're going to take one minus that probability, we can figure out
how many patients that we have served. Again, figuring out this probability is at
the heart of dealing with the subs of loss problems.
In this graph, that shows the relationship between the implied utilization and the
probability that all servers are utilized. Let me emphasize why I plot the implied
utilization here compared to the utilization which is what we drew in the
graph while we looked at how Tq is increasing with utilization.
Remember, that in the Tq model, the assumption was that u was less than 100%..
While implied utilization over 100% if I have the situation where demand exceeds
capacity, the line here would just go through the roof.
This is not a matter of variability, this is a matter of insufficient capacity.
Things are different in this type of model we are discussing right now.
Here, if I have demand exceeding capacity, the system simply clears up itself.
It just drops customers from the system. These customers get lost.
And even in the situation where I have 50% more demand than I have capacity, I
actually will observe on occasional idle time at the resource.
Alright, so this is why I plot here the relationship between the implied
utilization, and the probability that all servers are busy.
In order to set for 50% utilization, I have about a 30% probability that all
servers are busy. If you think about the fire truck, for
example, and assuming that you don't want to have a really long waiting line of
calls asking for 911 support, waiting for the fire truck,
You notice that at a 50% utilization of the fire truck, 30% of the calls would
actually get a problem. The other thing that you see in this graph
is the power of pooling. At an m equals one, one individual fire
truck, at a 50% utilization my service is going to be a disaster.
If however, I'm able to pool demand, and I'm moving up from m equals one to m
equals, say twenty, I can afford to run a much higher level of utilization and
provide still decent responsiveness. This is very similar to the example that
we had in the case of pooling in the Tq formula.
Let's look at a specific example. I mentioned earlier on the trauma center,
where I have three trauma base. And a customer coming in every three
hours, processing time was two hours. Let's ask ourself what would happen if I
would pool two such systems, If I would pool this hospital with another
hospital that also has an a equals to three, P equals to two, and m equals to
three. Alright.
Let's figure this out. Once I have pooled the two hospitals, I
have an m equal to six. My processing time would not be affected
by the pooling, and stays at two hours. However, now I have more demand.
I have had a customer come in every three hours in one hospital.
I have a customer come in every three hours in the other hospital.
So, I have a new inter-arrival time of 1.5.
To see this, just go to timeline. If you have one customer every three hours
from the one system, One customer every three hours on the
other system and you know that the pool demand has a shorter inter-arrival time.
Now, how do I take m equals six, P equals two and a equals 1.5 and figure
out the probability of waiting. While I promised you at some point I would
show you the formula, so here it is. This is a model known as the Erlang Loss
Formula. Mr.
Erlang was an engineer working for the Danish telephone company some hundred
years ago. His job was to figure out is what
likelihood all the telephone lines would be busy.
He came up with a lots of cool math, including the one that we're discussing
right here. So, you'll notice that the table I gave
you earlier on was a little on the small side, and as we're now looking at an m6
equals to six and then rP/A equals P over one a equals to two divided by 1.5,
I would need this bigger table. So, let's take a look.
And them m equals to six and then 1.33, I'm looking at a 0.2% probability of
diversion. So, notice again this is the power of
pooling. I've not added any capacity.
I've just pooled the system, I pooled the demand, I pooled the capacity, and I'm
dramatically improving the level of service.
Buffer or suffer. That's what we're set when we first
encounter variability in our process analysis module a long time ago.
Buffer or suffer. If we cannot buffer our customers because
they're either not willing or able to wait we will have to suffer a loss of
[UNKNOWN]. Buffer or suffer. In this session, we introduced the Erlang
loss formula as a way of predicting how bad that suffering of flow rate really
will be. We computed what percentage of demand
would be unserved, if the occupancy or the utilization of the resource is high.
We notice that once again, the variability was a root cause of all the problems.
Ознакомьтесь с нашим каталогом
Присоединяйтесь бесплатно и получайте персонализированные рекомендации, обновления и предложения.
Coursera делает лучшее в мире образование доступным каждому, предлагая онлайн-курсы от ведущих университетов и организаций.
© Coursera Inc., 2018 Все права защищены.
