Module 2

System Planning and Design

Course Map

• Introduction
• Module 1 – Capacity Max Review
• Module 2 – System Planning and Design
• Module 2 – Physical System Installation
• Module 4 – Capacity Max IP Networking
• Module 5 – Radio Management
• Module 6 – Capacity Max Configuration
• Module 7 – System Advisor
• Module 8 – Maintenance and Troubleshooting

2
Module 2 Objectives

At the end of this module, you should be able to:

• Develop an awareness of regulatory licensing requirements.

• Understand Motorola Solutions licensing for Capacity Max products.
• Be able to successfully use the MOTOTRBO System Designer Tool as part of
the design process for a Capacity Max system.
• Determine the appropriate system topology.
• Complete a basic fleetmap.
• Determine the infrastructure device ID map.
• Develop a channel plan.
• Understand the networking equipment requirements for a Capacity Max system.

3
Module Map

• Section 1: Planning Considerations

• Section 2: RF Channel Plan
• Section 3: Networking Requirements

4
High Level System Planning

This module will describe the key elements of how to plan a Capacity Max system.

• Correctly sizing the Capacity Max system is an important part of the planning
process.
• The following items need to have the required quantities defined as part of the
planning process:
• Radios
• RF Sites
• Trunked repeaters
• Data revert repeaters
• Voice gateway talk paths

5
High Level System Planning

• Motorola Solutions has created a group of software tools to assist in the planning
for MOTOTRBO systems called “MOTOTRBO System Design Tools (SDT)”.
• There are tools in the MOTOTRBO SDT to assist you in:
– Estimating the number of repeaters, trunked or data revert, needed at each
Capacity Max site.
– Estimating the site link bandwidth need for each site in the system.
– Determining the number of MNIS VRC Gateways needed in the system.
– Estimating the number of talkpath licenses needed for each MNIS VRC Gateway.

6
High Level System Planning

In order to effectively use the

MOTOTRBO System Design
Tools (SDT), there are some
basic planning considerations
you must first understand.
We will use the MOTORBO
System Design Tools later in
this module once we have
reviewed the basic planning
considerations for a Capacity
Max system.

7
Section 1

Planning Considerations

8
Regulatory Licenses

Regulatory Licensing Considerations help to determine the number of frequency

licenses required for a Capacity Max system:
• Capacity Max Control Channel normally requires an exclusive use license for a
frequency pair.
• If you have an exclusive license, the downlink to the Control Channel will transmit
continuously.
• Optimum performance for features like call grant or roaming is achieved when
using an exclusive license.
• As of MOTOTRBO Release 2.9, an option for a Shared Frequency Control
Channel is available if you do not have an exclusive license.
• As many as four repeaters per site may be designated as control channel
capable.

9
Motorola Solutions Licensing Considerations

• A Capacity Max system requires at least one CMSS. A Capacity Max System
Server comes pre-installed with the Trunking Controller, the MNIS VRC Gateway,
and the System Advisor server. All these components must be licensed individually
to function.
• Each RF site in the system requires a Capacity Max Site License to enable it to
attach to the system. Each CMSS (primary or backup) that hosts the Trunking
Controller requires the appropriate number of Capacity Max Site Licenses.
• Many additional features may also require licenses to function. For more details
on MOTOTRO licensing requirements, please refer to the MOTOTRBO System
Planner.

10
Single Site Considerations
Site Considerations include the following:
• Capacity Max systems support 15 trunked
repeaters and 6 data revert repeaters per site.
• Each repeater may have a backup repeater.
• Normally, site frequencies must be in the same
RF band.
• In two RF band systems, the sites can be co-
located but must have different site IDs.
Repeater’s Device ID = 1 TX = f1 RX = f2 Color Code 1
• All frequencies must be unique with no re-use
TX = f3 RX = f4 Color Code 1
in the same site. Repeater’s Device ID = 2

• Site repeaters must have the same coverage Repeater’s Device ID = 3

TX = f5 RX = f6 Color Code 1

footprint. TX = f7 RX = f8 Color Code 1

Repeater’s Device ID = 4
• Repeater color codes must be the same within TX = f9 RX = f10 Color Code 1
a site. Repeater’s Device ID = 5

