Proprietary vs Non-proprietary Access Control Systems: A Comparative Analysis (Part 2)

Proprietary vs Non-proprietary Access Control Systems: A Comparative Analysis (Part 2)

The debate between proprietary and non-proprietary access control systems has been a contention within the industry. In an earlier article, we heard the perspectives shared by industry leaders IDCUBE , CoreWillSoft GmbH , Tapkey , Galaxy Control Systems , and acre security at The Forum at The Security Event (TSE) in Birmingham, UK. This article explores perspectives from additional industry leaders, Wavelynx , Comelit-PAC , and AMAG Technology , to comprehensively view the topic.

Robert Lydic of Wavelynx Perspective: The Evolution of the Industry

Rob believes that the industry started with proprietary systems and it worked...till it didn't anymore. As the market expands, we need more non-proprietary solutions that prevent lock-in. He warned that if our industry remains proprietary, it will not achieve mainstream acceptance, missing the opportunity to meet the market where it is and in a way it needs.

Steve Riley of Comelit-PAC Perspective: Functionality or Flexibility

Steve argues that the choice between proprietary and non-proprietary systems hinges on your needs—whether you prioritize functionality or flexibility. Additionally, he points out that proprietary systems might be necessary to keep up with technological advancements, as some standards are catching up.

Kyle Gordon of AMAG Technology Perspective: The Need for Standards

Kyle emphasizes the importance of standards. In his early days being in the industry, he believed he was selling non-proprietary systems, but he found out it was not the case. Kyle advocates for integrating with systems that align well with one's requirements. He also points out that the choice between proprietary and non-proprietary is both a technical and business decision and that market demand will drive the choice.

Ivan Kravchenko of CoreWillSoft's Balanced Approach (as shared in the prior article)

Ivan takes a balanced approach, supplying both open and proprietary technology. He argues that standards, like Bluetooth, can only partially support innovation, and proprietary technology is sometimes necessary. However, he also advocate for using open hardware to prevent vendor lock-in.

Key Takeaways

Choosing between proprietary and non-proprietary access control systems is not a one-size-fits-all decision. It depends on various factors, including specific needs, market demand, and the industry's stage.

The industry initially leans towards proprietary systems, but as the market expands, we will see an increased adoption of non-proprietary systems. However, proprietary systems that can offer functionality standards will still be prevalent and relevant.

Full stop: The industry needs standards. A system that integrates well with proprietary or non-proprietary requirements is crucial.

It's important to note that the choice between proprietary and non-proprietary isn't solely a technical decision; it's also a business decision. Market demands, differences between regions, and resistance to standards in the access control industry could influence this decision.

End users, who are ultimately driving these changes, are critical to this discussion. As technology evolves, we see changes in tech, readers, software, and many others at different speeds. Acquisitions are driving these changes, leading to various players in the industry.

The market is projected to accelerate from region to region but vary, with an expected total addressable market of 70 billion USD. The conversation is shifting from proprietary as a buzzword to a focus on standards. Ultimately, the choice between proprietary and non-proprietary systems depends on each stakeholder's specific circumstances and goals.

In conclusion, the debate between proprietary and non-proprietary access control systems is complex and depends on various factors. As the industry evolves, companies must stay flexible and consider both approaches to remain competitive.

The Access Control Executive Brief recently partnered with the Nineteen Group at The Security Event in Birmingham to host the X Forum, a thought leadership stage. Over three days, 32 engaging presentations were delivered by over 40 speakers from 35 leading global companies,?including 霍尼韦尔 , Brivo , HiveWatch , and HID . The forum adopted various presentation formats, encouraging a diversity of viewpoints on topics like trends and vertical market discussions. This successful event provided a wealth of content?to?be shared in depth in the Access Control Executive Brief and LinkedIn.

Steve Pineau

Chief Visionary Officer/CEO Gloocel Innovations Inc.

10 个月

This topic confuses me but perhaps someone could assist. Our company provides a different architecture called Direct to Cloud. With Direct to Cloud there are no readers, cards or control panels. The only credentials are mobile phones that connect to the cloud. The optional local hardware consists solely of computers designed with large numbers of Input/Output ports to send/receive cloud messages since these "controllers" host no data and don't make decisions. However, even though any software could be loaded on the "controller" we limit the ability of clients to do so since there is not much reason to run other programs or check email on an access control system. Does this make the system proprietary and how bad is that? Direct to Cloud is no threat to the big control panel companies and is probably too lowbrow for the larger integrators who post on these threads but I'd like to know in case anyone asks.

Mark Schweitzer, PMP, RCDD, CISSP, PSP

Transformative Physical and Technical Security Leader

10 个月

Lee, I think it's equally important to understand what some are claiming are proprietary vs open and the context. For example I know at least on PACs company that claims they are open because they use Mercury hardware. The same company though requires a very complicated process to be able to utilize approved methods to access data or interact with the ACS programatically. Compare that with another vendor who has a published API and allows anyone to programmatically interact with their PACS with need of any licensing or agreements. Which one is truly open?

Robert Lydic

President @WaveLynx | The leading expert in NFC Wallet Credentials for Access Control

10 个月

Grateful to be a part of the conversation with amazing people. Thanks for pushing the industry to have the conversations that need to be had.

要查看或添加评论,请登录

Lee Odess的更多文章

社区洞察

其他会员也浏览了