National Public Safety Telecommunications Council (NPSTC) Meeting

Transcription

1 National Public Safety Telecommunications Council (NPSTC) Meeting Alexandria, Virginia Alexandria Police Department Meeting Room L75 June 5, 2012 Call In: (877) Conference ID: # The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's! Science and Technology Directorate, Office for Interoperability and Compatibility (OIC) and the! National Protection and Programs Directorate, Office of Emergency Communications (OEC)! Points of view or opinions expressed are those of the originators and do not necessarily represent the official position! or policies of the U.S. Department of Homeland Security.!.!

2 NPSTC Meeting Call to Order Ralph Haller, NPSTC Chair Welcome Official Business Pledge of Allegiance Roll Call Agenda Approval communications and interoperability through collaborative leadership.! 2

3 NPSTC Meeting Department of Homeland Security (DHS) Dr. David Boyd, Director, Office for Interoperability and Compatibility (OIC) Chris Essid, Director, Office of Emergency Communications (OEC) communications and interoperability through collaborative leadership.! 3

4 Public Safety Broadband Directory Tom Sorley, Technology Committee Chair The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's! Science and Technology Directorate, Office for Interoperability and Compatibility (OIC) and the! National Protection and Programs Directorate, Office of Emergency Communications (OEC)! Points of view or opinions expressed are those of the originators and do not necessarily represent the official position! or policies of the U.S. Department of Homeland Security.!.!

5 Public Safety Broadband Directory The Public Safety Broadband Directory (PSBB) has links to a wide range of current information on the nationwide efforts to bring broadband to public safety. The directory categorizes all resource links, both by activities and organizations. communications and interoperability through collaborative leadership.! 5

6 Introduction communications and interoperability through collaborative leadership.! 6

7 Public Safety Broadband Directory Activities Advocacy Governance Policy Requirements Standards Testbeds Training New Information Organizations Federal, state, local, and regional governments National public safety organizations Standards-setting organizations communications and interoperability through collaborative leadership.! 7

8 Activities communications and interoperability through collaborative leadership.! 8

9 Organizations communications and interoperability through collaborative leadership.! 9

10 What s next? We are seeking your input to make this directory as useful as possible. Please send any recommended submissions, changes, and/or additions to directory_input@npstc.org. communications and interoperability through collaborative leadership.! 10

11 NPSTC Meeting Break communications and interoperability through collaborative leadership.! 11

12 NPSTC Meeting Federal Communications Commission (FCC) Roberto Mussenden, Advisor, Policy and Licensing Division, Public Safety Homeland Security Bureau (PSHSB) Canadian Interoperability Technology Interest Group (CITIG) Lance Valcour, Executive Director, CITIG National Public Safety Broadband Network (NPSBN) Update Chief Harlin McEwen, Chairman, Communications & Technology Committee International Association of Chiefs of Police communications and interoperability through collaborative leadership.! 12

13 Chief Harlin R. McEwen Chairman Communications & Technology Committee International Association of Chiefs of Police Chief of Police (Ret) City of Ithaca, NY FBI Deputy Assistant Director (Ret) Washington, DC ! National Public Safety Telecommunications Council Alexandria, Virginia June 5, 2012

14 Nationwide Public Safety Broadband Network The Brief History 1995 FCC & NTIA established the Public Safety Wireless Advisory Committee (PSWAC) 1996 PSWAC final report. Recommended 97.5 MHz of new spectrum Congress directed the FCC to allocate 24 MHz of spectrum to public safety in the 700 MHz band (TV Channels 63, 64, 68, 69) 1999 FCC established the Public Safety Coordination Committee (NCC) to recommend how the 24 MHz of Public Safety Spectrum should be used 2003 NCC final report. Recommended 12 MHz voice & 12 MHz for data 2007 FCC changed channel assignments within the 24 MHz & set forth rules for a new nationwide public safety broadband license resulting in formation of the Public Safety Spectrum Trust (PSST) who was issued the nationwide license 2012 Congress passed groundbreaking legislation for a new Nationwide Public Safety Broadband Network (PSBN)

