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

Service IT3A

Device Provisioning

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

Runs a week

855

181 in flight right now.

Stations

7

0 person · 1 agent · 6 spine

Agent share of steps

100%

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

Decisions a person makes

0

Nothing on this service waits for a person.

Touchless

83%

Share of runs that complete without anybody opening them.

Timetable against actual

23.3h

Actual 24.4h, 1.1h over the timetable.

Operations

The lane diagram

Read it left to right.

Person0 stations and 0% of the dwellAgent1 station and 15% of the dwellShared spine6 stations and 85% of the dwell2 crossings 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
Configuration Management Database
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

Trigger

Hands over at human-resources

GBSDevice Provisioning Agentgbs37m44m20IT Service Management
2

Select build

GBSDevice Provisioning Agentgbs21m36m42IT Service Management
3

Order

Hands over at procurement

GBSDevice Provisioning Agentgbs2h 50m4h 8m7IT Service Management
4

Image

GBSDevice Provisioning Agentgbs2h 24m3h 46m35IT Service Management
5

Ship

AgentRefresh Planning Agentworkflow1h 38m2h 13m43Configuration Management Database
6

Enroll

GBSDevice Provisioning Agentgbs2h 44m4h 3m2IT Service Management
7

Confirm

GBSDevice Provisioning Agentgbs21m43m32IT 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%
855 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
855 items at 0 minutes of decision each.
Agent time a week
9,333.8h
655 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 655 minutes of worked time end to end against 655 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 Device Provisioning

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 Trigger · Device Provisioning Agent · 37 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 16 hrs

now Trigger · Device Provisioning Agent · 37 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.

2 systems attributed

0 of 2 returning records

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

6 of 7 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 7 stations attributed here · read only

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
human-resources, procurement

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.