<< Click to Display Table of Contents >> Navigation:  Modules > Asset Management > Software License Management > Licenses > Software License Allocation > Allocation Constraints

The MIE has a sophisticated and automated license allocation engine that automatically assigns (allocates) available licenses to cover deployments (authorizations).  The allocation engine also contains an optimizer that will change how licenses are allocated over time in order to arrive at the most cost-effective use of those licenses.

The MIE does not support manual assignment of licenses to deployments (authorizations).  In order to "steer" how licenses are assigned, the MIE supports several methods of constraining allocation.

The methods used for constraining allocation are defined in subsequent help topics.  It is important to note, however, that no method of constraint will work unless the underlying device or person to which the software has been deployed has associated information that matches the license constraint.  This usually means a commitment to Hardware Asset Management and various processes to ensure asset and "people" records are kept populated with accurate business level information (such as department, cost center, and organization).  It also means potentially keeping asset records populated with information such as role, environment, and geography.  

If this commitment cannot be made, it is recommended you do not place constraints on license allocation as there will likely be no device or person to match the constraint, meaning licenses will go unallocated.  This will result in the appearance of an out-of-compliance position even though there appear to be sufficient counts of owned licenses.

TO USE LICENSE CONSTRAINTS REQUIRES A COMMITMENT TO HARDWARE ASSET MANAGEMENT.