Does a License Agreement have to have at least one feature group? VLM is really just a Party 'Simplified' attributes for this Vendor are VendorName, and Description, which can be gotten from the Pary model There are a bunch of attributes feature group attributes in SAm Definitions - maybe not in SDC?? Only EntitlementPoolDesc attributes currently being used are Name and MRN. Other fields are present but not supported in downstream systems. Only attributes presently used are name, metric type and metric value. What do we do with keyFunction,LicenseKeyType, etc? StartDate and ExpiryDate attributes are covered by validFor. Note that these fields are presently not used. Description and Status is not presently required, but from a modeling view, it should be. Only name and type are required. MRN should also be provided, but is not required. ASDC has a pool (group) desc, not license or entitlement desc because they are not in SDC.

Lifecycle stage or state (e.g., Instantiation or Activation) at which the license key is applied to the software. Valid values: Universal, Unique Universal - a single license key value that may be used with any number of instances of the software. Unique - a unique license key value is required for each instance of the software. A License Key Group is created for each type of License Key that is required for the software. Each License Key Group is assigned a Name and Description for modeling purposes and is uniquely identified by a UUID. In addition, a list of characteristics of the License Key Group are defined. The license key group model provides a description to systems like ALTS for the license keys that are provided by a vendor. ALTS will create a “group” and Purchasing systems (GPS and HP Asset Center) will send the inventory of license keys/files to be held by ALTS in the appropriate group. Controllers will request license keys from ALTS using the UUID of the group, as directed by the ASDC models for the software (i.e. VFs). A license key group is not specific to a feature group. A license key group may be related to multiple feature groups of a software item or even to multiple software items. Pool limits applied by the service provider Pool limits applied by the vendor. The license key may be ‘universal’ or ‘unique’ or ‘one-time’. - A ‘universal’ value indicates that the same exact license key (string) may be associated with all instances of the software. - A ‘unique’ value indicates that each instance of the software must be related to a unique license key (string). When no longer needed, the key may be returned to the license key pool for reuse. - A ‘one-time’ value indicates that each instance of the software must be related to a unique license key (string). When no longer needed, the key may not be reused. Units can be either absolute or a percentage (%). Specified threshold value for the license key pool. Specifies how the key must be purchased. If in blocks of 1000, the increment would be 1000. Identifier for the entitlement as described by the vendor in their price list / catalog /contract. The Vendor License Model enbables a service provider to track the usage of vendor products used used in resources created in ASDC. VLM is used to track instaantiations ("entitlements") of the vendor provided software used by the servi e provider for given resources. A VLM is actually be a "Party". There should only be on VLM per vendor (given it appears to be "party", but there is no restriction. The name of the vendor providing this resource. Specifies the use rights for the software as described by the license. The use rights may be quantified by various metrics: # users, # software instances, # units. Customer RTU is within the customer subscription. Entitlement is related to how the service provider purchased the software from the supplier, 1 RTU may equate to 5 instances of the software. Either no key, universal key, or unique key per instance required. Identifier for the entitlement as described by the vendor in their price list / catalog / contract. The minimum number of entitlements that need to be purchased. For example, the entitlements must be purchased in a block of 100. If no minimum is required, the value will be zero. A list of any reporting requirements on the usage of the software product. (e.g.: quarterly usage reports are required) Type of license applicable to the software product. (e.g.: fixed-term, perpetual, trial, subscription.) Valid values: year, quarter, month, day. Not applicable when license type is Perpetual. Number of years, quarters, months, or days for which the license is valid. Not applicable when license type is Perpetual. A variable set of values that identify the limits that may be imposed by an entitlement instance in the pool. Multiple constraints may be applicable for an instance of entitlement in the pool. For example, an entitlement based on GB and number of sessions. Increments, aggregation function, time scope, threshold value may repeat for each metric in the list. Limits can be applied by the vendor or the service provider. Specifies if this pool holds entitlements based on usage of the software (number of users), number of sessions, country, line of business, etc. The value of some limit being applied. Type of aggregation being performed (Peak or Average) The units of the limit (Trunks, Users, Subscribers, Sessions, tentants, Tokens, Seats, TB, GB, MB, ...) Units time is specified in (day, month, hour, minute, second, millisecond. LimitMetricType if Other enumeration is selected. Represents an instance of a EntitlementDesc. Specifies the use rights for the software as described by the license. An EntitlementPool is created for each type of Entitlement that is required for the software products. An EntitlementPool is not specific to a Feature Group. An Entitlement Pool may be related to multiple Feature Groups of a software product or even to multiple software products. Purchased entitlements are inventoried in the Entitlement Pools. Multiple pools for the same type of entitlement may be created based on the constraints. An Entitlement Pool is created for each type of Entitlement that is required for the software products. Each Entitlement Pool is assigned a Name and Description for modeling purposes and is uniquely identified by a UUID. In addition, a list of characteristics of the Entitlement Pool are defined. Controllers will request entitlements. An entitlement pool is not specific to a feature group. An entitlement pool may be related to multiple feature groups of a software item or even to multiple software items. Note: The only fields being used in this class are Name and MRN (manufactureReferenceNumber. The rest are optional. Note: StateDate and ExpiryDate are covered by the inherited validFor attribute. Note: description is required according to the inherited attribute, but it presently is optional. Note: description is required according to the inherited attribute, but it presently is optional. Pool limits applied by the service provider Pool limits applied by the vendor. EntitlementPoolDesc is the basis for an EntitlementPoolInstance. Identifier for the entitlement as described by the vendor in their price list / catalog /contract. This field contains information to tell a Designer how the entitlement must be purchased. For example, if the entitlement must be purchased in blocks of 1000, the increment would be 1000. A description of a threshold that will be assessed for some business purpose (e.g. 20% of entitlement pool remains available). (The threshold of interest to DCAE or Capacity Planning, etc.) This may be an absolute value or a percentage. For example: when 90% of the pool is in-use, trigger an additional purchase of inventory. A description of a threshold that will be assessed for some business purpose (e.g. 20% of entitlement pool remains available). (The threshold of interest to DCAE or Capacity Planning, etc.) This may be an absolute value or a percentage. For example: when 90% of the pool is in-use, trigger an additional purchase of inventory. Specifies the Units for the ThresholdValue. This field contains information to tell a Designer how the entitlement must be purchased. For example, if the entitlement must be purchased in blocks of 1000, the increment would be 1000. Identifier that stays the same irrespective of version. An EntitlementPool describes the characteristics of a type of entitlement and the behavior of the entitlement instances in the pool. Management of the collection. Feature groups represent a set of the features of the software. Feature groups may be defined by the vendor and/or by the service provider. Software may be related to multiple feature groups. At least one feature group will be related to software. If no sub-sets are needed, a single feature group will be defined that represents the base or core capabilities of the software. If an Entitlement Pool or License Key Group is associated with a particular Feature Group, the Feature Group becomes a “constraint” for the pool/group. An agreement between the service provider and a given vendor granting the service provider to use the vendor's products. Generally the license agreement is specific to a family of vendor products and/or to some service provider's project/product or product family. License agreement description. Free form text. Includes information such as operating system or hypervisor required for the software. This may also contain factors to be considered in deployment/placement of the software instances. These requirements and constraints may need to be abstracted as policies or other business rules. Term of the license: -fixed term -perpetual -unlimited -subscription OCL true Valid values: year, quarter, month, day. Not applicable when license type is Perpetual. Units of the entitlement/license term. Valid values: year, quarter, month, day.