LensReading which lens this session carries.
The catalogueMarketingField & EventsAnalytical

Service MK8C

Event Portfolio Review

Runs analytical. Starts when the reporting period closes. It runs 26 times a week across 4 stations. One of those stations stops for a person and 3 are done by an agent, none of them on the shared spine.

Runs a week

26

29 in flight right now.

Stations

4

1 person · 3 agent · 0 spine

Agent share of steps

75%

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

Decisions a person makes

1

Held by Director, Field Marketing.

Touchless

61%

Share of runs that complete without anybody opening them.

Timetable against actual

196.2h

Actual 232.2h, 36.0h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 39% of the dwellAgent3 stations and 61% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Marketing Automation
Digital Analytics
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

Aggregate return

AgentEvent Selection Agentworkflow13h 24m29h 26m6Customer Relationship Management
2

Rank

AgentLogistics Coordination Agentworkflow13h 50m29h 43m6Marketing Automation
3

Draft recommendation

AgentAttendee Targeting Agentworkflow2h 4m3h 51m16Digital Analytics
4

Leader review

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

HumanDirector, Field Marketingpolicy18h 41m35h 23m1Customer 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%
26 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 gates14 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
485.8h
26 items at 1,121 minutes of decision each.
Agent time a week
761.8h
1,758 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 4.2h of headroom.
Stations without a person
75%
1 gate left on 4 stations.
Where an item spends its time
39% waiting on a person
61% in the agent lane
An item now takes 2,879 minutes of worked time end to end against 2,879 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 Event Portfolio Review

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.

4 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

4 stations, nothing waiting, nothing sent back

0 min of 48 hrs

now Aggregate return · Event Selection Agent · 13 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 2.2 days

now Aggregate return · Event Selection Agent · 13 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

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

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

2 of 4 stations attributed here · would write back

Marketing Automation

Marketo Engage · marketing · bidirectional · medium

modeled

1 of 4 stations attributed here · would write back

Digital Analytics

Adobe Analytics · marketing · inbound · medium

modeled

1 of 4 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Events Orchestrator
That orchestrator’s remit
Owns event work end to end inside Marketing. Runs 3 lines across 18 stations, drains the repeatable share into the A2L tower, and holds 2 human gates.
Accountable person
Director, Field Marketing
Sub-function
Field & Events
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

What this page is and is not

This is a catalogue of the modeled estate.