InnerWeb
Skip to main content

Rollout order for the next plants in a group

A group board that has completed a successful pilot in one plant faces the question of where to go next. A poor choice of order slows everything down, because the problems of the first plant repeat in the following ones. Below are recommendations on how to order the rollout, using the pilot as the reference point.

100%
of pilots converted into deployments
Source: InnerWeb company data, 20 deployments and pilots
18
modules on one platform
Source: InnerWeb company data

Who this order is for, and why

The recommendations are for the board or operations director of a group that has a completed pilot in one plant and must decide where the system goes next. The pilot is the reference point here: across InnerWeb's past deployments and pilots, 100% of pilots converted into deployments, out of 20 deployments and pilots, so the question is no longer whether to deploy, but in what order.

A good order follows from several objective criteria, not from the sequence of plants on the board's list. The six recommendations below organize those criteria.

Recommendation 1: first the plant most similar to the pilot

The second plant should resemble the first: similar technology, similar building structure, similar model of work by external companies. Then the location structure, permission templates and role layout from the pilot transfer without rebuilding. Every difference in the second plant is a risk, so it is worth limiting their number at this stage.

Sample wave layout for a group of five plants

Sample wave layout for a group of five plantsBar chart: 1 plant in the first wave, 2 in the second and 2 in the third.012plantsWave 1 (pilot): 1 plants1 plantsWave 1 (pilot)Wave 2 (similar): 2 plants2 plantsWave 2 (similar)Wave 3 (different): 2 plants2 plantsWave 3 (different)
Source: Sample calculation: a group of five plants, assumed split 1 + 2 + 2

Recommendation 2: choose a plant with a ready process owner

Success depends on the person who is responsible for the deployment on the plant side: the OHS or security manager with time for training and decisions. A plant with such an owner will start faster than a plant with better technical parameters but without a person to run the process.

Recommendation 3: check readiness of integrations with existing systems

InnerWeb works as an independent system complementing the client's existing systems: access control, time and attendance, HR and ERP. If the access control system in the next plant is entirely different from the first one, the integration has to be prepared separately. Plants on the same access control platform start faster, because the specification of card swipe events is the same.

It is therefore worth ordering the plants so that those with the same access control and time-and-attendance platforms go in one wave, and those with a different environment go in a separate wave, with extra time for integration.

Recommendation 4: roll out plants in waves, not all at once

The platform has 18 modules, and each module enabled requires training and the assignment of owners. Rolling out plants in waves of one or two makes it possible to carry lessons from one wave into the next: improve templates, complete instruction videos, clarify roles.

The gap between waves is worth defining as a condition, not a date: the next wave starts when the previous one has a closed list of remarks and working reports.

  • Wave 1: the pilot plant, already working as the template.
  • Wave 2: plants similar in technology and on the same access control platform.
  • Wave 3: plants with a different environment, with time for integration.
  • Each wave ends with a review: remarks, reports, roles.

Recommendation 5: build the group standard from the pilot, not from scratch

Permission templates, the role layout, report rules and the names of structure levels developed in the pilot become the group standard. Subsequent plants adapt it locally but do not create it anew. This saves time and gives the comparability between plants that the board needs.

Recommendation 6: measure the pace and quality of each wave

For each wave, set three indicators: time from start to the first consolidated report, the number of remarks closed in the first month, and the share of employees trained on time. If any of them is clearly worse than in the previous wave, stop the next wave and find the cause. A quick deployment with a growing number of open remarks costs more than a slower one that is closed out.

Example layout of three waves

A group of five plants may adopt the following layout: one pilot plant as the template, two technologically similar plants in the second wave, and two with a different environment in the third. The chart below shows this layout: the number of plants in each wave in a sample calculation.

Video

Frequently asked questions

Is it better to roll out all plants at once?

Usually not. Waves let you carry lessons from one wave to the next and limit the load of training and support.

Which plant should be the second one?

The one most similar to the pilot that has a ready process owner on the plant side.

What about plants with a different access control system?

InnerWeb receives swipe events from the plant's existing access control system, so it does not replace readers, but the integration has to be prepared separately. Such plants are worth including in a later wave.

Let's set the waves for your group

Let's talk about which plant to start with and how to carry the standard from the pilot. We will help set the order and the start conditions for each wave.

Let's talk