LensReading which lens this session carries.
The catalogueAdministrationFacilities & WorkplaceTransactional

Service AD1A

Work Order to Close

Runs transactional. Starts when a threshold is crossed. It runs 6,703 times a week across 7 stations. No station stops for a person and 7 are done by an agent, 2 of them on the shared spine.

Runs a week

6,703

223 in flight right now.

Stations

7

0 person · 5 agent · 2 spine

Agent share of steps

100%

Autonomy on this service is set at 73% against a ceiling of 86%.

Decisions a person makes

0

Nothing on this service waits for a person.

Touchless

80%

Share of runs that complete without anybody opening them.

Timetable against actual

25.4h

Actual 19.5h, 5.9h under the timetable.

Operations

The lane diagram

Read it left to right.

Person0 stations and 0% of the dwellAgent5 stations and 53% of the dwellShared spine2 stations and 47% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
IT Service Management
Group ERP — Financials
Group ERP — Financials
IT Service Management
Group ERP — Financials
Group ERP — Financials
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

Report

AgentSpace Utilization Agentworkflow3h 2m4h 41m46Group ERP — Financials
2

Triage

AgentWork Order Triage Agentworkflow6m7m24IT Service Management
3

Classify

AgentPreventive Maintenance Agentworkflow45m1h 44m34Group ERP — Financials
4

Dispatch

GBSSpace Utilization Agentgbs2h 16m4h 18m23Group ERP — Financials
5

Execute

AgentEnergy & Utilities Agentworkflow1h 2m1h 13m20IT Service Management
6

Verify

AgentOccupancy Sensing Agentworkflow1h 7m1h 50m36Group ERP — Financials
7

Close

GBSSpace Utilization Agentgbs3h 9m3h 47m40Group ERP — Financials

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%
6,703 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
6,703 items at 0 minutes of decision each.
Agent time a week
76,749.4h
687 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 7 stations.
Where an item spends its time
100% in the agent lane
An item now takes 687 minutes of worked time end to end against 687 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 Work Order to Close

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.

7 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

7 stations, nothing waiting, nothing sent back

0 min of 11 hrs

now Report · Space Utilization Agent · 3.0 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 17 hrs

now Report · Space Utilization Agent · 3.0 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.

2 systems attributed

0 of 2 returning records

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

5 of 7 stations attributed here · would write back

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

2 of 7 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Workplace Operations Orchestrator
That orchestrator’s remit
Owns work order work end to end inside Administration. Runs 4 lines across 24 stations, drains the repeatable share into the S2P tower, and holds 2 human gates.
Accountable person
Director, Workplace Services
Sub-function
Facilities & Workplace
Shared spine tower
s2p
Hand-over points
None — this service stays inside its function

Other services in this sub-function

3 alongside this one

What this page is and is not

This is a catalogue of the modeled estate.