Service continuity management

You are here:
< All Topics
Table of Contents

The goal of this service is to enable the organization to manage the continuity of its services while a disaster occurs and survive from that it when corruption occurs that is bigger than an incident or a major incident and it can not be recovered by incident management or major incident management practices. 

Disaster: An unplanned incident that makes a big corruption or important loss for an organization and its business. It results that the organization will not be able to perform its important business activities in a period of time.  

It is important that an organization have an analysis of different kinds of disasters and the components which form those disasters. And it’s also important to recognize the source which created the disaster and the way to recover from it. Another aspect that should be considered is the stakeholder who the disaster impact and the type of impact on it. Some conditions and levels of impact are listed here in the table below: 

table 5.3 

Recovery Time Objective (RTO)

Maximum time after a service corruption occurrence which is acceptable for the organization to wait for services returning to their normal state.

Recovery Point Objective (RPO)

A point of time to which should service return in order to recontinue normal services. 

Disaster Recovery Plans

A set of predetermined plans to declare the way an organization should recover from a disaster.     

Business Impact Analysis (BIA)

A key activity in service continuity management practice which leads to identifying vital business functions (VBF) and related items. These related items could be suppliers, people, and other business processes and IT services. With BIA recovery conditions and specifications such as RTO, RPO, and minimum service level for each service are recognized. 

Figure 5.31