InnerWeb
Skip to main content

Reader replacement plan: 7 recommendations for the head of security

A reader replacement without a plan ends in a queue at the gate during a shift. The head of security can prevent this by writing down recommendations before ordering work from the access control vendor. Below are seven recommendations for the planning stage of gates and doors.

7
recommendations to write down before ordering
Source: sample plan
23%
share of external contractor cards in the sample fleet (300 out of 1,300)
Source: sample calculation

Who this plan is for

These recommendations are addressed to the head of security at a production plant that plans to order an access control reader replacement and wants to keep passage continuous across shifts. For the sample calculation we assume a plant with 1,000 employee cards, 300 external contractor cards and 20 readers at gates and doors.

The reader and card technology is supplied by the access control vendor. InnerWeb's role is limited to software: InnerWeb does not manufacture or replace readers. It only receives punches from the access control system and links them to working days.

Recommendations 1 and 2: know the current state and justify the replacement

Recommendation 1: before ordering, list which readers are on gates and which on internal doors, and which technologies they support. Without this list the vendor's offer will be an estimate.

Recommendation 2: record the reason for the replacement. 125 kHz cards such as EM4100 or HID Prox transmit a fixed number without authentication, so copying them is cheap. MIFARE DESFire EV2 and EV3 cards use AES encryption and mutual authentication. The OSDP protocol with Secure Channel encrypts communication between the reader and the controller, unlike Wiegand, which sends data in clear. A written reason makes the later acceptance easier.

Split of the card fleet at the sample plant

Split of the card fleet at the sample plantPie chart: 1,000 employee cards and 300 external contractor cardsEmployees: 1000 cards (76.9%)External contractors: 300 cards (23.1%)1300cardsEmployees1000 cards (76.9%)External contractors300 cards (23.1%)
Source: Sample calculation: 1,000 employee cards and 300 external contractor cards

Recommendations 3 and 4: order and transition cards

Recommendation 3: replace readers gate by gate, not all at once. Start with the gate that has the lowest traffic and leave the busiest one for last.

Recommendation 4: during the transition period use dual-frequency cards, which combine a 125 kHz circuit and a 13.56 MHz circuit and work on both old and new readers. Write into the plan that security improves only when reading of the 125 kHz circuit is switched off at the gate.

Recommendations 5 and 6: entry and exit readers and external contractors

Recommendation 5: describe whether a gate has separate readers for entry and exit. Readers can be described in the reader dictionary, which allows the time recording system to recognise the direction of a punch. When the access control system does not pass the direction, InnerWeb pairs an entry with an exit in the software, with a limit of 13 hours between them, but it is better to have the direction from the hardware.

Recommendation 6: plan external contractors separately. Their cards make up about one quarter of the fleet in the sample calculation (300 out of 1,300), and their contact with security runs through a different channel than communication with the company's own employees.

Recommendation 7: evidence after the replacement

Recommendation 7: define the proof of acceptance. It can be a summary of punches at the converted gate for the previous and the current week, with the number of unknown card punches. In InnerWeb a punch from an unknown card goes to the "card to be assigned" queue instead of creating an account from an unknown punch, so this list is one of the acceptance measures.

The summary supports audit evidence that access control was working during the replacement. It is not a promise of compliance with any specific legal requirement.

Summary of recommendations and responsibilities

Below is the split of tasks between security, the access control vendor and the software provider. It prevents each side from assuming that the other party will perform a given task.

  • Security: the list of gates and doors, the order, communication with staff, acceptance criteria.
  • Access control vendor: readers, cards, controller configuration, export of cards to personnel numbers.
  • InnerWeb: receiving HTTPS POST punches, working days, reports, the queue of cards to be assigned.
  • IT: outbound HTTPS traffic from the access control server, the technical integration account.

Checklist

Video

Frequently asked questions

Should security choose the reader technology itself?

The choice of technology rests with the access control vendor and procurement. Security specifies the requirements: gates, traffic, direction and acceptance criteria.

Is OSDP required?

It is not required, but OSDP with Secure Channel encrypts the reader-to-controller link, while Wiegand sends data in clear. It is an argument to consider during purchasing.

Does InnerWeb replace readers?

No. InnerWeb is a software producer and integrates with the existing access control system.

Sources

Write the reader replacement plan with us

We will help define which punches and reports the time recording register must keep. Book a conversation with InnerWeb.

Let's talk