Sales FAQ

Academic research purposes are defined as conducting not-for-profit research projects which are not intended to or in fact produce results, works, services, or data for commercial use by anyone or to generate revenue. The results should be in the public domain and suitable for submission to a peer-reviewed journal or conference for publication. These academic licenses are not for use in a direct revenue generating capacity.

If any deduction or withholding is required by law, you will notify us and will pay us any additional amounts necessary to ensure that the net amount that we receive, after any deduction and withholding, equals the amount we would have received if no deduction or withholding had been required.

You shall identify those employees assigned to a Named User license on the “Managed Named Users” list (the “List”). This List can be maintained by your System Administrator (or similar person) using anything from a simple spreadsheet to a complex licensing management tool and should always be kept up-to-date in order to avoid any compliance surprises should an externally triggered software audit occur.

A Named User license may not be reassigned to another employee except in the following circumstances:

• (a) Upon termination of the Named User’s employment with your company.
• (b) Permanent reassignment of a Named User to a position that does not involve the use of the Software.

For example, suppose Jane has been assigned an Oxygen XML license and she leaves your company. When she leaves, you can simply reassign her license to John, her replacement. In the event that you do reassign the Named User license in accordance with the restrictions above, you do not need to notify Syncro of such a reassignment.

There is no limitation on end-users accessing and reviewing documentation through Content Fusion. These users do not necessarily have to be employees of the customer that has purchased the Content Fusion Enterprise license. They can also be subject matter experts belonging to third-party companies. Access to the Content Fusion Enterprise service installed by the customer will be granted by the customer itself, within the limits specified in the license (such as the number of floating licenses included in the purchased license package).

The number of CPU-core licenses required depends on how the Software is deployed on your Server:

• If you are running the Software inside an operating system on a Physical Server, then the number of cores for the licenses you deploy to that Server must be equal to or greater than the number of Physical Cores.
• If you are running the Software inside a virtual machine, then the number of cores of the licenses you deploy must be equal to or greater than the number of Virtual Cores shown available in that virtual machine. A virtual operating system uses a fraction of a virtual CPU and that fraction will be included in the calculation and be counted as a full virtual CPU.

Important Notes:

• The number of cores licensed must be greater than or equal to the number of cores available on that server machine, whether the server is a physical or virtual machine. For example, if a server has eight cores, you must purchase an 8-core license. You can also combine licenses to achieve the core count. So, two 4-core licenses can be used for an eight-core server instead of one 8-core license.
• If you are using a computer server with a large number of CPU cores but only have a low volume to process, you may also create a virtual machine that is allocated with a smaller number of cores, and purchase a multi-core license for that number. Note that such a deployment will have less processing speed than if all available cores of the computer were utilized.
• One CPU Core license key of the Software must not be used on multiple physical machines, multiple virtual machines, or any combination thereof. Additional Licenses must be obtained to use the Software on multiple physical or virtual machines.