Availability & Uptime vs SLO The engineering team measures system availability against a defined SLO documented in the AISDP. For high-risk systems where unavailability could force deployers to make decisions without AI support, availability degradation is a compliance concern. The monitoring tracks both planned and unplanned downtime, computes rolling availability percentages over defined windows (hourly, daily, monthly), and alerts when availability trends downward or when a single outage exceeds the maximum tolerable duration. Where a fallback mechanism does not exist (the deployer’s process assumes a valid AI output is always available), unavailability can introduce silent failures in the deployer’s workflow. The SLO must account for this dependency, and the fallback procedure documentation (Instructions for Use) must specify what the deployer should do when the system is unavailable. Key outputs

• Availability monitoring against AISDP-declared SLO
• Planned and unplanned downtime tracking
• Rolling availability computation over multiple windows
• Fallback procedure documentation for deployers