11
Multi-Site Considerations
Capacity Max Site 1 Capacity Max Site 2 Capacity Max Site 3

Device ID=1 TX=f1 RX=f2 CC=1 Device ID=1 TX=f11 RX=f12 CC=2 Device ID=1 TX=f1 RX=f2 CC=3

Device ID=2 TX=f3 RX=f4 CC=1 Device ID=2 TX=f13 RX=f14 CC=2 Device ID=2 TX=f3 RX=f4 CC=3

Device ID=3 TX=f5 RX=f6 CC=1 Device ID=3 TX=f15 RX=f16 CC=2 Device ID=3 TX=f5 RX=f6 CC=3

Device ID=4 TX=f7 RX=f8 CC=1 Device ID=4 TX=f17 RX=f18 CC=2 Device ID=4 TX=f7 RX=f8 CC=3

Device ID=5 TX=f9 RX=f10 CC=1 Device ID=5 TX=f19 RX=f20 CC=2 Device ID=5 TX=f9 RX=f10 CC=3

Circles Represent Areas Of Repeater RF Coverage

Multi-Site considerations include the following:

• Frequencies may be reused at different sites where coverage does not overlap.
• Any time a frequency is reused, different color codes must also be used.
• For call processing to function when using a fixed channel plan, all repeaters at a site must
be in the same color code.
• For multiple network sites accessed by a single SU, the sites would usually be in the same
RF band. The exception to this is the Dual Band 800/900 SU.

12
Sources of Information to Predict Usage

What are the sources of information we can use to predict usage?

In the space below, list some considerations which can help determine system
usage levels.

13
Sources of Information to Predict Usage

• Sources of Information which can be used to Predict Usage:

• Interviewing the customer
• Reviewing log files of any existing radio system
• Reviewing typical usage profiles

14
Typical Usage Profiles

• What are typical usage profiles?

• If historic call logs are not available from the customer, typical usage profiles can
be used to help product predicted usage levels for system planning purposes.
• Motorola SoIutions Engineering has done extensive research and has attempted
to create "typical" usage profiles and charts to provide guidance in determining a
prediction of typical usage levels.
• It is possible to create additional usage profiles based on customer requirement,
if there’s such a need.

15
Typical Usage Profiles

Data
Talkgroup Average Individual Average Data Total Call Weighted
Message
Call Rate Talkgroup Call Rate Individual Message Rate (call Average
Call Rate
Profile Name (Call per Call (call per Call Call per user Call
(call per
user per Duration user per Duration Duration per hour) Duration
user per
hour) (seconds) hour) (seconds) (seconds) (seconds)
hour)
High Voice
2.7 10 0.3 20 3 11
User
Low Voice
0.9 10 0.1 20 1 11
User
High Text
2.5 1.5 2.5 1.5
User
Low Text
0.5 1.5 0.5 1.5
User
High Voice
2.7 10 0.3 20 2.5 1.5 5.5 6.68
and Text User
Low Voice
0.9 10 0.1 20 0.5 1.5 1.5 7.83
and Text User

16
Determining the Quantity and Location of Physical RF Sites

Site selection for RF sites can vary depending on whether the system is:

• A new system.
• An update to an existing system.
• Constrained by requirements from the customer.

Predicting coverage for an RF site can be complicated.

Use your preferred RF propagation model or RF prediction software to help.

17
Determining the Quantity and Location of Non-RF Sites

Non-RF Site selection can vary depending on:

• Required physical location of the CMSS, console,

and data applications.
• User access and operational needs.
• The setup and/or configuration of the IP network.

18
Examples of System Topologies

• Co-located RF Sites • Co-located Core/RF Site

– Two RF sites sharing same router – RF and Core Site sharing same
router
Site 1 Site 2
Repeater
Repeater Repeater Repeater

CMSS Repeater Repeater Repeater

Repeater

Repeater Repeater CMSS Repeater

Repeater
Switch
Switch Switch
Switch
Router
Router Router
Router

Internet
Internet

• Private Network Connectivity

19
System Resilience Considerations

Capacity Max systems support redundancy option for the following:

