InnerWeb
Skip to main content

Shared licence pool for two plants of a group: a rollout scenario

How do you split 50 licences between two plants of one group and shift the split without an amendment? We describe the scenario from the point of view of the group security manager: what this setup costs in the first 12 months, what is shared, and what is billed separately for each plant.

72,600 PLN
first 12 months, 2 sites, 50 licences (net)
Source: price list
4,300 PLN
monthly fee after rollout (net)
Source: illustrative calculation
5,000 PLN
price of the entry point when extending (net)
Source: price list

Starting scenario: a group with two plants

We describe a concept, not the billing of a specific company. Imagine an industrial group with two plants in Poland. The group security manager is responsible for uniform rules for entry, notification of external companies and training, but each plant uses a different set of people in the system: gatehouse staff, OHS coordinators and supervisors of external companies.

The purchasing question is simple: should they buy two separate sets of licences or one pool that the group divides according to needs? The answer matters, because the needs of the plants change from month to month, for example during shutdowns, when the number of external companies and coordinators grows.

How a shared pool of 50 licences works

The fixed package is 50 licences for 2,500 PLN net per month, payable in advance. When the system is extended to a second plant, licences are counted jointly for both sites, on a shared server. The split of the pool can be flexible, for example 35 licences in one plant and 15 in the other, and it can be shifted without an amendment.

The system runs on a shared platform, and each plant has its own instance. As a result, data and permissions remain organisationally separated, while licence billing is common. The group security manager sees the full cost in one place, and plant managers administer their own accounts.

What is shared and what is separate

The server and the licence pool are shared. The training module is billed separately: 1,200 PLN net per month for the first site and 600 PLN net per month for each further one, with no limit on the number of trained people. This means the second plant adds 600 PLN per month to the bill for training, regardless of the number of trained employees, external company workers, visitors and drivers.

First 12 months cost: three configurations

First 12 months cost: three configurationsBar chart: 37,000 PLN, 52,200 PLN and 72,600 PLN net for the first 12 months in three sample configurations.020,00040,00060,00080,000PLN net1 site, 10 users: 37,000 PLN net37,0001 site, 10 users2 sites, 10 users: 52,200 PLN net52,2002 sites, 10 users2 sites, 50 licence pool: 72,600 PLN net72,6002 sites, 50 licence pool
Source: Illustrative calculation: rollout of 13,000 PLN (1 site) and 21,000 PLN (2 sites) plus 12 months of maintenance

Cost of the first 12 months

Extending to a second plant is priced as an entry point: 5,000 PLN net per point. In the sample quote, the rollout for two sites is 21,000 PLN net one-off. On top of that comes the monthly fee: the 50-licence package (2,500 PLN), the training module for the first site (1,200 PLN) and for the second (600 PLN), in total 4,300 PLN net per month.

The full cost of the first 12 months in this configuration is 72,600 PLN net, which is 21,000 PLN + 12 × 4,300 PLN. For comparison: two sites with 10 users on a flexible licence come to 52,200 PLN net (21,000 PLN + 12 × 2,600 PLN). The difference of 20,400 PLN is the price of a larger licence pool and of the certainty that the split will not limit any plant. This is an illustrative calculation, and the quote is always individual.

Shifting the split in practice

Assume the first plant has 35 licences and the second has 15. During a shutdown in the second plant the number of coordinators of external companies who must announce workers grows. The group security manager shifts the split to 25 and 25. There is no amendment, no interruption of work and no additional payment, because the total pool stays at 50.

It is worth remembering that the counter includes people working in the system on the plant side and coordinators of external companies, but not workers of external companies, drivers and visitors. The pool therefore concerns a dozen or several dozen management roles, not everyone entering the site.

Split of the 50 licence pool in two scenarios

First plant

Split of the 50 licence pool in two scenariosChart: in the regular period 35 and 15 licences, during a shutdown 25 and 25 licences between the two plants.Regular period (35): 35 licences (58.3%)Shutdown period (25): 25 licences (41.7%)60licencesRegular period (35)35 licences (58.3%)Shutdown period (25)25 licences (41.7%)

Second plant

Split of the 50 licence pool in two scenariosChart: in the regular period 35 and 15 licences, during a shutdown 25 and 25 licences between the two plants.Regular period (15): 15 licences (37.5%)Shutdown period (25): 25 licences (62.5%)40licencesRegular period (15)15 licences (37.5%)Shutdown period (25)25 licences (62.5%)
Source: Illustrative calculation on a 50-licence pool, split 35 and 15, then 25 and 25

The role of the group security manager

In this model the security manager sets the shared rules: the language of messages, permit templates and training requirements. Plants keep operational autonomy within their own instance. The first task is to define who in each plant receives a licence, and who uses the system as a visitor or as a worker of an external company without a licence.

The second task is a monthly review: how many people logged in at each plant and whether the split of the pool matches reality. When the total number of active people approaches 50, a 100-licence package at 4,000 PLN net per month should be considered.

Risks and traps of the scenario

The most common mistake is assuming that the training module is shared too. It is billed separately for each plant, so it must be entered in the budget twice, with a lower rate for the second site. The second mistake is having no owner of the pool split: when nobody is responsible for the shifts, one plant can end up holding licences it does not use.

The third trap is expecting the pool to replace separate accounts for coordinators. Every person working in the system must have their own account, and the pool only determines how many such accounts are licensed at the same time.

Video

Frequently asked questions

Does shifting licences between plants require an amendment?

No. The split of the pool, for example 35 and 15, can be changed without an amendment, as long as the total number of licences does not exceed the purchased package.

Is the training module shared by both plants?

No. It is billed separately for each site: 1,200 PLN net per month for the first and 600 PLN net for each further one, with no limit on trained people.

Does each plant have a separate server?

In the described scenario licences are counted jointly on a shared server, and the platform is shared, while each plant has its own instance.

Plan licences for your group of plants

We will prepare a quote for your group and show how to split the licence pool. Book a meeting with the InnerWeb team.

Let's talk