Business impact analysis, UAE

Where did your four hour RTO come from? For most organisations, a vendor datasheet.

Recovery objectives are supposed to be derived from what a disruption actually costs the business. A business impact analysis produces those numbers properly, so the recovery investment matches the exposure rather than the sales pitch.

Business impact analysis for UAE organisations
  • 3 stepsCriticality, resources, recovery priorities
  • MTD, RTO, RPOThree different measures, often confused
  • RTO under MTDBecause RTO must ensure MTD is not exceeded
  • Step 2 of 7In the contingency planning process
The question that exposes the gap

Ask your team where the recovery targets came from.

It is a fair question and it is uncomfortable in most organisations, because the honest answer traces back to a procurement decision rather than an analysis.

  • The common origin is a vendor tier. A backup or replication product offered four hour recovery, the organisation bought it, and four hours became the recovery time objective by default rather than by decision. Nothing tested whether four hours is tolerable.
  • The second common origin is symmetry. Every system gets the same target because differentiating them requires knowing which processes matter more, and nobody has done that work. That over-invests in the unimportant and under-invests in the critical.
  • Both produce the same failure. During a real disruption the recovery sequence is decided in the moment by whoever is in the room, because recovery priorities were never established from process criticality, outage impacts, tolerable downtime and resources.
  • The analysis fixes this with a defensible chain. Process criticality drives tolerable downtime, tolerable downtime constrains the recovery time objective, and the recovery objective determines what technology is actually required rather than what was already purchased.
Ask us to derive your real numbers
What a BIA produces

Eight outputs that a continuity plan cannot be written without.

Most UAE organisations write the continuity plan first and reverse engineer the analysis afterwards. That produces a document that reads well and recovery targets nobody can defend when asked where the number came from.

It connects systems to business consequence

The stated purpose is to correlate the system with the critical mission and business processes and services provided, and based on that information characterise the consequences of a disruption. That correlation is the whole point and it is what gets skipped.

Maximum tolerable downtime, defined properly

The total amount of time the owner is willing to accept for a process outage or disruption, including all impact considerations. It is a business decision about tolerance rather than a technical statement about capability.

Recovery time objective is a different number

The maximum amount of time a system resource can remain unavailable before there is an unacceptable impact on other resources, on the processes it supports, and on the MTD. Because RTO must ensure the MTD is not exceeded, it must normally be shorter.

Recovery point objective is about data loss

The point in time, prior to the disruption, to which process data can be recovered given the most recent backup. Unlike RTO it is not considered part of MTD. It is a factor of how much data loss the process can tolerate during recovery.

Three steps, in a fixed order

Determine business processes and recovery criticality with outage impacts and estimated downtime. Identify resource requirements. Identify recovery priorities for system resources. Skipping the first makes the third arbitrary.

Resources means more than servers

The published examples include facilities, personnel, equipment, software, data files, system components and vital records. Recovery plans that account for infrastructure but not for the people who operate it fail in a predictable and avoidable way.

It settles the cost argument with evidence

The longer a disruption continues the more costly it becomes, and the shorter the RTO the more expensive the recovery solution. Plotting those against each other shows an optimal point, and that point is different for every organisation and system.

It often finds prevention is cheaper

Outage impacts identified in the analysis can sometimes be mitigated or eliminated through preventive measures. Where feasible and cost effective, preventive methods are preferable to actions needed to recover a system after a disruption.

Three measures

MTD, RTO and RPO are not interchangeable.

They are routinely used as synonyms in UAE continuity documents, which is why recovery plans so often contain internally inconsistent targets.
MeasureWhat it actually measuresWhose decision it is
Maximum tolerable downtimeTotal outage time the owner will accept, all impacts includedThe business process owner
Recovery time objectiveHow long a system resource can be unavailable before unacceptable impactDerived, must normally be shorter than MTD
Recovery point objectiveHow far back data recovers to, given the most recent backupThe business, based on tolerable data loss
Relationship to MTDRTO sits inside it, RPO is not part of itFrequently misunderstood
Driven byImpact on processes and the organisationNot by product capability
Cost behaviourShorter RTO means more expensive recoveryBalanced against cost of disruption
Differs per systemYes, and it shouldUniform targets are a warning sign
Reviewed whenProcesses or systems change materiallyNot only at audit time
How we approach it

