Overview of the Manage CPC Configurations tool


Use the Manage CPC Configurations cost management tool to configure the CPCs of your enterprise with your IBM contract so that all pricing arrangements are accounted for and included in the cost models.

The Manage CPC Configurations tool enables you to control the pricing method to apply to each CPC when building the cost models. For each CPC, you can choose one of the following methods:

  • Sysplex pricing
  • Country Multiplex Pricing (CMP)
  • Multi-Version Measurement (MVM) pricing

    Note

    When you enable Country Multiplex Pricing:

    • The pricing metrics for all CPCs default to CMLC
    • Any LPARs specified as zNALC are changed to MzNALC
    • Sysplex pricing and MVM pricing are deactivated and are not available for selection

For each CPC, the Manage CPC Configurations tool lists the default pricing metric type applied to the cost models for all MLC products on that CPC. If applicable, the configuration also specifies the PricingPlex that aggregates the MSU utilization of the CPC into a group for pricing purposes.

The Manage CPC Configurations dialog box is as follows:

image2020-7-31_17-7-53.png

Note

CPC configuration within a PricingPlex is applicable only if your CPCs are combined into a PricingPlex as allowed by your IBM license agreement. If no PricingPlex exists for a CPC based on the information from the cost models, the PricingPlex name should be blank.

How the configuration determines the Pricing Metric Type

In general, the Pricing Metric Type default is determined by the CPU type you are using. However, depending on your contractual agreement with IBM, your Pricing Metric Type might vary from these established defaults. The Manage CPC Configurations tool allows you to edit the value of the Pricing Metric Type to account for any variation that might exist for your enterprise.

How the configuration determines Country Multiplex Pricing

BMC AMI Cost Management  cannot automatically determine whether Country Multiplex Pricing applies to your enterprise. However, you can specify to use Country Multiplex Pricing when building cost models by setting the Use Country Multiplex Pricing? toggle to Yes.

The Manage CPC Configurations tool then changes the display to indicate CMLC (Country Multiplex Licensing Charge) as the pricing metric type for each CPC. If you use Country Multiplex Pricing, the CMLC is the only supported pricing metric type.

Note

If you enable Country Multiplex Pricing, both Sysplex Pricing and MVM Pricing are deactivated and are not available for selection in the Manage CPC Configurations.

After changing the configuration to use Country Multiplex Pricing, you must rebuild the cost models for each affected month in order to generate MLC Monthly Summary Reports that contain CMP data. For more information, see Managing-Country-Multiplex-Pricing.

How the configuration determines Multi-Version Measurement Pricing

BMC AMI Cost Management  cannot automatically determine whether Multi-Version Measurement Pricing applies to your enterprise. However, you can specify to use MVM when building cost models by setting the Use MVM Pricing? toggle to Yes.

The Manage CPC Configurations tool then configures your cost models to use an MLC program family for software programs that have multiple MVM-eligible versions.

After changing the configuration to use Multi-Version Measurement Pricing, you must rebuild the cost models for each affected month in order to generate MLC Monthly Summary Reports that contain MVM data. For more information, see Running-the-Model-Builder-Task-manually.

How the configuration determines the PricingPlex parameter

BMC AMI Cost Management defines the PricingPlex for each CPC by determining the most active Sysplex to which the CPC is connected. However, your actual PricingPlex groupings might be different, so you can use the Manage CPC Configurations tool to add or change the PricingPlex parameter. If a CPC is not part of a PricingPlex, you can also edit the PricingPlex parameter so that its designation is blank, indicating that a PricingPlex does not apply to this CPC.

After you verify or change the PricingPlex parameter for each CPC, Cost Management does not apply the changes to the costs that are generated in the MLC Monthly Summary Report unless Use Sysplex Pricing? is set to Yes.

If Use Sysplex Pricing? is set to No, the PricingPlex groupings indicated in the PricingPlex column have no effect on cost calculations.

Note

IBM allows CPCs to be aggregated across a qualified Parallel Sysplex ('Sysplex Pricing') only when certain criteria are met. Before using Sysplex Pricing with Cost Management, you must confirm that your IBM contract contains this arrangement. Cost Management does not verify Sysplex Pricing criteria and does not use Sysplex Pricing automatically. It is the responsibility of the administrator to set Use Sysplex Pricing? correctly.

How the CPC Configuration is updated

Each time a Model Builder Task runs and a cost model is built, the CPC configuration is updated from the most recent cost data. However, Cost Management  applies the updates only to the parameters that are saved in the Manage CPC Configurations when certain conditions are met. The updates are applied as follows:

  • Cost Management adds any new CPCs to the CPC configuration with a default Pricing Metric Type and PricingPlex designation that requires your verification.
  • Cost Management does not change any values that you previously edited in the Manage CPC Configurations. Values that you defined for the CPC override the updates.
  • Based on the most recent cost model, Cost Management updates the configuration only when:
    • The CPC configuration does not yet exist
    • The CPC model does not exist in the current configuration
  • Preexisting CPCs in the CPC Configuration that no longer exist in the most recent Cost Model are not changed. These CPCs remain listed in the Manage CPC Configurations, but they are inactive and their parameters do not affect the costing data.

Note

When using the Manage CPC Configurations tool, all changes to the configuration take effect for the current month's cost model only after a model build process has run. Any cost models that have already been built for a previous month remain unaffected and reflect the pricing method that was in effect when they were built.





 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*