How to use this list
Go through the list in order. Each item has a verifiable condition: something you can see in the panel, hear on a test drive or read from the log. An item that cannot be checked must be reworded before it is considered passed.
People: logistics is responsible for the matrix and the language, traffic maintenance or IT for the transmitters and coverage, IT for the locator app, and security for issuing the locators. Record who ticks which item, so that nobody assumes a colleague has done it.
Matrix and transmitters
The basis of navigation is the editable decision matrix: for each junction it records the instruction, the absolute direction and the triggering transmitters. No entry means no message, not a default message, so a skipped junction will not be noticed unless someone checks it.
Triggering transmitters stand on the approaches to junctions, not in their middle. Two consecutive location readings from a transmitter on the approach trigger the message, and at a special point the first signal is enough. Keep this in mind during the test, because a vehicle driving too slowly or too fast may behave differently from normal traffic.
The matrix can be corrected in the panel without a deployment and without a restart, so you do not close the list when the matrix is perfect, but when you know all the gaps and who will fix them.
Example preparation time for the checklist items
Application, language and message expiry
Messages are played by the locator app and sent as push messages valid for 55 seconds. The test should include a phone without coverage: a message not delivered within that time expires and is not played after a few minutes, so once coverage returns the driver does not hear an outdated instruction.
When a locator is issued, security records three decisions: whether the driver wants voice navigation, in which language, and whether the delivery is under special supervision. Switching navigation off clears the language, and switching it on without a choice sets Polish. Check this on several devices and in several of the 10 available languages: Polish, Ukrainian, English, Russian, Romanian, Bulgarian, Slovak, Czech, German and Hungarian.
The final test: each junction speaks at most once during a single delivery. Drive through a junction twice within one delivery and check that the second time it stays silent.
Special points, the log and the go decision
A special point, for example a weighbridge or a tight spot at the gate, speaks already after the first signal, without double confirmation. Check each such point separately, because the transmitter stands closer there and a false trigger is easier when a vehicle passes alongside.
The message log is an acceptance tool: when the system cannot determine from which side the driver approached a junction, it stays silent and records this in the log. Review the entries from the test drives and for each one decide whether the matrix needs correcting, the transmitter needs moving, or the lack of a message should be accepted.
The decision to go live belongs to logistics and security jointly. Record the date of a review after the first week of operation: the log will then show where real drivers, not testers, encounter gaps.
Checklist
Video
Frequently asked questions
Can the matrix be changed after launch?
Yes, in the panel, without a deployment and without a restart.
What about a driver who does not want navigation?
Security records at issue that navigation is switched off, and then the language is cleared.
How do I find the places where the system stayed silent?
Cases where the direction of approach could not be determined are recorded in the log.
Let us go through the list together
A week before launch we can walk through this checklist with your IT and logistics teams.
Let's talk