# ERP Named vs Concurrent User Licence Calculator

> Source: https://netray.co/tools/erp-named-vs-concurrent-user-licence-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Compare the annual cost of named full and limited users with a concurrent licence pool and see the break-even concurrency level.

## Category

erp-migration

## Region

Europe

## Audience

- IT manager
- Procurement
- ERP administrator

## Tool

**Kind:** calculator

**Currency:** EUR 

**Inputs:**

#### Named full users

**Key:** full

**Type:** number

**Default:** 45

**Min:** 0

**Step:** 1

**Unit:** users

#### Named limited or self-service users

**Key:** limited

**Type:** number

**Default:** 60

**Min:** 0

**Step:** 1

**Unit:** users

**Help:** Shop floor entry, approvals, time booking, read-only.

#### Full user price per month

**Key:** full_price

**Type:** number

**Default:** 135

**Min:** 0

**Step:** 5

**Unit:** EUR

#### Limited user price per month

**Key:** lim_price

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 1

**Unit:** EUR

#### Concurrent licences needed

**Key:** conc

**Type:** number

**Default:** 55

**Min:** 0

**Step:** 1

**Unit:** sessions

**Help:** Peak simultaneous sessions from login logs.

#### Concurrent licence price per month

**Key:** conc_price

**Type:** number

**Default:** 260

**Min:** 0

**Step:** 5

**Unit:** EUR

**Outputs:**

#### Named licence cost per year

**Key:** named_cost

**Expr:** (full * full_price + limited * lim_price) * 12

**Format:** currency

#### Concurrent licence cost per year

**Key:** conc_cost

**Expr:** conc * conc_price * 12

**Format:** currency

#### Annual saving with concurrent

**Key:** saving

**Expr:** named_cost - conc_cost

**Format:** currency

**Primary:** true

**Description:** Negative means the named model is cheaper.

#### Total named users

**Key:** total_users

**Expr:** full + limited

**Format:** integer

#### Break-even concurrent sessions

**Key:** breakeven

**Expr:** named_cost / (conc_price * 12)

**Format:** decimal

**Primary:** true

**Description:** Concurrent pool size at which both models cost the same.

#### Peak concurrency ratio

**Key:** ratio

**Expr:** if(gt(total_users,0), conc / total_users * 100, 0)

**Format:** percent

**Chart:**

#### Concurrent vs named annual cost by session count

**Type:** line

**X:** conc

**From:** 0

**To:** 120

**Steps:** 30

**Series:**

- conc_cost
- named_cost

**Disclaimer:** Licence metrics differ by vendor and contract. Confirm definitions of full, limited and concurrent users with your vendor before using the result in negotiation.

## Content

**Intro:** Many European mid-market ERPs offer named-user, limited-user and concurrent-user models, and the right mix depends on how people actually work. This calculator shows which model costs less for your population and where the break-even sits.

**Sections:**

#### How to use it

**Body:** Count named users by role: full users who work in the ERP all day, and limited users who book time, approve or view. Pull peak simultaneous sessions from login logs for several weeks, ideally including month-end. Enter vendor prices and compare. The chart shows how the concurrent cost climbs as the pool grows against the flat named cost.

**Bullets:**

- Use login logs, not headcount
- Include month-end and quarter-end peaks
- Separate shop floor terminals from office users
- Check whether API or integration users consume licences

#### The break-even logic

**Body:** The named model costs (full times full price plus limited times limited price) times 12. The concurrent model costs sessions times concurrent price times 12. Break-even sessions equal named annual cost divided by 12 times concurrent price. If your measured peak is below the break-even value, concurrent licensing is cheaper. A peak ratio above roughly half of total users often favours named licences.

#### Reading the result

**Body:** A positive saving means the concurrent pool wins on cost. But factor in risk: if the pool is exhausted, users are locked out at the worst time, such as an inventory count or month-end close. Add a buffer of 10 to 20 percent to the measured peak and test again. Also consider that limited licences often cover most occasional users cheaply.

#### Common mistakes

**Body:** People size concurrency from average, not peak, usage and forget scheduled jobs or integrations that hold sessions open. Another error is assuming every vendor treats shop floor terminals the same way. Some count a shared kiosk as one named user per person, others as one device.

**Cta:** If you want licence consumption analysed from your real ERP audit logs, Netray can build a read-only report of peak sessions by role.

**Faq:**

#### Which model is usually cheaper?

**Answer:** It depends on usage patterns. Large populations with low simultaneous use often favour concurrent licences, while small teams who are all logged in all day favour named licences.

#### How do I find peak concurrent sessions?

**Answer:** Export login and logout timestamps from the ERP or application server for at least a month, and count the maximum overlapping sessions in any five-minute window.

#### Do API users consume licences?

**Answer:** Often yes, or they need a separate integration licence. Check your contract, because several scheduled interfaces can quietly hold sessions.

#### Can I mix models?

**Answer:** Some vendors allow it. Enter the named part in the named fields and the rest as concurrent, then add the two costs yourself.

## Search terms

erp named user vs concurrent user, erp licence calculator, concurrent user licence cost, erp user licensing comparison, limited user erp licence, erp licence optimisation, erp licence true up

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