Higher Ed Enterprise Model Conceptual model Search
Core systems / Application portfolio / Resilience & recovery

Resilience and recovery

Every application with its recovery tier, how quickly it must come back (RTO), how much data it may lose (RPO), how it recovers and when that was last proven. Pick a system to see which lifecycle stages stop if it goes down, directly or through the systems that depend on it.

Sample data: tiers, objectives, test dates and dependencies are illustrative, for the fictional Example State University. Replace them with your own business impact analysis and test results. HERM capability: BC161 Business Continuity Management.

Playbook: business continuity and DR → Prioritize risk & continuity → NIST CSF: Recover →
Show {{ rowCount }}
SystemTierRTO / RPORecovers byLast testDepends onGaps
{{ r.own }} · {{ r.host }}
{{ r.tl }} {{ r.rto }}RPO {{ r.rpo }} {{ r.pat }} {{ r.test }}{{ r.ach }}
{{ g.t }}

Gaps are calculated: a system outside the DR plan; a tier 1 or 2 system not tested in the last 12 months; a test that recovered slower than the target; and a dependency on a system with a lower tier than its own. External portals run by banks, agencies and providers are noted but not counted as gaps.

Outage impact

{{ downTitle }}

{{ downSum }}

Stops: uses the system directly Degraded: a system it uses depends on it Unaffected
{{ l.name }}{{ l.count }}
{{ s.name }} {{ s.via }}
Dependency chain
{{ c.label }}
No other system in the register depends on this one.