LensReading which lens this session carries.
The catalogueInformation TechnologyEnd-User ComputeTransactional

Service IT3B

Patch Cycle

Runs transactional. Starts when a threshold is crossed. It runs 391 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 4 of them on the shared spine.

Runs a week

391

55 in flight right now.

Stations

5

1 person · 0 agent · 4 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, Workplace Technology.

Touchless

89%

Share of runs that complete without anybody opening them.

Timetable against actual

7.9h

Actual 7.6h, 0.3h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 46% of the dwellAgent0 stations and 0% of the dwellShared spine4 stations and 54% of the dwell1 crossing between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
IT Service Management
IT Service Management
IT Service Management
IT Service Management
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

Detect patch

GBSDevice Provisioning Agentgbs2h 44m5h 29m1IT Service Management
2

Ring test

GBSDevice Provisioning Agentgbs23m33m25IT Service Management
3

Deploy

GBSDevice Provisioning Agentgbs2h 40m5h 1m19IT Service Management
4

Verify compliance

GBSDevice Provisioning Agentgbs1h 1m1h 12m9IT Service Management
5

Escalate holdout

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

HumanDirector, Workplace Technologypolicy5h 48m11h 39m1IT 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%
391 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 gates65 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
2,267.8h
391 items at 348 minutes of decision each.
Agent time a week
2,658.8h
408 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 7.2h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
46% waiting on a person
54% in the agent lane
An item now takes 756 minutes of worked time end to end against 756 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 Patch Cycle

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.

5 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

5 stations, nothing waiting, nothing sent back

0 min of 13 hrs

now Detect patch · Device Provisioning Agent · 2.7 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 14 hrs

now Detect patch · Device Provisioning Agent · 2.7 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

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

1 systems attributed

0 of 1 returning records

The system register

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

5 of 5 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
End-User Compute Orchestrator
That orchestrator’s remit
Owns device work end to end inside Information Technology. Runs 3 lines across 19 stations, drains the repeatable share into the IT tower, and holds 2 human gates.
Accountable person
Director, Workplace Technology
Sub-function
End-User Compute
Shared spine tower
it
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Device ProvisioningIT3ADevice RefreshIT3C

What this page is and is not

This is a catalogue of the modeled estate.