Utility and warranty

A service must do the right thing, and it must do it well enough. ITIL captures these two requirements with the terms utility and warranty. A banking app that lets you transfer money has utility; a banking app that lets you transfer money at 2 a.m. on payday without crashing or leaking your data also has warranty. This lesson defines both terms, explains why both are needed for value, breaks warranty into availability, capacity, security, continuity and performance, and works through the arithmetic of availability targets, service credits and capacity headroom.

Utility: what the service does

ITIL defines utility as the functionality offered by a product or service to meet a particular need. Utility is often summarized as "what the service does" and described as fitness for purpose. A service has utility if it either supports the performance of the consumer, by helping them do something better, or removes constraints from the consumer, by taking away something that was holding them back.

• Supporting performance: a reporting service that helps managers make faster, better decisions.
• Removing constraints: a remote access service that lets staff work from home, removing the constraint of being in the office.

Utility is about features and functions. If a payroll service cannot handle overtime rules for your industry, it lacks utility for you, however reliable it is.

Warranty: how the service performs

ITIL defines warranty as the assurance that a product or service will meet agreed requirements. Warranty is often summarized as "how the service performs" and described as fitness for use. It is usually expressed through agreed service levels in areas such as:

• Availability: the service is there when consumers need it.
• Capacity: the service can handle the volume of demand, now and in the future.
• Security: confidentiality, integrity and availability of information are protected.
• Continuity: the service can recover from serious disruption within acceptable time and data loss.
• Performance: the service responds quickly enough, for example pages load in a few seconds.

Warranty is about assurance. Consumers need confidence that the functions they rely on will be there, at the speed and scale they need, safely.

Why both are needed

A service with utility but no warranty is like a powerful car that will not start on cold mornings: impressive in theory, useless when you need it. A service with warranty but no utility is like a perfectly reliable car that cannot carry the load you need to move: dependable but pointless for you. Value requires both.

Availability in numbers

Availability is usually expressed as a percentage of agreed service time. The difference between targets that sound similar can be large in practice. The table shows how much downtime each level allows in a year of 8,760 hours (365 days of 24 hours).

Higher availability costs more, because it needs redundant components, automated failover, more monitoring and faster response. The right target is the one that matches the consumer's needs and willingness to pay. An internal reporting tool used during office hours may need far less than a payment service that customers use around the clock.

Agreed service time also matters. A service agreed to be available Monday to Friday, 08:00 to 18:00, has 10 × 5 × 52 = 2,600 hours a year of agreed time, not 8,760. At 99.5 %, that allows 13 hours of downtime during business hours, while maintenance at night does not count.

Capacity and performance

Capacity means the service can handle demand. Performance means it responds quickly enough while doing so. They are closely linked: as load approaches capacity, response times usually rise sharply. Providers therefore plan for headroom, a margin of spare capacity above expected peak demand.

Security and continuity

Security warranty assures consumers that information is protected: kept confidential, accurate and available to authorized people. For many services, especially those handling personal, financial or health information, security is the first warranty consumers ask about. Continuity assures that the service can recover from serious events such as data centre failures, cyberattacks or natural disasters. Two common continuity measures are:

• Recovery time objective (RTO): the maximum acceptable time to restore the service after a disruption.
• Recovery point objective (RPO): the maximum acceptable amount of data loss, measured in time. An RPO of 15 minutes means backups or replication must ensure no more than 15 minutes of data is lost.

Experience and sustainability alongside utility and warranty

ITIL (Version 5) places experience and sustainability next to utility and warranty as key considerations. A service may be fit for purpose and fit for use but still be unpleasant to use, which lowers perceived value (lesson 9 covers experience). It may also meet every service level while using far more energy than necessary. Many organizations now include sustainability measures, such as energy use per transaction or hardware lifespan, in how they judge services. For the exam, know utility and warranty precisely, and be aware that Version 5 treats experience and sustainability as essential parts of the value picture.

Agreeing utility and warranty with consumers

Utility and warranty requirements should be agreed with consumers, not guessed by the provider. Utility requirements usually come from conversations about outcomes: what consumers need to be able to do. Warranty requirements come from asking how much disruption consumers can tolerate, when they need the service most, how much demand they expect and what information is sensitive. The answers often differ by consumer group. Finance may need near-perfect availability during the last three days of each month and very little at other times; a sales team may need speed during business hours in several time zones.

Over-specifying warranty is as wasteful as under-specifying it. Moving from 99.9 % to 99.99 % availability can require redundant data centres, extra staff on call and more expensive suppliers. If consumers cannot perceive the difference, the extra cost destroys value rather than creating it. Good providers present options with their costs, such as "99.5 % at the current price, 99.9 % for an extra $2,000 a month", and let the customer and sponsor choose.

A final point concerns how warranty is reported. Averages can hide problems: a monthly availability of 99.9 % may conceal one four-hour outage during the busiest morning of the month. Reporting the timing and impact of outages, not just the percentage, gives consumers a truer picture of the warranty they actually received.

Utility and warranty together describe what consumers can rely on; neither alone is a promise of value.