Interoperability through Shared Systems

1
InteroperabilitythroughShared Systems

• Joe Noce
• 800 MHz Project Manager
• City of Mesa (AZ)
• Don Pfohl
• Manager
• OSP Wireless Communications

2
Mesa-Phoenix Sponsorship Plan

• Get the Right People Involved
• Visionaries create the concept
• Visionaries educate operations managers about the
  concept
• Visionaries and operations managers educate
  agencies management
• Educate city management
• All go to the politicians

3
Mesa-Phoenix Needs Analysis

• Bring Police and Fire on board
• They have the requirements listen to their
  requirements
• Wide area coverage
• Roaming
• Interoperability
• Building penetration/levels of signals
• Encryption

4
The Mesa-Phoenix Vision

• Police Interoperability
• Due to coverage needs
• Wide-area radio coverage needed for internal
  communications
• Interagency and discipline communications also
  needed
• Full-function cities have to involve all
  departments in a consolidated system
• Three dispatch centers three cities

5
The Mesa-Phoenix Vision

• Fire Interoperability
• Due to automatic aid needs
• Two dispatch centers 25 agencies
• Automatic dispatch of all forces requires
  complete use of the system
• Agencies response areas expand
• Sharing of support functions

6
The Mesa-Phoenix Vision

• Multi-Discipline Interoperability
• Full-function cities have to involve all
  departments in a consolidated system
• Natural Disasters include other public service
  entities
• Homeland Security plans involve other city
  services

7
Mesa-Phoenix Sponsorship

• Police, fire and technical people educate the
  city managers
• Agency sponsors determine if the project is
  doable
• Agency sponsors suggest methods of finance
• Agency sponsors take the heat for some decisions
  that are made

8
Mesa-Phoenix Needs Analysis

• Business processes and user needs affect
  requirements
• Clearly define expectations through education
• Mobile v. portable coverage
• Building penetration and signal levels
• Talk group management v. a channel for each pair
  of users
• Interconnect and private call
• Encryption

9
Mesa-Phoenix Needs Analysis

• Business processes and user needs affect
  requirements
• Shared Costs
• Who pays what?
• Shared infrastructure costs?
• What about later buy in?
• Continuing operational costs?
• How do we expand?
• Do we add newcomers?

10
Shared Systems with Other Techniques and
Technologies

• Shared Radios
• Time consuming
• Shared Channels
• Talk around
• Programming issues
• Mutual Aid Channels
• Easily deployed

11
Shared Systems with Other Techniques and
Technologies

• Interconnects
• Console patches
• Gateways
• Proprietary systems roaming
• Other standards-based shared systems

12
Shared SystemValue Elements

• Shared expertise in purchasing, legal support,
  engineering and operations
• Leverage everyones use of each others systems
• Price advantages due to scale

13
Shared SystemValue Elements

• Share spare assemblies and parts
• Shared system management
• Increasing knowledge pool as the system is
  implemented

14
Shared Systems Risk Factors

• Personal and professional risks
• People who stand up are targets
• Naysayers far outnumber those with vision
• These things take a lot more time than you ever
  expected
• Vendors are bound to be unhappy

15
System Design
16
InteroperabilitythroughShared Systems
Questions?