InnerWeb
Skip to main content

Extending the system to another site: how to do it and how to price it

A second site starts on the same platform, with a separate instance and without reinstalling. The extension is priced per entry point (5,000 PLN net), and licenses are counted together for both locations. The guide walks through the steps from the point of view of a group director who has to calculate the cost and plan the trainings.

5,000 PLN
net per entry point at the second site
600 PLN
net per month for the training module of an additional site

Architecture: shared platform, separate instance

The platform is shared, and each plant has its own instance. The system works locally without a connection to the producer or in the cloud, as the plant decides. This keeps the data of the second site separate from the data of the first, while the group director can still apply uniform rules and permit templates.

The extension does not require reinstalling the platform. A new instance is created with its own map, rules and list of external companies, and the configuration of the first site can be used as a template.

How to calculate the cost of the second site

The extension to a second site is priced per entry point: 5,000 PLN net per point. The server is shared, licenses are counted together for both locations, and the training module is billed separately for each site: 1,200 PLN net per month for the first site and 600 PLN net per month for each additional one.

In the sample pricing the extension to a second site after the pilot is 8,000 PLN, which gives the same total as ordering two sites at once (13,000 PLN plus 8,000 PLN makes 21,000 PLN). Amounts are indicative ranges from 2025-2026 deployments; individual quote.

Deployment: one site versus two sites

Deployment: one site versus two sitesBar chart: 13000 PLN for one site, 8000 PLN for the extension, 21000 PLN in total.0500010,00015,00020,00025,000PLN net1 site: 13,000 PLN net13,0001 siteExtension after the pilot: 8000 PLN net8000Extension after the pilotTotal 2 sites: 21,000 PLN net21,000Total 2 sites
Source: sample calculation; indicative ranges from 2025-2026 deployments

Shared license pool

The licenses of the second site are counted together with the licenses of the first. A shared pool of 50 licenses for two sites can be divided in a variable way, for example 35 and 15, without an annex. For the group director this means there is no need to allocate a fixed number of licenses to each site in advance, and billing follows actual use.

Example: when the first site has 35 active users and the second has 15, the package of 50 licenses covers both. When the second site grows, licenses shift within the pool.

Trainings and the start of the new site

The training of the entry point on the day of installation covers up to 5 people and takes about one hour. Classroom training is held on two dates of about 3 hours each, in groups of up to 12 people. For the second site plan the training date so that the administrators (at least two) are present at both sessions.

The payment for the deployment is split into 50% at the order and 50% after go-live, independently of the maintenance contract. As a result the group director can launch the second site without changing the terms of the first contract.

Order of actions in the group

First agree the scope of the second site: the number of entry points, external companies and the map. Then place the order for the extension, prepare the list of administrators and permit templates. After installation, run the trainings and start the first permits in a limited scope.

  • Agree the number of entry points: each costs 5,000 PLN net.
  • Place the order for the extension and keep the shared license pool.
  • Prepare the site plan, permit templates and the list of external companies.
  • Plan the entry point training (up to 5 people) and the classroom training (up to 12 people, two dates).
  • Activate the training module of the second site: 600 PLN net per month.

What the group director should standardize

Before launching the second site it is worth standardizing permit templates, role names and the rules for registering external companies. The shared platform makes it possible to compare the indicators of both sites, but only if the categories of incidents and permits are named the same way. The second site may keep local deviations where site conditions require them, for example additional zones. The shared license pool also makes it easier to move teams between sites without extra formalities, and the cost of the training module for an additional site (600 PLN net per month) is known in advance.

How to assess the effect after 90 days

Three months after the start of the second site compare three things: the number of active users against the license pool, the number of external companies registering in the system, and the time needed to handle permits. If one site consistently uses fewer than 15 licenses from the pool of 50, consider changing the billing model from the fixed package to the flexible one.

Checklist

Video

Frequently asked questions

Is the data of both sites separated?

Yes. Each site has a separate instance, so the data is kept apart, while the platform remains shared.

Does the second site need a new server?

The extension is priced on the shared server. A local or cloud deployment depends on the decision of the plant.

Do the licenses have to be divided in advance?

No. The shared pool can have a variable split without an annex.

Let us plan the next site in your group

We will prepare a quote for entry points, the shared license pool and the training module for the second location.

Let's talk