InnerWeb
Skip to main content

Visit card telemetry: how to settle the dispute over inactive cards

The logistics department reports that some visit cards do not work at the gate. The appointment system vendor replies that the cards are correct. Without a trace of failed lookups, both sides only have opinions. We describe a scenario where a record of every lookup turns the dispute into data analysis.

5 fields
recorded for each lookup: code, result, status, time, source
Source: delivery functions sheet

A report without evidence

The scenario is typical for large plants. The logistics manager hears from security that drivers give card codes that return no delivery data. They report it to the appointment system vendor. The vendor checks a few cards by hand, sees valid records and closes the case as not confirmed.

A few weeks later the report comes back, because security still sees the same problem. Nobody can say how many times a lookup failed, at what time, for which codes, or whether the lack of result was caused by the card, the code or the response of the external system.

This description is not about a specific client. It shows a class of problem that appears wherever two systems exchange data at the gate and each side sees only its own fragment.

What the lookup telemetry records

Every lookup by visit card code is recorded in telemetry. The record contains the code, the result, the status, the response time and the source. This means recurring reports about inactive cards can be confirmed or disproved with numbers.

The value of this record is that it also covers failed lookups. A plain delivery register only shows deliveries that were created. Telemetry also shows attempts after which no delivery was created, and those attempts are exactly what the dispute is about.

  • Code: the code typed by security or scanned by the reader
  • Result: data found, no data, or an error
  • Status: the state of the response from the appointment system
  • Response time: how long the query took, which separates a card error from a slow service
  • Source: where the query came from, for example the security terminal

Sample split of lookups without results by cause (example calculation)

Sample split of lookups without results by cause (example calculation)Pie chart: 40 percent completed transport, 30 wrong code, 20 slow service, 10 otherCompleted transport: 40 % (40%)Wrong code: 30 % (30%)Slow service: 20 % (20%)Other: 10 % (10%)100%Completed transport40 % (40%)Wrong code30 % (30%)Slow service20 % (20%)Other10 % (10%)
Source: Example calculation: an assumed split that illustrates the method of analysis, not client data

Four sources of a seemingly inactive card

Once the trace is collected, a report usually breaks down into several different causes. Each one requires a different action and a different addressee.

Leading zeros and code format

The card lookup goes out with one canonical five-character code. Security typing leading zeros does not change the result, so this cause is ruled out at system level and there is no need to look for it in operator habits.

Delivery already completed in the appointment system

A delivery with a completed transport in the appointment system is deliberately treated as missing data. The external system can return the last completed transport for unknown codes, which would risk wrongly identifying the driver and breaching GDPR. For security it looks like a card that does not work, although the system behaved as designed.

Slow or unavailable SOAP service

The integration with the appointment system runs over SOAP. The response time in telemetry shows whether a missing result was caused by a timeout on the service side. Such a pattern belongs to the appointment system vendor and is a concrete piece of evidence for them.

Wrong or non-existent code

A code entered with a typo, or taken from a card of another plant, will never find a record. Telemetry then shows repeated codes without results from the same terminal, which points to operator training, not to a fault in the cards.

How to talk to the vendor using data

Good practice is to prepare for the vendor a summary of one period: number of lookups, share of results with data, share of no-data and error results, and the median response time. Such a document shortens the conversation, because instead of asking whether the cards work, both sides discuss a specific category of errors.

In a dispute it is worth agreeing with the vendor on a shared vocabulary: what no data means, what an error means, and what a completed transport means. Without this, the same number can be interpreted in different ways. Agreements are recorded in the implementation protocol, so they do not come back after people on either side change.

The lookup record contains card codes that may be linked to delivery data. Access to telemetry is limited to the people responsible for diagnostics, and the retention period is agreed with the customer's data protection officer.

Conclusions for the plant

Telemetry does not fix the appointment system, but it changes the nature of the dispute. Instead of the statement the card does not work, a specific category appears: operator error, completed transport, slow service or wrong code. This allows the report to be directed to the right person and the effect of a fix to be measured.

InnerWeb is an independent system that complements the customer's existing systems, so its telemetry can serve as a neutral witness for both sides. It does not decide who is right, but it provides evidence for the conversation.

Video

Frequently asked questions

Does the telemetry also show failed lookups?

Yes. Every lookup by card code is recorded with its result and status, so attempts after which no delivery was created are visible too.

Can leading zeros in the code cause errors?

No. The lookup goes out with one canonical five-character code, so zeros typed by security do not change the result.

Who should have access to the telemetry?

The people responsible for diagnosing the integration. The scope of access and the retention period should be agreed with the customer's data protection officer.

Sources

Turn the card dispute into data analysis

Let's talk about how a record of lookups can help your logistics team and your appointment system vendor find the causes of errors.

Let's talk