Customers occasionally have some confusion about the InduSoft licensing types and the correlation between Site Keys, Site Codes and what the Register Utility does.
The InduSoft Web Studio Family is an offering of numerous products and add-ins or add-ons that operate on large number of varied platforms. Some of the most popular products are:
- -InduSoft Web Studio for Windows and Embedded Operating Systems
- -InduSoft EmbeddedView Runtime
- -InduSoftCEView Runtime
- -Indusoft Thin Client
- -InduSoft Secure Viewer
- -InduSoft SMA and Enhanced SMA for HTML5
- -Indusoft Device Drivers
- -InduSoft Add-Ons such as:
- -Business Intelligence Dashboard Template
- -Import Wizards for PanelMate and PanelView
- -Electrical Industry Drivers
- -InduSoft DNP3 and IEC Driver Information
- -OPC XML
- -Overall Equipment Effectiveness (OEE) Dashboard
All these products and Add-Ons require registration, changes, or additions in licensing in order to run properly. Selecting the correct configuration of your components and understanding the roles of your machines will help you determine the licensing model needed for each machine.
Please Refer to, and Follow, the Flow Chart for More Information on the Following Steps
I: Select a Runtime Platform for your Application
Starting at the beginning with InduSoft Web Studio Licensing, the first thing that you need to know is what platform that the developed application is going to RUN on. There are 3 choices of platforms:
A) A full-sized machine running Windows XP, Windows 2003 or 2008 Server, and Windows 7.
– These Microsoft operating systems are usually installed by the end user using removable media such as optical drives or USB drives.
B) A resource-light machine running an Embedded Standard operating system such as Windows Embedded Standard 7, or Windows Embedded Standard 8.
– The legacy Operating System is XPe.
– These machines require an x86 or x64 processor.
– A common configuration of this machine is a Panel PC that may have a Hard Drive, USB Ports, an Ethernet Port, and an Optical Drive.
– The Operating System is usually installed or provided by the device manufacturer.
– This device is usually used as an HMI/SCADA Interface and possibly a data storage unit.
C) A resource-light machine running Windows Embedded Compact 7.
– The legacy Operating System is Windows CE.
– Processor types are ARM, Atom, and x86.
– A common configuration of this machine is a Panel PC that may have a Flash Drive used as the storage media, USB Ports, and an Ethernet Port.
– The RAM and processor on these machines are usually minimal.
– The Operating System is always installed by the manufacturer of the device.
– This device is usually used as an operator workstation with light graphical screens and no intensive computing, scripts or database queries, and has minimal Thin Clients.
II: Decide What Role the Runtime Machine is going to have
A) If the machine is a Full-Sized Runtime Machine (Windows 7, Windows 2008 Server), it could have one of two roles:
1) A Runtime Machine with Development capability
2) A dedicated Runtime Machine.
B) If the machine is an Embedded Standard (XPe, 7, or 8) machine, it could have one of two roles:
1) It can be loaded with the full installation of the IWS Development Platform or
2) It can be loaded with the “CE” style installation of EmbeddedView Runtime.
C) If the machine is an Embedded Compact (Win CE, 7) machine, it can only be a runtime machine:
1) It will be loaded with the CEView Runtime.
III: Determine the Number of Tags in your Runtime Project, the License Level and the Type of Projects that you are going to develop in the future.
A) Select the Runtime License Level from the list of available licenses for your runtime machine.
B) Now is the time to determine the role of your Development License.
1) One role is if you are going to only develop a single project or projects similar in size, scope and target platform, your selection of the Development License Level need to will be large enough to accommodate the current runtime project and future changes. This type of licensing is usually split between 2 machines: One for runtime, and one for development.
i) It is OK to split the license such that the Development License is a Hardkey and the Runtime License is a Softkey.
ii) You can also split the license between 2 Hardkeys or 2 Softkeys; however there are some pricing issues that should be discussed with a sales person, depending on the platforms being developed for.
2) The other role for the development license level is if you are going to develop projects of varying sizes and target platforms. This type of licensing is usually a Combined or Joint single Hardkey or Softkey license.
C) Determine how many tags you need
When purchasing licenses for InduSoft Web Studio SCADA software, it’s important to know an approximation of how many tags you will need for your SCADA project. It’s equally important to understand how InduSoft Web Studio counts tags, so that you can come up with an accurate estimate for your project’s needs. InduSoft’s license levels depend primarily on the maximum number of application tags required for the application.
Each tag is a “variable” capable of holding an independent value, such as “PressureTankA”, “TemperatureOver1”, “StateMotorC”, and so forth. The following rules apply for InduSoft’s tag count:
– The tags created by the user. Application or Project tags in the SCADA software are counted against the license limit. However, the System Tags, created automatically for any project, are not counted against the license tag limit (e.g.: Time, Date, UserName, and so forth).
– The tag count does not depend on the data type supported by each tag (Boolean, Integer, Real, or String).
– The same tag can be configured in many interfaces, and it still counts as only one tag. For example, the same tag can be configured on Screens, Trend worksheets, Alarm worksheets, Driver worksheets, OPC worksheets, and this will not affect your tag count.
– Any tags created for the project are counted against the license limit, even if they are not linked to an external device (e.g.: PLC) via communication drivers, OPC, or any other task. In other words, as soon as the tag is configured in the application, it is counted against the license limit.
– VBScript variables are commonly used to manipulate temporary values used in calculations. VBScript variables can be used in any VBScript interface of the SCADA software (VBScript tasks, Global Procedures, Graphic Scripts, Screen Scripts, and so forth) and they do not count against the license tag limit in the SCADA software.
– Each array position counts as one tag because it holds an independent value. For example, a tag configured with 3 array elements counts as three tags (Tag, Tag, and Tag).
– Each member of a class tag counts as one tag because it holds an independent value. For example, a class tag with 2 members counts as two tags (Tag.MemberA and Tag.MemberB).
– Class tags configured as arrays count as the number of array positions multiplied by the number of members. For example, a class tag with 2 members and configured with 3 array elements counts as six tags (Tag.MemberA, Tag.MemberA, Tag.MemberA, Tag.MemberB, Tag.MemberB, and Tag.MemberB).
IV: Select the License Key Type
– Advantages: Portability between machines
– Disadvantages: Can break or be lost, can’t get a new license immediately if lost or damaged.
– Advantages: Can’t be removed from machine, can be reset or renewed over the Internet.
– Disadvantages: Always stays with the same machine.
V: Install and Register your License
1) Simply plug the key into a USB Port after the installation of, but before starting, InduSoft Web Studio or the Runtime Components in EmbeddedView and CEView machines.
Use one of the following two steps depending on the machine that you are licensing:
1) After the full installation of Indusoft Web Studio on your Full-Sized or Embedded Standard machine, and before starting the development environment, use the following steps:
i) From your Windows Desktop, press “Start”, then “Programs”, and find the Indusoft Folder(s) in the programs list. If you have multiple versions of IWS installed you must select the folder of the version that you want to license, i.e., “InduSoft Web Studio v7.1”, then double-click on the Register Utility to start it..
(1) The Register Utility of one version CANNOT be used to register a different version of Indusoft Web Studio.
ii) In the Register Utility, choose “SoftKey”, “Change License”, and copy the Site Code. Paste the Site Code and the NS number on your Certificate of Authenticity into a Licensing Chat or into an email to email@example.com, and you will receive a Site Key back. Paste this into the Site Key field and press “Authorize”.
iii) After the installation of the System Files using the Local or Remote Agent on the Embedded Standard or Embedded Compact machine, push “Change License” ”, and copy the Site Code. Paste the Site Code and the NS number on your Certificate of Authenticity into a Licensing Chat or into an email to firstname.lastname@example.org, and you will receive a Site Key back. Paste this into the Site Key field and press “Authorize”.