Scheduled Maintenance and Availability Accounting
What you'll learn: How planned maintenance windows affect your availability calculations and what strategies keep you SLA-compliant.
The Core Idea
When calculating availability using the formula Availability = MTBF / (MTBF + MTTR), not all downtime is created equal. Scheduled maintenance is planned downtime where you intentionally take systems offline for upgrades, patches, or infrastructure changes. The critical question: should this count against your availability SLA?
Accounting Strategies
Exclude from SLA calculations:
Most organizations exclude properly announced maintenance windows from availability metrics. If you promise "99.9% uptime excluding scheduled maintenance," you're contractually protected during planned work. This is like a store posting "Closed Sundays for inventory"—customers know not to expect service.
Include in calculations (stricter):
Some SLAs count all downtime, planned or not. This forces extreme discipline—maintenance must use rolling deployments, blue-green switches, or happen so rarely it barely impacts the numbers. Think of airlines: passengers don't care if a delay is "scheduled"—they just want to arrive on time.
Key Considerations
- Advance notice requirements: SLAs typically specify how far ahead you must announce maintenance (e.g., 7 days)
- Maintenance window limits: Often capped at X hours per month or quarter
- Off-peak timing: Maintenance during low-traffic hours minimizes user impact even if excluded from SLA
- Transparency: Even if excluded, tracking maintenance downtime builds trust and reveals optimization opportunities
Key Takeaway: Scheduled maintenance can be excluded from availability SLAs with proper notice and limits, but how you account for it determines whether you optimize for operational convenience or true user experience—choose the approach that aligns with your reliability commitments and competitive positioning.