Professional OPC Development Tools and Services

opc logo

QuickOPC Editions

Following table will help you to understand the features of different QuickOPC editions, and assist in selecting the edition that is best for you.

Product EditionStandard 2)ProfessionalUltimate
OPC Specifications
OPC Data Access

OPC-DA is the original specification. It is commonly used to move real-time data from PLCs, DCSs, and other control devices to HMIs and other clients, for display purposes and further processing.

tick-alt tick-alt

OPC XML-DA specification builds on the OPC-DA specifications to communicate data in XML. It incorporates SOAP and Web services.

tick-alt tick-alt tick-alt
OPC Alarms and Events OPC-A&E provides alarm and event notifications on demand (in contrast to the continuous data flow of Data Access). These include process alarms, operator actions, informational messages, and tracking/auditing messages. tick-alt tick-alt
OPC Unified Architecture (Generic/Data) OPC-UA is the next generation of OPC. It brings the existing specifications together with a unified data model and uses Web services, rather than Microsoft COM, for messaging. tick-alt tick-alt tick-alt
OPC Unified Architecture (Alarms & Conditions) This standard deals with Conditions, Dialog Conditions, and Alarms, including acknowledgement capabilities.

tick-alt New



Development Models
Procedural Coding Model This is the traditional programming. You write code to instantiate objects, and call methods to perform the OPC operations. tick-alt tick-alt tick-alt
 Live Binding Model 1) Simply use the Visual Studio Designer to configure bindings between properties of visual or non-visual components, and OPC data. For Windows Forms, code-less. tick-alt tick-alt
 Live Mapping Model 1) Allows you to write objects that correspond logically to a functionality provided by whatever is “behind” the OPC data. You map your objects and members to OPC by annotating them with attributes. tick-alt
 Reactive Programming Model 1) High-level abstraction that allows you to compose asynchronous and event-based programs using data streams and LINQ-style query operators. Uses Microsoft Reactive Extensions (Rx) for .NET. tick-alt
Browsing Dialogs Pre-made, highly configurable OPC browsing dialogs for Windows Forms (callable from WPF as well). Provide interactive viewing and selection features. tick-alt tick-alt
Browsing Controls 1) Configurable OPC browsing controls for Windows Forms. Can be combined with other controls on the form to achieve the desired functionality. tick-alt tick-alt
 .NET For languages and tools based on Microsoft .NET on Windows. Typical usage is from Visual Basic (VB.NET) or C#, but other languages can be used  as well (e.g. managed C++, or F#). tick-alt tick-alt tick-alt
COM For languages or tools that supports Microsoft OLE Automation, e.g. Delphi, VB6, VBScript (such as in ASP), JScript, Perl, PHP, Python, VBA (such as in Excel), Visual FoxPro, REALbasic, Xbase, T-SQL, and many others. Also works from native C/C++. tick-alt tick-alt tick-alt


The StreamInsight Option for QuickOPC is only available with the Ultimate edition.


  1. Only available on .NET platform.
  2. For licenses granted prior to April 2, 2015, the capabilities of the Standard edition were as of the Professional edition today.

Click here for information about QuickOPC licensing and license types. The installation package is the same, regardless of the product edition; the enabled/allowed product capabilities are distinguished in the license.

Component And Part Names

QuickOPC is a name for the product as a whole. It is constituted of various components and modules.

EasyOPC is a main component of QuickOPC, and it allow programmatic client access to OPC servers. Other parts of QuickOPC are user interface objects (dialogs and forms), extension objects, utilities and so on.

In order to distinguish between the technologies and platforms that the product is aimed at, we refer to parts or subsets of QuickOPC as follows (earlier they have constituted separate products):

  • QuickOPC.NET, for Microsoft .NET Framework technology, and connection to OPC "Classic" (OPC COM and OPC XML) servers.
  • QuickOPC-COM, for use with Microsoft COM (automation), and connection to OPC "Classic" servers.
  • QuickOPC-UA, for OPC Unified Architecture specifications.

The following table explains the product parts, and how they relate to OPC specifications they cover, and to the development tools platform that can be used with them.

Development Tools PlatformMicrosoft .NET
NET logo
Microsoft COM
COM icon
OPC Specifications
OPC "Classic"
(DCOM based)
OPC Data Access QuickOPC.NET QuickOPC-COM
OPC Alarms and Events
OPC XML-DA (Data Access)
OPC Unified ArchitectureGeneric/Data

QuickOPC-UA (for .NET)

QuickOPC-UA for COM

Alarms & Conditions



The OPC XML-DA support in QuickOPC.NET is transparently integrated into the component. Wherever this site or the product documentation refers to “OPC Data Access”, it also usually applies to OPC XML-DA.


All product parts are delivered in a single installation package.


Product Part Capabilities

Following table explains the capabilities of various product parts. Note that this table is NOT relevant for choosing between product editions (Standard or Ultimate), because all products parts are available in the QuickOPC product, regardless of the edition.

Product PartQuickOPC
QuickOPC-UA for  COMQuickOPC-UA (for  .NET)
OPC Specifications
OPC Data Access tick-alt tick-alt    
OPC XML-DA tick-alt tick-alt    
OPC Alarms and Events tick-alt tick-alt    
OPC UA (Generic/Data) 1) 1) tick-alt tick-alt
OPC UA (Alarms & Conditions) 1) 1)

tick-alt New

tick-alt New

Development Models
Procedural Coding tick-alt tick-alt tick-alt tick-alt
Live Binding   tick-alt   tick-alt
Live Mapping   tick-alt   tick-alt
Reactive Programming   tick-alt   tick-alt
Browsing Dialogs tick-alt tick-alt tick-alt tick-alt
Browsing Controls   tick-alt   tick-alt
Languages and Tools
 C/C++  2)    2)  
 COM-based (OLE Automation)      
 .NET Languages    



  1. Connection to OPC Unified Architecture Servers can be accomplished through UA Proxy for OPC COM Clients (included with the product). For native OPC UA connection, use the QuickOPC-UA product part.
  2. You can use the QuickOPC-COM product part from native code in C/C++ by making COM calls.


Managed C++ (C++/CLI) can be used wherever .NET Development Tools are indicated.

Development Tools, and .NET Framework Versions

For use with Microsoft development tools (not a requirement), the current QuickOPC version (2016.2 or later) targets the commercial developer editions of Visual Studio 2012, 2013, 2015 or later. If you are doing COM development (not .NET), earlier versions of Visual Studio will supposedly work fine, backwards down to Visual C++ 6.0. We do not officially target or support the non-commercial editions, such as Visual Studio Community (they may work though... it's up to you to figure out, if you are interested).

For .NET development, the current QuickOPC version (2016.2 or later) targets .NET Framework 4.5.2 or later. Note that .NET Framework 4.5.2 uses the same CLR (Common Language Runtime) as .NET Framework 4.0, so if you are using .NET Framework 4.0, you should have no problem upgrading to .NET Framework 4.5.2.