TRBOnet Enterprise Server or TRBOnet Agent
Voice Channels	4	8	16	24	24+
CPU	Intel Core i5	Intel Core i5	Intel Core i7, 4 Cores	Intel Core i7, 6 Cores	For calculations, see the Server PC requirements section below
Memory	2 GB	4 GB	4 GB	8 GB
HDD	2 GB for installation files, +1 MB per 1 minute of voice recording (see Server requirements part for more info on audio format save options)
Sound Card	No
Supported OS	See TRBOnet.Enterprise Compatibility Table
Software
SQL	MS SQL Server 2016 and higher Standard or Express editions
Note!	Firmware version for repeaters from R01.08.10 or later

TRBOnet Enterprise Server or TRBOnet Agent with Control Stations
Control Stations	1	2+
CPU	Intel Core i5
Memory	2 GB
HDD	2 GB for installation files, +1 MB per 1 minute of voice recording
Sound Card	An Integrated sound card can be used, and if used, ensure that there is a good ground connection for the PC, otherwise the audio may be 'noisy'. A Sound Card with an equalizer (better than built-in Windows equalizer) allows tuning the audio for each particular dispatcher	Multi-channel Sound Card required. Recommended: Roland OCTA CAPTURE Hi-SPEED USB Audio Capture M-Audio Delta 1010 LT Note: Sound cards were not tested for compatibility with Windows Server OS and may be not compatible. Please contact Microsoft or Manufacturer support for compatibility information
Additional Devices	Cable connector Motorola PMKN4016
Supported OS	See TRBOnet.Enterprise Compatibility Table MOTOTRBO CPS with drivers
Software
Note!	Firmware version for Mobile radios: MOTOTRBO 1st generation Control Stations: from R01.08.32 or later MOTOTRBO 2nd generation Control Stations: from R02.20.01 or later It is recommended to use a display radio (DM 3600/3601/4600/4601, XPR 4500/4550/5500/5550) as a master radio in order to receive EMERGENCY CALL.

TRBOnet Dispatch Console
CPU	Intel Core i5
Memory	4 GB
HDD	2 GB for installation files
Sound Card	Yes
Display	1600x900 minimal resolution, 1920x1080 and higher resolution recommended
Additional Devices	Speakers and microphone or headset. Imtradex devices are recommended.
Supported OS	See TRBOnet.Enterprise Compatibility Table
Software	.NET Framework 4.8

TRBOnet Enterprise Server or TRBOnet Agent (before 6.0)
Voice Channels	4	8	16	24	24+
CPU	Intel Core i5	Intel Core i5	Intel Core i7, 4 Cores	Intel Core i7, 6 Cores	For calculations, see the Server PC requirements section below
Memory	2 GB	4 GB	4 GB	8 GB
HDD	1GB for installation files, +1 MB per 1 minute of voice recording
Sound Card	No
Supported OS	See TRBOnet.Enterprise Compatibility Table
Software
SQL	MS SQL Server 2008R2 and higher Standard or Express editions
Note!	Firmware version for repeaters from R01.08.10 or later

TRBOnet Enterprise Server or TRBOnet Agent with Control Stations (before 6.0)
Control Stations	1	2+
CPU	Intel Core i5
Memory	2 GB
HDD	1 GB for installation files, +1 MB per 1 minute of voice recording
Sound Card	An Integrated sound card can be used, and if used, ensure that there is a good ground connection for the PC, otherwise the audio may be 'noisy'. A Sound Card with an equalizer (better than built-in Windows equalizer) allows tuning the audio for each particular dispatcher	Multi-channel Sound Card required. Recommended: Roland OCTA CAPTURE Hi-SPEED USB Audio Capture M-Audio Delta 1010 LT Note: Sound cards were not tested for compatibility with Windows Server OS and may be not compatible. Please contact Microsoft or Manufacturer support for compatibility information
Additional Devices	Cable connector Motorola PMKN4016
Supported OS	See TRBOnet.Enterprise Compatibility Table MOTOTRBO CPS with drivers
Software
Note!	Firmware version for Mobile radios: MOTOTRBO 1st generation Control Stations: from R01.08.32 or later MOTOTRBO 2nd generation Control Stations: from R02.20.01 or later It is recommended to use a display radio (DM 3600/3601/4600/4601, XPR 4500/4550/5500/5550) as a master radio in order to receive EMERGENCY CALL.

