LensReading which lens this session carries.
The catalogueSalesDeal Desk & ApprovalsJudgment

Service SL6C

Discount Doctrine Position

Runs judgment. Starts when a leadership team frames the question. It runs 3 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, none of them on the shared spine.

Runs a week

3

91 in flight right now.

Stations

5

1 person · 4 agent · 0 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, Deal Desk.

Touchless

32%

Share of runs that complete without anybody opening them.

Timetable against actual

792.4h

Actual 643.9h, 148.5h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 17% of the dwellAgent4 stations and 83% 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
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

AgentDiscount Policy Agentstrategy57h 19m74h 28m32Customer Relationship Management
2

Model elasticity

AgentMargin Impact Agentstrategy57h 56m135h 23m14Customer Relationship Management
3

Draft position

AgentNon-standard Terms Agentstrategy17h 47m38h 5m18Customer Relationship Management
4

Challenge

AgentApproval Routing Agentstrategy10h 54m17h 25m23Customer Relationship Management
5

Ratify

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

HumanDirector, Deal Deskpolicy29h 51m37h 19m4Contract 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%
3 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
89.6h
3 items at 1,791 minutes of decision each.
Agent time a week
431.8h
8,636 minutes an item, which does not compete for a person.
Gate load
85%
Inside capacity, with 15.5h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
17% waiting on a person
83% in the agent lane
An item now takes 10,427 minutes of worked time end to end against 10,427 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 Discount Doctrine 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.

5 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

5 stations, nothing waiting, nothing sent back

0 min of 7.2 days

now Frame · Discount Policy Agent · 2.4 days

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 7.5 days

now Frame · Discount Policy Agent · 2.4 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

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

4 of 5 stations attributed here · would write back

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

1 of 5 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Deal Desk Orchestrator
That orchestrator’s remit
Owns deal work end to end inside Sales. Runs 3 lines across 18 stations, drains the repeatable share into the O2C tower, and holds 4 human gates.
Accountable person
Director, Deal Desk
Sub-function
Deal Desk & Approvals
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

What this page is and is not

This is a catalogue of the modeled estate.