15 Previous Band Plan Upper 700 MHz Base Transmit Mobile Transmit A 1 C 5 D 10 B 2 PS NB 3 G B 1 PS WB 4 G B 1 PS NB 3 A 1 C 5 D 10 B 2 PS NB 3 G B 1 PS WB 4 G B 1 PS NB New Band Plan Adopted by FCC on July 31, C 11 A 1 D 5 PS BB 5 G B 1 PS NB 3 PS NB 3 B C 11 Single Nationwide Public Safety Broadband License (Licensed to the Public Safety Spectrum Trust) To Be Licensed to FirstNet Public Law /22/2012 A 1 D 5 PS BB 5 G B 1 PS NB 3 PS NB 3 B 1 D-Block Spectrum Allocated to Public Safety To Be Licensed to FirstNet Public Law /22/2012

16 Nationwide Public Safety Broadband Network LEGISLATIVE SUCCESS Public Law Middle Class Tax Relief & Job Creation Act of 2012 Title VI - Public Safety Communications & Electromagnetic Spectrum Auctions Approved by Congress February 17, 2012 Signed by President Obama - February 22, 2012

17 Nationwide Public Safety Broadband Network Vice President Joseph Biden & Public Safety Leaders White House, February 21, 2012 Commemorating Legislation Creating Nationwide Public Safety Broadband Network Left to Right: Chief Charles Werner, Richard Mirgon, Deputy Chief Charles Dowd, Chief Jeff Johnson, Chief Chris Moore, Commissioner Ray Kelly, Chief Al Gillespie, Vice President Biden, Chief Walt McNeil, Chief Harlin McEwen, Mick McHale, Tommy Nee

18 Nationwide Public Safety Broadband Network LEGISLATIVE SUCCESS Public Law Middle Class Tax Relief & Job Creation Act of 2012 Title VI - Public Safety Communications & Electromagnetic Spectrum Auctions Signed by President Obama on February 22, 2012 MOSTLY POSITIVE 1. Allocates D Block to Public Safety 2. Provides $7 billion federal funding for the network 3. Establishes new nationwide governance (FirstNet) ONE NEGATIVE 1. Takes back T-Band spectrum allocation from public safety in 9 years Negatively affects a number of major cities and urban areas

19 FCC Waiver Entities States 8 Regions 5 Cities

20 S 1 Hawaii (HI) S 2 Iowa (IA) S 3 Mississippi (MS)... $70.0 million BTOP Grant S 4 New Jersey (NJ)... $39.6 million BTOP Grant S 5 New Mexico (NM)... $38.7 million BTOP Grant S 6 New York State (NY) S 7 Oregon (OR) S-8 Texas (TX) R 1 Adams County Denver Airport (CO)... $12.1 million BTOP Grant R 2 Bay Area (CA)... $50.0 million BTOP Grant (Motorola) R 3 Los Angeles (CA)... $154.6 million BTOP Grant R 4 Mesa TOPAZ (AZ) (Lease Terminated Effective 06/23/12) R 5 Wisconsin Counties (WI) C 1 Boston (MA) C 2 Charlotte (NC)... $16.7 million BTOP Grant C 3 Chesapeake (VA) C 4 District of Columbia (DC) C 5 New York City (NY) C 6 Pembroke Pines (FL) C 7 San Antonio (TX) C 8 Seattle (WA) BTOP Grants Suspended By NTIA Pending Further Review S States 8 R Regions 5 C Cities

