It's true. The resources are different from country to country. We're implementing our own infrastructure, making sure everything is securely backed up. There are several different lines for power provisioning. We have UPSs (uninterruptible power supplies) on site, diesel generators on site. We cannot afford a power failure. How does the size of the Athens projects compare with Salt Lake City?
The summer games are two to three times bigger as far the number of sports, the number of athletes, the number of media people. As far as venues, we had about 40 in Salt Lake City, including 10 competition venues. We're looking at 70, including 35 competition venues, in Athens. We had 2,400 athletes in Salt Lake City, and we have 10,500 in Athens. There are 37 sports in the summer game, compared to 15 in Salt Lake City. As a good example, one of those summer sports, track and field, on its own is bigger than all the winter sports put together. So do the IT resources scale up in relation?
Oh, yes. We had half the number of desktops in Salt Lake City compared to what we're installing here. There were about 450 servers in Salt Lake City, compared to the 850 we have here. What are some of the lessons you're applying from the winter games?
When the IOC awarded the contract, one of the key things for them was reducing the cost of putting on the games, just so it's more affordable to Third World countries. Technology is one of the big costs of the games, so reducing the cost was a decision implemented through a knowledge management programme. From Salt Lake City on, we tracked everything -- how many people did we hire for each position, how many people did we have at any given time? All the information we tracked down, and after the games we did a series of after-action reviews where we reviewed all the data...to see what we could do to make things happen better and cheaper the next time. We looked at everything -- the starting plan, the number of volunteers, the amount of equipment, decisions about tools, decisions about what level of redundancy was appropriate in each area. Are those tough decisions to make, given the reliability demands?
Sure, because you always want to do more. But we found places we could cut back without compromising performance. The IT budget for Salt Lake City was around $300m. For the summer games, we don't have the budget finalized yet -- but the trend is to go for something very similar, like $350m even though the amount of work is two to three times bigger. And we're on track to do that. You deal with some pretty unusual IT situations. How do you find people who are expert at networking precision timing systems with back-end servers, for example?
We use several different levels of skills. We have a team that has Olympics games experience in several areas -- technical areas, logistics, etc. And we rely on our partners. For Unix, for example, Sun is supplying a lot of talent. How big a concern is security?
All the Olympics games are very highly visible events. Our goal is to implement quite strong preventive measures against any breach of security or denial-of-service attack. We're using both people awareness and a good suite of tools that helps us at every level -- from the very technical level to the managerial level, so everyone has a good sense what the issues are. This is deployed very early, because we're dealing with sensitive information from very early in the process, like private data on athletes or VIPs. You decided in Salt Lake City to pass on 802.11 wireless networking support because of security concerns. Any change in your position on Wi-Fi? We're doing the same thing in Athens. The IOC thinks -- and we agree -- that the security is not major enough to be used for such an event. I think the trend is in favour of wireless and we'll be able to do that at some future games, but not now. How did IBM's problems in Atlanta affect the way you're approaching the Olympics?
I won't comment on IBM's accomplishments previously. But the experiences the IOC had from that era were translated in their bid and the contract we have. The two key aspects we are obliged to meet is to get a good knowledge transfer to make the games cheaper and cheaper and to make it more reliable by using mature technology. We're not a hardware provider. We're agnostic; we implement whatever technology we need on any hardware. (Editors' note: Athens Olympics sponsors include Dell for PCs and Sun Microsystems for servers.) We're not using the games to showcase any fancy products. We're arranging it to show we can deliver the job on time and on target. We're using this quite challenging project to show we can do this one, and if we can do a project like this that is quite in front of the world, because no failure is acceptable, we can do quite a job for our usual customers. Are you using any open-source software to cut costs?
No. It's not a religion that we use this or that. Sun is a sponsor and is providing Solaris (Sun's version of Unix), so that's what we use. Maybe for the next games we use Linux.
