InnerWeb
Skip to main content

Dock and carrier dictionary: implementation notes

Dictionaries of docks and carriers are not loaded by migrations, so a new plant does not wait for a developer. The logistics system administrator completes them in the panel, and this page suggests the order to do it in before the gate goes live and which traps to watch for.

5 characters
canonical code of the query to the appointment system
Source: card
5
stages of completion before the gate goes live
Source: recommendation from this page

Why the dictionaries are data, not code

In the InnerWeb system, the dictionaries of docks and carriers are not loaded by migrations. The master stays generic, and the data of a specific plant is completed through the panel. In this way the same system image can be deployed in many plants, and each has its own list of docks and carriers.

For the administrator this is good news: starting a new plant requires no changes in the code and no release cycle. It is also a rule of order: the plant's data lives in the plant, not scattered across migration files. Renaming a dock after the yard is renovated is an operation in the panel, not a request for a developer.

Order of completion before the gate goes live

The recommended order follows from the dependencies: first what the other elements point to. The stages below help move from an empty system to a gate ready for the first delivery.

  • Stage 1: the list of warehouses with their codes, because service point names are matched exactly to warehouse codes.
  • Stage 2: the list of unloading docks with their assignment to warehouses.
  • Stage 3: the list of carriers, starting with those who arrive most often.
  • Stage 4: test reads of codes from the delivery card on several real deliveries, with the result compared to the plan.
  • Stage 5: training of the security shift supervisors in using the delivery form.

Stages of preparing the gate in order

Stages of preparing the gate in orderFive stages of preparing the gate: warehouses with codes, docks, carriers, read test and security training.012345stageWarehouses with codesWarehouses with codes: 1 stage1DocksDocks: 2 stage2CarriersCarriers: 3 stage3Read testRead test: 4 stage4Security trainingSecurity training: 5 stage5
Source: Order recommended on the basis of the dependencies in the dock dictionary function card

How the system uses the dictionary at the gate

From the code on the delivery card, the system pulls the data of the planned delivery from the client's appointment system and pre-fills the form: the gate, the dock or warehouse, and the carrier. The type of operation decides the label: unloading or loading, and the service point name is matched against the warehouse codes in the dictionary of unloading docks.

The practical conclusion: a warehouse missing from the dictionary means no match for the service point, so the form will not show the correct dock. That is why the warehouse list comes first, and it is not worth skipping it for rarely used warehouses.

5-character codes and leading zeros

The query to the appointment system is sent once, using the canonical 5-character code. Codes with leading zeros stored in another form are reduced to one format. During the tests of stage 4 it is worth checking deliveries with codes starting with zero, because that is where a mistake in the form of entry is easiest to make.

Traps that only show up at the gate

The first trap is inconsistent names: the same carrier entered in three ways creates three items and spoils the statistics. It is worth agreeing on one form of entry before the first item is added.

The second trap concerns deliveries completed in the appointment system. The system deliberately treats them as no data, because the external system can return the last completed transport for many unrecognised codes. Security then fills in the form by hand, so the shift supervisor's instructions must describe how to do it quickly.

The third trap is expecting the dictionary to replace location. The dictionary says which dock exists, not where the driver is. Position is tracked by transmitters: on the site roads roughly every 100 m, and inside a building one transmitter per 100 to 200 m2. The system averages the signals of many transmitters and works without GPS.

What comes next after the start

After the start the dictionaries live together with the plant: a new dock, a new carrier, a renamed warehouse. We recommend that one person in logistics is responsible for the dictionary, and that security reports gaps instead of adding items on its own.

Read telemetry lets you check how often a code does not return a delivery. Each read is saved with the code entered, the result, the transport status, the response time and the operator. A high share of gaps signals that something in the dictionary or in the communication with the appointment system needs correction.

Video

Frequently asked questions

Does the dictionary need a developer to change it?

No. The plant completes the dictionaries of docks and carriers in the panel, and the system master stays generic.

Where should I start completing it?

With the warehouses and their codes, because the service point name is matched against the warehouse codes in the dock dictionary.

What if a delivery is completed in the appointment system?

The system treats it as no data, so a stranger driver and stranger registration numbers are not assigned. Security fills in the form by hand.

Does the dictionary replace transmitters on the yard?

No. The dictionary describes the docks, while the driver's position comes from BLE transmitters, averaged without GPS.

Sources

Launch the gate in a new plant

Book a talk about the dictionaries and the order of the start. We will go through the stages using an example of a plant like yours.

Let's talk