InnerWeb
Skip to main content

Card tap events from airlocks to InnerWeb: notes for the vendor

The plant's integrator and the access control system vendor often ask what exactly the access control system should send to InnerWeb, and what InnerWeb does not do. Below are implementation notes: the scope of the webhook, the division of sources of truth for the event and the limit of responsibility, including the fact that we do not produce readers.

0
readers produced by InnerWeb
Source: company fact: InnerWeb is a software producer
5
recommended fields in a tap event
Source: example calculation: recommendation from the section on the scope of events

Who this text is for

For the integrator running the implementation at the plant, and for the access control system vendor who will configure event sending. The text describes the integration model, not the technical specification of a particular product: fields and format are agreed individually with the vendor and the plant team.

The boundary: what InnerWeb does not do

InnerWeb is a software producer and does not produce access control readers. It integrates with the client's access control system, receiving card tap events by webhook and linking them with qualifications, permits and attendance. The plant therefore does not replace cards, readers or controllers, and the access control vendor keeps its role: it is responsible for the devices, firmware, keys and their management.

This boundary is written into the implementation agreement, so that nobody on the plant side expects us to act on the readers.

Example: number of event fields versus the risk of discrepancies

Example: number of event fields versus the risk of discrepanciesBar chart: recommended set 5 fields, extended set 12 fields.02.557.51012.5fieldsRecommended set: 5 fields5 fieldsRecommended setExtended: 12 fields12 fieldsExtended
Source: Example calculation: illustrative figures; the plant sets its own set with the access control vendor.

The source of truth for the event

A card tap at the reader is a fact on the access control side. We accept it as it was sent: timestamp, card identifier and tap point, and the direction if available. We do not correct the event or conclude that the reader made a mistake. If the access control system recorded a tap and InnerWeb shows no reaction to it, we diagnose the difference on both sides: first we check whether the event arrived, then how it was linked to the person.

The event is then linked with InnerWeb data: qualifications, permit or visit, declaration and training. At a pharmaceutical plant, this is where the declaration gate adds the requirement to the tap: without a declaration, the system does not record the entry.

Scope of events to agree

Agree with the vendor on a short set of fields. We recommend: the card identifier (or its encrypted form, depending on card technology), the timestamp in an agreed time zone, the tap point identifier and the direction. More fields increase the risk of discrepancies and the network load, and do not improve the gate's decisions.

Also agree how repeated events are handled: the access control system may send the same tap twice if it does not receive an acknowledgement. On the InnerWeb side the declaration has one row per person per day, so a repeat does not create a duplicate declaration, but it is worth describing the behavior for all events in the specification.

  • Card identifier, or its encrypted form.
  • Timestamp and time zone.
  • Tap point (airlock, gate, door).
  • Direction, if the access control system knows it.
  • Behavior when the event is sent again.

Airlocks: entry, exit and direction

For cleanroom zones, an event from the reader at an airlock must say whether it is an entry or an exit. The declaration is required only at entry, and a person already on site can always leave. If the reader does not distinguish direction, the plant should install separate entry and exit points on the access control side; InnerWeb cannot replace them, because it has no readers of its own.

Acceptance tests and responsibility

Before go-live, the teams run tests on shared scenarios: a tap by a person with a valid declaration, without a declaration, with a visit, after an exit, and with a repeated event. Both teams record the test result. It is also good to agree who receives a discrepancy report first: we recommend the plant's integration owner, who passes it to the right side.

The EU GMP guidelines (EudraLex, Volume 4) include the chapter on personnel and Annex 1, in the version applicable from 25 August 2023. The access control system and InnerWeb do not change these requirements; they provide records that the plant can show during an audit.

Video

Frequently asked questions

Does InnerWeb supply readers?

No. We are a software producer and integrate with the client's access control system without replacing readers.

Who is the source of truth for a card tap?

The access control system. InnerWeb receives the event by webhook and links it with qualifications, permits and attendance.

What if the access control system sends an event twice?

Describe the behavior for repeated events in the specification. The declaration has one row per person per day, so no duplicate declaration is created.

Sources

Let us agree the integration with the access control vendor

We will prepare the set of event fields and acceptance test scenarios for a conversation with the access control system vendor.

Let's talk