Wipro and other off shore consulting companies have a history of disappointments with US companies. They promise cost savings. Initially, there are savings. But, they have a payment escalation clause. After a few years, they're costing the company the same as the displaced US workers. The other common complaint is that these off-shoring companies staff with their brightest people for the first six months, so they can get their arms around what they're inheriting, and then these workers get replaced with less experienced people who flounder. When new projects are needed, the off shore IT company gets to charge whatever they think the customer will pay. If the customer brings in outside consultants, the off shore company's personnel suddenly cannot speak English and stonewall the outsiders. In the case where these off shore companies bring in some workers to augment US staff, the workers work together to 1) protect their jobs and 2) expand their company's consulting role by cutting the US workers out of projects. There are many pharmaceutical companies which have entire departments of non-US workers, because US workers were laid off or fired because they "couldn't effectively communicate" or "work effectively with" the non-US consultants who refused to work with US workers.
Disney's IT is a complete disgrace. Making reservations in an easy manner is a "core" requirement for a hospitality company.
I suspect Disney's dining reservation has a database or server capacity issue. It works flawlessly at odd hours, and breaks down horribly at peak hours. Consider what's required to actually make reservations. First, they have to determine if the restaurant is open for that meal. Then, they need to check "around" the time you put in for open slots. Because there are only N tables in the restaurant, and a total capacity (usually in theory) of X, and some restaurants can't accommodate large groups, they need to calculate how many tables remain, and how many diners can be accommodated at those tables. Once they've done that, they can present you options for what's available. Once you say "I want it" to that Noon reservation at BOG, they "hold" the reservation (removing it from inventory) for some number of minutes. During that time, you may decide you don't want it (and it will return to inventory when the "hold" time expires) or you do, in which case, if you don't exceed their "hold" period, you'll get the reservation. There's a lot of database work here. At high volumes, you may have many people who are shown that Noon reservation at BOG, and they all want it. If there is only one, they then have to figure out when else it is available and offer you that. If there are multiple slots open, they give you one. So, even more database work at high volume, all trying to reserve or hold the same resources. While it could be made to work better at peak times by "holding" reservations when the option is presented to the user, that would create the problem that all reservation times being shown would lock up, and further compound the problem by unnecessarily "holding" reservations that, in most cases, will not end up attached to the user's reservation.
