MatrikonOPC OPC Exchange


Wireless and a Familiar OPC Story

Posted on August 2nd, 2007 by Eric Murphy

The buzz in the automation blogsphere this week is undoubtedly on wireless (yet again).  Most of it is in regards to the ISA Wireless Summit, which Walt Boyes and Gary Mintchell had some good conversations on.  In reading Jim Cahill’s break down of John Berra’s speech, it struck me as a very familiar story.  The push for standardization, the adoption cycle, and potential for increased access to information and the side effects this may produce are all echo the history of OPC and where it is going with OPC UA.  The same can probably be said for many established standards, but here’s my OPC take on John’s speech.

On Opportunities:

 “But if what we do as a technology doesn’t transfer into allowing plants to run better, safer…it isn’t going to survive.”

OPC survives because it offers value by providing access to data that was difficult or impossible for higher applications to get at previously.  You can replace the word ‘Wireless’ with ‘OPC’ in John’s next statement, and create the perfect OPC quote.

“Wireless offers opportunities for better business and plant management, for better workforce productivity, for better plant and process information. It provides access to information that was out of reach or very expensive to access, so you can do things you couldn’t do before. The technology is proven and ready to deliver results today – with more capabilities coming.”

On Moving to Reality:

“Reliability and security are also critical to overcome. […]  We have not achieved 100%, but I don’t think, that we have to wait for the 100%. We all have products in the field that are meeting many of those objections, and perhaps even all of them. […]”

As someone once said “With great power comes great responsibility”.  The first step is accessing the data, the next is ensuring it gets to the right people at the right time.    When someone starts talking about wireless, the topics of security and reliability are sure to surface.  These are the same challenges OPC is dealing with, through innovative products, proper architecture and are key features of the OPC UA specification.   As with any technology that offers the power of increased access to information, OPC and wireless need to be implemented responsibly.

On Standards:

“Users want standards for wireless – and so do I. Users want confidence wireless equipment and networks will work together, regardless of supplier – now, and years from now. They don’t want to be locked into proprietary networks. Standards are good for suppliers, too. […]   Standards increase user willingness to buy. They give us confidence the approach we’re taking will be accepted in the marketplace.  But mostly, standards are good for our customers.”

Again if you replace ‘wireless’ with ‘OPC’ you hear echoes from the dark times of device connectivity before OPC came about.   Many of the points John makes on creating standards are right on the money in terms of OPC and the development of the OPC UA specifications.

• “Don’t invent the standard unless you have to, unless there is nothing that can serve.”
• “Don’t try to reinvent something that is already well proven and already exists. “

  • “Stay close to the end users.”
  • “Leverage the hard work that has already been done”
  • “…setting politics aside and leveraging proven technologies to deliver a solid, usable standard as quickly as possible. “

You have to remember that John’s whole speech was an excellent talk on wireless standards, but there were just so many parallels to OPC, that I couldn’t say it better myself.  So I didn’t try.

Love it or not, OPC has opened a world of opportunities for data access.  Wireless is going to up that number exponentially, and OPC UA even more.  So as the man said, let’s get on with it.

2 Responses to “Wireless and a Familiar OPC Story”

  1. Jim Cahill Says:

    Eric, This is a great post comparing wireless with the OPC standards efforts.

    I had the pleasure of being in on the original OPC meetings back in 1995 with the a small group of fellow vendors: Intellution, Rockwell Software, Opto 22, us (Fisher-Rosemount at the time), and Intuitive Technologies along with the support of Microsoft.

    This effort was successful because the need was great (performance/robustness limitations with DDE and netDDE at the time for real-time data sharing), the group working on it was small, it had aggressive deadlines, and specs were published for all vendors (and interested process manufacturers) to comment. Start to finish took only a year.

    The timing also worked very well since there was a major shift going from various flavors of UNIX over to Windows NT which had become stable by the time it hit v3.51. This meant that most suppliers were at least thinking about how this communications might happen in future products.

    Looking back over the last decade, it’s great to see the standard continue to advance.

    I appreciate you pointing to the post.

    Take it easy, Jim

  2. Eric Murphy Says:

    Hi Jim,

    I was just following your lead. Thanks for providing it :)
    You comments on the history of OPC reinforce John’s two main points
    1. Move quickly as possible (about 1 year for initial release)
    2. Take advantage of what exists (NT was stable and COM did the job)

    Thanks for the comments and the link back.

    Cheers,
    Eric

Leave a Reply

For spam filtering purposes, please copy the number 8807 to the field below: