Thomas Burke

President and Executive Director
Director, was the architect for the OPC Data Access Specifications. He has served as the designer and leader for OPC Compliance and all OPC Data Access specifications. His vision is the OPC Unified Architecture, which is a multi-vendor, multi-platform, service-oriented architecture that addresses the unification of all OPC Foundation specifications. It provides the standard for secure, reliable interoperability that integrates the plant floor with the enterprise. Mr. Burke has been instrumental in the success of the OPC Foundation, both from a technical and marketing standpoint. The Foundation has created a collaborative community where competitors and consortia can work together to develop the best specifications, technology, certification and process. This has been a driving force for vendors to successfully introduce certified interoperable products into the marketplace. The realization of this vision can be measured by the growing level of OPC adoption. The OPC classic specifications have been adopted by approximately 3,500 different companies, resulting in over 22,000 different products. The estimated number of OPC products in use is over 17 million.

OPC Foundation

OPC is the interoperability standard for the secure and reliable exchange of data in the industrial automation space and in other industries. It is platform independent and ensures the seamless flow of information among devices from multiple vendors. The OPC Foundation is responsible for the development and maintenance of this standard. The OPC standard is a series of specifications developed by industry vendors, end-users and software developers. These specifications define the interface between Clients and Servers, as well as Servers and Servers, including access to real-time data, monitoring of alarms and events, access to historical data and other applications. When the standard was first released in 1996, its purpose was to abstract PLC specific protocols (such as Modbus, Profibus, etc.) into a standardized interface allowing HMI/SCADA systems to interface with a “middle-man” who would convert generic-OPC read/write requests into device-specific requests and vice-versa. As a result, an entire cottage industry of products emerged allowing end-users to implement systems using best-of-breed products all seamlessly interacting via OPC. Initially, the OPC standard was restricted to the Windows operating system. As such, the acronym OPC was borne from OLE (object linking and embedding) for Process Control. These specifications, which are now known as OPC Classic, have enjoyed widespread adoption across multiple industries, including manufacturing, building automation, oil and gas, renewable energy and utilities, among others. With the introduction of service-oriented architectures in manufacturing systems came new challenges in security and data modeling. The OPC Foundation developed the OPC UA specifications to address these needs and at the same time provided a feature-rich technology open-platform architecture that was future-proof, scalable and extensible. These are just some of the reasons why so many members and other technology organizations (collaborations) are turning to OPC UA for their interoperability platform.

Do NOT follow this link or you will be banned from the site!