Skip to main content

You are tasked with ordering bottled water for an upcoming outdoor event. Bottles cost you $0.10 a piece and you can sell them that night for $2....

Since we make them for $0.10 and sell them for $2.00, each bottle we sell will make us a profit of $1.90.

But since we can only resell them later for $0.05, each bottle we make but do not sell will force us to take a loss of $0.05.

We don't know how many we will sell, but we know that it is normally distributed with a mean of 10,000 and a standard deviation of 1,000. The goal is to find the amount of production that will maximize our expected profit.


To do this, we want to find the point where the marginal expected profit from making another bottle is zero, which is the point where the probability of selling that bottle and making $1.90 is exactly balanced by the probability of not selling that bottle and losing $0.05.
Thus, we know that the following holds, at the desired number of bottles n, with p(n) being the probability of selling the nth bottle:


`p(n) (1.90) - (1-p(n)) (0.05) = 0`


`1.90 p(n) + 0.05 p(n) - 0.05 = 0`


`1.95 p(n) = 0.05`
`p(n) = 0.05/1.95 = 0.0256`


This is essentially a p-value; it's the probability of selling at least that many bottles, when the number of bottles sold is normally distributed. Only the right-tail p-value is important here.

This is actually extremely close to the p-value of z=2, 2 standard deviations above the mean. A more precise z-score is actually 1.95; we want to make enough bottles to cover 1.95 standard deviations above the mean. Below that point, we're likely enough to sell those bottles that it's worth the risk; above that point, the probability of selling them is too low to be worth taking the risk.

Since the mean is 10,000 and the standard deviation is 1,000, 1.95 standard deviations above the mean is 11,950 bottles--just shy of 12,000.

Comments

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...