LensReading which lens this session carries.
The catalogueMarketingField & EventsTransactional

Service MK8B

Field Program

Runs transactional. Starts when a request lands in the queue. It runs 1,347 times a week across 6 stations. No station stops for a person and 6 are done by an agent, 1 of them on the shared spine.

Runs a week

1,347

176 in flight right now.

Stations

6

0 person · 5 agent · 1 spine

Agent share of steps

100%

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

Decisions a person makes

0

Nothing on this service waits for a person.

Touchless

78%

Share of runs that complete without anybody opening them.

Timetable against actual

11.1h

Actual 9.2h, 1.9h under the timetable.

Operations

The lane diagram

Read it left to right.

Person0 stations and 0% of the dwellAgent5 stations and 75% of the dwellShared spine1 station and 25% of the dwell2 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
Marketing Automation
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

Plan

AgentEvent Selection Agentworkflow10m14m40Customer Relationship Management
2

Invite

GBSEvent Selection Agentgbs1h 43m4h 7m35Customer Relationship Management
3

Confirm

AgentAttendee Targeting Agentworkflow39m1h 19m43Marketing Automation
4

Deliver

AgentBooth Content Agentworkflow1h 50m2h 41m12Digital Analytics
5

Debrief

AgentFollow-up Sequencing Agentworkflow1h1h 35m15Customer Relationship Management
6

Score return

AgentEvent Return Agentworkflow1h 37m1h 57m31Marketing Automation

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%
1,347 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 gates1 person
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
0h
1,347 items at 0 minutes of decision each.
Agent time a week
9,406.6h
419 minutes an item, which does not compete for a person.
Gate load
0%
Inside capacity, with 35h of headroom.
Stations without a person
100%
0 gates left on 6 stations.
Where an item spends its time
100% in the agent lane
An item now takes 419 minutes of worked time end to end against 419 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 Field Program

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

now Plan · Event Selection Agent · 10 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 12 hrs

now Plan · Event Selection Agent · 10 min

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

3 of 6 stations attributed here · would write back

Marketing Automation

Marketo Engage · marketing · bidirectional · medium

modeled

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