Makes sure services are as available as agreed (availability being the ability of a service or component to carry out its agreed function when needed), so customers and users get what they need. It negotiates and agrees targets that can be met; designs infrastructure and applications to reach the levels required; makes sure services and components can gather the data needed to measure availability; monitors, analyses and reports on it; and plans improvements. Availability depends on how often a service fails (MTBF) and how fast it is restored (MTRS). Targets take into account which vital business functions are affected, how slow the service can get before it is unusable, and when it must be up as opposed to maintenance windows. Measures such as minutes of user outage, lost transactions, lost business value and user satisfaction suit different services. Availability is weighed in portfolio decisions, protected during improvements, captured as requirements in engage, designed and tested for in transition, considered when building or buying, and measured and acted on as events occur in delivery.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.