2. Planning
In Beowulf, bringing down the dragon required knowledge and great skill. Thanks to the planning phase, I figured I could conjure the internal resolve needed to gut the dragon of massive wait times and dangerous slowdowns in Disney Magic.
The strategy began with the cost principle, which states that the cost of slaying miles-long lines are to be matched with the revenues they help produce.
And so, with the help of paid testimonials, I decided to join forces between two pieces of software--Ridemax and TouringPlans' routing program--in the joint tour of duty that is called Operation Disney.
Ridemax is a software program that its author claims minimizes wait time for attractions at DLR. It was written by a WDW buff, but the software had been tested by Disney aficionados here on the west coast. It solves (perhaps) a very difficult problem in the world of computing: the traveling salesman problem. More, it (likely) solves it in an intelligent way, using data collected in-park from the author, his family, and other patrons. TouringPlans (Google it) seemed and felt similar.
DLR (DL and DCA) has several attractions. Some of them have very good ratings, like Paint The Night and RSR, and others not so much. Some offer FastPass, others single rider lines, and most neither of the latter two. Others are closed for good, and a few are in refurbishment. Attractions that feed humans are attractions. The bottom line: Ridemax claims to find the best way to see everything on your list in the shortest time possible, including walking time, provided you agree to their contract.
Okay! Day 1 is
Disneyland, and it was time to choose my must-sees. Matterhorn, you're in. Chip and Dale's Treehouse, sorry. And so forth until I had built my T-Rex. Note that some plans "could not be accomplished in the time allotted" because I had chosen too many things to do. After my plan was built, I figured that I would go into town during the most busy and hot times of day using the block of time that the software had allotted from about 1 PM to 6:30 PM. I scheduled a bowling trip at the local alley and possibly a trip to miniature golf. I also asked the software to figure my handicap.
Revenue expenditures would begin shortly. Since expenses are the cost of revenues, I asked the software, in effect, to calculate maximum ROI by running it across days within my meager vacation window. The weekend of the 4th was out of the question. (Added: But who knew that Disneyland would see RECORD LOW attendance for Independence Day the previous Monday!? Not me. And not the software....) Fridays and Saturdays were forbidden, too, and Sundays were not rated. Some days had EMH (which is partial 1-hour ERT for hotel guests and certain ticketholders). That left Wednesday of this week. Therefore, RevEx would take place for that day.
On-ride percentage for this plan (exclusive of shows, breaks, and parades) is about 35%. The circled numbers are references to a condensed map that I would bring along. Even though Disney had its own map, I found it too detailed for my own use and decided to play "connect the dots" with the condensed version instead, which, by the way, came from a different program. I decided to use Ridemax because some of the other program's data just didn't feel right: (1) 15 minutes for RSR in the stand-by line didn't seem right based on others' reports of waits double that and (2) there were bad variances between observed and expected crowds for several other attractions. However, I did find the map useful and decided to--yes, that's right!--
map Ridemax's tour to the other program's map.