EpicorFree calculatorPDF, Excel, Word exportEpicor Kinetic

Epicor Concurrent License Sizing Calculator

How many concurrent licenses do you really need? If each person is logged in a fraction of the time, the number online at once is predictable. This calculator uses a binomial model with a normal approximation to size licenses for a chosen confidence level and compares the annual cost with named users.

Your numbers

users
35 %

Take from login history during your busiest hour.

$ per year

Enter your quoted figure. Prices vary by contract.

$ per year

Enter your quoted figure.

Your results

Concurrent licenses needed
63
Normal approximation of the binomial, capped at total users.
Concurrent minus named
-$4,500
Negative means concurrent is cheaper at these prices.
Peak probability per user
0.35
Expected concurrent users
52.5
Standard deviation
5.8417
Concurrent license cost
$220,500
Named license cost
$225,000

Statistical planning aid, not a licensing opinion. Epicor license terms, metrics and prices are set by your contract. Confirm with Epicor or your reseller.

Save results:

Concurrent licenses needed vs total users

Sweeps Total users who need access from 10 to 500, holding your other inputs fixed.

License usage analysis

Optional: we can analyse real login data from your ERP to right-size your licenses.

Optional. The tool and every export work without this. No spam.

How to use it

Enter the total number of people who need access and the chance any one of them is logged in at your busiest hour. Take that figure from login history rather than guesswork. Choose a confidence level, and enter the prices from your own quote for concurrent and named licenses. The tool returns licenses needed, the cost of each model and the difference.

  • Include occasional users such as managers and auditors in the user count.
  • Use peak-hour login data, not a daily average.
  • Check whether your contract counts sessions, modules or device types separately.

The model

If each of N users is online with probability p, the number online follows a binomial distribution with mean N times p and standard deviation the square root of N times p times one minus p. We approximate with a normal curve and add the z score for your confidence level times the standard deviation to the mean. The result is rounded up and capped at the total user count.

Reading the chart

The licenses line rises more slowly than the user count because larger pools smooth out peaks, so the cushion above the mean shrinks relative to size. Small teams need proportionally more headroom. If your concurrency probability is close to 100 percent, concurrent licensing saves nothing and named users are usually simpler.

Common mistakes

Teams use average concurrency instead of peak, forget shift overlap, month-end spikes and integration or API sessions, and ignore that people leave sessions open all day. Idle sessions inflate concurrency, so a timeout policy can reduce licenses needed. Re-run the sizing at renewal with fresh login data.

Frequently Asked Questions

Is the result a guarantee I will never hit the limit?

No. It is a probability at your chosen confidence level, based on the assumptions you enter. Unusual events such as an unplanned all-hands entry day can still exceed it.

How do I estimate peak concurrency?

Export session or login history from your system and count simultaneous sessions in the busiest hours, then divide by total users. Use several weeks, including month-end, to avoid underestimating.

Are API or integration sessions included?

That depends on your license terms. Some integration access may consume licenses or need specific types. Check your agreement and add any such sessions to the user count if they apply.

When are named users better?

When most users are online most of the day, or when a named price is low relative to the concurrent price. The comparison output shows the break-even at your quoted prices.

Netray can pull login and usage data from your ERP to ground this analysis. The calculator itself needs no contact.