Desktop Readiness and Configuration

The initial deployment must consider issues across the entire information chain, from the source systems to the users computer screen. Most desktop PCs can handle the rigors of querying, reporting, and analysis. They already support large spreadsheets and Access databases. In some ways, the DW/BI system should reduce the strain on the users PC by moving most of the data management back to the servers. Dont assume that everything will work fine at the user desktop. Test this assumption well before users attend training.

Before you inspect the situation, decide how much capability a users desktop machine will need to have. Create a minimum configuration based on the front end tools, the amount of data typically returned, and the complexity of the BI applications. This minimum configuration includes CPU speed, memory, disk space, and monitor size . It should also indicate the base computer type and operating system supported, and browser version requirements. Weve been in organizations that insist on supporting multiple operating systems on users desktops: Windows, Apple, Linux, and UNIX. Obviously, this diversity has a big impact on the architecture and tool selection steps, long before you get to deployment. Lets hope those who are implementing a Microsoft DW/BI system are less interested in supporting multiple types of operating systems, but there are still many flavors of Windows.

When you go out into the user community, consider the following issues.

• Connectivity: Connectivity is not usually an issue in todays highly networked organizations, but there could be a problem getting from one part of the organization to another. For example, a remote field office may not have the appropriate network configuration to get to the DW/BI server. Bandwidth to the desktop is usually not an issue either, but its worth verifying. You may have some sales reps who work from home and dont have broadband connections. If theyre working with large datasets, their user experience may be disappointing. If you know about the problem, you can at least set expectations, even if you cant fix it.

  Tip 

  Windows Remote Desktop can be a good, inexpensive solution for bandwidth problems. This feature of WindowsXP Professional and Windows servers works very well across even fairly slow connections. We use it all the time over a virtual private network to shared servers. Many of our clients have reported great success in increasing user satisfaction especially for salespeople and others who are often on the road.

• Installation: Some front-end tools are desktop-based and need to have software installed on the users machine. Most are now browser-based and dont need local software installed. Be careful, however, as many of the browser-based tools actually download a plug-in that runs on the local PC. This can lead to version problems with the client software. Test the installation process from a selection of user machines and document any problems. If the installation process is anything more than clicking a button on the BI portal, make sure you document it clearly and use it to create a set of installation instructions.