Starting point: a 1 x 1 m machine marker
In the previous system a machine was a square with a side of 1 m, drawn where the team considered it to stand. It had no assigned line or area. The new structure requires the opposite approach: a line has an area, and the machine is inside that area.
The first step is therefore to establish in which building the marker physically lies. A line with a machine marker moves to the building zone in which that marker lies. The rule sounds simple, but it requires exact building geometry, because markers close to building boundaries are easy to assign to the wrong hall.
Trap 1: a stack of lines at one point
The worst migration result is several lines stacked on one point. A stack of at least three lines at one point is not a position: the operator sees one pin, with the others hidden beneath it.
Before implementation it is therefore worth counting the points where at least three lines lie. Each such point is a candidate for splitting the fields or correcting the assignment of machines to buildings. The absence of stacks is one of the conditions for moving on.
- Count the points with at least three lines.
- Verify the assignment of markers to buildings at the boundaries of halls.
- Split the line fields before creating the locations.
- Repeat the test after every correction of the geometry.
Example: points with a line stack before and after splitting the fields
Trap 2: the first location outside the machine
The first location of a line stands exactly at the machine point, and the line field is calculated by a guillotine split so that it contains its own machine. A guillotine split cuts the building area with straight cuts between the lines, so each line gets a rectangular or polygonal field with its own machine.
The control tolerance is 1.5 m: if the distance between the machine point and the first location, or the edge of the field, exceeds this value, the gate reports an error. The 1.5 m value matches the accuracy of the location we use in the map, so stricter control makes no sense.
Trap 3: pins outside the line and no red tests
The migration gates, that is overlapping lines, pins outside the line, Other outside the middle and duplicates, have red tests: each was checked on a deliberately broken example. A pin outside the line field means that the location points to a place that does not belong to its line.
After regenerating the structure, the comparison is made by content (name, area, level, geometry), not by identifiers. The identifiers are new after regeneration, so a comparison by them says nothing about correctness.
Order of work before implementation
The order: list of machines and markers, assignment to buildings, guillotine split, creation of locations at the machine points, review of stacks, running the gates, a trial in the test environment, a review of the map by the maintenance representative. Only then production.
A plant representative should confirm a dozen or so machines in the field. A test on the map does not replace checking whether the pin really lies at the filter and not next to it.
Example of a review of line stacks
| Parameter | Value |
|---|---|
| Machines to move | 120 pcs |
| Points with a line stack | 14 points |
Result: 14 points require splitting the fields before implementation.
Note: Example calculation; the figures are assumptions, not data from a specific plant.
Checklist
Video
Frequently asked questions
Why are the machine markers 1 x 1 m?
That is how they were recorded in the previous system. They carry no information about a line or an area, so they must be assigned to a building and a field.
What is a guillotine split?
It is the division of a building area by straight cuts into disjoint fields, one per line, each containing the point of its machine.
How large a deviation is accepted?
The control tolerance is 1.5 m. A larger distance between the machine and the first location, or the edge of the field, is reported as an error.
Do you have machine points to move?
We will analyse the markers from the old system and prepare a plan for splitting the halls with control gates.
Let's talk