# ESM-license-generation-detail_686070325
## SMAX

For SMAX we sell the licenses based on a number of “user units”.

- Every customer will purchase 1 foundation license + a quantity of the add on 1 unit license
- for each foundation there is a matching 1 unit sku
- We then have 2 different license types “Express” And “Premium”.
- A customer cannot mix license types on the same tenant
- Premium licenses include 1 prod and 1 dev tenant
- Express licenses only include 1 prod. There is no dev tenant included
- There is 1 exception to this and that is the “powered by” Express foundation SKU – a special sku that includes the dev tenant ( its limited to only certain partners)
- 1 <sup>st</sup> Dev tenant for a customer must always be provisioned on the same farm as their production tenant.

In the tables below I have listed the quantity of units included with each license type.

When it comes to licenses being applied to dev instances the general rule of thumb is 25% of the total number of “user units” is applied to the dev tenant

- So for example if a customer purchased 1x SA-AB918 + 10x SA-AB919 ( providing a total of 60 units), 15 units would be applied to the dev tenant.
- We are ok with rounding up on dev tenants, so for example if a customer just bought the SA-AB918 license ( 50 units) then you can deploy 13 units on dev.
- In general we are “ok” if we apply a few extra on dev.
- I guess if we want to make sure control tower does this properly and generates the license files, we should assume the foundation includes that 25% quantity ( 13 for a 50 unit foundation and 5 for a 20 unit foundation)

**complicated bit**

- There is a non-production tenant SKU that allows a customer to purchase a “dev” ( customer can purchase as many additional non production tenants as they like).
- Each non production tenant follows the above plan and gets 25% of production units applied to the tenant
- We typically see express customers purchase this ( to get a “dev” tenant) and in those cases the tenant would be deployed on the same farm
- but we also see many customers use this to purchase a 2 <sup>nd</sup> non production tenant
	- We allow the customer to choose the deployment location of this tenant. Some choose to have it on the same farm as the others, but some will ask for this to go on the EU3 / US7 farms that get upgraded earlier, so that they can get early access to play with the new release
- For non-production tenant SKU, CS Ops will follow the same strategy to generate license for a "dev" tenant.

| **SKU** | **Name** | **units included for prod** | **Dev included as standard?** |
| --- | --- | --- | --- |
| **SA-AC055** | MSP SMAX Express 1 unit | 1 | N |
| **SA-AC054** | MSP Express Foundation | 20 | N |
| **SA-AC190** | Fedramp SMAX express 1 unit | 1 | N |
| **SA-AC189** | Fedramp SMAX express foundation | 20 | N |
| **SA-AB923** | SMAX Express 1 unit | 1 | N |
| **SA-AB922** | SMAX Express Foundation | 20 | N |
| **SA-AB998** | Express Powered By Foundation | 20 | Y |
| **SA-AB999** | Express Powered By 1 Unit | 1 | Y |

| **SKU** | **Name** | **units included for prod** | **Dev included as standard?** |
| --- | --- | --- | --- |
| **SA-AC053** | MSP SMAX Premium 1 unit | 1 | Y |
| **SA-AC052** | MSP SMAX Premium foundation | 20 | Y |
| **SA-AC188** | Fedramp Premium 1 unit | 1 | Y |
| **SA-AC187** | Fedramp Premium Foundation | 50 | Y |
| **SA-AB919** | SMAX Premium 1 unit | 1 | Y |
| **SA-AB918** | SMAX premium Foundation | 50 | Y |
| **SA-AB921** | Premium Powered By 1 unit | 1 | Y |
| **SA-AB920** | Premium Powered By Foundation | 20 | Y |

## UCMDB

There are 2 deployment modes for Universal Discovery and CMDB in SaaS. Customers may purchase Universal Discovery capability as part of their SMAX/AMX/HCMX purchase which then includes the UCMDB Foundation license as part of the SMAX/AMX/HCMX Foundation product. Or they can purchase a UCMDB Foundation license separately and use Universal Discovery and CMDB outside the scope of SMAX/AMX/HCMX.

UCMDB Foundation licenses would typically be sold when the customer has another ITSM tool they use instead of SMAX (i.e. ServiceNow, JiraSM, BMC, or their own ITSM software).

- Standalone UCMDB Foundation (SA-AC098) provides 1 UCMDB Foundation license + 500 Premium Discovery licenses. This deployment is based on the standard ESM SaaS deployment and can be shared with other customers.
- Dedicated UCMDB Foundation (SA-AC236) provides 1 UCMDB Foundation license + 20,000 Premium Discovery licenses. This deployment is based on the standard ESM SaaS deployment but does not have any other customer assigned to this farm.

Universal Discovery licenses work in either deployment mode.

- Premium Discovery licenses (SA-AB820) provide for full discovery of 1 server and include capacity for 1,000 CIs and relationships
- Asset Discovery licenses (SA-AB882) provide inventory discovery for 1 server or desktop, and includes the ability to run any discovery job necessary to fully meet the SAM requirement of AMX. Asset Discovery license also provide for 1,000 CIs and relationships per license.
- CI Management licenses are the same SKU as the Asset Discovery license (SA-AB882) and can be used to import 20 devices (servers or desktops/laptops), or can simply be used to provide additional storage capacity (1,000 CIs and relationships per license).
- In all cases, each license, regardless of the type (except for Probe Connection licenses), provides storage capacity for 1,000 CIs and relationships.
- Probe connection licenses (SA-AC238) are available for every 1,000 licenses (regardless of type)
- 1 – 1,999 licenses = 1 probe
	- 2,000 – 2,999 licenses = 2 probes
	- 3,000 – 3,999 licenses = 3 probes
	- etc
- Universal Discovery Foundation licenses provide for 1 prod tenant and 1 dev tenant. Universal Discovery licenses purchased as part of a SMAX/AMX/HCMX deal will follow whatever tenant rules apply for the SMAX purchase.
- 1 <sup>st</sup> Dev tenant for a customer must always be provisioned on the same farm as their production tenant.

In the tables below I have listed the quantity of units included with each license type.

Dev license rule of thumb

When it comes to licenses being applied to dev instances the general rule of thumb is 25% of the total number of Universal Discovery licenses (Premium or Asset or CI Management) is applied to the dev tenant

- So for example if a customer purchased 1,000 x SA-AB882 + 1000 x SA-AB820 (providing a total of 2,000 licenses), 250 x SA-AB882 and 250 x SA-AB820 would be deployed to DEV
- We are ok with rounding up on dev tenants.
- If a customer requests more than 25% license on their DEV, contact the Universal Discovery and CMDB Product Managers.

| **SKU** | **Name** | **units included for prod** | **Dev included as standard?** |
| --- | --- | --- | --- |
| **SA-AC098** | Universal Discovery and CMDB Foundation 500 Unit SaaS | 1 | Y |
| **SA-AC236** | Universal Discovery Dedicated Foundation 20000 Unit SaaS | 1 | Y |
| **SA-AB882** | Universal Discover (UD) Asset Discovery and CI Management 1 Unit SaaS | 1 | N |
| **SA-AB820** | Universal Discovery 1 Premium SaaS | 1 | N |
| **SA-AC238** | Universal Discovery Additional DFP Connection 1 Unit SaaS | 1 | N |
| **SA-AC194** | Universal Discovery Asset Discovery and CI Management FedRAMP 1 Unit SaaS | 1 | N |
| **SA-AC193** | Universal Discovery 1 Premium FedRAMP SaaS | 1 | N |
