LensReading which lens this session carries.
The catalogueMarketingAttribution & AnalyticsAnalytical

Service MK11A

Monthly Performance Read

Runs analytical. Starts when a drift signal breaches tolerance. It runs 71 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 2 of them on the shared spine.

Runs a week

71

81 in flight right now.

Stations

6

1 person · 3 agent · 2 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Director, Marketing Analytics.

Touchless

58%

Share of runs that complete without anybody opening them.

Timetable against actual

39.7h

Actual 42.1h, 2.4h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 14% of the dwellAgent3 stations and 47% of the dwellShared spine2 stations and 39% of the dwell3 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
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

Ingest

GBSAttribution Model Agentgbs7h 50m14h 45m8Customer Relationship Management
2

Attribute

AgentMix Modeling Agentworkflow2h 54m4h 10m4Customer Relationship Management
3

Detect anomaly

AgentAnomaly Detection Agentworkflow2h 6m3h 21m38Marketing Automation
4

Draft readout

AgentReporting Automation Agentworkflow14h 28m28h 54m2Digital Analytics
5

Leader review

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

HumanDirector, Marketing Analyticspolicy5h 44m13h 2m9Customer Relationship Management
6

Publish

GBSAttribution Model Agentgbs8h 2m15h 11m20Customer 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%
71 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 gates12 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
407.1h
71 items at 344 minutes of decision each.
Agent time a week
2,508.7h
2,120 minutes an item, which does not compete for a person.
Gate load
97%
Inside capacity, with 12.9h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
14% waiting on a person
86% in the agent lane
An item now takes 2,464 minutes of worked time end to end against 2,464 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 Monthly Performance Read

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

now Ingest · Attribution Model Agent · 7.8 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 3.3 days

now Ingest · Attribution Model Agent · 7.8 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.

3 systems attributed

0 of 3 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

4 of 6 stations attributed here · would write back

Marketing Automation

Marketo Engage · marketing · bidirectional · medium

modeled

1 of 6 stations attributed here · would write back

Digital Analytics

Adobe Analytics · marketing · 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
Marketing Analytics Orchestrator
That orchestrator’s remit
Owns analysis work end to end inside Marketing. Runs 3 lines across 16 stations, drains the repeatable share into the DATA-ANALYTICS tower, and holds 3 human gates.
Accountable person
Director, Marketing Analytics
Sub-function
Attribution & Analytics
Shared spine tower
data-analytics
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Incrementality TestMK11BMix Reallocation PositionMK11C

What this page is and is not

This is a catalogue of the modeled estate.