Who these recommendations are for
The recommendations are aimed at the director of a plant that belongs to an international group, has its own OHS manager and an IT department that partly reports to the head office. Such a plant follows group standards, but it is responsible for Polish regulations, the Polish workforce and the contractors.
The recommendations rest on functions the system already has and on the pattern of a machinery plant in the group, which is described as a demo scenario, not as a rollout.
Seven recommendations before ordering a pilot
The recommendations below are arranged in the order in which they are worth discussing. Each has a rationale that can be presented to the head office.
1. Limit the scope to one hall
A pilot covering one hall and one group of contractors gives a result measurable within weeks. A scope covering the whole plant blurs responsibility and lengthens the agreement with the head office.
2. Define what the system does not replace
InnerWeb is an independent system that complements the client's existing systems: access control, time and attendance, HR and ERP. It is not a replacement for them, so the pilot does not require replacing them. This makes it easier for the head office to agree, because global systems are not touched.
3. Write down the group standard requirements
Before technical discussions begin, collect the group's EHS requirements on permits, reports and training. Only with this list can you assess which pilot functions are mandatory and which are optional.
4. Define the role of the IT department
The IT department needs a clear scope: who grants access, who is responsible for accounts and who reports changes. Settling this at the start shortens the internal agreement.
5. Decide on document languages
The system supports six languages: Polish, English, German, Finnish, Russian and Swedish. Choose those that will actually appear at the plant and check their printouts before the start.
6. Set the look of the instance
The logo in light and dark mode and the login screen background are set by the administrator. The decision whether the plant's logo or the group's logo is used should be made before the pilot, because it shapes the workforce's first impression.
7. Define the pilot success criterion
Write down how you will know the pilot has succeeded: the number of permits issued, the share of documents in the worker's language, the time from request to issue. Without a criterion, the pilot ends with an opinion rather than a decision.
System languages and the sample pilot scope
What to avoid
The most common mistake is entering a pilot without an agreed group standard, which ends with templates being corrected after launch. The second is too broad a scope. The third is leaving out the contractors, who generate most of the permits and need documents in their languages.
How to present this to the head office
For the head office, prepare one page: scope, indicators, languages and the dependency on existing systems. Periodic reports can go to the head office by e-mail daily, weekly or monthly, as tables in the body and as a PDF attachment with the client's logo, and optionally as XLSX. The details are described on the page about reports for the head office.
Sample pilot timeline
For one hall, plan three stages: preparing data and agreements, launch for the selected group of contractors, and assessment. Exact dates depend on the number of workstations and the pace of approval on the head office side, so set them only after a site survey.
It matters that the assessment of results has an owner. If nobody is responsible for comparing the indicators against the success criterion, the pilot ends in discussion rather than in a decision to extend the scope to further halls.
Also record what happens after the pilot: extension to further halls, staying in the current scope, or closure. It is better to prepare this decision in advance, because the assessment is then simpler.
Video
Frequently asked questions
Does the pilot require replacing the plant's systems?
No. InnerWeb complements access control, time and attendance, HR and ERP, and does not replace them.
Who should approve the pilot scope?
The plant director together with the OHS manager and the IT department, and the group's head office if needed.
How many languages should be covered at the start?
As many as actually appear among the workforce and the contractors. Out of the six available, two or three are often enough.
Set the pilot scope
We will go through the seven decisions with you and propose a pilot scope for one hall of your plant.
Let's talk