Georgia Interoperability Network GIN Implementation Introductions SFC Jamie Sullivan Georgia Interoperability Network

Interoperable Communications – A Definition Interoperability is the ability of public safety service and support providers to communicate with each other via voice and/or data: On demand In real time When needed When authorized SAFECOM definition of Interoperable Communications

GIN Solution Interoperable Communications System that: Uses existing Radio Frequency infrastructure Achieves “on demand” interoperability through overlay additions to the current RF infrastructure: IP network backbone, IP network components and Mobile Communication Units Allows interoperability between disparate radio system technologies Provides flexibility and scalability Achieves functionality in most areas of state population with fixed communications assets; in remaining areas with mobile communication assets Will be implemented in multiple phases Will be completed by June 2010 Is being managed effectively by three working groups: HSTF Communications Subcommittee, Technical Working Group, Operations Working Group Feasibility Study – What can we do with this money to address interoperable communications? The requirement from GEMA was for the functionality to meet or exceed the 75% of the state population. Actually, it is over 80%.

Project Organization

Coverage Map How did the counties get selected? 1) Population – Took top 40 most populous counties 2) Critical infrastructure – nuclear power plants (Appling (Hatch, Appling GA), Burke (Vogtle, GA), & Early (Farley, Dothan AL) counties. 3) Transportation corridors – 75, 95, 16 big ones for hurricane evacuation

Motorola MOTOBridge Comprised of 4 basic components: Operational Management Control (OMC) Server Keeps track of network configuration and is used to manage entire system Two redundant systems (main and backup) Session Initiated Protocol (SIP) Server Sets up calls on the system Radio Gateway Unit (RGU) Connects the radio systems into the network Resides in every jurisdiction (usually in communications center) Work Station Gateway Unit (WSGU) Gives dispatcher access to the system The first two (OMC & SIP) don’t really affect the PSAP. They are located in Glynn County and at the State Patrol (Confederate Ave, ATL GA) The last two are the equipment located at a PSAP.

MOTOBridge Technology System A MCU System B 800 MHz VHF RGU RGU MPLS VHF UHF Top level function diagram. WSGU Dispatch WSGU 911 Dispatch OMC Server SIP Server

Point out that Motorola is monitoring the network for problems and failures. Two MCUs located at Cobb and Wayne counties

R-GU Interoperability Serial (RS232) (Enables Radio controls, Emergency Notification and Wireless Data) 4W+E&M/Tone Remote Control SmartZone 800 MHz System P-25 MPLS Network CEB BIM 4W Serial (RS232) Station Conventional/Trunked PSTN Consolette 1 to 8 interface Connections per RGU Cell LMR System Aviation 4W+Tone Remote Control

Workstation Installation

Workstation Installation

Rack Installation

MCU

INTEROP 1

Interop-1 on Post Americus 2007

Scout