• Repeaters
• 15 Voice and 15 Data Gateways
• 5 System Advisor Servers
• Trunking controller redundancy

Note: For more detailed information on Capacity Max system redundancy options,
please refer to the MOTOTRBO System Planner.

20
Trunking Controller Resilience

In the event of a Trunking Controller failure in a Capacity Max system with

redundancy:
• The redundant Trunking Controller can assume control without required re-
registration of subscribers.
• Redundant Trunking Controllers can quickly build a registration database and
recover network elements.
• Capacity Max systems support up to 5 trunking controllers but only 1 will be
active at any given time and the others will act as redundant units.

21
Choosing the Number of Trunked Repeaters

This chart shows the number of repeaters required at a site to achieve less than
3% blocking at a site for various values of the average weighted call duration for
the site and the total inbound call rate (over the air plus the over the wire) for the
site.
Number of Required Repeaters versus Call Rate versus Call Duration

Average Weighted
Number of Repeaters

Call Duration for

the Site
30 Second Call Duration
20 Second Call Duration
15 Second Call Duration
10 Second Call Duration
7 Second Call Duration
5 Second Call Duration
4 Second Call Duration
3 Second Call Duration
2 Second Call Duration
1 Second Call Duration

Total Call Rate for the Site (calls per hour)

22
Enhanced GPS Revert (1/2)

Enhanced GPS (EGPS) Revert Channel with IP Data

The table below illustrates the number of updates per minute a time slot supports
for various Periodic Window Reservation and Window Size settings.

Number of EGPS Revert channels required at a site for IP Data use:

(Location Radios) * (avg. location updates/minute) / (appropriate chart value)

% Periodic Radio to Server IP Data Messages/Minute/Site

Window
Window Window Window Window Window Window
Reservation
=5 =6 =7 =8 =9 = 10
90% 180 150 128 112 100 90
75% 150 125 107 93 83 75
60% 120 100 86 75 66 60
45% 90 75 64 56 50 45

23
Enhanced GPS Revert (2/2)

Enhanced GPS (EGPS) Revert Channel with High Efficiency Data

The table below illustrates the number of updates per minute a time slot supports
for various Periodic Window Reservation and Window Size settings.

Number of EGPS Revert channels required at a site for High Efficiency Data use:
(Location Radios) * (avg. location updates/minute) / (appropriate chart value)

Radio to Server IP Data

% Periodic Window Messages/Minute/Site
Reservation
Window = 1 Window = 2
90% 900 450
75% 750 375
60% 600 300
45% 450 225

24
MOTOTRBO System Design Tools: Capacity Max

• A set of tools to help you plan the estimates for the needed infrastructure in your
Capacity Max system.
• The tools have the ability to Save/Load your estimates.

25
Workbook Activity

Download and Launch the Capacity Max System Design Tool

Instructor Demo:

• Capacity Max System Capacity Estimator

• Capacity Max Site Link Bandwidth Calculator
• Capacity Max VRC Gateways and License Calculator

Refer to the Lab Guide

26
Section 2

RF Channel Plan

27
What is a Channel Plan?

• The DMR trunking protocol uses an identifier to represent a pair of transmit and
receive frequencies.
• The DMR trunking protocol also uses a number between 1 and 4094 inclusive to
represent a channel or Channel ID.
• This one-to-one mapping between channel number and frequency pair is called a
Channel Plan.

28
What information is used in a Channel Plan?

• Channel Numbers
• Transmit and Receive Frequencies
• Radio Identifiers (IDs)
• Talkgroup Identifiers
• Device Identifiers
• Site IDs

We will review each of these items in more detail shortly.

29
Types of Channel Plan

There are two types of Channel Plan for Capacity Max systems:

• Fixed plan where a channel number is mapped to absolute transmit/receive

frequencies.
• Flexible plan provides a more dynamic option when you may need to map
channels to different transmit/receive frequencies in your Capacity Max system.

We’ll look at examples of when it is best to use the two different types of channel
plan later in this section.

30
Radio Identifiers (IDs)

