LensReading which lens this session carries.
The catalogueCustomer ServiceWorkforce ManagementAnalytical

Service CS10A

Forecast to Schedule

Runs analytical. Starts when a leader asks the question. It runs 54 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 1 of them on the shared spine.

Runs a week

54

77 in flight right now.

Stations

6

1 person · 4 agent · 1 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Director, Workforce Management.

Touchless

70%

Share of runs that complete without anybody opening them.

Timetable against actual

169.7h

Actual 202.7h, 33.0h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 47% of the dwellAgent4 stations and 38% of the dwellShared spine1 station and 14% of the dwell3 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
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

Forecast volume

AgentVolume Forecast Agentworkflow5h 41m12h 54m6Customer Relationship Management
2

Model capacity

AgentCapacity Model Agentworkflow5h 6m10h 20m3Contact Center Platform
3

Draft roster

AgentShift Scheduling Agentworkflow12h 49m15h 36m11IT Service Management
4

Compliance check

GBSShift Scheduling Agentgbs11h 41m16h 2m43Customer Relationship Management
5

Publish

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 Managementpolicy38h 52m82h 44m3Customer Relationship Management
6

Distribute

AgentSkill Coverage Agentworkflow7h 45m9h 1m11Workforce 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%
54 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 gates60 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,098.8h
54 items at 2,332 minutes of decision each.
Agent time a week
2,323.8h
2,582 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 1.2h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
47% waiting on a person
53% in the agent lane
An item now takes 4,914 minutes of worked time end to end against 4,914 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 Forecast to Schedule

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.

6 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

6 stations, nothing waiting, nothing sent back

0 min of 3.4 days

now Forecast volume · Volume Forecast Agent · 5.7 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 5.4 days

now Forecast volume · Volume Forecast Agent · 5.7 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

5 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.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

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

3 of 6 stations attributed here · would write back

Contact Center Platform

Genesys Cloud CX · service · bidirectional · high

modeled

1 of 6 stations attributed here · would write back

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

1 of 6 stations attributed here · would write back

Workforce Management

NICE WFM · service · inbound · medium

modeled

1 of 6 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
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Intraday RebalanceCS10BOutsourcer AllocationCS10C

What this page is and is not

This is a catalogue of the modeled estate.