InnerWeb
Skip to main content

Transmitter position correction and route history: implementation notes for logistics

After a transmitter position fix, new deliveries are drawn correctly, but old ones still show the jump. For the logistics manager this is important, because a report covering the period before and after the change, without an annotation, can lead to wrong conclusions. We describe what to expect and how to plan for it.

0
jumps on new deliveries after a correct fix
Source: karta
6
stages of the fix process in this list
Source: example calculation

What the correction changes and what it leaves alone

Correcting the stored position of a transmitter removes the jump for all future deliveries. From the moment of the change, subsequent trips draw a route that matches the actual road.

The correction does not change the past, however. Route points are immutable records of the moment the signal was received, so a transmitter correction does not rewrite history. Deliveries made before the fix keep the jump in the preview. This is not a fault but a principle: a historical record should reflect what the system registered at the moment of the signal.

Why history is not rewritten

The temptation to correct the old points as well is natural, but it carries a risk. A record from the moment of the signal can be evidence in a complaint, a dispute with a carrier or the analysis of an incident. Changing it retrospectively undermines the credibility of the whole set.

If the plant wants tidy historical reports, a better solution is an annotation with the date of the correction rather than rewriting the points. The annotation tells the reader of the report that a jump before that date has a known cause.

Stages of implementing the fix

A position fix is usually a short task, but it is worth placing it in a simple process so that nothing is left unclear afterwards.

  • Establish which transmitter row is active and confirm that the problem does not come from a duplicated identifier.
  • Record the date and time of the correction and the person who made it.
  • Correct the position on the map to the place of actual installation.
  • Synchronise the positioning cache without clearing it entirely.
  • Run a control trip and check whether the jump has disappeared from the new route.
  • Add an annotation with the date of the correction to the report template for any period that covers it.

Pitfalls

The first pitfall is a correction made for a physical duplicate of the identifier. Changing the stored position then does not remove the error, it only moves it to a second place, so the jump appears somewhere else after the fix. Before editing, check whether two devices do not share the same major:minor pair.

The second pitfall is the name change. The transmitter name shown on the map comes from the location assigned to it, so changing the location also changes what users see. Warn the people who use the map.

The third is deleting records of inactive transmitters. Spare transmitters are not deleted, because they may someday start transmitting again. Spare records may receive a name with a zero appended to tell the pair apart.

The fourth concerns synchronisation. After the change, the positioning cache must be synchronised without clearing it entirely, and afterwards you should check that the silenced transmitter records no new points while the others do.

How to communicate the change to report users

The logistics manager should warn the recipients of reports that deliveries made before the correction date may show a jump. One sentence in the report footer or in an internal message is enough: when the position of the transmitter causing the bounce was corrected, and that older routes have not been changed.

This way nobody will read a jump from before the change as a new fault, or compare route lengths from before and after the correction without taking this difference into account.

Video

Frequently asked questions

Do old routes get fixed after the correction?

No. Route points are immutable records of the moment the signal was received, so deliveries made before the correction keep the jump in the preview.

How do I mark a report that covers the correction date?

Add an annotation with the date of the fix and a note that older routes were not changed. One sentence in the report footer is enough.

Does the correction always remove the jump?

No, not if the cause is a physical duplicate of the identifier. Then the position change moves the error to a second place, and the identifier of one of the devices has to be changed.

Planning a transmitter correction at your plant?

We will help prepare the fix process and the annotation template for reports. Book a conversation with the InnerWeb team.

Let's talk