700 MHz Regulatory Review

1. 700 MHz Regulatory Review Regional Planning Next Steps

2. Topics Covered • Why are we here? • Establishing the RPC • Notification • Writing the Plan • What has to be included? • 90.527 • What does the RPC want to include? • How will the RPC handle applications? • Filing the Plan with the FCC

3. Why are we here? • Region 38 (South Dakota) Regional Planning Committee is responsible for administering the 700 MHz narrowband general use channels • South Dakota needs to develop a Regional Plan and submit it to FCC for approval before any PS agency can get a license • Even if there’s no interest in 700 MHz at this time, Region 38 should still form and implement a procedure to review and approve adjacent Region’s Plans and applications

4. 700 MHz Spectrum • What’s it used for? • Narrowband (6.25 kHz) channels that can be aggregated to a maximum of 25 kHz bandwidth (if meet efficiency standards) • Voice (currently one voice path/12.5 kHz) • Data (4800 kpbs/6.25 kHz)

5. 700 MHz Narrowband Deadlines • 6.25e interim deadlines • 12.5 kHz applications can be filed until 12/31/2014 • On 1/1/2015 New Applications must be 6.25/6.25e • 12.5 kHz-only equipment can be manufactured and sold until 12/31/2014 • Ultimate 6.25e deadline is 1/1/2017 • Applies to General Use and State License channels • Low-power channels exempt

6. 746 752 762 773 764 776 747 767 777 806 782 792 803 794 797 A 1 Auction C 5 Auction D 10 B 2 PS NB 3 PS WB 6 PS NB 3 A 1 Auction C 5 Auction D 10 B 2 PS NB 3 PS WB 6 PS NB 3 800 MH Band Lower 700auction Narrowband Consolidation 60 61 62 63 64 65 66 67 68 69 746 763 757 758 768 769 775 776 787 788 793 799 805 806 798 Auction C 11 A 1 Auction D 5 PS BB 5 G B 1 PS NB 3 PS NB 3 B 1 Auction C 11 A 1 Auction D 5 PS BB 5 G B 1 PS NB 3 PS NB 3 B 1 800 MH Band Lower 700auction 60 61 62 63 64 65 66 67 68 69 700 MHz Bandplan Change Original Plan PS NB = Public safety narrowband spectrum New Plan Hybrid Broadband Network Consolidated Narrowband Hybrid Broadband Network Consolidated Narrowband Base Transmit Mobile Transmit

7. 746 763 757 758 768 769 775 776 787 788 793 799 805 806 798 Auction C 11 A 1 Auction D 5 PS BB 5 G B 1 PS NB 3 PS NB 3 B 1 Auction C 11 A 1 Auction D 5 PS BB 5 G B 1 PS NB 3 PS NB 3 B 1 800 MH Band Lower 700auction 60 61 62 63 64 65 66 67 68 69 700 MHz Bandplan Change Base Transmit Mobile Transmit • Public safety narrowband voice blocks consolidated • Guardband protects narrowband from broadband • C and D blocks auctioned in January 2008 • D Block auction winner required to implement a hybrid public safety / commercial national broadband network Hybrid Broadband Network Consolidated Narrowband Hybrid Broadband Network Consolidated Narrowband

8. PS Broadband • Broadband • Currently awarded to PS Broadband Licensee • To be used in conjunction with D Block CMRS spectrum to construction a nationwide public/private broadband PS network • D Block License was not awarded • Pending rulemaking to revise auction/build-out requirements • One of most important decisions facing new FCC Chair

9. State License Frequencies

10. 700 MHz State License • FCC gave States a 2.4 MHz narrowband state allocation • All 50 states plus DC, Puerto Rico and the Virgin Islands were granted 700 MHz State Licenses in 2002 • Geographic license – can use throughout the state without holding a license for each site • Each state is licensed for the same frequencies • Must coordinate at state borders

11. State License Construction • Two ‘substantial service’ deadlines: • By January 1, 2012 the state must be providing or prepared to provide substantial service to 1/3 of the population or territory • By January 1, 2017 the state must be providing or prepared to provide substantial service to 2/3 of the population or territory • A state is ‘Prepared to provide’ service if it can certify that a radio system meeting the substantial service requirements has been approved and funded • If either of these deadlines is not met, the state license will be modified to show what frequencies and what parts of the state are constructed • Recovered state license frequencies will revert to the RPC for reassignment

12. Interoperability Frequencies

