Conversion From HID Thinline Readers /Iclass To HID SE Readers/Seos With OSDP

Notionally it meets requirements, but distance is not given. Do the controllers also support OSDP?

By default you can still transition to SEOS technology using weigand communications. Next you can ROM the cost to the customer in order to update to controllers that support OSDP. That's if your access control system currently supports it. I cannot speak for the integrity of the existing cabling infrastructure you are dealing with, however you can mock up the OSDP capable controllers and field test the OSDP communications over the existing, presumed 22/6 OAS cabling. Use the longest available distanced doors in your testing and in most cases you should be fine. Many integrators that have re-terminated readers such as the RP40 using the OSDP terminations on legacy cable have done so without no issue. On future installations, use the correct twisted pair cabling.

Exterior card readers, most people just drill these into the mullion or somewhere on the outside of the glass or exterior surface, since HID has been hack-able for ages I have always tried to install card readers on the inside(behind glass if available) to mitigate tampering with the known BLE key hack.

Cheap customers.....well here you have customers that only want to upgrade the exterior readers and leave the interior on legacy weigand 26bit. I just want to slap these customers.

Elite key or no elite key. This could be a lock in, however the additional layer against duplication is nice to have on paper. It all depends on the application and what these particular card readers grant access to. Doors with Elite keys(matched reader, paired cipher/bit) should never have basic janitorial access, installer access or anyone, just the select few. If you are still concerned at this level then you need to go FIPS, PIVclass or TWIC, CAC and just freak everyone out.

Long story short. All access control systems need to rid themselves of HID 26B get hacked format or, do not call themselves an access control system. To help enlighten my frustration, take MERCURY panels, why don't they just incorporate firmware that does not decode any known hack-able technology? Do that and you fix all the lazy access control software companies too scared to enforce SECURITY.

There are a dozen other considerations to be able to give any real direction on your project as a whole, but I would say without hesitation that the cable you have currently will be sufficient and then some to support OSDP. Connecting an HID iClass SE reader with OSDP requires only a total of 4 wires -- 2 for power, 2 for data. Additionally, the distance capabilities for OSDP communications far surpass what Weigand can do, so anything that currently works over Weigand is -- at least conceptually -- almost guaranteed to work as OSDP.

All beeper and LED functions are controlled via the OSDP communications between ACS/panel and reader, so no additional beeper/LED wires are required.

As a sidenote, since you will automatically have a spare pair of wires, I would suggest connecting one of those wires to the tamper outputs on the readers. While this may be redundant depending upon the system/controllers you'll be connecting them to, it guarantees you can receive tamper alarms in the event that whatever platform you use doesn't support the OSDP tamper alarms.

We are currently getting ready to do this to a site. However we are also fork lifting the existing Mercury series 1 and 2 boards out and putting in all new series 3 and "X" controllers to take full advantage of true encryption from reader to database. Cabling wise we are still just going to run the standard reader bundle where there was old non bundled cable to clean up the installation as well and because we are also moving panels to new locations. We are putting in the SEOS readers w/Bluetooth and SEOS cards. The customer isn't using the Elite key however. 

I agree with U2 about putting the exterior readers inside for the Bluetooth portion. Not because of a hack but because the Bluetooth module does not hold up very well in the elements. Let me rephrase that part. Normal rain isn't an issue but if the reader gets a direct water splash down the BLE module will short out the reader. Installing the reader behind glass is great for the BLE portion but no so good if the customer is still using cards due to the read range of the iclass signal.