Peak Shift Simulator
R4HA Peak Shift Simulator

What if your batch left the peak?

Under peak-based mainframe software pricing, the monthly bill follows the highest rolling four-hour average (R4HA) of MSU usage. Move part of your batch out of the peak hours and see what happens to the peak, and to the bill.

MSUYour peak day, hour by hour

Hourly MSU after the shift Hours work moves out of Hours work moves into R4HA before R4HA after

01Your usage profile

Start from an example day, or paste your own hourly MSU from your peak day.

Edit hourly values
Separate with commas, spaces or new lines. Changes apply as you type.

02The shift

Only move work that can really move. Jobs tied to end-of-day cutoffs or tight dependencies stay where they are.

Move work out of these hours
to
Into these hours
to
25% Applied to the MSU in the source hours
$
Example value. Use the incremental rate from your contract.

How this works, and its limits

The R4HA for each hour is the average of that hour and the three before it, wrapping around midnight. Real reporting measures it every five minutes across the whole month, and the bill uses the month's highest value. This tool uses hourly values for one representative peak day.

Savings use one flat rate per MSU of peak. Real pricing is tiered, so the incremental rate is usually lower than the average rate; enter the incremental rate from your contract. Capping changes the picture too.

Under consumption-based pricing, such as Tailored Fit Pricing, moving work in time doesn't lower the bill; reducing total usage does. This is a planning estimate, not a quote.