Wireless Video Surveillance The Phoenix Model

1
Wireless Video SurveillanceThe Phoenix Model

• Det. Chris Jensen
• Phoenix Police Department
• Drug Enforcement Bureau

2
History of Video Surveillance in Phoenix

• Old System
• Analog
• Microwave
• Terrible image quality
• No range
• Seldom used by investigators
• Never used for patrol operations

3
Genesis for Change

• Spoke of IP based video as far back as 2004.
• Resistance from technical staff
• Early 2006 used citizens webcam to investigate
  a narcotic complaint.
• Began discussions about moving to Mesh based IP
  video surveillance.
• No experience or knowledge within city.

4
Summer 2006

• Baseline Rapist Random Shooters
• Mandate from city hall to establish video
  surveillance to support investigations.
• Chose technologies, supplier and integrator for
  project.
• Established a 30 IP camera network on 5 Firetide
  mesh networks within a 5 sq miles area of Phoenix
  In 2 WEEKS.

5
Results

• Surveillance video freed up to 30 surveillance
  officers.
• Resources able to follow-up other leads.
• All suspects arrested summer of 2006.
• Start of Phoenixs IP Wireless video surveillance
  system Desert Guardian

6
Phoenix Model

• Event (investigation) based, temporary
  deployments.
• Normally covert
• Deployments geared to achieve specific goals.
• Once event goals are met, resources are
  redeployed to meet the needs of other events.
• To date no permanent installations.

7
Desert Guardian Design Considerations

• Flexibility is a main design feature.
• NVR
• Mesh Infrastructure
• IP cameras
• Backhaul design
• City fiber
• DSL/Cable
• EVDO

8
Monitor Room
9
Super Bowl

• Phoenix Area of Operations
• NFL Headquarters
• International Media Center
• Numerous NFL events
• 42 cameras / 5 mesh networks
• 2 Operation centers established
• New technologies used
• Rapid deployable cameras
• VoIP communications between operation centers

10
Super Bowl
11
Super Bowl
12
Planning a Successful Deployment

• Define goals and expected outcomes.
• Complete a technical and operational site survey.
• Identify backhaul infrastructure (end to end).
• Identify and communicate tasks for all parties
• Integrators
• IT department
• PD
• Establish operational policies to establish
  boundaries for your employees.
• TRAIN

13
Lessons Learned For Success

• Relationships are essential.
• No one department owns infrastructure.
• Before deploying system, have clear defined
  goals.
• Training is essential.
• Allow time for staff to accept new technologies.
• Three keys to success
• Proven technologies
• Proven Integrators/Suppliers
• Proper infrastructure