Back to Assessments & Documents
IT Operations and Reliability Active

Service Availability Management Maturity Assessment

A 59-question diagnostic across 9 domains that tests whether availability targets come from business need and obligations, services are designed, monitored end to end, tested, maintained and supported to meet them, and d...

Overview

A 59-question diagnostic across 9 domains that tests whether availability targets come from business need and obligations, services are designed, monitored end to end, tested, maintained and supported to meet them, and delivered availability is measured, reported and improved. Written for the Head of IT Operations, Availability Manager or Head of Infrastructure who needs to answer: do we know how available each critical service must be and what an outage costs, is every service built and run to meet that target, and can we prove the availability users actually experience?

Detailed Description

This assessment asks whether the organization knows how available each critical service must be and what an outage costs, whether services are designed, monitored, tested, maintained and supported to meet those targets, and whether the availability users actually experience is proven. It starts with governance: the availability policy, a register of regulatory, critical infrastructure, contract and data residency obligations, roles, criticality tiers drawn from business impact analysis, a measurement standard that counts degraded service, and analyst competency. Requirements cover vital business functions, cost of downtime, targets, reliability requirements for new services and planned downtime. Design and analysis test the resilience standard, graceful degradation, dependency maps that include hidden shared services such as name resolution, certificates and identity, single points of failure in components, people, credentials and tools, fault trees, predicted availability and design review. Monitoring is assessed at two levels that are often confused: component health coverage, and end-to-end monitoring of each vital business function from the user's view, with delivered availability calculated from the end-to-end signal, reliability data collected from real outages and failures predicted before they happen. Resilience operations test redundancy health, denial of service protection, failover tests, controlled resilience experiments, safety limits on automation and AI agents that can change production, and break-glass and out-of-band access for when the usual paths are down. Maintainability covers maintenance strategy chosen from failure modes, preventive maintenance, downtime minimization, staged release of changes and vendor-pushed updates, prevention of outages from expired certificates, keys and contracts, restoration including cold start order, spares and unsupported components. Supplier and dependency questions address contracted availability, cloud zones and regions within data residency limits, supplier monitoring, shared platforms, power, cooling and carrier route diversity including subsea paths, concentration on one provider, route or country, and AI model provider fallback. The final domains test risk treatment, reporting, outage analysis, cost of downtime, error budgets, the availability plan and measured improvement. Each question is scored on whether the practice is documented, carried out and demonstrably effective, so results show whether a gap is a missing standard, an adoption problem or a lack of evidence.

Assessment Details

Audience

Primary: Head of IT Operations / Availability Manager / Head of Infrastructure and Cloud / Site Reliability Lead. Secondary: service owners, enterprise and solution architects, monitoring and platform engineers, supplier and cloud managers, risk, compliance and finance staff, and internal audit.

Purpose

Shows whether critical services are built and run to meet the availability the business and regulators need, where hidden dependencies, single points of failure, blind spots in monitoring, unsafe automation, expiring credentials, weak suppliers or concentrated routes threaten it, and which improvements most reduce outage frequency, duration and cost.

Effort

Initial assessment: 12 to 16 hours of assessor time over two to three weeks with availability, architecture, monitoring, infrastructure and cloud, supplier, risk and service owners. Evidence gathering: obligation and target registers, dependency maps and availability models, monitoring coverage and end-to-end checks, outage and reliability records, failover and experiment results, maintenance, release and expiry records, and supplier reports. Reassessment: 6 to 8 hours.

Cadence

Annually, and after a major outage, a significant architecture, cloud or supplier change, a change in regulatory obligations or business criticality, or the introduction of automation or AI agents that act on production.

Framework Alignment

ISO/IEC 20000-1:2018 COBIT 2019 ITIL 4 Foundation ISO/IEC 27001:2022 NIST SP 800-53 Rev 5 IEC 60300-1:2024 IEC 60300-3-2:2004 IEC 60300-3-11:2009 IEC 60300-3-14:2024 IEC 61078:2016 IEC 60812:2018 IEC 61025:2006 ISO/IEC 25010:2023 ISO/IEC 42001:2023 OWASP Top 10 for LLM Applications 2025 UAE CIIP Policy v2.0 UAE National Cloud Security Policy v2.0 ADHICS v2 NCA ECC-2:2024

KPIs

  • Critical Services Meeting Availability Target - Share of critical services whose delivered availability met their target in each of the last 12 months, from the Availability Report. Target: at least 95%.
  • End-to-End Monitoring Coverage - Share of vital business functions of critical services covered by external scripted transactions. Target: 100%.
  • Failover Test Success - Share of redundant critical components failed over successfully in a planned test within the last 12 months. Target: 100%.
  • Restoration Readiness - Share of critical components with a restoration procedure tested within 12 months whose measured restore time meets the target. Target: 100%.
  • Expiry-Caused Outages - Number of critical service outages caused by an expired certificate, domain, license, key or contract. Target: 0.

Dependencies

None required: the model stands alone. Business Impact Analysis: recommended first; criticality tiers, vital business functions and cost of downtime draw on its results where they exist. Business Continuity and Disaster Recovery Management: owns site and region loss and recovery; this model owns redundancy, failover and degradation within the design. Capacity Performance Management and Data Center and Facilities Operations: own capacity headroom and power and cooling engineering; this model records power, cooling and route diversity as availability dependencies. Incident Management, Problem Management and Post-Incident Review and RCA Quality: own incident handling, root cause and review quality; this model uses their outputs for outage analysis. Change Management, Service Level Agreements and Performance and AI Governance: own change control, agreements and AI agent authorization; this model assesses release safety, targets and automation safety for availability. Recommended: access to monitoring, outage, configuration and supplier data so delivered availability is scored from records.

