LensReading which lens this session carries.
The catalogueRevenue Growth ManagementTerritory & Comp OpsTransactional

Service RO8A

Assignment Change

Runs transactional. Starts when a request lands in the queue. It runs 8,139 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 3 of them on the shared spine.

Runs a week

8,139

173 in flight right now.

Stations

6

1 person · 2 agent · 3 spine

Agent share of steps

83%

Autonomy on this service is set at 71% against a ceiling of 84%.

Decisions a person makes

1

Held by Director, Sales Operations.

Touchless

77%

Share of runs that complete without anybody opening them.

Timetable against actual

23.9h

Actual 28.4h, 4.5h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 26% of the dwellAgent2 stations and 34% of the dwellShared spine3 stations and 40% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Customer Relationship Management
Enterprise Data Warehouse
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
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

Request

AgentTerritory Assignment Agentworkflow1h 30m2h 25m35Customer Relationship Management
2

Validate rules

GBSTerritory Assignment Agentgbs1h 4m1h 47m18Customer Relationship Management
3

Model credit impact

AgentSplit Resolution Agentworkflow3h 5m5h 16m41Enterprise Data Warehouse
4

Approve

Held for a named human when the unit exceeds the assignment decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

HumanDirector, Sales Operationspolicy3h 30m5h 30m3Customer Relationship Management
5

Apply

GBSTerritory Assignment Agentgbs3h 8m4h 28m32Customer Relationship Management
6

Notify

GBSTerritory Assignment Agentgbs1h 15m2h 54m44Customer Relationship Management

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%
8,139 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 gates814 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.
Person time a week
28,486.5h
8,139 items at 210 minutes of decision each.
Agent time a week
81,661.3h
602 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 3.5h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
26% waiting on a person
74% in the agent lane
An item now takes 812 minutes of worked time end to end against 812 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 Assignment Change

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

now Request · Territory Assignment Agent · 1.5 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 30 hrs

now Request · Territory Assignment Agent · 1.5 hrs

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

5 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.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

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.

2 systems attributed

0 of 2 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

5 of 6 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 6 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Territory Ops Orchestrator
That orchestrator’s remit
Owns assignment work end to end inside Revenue Growth Management. Runs 3 lines across 15 stations, drains the repeatable share into the H2R tower, and holds 3 human gates.
Accountable person
Director, Sales Operations
Sub-function
Territory & Comp Ops
Shared spine tower
h2r
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Credit & Split ResolutionRO8BPlan Load CycleRO8C

What this page is and is not

This is a catalogue of the modeled estate.