Interoperability Standards Summit on Implementing Wireless Communications May 2, 2005 Thomas Coty (SAFECOM, DHS) Dereck Orr (NIST) Objectives •Objectives for 2008: Public safety interests, rather than vendors, drive communications and interoperability solutions and standards. Implications and Assumptions (2008): A disciplined, structured process will be required to ensure that public safety’s interests drive the development of solutions and interface standards (specifications). • Objectives for 2023: There is an integrated system-of-systems, in regular use, that allows public safety personnel to communicate (voice, data and video) with whom they need on demand, in real time, as authorized. Implications and Assumptions (2023): An integrated “system-of-systems” in the year 2023 implies the widespread acceptance and use of interface standards by industry, and the widespread procurement and deployment of these systems by public safety. A Lifecycle Approach to Standards Development Image of lifecycle flow chart Standards Process Organization Image of standards process organizational chart Public Safety Statement of Requirements (SoR) The SoR is a practitioner created set of communications requirements - It is a living document •Version 1.0 -Released in March 2004 • Version 1.1 -Draft is complete; being vetted through Public Safety/NPSTC • Version 2.0 -Will begin to focus on quantitative requirements -Work is underway Conceptual Network Diagram Image of conceptual network diagram What is an Architecture Framework? The Framework is .. • A discipline for examining processes and system alternatives in context with operations and the information required • Common, pragmatic guidelines for describing architectures to enable comparisons and dovetailing • Tailor-able and modifiable to suit requirements The Framework is not.. • A single architecture • A tool prescription • A defined process The WHAT and HOW • The Architecture Framework will comprehensively describe WHAT the overall structured approach is to achieve a system-of-systems for nationwide interoperability • Interface Standards define HOW the elements of the Architecture Framework will work together. That is, HOW interoperability through a system-of-systems approach will be achieved. The Confidence Connection • Public safety must have confidence that the P25 equipment being purchased does what the standard requires! • The government programs requiring P25 acquisition through federal grants must have confidence that the equipment required operates to the standard! There is currently no mechanism to ensure compliance The Problem • NIST/OLES tests performed on P25 subscriber units found the following: – Conventional Voice Interoperability Testing • Identified numerous deficiencies with radios lacking required features or incorrectly implementing them –One radio while in talkaround mode transmits on the wrong frequency when an emergency call is placed The Problem (cont. -Performance Testing • Identified radios in the federal inventory certified by the vendor as TIA-102 compliant which are not compliant • Discovered widespread differences in quality of receivers—especially in the wideband analog mode – Two models of radio operating in widebandanalog mode subject to the same levels ofadjacent-channel interference » Radio #1 Radio #2 Supplier’s declaration 1st party conformity assessment certification 3rd party conformity assessment Perceived Risk Independence and Rigor of Conformity Assessment P25 Conformity Assessment Program • Components: – Grant guidance requiring P25 products purchased with federal funds meet the requirements of the conformity assessment program –3rd party type testing to evaluate compliance to requirements of the P25 Standard by accredited independent laboratories – Formal suppliers declaration of conformity to P25 requirements with results made available to public safety Questions? www.safecomprogram.gov info@safecomprogram.gov 1-866-969-7233 (SAFE)