InnerWeb
Skip to main content

Group Plant Pilot: Step-by-Step Guide

A pilot at a Polish plant of a foreign group starts with head office approval and ends with settings in the system. This guide sets the order: what to prepare in documents, which access to order and what to configure, so the pilot does not get stuck waiting.

6
interface and document languages
Source: card
5
steps to prepare for the pilot
Source: card

Step 1: establish what head office has to approve

The first question is: who in the group decides on IT and EHS tools at the plant. Often there are two people, one from IT and one from EHS, while the plant only has the right to make a request. Write down the names of the roles and the order of approvals before sending any document.

The second question concerns the scope of the pilot. The narrower it is, the easier the approval. A good pilot covers one hall, one type of permit and one group of external companies. The scope is extended based on results, not at the start.

InnerWeb is an independent system that complements the client's existing systems (access control, time and attendance, HR, ERP) and does not replace them. It is worth putting this sentence in the first paragraph of the request, because it dispels the most common head office concern about duplicating tools.

Step 2: prepare the document package for head office

The package should be short and understandable for a person outside the plant. It consists of a description of the pilot's purpose, scope, duration, success criteria and a description of integrations with existing systems. Add information about languages: the interface and documents work in six languages, including English and German, so head office sees the data in its own language.

Attach a short description of what the group plant scenario shows: an isometric map of the hall with transmitters, permits from templates, hazards assigned to locations, guest registration at a kiosk with a QR code, and SOS and no-movement alerts on the map. This is a deployment scenario, not a description of a completed project, and it should be presented as such.

The IT department of head office will ask about data and hosting. Prepare an answer on where the system will run and who has access to the data. Agree the answer with the provider before sending the package.

Settings to prepare before the pilot

Settings to prepare before the pilotHorizontal bar chart: six languages, eight permit labels, two logo and background modes.02468pcsSystem languagesSystem languages: 6 pcs6Permit field labelsPermit field labels: 8 pcs8Logo and background modesLogo and background modes: 2 pcs2
Source: Documentation of the internationalization and system branding features

Step 3: order the access on the plant side

Access usually takes the most time, so we order it in parallel with the work on approval. What is needed: administrator accounts in the system, network access for the devices at the gate and in the hall, and possibly a connection to the access control system.

If the plant has an access control system, InnerWeb does not replace the readers. The integration consists of receiving card punch events from the client's system, so the access control provider must make these events available. It is worth sending them the request before the pilot starts.

Step 4: set up the system for the plant

After approval we move to the settings. The administrator uploads the system logo and the login screen background, separately for light and dark mode. The editor is in the system settings, in the Facility tab. Add the logos of the key external companies so the company list is readable.

Next, establish the languages. Check which languages contractors and visitors work in, and prepare an induction training for each one. When the training is missing in the account language, the gate requires the training in Polish, so this work must be done before the start.

Finally, check the permit labels. Eight permit field labels can be overridden per installation. An override takes precedence over the translation, so set them deliberately, preferably bilingually.

Step 5: plan how to measure success

Establish the success criteria before the start, not after it. Good criteria are countable: the time to issue a permit, the number of permits in the system compared with paper ones, the share of visitors who completed the training at the gate, the time to prepare the report for head office.

Set the moment of review, for example after four weeks, and the person who leads it. The review results are the basis for the conversation about extending the scope.

Checklist

Video

Frequently asked questions

How long does it take to get head office approval?

It depends on the structure of the group. A narrow pilot scope and a package that immediately answers IT and EHS questions help shorten it.

Does the pilot require replacing the plant's systems?

No. InnerWeb works as an independent system complementing access control, time and attendance, HR and ERP.

What should be prepared first?

The map of approvals in the group and the pilot scope. Only then the documents, access and settings.

Let us prepare the pilot together

We will help put together the package for head office and the list of access. Let us arrange a conversation about the scope of the pilot at your plant.

Let's talk