Results **********
*** ************ ******** ** *********** ******** they '*****' ** ****** *** ****.
****, ******* ***** ******** ** * replacement ** *******, **% ** *********** answered **** *** ******* **** **** they *** ****:

**** *** ****** ******* ** ******* for **** ********:
- **** *** ****** ****** **** ********* and ** *** ********* ** *********** outside ** ****-********/ ********** *******.
- **********'* ********* ****** ******* ** *** support ****.
- **** ***** **** **** ******* *** the ******** *** ******* ** **** a ******.
- ********* *** ***-***** ***** ** *** understand ** ****'* ******** **** ****.
** ***** **** ** ***** **** in ******** ******** **** ********** ***** comments *****.
OSDP ******* *****
******, ******* **** ******** ** **** enough, *** *********** ** ****** ********* may ** * ********** *******.
****** ****'* **** ******* ** **** its ********* *********, *********** ******** *********** (***), ** *** **** ***** ***** end ***** *** ***** *********** **** other ******** ****** *********, ******* ** ****, ****, *** Bosch *** *** ***** ************.
**** *** *********** *******, **** ** an **************** ******** ******* ******* *** controllers. *******, **** ****** **** ************ like ************* *************, '****** *******' **********, and *-*** ********* ******* *** ********* with *******.
*******, ******* *** **********, ********** ******** make ** ***** **** **** ******** is *** * **** ***** ** access, *** **** ** **** **** place ** ******* ******, ** ******** segments ** *** ****** *** ********* of *******'* ******** ***** *** *** necessarily * ******** ****** *** ********.
For ****, **** *** ****
*** **** ******** ** *********** ******** they ****** ***** *** **** *** stick **** ******* *** ** **** of ******, **** ** ********* *******, and ** ************** ********* **:
- "**** **** **** ****. *** ******** haven't ******** *** ****** ***. **'** most ******** **** *******."
- "*%, *** ** **** ** ******** to ** *** *** **** ** customers ********** **."
- "****, ** ******"
- "*%. *** ****** *** *** ********* since ******* ** **** ********."
- "****. **** *** ******** ** *** OSDP *******."
- "****** ****** ** *** ***** **** on *****/*** *********. ******* ********** ********* as *** ***** *** *** **********."
- "*%. ******** *** ******** ** *** installing ******* ** (***), ** ** not ******* **** ********."
- "*% ** *** *** ****** **** types ** ******* ***."
- "*% ** **** *****'* ******** **** option."
- "*% *** **** **** ***** ********* with ******* ** *** ******** ****** for *** *** ********** ******** ******* and ******"
- "*** ** *** ***** ******* ** consultants."
- "*%. ** ** *** ********* ** me."
- "****, ** ***'* *** *** **** reader *** *** ****** *******, ** are ******* ******* ** *** ******* for *** ****** ******* ********."
- "*% ** *** *** **** ********** at *** ******."
- "*. ** *** *** **** **."
- "*%-*** ****** ********/*********/******** ***"
Not ********* ** ****** *******
** **** ** ***** **** **** is ****** *** ****** ********* ** Wiegand ** ****** *********.
***** *** ******* ****** *************** ********** **** ** *******, ***** *** ***** *********** **** in ******* **** ******* ****** ***** limited ** *******:
- "*% *** ********* ** *** *** AC ****** *** *** ***** ** all."
- "****. ** ****** *** **** *** Paxton *********."
- "*% ** ****** ** **** *** DMP ***** ***'* ******* **. ** are ******* ***** ** **** ** out ** * *** *** ********* on *** *** ***** *** *****."
- "***** **** ******* * ** ******* that **** ** ********* *** *** Security *** **************** ** ****** ******* Systems. *** **** ************ * *** is ****** *** **** **** ******* Wiegand."
- "****. *** ****** ******* ** *** offer ** *** ** *** ********."
- "** *** * ***** ****** ******* of ****** **** ******* **** **** specifically ******** **** **** *** ***** not ***% ****** **** ***** ****** phases ******* *** ***********. ** * practice ** *** ** ******* **** on ****** ***** ********."
- "**** ******* ** *** ******* **********"
- "*% ******* **** ****** ***'* ******* OSDP."
- "*% *** *** **** *** **** such * ******* ***. ******."
- "*. ****** ******* ******* ** *** does *** ******* ****."
- "******* ** ***** ********* ** *** industry. ** ** **** * ****** of ***********."
- "*** **** **** *** **** *** OSDP ******* *** ***** * ****** - ** ****** ****** ****** ** the **** ******."
- "**'** ****** ***** ** *** *****, but ******** ******** ******* ***** *** weigand ** */**"
** ****, **** ****** *** ********** must ******* **** ** ** ***********, a *** ***** ** ******* ** our**** ****** ******* *****.
Do *** ********** ****
******* ***** ** *** **** **** end *****, ****** *******, *** ********** do *** ********** *** ********* ** OSDP. *** **** ** ************* ** a ******* ** ********** *** ******** to ******* ******** ***** ** ***** it ** ******* *********** ******* ****** and **********.
*** ******* ******** *********** ****:
***** **% [*** ****]. ** *** to ****** *** ******* **** **** security ** **** ** * ******* standard, ****** **** ** *** ********* are *** ** ********** ** ** enough ** **** ** ********* ** their ****. ** **** *** **** few ******** ********* ***** *** ********** between *** ****** & **********. **** of *** ********* ** *** **** that **** ** ****** ** ******.
*******, **** ********* *** *** ******* reason **** *****:
- "* ***** *** ** ** *** being **** ******* ** ********. **** few **** ***** ** ***/** ********** the ********. *** **** ********* ***'* know ***** ** ** ***'* **** it."
- "*** ****** ******** *** *** ***********, not ****** *********** *** ********* ** change ***** ******. *******, **** ** a **** *** ** **** *** next ****."
- "[*** **] ******* *** *** ********** yet. ********* **** ****** *** **************. Wiegand ***** ********."
- "*** **** ****** *********** ****'* ********** it **** ****."
- "** ** *** ********* ****** *** familiar **** *** *** * ***** we ****** **** **** ** ****."
- "*** ********* **** ******* ******* **** we *** ********* *** ******* *** OSDP ** *** * *********** ***. Will **** ** ** ** ** some ***** ******."
- "** **** *** *** ********* ***** OSDP. *** ****** ** **** ******* that ** **** *** ***** *** ready *** **** ********. ***** ** still * *** ** ********* *** market."
- "** **** ******* ***** *** ******* vulnerability ***** **** **** *** ** informing *********"
- "*********** ** ***** *** *** *****. Have ** **** ** ** ********. Sad **** *********** *****'* **** **** what **** **"
- "*** ****** ********* ***** ****."
*** ***** ******* ** *** ******* structure *** ******** ** ****, **** published**** ****** ******* ******* ******* *** ***** *********** ******** to *******.
Extra ****, ******* *******
******* ************ *** ** *** **** OSDP ********** ***** **** **** **** their ******* ************, **** ****** *********** that ********** ***** (**: ****** ******* costs) *** ***** ****** ** ***** the ******** *** ***, *** *** for ******* *******:
- "** **** *****, *** ********** **** of **** ******* ***'* **** ** being ***** *** ********** ******** ** provides."
- "**%, ******** ** ********* **** ********* the ***** **** ******."
- "************ ******** **** *** *********. ** educate *** **** *** ******** ** utilizing ** *** ******* *** *** investment ** **** ******** ****** *** bottom **** ************* ** ****** *******."
- "* ***’* ***** * **** *** into *** ****. ****** **** ******* and ******* **** ** *** ******* are ******** ******** *** ***** ****** not ** ************ ***** ** ****** out ******* *********."
- "**** ** *** ******* *** **** expansions ** ******** ******* ** ********* where ****** ** ********** *** ** want ** ******** **********. ******** *** the **** ********."
- "**% ** *** *** ******* **** had **** ***** ******* *** ** higher **** ** **** ******* *** customer ********* ******* ******** **** **** budget."
- "** **** ***** ********* ******* **** used ****. ** *** ***** ** the ********** *** *** *** ***** use ** *** ** **** **** not *** * *** ****** **** customers *** ** ** ** *** of *** *** ** ***** ***** it ** ******** *** *********** *** engineers. ** ***** **** **** ******* is *** **** *** *********. ** are ******* **** ****** ** *** customers ** **** ***** ****** *******."
- "****. *** ** * **** ********. Not **** ** *** **********. ***** able ** ***** ***** ******* ***'* helpful ***** *** **** ** *** all *** ***** ****** ** *** door."
- "********* ****** ** **** ***** *** use *******."
***** *** **** ********** ** ********** in *** **** *******, **** ************* like *** *** ******* *********** ******** the **** *** ****** ******, ***** manufacturers ****** * ******* *** ****.
*** *******, ** ************ **** ****** ****** ****, *** **** ******* ** ****** cost ~**% **** **** *** ********** Wiegand *****.
Heavy **** *****
*** ******* ********* ******** ** **** OSDP ********, **** ***** ********* ***** it ** ******** ** '**** ********' applications*** ********** *** ************* *******.
************, ******** ********* ** *************** ********* ************ ******* **** *** ******* *** bulk ** ***** *************** ******* ** 'regular' ********** ******:
- "** **** ***** ** **** ** the *******. *****, ** ** **** secure. ***, *** *** ******* ****** is ******* ** ******* ******* *** additional *******. ***, ** *** ********* a ******* ********** ********** *** **** is ******** *** ***** **********, ** least ** ***** **** ** *** show **** *** ******** ** ****** some ******/******** ** *** ***** *********."
- "**** *** ****** ***** **** **** centers. **** *** ***** ***** *******."
- "** **** **** ***** * ***** Government ************ **** ******** ****-** **********. This ******** *** *** ** ****."
- "******** ** *** ******* ********* ***** cloning ** **** *****. ******* ****** educated *** **** *** ********** *** security ******** ******* ** ****."
- "***%. **'* **** **** ******."
- "** *** ** *** *** *** Customers *** **** *** ***********"
SIA ********
** ****** ***** ******* **** ***, the ******** ***** ************ ****, ****** '**** ***** *** *** and *********** ******* ****** ** ******* OSDP *** **** *******?' *** '**** does *** ******* *** *********** ** educate ***** ********* ** ****?'
**** ************ *** *******, *********** **** OSDP ********* ** * ********* *** group ** ********* ******* ** *******:
*** ********** *** **** *** **** education ** **** *** ********** *** implementation ** *** *** **** *************.
*** **** ******* *****, *** *** Member ********* **** ***** ******** ***** to ******** *** ****** ** **** education ****** *** ****** ******** ********* (manufacturers, ***********, *********** *** *************).
*** *** ****** ********* **** ********* and ****** ************ **** *** **** 18 ****** ** ******** **** ********* through ********, **** ******** ** ********** and ***********, *** ***** *********.
*** *** ********* *** *** **** Boot ****, ******** ** **** **-*****, hands-on **** ********* ** ***********, ************* and ************ ********. *** **** **** Camp **** ** ********* *** ***** October **** ** *** *******, *** the *** **** **** **** ****** will ** **-******* ********** **** * number ** ******** ****** ********** *** rest ** *** **** *** ****.
*** ** **** ** *** ******* of ********** **** ******, **** *** free ***** ************* ****** ******** ** help ************ **** *** ****** *********** between ********* **** *** *******.
***** ******* *** ** ******** ** the ****** *** *********** *** ******* events ** *** **** **** ******** the ******** ** *** **** *** promote *** *** ** ******* *** OSDP ************** *********** ** *** ********* that **** ****** **** ** ***** access ******* ********.
*******, *** ****** **** **** '****' education ******* *** ***** ** ***********, and ***~$*** **** **** *********** **** ** *** * ********* option *** **** ****** ********** *** specifiers.
*******, ** ***** ** ****** **** than * ****** ****** *** ******, OSDP ********** **** ** ****** **** effective ** ************* *** ********* ****** specifiers ** *** ********** *** ********* implementations.
Comments (25)
Undisclosed #1
Great writeup!
Only people who work in specific verticals seem to be comfortable with the nuances that exist with OSDP. This permeates beyond only integrators and specifiers: even cable manufacturers seem to struggle with a composite access control cable that doesn't have a 22/6 shielded cable.
The risk in broad adoption currently lies with the integrator. Adopting the change in standards becomes an education effort for a sales team, an engineering team but also every technician. Integrators run risks in labor overage when working within the unknown - and right now the end users are not providing the demand for them to do so.
I had to become comfortable on it by cutting my own teeth. Integrators are not going to risk the extra labor in implementing a new technology when the end user doesn't feel like they have much ROI. Yes, it is the same cost... but not when integrators need to fork over extra labor to learn on the job.
Create New Topic
Scott Fischer
IPVMU Certified | 07/09/19 06:24pm
Thanks for posting! As a consultant and end-user, I have spec'd OSDP v2 (with SCP enabled!) in multiple access control installations since mid-2018. We have used three different integrators; however, I have yet to see anyone successfully set up the system to include properly configuring OSDP. We have worked closely with the manufacturers to develop compatible specifications and even included manufacturer-provided part numbers to facilitate ordering the correct equipment.
We have been told "the wrong part was shipped", "the technician was not familiar with the technology and threw away a critical piece", "the reader is bad", and "it is set up correctly" (even though the system clearly shows OSDP and/or SCP is not active).
With these issues, OSDP installations must be frustrating for the integrators since they have to re-order parts, send technicians back out to the site, and overall significantly increase their costs in an effort to get the systems running. It is also extremely frustrating for an end-user who wants to install a system that will be able to take advantage new capabilities as manufacturers continue improving their implementation of OSDP.
Create New Topic
Undisclosed Integrator #3
What is it with osdp that makes it so much more labor intensive to setup?
Create New Topic
Undisclosed #4
How about going with server based mobile credentials and just get rid of most of the readers, reducing cost and complexity. It's out there and it works.
Create New Topic
Nathan Adams
If you ask these same integrators how often they change default user names and passwords for their clients you will likely get the same percentage responses. This is a matter of taking it upon yourself as a security professional to educate the customer. If they then reject the technology because it would raise the total price of the project by 1% then that is their prerogative. But most of these excuses sound like lazy integrators who wont adopt higher security standards until they are forced to.
Create New Topic
Salvatore D'Agostino
Not sure if you know about this effort https://osdp.equipment/
Create New Topic
Salvatore D'Agostino
Thanks Brian, don't always click through, . Sure there is more Wiegand than OSDP in the world and the deployment of OSDP is still uneven I think the point is that it is an option from a sufficient number of vendors and its security and communication capabilities make it more common with enterprise class customers. The economics should be in its favor across use case, fewer wires, remote update, reader competition, nice to see some comments here back and forth.
Create New Topic
James Talmage
We're doing our first OSDP deploy next week (six of em).
For us, the motivation is cost savings on doors with entry and exit readers. OSDP allows you to daisy chain multiple readers on a single mercury card reader port. $60 more per reader * 2 readers, is well less than buying a second MR-50 (same for 4 readers and an MR-52).
And, it all really seems like an intentional software limitation. OSDP would allow for far more than two readers per port, and with the number of available inputs and relays on an MR-52 there's no good reason it couldn't handle 4+ doors (with entry and exit readers on each).
Create New Topic
ROBERT VERHULST
As a consultant, I refuse all Wiegand interfaces. Even when cabling is well protected it does not give any information on the state of operation of the reader and has to be avoided.
Create New Topic