Business Continuity: Impact Analysis, RTO/RPO & Recovery Priorities

What you'll build

What you will be able to do

Each lab ends with a concrete result that you build yourself and the checker confirms, cell by cell.

• Count what each of Meridian Parcel's eight processes depends on and how many processes rely on each resource, find the resource that would hurt most if it failed and flag the processes with many dependencies.
• Put a dollar figure on one hour of downtime for each process: lost revenue, contractual penalties and recovery overtime, then the cost of a site-wide outage and the costliest process.
• Project the cumulative impact of an outage of 1, 4, 24 and 72 hours for four processes with one mixed-reference formula, total the 24-hour impact and draw the impact curves.
• Read each process's impact scores over time, find the maximum tolerable downtime (MTD), derive a recovery time objective (RTO) with a safety margin and count the processes that need the fastest recovery.
• Compare six backup intervals for the order database: the yearly cost of the backup option against the expected cost of lost data, and choose the interval with the lowest total as the recovery point objective (RPO).
• Combine four impact criteria into one weighted score per process, rank the processes, sort them into recovery tiers with limits kept in cells and name the top priority.
• Test five recovery strategies: expected loss avoided per year (probability × reduction in impact), net benefit after the strategy's annual cost, a Fund / Reject decision and the budget needed.
• Evaluate a disaster-recovery exercise: actual recovery time per process from two timestamps, Pass/Fail against the RTO, the pass rate, and a formula rule that colours every failed row.