Region 43 Washington and Region 35 Oregon

1

• Region 43 (Washington) and Region 35 (Oregon)
• 800 MHz Regional Planning Committees
• April 27, 2005 0900 to 1230
• Clark County (WA) Elections building
• www.region43.org
• Please get signed up on the attendee roster
• Region 43 Minutes are on the back table
• Refreshments are on the back table
• If you parked in the Parking Garage, you will
  need to re-feed the meter at 2 hours. Well take
  a break at about 1030 to accomplish this..

2
Agenda for Todays 800 MHz Meetings

• Opening Introductions and Facility Logistics
  0900 to 0915
• Joint Meeting of the Region 43 and Region 35 RPCs
  with the 800 MHz Transition Administrator 0915
  to 1100
• Follow-up and clarification on information
  provided at the APCO Symposium the previous day
• Specific coordination issues in the
  Oregon/Washington border as Oregon proceeds in
  Wave 1 of the rebanding effort and Washington
  waits for Wave 4
• Coordination with local systems (Clark County,
  Portland, Washington County, etc.)
• Coordination with statewide systems (WSDOT,
  WSDOC, etc.)
• Strategies for interactions and coordination
  between the RPCs during entire rebanding process
• Joint discussion of the future path of the
  National Association of Regional Planning
  Committees (NARPC) 1100 to 1130
• Review of history of NARPC original formation
• Review of proposed direction
• Debate and possible adoption of a joint Region 43
  and 35 position statement
• Region 43 800 MHz Approval of Minutes of February
  23, 2005 Meeting
• Region 43 Spring Filing Window 800 MHz
  Application Processing (Region 35 encouraged to
  stay for Spring Filing Window) 1130 to 1230
• WSDOT
• Clark County

3
Introductions

• Name
• Agency youre with
• Brief description of your 800 MHz system and
  service area
• Please sign up on the sign-in sheet
• If youre interested in keeping in touch with
  activities in Region 43, please self-subscribe to
  the Listserver on the web site www.region43.org

4

Current 800 MHz Band Allocations in Non-Border
Areas
806
824
764
762
776
792
777
794
849
851
747
Mobile
A
C
D
D
C
A
B
B
A
B
B
A
700 MHz Public Safety (Base)
700 MHz Public Safety (Mobile)
800 MHz Band
Upper 700 MHz Commercial
Upper 700 MHz Commercial
Upper 700 MHz Commercial
Cellular
ATG
894
Base
700 MHz Guard Band

869
851
700 MHz Commercial and 700 MHz Guard Band do not
have specified Base and Mobile channels
Mobile and Control Station Transmit Frequencies
(in MHz)
824
806
809.75
821
816
NPSPAC (Public Safety)
General Category
Interleaved Spectrum
ESMR (Upper 200)
851
854.75
866
861
869
Base Station Transmit Frequencies (in MHz)
General Category -7.5 MHz 150 Channels Licensed
by EA Blocks of 25 channels (SMR) Some Incumbent
Operators Remain
Interleaved Spectrum -12.5 MHz 250 Channels 80
SMR Channels (Licensed by EA, Some Incumbent
Operators Remain) 70 Public Safety Channels 50
Business Channels 50 Industrial Land
Transportation Channels
NPSPAC - 6 MHz 225 Channels _at_ 12.5 kHz spacing 5
Channels _at_ 25 kHz spacing 5 Mutual Aid Channels
ESMR/Upper 200 10 MHz 200 Channels Licensed by
EA Non EA incumbents are currently undergoing
mandatory relocation
5

Post Re-banding 800 MHz Band Allocations in
Non-Border Areas

