The catalogue MarketingField & EventsTransactional

Service MK8A

Event Delivery

Runs transactional. Starts when a request lands in the queue. It runs 1,562 times a week across 8 stations. One of those stations stops for a person and 7 are done by an agent, 3 of them on the shared spine.

Runs a week

1,562

172 in flight right now.

Stations

1 person · 4 agent · 3 spine

Agent share of steps

88%

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

Decisions a person makes

Held by Director, Field Marketing.

Touchless

77%

Share of runs that complete without anybody opening them.

Timetable against actual

24.9h

Actual 28.2h, 3.3h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 43% of the dwellAgent4 stations and 31% of the dwellShared spine3 stations and 26% of the dwell4 crossings 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.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Select event	Agent	Event Selection Agent	workflow	23m	40m	24	Customer Relationship Management
2	Budget approve 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.	Human	Director, Field Marketing	policy	6h 51m	10h 41m	2	Customer Relationship Management
3	Contract Hands over at procurement	GBS	Event Selection Agent	gbs	51m	1h 21m	30	Customer Relationship Management
4	Target attendees	Agent	Booth Content Agent	workflow	1h 4m	2h 15m	40	Marketing Automation
5	Build content	Agent	Follow-up Sequencing Agent	workflow	1h 57m	2h 47m	37	Digital Analytics
6	Run	Agent	Event Return Agent	workflow	1h 30m	3h 34m	6	Customer Relationship Management
7	Capture leads	GBS	Event Selection Agent	gbs	14m	32m	9	Customer Relationship Management
8	Follow up Hands over at sales	GBS	Event Selection Agent	gbs	3h 2m	5h 46m	24	Customer 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. more

Move something

Demand100%

1,562 a week is what the estate records. more

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 gates306 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. more

Person time a week

10,699.7h

1,562 items at 411 minutes of decision each.

Agent time a week

14,084h

541 minutes an item, which does not compete for a person.

Gate load

100%

Inside capacity, with 10.3h of headroom.

Stations without a person

88%

1 gate left on 8 stations.

Where an item spends its time

43% waiting on a person

57% in the agent lane

An item now takes 952 minutes of worked time end to end against 952 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 Delivery

The simulation is arithmetic on the estate, not a queueing model. more

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking. more

8 stations, walked twice

Once clean, once with the categories the estate counts

This is the same unit on the same stations, breaking. more

No break below was chosen. more

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

now Select event · Event Selection Agent · 23 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 21 hrs

now Select event · Event Selection Agent · 23 min

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

3 counted categories land on this procedure. more

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen. more

Two clocks run. Worked time is the sum of the time the work is actually being done … more

Live observability

Systems this service would touch

Attributed by rule from the function's system list. more

3 systems attributed

0 of 3 returning records

The system register

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

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: a2l
Hand-over points: procurement, sales

Other services in this sub-function

2 alongside this one

Field ProgramMK8B Event Portfolio ReviewMK8C

What this page is and is not

This is a catalogue of the modeled estate. more