Modernisation order
- Most exposed: Mainframe batch scheduler (stops 3 items).
- For this failure: none stops none.
Executive Intelligence · Technology and Innovation
A register of systems with age, support status, risk and owner, and a modernization plan.
Demonstration: Fairholme Holdings (fictional) · Diversified holding company. Fictional data and a scripted answer.
What depends on our oldest systems, and what would a failure cost the business?
Fail one or more items and see what stops and what only degrades, worked out by following the dependencies.
Choose what fails or loses support. Hard dependencies stop with it; soft ones carry on, degraded.
Simulated answer. Written for this fictional case, not produced by a live model. Only the figures in it are computed, from what you decided above.
Following the dependencies, a failure of none stops none and degrades none [S1][S2]. The system whose failure stops the most is Mainframe batch scheduler, which stops 3 other item(s).
The scheduler is the quiet risk: it supports the whole close and depends on two people. A modernisation plan that starts with the system the vendor is dropping may miss the one the business is most exposed through.
Relies on: S1 · Application inventoryS2 · Vendor support notices
The chief technology officer decides. Approving sets the order of the modernisation roadmap. It does not fund or begin any replacement.
Not ready to approve. Fail at least one item first, to see what depends on it.
In the product this is a different person with the right permission. Here you play that role to see the rule.
The Executive Intelligence story · This capability in the full register