LensReading which lens this session carries.
The catalogueSalesIncentive CompensationJudgment

Service SL11C

Plan Design Cycle

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

Runs a week

1

131 in flight right now.

Stations

7

1 person · 6 agent · 0 spine

Agent share of steps

86%

Autonomy on this service is set at 78% against a ceiling of 80%.

Decisions a person makes

1

Held by Director, Sales Compensation.

Touchless

34%

Share of runs that complete without anybody opening them.

Timetable against actual

507.3h

Actual 590.3h, 83.0h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 33% of the dwellAgent6 stations and 67% of the dwellShared spine0 stations and 0% of the dwell2 crossings 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
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

Frame objectives

AgentPlan Modeling Agentstrategy69h 44m149h 31m14Customer Relationship Management
2

Model behaviors

AgentAttainment Calculation Agentstrategy44h 16m97h 11m2Customer Relationship Management
3

Cost scenarios

AgentDispute Triage Agentstrategy12h 18m19h 40m15Customer Relationship Management
4

Draft plan

AgentAccrual Agentstrategy45h 32m62h 31m28Customer Relationship Management
5

Challenge

AgentPlan Communication Agentstrategy57h 26m72h 15m35Customer Relationship Management
6

Leadership ratify

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

HumanDirector, Sales Compensationpolicy143h234h 49m8Contract Lifecycle Management
7

Publish

AgentComp Design Agentstrategy58h 12m73h 1m29Customer 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%
1 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 gates5 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
143h
1 items at 8,580 minutes of decision each.
Agent time a week
287.5h
17,248 minutes an item, which does not compete for a person.
Gate load
82%
Inside capacity, with 32h of headroom.
Stations without a person
86%
1 gate left on 7 stations.
Where an item spends its time
33% waiting on a person
67% in the agent lane
An item now takes 25,828 minutes of worked time end to end against 25,828 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 Plan Design Cycle

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.

7 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

7 stations, nothing waiting, nothing sent back

0 min of 17.9 days

now Frame objectives · Plan Modeling Agent · 2.9 days

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 18.0 days

now Frame objectives · Plan Modeling Agent · 2.9 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

2 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

6 of 7 stations attributed here · would write back

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

1 of 7 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Incentive Comp Orchestrator
That orchestrator’s remit
Owns comp statement work end to end inside Sales. Runs 3 lines across 20 stations, drains the repeatable share into the H2R tower, and holds 4 human gates.
Accountable person
Director, Sales Compensation
Sub-function
Incentive Compensation
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

Monthly Commission RunSL11ADispute ResolutionSL11B

What this page is and is not

This is a catalogue of the modeled estate.