System Recovery Plan -using omega case study and bia , fill the system recovery plan.(files attached)

BIA TEMPLATE 7

Bia Template

3.1 Determine Process and System Criticality

Paying Vendor Invoice

This is works with the process of obligating funds. At the same time, it is the one that is in charge of issuing a check or even electronic payment and acknowledging of receipts(Snedaker,2014).

Business Process

Description

Pay vendor invoice

Process of obligating funds, issuing check or electronic payment and acknowledging receipt

Cash Sales

Goods and services given out and received with cash

Debt Receipt

Documents showing funds outside a company

Cash sales

In business, these are documents that give information of the kind of goods that have been bought by customers(Weltma,2007). The documents indicate the value of the products and services and it is also inclusive of the commodities that have been shown. In respect, to this, they are for indicating what customers have bought.

Debt Receipt

In determining the process and the system critically, these are documents showing what is owed to a company and what a customer owes to the company. They are great documents for keeping history making the trust to be much available(Snedaker,2014).

3.1.1 Identify Outage Impacts and Estimated Downtime

Outage Impacts

In the business process, when vendor invoice is in severe situations which are inclusive of temperature staffing, overtimes and the value being greater than $1 million, the resulting situation is that a business will tend to pay more and it may make a business to incur losses.

In situations of moderate when there are penalties and fines a business is able to perform well as things move in a direction that is great(Weltman,2007). This, therefore, means that a business is not bound to make many losses in such situations.

In situations of new contracts and supplies at $75k, there are issues whereby there are minimal issues. In these circumstances, what comes out clearly is that the business, may not be cost so much in terms of paying off its debts. In this case, things tend to work out more clearly(Snedaker,2014).

Business Process

SEVERE MODERATE MINIMAL Impact Category

{insert}

{insert}

{insert}

{insert}

Impact

Pay vendor invoice

More pay

No losses

Debts down down

$5

$200k

$20k

Estimated Downtime

In the business process in the pay vendor invoice at the MTD situation within 72 hours. During this period of time, it is expected that decisions made within an organization are meant to make things work more favourable. This period is enough as the managers and other top leadership take a good time in making decisions that are long-lasting and which tend to be successful for Maximum Tolerable Downtime(Weltman,2007).

Within the period of 48 hours of Recovery Time Objective, means that other systems will get affected when there is no service to the relying systems. As a result of this, communication becomes limited as things do not move the way they should with situations turning out to be deplorable. This is the point that there ought to be great communication for systems to work properly.

In a period of 12 hours when a previous backup was made, the Recovery Point Objective leads to a disruption that may not ogre very well within the system. The outage may lead to significance breakdown of all the processes and even there can be a loss of data(Snedaker,2014).

Business Process

MTD

RTO

RPO

Pay vendor invoice

72 hours

48 hours

12 hours (last backup)

favorable

Communication

No disruption

Great ideas

System failure

Breakdown

3.3 Identify Resource Requirements

In the web server 2, the version of the platform is expected to be OptiPlex GX280-1. In the e case of the website host, the host is expected to remain the same. In the case of web server 2, the platform is expected to be OptiPlex GX280-3 as the website host remains just the same.

System Resource/Component

Platform/OS/Version
(as applicable)

Description

Web Server 1

OptiPlex GX280

Web Site Host

Web server 2

OptiPlex GX280-1

Web Site Host

Web server 3

OptiPlex GX280-3

Web Site Host

3.3 Identify Recovery Priorities for System Resources

In the priority under website 1, it is expected that the system is OptiPlex GX280 and this is supposed to add up to 24 hours for the rebuilding in the RTO.In the Web server 2, the system is supposed to be at OptiPlex GX280 and it is supposed to rebuild within a period of 36 hours in the case of the Recovery Time Objective. In instances where there is web server 3, the system will be OptiPlex GX280-2 as the time for rebuilding can be 72 hours for the Recovery Time Objective(Weltman,2007).


Priority

System
Resource/Component

Recovery Time Objective

Web Server 1

OptiPlex GX280

24 hours to rebuild or replace

Webserver 2

OptiPlex GX280-1

36 hours to rebuild or replace

Webserver 3

OptiPlex GX280-2

72 hours to rebuild or replace



Results Summary

In any organization, the priority for the business function is to gain profits and to, later on, make customers feel at ease. It is not different from Omega executive team as the company wants to make profits in its operations. Once there are profits, Omega a s a company will be able to maintain its daily expenditure. These expenditures include paying the workers and maintenance of its systems. The other priority for Omega as a business is to get the best workforce. Good employees do not just come to be but a company should show that it has the urge to do so(Snedaker,2014). This means that Omega should be able to offer its employees the best pay and even services.

As businesses, operate, they tend to face difficulties like loss and even outages. This is no different as Omega being in a rea of earthquakes, once such occurrences occur there is the likelihood of the business losing in its infrastructure. This includes issues like machines getting soaked in water and also other things like power burning out the other systems other losses that may bound to happen is the loss of data in case there is no good way of maintaining data but with the current technology, data is rarely lost. Omega management should be in the forefront in promoting best ways to deal with disasters like disaster recovery and even disaster management(Weltman,2007).













References

Snedaker, C. (2014). Business continuity and disaster recovery planning for IT

professionals. Waltham, MA: Syngress.

Weltman, B. (2007). The rational guide to building small business credit. Rollinsford, NH,

USA: Rational Press.