Security Technology Executive

JUL-AUG 2015

Issue link: https://securitytechnologyexecutive.epubxp.com/i/557126

Contents of this Issue

Navigation

Page 21 of 39

22 SECURITY TECHNOLOGY EXECUTIVE • July/August 2015 www.SecurityInfoWatch.com PROJECT MANAGEMENT networks can avoid costly mistakes. If your integrator has brought the concept of a wireless solution to you, do the same. Charge them with the responsibility to identify the pros and cons of wireless versus traditional wired solutions. Once they 've established a familiarity with the project, engage your IT stakeholders right away. Allow your IT staff to help you determine the required level of technical competency and support expected from the integrator. W hen interviewing an integrator, it is best to have IT take part in the conversation to verify that their degree of experience and knowledge satisfies the pre-determined set of requirements. If you have trouble identifying an integrator who can help you meet the requirements for your project ask the manufacturer. It is in the best interest of the manufacturer to have their most competent integra- tor/dealer perform the installation to ensure their product is being used properly, that the expectations for performance are reasonable, and to have a track record of success. The system design, installation and initial testing are where the skills of the integrator and the prod- uct readiness for the site-specific application become apparent. It is in this phase that the skills of your integrator and IT department must complement one another for a successful outcome. In addition to the functionality of the system, being prepared to use it as intended is crucial. Identify who is responsible for the ongoing main- tenance of the system. Is it your team of operators, your IT administrators, your integrator or even the manufacturer who is going to take the lead when updates are required or the system goes down? Establishing a life-cycle management program can greatly enhance the performance of the sys- tem while mitigating risk and reducing exposure for the organization. This is because a proper life- cycle management program is proactive, just as maintenance should be in a computing environ- ment. Waiting for a reason to place a service call means waiting for system failure. The traditional Time & Materials service model is risky with any system, but particularly wireless systems. Proac- tive testing, auditing and updating can alert you and your integrator of potential points of failure. Knowing the status of the system at all times can prevent outages and address issues before they become problematic. Like any technolog y, there is a formula for mean-time-to-failure (MTTF). Awareness of the component's MTTF can help you with long-term maintenance strategies and budgeting. Ask- ing the manufacturer about the product's MTTF upfront helps determine whether that product is the best choice or not from a cost-performance standpoint. T here are factors and variables based on the environment where the technology is being used that may affect its overall perfor- mance. In some cases it is necessary to engage the manufacturer, the integrator and all organiza- tional stakeholders in a site walk to identify any potential performance hindrances. The integrations that tie into the wireless tech- nologies also need to be treated with the same amount of attention as the wireless system itself. Research ahead of time what integrations are available with the solutions you are considering and plan for the next several years. If you have an enterprise access control system that is approach- ing end-of-life, perhaps you should investigate a wireless technology that integrates with the sys- tem in use today and with the system you plan on using in the future. Performing the proper due diligence prior to engaging in a wireless project is just as critical as any other security project, however, the added complexity of the technology and the required skillset to design, install, operate and maintain the system can be a blind spot for many organi- zations. There is an ongoing accountability with the manufacturer, the integrator, and the end-user to properly utilize these systems and leverage the technology for the reasons identified in the begin- ning, however, it is primarily the security director's credibility that is at stake. Research and education go a long way but ensuring that the right partners are involved early on is critical. ■ About the Author: Wayne Smith is Vice President of Sales & Professional Services for Tech Systems, Inc. In his role, Smith leads this team in providing network and converged security solutions to Fortune 500 companies. He provides clients and prospects with the essential information, technology, and training to manage the ever-increasing convergence of logical and physical security solutions. Smith currently holds the following certifications; Certified Information Systems Security Professional (CISSP) Certified Information Security Manager (CISM), ASIS International Certified Protection Professional (CPP). Mr. Smith has over 25 years' experience in the IT and physical security related fields. Smith was a Military Police Officer with the United States Army. Smith received his Bachelor's degree from Columbus State University and his MBA from Kennesaw State University. The integrations that tie into the wireless technologies also need to be treated with the same amount of attention as the wireless system itself.

Articles in this issue

Links on this page

Archives of this issue

view archives of Security Technology Executive - JUL-AUG 2015