Skip to content
Calcrivo

Maintenance Window Calculator

Plan a change window: task time, rollback reserve, verification and whether it fits before the impact deadline.

Inputs

devices
minutes
streams
minutes
minutes
minutes

Total Time Required

142minutes

Execution Time

72minutes

Rollback Reserve Held Back

76minutes

Point of No Return

164minutes into the window

Does It Fit?

Fits with 98 minutes of slack

Step by step

  1. Values used

    Devices to change = 24 devices; Time per device = 12 minutes; Devices worked in parallel = 4 streams; Pre-checks and preparation = 30 minutes; Post-change verification = 40 minutes; Window length available = 240 minutes

  2. Maintenance Window

    total = preparation + (devices × time per device ÷ parallel streams) + verification; rollback reserve = half the execution time + verification.

  3. Total Time Required

    = 142 minutes

  4. Execution Time

    = 72 minutes

  5. Rollback Reserve Held Back

    = 76 minutes

  6. Point of No Return

    = 164 minutes into the window

  7. Does It Fit?

    = Fits with 98 minutes of slack

How it works

Execution time scales down with parallelism but preparation and verification do not, so they dominate small changes. The rollback reserve is subtracted from the end of the window to give the point of no return — the moment after which backing out no longer fits. Changes that overrun their window turn into unplanned outages with no rollback path, which is why the point of no return matters more than the total duration.

Formula

Maintenance Window

total = preparation + (devices × time per device ÷ parallel streams) + verification; rollback reserve = half the execution time + verification.

parallel streams
How many devices are worked on simultaneously
point of no return
Latest start time from which a rollback still completes inside the window

Frequently Asked Questions

How is Maintenance Window calculated?

total = preparation + (devices × time per device ÷ parallel streams) + verification; rollback reserve = half the execution time + verification. Execution time scales down with parallelism but preparation and verification do not, so they dominate small changes. The rollback reserve is subtracted from the end of the window to give the point of no return — the moment after which backing out no longer fits.

Why does Maintenance Window matter?

Changes that overrun their window turn into unplanned outages with no rollback path, which is why the point of no return matters more than the total duration.

What values do I need to enter?

This calculator takes 6 inputs: Devices to change, Time per device, Devices worked in parallel, Pre-checks and preparation, Post-change verification, Window length available. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

You might also need