21 Nationwide Public Safety Broadband Network Title VI - Public Safety Communications & Electromagnetic Spectrum Auctions T-Band Spectrum Reallocation Not later than 9 years after date of enactment (February 22, 2012) the FCC shall reallocate the spectrum and begin a system of competitive bidding to grant new licenses for the spectrum. The spectrum auction proceeds shall be available to the Assistant Secretary of Commerce to make grants to cover relocation costs for the relocation of public safety entities from the T-Band. Relocation of public safety shall be completed not later than 2 years after the date on which the system of competitive bidding is completed. Study on Emergency Communications By Amateur Radio and Impediments to Amateur Radio Communications FCC must complete (in consultation with OEC) not later than 180 days after the enactment (August 20, 2012)

22 Nationwide Public Safety Broadband Network The Future Benefits In addition to reliability, security, coverage, and public safety priority access, the future is exciting and almost unlimited. Specialized Public Safety Applications (Apps) similar to those currently available on smart phones & devices such as iphones, ipads, and Android Devices. Next Generation information (text messages, photos & video) sent in by citizens using smart phone devices will be able to be forwarded to public safety field personnel. Law Enforcement Apps that will access FBI CJIS Services like NCIC, Criminal History Information, and Nlets Services like access to DMV records, Driver s License & Corrections Photos and easy access to records management systems (RMS). Fire Service Apps that will access records of building plans, hydrant locations, hazardous material records, etc. Emergency Medical Apps such as transmission of vital signs to hospitals, access to medical histories, etc.

23 Technology Committee Tom Sorley, Committee Chair Andy Thiessen, Committee Vice Chair The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's! Science and Technology Directorate, Office for Interoperability and Compatibility (OIC) and the! National Protection and Programs Directorate, Office of Emergency Communications (OEC)! Points of view or opinions expressed are those of the originators and do not necessarily represent the official position! or policies of the U.S. Department of Homeland Security.!.!

24 The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's! Science and Technology Directorate, Office for Interoperability and Compatibility (OIC) and the! National Protection and Programs Directorate, Office of Emergency Communications (OEC)! Points of view or opinions expressed are those of the originators and do not necessarily represent the official position! or policies of the U.S. Department of Homeland Security.!.!

25 Working Group Activity BBWG Activity since last NPSTC meeting Published Local Control document Published Priority/QOS document Published Multi-Media Emergency Services (MMES) document Initiated review and development of the Statement of Requirements (SoR) document for 700 MHz broadband services. communications and interoperability through collaborative leadership.! 25

26 SoR Activity Organized SoR work teams First stage 3 teams Executive Summary writing team Reference Models writing team Administrative Requirements writing team Second stage 8 teams Each of the 8 teams is covering a different section of the technical requirements portion communications and interoperability through collaborative leadership.! 26

27 Timeline!"#"$%$&"'()'*$+,-.$%$&"'/(.0'1$#%2'!"#$%&'#()%**+,-(./*01023,+&'#(4#5%0,#*#132( 6#$710$+8(4#5%0,#*#132( 6)94(!/03:,0+8(;:+,/( <2#,()#,'0$#2( =#3>:,?()#,'0$#2( 9A(=#3>:,?( )-23#*(B#20C1( E0C,+&:1( communications and interoperability through collaborative leadership.! 27

28 Facilitators TSOR Editorial Board (Hengeveld, Buchanan, etc.) User Services (Trent Miller,Motorola) Network Services (Mark Adams, Northrup Grummon) Transport (Dave Helm, Motorola) Off-Network (Off-network Comms,Stephen Devine, MO) System Design (Tewfik Doumi, ALU) User Equipment (Roy McClellan, Cassidian) Local Operations (T. Hengeveld, Harris) Migration (Dominick Arcuri, RCC) communications and interoperability through collaborative leadership.! 28

29 First Meeting Boulder, Colorado May 23-24, persons in attendance + ~20 on conference line. Good representation from public safety, commercial, vendor, and consulting communities. Local, State and Federal agencies were represented Reviewed High and Medium priority feedback comments with entire group Each writing team had a half day to kick off their groups. communications and interoperability through collaborative leadership.! 29

