InnerWeb
Skip to main content

Pre-Arrival Notice and Gate Locator: Implementation Notes

The yard status matches the logistics system only when the pre-arrival notice data, the delivery form and the issued locator form one chain. We set out implementation notes for the logistics and IT teams: the order of work, the integration tasks required, the settings at locator issue and how the delivery route is verified.

3
decisions recorded at locator issue
Source: feature card
1 min
stop threshold shown on the delivery map
Source: feature card

What we connect and why

Using the pre-arrival card code, the system retrieves the planned delivery data from the client's pre-arrival notice system and pre-fills the form. The integration requires implementation work on both systems, so it is planned as a separate stage, not as a minor configuration.

The aim is practical: security does not retype the pre-arrival data, and the yard status shows the same deliveries that logistics sees. Discrepancies between the systems usually start with manual retyping.

Step 1: decide which system is the source of truth

Before you start the integration, decide which system is the source of data on the planned delivery. The pre-arrival notice system remains the source of the plan, and InnerWeb takes over the data at the gate and supplements it with facts from the yard.

Record which fields pass to the form: carrier details, vehicle, target warehouse, time window. Fields that the notice does not provide are completed manually by security.

Example sequence of implementation work in weeks

Example sequence of implementation work in weeksChart: example stage durations: decisions 1 week, integration 4 weeks, locator issue 2 weeks, route verification 2 weeks.01234weeksDecisions and data fieldsDecisions and data fields: 1 weeks1Integration with the noticesystemIntegration with the notice system: 4 weeks4Locator issueLocator issue: 2 weeks2Route verificationRoute verification: 2 weeks2
Source: Example calculation: assumed stage durations, to be confirmed after analysis of the pre-arrival notice system

Step 2: integration and the pre-filled form

Run the data retrieval by pre-arrival card code and check the pre-filled form on several dozen real notices. Pay attention to rare cases: a vehicle change, several warehouses in one delivery, a delivery with no notice.

A delivery without a notice must have a manual path, otherwise security will be forced to work around the system. The manual path is also where organisational problems in logistics are easiest to spot.

Step 3: locator issue and driver settings

After the form is filled in, security issues the locator and records three decisions: whether the driver wants voice navigation, in which language, and whether the delivery is under special supervision. This step links the notice with the map: the vehicle appears on the online map in a colour that depends on the settings.

The delivery route comes from BLE transmitters detected by the locator, not from GPS. The position is averaged from signals of several transmitters on the map, which also works in places without satellite coverage.

Step 4: verifying the route and stops

The operator can isolate one active delivery on the map and see the route from entry up to the present moment, stops longer than one minute and a pin for the declared destination. This makes it possible to compare the declared destination with the actual course.

During deployment, compare a dozen or so deliveries: does the destination pin match the warehouse on the notice, and do the stops match unloading? Discrepancies will point to errors in the data or in the layout of the transmitters.

Deployment pitfalls

The most common pitfalls are warehouse names that differ between the notice and the system, no path for deliveries without a notice, and inconsistent locator issue: the language question is sometimes asked and sometimes not.

Set an owner of the integration on the logistics side and on the IT side, and a review day after the first two weeks of work. Then you have data, not impressions.

What to report after go-live

After go-live, collect three simple indicators: the share of deliveries pre-filled from the notice, the number of deliveries entered manually, and the number of discrepancies between the destination in the notice and the actual stop. The first shows the quality of the integration, the second the tightness of the process, the third the consistency of the yard with the logistics system.

Recurring delivery reports can go by e-mail to logistics as PDF. Compare them with the pre-arrival notice system data every week for the first month, and then every month. Explain discrepancies at a short logistics and security meeting, rather than quietly correcting the data.

Video

Frequently asked questions

Is the pre-arrival notice integration a configuration task?

No, it requires implementation work. It is planned as a separate stage together with the IT team.

What about a delivery with no notice?

Security fills in the form manually. The manual path should be described before go-live.

Does the delivery route come from GPS?

No. It comes from BLE transmitters detected by the locator.

Connect the notice system with the yard

Describe your pre-arrival notice system and how you receive deliveries. We will plan the order of integration tasks together with your IT team.

Let's talk