Removal Phase Clause Samples
Removal Phase. When a customer subscription to a service is ended the SLA and all associated configuration infor- mation in the service systems needs to be removed. The same service sub-systems that were ad- dressed for SLA creation are again involved for this step. The event that triggers SLA removal is the fact that the customer service subscription is not renewed, or actively ended. The service subsystems contain configuration information about this subscription, that information needs to be removed. Resources that were claimed to support this subscription need to be freed. Note that the configuration information for a given subscription can be aggregated with configuration information for other subscriptions. It is therefore possible that information needs to be changed, not just only deleted.
Removal Phase. There are generally two scenarios that might cause SLA termination: normal time-out, or violation of contract terms [7]. Violations do not necessarily cause termination of the SLA, but when they do, penalties might apply as agreed upon in the SLA. When an SLA is in its removal phase, monitoring should be stopped and any remaining configuration should be cleaned up.
Figures 2.1 and 2.2 take a slightly different approach to this phase: ▇▇ et al. differentiates between the termination (Terminate SLA) and enforcement (Enforce Penalty) steps of this process, whereas ▇▇▇▇▇▇▇▇ et al. shows those together as the Settlement step, followed by an Archive step [7], [11], [13]. The archiving step follows from a statutory period where the SLA must be kept as a legal document describing how services where provided [11]. While the removal phase is not directly related to the core of this project, it could be important to support proper archiving and clear information for use in a penalty enforcement step.