S2 Founder Touts Mercury Board To Replace Software House

By Brian Rhodes, Published Sep 08, 2016, 01:16pm EDT

Access control is a stoic market typically devoid of glitzy, flashy product releases. But one new product is notable because of who is touting it and what it aims to do. 

One of the most well-known access control leaders, S2 Security's John Moss [link no longer available] said:

Will this help replace Software House? In this note, we examine the offering.

Software ***** *******

*** ****/************ ** ********** interesting ******* ** *** made ****** ****, *** ******* *** former *** ** ******** House, *** ** *** largest ****** ****** ******* brands. ***** ******* *** company ** ****, **** started ******* ******** ****** control *******, ** ********.

***********, ***** ******** ***** uses **** **************** **** ***********,** ******** *** ********* with ******* ******** ***********.

New ******** *************

** *******, *** ******** post ** ******* * new ****** *** ****' current ** ******* ** take **** ******** ***** systems, *** ******** *******. 

*** ** ****** ***** that ******* **** (********* John ****' **) *** better chase *** '*** ***' of ******** *****'* ********* base *** ***** ************ **** ** ********* ******** changeover.

New ******* ** ****** ********

* ***** ****** ** a ****-** **** ******* why ******* *** ******** this *** *******:

**** **** *** ***** and *********** ** ********** between **** ******** ** nearly *********. *** *****/****** connections *** **** *** same, ** *** ***** they ***** *** *********** **********, *** ******* ****** exchanging *** ****** *** each ***** *** ** quickly **** ******* *****.

*** *** '**' ****** hardware ** ******* ** scope *********'* '**' ******** ** ******** ** take **** ***-******* ****-***** systems.  *** ***** ********** is **** ****** *** old *********** ** ******** Commander ** ******* ******* systems, ******* *** ******* can ****** *** ***** actively *********** *** ****** deployed ******** ***** *-**** platform.

*** ** ****** ******** several **** *******, **** resembling ***** ******** *** using ******* ****** *** firmware *******. *** *** parts *******:

  • **-*** [**** ** ****** available], * ******* ********** replacement *** *** *-**** iStar *** ***
  • **-*** [**** ** ****** available], * *********** ****** interface ****** *** *** iStar *** ***
  • **-*** [**** ** ****** available], ** * ************ output ***** *** ********* the ***** *** **
  • **-*** [**** ** ****** available], ** * ************ input ***** *** ********* the ***** *** **

** ***********, ***** **** ****** *** the *********** ********** **** ** Software *****'* *-**** ********, regardless ** *******.

Same *****, *** *** ******

*** ******** ***** ******** those ******* ** ****** from ******** ***** ** buy *** ******* ********** boards. *** *** ******** Software ***** ********** *** component *********** *** ** reused. ******* ******** ** Series **:

*** ** ****** ********** *** iStar ****** ******* ******** form ****** *** **** “***************” change **** *** **** migration ** ******** ***** ****** infrastructure ** *** ********* ******* software ******* *********.

** ***** ******* ** Mercury *** ********* *** still ****** ** ** expensive, ******* ** ********* per **** ** *** Mercury ****** *** ******* software, *** ******** ********* equipment *** ** ********* disturbed **** ***** *** MS ****** ******** ** standard ******* *** *****.

Labor ******* **********

*** **** ******* ** using ***** *********** ****** could ***** *********** ** a **********, ** *** order ** ******** ** dollars *** *********, *** perhaps **** ****.  

******* **** ****** ********* recommend, *** ********** *** 'neat' ******, ********* ****** is ***** *** ***** to ***** *********** ****** before ********* **** * connector.  ****** * ********** point **** ********* ******, even ** ** **** or ***, *** **** wires *** *** **** enough ** ***** *** warrant ********* ****** ******* of *** ***** ** reach, ** ********* ********* splices.

*** '**** **' ************* of *** ** ****** means ************ ***** ** only * *** ******* per *****, ****** ***** if ************ ******** *** used.

More ** *********** **** ***********

*******, *** ***** **** of ******** **** **** a ******** ***** ****** could ***** ***** **** steep.

