LensReading which lens this session carries.
The catalogueAI GBS & Global Business ServicesAutomation FactoryTransactional

Service GB7B

Regression Response

Runs transactional. Starts when a threshold is crossed. It runs 2,123 times a week across 6 stations. No station stops for a person and 6 are done by an agent, 1 of them on the shared spine.

Runs a week

2,123

125 in flight right now.

Stations

6

0 person · 5 agent · 1 spine

Agent share of steps

100%

Autonomy on this service is set at 68% against a ceiling of 80%.

Decisions a person makes

0

Nothing on this service waits for a person.

Touchless

81%

Share of runs that complete without anybody opening them.

Timetable against actual

21.1h

Actual 22.5h, 1.4h over the timetable.

Operations

The lane diagram

Read it left to right.

Person0 stations and 0% of the dwellAgent5 stations and 79% of the dwellShared spine1 station and 21% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Enterprise Data Warehouse
Group ERP — Financials
Core HR and Payroll
Source-to-Pay Suite
Group ERP — Financials
Invoice Capture and AP Automation
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

Detect drift

AgentOpportunity Mining Agentworkflow47m1h 16m40Enterprise Data Warehouse
2

Diagnose

AgentFeasibility Scoring Agentworkflow33m1h 18m33Group ERP — Financials
3

Patch

AgentBuild Agentworkflow2h2h 43m0Core HR and Payroll
4

Test

AgentTest Harness Agentworkflow2h 9m3h 57m4Source-to-Pay Suite
5

Redeploy

GBSTest Harness Agentgbs1h 49m3h 58m33Group ERP — Financials
6

Confirm

AgentRegression Monitor Agentworkflow1h 15m1h 43m15Invoice Capture and AP Automation

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%
2,123 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 gates1 person
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
0h
2,123 items at 0 minutes of decision each.
Agent time a week
18,151.7h
513 minutes an item, which does not compete for a person.
Gate load
0%
Inside capacity, with 35h of headroom.
Stations without a person
100%
0 gates left on 6 stations.
Where an item spends its time
100% in the agent lane
An item now takes 513 minutes of worked time end to end against 513 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 Regression Response

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.

6 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

6 stations, nothing waiting, nothing sent back

0 min of 8.6 hrs

now Detect drift · Opportunity Mining Agent · 47 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 14 hrs

now Detect drift · Opportunity Mining Agent · 47 min

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.

5 systems attributed

0 of 5 returning records

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

2 of 6 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 6 stations attributed here · read only

Core HR and Payroll

Workday HCM · hcm · bidirectional · critical

modeled

1 of 6 stations attributed here · would write back

Source-to-Pay Suite

SAP Ariba · procurement · bidirectional · critical

modeled

1 of 6 stations attributed here · would write back

Invoice Capture and AP Automation

Basware · procurement · bidirectional · high

modeled

1 of 6 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Automation Factory Orchestrator
That orchestrator’s remit
Owns automation work end to end inside AI GBS & Global Business Services. Runs 4 lines across 26 stations, drains the repeatable share into the AI-OPS tower, and holds 4 human gates.
Accountable person
Head of Automation
Sub-function
Automation Factory
Shared spine tower
ai-ops
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.