LensReading which lens this session carries.
The catalogueInformation TechnologyAsset & LicenseTransactional

Service IT9B

Renewal Cycle

Runs transactional. Starts when an upstream system posts an event. It runs 4,304 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 2 of them on the shared spine.

Runs a week

4,304

29 in flight right now.

Stations

5

1 person · 2 agent · 2 spine

Agent share of steps

80%

Autonomy on this service is set at 87% against a ceiling of 91%.

Decisions a person makes

1

Held by Director, IT Asset Management.

Touchless

92%

Share of runs that complete without anybody opening them.

Timetable against actual

6.0h

Actual 7.2h, 1.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 54% of the dwellAgent2 stations and 19% of the dwellShared spine2 stations and 27% of the dwell3 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
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 renewal

GBSDiscovery Agentgbs2h 37m4h 36m8IT Service Management
2

Model need

AgentLicense Reconciliation Agentworkflow1h 31m3h 16m7Configuration Management Database
3

Recommend

AgentRenewal Agentworkflow1h 4m1h 46m2IT Service Management
4

Owner approve

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

HumanDirector, IT Asset Managementpolicy7h 10m10h 51m1IT Service Management
5

Renew

Hands over at procurement

GBSDiscovery Agentgbs1h1h 31m11IT 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%
4,304 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 gates882 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
30,845.3h
4,304 items at 430 minutes of decision each.
Agent time a week
26,684.8h
372 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 24.7h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
54% waiting on a person
46% in the agent lane
An item now takes 802 minutes of worked time end to end against 802 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 Renewal 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 renewal · Discovery Agent · 2.6 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 27 hrs

now Detect renewal · Discovery Agent · 2.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

4 of 5 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Asset Orchestrator
That orchestrator’s remit
Owns license position work end to end inside Information Technology. Runs 3 lines across 15 stations, drains the repeatable share into the IT tower, and holds 5 human gates.
Accountable person
Director, IT Asset Management
Sub-function
Asset & License
Shared spine tower
it
Hand-over points
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.