InnerWeb
Skip to main content

Driver navigation matrix: best practices for building and tuning

The navigation matrix is a table that tells the system what the driver should hear at a given junction when heading to a given warehouse. Its quality decides whether the driver reaches the ramp or stops in the wrong place. We have collected practices for the administrator who builds and tunes it.

2
consecutive signals from the same transmitter that confirm an announcement
Source: navigation functions sheet
55 s
validity time of a prompt
Source: navigation functions sheet

What the matrix is and what it does not do

Voice navigation is not GPS and not live routing. It relies on an editable matrix that defines what to say at a junction for a given warehouse, without fixed routes. The administrator therefore defines pairs: a junction and a target warehouse, and assigns a directional prompt to each pair.

This is a simple model, but it requires discipline. Every new junction and every new warehouse increases the number of combinations, and a poorly prepared combination means either silence or a wrong prompt. The practices below are meant to limit this risk.

Practice 1: build the matrix from the warehouses, not from the junctions

Start with a list of the warehouses and docks that drivers actually go to. Navigation leads to warehouses covered by the matrix, and a test delivery must have the target dock code entered, because the dock code determines the warehouse. For each warehouse, describe the approach route from the gate as a sequence of junctions.

Only then assign prompts to the junctions. This approach limits the risk that an important junction is skipped only because it is rarely used.

Number of matrix cells grows with warehouses (example calculation)

Number of matrix cells grows with warehouses (example calculation)Bar chart: 24 matrix cells for 3 warehouses, 48 for 6, 72 for 9020406080cells3 warehouses: 24 cells24 cells3 warehouses6 warehouses: 48 cells48 cells6 warehouses9 warehouses: 72 cells72 cells9 warehouses
Source: Example calculation: 8 junctions on the route assumed, number of cells = warehouses x 8

Practice 2: tune the matrix live, but keep a change log

The navigation matrix is edited in the administrator panel on the fly, without deployment and without restart, including during tests at the client's site. This is a great advantage, but also a temptation. A change made during a test drive is hard to reproduce when nobody has recorded it.

Keep a simple log: date, junction, warehouse, what was changed and why. When drivers report a mistake, the administrator knows which change started the mistake and can go back to the previous value.

Practice 3: remember the rules of announcement

A directional prompt is announced about one transmitter before the junction, after the same transmitter has been confirmed in two consecutive signals, which rejects a single distant reading. With transmitters placed about every 100 m along plant roads, this means an announcement roughly 100 m before the junction.

A practical consequence follows: if two junctions lie closer together than the transmitter spacing, the prompts may overlap in time. In that case it is worth shortening the content of the prompts or adding a transmitter, rather than lengthening the matrix.

Practice 4: accept silence and repeats that follow the rules

The relative direction is calculated at the moment of passing, from the actual approach segment driven by the driver. When the approach arm is unknown, the system stays silent, because a wrong direction is worse than no prompt. The administrator should not treat silence as a fault of the matrix until checking which arm the driver entered from.

Each junction speaks once per delivery, and a prompt expires after 55 seconds. During tests, therefore, a new test delivery has to be created if we want to hear the same prompt again.

Practice 5: test with a driver, not only with the dashboard

The panel shows what is stored in the matrix. It does not show whether the prompt is understandable at the moment when the driver has a truck, noise and a queue behind him. Run a test drive with a person from outside the team, preferably in a language they do not speak, and note where they hesitated.

After the test, correct the matrix straight away in the panel and repeat the drive with a new delivery.

Checklist

Video

Frequently asked questions

Does changing the matrix require a deployment?

No. The matrix is edited in the administrator panel on the fly, without deployment and without restart, including during tests at the client's site.

Why does the system sometimes stay silent at a junction?

When the driver's approach arm is unknown, the system gives no prompt, because a wrong direction is worse than silence.

Does the same junction prompt repeat?

No. Each junction speaks once per delivery, and a prompt expires after 55 seconds.

Let's build the matrix for your warehouses

Book a call. We will help you list the warehouses and junctions and plan the test drives.

Let's talk