Service AD9A
Plan Refresh Cycle
Runs analytical. Starts when a leader asks the question. It runs 34 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, none of them on the shared spine.
Runs a week
34
103 in flight right now.
Stations
5
1 person · 4 agent · 0 spine
Agent share of steps
80%
Autonomy on this service is set at 58% against a ceiling of 60%.
Decisions a person makes
1
Held by Director, Business Continuity.
Touchless
47%
Share of runs that complete without anybody opening them.
Timetable against actual
127.7h
Actual 111.8h, 15.9h under the timetable.
Operations
The lane diagram
Read it left to right. more
Operations
Every station in order
The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.
| # | Station | Lane | Who | Layer | Dwell | Target | In flight | System |
|---|---|---|---|---|---|---|---|---|
| 1 | Pull dependencies | Agent | Business Impact Analysis Agent | workflow | 10h 30m | 16h 8m | 33 | Group ERP — Financials |
| 2 | Impact analysis | Agent | Dependency Mapping Agent | workflow | 7h 7m | 13h 3m | 43 | IT Service Management |
| 3 | Draft plan | Agent | Plan Maintenance Agent | workflow | 6h 9m | 14h 44m | 12 | Group ERP — Financials |
| 4 | Review Held for a named human when the unit exceeds the continuity plan decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | Director, Business Continuity | policy | 31h 34m | 72h 12m | 5 | Group ERP — Financials |
| 5 | Publish | Agent | Crisis Comms Agent | workflow | 14h 18m | 34h 5m | 10 | IT Service Management |
Operations
Run it
Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through. more
The simulation is arithmetic on the estate, not a queueing model. more
How it runs
Run it again, going wrong
The same unit and the same stations, broken the way the estate already records breaking. more
5 stations, walked twice
Once clean, once with the categories the estate counts
This is the same unit on the same stations, breaking. more
No break below was chosen. more
One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.
As written
5 stations, nothing waiting, nothing sent back
0 min of 2.9 days
now Pull dependencies · Business Impact Analysis Agent · 11 hrs
As the ledger has it
the same stations, plus 3 categories the estate already counts
0 min of 3.1 days
now Pull dependencies · Business Impact Analysis Agent · 11 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
3 counted categories land on this procedure. more
What this run cannot claim
These breaks are shown together on one unit so the shape of a bad day fits on one screen. more
Two clocks run. Worked time is the sum of the time the work is actually being done … more
Live observability
Systems this service would touch
Attributed by rule from the function's system list. more
2 systems attributed
0 of 2 returning records
Group ERP — Financials
SAP S/4HANA · ledger · bidirectional · critical
3 of 5 stations attributed here · would write back
IT Service Management
ServiceNow ITSM · itsm · bidirectional · high
2 of 5 stations attributed here · would write back
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Continuity Orchestrator
- That orchestrator’s remit
- Owns continuity plan work end to end inside Administration. Runs 4 lines across 22 stations, drains the repeatable share into no shared tower, and holds 5 human gates.
- Accountable person
- Director, Business Continuity
- Sub-function
- Business Continuity
- Shared spine tower
- Not on the shared spine
- Hand-over points
- None — this service stays inside its function
Other services in this sub-function
3 alongside this one
What this page is and is not
This is a catalogue of the modeled estate. more