**** ** *** **** of ********** ******** ******** boards *** ** ******** by ***** ** ******, there ** ** ********* that * *** ******* based ******** ******** *** same ***** ** ************ that ******** ***** ********* does. ******* ********* *********** with ***** **** ****** like ******** ******** *** Exacq, *** ***** *********** and ******* ** ***** systems *** *** ** available ** * ******* OEM

Comments (28)

Been hearing about this board for about a year now and I thought I was chasing a unicorn. This is going to be very useful!

Are there other platforms in sight with this Mercury Bridge?

Maybe AMAG?

"In sight"?

You mean potential takeover targets with MS series?

In the case of AMAG; no. They use an altogether different board system than iStar.

Yes, meaning this strategy of creating drop-in replacements for other propritiery systems. Like an MA bridge.

Sure, I think Mercury could design other 'bridges' in the same way. But there needs to be a substantial installed base to justify it.

I don't think AMAG would make the cut. Nor would DSX. So once C-Cure is addressed by the MS Bridge, I'm not sure which other platform would be a target?

How about Lenel?

Lenel already uses Mercury, no?

Lenel primarily uses stock Mercury hardware. No special parts needed. See: Axis vs HID vs Mercury Access Controllers for more.

That's interesting, good find.

RS2 is supporting this MS bridge, not iStar. Their notation might confuse some.

The Vanderbilt support is due to the gradual migration of Vanderbilt access to Mercury Security firmware/hardware designs. Vanderbilt and Mercury are both owned by ACRE, who told us:

"All of Vanderbilt's platforms (including Bright Blue, SMS, ACT, Siemens, among others) will migrate to Mercury over time."

So since RS2 supports Mercury, it isn't too surprising to see them support Vanderbilt's hardware now running Mercury firmware.

Lenel has this same iStar takeover board. I think this more of a Mercury brain child than an S2.

Now if S2 would only remove the commitment to $75000 in annual sales, two technicians classroom certified and the purchase of a demo system. This could help smaller companies compete and grow. As a startup I am by myself until I can bring on employees, and would prefer to offer S2 over other PACS.

If I were a dealer offering Softwarehouse or any Mercury supported products I would look toward an access control partner that offers proprietary hardware to protect my company and my customers.

I would look toward an access control partner that offers proprietary hardware to protect my company and my customers.

Let me guess, you sell proprietary access control hardware? ;)

I definitely see how it could protect your dealer 'customers' but not sure why it protects the end user?

Within my current position at a large integrator, I have a number of customers that would love to leave. They are tied to this integrator because they are the only integrator that is a Dealer\Partner of 2 proprietary systems being used.

Still working on my exit strategy

Sell and own a Privately held access control manufacturer that does provide it's own hardware and software.

The current trend of the Mercury based systems is the fact that take overs are becoming more common. This places the end user in a position of power over the integrator. They decide to not pay the annual software support agreement they can simply bring in another provider to "Flash" the system and provide a new UI. Mercury itself admits that their hardware sales are not growing at the pace of their partners sales...This is a direct result of the above mentioned practice.

I think I would try to lock in the customer with great customer service, fair pricing and the correct product for their application.

Software House IS proprietary. The rub there is significant enough that a non-proprietary 3rd party has built retrofit hardware to fit existing installs.

So a 'proprietary' strategy is not absolute 'protection'.

S2 is also proprietary.

No. While they do offer their own controllers, S2 supports Mercury Hardware.

At the end of the day they are still proprietary. Yes you can use the Mercury controller, but what good is it when you not a dealer. You still cannot replace a SWH system with S2.

Genetec and Mercury promoting the Bridge product for takeovers:

Anyone know if these boards talk to RM-4 field modules?

Why aren't we talking about iStar Ultra vs. Mercury EP4502?  If we're going to make panel comparisons shouldn't we at least use the two modern panel designs?

 

Please share your recommendations for "two modern panel designs?"

Excellent article, I will work on this ASAP to rid my corner of the world of Software House and Lenel.

I would love to pickup S2 to take over Swh customers, but as a start-up I can not commit to S2 requirements. It's impossible as a 1 man start-up.

Read this IPVM report for free.

This article is part of IPVM's 6,741 reports, 909 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now
Loading Related Reports