Office for Interoperability and Compatibility Interoperability Initiatives Kathy

Office for Interoperability and Compatibility: Interoperability Initiatives Kathy Higgins Branch Chief Command, Control and Interoperability Science and Technology Directorate November 18, 2008

OIC Background The Office for Interoperability and Compatibility (OIC) is working with the emergency response community and Federal partners to improve local, tribal, state, and Federal emergency preparedness and response. OIC programs address both data and voice interoperability. OIC is creating the capacity for increased levels of interoperability by leading technology projects that improve emergency response communications today. OIC also is improving incident response and recovery by supporting the development of technologies and messaging standards that help emergency responders manage incidents and exchange information in real time. 2

Technology Continuum A national strategy for improving interoperability must take into account all of the factors critical for a successful interoperability solution. Without technology, there will be no interoperability solution 3

Outreach to Industry to Develop Prototypes Develop/Define Solutions OTHER RESPONDERS Research User Needs TECHNOLOGY TRANSITION Test Prototypes in User Environment TRANSPORTATION LAW ENFORCEMENT FIRE-RESCUE EMS REQUIREMENTS Evaluate Final Product ACCEPTANCE Building Tomorrow’s Interoperability Super Highway Today 4

Strategic Solutions Local Public Service Tribal Fire State Law Enforcement Federal EMS Levels of Government Interoperability: Connecting diverse stakeholders across multiple levels of government. Missions Interoperability directly impacts the emergency response community, which consists of more than 60, 000 emergency response agencies nationwide; state homeland security officials; and policy makers at the local, tribal, state, and Federal levels.

Current OIC Technology Initiatives • In conjunction with research, development, and evaluation interoperability initiatives, OIC is working with emergency responders, Federal agencies, and manufacturers to field technology projects on multiple important fronts. • While addressing interoperability challenges from different angles, technology demonstration projects share a common goal: to ensure that emergency responders nationwide can communicate with each other on demand. • In keeping with OIC’s practitioner-driven approach, emergency responders are involved on the front end of each technology initiative.

Multi-Band Radio Project • Until recently, emergency response radios were built to operate within a single radio band. As a result, emergency response agencies and support units had to rely on the use of several single-band portable or mobile radios to maintain a level of interoperability with partner agencies. • OIC awarded a contract to Thales Communications, Inc. to demonstrate a multi-band radio (MBR) that enables emergency responders to communicate with partner agencies—regardless of the radio band on which they operate. • Carrying a price tag of $4, 000 -$6, 000, the MBR is equal in form, factor, and cost to existing high-end portable radios. • A significant difference between the MBR and other systems is that the MBR equips emergency responders with the unprecedented capability of operating across the entire range of public safety radio bands. • To communicate with another agency, MBR users simply select the assigned channel. • OIC will soon test and evaluate the MBR through pilots nationwide. 7

ROW-B Project • An increasing number of agencies are using wireless radio systems— known as land mobile radios (LMRs)— and separate wireless broadband systems to communicate. • Because the LMR and broadband systems serve specific and different needs, they were not designed to communicate with each other. The lack of interoperability between these two systems may compromise emergency response operations when emergency responders using a broadband system are unable to communicate with emergency responders employing an LMR system. • Through the Radio Over Wireless Broadband (ROW-B) project, OIC is working with emergency responders, Clarity Communication Systems, and a locality to connect existing LMR systems with advanced wireless broadband technologies, such as laptops and smart phones.

Vo. IP Specifications • To connect radio systems, emergency responders rely on bridging devices. • Computer networks are increasingly being used to transmit voice communications among radio systems using a technology known as Voice over Internet Protocol (Vo. IP). • OIC is working with emergency responders and the National Institute of Standards and Technology (NIST) to define a common connection for bridging devices that use Vo. IP. • OIC’s goal is for the connection to allow one vendor’s bridge to pass a voice call to another vendor’s bridge. • The Bridging Systems Interface (BSI) is the first interface that OIC and its project partners have developed and tested. When implemented into bridging equipment, the BSI provides a common, efficient connection point between disparate Vo. IP-based radio systems.

Acceleration of Standards The acceleration of standards is a key component of both data and voice interoperability. • OIC supports the acceleration of Project 25 (P 25) standards that help produce equipment that is interoperable and compatible regardless of the manufacturer. P 25 is a suite of eight standards intended to help produce interoperable and compatible equipment. • At the request of Congress, OIC is working with NIST, the Department of Justice, and the P 25 Steering Committee to develop and implement a Compliance Assessment Program. It will validate that P 25 standardized systems are indeed P 25 -compliant and that equipment from different manufacturers can interoperate. This will help ensure Federal grant dollars are being used appropriately. • OIC also leads the Information Exchange Standards Initiative, a public-private partnership to create messaging standards to share information between disparate incident management systems and software applications. 10

Project 25 Compliance Assessment Program Overview • An independent Governing Board (GB) represents the collective interests of buyers, sets policy of the program and assists in the administration of the program. Summary Test Report • The compliance definitions, used by labs, are jointly developed by users and manufacturers. • The GB issues Compliance Assessment Bulletins (CABs) in support of the Compliance Acceptance Program (CAP). • Labs are assessed by independent parties prior to being recognized for participation by DHS. • Labs assess/validate equipment as being P 25 compliant. • Upon validation, manufacturers declare equipment P 25 compliant and submit a Summary Test Report reflecting test results. Provides ‘at-a-glance’ summary reviews of test results • User community has access to CAP database to identify equipment that is compliant. • Entire process is auditable to verify content. 11

Vocoder Testing • Some firefighters have reported that background noise common to emergency operations—such as sirens, helicopters, breathing apparatus, and alarms—causes unintelligible audio in portable two -way digital radios. • OIC has partnered with the International Association of Fire Chiefs (IAFC), NIST, fire service leaders, and manufacturers to identify the causes of and potential solutions for this critical communications problem. • The vocoder—a hardware/software component in every digital radio—was identified as the possible cause of voice audio distortion for some digital radio users. • OIC, IAFC, NIST, practitioners, and manufacturers are working to understand how background noise affects voice audio; they are also determining what technology improvements are needed to overcome background noise issues. To objectively identify the technology problem and potential solutions, NIST is working with fire service leaders to develop and implement practical test scenarios.

Data Messaging Standards • Data messaging standards enable emergency responders to share critical data—such as a map, a situational report, or an alert—seamlessly across disparate software applications, devices, and systems. • OIC is supporting the development and implementation of the following data messaging standards: • Common Alerting Protocol Standard • Distribution Element Standard • Hospital Availability Exchange Standards • Resource Messaging Standards • Situational Reporting Standard

14