# ERP WAN Bandwidth Sizing Calculator for Plants and Remote Sites

> Source: https://netray.co/tools/erp-wan-bandwidth-sizing-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Estimate the circuit size a plant or branch needs for ERP sessions, report downloads, voice and replication, with burst, overhead and utilization targets.

## Category

erp-operations

## Audience

- IT manager
- Network engineer
- ERP administrator

## Tool

**Kind:** calculator

**Inputs:**

#### Concurrent ERP users at site

**Key:** users

**Type:** number

**Default:** 60

**Min:** 1

**Step:** 5

**Unit:** users

**Help:** Peak concurrent sessions, not total accounts.

#### Interactive traffic per user

**Key:** kbps

**Type:** number

**Default:** 150

**Min:** 10

**Step:** 10

**Unit:** kbps

**Help:** Thin client or web ERP is often 50 to 200 kbps. Measure your own.

#### Report and file downloads per user

**Key:** report_mb

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 5

**Unit:** MB per hour

#### Burst factor on interactive traffic

**Key:** burst

**Type:** slider

**Default:** 2

**Min:** 1

**Max:** 4

**Step:** 0.5

**Unit:** x

#### Concurrent voice or video calls

**Key:** calls

**Type:** number

**Default:** 8

**Min:** 0

**Step:** 1

**Unit:** calls

#### Backup or replication traffic in business hours

**Key:** repl

**Type:** number

**Default:** 5

**Min:** 0

**Step:** 1

**Unit:** Mbps

#### Protocol and VPN overhead

**Key:** overhead

**Type:** slider

**Default:** 20

**Min:** 0

**Max:** 50

**Step:** 5

**Unit:** %

#### Target peak link utilization

**Key:** util

**Type:** slider

**Default:** 70

**Min:** 40

**Max:** 90

**Step:** 5

**Unit:** %

**Outputs:**

#### Interactive ERP traffic

**Key:** erp_mbps

**Expr:** users * kbps / 1000

**Format:** decimal

#### Report and file traffic

**Key:** rep_mbps

**Expr:** users * report_mb * 8 / 3600

**Format:** decimal

**Description:** MB per hour converted to Mbps.

#### Peak interactive traffic

**Key:** peak_int

**Expr:** (erp_mbps + rep_mbps) * burst

**Format:** decimal

#### Voice and video

**Key:** voice_mbps

**Expr:** calls * 0.087

**Format:** decimal

**Description:** About 87 kbps per G.711 call with headers. Video needs far more.

#### Total peak demand with overhead

**Key:** total

**Expr:** (peak_int + voice_mbps + repl) * (1 + overhead / 100)

**Format:** decimal

**Primary:** true

#### Recommended circuit size

**Key:** link

**Expr:** total / (util / 100)

**Format:** decimal

**Primary:** true

**Description:** Round up to the next carrier tier in Mbps.

**Chart:**

#### Recommended circuit (Mbps) vs concurrent users

**Type:** line

**X:** users

**From:** 5

**To:** 400

**Steps:** 40

**Series:**

- link

**Disclaimer:** Planning estimate. Measure real flows with NetFlow or your firewall reports before ordering a circuit, and add latency requirements separately.

## Content

**Intro:** Plants ask carriers for bandwidth by gut feel and then blame the ERP when screens lag. Most slow sessions are latency or packet loss, but undersized circuits do cause real queueing. This calculator builds the number from users, reports, voice and replication.

**Sections:**

#### How to use it

**Body:** Enter the peak number of concurrent users at the site. For interactive traffic per user, start with 100 to 200 kbps for RDP or web ERP, then replace it with a measured figure from your firewall or NetFlow. Add the average data users pull each hour such as reports, attachments and drawings. Include concurrent calls and any backup replication that runs in the working day, then set overhead and a target peak utilization.

**Bullets:**

- Use the busiest 15 minutes, not the daily average
- Count both directions and size for the busier one
- Keep drawings, CAD and software updates out of the average

#### The method

**Body:** Interactive demand is users times kbps. Report demand converts MB per hour into Mbps using 8 bits per byte over 3,600 seconds. Their sum is multiplied by a burst factor, since people click at the same moment after a shift change. Voice and replication are added, then protocol and VPN overhead. Dividing by the utilization target leaves headroom, because queueing delay rises quickly beyond about 70 percent load.

#### Worked example

**Body:** Sixty users at 150 kbps is 9 Mbps. Reports at 40 MB per hour per user add about 5.3 Mbps. With a 2x burst the interactive peak is 28.7 Mbps. Eight calls add 0.7 Mbps and replication 5 Mbps. With 20 percent overhead the total is about 41 Mbps, and at 70 percent utilization the recommended circuit is around 59 Mbps, so a 100 Mbps tier is the sensible purchase.

#### Common mistakes

**Body:** Sizing from total employee count, forgetting that shop floor terminals and Wi-Fi scanners also generate traffic, and running full backups across the same circuit as production. Also check latency: a clean 20 ms path to a cloud ERP matters more than raw megabits. Use QoS to protect voice and ERP traffic, and schedule large transfers outside shift hours.

**Cta:** If you are weighing a cloud move or an on-prem private AI layer for the ERP, Netray can help you map which traffic must leave the plant and which can stay local.

**Faq:**

#### How much bandwidth does one ERP user need?

**Answer:** Typically 50 to 200 kbps for interactive sessions over RDP or a web client, plus bursts for reports and attachments. Heavy use of drawings or BI dashboards can add several megabits per user, so measure your own traffic.

#### Is latency or bandwidth more important for ERP?

**Answer:** For chatty client-server ERP and RDP, latency and packet loss usually matter more than raw bandwidth. Aim for low and stable round trip time. Extra bandwidth does not fix a poor path.

#### Why use a 70 percent utilization target?

**Answer:** Queueing delay and packet drops rise sharply as a link approaches saturation, and bursts will exceed the average. Designing for a peak of about 70 percent leaves room for bursts and growth.

#### Should I include backup traffic?

**Answer:** Include anything that runs during working hours. If backups or replication run overnight on a schedule, exclude them from the daytime number but check they finish inside the window.

## Search terms

erp bandwidth requirements per user, wan bandwidth calculator, how much bandwidth per erp user, branch office bandwidth sizing, remote plant erp bandwidth, bandwidth for cloud erp, internet circuit sizing calculator, rdp bandwidth per user

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json