QuickOPC and PicoOPC License Types
- Single Developer + Runtime Free License. One person can develop software with the product, but you can deploy to any number of computers, free of any further royalty payments. This is the most popular choice, largely used by System Integrators (SI). You should generally have control over the deployment of the developed software, e.g. by providing a service where the software is part of your deliverables (otherwise, look for ISV/OEM license). If more developers need to work with the software, you can also purchase "Additional Developers License", or choose a "Site License".
- Additional Developers License. This license is only available in addition to "Single Developer + Runtime Free License", and allows an additional developer to work with the software concurrently. It is your responsibility to assure that number of developers using the software does not exceed the number of purchased licenses.
- ISV/OEM License. This license is for usage where you develop a software or hardware that is then subsequently freely sold as a standalone product, and you generally have no control over where and how it is deployed. The only limitation of this license is that you cannot create a software that is also an OPC client component for developers' usage, or competes with it. The license can be used by any number of developers in the company. Depending on the negotiated conditions, there may be no royalty fee for deploying the software created with the component. ISV/OEM license holders may also get priority, developer level support, and early access to Beta versions. Note: ISV stands for Independent Software Vendor; OEM stands for Original Equipment manufacturer.
- Site License. Any number of persons on a single site can develop software with the product, and you can deploy to any number of computers on any site, free of any further royalty payments.
For QuickOPC, you will receive a single license file with each purchase, and install it onto the computer(s) using a License Manager utility. There are also alternative, documented methods of deploying the license e.g. on the runtime machines automatically, using your own installation program, or embedded in your application. The license types are the same for all Product Editions.
For PicoOPC, the license key is a GUID that you specify in your code according to the procedure described in the documentation.