Eric - thanks for your input. I welcome your argument as to what makes Matrikon the better OPC server.
For the purposes of this post, you can probably expect users to be referring to OPC-DA as requested through FactorySQL (sorry - get’s back to my frustration with the usefulness of our product and HDA). For the record, I’m interested in hearing what you have to say on a different level.
Compliance and standardization are big ones. They’re the main reason that I generally throw out “Kepware” and “Matrikon” by name, but exclude the “little guys”, when a customer asks.
Configuration, communication options, and error reporting are also very relevant.
I would say that, although difficult to quantify, your caching and read/write aggregation algorithms are incredibly important as the system scales.
I welcome more info from Eric, Kepware, or other OPC Server vendors on the topic.