How to use this checklist
Two people go through the list together: a representative of IT and a representative of EHS. Each point has one owner and one date. We mark a point as closed only when we have evidence, for example a screenshot, an e-mail confirmation or a record from a test.
We fill in the checklist two to three weeks before the planned start. With a shorter timeline, some points, especially access and head office approvals, will not be closed in time.
Approvals and architecture
Start by asking whether head office has approved the pilot in writing, not only verbally. The approval should cover the scope, the duration and the data that will be processed in the system.
Prepare one sentence on the role of the system. InnerWeb is an independent system that complements the client's existing systems (access control, time and attendance, HR, ERP) and does not replace them. If head office sees the system as a complement, not a competitor to the group's tools, approval comes faster.
Number of control points by area
Access and network
The IT department confirms which accounts and access are needed: system administrators, devices at the gate, tablets and possible workstations in the hall. For integration with access control we ask the access control provider to make card punch events available, because this is the only way to exchange data; InnerWeb does not replace the readers.
Test task: before the pilot we check whether the device at the gate connects to the system and displays the registration screen. Lack of connectivity right at the gate is the most common reason for delays.
Languages and trainings
The interface and documents work in six languages: Polish, English, German, Finnish, Russian and Swedish. For each language in which guests or contractors appear at the plant, an induction training must be available. When it is missing, the gate requires the training in Polish.
Also check local names in dictionaries that have no English column. They are entered in the language in which they are to be read. It is good to print one permit in each language and have it checked by a person who knows the language.
Appearance of the system and documents
The system logo and the login screen background are set by the administrator in the system settings, in the Facility tab, separately for light and dark mode. Agree the versions of the logo with head office before they are uploaded.
If head office receives reports, agree the rhythm: daily, weekly or monthly. Scheduled reports go out by e-mail with tables in the body, a PDF attachment carrying the client's logo and an optional XLSX file.
Success criteria and accountability
Before the start, write down how you will know the pilot has succeeded: the time to issue a permit, the share of visitors who completed the training, the time to prepare the report for head office. Set a review date and the person who leads it.
Appoint one coordinator on the plant side. A pilot where nobody is responsible for the whole gets lost in small IT and EHS matters.
Checklist
Video
Frequently asked questions
Who should lead the checklist?
IT and EHS together, with one plant coordinator responsible for the whole.
What most often delays the start of the pilot?
Network access at the gate and a missing training in the language of one of the guest groups.
Do the access control readers have to be replaced?
No. The integration consists of receiving card punch events from the client's system.
Let us go through the checklist together
During a short meeting with IT and EHS we will go through the list and mark the points that need action before the start.
Let's talk