Trecerdo, LLC | 10/05/15 11:42pm
Sergio, I figured I can help here. Full disclosure: I ran panel firmware development at Mercury for many years and still provide consulting services to them. Before that, I was on the Honeywell Pro-Watch product team, a Mercury PACS head-end (the PW-6K and 5K panels are Mercury variants).
One thing to consider is what you actual metrics are. For example, the Mercury feature set goes well beyond what a typical site might use. I suspect that each Mercury OEM partner implements maybe 50% of it, but the partners all choose a different 50%. For example, while everyone will implement the core access control functions, not everyone will implement the native intrusion features, asset tracking, fancy trigger/procedure logic, and so forth.
A "feature implementation count / partner" matrix wouldn't be helpful, so all other comparisions are going to be subjective. Also, different partners have different strengths in different verticals and markets, and have implemented the features that best suit them.
That said, S2 is a first-rate organization with good talent. John Moss is a legend and has built [another] excellent company at S2.
I hope this helps. I am more than happy to help your further offline, if you like.
As years of experiance go by, I find it more important to ask lately is "who has their own team of developers for custom integration work" when evaluating manufacturer products. Maybe not important in your case, but I think something to consider.
Johnathan. Could one conclude that if its a Mercury box, then it can be used with any Mercury-using manufacturer? What are the considerations when selecting a Mecury Partner that one should look for when selecting a Mercury based system? Point its, if a company dumps my favorite integrator, what do i have to know to get another manufacturer to who can talk to my controllers? Does the firmware need to be replaced or flashed. If so, does it mean we have to go to each controller?
IPVMU Certified | 10/06/15 03:58pm
For gross hardward interoperability among major EAC brands, see Axis vs HID vs Mercury Access Controllers and specifically this chart:
Hardware is interoperable, but as Jon and others note, it does not mean the software integration is equal. Even though they both use Mercury Security hardware, features in platform A may not be available/supported in platform B.