Service Level Agreement Characteristics of Monitoring Wireless Sensor Networks for Water Resource Management (SLAs4Water)

Abstract

Abstract:One of the most important characteristics of a Service Level Agreement (SLA) when discussing about Monitoring Wireless Sensor Networks (MWSNs) is its effectiveness in assuring business success, a high provider profit, an increased level of client satisfaction and trust. In order to ensure that these goals will be achieved the provider of the MWSN must define some parameters that characterize the Service Level Agreement that occurs between MWSN provider and the MWSN customer. This paper addresses a solution behind an efficient and effective Service Level Agreement (SLA) design and implementation related to a Monitoring Wireless Sensor Network (MSN) and applies the SLA in the case of water resources management. The characteristics of the SLA in place between the MWSN provider and the MWSN customer must be defined by taking into consideration various parameters that are particular to the MWSN such as routing algorithms, recovery from failure, monitoring and reporting aspects. An appropriate definition of a SLA contract helps identify the responsibilities of both the provider and customer of the Monitoring Wireless Sensor Network (MSN) and makes the interaction between the provider and customer easier.

Service Level Management of Information Technology and System in ITB STIKOM Bali

“…It defines the functional and non-functional requirements, such as reliability, availability, successability, accessibility, and others [15]. It is a contract between two parts (the provider and the customer) when the customer requests and receives a service from a provider [16]. It is also a key component of the overall SLM strategy of an IT organization.…”

Scheduling in CloudSim of Interdependent Tasks for SLA Design

“…A node without parents is said to be at an entry level and a node without children is said to be at an exit level. The set of nodes can be used when computing the SLA parameter called Number and type of virtual machines (Iordache et al, 2017). For example, based on the V of the DAG and on the scheduling policy one can decide which number and type of virtual machines of the CSPs can be rented for scheduling that DAG.…”

“…A SLA between the CSP and the CSC might state the following: "The Total Execution Time in the case of the given DAG must have a finish time of at most 37" (Iordache et al, 2017). A generic SLA rule of the form "if-then" can be the following:…”

“…"If the Total Execution Time in the case of the given DAG is greater that the agreed one (e.g. 37) then the CSP needs to pay a penalty of 10% for this violation" (Iordache et al, 2017).…”

“…-Total time of execution (Iordache et al, 2017): although this parameter is hard to minimize because the actual execution time on a certain resource it is usually unknown, in this paper it is considered that this parameter can be reduced because the DAG of the CSC is already known. This parameter is useful when designing the CSP infrastructure because based on it one can decide for example the number of Virtual Machines that are offered by the provider to the customer.…”