Robert Martens4:31
Do you agree with that? And I think it's important to keep in mind we obviously have some advantages on the non-residential side of businesses, and that we have codes and we have some standards that everyone adheres to that you don't see on the residential side of security. That's caused a lot of the challenges. I think just an incredible number of standards and other pieces. So the way we approach it is kind of threefold, and we're improving, or at least I hope we're improving every day and trying to do it. And that is we believe that in order to be successful, you got to offer three things. One, you got to be secure. Okay, and I know I'm preaching to the choir here, but when I talk about secure, I mean both physical and digital. So a simple example of security physically is, hey, you know, if you have our lock maker like Allegion, you've got to perform against picking, you got to perform against kick-in attempts, all of those things like that. Digitally, what we're talking about from a security standpoint is protecting the information that may be in that device, but also preventing things like DoS attacks, denial of service attacks, or other elements like that, your cyber elements. So security is one. Scalability is number two. Scalability, giving examples again from a physical standpoint, scalability means things like cycle testing: how many times can I use that lever, use that lock before it's going to break down and not perform the way that it should? So that's scalability in the form of the physical lock. Scalability in terms of software, in terms of platforms and things like that, has more to do with how does it behave when you have 500 users versus 5,000 versus 50,000 versus 500,000? How well does it scale? And Lee, as you well know, depending on how you've architected your solution, how you built it, scale exposes small problems that then become big problems. So for example, if you have a small memory leak or something of that nature, that can be exacerbated in a massive way at that scale. And then last but not least, simplicity. We all get simplicity from the standpoint of interface. You know, when people walk up to a lever handle or something, they know intuitively to put their hand on it. What other types of solutions do we have? I would argue that people like Openpath and PinDrop and other Allegion Ventures portfolio companies are extremely intuitive. They understand that simplicity is terribly important for adoption. But simplicity also crosses over to your very point in terms of the digital UI/UX, the digital user experience and user interface that you're providing, and how simple is that. But if we take on those three S's — security, scalability, and simplicity — as an enablement platform, one of the things we want to do is when we're working with a partner like Openpath, is how simple can we make it for you to interface and integrate with us? That is our job. It's no longer about having proprietary exclusive platforms that make it so you're locked in. It's about how quickly can you do it and how quickly can you add value to not only the partner but more importantly the end user, the facility manager, the people that are managing those systems. So I think we're working our way out of this mindset of proprietary where I have more control over these pieces, and more to a value-added, value development mindset, which has everything to do with adhering to a little bit more open focus. We may not get to completely open standards, that's difficult to do, but I do think we can get to a mindset of 'I have to be the easiest partner and enablement platform for people to work with in order to be successful.'