LensReading which lens this session carries.
The catalogueAdministrationBusiness ContinuityAnalytical

Service AD9B

Exercise to Findings

Runs analytical. Starts when the reporting period closes. It runs 54 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

54

76 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

42%

Share of runs that complete without anybody opening them.

Timetable against actual

71.0h

Actual 83.8h, 12.8h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 9% of the dwellAgent4 stations and 91% of the dwellShared spine0 stations and 0% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
IT Service Management
Group ERP — Financials
Group ERP — Financials
IT Service Management
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.

#StationLaneWhoLayerDwellTargetIn flightSystem
1

Design scenario

AgentBusiness Impact Analysis Agentworkflow9h 32m11h 40m20Group ERP — Financials
2

Run exercise

AgentDependency Mapping Agentworkflow11h 58m23h 37m0IT Service Management
3

Capture findings

AgentPlan Maintenance Agentworkflow6h 25m13h 16m11Group ERP — Financials
4

Remediation plan

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.

HumanDirector, Business Continuitypolicy3h 3m7h 14m6Group ERP — Financials
5

Track

AgentCrisis Comms Agentworkflow1h 56m4h 35m39IT 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.

Move something
Demand100%
54 a week is what the estate records.
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 gates5 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.
Person time a week
164.7h
54 items at 183 minutes of decision each.
Agent time a week
1,611.9h
1,791 minutes an item, which does not compete for a person.
Gate load
94%
Inside capacity, with 10.3h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
91% in the agent lane
An item now takes 1,974 minutes of worked time end to end against 1,974 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 Exercise to Findings

The simulation is arithmetic on the estate, not a queueing model.

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking.

5 stations, walked twice

Once clean, once with the categories the estate counts

This is the same unit on the same stations, breaking.

No break below was chosen.

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 33 hrs

now Design scenario · Business Impact Analysis Agent · 9.5 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 38 hrs

now Design scenario · Business Impact Analysis Agent · 9.5 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

3 counted categories land on this procedure.

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen.

Two clocks run. Worked time is the sum of the time the work is actually being done …

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

2 systems attributed

0 of 2 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

3 of 5 stations attributed here · would write back

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

2 of 5 stations attributed here · would write back

System attribution is a rule, not a reading.

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 CycleAD9ALive Disruption ResponseAD9CResilience PositionAD9D

What this page is and is not

This is a catalogue of the modeled estate.