The catalogue AI GBS & Global Business ServicesContinuous ImprovementTransactional

Service GB10B

Idea to Backlog

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

Runs a week

3,445

138 in flight right now.

Stations

0 person · 5 agent · 0 spine

Agent share of steps

100%

Autonomy on this service is set at 70% against a ceiling of 78%.

Decisions a person makes

Nothing on this service waits for a person.

Touchless

73%

Share of runs that complete without anybody opening them.

Timetable against actual

14.8h

Actual 14.3h, 0.5h under the timetable.

Operations

The lane diagram

Read it left to right. more

Person0 stations and 0% of the dwellAgent5 stations and 100% of the dwellShared spine0 stations and 0% of the dwell0 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

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.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Intake	Agent	Waste Detection Agent	workflow	2h 52m	3h 30m	24	Enterprise Data Warehouse
2	Score	Agent	Root Cause Agent	workflow	2h 40m	6h 23m	34	Group ERP — Financials
3	Route	Agent	Experiment Design Agent	workflow	1h 56m	3h 22m	28	Core HR and Payroll
4	Track	Agent	Benefit Measurement Agent	workflow	2h 3m	3h 29m	16	Source-to-Pay Suite
5	Close loop	Agent	Idea Intake Agent	workflow	2h 1m	4h 7m	36	Invoice 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. more

Move something

Demand100%

3,445 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 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. more

Person time a week

3,445 items at 0 minutes of decision each.

Agent time a week

39,732.3h

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

Gate load

Inside capacity, with 35h of headroom.

Stations without a person

100%

0 gates left on 5 stations.

Where an item spends its time

100% in the agent lane

An item now takes 692 minutes of worked time end to end against 692 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 Idea to Backlog

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

now Intake · Waste Detection Agent · 2.9 hrs

As the ledger has it

the same stations, plus 1 categories the estate already counts

0 min of 13 hrs

now Intake · Waste Detection Agent · 2.9 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

1 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

5 systems attributed

0 of 5 returning records

The system register

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 5 stations attributed here · read only

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

1 of 5 stations attributed here · would write back

Core HR and Payroll

Workday HCM · hcm · bidirectional · critical

modeled

1 of 5 stations attributed here · would write back

Source-to-Pay Suite

SAP Ariba · procurement · bidirectional · critical

modeled

1 of 5 stations attributed here · would write back

Invoice Capture and AP Automation

Basware · procurement · bidirectional · high

modeled

1 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: Continuous Improvement Orchestrator
That orchestrator’s remit: Owns improvement work end to end inside AI GBS & Global Business Services. Runs 3 lines across 17 stations, drains the repeatable share into the AI-OPS tower, and holds 2 human gates.
Accountable person: Head of Continuous Improvement
Sub-function: Continuous Improvement
Shared spine tower: Not on the shared spine
Hand-over points: None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Signal to ImprovementGB10A Benefit VerificationGB10C

What this page is and is not

This is a catalogue of the modeled estate. more