Ensuring Complex Security Project Success
Friday, February 26th, 2010By Larry Mays
The New York City Metropolitan Transit Authority (MTA) may no longer have the funding necessary to complete its original plans to install a state-of-the-art security system throughout its bus and subway systems.
According to a report from the state comptroller, the project — begun after 9/11 — has made improvements through the installation of thousands of surveillance cameras and motion detectors, but the anticipated final cost of the project is now nearly more than $200 million over original estimates. Part of the problem lies with disputes between the MTA and the prime contractor resulting in lawsuits being filed by both parties.
It’s not my job to sort through the complaints and affix blame, but I would hope this project would serve as a wakeup call for other jurisdictions looking to upgrade security for their transit systems. As with any project — large or small — there is a right way and a wrong way to achieve wanted results.
Too many jobs fail because of one or more of these common mistakes. Be careful to not let these foil your efforts to secure your transit system’s passengers and employees:
- The requirements of the project are poorly defined. No project should begin until both the end user (transit authority) and the contractor fully understand what will be expected of each of them.
- During the design phase, there is inadequate input from the end users (usually police agency). A contractor can’t be expected to design and install the perfect security system without significant input from the officials and employees who will be using it on a daily basis.
- Senior management has not taken ownership of the project. This applies to both the end user and the contractor. Someone from both parties has to take responsibility for the success of the project and provide the leadership to help make it work.
- Unrealistic implementation timeline. This is another area where good communication between the end users and the contractor can make a huge difference. As a transit operator, be realistic about how much time it takes to install security equipment that will meet your needs for the long haul. And as a contractor, don’t promise what you know you can’t deliver.
- Unproven technology has been selected. It’s nice to always stay on the cutting edge, but sometimes it is best to invest in equipment that has been shown to work in a transit environment similar to yours.
- There is no clear training and transition plan. No project should be considered complete until the employees charged with implementing the system are fully trained and competent in its use.
Transit system security is more important than ever and with tight budgets it is vital that you and your system integrator/contractor get it right the first time.
So here is a look at some of the steps that I believe will lead to a successful project:
- Select the integrator first. Don’t try to move forward without the expertise of a security systems integrator experienced in securing transit systems. That expertise can save you time and money throughout the project process.
- Make sure there is a discernable public safety issue for the project. Don’t install cameras and other equipment without a clearly defined reason.
- Develop solid requirements in collaboration with the project integrator. Get everyone on the same page to eliminate as many possible misunderstandings from the start.
- Make sure that everyone is clear on the procedures and practices before, during and after a project. It is wise to know well in advance if the job will require the temporary closure of a route or station.
- Define what will constitute a successful project. That will give both you and the integrators a clear idea of the ultimate goal.
- Clearly define scope. Scope creep is a big challenge. As the project progresses people’s ideas change and even grow into grander ideas. Have clear boundaries — what’s in and what’s out. While big ideas are great for the boardroom there is no place for them during a project.
- Have a realistic phased implementation plan. That will give you set milestones to check and see if the integrator is living up to its end of the bargain. But do allow for problems beyond anyone’s control, such as bad weather and other natural disasters.
- Insist that your integrators lab test the equipment to simulate the environment of a subway tunnel, bridge or parking lot. It may cost a little more upfront, but it can save a lot of money down the line by limiting likely problems during and after installation.
- Create a win/win situation where both you and your integrator share the risks. That encourages teamwork and helps get everyone more involved in making the project a success. No one likes to fail.
- Finally, ensure that the appropriate security and operations staff are properly trained on security procedures and systems management for any new or upgraded solutions.
By following these tips, I can’t guarantee your entire security project will go smoothly without problems. But don’t leave success to chance. Careful planning in conjunction with your integrator will greatly increase the likelihood of achieving your goals.
Larry Mays is group director for transportation and logistics for ADT Security Services. He brings 31 years of transportation information management experience, helping to develop strategic network-based solutions for companies such as Unisys and Pan American World Airways. Mays can be contacted at lmays@adt.com.
