Operational Resilience Management demo
Each important business service mapped, its recovery timed from test evidence, and each breach tracked to a fix 1:31
What the demo shows
Risk teams map important business services, test impact tolerances and track fixes
A Mapping agent builds each important business service's chain from the CMDB, the third-party register, continuity plans and runbooks, and proposes changes for the Service Owner to confirm. A Scenario agent runs severe but plausible scenarios and times every recovery step from failover tests and incidents, not estimates. An Impact agent counts the payments, customers and value affected from a real day's volumes. A Third-party agent finds suppliers that share a failure. A Remediation agent proposes fixes and re-tests each on the same clock. A Self-assessment agent drafts the board document with every line cited. The Head of Operational Resilience checks every result, and the SMF24 accepts fixes and approves the self-assessment.
Transcript
- Operational Resilience Management helps UK banks prove services survive severe disruption.
- Nine UK banks logged 803 hours of IT outages in two years.
- Corvane Bank UK has eleven important services; this Faster Payment has a four-hour tolerance.
- The Mapping agent built its chain, from people and processes to suppliers.
- Then ransomware hits the gateway supplier; steps are timed from the May failover test.
- Recovery takes 6 hours 10 minutes: 2 hours 10 over tolerance.
- 312,000 payments, worth 48.6 million pounds, would be delayed.
- A warm standby gateway re-tests at 3 hours 5 minutes.
- Diane, the accountable executive, accepts it for March 31, 2027.
- Every map, tolerance and result has a maker and a checker.
- The result: proven recovery times and a cited self-assessment for the board.
- Built on Botminds: agents, data, screens and governance on one platform.
The narration as written for the film. Captions are on the player.