1. COPS 2007 Technology Program Kickoff Conference Interoperability Through Shared Systems Jesse W. Cooper, Communications/IT Project Manager Phoenix Police Department

2. Defining Interoperability Interoperability – what is it? Communications interoperability is the ability of public safety agencies to talk to one another via radio communication systems—to exchange voice and/or data with one another on demand, in real time, when needed, and as authorized. -National Task Force on Interoperability This is not the ability for all responders at an incident to be able to talk to everyone else.

3. The Importance of Interoperability Five years to the day before the 9/11 terrorist attack, the Public Safety Wireless Advisory Committee (PSWAC) reported that “unless immediate measures are taken to alleviate spectrum shortfall and promote interoperability, public safety will not be able to adequately discharge their obligation to protect life and property in a safe, efficient, and cost-effective manner.” - National Task Force on Interoperability “It is also clear, however, that the response operations lacked the kind of integratedcommunications and unified command contemplated in the directive. These problems existed both within and among individual response agencies.” (emphasis added) - 9/11 Commission Report, Page 319

4. Interoperability Continuum

5. Advantages of Shared Systems • Shared Resources/Personnel • Common/Standards Based Infrastructure • Shared Maintenance Costs • Shared Operating Costs • Expanded Capabilities (voice, data, secure communications, etc.) • Expanded Grant Funding Opportunities • Competitive Quantity Purchase Pricing Agreements

6. Critical Elements • First Responder Participation (law enforcement, fire/EMS, public works, utilities, etc.) • Local/State/Tribal/Federal Involvement (for border states – consider international issues) • Utilization of the Incident/Unified Command Structure (NIMS) • Successful Planning • Training and Exercises

7. Challenges • Governance • Funding Agreements • Grant Applications • Cooperation/Collaboration • Regionalized Interoperability • System Configuration and Complexity • Training and Exercises

8. Challenges (continued) • Technology Support • Vendor Contracts • Expanding Interoperability • Operational Changes • Control and Asset Ownership • Liability • Control Issues

9. Human and Technology Challenges

10. Technology • No one technology can solve every interoperability challenge • Several technology solutions must generally be employed to achieve interoperability • Technology is only one of the factors to consider for complete interoperability (Interoperability Continuum)

11. Planning for a Shared System

12. Building the Environment

13. Implementing Technology

14. Bringing it all Together

15. Phoenix/Mesa Regional Wireless Network Overview

16. System Background • Project 25, Phase I compliant, digital, trunked, ASTRO 25, simulcast • Regional network supporting multiple agencies • Phoenix Regional Wireless Network - PRWN • Trunked OPen AriZona Network – TOPAZ

17. PRWN/TOPAZ Basic System Configuration Waddell Dam Daisy Mtn.* New River Thompson Peak Simulcast A Police and Municipal Simulcast E West Valley Simulcast D Mesa Public Safety & Public Service Simulcast B Fire and Municipal Sky Harbor Simulcast C Phoenix (Ahwatukee – Tempe – Chandler) Goodyear (Estrella) Simulcast F Tempe * Daisy Mtn conventional not trunked operation

19. System Description

20. Current Participants ~2000 sq mi

21. System Description • Phoenix radios 10,526 • Mesa radios 3,507 • Total 14,033 • Average calls per day 74,000 • Average calls per month 2,200,000

22. Regional Interoperability

23. Regional Interoperability

24. Regional Interoperability

25. Metropolitan Phoenix Projects • 2005 DOJ 25 Safe-Cities – Cache Radios and Control Stations • 2005 COPS Grant – Integrate Tempe and Apache Junction • 2005 SHSGP – Additional Cache Radios and Gateways • 2005 UASI – Communications Response Vehicle • 2006 BJA Award – Addition Control Stations • 2007 COPS Grant – Expand Capacity on System for Interoperability Partners

26. Metropolitan Phoenix Projects • 2007 PSIC Grant – Add State Partners and Expand System • 2007 PSCC Demonstration Project – Connect Phoenix/Mesa System and Yuma Regional Communications System • 2007 UASI – Expand Statewide Rapid Response Team Capabilities • 2007 SHSGP – Expand Interoperable Communications Capabilities to all Phoenix Area EOCs • 2007 DHS Demonstration Project – Add VHF Trunked System to PRWN/TOPAZ

27. Metropolitan Phoenix Projects All Projects Geared Towards the Ultimate Goal of a Regionally Shared System!

28. Events Utilizing Shared Systems and Other Resources • 2006 Immigration March • 2006 TICP Validation • 2006 Baseline Killer/Serial Shooter Cases • 2007 Fiesta Bowl Series • 2007 BCS Game • 2007 TOPOFF 4 • 2008 Super Bowl XLII • 2008 SCIP Validation • Public Safety Funerals

29. Shared System Governance • Define Mission and Objectives • Define Roles and Responsibilities • Structure • Voting Rights • Organization • Fiscal Management • Operations and Maintenance • Asset Ownership

30. Shared System Governance • Performance Standards • Legal and Liability Issues • Dispute Resolution Process • Duration and Severability • Refresh Cycles • Short-term and Long-term Planning (Sustainment)

31. The Critical Factors of Shared Systems • Respect • Trust • Acceptance • Focus on regionalization • Focus on end user needs As the saying goes – it’s all about relationships!

32. Questions or Comments? Jesse W. Cooper Communications/IT Project Manager Phoenix Police Department Office/602.534.0315 Mobile/602.768.4314 Jesse.cooper@phoenix.gov *Special thanks to Charlottesville, Virginia, Fire Chief Charles Werner for use of graphics and ideas for this presentation.