30 First Meeting Feedback Group worked very well through complex and contentious issues. Excellent discussions from blending first responders with technical personnel Everyone seemed to have a much better grasp of the big picture by the end of Day #2 Most issues have been clearly assigned to a specific writing group. An Editorial Review Board, composed primarily of public safety, will quickly resolve any issues over where to place an item or issue. communications and interoperability through collaborative leadership.! 30

31 Revamping the SoR Timeline Actions Completed March April» TOC draft created» Glossary created» Document template created» Writing teams created 1 st drafts» Executive Summary» Reference Models» Administrative Requirements communications and interoperability through collaborative leadership.! 31

32 Revamping the SoR Cont d Timeline Actions Pending Late May/Early June» 2 nd draft written, vet Face to Face» Technical requirements section kicks off Mid July» 3 rd drafts submitted Early August» 3 rd face to face to finalize documeny=t Mid August» SOR submitted to NPSTC GB for review/approval» Editorial review led by Stu Overby & Dave Buchanan Early September» NPSTC submits SOR to FirstNet for consideration communications and interoperability through collaborative leadership.! 32

33 Development Schedule communications and interoperability through collaborative leadership.! 33

34 Video Technology Advisory Group John Contestabile, Chair The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's! Science and Technology Directorate, Office for Interoperability and Compatibility (OIC) and the! National Protection and Programs Directorate, Office of Emergency Communications (OEC)! Points of view or opinions expressed are those of the originators and do not necessarily represent the official position! or policies of the U.S. Department of Homeland Security.!.!

35 Video Quality in Public Safety Initiative Meeting the Need The Office for Interoperability and Compatibility (OIC) within the U.S. Department of Homeland Security (DHS) partnered with the U.S. Department of Commerce s Public Safety Communications Research (PSCR) program to develop a partnership of local, state, and Federal representatives to address video quality. This partnership, along with a combination of participants from the public and private sectors as well as academia, are working to enhance and standardize video quality through the formation of the Video Quality in Public Safety working group (VQiPS). communications and interoperability through collaborative leadership.! 35

36 Video Quality in Public Safety Initiative Background/Milestones First VQiPS Conference in February, 2009 Second VQiPS Workshop in September, 2009 Third VQiPS Workshop in February, 2010 Hardcopy of the report Defining Video Quality Requirements: A Guide for Public Safety released in July, 2010 Hardcopy guide is published online, see: videoquality/videoquality.htm The Consumer Digital Video Library, see: Fourth VQiPS Workshop in February, 2011 Reviewed current effort to develop an interactive web based version of the guide. communications and interoperability through collaborative leadership.! 36

37 Video Quality in Public Safety Initiative Background/Milestones Standards team working with the American National Standards Institute (ANSI) and an existing industry group Building Industry Consulting Service International (BICSI) with a goal of producing a handbook by this fall. Online VQiPS Video Requirements Web Tool is now available: define_vid_qual_reqs.php See screen shot, next slide communications and interoperability through collaborative leadership.! 37

38 Video Quality in Public Safety Initiative Background/Milestones communications and interoperability through collaborative leadership.! 38

39 Video Quality in Public Safety Initiative Background/Milestones VQiPS Leadership Team 1. Cuong Luu, DHS S&T (Program Manager) 2. John Contestabile, Johns Hopkins/APL (Chairperson) 3. Kevin McGinnis, Nat l Assoc. of State EMS Officials (End User Team lead) 4. Don Zoufal, SDI Systems Development Integration (Outreach and Marketing Team Lead) 5. Steve Surfaro, Axis Communications (Standards Team Lead) 6. Joel Dumke, PSCR (Performance Requirements Team Lead) 7. Andrew Hartigan, Touchstone (Program Management Support) communications and interoperability through collaborative leadership.! 39

40 NPSTC Partner Video Technology Advisory Group (VTAG) In order to promote awareness of the video research effort and increase outreach to end users, VQiPS sought to partner with NPSTC. While PSCR provides the technical support, OIC the funding support and VQiPS leadership direction, VTAG can provide advisory support. VTAG can also look beyond video quality to other issues such as interoperability and broadband as well as coordinate with other NPSTC committees as appropriate. communications and interoperability through collaborative leadership.! 40