Four things that make an analysis produce usable numbers.

A business impact analysis is only as good as the honesty of the conversations behind it, and those conversations are with the business rather than with IT.

We interview process owners, not just IT

Maximum tolerable downtime is the total time the owner is willing to accept for an outage, including all impact considerations. That is a business judgement, and an analysis conducted entirely within IT produces technical estimates dressed as business tolerances.

We keep MTD, RTO and RPO distinct

RTO must normally be shorter than MTD because it has to ensure the MTD is not exceeded, and RPO is not part of MTD at all since it concerns tolerable data loss. Conflating them is the most common defect we find in existing continuity documents.

We make the cost trade-off explicit

The shorter the recovery objective, the more expensive the solution. Plotting the cost of disruption against the cost of recovery finds an optimal point that differs for every organisation and system, and it makes the investment decision a business one.

We look for prevention before recovery

Some outage impacts identified in the analysis can be mitigated or eliminated by preventive measures, and where feasible and cost effective those are preferable to recovery actions. That finding often pays for the analysis on its own.

How an engagement runs

Three phases across roughly five to eight weeks.

The analysis is interview driven, so the elapsed time depends mostly on how quickly process owners can be brought together rather than on technical work.
  1. 01
    Weeks 1 to 3

    Processes and recovery criticality

    Working with process owners and management to identify the mission and business processes that depend on each system, the impact of a disruption, and the maximum time the organisation can tolerate while still maintaining the mission.

    • Business processes mapped to supporting systems
    • Outage impacts characterised per process
    • Maximum tolerable downtime agreed with owners
    • Interdependencies documented, including external ones
  2. 02
    Weeks 4 to 6

    Resource requirements

    A thorough evaluation of what resuming each process actually requires. Not only system components, but facilities, personnel, equipment, software, data files and vital records, since recovery plans that omit any of those fail at that point.

    • Resource requirements documented per process
    • People and facility dependencies captured
    • Vital records identified
    • External dependencies and suppliers listed
  3. 03
    Weeks 7 to 8

    Recovery priorities and objectives

    Priorities established from process criticality, outage impacts, tolerable downtime and system resources, producing a recovery priority hierarchy. Then recovery objectives derived, with the cost balance made explicit rather than assumed.

    • Recovery priority hierarchy for the estate
    • RTO and RPO derived per system with reasoning
    • Cost of disruption weighed against cost of recovery
    • Preventive options identified where cheaper than recovery
Where this matters

Six situations that make the analysis urgent.

The trigger is usually somebody external asking a question the organisation cannot answer with evidence.

A regulated firm asked to justify its recovery targets

Stating a four hour objective is easy. Explaining how it was derived from process criticality and outage impact is what a supervisor actually asks for, and a documented analysis is the only comfortable answer to that question.

A business renewing cyber or business interruption cover

Insurers increasingly ask how downtime tolerance was established and what recovery priorities exist. An analysis with named process owners and documented impacts is a materially stronger submission than a plan with uniform targets.

An operation with production or logistics dependencies

Where a process depends on facilities, equipment and people as much as systems, a technology only view misses most of the recovery requirement. The published resource categories include exactly those, and omitting them is why recovery plans stall.

A healthcare provider prioritising system recovery

When several systems are down at once, the order of restoration is a clinical question before it is a technical one. A recovery priority hierarchy established in advance removes that argument from the middle of the incident.

An organisation that over-invested in replication

Uniform low recovery objectives across an estate are expensive. An analysis frequently shows that a minority of processes need aggressive targets and the remainder do not, which funds the improvements the critical ones actually require.

A business that had a disruption and improvised

The retrospective always shows the same thing: recovery order was decided in the room, and it was not the order anybody would have chosen calmly. Establishing recovery priorities in advance is the specific remedy for that failure.

Three positions

How UAE organisations arrive at recovery targets.