• Each radio in the system, as well as each data gateway and each console
position when deployed, is required to have a unique Motorola SolutionsD/Radio
ID.
(Motorola SolutionsD = Mobile Subscriber ID)
• Capacity Max supports the DMR defined Mobile Subscriber Identifier (Radio ID)
addressing range as defined below.
– 00000116 – FFFCDF16 (1 – 16,776,415)
• Recommendation in the installation for the radio ID for data and voice:
– The MNIS Data Gateway should be configured with a Radio ID from 3000000
to 3999999. The voice console be configured with a Radio ID from 4000000
to 4999999.

31
Talkgroup Identifiers (TGID)

DMR Talk Group Identifier

• 1 – 16,776,415 (00000116 – FFFCDF16)
• Site All Call ID: 16,777,213 (FFFFFD16)
• Multi-Site All Call ID: 16,777,214 (FFFFFE16)
• System-Wide All Call ID: FFFFFF
• Multiple-Multi Site All Call: FFFF60 – FFFFDF (128 IDs)

Short Talk Group Identifier

• 1 – 1020 (00000116 – 0003FC16)
• Reduces message latency and improves signaling efficiency

32
Device Identifiers

Infrastructure devices need a device ID which is unique to the site to which it

belongs.
• The range of device ID for a repeater is 1 to 21. It is highly recommended to
number sequentially.
• For redundant repeaters, the Device ID of the primary and the redundant
repeaters should be same and their Redundancy Group ID should be different.
• For other devices (CMSS, MNIS Data Gateway, RMDP) the Device ID must be
unique, but it may duplicate with repeaters. The range of device ID for these
devices is 1 to 63.
• It is recommended that the primary CMSS be configured with a Device ID of 1
and the alternate CMSS be configured with a Device ID of 2 to 4.
Note: Capacity Max can support up to four alternate CMSS boxes with a trunking
controller.
• The Trunking Controllers that reside on the CMSSs acquire their Device ID and
Redundancy Group ID from the CMSS configuration.

33
Creating a Fixed Channel Plan for Capacity Max

• Used to map a Channel Number into absolute transmit/receive frequencies of a

radio:
FMS_Tx = Fbase + ((CHAN - MIN_CHAN_Num) x (Fseparation/1000))

• Where:
– FMS_Tx: absolute transmit frequency of a radio, in MHz
– FMS_Rx: FMS_Tx + Fduplexsplit
– CHAN: Channel Number, between 1 to 4094 (inclusive)
– MIN_CHAN_Num: Minimum Channel Number is the minimum values of the Channel
Number
– Fseparation: Channel Separation (or spacing), (12.5 KHz or 25 KHz)
– Fduplexsplit: Duplex Split or the difference (positive or negative number) of the receive
frequency from the transmit frequency, (-50 MHz to 0 MHz to 50 MHz in 2.5 KHz steps)
– Fbase: Base TX frequency in MHz

34
Fixed Channel Plan Example

Example 1 Multiband Radio:

• Tx ranges:
– 800 MHz Band: 806–824 MHz
– 900 MHz Band: 896–901 MHz
• Channel Separation:
– 800 MHz Band: 12.5 kHz
– 900 MHz Band: 12.5 kHz
• Duplex Split:
– 800 MHz Band: 45 MHz
– 900 MHz Band: 39 MHz

Base Channel Duplex

Number of
Segment Radios Tx Frequency range Frequency Separation Split
channels
(In MHz) (In KHz) (In MHz)
1 (806 0125, 823 9875) N1 = 1440 806 12.5 45

2 (896 0125, 900 9875) N2 = 400 896 12.5 39

35
Creating a Flexible Channel Plan for Capacity Max

• Used in the following scenarios:

– The mapping requires more than four segments.
– One or more frequency pairs are beyond the range of frequency pairs
covered by all the four segments.
– One or more frequency pairs are within the range of segments but cannot be
mapped by them.
Note:
• Any Channel Number not used by a frequency in the system can be used for the
Flexible Channel Plan.
• Combinations of Fixed and Flexible Mapping is supported.

36
Section 3

Networking Requirements

37
Physical Location Requirements for a Capacity Max System

• Each physical site requires an Ethernet switch and a router.

