Solution Decision

• Technical Evaluation Document

1. Set up a working version of the system.
2. Work through the technical areas with the Vendor.

• Completed Technical Evaluation Document

The Vendor works with the client technical team to carry out the installation, and go through a list of technical tests. These tests are to prove that the solution can be set up within the client environment to provide a stable platform for the business both now and into the future.

Some issues that might be covered are:

• Ease of installation
• Bandwidth demands
• Integration with other systems
• Accessibility
• Compatibility
• Scalability
• Flexibility
• System tools
• Development tools
• Configuration tools
• Security
• Database operation
• Load testing
• Capacity constraints

The business and technical evaluations should ideally occur in parallel to ensure the process is completed as quickly as possible. This may require the Vendor to provide two teams to work with two customer teams (Business and Technical). If they cannot do the work in parallel, it is usually best to do the business evaluation first. Examining the functionality of the system is more likely to raise technical issues than vice versa. The initial setup of the system may form part of the technical evaluation.

Given the demands on the Vendor, it is sometimes necessary to pay the Vendor for the technical team provided. Make sure you are clear on the Vendor's attitude to this before you start. If payment is to occur, an hourly rate may be negotiated.

The whole exercise may take from a day to a week depending on the scope of the solution. It may also involve a number of people so scheduling in advance is important. Make sure that if you require your DBA or Infrastructure Manager on a particular day, they are available.

If particular issues cannot be resolved, ask for a follow up after the evaluation period. The key is to move as quickly as possible through this exercise while so many people are involved. Difficult problems are best taken off line. Don't stick only to the script during the evaluation. If a path opens that might lead to an area that could be a concern, explore that area. If there is not enough time, address it after the allocated period or take it off line.