Availability Management Policy
From IT frameworks
This policy defines optimum availability for the various services. The policy covers only the most important standards for Availability Management.
The Availability Manager must aim to have the service availability up to the requirements set by the SLAs. The SLAs dictate the system requirements for availability. This policy gives some guidelines to how that is best achieved.
Critical services and systems
The Availability Manager has the responsibility for marking the appropriate services and systems as Business Critical. The Availability Manager must see to it that all business critical services and systems have:
- Proper redundancy
- Monitoring of availability (according to the SLA)
- A defined MTRS (Main Time to Restore Service)
- Procedures for restoring service components in the case of unavailability
- Proper backup and restore routines (coordinate with ITS Continuity Management and Information Security Management)
- A test platform and proper release procedures for upgrades (coordinate with Release and Deployment Management and Validation and Testing Management)
- Proper security to ensure that availability is not compromised by security breeches (coordinate with Information Security Management, refer to the security policy)
- Underpinning contracts with vendor(s) to ensure availability
- An entry in the Service Catalogue so that the service is indeed available to the customers (if relevant)
Non-critical services and systems
Where the SLA for non-critical services and systems does not give a set standard, the Availability Manager must still ensure that they have:
- Basic monitoring of availability
- Basic backup and restore routines
- Basic security
- Underpinning contract with vendor(s) in case the IT department does not have the proper competence in-house
- An entry in the Service Catalogue (if relevant)
Every autumn, the Availability Manager submits an availability plan to Change Management for the next year.

