Came across this article on open standards not long ago. “Is our idea of “Open Standards” good enough? Verifiable vendor-neutrality” Can’t remember how I stumbled upon it, maybe a link from Gary or Jim? Either way, since it’s all about open standards, of course it got me thinking about how OPC measures up.
According to his bio, the author is a proponent for open standards, and the opening statement backs that up.
“Open standards are clearly a good thing. Hurrah for open standards, etc. Nail my hat to the ceiling!
But anyone who has been involved in community and consortium committees where there are commercial rivalries engaged knows that the thing that kills or corrupts a standard is when the spirit of mutual accommodation is overtaken by the spirit of competition”
I’ve been involved with many of the OPC specifications working groups, including OPC UA, and I can honestly say that the spirit of mutual accommodation is alive and well with OPC. I think one of the main reasons for this, is from the beginning the charter members were focused on solving the problem of interoperability, not trying to push any one proprietary standard to the for front. Too often ‘open standards’ evolve from competing solutions vying for the lion share of adoption. OPC really doesn’t have any direct competitor. I’d argue (and have before) that other protocols that may have overlap in some areas are complementary not competitors.
The main thrust of the article is that those that drive open standards need to meet his definition of verifiably vendor-neutral.
“Vendor-neutral here means that the standard does not discriminate against any realistic players, either by making basic implementation too hard or by disallowing vendor-specific features or innovations or experiments, where appropriate.”
Again OPC as a standard does a good job of this. Although the ‘classic’ OPC specifications didn’t specifically provide ways to extend the standard interfaces, they didn’t do anything to preclude this either. That’s the main reason users can get products that add functionality such as redundancy, tunneling or calculations without sacrificing standardization. OPC UA does go one step further and actually provides methods for extending the specs or providing vendor specific information. (I’ve blogged on that as well).
Of course a goal on any OPC vendor is to provide universal connectivity to a wide range of systems. Therefore it is in their best interests to be vendor neutral, and have good working relationships with all the major players. Seems to be working for OPC.
The article that got me thinking on this stuff is on an O’Reilly site, which got me thinking about when is there going to be an ‘OPC in A Nutshell’ from O’Reilly? (Yes, I am easily distracted). Of course, the biggest challenge is coming up with what animal to put on the cover. It’s all about connectivity, so I’d say a Spider, but I think that one’s taken. Anyone? Maybe a Peruvian Boomslang?