Why identifiers are unsuitable for comparison
After a structure is regenerated, new records with new identifiers appear, even when the location is the same physical location. A comparison by number would therefore report the removal of every old item and the addition of every new one, regardless of whether anything physically changed.
The tester has the opposite problem too: when the number matches but the content has changed, a comparison by number does not detect it. That is why the only safe method is comparison by content.
Four fields you compare by
After a structure is regenerated, the comparison is made by content: name, area, level and geometry. Each of these fields answers a separate question for the tester and detects a different kind of error.
Name and area
Line names must be unique within a building, thanks to a zone suffix. Comparing names detects duplicates, and comparing the area detects locations that moved to another line or building.
Level
The editor draws a location without a floor on the ground level, so the level comparison must count levels the way the editor renders them, not by identifier. In a building with seven levels, a line with no assigned floor goes to Level 0 m, and room codes with a level-number prefix go to the matching floor.
Geometry
Compare geometry with a tolerance. For the coordinate transformation, the maximum error on 64 control points was 0.01 m, and the tolerance for the check of a machine's position within the line field is 1.5 m.
Tolerances in the geometry check
Gates that must have a red test
The migration gates are: overlapping lines, pins outside their line, the Other location away from the middle, and duplicates. Each has a red test, meaning deliberately wrong data that the gate must reject. A gate without a red test is a hypothesis, not proof.
Add to this the rule for the collective location: each line contains exactly one Other location, with the highest identifier, placed in the middle of the line. The tester checks this rule separately, because it is the only case where the identifier matters.
Special cases in the comparison
Registry objects with no known position go to the Plant grounds area without geometry and without a point. They are invisible on the map, so the geometry comparison will not cover them. Check them separately, by name and area.
A line without its own shape gets a separate field carved out of the building, so the comparison after regeneration should show that the line fields do not overlap. The first location of the line stands exactly at the machine point, and the field is computed by guillotine division so that it contains its own machine.
How to record the result of the comparison
Record the number of items unchanged, changed and new in each of the four fields, together with the list of exceptions. This record is audit proof and lets you return to the same check after the next regeneration. The cost calculation of manual comparison and of a script is described separately.
Checklist
Video
Frequently asked questions
Does the identifier never matter?
It matters in one place: the Other location has the highest identifier in the line and stands in the middle of the line. Apart from that, the comparison is made by content.
How do I know that a gate really works?
From its red test: deliberately wrong data that the gate must reject. A gate without such a test is only a hypothesis.
How do I compare levels when the editor shows no floor on the ground level?
Compare levels the way the editor renders them, not by identifier. Treat a missing floor and the ground floor as the same level.
What about objects that have no position?
They go to the Plant grounds area without geometry and without a point, so they are invisible on the map. Compare them by name and area until a position is given.
Plan a test of the structure regeneration
We will go through the comparison fields and the gates with red tests for your plant. Book a conversation with the tester and the data department.
Let's talk