InnerWeb
Skip to main content

Location structure migration: a plant case study

A plant already has a location register in which risks, documents and equipment have been assigned for years, and an IT integrator has to move them into the plant map of a new system. The worst possible outcome is losing the map calibration and identifiers. Below we describe the sequence of actions that avoids this, based on a documented plant structure migration.

0,01 m
maximum error of outlines converted back
Source: location structure migration documentation
64
control points in one verification
Source: location structure migration documentation

Starting point: an old register and a new map

In the case we describe in general terms, an industrial plant had a list of several hundred items: areas, lines and workplaces, linked to risks, documents and equipment calibration. The integrator was responsible for ensuring that after the system change every item had its counterpart in the map and that all links remained traceable.

The migration was planned as a repeatable procedure, not a one-off manual operation. Repeatability has a practical consequence: an error found after the first run is fixed in the script and the whole run is started again, instead of patching production data by hand.

Rule 1: identifiers stay, new items get a separate range

Data from the client's existing system is moved while keeping its identifiers. New lines and locations that were not in the old register receive numbers from a separate range. This keeps the mapping of old items to new ones reproducible: it is enough to compare the number with the range to know whether an item comes from the register or was created during the migration.

In practice the integrator keeps a compatibility table: old identifier, new path in the structure, status. Such a table is also evidence for an auditor that no item was lost along the way.

Migration stages and number of gates with a red test (sample plan)

Migration stages and number of gates with a red test (sample plan)Horizontal bar chart: 64 control points and a maximum error of 1 centimetre.020406080control pointsGeometry control pointsGeometry control points: 64 control points64Max error (cm)Max error (cm): 1 control points1
Source: Location structure migration documentation: 64 control points, maximum error 0.01 m (1 cm)

Rule 2: do not touch the view where the calibration lives

Georeferencing, meaning the anchor point, rotation and scale, together with the orthophoto, belongs to the plant view. Deleting or replacing such a view during a structure migration removes the map calibration. Restoring it means a new measurement and re-alignment, which is days of work for the field team.

That is why the migration does not start with cleaning: the existing view stays, and the new structure of buildings, lines and locations is created inside it. Only after verification can the old items be marked as withdrawn.

Rule 3: trial mode with transaction rollback

The migration is first run in trial mode, in which all changes are calculated and then rolled back. Only after the gates are green does the write mode run. Before writing, a copy of the structure is made, so if in doubt it is possible to return to the starting state.

The script writes data only when all consistency gates show zero. Each gate has a test in which an injected known error turns it red. A gate that has never detected an error is a hypothesis, not a safeguard.

  • A copy of the structure before writing, with its size and checksum recorded.
  • Trial mode with transaction rollback until the full gate report has been reviewed.
  • Writing only when there are zero violations in all gates.
  • A red test for each gate: the injected error must trigger it.

Geometry verification: control points

Coordinates must be calculated with the same transformation function the editor uses: local metres to WGS84 with the PUWG92 correction. Using a different formula produces an offset that looks like a small inaccuracy on screen, but in the field means a position in the wrong building.

In one verification of the structure migration, outlines converted back landed on the plan with a maximum error of 0.01 m across 64 control points. A back-conversion test like this should be part of every run, because it is cheap and catches a transformation error before the data reaches production.

Result and conclusions for the integrator

The case shows that a migration runs smoothly when three things are settled before the first run: identifiers and number ranges, protection of the view with calibration, and gates with red tests. An integrator who has these three elements can repeat the migration without risk to the client's data.

InnerWeb works here as an independent system complementing the client's existing solutions, so the old register does not have to be switched off on migration day. Both can run in parallel until the compatibility table is approved.

Video

Frequently asked questions

Can the migration be repeated after an error is found?

Yes. The migration is repeatable, and a copy of the structure is made before writing. The error is fixed in the script and the procedure is started again.

Why a separate number range for new items?

It keeps the mapping of old items to new ones reproducible. The number shows at once whether an item comes from the register or was created during the migration.

Does the old system have to be switched off on migration day?

No. InnerWeb works as an independent complementing system, so both registers can run in parallel until the compatibility table is approved.

Migration without losing calibration

If you are moving a location register to a new system, we will show the procedure with trial mode and gates. Let's arrange a talk with your integrator.

Let's talk