OEM machines use legacy protocols like OPC and Modbus that lack standardized data mappings, forcing engineers to manually configure each customer integration. There's no universal way to connect machine data to cloud platforms, so every setup requires custom engineering work.
That's one of the main things I think that's still missing is not just standardization of the data, but also standardization of protocols or something around that so that machines that NOEM provide fit in. I'm not saying they don't fit in because, I mean, we're talking about, you know, 40 years of at least of technology that we've been used to, which is like OPC, Modbus, PROFIBUS, whatever. So data is available from every machine, right? It's just not It's just not— you can't just point to it and here it is, right? There has to be some workaround, especially like if it's not OPC, if you don't have a namespace that's exposed, you've got to now go look at documentation and figure out, okay, here's the Modbus map and here are the ports that I need to connect to and here's the addresses that I need to pull, etc., etc., right? So that's one thing for OEMs is what's the next step when you're talking about Industry 4.0, IoT, what is it that makes sense for our end customers? And it's not just OPC UA. Because again, yeah, our raw data is definitely something that's easy enough for our customers to pull if it's Modbus, OPC UA, or something else. But we get more customers more and more coming to us. We know you're pulling data up into your cloud, you're doing something with it, we want to get access to that. Mm-hmm. And that's, that's a, that's a tricky part. Because I mean, We could absolutely do that. And in most cases, we would have to engineer a solution almost per customer because they're all gonna be different. They're all gonna have different systems that they wanna utilize to connect to our system, to our data. And so we're missing that standard component that integrates an OEM back into their end customers.
