What can be copied from the first plant to the second?
The configuration and the methodology are copied: the layout of roles, permit templates, admission matrices, approval paths, print templates, training content and the way the deployment is run. A plant that has gone through a deployment already has a proven set of settings, so the second and third plants do not start from an empty screen.
The ability to copy follows from the architecture: each client has an isolated instance. Thanks to this, the configuration can be moved without mixing the data of one plant with the data of another, and changes in one do not affect the others.
However, not everything is copied unchanged. The map and the beacons are prepared separately for each plant, because buildings, roads and the layout of the halls differ. A copy of the configuration shortens the work, but does not replace the site visit.
What has to be prepared from scratch in each plant?
Everything that depends on the place is prepared from scratch: the naming of locations, the map, the placement of beacons (if the plant uses localization), the list of gates and gatehouses and the people responsible for areas. Each plant also has its own administrators and its own gate security procedures.
The group director should expect that some settings will be deliberately changed. For example, the admission matrix for external companies is often shared, but the list of especially hazardous work depends on the production process, so in a plant with a different profile it requires a review.
- Shared across the group: templates, roles, print templates, deployment methodology, training content.
- Separate for each plant: map, location naming, beacons, gates, administrators.
- To be reviewed: especially hazardous work and admission matrices where the production profile differs.
Training time when extending a plant
How is the extension settled and what is an entry point?
An extension to the next plant of the group is charged per entry point, that is, the place where people or external companies enter the system: a gate, a gatehouse or a secretariat. With a shared server and licences, the extension does not require building infrastructure from scratch.
Such settlement is transparent for purchasing: the number of entry points can be counted, and each next plant adds further points. We show the detailed cost structure and the calculation on a separate page about the cost of an entry point in an extension.
When planning the group budget, remember that the price depends on the scope. Indicative ranges from deployments in 2025–2026 are given in the offer; the quotation is individual.
How long does the launch in the next plant take?
Launching an extension takes about 5 weeks. This is shorter than the first deployment, because the configuration is already ready and the group's team knows the system.
These 5 weeks cover the preparation of the entry point, the installation of the workstations, training and acceptance. If the plant additionally introduces localization in a hall, the time for the site visit, the layout design and the mounting of beacons is counted separately, according to the rules described in the notes on the site visit and the layout design.
What does the training in the next plant look like?
The entry point training on the day of installation covers up to 5 people and lasts about 1 hour. It is operational training for the people who will operate the workstation: gate security or secretariat staff.
Classroom training takes place on two dates, about 3 hours each, in groups of up to 12 people. Two dates make it possible to cover the working shifts without taking the whole staff off work at the same time.
Who should take part in the classroom training?
Administrators, area supervisors and the people who approve permits. A group of up to 12 people is small enough for everyone to carry out the exercise on their own device, and large enough to fit the staff of one plant into two dates.
Does each plant need a separate server?
In the extension model described in our offer, the entry points of the next plants use a shared server and licences. This means one place of maintenance and one backup policy, which simplifies the work of the group's IT.
If the group has requirements for data separation, for example because of separate companies, the data remain separated between plants, and the configuration can be copied without transferring personal data. The choice between the shared and the separated model is made by the group's IT together with its legal department.
Video
Frequently asked questions
Can the second plant start without a site visit?
An entry point without localization can start on the copied configuration. If the plant wants localization of people, a site visit and a beacon layout design are needed, because the map is separate for each plant.
Does a change in the first plant change the settings of the second?
No. Instances are isolated, so a change in one plant is not transferred automatically to the others. The configuration is copied deliberately when the group considers it a template.
How many people from the plant must be trained at the start?
At the workstation up to 5 people in about an hour, and in a classroom in groups of up to 12 people on two dates of about 3 hours each. The number of dates is matched to the working shifts of the plant.
Does the extension require new licences?
In the model described in the offer, the entry points are counted with a shared server and licences. The details depend on the scope and are included in the individual quotation.
Planning further plants in your group?
Tell us how many plants and entry points you want to cover. We will prepare an extension plan and show what we will copy and what we will do from scratch.
Let's talk