Starting point: an isolated instance as the base model
Every InnerWeb client gets an isolated instance with its own database and its own mail system. Instances run in Docker containers, including on the client's server. This is the base model from which we start the conversation with a group: isolation is built into it by design and needs no additional steps.
The question is therefore not whether to provide isolation, but whether the group wants each plant to have it, or prefers one instance serving several plants.
What the model changes for the database
In the instance-per-plant model, each plant's database is separate. The data of people, trainings and permits of one plant do not mix with those of another, and a failure or backup concerns only that plant. With one shared instance, the data of all plants sit in one database, and permission scopes separate it.
For the group's IT team the difference in responsibility matters: in the first model a plant can have its own administrator and its own maintenance schedule, while in the second, changes touch all plants at once.
Number of databases and mail systems: group of five plants, two models
- Instance per plant
- One shared instance
What the model changes for mail
A system mail of its own means that system messages, such as guest invitations and reports, go out from the plant's own domain and do not mix with the correspondence of other plants. Recurring reports can be directed to the recipients of a given plant without the risk of addressing mistakes, because the rules of each instance are independent.
With a shared instance, mail is steered through rules and scopes, so recipient settings require more attention: the location scope and recipients are set separately for each report rule, and dispatch is idempotent, but a wrong address will still reach the wrong plant.
Integrations with access control, time and attendance and HR
InnerWeb works as an independent system complementing the client's existing systems: access control, time and attendance, HR and ERP, and on one platform it offers 18 modules. It does not manufacture or replace access readers: it receives card swipe events from the plant's access control system.
In the instance-per-plant model, each instance connects to the access control and time-and-attendance systems of its own plant. This is natural when plants have different systems. With one shared instance, a single set of event sources and a common specification for access control vendors has to be agreed, and each plant with a different system requires a separate integration into the same instance.
- Different access control and time-and-attendance systems across plants: the instance-per-plant model is simpler.
- The same access control vendor across the group: a shared instance may be sufficient.
- Common group requirements for consolidated reports: both models, different configuration effort.
- Legal or HR separateness of the plants: favours an instance per plant.
Criteria for choosing the model
Five questions help the decision: whether the plants have their own administrators, whether they use different access control and HR systems, whether the plants' data must be separated, whether the group needs one view for the board, and whether the plants are deployed at the same time. The answer to most of these questions points to the direction.
When in doubt, we recommend starting with an instance per plant for the first plant and standardizing the configuration, because carrying a standard over to further instances is simpler than later separating a shared database.
Pitfalls and final notes
The most common pitfall: configuration differences between instances grow, because each plant changes something locally. The group standard prevents this: a shared table of roles, templates and report rules, whose changes are approved by the group administrator. The second pitfall is the lack of a plan for a shared picture for the board: with separate instances, consolidated reports have to be planned from the start.
Video
Frequently asked questions
Does an instance per plant mean a separate server?
Not necessarily. Instances run in Docker containers, including on the client's server, so several instances can run on the same infrastructure.
Does a shared instance require changing the access control readers?
No. InnerWeb does not replace readers and receives swipe events from the existing access control systems.
How do you keep consistency across several instances?
Through the group standard: a shared table of roles, templates and report rules, whose changes are approved by the group administrator.
Let's choose the model for your group
We will discuss with the group's IT team whether an instance per plant or a shared one is better. Arrange an architecture talk.
Let's talk