Common use of Utility Architecture Clause in Contracts

Utility Architecture. The layered architecture of a typical utility computing system is shown in Figure 2. From top to bottom it is possible to identify four layers, a User or Broker submits its requests using various applications to the utility computing system, the Service Request Examiner is responsible for admission control, SLA Management balances workloads, and a Resource or Service Provider offers resources or services. Us- ers or Brokers, who act on users‟ behalf, submit their service requests and applications, from anywhere in the world, to be processed by utility computing systems. When a service request is submitted, the Service Request Examiner uses Admission Control mechanism to interpret its QoS requirements before determin- ing whether to accept or reject it. Thus, it ensures that there is no overloading of resources whereby many service requests cannot be fulfilled successfully due to limited availability of resources/services. Then, the Service Request Examiner interacts with the SLA Management to decide whether to accept or reject the request. - User-driven Service Management - Computational Risk Management - Autonomic Resource Management

Utility Architecture. The layered architecture of a typical utility computing system is shown in Figure 2. From top to bottom it is possible to identify four layers, a User or Broker submits its requests using various applications to the utility computing systemsys- tem, the Service Request Examiner is responsible for admission control, SLA Management balances workloads, and a Resource or Service Provider offers resources or services. Us- ers Users or Brokers, who act on users‟ behalf, submit their service requests and applications, from anywhere in the world, to be processed by utility computing systems. When a service request is submitted, the Service Request Examiner Ex- aminer uses Admission Control mechanism to interpret its QoS requirements before determin- ing determining whether to accept or reject it. Thus, it ensures that there is no overloading of resources whereby many service requests re- quests cannot be fulfilled successfully due to limited availability of available resources/services. Then, the Service Request Re- quest Examiner interacts with the SLA Management to decide whether to accept or reject the request. - User-driven Service Management - Computational Risk Management - Autonomic Resource Management