• If your system is using a Public ISP, a modem connected to an Internet Service
Provider (ISP) is required.
• If your system is using a Private Enterprise network, the appropriate IP based
microwave, leased line or fiber equipment will be required.

Motorola SoIutions-Recommended Router

Motorola SoIutions-Recommended Switch

38
Motorola Solutions-Recommended Equipment

• Motorola Solutions Recommended Equipment for Capacity Max Systems

• The switches and routers which Motorola Solutions currently recommends for
Capacity Max systems are manufactured by HPE and Juniper.
• Motorola Solutions provides a “Network Quick Setup Reference Guide” for a
number of the most common system configurations and recommend IP plans.

Motorola SoIutions-Recommended Router

Motorola SoIutions-Recommended Switch

39
Replicator

• Any CMSS with a Trunking Controller has replicator functionality.

• There is one replicator active in a system at a time.
• No license required.
• Used (on a as needed basis) when:
– Talkgroup Call requires 16 or more sites.
– Individual voice calls or Talkgroup calls to 3 or more sites where at least 1 site
is configured for centralized distribution.
• Reduces link bandwidth requirements at centralized distribution site.
• It increases bandwidth requirements at the site with the replicator.
• Supports up to 400 simultaneous talkpaths.

40
Site Bandwidth Requirements

There are a number of factors that determine the bandwidth requirements for a site.
These include:

• The number of trunked repeaters at the site.

• The number of data revert repeaters at the site.
• The average number of other repeaters sites associated with talkgroup calls.
• The number of hardware redundant repeaters located at the site.
• The number of System Advisors Servers/Clients present at the site.
• The number of VRC Gateways present at the site.
• The number of Data Gateways present at the site.
• The number of RM clients present at the site.
• The use of a centralized distribution site.

41
Inter-Site Bandwidth Requirements

Bandwidth requirements for any given system are primarily determined by the
following:
• The number of voice slots at the site(s).
• The number of data revert slots at the site(s).
• Total number of trunked sites.
• Type and technology of the network.
• Use of VPN tunneling protocols.
• Physical Network location(s).
• Location and quantity of CMSS, VRC Gateways, Data Gateways, and System
Advisor servers.
• Use of third party systems that monitor airtime and system usage.

42
Site Link Bandwidth Requirements

Use the calculator to calculate bandwidth requirements.

43
Type/Level of Secure Virtual Private Network (VPN) and
Bandwidth Requirements Impacts
• Site link bandwidth requirements are impacted based on whether or not VPN is
used.
• The baseline requirements assume GRE (Generic Routing Encapsulation)
tunneling without security.
• Absence of tunneling decreases the baseline by 12%, but is not recommended.
– Complicates inter-site configuration.
– Invalidates recommended IP Plans.
• GRE IPsec AH and ESP is not recommended due to large bandwidth impact
(+40%) and is largely unnecessary due to high level of security provided by using
IPsec ESP(Encapsulating Security Payload) without AH (Authentication Header).
Tunnel Type Data Integrity Sender Replay Confidentiality Site Link Bandwidth
Protection Authentication Prevention Protection Impact
No Tunneling NO NO NO NO Baseline -12%
GRE Tunneling NO NO NO NO Baseline
GRE w/IPsec AH YES YES YES NO Baseline +25%
GRE w/IPsec ESP YES YES YES YES Baseline +30%
GRE w/IPsec AH and ESP YES YES YES YES Baseline +40%

44
Workbook Activity

Planning and Designing a Capacity Max System

• Draco Motors Customer Use Case/Profile

• Small Group Discussion – Customer Interview Questions
• Determine the number of repeaters per site for Draco Motors
• Practice using the System Design Tool
• Team Activity – Create a Fleetmap for your system

Refer to the Lab Guide

45
End of Module
You should now be able to:​
• Develop an awareness of regulatory licensing requirements.

• Understand Motorola Solutions licensing for Capacity Max products.

• Be able to successfully use the MOTOTRBO System Designer Tool as part of the
design process for a Capacity Max system.

• Determine the appropriate system topology.

• Complete a basic fleetmap.

• Determine the infrastructure device ID map.

• Develop a channel plan.

• Understand the networking equipment requirements for a Capacity

Max system.

46