LensReading which lens this session carries.
The catalogueMarketingDemand GenerationTransactional

Service MK3A

Campaign Launch

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

Runs a week

3,805

141 in flight right now.

Stations

8

2 person · 4 agent · 2 spine

Agent share of steps

75%

Autonomy on this service is set at 80% against a ceiling of 88%.

Decisions a person makes

2

Held by VP Demand Generation.

Touchless

85%

Share of runs that complete without anybody opening them.

Timetable against actual

18.0h

Actual 20.8h, 2.8h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 46% of the dwellAgent4 stations and 45% of the dwellShared spine2 stations and 9% of the dwell5 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
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

Brief

AgentAudience Build Agentworkflow2h 9m2h 29m4Customer Relationship Management
2

Build audience

GBSAudience Build Agentgbs53m1h 18m19Customer Relationship Management
3

Generate variants

AgentBid Optimization Agentworkflow2h 27m5h 42m25Marketing Automation
4

Brand check

AgentCreative Variant Agentworkflow2h 37m5h 53m4Digital Analytics
5

Legal check

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

Hands over at legal

HumanVP Demand Generationpolicy15m34m5Customer Relationship Management
6

Launch

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

HumanVP Demand Generationpolicy8h 36m19h 3m8Customer Relationship Management
7

Optimize

GBSAudience Build Agentgbs47m1h 45m35Customer Relationship Management
8

Report

AgentDemand Gen Orchestratorworkflow1h 27m3h 25m41Customer 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,805 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 gates963 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
33,674.3h
3,805 items at 531 minutes of decision each.
Agent time a week
39,318.3h
620 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 30.8h of headroom.
Stations without a person
75%
2 gates left on 8 stations.
Where an item spends its time
46% waiting on a person
54% in the agent lane
An item now takes 1,151 minutes of worked time end to end against 1,151 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 Campaign Launch

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.

8 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

8 stations, nothing waiting, nothing sent back

0 min of 19 hrs

now Brief · Audience Build Agent · 2.1 hrs

As the ledger has it

the same stations, plus 6 categories the estate already counts

0 min of 2.2 days

now Brief · Audience Build Agent · 2.1 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

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

3 systems attributed

0 of 3 returning records

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

6 of 8 stations attributed here · would write back

Marketing Automation

Marketo Engage · marketing · bidirectional · medium

modeled

1 of 8 stations attributed here · would write back

Digital Analytics

Adobe Analytics · marketing · inbound · medium

modeled

1 of 8 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Demand Gen Orchestrator
That orchestrator’s remit
Owns campaign work end to end inside Marketing. Runs 3 lines across 17 stations, drains the repeatable share into the A2L tower, and holds 3 human gates.
Accountable person
VP Demand Generation
Sub-function
Demand Generation
Shared spine tower
a2l
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.