Add a Points Rule
You may add points rules to sets that you create locally, or to sets downloaded with the Application Recognition Library.
Individual points rules can be created only within the context of their parent points rule set. Remember that points rule sets are restricted to a specific type of license, and the rules in the set must match the conditions of that license type.
To add a points rule:
Depending on the license type, the following controls may appear in the rule editor. (For a listing of which license types support which control, see What Are Points Rule Sets?). Possible controls are listed here alphabetically.
Control  Notes 

Applies to 
When this points rule set is applied to a license, these settings are tested against the Hosted in value set on the inventory device properties. Where there is a match, this points rule is used to calculate license points consumption for that inventory device. Select one or more of the following check boxes:

BYOL 
Whether this points rule can apply for "bring your own license" (BYOL)
scenarios, and in particular for the Microsoft Azure Hybrid Benefit
(AHB), or license mobility rights. In the editor, choose one of the
following options:

Computer model no  As well as entering a full model identifier, you may use:
(For details, see Special Cases and Regular Expressions.)

Earliest purchase date 
The earliest date when the server under test could have been purchased to qualify for the license to which this rule set is linked. This property may account for price changes over time for a given license type, for example. Enter a date, or click the calendar icon at the right of the field to use a date picker. This field may be left blank (or cleared) when it is not relevant to the linked license(s). (Earliest and latest purchase dates may be cleared independently of each other.) 
Latest purchase date 
The latest date when the server under test could have been purchased to qualify for the license to which this rule set is linked. This property may account for price changes over time for a given license type, for example. Enter a date, or click the calendar icon at the right of the field to use a date picker. This field may be left blank (or cleared) when it is not relevant to the linked license(s). (Earliest and latest purchase dates may be cleared independently of each other.) 
Mapped products 
In the list of all points rules in this set, this column shows the end product(s) of any transition to which the given points rule may apply. For example, in the points rule for License mobility  Enterprise Edition to Standard Edition (which starts from onpremises Enterprise Edition), the end product mapped to the points rule is Microsoft SQL Server Standard Edition (regardless of the release version). To set mapped products, you must move to the second page of the properties editor, as described in the process above. 
Max. clock speed (MHz) 
The maximum value of the processor clock speed (in MHz) that qualifies for consumption from a license linked to the set containing this rule. Enter (or spin up) the whole number of MHz that forms the upper bound for this rule. Use zero to represent Any number (which is displayed when you move to a different control). 
Max. cores 
The maximum number of cores permitted on a server for a software installation on that device to consume from the related license. Enter or spin up a number, using zero to represent Any number (that is, all installations will match this criterion within the overall rule). 
Max. cores per socket 
The maximum average number of processor cores per socket permitted on a server for a software installation there to match this rule. The number of cores per socket is calculated by dividing the computer's inventoried number of cores by the number of sockets. Enter or spin up a number, using zero to represent Any number (that is, all installations will match this criterion within the overall rule). 
Max. processors 
The maximum number of processors permitted on the server for a software installation on that device to consume from the related license. Enter or spin up a number, using zero to represent Any number (that is, all installations will match this criterion within the overall rule). 
Max. resource 
The maximum number of the particular resource specified by the linked license to match this rule. Enter a decimal value (or spin up the integer part), using zero to represent Any number (that is, all installations will match this criterion within the overall rule). 
Max. sockets 
The maximum number of sockets that may be available on the server for a software installation on that device to consume from the related license. Enter or spin up a number, using zero to represent Any number (that is, all installations will match this criterion within the overall rule). 
Max. users 
The maximum number of endusers specified by the linked license to match this rule. Enter or spin up a number, using zero to represent Any number (that is, all installations will match this criterion within the overall rule). 
Min. clock speed (MHz) 
The minimum value of the processor clock speed (in MHz) that qualifies for consumption from a license linked to the set containing this rule. Enter (or spin up) a numerical value. For minima, zero has no special value, but just sets the lower bound to zero. 
Min. cores 
An inventory device must have this number of cores (or more) for a software installation on that device to consume from the related license. Enter or spin up a number. For a minimum value, zero is just zero and has no special meaning. 
Min. cores per socket 
The minimum average number of cores per socket on a server before a software installation there will match this rule. From inventory, the total number of cores is divided by the total number of sockets to get the average for each server. Enter or spin up a number. For a minimum, zero is just zero and has no special meaning. 
Min. processors 
The minimum number of processors that must be available on the server before a software installation there may consume from the related license. Enter or spin up a number. For minimum values, zero has no special meaning (and is just zero). 
Min. resource 
The minimum number of the particular resource specified by the linked license to match this rule. Enter a decimal value (or spin up the integer part). As for all minima, zero has no special meaning, but sets the lower bound of the rule to zero. 
Min. sockets 
The minimum number of processor sockets that must be available on the server before a software installation there will match this rule, and consume from the related license. Enter or spin up a number. As for all such minima, zero has no special meaning, and simply sets the lower bound of the rule to zero. 
Min. users 
The minimum number of endusers specified by the linked license to match this rule. Enter or spin up a number. As for all such minima, zero has no special meaning, and simply sets the lower bound of the rule to zero. 
Points 
The number of points consumed from the associated license if an installation matches this rule from the set. It would be unusual for this value to be left at zero. License that allow for installations to consume zero points usually do so on the basis of the business purpose of the particular server (such as backup), and these installations should be given a clear Exemption reason to prevent points consumption. In most licenses, the Points value is a whole number, and is normally determined by the software publisher. However, there are cases where you may need to enter a fraction of a point, and fractions can be listed as decimal numbers. For example, if a license entitlement (or a point) authorizes software running on two VMs, then each VM that matches this rule consumes half a point, which may be entered as 0.5 in the Points value. For these special cases, you may enter up to two decimal places (such as 0.25). 
Points rule name 
Remember the value you enter may be truncated in lists, and try to keep the unique part of the description up first. 
Processor type  An expression used to test for matching processors. Enter an expression that will match against one or more processor types identified in inventory. As
well as the plain text name of a particular processor, you may use:
For more information, see Special Cases and Regular Expressions.

Source 
The origin of this rule. Values are:
Not editable. 
FlexNet Manager Suite (OnPremises)
2022 R2