Overlapping functionality for sure. I think the primary difference is that there's not stock MES built into something like kepware, which keeps a large number o

Overlapping functionality for sure. I think the primary difference is that there's not stock MES built into something like kepware, which keeps a large number of smaller manufacturers from using it. An API on its own is useless to them. OPC (UA) is one of the protocols we offer as an endpoint, but to be honest I think OPC (again, UA) is too complex for most use cases. It's a good protocol, but there's not enough tooling built up around it yet, and it's very much geared toward large enterprise. Not to mention the saga of legal issues it just escaped from. We also offer an HTTP API which uses swagger and swagger UI for documentation and testing, and normalize data across machine types before storing it in a database. This allows a company to grow from our opinionated MES into their own customized system as they grow. Additionally, we offer two way integrations with ERP systems. There are some other common interconnectivity applications required by most of the manufacturers we work with (we've been doing services for a long time and have 1000+ active service customers). These are not commonly covered by OPC servers, but are covered within our software.