“Are all “standards” created equally?” What does it mean when someone buys such systems under the illusion that they’re making the right investment to enable their systems to run efficiently (we hope) and reliably?

Nathan Pocock Director of Compliance, OPC Foundation

At the OPC Foundation, we are constantly fielding questions from end-users about OPC technology. A recent question was regarding the value of product certification. The question was “Why should I care if the OPC product that I use has been through certification?” It is a very fair question that should be answered with another question. Are you an engineer who has been woken up from a blissful sleep at 3am because plant production has stopped and no one knows why? Or have you spent 3 months installing a system that should have only taken seven days, and have seen your blood-pressure numbers match the national-debt while working with technical support to fix the problem? If you answered “Yes” to either of these questions, then you, my friend, purchased un-certified OPC software.

[an error occurred while processing this directive]

[an error occurred while processing this directive]

This is not an article where, as an author, I will stand up on my soap-box and preach about the importance of software certification. This is an article where, as an author, I want to outline the lesson learned from a fellow software developer and engineer. Like me, you are probably the same person that spends weeks testing somebody else’s products to avoid being burned again! What if you didn’t need to… what if somebody else did that for you? This article will outline a process that will give you back your weekend.

Most automation systems today are based on, or utilize, a standard like OPC (www.opcfoundation.org/) for inter-system device communication. The question that naturally comes next is: “Are all “standards” created equally?” What does it mean when someone buys such systems under the illusion that they’re making the right investment to enable their systems to run efficiently (we hope) and reliably?

In an effort to prevent the 3am wake-up call, the OPC Foundation introduced the Compliance and Certification program (www.opcfoundation.org/certification/) to provide the necessary policing of what is essentially an open-standard – specifically the OPC Specifications - or as some might say, a standard “open to interpretation” – which is the case for any standard!

By having a Compliance and Certification program, the OPC Foundation members who develop and create OPC-based systems have all of the tools they need to:

• Develop systems that are proven to be compliant to the specifications by using automated test tools and test-case documentation

• Follow best-practices guidelines that define the behavior and usability of an OPC system

• Interoperate with other systems from other vendors

The OPC Foundation Compliance and Certification program is an ever-expanding group of OPC Foundation members including: ascolab GmbH, Embedded Labs, Honeywell, Inductive Automation, Kepware, MatrikonOPC, SMAR, Softing, Software Toolbox and Yokogawa. The Compliance and Certification program is continually looking for companies to participate in the program. Their responsibilities include defining test-cases based on the interpretation of the OPC Specifications, developing test-tools, and defining the “best-practices” which developers and application designers will use to develop future OPC products.

The OPC Foundation Compliance and Certification program offers different levels of certification. It is extremely important for individuals who purchase this software to understand the rigors that each level of certification requires, and the benefits of those results.

OPC Foundation member products that are “OPC Compliant” and pass the Compliance Test Tools are said to be “Self-Certified.” This level of certification is a must for any OPC product that is in production use in any environment today. Products bearing this logo tell end-users of Self-Certified products that these OPC products are compliant with the OPC Standards, and provide the test results in document form. These test results provide the first level of quality control for the guarantee of interoperability.

[an error occurred while processing this directive] Providing test-tools and test documentation is a first step towards product quality. Attending an Interoperability workshop is the logical next step toward ensuring complete software compatibility with other OPC Foundation members. These Interoperability workshops provide Foundation members with the opportunity to “test” their software for compatibility against other OPC Foundation member’s products. The results of these interoperability workshops are essential to ensure that OPC Foundation members continue to improve and evolve their software development as the technology standards continue to evolve.

The highest level of OPC Foundation testing is “Lab Certification.” The OPC Foundation Lab Certification can be performed in one of two locations: Erlangen, Germany or Scottsdale, AZ. These Certification Test Labs conduct vigorous testing of products to ensure:

• They comply to the OPC Specifications

• Are resilient against badly-behaved systems by passing error-injection tests

• Prevent a system from crashing, despite best-attempts to cause a crash

• Have the ability to efficiently recover from communications losses

• Ensure the following of “best-practices”

• Ensure documented data throughput performance and that load-testing are verified against a vendor’s claims.

It is OPC software that is able to withstand the battering of tests conducted by an OPC Certification Test Lab that are truly considered “best-of-breed.” Achieving the highly acclaimed “Lab Certified” status is no easy task. End-users who invest in “Lab Certified” OPC products can truly appreciate that they have invested in quality. The next time you are investigating a new system, or OPC product, take the time to see what level of certification the product has achieved. Know that the investment you made is one of quality, and has the documentation to substantiate that mark of quality. Or perhaps you would rather just keep the cell phone by your bed and hope for the best?

About the Author

Nathan Pocock - Compliance working group & certification and testing program for OPC UA
Nathan Pocock entered the Automation Industry in 1995 as an IT administrator. He later joined Siveco UK, a Computer Maintenance Management System company, as a trainer and consultant. After leaving the UK for the USA in 1999, Nathan became a technology instructor at the ECPI College of Technology. In 2001, Nathan re-entered the automation industry by joining Software Toolbox, where he was heavily involved in product sales, marketing and support before becoming the Chief Architect & Developer of software systems design and development. Nathan joined the OPC Foundation in early 2009 to lead the Compliance working group and launch the certification and testing program for OPC UA, located in Scottsdale, AZ. Nathan enjoys mountain biking, the UFC, and coaches 2 kids soccer teams.

[an error occurred while processing this directive]
[Click Banner To Learn More]

[Home Page]  [The Automator]  [About]  [Subscribe ]  [Contact Us]