41 NPSTC Partner Video Technology Advisory Group (VTAG) communications and interoperability through collaborative leadership.! 41

42 NPSTC Partner Video Technology Advisory Group (VTAG) Current Members EMS Community Pret Bjorn, Maine Airport Community Dave Cardenas, LAX Associations Joe Gitten, SIA Lou Chavez, UL Emergency Management Community Josh Jack, DC EMA Jon Lewin, Chicago EMA Police Community Jan Garvin, FBI Ron Derderian, Beverly Hills Michael Falcone, Boca Raton, FL Fire Community Charles Werner, Charlottesville (Virginia) Fire Chief ERIC Community Eddie Reyes, Deputy Police Chief, City of Alexandria, VA Cuong Luu, Program Manager, DHS, Wasington, DC Commercial Community Ty Bekiares, Motorola Solutions, Schaumburg, IL, communications and interoperability through collaborative leadership.! 42

43 NPSTC Partner Video Technology Advisory Group (VTAG) Activities Initial VTAG Conference Call held September 21, 2011 Discussed VTAG role and provided an update on VQiPS activities. Discussed draft DHS report Video Quality Tests for Object Recognition Applications prepared by PSCR for DHS S&T OIC Relay comments on DHS report Review ANSI handbook Held quarterly calls on November 8, 2011 and April 10, 2012 communications and interoperability through collaborative leadership.! 43

44 VQiPS 2012 Workshop Help Determine the Path Forward You re Invited to the Video Quality in Public Safety: VQiPS 2012 Workshop July 26-27, 2012, Denver, Colorado communications and interoperability through collaborative leadership.! 44

45 Video Technology Advisory Group (VTAG) Questions? Thank you John Contestabile Johns Hopkins University/Applied Physics Lab communications and interoperability through collaborative leadership.! 45

46 NPSTC Meeting Lunch Provided by TIA and FCCA communications and interoperability through collaborative leadership.! 46

47 PSWAC Follow-up: Assessment of Future Spectrum Technology (AFST) Working Group Joe Ross, Chair The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's! Science and Technology Directorate, Office for Interoperability and Compatibility (OIC) and the! National Protection and Programs Directorate, Office of Emergency Communications (OEC)! Points of view or opinions expressed are those of the originators and do not necessarily represent the official position! or policies of the U.S. Department of Homeland Security.!.!

48 AFST Update Report reviewed by NPSTC Executive Board in February Report released for 30 day public comment period ending April 20, Public comment edits have been reviewed and incorporated where appropriate. Final Version now presented for approval. communications and interoperability through collaborative leadership.! 48

49 AFST Update Changes in the Final Document: Report name change Public Safety Communications Assessment , Technology, Operations & Spectrum Roadmap Acknowledges the Congressional Spectrum Act and associated changes with D Block, T Band give back. Added new recommendation to work on Bomb Robot and other on scene technical system spectrum issues. Added new recommendation to study impact of T Band spectrum give back on affected areas. Miscellaneous editorial and syntax clean up. communications and interoperability through collaborative leadership.! 49

50 AFST Recommendations Summary Separate narrowband and broadband frequency allocations should continue until broadband technologies are proven. Public Safety agencies should work toward optimal implementation of the SAFECOM continuum. Use of open standards and full implementation of SAFECOM continuum will provide sufficient talk path capabilities, except for VHF NPSTC should develop a White Paper on interoperability best practices for user agencies with disparate technology and frequencies. Public Safety Agencies should provide initial and recurring training on operability and interoperability. communications and interoperability through collaborative leadership.! 50

51 AFST Recommendations Summary Future I/O solutions and subscriber equipment should be designed for ease of use and minimum complexity Public Safety agencies are encouraged to leverage the use of a COML to enhance incident interoperability. Next generation systems should assess available network options and automatically create a talk path for the first responder. Public Safety agencies should be able to access a broadband network designed for a public safety grade of service and managed by public safety. Mission critical PTT over broadband must include automatic connection to other agencies without reprogramming. communications and interoperability through collaborative leadership.! 51

52 AFST Recommendations Summary NPSBBN should provide interoperable common applications and features nationwide that support operational needs; and the device should let the user know that they are in fact connected. NPSTC should support work to identify impediments and solutions for mission critical PTT over LTE. Public Safety agencies need broadband application standards to allow multiple agencies to share information. The NPSBBN should be sufficiently robust to support the needed applications at the required quality of service. The NPSTC BBWG should identify short term and long term opportunities for mission critical voice over LTE; short term benefits should not be held up by longer term goals. communications and interoperability through collaborative leadership.! 52

53 AFST Recommendations Summary Broadband networks and applications must affordably satisfy all of the requirements for public safety before it can replace LMR systems. NPSTC should continue the work of the BBWG to develop broadband requirements and solutions. NPSTC should work with appropriate standards bodies to improve cell edge spectral efficiency. Technical standards are needed to enhance the usability of broadcast and multicast solutions in LTE. Public Safety needs additional VHF spectrum; review Part 22 channels and request FCC Audit of VHF. communications and interoperability through collaborative leadership.! 53

54 AFST Recommendations Summary NPSTC should create a working group to study the impact and possible solutions regarding loss of the T Band spectrum. Microwave spectrum should be monitored and may need to be increased, especially in areas where fiber cannot be deployed; broadband fiber and shorter microwave hops should be encouraged whenever possible. Examine increased use of 4.9 GHz for backhaul. Additional interoperability channels are needed in VHF and could be assigned from the Part 22 channels (if allocated); the FCC should audit the UHF spectrum to determine is any recovered channels after narrowbanding should be allocated for interoperability. communications and interoperability through collaborative leadership.! 54

55 AFST Recommendations Summary NPSTC should facilitate discussions with public safety users, wireless vendors and equipment manufacturers to find solutions to accommodate narrowband and broadband spectrum needs for bomb robots and other on scene technical devices. communications and interoperability through collaborative leadership.! 55

56 Request for Approval Approve the Final Report Approve Ex Parte filing of the report with the FCC communications and interoperability through collaborative leadership.! 56

57 Request for Approval Approve Work Plan: Assign responsibility for a White Paper on Interoperability Best Practices. Continue the work of the BBWG regarding requirements and solutions for public safety and issues noted in this report. Work with appropriate bodies regarding enhancements to Cell Edge Spectral efficiency Request the FCC to address issues with Part 22 radio channels (audit, freeze, reallocate, interoperability) Request FCC to audit the UHF spectrum and determine if additional interoperability channels can be allocated. communications and interoperability through collaborative leadership.! 57

58 Request for Approval Approve Work Plan: Create a working group to study the impact of the loss of T Band spectrum on public safety agencies Assign a study group to examine bomb robot spectrum allocation issues. communications and interoperability through collaborative leadership.! 58

59 Radio Programming Compatibility Requirements Working Group Pam Montanari, Chair Scope of Effort Presentation Work Session June 4-6, DHS-OEC Kenneth J Link Jr. ( Workgroup Member ) The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's! Science and Technology Directorate, Office for Interoperability and Compatibility (OIC) and the! National Protection and Programs Directorate, Office of Emergency Communications (OEC)! Points of view or opinions expressed are those of the originators and do not necessarily represent the official position! or policies of the U.S. Department of Homeland Security.!.!

60 Radio PCR Workgroup Problem Statement: P25 Technology was designed to allow multiple manufacturers radios operate on the same system. Radio programming software from manufacturers varies in design and is not compatible between manufacturers. There is no standard established for the programming software and user agencies are required to maintain and train personnel on multiple vendor s software. Current programming software hampers operations due to software design. communications and interoperability through collaborative leadership.! 60

