LensReading which lens this session carries.
The catalogueMarketingContent StudioTransactional

Service MK4B

Localization Run

Runs transactional. Starts when a scheduled window opens. It runs 635 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 2 of them on the shared spine.

Runs a week

635

103 in flight right now.

Stations

5

1 person · 2 agent · 2 spine

Agent share of steps

80%

Autonomy on this service is set at 75% against a ceiling of 78%.

Decisions a person makes

1

Held by Director, Content.

Touchless

71%

Share of runs that complete without anybody opening them.

Timetable against actual

3.8h

Actual 3.6h, 0.2h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 44% of the dwellAgent2 stations and 23% of the dwellShared spine2 stations and 33% 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
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

Select assets

AgentContent Brief Agentworkflow1h 16m2h 36m22Customer Relationship Management
2

Translate

GBSContent Brief Agentgbs2h 25m4h 17m36Customer Relationship Management
3

Cultural check

AgentDesign Variant Agentworkflow1h1h 37m16Marketing Automation
4

Market review

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

HumanDirector, Contentpolicy4h 19m6h 38m2Customer Relationship Management
5

Publish

GBSContent Brief Agentgbs47m1h 5m27Customer 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%
635 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 gates79 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,741.1h
635 items at 259 minutes of decision each.
Agent time a week
3,471.3h
328 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 23.9h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
44% waiting on a person
56% in the agent lane
An item now takes 587 minutes of worked time end to end against 587 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 Localization Run

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 9.8 hrs

now Select assets · Content Brief Agent · 1.3 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 25 hrs

now Select assets · Content Brief Agent · 1.3 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

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

2 systems attributed

0 of 2 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

4 of 5 stations attributed here · would write back

Marketing Automation

Marketo Engage · marketing · bidirectional · medium

modeled

1 of 5 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Content Orchestrator
That orchestrator’s remit
Owns content asset work end to end inside Marketing. Runs 3 lines across 17 stations, drains the repeatable share into the A2L tower, and holds 4 human gates.
Accountable person
Director, Content
Sub-function
Content Studio
Shared spine tower
a2l
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Content ProductionMK4AContent RefreshMK4C

What this page is and is not

This is a catalogue of the modeled estate.