The middle column is by far the most common, and it is the one that produces a continuity plan nobody can defend when a regulator or an insurer asks a follow up question.
Targets traceable to business impact
Derived from analysisYes
Inherited from a productNo
Not definedNo
Differentiated by system
Derived from analysisYes
Inherited from a productRarely
Not definedNot applicable
MTD, RTO and RPO distinguished
Derived from analysisYes
Inherited from a productUsually conflated
Not definedNo
Recovery priority order exists
Derived from analysisDocumented
Inherited from a productImprovised
Not definedNone
People and facilities included
Derived from analysisYes
Inherited from a productRarely
Not definedNo
Cost balance made explicit
Derived from analysisYes
Inherited from a productImplicit in the purchase
Not definedNo
Prevention considered as an option
Derived from analysisYes
Inherited from a productNo
Not definedNo
Defensible to an auditor or insurer
Derived from analysisYes
Inherited from a productWeakly
Not definedNo
Behaviour during a real disruption
Derived from analysisSequenced
Inherited from a productDebated
Not definedChaotic
Effort to reach
Derived from analysisWeeks
Inherited from a productNone
Not definedNone
The conversation that produces the numbers

Four questions to ask a process owner, in this order.

Tolerable downtime is a business judgement, and it emerges from a specific conversation rather than from a form sent round by email.

  • What happens in the first hour this process is unavailable? Most owners answer that nothing much happens, which is useful, because it establishes that the immediate recovery pressure is lower than the technology team usually assumes it to be.
  • At what point does it start to hurt, and who feels it first? This is where the impact categories emerge naturally, covering operations, customers, regulatory obligations, financial consequences and reputation, expressed in terms the owner actually uses.
  • What is the point at which the organisation cannot recover the position afterwards? That is the maximum tolerable downtime, the total time the owner is willing to accept for an outage including all impact considerations, and it is their decision rather than an estimate.
  • How much data could you reconstruct or re-enter? That produces the recovery point objective, since it measures tolerable data loss rather than tolerable downtime, and it is frequently a very different answer from the recovery time question.
How an engagement runs

Five steps, following the published three step analysis.

The sequence matters. Recovery priorities established without criticality and resource work behind them are just an opinion with numbers attached.
  1. 1

    Correlate systems with business processes

    Identifying the mission and business processes each system supports, and the interdependencies between them. The purpose is to characterise the consequences of a disruption in business terms, which is what makes the resulting numbers defensible.

  2. 2

    Establish tolerable downtime with process owners

    Maximum tolerable downtime reflects the maximum time the organisation can tolerate while still maintaining the mission, and it includes all impact considerations. It is agreed with the people accountable for the process, not estimated by IT on their behalf.

  3. 3

    Identify the full resource requirement

    Facilities, personnel, equipment, software, data files, system components and vital records. Realistic recovery requires a thorough evaluation of what resuming each process actually needs, and the non technical resources are the ones usually missing.

  4. 4

    Derive recovery objectives and priorities

    Recovery time objectives constrained so the maximum tolerable downtime is not exceeded, recovery point objectives set from tolerable data loss, and a recovery priority hierarchy built from criticality, impacts, tolerable downtime and resources.

  5. 5

    Test the cost balance and consider prevention

    Cost of disruption plotted against cost of recovery to find the point that fits your financial constraints and operating requirements, and preventive measures identified where they would be cheaper and more effective than recovering after the event.

Straight answers

What organisations ask about business impact analysis.

Before you start

Twelve questions that show whether an analysis is needed.

If the first group produces vague answers, the recovery investment is currently being sized by something other than business impact.

Current position

  • Where did our RTO come from?
    Often a product tier.
  • Do all systems share one target?
    A warning sign.
  • Do we distinguish MTD from RTO?
    They are different.
  • Is RPO set separately?
    It is about data loss.

Process knowledge

  • Can we list our critical processes?
    Processes, not systems.
  • Do we know which systems support each?
    The correlation matters.
  • Have process owners been asked?
    MTD is their decision.
  • Are external dependencies included?
    Suppliers and utilities.

Resources

  • Have we accounted for people?
    Not just systems.
  • And facilities?
    A named resource category.
  • And vital records?
    Also named.
  • Is there a recovery priority order?
    The third BIA step.
Next step

Ask three people what your recovery time objective is.

Tell us about business processes, peak operating periods, dependencies and the owners who can approve priorities. We will confirm the requirements and proposed scope with you.