806
824
764
762
776
792
777
794
849
851
747
Mobile
A
C
D
D
C
A
B
B
A
B
B
A
700 MHz Public Safety (Base)
700 MHz Public Safety (Mobile)
800 MHz Band
Upper 700 MHz Commercial
Upper 700 MHz Commercial
Cellular
ATG
894
Base
700 MHz Guard Band
869
851
700 MHz Commercial and 700 MHz Guard Band do not
have specified Base and Mobile channels
Mobile and Control Station Transmit Frequencies
(in MHz)
824
817
806
809
815
816
809
Public Safety B/ILT Non-Cellular SMR
NPSPAC (Public Safety)
Guard Band
Expansion Band
ESMR
NPSPAC
869
861
851
854
860
862
Base Station Transmit Frequencies (in MHz)
No public safety system will be required to
remain in or relocate to the Expansion Band
although they may do so if they choose. No
public safety or CII licensee may be
involuntarily relocated to occupy the Guard Band.
6
Before
Non-Border Areas
Mobile and Control Station Transmit Frequencies
(in MHz)
Base Station Transmit Frequencies (in MHz)
Mobile and Control Station Transmit Frequencies
(in MHz)
824
817
806
809
815
816
809
Public Safety B/ILT Non-Cellular SMR
NPSPAC (Public Safety)
Guard Band
Expansion Band
ESMR
NPSPAC
869
851
854
860
862
861
Base Station Transmit Frequencies (in MHz)
813.5/858.5 Southeast ESMR Band Plan Moves the
Expansion Band edge (see Appendix G for list of
affected states/counties)
After
7
(No Transcript)
8
From December 24, 2002 Filing by Consensus Parties
9
From December 24, 2002 Filing by Consensus Parties
10
From December 24, 2002 Filing by Consensus Parties
11
From December 24, 2002 Filing by Consensus Parties
12
Proposed Prioritization Waves
13
Meeting with the 800 MHz Transition Administrator

• Joint Meeting of the Region 43 and Region 35 RPCs
  with the 800 MHz Transition Administrator 0915
  to 1100
• Follow-up and clarification on information
  provided at the APCO Symposium the previous day
• Specific coordination issues in the
  Oregon/Washington border as Oregon proceeds in
  Wave 1 of the rebanding effort and Washington
  waits for Wave 4
• Coordination with local systems (Clark County,
  Portland, Washington County, etc.)
• Coordination with statewide systems (WSDOT,
  WSDOC, etc.)
• Strategies for interactions and coordination
  between the RPCs during entire rebanding process

14
NARPC

• Joint discussion of the future path of the
  National Association of Regional Planning
  Committees (NARPC) 1100 to 1130
• Review of history of NARPC original formation
• Review of proposed direction
• Debate and possible adoption of a joint Region 43
  and 35 position statement

15
NARPC - History

• One of the functions of the National Public
  Safety Telecommunications Council (NPSTC) is to
  carry forward any work remaining after the sunset
  of the 700 MHz National Coordination Committee
  (NCC)
• This included a significant body of work to make
  sure that 700 MHz Regional Planning Committees
  got formed and got moving on developing plans
• NPSTC identified sub-groupings of RPCs and
  provided funding for a representative from each
  of these to attend NPSTC meetings and represent
  RPC views and needs

16
NARPC - History

• After a couple of meetings, there was some
  questioning of how these individuals were
  selected and whether they truly represented the
  views of the RPCs in their area. There was a
  sense that some form of selection process needed
  to be executed by the RPCs themselves to select
  these representatives.
• Further, there was some interest in forming an
  association of RPCs to serve as a clearinghouse
  for information and perhaps to even sound as a
  common voice for PRC interests
• In November 2003, Steve Devine, Region 24 (MO)
  Chair, sent out material to introduce the concept
  of forming NARPC
• This was envisioned as a body without a lot of
  formal processes and procedures and no dues
  structure
• Sample letters of support were circulated and in
  December 2003, Region 43 sent in a letter of
  support.

17
NARPC History

• The model NARPC support letters requested that
  NARPC be recognized as a formal member of NPSTC
  and have a seat on the NPSTC Governing Board
• However, due to NPSTC governing principles and
  funding provisions, NARPC as an informal body
  with no ability to contribute to the operational
  costs and functions of NPSTC (like APCO, IACP,
  IAFC and others can) limited that possibility
• There has also been some concern expressed from
  various quarters that forming another public
  safety communications oriented association might
  weaken the voice of public safety and create the
  opportunity for mixed messages
• Renewed efforts are underway to formally
  constitute NARPC as a free-standing association

18
NARPC Current Re-Draft Mission Statement

• The National Association of Regional Planning
  Committees (NARPC), a collaborative network of
  locally conscious national public safety planning
  regions, exists
• To freely and efficiently promote public safety
  communications information and ideas both among
  the committees and between the committees and the
  local regional, and national communities they
  serve,
