Operate · item 27
Platform continuity
Continuity of the platform is held separately from continuity of the functions it runs, because the two fail differently. more
Health
What survives the loss of a component
Components with a proven, partial or unproven recovery path, and the lines that cannot be reversed.
Function continuity asks what happens to invoices, hires and orders when a line goes down, and the answer is usually a manual fallback and a backlog. more
Platform continuity asks a different question: what happens when the machinery that runs, watches and proves the work goes down. more
Tier 1 — Everything stops without it.
5 components
Tier 2 — A capability is lost and processing continues.
4 components
Tier 3 — Convenience or reporting only.
2 components
Platform drills on the calendar
7 drills scoped to the platform rather than to a function
Actions
What is waiting on a person
Continuity work is slow and nobody asks for it until the day it matters. more
Operations
What this desk is allowed to start
A surface that only reports is not operable. more
Trigger and bound
This desk can start a component assessment and record a proven recovery objective against evidence from a drill. more
Live observability
What the record shows right now
Component recovery status. Proven means a rehearsal met the stated objective.
Current distribution
11 components
Is policy and strategy coming to fruition
Whether the written intent is holding here
1 of 11 components have a proven recovery path. 6 remain single points of failure.
Not holding on the record
The written intent is that this platform can lose any one component and keep running. more
Drill results are measured against a modeled estate on a rehearsal calendar of our own making. more
6 of the 11 platform components are single points of failure, 4 of them tier 1. 8 have a failover path that has never been exercised and 2 have no failover path at all. Those are stated as findings, not as a maturity score.
Recovery point targets on this page are targets. more
Vendor lock is recorded on 5 components and 2 of those have no exit plan written down. Portability is a continuity question, not a procurement one, which is why it sits here.