End users are advised not to bring preconceived biases into the implementation of card access as well. Again, the integrator probably knows the pros and cons of various card and reader technologies, and his application to a specific system. For example, an integrator may have a job in which the end user has an existing bar code reader in place for time and attendance, so it seems logical to the user that he should buy a new access control system that uses bar code technology. But even though the end user may imagine implementing a similar system to cut costs, the integrator may know that bar code technology is not very secure when compared to proximity card readers. In just such a real life situation, the integrator countered by asking his customer, “What is the true cost savings if a bad guy can reproduce a bar code card on a copy machine?”
The anecdote exemplifies a common theme in disagreements between end users and integrators: cost vs. effectiveness. In such cases, it’s important to remember that the integrator also wants to keep costs down and only will recommend technology that appears to be necessary to accomplish security and safety goals.
Lack of written and accurate data. Improper documentation often drives installing companies crazy, and usually costs the customer money. The end user should be responsible for describing in writing exactly what he expects of the integrator, and which parties will do what during the project. Specifically, documentation should be clear as to what, if any, city permits are required and who provides them, as well as pointing out exactly what is excluded from the project’s scope.