Who these recommendations are for
The text is written for the plant director, the purchasing manager and the investor who order an access control system for a new building or an extension. At this moment no cable has been laid yet, so the cost difference between protocols is at its smallest.
We do not discuss the choice of card or controller brand here. We focus on the link between the reader and the controller, because it determines the possibility of encryption, reader supervision and the number of wires in the trays.
Recommendations 1 and 2: choose OSDP and encryption
Recommendation 1: in a new facility, require OSDP rather than Wiegand. OSDP runs on an RS-485 link and is a bidirectional protocol: the command and the response confirm that the message was delivered. OSDP was adopted as the IEC 60839-11-5 standard in 2020, so you are ordering an open standard, not a single manufacturer's solution.
Recommendation 2: require Secure Channel. OSDP Secure Channel encrypts the communication between the reader and the controller with AES-128. Wiegand sends data in clear text, without encryption, and a credential can be copied and replayed, because the transmission has no authentication and no counter.
Wiegand vs OSDP: number of bundles for 8 readers (example)
Recommendations 3 and 4: supervision and cabling
Recommendation 3: treat reader supervision as a requirement, not an extra. An OSDP controller constantly supervises the state of the reader, which makes its disconnection or tampering detectable. With Wiegand, removing a reader without additional wiring does not raise an alarm.
Recommendation 4: count the cabling. On a single RS-485 bus, OSDP can run several readers in a chain, whereas Wiegand requires a separate bundle for each reader. The permissible cable length for OSDP is in the order of several hundred metres, and for Wiegand about 150 m. The values depend on the cabling and must be confirmed in the manufacturer's specification.
Recommendations 5 and 6: cards and keys
Recommendation 5: do not mix the decision about the link with the decision about the card. Moving from Wiegand to OSDP alone does not secure the card: if the card is 125 kHz or another unprotected technology, it can be cloned in front of the reader. When ordering a new plant, define the card technology and the reader protocol as two separate items.
Recommendation 6: plan the keys. Encryption protects the transmission, but security also depends on how the keys are protected, and with weak key management the system stays exposed. In the request, record who generates the keys, where they are stored and how a reader replacement is handled.
Recommendation 7: when Wiegand still makes sense
Wiegand may still be justified when you add a single gate to an existing installation and the controller does not support OSDP. In that case you reduce the risk organisationally: a short line in a closed tray, seals on the boxes, an inspection procedure.
In a new hall, Wiegand is chosen out of habit. If the vendor proposes it because of a lower reader price, ask for a total cost calculation including cables, bundles and the lack of supervision. The difference usually disappears once the number of wires and the future migration are counted.
Where InnerWeb fits in the chain
InnerWeb does not produce or replace access control readers. It integrates with the client's existing access control system and receives punch events through an HTTPS webhook. Changing the reader-to-controller protocol does not require changes on the InnerWeb side, as long as the access control system keeps sending events.
For the director this means that choosing OSDP does not tie the plant to a single software vendor for permits, attendance and working time. In the request, one requirement is enough: the controller sends punch events to an external system.
Checklist
Video
Frequently asked questions
Is OSDP expensive compared with Wiegand?
The reader itself can cost more, but a chain on one bus reduces the number of bundles. Compare the total cost including cabling, not the price of the reader.
Does OSDP protect against card cloning?
No. It protects the reader-to-controller link. A 125 kHz card can be cloned in front of the reader regardless of the protocol.
Does the choice of OSDP affect the integration with InnerWeb?
No, as long as the access control system keeps sending punch events. InnerWeb works as an independent system complementing access control, time attendance, HR and ERP.
Can OSDP and Wiegand be mixed in one plant?
Yes, if the controller supports both. It is still worth writing a migration plan so that Wiegand does not remain on the gates with the highest risk.
Sources
Are you designing a new hall?
Send us the assumptions for your access control system. We will help formulate the punch event requirements so that the system works with InnerWeb regardless of the link you choose.
Let's talk