Critical Service and Disruption Impact Analysis · Lesson 2

Analyze Service Interruption Over Time

6 min read

Lesson objectives

  • Apply analyze service interruption over time in an operating case and justify the decision with evidence and limits.
Reading tools

The previous lesson identified the outcome a guest needs and the resources that produce it. Now add time. A five-minute check-in interruption has different consequences from two hours of interruption while another coach arrives. Business impact analysis asks how harm changes as disruption continues and when a service level becomes unacceptable, before a recovery technology is selected. Do not begin by asking a worker for the 'most important system'; that may be the most frequently used application while a less visible resource protects guest safety. Start with defined units: guests unable to reach a verified safe room, waiting time by guest group, and people who have not received a credible update. These are outcome measures. Estimate them in intervals and state uncertainty instead of presenting forecasts as observations.

Choose the analysis horizon before interviews: at the start of the outage and, for a busy arrival case, at 15, 30, 60 and 120 minutes. These intervals are teaching assumptions for the case, not universal hotel thresholds. For each service capture four things: expected demand, remaining capacity with the approved workaround, harm from the capacity gap, and who can confirm the figures. If the front desk receives 30 guests per half-hour and can check 18 manually, the waiting list grows by 12 in the first half-hour if demand and capacity remain steady. After an hour of the same flow, the cumulative gap is 24. This does not mean all 24 have waited the same length of time; arrivals differ. Show the cumulative number and a waiting-time distribution or oldest outstanding case rather than treating one as the other.

Separate safety impact from service inconvenience. If a guest with limited mobility cannot call for help from a room, a safety threshold may require immediate escalation even when the lobby queue is small. If invoice printing fails while an approved secure payment path remains available, the document may tolerate a longer delay. Do not make a single arithmetic score in which thousands of minutes of convenience compensate for a severe individual risk. First use a gate to reject unsafe options. Compare the remaining choices by delay, affected guests and reversibility. Each choice depends on the property plan, privacy policy and staff training. An editorial time estimate in this lesson is neither legal permission nor authority to direct emergency response.

Build a table with services as rows and time intervals as columns. In each cell put a described effect, its measure, and the owner of the estimate: 'After 30 minutes, 12 guests await room verification; estimate from the arrivals log and a timed trial of manual processing.' Add a range where evidence is uncertain. If manual capacity ranges from 14 to 18 guests per half-hour against demand of 30, the queue grows by 12 to 16 in that period. Before setting a recovery objective, test whether it is defensible under a plausible adverse case, not just the average. Put conflicting evidence into the table. Reservations may show 30 expected arrivals while transport reports that a coach carrying 20 will be delayed. The temporary decision should state which account it used, why, and when it will be checked again.

Keep three times distinct. One is the interruption duration a service can tolerate before a specified harm; derive it from guest effects rather than the IT team's preference. Another is the process recovery objective: when the team plans to restore an acceptable level of work. It should normally allow a margin before the harm threshold instead of being set equal to it by habit. The third is the time until records are trustworthy again. A system may return in 40 minutes while reconciliation of manual room assignments needs another hour. Technical success at minute 40 does not automatically make those assignments accurate. A process owner needs a guest-side and record-side check before closing the incident, plus a list of exceptions that remain unresolved.

Lesson summary

Worked answer: at 14:30 demand is 24 and capacity serves 15, leaving nine