TRBOnet Dispatch Console (before 6.0)
CPU	Intel Core i5
Memory	4 GB
HDD	600 MB for installation files
Sound Card	Yes
Display	1280x1024 minimal resolution, 1600x900 recommended resolution
Additional Devices	Speakers and microphone or headset. Imtradex and Buddy DesktopMic 7G devices are recommended.
Supported OS	See TRBOnet.Enterprise Compatibility Table
Software	.NET Framework 4.0

TRBOnet Map Server
CPU	x64 compatible 1.4 Ghz minimum, 2.0 Ghz and higher recommended Examples: (AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support).
Memory	Depending on MSSQL Server installed. SLQ Express 512 Mb, other versions 1Gb, Recommended 1 Gb. For MSSQL Standard, not less than 4Gb required with gradual RAM increasing due to Database size increase over time.
HDD	10Mb for installation files + Data storage 200 Gb
Supported OS	Windows 7/8.x/10/2012/2016/2019
Software	.NET Framework 4.6.2
Internet connection	Required for address to coordinates translation, map tiles download and update

Server PC requirements

TRBOnet can handle up to 4 simultaneous voice sessions per one CPU Thread.
For example, to handle 48 simultaneous calls you will require 48/4 = 12 CPU threads = 6 Cores.
Usually in the case of a large system with 24+ voice sessions, the requirements are:
1.      CPU – calculated by the formula above
2.      RAM (Memory): 

16 GB for cases with 25 to 50 channels (paths), 32 GB for the case where virtual machines are used on the physical server .

For bigger systems the following calculation is applied:

• Recommended RAM per CORE (min / average) is 2GB / 4GB per core;
• TRBOnet requires 1 core (2 threads) per 8 audio paths;
  

Example calculation for cases with 100 audio channels (paths):

• Minimum = 100 / 8 * 2 = 25GB;
• Average = 100 / 8 * 4 = 50GB;

3.      2xHDD 500GB in RAID 1 – for windows installation
4.      2xHDD 1TB in RAID 1 – for audio storage & database archives.

For Audio size storage calculation:

• WAV (default) - up to 1Mb for 1 minute voice record.
• TNA (proprietary, can be played in TRBOnet only, contains metadata) up to 1Mb.
• OGG (available in 6.0 and newer) - up to 100Kb for 1 minute voice record.

An example of MSSQL Server Database size calculation

24 channels busy system with 700 radios generates:
Database – 3 GB per month (a large amount of GPS data)
For audio recordings storage, 1 min = 1 Mb.

You may use Microsoft SQL Express (it is free of charge) but it has a 10 GB Database size limit. If calculations result in a data size that is more than 10 GB and all data needs to be immediately accessible, then consider using a full (non-Express) version of the SQL server.

IP Backend Network Performance Requirements

Before planning any IP connected MOTOTRBO systems please check System Planner (chapter “4.9.3. Considerations for the Back-End Network in IP Site Connect Mode”)

• Delay/Latency is characterized as the amount of time it takes for voice to leave the source repeater and reach the destination repeater. Delay should be less than 60 ms. It can be up to 90 ms, but requires changes in CPS for subscriber units and for repeaters..
• Jitter is the variation of packet inter-arrival time. It should be less than 60 ms.
• Packet Loss. In the case of voice, the ongoing call ends if six consecutive packets do not arrive within 60 ms. of their expected arrival time. In the case of data, the repeater waits for the expected number of packets (as per the data header) before ending the call.
• Bandwidth. Refer to System Planner for bandwidth calculations, but roughly, it requires 96 Kbps for each repeater connection and should be summarized for all repeaters.

If the IP backend network does not satisfy MOTOTRBO requirements, it will degrade audio quality significantly to a point where there could be dropped voice calls.

TRBOnet Enterprise Network Performance Requirements (TRBOnet 5.2.5.1427 and higher)

Note. All delay values are to be considered as "round-trip delay time” (RTD).
It should be considered that every hop (that occurs at the process of network packets delivery) also takes 1-2 ms.

1. TRBOnet Server – Dispatch Console connection

1.1. IP Connection Network performance requirements:

Delay < 2900 ms
Jitter < 50 ms
Packet loss < 2%


1.2. From Dispatch console to Server:

Bandwidth calculations are based on the number of Dispatch Consoles.
Each connection requires 128 Kbps for voice and 66 Kbps for data


1.3. From server to dispatch console:

a) Voice traffic:

Bandwidth calculations are based on the number of Voice sessions and the type of Codec used:
Bandwidth_Voice = X * N
Where X is the number of connected systems (simultaneous voice sessions) to the server
N is the bit rate for the type of Codec used.

