LensReading which lens this session carries.
The catalogueCustomer ServiceWorkforce ManagementAnalytical

Service CS10C

Outsourcer Allocation

Runs analytical. Starts when a leader asks the question. It runs 74 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

74

112 in flight right now.

Stations

5

1 person · 4 agent · 0 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, Workforce Management.

Touchless

71%

Share of runs that complete without anybody opening them.

Timetable against actual

151.9h

Actual 188.7h, 36.8h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 50% of the dwellAgent4 stations and 50% 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
Contact Center Platform
IT Service Management
Customer Relationship Management
Workforce 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

Model demand

AgentVolume Forecast Agentworkflow13h 36m16h 29m43Customer Relationship Management
2

Score partners

AgentCapacity Model Agentworkflow10h 59m17h 45m8Contact Center Platform
3

Draft allocation

AgentShift Scheduling Agentworkflow2h 44m5h 2m32IT Service Management
4

Approve

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

HumanDirector, Workforce Managementpolicy37h 45m58h 15m7Customer Relationship Management
5

Issue

Hands over at procurement

AgentShrinkage Agentworkflow9h 59m12h 17m22Workforce 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%
74 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 gates80 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,793.5h
74 items at 2,265 minutes of decision each.
Agent time a week
2,760.2h
2,238 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 6.5h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
50% waiting on a person
50% in the agent lane
An item now takes 4,503 minutes of worked time end to end against 4,503 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 Outsourcer Allocation

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

now Model demand · Volume Forecast Agent · 14 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 3.2 days

now Model demand · Volume Forecast Agent · 14 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

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.

4 systems attributed

0 of 4 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

2 of 5 stations attributed here · would write back

Contact Center Platform

Genesys Cloud CX · service · bidirectional · high

modeled

1 of 5 stations attributed here · would write back

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

1 of 5 stations attributed here · would write back

Workforce Management

NICE WFM · service · inbound · medium

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
Workforce Management Orchestrator
That orchestrator’s remit
Owns roster work end to end inside Customer Service. Runs 3 lines across 16 stations, drains the repeatable share into no shared tower, and holds 2 human gates.
Accountable person
Director, Workforce Management
Sub-function
Workforce Management
Shared spine tower
Not on the shared spine
Hand-over points
procurement

Other services in this sub-function

2 alongside this one

Forecast to ScheduleCS10AIntraday RebalanceCS10B

What this page is and is not

This is a catalogue of the modeled estate.