LensReading which lens this session carries.
The catalogueSalesTerritory & Quota PlanningJudgment

Service SL1C

Coverage Model Position

Runs judgment. Starts when a break condition on a live position fires. It runs 5 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, none of them on the shared spine.

Runs a week

5

109 in flight right now.

Stations

6

1 person · 5 agent · 0 spine

Agent share of steps

83%

Autonomy on this service is set at 46% against a ceiling of 66%.

Decisions a person makes

1

Held by VP Sales Strategy.

Touchless

32%

Share of runs that complete without anybody opening them.

Timetable against actual

248.4h

Actual 196.1h, 52.3h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 8% of the dwellAgent5 stations and 92% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
Contract Lifecycle 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

Frame question

AgentAccount Segmentation Agentstrategy49h 31m62h 37m44Customer Relationship Management
2

Gather evidence

AgentCapacity Model Agentstrategy50h 19m109h 18m13Customer Relationship Management
3

Model options

AgentQuota Distribution Agentstrategy47h 4m98h 2m11Customer Relationship Management
4

Draft position

AgentWhite Space Agentstrategy51h 45m61h 6m0Customer Relationship Management
5

Challenge

AgentCoverage Gap Agentstrategy49h 43m68h 58m40Customer Relationship Management
6

Ratify

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

HumanVP Sales Strategypolicy20h 27m36h 53m1Contract Lifecycle 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%
5 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 gates3 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
102.3h
5 items at 1,227 minutes of decision each.
Agent time a week
1,241.8h
14,902 minutes an item, which does not compete for a person.
Gate load
97%
Inside capacity, with 2.8h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
92% in the agent lane
An item now takes 16,129 minutes of worked time end to end against 16,129 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 Coverage Model Position

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 11.2 days

now Frame question · Account Segmentation Agent · 2.1 days

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 11.4 days

now Frame question · Account Segmentation Agent · 2.1 days

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

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

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

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

1 of 6 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Territory Planning Orchestrator
That orchestrator’s remit
Owns territory work end to end inside Sales. Runs 3 lines across 20 stations, drains the repeatable share into the P2P tower, and holds 4 human gates.
Accountable person
VP Sales Strategy
Sub-function
Territory & Quota Planning
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

Annual Territory BuildSL1AMid-year RebalanceSL1B

What this page is and is not

This is a catalogue of the modeled estate.