Assessment Outline

(9 domains · 59 questions)
  1. 1

    1 Availability Governance

    Availability policy, regulatory and contractual availability obligations, roles, service criticality tiers, measurement standard and analysis competency

    • 1.1 Availability Management Policy 1 questions
    • 1.2 Availability Obligations 1 questions
    • 1.3 Availability Roles and Ownership 1 questions
    • 1.4 Service Criticality Tiers 1 questions
    • 1.5 Availability Measurement Standard 1 questions
    • 1.6 Availability Analysis Competency 1 questions
  2. 2

    2 Availability Requirements

    Vital business functions, cost of downtime, availability targets, availability and reliability requirements for new services, planned downtime agreements

    • 2.1 Vital Business Functions 1 questions
    • 2.2 Cost of Downtime 1 questions
    • 2.3 Service Availability Targets 1 questions
    • 2.4 Availability Requirements for New and Changed Services 1 questions
    • 2.5 Planned Downtime Agreements 1 questions
  3. 3

    3 Availability Design and Analysis

    Resilience design standard, graceful degradation, dependency mapping and reliability block diagrams, single points of failure, fault trees, predicted availability, design review

    • 3.1 Resilience Design Standard 1 questions
    • 3.2 Graceful Degradation Design 1 questions
    • 3.3 Service Dependency Discovery 1 questions
    • 3.4 Reliability Block Diagram Modeling 1 questions
    • 3.5 Single Point of Failure Analysis 1 questions
    • 3.6 Fault Tree Analysis 1 questions
    • 3.7 Predicted Availability 1 questions
    • 3.8 Availability Design Review 1 questions
  4. 4

    4 Availability Monitoring and Measurement

    Component monitoring coverage, end-to-end service monitoring, outage register, delivered availability, reliability data collection, predictable failure detection

    • 4.1 Component Monitoring Coverage 1 questions
    • 4.2 End-to-End Service Monitoring 1 questions
    • 4.3 Service Health Model 1 questions
    • 4.4 Outage Recording and Classification 1 questions
    • 4.5 Delivered Availability Measurement 1 questions
    • 4.6 Reliability Data Collection 1 questions
    • 4.7 Predictable Failure Detection 1 questions
  5. 5

    5 Resilience Operations and Testing

    Redundancy health, denial of service resilience, failover testing, resilience experiments, automation and AI agent safety, emergency and out-of-band access

    • 5.1 Redundancy Health Verification 1 questions
    • 5.2 Denial of Service Resilience 1 questions
    • 5.3 Failover Testing 1 questions
    • 5.4 Resilience Experiments 1 questions
    • 5.5 Automation and AI Agent Safety 1 questions
    • 5.6 Emergency and Out-of-Band Access 1 questions
  6. 6

    6 Maintainability and Planned Downtime

    Maintenance strategy selection, preventive maintenance, downtime minimization, release safety, expiry-driven outage prevention, restoration, spares and support, unsupported components

    • 6.1 Maintenance Strategy Selection 1 questions
    • 6.2 Preventive Maintenance 1 questions
    • 6.3 Planned Downtime Minimization 1 questions
    • 6.4 Release Safety 1 questions
    • 6.5 Vendor-Pushed Update Staging 1 questions
    • 6.6 Expiry-Driven Outage Prevention 1 questions
    • 6.7 Restoration Procedures 1 questions
    • 6.8 Spares and Support Coverage 1 questions
    • 6.9 Unsupported Component Replacement 1 questions
  7. 7

    7 Supplier and Dependency Availability

    Supplier commitments, cloud zones and regions within data residency limits, supplier monitoring, shared platforms, power, cooling and connectivity diversity, concentration risk, AI provider fallback

    • 7.1 Supplier Availability Commitments 1 questions
    • 7.2 Cloud Provider Availability Design 1 questions
    • 7.3 Supplier Availability Monitoring 1 questions
    • 7.4 Shared Platform Availability 1 questions
    • 7.5 Power, Cooling and Connectivity Diversity 1 questions
    • 7.6 Provider Concentration Risk 1 questions
    • 7.7 AI Model Provider Availability 1 questions
  8. 8

    8 Availability Risk, Reporting and Planning

    Risk treatment, availability and reliability reporting, outage analysis, cost of downtime reporting, error budget policy, availability plan

    • 8.1 Availability Risk Treatment 1 questions
    • 8.2 Availability and Reliability Reporting 1 questions
    • 8.3 Service Outage Analysis 1 questions
    • 8.4 Business Cost of Downtime Reporting 1 questions
    • 8.5 Error Budget Policy 1 questions
    • 8.6 Availability Plan 1 questions
  9. 9

    9 Measurement and Improvement

    Availability metrics, process review, audit, target recalibration, improvement plan

    • 9.1 Availability Metrics Dictionary 1 questions
    • 9.2 Availability Process Review 1 questions
    • 9.3 Availability Process Audit 1 questions
    • 9.4 Availability Target Recalibration 1 questions
    • 9.5 Availability Improvement Plan 1 questions

At a Glance

Category IT Operations and Reliability
Type Free
Roles 6
Domains 9
Questions 59

Still have questions? Get in touch

ITSGovernance