Fleetmap For Com
Fleetmap For Com
Fleetmap For Com
For
Trunked Radio Systems
Joe Kuran
April 2014
Fail Soft
CSSI
Types of Operational Needs
Subscribers
User IDs
Talk
Groups
Number of
Subscribers
Fleet Map
FLEETMAPPING Defined
The first task in fleetmapping is dividing the entire range of INV (Individual Radio Unit) IDs
that are available into blocks, or often called partitioning. Depending on the demographics of the
trunked radio system, INV IDs can be called radio ID, subscriber ID, UNIT ID, or customer ID,
for this document, Subscriber ID will be used to describe the unique number assigned to each
radio in the system. This unique number can be a number from 1 to 16,777,211.
There has been some previous work done in Oregon by the City of Eugene and Motorola to
divide up this range into blocks of 100,000 IDs each (See Appendix A). This document labeled
Oregon County Fleetmapping Guide is certainly a good start, but there are a few limitations to
this guide that need to be addressed. This guide assigns a block of 100,000 Subscriber IDs per
county and to each large State Agencies. This guide assigns the 1st two digits of the Subscriber
ID to represent that unique county.
This only allows ninety nine (99) counties. Some States have more than 99 counties.
Also, this can be problematic when there are two or more systems per county, such as
Multnomah County, which has the City of Portlands system and TriMets system. At the other
end, the Tri-County Frontier 700MHz trunked system covers Gilliam, Sherman, and Wheeler
Counties. This would tie up 300,000 Subscriber IDs for system that has fewer than 2,000 radios.
Plus allowing only 2 digits for county ID prevents the range from going past 10 million. And
finally there could be counties in adjacent States that are part of an Oregon system that might
have a duplicate county name.
The following is a proposed guide to address these limitations (See Appendix B). This proposed
fleetmapping takes advantage of the entire range of 16 million available Subscriber IDs, while
still preserving the Original County and State Agency allotment guide. For example, the
proposed guide preserves Lane Countys Subscriber ID range of 2,000,000 to 2,099,999 and this
proposal adds a zero in front of county ID changing it from 20 to 020. Plus, changing the
nomenclature from county ID to SYS (System) # will allow for unique system # to identify ISSI
roaming information needed for fleetmapping. And additionally, there will now only be one SYS
# for the Tri-County Frontier system, instead of three. And finally, City of Portland can use the
original Multnomah County ID and a new one can assigned to Tri-Met. (See Appendix C for in
depth ID analysis)
Once the entire region wide master subscriber ID FLEETMAP is partitioned out, each system
owner has the opportunity to craft their own subscriber fleetmap to meet their specific
operational requirements. Lane County/City of Eugene has already developed their own
subscriber fleetmap (See Appendix E). The advantage to this fleetmap is that the system
manager can tell by the subscriber ID number what the service is (i.e. police, fire) and type of
radio (i.e. portable, mobile). Another example (See Appendix F) could be where the type of
radio is not a concern and more service categories are needed.
Both Fleetmap E and F are adequate until the range is exceeded, for example, the Lane County
fleetmap only allows for 2000 police mobiles. Once that range is exceeded, the system manager
may have start using IDs from another service range, such as utilities.
It depends on the system size and anticipated number of subscribers on the system as to what
plan is used.
A third example, could be to have one continuous block of all 100,000 subscribers IDs and
assign IDs on come first come basis. Since all subscribers IDs that are entered into the database
system usually has an associated alias, a simple ID search would reveal the identity of the
subscriber. Also, having a continuous range may assist the technical system manger in
controlling as to what IDs are already in use, and which IDs are open.
This way the radio programming technicians can grab the next available range of IDs needed.
By using the continuous subscriber ID fleetmap leads us right into the discussion of assigning the
subscriber parameters to each ID (See Appendix G). Again, this is just an example; its up each
Technical System Manager to tailor the layout to their specific system requirements and vendor
specific terms.
Discussing the actual Subscriber ID parameters is a subject for future discussion. The goal of
this document is to offers a few proposed changes to the general fleetmap layout to facilitate
http://npstc.org/download.jsp?tableId=37&column=217&id=3010&file=NPTSC_PAM_Tool_A1.x
lsx
The Talkgroup can also have various configurations, Appendix H represents the existing Lane
County Talkgroup Fleetmap and Appendix I represents typical example of the Talkgroup
information that could be associated with each Talkgroup. Appendix I also does not follow the
unique pre-assigned blocks, but uses the continuous list of IDs.
APPENDIX E: Existing Lane County subscriber ID mapping. This plan assigns unique blocks
of 100 subscriber IDs to specific types of radio service and type of radio. Limits radio service to
10 categories.
APPENDIX F: Example similar to Lane County, but assigns blocks based only radio service.
This example allows for a larger variety of radio service categories, but lacks the ability to
specific radio types.
APPENDIX G: This is an example where the entire subscriber ID list would be a continuous
list of all 100,000 assigned per system. As new IDs are needed, they assigned in sequential
order.
Plus allows creating master database list of all programing parameter assigned to each subscriber
ID.
APPENDIX H: Existing Lane County talkgroup ID mapping. This plan assigns unique blocks
of 100 talkgroup IDs to types of radio service. Limits radio service to 10 categories.
APPENDIX I: This is an example where the entire talkgroup list would be a continuous list of
all 1000 TGs assigned per system. As new talkgroups are needed, they assigned in sequential
order. Plus it allows creating master database list of all talkgroup information assigned to each
talkgroup.
Example:
20 - LANE COUNTY RADIO ID RANGE 2,000,000 - 2,099,999 (1E8480 - 200B1F HEX)
COUNTY ID COUNTY ID
Baker (1B) 01 Wheeler (3W) 35
Benton (2B) 02 Yamhill (1Y) 36
Clackamas (1C) 03 System Wide 37
Clatsop (2C) 04 OSP 38
Columbia (3C) 05 DOC 39
Coos (4C) 06 ODOT 40
Crook (5C) 07 ODFW 41
Curry (6C) 08 State Forestry 42
Deschutes (1D) 09 DHS/OEM 43
Douglas (2D) 10 Other-State 44
Gilliam (1G) 11 Tribal 45
Grant (2G) 12 Federal 46
Harney (1H) 13 FUTURE 47
Hood River (2H) 14 FUTURE 48
Jackson (1J) 15 FUTURE 49
Jefferson (2J) 16 FUTURE 50
Josephine (3J) 17 FUTURE 51
Klamath (1K) 18 FUTURE 52
Lake (1L) 19 FUTURE 53
Lane (2L) 20 FUTURE 54
Lincoln (3L) 21 FUTURE 55
Linn (4L) 22 FUTURE 56
Malheur (1M) 23 FUTURE 57
Marion (2M) 24 FUTURE 58
Morrow (3M) 25 FUTURE 59
Multnomah (4M) 26 FUTURE 60
Polk (1P) 27 FUTURE 61
Sherman (1S) 28 FUTURE 62
Tillamook (1T) 29 FUTURE 63
Umatilla (1U) 30 FUTURE 64
Union (2U) 31
Wallowa (1W) 32
Wasco (2W) 33
Washington (3W) 34
WACN ID
SYSTEM ID UNIT ID
20 BITS
12 BITS 24 BITS
(WIDE AREA COMMUNICATIONS NETWORK
(SYSTEM IDENTIFIER) (RADIO SUBSCRIBER ID)
IDENTIFIER)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
9 2 6 B 9 B E A 3 3 E 1 4 0
1 2 3 4 5 1 2 3 1 2 3 4 5 6
Motorola P25 7.13 system valid INDIVIDUAL RADIO ID RANGE for ASTRO 7.x is 1 to 16,777,211
Motorola P25 7.13 system has the capacity to support 128,000 ID's per system and 64,000 per Zone
Project 25 terms:
In the proposed Fleetmapping Subscriber ID partioning (Appendix B) the SYS # is used as a reference to
help manage the systems in cronological order, and the SYSTEM ALIAS increase the user friendliness.
The actual SYSTEM ID is a vendor generated three (3) character Hexidemical number. The SYSTEM ID
has no relationship to rhe SYS #.
RADIO ID
000
SERVICE 001
0 - POLICE 002
1 - POLICE *
2 - FIRE/EMS RADIO TYPE *
3 - FIRE/EMS 0 - PORTABLE *
4 - PUBLIC WORKS 1- PORTABLE *
5 - UTILITIES 2 - MOBILE *
6 - FED/BLM/CORPS 3 - MOBILE *
7 - MISC 4 - CONTROL STATION *
8 - FUTURE 5 - DISP CONT STA 999
9 - FUTURE 7 - FUTURE
7 - FUTURE
8 - FUTURE
9 - FUTURE
BLOCK NUMBER
SERVICE (1000 IND ID's PER BLOCK) START OF RANGE END OF RANGE
(100,000 Available)
(S)tatic Non-Tactical
(N)one No
4 A 3,403,000 33ECF8 COMMANDER CODY 10.7.0.1 S A B CKR1 CKR2 CKR3 KING COUNTY
5 A 3,404,000 33F0E0 SHADOW LEADER 10.7.1.1 S A B CKR1 CKR2 CKR3 CKR4 CKR5 KING COUNTY
CKR (Common Key Reference) is a Motorola term for the P25 term SLN (Storage Location Number)
800 XX X XX
COUNTY
SERVICE TALKGROUP ID
0 - POLICE 00
1 - POLICE 01
2 - FIRE/EMS 02
3 - FIRE/EMS *
4 - PUBLIC WORKS *
5 - UTILITIES *
6 - FED/BLM/CORPS *
7 - MISC *
8 - FUTURE *
9 - FUTURE 99
COUNTY ID COUNTY ID
Baker (1B) 01 Wheeler (3W) 35
Benton (2B) 02 Yamhill (1Y) 36
Clackamas (1C) 03 System Wide 37
Clatsop (2C) 04 OSP 38
Columbia (3C) 05 DOC 39
Coos (4C) 06 ODOT 40
Crook (5C) 07 ODFW 41
Curry (6C) 08 State Forestry 42
Deschutes (1D) 09 DHS/OEM 43
Douglas (2D) 10 Other-State 44
Gilliam (1G) 11 Tribal 45
Grant (2G) 12 Federal 46
Harney (1H) 13 FUTURE 47
Hood River (2H) 14 FUTURE 48
Jackson (1J) 15 FUTURE 49
Jefferson (2J) 16 FUTURE 50
Josephine (3J) 17 FUTURE 51
Klamath (1K) 18 FUTURE 52
Lake (1L) 19 FUTURE 53
Lane (2L) 20 FUTURE 54
Lincoln (3L) 21 FUTURE 55
Linn (4L) 22 FUTURE 56
Malheur (1M) 23 FUTURE 57
Marion (2M) 24 FUTURE 58
Morrow (3M) 25 FUTURE 59
Multnomah (4M) 26 FUTURE 60
Polk (1P) 27 FUTURE 61
Sherman (1S) 28 FUTURE 62
Tillamook (1T) 29 FUTURE 63
Umatilla (1U) 30 FUTURE 64
Union (2U) 31
Wallowa (1W) 32
Wasco (2W) 33
Washington (3W) 34
A
DES B
Yes AES Yes Yes Yes Auto C
xxx 2-10 No No xxx No xxx.xxxxx xxx.xxxxx No No Manual D
HOME TALKGROUP NAME PRIORITY ENCRYPTE FAILSOFT TX FREQ RX FREQ ANNONCE ALLOWED
TG # DEC ID HEX ID RECORDED CKR ROAM TYPE AGENCY
SYS ID (ALIAS) LEVEL D ENABLED (MHz) (MHz) TG SYSTEMS
7 34007
8 34008
9 34009
10 34010
11 34011
12 34012
CKR (Common Key Reference) is a Motorola term for the P25 term SLN (Storage
PRIORITY LEVEL
Location Number)
2 = Highest
10 = Lowest
1 reserved for
emergency