Symbol Factory - What if I want to bundle Symbol Factory my Commercial HMI?

If you have a commercial HMI software package that can support the Symbol Factory and you would like to bundle our product with your software, a special OEM license is required for this, as stated in the End User License Agreement that is presented when you install the Trial Versions of the products.

OEM licensing is an easy process, consisting of a technical and commercial part:

Technical:

Before we have commercial discussions, we should make sure that your application works  with the Symbol Factory graphics or if you are looking to use Symbol Factory ActiveX or Symbol Factory .NET.

Please download the trial version that you wish to consider and try it with your product.   If you run into issues, realize that they may be issues on your side or our side.  Document what you find and we can discuss any issues with you.  Do be prepared that we may ask you to involve a member of your development team in the discussion, as we will also if needed on our side.

Submit a case to us here and include as much information as possible if there are issues.

Choosing the Correct Symbol Factory Product:

All 3 products provide the SAME library of 4,000+ Industrial Automation Graphics.  The majority of the graphics are vector based graphics.  This means you can scale them larger or smaller without loss of quality, and the memory footprint for individual symbols is very small - average 7Kb/symbol, largest is about 13 Kb.

What is difference between the Editions of Symbol Factory?

Symbol Factory Universal - provides a symbol library management application that allows your user to browse the categories of symbols, pick symbols, copy/paste or drag/drop them into target applications as Windows Metafile or BMP format.  Export to SVG, VML, JPG, GIF also possible.  Users can resize, recolor symbols before exporting, and can add their own categories and import symbols of their own making.

Trial Version: Try Symbol Factory Universal

Symbol Factory ActiveX - using the same library as Symbol Factory Universal, the user places the ActiveX control into your application, and can pick the symbol, set color, and then at runtime change color and/or blink the symbol based on analog or digital inputs.  Your HMI/SCADA or other application must support the use of ActiveX controls if you are considering licensing this edition.  For best results your application must also support what is called Windowless Activation of ActiveX controls so that you can use background transparency.  If you are unsure if your application supports windowless activation, get our trial version and try it.  If you can insert a control and set the BackStyle property to Transparent, then you do, because our code checks to see if your application supports background transparency on ActiveX controls.

Trial Version: Try Symbol Factory ActiveX

Symbol Factory.NET - same functionality as Symbol Factory ActiveX, but for use in applications that support .NET user controls and .NET Framework 2.0, 3.0, or 3.5.

Trial Version: Try Symbol Factory .NET

If you need help deciding which version is right for you, please tell us more about your software, whether it supports ActiveX controls, .NET controls, or vector graphics.

Commercial:

Once we know that our products do work well together, or at least know what steps are needed in order to make them work well together, we can have a commercial discussion.  We craft each OEM agreement to meet your specific needs, as we have found in our extensive experience in this area, that each client's needs are unique.

In general our agreements provide very attractive pricing for OEMs that is nothing like our retail pricing, direct developer level support, easy administration, and include updates/upgrades for the life of the agreement.  

Please try and answer as many of these questions as possible:

1. What is the name of your software and the current version #?
2. If your product is a new product that has not yet shipped, when do you anticipate releasing the product?
3. Do you license development users of your product separate from runtime users?  If yes, do you have a way to track the number of licenses of your development software that you sell?
4. Do you need a non-disclosure in place in order to share with us your forecast for sales of licenses of your software for the current year and next 2 years?  If yes, who should we send a non-disclosure agreement to.  If you do not need a non-disclosure in place, please include a forecast for sales of licenses of your software for the current year and next 2 years.
5. Name, Title, Email, and Phone Number for yourself or the person we should contract to handle your OEM licensing requirements.