MCU Resources MCU Resources MCU Operational Modes 1 VHF repeater 5 channel 800 MHz Trunking Capable Repeater System (MCU #1 only) 1 Aviation Radio 2 HAM Radios 2 800 MHz Control Stations 2 VHF Control Stations 2 UHF Control Stations 1 Low Band Control Station Cache of 25 800 MHz and 25 VHF portables MCU Operational Modes Interconnected to GIN MPLS via satellite Free standing

GIN Security Solution IP Network Uses private IP addressing Has no public internet access All gateway units protected with built-in firewalls All core equipment protected with external firewalls Dedicated equipment with applications used only for the Georgia Interoperability Network AES encryption of voice communications on the MPLS network and satellite link Signaling and control information between the SIP and OMC servers to Gateway Units use IP-Sec tunnels Georgia Interoperability Network satellite traffic is only routed to intended destination

Capacities Network PSAPs 1000 Dispatch positions, 5000 radio ports, and 64,000 talkpath connections PSAPs 15 talkpaths per Radio Gateway Unit (R-GU) port 60 talkpaths per R-GU 9 conference bridge participants per Workstation Gateway Unit (WS-GU) 24 talkpaths per WS-GU 60 seconds audio replay duration per WS-GU talkpath

What Project Will Not Do Increase Radio Frequency Coverage Increase Channel Capacity Allow Radio of One Type to Communicate with Transmitter of Different Type Eliminate Technology Obsolescence

Importance of Project Georgia’s First State-wide Interoperable Communications Project Funded Mostly by Federal Grants with Additional Local and State Investments Local Governments and State Agencies Involved in Design Will Serve as a Model for Larger State-wide Initiatives

Value Proposition for System Local Law Enforcement Interoperable communications for law enforcement and other first responders at local level Interoperability with neighboring agencies with overlapping radio frequency coverage Dispatch back-up capability with other agencies for continuity of operations Dispatch conferencing with other departments and agencies Interoperable communications statewide in major events State Agencies Centralized broadcast, remote monitoring statewide in major event situations Selective dispatch center conferencing statewide Dispatch consolidation All Participate in first statewide interoperable communications project Help create a model for future state wide interoperable communication projects involving multiple local and state government agencies Project mostly funded by federal money Might want to go to the core applications

Core Applications Overlapping RF Coverage System A System B Communications between responders in areas where different RF systems provide overlapping coverage. Typical scenario: An incident near a county border. Even if each jurisdiction has RF coverage in the area, it is difficult for responders from each to intercommunicate with each other. It requires using talkaround (if the radios are in the same frequency band), swapping radios, or using an on-scene ACU-1000. Each of these is limited; one large drawback for each of these is the ability to keep the command and control for each jurisdiction (e.g. dispatch centers) in the communications loop. A gateway solution would allow each jurisdiction’s responders to use their native RF systems and still intercommunicate with each other. It would also allow both command and control structures to be connected as well.

Core Applications Large Scale Events System A System B Communications between responders in different areas during large-scale events. Typical scenario: Mass evacuation across multiple counties (e.g. hurricane evacuation up I-16). There may be cases where a responder in one jurisdiction needs to communicate with another responder located in anther jurisdiction. This could occur for large-scale traffic control. This could also have been used to communicate with multiple agencies during the Brian Nichols manhunt. Using their native RF system, each user would be able to talk to someone else on their native RF system.

Core Applications Dispatch Consolidation/Backup System A System B Dispatch center backup/consolidation for continuity of operations. Typical scenario: Dispatch center is rendered inoperable due to natural disaster. There are times where a jurisdiction’s dispatch center may be rendered inoperable due to natural disaster or other unforeseen circumstances. A gateway system will allow another jurisdiction, be it neighboring or across the state, to assume those duties and be able to dispatch over the first counties own radio system. In other words, in provides geographic diversity in dispatch capabilities to ensure continuity of operations. Typical scenario: Dispatch consolidation. For example the Georgia State Patrol mans a number of dispatch centers throughout the state. Currently, each of these centers must be manned 24x7, even though the dispatch traffic at certain times (e.g. the middle of the night) is minimal. This leads to overstaffing and strain on the budget. A gateway system would allow the dispatch capability from multiple centers to be sent to one remote location at night, allowing one or two persons to perform these duties more efficiently.

Core Applications Centralized Broadcast GEMA System B System A System C System D Remote broadcast over multiple radio systems. Typical scenario: Sending emergency message to large group of individuals at once. There are some cases where a message needs to be sent to a number of individuals on multiple systems. For example, assume a 9/11-type situation where fire and police from multiple entities are responding to an incident in a building. If someone noticed the building about to collapse, they could send the message to everyone involved with a push of a button. This speeds up the delivery of critical messages, improving response efficiency and saving lives. GEMA

Core Applications Remote Monitoring/Control GEMA System B System A System C System D Remote monitoring of radio communications. Typical scenario: Situational awareness for centralized agency. In the case of a regional or statewide emergency, an entity such as GEMA may want to be aware of the situation as it progresses and be reconfiguring resources on the fly. Instead of having to personally contact the entities involved to get information, which distracts those entities from the job at hand, a gateway system will allow GEMA to passively monitor the radio and other communications from a remote site. This gives them real time situational awareness without the need to directly contact someone. GEMA

Core Applications Dispatch Conferencing Conferencing between multiple dispatch centers. Typical scenario: Command and control for multi-agency, multi-jurisdiction response. Intercommunication is not only needed by personnel on the street. It is also needed by the command and control structure to best plan a large-scale response and deploy resources most effectively. A gateway system would allow as few or as many dispatch centers as possible to communicate on demand to meet those needs.

Core Applications Mobile Platform System B System A System C Connecting a mobile communications unit to PSAPs or Dispatch Centers. Typical scenario: Major event in an isolated rural area (e.g. plane crash). Limited funding will probably mean that only part of the state will be equipped with a permanent gateway installation in the first round of the system. To cover the other areas, a mobile communications unit can be created (or an existing unit can be refitted) to provide some of the same capabilities as the fixed installations. These units can be strategically staged in the state to provide optimal response time.

Core Applications Traveling Across Jurisdiction System A System B System C Communications back to home base while traveling across jurisdictions. Typical scenario: Prisoner transport. There are many times where public safety personnel must venture outside the coverage of their native RF system. Even if that becomes necessary, if the responder is an area covered by an RF system that is compatible with their radio (i.e. both VHF or both 800 MHz), the local operator could give the guest user permission to get on their channel and talk back to the guest home command and control.

Agency Responsibilities OHS/GEMA - Implementation GSP - Business Owner & Network Administrator Local Governments - Operators Point out that we work for GEMA

Training and Exercises Vendor Training End Users (Train the Trainer) System Administrators System Engineers MCU Georgia Interoperability Network Exercises Local Regional State-wide

Channel Naming

Communications with Public Safety Community Newsletter Site Meetings Workshops Site Specific Reports Training CD Site Survey Tools Operations Manual Newsletter is working out to be 3-4 months in between updates

Questions? www.gainterop.com Thanks Jamie Sullivan (404) 624-7071