LensReading which lens this session carries.
The catalogueInformation TechnologyIT Financial ManagementAnalytical

Service IT11B

Unit Cost Read

Runs analytical. Starts when the cycle calendar fires. It runs 9 times a week across 4 stations. One of those stations stops for a person and 3 are done by an agent, 1 of them on the shared spine.

Runs a week

9

53 in flight right now.

Stations

4

1 person · 2 agent · 1 spine

Agent share of steps

75%

Autonomy on this service is set at 66% against a ceiling of 88%.

Decisions a person makes

1

Held by Director, IT Financial Management.

Touchless

61%

Share of runs that complete without anybody opening them.

Timetable against actual

151.2h

Actual 156.3h, 5.1h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 44% of the dwellAgent2 stations and 39% of the dwellShared spine1 station and 17% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
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

Model cost per service

GBSCost Attribution Agentgbs9h 38m12h 1m34IT Service Management
2

Benchmark

AgentShowback Agentworkflow14h 56m33h 37m9Configuration Management Database
3

Draft finding

AgentBudget Tracking Agentworkflow7h 39m8h 54m8IT Service Management
4

CIO review

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

HumanDirector, IT Financial Managementpolicy25h 34m34h 59m2IT 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%
9 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 gates7 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
230.1h
9 items at 1,534 minutes of decision each.
Agent time a week
290h
1,933 minutes an item, which does not compete for a person.
Gate load
94%
Inside capacity, with 14.9h of headroom.
Stations without a person
75%
1 gate left on 4 stations.
Where an item spends its time
44% waiting on a person
56% in the agent lane
An item now takes 3,467 minutes of worked time end to end against 3,467 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 Unit Cost Read

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.

4 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

4 stations, nothing waiting, nothing sent back

0 min of 2.4 days

now Model cost per service · Cost Attribution Agent · 9.6 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 4.2 days

now Model cost per service · Cost Attribution Agent · 9.6 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

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

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

3 of 4 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 4 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
IT Finance Orchestrator
That orchestrator’s remit
Owns cost line work end to end inside Information Technology. Runs 3 lines across 14 stations, drains the repeatable share into the IT tower, and holds 3 human gates.
Accountable person
Director, IT Financial Management
Sub-function
IT Financial Management
Shared spine tower
it
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.