• To stimulate peer review and develop national
  consensus-based conclusions when applicable,
  while giving due consideration to the existence
  of unique public safety communications
  requirements within regions, and
• To provide a united national voice for the
  nations FCC designated planning committees when
  addressing public safety spectrum management
  issues at national forums.

19
NARPC Discussion/Direction

• Discussion/Debate on the NARPC concept
• Direction?

20
Minutes of the February 23, 2005 Region 43 800
MHz RPC

• Motion and 2nd to Approve?
• Action

21
Spring Filing Window

• Region 43 Spring Filing Window 800 MHz
  Application Processing (Region 35 encouraged to
  stay for Spring Filing Window discussion) 1130
  to 1230
• WSDOT
• Clark County
• Benton County
• WSDOC McNeil Island

22
WSDOT Requests
23
WSDOT Dusty Whitman County

• 644 is already assigned as a WSDOT statewide
  channel, so no problem there. Chair recommends
  approval.
• 680 is assigned to WSDOC for statewide use, so
  well need to get confirmation from DOC that they
  are OK with DOT using this channel at this
  Whitman County location. Chair recommends
  approval if DOC confirmation is positive.

24
WSDOT Blagg Mountain Chelan Co.

• 758 is already assigned as a WSDOT statewide
  channel, so no problem there. Chair recommends
  approval.
• 829 was Unassigned in the Plan. Weve already
  assigned it several times to WSDOT and it is also
  used by EPSCA in North Seattle. Totally terrain
  blocked to King County so no problem there.
  Adjacent channels were also Unassigned in the
  Plan and have been assigned to WSDOT at lots of
  sites, so no apparent problem there. Chair
  recommends approval.
• 784 was Unassigned in the Plan. Weve already
  assigned it to several WSDOT sites. Pierce and
  King have adjacent channels but terrain blocking
  makes this not a problem. Chair recommends
  approval.

25
WSDOT Federal Way King County

• 830 is unassigned in the Plan, and weve already
  given it to WSDOT at several other sites. EPSCA
  uses 829 at the North Seattle site and this may
  create an adjacent-channel problem for either
  WSDOT or EPSCA.
• Chair recommends we require interference testing
  before approving this one.

26
WSDOT Pinus Lake Whatcom County

• 758 is already assigned as a WSDOT statewide
  channel, so no problem there. Chair recommends
  approval.
• 829 was Unassigned in the Plan. Weve already
  assigned it several times to WSDOT and it is also
  used by EPSCA in North Seattle. Coverage
  prediction map indicates no co-channel signal
  problems outside of Whatcom County. Adjacent
  channels were also Unassigned in the Plan and
  have been assigned to WSDOT at lots of sites, so
  no apparent problem there. Chair recommends
  approval.
• 784 was Unassigned in the Plan. Weve already
  assigned it to several WSDOT sites. Pierce and
  King have adjacent channels but terrain blocking
  makes this not a problem. Chair recommends
  approval.

27
WSDOT Ellis Mountain Clallam County

• 626 is in use in the Seattle area simulcast
  system. WSDOT has proposed using a directional
  antenna to avoid signal towards Seattle. No
  apparent co-channel issues into the King County
  area. Adjacent channels are Unassigned. Chair
  recommends approval.

28
WSDOT Kamilche Mason County

• WSDOT is proposing this site as a substitute for
  the previously approved South Mountain site.
• 728 was assigned for use in Mason County in the
  Plan and weve previously approved it for use at
  South Mountain by WSDOT.
• 810 was assigned for use in Mason County in the
  Plan and weve previously approved it for use at
  South Mountain by WSDOT.
• When we approved South Mountain, WSDOT planned to
  use a directional antenna to minimize signal
  towards King and Snohomish counties to avoid
  adjacent-channel interference to 809 in the King
  County simulcast system and 811 in the SERS East
  simulcast system.
• A directional antenna is also now proposed for
  Kamilche.

29
WSDOT South Mountain (previously approved)
30
WSDOT Queets Jefferson County

• 683 is already a WSDOT statewide channel, so no
  problem there. Chair recommends approval.
• 759 is a Guard channel between two WSDOT
  statewide channels. Chair recommends approval.

31
Washington State Homeland Security Region IV
Interoperability Project

