LensReading which lens this session carries.
The catalogueAdministrationHospitality & ReceptionTransactional

Service AD11A

Visitor Arrival

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

Runs a week

5,806

96 in flight right now.

Stations

6

1 person · 4 agent · 1 spine

Agent share of steps

83%

Autonomy on this service is set at 83% against a ceiling of 90%.

Decisions a person makes

1

Held by Manager, Hospitality Services.

Touchless

83%

Share of runs that complete without anybody opening them.

Timetable against actual

9.1h

Actual 11.5h, 2.4h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 48% of the dwellAgent4 stations and 35% of the dwellShared spine1 station and 17% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
IT Service Management
Group ERP — Financials
IT Service 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

Pre-register

AgentVisitor Pre-registration Agentworkflow19m39m18Group ERP — Financials
2

Screen

GBSVisitor Pre-registration Agentgbs2h 3m4h 1m35Group ERP — Financials
3

Credential

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

HumanManager, Hospitality Servicespolicy5h 41m8h 57m3Group ERP — Financials
4

Arrive

AgentCatering Coordination Agentworkflow1h 7m1h 20m5IT Service Management
5

Host notify

AgentMeeting Room Agentworkflow1h 54m2h 14m26Group ERP — Financials
6

Depart

AgentVisitor Experience Agentworkflow50m1h 54m9IT Service 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%
5,806 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 gates943 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
32,997.4h
5,806 items at 341 minutes of decision each.
Agent time a week
36,094h
373 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 7.6h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
48% waiting on a person
52% in the agent lane
An item now takes 714 minutes of worked time end to end against 714 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 Visitor Arrival

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

now Pre-register · Visitor Pre-registration Agent · 19 min

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 25 hrs

now Pre-register · Visitor Pre-registration Agent · 19 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

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

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

4 of 6 stations attributed here · would write back

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

2 of 6 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Hospitality Orchestrator
That orchestrator’s remit
Owns visit work end to end inside Administration. Runs 3 lines across 16 stations, drains the repeatable share into the S2P tower, and holds 1 human gates.
Accountable person
Manager, Hospitality Services
Sub-function
Hospitality & Reception
Shared spine tower
s2p
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.