61 Radio PCR Workgroup Statement of Need: There is a requirement for a plug and play interface between manufacturer s P25 radio programming software that provides compatibility and allows users to effortlessly program multiple vendors P25 radios onto a single infrastructure and eliminate the need for additional training and reduce the chance of programming errors that may adversely impact operations. communications and interoperability through collaborative leadership.! 61

62 Radio PCR Workgroup Working Group Goals: The goal of this working group is to work with P25 radio vendors and user groups to develop a requirements document that outlines specific programming functions and features that are part of the P25 standard and should be easily transferred from one vendors radio to another. communications and interoperability through collaborative leadership.! 62

63 Radio PCR Workgroup Various vendors utilize radio programming software to enable / disable the feature sets of Project-25 subscriber equipment. Presentation created to provide high level view of actual problem and/or discrepancies between vendor software's within the same Project-25 value ** The presentation is not vendor specific, nor is it a means to identify flaws or highlights in any one specific vendor s product ** Multiple vendors platforms will be reviewed and sample fields will be captured for discussion at NPSTC Radio PCR meeting communications and interoperability through collaborative leadership.! 63

64 Vendor Software Review Motorola EF Johnson Kenwood Thales Bendix King Harris communications and interoperability through collaborative leadership.! 64

65 Motorola ASTRO 25 CPS/APX Motorola identifies various features and P25 nomenclature via a tree and root menu system Various programming languages are utilized to create Motorola CPS Current availability in CPS to export various features into either.xml or.csv file formats Various security features utilized to allow / disallow access of the feature sets communications and interoperability through collaborative leadership.! 65

66 Motorola ASTRO 25 CPS/APX P25 Language Utilized! System ID! WACN! Exportable Properties would include at least these to a minimum! ASTRO 25 name is proprietary to vendor! communications and interoperability through collaborative leadership.! 66

67 EF Johnson PCConfigure Utilizes similar nomenclature as Motorola Motorola Non-P25 systems such as propietary Smartnet and Smartzone technologies can be programmed into this software Significant differences in conventional and trunking nomenclature to other vendors communications and interoperability through collaborative leadership.! 67

68 EF Johnson PCConfigure communications and interoperability through collaborative leadership.! 68

69 Thales Liberty Programming Utilizes mostly standards based nomenclature Exportable data sets into.xml and.sql formats communications and interoperability through collaborative leadership.! 69

70 Thales Liberty Programming communications and interoperability through collaborative leadership.! 70

71 Bendix King DPHedit Has significant nomenclature differences in relation to other vendors but does related to P25 well. Does not appear to be exportable into.xml ( Possibly due to version that was tested) Several steps required for trunking setup Conventional relatively simple communications and interoperability through collaborative leadership.! 71

72 Bendix King DPHedit communications and interoperability through collaborative leadership.! 72

73 Radio PCR Workgroup Notes Working Meeting Notes : 06/04/2012 (DHS-OEC) Team captured general, conventional, trunking parameters that would be initial requirement for the middleware or X product deliverable. Various features such as CAI data, and RFSS data need to be authenticated and verified at the P-25 Standards level to ensure clarity across vendor software s. (Ex. Check box for Moto Prop features or Harris features in the CAI area) communications and interoperability through collaborative leadership.! 73

74 Radio PCR Workgroup Notes Features and functionalities impacting overall radio specific to programming a P25 Radio for both Conventional and Trunking Conventional Personality (RX) Conventional Personality (TX) Talkgroup List Zone/Channel Assignment Trunking Features Trunking System and Features communications and interoperability through collaborative leadership.! 74

75 Interoperability Committee John Powell, Committee Chair Pam Montanari, Committee Vice Chair The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's! Science and Technology Directorate, Office for Interoperability and Compatibility (OIC) and the! National Protection and Programs Directorate, Office of Emergency Communications (OEC)! Points of view or opinions expressed are those of the originators and do not necessarily represent the official position! or policies of the U.S. Department of Homeland Security.!.!

