LensReading which lens this session carries.
The catalogueSalesSolution & ProposalTransactional

Service SL5A

RFP Response

Runs transactional. Starts when a threshold is crossed. It runs 2,255 times a week across 9 stations. 2 of those stations stop for a person and 7 are done by an agent, none of them on the shared spine.

Runs a week

2,255

212 in flight right now.

Stations

9

2 person · 7 agent · 0 spine

Agent share of steps

78%

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

Decisions a person makes

2

Held by Director, Solution Consulting.

Touchless

85%

Share of runs that complete without anybody opening them.

Timetable against actual

4.8h

Actual 6.0h, 1.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 55% of the dwellAgent7 stations and 45% 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
Configure, Price and Quote
Customer Relationship Management
Contract Lifecycle Management
Configure, Price and Quote
Contract Lifecycle 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

Intake RFP

AgentRequirements Extraction Agentworkflow2h 2m3h 59m45Customer Relationship Management
2

Extract requirements

AgentSolution Configuration Agentworkflow1h 28m2h 17m42Contract Lifecycle Management
3

Compliance matrix

AgentReference Selection Agentworkflow1h 5m1h 28m20Configure, Price and Quote
4

Configure solution

AgentProposal Drafting Agentworkflow19m29m7Customer Relationship Management
5

Assemble pricing

Hands over at revenue-operations

AgentPricing Assembly Agentworkflow42m1h 34m43Contract Lifecycle Management
6

Draft response

AgentCompliance Matrix Agentworkflow6m13m9Configure, Price and Quote
7

Legal check

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.

Hands over at legal

HumanDirector, Solution Consultingpolicy2h 37m3h 43m7Contract Lifecycle Management
8

Bid decision

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 34m8h 4m3Contract Lifecycle Management
9

Submit

AgentRequirements Extraction Agentworkflow4m6m36Customer 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%
2,255 a week is what the estate records.
Decisions handed to agents0 of 2
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates463 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
16,198.4h
2,255 items at 431 minutes of decision each.
Agent time a week
13,003.8h
346 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 6.6h of headroom.
Stations without a person
78%
2 gates left on 9 stations.
Where an item spends its time
55% waiting on a person
45% in the agent lane
An item now takes 777 minutes of worked time end to end against 777 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 RFP Response

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.

9 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

9 stations, nothing waiting, nothing sent back

0 min of 13 hrs

now Intake RFP · Requirements Extraction Agent · 2.0 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 29 hrs

now Intake RFP · Requirements Extraction Agent · 2.0 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

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

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

4 of 9 stations attributed here · would write back

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

3 of 9 stations attributed here · would write back

Configure, Price and Quote

Salesforce CPQ · crm · inbound · high

modeled

2 of 9 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
revenue-operations, legal

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.