AWLC and Advanced Workload License Charges.

Advanced Workload License Charges (AWLC) is one specific pricing metric inside the Monthly License Charge family. It applies to the WLC eligible IBM Z software stack, z/OS, CICS, Db2 for z/OS, IMS, and MQ among them, on supported IBM Z hardware. AWLC superseded the older Variable Workload License Charges metric and lowered the per MSU rates while keeping the same underlying mechanic: under sub-capacity terms, you pay on the peak rolling four hour average MSU recorded that month, not on the rated capacity of the machine.

For smaller machines, IBM applies AEWLC, Advanced Entry Workload License Charges, the entry tier counterpart with its own rate table tuned to lower capacity systems. The mechanics are identical. Which metric governs your contract is determined by the machine model, not by a buyer election. On current hardware, AWLC or AEWLC is what is actually setting the monthly number most organizations call simply MLC.

Directional only, using illustrative per MSU figures to show the mechanic, not a quote. AWLC rates are banded and regressive: the first block of MSU carries the highest per MSU rate, and each higher band carries a lower one. A product whose monthly peak rolling four hour average lands at 1,200 MSU is priced by walking up the bands, not by multiplying 1,200 by a single rate.

Illustrative rate index, not pricing. Real AWLC bands and rates are published by IBM and vary by product.

Two consequences follow for the buyer. First, because the metric is the peak rolling four hour average, a single busy hour can set the whole month for that product, exactly as under the broader MLC model. Second, because the rate falls as capacity climbs, the cost of growth is non linear: adding MSU at the top of a large stack is far cheaper per unit than the cost of the first block, while shaving MSU near the base saves more per unit than shaving at the top. Capacity decisions made without modeling the curve leave money on the table in both directions.

AWLC exposure concentrates in the same failure modes as the rest of the MLC stack. Incomplete or late Sub-Capacity Reporting Tool submissions risk reverting to full capacity, the most expensive basis, and an audit with unreliable data lands the same way. Peak creep is the quiet cost: one new batch job or a report scheduled into the existing peak window can lift the rolling four hour average for the month and reprice the band. And because AEWLC and AWLC apply to different machine classes, a hardware refresh can silently move you between metrics, changing the rate table under your contract without anyone modeling the before and after.

Every AWLC lever acts on the peak that sets the bill. Move non urgent batch and reporting out of the peak window with disciplined peak shaving so they never contribute to the billed hour. Set defined capacity soft caps on LPARs to hold the rolling four hour average below a ceiling you choose. Offload eligible work to the zIIP engine, which does not count toward the general purpose peak. Keep SCRT clean and on time so sub-capacity holds. Model the regressive tiers before any capacity change. And at renewal, weigh AWLC against Tailored Fit Pricing, where an annual baseline replaces the monthly peak as the thing you manage. The full set of technical levers lives on our MSU consumption optimization page.

Related metrics: Monthly License Charge, MSU explained, and the rolling four hour average. Where these products live: z/OS licensing. Put it to work: IBM cost optimization.