Where a plant starts when it has no system
The typical starting point is work orders on paper and in Excel spreadsheets, contractors invited by different people, and training validity tracked by hand. A plant like that has no single list of people and no single list of companies, so the first question is not about the tool but about where the data lives today.
Migration is not a one-off transfer of everything. It is an ordered sequence: the list of people and companies, the plant structure, permit templates, risks assigned to locations, and only then daily work in the new system.
What can be loaded from spreadsheets and what cannot
The system has no mass import of accounts. Mass entry works as a loop: for each row of the spreadsheet an account is created and an invitation is sent, on average about 2 seconds per account. The spreadsheet is therefore a data source for a script or an operator, not a file you point to in the panel and import with one button.
Permit templates, their tasks and scope are configured in the installation data, without changes to the code. The printout can reproduce a paper form of the plant through an uploaded template matrix, but no arbitrary form is promised without implementation work on that matrix.
- People and companies: an account creation loop with an invitation, duplicate control when the invitation is sent from the panel.
- Permit templates and tasks: configured in the installation data.
- Permit printout: a template matrix that reproduces the paper form, after implementation work.
- Plant structure: entered in five levels, with a test run and a backup before saving.
- Training validity: carried over from the register that the plant treats as the source.
Machine time of the invitation loop by number of accounts (example)
How long it takes: a machine time calculation
Assuming about 2 seconds per account, the loop for 500 people takes about 1000 seconds, which is a few dozen minutes of machine time. This is the run time of the script, not the time needed to prepare the data. The preparation depends on the quality of the spreadsheet and is usually longer than the saving itself.
That is why the schedule rests on two numbers: how many people and companies are in the spreadsheets, and how many rows need correction before loading. The first gives the saving time, the second the preparation time.
Migration order and the parallel run
The plant structure has five levels: plot, view (department), building, line and location. A view is not a building, so a list of locations taken from a floor plan must not be loaded as views. The structure is set before risks and permits, because risks are assigned to locations.
Migration does not require switching off existing systems, because InnerWeb works as an independent system that complements the client's systems: access control, time-attendance, HR and ERP. A pilot can run for several months at no extra cost, and modules can be tested in parallel on the same instance, which the plant uses as a parallel run with paper.
Errors that only show up after loading
The most common error is a duplicated person. In one production case the same person had two accounts: one created at the gate without an e-mail, the other six minutes later from a QR poster, and the person completed the training twice. Duplicate control covers invitations sent from the panel and registration from a QR code, but it works from the moment of deployment, not retroactively.
Merging duplicates that already exist is a change to data and requires a separate decision. That is why the list of people is cleaned before loading: one row per person, with an e-mail or employee number wherever one exists.
Video
Frequently asked questions
Can I load an Excel file in one click?
No, the system has no mass import of accounts. People from the spreadsheet are entered in a loop that creates the account and sends the invitation, which takes a few dozen minutes of machine time for 500 accounts.
Do I have to switch off my existing access control or time-attendance system?
No. InnerWeb works as an independent system that complements the client's existing systems, so migration does not require switching them off.
Will my paper permit form be reproduced?
The printout can reproduce the plant's form through an uploaded template matrix. No arbitrary form is promised without implementation work on the matrix.
Will the system fix duplicates that are already in my spreadsheet?
Not retroactively. Duplicate control works from deployment for invitations and QR code registration, and merging existing duplicates requires a separate decision.
Do you have spreadsheets and paper, but no system?
Tell us where the lists of people, companies and training records are kept today. We will propose the migration order and show it in a demo.
Let's talk