Protocol and standard
Require OSDP version 2 with Secure Channel and name the version of the specification. OSDP was adopted as the IEC 60839-11-5 standard in 2020, and SIA OSDP version 2.2 aligns the format of the specification with the IEC version. Referring to the standard gives a basis for rejecting an offer that names the protocol without details.
Also ask for a certificate or a declaration of OSDP conformity from the manufacturer, not only from the bidder.
Encryption and keys
Write down that the readers must operate in Secure Channel mode (AES-128), not in installation mode. OSDP in installation mode sends data in plain text, so the offer should describe how encryption is enabled and how the key is exchanged in the reader and the controller.
Add a requirement that the key is different from the default one and that its handover to the contracting authority is part of acceptance. Encryption protects the transmission, but security depends on the protection of keys.
Division of requirements into thematic groups (number of items)
Reader supervision and cabling
The OSDP controller supervises the reader status continuously, which makes it possible to detect disconnection or sabotage. Require that supervision events are recorded and available in the system, with the reader address. Ask about the topology of the RS-485 bus and the number of readers on one line.
The permissible OSDP cable length is in the range of several hundred metres, and the values depend on the cabling, so the offer should state a length that the bidder confirms in the manufacturer's specification. One bus can carry several readers, so the offer should indicate which doors share a line.
Compatibility with the existing controllers
If the plant keeps the current controllers, the tender must include their model and firmware version, and a request for confirmation of OSDP support or a description of the interface. The lack of such information is the most common source of cost surprises after the contract is signed.
Require written confirmation from the access control supplier that the selected readers will work with the described controller.
Cards and integrations
Moving from Wiegand to OSDP alone does not secure the card: if the card is 125 kHz, it can be cloned in front of the reader. Ask therefore in a separate item about the card technology and about a reader that supports cards with authentication.
If the plant uses a system of the InnerWeb type, add a requirement that the access control system sends swipe events through an HTTPS webhook with the swipe time, the reader identifier, the person and the card number. InnerWeb does not produce readers and integrates with the client's access control system, and a change of protocol requires no changes on its side, as long as the events keep being sent.
How to use the list when assessing offers
Run the list through each offer as a table of compliant / non-compliant / unclear, and clarify unclear answers in writing before the price assessment. This way a cheaper offer based on plain-text mode does not win over a more expensive but complete one.
Checklist
Video
Frequently asked questions
Is it enough to write OSDP in the tender?
No. State version 2, Secure Channel and the IEC 60839-11-5 standard, otherwise the offer may cover plain-text mode.
How do I check compatibility with the existing controller?
Give the model and firmware version of the controller and request written confirmation from the access control supplier.
Should the tender ask about cards?
Yes, as a separate item. A 125 kHz card can be cloned even with an encrypted link.
What should be written about the InnerWeb integration?
Swipe events sent by HTTPS webhook with the time, the reader, the person and the card number.
Sources
Let's talk about integrating with your access control system
We will describe which events from the InnerWeb access control system can be received and how to connect them with permits, attendance and working time recording. We will propose a demonstration on your data.
Let's talk