CODEC	Bit Rate (Kbps)
G.711 µ-Law/8000	64
G.711 A-Law/8000	64
G.729/8000	8
SPEEX/8000	8
SPEEX/16000	16
AMR/8000	4.75-12.2
AMR/16000	6.60-23.85
AMBE/8000	2-9.6
OPUS/8000	20
OPUS/16000	6-128
PCM/8000	128
PCM/16000	256
PCM/22050	352
PCM/44100	705

NOTE: for LCP/Cap+ systems, each audio path added at the server is considered as one system.

b) Data traffic:

Bandwidth calculations are based on the number of Subscriber Units (radios)
The requirement is 64 Kbps for 300 Subscriber Units and 128 Kbps for 600 Subscriber Units.
Bandwidth_Data = (SU / 300) * 64 Kbps
Where SU is the number of radios in the system.

Final Bandwidth formula = (Traffic for Voice + Traffic for Data) * Number of Dispatch Consoles

2. TRBOnet Server in fail-operational capability mode (Redundancy mode)

Delay < 1500 ms
Jitter < 100 ms
Packet loss < 2%

Bandwidth calculations are based on the number of systems connected to the Remote Agent/Server and the type of Codec used (See above).
Bandwidth = X * (N + Data)
Where X is the number of systems connected to the remote agent/server (simultaneous voice sessions) 
N is the bit rate for the type of Codec used.
Data is 50 Kbps average


Calculation example for Default PCM/8000:

Bandwidth = X * (N + Data)
Where X is the number of Dispatch consoles connected to Server
N is the bit rate for the type of Codec used (in this example PCM/8000 = 128 Kbps) Data = Maximum Data traffic between Server and Console = 66 Kbps
Bandwidth for single connected console (outgoing\uplink)  = 1 * (128 Kbps + 66 Kbps) = 194 Kbps
For 1 console receiving 40 simultaneous calls (max simultaneous voice sessions) * 128 Kbps + 66 Kbps = 5,186 Kbps = approximately 5 Mbps 
40 Consoles receiving 40 simultaneous calls =  5,186 Kbps * 40 = 207,440 Kbps = approximately 202,5 Mbps

Calculation example for customized Audio3.config with OPUS/8000:
Bandwidth = X * (N + Data)
Where X is the number of Dispatch consoles connected to Server
N is the bit rate for the type of Codec used (in this example PCM/8000 = 20 Kbps)
Data = Maximum Data traffic between Server and Console = 66 Kbps
Bandwidth for single connected console (outgoing\uplink)  = 1 * (20 Kbps + 66 Kbps) = 86 Kbps
For 1 console receiving 40 simultaneous calls (max simultaneous voice sessions) * 20 Kbps + 66 Kbps = 866 Kbps
40 Consoles receiving 40 simultaneous calls =  866 Kbps * 40 = 34,640 Kbps = approximately 33,8  Mbps


3. TRBOnet Server – Remote Server and Remote Agent

Delay < 2900 ms
Jitter < 50 ms
Packet loss < 2%

4. TRBOnet Server – Friendly Server

Bandwidth calculations are based on the number of dispatcher connections.
Each connection requires 128 Kbps for voice and approx. 50 Kbps for data;
For example, for 5 dispatchers, Bandwidth = 5 * (128+50) = 5 * 178 Kbps

Swift Agent <-> TRBOnet Enterprise Network Performance Requirements Swift Agent A001/A002
Maximum latency < 300 ms
Jitter < 60 ms
Packet loss < 1%
Bandwidth 160 Kbps which are used exclusively by Swift Agent

Swift Agent A100/A200
Firmware R03.XX:
Delay < 1800 ms Jitter < 400 ms
Packet loss < 2%

Firmware R04.XX:
Delay < 3000 ms
Jitter < 1200 ms
Packet loss < 2%

Mobile Client <-> TRBOnet Enterprise 5.2.5 Network Performance Requirements:

Delay < 200 ms
Jitter < 100 ms
Packet loss < 2%
Reordering < 2% (not being summarized with the packet loss requirement, both parameters should be < 2%)

Bandwidth = N*5 +- 5Kbps.
N is the bit rate for the type of Codec used.

Mobile Client <-> TRBOnet Enterprise 5.3.5 or higher Network Performance Requirements:

Delay < 800 ms
Jitter < 100 ms
Packet loss < 3%

Mobile Client <-> TRBOnet Enterprise 5.7 and newer Network Performance Requirements:

Delay < 2900 ms
Jitter < 50 ms
Packet loss < 2%