Math buffs: A probability question for you.

Whew, OK now you’re making sense. :slight_smile:

The fault is partly mine.

The OP is a real life situation. To make my work situation understandable to the lay person, I analogized it as I did in my OP.

The “Cabinets” are actually machines. Machines designed to hold these “Widgets”. These widgets are sensitive material. They can not simply be stored outside the machine. Nor can these expensive machines be jerry rigged to keep the doors open.

And truth be told, they don’t actually randomly “lock” their doors. What they do, is break down a lot. When they do break down, it usually takes a tech an hour to get it back up and running again. During that hour we are unable to retrieve the widgets.

So basically you were dumbing it down for me. Uh huh. I see. Well, don’t do me any fuckin’ favors, m’kay bud? (kidding :slight_smile: :slight_smile: )

But it’s good for me to be reminded of my social ineptness with some regularity. Here for example, I should have tried to look a little past the exact literal facts and tried to think a little about what might have been behind them being aware (in theory at least) of the limitations of this medium.

And no I’m not just putting myself down for sport, I need to do this from time to time so it sinks in. Some people need to practice juggling more than one ball at a time. And I’m going to get right on that, probably tomorrow. :smack:

The bolded part above is what makes your problem different than the OP’s problem (and therefore your solution different than the OP’s solution).

Sounds like you need more redundancy. But since you’re probably not allowed to put your material on multiple machines and I’m guessing you can’t implement things like RAIDs to improve server reliability, then it doesn’t matter where the widgets are distributed.

However, in real life there are other factors to consider. If a particular widget is unavailable, can a user request another widget to work on while waiting? If so, then you don’t want to put them all in the same cabinet.

I thought he had said they locked at least once a day, but the closest he came was saying

Wouldn’t it always be a matter of choosing between variance and stability? As a thought experiment, let’s compare a situation where all 1000 widgets are in one machine vs. a hypothetical where they are in 1000 different machines (one widget per machine). If we accept that each will lock 1 hour per day, the first scenario ensures one break down per day, but only one per day. The latter, on a good day, will likely not breakdown, but on a bad day, you could be down essentially all day.

The only wrinkle is that multiple machines can be locked at once. Seeing that that can happen I would lean slightly towards putting them all in one because you get less upside from spreading them out if all the machines could theoretically be locked simultaneously.

I think it would come down to a few outside factors like:

  1. Do the machines “lock” as a result of use/overuse
  2. Can multiple machines be fixed at once?
  3. Are the machines serviced or replaced at a regular interval w/o regard to use.
  4. Are the repair people on call or on site?
  5. Can you mitigate the lost labor costs during downtime if you knew roughly when it would occur?