• Text from the Chairs Initial Review Memo
• Clark County is requesting channel assignments to
  expand the coverage of their system to support
  the interoperability plan adopted for
  Washingtons Homeland Security Region IV. The
  goal of their project is to add two 3-channel
  trunking sites and one 2-channel conventional
  site to expand coverage up the Columbia River and
  the I-5 corridor so that VHF-to-800 patching can
  be better accomplished when needed for
  interoperable communications.
• They are currently completing the coverage
  predictions for their candidate sites, so Im not
  yet able to make any specific channel
  recommendations to the Committee. Ive attached
  their initial application letter and a quick map
  showing the sites they are considering in their
  planning work. As soon as the coverage
  predictions are available Ill get them forwarded
  out to the Committee. In general terms, I think
  their plan sounds like a good one and Im
  confident well be able to identify the 8
  channels they need.

32
Washington State Homeland Security Region IV
Interoperability Project
33
Benton County - ICALL
34
Benton County ICTAC-1
35
WSDOC McNeil Island

• WSDOC had previously requested the Committee to
  identify up to three (3) additional channels for
  expansion of system capacity and coverage at
  their McNeil Island facility
• A subcommittee from Zone 2 agencies developed a
  list of candidate channels (606, 623, 640, 699,
  735, 828) with 623, 735 and 828 determined as
  best.
• 828 seems to be the best for this
  single-channel use.
• WSDOT is co-channel up in Snohomish County
• EPSCA is adjacent on 827 and 829 at their North
  Seattle site
• Testing should be performed to make sure
  appropriate power levels and antenna
  configuration is used at the McNeil Island site
  to avoid interference to WSDOT and EPSCA, and to
  tolerate their incumbent signal levels

36
WSDOC McNeil Island
37
Break

• We will take a 1 hour lunch break and then begin
  the 700 MHz/4.9 GHz Regional Planning Committee
  meeting

38
Agenda for 700 MHz/4.9 GHz Meeting

• Introductions
• Approval of 700 MHz Minutes of February 23, 2005
• Information Updates
• SIEC Updates
• Actions in other RPCs, NPSTC, etc.
• General FCC or industry information of interest
• 700 MHz Regional Plan status update
• 4.9 GHz Regional Planning Subcommittee
• Information Updates
• Region 43 plan final editing and adoption

39
SIEC Activities

• Work is now underway on a final draft of the
  Alternatives Report
• Other key documents are posted on their web site
• http//isb.wa.gov/siec/SIECPublications.htm

40
Actions in Other RPCs and NPSTC

• Region 35s (Oregon)
• The concurrence documents are being routed to the
  Vice Chair for signing
• Region 12s (Idaho)
• Region 43 Concurrence documents have been sent to
  Idaho

41
NPSTC Updates

• March 2005 Spectrum Newsletter is available on
  the NPSTC website http//www.npstc.org/newsletter/
  v5issue1.pdf
• Presentations from the NPSTC Committee and Board
  meetings held in January are posted on the NPSTC
  web site. http//www.npstc.org/meetings.htm
• Presentations from the March 29/30 meetings are
  not yet posted

42
Canadian 700 MHz Band Allocation

• No new information on this issue

43
4.9 GHz Regional Planning Workgroup

• Edits/Changes to Draft Version 3
• Motion/Action to Approve the Plan for submission
  to the FCC

44
Other Items/Good of the Order

• Any?

45
700 MHz/4.9 GHz Future Meeting Dates

• Next Meeting
• May 25th Benton County Emergency Services
• June 29th Vancouver/Portland area, location TBD
• July 27th Eastside location TBD
• August 31st Vancouver/Portland area, location
  TBD
• September 28th Eastside location TBD
• October 26th Vancouver/Portland area, location
  TBD
• November 30th Eastside location TBD
• December 28th - ??????

46
Vendor Presentations

• Presentations Today
• None due to the joint meeting
• May 25th
• ?
• ?
• June 29th
• ?
• ?
• July 27th
• ?
• ?

47
Next Meeting
May 25, 2005 Benton County Emergency Services 651
Truman Avenue, Richland, WA Conference Call Phone
Number 253-512-7310 Agenda and meeting material
will be posted to the web site ( www.region43.org
) and sent to the email listserver in advance of
the meeting