The catalogue AI GBS & Global Business ServicesService Catalog & IntakeTransactional

Service GB5B

Catalog Item Change

Runs transactional. Starts when a threshold is crossed. It runs 3,413 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 1 of them on the shared spine.

Runs a week

3,413

56 in flight right now.

Stations

1 person · 3 agent · 1 spine

Agent share of steps

80%

Autonomy on this service is set at 83% against a ceiling of 90%.

Decisions a person makes

Held by Head of Service Catalog.

Touchless

94%

Share of runs that complete without anybody opening them.

Timetable against actual

13.3h

Actual 15.3h, 2.0h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 52% of the dwellAgent3 stations and 35% of the dwellShared spine1 station and 13% of the dwell3 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

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	Propose	Agent	Catalog Definition Agent	workflow	15m	33m	10	Enterprise Data Warehouse
2	Impact assess	Agent	Demand Intake Agent	workflow	2h 17m	5h 16m	17	Group ERP — Financials
3	Approve Held for a named human when the unit exceeds the service request decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	Head of Service Catalog	policy	8h 5m	15h 8m	2	Group ERP — Financials
4	Publish	GBS	Catalog Definition Agent	gbs	2h 2m	2h 29m	23	Group ERP — Financials
5	Communicate	Agent	Entitlement Agent	workflow	2h 57m	6h 10m	4	Core HR and Payroll

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,413 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 gates789 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

27,588.4h

3,413 items at 485 minutes of decision each.

Agent time a week

25,654.4h

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

Gate load

100%

Inside capacity, with 26.6h of headroom.

Stations without a person

80%

1 gate left on 5 stations.

Where an item spends its time

52% waiting on a person

48% in the agent lane

An item now takes 936 minutes of worked time end to end against 936 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 Catalog Item Change

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

now Propose · Catalog Definition Agent · 15 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 21 hrs

now Propose · Catalog Definition Agent · 15 min

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

3 systems attributed

0 of 3 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

3 of 5 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 5 stations attributed here · read only

Core HR and Payroll

Workday HCM · hcm · bidirectional · critical

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

Other services in this sub-function

2 alongside this one

Request to TowerGB5A Off-catalog DemandGB5C

What this page is and is not

This is a catalogue of the modeled estate. more