Service GB5A
Request to Tower
Runs transactional. Starts when a threshold is crossed. It runs 6,982 times a week across 5 stations. No station stops for a person and 5 are done by an agent, 5 of them on the shared spine.
Runs a week
6,982
106 in flight right now.
Stations
5
0 person · 0 agent · 5 spine
Agent share of steps
100%
Autonomy on this service is set at 83% against a ceiling of 90%.
Decisions a person makes
0
Nothing on this service waits for a person.
Touchless
88%
Share of runs that complete without anybody opening them.
Timetable against actual
8.8h
Actual 7.2h, 1.6h under the timetable.
Operations
The lane diagram
Read it left to right. more
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 | GBS | Catalog Definition Agent | gbs | 54m | 2h | 37 | Group ERP — Financials |
| 2 | Classify | GBS | Catalog Definition Agent | gbs | 2h 39m | 3h 11m | 3 | Group ERP — Financials |
| 3 | Check entitlement | GBS | Catalog Definition Agent | gbs | 2h 55m | 5h 14m | 26 | Group ERP — Financials |
| 4 | Route to tower | GBS | Catalog Definition Agent | gbs | 42m | 1h 31m | 24 | Group ERP — Financials |
| 5 | Acknowledge | GBS | Catalog Definition Agent | gbs | 1h 11m | 2h 12m | 16 | 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
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 8.3 hrs
now Intake · Catalog Definition Agent · 54 min
As the ledger has it
the same stations, plus 2 categories the estate already counts
0 min of 13 hrs
now Intake · Catalog Definition Agent · 54 min
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
2 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
Group ERP — Financials
SAP S/4HANA · ledger · bidirectional · critical
5 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
What this page is and is not
This is a catalogue of the modeled estate. more