The catalogue AdministrationBusiness ContinuityJudgment

Service AD9D

Resilience Position

Runs judgment. Starts when a leadership team frames the question. It runs 5 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, none of them on the shared spine.

Runs a week

77 in flight right now.

Stations

1 person · 5 agent · 0 spine

Agent share of steps

83%

Autonomy on this service is set at 58% against a ceiling of 60%.

Decisions a person makes

Held by Director, Business Continuity.

Touchless

12%

Share of runs that complete without anybody opening them.

Timetable against actual

740.6h

Actual 563.3h, 177.3h under the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 50% of the dwellAgent5 stations and 50% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Group ERP — Financials

Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

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	Frame question	Agent	Business Impact Analysis Agent	strategy	11h 45m	25h 54m	38	Group ERP — Financials
2	Gather evidence	Agent	Dependency Mapping Agent	strategy	25h	31h 26m	3	Group ERP — Financials
3	Model options	Agent	Plan Maintenance Agent	strategy	49h 33m	89h 41m	17	Group ERP — Financials
4	Draft position	Agent	Exercise Design Agent	strategy	53h 31m	123h 32m	13	Group ERP — Financials
5	Challenge	Agent	Crisis Comms Agent	strategy	21h 35m	26h 12m	6	Group ERP — Financials
6	Ratify 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	162h 25m	344h 7m	0	Group ERP — Financials

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

Move something

Demand100%

5 a week is what the estate records. more

Decisions handed to agents0 of 0

This service has at most one gate, so there is nothing to hand over without removing the last human decision.

People on the gates24 people

Each one is assumed to have 2,100 productive minutes a week, which is 35 hours.

Agent speed100%

100% is the dwell the estate records today. more

Person time a week

812.1h

5 items at 9,745 minutes of decision each.

Agent time a week

807h

9,684 minutes an item, which does not compete for a person.

Gate load

97%

Inside capacity, with 27.9h of headroom.

Stations without a person

83%

1 gate left on 6 stations.

Where an item spends its time

50% waiting on a person

50% in the agent lane

An item now takes 19,429 minutes of worked time end to end against 19,429 in the recorded estate, a change of +0%. This is worked time, not calendar time: nothing here models a queue or a weekend.

What this model is, on Resilience Position

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

6 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

6 stations, nothing waiting, nothing sent back

0 min of 13.5 days

now Frame question · Business Impact Analysis Agent · 12 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 13.7 days

now Frame question · Business Impact Analysis Agent · 12 hrs

personagentshared spinework the break addsnobody working it

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

1 systems attributed

0 of 1 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

6 of 6 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

Plan Refresh CycleAD9A Exercise to FindingsAD9B Live Disruption ResponseAD9C

What this page is and is not

This is a catalogue of the modeled estate. more