went to the world this weekend.. and idk if this is just an ak problem because I didnt really experience it at any of the other parks, but while we were there, there was a posted wait time for kali of 70 min. We decided to wait since it was really hot, but surprisingly enough, we literally walked right on. When we left I noticed the wait time was still posted at 70 min.. Headed over to Everest, posted time of 30, and we waited almost 50.. Should disney stay on top of the wait times? seems to me like they are really off
-
Welcome to the WDWMAGIC.COM Forums!
Please take a look around, and feel free to sign up and join the community.
Disney Needs More Accuracy With Wait Times
- Thread starter MickeyMind
- Start date
Mansion Butler
Active Member
Wait time cards are sent every few minutes, and many (most now, I think) attractions have people watching on camera trained to read wait time by visual read adjusting it when the cards aren't registering properly/fast enough.
I can't imagine how it could be done much more efficiently. It's not an easy science, especially at certain times of the day.
SyracuseOrange
Well-Known Member
Sometimes guests mess with the wait time displays. Also, it's a good strategy to over guess the times; restaurants do it too. If you see a wait time that is long, but then you get on the ride in a shorter time than was posted, you are happy. If they lower the time and you end up waiting longer than the posted time, Disney has an angry guest on their hands.
Rob562
Well-Known Member
Inattentive Guests who have been asked to carry a FLIK card through the line can also mess up the wait times. If they forget to turn in the card when they get to the front of the line, or even worse, they do turn it in but on a subsequent ride later on, it'll mess up the system.
The system calculates the time between the scans of the card at the end and front of the lines, and uses that toward figuring the posted wait times. So if an errand scan throws things off, it can take some time for it to correct itself. (Managers can go in and override it, but they often have more important things to worry about)
-Rob
The system calculates the time between the scans of the card at the end and front of the lines, and uses that toward figuring the posted wait times. So if an errand scan throws things off, it can take some time for it to correct itself. (Managers can go in and override it, but they often have more important things to worry about)
-Rob
thelookingglass
Well-Known Member
FLIK is a poorly thought out system. Even if the card is scanned correctly, its still updating the system with what that person's wait time WAS, not what the wait time currently IS.
That person may have waited 30 minutes, but what if barely anyone got in line after them? Or a big rush of people?
That person may have waited 30 minutes, but what if barely anyone got in line after them? Or a big rush of people?
Mad Stitch
Well-Known Member
^ Or something like the Nemo show lets out and the masses flock next door to Everest. Overall I think Disney does a good job managing it seeing that it’s not an exact science.
Until they implement NextGen technology with RFID's in theme park tickets, that could measure your movement within a queue, as well as the amount of people ahead of you and behind you, FLIK is the best they can do - it's been working fairly well for years.
dreamfinder
Well-Known Member
Remember that the waits were what was experienced that long ago. So if it says 30 minutes, it means that the last person with a card took 30 mins to get through the line. If a hoard of people joined the line, or they had to temporarily stop/slow down for an assisted board, then your wait would be longer.
castevens
Member
This is one thing that can be fixed though. The computer should recognize that 5+ people who were handed the card AFTER this particular person reached the end of the line BEFORE this particular person. While this is theoretically possible when lines split, they system coding should not allow things of this nature to affect it if it crosses a certain threshold of believability.
PurpleDragon
Well-Known Member
I've never had a real issue with this. Usually the wait times are only off by maybe 5 or 10 minutes when I'm there. I've had a few random incidents where the sign read 30 minutes but it only took 5 minutes or less to get on the ride, but those situations are few and far between.
JIMINYCR
Well-Known Member
I've never looked at the wait times listed as fact. I always assume they are guestimates and plan that it may be shorter or longer. Thats why I always bring something with me to pass the time. Usually I'm surprised by the wait time as being somewhat shorter than was displayed. Now with wait times being tweeted by guests there may be better accuracy for those getting in line. I've seen people "forget" to give the FLIK cards to the CM's and try to scoff one up for a souvineer, but I've reminded them that it has to be turned in.
Also sometimes the employees mess up the counts. I forget what ride it was now but one time at the MK the attendants were giving the flick cards to the people going into the fast pass line :brick: not the peeps going into the stand by line. Consequently the standby line time was ridiculously short and judging by the amount of people in it the actual wait was probably 2 to 3 times what was posted.
Mansion Butler
Active Member
That's why we send them every five minutes (might vary by attraction, though) and have trained CMs monitoring the line on camera.
Mansion Butler
Active Member
They weren't messing it up. FLIKs go in Fastpass, too.
They do more for informational purposes than just change the wait time.
Information is great but when it artificially lowers the standby wait time how does it help.