76 Tampa Bay Goal 3 Exercise Pam Montanari The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's! Science and Technology Directorate, Office for Interoperability and Compatibility (OIC) and the! National Protection and Programs Directorate, Office of Emergency Communications (OEC)! Points of view or opinions expressed are those of the originators and do not necessarily represent the official position! or policies of the U.S. Department of Homeland Security.!.!

77 Tampa Bay Goal 3 Exercise Tampa Bay Region requested Technical Assistance from OEC Initial Goal 3 Demonstration for OEC Planned a Functional Exercise Participants from all disciplines Local, State and Federal agencies Large scale event communications and interoperability through collaborative leadership.! 77

78 Tampa Bay Goal 3 Exercise Exercise was held on March 29, 2012 Over 140 in attendance Test existing capabilities After-Action Report Provided specific recommendation Used for preparation and planning Identify Gaps communications and interoperability through collaborative leadership.! 78

79 Interoperability Committee Border Issues Working Group Terry LaValley, Chair Emergency Medical Services Working Group Kevin McGinnis, Chair Emerging Digital Radio Technologies (EDRT) White Paper John Powell, Committee Chair communications and interoperability through collaborative leadership.! 79

80 EDRT White Paper Generally unaware users are buying proprietary features and/or radios that are hampering (in worst cases defeating) interoperability with their neighbors for day-to-day interoperability and outside agencies for mutual aid. In addition to the well-documented issues within P25 (e.g., non-aes standard encryption), a number of manufacturers have introduced other non-p25 digital systems (some proprietary) resulting in neighboring agencies being unable to interoperate on infrastructure and (in some cases) in direct analog mode. communications and interoperability through collaborative leadership.! 80

81 EDRT White Paper Using resources from all committees, the EDRT White Paper WG has been meeting bi-monthly to better identify the problem and prepare a paper to document the issues and potential solutions. The FCC as recently as May 31 has expressed an interest in the paper as it considers during upcoming months current proceedings such as the TETRA petition and the impact these technologies are having on interoperability Detailed outline with some first draft text will be presented to the Governing Board for their initial review and comments communications and interoperability through collaborative leadership.! 81

82 Policies & Procedures for Use of the National Interoperability Channels A generic document was prepared for the State of Nevada that has been scrubbed to make it generic; this document was presented to the Governing Board in late 2010 Content needs to be finalized and posted as a best practice document on the NPSTC website communications and interoperability through collaborative leadership.! 82

83 Channel Naming Approval by the FCC of the NPSTC petition to assign 8 reserved 700 MHz interoperability channels for airground use will require reopening of the ANSI Naming Standard for revision to add names for these new channels communications and interoperability through collaborative leadership.! 83

84 Channel Naming Now that the public safety community has widely accepted and is programming the ANSI names into their radios, is the time approaching for NPSTC to ask the FCC to, at some future date TBD, require the use of these names as a condition of their licensing? Should manufactures likewise be required to load these names as the default when one of the national interoperability frequencies is programmed into a radio? communications and interoperability through collaborative leadership.! 84

85 NPSTC Meeting TETRA Critical Communications Association (TCCA) Tony Gray, Chairman, Critical Communications Broadband Group (CCBG) First Net Update Anna Gomez, Deputy Assistant Secretary of Communications, National Telecommunications and Information Administration (NTIA) communications and interoperability through collaborative leadership.! 85

86 NPSTC Meeting Public Safety Acknowledgements Ralph Haller, NPSTC Chair Cake & Coffee provided in Honor of DJ Atkinson by AASHTO communications and interoperability through collaborative leadership.! 86

87 NPSTC Meeting Recess communications and interoperability through collaborative leadership.! 87

88 NPSTC Meeting Reconvene Tuesday, June 6, :30 AM Alexandria Police Department Meeting Room L75 communications and interoperability through collaborative leadership.! 88