Contract structure

A contract can contain multiple package mappings. Each package mapping includes a base package with one DEV tenant, one TEST tenant, and one PROD tenant by default. How entitlements are scoped, shared, and pooled across these tenants depends on the customer type.

Standard customer

For Standard customers, entitlements are tracked and reported for each package mapping individually.

• Entitlements are managed for each package mapping and are not pooled across package mappings.
• CP is tracked for each tenant, while RSU, API, and RIH are shared across the package mapping.
• A package mapping can include additional tenants.

Usage customer

For Usage customers, entitlements are shared across the base package.

• CP entitlement is shared across all tenants (PROD, TEST, and DEV) in the base package. DEV usage cannot exceed 200,000 CP.
• RSU, API, and RIH are shared across the base package.
• Additional tenants are not supported.

Pooled customer

For Pooled customers, entitlements are shared across all contracts and package mappings in the pool.

• RSU, API, and RIH are pooled across all package mappings and contracts that share the same package mapping and are marked as pooled.
• CP is pooled by environment, and base package tenants and additional tenants pool separately:
  • Base package PROD and TEST tenants pool with other base package tenants of the same environment.
  • Additional PROD and TEST tenants pool with other additional tenants of the same environment, not with the base package tenants.
  • DEV tenants are never pooled.

Package mapping and tenant views

The page presents entitlement and usage information at the following levels:

• Package Mapping Entitlements and Usage: Displays usage and entitlement details for each contract and package mapping. This view helps you compare usage with entitlements, monitor consumption trends, and identify package mappings that are nearing contractual limits.
• Usage CP Entitlement (only for Usage customers): Displays CP usage against the CP entitlement that is shared across all tenants (PROD, TEST, and DEV) in each base package. DEV usage cannot exceed 200,000 CP.
• Pooled CP Summary (only for Pooled customers): Displays aggregated CP usage against the pooled CP entitlement for each environment, with separate rows for PROD and TEST tenants. DEV tenants are not pooled.
• Tenant Entitlement and Usage: Displays usage and entitlement details for individual PROD, TEST, and DEV tenants within each package mapping. This helps you track usage against allocated entitlements and review capacity and renewal needs.

For more information on entitlements and metrics on this page, see Entitlements.

Usage status indicators

The Entitlement and Usage Summary page uses color-coded badges to show how current usage compares with entitlement thresholds. These indicators help you quickly identify usage that is within limits, approaching a limit, nearing an overage, or over entitlement.

Usage by month

Use the date selector dropdown to view usage metrics for the selected month. This month displays month-to-date usage.

The page updates to show entitlement and usage information for the selected month.

Entitlement and usage calculation

The Entitlement and Usage Summary page calculates usage over a calendar month based on values collected through the tenant reporting process. Entitlements are always shown in real time and do not reflect historical states. When you review past months, usage is evaluated against the current entitlement values.

The aggregation level depends on the customer type. For metrics that use a monthly average, the average is updated each day during the month, so the value shown during the month reflects usage collected so far.The following table shows when each metric is measured, how the monthly value is calculated, and how usage is aggregated.

For compliance evaluation, the value shown on the last day of the month is used.