Concepts such as quality and availability have become self-evident in traditional utilities. Electricity is supplied in Europe as alternating current at a voltage of +/- 230 Volt and a frequency of 50 Hz. Water must also meet several criteria before it can be supplied as drinking water. The suppliers of water and electricity must also respect criteria regarding availability and communicate clearly if these criteria are not met.

Cloud solutions are end-to-end solutions whose quality and availability must also be recorded. After all, this process is slightly more complex than what we are used to with water and electricity. How do you define the quality of software and cloud solutions? Clarity must be provided here through product specifications that are well-defined and interpreted in the same way by all parties. Availability must be detailed in a set of service levels that are -also- well-defined and interpreted in the same way by all parties.

Software vendors offering cloud solutions need to ensure and explicitly list the responsibility they take regarding these product specifications and service levels. Different aspects should be considered:

• In a cloud solution the customer makes abstraction of the lower layers of the technology stack. For example, in a Software-as-a-Service solution, the customer does not have access to the physical infrastructure and the storage, but instead only consumes the front-end application or website. The agreement should specify service descriptions, service level KPIs, the consequences for not meeting the service levels, response and resolution times.
• A cloud solution can use open components but also proprietary components, protected by IP. The vendor remains responsible for indemnifying and holding the customer harmless.
• The same solution can be used by different types of customers under different circumstances. Therefore, the product and service described in the contract should match the requirements of each type of customer. If the solution is critical for the business continuity, the vendor should not disclaim its responsibility and offer the service which is aligned with the industry expectations.
• In many cases upgrade cycles are too fast for customer to perform regression testing before the cloud upgrade is required.

This brings us to principle eight: service levels and product specifications shall be explicitly listed and take into account the context of the customer.