InnerWeb
Skip to main content

Plant Data Migration Order: Implementation Notes

Plant data depend on each other: people belong to companies, trainings to people, risks to locations, permits to templates. A project manager who schedules the plan in the order of dependencies avoids rework and repeated saves.

5
levels of plant structure: plot, view, building, line, location
Source: migration documentation
5 weeks
sample schedule for five stages (assumption)
Source: example calculation

Rule: first what the other data depend on

The migration order follows from dependencies. A risk cannot be assigned to a location that does not exist yet, nor a training to a person who has not been entered. The typical starting point at a plant is work permits on paper and in Excel sheets, companies invited by different people and training validity tracked by hand, so data lie in different places and must be put in one order.

InnerWeb works as an independent system supplementing the client's existing systems, so migration does not require switching off access control, time attendance, HR or ERP. The order concerns only moving data into InnerWeb.

Stage 1: plant structure

The plant structure has five levels: plot, view (department), building, line, location. A view is not a building. This is the foundation, because risks, permits and presence of people are attached to locations. Structure migration is performed with a backup to an SQL file, in trial mode and with consistency gates.

Structure errors are the most expensive: confusing a view with a building can erase the only view with a calibration. That is why structure goes first and passes an independent check before anything is built on it.

Stage 2: companies

The second stage is external companies and their coordinators. People are entered only after companies, because the role of an external worker is tied to the company account and invitations go through it. Tidy up company names and remove repetitions before creating accounts.

Stage 3: people

The third stage is people. The system has no bulk import of accounts: entry is a loop of invitations, about 2 seconds per account, so 500 people take about 1000 seconds of machine time (500 x 2 s). Before the loop we tidy the sheet: phone numbers in E.164, e-mails, names. Internal accounts are entered separately from guests, because they are never linked with them.

Stage 4: trainings

Trainings and their validity are assigned to accounts that already exist. If the data come from a sheet kept by hand, unify training names and validity dates before entry. Trainings assigned to duplicated accounts split the history, so this stage follows the resolution of the duplicate queue.

Stage 5: risks and permit templates

Risks are assigned to locations, so they require a ready structure. Permit templates, their tasks and scope are configured in the installation data, without changes to the code. A print layout can reproduce the plant's paper form through an uploaded template matrix, but no arbitrary form is promised without implementation work on the matrix.

Templates are left for last, because they require decisions by people: which tasks and what work the plant recognises as standard. Once structure, people and trainings are working, the discussion about templates rests on real data.

  • risks: after a ready location structure,
  • templates: after agreeing the standard of work with the plant,
  • print layout: separate work on the template matrix.

Sample schedule and checkpoints

In an example calculation for a plant with several halls, the project manager can spread the five stages over five weeks, one week per stage, with a data quality check at the end of each. Such a layout is an assumption for discussion: the real time depends on the size of the plant and the availability of people. The pilot can last several months at no additional cost, so there is no pressure to fit everything into a few days.

Video

Frequently asked questions

Why is the plant structure first?

Risks, permits and presence of people are attached to locations. An error in the structure spoils all later stages.

Do permit templates require code changes?

No. Templates, their tasks and scope are configured in the installation data, without changes to the code.

Does the migration require switching off access control, time attendance or ERP?

No. InnerWeb works as an independent supplementing system, so the existing systems keep working unchanged.

Let's plan the migration schedule for your plant

During the talk we will go through the five stages and establish what your plant already has ready. Book a talk or a demo.

Let's talk