LensReading which lens this session carries.
The catalogueMarketingCustomer AdvocacyTransactional

Service MK9A

Case Study Production

Runs transactional. Starts when a scheduled window opens. It runs 3,417 times a week across 7 stations. 3 of those stations stop for a person and 4 are done by an agent, none of them on the shared spine.

Runs a week

3,417

74 in flight right now.

Stations

7

3 person · 4 agent · 0 spine

Agent share of steps

57%

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

Decisions a person makes

3

Held by Director, Customer Advocacy.

Touchless

69%

Share of runs that complete without anybody opening them.

Timetable against actual

9.7h

Actual 11.2h, 1.5h over the timetable.

Operations

The lane diagram

Read it left to right.

Person3 stations and 69% of the dwellAgent4 stations and 31% of the dwellShared spine0 stations and 0% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Customer Relationship Management
Marketing Automation
Digital Analytics
Customer Relationship Management
Customer Relationship 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

Identify candidate

AgentAdvocate Identification Agentworkflow1h 54m4h 16m14Customer Relationship Management
2

Secure consent

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

HumanDirector, Customer Advocacypolicy4h 49m10h 40m2Customer Relationship Management
3

Interview

AgentCase Study Drafting Agentworkflow26m59m14Marketing Automation
4

Draft

AgentReview Solicitation Agentworkflow12m19m20Digital Analytics
5

Customer approve

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

HumanDirector, Customer Advocacypolicy3h 45m4h 40m5Customer Relationship Management
6

Legal clear

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

Hands over at legal

HumanDirector, Customer Advocacypolicy1h 50m2h 24m9Customer Relationship Management
7

Publish

AgentAdvocacy Orchestratorworkflow2h 6m2h 31m10Customer 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%
3,417 a week is what the estate records.
Decisions handed to agents0 of 3
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates1016 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
35,536.8h
3,417 items at 624 minutes of decision each.
Agent time a week
15,832.1h
278 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 23.2h of headroom.
Stations without a person
57%
3 gates left on 7 stations.
Where an item spends its time
69% waiting on a person
31% in the agent lane
An item now takes 902 minutes of worked time end to end against 902 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 Case Study Production

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.

7 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

7 stations, nothing waiting, nothing sent back

0 min of 15 hrs

now Identify candidate · Advocate Identification Agent · 1.9 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 36 hrs

now Identify candidate · Advocate Identification Agent · 1.9 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.

Attestations on this estate are written against intake items, not against procedures, so a step done off the platform cannot be matched to the attestation that covers it.

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

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

5 of 7 stations attributed here · would write back

Marketing Automation

Marketo Engage · marketing · bidirectional · medium

modeled

1 of 7 stations attributed here · would write back

Digital Analytics

Adobe Analytics · marketing · inbound · medium

modeled

1 of 7 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

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