Speaker B breaks down why IoT projects lose money: vendor lock-in through proprietary drivers, private cloud gateways that route through AWS, and hidden double-billing where you pay both the vendor and the underlying cloud provider. Data gets trapped and costs spiral.
So, so tell me a little bit about your perspective on that article and, and what, what it is you're seeing, because nobody wants negative ROI. What happens when— what's the causes of that and how can you avoid it?
Yeah, yeah, great question. I think this was kind of motivated by the, the decades of what I'll call vendor lock-in, right? I think when you look at something like, um, and all of them do it, right, not to just pick on one, There's always been this value of ease of integration with their drivers. You could have an add-on instruction or a GSD file. And for those unfamiliar with it, it basically means you're going to have a few clicks. And I mentioned the Excel spreadsheet comparison to PLCs earlier. And so they were able to kind of have this locked ecosystem where you click add device and it neatly kind of labels all your data for each row, and then you're able to get a much easier understanding of it. And so that kind of— I'm recognizing with a lot of these different smart solutions, they may have a proprietary gateway vendor that they're doing where, hey, these sensors only communicate with our gateway, and then it goes directly to our private cloud, and then from there we can port it to AWS, and then from there we can port it to whatever your system So now that private cloud is usually hosted in AWS anyways, so you're paying twice to get your data to someplace that doesn't always make sense.
