InnerWeb
Skip to main content

Anti-passback hard or soft: plant concept

The security manager of a plant working with several staffing agencies has to decide whether the first anti-passback stage should block entry or only record violations. Below is a deployment scenario for a production plant, with the order of steps and the place of InnerWeb in the whole chain. This is a concept, not a description of a completed deployment.

2 000+
card punches per working day at a plant with many staffing agencies
Source: unit card
Automatic
short-lived token, renewed automatically by the integration
Source: unit card

Starting point: a plant, three shifts and several staffing agencies

We describe a concept for a production plant where its own employees and people delegated by several staffing agencies work on the same site. Access control already works: cards, readers at the gate and at the hall entrances, and controllers on the side of the access control vendor. What is missing is a rule that makes sure the same card cannot enter twice without a registered exit.

Anti-passback is a rule of the access control system, not of InnerWeb. It runs in the controllers and the access control software, so the security manager decides on its mode together with the access control vendor. InnerWeb is an independent complementary system that receives card punch events and links them with qualifications, permits, attendance and location on the map.

Three variants of the rule and what each means at the gate

Hard anti-passback blocks entry when the system has no recorded exit for the same card. Soft anti-passback does not block: it lets the person through and records the violation in the report. Timed anti-passback releases the card after a set time, even when no exit was registered.

The difference has organizational consequences. Hard mode gives the greatest control, but every data error ends in a queue at the gate, because someone has to unblock the card. Soft mode is safer for the flow of a shift, but it requires someone to read the report every day.

  • Hard: entry blocked, manual unblock by security
  • Soft: entry allowed, entry recorded in the violation report
  • Timed: card returns to circulation after the set time

Events to resolve per day at 2 000 punches

Events to resolve per day at 2 000 punchesBar chart: at 2 000 punches per day, a violation rate of 1, 2 and 3 percent gives 20, 40 and 60 events per day respectively0204060events1 percent: 20 events20 events1 percent2 percent: 40 events40 events2 percent3 percent: 60 events60 events3 percent
Source: Sample calculation: 2 000 punches per day multiplied by the assumed violation rate

Concept recommendation: soft mode for the first stage

In a plant with several staffing agencies we recommend starting with soft mode on selected passages. The reason is practical: in a plant of this type, card traffic can exceed 2 000 punches per working day, so even a small share of direction errors gives several dozen events a day.

In hard mode each such event is a person stopped at the gate at the start of a shift. In soft mode it is an entry that a security officer resolves after the fact. During the first weeks the report will show whether the problem lies with people (borrowed cards, entering behind someone else) or with equipment (a reader without direction, a read time that is too long).

Only when the violation rate drops to a level that security can handle manually is it worth switching selected passages to hard mode, starting with the zones of highest risk, for example the entrances to production halls.

Technical condition: the passage direction must be known

Anti-passback has nothing to work on if the readers in both directions of a passage do not report the direction, entry or exit. This is the first thing to check with the access control vendor before anyone enables the rule. A missing exit reader on one of the gates means that every exit through that gate will be seen as a missing exit.

It is worth listing all passages in a spreadsheet: gate name, entry reader, exit reader, rule mode, parent zone. Such a sheet later becomes the basis for the conversation with the vendor and for reconciling the report.

How the report and the punches reach InnerWeb

The integration point is the card punch webhook: the access control system sends an HTTP POST request to InnerWeb on every punch. The call is authenticated with a short-lived token, renewed automatically by the integration.

A card punch in the access control system only says that a person passed a point, not where the person is after passing it. Linking it with the location on the map and the evacuation list is the added value of InnerWeb. The integration specification requires the access control system to send events in real time, with the reader event time, the direction entry or exit, and an event identifier. The rules for pairing entries with exits and for rejecting duplicates are agreed with the access control vendor before deployment.

The anti-passback rule and its violation report therefore stay in the access control system. In InnerWeb the person's presence, their entry verdict and their location appear, which lets the security officer check the context of a violation without switching between three screens.

Order of steps in the scenario

The order below limits the risk of stopping a shift and provides the data for the decision to move to hard mode.

  • List of passages and reader directions agreed with the access control vendor
  • Soft mode enabled on selected gates
  • Daily review of the violation report by the security officer for four weeks
  • Splitting violations into people errors and equipment errors
  • Removing equipment causes and training the staffing agencies
  • Moving selected zones to hard mode with an unblock procedure
Example calculation

How many violations must be handled per day

Assumptions
ParameterValue
Punches per working day2000 punches
Assumed violation rate at the start2 percent
Time to resolve one event3 minutes

Result: 40 events per day and about 120 minutes of security officer work per day

Note: Sample calculation with explicit assumptions; at a specific plant the rate should be measured in the first weeks of soft mode.

Video

Frequently asked questions

Does InnerWeb switch anti-passback on?

No. The rule works in the controllers and the access control software. InnerWeb integrates with the existing access control system and receives card punch events.

Is hard mode always better?

No. It gives more control, but every data error stops a person at the gate. In the first stage in a large plant, soft mode is safer.

Does InnerWeb record the passage direction from the punch?

Yes, if the access control system sends it in the event. The integration specification requires the reader event time, the direction and an event identifier; the details are agreed with the access control vendor before deployment.

Sources

Let's plan the integration with your access control system

We will go through the list of passages and the punch format with your security team and the access control vendor, so that the first anti-passback stage does not stop a shift.

Let's talk