LensReading which lens this session carries.
The catalogueSalesSolution & ProposalTransactional

Service SL5C

Reference & Proof Pack

Runs transactional. Starts when an upstream system posts an event. It runs 589 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

589

90 in flight right now.

Stations

5

1 person · 4 agent · 0 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, Solution Consulting.

Touchless

82%

Share of runs that complete without anybody opening them.

Timetable against actual

1.0h

Actual 1.0h, 0.0h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 41% of the dwellAgent4 stations and 59% 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
Contract Lifecycle Management
Contract Lifecycle Management
Configure, Price and Quote
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

Match profile

AgentRequirements Extraction Agentworkflow33m1h 1m29Customer Relationship Management
2

Select references

AgentSolution Configuration Agentworkflow42m1h 32m43Contract Lifecycle Management
3

Clear usage

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

HumanDirector, Solution Consultingpolicy4h 18m8h 32m0Contract Lifecycle Management
4

Assemble pack

AgentProposal Drafting Agentworkflow3h 4m5h 37m17Configure, Price and Quote
5

Deliver

AgentPricing Assembly Agentworkflow1h 56m3h 33m1Customer 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%
589 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 gates73 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
2,532.7h
589 items at 258 minutes of decision each.
Agent time a week
3,681.3h
375 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 22.3h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
41% waiting on a person
59% in the agent lane
An item now takes 633 minutes of worked time end to end against 633 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 Reference & Proof Pack

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

now Match profile · Requirements Extraction Agent · 33 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 16 hrs

now Match profile · Requirements Extraction Agent · 33 min

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.

3 systems attributed

0 of 3 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

2 of 5 stations attributed here · would write back

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

2 of 5 stations attributed here · would write back

Configure, Price and Quote

Salesforce CPQ · crm · inbound · high

modeled

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

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

RFP ResponseSL5AStandard ProposalSL5B

What this page is and is not

This is a catalogue of the modeled estate.