The catalogue Information TechnologyInfrastructure & CloudTransactional

Service IT4B

Cost Optimization

Runs transactional. Starts when a request lands in the queue. It runs 1,227 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 3 of them on the shared spine.

Runs a week

1,227

159 in flight right now.

Stations

1 person · 2 agent · 3 spine

Agent share of steps

83%

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

Decisions a person makes

Held by Director, Cloud Infrastructure.

Touchless

86%

Share of runs that complete without anybody opening them.

Timetable against actual

7.2h

Actual 9.0h, 1.8h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 30% of the dwellAgent2 stations and 14% of the dwellShared spine3 stations and 55% of the dwell5 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

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.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Detect waste	GBS	Capacity Agent	gbs	2h 59m	3h 48m	42	IT Service Management
2	Model saving	Agent	Cost Optimization Agent	workflow	20m	24m	41	Configuration Management Database
3	Auto-remediate low risk	GBS	Capacity Agent	gbs	2h 55m	4h 6m	25	IT Service Management
4	Owner approve Held for a named human when the unit exceeds the infrastructure change decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	Director, Cloud Infrastructure	policy	4h	6h 46m	8	IT Service Management
5	Apply	GBS	Capacity Agent	gbs	1h 20m	1h 55m	26	IT Service Management
6	Verify saving	Agent	Infrastructure Policy Agent	workflow	1h 34m	3h 1m	17	IT 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. more

Move something

Demand100%

1,227 a week is what the estate records. more

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 gates141 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. more

Person time a week

4,908h

1,227 items at 240 minutes of decision each.

Agent time a week

11,206.6h

548 minutes an item, which does not compete for a person.

Gate load

99%

Inside capacity, with 27h of headroom.

Stations without a person

83%

1 gate left on 6 stations.

Where an item spends its time

30% waiting on a person

70% in the agent lane

An item now takes 788 minutes of worked time end to end against 788 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 Cost Optimization

The simulation is arithmetic on the estate, not a queueing model. more

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking. more

6 stations, walked twice

Once clean, once with the categories the estate counts

This is the same unit on the same stations, breaking. more

No break below was chosen. more

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

6 stations, nothing waiting, nothing sent back

0 min of 13 hrs

now Detect waste · Capacity Agent · 3.0 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 27 hrs

now Detect waste · Capacity Agent · 3.0 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

4 counted categories land on this procedure. more

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen. more

The separation register records a duty conflict against a sub-function and a named post, not against one procedure. more

Two clocks run. Worked time is the sum of the time the work is actually being done … more

Live observability

Systems this service would touch

Attributed by rule from the function's system list. more

2 systems attributed

0 of 2 returning records

The system register

IT Service Management

ServiceNow ITSM · itsm · bidirectional · high

modeled

5 of 6 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 6 stations attributed here · read only

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Infrastructure Orchestrator
That orchestrator’s remit: Owns infrastructure change work end to end inside Information Technology. Runs 3 lines across 16 stations, drains the repeatable share into the IT tower, and holds 3 human gates.
Accountable person: Director, Cloud Infrastructure
Sub-function: Infrastructure & Cloud
Shared spine tower: it
Hand-over points: None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Capacity ResponseIT4A Backup AssuranceIT4C

What this page is and is not

This is a catalogue of the modeled estate. more