And while Flyinnbus seems to think parkhopping has no value (which is contrary to all evidence and the fact that they charge to in fact do this)
No - that's not what I said at all. But I about spit out my drink when I read people are arguing people don't visit parks because they aren't on the monorail (instead of actually what is in the park) and that the lack of monorail is what keeps people from park hopping.
Wanting to ride EE or TSMM is going to dictate if they want to goto a park.. not 'eww.. a bus??'.
I can see it now.. the Booking Agent on the phone saying ' Sir, would you like to add park hopper privileges to your ticket? It allows you to experience multiple parks in the same day'
Customer: "Are those additional parks on the monorail? If not, I don't want it. I'll ride a bus to get to the park if its my first park of the day.. but no way do I want to switch parks via bus.."
:ROFLOL::ROFLOL::ROFLOL:
And I'm tired of you pretending I don't answer your questions (and aren't we really all on the same team here?!?)
Because you don't see the difference between
Identifying a problem and proposing solutions for them
vs what you are doing which is
'I wish there was this cool thing.. and here's how I'd justify it'
You're setting the solution before you even agree what the problem that needs solving is.
If the monorail took people 90mins to get from A to B - you can guarantee they'd complain about the monorail just as much as buses. And you would have sunk billions into a trophy project without solving the problems. Such a solution would never get out of a dreamers head because you set out to 'improve the transportation system' - yet you don't address any of the problems. The decision makers would throw you out.
If you want to 'build a cool new attraction at WDW' - fine.. continue down this path.
But if you want to 'fix transportation at WDW' - you need to start off by identifying what the problems for guests and operations is... prioritize them.. value them.. and then propose solutions on how to address them and weigh the proposed solutions.
You clearly think like the current suits, which is a lack of "hey wow, we are Disney and our guests shouldn't have to take busses between our theme parks."
No - I think like every customer out there. 'Here are my problems, how are you going to fix them?'. If you don't fix them, you suck. That's what the customer in transportation is about today.
You are measuring success by 'its a monorail?? Ok, win!'. As opposed to actually addressing the current limitations and complaints of the system.
You can't do the latter if you don't know what the problems and limitations are. And you don't want to accept what those current problems are because the monorail doesn't help them.
The real problems with the system today are
#1 - people don't like transfers
#2 - people don't like the wait for a transportation vehicle
#3 - people don't like the vehicle showing up and not having space for them causing them to wait longer
#4 - People are concerned about the total time needed to move between resorts and attractions, and attraction to attraction
#5 - complaints about passenger space and lack of per passenger seats
#6 - Americans have a stigma against buses as 'poor people' transport
#7 - Existing space available at park entrances for transportation stations
The
total solution needs to be able to
- route guests from any resort to any attraction or park on property
- route guests between attractions on property
- be able to get a guest from any resort to any park within X-min SLA
- be able to get a guest from any resort to any attraction within Y-min SLA
- be able to get a guest from attraction to attraction within Z-min latency
- be able to deliver passengers close enough to the attraction to not require additional transportation to the attraction itself
- be able to deliver passengers close enough to the resort or the internal resort transportation system to not require additional transfers to reach the resort itself
- be able to effectively operate with both minimal passenger load during off-peak periods as well as ramp up for peak passenger load during peek periods
- be able to be deployed without requiring relocating any existing attraction or resort
- be able to transport both passengers and ECV/wheelchairs effectively
- be able operate in all typical weather conditions, day or night
- <insert athestic desires>
- <insert energy efficency targets>
- <insert targeted overhead per passenger costs>
- <insert operational uptime targets>
- <insert assumptions on classes of service allowed if any>
etc
That is how you start off deciding 'what to build' when you are proposing to fix something.
Even when they build attractions - they start off with targets the attraction must satisfy because that's why the attraction is being built in the first place. And part of the decision of greenlighting it or not is 'will it actually fit the need'
You start by outlining the NEED to fill or PROBLEM to fix (both are really the same thing). Else, it's purely for fun/art/whatever.
And if that's the case, then stop trying to pretend it's a solution to transportation needs. If you want that kind of value associated with the project, you need to address the transportation system's needs.