13. State Administration of Interoperability Channels • Were required to notify FCC by 12/31/01 if were planning to administer the 700 MHz I/O channels • Administration involves holding the license, resolving licensing issues and developing a state-wide I/O plan • If FCC did not receive notice, administration of I/O channels reverted to the RPC 1/1/02 • Has the state formed an interoperability committee?

14. Tools for Regional Planning

15. 700 MHz Plan Status • Thirteen Plans are approved • AL, S. CA, AK, AZ, CO, MI, MO, MN, TN, WA, MD/N.VA/DC, WI, Region 51 (Houston area) • These can be used as templates • Fourteen are pending: • N. California (Region 6), NYC/N.NJ (Region 8) Florida (Region 9), Georgia (Region 10), Idaho (Region 12), Kansas (Region 16), Louisiana (Region 18), Nevada (Region 27), E.NY (Region 30), Ohio (Region 33), Dallas Area (Region 40), Utah (Region 41), Chicago/Great Lakes (Region 54), W. NY State (Region 55)

16. CAPRAD • A national database established in 2003 to pre-allot the 700 MHz band to protect slow-to-form Regions • Frequencies are allotted within a county but are available to any eligible entity within the County (including the State) • Can be used to: • File license applications to the Region • To allocate frequencies to license applicants • Post plan documents

17. Next Steps • Establishing the Committee • Notification • All disciplines • Federal Agencies • Tribal Nations • Keep records • NCC Appendix U provides a template

18. At First Meeting • Sign up Sheet • Name, agency, contact info (mailing address, phone #) • Establish subcommittees/working groups and assign chairpersons and tasks • Review required elements of the Regional Plan and assign to subcommittees (90.527 and NCC Guidelines document) • Bylaws • Technical • Implementation/Outreach • Interoperability • Writing • Set dates for RPC meetings through 2009 • Subcommittees could meet weekly, bi-weekly or monthly either in person or conference calls • Full meetings might be monthly or bi-monthly • Hold meetings in different parts of the state to encourage maximum participation if this makes sense

19. What Has to be in the Plan • 90.527 • Name, address, contact information of Chair • List of RPC Officers • Statement that 60 days notice was given prior to the 1st meeting • Summary of the major elements of the Plan • Description of how input was solicited from all RPC members • Description of the Region

20. What has to be in the Plan • Description of the types of agencies that are included in the Region • Technical procedures for requesting channels • How the Region will decide between competing applications • What role the RPC will play in administering the I/O channels

21. What does the RPC want in the Plan? • How will applications be handled? • Filing windows? • First come/first served? • State applications for general use frequencies • What showings required? • Loading requirements • Scoring matrix

22. Once Draft is Complete • Circulate final draft to members • Via list serve • Post on website • Post on CAPRAD • Call a full meeting to discuss/vote on the Plan • Document any discussion of the Plan • Vote to accept draft as the Region’s 700 MHz Plan

23. After Plan is Approved by Region • Must be sent to adjacent Regions for concurrence • Via CAPRAD • Via mail/email • NCC templates available on CAPRAD website • Draft cover letter • Draft concurrence letter

24. Inter-Regional Dispute Resolution • Each Plan must include a signed Inter-Regional Dispute Resolution Agreement from each adjacent Region • Draft NCC IRDRA available on CAPRAD database

25. Filing the Plan with the FCC • Use NCC’s Appendix R as a final checklist • May use FCC’s website electronic filing (ECFS) or an original and four copies may be filed with the Office of the Secretary • Email an electronic version to Jeannie Benfaida (jeannie.benfaida@fcc.gov) • Plan will be posted on the FCC’s website under Docket 02-378

26. FCC Has Stressed • Documentation of 60 day notice for the first meeting • Demonstrate how provided notice to all disciplines, tribal governments • FCC Public Notice should not be considered primary method • Adjacent Region Concurrence • Dispute resolution • Primarily between Regions, but also within the Region • First 2-5 pages should orient the reader and the public to what’s in the Plan • Include: • Bylaws • Membership list including contact information and voting status

27. FCC Process • Plan Approval: Generally within 4-6 months from date of filing. • Will review submitted Plans for completeness and contact Chair for additional info • If complete, Plan will be placed on Public Notice • 21 days for comments; 10 days for Replies • Absent a protest, Plan will be approved after the Comment period ends

28. Timing • Plan completed by end of July • Plan adopted by Region in July • To adjacent Regions in July • Adjacent Region sign-off by October • File Plan with FCC October • Plan approved by December • Best case scenario