Disstevefan1
Well-Known Member
So in this example, in order to keep the stand by wait times down to a reasonable wait, up to 15 percent of the riders must use Fastpass?Sure! I don't have my paper with me, but I remember enough of the constraints to explain through it.
I treated both Fatspass and Standby as independent systems to reach the final goal. I had multiple goals and situations broken down.
1) Reach maximum hourly capacity. I used an hourly capacity number I found online as the pinpoint number for every situation. I wanted to make sure the coaster was filled at least 90% of the operating day.
Now, for the actual amounts. They depended on what I was trying to do. I had one situation where my objective was solely to keep the fastpass line at the minimum return time of 6 minutes. There is a saturation point here, as although the standby does not have a waiting constraint, the amount of fastpasses can essentially turn it into another standby line.
To keep it down to 6 minutes, I remember the % of line had to be around 5-15% to keep standby wait times within a reasonable wait. I defined "reasonable" as within some percentage above the average of a Monte Carlo simulation.
If you didn't care about standby, you could push Fastpass to 40% of capacity. But that really effected standby line waits.
I hope that mildly helps! It was a fun project!