The catalogue Revenue Growth ManagementBooking & Order ManagementTransactional

Service RO4A

Order-to-Provision

Runs transactional. Starts when a scheduled window opens. It runs 2,101 times a week across 7 stations. No station stops for a person and 7 are done by an agent, 5 of them on the shared spine.

Runs a week

2,101

202 in flight right now.

Stations

0 person · 2 agent · 5 spine

Agent share of steps

100%

Autonomy on this service is set at 82% against a ceiling of 91%.

Decisions a person makes

Nothing on this service waits for a person.

Touchless

91%

Share of runs that complete without anybody opening them.

Timetable against actual

14.0h

Actual 12.6h, 1.4h under the timetable.

Operations

The lane diagram

Read it left to right. more

Person0 stations and 0% of the dwellAgent2 stations and 36% of the dwellShared spine5 stations and 64% of the dwell3 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Customer Relationship Management

Enterprise Data Warehouse

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	Receive order	GBS	Order Validation Agent	gbs	1h 57m	3h 50m	18	Customer Relationship Management
2	Validate	GBS	Order Validation Agent	gbs	1h 58m	2h 26m	33	Customer Relationship Management
3	Credit check Hands over at finance	GBS	Order Validation Agent	gbs	54m	1h 38m	20	Customer Relationship Management
4	Book	GBS	Order Validation Agent	gbs	1h 40m	2h 28m	38	Customer Relationship Management
5	Trigger provisioning Hands over at information-technology	Agent	Backlog Agent	workflow	1h 45m	3h 10m	37	Customer Relationship Management
6	Confirm to customer	GBS	Order Validation Agent	gbs	1h 8m	1h 53m	39	Customer Relationship Management
7	Close	Agent	Order Management Orchestrator	workflow	2h 35m	4h 33m	17	Enterprise Data Warehouse

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%

2,101 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

2,101 items at 0 minutes of decision each.

Agent time a week

25,107h

717 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 7 stations.

Where an item spends its time

100% in the agent lane

An item now takes 717 minutes of worked time end to end against 717 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 Order-to-Provision

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

7 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

7 stations, nothing waiting, nothing sent back

0 min of 12 hrs

now Receive order · Order Validation Agent · 1.9 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 17 hrs

now Receive order · Order Validation Agent · 1.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

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

2 systems attributed

0 of 2 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

6 of 7 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 7 stations attributed here · read only

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Order Management Orchestrator
That orchestrator’s remit: Owns order work end to end inside Revenue Growth Management. Runs 3 lines across 16 stations, drains the repeatable share into the O2C tower, and holds 2 human gates.
Accountable person: Director, Order Management
Sub-function: Booking & Order Management
Shared spine tower: o2c
Hand-over points: finance, information-technology

Other services in this sub-function

2 alongside this one

Order ExceptionRO4B Backlog ReviewRO4C

What this page is and is not

This is a catalogue of the modeled estate. more