Does each plant get a separate instance or one shared instance?
The default InnerWeb model is an isolated instance for each client, with its own database and its own mail system. Instances run in Docker containers, including on the client's server, so a plant that needs its data kept on its own infrastructure is not an exception to the standard. For a group this means you can keep the plants separate or base them on a shared environment. The choice depends on who should see the data and where it has to be stored.
The practical difference is this: a separate instance per plant limits the effects of a failure and of permissions to one place, while a shared instance makes group reports easier. We describe the detailed comparison in our implementation notes on one instance per plant versus a shared instance. The operations director should make this decision before the second plant goes live, because changing the model later means moving data.
What do we repeat at the next plant, and what must be built from scratch?
The logic is repeatable, the geometry is local. The structure of a plant in InnerWeb has fixed levels: plot, view (division), building, line and location. Documents, audio and video recordings are assigned at each of these levels, with inheritance down the tree, and risks are assigned to a location and to a type of hazardous work. What was built once as a template can be copied to the next plant and adjusted.
What is built from scratch is the map of the specific plant: building outlines, georeferencing and transmitter placement. As a rough guide we assume one transmitter per 100-200 m2 inside buildings and about one every 100 m along plant roads. Position is calculated from the signals of several transmitters and averaged on the map, and the system works without GPS. In the planning example in the chart below we assumed that about 60 percent of configuration work is repeatable and 40 percent is local. This is an illustrative assumption, not a measurement from a specific plant.
Sample split of configuration work at the next plant
How does the system work together with the group's existing systems?
InnerWeb is an independent system that complements the systems a group already has: access control, time and attendance, HR and ERP. It offers 18 modules on one platform, so you can start with a single area, for example hazardous work permits, and add others later. We do not replace access control readers or sell cards. The system receives check-in events from the existing access control system and links them with qualifications, permits and attendance.
For a group in which each plant uses a different access control vendor, this is an important point. The integration is based on events from existing systems, so a plant does not have to standardise its hardware to join the common safety standard.
What is the risk of extending the rollout, and does the pilot remove it?
In past implementations and pilots InnerWeb records a 100 percent conversion of pilots into full deployments, across 20 implementations and pilots. This is the company's statistic, not a guarantee for a specific plant. It should be read as evidence that a pilot gives a reliable picture, not as a promise.
The real risks of an extension lie elsewhere: inconsistent names and structures of locations between plants, non-uniform roles, and underestimated work on the map. A shared standard prepared before the second plant goes live addresses the first two, and a site survey carried out in advance addresses the third.
Who manages permissions across the group?
Permissions follow from roles with inheritance, a scope matrix and a ladder for granting roles. The most important rule for a group is this: no one can grant a role higher than their own. A plant administrator therefore cannot hand out permissions above their level, and headquarters keeps control over high-level roles. We describe the recommended role layout for a group separately, in our recommendations on roles and permissions across a group of plants.
How do you check that the extension has worked?
The simplest way is to compare the plants using the same measures. The same BHP checklist can be run at many sites, and the results are comparable between sites and periods. Periodic reports are configured separately for each product (permits, employees, notifications, training, deliveries) with a daily, weekly or monthly cadence, and are sent by email with a PDF attachment and optionally an XLSX. In this way the operations director receives the same summaries from every plant without assembling them by hand.
Video
Frequently asked questions
Does the second plant have to have the same structure as the first?
It does not have to, but it is worth keeping the same levels (view, building, line, location) and consistent names. Then checklists, risks and reports work the same way and the results are comparable.
Can we start with one module and add more later?
Yes. The platform has 18 modules, so a plant can start with hazardous work permits, for example, and widen the scope as its staff become ready.
Does the next plant have to change its access control vendor?
No. InnerWeb integrates with the existing access control system and receives its check-in events, without replacing readers or cards.
When should the instance model be decided?
Before the second plant goes live. Changing the model after deployment means moving data and setting permissions again.
Planning to extend the system to more plants?
Let's talk about the group standard and the order of go-lives. We will prepare a rollout plan matched to your plants.
Let's talk