Before getting too far with the wireless project, understand as much as possible about requirements, such as needs of users and applications, interfaces with existing systems, facility composition, and so on. This provides the basis for making decisions when designing the solution. If you don't do a good job of defining the requirements, then the solution may not meet the needs of users. For smaller networks, the requirements gathering process could be as simple as spending a couple days thinking about requirements and preparing a two to three page document that defines them. Larger systems, however, will likely need for a more involved process because of a broader base of users and systems. If requirements are not well understood, then consider using prototyping and construct a solution based on known requirements. The testing of a small prototype with a limited number of users will often lead to better understood requirements. Before allowing users on the wireless network, ensure there's definition and activation of adequate operational support. This includes elements such as trouble resolution, periodic maintenance, and system monitoring. What most people don't realize is that this phase of the system's life can be much more expensive than the cost of the installation. As a result, define enough details of the support elements to provide an ongoing budget. The installation phase of the wireless project is when the tires hit the pavement. If the design is done effectively, then the installation should be a smooth process. For example, the design should specify where to mount the base station. It's generally best to place the base station as high as possible, but be practical. Warehouses have high ceilings; however, avoid mounting the base station so high that you need expensive equipment to reach them.